You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Next »

Status

  Approved

OwnerBIDALIA-ext, Kuldeep 
Stakeholders
Jira Request ID

ERP-21 - Getting issue details... STATUS

Jira Development ID

ERP-65 - Getting issue details... STATUS

High- Level Specification

ParameterValue
Application SystemS/4Hana ROW, S/4Hana China, S/4Hana CUI
Business Process Reference10.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).


Process Flow Diagram

N/A


Step

Description

Comment

1Create 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.

2Create 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).

3Create 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


TableField NameComments/Calculation/Field Manipulation
PRPSSYMAIN_EVTData source for this field will be T352R-REVNR. 
PRPSSYTRADE_CCData source for this field will be T001-BUKRS


Data Validation Considerations


TableField NameComments/Calculation/Field Manipulation
PRPSSYMAIN_EVTUpon submission with incorrect field values, this field should raise a standard validation error as defined by data element REVNI
PRPSSYTRADE_CCUpon submission with incorrect field values, this field should raise a standard validation error as defined by data element PS_PBUKR


Custom Tables

N/A

Master Data

N/A

FieldDescriptionData Type/LengthValidation rule/ Value Help









Configuration Table

N/A

FieldDescriptionData Type/LengthValidation rule/ Value Help








Selection Screen Enhancement

N/A

Field NameDescription

Select:

Data Type/LengthDefault Value/ Validation rule/ Value HelpSelection Logic












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-

Field CAPEX/OPEXMaintenance EventTrading Company Code
DescriptionCAPEX/OPEXMaintenance EventTrading Company Code
Field IDSYCAP_OPXSYMAIN_EVTSYTRADE_CC
TablePRPSPRPSPRPS
Field length884
Data TypeCHARCHARCHAR
Data ElementCustomREVNIPS_PBUKR
Field Values

CAPEX

OPEX

Allow Blank

Standard Search helpStandard Search help

Add in User Interface

(SAP Fiori)

Yes

YesYes
Add in WBS CDS Views

Yes

YesYes

Field catalog used for validation and substitution

Yes

Yes Yes 

Add in WBS specific ALV reports

Yes

YesYes

Applicable Project Profiles

This field is applicable to WBS elements across all project profiles

This field is applicable to WBS elements where project profile is ZPS0001 i.e. "Capital/ Operational Expenses". PROJ-PROFL = ZPS0001This field is applicable to WBS elements where project profile is ZPS0004 i.e. "Intercompany Recharges". PROJ-PROFL = ZPS0004

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

IDConditionExpected Result
1.1

Create a project using project profile ZPS0001 and structure WBS elements up to level 4.


Custom field "CAPEX/OPEX" & "Maintenance Event" will appear against all WBS elements. 

The custom field 'Trading Company Code' will not be displayed on the WBS element screen.

1.2

Check drop down values in "CAPEX/OPEX" field

Drop down field selection will allow any of CAPEX, OPEX or blank entry.

No text entry will be allowed.

1.3

Check search help of the "Maintenance Event" field

Standard "Revision" search help will appear allowing selection of a Maintenance Event with following search criteria categories-


1.4

Enter invalid data in the 'Maintenance Event' field and submit the entry

A standard error message will be triggered by the system

2

Create a project using project profile ZPS0002 and structure WBS elements up to level 3.


Custom field "CAPEX/OPEX" will appear against all WBS elements. 

The custom fields 'Maintenance Event' and 'Trading Company Code' are not displayed on the WBS element screen.

3

Create a project using project profile ZPS0003 and structure WBS elements up to level 2.


Custom field "CAPEX/OPEX" will appear against all WBS elements. 

The custom fields 'Maintenance Event' and 'Trading Company Code' are not displayed on the WBS element screen.

4.1

Create a project using project profile ZPS0004 and structure WBS elements up to level 2.


Custom field "CAPEX/OPEX" will appear against all WBS elements. 

Custom field "Trading Company Code" will appear against all WBS elements. 

The custom fields 'Maintenance Event' will not be displayed on the WBS element screen.

4.2

Check search help of the "Trading Company Code" field


Standard "Company Code" search help will appear allowing selection of a single company code.

4.3

Enter invalid data in the 'Trading Company Code' field and submit the entry

A standard error message will be triggered by the system

5

Create a project using project profile ZPS0005 and structure WBS elements up to level 2.


Custom field "CAPEX/OPEX" will appear against all WBS elements. 

The custom fields 'Maintenance Event' and 'Trading Company Code' are not displayed on the WBS element screen.

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

Package NameParent Package




Enhancement Implementation

Enhancement TypeStandard Definition NameCustom Implementation NameDesign Rationale Reference









Other Development Objects

Object TypeObject NamePurpose/High Level LogicDesign 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

ZFIZMMZPSZCOZSDZBCZFIZCA
TABLESZFITZMMTZPSTZCOTZSDTZBCTZFITZCAT

See also


No files shared here yet.

Change log

Version Published Changed By Comment
CURRENT (v. 17) Apr 29, 2026 10:53 BIDALIA-ext, Kuldeep
v. 45 Apr 27, 2026 11:36 BIDALIA-ext, Kuldeep
v. 44 Nov 24, 2025 12:22 WEINERT-ext, Patrick
v. 43 Nov 18, 2025 13:46 BIDALIA-ext, Kuldeep
v. 42 Nov 18, 2025 13:39 BIDALIA-ext, Kuldeep
v. 41 Nov 18, 2025 13:30 BIDALIA-ext, Kuldeep
v. 40 Nov 18, 2025 13:22 UPADHYAY-ext, Anjali
v. 39 Nov 18, 2025 13:17 BIDALIA-ext, Kuldeep
v. 38 Nov 18, 2025 13:16 UPADHYAY-ext, Anjali
v. 37 Nov 18, 2025 13:08 BIDALIA-ext, Kuldeep

Go to Page History

  • No labels