Status
Owner	NADAR-ext, Parvati
Stakeholders

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 like a 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 converting applicable active WBS - CAPEX/OPEX Settlement Rule from Legacy Source Systems into S/4HANA following the WBS - CAPEX/OPEX Settlement Rule Master Data Design Standard.

The data being sourced using DCT (Data Collection Template).

Relevancy criteria

The data from legacy system includes:

Settlement rules for Migrated WBS as per the scope of object 1026 - WBS - CAPEX, OPEX, Statistical.
Capex WBS Settlement rule to fixed asset - AUC cost to fixed asset
WBS Settlement Rule to PSG (Opex - R&I & Industrial WBS) - Rule generated automatically on execution of standard t-code (CJB1) mass generation of settlement rules
WBS Settlement Rule to Cost Centre (Opex - IT) - Rule generated automatically ?
WBS Settlement Rule to Cost Centre (Opex - Expense WBS budget managed) - Rule generated automatically on execution of standard t-code (CJB1) mass generation of settlement rules. Settlement receiver is the responsible Cost Centre as maintained in the WBS.
Provision WBS (with project profile ZPS0005) - Settlement rule to B/S GL account.

The data from legacy system excludes:

Capex WBS 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.
Settlement rule to superior WBS - Rule generated automatically on on execution of standard t-code (CJB1) mass generation of settlement rules (SAP Note 211324 implemented)
Capex / Opex WBS with assigned workorder - Rule generated automatically
Recharged Project (with project profile ZPS0004) WBS - No settlement required
Statistical Project (with project profile ZPS0003) WBS - Not applicable

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
DKOBR	EMPGE	ABR_EMP	Settlement Receiver	CHAR	40	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
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	EXTNR	COBR_EXTNR	Distribution Rule Number	NUMC	3	System Generated
			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 below:

SyWay Project > CNV-9102-WBS - CAPEX/OPEX Settlement Rule > image-2025-11-4_18-2-43.png

Data Privacy and Sensitivity

Not applicable

Extraction

The data is manually collected by the business directly in 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

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 will be created for WBS - Capex, Opex, Settlement Rule data with exception of some fields which require transformation as mentioned in the transformation rule.

WBS - Capex, Opex, Settlement Rule DCT Rules

Field Name	Field Description	Rule
OBJNR	WBS element	Sender WBS element that will have its costs settled. Rule: For WBS elements governed by CAPEX project profile ZPS0001, Account assignment element PRPS-BELKZ = active, WBS level PRPS-STUFE=3, with investment profile PRPS-IMPRF not blank and Capex flag PRPS-ZX01 b. G/L- G/L account - Account assignment category G/L specifies a receiver category of "G/L Account'. Rule: Provision WBS with project profile ZPS0005, WBS level PRPS-STUFE=2, Account assignment element PRPS-BELKZ = active It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template.
KONTY	Account Assignment Category	Account assignment category determine the type of settlement receiver type. a. FXA- Asset - Account assignment category FXA specifies a receiver category of "Fixed Asset". Required for AUC cost on Capex WBS to Settled to fixed asset. Rule - For WBS elements governed by CAPEX project profile ZPS0001, Account assignment element PRPS-BELKZ = active, WBS level PRPS-STUFE=3, with investment profile PRPS-IMPRF not blank and Capex flag PRPS-ZX01 not blank. It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template. b. G/L- G/L account - Account assignment category G/L specifies a receiver category of "G/L Account'. Rule - Provision WBS with project profile ZPS0005, WBS level PRPS-STUFE=2, Account assignment element PRPS-BELKZ = active It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template. Note: Account assignment category, CTR- Cost Center, PSG- Profitability Segment, WBS- WBS element are applicable for Automatic settlement rule
EMPGE	Settlement Receiver	Settlement receiver based on the account assignment category selected. For account assignment category - FXA- Asset, Capex WBS with project profile ZPS0001 as WBS per rule defined above, settlement receiver = Fixed asset For account assignment category - G/L- G/L account -Provision WBS with project profile ZPS0005 as per WBS rule defined above, settlement receiver = G/L Account It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template.
PROZS	Percent	This field specifies the percentage, at which costs collected in the sender object are distributed to the specified settlement receiver. Conditional field
BETRR	Amount	Fixed amount to be settled to settlement receiver. Conditional field
PERBZ	Settlement type	Settlement type determines whether costs are settled periodically or in a full settlement. Settlement rule with Account Assignment Category = FXA or G/L account, settlement type = FUL Full Settlement
GABPE	Valid From Period	Period value from which a distribution rule is applied to limit the validity duration of a distribution rule. Conditional field
GABJA	Valid From Year	Year value from which a distribution rule is applied to limit the validity duration of a distribution rule. Conditional field
GBISJ	To Period- Valid To	Period value up to which a distribution rule is applied to limit the validity duration of a distribution rule Conditional field
GBISP	To Fiscal Year- Valid to Year	Year value up to which a distribution rule is applied to limit the validity duration of a distribution rule. Conditional field
ANLN1	Settlement Receiver- Fixed Asset	For account assignment category - FXA- Asset, Capex WBS with project profile ZPS0001 as per rule defined above. It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template.
HKONT	Settlement Receiver- G/L Account	For account assignment category - G/L- G/L account -Provision WBS with project profile ZPS0005 as per rule defined above. It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template.
	Instance	Instance where the WBS Settlement Rule is to be loaded. (Field required in DCT)

