| Status | Approved |
|---|---|
| Owner | BIDALIA-ext, Kuldeep |
| Stakeholders | |
| Jira Request ID | ERP-21 - Getting issue details... STATUS |
| Jira Development ID | ERP-65 - Getting issue details... STATUS |
High- Level Specification
| Parameter | Value |
|---|---|
| Application System | S/4Hana ROW, S/4Hana China, S/4Hana CUI |
| Business Process Reference | 10.02.01.01. Manage Project/WBS Changes |
Functional Overview
Standard SAP WBS element tables offer foundational fields for project structuring, but they often need to be enhanced for business-specific attributes. Within the Syensqo business solution, some custom fields are introduced to capture critical dimensions such as financial nature (e.g., CAPEX/OPEX), operational context (e.g., Maintenance Event), and legal entity mapping (e.g., Trading Company Code). These fields will enable reporting, better compliance and cross-steam integration.
Scope and Objectives
Scope of the enhancement are-
- To add three new fields to the WBS element master data i.e. CAPEX/OPEX, Maintenance Event & Trading Company Code.
- Enable data entry, validation, and storage in the appropriate database tables.
Objective- Enable additional Syensqo specific fields for classification of WBS elements by financial nature (CAPEX/OPEX), operational context (e.g., Maintenance Event), and legal entity mapping (Trading Company Code).
N/A
Step | Description | Comment |
|---|---|---|
| 1 | Create a Capital project from PPM Item and maintain CAPEX/OPEX field in eligible WBS element. | CAPEX/OPEX field will be available with drop-down values for account assigned WBS elements. Select a WBS element and pick CAPEX in the field and save. Select another WBS element and pick OPEX in the field and save. |
| 2 | Create a Turnaround project from PPM Item and enter Maintenance Event in eligible WBS element. | For Turnaround Project where Project Type = "Turnaround Projects", Maintenance Event field will be available for maintenance (with standard search help options). |
| 3 | Create a Intercompany Recharges project and enter Trading Company Code in eligible WBS element. | Trading Company Code field will be available with drop-down values for account assigned WBS elements. Maintain Trading Company Code in a WBS element and save. |
Assumptions
- The addition of Z-fields within the standard table structure ensures that standard SAP functionality remains unaffected.
- The newly introduced custom fields will be seamlessly integrated into the SAP user interface across both Fiori and GUI, ensuring consistent availability within project and WBS specific applications and t-codes.
Dependencies
Security, Integrity and Controls
Standard authorization object checks will be applicable to the newly created Z-fields.
Configuration Requirements
N/A
Language Requirements
N/A
Special Requirements
N/A
Design Rationale
Functional Requirements
The I2M functional design introduces three custom fields to the WBS element master data i.e. CAPEX/OPEX, Maintenance Event, and Trading Company Code to enhance financial classification, maintenance tracking, and intercompany governance.
The CAPEX/OPEX field is mandatory and identifies whether the WBS element is intended for capital investment or expense capture, driving downstream reporting and settlement logic.
The Maintenance Event field is conditionally editable and applicable only to turnaround-specific WBS elements, allowing linkage to predefined maintenance cycles or events.
The Trading Company Code field is mandatory for intercompany recharge projects, ensuring accurate identification of the trading partner for billing and reconciliation.
All fields will be integrated into the WBS master data screen via a custom tab, with validation logic, dropdowns, and field help to support user experience, audit-readiness, and governance compliance.
Proposed Technology to Use
SAP provides for the development of WBS custom fields through in-app extensibility.
Data Source Considerations
| Table | Field Name | Comments/Calculation/Field Manipulation |
|---|---|---|
Data Validation Considerations
| Table | Field Name | Comments/Calculation/Field Manipulation |
|---|---|---|
Custom Tables
N/A
Master Data
N/A
| Field | Description | Data Type/Length | Validation rule/ Value Help |
|---|---|---|---|
Configuration Table
N/A
| Field | Description | Data Type/Length | Validation rule/ Value Help |
|---|---|---|---|
Selection Screen Enhancement
N/A
| Field Name | Description | Select: | Data Type/Length | Default Value/ Validation rule/ Value Help | Selection Logic |
|---|---|---|---|---|---|
Processing Logic
Create three custom fields on the WBS element (table PRPS) using the in‑app extensibility framework-
- CAPEX/OPEX
- Maintenance Event
- Trading Company Code
Field details-
| Field | CAPEX/OPEX | Maintenance Event | Trading Company Code |
|---|---|---|---|
| Description | CAPEX/OPEX | Maintenance Event | Trading Company Code |
| Field ID | SYCAP_OPX | SYMAIN_EVT | SYTRADE_CC |
| Table | PRPS | PRPS | PRPS |
| Field length | 8 | 8 | 4 |
| Data Type | CHAR | CHAR | CHAR |
| Data Element | Custom | REVNI | PS_PBUKR |
| Field Values | CAPEX OPEX Allow Blank | Standard Search help | Standard Search help |
Add in User Interface (SAP Fiori) | Yes | Yes | Yes |
| Add in WBS CDS Views | Yes | Yes | Yes |
Field catalog used for validation and substitution | Yes | Yes | Yes |
Add in WBS specific ALV reports | Yes | Yes | Yes |
Volumetrics
N/A
Performance Considerations
N/A
Error Handling
N/A
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 |