High- Level Specification

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

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

Indicate any dependencies or constraints that may impact this development, in terms of requirements from internal or external applications, other work streams, time constraints, data or system access restrictions. Also, please specify scheduling or process dependencies, e.g. interface/batch job that must run beforehand or process steps that need to be completed prior to executing this development.

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

Data Validation Considerations

Custom Tables

N/A

Master Data

N/A

Configuration Table

N/A

Selection Screen Enhancement

N/A

Processing Logic

Create three custom fields on the WBS element (table PRPS) using the in‑app extensibility framework-

1. CAPEX/OPEX 
2. Maintenance Event
3. Trading Company Code

Field details-

Relationship between WBS element and Project Profile- 

Pass WBS element in PRPS-PSPNR ad pick Project number from field PRPS-PSPHI. Pass Project Number in PROJ-PSPNR and read project profile PROJ-PROFL.  

Volumetrics

N/A

Performance Considerations

N/A

Error Handling

N/A

Testing

How to Test

Ensure that projects are created using the project profiles: ZPS0001, ZPS0002, ZPS0003, ZPS0004, and ZPS0005. Confirm that the three custom fields are visible in the WBS elements as per predefined logics.

Test Conditions and Expected Results

Test Considerations/Dependencies

• Project profiles must be configured exactly as specified to ensure proper validation of associated custom fields.
• A2D team should provide sample Maintenance Events for validation and testing purposes.

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

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.

Change log