Status

In Progress

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 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
	-000000-00-00-XX-XX-XX
CAPITAL/ Operational Expense Projects	Z002 Industrial Project	ZPS0001 - CAPITAL/ Operational Expense
One Project per CoCode
ZPS0005 - Provisional Expense	F	-000000-00-00-XX-XX-XX
CAPITAL/ Operational Expense Projects
Z003 Industrial Project - Simple ?	ZPS0001 - CAPITAL/ Operational Expense	A	-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
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

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.

The conversion will ensure all projects are aligned to the defined project coding mask and relevant Organizational Units as designed for the target S/4HANA 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
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 existing active Project Definition from SAP ECC systems WP2 and PF2.
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 –

Open Projects WBS from in scope company codes.

Proj elements not in closed status

Table PROJ

Key in field "Company Code" in scope.

Field project profile not in excluded project profile.

Result: Object numbers of WBS that are in company codes in scope.

Table JEST:

Field "Object number" = Key in the object numbers of WBS (from Step A), Field "Status Inactive" = blank, Then filter object number that do not have status I0046 (Closed)

2. Closed Project from in scope company codes with postings in migration relevant financial year (currently migration relevant is 2028). The postings technically does not occur directly against the project definition but against objects within the project therefore, postings against a WBS element is used as a proxy for determination of postings against the project.

Closed Project that have WBS element with cost in current year must also be migrated.

Logic:

Table PROJ

Field "Company Code" in scope.

Field project profile in scope project profile.

Result: Object numbers of WBS that are in company codes in scope.

Table JEST:

Field "Object number" = Key in the object numbers of Project

Field "Status Inactive" = blank, Then filter object number that has status I0046 (Closed).

Result closed projects.

Table PRPS

Field PSPHI For closed projects numbers, Result WBS numbers for

Table RPSCO / COSP:

Field "Object number" = Key in the object numbers of WBS

Field "Fiscal Year" = Current year, Field "Value Type" = 4

Result = Object numbers that have cost in current year.

These WBS needs to be migrated.

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

These Project Profile need to be migrated dependent on project profile mapping.

The data from legacy system excludes:

Where the mapped project profile is ZPS0001 or ZPS0002 linked to PPM item type.
Project not in scope company code.

List of source systems and approximate number of records

SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

WP2

Project Definition

14500S/4HANAPF2Project DefinitionS/4HANADCT

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.

TableFieldData ElementField DescriptionData TypeLengthRequirementPROJPSPIDPS_PSPIDProject definitionCHAR24MandatoryPROJPOST1PS_POST1DescriptionCHAR40MandatoryPROJSTSPRPS_STSPRWBS status profileCHAR8System GeneratedPROJVERNRPS_VERNRNo. of Person Resp.NUM8

Mandatory

PROJASTNRPS_ASTNRApplicant no.CHAR25

Mandatory

PROJVBUKRPS_VBUKRCompany codeCHAR4

Mandatory

PROJVKOKRPS_VKOKRControlling areaCHAR4

System Generated

PROJ

PRCTRPRCTRProfit CenterCHAR10

Mandatory

PROJPWHIEPS_PWHIEProject CurrencyCHAR5

System Generated

PROJPLFAZPS_PLFAZ_CHGStart dateDATS8

Mandatory

PROJPLSEZ

PS_PLSEZ_CHG

Finish dateDATS8

Conditional

PROJWERKSWERKS_DPlantCHAR4

Conditional

PROJ

KALIDFABKLFactory CalendarCHAR2

System Generated

PROJPROFLPROFIDPROJProject ProfileCHAR7

Mandatory

PROJBPROFBP_BPROFILBudget ProfileCHAR6

System Generated

PROJBESTAPS_BESTANDProject stockCHAR1

System Generated

PROJ-XSTAT

PS_XSTAT

StatisticalCHAR1

Conditional

PROJPPROF

BP_PPROFIL

Planning ProfileCHAR6

System generated

PROJPLINTPLINTIntegrated PlanningCHAR1

System generated

PROJFUNC_AREAFKBERFunctional AreaCHAR16

