Status
Owner	KOHN-ext, Jacob
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 create the WBS - CAPEX, OPEX, Statistical

in S/4 HANA.

In SAP, a WBS element (Work Breakdown Structure element) is a key component in project structure. WBS elements are organized hierarchically and facilitates planning, execution, and control.

Conversion Scope

The scope of this document covers the approach for converting active WBS - CAPEX, OPEX, Statistical from Legacy Source Systems into S/4HANA following the WBS - CAPEX, OPEX, Statistical Master Data Design Standard. tems into S/4HANA: 

The guiding principle is that we should only migrate data necessary to support ongoing business operations. This may also involve cleansing activities within the source systems to align with the migration criteria.

In terms of Historical Data, it will not be migrated except where specific records are required to support application functionality, meet legislative obligations or ensure regulatory compliance.

WBS from the legacy system to be used for the basis of the system include projects from PF2 and WP2.

The data from legacy system includes:

1. WBS elements not in closed status
2. Closed CAPEX WBS elements which has current year postings - require postings according to CNV-9031.
3. The parent WBS elements included in the above.
4. New projects to be created to replace Internal orders with current year postings – require postings according to CNV-9032

The data from legacy system excludes:

1. WBS elements for company codes out of scope

Logic:

1. WBS elements not in closed status
2. Table PRPS

Key in field "Company Code" in scope.

Result: Object numbers of WBS that are in company codes in scope.

1. Table JEST:

Field "Object number" = Key in the object numbers of WBS (from Step A)

Field "Status Inactive" = blank

Then filter object number that do not have status I0046 (Closed) or IFO07 (Closed) 

These WBS need to be migrated.

1. Closed CAPEX WBS element that have cost in current year must also be migrated.

Logic:

1. Table PRPS

Key in field "Company Code" in scope.

Result: Object numbers of WBS that are in company codes in scope.

1. Table JEST:

Field "Object number" = Key in the object numbers of WBS (from Step A)

Field "Status Inactive" = blank

Then filter object number that has status I0046 (Closed) or IFO07 (Closed).

Result: Object number with status I0046 (Closed) or IFO07 (Closed).

1. Table RPSCO:

Field "Object number" = Key in the object numbers of WBS (from Step B) 

Field "Fiscal Year" = Current year

Field "Value Type" = 4

Result = Object numbers that have cost in current year.

These WBS needs to be migrated.

  

1. Parent WBS elements

For each WBS element with closed status include all superior level WBS elements.  If status of element is not closed superior WBS elements will also be not closed.

1. Table PRHI:

Field “WBS elements” (All PS_POSNR from PRPS)

IF “UP” is Null no superior objects

Result = Field “UP” additional WBS to be migrated

Repeat until “UP” is Null.

Predecessor Objects

CNV-1024 Project Definition

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
PF2			S/4 Hana
WP2			S/4 Hana
DCT			S/4 Hana

Additional Information

Multi-language Requirement

Summarize Multi-language Requirement/s, if any

Document Management

Summarize Document Management requirement, if any

Legal Requirement

