Status	Revision in Progress
Owner	Maytingsari Tjahjo
Stakeholders

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.

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:

The data from legacy system excludes:

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

Target Design

The technical design of the target for this conversion approach.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement

Data Cleansing

ID	Criticality	Error Message/Report Description	Rule	Output	Source System

Conversion Process

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

Data Privacy and Sensitivity

Extraction

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

The data exists. connects to the source and loads the data into . 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 ; cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
The data does not exist (or cannot be converted from its current state). The data is manually collected by the business directly in . This is to be conducted using DCT (Data Collection Template) in

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

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 with exception of some fields which require transformation as mentioned in the transformation rule.

DCT Rules

Field Name	Field Description	Rule
PRPS-VERNR	Person Responsible	Person responsible for the project (Running number or Position number?)
PRPS-AKSTL	Requesting Cost Centre	Represents the cost center from where the activity is being performed.
PRPS-PRCTR	Profit Centre	An organizational unit representing accountability for Profit/Loss.
PRPS-PLAKZ	Planning Element	Select if Account Assignment key is selected.
PRPS-BELKZ	Account Assignment Element	Activation of this field enables postings and commitments to be made.
PRPS-FKOKR	Controlling Area	?
PRPS-PBUKR	Company Code	Designated Company Code.
PRPS-WERKS	Plant	Plant must be in table and be applicable to the Company Code above.
PRPS-FABKL	Factory Calendar	To be defaulted from Plant.
PRPS-SLWID	Field Key	Will default from Project Profile as per in PPM Items and Project Definition DCT
PRPS-SCOPE	Object Class	Will default from Project Profile as per in PPM Items and Project Definition DCT
PRPS-IMPRF	Investment Profile	Will default from Project Profile as per in PPM Items and Project Definition DCT
PRPS-IZWEK	Investment Reason	Specifies the investment reason related to the project.
JEST-STAT	System Status	Standard SAP status controlling. Values are system-defined, mainly CRTD, REL, TECO.
JEST-STAT	User Status	?
DKOBR-EMPGE	Settlement Rules	Capture all settlement rules. Especially those where the WBS Element is in TECO phase. These will have Fixed Assets in the Settlement rule that needs to be mapped to the new S4 HANA fixed asset.

Extraction Dependencies

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 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.	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.	PF2 and WP2	PRPS	POSID	WBS Element	S/4HANA	PRPS	POSID	WBS Element	Mapping Table in ADMM. Table is required to map the legacy WBS Element numbers to the Project Definition created from the PPM Item. The new Project Definition number will be the same as the PPM Item number. This will apply to all levels of the WBS Element. There will be a field in the PPM Item that can be mapped back to the legacy WBS Element.
2.	PF2 and WP2	PRPS	POST1	Short Description	S/4HANA	PRPS	POST1	Short Description	Description as per legacy.
3.	PF2 and WP2	PRPS	PRART	Project Type	S/4HANA	PRPS	PRART	Project Type	Use the mapping table to map the legacy Project Types to the S4 Project Types. The Project Types are: ......
4.	N/A				S/4HANA	PRPS	PKOKR	Controlling Area	Default to ?
5.	PF2 and WP2	PRPS	PBUKR	Company Code	S/4HANA	PRPS	PBUKR	Company Code	Map the legacy company code to the S/4HANA legal entities.
6.	PF2 and WP2	PRPS	WERKS	Plant	S/4HANA	PRPS	WERKS	Plant	Map the legacy plants to the S/4HANA plants.
7.	N/A				S/4HANA	PRPS	VERNR	Person Responsible	Copy the Person Responsible from Project Definition
8.	N/A				S/4HANA	PRPS	PRCTR	Profit Centre	Copy the Profit Centre from the S4 Project Definition.
9.	N/A				S/4HANA	PRPS			?
10.	PF2 and WP2	PRPS	AKSTL	Requesting Cost Centre	S/4HANA	PRPS	AKSTL	Requesting Cost Centre	Map the legacy Cost Centre to the S/4HANA Cost Centre.
11.	PF2 and WP2	ANLA	ANLKL	Asset Class	S/4HANA	PRPS	IMPRF	Investment Profile	?
12.	N/A				S/4HANA	PRPS	SCOPE	Object Class	Copy the Object Class from the Project Profile in the Project Definition.
13.	PF2 and WP2	PRPS	ABUKR	Company code for Requesting Cost Centre	S/4HANA	PRPS	ABUKR	Company Code for Requesting Cost Centre	Derive company code from S/4HANA Cost Centre mapping tables
14.	PF2 and WP2	PRPS	STUFE	WBS Element level	S/4HANA	PRPS	STUFE	WBS Element level	?
15.	N/A				S/4HANA	PRPS	?
16.	N/A				S/4HANA	PRPS
17.	N/A				S/4HANA	PRPS	BELKZ	Account Assignment	Always set the Account Assignment Indicator at the lowest level
18.	PF2 and WP2	JEST	STAT	System Status	S/4HANA	JEST	STAT	System Status	System Status will be posted as CRTD
19.	PF2 and WP2	JEST	STAT	User Status	S/4HANA	JEST	STAT	User Status	User Status will be posted as CRTD

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

