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 custom fields 'Maintenance Event' and 'Trading Company Code' will leverage SAP’s standard F4 search functionality.
• Newly appended Z-fields to the PRPS table will also be incorporated into the field catalog used for validation and substitution rules.
• Newly appended Z-Fields to be available for WBS Element Field Selection.
• Newly appended Z-fields to the PRPS table must be incorporated into all relevant standard SAP Project System (PS) reports e.g. in ALV reports
• Newly appended Z-fields to the PRPS (WBS Element Master Data) table must also be explicitly extended to all WBS elements relevant CDS views.
• 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.
• Ensure fields CAPEX/OPEX & Maintenance Event for data migration purpose. 

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

Include an overview of the source

Data Validation Considerations

Include an overview of the data validation requirement

Custom Tables

N/A

Master Data

N/A

Configuration Table

N/A

Selection Screen Enhancement

N/A

Processing Logic

This section defines the detailed step-by-step logic implemented within the BAdI/User Exit to process the data received from the standard SAP program and database retrieval. It explains the operations performed on the data, the expected outcomes in different scenarios and how the system should behave in response to specific conditions.

Volumetrics

N/A

Performance Considerations

N/A

Error Handling

N/A

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

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

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