Mandatory

PROJUSR00USRCHAR20Legacy Project IDCHAR20

Conditional

PROJUSR02USRCHAR10Item TypeCHAR10

Conditional

Data Cleansing

IDCriticalityError Message/Report DescriptionRuleOutputSource System

1

C1

Projects marked as Closed /deletion

Report

WP2/PF2

2

C2

Active Projects with no movement over 5 years

Report

WP2/PF2

3

C4

Internal orders marked as Closed / deletion

Report

WP2/PF2

4

C5

Active internal order with no movement over 5 years

Map internal order to WBS

Report

WP2/PF2

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-' with project profile as ZPS0003 - Statistical Expense2

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-' 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 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 Generated
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	SLWID	SLWID	Field key	CHAR	7	System generated
PROJ	FUNC_AREA	FKBER	Functional Area	CHAR	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 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 Sheet

Req #	Requirement Description	Team Responsible
1	Ensure DCT is collected for Project Definition	Data Team (I2M), Data Team (Syniti)
2	Perform preliminary completeness check	Technical / Basis Team, Data Team (Syniti)
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)

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

Field Name	Field Description	Rule
PSPID	Project definition	Unique Identifier for the project definition via coding mask starting with "F-000000". 1. Recharge Cost Collectors - Expense Project wth Project profile ZPS0004 2. Provision Cost collectors - Expense Projects with Project Profile ZPS0005 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 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. 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. Refer configuration table field TCJ05-ASTNR for data validation. 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

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:

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

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 from both source systems WP2, PF2

Data Team (Syniti)

4

Extract Project Definition 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 Project 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)

7

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

Data Team (I2M), Data Team (Syniti)

8

Review and approve extracted data sample sets from each source system before transformation begins

Business / Functional Team

Selection Screen

Not Applicable
Selection Ref ScreenParameter NameSelection TypeRequirementValue to be entered/setNot 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.

Delta Data Management: Initial collection will be done via the report and one-time load to the DCT will be performed. Any delta after the initial collection within the DCT will require business to take due diligence to ensure any subsequent delta cleansing is verified and aligned within the DCT.

Note: All rules specified below should be documented as a tooltip in the DC Page

Applicable to project created manually, with project profile, PROJ-PROFL=

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

Field NameField DescriptionRulePSPIDProject definition

Unique Identifier for the project definition via coding mask starting with "F-000000".

It is a Required Field.

Statistical Project Project Profile ZPS0003:

Rule 1:

Target Ready Data Collection Template will be created for Project (ESG) which represent project per GBU/Cocd/ Plant (site specific) with project type:
22 Environmental Fines
23 Social Fines
24 Corruption Fines
32 Site impact of Strikes
33 Campaigns

Rule 2:

Mapping with Internal orders to project:

Other expenses, for active internal order exist as per the mapping relevancy, target ready Data Collection Template will be created for Project which represent project per Company code/ Plant (site specific).

2. Recharge Cost Collectors - Expense Project - 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

3. Provision Cost collectors - Expense Projects - 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

POST1DescriptionShort description, Name of the Project
It is a Required FieldSTSPRWBS status profile

Profile used to Control User Statuses.

Automatically Inherited from the Project Profile. Change not allowed.

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

ASTNRApplicant 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 VBUKRCompany codeRepresents legal entity . Refer configuration table field T001-BURKS for data validation.
Company code is entered manually for project created manually, with project profile, PROJ-PROFL VKOKRControlling areaControlling Area is a self-contained organizational unit used for internal cost accounting, Default from Project Profile and Cannot be changedPRCTRProfit 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

PWHIEProject CurrencyCurrency of the Project derived from the Company code and cannot be changedPLFAZStart date

Planned Start date of the Project.

Entered Manually, it is a required field

PLSEZFinish date

Planned finish date of the Project,

Conditional entered manually.

WERKSPlant

Plant represent a site of Project. Entered manually.

KALIDFactory CalendarDerived from the Plant. Refer configuration table field TFACD-IDENT for allowed values.PROFLProject 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:
ZPS0003 - Statistical Expense
ZPS0004 - Recharge Projects
ZPS0005 - Provisional Projects