Summarize Legal Requirement/s, if any

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
PRPS	POSID	PS_POSID	WBS element	CHAR	24	Mandatory
PRPS	PS_POSNR	PS_POSNR	WBS Element internal number	CHAR	8	Conditional
PRPS	OBJNR	J_OBJNR	Object Number	CHAR	8	Conditional
PRPS	POST1	PS_POST1	Description	CHAR	40	Mandatory
PRPS	VERNR	PS_VERNR	No. of Person Resp.	NUMC	8	Mandatory
PRPS	ASTNR	PS_ASTNR	Applicant no.	NUMC	8	Mandatory
PRPS	PBUKR	PS_PBUKR	Company code	CHAR	4	Mandatory
PRPS	PKOKR	PS_PKOKR	Controlling area	CHAR	4	Mandatory
PRPS	PRCTR	PRCTR	Profit Center	CHAR	10	Mandatory
PRPS	PRART	PS_PRART	Project Type	CHAR	2	Mandatory
PRPS	PLAKZ	PS_PLAKZ	Planning Element	CHAR	1	System
PRPS	BELKZ	PS_BELKZ	Acct asst elem.	CHAR	1	Mandatory
PRPS	FAKKZ	PS_FAKKZ	Billing Element	CHAR	1	Conditional
PRPS	FKSTL	PS_FKSTL	Responsible CC	CHAR	10	Mandatory
PRPS	FKOKR	PS_FKOKR	CA resp. cost center	CHAR	4	Mandatory
PRPS	FABKL	FABKL	Factory Calendar	CHAR	2	Mandatory
PRPS	PWPOS	PS_PWPOS	Currency	CUKY	5	Mandatory
PRPS	WERKS	WERKS_D	Plant	CHAR	4	Mandatory
PRPS	SCOPE	SCOPE_CV	Object class	CHAR	2	Mandatory
PRPS	XSTAT	PS_XSTAT	Statistical	CHAR	1	Conditional
PRPS	KOSTL	PS_KOSTL	CCtr posted actual	CHAR	10	Conditional
PRPS	IMPRF	IM_PROFIL	Investment Profile	CHAR	6	Conditional
PRPS	FUNC_AREA	FKBER	Functional Area	CHAR	16	Mandatory
PRPS	PSPHI	PS_PSPID	Project Definition	CHAR	24	Mandatory
PRPS	STUFE	PS_STUFE	Level	CHAR	3	Mandatory
PRPS	LEFT		WBS_LEFT			Conditional
PRPS	UP		WBS_UP			Conditional
PRPS	ZX01		CAPEX/ OPEX Indicator	char	10	Conditional
PRPS	ZX02		Maintenance event	char	40	Conditional
PRPS	ZX03		Maintenance WC	char	40	Conditional
PRPS	ZX04		Trading company code	CHAR	4	Conditional

Data Cleansing

Data cleansing tasks are set out in CNV-1024 which deals with projects and also by definition includes the closing of WBS elements in those projects.

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
1026-001	C3	Old projects with no actuals / commitment	If the old projects do not have any actual (and/or) commitments in the past year, set the project to status CLSD (CJ20N)	Old project set to closed	WP2/PF2

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
1026-001	Confirm scope and extraction approach for each ECC source systems WP2, PF2 (direct DB or manual extract)	Data Team (I2M), Data Team (Syniti)
1026-002	Establish and validate Syniti connectivity to both ECC source systems	Technical / Basis Team, Data Team (Syniti)
1026-003	Perform full data extraction from relevant SAP WBS elements from both source systems WP2, PF2	Data Team (Syniti)
1026-004	Extract WBS via the application layer for additional validations for Manual Data Collection using DCTs	Data Team (I2M)
1026-005	Apply agreed Relevancy Criteria to filter only applicable WBS records for S/4HANA	Data Team (I2M), Data Team (Syniti)
1026-006	In case of restricted access or connectivity issues, receive pre-extracted reports/files from source system team and upload to Syniti Migrate manually	Data Team (I2M), Data Team (Syniti)
1026-008	Perform data quality checks on extracted records (e.g., missing fields, invalid dates, incorrect formats)	Data Team (I2M), Data Team (Syniti)
1026-009	Review and approve extracted data sample sets from each source system before transformation begins	Business / Functional 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

Data Collection Template (DCT)

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

Field Name	Field Description	Rule

Extraction Dependencies

List the steps that need to occur before extraction can commence

