| Status | |
|---|---|
| Owner | FRUTEAU-ext, Sabrina |
| Stakeholders | The business stakeholders involved in making, reviewing, and endorsing this decision. Type @ to mention people by name |
| Jira Request ID | |
| Jira Development ID |
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.
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.
Enable proper project governance and control by ensuring operational PS structures are immediately aligned with the lifecycle decisions made in PPM.
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
To detail the security requirements for processing this enhancement, any data integrity issues associated with the object and the teams that will be responsible for processing the object, i.e. authorization/roles required to who can execute the enhancements, etc.
- Custom Tables, enhancement, transaction codes, programs, Web Dynpro Application, Code Data Services (CDS), Open Data Protocol (OData), BI reports, and Functional Modules need to have at least one authority check either standard or custom. (custom should be an exception)
- All custom tables will be maintained in a certain Authorization Group (example: ZFIN, etc.)
- In the case of transaction codes an additional check other than the object S_TCODE is required. You can use SU24 to find the related authorization objects to check.
All other WRICEFs
- If the authorization check is already performed in the calling Programs, this section can be filled as “Follow calling programs authorization check” (example : BADI to redirect DMS to OpenText, in which the calling Manage Purchase requisition Fiori App already performed authorization check)
- If the authorization check is not checked in any of the development, this section should be filled with the proposed authorization check. You can refer to SU24 to see the standard authorization objects. (example: full custom Fiori App to enable user to download/upload the project plan)
Configuration Requirements
Specify the configuration requirements for this object. Like in case of substitution/ routine specify the configuration needed
Language Requirements
Specify the language requirements for this object. Specify the required language and type of translation, like labels, data.
Special Requirements
Specify any special requirements or considerations that may impact the enhancement based on specific locations, regulatory compliance or system limitations. Clearly outline requirements e.g. localization rules for countries like China
If the enhancement interacts with third-party systems such as Icertis, describe any additional integration, security or authentication considerations that must be taken into account.
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:
| From | To | Expected behavior |
| 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 | TECO system status handled by DFM configuration. User status Cancelled is already assigend to PS project. |
| Closed/Cancelled | TECO/Cancelled | Closed system status handled by DFM configuration. User status Cancelled is already assigned to 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
Typically, an enhancement will be based on an existing SAP BADI / user exit. If this is the case, please provide the proposed details of the BADI / user exit.
Data Source Considerations
Include an overview of the source. Can be deleted if not needed.
| Table | Field Name | Comments/Calculation/Field Manipulation |
|---|---|---|
| /RPM/ITEM_D | STATUS | Check PPM item status assigned |
| TJ30 | ESTAT, TXT04, TXT30 | SAP PS user statuses definition table |
| /RPM/STATUS_T | STATUS, TEXT | PPM item status definition table |
Data Validation Considerations
Include an overview of the data validation requirement. Can be deleted if not needed.
| Table | Field Name | Comments/Calculation/Field Manipulation |
|---|---|---|
Custom Tables
If any custom configuration tables are required, which will be read by the enhancement logic, then specify them here. Can be deleted if not needed.
Master Data
<Title Custom Table 1>
<Include an overview of the table and what it’s used for>
| Field | Description | Data Type/Length | Validation rule/ Value Help |
|---|---|---|---|
Configuration Table
Title Configuration Table 1
Include an overview of the table and what it’s used for
| Field | Description | Data Type/Length | Validation rule/ Value Help |
|---|---|---|---|
Selection Screen Enhancement
This section will give the details on the selection screen parameters, parameter type and whether it’s obligatory or not. This section can be used to define the Import Export parameters for Function Module or User Exit or Screens. Can be deleted if not needed.
| Field Name | Description | Select: Option or Parameter Check box or Radio button Import or Export | Data Type/Length | Default Value/ Validation rule/ Value Help | Selection Logic |
|---|---|---|---|---|---|
Processing Logic
- Detect change in Item Status.
If the field STATUS on the PPM item 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:
PPM Status | Corresponding SAP PS User status |
On Hold | On Hold |
TECO/Cancelled | Cancelled |
Closed/Cancelled | Cancelled |
- 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
From | To | Expected results |
On Hold | Approved | Deactivate user status On Hold on PS Project |
On Hold | TECO | Deactivate user status On Hold on PS Project |
TECO/Cancelled | TECO | Deactivate user status Cancelled on PS Project |
TECO/Cancelled | Closed/Cancelled | Check that user status Cancelled is already assigned to PS project. If not, Set. |
Closed/Cancelled | TECO/Cancelled | Check that user status Cancelled is already assigned to PS project. If not, Set. |
Volumetrics
Unknown.
Performance Considerations
Specify if there are any specific performance factors that need to be taken into consideration during development i.e. enhancement must be able to be executed by 10 users at the same time, etc.
Error Handling
Detail how errors will be handled: Notification, Restart/ Recovery and Re-Processing Procedures
Testing
How to Test
Please provide some guidance and/or test data to help the developer unit test the enhancement. Please include both positive and negative testing (to validate error situations handling). The developer will need to test repeatedly, so where appropriate provide instructions to reverse the actions performed so the test may be run again or explain how to create new input data to the test. The developer will need logons for test users representing the various roles within the approval process.
Test Conditions and Expected Results
| ID | Condition | Expected Result |
|---|---|---|
| 1 | Create 3 PPM items and approve the first Stage Gate to trigger the PS Project creation. | SAP PS project created with same id as PPM item. |
| 2 | Change the projects status to:
| Statuses are replicated to the corresponding SAP PS projects. |
| 3 | Change again the statuses on the 3 projects:
| Changes are reflected to the SAP PS project. |
| 4 |
Test Considerations/Dependencies
List any considerations essential for application test planning (e.g., test this before ABC along with DEF separate from GHI). If the development encompasses a user interface, explain how to test it. List any insights as to how this component could be tested the most efficiently.
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 |
See also
Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.
