You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 24 Next »

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

PS Project ProfilePRJIDPS Coding MaskPS Coding Mask DescriptionDCT

ZPS0004 - Intercompany Recharges

F-000000-00-00-XX-XX-XXStatistical/ Recharge & Provision ProjectsOne Project per CoCode with L2 WBS per Trading Partner

ZPS0005 - Provisional Expense

F-000000-00-00-XX-XX-XXStatistical/ Recharge & Provision ProjectsOne project per company code with L2 WBS

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. 

Exclude, project with project profile is ZPS0001 or ZPS0002 linked to PPM item type,

Project with project profile ZPS0003 - Statistical Expense, created as needed in S/4 Hana

  

List of source systems and approximate number of records

SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

DCT

S/4 HanaTBD

Additional Information

Multi-language Requirement

Project definition, must be maintained in:

  - 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 TypeLengthRequirement
PROJPSPIDPS_PSPIDProject definitionCHAR24Mandatory
PROJPOST1PS_POST1DescriptionCHAR40Mandatory
PROJSTSPRPS_STSPRWBS status profileCHAR8System Generated
PROJVERNRPS_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


C2

All active internal orders to be closed and map to Project

Map internal order to Project

  • Recharge Project

One Project per CoCode with L2 WBS per Trading Partner

  • Provision Projects: 
    One project per company code with L2 WBS

Report

WP2/PF2


Conversion Process

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

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

Data Team (I2M), Data Team (Syniti)

5

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

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 ScreenParameter NameSelection TypeRequirementValue 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 NameField DescriptionRule
PSPIDProject definition

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

It is a Required Field.

  1. Statistical Project Project Profile ZPS0003:

No migration, to be created as needed

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
22  Environmental Fines
23  Social Fines
24  Corruption Fines

 POST1DescriptionShort description, Name of the Project
It is a Required Field
STSPRWBS 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 
PRCTRProfit 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

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

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:  
ZPS0004 - Recharge Projects
ZPS0005 - Provisional Projects

Entered Manually, it is a required field.

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


Not Applicable

Data Team


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

Item #Step DescriptionTeam 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
8Re-transform and re-validate the Pre-load reports if necessary.Data Team
9Validate the transformed file as part of pre-load validation, raise data defects or provide the pre-load sign-off.Business
10Analyze and resolve any pre-load defects logged by business.Data Team
11Repeat steps 7 to 10 if necessaryData Team
12Proceed to pre-load validationsData Team


Transformation Rules

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic

DCT
PSPIDProject definitionS/4PROJ PSPIDProject ID

Mapping from source


DCT
USR00Legacy Project IDS/4PROJ USR00Legacy Project ID

Blank


DCT
 POST1DescriptionS/4PROJPOST1DescriptionCopy from source

DCT


S/4PROJSTSPRWBS status profileInherit from Project Profile

DCT
VERNRNo. of Person Resp.S/4PROJVERNRNo. of Person Resp.Copy from source

DCT
ASTNRApplicant no.S/4PROJASTNRApplicant no.Copy from source

DCT
VBUKRCompany codeS/4PROJVBUKRCompany codeMapping from source:  Company Code  Old to new

DCT


S/4PROJVKOKRControlling areaDefault from project profile

DCT
PRCTRProfit CenterS/4PROJPRCTRProfit CenterMapping from source:  Profit Center Old to new

DCT


S/4PROJPWHIEProject CurrencyMapping from Company Code

DCT
PLFAZStart dateS/4PROJPLFAZStart dateCopy from source

DCT
PLSEZFinish dateS/4PROJPLSEZFinish dateCopy from source

DCT
WERKSPlantS/4PROJWERKSPlantMapping from Source:  Plant Old to new

DCT


S/4PROJKALIDFactory CalendarMapping from Plant

DCT
PROFLProject ProfileS/4PROJPROFLProject ProfileCopy from source

DCT


S/4PROJBPROFBudget ProfileInherit from Project Profile

DCT


S/4PROJBESTAProject stockInherit from Project Profile

DCT


S/4PROJ-XSTATStatistical

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/4PROJPPROFPlanning ProfileInherit from Project Profile

DCT


S/4PROJPLINTIntegrated PlanningInherit from Project Profile

DCT
FUNC_AREAFunctional AreaS/4PROJFUNC_AREAFunctional AreaCopy from source

DCT
USR02Item TypeS/4PROJUSR02Item TypeBlank
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 NameMapping Table Description
Company CodeValue Mapping: Old to New Company Code
T001Value Mapping: Currency From Company Code
PlantValue Mapping: Old Plant to New
Profit CenterValue Mapping:  Profit Center Old to New
Internal OrderValue Mapping:  internal order to Project

Transformation Dependencies

List the steps that need to occur before transformation can commence
Item #Step DescriptionTeam Responsible

Ensure all the fields and values are imported into ADM Construction page correctlyData Team


Pre-Load Validation

Project Team

Completeness

TaskAction
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

TaskAction

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

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

TaskAction

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

TaskAction

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:

  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 DescriptionTeam 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
1Controlling Area 
2Company Code 
3Factory Calendar
4Currency Code
5Project Profile
6Budget Profile
7Planning Profile
8Functional Area
9Profile for WBS scheduling
10Project Coding Mask
11Plant
12Settlement Profile

Conversion Objects

Object #Preceding Object Conversion Approach
1073Profit Centre

Error Handling


Error TypeError DescriptionAction Taken
Invalid DataProject Definition already existCorrect upload data
Invalid DataNo. of Person Resp. does not existCorrect upload data
Invalid DataApplicant no. does not existCorrect upload data


Post-Load Validation

Project Team

Completeness

TaskAction

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

TaskAction

Conversion Accuracy

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

Business

Completeness

TaskAction
Verify template Project data - Project Definition Extract data from PS report CN41N in S/4 Hana

Accuracy

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


See also


Change log

Version Published Changed By Comment
CURRENT (v. 24) Apr 13, 2026 09:14 NADAR-ext, Parvati
v. 34 Mar 23, 2026 06:54 NADAR-ext, Parvati
v. 33 Mar 12, 2026 12:32 NADAR-ext, Parvati
v. 32 Mar 09, 2026 19:43 NADAR-ext, Parvati
v. 31 Oct 29, 2025 13:01 NADAR-ext, Parvati
v. 30 Oct 29, 2025 12:04 NADAR-ext, Parvati
v. 29 Oct 29, 2025 08:29 NADAR-ext, Parvati
v. 28 Oct 29, 2025 07:57 UPADHYAY-ext, Anjali
v. 27 Oct 29, 2025 07:56 UPADHYAY-ext, Anjali
v. 26 Oct 28, 2025 15:48 NADAR-ext, Parvati

Go to Page History

  • No labels