| Status | |
|---|---|
| Owner | |
| Stakeholders | |
| Jira Request ID | |
| Jira Development ID |
High- Level Specification
| Parameter | Value |
|---|---|
| Application System | S/4Hana ROW, S/4Hana China, S/4Hana CUI |
| Business Process Reference | 10.01.01.04. Identify Initiatives and Items |
Functional Overview
The functional design of the enhancements describes the scenario(s) where enhancements to existing SAP programs are required.
Scope and Objectives
All Capital and Expense projects Structures will be initiated as Items in PPM with the exception of some Finance cost buckets (such as Recharge project and Statistical Projects). Once approved they will generate a corresponding PS Project so there is a 1:1 relationship between the Item and the PS Project.
Standard PPM provides system generated number for PPM items which is 24 digit number with FY Suffix. PS Project is automatically created and inherits this 24digit number which is not aligned with coding mask. The numbering is not ideal and have no mask or identification.
On the other hand PS allows coding masks which begin with an alphabet and provides a clear distinction of the type of project being (A-000001) Asset Project , (R-000001)R&I project, (E-000001) Expense Project. Project Coding mask is mandatory for Creating WBS elements and generating WBS numbers in a hierarchy.
In the same way Initiative number is required to be defined as alphanumeric coding mask IN-00001.
Therefore there is a need to enhance the PPM item number.
Step | Description | Comment |
|---|---|---|
1. | PPM Initiative | In standard PPM, the Initiative is automatically assigned a sequential 20-digit number, suffixed by current year as an identifier. This enhancement provides capability to customise ‘coding masks’ for the identifier so that they conform to a specific format. For example, the coding mask ‘IN-XXXXXX’ will generate sequentially numbered identifiers in the format IN-000001 etc. |
2. | PPM Item | In standard PPM, the Item is automatically assigned a sequential 20-digit number, suffixed by current year as an identifier. This enhancement provides capability to customize ‘coding masks’ for the identifier so that they conform to a specific format. For example, the coding mask ‘A-000000’ will generate sequentially numbered identifiers in the format A-000001 etc. The enhancement also provides for hierarchical Initiative -> Item coding masks, but this is not part of the Syway Design |
3. | PS Project Definition | The PS Project Identifier format is defined by a coding mask in standard PS configuration. The identifier of the PS Project will be inherited from the PPM Item from which it is generated, so the PPM and PS masks must align. |
4. | WBS Element | The WBS Element Identifier format is defined by the same PS coding mask and the Project Definition. The PS coding mask includes the format for hierarchical suffixes which are automatically generated based on the level of the WBS Element in the Project Hierarchy. For example, the coding mask “A-000000-XX-XX’ will generate the following identifiers: Level 1 – A-000001 Level 2 – A-000001-01 Level 3 – A-000001-01-01 |
Assumptions
There is separate numbering range defined for Rest of world, China and CUI instance, so the numbers do not overlap. Such as,
A-100000 to A-199999 in ROW Instance
A- 900000 to A-999999 in China
A- 800000 to A-899999 in CUI
Dependencies
None
Security, Integrity and Controls
There is no specific security required for this enhancement
Configuration Requirements
The following configuration will be completed, based on this enhancement:
- Number ranges for Initiative & Item identifiers
- Initiative coding mask
- Item coding mask
Language Requirements
Coding Mask will only be maintained in English
Special Requirements
Please refer to Assumptions section
Design Rationale
Functional Requirements
Please refer to the Scope and Objectives section
Proposed Technology to Use
Below SAP note to be implemented
Data Source Considerations
N/A
| Table | Field Name | Comments/Calculation/Field Manipulation |
|---|---|---|
Data Validation Considerations
N/A
| Table | Field Name | Comments/Calculation/Field Manipulation |
|---|---|---|
Custom Tables
None
Master Data
N/A
| 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
N/A
| 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
Please refer to the SAP Note in " Proposed Technology to use" Section
Volumetrics
- A coding mask configuration entry is required for each Item & Initiative Type approximately 25 Item types
- 3 number ranges are required; Capex Items, Expense Items, R&D Items, Initiatives
Performance Considerations
Item and Initiative Ids will be automatically generated in real-time on creation of the object
Error Handling
Any errors are to be written to the Item or Initiative message log as per standard PPM. Object Should not be created without number
Testing
How to Test
Test Conditions and Expected Results
| ID | Condition | Expected Result |
|---|---|---|
1 | Create a new Industrial Project with Qualification item | Item is assigned identifier according to Capex coding mask with next sequential number |
2 | Create a New Product Introduction Item | Item is assigned identifier according to R&D coding mask with next sequential number |
3 | Create a new Initiative | Initiative is assigned identifier according to Initiative coding mask with next sequential number |
4 | Create a New IT Small Project item | Item is assigned identifier according to Capex coding mask with next sequential number |
5 | Create a New Opex Project Item | Item is assigned identifier according to Expense coding mask with next sequential number |
6 | Update an existing Item and save | No impact on identifier |
7 | Update an existing Initiative and save | No impact on identifier |
8 | Approve Item and generate the PS Project | PS Project inherits same identifier as Item |
9 | Create new Item of same type in 3 instances | Item assigned identifier as per defined coding and number range |
Test Considerations/Dependencies
PPM Buckets are required for Testing
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.
