# Project WBS Schedule Slippage Report (Basic, Forecast and Actual Dates)

> 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.

- Type: Report, Custom development, ALV report
- Module: PS
- Estimated effort: S (3–4 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/project-wbs-schedule-slippage-report/


## 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.

### Closest standard alternatives

- CN41N: Shows the project structure with dates; does not calculate the slip in days or filter by slip.
- CN53N: Lists milestones; does not show them on the same line as the WBS date slip.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| PROJ | Project definition | Read | - | ECC + S/4 |
| PRPS | WBS element: description, level and responsible person (driving table) | Read | PRPS-PSPHI = PROJ-PSPNR | ECC + S/4 |
| PRTE | WBS dates: basic, forecast and actual | Read | PRTE-POSNR = PRPS-PSPNR | ECC + S/4 |
| MLST | Milestones: planned and actual date | Read | MLST-PSPNR = PRPS-PSPNR | ECC + S/4 |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_PSPID | Project definition | Range / multiple | PROJ-PSPID | Yes |
| S_POSID | WBS element | Range / multiple | PRPS-POSID | No |
| S_VERNR | Responsible person | Range / multiple | PRPS-VERNR | No |
| S_PENDE | Basic finish date | Range / multiple | PRTE-PENDE | No |
| P_LEVEL | Maximum level | Single value | PRPS-STUFE | No |
| P_MINSL | Minimum slip (days) | Single value | - | No |
| P_MLST | Check milestones | Checkbox | - | No |
| P_KEYDT | Key date | Single value | SY-DATUM | Yes |

## Output columns

| Column | Source |
|---|---|
| Project | PROJ-PSPID |
| WBS element | PRPS-POSID |
| Description | PRPS-POST1 |
| Responsible | PRPS-VERNA |
| Basic start | PRTE-PSTRT |
| Basic finish | PRTE-PENDE |
| Forecast start | PRTE-PSTRM |
| Forecast finish | PRTE-PETRM |
| Actual start | PRTE-ISTRT |
| Actual finish | PRTE-IENDE |
| Start slip (days) | Calculated: (ISTRT, else PSTRM) − PSTRT |
| Finish slip (days) | Calculated: (IENDE, else PETRM) − PENDE; if neither exists and PENDE has passed, key date − PENDE |
| Overdue milestones | Calculated: Number of milestones with MLST-TEDAT < key date and empty MLST-LST_ACTDT |
| Status | Calculated: Green: slip ≤ 0; yellow: slip ≤ threshold; red: slip > threshold or overdue milestones exist |

## How does the report work?

1. PROJ and PRPS are read by project, WBS, responsible person and maximum level.
2. Dates are taken from PRTE: basic start / finish (PSTRT, PENDE), forecast start / finish (PSTRM, PETRM), actual start / finish (ISTRT, IENDE).
3. 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.
4. 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.
5. The minimum slip filter is applied; the status light is set from the finish slip and the number of overdue milestones.

## Authorization objects

- C_PROJ_KOK: Project display authorization by controlling area
- C_PRPS_VNR: WBS 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.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=ps-wbs-schedule-slippage
