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. In Syway design, custom fields are introduced to capture business specific attributes for reporting, compliance and cross-steam integration.

Scope and Objectives

Following are the scope of this enhancement to enable reporting and compliance

• 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.

Process Flow Diagram

The diagram above illustrates the potential levels within the WBS where new custom fields could be integrated, depending on the nature of the project.

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 WBS specific applications and t-codes.

Dependencies

• New custom fields in WBS elements will be controlled using validation and substitution rules defined in the project profiles.

Security, Integrity and Controls

Standard WBS authorization object checks will be applicable to the newly created custom fields.

Configuration Requirements

N/A

Language Requirements

N/A

Special Requirements

N/A

Design Rationale

Functional Requirements

Custom fields are required on the WBS element master data i.e. CAPEX/OPEX, Maintenance Event, and Trading Company Code to report financial classification, maintenance tracking, and intercompany relevance.

• CAPEX/OPEX field is mandatory and identifies whether the WBS element is intended for capital investment or expense, driving downstream reporting and settlement.
• Maintenance Event field is conditionally editable and applicable only to WBS elements of project profiles "Capital/ Operational  Expense" and "Operational Expense", allowing linkage to predefined maintenance cycles or events.
• Trading Company Code field is mandatory for intercompany recharge projects, ensuring accurate identification of the trading partner for intercompany billing and reconciliation.

All fields will be available in the WBS master data screen with validation, dropdowns, and standard search help to support user experience, audit-readiness, and governance compliance.

Proposed Technology to Use

Custom fields for WBS elements will be created using SAP Enhancement Framework (CI Includes) and standard Append Structures. 

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-

To maintain future scalability, Project Profiles should not be hardcoded in the program.

Custom fields will be added to the WBS element screen. The exact tab/screen will be decided later.

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 (Capital/ Operational  Expense), ZPS0002 (Operational Expense), ZPS0003 (Statistical Expense), ZPS0004 (Intercompany Recharges), and ZPS0005 (Provisional Expense). Confirm that the three custom fields are visible in the WBS elements as per predefined logics.

Test Conditions and Expected Results

Test Considerations/Dependencies

• A2D team need to 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