Status

Peer Review

Page Status

Owner

NADAR-ext, Parvati

Stakeholders

KOHN-ext, Jacob STEFANESCU-ext, Aurelia VAN DE REE-ext, Ramon UPADHYAY-ext, Anjali

Purpose

The purpose of this document is to define the conversion approach to create Operative Project Definition in S/4 HANA.

In SAP PS, the project definition acts as a framework that provides a binding structure for organizational element of a project, such as Work Breakdown Structures. It serves as the top-level element for creating a project, defining default values for company code, plant, and responsible persons, and is essential for structuring, planning, and controlling all aspects of a project, from initiation to closure.

Conversion Scope

The scope of this document covers the approach for converting active Project Definition from Legacy Source Systems into S/4HANA following the Master Data Design Standard- Project Definition.

As per SyWay design, there are two ways to create an Operative Project definition based on the scenarios,

Scenario 1: PS Project definition with WBS element hierarchy (Level 1 & 2) can be automatically created from the approved PPM item once stage-gate 1 is approved. This process involves mapping the PPM item type to a predefined PS template project (created as per CVN-1019 Template Projects) with the Decision Flow Management settings in the SAP system.

A project definition is automatically created for the specified PPM item types, using the corresponding project profile and applicable project coding mask. The conversion approach is dealt is defined with in CNV-1022 Portfolio Item.

All project definition (new project profile ZPS0001, ZPS0002) relevant to PPM item type linking will be created from PPM items and is excluded from this conversion scope.

Scenario 2: A project definition created manually independent of the PPM item, with the data being sourced using a DCT (Data Collection Template).

Conversion scope includes all projects that belong to Scenario 2, except statistical expense project. Statistical projects (with project profile ZPS0003 - Statistical Expense) are created as needed in S/4 Hana

Below project profiles are configured to allow the creation of a project definition directly in the Project System, without requiring integration with a Portfolio and Project Management (PPM) item.

AA

PS Project Profile	PRJID	PS Coding Mask	DCT
ZPS0004 - Intercompany Recharges	F
PPM Item Type	PS Project Profile	PRJID	PS Coding Mask	Description
Z001 Industrial Project with Qualification	ZPS0001 - CAPITAL/ Operational Expense	A	-000000-00-00-XX-XX-XX	CAPITAL/ Operational Expense Projects
Z002 Industrial Project	ZPS0001 - CAPITAL/ Operational Expense
	-000000-00-00-XX-XX-XX
CAPITAL/ Operational Expense Projects	Z003 Industrial Project - Simple ?	ZPS0001 - CAPITAL/ Operational Expense
One Project per CoCode
ZPS0005 - Provisional Expense	F	-000000-00-00-XX-XX-XX
CAPITAL/ Operational Expense Projects
Z004 New Product Introduction	ZPS0001 - CAPITAL/ Operational Expense	R	-000000-00-00-XX-XX-XX	R&I Projects
Z005 Product & Process Improvement	ZPS0001 - CAPITAL/ Operational Expense	R	-000000-00-00-XX-XX-XX	R&I Projects
Z006 Customer and business support	ZPS0001 - CAPITAL/ Operational Expense	R	-000000-00-00-XX-XX-XX	R&I Projects
Z007 OPD Opportunity Development	ZPS0002 - Operational Expense	R	-000000-00-00-XX-XX-XX	R&I Projects
Z008 IT Full Lifecycle Project	ZPS0001 - CAPITAL/ Operational Expense	A	-000000-00-00-XX-XX-XX	CAPITAL/ Operational Expense Projects
Z009 IT Small Project	ZPS0001 - CAPITAL/ Operational Expense	A	-000000-00-00-XX-XX-XX	CAPITAL/ Operational Expense Projects
Z010 Opex Project	ZPS0002 - Operational Expense	E	-000000-00-00-XX-XX-XX	Internal/ Operational Projects
Z011 Turnaround Projects	ZPS0001 - CAPITAL/ Operational Expense	A	-000000-00-00-XX-XX-XX	CAPITAL/ Operational Expense Projects
Z012 Direct Asset Purchase	ZPS0001 - CAPITAL/ Operational Expense	A	-000000-00-00-XX-XX-XX	CAPITAL/ Operational Expense Projects
Z013 Capitalised Maintenance	ZPS0001 - CAPITAL/ Operational Expense	A	-000000-00-00-XX-XX-XX	CAPITAL/ Operational Expense Projects
Z014 Capital Lease	ZPS0001 - CAPITAL/ Operational Expense	A	-000000-00-00-XX-XX-XX	CAPITAL/ Operational Expense Projects
Z017-New Application Development	ZPS0001 - CAPITAL/ Operational Expense	R	-000000-00-00-XX-XX-XX	R&I Projects
Z018-Capital Spares	ZPS0001 - CAPITAL/ Operational Expense	A	-000000-00-00-XX-XX-XX	CAPITAL/ Operational Expense Projects

