Status
Owner	KOHN-ext, Jacob
Stakeholders	NADAR-ext, Parvati BIDALIA-ext, Kuldeep AGGARWAL-ext, Vikhyat UPADHYAY-ext, Anjali

Purpose

The purpose of this document is to define the conversion approach to maintain the project status in S/4 HANA.

Project and WBS element status consists of System and user statuses which together controls business functions allowed on the object.  In the SyWay solution there is integration between the status of the project in PS and the PPM Item.

Conversion Scope

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

There are 2 group go-live as below:

• Group 1 go-live (1 July 2028) (Source System: PF2)
  • Selection based on Company Code
• Group 2 go-live (1 Jan 2029) (Source System: WP2)
  • Selection based on Company Code

Note:  There is possibility to shift into 1 go live date, this option is currently still being considered.

Projects created in each group are treated separately.

Projects created for the go-live group in S/4 with Created status are to be released to allow WBS element to be used for financial posting, excludes template projects.  Template project status changes are included in CNV-1019.

The status of Projects and WBS elements migrated from Legacy system is aligned with the status in Legacy system, where the status in the legacy system is not created or released.

Relevancy Criteria

The data from legacy system includes:

1. Projects Definition migrated to S/4 Hana where
   1. Project System Status is Account assignment Locked, Closed, Technically Complete, Master Data Locked or
   2. Project User Status is Maintained
2. WBS elements migrated to S/4 Hana where
   1. WBS System Status is Account assignment Locked, Closed, Technically Complete, Master Data Locked or
   2. WBS User Status is Maintained
3. Projects, without reference to PPM items created in S/4 with system status Created 

The data from legacy system excludes:

1. Template projects in S/4

Before Posting Financials:

Release all projects in S/4 (Scenario 1).   

This will allow the posting of actuals and the settlement of cost where relevant by 

• CNV-9031 Project-Actual GL Line Items (PNL-WBS for AuC)
• CNV-9032 GL Line Items (PNL Internal Order, Statistical/Opex WBS)

After Posting Financials :

1. WBS Elements created in CNV-1022 Portfolio Items - update WBS element status as per the status in legacy system
   1. This includes system and user status (Scenario 2)
2. Projects Created in CNV-1022 Portfolio items - update project status as per the status in legacy system
   1. This includes system and user status (Scenario 3)

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
WP2	Project Definitions with Reference to PPM Items		S/4
WP2	WBS elements with Mapping from CNV-1026		S/4
PF2	Project Definitions with Reference to PPM Items		S/4
PF2	WBS elements with Mapping from CNV-1026		S/4
S/4	Projects in S/4 with created status		S/4

Identification

Project Status

Select Object number from table PROJ for PSPID equals Legacy ID

Select Statuses from table JEST using Object Number

1. Where JEST-INACT not equal to X
2. STATUS is Locked (I0043) ,Technically Complete (I0045), Closed (I0046), Account Assignment Locked (I0064), Master Data Locked (I0065) or any user statut (E*)

WBS Status

Select Object number from table PRPS for PSPHI equals Legacy ID

Select Statuses from table JEST using Object Number

1. Where JEST-INACT not equal to X
2. STATUS is Locked (I0043) ,Technically Complete (I0045), Closed (I0046), Account Assignment Locked (I0064), Master Data Locked (I0065) or any user status (E*)

S/4 Projects Status Created (excluding template projects)

Select Object number from table PROJ where PSPID <> T*

Select Statuses from table JEST using Object Number where status is Created (I0001)

And created by Migration User

Additional Information

Multi-language Requirement

Not Applicable

Document Management

Not Applicable

Legal Requirement

Not Applicable

Special Requirements

Not Applicable

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.

Project Level

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
PROJ	PSPID	PS_PSPID	Project Definition	CHAR	24	Mandatory
PROJ	OBJNR	J_OBJNR	Project Object Number	CHAR	22	System Generated
TJ02T	TXT04	J_TEXT_04	System Status Text	CHAR	4	Optional
TJ30T	TXT04	J_TEXT_04	User Status Text	CHAR	4	Optional
JEST	OBJNR	J_OBJNR	Object Number	CHAR	22	System Generated
JEST	STAT	J_STATUS	Status	CHAR	5	System Generated
JEST	INACT	J_INACT	Indicator Status is inactive	CHAR	1	System Generated
JEST	CHGNR	J_CHGNR	Change Number	NUMC	3	System Generated

WBS Level

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
PRPS	POSID	PS_POSID	WBS ID	CHAR	24	Mandatory
PRPS	OBJNR	J_OBJNR	WBS Object Number	CHAR	22	System Generated
TJ02T	TXT04	J_TEXT_04	System Status Text	CHAR	4	Optional
TJ30T	TXT04	J_TEXT_04	User Status Text	CHAR	4	Optional
JEST	OBJNR	J_OBJNR	Object Number	CHAR	22	System Generated
JEST	STAT	J_STATUS	Status	CHAR	5	System Generated
JEST	INACT	J_INACT	Indicator Status is inactive	CHAR	1	System Generated
JEST	CHGNR	J_CHGNR	Change Number	NUMC	3	System Generated

