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:

1. Settlement rules for Migrated WBS as per the scope of object 1026 - WBS - CAPEX, OPEX, Statistical.

The data from legacy system excludes:

1. Capex WBS Settlement Rule for AUC generation - Rule generated automatically
2. Settlement rule to superior WBS - Rule generated automatically
3. Settlement rule to fixed asset - Rule generated automatically
4. Recharged Project (with project profile ZPS0004) WBS - No settlement required
5. Capex / Opex WBS workorder - Rule generated automatically
6. Settlement Rule to PSG - Rule generated automatically
7. Opex IT ?? 

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

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
COBRB	PROZS	BRGPROZS	Percent	DEC	5
COBRB	AQZIF	AQZIF	Equivalence No.	DEC	10
COBRB	BETRR	BETRR	Amount	CURR	23
COBRB	BRTYP	BRTYP	Amount Rule Type	CHAR	2
COBRB	PERBZ	PERBZ_LD	Settlement Type	CHAR	3
COBRB	EXTNR	COBR_EXTNR	Distribution Rule No.	NUMC	7
COBRB	SRSTRAT	SR_STRAT	Strategy	CHAR	3
COBRB	GABPE	GABPE	From Period- Valid From Period	NUMC	3
COBRB	GABJA	GABJA	From Fiscal Year- Valid From Year	NUMC	4
COBRB	GBISJ	GBISJ	To Period- Valid To	NUMC	4
COBRB	GBISP	GBISP	To Fiscal Year- Valid to Year	NUMC	3
COBRA	APROF		Settlement Profile
COBRB-	KOSTL	BRGKOSTL	Settlement Receiver- Cost Center	CHAR	10
COBRB	PAOBJNR	RKEOBJNR	Settlement Receiver- Profitability Segment	CHAR	10
COBRB	HKONT	SAKNR	Settlement Receiver- G/L Account	CHAR	10

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:

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

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:

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

Transformation Mapping

Mapping Table Name	Mapping Table Description
Not applicable

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
	Not applicable

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:

1. Execute the automated data load into target system using load tool or product the load file if the load must be done manually
2. 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

Identify the phase as to “when” the load for this object will occur. <Pre-Cutover, Cutover, Post Cutover> and list the steps that need to occur before the load can commence

Configuration

List the Configurations required before loading can commence

Item #	Configuration Item

Conversion Objects

Object #	Preceding Object Conversion Approach
	list the exact title of the conversion object of only the immediate predecessor – this will then confirm the DDD (Data Dependency Diagram)

Error Handling

The table below depicts some possible system errors for this data object during data load. All data load error is to be logged as defect and managed within the Defect Management

Error Type	Error Description	Action Taken

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.

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