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 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.

The status of Projects and WBS elements migrated from Legacy system is aligned with the status Legacy system, the status from legacy may be mapped to either a system or a user status in S/4 Hana.

Projects created in S/4 with status created has the system status released applied, this does not apply to template projects .

Relevancy Criteria

The data from legacy system includes:

1. Projects Definition migrated to S/4 Hana where
   1. Project System Status not Created or Released or
   2. Project User Status is Maintained
2. WBS elements migrated to S/4 Hana where
   1. Project System Status not Created or Released or
   2. Project User Status is Maintained
3. Projects in S/4 with system status Created

The data from legacy system excludes:

1. Projects not migrated to S/4

Projects with created status in S/4

This will allow the posting of actual and the settlement of cost to AUC's as required by 

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

 

Before Posting Financials (Scenario 1):

1. Projects in Created Status - Release projects to allow for posting

After Posting Financials (Scenario 2 and 3):

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
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

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 with created in 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 excluding Created (I0001) or Released (I0002)

WBS Status

Select Object number from table PRPS for PSPHI equals Legacy ID

Select Statuses from table JEST using Object Number excluding Created (I0001) or Released (I0002)

S/4 Projects Status

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

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

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
			System Status	CHAR		Optional
			User Status	CHAR		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	Information only
			System Status	CHAR		Optional
			User Status	CHAR		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.
   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 in source system but has already been captured in a Syniti DCT.

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	Ensure DCT for CNV-1024 has been collected	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

Transformation

The Target fields are mapped to the applicable Legacy field that will be its source, this is a 3-way activity involving the Business, Functional team and Data team. This identifies the transformation activity required to allow Syniti Migrate to make the data Target ready:

1. Perform value mapping and data transformation rules.
   1. Legacy values are mapped to the to-be values (this could include a default value)
   2. Values are transformed according to the rules defined in Syniti Migrate
2. Prepare target-ready data in the structure and format that is required for loading via prescribed Load Tool. This step also produces the load data ready for business to perform Pre-load Data Validation

Transformation Run Sheet

Item #	Step Description	Team Responsible
1	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	JEST	STAT	Status	Default to "REL"

Scenario 2

Update the status of WBS elements migrated through CNV-1026 where mapping exists to legacy data.  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	JEST	STATUS	System Status	Mapping: Legacy_PRPS_Status where Legacy status has Hana_System_Status
	PF2/WP2	JEST	STATUS	Status	S/4 Hana	JEST	USER_STATUS	User Status	Mapping:  LLegacy_PRPS_Status where Legacy status has Hana_User_Status

Scenario 3

Update the Project Definitions with Legacy ID's where for legacy data.  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
	S/4	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	JEST	STATUS	System Status	Mapping: Legacy_PRPS_Status where Legacy status has Hana_System_Status
	PF2/WP2	JEST	STATUS	Status	S/4 Hana	JEST	USER_STATUS	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 (PD or WBS), Legacy Status, Hana_System_Status, Hana_User_Status
WBS Elements	POSID: Old WBS Elements to New WBS Elements

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

Conversion Objects

Object #	Preceding Object Conversion Approach
	list the exact title of the conversion object of only the immediate predecessor – this will then confirm the DDD (Data Dependency Diagram)

Error Handling

The table below depicts some possible system errors for this data object during data load. All data load error is to be logged as defect and managed within the Defect Management

Error Type	Error Description	Action Taken

Post-Load Validation

Project Team

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

Completeness

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

Accuracy

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

Business

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

Completeness

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

Accuracy

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

Key Assumptions

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

Any additional key assumptions.

See also

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log