| Status | Approved |
|---|---|
| Owner | FRUTEAU-ext, Sabrina |
| Stakeholders | |
| Jira Request ID |
ERP-1018
-
Getting issue details...
STATUS
|
| Jira Development ID | ERP-714 - Getting issue details... STATUS |
High- Level Specification
| Parameter | Value |
|---|---|
| Application System | SAP S/4HANA - CUI instance  SAP S/4HANA - Rest of World instance |
| Business Process Reference |
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.
Step | Description | Comment |
|---|---|---|
| 1 | Trigger: User changes of PPM Item Status to:
| Upon saving, the PPM item status is updated. |
| 2 | System triggers the status change on the corresponding SAP PS project to Cancelled or On Hold. | Item changed to status On Hold => PS project status changed to On Hold Item changed to status TECO/Cancelled =>
Item changed to status Closed/Cancelled =>
|
| 3 | User changes the PPM item status from On hold to Approved. The system removed status On Hold on the corresponding PS project. | |
| 4 | User changes the PPM item status from TECO/Cancelled to Closed/Cancelled. PS project system status updated to Closed via DFM | |
| 5 | User changes the PPM item status from TECO/Cancelled to TECO. The system removed status Cancelled on the corresponding PS project. | |
| 6 | User changes the PPM item status from Closed/Cancelled to TECO/Cancelled. PS project system status updated to TECO via DFM. |
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
- 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:
| PPM item status From | To | Expected results |
| On Hold | Approved | Custom program deactivate user status On Hold on PS Project |
| On Hold | TECO | Custom program deactivate user status On Hold on PS Project |
| TECO/Cancelled | TECO | Custom program deactivate user status Cancelled on PS Project |
| TECO/Cancelled | Closed/Cancelled | Handled by DFM configuration. |
| Closed/Cancelled | TECO/Cancelled | Handled by DFM configuration. |
Proposed Technology to Use
Data Source Considerations
| Table | Field Name | Comments/Calculation/Field Manipulation |
|---|---|---|
Data Validation Considerations
| Table | Field Name | Comments/Calculation/Field Manipulation |
|---|---|---|
Custom Tables
Master Data
| Field | Description | Data Type/Length | Validation rule/ Value Help |
|---|---|---|---|
Configuration Table
| Field | Description | Data Type/Length | Validation rule/ Value Help |
|---|---|---|---|
Selection Screen Enhancement
| Field Name | Description | Select: | Data Type/Length | Default Value/ Validation rule/ Value Help | Selection Logic |
|---|---|---|---|---|---|
Processing Logic
Volumetrics
Performance Considerations
Error Handling
Testing
How to Test
Test Conditions and Expected Results
| ID | Condition | Expected Result |
|---|---|---|
Test Considerations/Dependencies
Other Information
Development Details
Package
| Package Name | Parent Package |
|---|---|
Enhancement Implementation
| Enhancement Type | Standard Definition Name | Custom Implementation Name | Design Rationale Reference |
|---|---|---|---|
Other Development Objects
| Object Type | Object Name | Purpose/High Level Logic | Design Rationale Reference |
|---|---|---|---|
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.
ABAP | ZFI | ZMM | ZPS | ZCO | ZSD | ZBC | ZFI | ZCA |
|---|---|---|---|---|---|---|---|---|
| TABLES | ZFIT | ZMMT | ZPST | ZCOT | ZSDT | ZBCT | ZFIT | ZCAT |