Status	Revision under Review
Owner	KOHN-ext, Jacob
Stakeholders	BIDALIA-ext, Kuldeep NADAR-ext, Parvati STEFANESCU-ext, Aurelia VAN DE REE-ext, Ramon AGGARWAL-ext, Vikhyat

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

The DCT will contain transformed data from source system for Capital and Budget Managed Operating PS Project Definitions in scope for migration, enrichment will be necessary to produce properly formatted data load sheets for S/4 HANA.

Relevancy Criteria

The data from legacy system to be included in the initial extract includes:

1. The data from legacy system includes:
  1. 1. Capital projects (e.g. Industrial, Facility, IT and R&I) open as at migration date postings in the agreed migration time or has AUC balance.
    2. Budgeted Operating projects (e.g. Budgeted Maintenance, Marketing, Demolition projects) open as at migration date with postings in the agreed migration time
    3. Closed Capital Projects with postings within the agreed timeframe.
    4. Closed Budgeted Operational projects with postings within the agreed time frame.
    5. Specifically also included are IT and R&I Projects (open as at migration date and (closed projects with postings the agreed timeframe) with postings postings in the agreed migration time
  The data from legacy system excludes
  1. 1. Project Definition in out of scope Company Codes
    2. Project Definitions in out of scope Plants.
    3. Project which has deletion indicator set.
    4. Project marked as closed and not included in 3, 4 and 5 above
    5. Non Budgeted Maintenance Projects.

Additionally WBS elements without any initial extract will be created in the DCT only, this includes -

WBS elements with no reference to PPM items
1. For the Provisions (One project per company code per GBU)
2. Intercompany recharge (One Level 1 WBS per Company Code, Level 2 WBS per Trading Company Code)

List of source systems and approximate number of records

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

Inter-company recharge WBS elements are replicated to other S/4 Hana instances as per business process, refer ERP-165 - Getting issue details... STATUS for development.

Identification Logic

In principal any WBS element belonging

Capital project is a project that has any WBS elements with a Investment Profile. PRPS-IMPRF

Budgeted Opex is any other project that has any WBS elements with budget. WBS has entry in BPGE for value type 41

IT Project is a project that has a WBS element one of the following criteria

in WP2 user field 1 starting with IT PRPS-USR00
in PF2 user field 2 starts with IT PRPS-USR01
has a WBS element Family is SBS IS or IT

R&I Project is a project meeting one of the following criteria,

in PF2 Project ID starts with R- PROJ-PSPID
in WP2 Project ID starts with RR PROJ-PSPID
has a WBS element with WEGO ID field filled PRPS-ZZ_WEGO_ID
has a WBS element family indicated as R&I or R&I Others

Industrial projects

Capital project is a project that has any WBS elements with a Investment Profile. PRPS-IMPRF
Budgeted Opex is any other project that has any WBS elements with budget. WBS has entry in BPGE for value type 41
has a WBS element family indicated as GEC, Regular,RegAffairs, ING or Others

Facilities Projects

Capital project is a project that has any WBS elements with a Investment Profile. PRPS-IMPRF
Budgeted Opex is any other project that has any WBS elements with budget. WBS has entry in BPGE for value type 41
has a WBS element family indicated as Facilities

Additional Information

Multi-language Requirement

The WBS element name is maintained in a single language only, no translation required.

Document Management

Not required.

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
PRPS	POSID	PS_POSID	WBS element	CHAR	24	Mandatory
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	System Generated
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 Generated
PRPS	BELKZ	PS_BELKZ	Acct asst elem.	CHAR	1	Conditional
PRPS	FAKKZ	PS_FAKKZ	Billing Element	CHAR	1	Conditional
PRPS	AKOKR	PS_AKOKR	CA req. cost center	CHAR	4	Mandatory
PRPS	AKSTL	PS_AKSTL	Request. cost center	CHAR	10	Conditional
PRPS	ABUKR	PS_ABUKR	Requesting co. code	CHAR	4	Mandatory
PRPS	FKSTL	PS_FKSTL	Responsible CC	CHAR	10	Conditional
PRPS	FKOKR	PS_FKOKR	CA resp. cost center	CHAR	4	Conditional
PRPS	FABKL	FABKL	Factory Calendar	CHAR	2	System Generated
PRPS	PWPOS	PS_PWPOS	Currency	CUKY	5	System Generated
PRPS	WERKS	WERKS_D	Plant	CHAR	4	Conditional
PRPS	SLWID		Field key	CHAR		System Generated
PRPS	USR08	USR08	Expected Capitalization Date	DAT	8	Conditional
PRPS	USR10	USR10	Cross System	CHAR	1	Conditional
PRPS	SCOPE	SCOPE_CV	Object class	CHAR	2	System Generated
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	Conditional
PRPS	PSPHI	PS_PSPID	Project Definition	CHAR	24	Mandatory
PRPS	STUFE	PS_STUFE	Level	CHAR	3	Mandatory
PRHI	UP	PS_PHIUP	WBS_UP	NUMC	8	System Generated
PRHI	LEFT	PS_PHILE	WBS_LEFT	NUMC	8	System Generated
PRPS	SYCAP_OPX		CAPEX/ OPEX	CHAR	10	Conditional
PRPS	SYMAIN_EVT		Maintenance event	CHAR	40	Conditional
PRPS	SYTRADE_CC		Trading company code	CHAR	4	Conditional
PRPS	SYSITE		Site	CHAR	50	Conditional

Data Cleansing

Some Data cleansing tasks are set out in CNV-1024 which deals with projects.

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
1	C3	Projects with no actuals / Commitment in agreed timeframe	If the projects do not have any actual or commitments in the past year, and is not used as account assignment on open maintenance orders then set the projects should have status CLSD (CJ20N)	Identifies Old project which can be closed	WP2/PF2
2	C2	Open WBS elements, not relevant for migration, with assigned maintenance orders.	Scope of report moved to CNV-9005
3	C1	Open Projects where WBS Family is empty	An open project which falls in the scope of selection where the WBS Family cannot be determined.	Users to update the WBS Family field on open projects.	WP2/PF2
4	C3	Projects with locked/on hold status	Open projects with active status as per selection criteria	Users to close projects based on existing project status	WP2/PF2

Open Projects without posting since selected financial year

Selection

Selection Option for Start Fiscal year.

Identify projects going to PPM, using the logic for WBS element relevancy, from prep report ZACTIVE_PROJECT_OPEN_CLOSED = OPEN and ZACTIVE=TRUE

Returns projects with NO entries for WBS elements in tables COSS and COSP where fiscal year is greater or equal to selected fiscal year.

Where project created on date is less than or equal to today minus 365. PROJ-ERDAT.

COSS-OBJNR = WBS element Object number and GJAHR greater or equal to selected fiscal year. If any records returned then continue to next Project definitions.

COSP-OBJNR = WBS element Object number and GJAHR greater or equal to selected fiscal year. If any records returned then continue to next Project definitions.

Output

Project Number (PROJ-PSPID)

Project Description (PROJ-POST1)

Company Code (PROJ-VBUKR)

Profit Center (PROJ-PRCTR)

Plant (PROJ-WERKS)

Responsible Person (PROJ-VERNA)

Applicant (PROJ-ASTNA)

Global Business Unit (PROJ-ZZGBU)

Open WBS elements, not relevant for migration, with assigned maintenance orders

Scope of report moved CNV-9005 Work Order

Open Projects where WBS Family is empty

Selection

This is done for Projects which fall within the scope of migration (ZACTIVE = TRUE)

And for

Open projects (ZACTIVE_PROJECT_OPEN_CLOSED = "Open") with
Budget Opex or Capital projects (ZACTIVE_PROJECT_CATEGORY NE "Uncatogorised")

where the Company code and plant is relevant for migration.

but which does not have WBS Family

For PF2 from PROJ-ZZFAMIL = ''

For WP2 show projects where count of PRPS-Z_FAMIL not equal to blank = 0

Output

Project Number (PROJ-PSPID)

Project Description (PROJ-POST1)

Company Code (PROJ-VBUKR)

Profit Center (PROJ-PRCTR)

Plant (PROJ-WERKS)

Responsible Person (PROJ-VERNA)

Applicant (PROJ-ASTNA)

Global Business Unit (PROJ-ZZGBU)

Investment Reason (PROJ-ZZ_IZWEK), display text from T087J

Open Projects with locked status

Selection

Identify projects going to PPM, using the logic for WBS element relevancy, from prep report ZACTIVE_PROJECT_OPEN_CLOSED = OPEN with status locked, on hold, or user status locked.

Using project definition object number select from JEST-STAT = Master-data Locked I0065 OR Time Locked E0001 OR Commitment Locked E0002

Output

Project Number (PROJ-PSPID)

Project Description (PROJ-POST1)

Company Code (PROJ-VBUKR)

Profit Center (PROJ-PRCTR)

Plant (PROJ-WERKS)

Responsible Person (PROJ-VERNA)

Applicant (PROJ-ASTNA)

Global Business Unit (PROJ-ZZGBU)

System Status (JEST-STAT) display text from TJ02T-TXT30 for statuses starting with I and where Language is English

User Status (JEST-STAT) display text from TJ30T-TXT30, where STSMA=ZPS00001 for statuses starting with E and where Language is English

Conversion Process

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

Data Privacy and Sensitivity

Not applicable

Extraction

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

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.
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	Confirm scope and extraction approach for each ECC source systems WP2, PF2 (direct DB or manual extract)	Data Team (I2M), Data Team (Syniti)
2	Establish and validate Syniti connectivity to both ECC source systems	Technical / Basis Team, Data Team (Syniti)
3	Perform full data extraction from relevant SAP WBS elements from both source systems WP2, PF2	Data Team (Syniti)
4	Extract WBS via the application layer for additional validations for Manual Data Collection using DCTs	Data Team (I2M)
5	Apply agreed Relevancy Criteria to filter only applicable WBS records for S/4HANA	Data Team (I2M), Data Team (Syniti)
6	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)
8	Perform data quality checks on extracted records (e.g., missing fields, invalid dates, incorrect formats)	Data Team (I2M), Data Team (Syniti)
9	Review and approve extracted data sample sets from each source system before transformation begins	Business / Functional Team

