Status

Page Status

Owner

Stakeholders

KOHN-ext, Jacob BOYAR-ext, Sandeep AGGARWAL-ext, Vikhyat STEFANESCU-ext, Aurelia BIDALIA-ext, Kuldeep UPADHYAY-ext, Anjali AIT BOUDAOUD-ext, Boubekeur BECHTER-ext, Alex

Purpose

The purpose of this document is to define the conversion approach to create WBS - CAPEX/OPEX Settlement Rule in S/4 HANA.

Settlement rule is a set of parameters that defines how costs are transferred from a project's sender WBS element to receivers, such as a General Ledger account, Cost Centre, Asset Under Construction, fixed Asset, Profitability Segment, Superior WBS element.

Conversion Scope

The scope of this document covers the approach for creating settlement rule for the migrated WBS from Legacy Source Systems into S/4HANA.

The data from legacy system includes:

Provision WBS (with project profile ZPS0005) - Settlement rule to B/S GL account.
Recharged Project (with project profile ZPS0004) - Settlement rule to G/L account 7930010.

The data from legacy system excludes:

Capex WBS (with project profile ZPS0001) Settlement Rule for AUC generation - Rule generated automatically once Capex WBS (account assigned and having investment profile) is released and first settlement run is done.
WBS Settlement rule to fixed asset.
Statistical Project (with project profile ZPS0003) WBS - Not applicable

Note: For below scenarios, settlement rule is generated automatically (Mass Settlement rule generation - CJB1)

WBS Settlement Rule to PSG
WBS Settlement Rule to Cost Centre (Jira - ERP-315)
Settlement rule to superior WBS - (Pre-requisite SAP Note 211324 implemented as per FS ERP-315)

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
DCT	All Records		S/4HANA	TBD

Additional Information

Multi-language Requirement

Not applicable

Document Management

Not applicable

Legal Requirement

Not applicable

Special Requirements

Not applicable

Target Design

The technical design of the target for this conversion approach.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
COBRB	OBJNR	J_OBJNR	WBS element	CHAR	22	Mandatory
COBRB	KONTY	KONTY	Account Assignment Category	CHAR	2	Mandatory
COBRB	PROZS	BRGPROZS	Percent	DEC	5	Conditional
COBRB	BETRR	BETRR	Amount	CURR	23	Conditional
COBRB	PERBZ	PERBZ_LD	Settlement Type	CHAR	3	System Generated
COBRB	EXTNR	COBR_EXTNR	Distribution Rule No.	NUMC	7	System Generated
COBRB	SRSTRAT	SR_STRAT	Strategy	CHAR	3	System Generated
COBRB	GABPE	GABPE	From Period- Valid From Period	NUMC	3	Conditional
COBRB	GABJA	GABJA	From Fiscal Year- Valid From Year	NUMC	4	Conditional
COBRB	GBISJ	GBISJ	To Period- Valid To	NUMC	4	Conditional
COBRB	GBISP	GBISP	To Fiscal Year- Valid to Year	NUMC	3	Conditional
COBRA	APROF	APROF	Settlement Profile	CHAR	6	System Generated
COBRA	ABSCH	BRGABSCH	Allocation Structure for Settlement/Assessment	CHAR	6	System Generated
COBRB-	KOSTL	BRGKOSTL	Settlement Receiver- Cost Center	CHAR	10	System Generated
COBRB	PAOBJNR	RKEOBJNR	Settlement Receiver- Profitability Segment	CHAR	10	System Generated
COBRB	HKONT	SAKNR	Settlement Receiver- G/L Account	CHAR	10	Mandatory
COBRB	PS_PSP_PNR	PS_PSP_PNR	Work Breakdown Structure Element (WBS Element)	NUMC	8	System Generated
COBRB	EXTNR	COBR_EXTNR	Distribution Rule Number	NUMC	3	System Generated
COBRB	BWAER	BRGBWAER	Currency for the amount in the amount rule	CUKY	5	System Generated
COBRB	KOKRS	BRGKOKRS	Controlling Area of Receiver	CHAR	4	System Generated
COBRB	BUKRS	BUKRS	Company Code	CHAR	4	System Generated
COBRB	SRSTRAT	SR_STRAT	Strategy for automatic generation of settlement rules	CHAR	3	System Generated

Data Cleansing

Data object WBS - Capex, Opex, Settlement Rule will be collected specifically for data migration.

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
		Not applicable

Conversion Process

The high-level process is represented by the diagram

N/A

Data Privacy and Sensitivity

Not applicable

Extraction

The data is manually collected directly in the Syniti Migrate. This is to be conducted using DCT (Data Collection Template) in Syniti Migrate. The agreed Relevancy criteria is applied to the extracted records to identify the records that are applicable for the Target loads