Data Cleansing

All cleansing requirements dealt with in CNV-1024 Project Definition and CNV-1026 WBS - CAPEX, OPEX, Statistical

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

Not Applicable

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.

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 data from source system based on relevancy rule	SyWay Data Team
2	Extract data from S/4 system based on relevancy rule	SyWay Data Team
3	Perform preliminary completeness check, data quality check.	SyWay Data Team
4	Raise issues as defects if Req # 1 to 2 are not met	SyWay Data Team
5	Repeat Req # 1 to 3 if required	SyWay 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

Data Collection Template (DCT)

No requirement for collection

Field Name	Field Description	Rule

Extraction Dependencies

List the steps that need to occur before extraction can commence

Item #	Step Description	Team Responsible
1	Successful Load of CNV-1022 Portfolio Items	SyWay Data Team
2	Successful load of CNV-1024 Project Definitions	SyWay Data Team
3	Successful load of CNV-1026 WBS CAPEX, OPEX, Statistical	SyWay Data Team

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:

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	Execute Load and perform Transformation	Data team
2	Monitor the transformation progress and ensure performance and completion is within allowed timeframe	Data team
3	Review and Validate Error and Preload Reports	Data Team
4	Generate data load count.	Data team
5	Generate Load Files	Data Team
6	Log errors as defects, if any and address resolutions. Close defects.	Data team
7	Re-transform and re-validate the Pre-load reports if necessary.	Data team
8	Validate the transformed file as part of pre-load validation, raise data defects or provide the pre-load sign-off.	Business
9	Analyze and resolve any pre-load defects logged by business.	Data team
10	Repeat steps 7 to 10 if necessary	Data team
11	Proceed to pre-load validations	Data team

Transformation Rules

The transformation is done in 3 Scenarios.

Scenario 1.

Update the status of projects in S/4 in Created Status- the below transformation assumes BAPI_BUS2001_SET_STATUS or transaction CNMASSSTATUS

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
	S/4	PROJ	PSPID	Project Definition	S/4 Hana	PROJ	PSPID	Project Definition	Copy from Source
					S/4 Hana	TJ02T	TXT04	Status	Default to "REL"

Scenario 2

Align the status of WBS elements migrated through CNV-1026 with the status of the wbs element in legacy system.  The below transformation assumes BAPI_BUS2054_SET_STATUS or transaction CNMASSSTATUS

The status from legacy may be mapped to either a system or a user status in S/4 Hana

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
	PF2/WP2	PRPS	POSID	WBS Element	S/4 Hana	PRPS	PSPID	WBS Element	Mapping Table Old WBS Element to New WBS
	PF2/WP2	JEST	STATUS	Status	S/4 Hana	TJ02T	TXT04	System Status	Mapping: Legacy_PRPS_Status where Legacy status has Hana_System_Status
	PF2/WP2	JEST	STATUS	Status	S/4 Hana	TJ30T	TXT04	User Status	Mapping:  Legacy_PRPS_Status where Legacy status has Hana_User_Status

Scenario 3

Align the status of Project Definition, with Legacy ID's, with status of Project Definition in legacy system.  The below transformation assumes BAPI_BUS2001_SET_STATUS or transaction CNMASSSTATUS

The status from legacy may be mapped to either a system or a user status in S/4 Hana

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
	PF2/WP2	PROJ	PSPID	Project Definition	S/4 Hana	PROJ	PSPID	Project Definition	Mapping Table Old WBS Element to New WBS
	PF2/WP2	JEST	STATUS	Status	S/4 Hana	TJ02T	TXT04	System Status	Mapping: Legacy_PRPS_Status where Legacy status has Hana_System_Status
	PF2/WP2	JEST	STATUS	Status	S/4 Hana	TJ30T	TXT04	User Status	Mapping:  LLegacy_PRPS_Status where Legacy status has Hana_User_Status

Transformation Mapping

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

Mapping Table Name	Mapping Table Description
Legacy_PRPS_Status	Mapping System and User Status from Legacy Systems to S/4 Status Source System, Object Type (PD or WBS), Legacy Status (Number), Hana_System_Status (TXT04), Hana_User_Status (TXT04)
WBS Elements	POSID: Old WBS Elements to New WBS Elements

Status Mapping