Selection Screen

Not applicable

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

WBS - CAPEX, OPEX, Statistical Project Based DCT Rules: Used for Provision and Recharge Projects

Link DCT to the DCT 1024 from Conversion specification https://wiki.syensqo.com/display/public/ER/CNV-1024+Project+Definition

Source System is always construct.

Field Name	Field Description	Rule
PSPHI	Project Definition	Project ID assigned to the WBS elements. Refer table PROJ-PSPHI for allowed values. Dropdown values from DCT1024 - PSPHI It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template
POSID	WBS element	Unique Identifier for the WBS Element, as per project coding mask F-000000-00-00-XX-XX-XX Internal Information Validation required, WBS Element ID must begin with the same Current Number for Project. It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template.
POST1	Description	40 character description of the WBSE. It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template
VERNR	No. of Person Resp.	This field represents the position of the Person Responsible for a WBS Element. It will be derived from the Project Definition and can be overwritten. Dropdown values from TCJ04-PS_VERNR It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template.
ASTNR	Applicant no.	This field represent the position of the Project Financial Controller. It will be derived from the Project Definition and can be overwritten. Dropdown values from TCJ05-ASTNR. It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template.
PRCTR	Profit Center	In Syway, Profit Center represent a plant or a site or generic for GBU. It will be derived from the Project Definition and can be overwritten. Dropdown values from CEPC-PRCTR It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template.
PRART	Project Type	It is an attribute that serve as classification field that help to define the nature, purpose, and governance of a WBS element. They are useful for reporting, controlling, and compliance alignment. Internal Information Dropdown values from TCJ1-PRART. It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template.
BELKZ	Acct asst elem.	Tooltip : This indicator enables financial posting on the WBS element. Internal Information It will be checked in below conditions- 2. For WBS elements governed by Operational, Statistical & Recharge project profiles, activation of this checkbox is mandatory for all level 2 WBS elements. It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template where required and blank when not.
FAKKZ	Billing Element	Tooltip: This indicator enables for revenue postings. Required at level 2 for Intercompany Recharge projects Internal Information Only relevant for project profile of project maintained in PSPHI is a Recharge Project
AKSTL	Request. cost center	The Requesting Cost Center that owns the asset. Required only if the Requesting Cost Center is different to the Responsible Cost Center. If filled the Requesting Cost center must be in same company code as the Responcible Cost Center. This Cost Centre is automatically copied to AUC. Refer master data table field CSKS-KOSTL for allowed values. A preload check is to be done to confirm that the Company Code of the Request. cost center is equal to the company code to the Company Code of the Responsible Cost Center's (FKSTL) Company Code.
FKSTL	Responsible CC	Cost Center responsible for delivery of work. Refer master data table field CSKS-KOSTL for allowed values. It is a Required Field for all WBS elements flagged as account assignment element. Preload Check to be done to confirm that this is field in the Data Collection Template when required.
WERKS	Plant	Plant represent a site of the WBS element. Mandatory for all WBS elements. It is a conditional field used in conjunction with site. It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template
USR10	Cross System	This checkbox field, will be selected when inter-company services are needed for a WBS element.
KOSTL	CCtr posted actual	This field represents the receiver Cost Center of actual cost for financial posting on the statistical WBS element. This field is optional and available only on statistical WBS elements - WBS elements of project with Project Profile "ZPS0001" where Project Type is Capital Lease - WBS elements of project with Project Profile "ZPS0003" i.e. Statistical Expense. Dropdown values from KOSTL
FUNC_AREA	Functional Area	Functional Area is an organisational unit used to classify expenses based on their purpose or function. Dropdown values from TFKB-FKBER.
STUFE	Level	In a project, WBS elements are structured across multiple levels to form a tree-like hierarchy for better project controlling and monitoring.
UP	WBS_UP	This field represents the immediate superior WBS element required for establishing parent-child relationships in the WBS hierarchy, this is a required field for level 2 WBS elements. Can only be a WBS element within the same Project As per project coding mask F-000000-00-00-XX-XX-XX Internal Information Can only be a WBS element within the same project. It is a Required Field for level 2 and lower: Preload Check to be done to confirm that this is field in the Data Collection Template when required.
LEFT	WBS_LEFT	This field represents the left-adjacent WBS element in the same hierarchy level required for navigating sibling relationships within a WBS hierarchy. Can only be a WBS element within the same Project. As per project coding mask F-000000-00-00-XX-XX-XX Internal Information Can only be a WBS element within the same project. Preload Check to be done to confirm that this is field in the Data Collection Template when required.
SYTRADE_CC	Trading company code	Tooltip: This field will be applicable when Project Type = Intercompany Recharge. Mandatory at Level 2 WBS to determine the trading company for intercompany recharges Internal Information Dropdown values from T001-BURKS.
SYSITE	Site	Tooltip: A Site represents the highest-level physical boundary of Syensqo — a distinct, real-world physical location where Syensqo operates or maintains responsibility. Internal Information Currently this is a free text field which is optional in conjunction with plant - either plant or Site must be filed. No Site will be maintained for IAS19 Provision and ESG fines WBS elements i.e. with Project Types 14 & 22. this i mean
	Business Reviewed

