Mandatory

Only 1 Company Code allowed per PSPHI

Mandatory

Mandatory

Conditional

 It will be checked in below conditions-
1. For WBS elements governed by CAPEX project profiles, activation of this checkbox is mandatory for all elements at level 3 and subordinate levels.
2. For WBS elements governed by Operational, Statistical & Recharge project profiles, activation of this checkbox is mandatory for all WBS elements.

Conditional

Only relevant for project profile of project maintained in  PSPHI is a Recharge Project

Mandatory

Only 1 Company Code allowed per PSPHI

System Generated

Conditional

Required if IM_PROFIL is not initial

Conditional

System Generated

Conditional

Conditional

This field will be mandatory for all statistical WBS element (XSTAT = X)

Conditional

Required for CAPEX projects (with Project Profile ZPS0001) at Level 3 WBS elements if the CAPEX field is selected (STUFE=3).

Mandatory

Conditional

Required if (STUFE>1).

Can only be a WBS element within the same PSPHI.

Conditional

Can only be a WBS element within the same PSPHI.

Conditional

For project profile ZPS0001 this field will be mandatory for all STUFE >= 3

All Other profiles mandatory at all levels

Conditional

This field will be applicable when PRART =  Turnaround Projects and STUFE = 3

Conditional

Required for project profile ZPS0004 when  STUFE = 2

1026-001

Projects with no actuals / commitment / used in account assignment for maintenance orders

If the projects do not have any actual or commitments or settlement assignments in the past year, set the project to status CLSD (CJ20N)

Old project set to closed

WP2/PF2

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

Project ID assigned to the WBS elements. Refer table PROJ-PSPHI for allowed values. 

Dropdown values from PROJ-PSPHI

Unique Identifier for the WBS Element as per project coding mask.

The position ID assigned to the WBS element is based on the Project Definition created in S/4.

This field represents the position of the Person Responsible for a WBS Element and is mandatory field. It will be derived from the Project Definition and can be overwritten.

Dropdown values from TCJ04-PS_VERNR

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.

In Syway, Profit Center represent a plant or a site or generic for GBU and inherited from the Project Definition

Dropdown values from CEPC-PRCTR

This indicator enables financial posting on the WBS element.

Cost Center responsible for delivery of work. Required for WBS elements of Expense Project (Budget-managed) only.

Dropdown values from KOSTL-KOSTL for allowed values.

This field represents the receiver Cost Center of actual cost for any actual financial posting on the WBS element.

Dropdown values from KOSTL-KOSTL

Investment Profile on WBS element is used to enable auto generation of AuC w.r.t. predefined asset class.

Dropdown values from TAPRF-IVPRO for allowed values.

This field is used to determine the settlement rule receiver for the relevant maintenance Work Order.

This field will be applicable when Project Type = Turnaround Projects at level 3 WBS element

Dropdown values from 

This field will be applicable when Project Type = Intercompany Recharge. Mandatory at Level 2 WBS to determine the trading company for intercompany recharges
Dropdown values from T001-BURKS.

Instance where the project definition is to be loaded.

(Field required in DCT)

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

Load Dependent: PSPID: Old Project to new project mapping

If IMPRF Profile "" then "Opex"

Else "Capex"

Copy from Project Definition PSPHI.

Copy from source to target system

If IMPRF Profile "" then "Opex"

Else "Capex"

Copy from source to target system

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.

Conversion Accuracy

SyWay I2M Data Team to verify that all fields below meet pass the checks:

1. Mandatory Fields
2. Field and Value Mapping Correctness
3. Null Checks
4. Text Length Checks
5. 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.

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

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

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

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

Conversion Accuracy

Verify that the Project Definition in target S/4 HANA were loaded correctly via Project Builder display and table PROJ