Item #	Step Description	Team Responsible

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

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1		PRPS	POSID	WBS element	S/4 Hana	PRPS	POSID	WBS element	Old to new: Conversion Exit
2		PRPS	PS_POSNR	WBS Element internal number	S/4 Hana	PRPS	PS_POSNR	WBS Element internal number	Copy from source to target system
3		PRPS	OBJNR	Object Number	S/4 Hana	PRPS	OBJNR	Object Number	Copy from source to target system
4		PRPS	POST1	Description	S/4 Hana	PRPS	POST1	Description	Copy from source to target system
5		PRPS	VERNR	No. of Person Resp.	S/4 Hana	PRPS	VERNR	No. of Person Resp.	Old to new
6		PRPS	ASTNR	Applicant no.	S/4 Hana	PRPS	ASTNR	Applicant no.	Old to new
7		PRPS	PBUKR	Company code	S/4 Hana	PRPS	PBUKR	Company code	Value Mapping: Old to New Company Code
8		PRPS	PKOKR	Controlling area	S/4 Hana	PRPS	PKOKR	Controlling area	Value Mapping:  Old to New Controlling Area
9		PRPS	PRCTR	Profit Center	S/4 Hana	PRPS	PRCTR	Profit Center	Value Mapping:  Old to New Profit Centre
10		PRPS	PRART	Project Type	S/4 Hana	PRPS	PRART	Project Type	Old to new
11		PRPS	PLAKZ	Planning Element	S/4 Hana	PRPS	PLAKZ	Planning Element	Copy from source to target system
12		PRPS	BELKZ	Acct asst elem.	S/4 Hana	PRPS	BELKZ	Acct asst elem.	Copy from source to target system
13		PRPS	FAKKZ	Billing Element	S/4 Hana	PRPS	FAKKZ	Billing Element	Copy from source to target system
14		PRPS	FKSTL	Responsible CC	S/4 Hana	PRPS	FKSTL	Responsible CC	Value Mapping:  Old to New Cost Centre
15		PRPS	FKOKR	CA resp. cost center	S/4 Hana	PRPS	FKOKR	CA resp. cost center	Value Mapping:  Old to New Cost Centre
16		PRPS	FABKL	Factory Calendar	S/4 Hana	PRPS	FABKL	Factory Calendar	Old to new
17		PRPS	PWPOS	Currency	S/4 Hana	PRPS	PWPOS	Currency	Value Mapping: Currency From Company Code Company Code Currency from T001-WAERS where BUKRS = PBUKR
18		PRPS	WERKS	Plant	S/4 Hana	PRPS	WERKS	Plant	Value Mapping:  Old to New Plant
19		PRPS	SCOPE	Object class	S/4 Hana	PRPS	SCOPE	Object class	Copy from source to target system, if source empty Default from Project Profile
20		PRPS	XSTAT	Statistical	S/4 Hana	PRPS	XSTAT	Statistical	Copy from source to target system
21		PRPS	KOSTL	CCtr posted actual	S/4 Hana	PRPS	KOSTL	CCtr posted actual	Value Mapping:  Old to New Cost Centre
22		PRPS	IMPRF	Investment Profile	S/4 Hana	PRPS	IMPRF	Investment Profile	Old to new
23		PRPS	FUNC_AREA	Functional Area	S/4 Hana	PRPS	FUNC_AREA	Functional Area	Old to new
24		PRPS	PSPHI	Project Definition	S/4 Hana	PRPS	PSPHI	Project Definition	Old to new - updated for load - conversion exit
25		PRPS	STUFE	Level	S/4 Hana	PRPS	STUFE	Level	Copy from source to target system
26		PRHI	LEFT	WBS_LEFT	S/4 Hana	PRPS	PRHI-LEFT	WBS_LEFT	Old to new
27		PRHI	UP	WBS_UP	S/4 Hana	PRPS	PRHI-UP	WBS_UP	Old to new
28		PRPS	ZX01	CAPEX/ OPEX Indicator	S/4 Hana	PRPS	ZX01	CAPEX/ OPEX Indicator	Copy from source to target system
29		PRPS	ZX02	Maintenance event	S/4 Hana	PRPS	ZX02	Maintenance event	Copy from source to target system
30		PRPS	ZX03	Maintenance WC	S/4 Hana	PRPS	ZX03	Maintenance WC	Copy from source to target system
31		PRPS	ZX04	Trading company code	S/4 Hana	PRPS	ZX04	Trading company code	Value Mapping: Old to New Company Code

Transformation Mapping

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

Mapping Table Name	Mapping Table Description
T001	Value Mapping: Currency From Company Code
Company Code	Value Mapping: Old to New Company Code
Controlling Area	Value Mapping:  Old to New Controlling Area
Cost Centre	Value Mapping:  Old to New Cost Centre
Plant	Value Mapping:  Old to New Plant
Profit Center	Value Mapping:  Old to New Profit Centre

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible

Pre-Load Validation

Project Team

The following pre-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 pre-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.

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

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
1	Number Range
2	Company Code
3	Controling Area
4	Project Type
5	Factory Calendar
6	Currency Code
7	Plant
8	Investment Profile
9	Functional Area
10	Trading company code

Conversion Objects

Object #	Preceding Object Conversion Approach
1024	Project Definition
1074	Cost Centre
1070	Profit Centre

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