WBS - CAPEX, OPEX, Statistical ECC Extracted Data DCT Rules: Where WBS elements have ECC source data

Field Name	Field Description	Rule
PSPHI	Project Definition	Project ID assigned to the WBS elements. Internal Information This is a display only field with legacy project ID PROJ-PSPID from Preparation report It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template
POSID	WBS element	Unique Identifier for the WBS Element Internal Information This is a display only field PRPS-POSID from Preparation report Validation required, WBS Element ID must begin with the same Current Number for Project. It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template.
POST1	Description	40 character description of the WBSE. Internal Information Display only field, PRPS-POST1, description from Preparation report It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template
VERNR	No. of Person Resp.	This field represents the position of the Person Responsible for a WBS Element. It will be derived from the Project Definition and can be overwritten. Internal Information Display only field, the PRPS-VERNR responsible person from Preparation report Dropdown values from TCJ04-PS_VERNR It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template.
ASTNR	Applicant no.	This field represent the position of the Project Financial Controller. It will be derived from the Project Definition and can be overwritten. Internal Information Display only field from Legacy PRPS-ASTNR, applicant from Preparation report Dropdown values from TCJ05-ASTNR. It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template.
PRCTR	Profit Center	In Syway, Profit Center represent a plant or a site or generic for GBU. It will be derived from the Project Definition and can be overwritten. Dropdown values from CEPC-PRCTR Internal Information Display only field from Legacy PRPS-PRCTR, applicant from Preparation report It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template.
LEG_IZWEK	Legacy Investment Reason	Display only field to help user select the correct project type Internal Information Display only field to help user select the correct project typefrom Legacy PRPS-IZWEK, investment reason from Preparation report Display the text using T087J from ECC
LEG_IZWEK_T	Legacy Investment Reason Description	Display only field to help user select the correct project type Internal Information Display the text using T087J from ECC for PRPS-IZWEK
LEG_PRART	Legacy Project Type	Display only field to help user select the correct project type Internal Information Display only field text from ECC TCJI based on PRPS-PRART, project type from Preparation report
LEG_PRART_T	Legacy Project Type Description	Display only field to help user select the correct project type Internal Information Display text from TCJI from Preparation report
PRART	Project Type	It is an attribute that serve as classification field that help to define the nature, purpose, and governance of a WBS element. They are useful for reporting, controlling, and compliance alignment. Dropdown values from TCJ1-PRART. Internal Information It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template.
BELKZ	Acct asst elem.	This indicator enables financial posting on the WBS element. Internal Information Display only field from Legacy PRPS-BELKZ, account assignment from Preparation report. It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template where required and blank when not.
FAKKZ	Billing Element	Only relevant for project profile of project maintained in PSPHI is a Recharge Project Internal Information Display only field, value is always false.
AKSTL	Request. cost center	The Requesting Cost Center that owns the asset. Required only if the Requesting Cost Center is different to the Responsible Cost Center. If filled the Requesting Cost center must be in same company code as the Responcible Cost Center. This Cost Centre is automatically copied to AUC. Internal Information Display only field from Legacy PRPS-AKSTL, Refer master data table field CSKS-KOSTL for allowed values.
FKSTL	Responsible CC	Cost Center responsible for delivery of work. Refer master data table field CSKS-KOSTL for allowed values. Internal Information Display only field from Legacy PRPS-FKSTL, It is a Required Field: Required for all account assigned WBS elements. Preload Check to be done to confirm that this is field in the Data Collection Template when required.
WERKS	Plant	Plant represent a site of the WBS element. Mandatory for all WBS elements. Internal Information Display only field from Legacy PRPS-WERKS, It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template
LEG_USR08	Legacy Date WBS date field	Display only field to help user select the correct Expected Captillzation Date Internal Information Display only field from Legacy PRPS-USR08/USR09
LEG_PLSEZ	Legacy Project End Date	Display only field to help user select the correct Expected Captillzation Date Internal Information Display only field from Legacy PRPS-USR08/USR09
USR08	Expected Capitalization Date	Expected Capitalization date marks the anticipated execution of the AUC final settlement, restricted to WBS elements with Investment Profile. Date Field. Internal Information It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template where Investment reason is maintained
USR10	Cross System	This checkbox field, will be selected when inter-company services are needed for a WBS element.
KOSTL	CCtr posted actual	This field represents the receiver Cost Center of actual cost for financial posting on the statistical WBS element. This field is optional and available only statistical WBS elements WBS elements of project with Project Profile "ZPS0001" where Project Type is Capital Lease - WBS elements of project with Project Profile "ZPS0003" i.e. Statistical Expense. Internal Information Display only field from PRPS-KOSTL Dropdown values from KOSTL
IMPRF	Investment Profile	Investment Profile on WBS element is used to enable auto generation of AuC w.r.t. predefined asset class. Applicable for CAPEX projects (with Project Profile ZPS0001) - at Level 3 WBS elements if the CAPEX field is selected and project type is not "Capital Spares" - at level 2 WBS element if the CAPEX field is selected and project type is "Capital Spares" Investment Profile can not be changed once WBS is settled. Internal Information Display only field from PRPS-IMPRF Dropdown values from TAPRF-IVPRO for allowed values. Preload validation required to ensure field is filled when required.
FUNC_AREA	Functional Area	Functional Area is an organisational unit used to classify expenses based on their purpose or function. Internal Information Preload validation required to ensure field is filled when required. Dropdown values from TFKB-FKBER.
STUFE	Level	In a project, WBS elements are structured across multiple levels to form a tree-like hierarchy for better project controlling and monitoring. Internal Information Display only level based on the PREP report
SYCAP_OPX	CAPEX / OPEX	This field identifies expense as CAPEX or OPEX. Internal Information Display only level based on the PREP report Drop down field selection will allow any of CAPEX, OPEX or blank entry. Preload Check to be done to confirm that this is field in the Data Collection Template when required.
SYMAIN_EVT	Maintenance event	This field is used to determine the settlement rule receiver for the relevant maintenance Work Order. This field is used to determine the settlement rule receiver for the relevant maintenance Work Order. This field will be applicable for projects with Project Profile ZPS0001 & ZPS0002 at level 3 & 4 WBS element. Internal Information Data source for this field will be T352R-REVNR.
<CR0456 - WBS Number Generation Start> Phase	Phase	Tooltip To allow for assignment of WBS element to the correct phase of the project where projects have multiple phase level WBS elements. If left blank the WBS element will be assigned to the execution (or equivalent phase) Internal Information This is a dropdown field of Phase level WBS Elements as maintained in the DCT WBS - Project Template Assignment defined below. Dropdown to display Item Type, ITEM_PHASE and WBS Description <CR0456 - WBS Number Generation End>
ZREVIEW_STATUS	Review Status	Tooltip Allows indication of records readiness for load. Internal Information Dropdown with review status values