DCT Rule applicable for Settlement rule generated automatically in S/4 Hana with transaction code CJB1 / CJB2

Field Name

Field Description

Rule

OBJNR

WBS element

Sender WBS element that will have its costs settled.

Account assignment to be active.

Rule applicable for Settlement rule generated automatically in S/4 Hana with transaction code CJB1

a. Automatic Settlement rule to PSG - For WBS elements governed by project profile ZPS0001 with WBS Project type PRPS-PRART = 17, 26, 27, 37. 38. 40 and project project = zsp0002 with WBS project type = 39, with Account assignment element PRPS-BELKZ = active, PRPS-ZX01 OPEX flag active.

b. Automatic Settlement rule to Cost Centre - For WBS elements governed by project profile ZPS0001 with WBS Project type PRPS-PRART = 18 and project project = zsp0002 with WBS project type = 26, 27, 41, with Account assignment element PRPS-BELKZ = active, PRPS-ZX01 OPEX flag active.

It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template.

Period

It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template.

Fiscal year

It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template.

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 is a 3-way activity involving the Business, Functional team and Data team. This identifies the transformation activity required to allow Syniti Migrate 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 Syniti Migrate
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	Obtain DCT Sign-off from Business	Data Team
2	Execute and Load and perform Transformation	Data Team
3	Monitor the transformation progress and ensure performance and completion is within allowed timeframe	Data team
4	Review and Validate Error and Preload Reports	Data Team
5	Generate data load count.	Data team
6	Generate Load Files	Data Team
7	Log errors as defects, if any and address resolutions. Close defects.	Data team
8	Re-transform and re-validate the Pre-load reports if necessary.	Data team
9	Validate the transformed file as part of pre-load validation, raise data defects or provide the pre-load sign-off.	Business
10	Analyze and resolve any pre-load defects logged by business.	Data team
11	Repeat steps 7 to 10 if necessary	Data team
12	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	DCT	COBRB	OBJNR	WBS element	S/4 Hana	COBRB	OBJNR	WBS element	Copy from source to target system
2	DCT	COBRB	KONTY	Account Assignment Category	S/4 Hana	COBRB	KONTY	Account Assignment Category	Copy from source to target system
3	DCT	COBRB	ANLN1 (Fixed Asset) HKONT (G/L Account)	Settlement Receiver	S/4 Hana	DKOBR	EMPGE	Settlement Receiver	Value Mapping: Old to new Fixed Asset for Account Assignment Category = FXA Value Mapping: Old to new G/L Account for Account Assignment Category = G/L
4	DCT	COBRB	PROZS	Percent	S/4 Hana	COBRB	PROZS	Percent	Copy from source to target system
5	DCT	COBRB	BETRR	Amount	S/4 Hana	COBRB	BETRR	Amount	Copy from source to target system
6	DCT	COBRB	PERBZ	Settlement Type	S/4 Hana	COBRB	PERBZ	Settlement Type	Copy from source to target system
7	DCT	COBRB	GABPE	From Period- Valid From Period	S/4 Hana	COBRB	GABPE	From Period- Valid From Period	Copy from source to target system
8	DCT	COBRB	GABJA	From Fiscal Year- Valid From Year	S/4 Hana	COBRB	GABJA	From Fiscal Year- Valid From Year	Copy from source to target system
9	DCT	COBRB	GBISJ	To Period- Valid To	S/4 Hana	COBRB	GBISJ	To Period- Valid To	Copy from source to target system
10	DCT	COBRB	GBISP	To Fiscal Year- Valid to Year	S/4 Hana	COBRB	GBISP	To Fiscal Year- Valid to Year	Copy from source to target system
11				Controlling area of receiver	S/4 Hana	COBRB			Default from the Receiver
12				Company Code	S/4 Hana	COBRB			Default

Transformation Mapping

Mapping Table Name	Mapping Table Description
Controlling Area	Value Mapping: Old to New Controlling Area
Cost Centre	Value Mapping: Old to New Cost Centre
Fixed Asset	Value Mapping: Old to New Fixed Asset
Controlling Area
Company Code

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

Pre-Load Validation

Project Team

Completeness

Task	Action
Verify Record Count	SyWay I2M Data Team to verify that the total number of relevant records from the DCT is equal to the total number of 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
Text Length Checks

Review Error Reports

Review and correct the errors. Achieve a zero-error record count as much as possible. Raise defects for data remediated and requiring a correction in the source (DCT) data.

Business

Completeness

Task	Action
Verify Record Count	Business Data Owner/s to verify that the total number of relevant records from the DCT is equal to 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 (and signed-off DCT data).

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	Load 3 records for < > to validate if data is loaded successfully without errors	Data Team
4	Proceed with full load if steps 2 and 3 are validated	Data Team
5	Validate few records loaded by accessing	Data Team
6	Generate post load report if step 5 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
1070	Fixed Asset
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,
3	Asset not in company Code	Correct upload data
4	G/L Account not in chart of account	Correct upload data
5	Cost Centre does not exist	Correct upload data

Post-Load Validation

Project Team

The following post-load validations will be performed by the 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.
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 SE16 download

Business

Completeness

Task	Action
Verify Count	Extract data in S/4 Hana via fiori tile and verify the count

Accuracy

Task	Action
Verify Count	Extract data in S/4 Hana via fiori tile and verify the count

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.

Any additional key assumptions.

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Target Design

Data Cleansing

Conversion Process

Data Privacy and Sensitivity

Extraction

Extraction Run Sheet

Extraction Dependencies

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