Entered Manually, it is a required field.

BPROFBudget ProfileThe budget profile brings together the control parameters for budgeting Such as Time horizon, Currency Translation, availability control. This will be inherited from the Project profile.BESTAProject stock

This field determines the behavior of the stock for Project. The Field will be automatically determined from Project Profile. Once set it cannot be changed. No Project Stock will be used

XSTATStatistical

Indicator to specify whether a WBS element is only for statistical purposes or whether it may carry actual costs.

Mandatory for Statistical Projects with Project profile PROJ-PROFL= ZPS0003

PROFLPlanning ProfileProfile which control parameters for cost planning. This is derived from Project profilePLINTIntegrated PlanningThis indicator specifies whether an order/project participates in integrated planning or not. Derived from project profile. FUNC_AREAFunctional AreaFunctional Area will be maintained manually
Refer configuration table field TFKB-FKBER for allowed values."
USR00Legacy Project IDLegacy system Project ID, updated for migrated Projects Otherwise must be blank
USR02Item 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

1

Ensure DCT is collected for Project Definition based on relevancy rule

Data Team

2

Perform preliminary completeness check

Data Team

3

Raise issues as defects if Req # 1 to 2 are not met

Data Team

4

Repeat Req # 1 to 3 if required

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:

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 in

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

Rule #

Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation LogicDCTPSPID

Source system	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	USR01	Item Type	S/4	PROJ	USR01	Item Type	Blank
DCT	USR02	Need-to-know

Project definition

S/4

PROJ

PSPIDProject definition

Copy from source for ESG project.

Mapping from source (Internal order) to Project as per mapping relevancy

USR02	Need-to-know	Blank
	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

WERKSPlant

S/4

PROJ

WERKSDCTS/4PROJ

PlantMapping from Source: Plant Old to new

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 ProfileDCTS/4PROJ-XSTAT

Statistical

Inherit from Project Profile

Mandatory for Statistical Projects with Project profile, PROJ-PROFL= ZPS0003

	DCT				S/4	PROJ	PPROF	Planning Profile	Inherit from Project Profile
	DCT

PLINTIntegrated Planning

S/4

PROJ

PLINT

Integrated Planning

Copy

Inherit from

source

Project Profile
	DCT		FUNC_AREA	Functional Area	S/4	PROJ	FUNC_AREA	Functional Area	Copy from source

DCTUSR02Legacy Project IDS/4PROJUSR02Legacy Project IDCopy from source

Transformation



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

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
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.	SyWay I2M Data Team
2	Load 3 records for < > to validate if data is loaded successfully without errors	SyWay I2M Data Team
3	Load 3 records for < > to validate if data is loaded successfully without errors	SyWay I2M Data Team
4	Proceed with full load if steps 2 and 3 are validated	SyWay I2M Data Team
5	Validate few records loaded by accessing CN41N report	SyWay I2M Data Team
6	Generate post load report if step 5 is validated	SyWay I2M Data Team	7	Post Template upload, run CNMASSSTATUS to update the template status to Lock	is validated	SyWay I2M 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	Profile for WBS scheduling

Conversion Objects

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

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

Conversion Objects

Object #	Preceding Object Conversion Approach
1073	Profit Centre

Error Handling

Error Type	Error Description	Action 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	Company Code does not exist	Correct upload data
Invalid Data	Functional area does not exist	Correct upload data
Invalid Data	Two projects per company code not allowed for project with project profile ZPS0004 - Intercompany Recharges

Error Handling

Error TypeError DescriptionAction TakenProject Definition already exist

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 9

New Version Current

Key

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Legal Requirement

Special Requirements

Target Design

Data Cleansing

Additional Information

Multi-language Requirement

Target Design

Data Cleansing

Conversion Process

Extraction

Extraction Run Sheet

Extraction Dependencies

Transformation

Conversion Process

Extraction

Extraction Run Sheet

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

Conversion Objects

Error Handling

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

See also

Change log