WBS - CAPEX, OPEX, Statistical PPM relevant DCT Rules: Used for Direct Asset Purchase, Capital Lease and Capital Spares

Source System is CONSTRUCT_2

Field Name	Field Description	Rule
PSPHI	Project Definition	Project ID assigned to the WBS elements. Dropdown values from DCT1022 - PSPHI It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template
POSID	WBS element	Unique Identifier for the WBS Element, as per project coding mask F-000000-00-00-XX-XX-XX Internal Information Validation required, WBS Element ID must begin with the same Current Number for Project. It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template.
POST1	Description	40 character description of the WBSE. It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template
VERNR	No. of Person Resp.	This field represents the position of the Person Responsible for a WBS Element. It will be derived from the Project Definition and can be overwritten. Dropdown values from TCJ04-PS_VERNR It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template.
ASTNR	Applicant no.	This field represent the position of the Project Financial Controller. It will be derived from the Project Definition and can be overwritten. Dropdown values from TCJ05-ASTNR. It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template.
PRCTR	Profit Center	In Syway, Profit Center represent a plant or a site or generic for GBU. It will be derived from the Project Definition Internal Information Display only read from related PPM Item Profit center field Dropdown values from CEPC-PRCTR It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template.
PRART	Project Type	It is an attribute that serve as classification field that help to define the nature, purpose, and governance of a WBS element. They are useful for reporting, controlling, and compliance alignment. Internal Information Dropdown values from TCJ1-PRART. It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template.
BELKZ	Acct asst elem.	Tooltip : This indicator enables financial posting on the WBS element. Internal Information It will be checked in below conditions- 2. For WBS elements governed by Operational, Statistical & Recharge project profiles, activation of this checkbox is mandatory for all level 2 WBS elements. It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template where required and blank when not.
FAKKZ	Billing Element	Tooltip: This indicator enables for revenue postings. Required at level 2 for Intercompany Recharge projects Internal Information Only relevant for project profile of project maintained in PSPHI is a Recharge Project
AKSTL	Request. cost center	Tooltip Requesting Cost Center that owns the asset. The reqc CC must be in same company code as the resp CC. This CC is automatically copied to AUC. Internal Information Refer master data table field CSKS-KOSTL for allowed values. A preload check is to be done to confirm that the Company Code of the Request. cost center is equal to the company code to the Company Code of the Responsible Cost Center's (FKSTL) Company Code.
FKSTL	Responsible CC	Cost Center responsible for delivery of work. Internal Information Refer master data table field CSKS-KOSTL for allowed values. It is a Required Field: Required for all account assigned WBS elements. Preload Check to be done to confirm that this is field in the Data Collection Template when required.
WERKS	Plant	Plant represent a site of the WBS element. Mandatory for all WBS elements. Internal Information Display only read from related PPM Item plant field It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template
USR10	Cross System	This checkbox field, will be selected when inter-company services are needed for a WBS element.
KOSTL	CCtr posted actual	Tooltip This field represents the receiver Cost Center of actual cost for any actual financial posting on the statistical WBS element. This field is relevant for WBS element with Project Type Capital Lease Internal Information Dropdown values from KOSTL
IMPRF	Investment Profile	Tooltip Investment Profile on WBS element is used to enable auto generation of AuC w.r.t. predefined asset class. - at level 2 WBS element if the CAPEX field is selected and project type is "Capital Spares" Investment Profile can not be changed once WBS is settled. Internal Information Dropdown values from TAPRF-IVPRO for allowed values. Preload validation required to ensure field is filled when required.
FUNC_AREA	Functional Area	Functional Area is an organisational unit used to classify expenses based on their purpose or function. Dropdown values from TFKB-FKBER.
STUFE	Level	In a project, WBS elements are structured across multiple levels to form a tree-like hierarchy for better project controlling and monitoring.
UP	WBS_UP	This field represents the immediate superior WBS element required for establishing parent-child relationships in the WBS hierarchy, this is a required field for level 2 WBS elements. Can only be a WBS element within the same Project As per project coding mask F-000000-00-00-XX-XX-XX Internal Information Can only be a WBS element within the same project. It is a Required Field for level 2 and lower: Preload Check to be done to confirm that this is field in the Data Collection Template when required.
LEFT	WBS_LEFT	This field represents the left-adjacent WBS element in the same hierarchy level required for navigating sibling relationships within a WBS hierarchy. Can only be a WBS element within the same Project. As per project coding mask F-000000-00-00-XX-XX-XX Internal Information Can only be a WBS element within the same project. Preload Check to be done to confirm that this is field in the Data Collection Template when required.
SYCAP_OPX	CAPEX / OPEX	This field identifies expense is CAPEX or OPEX. For Direct Asset Purchase, Capital Lease and Capital Spares this indicator is mandatory at level 2 WBS elements. Internal Information Drop down field selection will allow any of CAPEX, OPEX or blank entry. Preload Check to be done to confirm that this is field in the Data Collection Template when required.
SYMAIN_EVT	Maintenance event	This field is used to determine the settlement rule receiver for the relevant maintenance Work Order. This field is used to determine the settlement rule receiver for the relevant maintenance Work Order. This field will be applicable for projects with Project Profile ZPS0001 & ZPS0002 at level 3 & 4 WBS element. Internal Information Data source for this field will be T352R-REVNR.
SYSITE	Site	Tooltip: A Site represents the highest-level physical boundary of Syensqo — a distinct, real-world physical location where Syensqo operates or maintains responsibility. Internal Information Currently this is a free text field which is optional in conjunction with plant - either plant or Site must be filed.
ZREVIEW_STATUS	Review Status	Tooltip Allows indication of records readiness for load. Internal Information Dropdown with review status values