Extraction Run Sheet

Req #	Requirement Description	Team Responsible
1	Ensure DCT is collected	Data Team
2	Perform preliminary completeness check, data quality check.	Data Team
3	Raise issues as defects if Req # 1 to 2 are not met	Data Team
4	Repeat Req # 1 to 3 if required	Data Team

Selection Screen

Selection Ref Screen	Parameter Name	Selection Type	Requirement	Value to be entered/set
Not Applicable

Data Collection Template (DCT)

Target Ready Data Collection Template not required, as pre-load file be created based on the transformation logic.

Extraction Dependencies

No Dependencies for Extract

Item #	Step Description	Team Responsible
	Not applicable

Transformation

The Target fields are mapped to the applicable Legacy field that will be its source, this activity involving the Business and Data team. This identifies the transformation activity required to allow to make the data Target ready:

Perform value mapping and data transformation rules.
1. Legacy values are mapped to the to-be values (this could include a default value)
2. Values are transformed according to the rules defined in
Prepare target-ready data in the structure and format that is required for loading via prescribed Load Tool. This step also produces the load data ready for business to perform Pre-load Data Validation

Transformation Run Sheet

Item #	Step Description	Team Responsible
1	Execute and Load and perform Transformation	Data Team
2	Monitor the transformation progress and ensure performance and completion is within allowed timeframe	Data team
3	Review and Validate Error and Preload Reports	Data Team
4	Generate data load count.	Data team
5	Generate Load Files	Data Team
6	Log errors as defects, if any and address resolutions. Close defects.	Data team
7	Re-transform and re-validate the Pre-load reports if necessary.	Data team
8	Validate the transformed file as part of pre-load validation, raise data defects or provide the pre-load sign-off.	Business
9	Analyze and resolve any pre-load defects logged by business.	Data team
10	Repeat steps 7 to 10 if necessary	Data team
11	Proceed to pre-load validations	Data team

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	S/4 Hana	PRPS	OBJNR	WBS element	S/4 Hana	COBRB	OBJNR	WBS element	Copy from source to target system Provision WBS with Project type PRPS-PRART = Restructuring Provision, Safety and Environment Provision, IAS19 Provision, Environmental Fines, Social Fines, Corruption Fines, PRPS-STUFE=2, project profile, PROJ-PROFL = ZPS0005 Recharged Project WBS, with Project type PRPS-PRART = 15 Intercompany Recharge PRPS-STUFE=2, project profile, PROJ-PROFL = ZPS0005
2					S/4 Hana	COBRB	KONTY	Account Assignment Category	Default = G/L (G/L Account)
3	S/4 Hana	COBRB	HKONT	Settlement Receiver	S/4 Hana	COBRB	HKONT	Settlement Receiver	Rule 1: Provision project WBS Settlement receiver from target S/4 from template Project starting with code 'T-' and its level 2 WBS with project type = Restructuring Provision, Safety and Environment Provision, IAS19 Provision, Environmental Fines, Social Fines, Corruption Fines Get WBS PRPS-OBJNR having code PRPS-PSPID = 'T-' with project type PRPS-PRART = 1Restructuring Provision, Safety and Environment Provision, IAS19 Provision, Environmental Fines, Social Fines, Corruption Fines, PRPS-STUFE=2 and pass in COBRB-OBJNR for Account Assignment Category COBRB-KONTY = G/L account, get Settlement Receiver = COBRB-HKONT Note: WBS with project type =IAS19 Provision multiple template WBS exist, lookup the WBS description PRPS-POST1 for all such template WBS and get the Gl account from COBRB for respective WBS as settlement receiver. Rule 2: Recharged Project WBS Settlement Receiver = 7930010
4					S/4 Hana	COBRB	PERBZ	Settlement Type	System generated 'Full - Full Settlement'
5					S/4 Hana	COBRB	EXTNR	Distribution Rule No.	System Generated
6				Settlement Profile	S/4 Hana	COBRA	APROF	Settlement Profile	Default from project profile
7				Allocation Structure for Settlement/Assessment	S/4 Hana	COBRA	ABSCH	Allocation Structure for Settlement/Assessment	Default from Settlement profile
8				Controlling area of receiver	S/4 Hana	COBRB	KOKRS	Controlling area of receiver	Default WBS controlling area PRPS-PKOKR
9				Company Code	S/4 Hana	COBRB	BUKRS	Company Code	Default WBS company code PRPS-PBUKR

Transformation Mapping

Mapping Table Name	Mapping Table Description

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
	Ensure all the fields that require value mapping, as stipulated. Mapping tables, have the correct values mapped and imported into tool.	Syway Data Team
	For provision project WBS, template project WBS to have settlement rule maintained	Syway Data Team