All project definition (new project profile ZPS0001, ZPS0002) relevant to PPM item type linking will be created from PPM items and is excluded from this conversion scope.

Scenario 2: A project definition created manually independent of the PPM item, with the data being sourced using a DCT (Data Collection Template).

These projects are:

Statistical Expense Projects: Used for tracking non-capital costs. These are statistical project without Budget, created by GBS and no PPM item is required.
Intercompany Recharges: Used for Inter company service recharge cost allocations. These are operational projects have billing WBS element without Budget, created by GBS and no PPM item is required.
Provisional Expense: Used for expense provision. These are operational projects without Budget, created by GBS and no PPM item is required.

Conversion scope includes all projects that belong to Scenario 2, except statistical project expense project. Statistical projects are created as needed in S/4 Hana

The conversion will ensure all projects are aligned to the defined project coding mask and relevant Organizational Units as designed for the target S/4 Hana landscape.

Below project profiles are configured to allow the creation of a project definition directly in the Project System, without requiring integration with a Portfolio and Project Management (PPM) item.

PS Project Profile	PRJID	PS Coding Mask	PS Coding Mask Description
ZPS0003 - Statistical Expense	F	-000000-00-00-XX-XX-XX	Statistical/ Recharge & Provision Projects (created as needed)
ZPS0004 - Intercompany Recharges	F	-000000-00-00-XX-XX-XX	Statistical/ Recharge & Provision Projects
ZPS0005 - Provisional Expense	F	-000000-00-00-XX-XX-XX	Statistical/ Recharge & Provision Projects

Scope include:

Extracting active Project Definition from SAP ECC systems WP2 and PF2 which has maintenance orders.
Extracting existing active Internal order having status Created / Release from SAP ECC systems WP2 and PF2.
Applying transformation and cleansing logic via Syniti to conform with the S/4HANA data model.
Loading the transformed Project definition into SAP S/4HANA while ensuring data integrity, correct assignment to project profile as per the project scenarios.

The data from legacy system includes:

All the projects below will be migrated from legacy source systems (PF2 and WP2) into S/4HANA (Within agreed timeframe), as needed.

Open Projects WBS from in scope company codes.

In addition to the migration of existing Project definitions from ECC there are also some internal orders in ECC which will be migrated to WBS elements in S4 Hana. As the project definition is a requirement for the creation of WBS elements, project definitions which does not exist in ECC will be required, these Project definitions will be defined in a DCT..

The data from legacy system excludes:

Project not in scope company code.
Project not in scope plant.
Project marked as closed / deletion flag set.

Exclude, project with project profile is ZPS0001 or ZPS0002 linked to PPM item type, ZPS0003 - Statistical Expense (created as needed in S/4 Hana).

Mapping Relevancy

Mapping relevancy for active internal order to Projects. Look for settlement rule assigned to the internal order in ECC WP2/PF2.

Internal Order SettlementMap to Project Definition1.

Internal order Settlement to CTR

list of internal order from AUFK, order category = 01 - Internal order, with status = CRTD, REL (exclude status = CLSD), get OBJNR.

OBJNR from AUFK, pass in COBRB, check for account assignment cat = CTR

Project code 'F-000000' with project profile as ZPS0003 - Statistical Expense

(To be created as needed)

2

Internal order Settlement to WBS

list of internal order from AUFK, order category = 01 - Internal order, with status = CRTD, REL (exclude status = CLSD), get OBJNR.

OBJNR from AUFK, pass in COBRB, check for account assignment cat = WBS, check WBS in PRPS = billing element = x

Project code 'F-000000' with project profile as ZPS0004 - Recharge Projects3

Internal order Settlement to order