In conjunction with DCT business user will be provided with Person Responsible / Applicant list for reference.

I2M - Item Type to Phase 2 WBS Template - this DCT will be maintained by the data team and is used in transformation

Field Name	Field Description	Rule
ITEM_TYPE	ITEM_TYPE	Item type Internal Information Refer configuration table field /RPM/ITEM_TYPE- ITEM_TYPE for allowed values. It is a Required Field and Key
ITEM_PHASE	ITEM_PHASE	Phase Internal Information Dropdown field from /RPM/ITEM_PHASE Required and Key
WBS_ELEMENT	WBS_ELEMENT	WBS Internal Information Dropdown field from DCT 1019 WBS Element - POSID, display Code and Description Required
WBS_ELEMENT_DESC	DESCRIPTION	Phase Description Required
ZDefault	Default	Used as the default phase when no phase assignment is done for the WBS element

Extraction Dependencies

Item #	Step Description	Team Responsible

Transformation

The Target fields are mapped to the applicable Legacy field that will be its source. 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	PF2/WP2	PRPS	POSID	WBS element	S/4 Hana	PRPS	POSID	WBS element	For sourceWBS element numbering is based on the rules set out in section Parent/Number/Level Determination below.
2	DCT	PRPS	POSID	WBS element	S/4 Hana	PRPS	POSID	WBS element	Manually copy from Non ECC source
3	PF2/WP2	PRPS	POST1	Description	S/4 Hana	PRPS	POST1	Description	Copy from source to target system
4	DCT	PRPS	POST1	Description	S/4 Hana	PRPS	POST1	Description	Manually copy from Non ECC source
5	PF2/WP2	PRPS	VERNR	No. of Person Resp.	S/4 Hana	PRPS	VERNR	No. of Person Resp.	Value Mapping: Responsible Person to new Person Responsible Position ID
6	DCT	PRPS	VERNR	No. of Person Resp.	S/4 Hana	PRPS	VERNR	No. of Person Resp.	Manually copy from Non ECC source
7	PF2/WP2	PRPS	ASTNR	Applicant no.	S/4 Hana	PRPS	ASTNR	Applicant no.	Value Mapping: Applicant to new Applicant Position ID
8	DCT	PRPS	ASTNR	Applicant no.	S/4 Hana	PRPS	ASTNR	Applicant no.	Manually copy from Non ECC source
9	PF2/WP2	PRPS	PBUKR	Company code	S/4 Hana	PRPS	PBUKR	Company code	Value Mapping: Old to New Company Code
10	DCT				S/4 Hana	PRPS	PBUKR	Company code	If Source of WBS is construct then Copy from Project Definition using target PSPHI
11	All				S/4 Hana	PRPS	PKOKR	Controlling area	Default to "CO01"
12	PF2/WP2	PRPS	PRCTR	Profit Center	S/4 Hana	PRPS	PRCTR	Profit Center	Value Mapping: Old to New Profit Centre
13	DCT	PRPS	PRCTR	Profit Center	S/4 Hana	PRPS	PRCTR	Profit Center	Manually copy from Non ECC source
14	ALL	PRPS	PRART	Project Type	S/4 Hana	PRPS	PRART	Project Type	Manually copy from Non ECC source
15	PF2/WP2	PRPS	BELKZ	Acct asst elem.	S/4 Hana	PRPS	BELKZ	Acct asst elem.	Copy from source to target system
16	DCT	PRPS	BELKZ	Acct asst elem.	S/4 Hana	PRPS	BELKZ	Acct asst elem.	Manually copy from Non ECC source
17	All	PRPS	FAKKZ	Billing Element	S/4 Hana	PRPS	FAKKZ	Billing Element	Manually copy from Non ECC source
	All				S/4 Hana	PRPS	AKOKR	CA req. cost center	Default to "CO01"
	PF2/WP2	PRPS	AKSTL	Request. cost center	S/4 Hana	PRPS	AKSTL	Request. cost center	Value Mapping: Old to New Cost Centre
	DCT	PRPS	AKSTL	Request. cost center	S/4 Hana	PRPS	AKSTL	Request. cost center	Manually copy from Non ECC source If Blank then Copy from FKSTL
	ALL				S/4 Hana	PRPS	ABUKR	Requesting co. code	Default from Cost Center using AKSTL
