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 is treated separately.

Projects created for the go-live group in S/4 with Created status is to be released to allow WBS elements to be used, 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 Legacy system.

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 (Examples are Technically Complete or Locked) or
   2. Project User Status is Maintained
2. WBS elements migrated to S/4 Hana where
   1. WBS System Status not Created or Released (Examples are Technically Complete or Locked) or
   2. WBS User Status is Maintained
3. Projects in S/4 with system status Created 

The data from legacy system excludes:

1. Projects for Template projects

Before Posting Financials (Scenario 1):

Release projects created in the group with created status in S/4.   

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

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

1. Where JEST-INACT not equal to X
2. excluding Created (I0001) or Released (I0002)

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)

Additional Information

Multi-language Requirement

Not Applicable

Document Management

Not Applicable

Legal Requirement

Not Applicable

Special Requirements

Not Applicable

Target Design

The technical design of the target for this conversion approach.

Project Level

WBS Level

Data Cleansing

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

Conversion Process

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

Data Privacy and Sensitivity

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

Selection Screen

Data Collection Template (DCT)

Extraction Dependencies

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

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

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

Scenario 3

Update the Project Definitions with Legacy ID's where for legacy data.  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

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

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

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

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

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.

See also

Change log