Project WBS Schedule Slippage Report (Basic, Forecast and Actual Dates)
Short answer: A custom ALV report that compares the basic start and finish dates of each WBS element with the forecast and actual dates, calculates the slip in days and counts milestones that are past due but not reached. It gives one list for the weekly project meeting.
- Estimated effort
- S · 3–4 working days
- System
- ECC and S/4HANA
- Tables
- 4
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
CN41N and CN43N show dates per object but do not calculate the slip in days between the basic finish and the forecast or actual finish, and cannot filter by slip. CN53N lists milestones separately and does not combine them with the WBS line. PMO teams calculate the slippage table in Excel every week.
Who uses it? Project managers, project scheduling and PMO teams.
Closest standard alternatives
Tables used
The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.
| Table | Role | Join | System |
|---|---|---|---|
| PROJProject Definition | Project definition | — | ECC + S/4 |
| PRPSWBS Element Master Data | WBS element: description, level and responsible person (driving table) | PRPS-PSPHI = PROJ-PSPNR | ECC + S/4 |
| PRTEScheduling Data for WBS Element | WBS dates: basic, forecast and actual | PRTE-POSNR = PRPS-PSPNR | ECC + S/4 |
| MLSTMilestone | Milestones: planned and actual date | MLST-PSPNR = PRPS-PSPNR | ECC + S/4 |
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_PSPID | Project definition | Range / multiple | PROJ-PSPID | Yes | P-26-0012 |
| S_POSID | WBS element | Range / multiple | PRPS-POSID | No | P-26-0012-* |
| S_VERNR | Responsible person | Range / multiple | PRPS-VERNR | No | 12 |
| S_PENDE | Basic finish date | Range / multiple | PRTE-PENDE | No | 01.10.2026 – 31.12.2026 |
| P_LEVEL | Maximum level | Single value | PRPS-STUFE | No | 3 |
| P_MINSL | Minimum slip (days) | Single value | — | No | 5 |
| P_MLST | Check milestones | Checkbox | — | No | X |
| P_KEYDT | Key date | Single value | SY-DATUM | Yes | 17.11.2026 |
Output columns
| # | Column | Source |
|---|---|---|
| 1 | Project | PROJ-PSPID |
| 2 | WBS element | PRPS-POSID |
| 3 | Description | PRPS-POST1 |
| 4 | Responsible | PRPS-VERNA |
| 5 | Basic start | PRTE-PSTRT |
| 6 | Basic finish | PRTE-PENDE |
| 7 | Forecast start | PRTE-PSTRM |
| 8 | Forecast finish | PRTE-PETRM |
| 9 | Actual start | PRTE-ISTRT |
| 10 | Actual finish | PRTE-IENDE |
| 11 | Start slip (days) | Calculated (ISTRT, else PSTRM) − PSTRT |
| 12 | Finish slip (days) | Calculated (IENDE, else PETRM) − PENDE; if neither exists and PENDE has passed, key date − PENDE |
| 13 | Overdue milestones | Calculated Number of milestones with MLST-TEDAT < key date and empty MLST-LST_ACTDT |
| 14 | Status | Calculated Green: slip ≤ 0; yellow: slip ≤ threshold; red: slip > threshold or overdue milestones exist |
Sample output
| Project | WBS element | Description | Responsible | Basic start | Basic finish | Forecast start | Forecast finish | Actual start | Actual finish | Start slip (days) | Finish slip (days) | Overdue milestones | Status |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| P-26-0012 | P-26-0012-01 | Engineering and design | S. Arslan | 02/01/2026 | 05/31/2026 | 02/03/2026 | 06/20/2026 | 2 | 20 | 0 | Yellow | ||
| P-26-0012 | P-26-0012-02 | Equipment procurement | M. Demir | 04/01/2026 | 10/31/2026 | 04/15/2026 | 12/15/2026 | 04/15/2026 | 14 | 45 | 2 | Red | |
| P-26-0012 | P-26-0012-03 | Site installation | E. Kaya | 11/01/2026 | 02/28/2027 | 11/10/2026 | 03/05/2027 | 11/12/2026 | 11 | 5 | 0 | Yellow | |
| P-26-0015 | P-26-0015-01 | Warehouse extension works | M. Demir | 03/01/2026 | 09/30/2026 | 03/01/2026 | 09/26/2026 | 0 | -4 | 0 | Green |
How does the report work?
- PROJ and PRPS are read by project, WBS, responsible person and maximum level.
- Dates are taken from PRTE: basic start / finish (PSTRT, PENDE), forecast start / finish (PSTRM, PETRM), actual start / finish (ISTRT, IENDE).
- Start slip = (actual start, else forecast start) − basic start. Finish slip = (actual finish, else forecast finish) − basic finish. If neither exists and the basic finish has passed, slip = key date − basic finish.
- Milestones assigned to the WBS element are read from MLST; those with a planned date (TEDAT) before the key date and an empty actual date (LST_ACTDT) count as overdue.
- The minimum slip filter is applied; the status light is set from the finish slip and the number of overdue milestones.
Performance notes
PRTE and MLST are small tables proportional to the number of WBS elements, so the report runs fast online. For forecast dates to be meaningful, the project team must update them regularly; otherwise the report shows the delay from the basic date to today.
Features
- ALV list (sort, filter, subtotals)
- User-specific layout variants
- Double-click drill-down to the document Double-clicking the WBS element opens CJ20N.
- Export to Excel
- Runs as a background job
- Send the result by email Red lines can be sent weekly to the responsible persons.
Authorization objects
- C_PROJ_KOKProject display authorization by controlling area
- C_PRPS_VNRWBS element authorization by responsible person
Frequently asked questions
Can network activity dates be included as well?
Yes. If activity level is needed, the same slip calculation is applied to the planned and actual dates in AFVV; this extends the effort range.
Can it compare against a project version (baseline)?
The base version uses the WBS basic dates as the reference. If a frozen baseline exists as a project version (CN72), the comparison can be extended to use the version data.
Does this report work on S/4HANA?
Yes. PRPS, PRTE and MLST are used in classic Project System on S/4HANA as well. On systems using enterprise projects, the scope is assessed separately.
Packages that include this solution
Project Budget and Schedule Controlling Pack
A pack that combines five reports for the project review meeting with one project definition and WBS selection: budget vs actual vs commitment, …
Related reports
Billing Milestones Reached but Not Invoiced Report
A custom ALV report that lists completed project milestones, those with an actual date, whose billing plan date in the sales order is still not …
WBS Budget vs Actual vs Commitment Report with Remaining Budget
A custom report that shows, for each WBS element, the current budget, plan, actual cost, requisition and order commitments, remaining budget and …
Let us build this report for your system
Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.