Source	Object Type	Legacy Status	System Status Description	S4_System_Status	System Status Description	S4_User_Status
PF2	Project	I0045	Technically completed	TECO	Technically completed
PF2	Project	I0046	Closed	CLSD	Closed
PF2	Project	I0065	Master data locked	MDLK	Master data locked
WP2	Project	I0045	Technically completed	TECO	Technically completed
WP2	Project	I0065	Master data locked	MDLK	Master data locked
WP2	Project	I0046	Closed	CLSD	Closed
WP2	WBS	I0045	Technically completed	TECO	Technically completed
WP2	WBS	I0046	Closed	CLSD	Closed
WP2	WBS	I0065	Master data locked	MDLK	Master data locked
PF2	WBS	I0045	Technically completed	TECO	Technically completed
PF2	WBS	I0046	Closed	CLSD	Closed
PF2	WBS	I0065	Master data locked	MDLK	Master data locked

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 in Section "Mapping tables", have the correct values mapped.	SyWay Data Team

Pre-Load Validation

Project Team

The following is executed for each scenario separately as the release 

Completeness

Task	Action
Verify Counts	Data team to verify the load count is the same as per identified identified from JEST.

Accuracy

Task	Action
Conversion Accuracy	SyWay I2M Data Team to verify that all fields below meet pass the checks: Mandatory Fields Field and Value Mapping Correctness Null Checks Text Length Checks
Review Error Reports	Review and correct the errors.  Achieve a zero-error record count as much as possible. Raise defects for data remediated and requiring a correction in the source data.

Business

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

Completeness

Task	Action
Verify Record Count	Business Data Owner/s to verify that the total number of relevant records 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.

Load

The load process includes:

1. Execute the automated data load into target system for each scenario separately using load tool
2. Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation

Load Run Sheet

Item #	Step Description	Team Responsible
1	Load Scenario 1 using transaction using load tool	SyWay Data Team
2	Load 3 records for < > to validate if data is loaded successfully without errors	SyWay Data Team
3	Load 3 records for < > to validate if data is loaded successfully without errors	SyWay Data Team
4	Proceed with full load if steps 2 and 3 are validated	SyWay Data Team
5	Validate few records loaded by accessing Project Report	SyWay Data Team
6	Load Scenario 2 using transaction using load tool	SyWay Data Team
7	Load 3 records for < > to validate if data is loaded successfully without errors	SyWay Data Team
8	Load 3 records for < > to validate if data is loaded successfully without errors	SyWay Data Team
9	Proceed with full load if steps 7 and 8 are validated	SyWay Data Team
10	Validate few records loaded by accessing WBS Report	SyWay Data Team
11	Load Scenario 3 using transaction using load tool	SyWay Data Team
12	Load 3 records for < > to validate if data is loaded successfully without errors	SyWay Data Team
13	Load 3 records for < > to validate if data is loaded successfully without errors	SyWay Data Team
14	Proceed with full load if steps 12 and 13 are validated	SyWay Data Team
15	Validate few records loaded by accessing Project Report	SyWay Data Team
16	Generate post load report if step 18 is validated	SyWay Data Team
17	Business to validate the post load files as part of post-load validation, raise data defects or provide the post-load sign-off.	SyWay Data Team

Load Phase and Dependencies

The project status update may be required to be executed before and after the financial postings i

• CNV-9031 Project-Actual GL Line Items (PNL-WBS for AuC)
• CNV-9032 GL Line Items (PNL Internal Order, Statistical/Opex WBS)

Generation of the Load file to consider the Project Definitions loaded to S/4 based on the Go-Live Group.

There are 2 group go-live as below:

• Group 1 go-live (1 July 2028) (Source System: PF2)
• Group 2 go-live (1 Jan 2029) (Source System: WP2)

Note:  There is possibility to shift into 1 go live date, this option is currently still being considered.

Configuration

List the Configurations required before loading can commence

Item #	Configuration Item
1	WBS User Status
2	Project Profile

Conversion Objects

Object #	Preceding Object Conversion Approach
1	1026 - WBS CAPEX, OPEX, STATISTICAL
2	9031 - Project - Actual GL Line Items (PNL - WBS for AuC)
3	9032 - GL Line Items (PNL - Internal Order, Statistical/ Opex WBS)

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
Invalid Data	Project Definition has not been created in S/4HANA hence status cannot be set	Review load of CNV-1022
Invalid Data	WBS has not been created in S/4HANA hence WBS hence status cannot be set	Review load of CNV-1026
System validation	Setting of new status not allowed due to active System / User Status	Correct upload data, review mapping rules

Post-Load Validation

Project Team

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

Completeness

Task	Action
Verify Count	SyWay I2M Data Team to verify the record count created in target S/4 HANA by accessing post load reports or standard reports (CN41n) 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 Reports like CN41N

Business

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

Completeness

Task	Action
Verify Project data - Project Definition	Extract data from PS report CN41N in S/4 Hana and compare with expected record counts

Accuracy

Task	Action
Verify Project data - Project Definition	Extract data from PS report CN41N in S/4 Hana
Reconcile	Post load report for projects with legacy project id's containing ECC Project and WBS System and User Status with S/4 Hana Project WBS element System and User Status

Key Assumptions

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