18	PF2/WP2	PRPS	FKSTL	Responsible CC	S/4 Hana	PRPS	FKSTL	Responsible CC	Value Mapping: Old to New Cost Centre
19	DCT	PRPS	FKSTL	Responsible CC	S/4 Hana	PRPS	FKSTL	Responsible CC	Manually copy from Non ECC source
20	All				S/4 Hana	PRPS	FKOKR	CA resp. cost center	Default to "CO01"
21	All				S/4 Hana	PRPS	FABKL	Factory Calendar	Copy Factory Calendar from Plant using Field WERKS
22	PF2/WP2	PRPS	PWPOS	Currency	S/4 Hana	PRPS	PWPOS	Currency	Copy from Project Definition
23	DCT				S/4 Hana	PRPS	PWPOS	Currency	Copy from Project Definition
24	PF2/WP2	PRPS	WERKS	Plant	S/4 Hana	PRPS	WERKS	Plant	Value Mapping: Old to New Plant
25	DCT	PRPS	WERKS	Plant	S/4 Hana	PRPS	WERKS	Plant	Manually copy from Non ECC source
26	ALL	PRPS	USR08	Expected Capitalization Date	S/4 Hana	PRPS	USR08	Expected Capitalization Date	Manually copy from Non ECC source
27	ALL	PRPS	USR10	Cross System	S/4 Hana	PRPS	USR10	Cross System	Manually copy from Non ECC source
28	ALL				S/4 Hana	PRPS	SCOPE	Object class	Copy from Project Definition
29	ALL				S/4 Hana	PRPS	XSTAT	Statistical	Set to X for WBS Elements of Project Profile ZPS0003 Set to X for WBS elements with Project Type 16
30	DCT	PRPS	KOSTL	CCtr posted actual	S/4 Hana	PRPS	KOSTL	CCtr posted actual	Manually copy from Non ECC source
31	PF2/WP2	PRPS	IMPRF	Investment Profile	S/4 Hana	PRPS	IMPRF	Investment Profile	Value Mapping: Old to new Investment Profile
32	DCT	PRPS	IMPRF	Investment Profile	S/4 Hana	PRPS	IMPRF	Investment Profile	Manually copy from Non ECC source
33	PF2/WP2				S/4 Hana	PRPS	FUNC_AREA	Functional Area	Copy from Project Definition PROJ-FUNC_AREA
34	DCT	PRPS	FUNC_AREA	Functional Area	S/4 Hana	PRPS	FUNC_AREA	Functional Area	Manually copy from Non ECC source
35	PF2/WP2/CONSTRUCT_2	PRPS	PSPHI	Project Definition	S/4 Hana	PRPS	PSPHI	Project Definition	Project Definition number determination rules.
36	DCT	PRPS	PSPHI	Project Definition	S/4 Hana	PRPS	PSPHI	Project Definition	Manually copy from Non ECC source
37	ALL	PRPS	STUFE	Level	S/4 Hana	PRPS	STUFE	Level	Manually copy from Non ECC source
38	ALL	PRPS	UP	WBS_UP	S/4 Hana	PRPS	PRHI-UP	WBS_UP	Manually copy from Non ECC source
39	ALL	PRPS	LEFT	WBS_LEFT	S/4 Hana	PRPS	PRHI-LEFT	WBS_LEFT	Manually copy from Non ECC source
40	ALL	PRPS	SYCAP_OPX	Capex / OPEX	S/4 Hana	PRPS	SYCAP_OPX	CAPEX/ OPEX	Manually copy from Non ECC source
41	ALL	PRPS	SYMAIN_EVT	Maintenance event	S/4 Hana	PRPS	SYMAINT_EVT	Maintenance event	Manually copy from Non ECC source
42	ALL	PRPS	SYTRADE_CC	Trading company code	S/4 Hana	PRPS	SYTRADE_CC	Trading company code	Manually copy from Non ECC source
43	ALL	PRPS	SYSITE		S/4 Hana	PRPS	SYSITE	Site	Manually copy from Non-ECC source

