Status
Owner	Maytingsari Tjahjo
Stakeholders	The business stakeholders involved in making, reviewing, and endorsing this decision. Type @ to mention people by name

Purpose

The purpose of this document is to define the conversion approach to migrate the balance of Capex WBS from legacy system to S/4HANA.

Summarise how the data is currently utilized and set up in the legacy system/s and how object is intended to be represented in S/4, and any other relevant information

Conversion Scope

The scope of this document covers the approach for converting active Capex WBS element from Legacy Source Systems into S/4HANA.

Below are the list of AUC classes for SyWay:

• Z1100 Intangible-AUC
• Z1101 Intangible-R&I under construction
• Z1300 Tangible-AUC

The data from legacy system includes:

1. Relevancy Criteria 1
2. Relevancy Criteria 2
3. Relevancy Criteria n

The data from legacy system excludes:

1. Exclusion Criteria 1
2. Exclusion Criteria 2
3. Exclusion Criteria n

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
Legacy systems	Project level exclusions based on following relevancy rules: All projects with an out-of-scope company code will not be migrated. All closed projects as at the end of the previous fiscal year will not be migrated. All projects marked for deletion as at the end of the previous fiscal year will not be migrated. All projects without relevant WBS elements will not be migrated. Projects marked as statistical will not be migrated.		S/4HANA
Legacy systems	Any WBS element that is not closed as at the end of the previous fiscal year will be migrated. After eliminating all closed WBS elements, the relevancy rule will look for any WBS element that is not marked for deletion as at the end of the previous fiscal year for migration. Exceptions: Any closed WBS element that exists within an open Project. Any WBS element that is marked for deletion that exists in an open Project. Any closed WBS element that is affected by an open Projects.
DCT	Where legal entities do not use SAP to record their projects, the DCT will be used to collect the WBS element data. This will be used in conjunction with the PPM Item DCT to collect Projects that are not in legacy systems. There will be a creation of one WBS element to one Project Definition.	TBC	S/4HANA	TBC

Additional Information

Multi-language Requirement

N/A

Document Management

N/A

Legal Requirement

N/A

Special Requirements

Specify any special requirements or considerations that may impact the data conversion process based on specific locations, regulatory compliance or system limitations. Clearly outline any regional or localization requirements such as country-specific data formats, legal reporting obligations or industry standards that must be adhered to (e.g., localization rules for countries like China).

If the data conversion involves third-party systems or external data sources, such as Icertis, describe any additional requirements related to data mapping, transformation logic, validation rules or security measures that must be followed.

Target Design

With Functional input, document the technical design of the target fields that are in the scope of this document.

The technical design of the target for this conversion approach.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
MARA	MATNR	MATNR	Material Number	CHAR	18	Mandatory

Data Cleansing

All data cleansing should take place in the data source system as defined in this document, unless system limitations prevent it.

If data cleansing is managed outside of the source system (e.g. Syniti Migrate, 3rd Party Vendor, DCT), the necessary documentation must be produced and appended to this deliverable for sign-off.

ID	Criticality	Error Message/Report Description	Rule	Output	Source System

Conversion Process

The high-level process is represented by the diagram below:

Summarize High-Level Process. Include diagrams, where applicable. Include information supporting details of Extract, Transform and Load specific to the Data Object

Data Privacy and Sensitivity

Summarize Data Privacy and Sensitivity Requirements, if any

Extraction

Extract data from a source into Syniti Migrate. There are 2 possibilities:

1. The data exists. Syniti Migrate connects to the source and loads the data into Syniti Migrate. There are 3 methods:
   1. Perform full data extraction from relevant tables in the source system(s).
   2. Perform extraction through the application layer.
   3. Only if Syniti Migrate; cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
2. The data does not exist (or cannot be converted from its current state). 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

Extraction Run Sheet

Req #	Requirement Description	Team Responsible
1.	Extract master data from PF2 & WP2 based on the current relevancy rules. Tables to be addressed are as below: PRPS (WBS elements) JEST (Individual object status)	Data team

Selection Screen