Pre-Load Validation

Project Team

Completeness

Task	Action

Accuracy

Task	Action

Business

Completeness

Task	Action

Accuracy

Task	Action

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

Load Phase and Dependencies

Configuration

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

Error Type	Error Description	Action Taken

Post-Load Validation

Project Team

Completeness

Task	Action

Accuracy

Task	Action

Business

Completeness

Task	Action

Accuracy

Task	Action

Key Assumptions

Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
is in scope based on data design and any exception requested by business.

Change log

Version	Published	Changed By
CURRENT (v. 5)	Apr 20, 2026 10:20	GOTTIPATI-ext, Madhu
v. 129	Apr 20, 2026 10:15	GOTTIPATI-ext, Madhu
v. 128	Feb 17, 2026 13:45	GOTTIPATI-ext, Madhu
v. 127	Feb 17, 2026 10:29	GOTTIPATI-ext, Madhu
v. 126	Feb 17, 2026 10:28	GOTTIPATI-ext, Madhu
v. 125	Feb 16, 2026 22:42	GOTTIPATI-ext, Madhu
v. 124	Feb 11, 2026 15:58	GOTTIPATI-ext, Madhu
v. 123	Feb 11, 2026 15:56	GOTTIPATI-ext, Madhu
v. 122	Feb 11, 2026 15:55	GOTTIPATI-ext, Madhu
v. 121	Feb 11, 2026 15:39	GOTTIPATI-ext, Madhu

Go to Page History

Workflow history

Title	Last Updated By	Updated	Status
There are no pages at the moment.

Apr 20, 2026	Actor	Type	Activity	Version
Revision in Progress	GOTTIPATI-ext, Madhu	Comment	commented 10:28 am PDM-1724 - Jira project doesn't exist or you don't have permission to view it.
		Edit	updated the page at 10:20 am
		State	changed state to Revision in Progress at 10:15 am	v129
Approved	GOTTIPATI-ext, Madhu	Edit	updated the page at 10:15 am
Mar 02, 2026
	TAN-ext, Charmaine	State	changed state to Approved at 3:10 pm (State override) [PMO Comments] Conversion Spec completed as per CS register and functional review completed.	v128
Feb 18, 2026
Peer Review	BIDALIA-ext, Kuldeep	State	gave Peer Review approval at 11:16 am
	GOTTIPATI-ext, Madhu	State	assigned approval Peer Review to BIDALIA-ext, Kuldeep at 10:33 am
		State	unassigned UPADHYAY-ext, Anjali from approval Peer Review at 10:33 am
		State	assigned approval Peer Review to UPADHYAY-ext, Anjali at 9:53 am

Workflow history

Space shortcuts

Page tree

CNY 9031-Project-Actual GL Line Items (PNL-WBS for AuC)

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

Data Cleansing

Conversion Process

Data Privacy and Sensitivity

Extraction

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

Extraction Dependencies

Transformation

Transformation Run Sheet

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

Load Run Sheet

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

See also

Change log

Workflow history