List of Custom Target Reports for this object is maintained here: Conversion Specification - Custom Reports Register.

The following does not apply to WBS elements created with Source system Construct DCT.

The transformation of WBS element structure from the legacy systems is changed from a multi-level structure to a formal phase based approach with adherence to pre-approved project structures across all project types.

To facilitate this only WBS elements flagged account assignment from PF2/WP2 will be created and assigned to the project structures in S/4 which has already created during PPM item creation (CNV-1022), (relevancy criteria for migration is the same), while a mapping of WBS elements will be provided as output.

The following is executed for WBS elements across a single project at a time.

Parent/Number/Level Determination

Project Definition number determination rules.

Project Definitions and phase level WBS elements for PPM relevant projects (All projects with source systems Construct_2, SAPWP2 and SAPPF2) are created during load of 1022 Portfolio Items. As part of the load the Legacy Project ID is stored in S/4 PROJ - USR00. This field will be used to retrieve the new Project Definition number from PROJ-PSPID_EDIT.

This is the target Project Definition Number PSPHI

Phase level WBS element number determination rules.

1. Target Structure, use mapping table between Item type of the associated PPM item and Project template, DCT I2M - Item Type to Phase 2 WBS Template, as basis for the maintenance of the project structure.

The Project component of the WBS_ELEMENT, first 8 characters, template DCT is replaced with the target PSPHI retrieved above.

examples

ITEM_TYPE	ITEM_PHASE	WBS_ELEMENT	PSPHI	PHASE - POSID
Z003 - Industrial 2 Phase	SG02-TC	T-900003-01	A-000001	A-000001-01
Z004 - New Product Introduction	SG02	T-900004-01	A-000002	A-000002-01
Z004 - New Product Introduction	SG03	T-900004-02	A-000002	A-000002-02

Level and Number determination

The account assignment WBS elements from the DCT is now mapped to the phase and the new WBS Number determined.

1. In order to do this we use the phase assigned to the wbs in the DCT, if no phase is assigned in the source then the default phase from the Template is assigned.

2. Sort the WBS element by Phase.

3. WBS elements are assigned to be assigned to the WBS element from the mapping table

3.1 Source AUC - From source system select all WBS elements for the project Investment Profiles

Loop by Source AUC WBS element assigning if count is >0

TARGET - PRHI-UP = PHASE-POSID of the phase assigned