If applicable, this section will give the details on any selection screen parameters, including the parameter type, that are required to be entered to ensure consistent data extracts.

Selection Ref Screen	Parameter Name	Selection Type	Requirement	Value to be entered/set
N/A

Data Collection Template (DCT)

This data collection template will be used to collect WBS element master data relating to project master data that is not in SAP PF2 & WP2. 

Target Ready Data Collection Template will be created for Data Object data with exception of some fields which require transformation as mentioned in the transformation rule.

<Object> DCT Rules

Extraction Dependencies

List the steps that need to occur before extraction can commence

Item #	Step Description	Team Responsible
1.	All WBS element cleansing has been completed in PF2 and WP2	Business

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.	Go to Process Area Launch and open the object 9031.	Data
2.	Execute the transformation to prepare the target tables of PRPS, PRHI, and COBRB	Data
3.	Check and confirm the transformed tables of PRPS, PRHI, and COBRB	Data
4.	Collect all the data to be migrated as a preload validation extract	Data
5.	Validate the Pre-Load extraction	Business

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1.					S/4HANA	ACDOCA	RBUKRS	Company Code	Company Code Mapping Table
2.					S/4HANA	ACDOCA	AWREF	Reference Document Number
3.					S/4HANA	BSEG	XREF3	Reference key for line item	Populated with AUC RECON
4.					S/4HANA	ACDOCA	DOCLN	Line Item Number	Group by • Company Code • Document Currency (must be equal to Company Code currency) All documents are to be posted to 31 Dec 2027 (For Group 1 go live). The document date must equal the posting date.  Document type must be 'UE' If the number of line items exceeds the number of lines per Journal in the "Lines per Journal" rule then it will be split into another document. Where there are more than the specified number of lines to post the entire Project Actuals then the last balancing line of the journal will be posted against the offset account 499000 (Clearing account)
5.					S/4HANA	ACDOCA	RACCT	G/L Account	Default account (715000). TBC
					S/4HANA	ACDOCA	GKONT	Offsetting Account	For the AUC transformation default to 294999 'For the non-AUC transformation default to 839110.  However, because the DMC load tool doesn't support having a cost object on offset line, this posting will need to be split into two documents using 499000 as the clearing account.
					S/4HANA	ACDOCA	BLART	Document Type	Default (UE)
					S/4HANA	ACDOCA	BUDAT	Posting Date in the document	Posting date will be a variable load parameter.  All documents are to be posted on the same day of the calendar year of the last Syensqo fiscal year end
					S/4HANA	ACDOCA	BLDAT	Document Date	Default (Same as Posting Date)
					S/4HANA	ACDOCA	BKTXT	Header Text	Default (Syensqo Migration)
					S/4HANA	ACDOCA	SGTXT	Item Text	Enter legacy PRPS-POSID- WBS Element
					S/4HANA	ACDOCA	RWCUR	Transaction Currency	Always local currency
					S/4HANA	ACDOCA	WSL	Amount	For AUC transformation ACDOCA-HSL = legacy RBURKS*, GJAHR = go live year, POPER = 0, AUC ANLN1** & AUC sub ANLN2** and AFABE = 01 For Non-AUC transformation ACDOCA-HSL = legacy RBURKS^, ANLN1^^^ & sub ANLN2^^^, GJAHR = go live year, POPER = 0, RACCT^^ and AFABE = 01 Note: Configuration will determine the total amount per document. If a document exceeds the allowed amount then reduce the "lines per journal" by 10% until the value is below the allowed amount. If a line item exceeds "99999,999,999.99" then it must be split into multiple lines
					S/4HANA	ACDOCA	HSL	LC Amount	Default (Same as WRBTR) Note: Configuration will determine the total amount per document. If a document exceeds the allowed amount then reduce the "lines per journal" by 10% until the value is below the allowed amount. If a line item exceeds "99999,999,999.99" then it must be split into multiple lines
					S/4HANA	ACDOCA	KSL	Group Amount	Group currency is EUR
					S/4HANA	ACDOCA	RASSC	Company ID of Trading Partner	-
					S/4HANA	ACDOCA	ZUONR	Assignment Number	Concatenate legacy company code and main asset number adding a full stop "." in between each field • BUKRS - Company Code • ANLN1 - Main Asset Number
					S/4HANA	ACDOCA	RMVCT	Transaction Type	-
					S/4HANA	ACDOCA	VALUT	Value Date	-
					S/4HANA	ACDOCA	HBKID	Short Key for House Bank	-
					S/4HANA	ACDOCA	RCNTR	Cost Center	-
					S/4HANA	ACDOCA	PRCTR	Profit Center	-
					S/4HANA	ACDOCA	PS_PSP_PNR	WBS Element	'WBS mapping table For AUC: In legacy table ANLA used ANLN1** = AUC and ANLN2** = sub AUC to lookup POSNR.  Use POSNR to map legacy WBS element to 1SAP WBS element For Non-AUC: - in table COBRB use ANLN1^^^ and ANLN2^^^ to lookup OBJNR - in table PRPS use OBJNR to lookup POSID
					S/4HANA	ACDOCA
					S/4HANA	ACDOCA
					S/4HANA	ACDOCA