list of internal order from AUFK, order category = 01 - Internal order, with status = CRTD, REL (exclude status = CLSD), get OBJNR.

OBJNR from AUFK, pass in COBRB, check for account assignment cat = ORD

Check if final settlement for receiver order is GL, If settlement to GL, get GL account and check in table SKA1 for which balance sheet account check = X

Project code 'F-' with project profile as ZPS0005 Provisional Projects4

Internal order Settlement to GL

list of internal order from AUFK, order category = 01 - Internal order, with status = CRTD, REL (exclude status = CLSD), get OBJNR.

OBJNR from AUFK, pass in COBRB, check for account assignment cat = GL, fetch GL account and check in table SKA1 for balance sheet account check = X

Project code 'F-' with project profile as ZPS0005 Provisional Projects

One project per company code per GBU(profit centre)

The conversion will ensure all projects are aligned to the defined project coding mask and relevant Organizational Units as designed for the target S/4 Hana landscape.

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
DCT			S/4 Hana	TBD

Additional Information

Multi-language Requirement

Project definition, should be maintained in if available:

- English (EN)
- French (FR)
- Italian (IT)
- Chinese (ZN)

Document Management

Not Applicable

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
PROJ	PSPID	PS_PSPID	Project definition	CHAR	24	Mandatory
PROJ	POST1	PS_POST1	Description	CHAR	40	Mandatory
PROJ	STSPR	PS_STSPR	WBS status profile	CHAR	8	System Generated
PROJ	VERNR	PS_VERNR	No. of Person Resp.	NUM	8	Mandatory
PROJ	ASTNR	PS_ASTNR	Applicant no.	CHAR	25	Mandatory
PROJ	VBUKR	PS_VBUKR	Company code	CHAR	4	Mandatory
PROJ	VKOKR	PS_VKOKR	Controlling area	CHAR	4	System Generated
PROJ	PRCTR	PRCTR	Profit

List of source systems and approximate number of records

SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

WP2 / PF2

Relevant Open PS Projects

S/4HANATBDWP2 / PF2Relevant Open Internal Orders (Provisional, Recharge)S/4HANATBDDCTS/4 HanaTBD

Additional Information

Multi-language Requirement

Project definition, the following four language keys must be maintained

- English (EN)
- French (FR)
- Italian (IT)
- Chinese (ZN)

Document Management

Not Applicable

Legal Requirement

Not Applicable

Special Requirements

Not Applicable

Target Design

The technical design of the target for this conversion approach.

PROJ

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
PROJ	PSPID	PS_PSPID	Project definition	CHAR	24	Mandatory
PROJ	POST1	PS_POST1	Description	CHAR	40	Mandatory
PROJ	STSPR	PS_STSPR	WBS status profile	CHAR	8	System Generated
PROJ	VERNR	PS_VERNR	No. of Person Resp.	NUM	8	Mandatory
PROJ	ASTNR	PS_ASTNR	Applicant no.	CHAR	25	Mandatory
PROJ	VBUKR	PS_VBUKR	Company code	CHAR	4	Mandatory
PROJ	VKOKR	PS_VKOKR	Controlling area	CHAR	4	System Generated
PRCTR	PRCTR	Profit Center	CHAR	10	Mandatory
PROJ	PWHIE	PS_PWHIE	Project Currency	CHAR	5	System Generated
PROJ	PLFAZ	PS_PLFAZ_CHG	Start date	DATS	8	Mandatory
PROJ	PLSEZ	PS_PLSEZ_CHG	Finish date	DATS	8	Conditional
PROJ	WERKS	WERKS_D	Plant	CHAR	4	Conditional
PROJ	KALID	FABKL	Factory Calendar	CHAR	2	System Generated
PROJ	PROFL	PROFIDPROJ	Project Profile	CHAR	7	Mandatory
PROJ	BPROF	BP_BPROFIL	Budget Profile	CHAR	6	System Generated
PROJ	BESTA	PS_BESTAND	Project stock	CHAR	1	System GeneratedGenerated
PROJ-	XSTAT	PS_XSTAT	Statistical	CHAR	1	Conditional
PROJ	PPROF	BP_PPROFIL	Planning Profile	CHAR	6	System generated
PROJ	PLINT	PLINT	Integrated Planning	CHAR	1	System generated
PROJ	FUNC_AREASLWID	FKBERSLWID	Functional AreaField key	CHAR	167	MandatorySystem generated
PROJUSR00	FUNC_AREA	USRCHAR20	FKBER	Functional AreaLegacy Project ID	CHAR	20	Conditional
PROJ	USR02	USRCHAR10	Item Type	CHAR	10	Conditional