Target - POSID = PHASE-POSID + .01 (incrementing by .01 for each subsequent WBS element (such that first would be A.0000001.01 second A.0000001.02 and so forth)

TARGET - PRPH-LEFT = Empty for first WBS at level, after that, previous WBS at same level

Target - STUFE = PARENT STUFE +1

3.1.1 Lower Levels - For each SOURCE AUC see if any lower level WBS elements with account assignment active and Settlement receiver object is a WBS element in subsequent levels taking note that the relationship may be more than 1 level lower. This is done using PSHI where SOURCE AUC WBS element is maintained in up.

Loop by Source CHILD WBS element assigning

TARGET - PRPH-UP =Target - POSID from 3.1 above.

TARGET - POSID = POSID from 3.1 above + .01 (incrementing by .01 for each subsequent WBS element (such that first would be A.0000001.01.01 second A.0000001.01.02 and so forth)

TARGET - PRPH-LEFT = Empty for first WBS at level, after that, previous WBS at same level

TARGET - STUFE= PARENT STUFE +1.

3.2 Source Opex - Any WBS elements which have not been assigned to the structure is now assigned to PARENT WBS from 1.1 This takes care of situations where there is no Capital settlements in the parent child relationships but where postings exist.

Loop at SOURCE OPEX WBS element - assigning

TARGET - PRHI-UP = PARENT from 1 above.

Target - POSID = Parent PSPNR + .01 (increments continue )

TARGET - STUFE= PARENT STUFE +1

Transformation Mapping

Mapping Table Name	Mapping Table Description
T001	Value Mapping: Currency From Company Code
Company Code	Value Mapping: BUKRS: Old Company Code 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 Plant to New Plant
Profit Center	Value Mapping: Old to New Profit Centre
Applicant	Value Mapping: Applicant to new Applicant Position ID
Person Responsible	Value Mapping Responsible Person to new Person Responsible Position ID
Investment Profile	Value Mapping: Investment Profile Old to New

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
1	Ensure all the fields that require value mapping, as stipulated. Mapping tables, have the correct values mapped and imported into tool.	Syway Data Team
2	Person Responsible and Applicant Position ID interface has been executed	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
WBS Ids aligned with different number ranges per instance.

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 CNMASSCREATE or Migration cockpit	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 CN41N report	Data Team
6	Generate post load report if step 5 is validated	Data Team

Load Phase and Dependencies

Configuration

Item #	Configuration Item
1	Project Coding Mask
2	Company Code
3	Controlling Area
4	Project Type
5	Factory Calendar
6	Currency Code
7	Plant
8	Investment Profile
9	Functional Area
10	Define Tolerance Limits
11	WBS Status Profile
12	Settlement Profile
13	Budget Profile
14	Project Profile
15	Validations and Substitutions

Conversion Objects

Object #	Preceding Object Conversion Approach
1022	Portfolio Item
1024	Project Definition
1074	Cost Center

Error Handling

Error Type	Error Description	Action Taken
Invalid Data	Project Definition does not exist	Correct upload data, review load of CNV-1024
Invalid Data	WBS Element already exist	Correct upload data.
Invalid Data	Person Responsible does not exist	Correct upload data
Invalid Data	Applicant does not exist	Correct upload data
Duplicate Records	More than one WBS element per Provision type per company code/plant based on project type	Remove Duplicate values from DCT
Duplicate Records	Trading partner is filled and appears more than once per Recharge Project	Remove Duplicate values from DCT
System Validation	All standard WBS element validations to be adhered to	Correct upload data

Post-Load Validation

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 or standard 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 Project Definition in target S/4 HANA were loaded correctly via Project Builder display and table PROJ

Business

Completeness

Task	Action
Verify template Project data - Project Definition	Extract data from PS report CN41N in S/4 Hana

Accuracy

Task	Action
Verify template Project data - Project Definition	Extract data from PS report CN41N in S/4 Hana

Key Assumptions

Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
WBS - CAPEX, OPEX, Statistical is in scope based on data design and any exception requested by business.
The DCT should validate the project WBS coding mask numbering as per the SAP instance config.
Validation / substitution might required to switched off at the time of load.

Change log

Version	Published	Changed By
CURRENT (v. 85)	Apr 23, 2026 11:34	KOHN-ext, Jacob
v. 88	Apr 23, 2026 11:07	KOHN-ext, Jacob
v. 87	Apr 23, 2026 06:13	KOHN-ext, Jacob
v. 86	Apr 22, 2026 13:02	KOHN-ext, Jacob
v. 85	Apr 22, 2026 10:39	KOHN-ext, Jacob
v. 84	Apr 22, 2026 09:35	KOHN-ext, Jacob
v. 83	Apr 22, 2026 09:26	KOHN-ext, Jacob
v. 82	Apr 21, 2026 12:52	KOHN-ext, Jacob
v. 81	Mar 11, 2026 12:05	KOHN-ext, Jacob
v. 80	Mar 11, 2026 11:55	KOHN-ext, Jacob

Go to Page History

Apr 29, 2026	Actor	Type	Activity	Version
Revision under Review	KOHN-ext, Jacob	Comment	commented 11:53 am Will be changed to USR01 based on latest discussions with functional
Apr 23, 2026
	KOHN-ext, Jacob	Edit	updated the page at 11:07 am
	KOHN-ext, Jacob	State	changed state to Revision under Review at 6:24 am	v87
Revision in Progress	KOHN-ext, Jacob	Comment	commented 6:14 am KOSTL_Cost Centre_XREF
Revision in Progress	KOHN-ext, Jacob	Edit	updated the page at 6:13 am
Apr 22, 2026
	VILLI-ext, Ramaraj	Comment	commented 3:07 pm Getting the PROJ.FUNC_AREA from table from S/4 System
		Comment	commented 3:03 pm Yes Resolved
		Comment	commented 3:02 pm Yes Resolved

Workflow history

Space shortcuts

Page tree

Purpose

Conversion Scope

Identification Logic

Target Design

Data Cleansing

Open Projects without posting since selected financial year

Selection

Open WBS elements, not relevant for migration, with assigned maintenance orders

Open Projects where WBS Family is empty

Open Projects with locked status

Conversion Process

Extraction

Extraction Run Sheet

Extraction Dependencies

Transformation

Transformation Run Sheet

Transformation Dependencies

Pre-Load Validation

Project Team

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

Workflow history

Space shortcuts

Page tree

CNV-1026 WBS - CAPEX, OPEX, Statistical

Purpose

Conversion Scope

Identification Logic

Target Design

Data Cleansing

Open Projects without posting since selected financial year

Selection

Open WBS elements, not relevant for migration, with assigned maintenance orders

Open Projects where WBS Family is empty

Open Projects with locked status

Conversion Process

Extraction

Extraction Run Sheet

Extraction Dependencies

Transformation

Transformation Run Sheet

Transformation Dependencies

Pre-Load Validation

Project Team

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