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

Compare with Current View Page History

« Previous Version 8 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 CAPEX in the field and save.

2Create a Capital 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 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.
  • Ensure fields CAPEX/OPEX & Maintenance Event for data migration purpose. 

Dependencies

Security, Integrity and Controls

Standard authorization object checks will be applicable to the newly created Z-fields.


Configuration Requirements

Language Requirements

Special Requirements


Design Rationale

Functional Requirements

Proposed Technology to Use

Data Source Considerations

TableField NameComments/Calculation/Field Manipulation











Data Validation Considerations

TableField NameComments/Calculation/Field Manipulation













Custom Tables

Master Data

FieldDescriptionData Type/LengthValidation rule/ Value Help









Configuration Table

FieldDescriptionData Type/LengthValidation rule/ Value Help








Selection Screen Enhancement

Field NameDescription

Select:

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













Processing Logic



Volumetrics


Performance Considerations



Error Handling


Testing

How to Test

Test Conditions and Expected Results

IDConditionExpected Result










Test Considerations/Dependencies


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. 8) 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