High- Level Specification

Parameter	Value
Application System	SAP S/4HANA - CUI instanceSAP S/4HANA - China instance SAP S/4HANA - Rest of World instance
Business Process Reference	10.02.04.01. Manage Project Settlement and Closure

Functional Overview

This functional specification defines the custom development required to automatically replicate specific PPM Item User Statuses to linked PS Project and WBS Element User Statuses.
The enhancement ensures that when an Item in PPM is updated to statuses: TECO/Cancelled, Closed/Cancelled or On Hold, the corresponding PS User Status is automatically set on the associated Project Definition.

Scope and Objectives

Standard PPM to PS integration (via DFM configuration) supports mapping PPM Item Status to PS System Status only.
Since Cancelled and On Hold are User Statuses in PS, standard functionality cannot be used, requiring custom development.

The objectives of this Functional Specification are to ensure consistency between PPM and PS project status management by synchronizing User Statuses across both modules whenever a relevant status change occurs in PPM.

Assumptions

Dependencies

PPM item status configuration defined.

DFM configuration to synchronize PPM item status with SAP PS project system status.

SAP PS user statuses Cancelled and On Hold defined. 

Security, Integrity and Controls

Configuration Requirements

Language Requirements

Special Requirements

Design Rationale

Functional Requirements

1. Automatic Synchronization

When a user sets the Item Status in PPM to one of the below statuses:

• TECO/Cancelled 
• Closed/Cancelled
• On Hold

,The corresponding PS Project and its WBS Elements must automatically receive the corresponding PS User Status. 

PPM is the controlling application. Users must not manually adjust the PS status for these cases.

The solution must ensure aligned user statuses between PPM and PS at all times.

The update must occur:

• Immediately upon Item status change
• With error logging and alerting in case of failures

2. Reversibility

If the PPM item status is changed from On Hold, TECO/Cancelled or Closed/Cancelled to another allowed status as per PPM configuration, the status change must be reflected on the SAP PS project: 

3. If corresponding SAP PS status is locked for edit by a user, do not allow the change on the PPM item. Error message in PPM stating that the SAP PS project is currently being used by user id, and therefore the status change is not allowed. 

Proposed Technology to Use

Data Source Considerations

Data Validation Considerations

Custom Tables

Master Data

Configuration Table

Selection Screen Enhancement

Processing Logic

1. Detect change in Item Status.

If the field STATUS on the PPM item (table /RPM/ITEM_D) is changed to values On Hold, TECO/Cancelled, Closed/Cancelled:

• Identify related SAP PS Project definition: PPM item id = PS Project definition id.
• Set PS User Status on the SAP PS Project definition to the corresponding PS user status:

• • Set/remove User Status accordingly using: STATUS_CHANGE_IN_PROJECT or BAPI_BUS2001_SETSTATUS

2. If status is changed from On Hold, TECO/Cancelled, Closed/Cancelled to another value:

• Identify related SAP PS Project definition: PPM item id = PS Project definition id.

• Set/remove User Status accordingly using: STATUS_CHANGE_IN_PROJECT or BAPI_BUS2001_SETSTATUS

3. If the status update fails because the PS Project is locked:

• Display a meaningful error message to the PPM user: “Status update cannot be applied because Project <Project ID> is currently locked in SAP PS by user <username>. Please try again later.”

• The status change is not saved on the PPM item. 

• Log the failure in the PPM log or message queue.

Volumetrics

Unknown.

Performance Considerations

Error Handling

All failures logged in SLG1.

Testing

How to Test

Test Conditions and Expected Results

Test Considerations/Dependencies

Other Information

Development Details

Package

Enhancement Implementation

Other Development Objects

Appendix

Custom Authorization Group Naming Convention

This table is based on the Syensqo development standards document. It provides the naming conventions for authorization groups to associated with custom reports and tables to comply with security requirements.

See also

Change log