Pre-Load Validation

Project Team

Completeness

Task	Action
Verify Record Count	SyWay I2M Data Team to verify that the total number of relevant records in the Preload and Load Sheets.

Accuracy

Task

Action

Conversion Accuracy

SyWay I2M Data Team to verify that all fields below meet pass the checks:

Mandatory Fields
Field and Value Mapping Correctness
Null Checks

Review Error Reports

Review and correct the errors. Achieve a zero-error record count as much as possible.

Business

Completeness

Task	Action
Verify Record Count	Business Data Owner/s to verify that the total number of records in the Preload and Load Sheets.

Accuracy

Task	Action
Conversion Accuracy	Business Data Owner/s to verify that all the data in the load table/file is accurate as per endorsed transformation/mapping rules.

Load

The load process includes:

Execute the automated data load into target system using load tool or product the load file if the load must be done manually
Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation

Load Run Sheet

Item #	Step Description	Team Responsible
1	Load using transaction custom upload / custom fiori app	Data Team
2	Load 3 records for < > to validate if data is loaded successfully without errors	Data Team
3	Proceed with full load if steps 2 is validated	Data Team
4	Validate few records loaded by accessing	Data Team
5	Generate post load report if step 4 is validated	Data Team

Load Phase and Dependencies

Configuration

Item #	Configuration Item
1	Controlling Area
2	Operating Concern
3	Project Profile
4	Determine Strategy for Settlement Rule
5	Settlement Profile
6	Assign Strategy to Project Profile
7	Create Allocation Structure

Conversion Objects

Object #	Preceding Object Conversion Approach
1067	GL Operational
1026	WBS - Capex, Opex, Statistical

Error Handling

Error Type

Error Description

Action Taken

1

Receiver missing for distribution rule

Correct upload data,

Enter the missing receiver

2

WBS element does not exist

Correct upload data,

4

G/L Account not in chart of account

Correct upload data

Post-Load Validation

Project Team

Completeness

Task

Action

Verify Count

SyWay I2M Data Team to verify the record count created in target S/4 HANA by accessing post load reports from S/4 HANA.

CNSETTLRULE - Project Settlement Rule

Verify Logs

Check if there is data that failed to load and perform the necessary actions (e.g. register as post load issue or attempt to load the record again, etc.).

Accuracy

Task	Action
Conversion Accuracy	Verify that the tables in target S/4 HANA were loaded correctly via report CNSETTLRULE - Project Settlement Rule

Business

Completeness

Task	Action
Verify Count	Extract data from PS report CNSETTLRULE - Project Settlement Rule in S/4 Hana

Accuracy

Task	Action
Verify Count	Extract data from PS report CNSETTLRULE - Project Settlement Rule in S/4 Hana

Key Assumptions

Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
WBS - Capex, Opex, Settlement Rule is in scope based on data design and any exception requested by business.
For WBS automatic settlement rule generation, required enhancement that will be in place.

Change log

Change History

limit	10

Mar 20, 2026	Actor	Type	Activity	Version
Revision in Progress	VILLI-ext, Ramaraj	Comment	commented 8:21 am Could you please update the PROFL value for Recharge Project WBS?
Mar 18, 2026
	WENNINGER-ext, Sascha	State	changed state to Revision in Progress at 5:50 pm	v38
Mar 09, 2026
Edited following Approval	VILLI-ext, Ramaraj	Comment	commented 1:07 pm Could you please add one row for POSID as well.
		Comment	commented 12:11 pm Could you please let us know on how to fetch the Settlement profile value from Project profile Configuration (i.e. Tables and fields)?
		Comment	commented 12:07 pm Could you please let us know on how to fetch the Settlement profile value from Project profile Configuration (i.e. Tables and fields)?
Mar 05, 2026
	NADAR-ext, Parvati	Edit	updated the page at 9:56 am
	NADAR-ext, Parvati	State	changed state to Edited following Approval at 8:56 am	v38
Dec 15, 2025
Approved	TAN-ext, Charmaine	State	changed state to Approved at 1:53 pm (State override) [PMO Comments] Conversion Spec completed as per CS register and functional review completed	v37

Workflow history

Space shortcuts

Page tree

Versions Compared

Old Version 37

New Version Current

Key

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Target Design

Data Cleansing

Conversion Process

Extraction

Transformation

Transformation Run Sheet

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

Load Run Sheet

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

See also

Change log

Workflow history

Space shortcuts

Page tree

Page History

Versions Compared

Old Version 37

New Version Current

Key

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Target Design

Data Cleansing

Conversion Process

Extraction

Transformation

Transformation Run Sheet

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

Load Run Sheet

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

See also

Change log