Data Cleansing

IDCriticalityError Message/Report DescriptionRuleOutputSource System

1

C1

Projects without postings in FY -3 to be closed

Not to migrate

Report

WP2/PF2

2

C2

All active internal orders to be closed and map to Project

Map internal order to WBS as per below mapping relevancy

Report

WP2/PF2

Conversion Process

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

Image Removed

Data Privacy and Sensitivity

Not Applicable

Extraction

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

16	Mandatory
PROJ	USR00	USRCHAR20	Legacy Project ID	CHAR	20	Blank
PROJ	USR01	USRCHAR20	Item Type	CHAR	20	Blank
PROJ	USR02	USRCHAR10	Need-to-know	CHAR	10	Blank

Data Cleansing

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
	C2	All active internal orders to be closed		Report	WP2/PF2

list of internal order from AUFK, order category =select 01 with status = CRTD, REL, or Investment profile not blank (exclude status = CLSD), get OBJNR from AUFK, pass in COBRB, check for account assignment cat = WBS, CTR, ORD, GL. get list of all such internal order.

Conversion Process

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

Image Added

Data Privacy and Sensitivity

Not Applicable

Extraction

The

The data exists. Syniti Migrate connects to the source and loads the data into Syniti Migrate. There are 3 methods:

Perform full data extraction from relevant tables in the source system(s).
Perform extraction through the application layer.
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 SheetSheet

Req #	Requirement Description	Team Responsible
1	Ensure DCT is collected for Project Definition	Data Team (I2M),

Req #Requirement DescriptionTeam 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 PROJ / AUFK (internal orders) /COBRB from both source systems WP2, PF2

Data Team (Syniti)

4

Google Sheet report pre-populated with PF2 and WP2 information to be generated based on relevancy criteria

2

Perform preliminary completeness check

Technical / Basis Team

Data Team (I2M)

, Data Team (Syniti)

5