Transformation Mapping

Use the exact name and reference this section in the “Transformation rules” above

Mapping Table Name	Mapping Table Description
WBS Element/Project Definition	Legacy WBS Element will be mapped to the new S/4HANA number which has been created from the PPM Item number.
Project Types	Legacy Project Types to be mapped to new S/4HANA Project Types.
Company Code	Legacy Company Codes mapped to new S/4HANA Company Codes.
Plant	Legacy Plant mapped to new S/4HANA Plants.
Investment Reason	???
Cost Centre	Legacy Cost Centers mapped to new S/4HANA Cost Centers.
Profit Centre	Legacy Profit Centers mapped to new S/4HANA Profit Centers.

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
1.	All records must be transformed after relevancy rules have been applied.	Data
2.	All cleansing reports must have been verified and endorsed. Only clean records will therefore be subject to transformation.	Business
3.	All mapping table values must be verified by the business.	Business
4.	All the fields within the WBS Elements must have the new values configured in S/4HANA	Data/Functional Team

Pre-Load Validation

Project Team

The following pre-load validations will be performed by the Project Team.

Completeness

Task	Action
Verify Counts	Data team to verify the load count is the same as per identified data from WBS Element file.
Number of WBS Elements per Project Definition	Verify that there is the same number of WBS Elements per Project Definition.
WBS Element Levels	Check that each WBS Element is at the correct level.
Verify against table COSP	Run all relevant transactions in table COSP and match the WBS Elements against the Pre-Load report to verify all relevant WBS Elements have been selected.

Accuracy

Task	Action
Validate	Check that each WBS element has the correct S/4HANA Project Definition code.

Business

The following pre-load validations will be performed by the Business.

Completeness

Task	Action
Verify counts	Business to verify the load count is the same as per identified data from WBS Elements relevancy. The report will be the same one used by the Data Team ready for upload.

Accuracy

Task	Action
Validate	Business to verify that all the data in the load table/file is accurate as per the endorsed transformation rules and mapping. It needs to be 100% accurate.

Load

To load Project Definition:

See the DCT for PPM Item Load Section. All these relevant Project Definitions will be loaded into the PPM modules as PPM Items. Within SAP there is a special upload file and upload program that will load these Project Definitions into PPM Items.

Once these Project Definitions are loaded into PPM Items there will be a trigger to use the Project Definition Template to post these PPM Items as Project Definitions together with the first two levels of WBS Elements in S/4HANA SAP Project Systems.

Then we will use the BAPI below to map the legacy WBS Elements to the correct level two WBS Element. The assumption here is that by cutover all WBS Elements will be created in the following manner thus making it easier to map to the correct WBS Element.

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.
2.
3.		Data
4.		Data
5.		Data
6.		Data
7.
8.
9.
10.
11.
12.

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
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Business

The following post-load validations will be performed by the business.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Key Assumptions

• Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
• Data Object 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

Workflow history