Perform data quality checks on extracted records (e.g., missing fields, invalid dates, incorrect formats


3	Raise issues as defects if Req # 1 to 2 are not met	Data Team (Syniti)
4	Repeat Req # 1 to 3 if required)	Data Team (I2M), Data Team (Syniti)

6

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

Data Collection Template (DCT)

Target Ready Data Collection Template will be created for Project Definitions data with exception of some fields which require transformation as mentioned in the transformation rule.

DCT applicable to project created manually, with project profile, PROJ-PROFL

- Recharge Cost Collectors - Expense Project - Project profile ZPS0004
- Provision Cost collectors - Expense Projects - Project Profile ZPS0005

Functional Area will be maintained manually
Refer configuration table field TFKB-FKBER for allowed values."
Legacy system Project ID, updated for migrated Projects Otherwise must be blank

Field Name	Field Description	Rule
PSPID	Project definition	Unique Identifier for the project definition via coding mask starting with "F-000000". It is a Required Field. Statistical Project Project Profile ZPS0003: No migration, to be created as needed "F-000000". 12. Recharge Cost Collectors - Expense Project - wth Project profile ZPS0004 As per the mapping relevancy, target ready Data Collection Template will be created for Project which represent project per Company code, project type for WBS as 15 - Intercompany Recharge 32. Provision Cost collectors - Expense Projects - with Project Profile ZPS0005 As per the mapping relevancy, target ready Data Collection Template will be created for Project which represent project per Company code project type for WBS as 13 Safety and Environment Provision 14 IAS19 Provision 12 Restructuring Provision 22 Environmental Fines 23 Social Fines 24 Corruption Fines It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template
POST1	Description	Short description, Name of the Project It is a Required Fieldis a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template
STSPR	WBS status profile	Profile used to Control User Statuses. Automatically Inherited from the Project Profile. Change not allowed.
VERNR	No. of Person Resp.	Project Owner Position number Refer configuration table field TCJ04-PS_VERNR for data validation. Project owner position entered manually for project created manually, with project profile, PROJ-PROFL
ASTNR	Applicant no.	This field represent the position of the Project Financial Controller. Refer configuration table field TCJ05-ASTNR for data validation. Project Financial Controller Position entered manually for project created manually, with project profile, PROJ-PROFL
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	VBUKR	Company code	Represents legal entity . Refer configuration table field T001TCJ05-BURKS ASTNR for data validation. Company code is entered manually for project created manually, with project profile, PROJ-PROFL
PRCTR	Profit Center	Profit Center represent a plant or a site or generic for GBU. Refer master data table field CEPC-PRCTR for allowed values. Entered Manually with either site specific PC or Generic PC for GBU
PLFAZ	Start date	Planned Start date of the Project. Entered Manually, it is a required field
PLSEZ	Finish date	Planned finish date of the Project, Conditional entered manually.
WERKS	Plant	Plant represent a site of Project. Entered manually.
PROFL	Project Profile	The profiles contain default values and control parameters for processing objects and functions in the Project System. Allowed Project Profiles for creation of Project definition: ZPS0004 - Recharge Projects ZPS0005 - Provisional Projects Entered Manually, it is a required field.
FUNC_AREA	Functional Area	USR00	Legacy Project ID
USR02	Item Type	It remains blank when the PS project is created manually for Project Profiles ZPS0003, ZPS0004 & ZPS0005 PROJ-USR02 = Blank.

Extraction Dependencies

Item #Step DescriptionTeam Responsible

Not Applicable

Data Team

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 to make the data Target ready:

It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template
VBUKR	Company code	Represents legal entity . Refer configuration table field T001-BURKS for data validation. One project per company code per GBU(profit centre) for Provisional Project with profile ZPS0005 One project per company code for Recharge project with profile ZPS0004 It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template
PRCTR	Profit Center	Profit Center represent a plant or a site or generic for GBU. Refer master data table field CEPC-PRCTR for allowed values. One project per company code per GBU(profit centre) for Provisional Project with profile ZPS0005
PLFAZ	Start date	Planned Start date of the Project. , It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template
PLSEZ	Finish date	Planned finish date of the Project, Conditional
WERKS	Plant	Plant represent a site of Project. Conditional
PROFL	Project Profile	The profiles contain default values and control parameters for processing objects and functions in the Project System. Allowed Project Profiles for creation of Project definition: ZPS0004 - Recharge Projects ZPS0005 - Provisional Projects It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template
FUNC_AREA	Functional Area	Refer configuration table field TFKB-FKBER for allowed values." It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template
	Instance	Instance where the project definition is to be loaded. (Field required in DCT)

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

Extraction Dependencies

Item #	Step Description	Team Responsible
	Not Applicable	Data Team

Transformation

Perform value mapping and data transformation rules.

Legacy values are mapped to the to-be values (this could include a default value)

Values are transformed according to the rules defined.

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

Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
DCT		PSPID	Project definition	S/4	PROJ	PSPID	Project ID	Mapping from source
DCT		USR00	Legacy Project ID	S/4	PROJ	USR00	Legacy Project ID	Blank
DCT		PROJUSR01	PSPIDItem Type	Project definition	S/4	PROJ	PSPID	Project ID	USR01	Item Type	BlankMapping from source
DCT	PROJ	USR00		USR02	Need-to-knowLegacy Project ID	S/4	PROJ	USR00	Legacy Project ID	USR02	Need-to-know	BlankMapping from source
DCT		POST1	Description	S/4	PROJ	POST1	Description	Copy from source
DCT				S/4	PROJ	STSPR	WBS status profile	Inherit from Project Profile
DCT		VERNR	No. of Person Resp.	S/4	PROJ	VERNR	No. of Person Resp.	Copy from source source
DCT		ASTNR	Applicant no.	S/4	PROJ	ASTNR	Applicant no.	Copy from source
DCT		VBUKR	Company code	S/4	PROJ	VBUKR	Company code	Mapping from source: Company Code Old to new
DCT				S/4	PROJ	VKOKR	Controlling area	Default from project profile
DCT		PRCTR	Profit Center	S/4	PROJ	PRCTR	Profit Center	Mapping from source: Profit Center Old to new
DCT				S/4	PROJ	PWHIE	Project Currency	Mapping from Company Code
DCT		PLFAZ	Start date	S/4	PROJ	PLFAZ	Start date	Copy from source	DCT	PLSEZ	Finish date	S/4	PROJ	PLSEZ	Finish date	Copy from source
DCT		WERKSPLSEZ	PlantFinish date	S/4	PROJ	WERKSPLSEZ	PlantFinish dateMapping	from Source: Plant Old to newCopy from source
DCT				S/4	PROJ	KALID	Factory Calendar	Mapping from Plant
DCT		PROFL	Project Profile	S/4	PROJ	PROFL	Project Profile	Copy from source
DCT				S/4	PROJ	BPROF	Budget Profile	Inherit from Project Profile
DCT				S/4	PROJ	BESTA	Project stock	Inherit from Project Profile		Inherit from Project Profile	DCT	S/4	PROJ-	XSTAT	Statistical	Inherit from Project Profile Mandatory for Statistical Projects with Project profile, PROJ-PROFL= ZPS0003 (Statistical project to be created as needed in S/4 Hana)
DCT				S/4	PROJ	PPROF	Planning Profile	Inherit from Project Profile
DCT				S/4	PROJ	PLINT	Integrated Planning	Inherit from Project Profile
DCT		FUNC_AREA	Functional Area	S/4	PROJ	FUNC_AREA	Functional Area	Copy from source	DCT	USR02	Item Type	S/4	PROJ	USR02	Item Type	Blank



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

The standard upload template to be used for Project Definition (Project Details template) upload in S/4 Hana.

Standard Upload template

Transformation Mapping

Mapping Table Name	Mapping Table Description
Company Code	Value Mapping: Old to New Company Code
T001	Value Mapping: Currency From Company Code
Plant	Value Mapping: Old Plant to New
Profit Center	Value Mapping: Profit Center Old to New
Person Responsible / Applicant	New Position to person name	Internal Order	Value Mapping: internal order to Project

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
	Ensure all the fields and values are imported into ADM Construction page correctly	Data Team
	Profit centers has been created (CEPC)

Pre-Load Validation

Project Team

Completeness

Task	Action
Generation of Pre-load report	Check all the required fields
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
Text Length Checks
Project 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	Controlling Area
2	Company Code
3	Factory Calendar
4	Currency Code
5	Project Profile
6	Budget Profile
7	Planning Profile
8	Functional Area
9	Profile for WBS scheduling
10	Project Coding Mask
11	Plant	12	Settlement Profile

Conversion Objects

Object #	Preceding Object Conversion Approach
1073	Profit Centre

Error Handling

Error Type	Error Description	Action

Taken

Taken
Invalid Data	Project Definition already exist	Correct upload data
Invalid Data	No. of Person Resp. does not exist	Correct upload data
Invalid Data	Applicant no. does not exist	Correct upload data
Invalid Data	Profit Centre does not exist	Correct upload data
Invalid Data

Project Definition already

Company Code does not exist	Correct upload data
Invalid Data

No. of Person Resp.

Functional area does not exist	Correct upload data
Invalid Data

Applicant no. does not exist

Two projects per company code not allowed for project with project profile ZPS0004 - Intercompany Recharges

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.
Project Definition is in scope based on data design and any exception requested by business.
The DCT should validate the project coding mask numbering as per the SAP instance config.
Validation / substitution might required to switched off at the time of load

Change log

Change History

limit	10

Apr 13, 2026	Actor	Type	Activity	Version
Revision under Review	NADAR-ext, Parvati	Edit	updated the page at 9:14 am
Mar 23, 2026
	NADAR-ext, Parvati	State	changed state to Revision under Review at 3:24 pm	v34
Revision in Progress	NADAR-ext, Parvati	Edit	updated the page at 6:54 am
Mar 18, 2026
	WENNINGER-ext, Sascha	State	changed state to Revision in Progress at 5:40 pm	v33
From Mar 09, 2026 to Mar 12, 2026
Edited following Approval	NADAR-ext, Parvati	Edit	updated the page at 7:43 pm

Workflow history

Space shortcuts

Page tree

Page History

Versions Compared

Old Version 19

New Version Current

Key

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Target Design

Additional Information

Multi-language Requirement

Target Design

Data Cleansing

Conversion Process

Extraction

Data Cleansing

Conversion Process

Extraction

Extraction Run SheetSheet

Extraction Dependencies

Transformation

Extraction Dependencies

Transformation

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 Dependencies

Pre-Load Validation

Project Team

Completeness

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