Status	In Progress
Owner	NADAR-ext, Parvati
Stakeholders	The business stakeholders involved in making, reviewing, and endorsing this decision. Type @ to mention people by name

Purpose

The purpose of this document is to define the conversion approach to create Project Definition (CAPEX, OPEX) in S/4 HANA.

Project Definition is the framework of the Work breakdown structure in SAP. Project Definition holds the default, header information such as Start and end date and scope of the Projects.

 As per Syensqo design below are the list of project scenarios.

CAPITAL/ Operational  Expense

Operational Expense

Statistical Expense

Intercompany Recharges

Provisional Expense

 As per Syensqo design below are the types of project.

Project Type	Description
11	Direct Asset Purchase
12	Restructuring Provision
13	Safety and Environment Provision
14	IAS19 Provision
15	Intercompany Recharge
16	Capital Lease
17	Industrial Projects
RI	New Product Introduction
RI	Product & Process Improvement
RI	Customer and business support
RI	OPD Opportunity Development
18	IT Project
19	Turnaround Projects
20	Contingency
21	Variation
22	Environmental Fines
23	Social Fines
24	Corruption Fines
25	Waste
26	Demolition - Recurring
27	Demolition - Non -Recurring
28	Marketing
29	Budgeted Maintenance
30	Continous Improvement
31	Operational Performance improvement
32	Site impact of Strikes
33	Campaigns

Conversion Scope

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

The data from legacy system includes:

All the projects below will be migrated from legacy source systems (PF2 and WP2) into S/4HANA –

Active Capex / Opex Projects, 

Closed project that have cost in current year

The data from legacy system excludes:

1. Exclusion Criteria 1
2. Exclusion Criteria 2
3. Exclusion Criteria n

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
PF2 and WP2	All Active Capex / Opex Projects,  Closed project that have cost in current year		S/4HANA

Additional Information

Multi-language Requirement

Summarize Multi-language Requirement/s, if any

Document Management

As per CNV-1025

Legal Requirement

Summarize Legal Requirement/s, if any

Special Requirements

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
PROJ	STSPR	PS_STSPR	WBS status profile	CHAR	8
PROJ	VERNR	PS_VERNR	No. of Person Resp.	NUM	8
PROJ	ASTNR	PS_ASTNR	Applicant no.	CHAR	25
PROJ	VBUKR	PS_VBUKR	Company code	CHAR	4
PROJ	VKOKR	PS_VKOKR	Controlling area	CHAR	4
PROJ	PRCTR	PRCTR	Profit Center	CHAR	10
PROJ	PWHIE	PS_PWHIE	Project Currency	CHAR	5
PROJ	PLFAZ	PS_PLFAZ_CHG	Start date	DATS	8
PROJ	PLSEZ	PS_PLSEZ_CHG	Finish date	DATS	8
PROJ	WERKS	WERKS_D	Plant	CHAR	4
PROJ	KALID	FABKL	Factory Calendar	CHAR	2
PROJ	PROFL	PROFIDPROJ	Project Profile	CHAR	7
PROJ	BPROF	BP_BPROFIL	Budget Profile	CHAR	6
PROJ	BESTA	PS_BESTAND	Project stock	CHAR	1
PROJ-	XSTAT	PS_XSTAT	Statistical	CHAR	1
PROJ	PPROF	BP_PPROFIL	Planning Profile	CHAR	6
PROJ	PLINT	PLINT	Integrated Planning	CHAR	1
PROJ	FUNC_AREA	FKBER	Functional Area	CHAR	16
PROJ	ZLEGACYID		Legacy Project ID	CHAR

Data Cleansing

All data cleansing should take place in the data source system as defined in this document, unless system limitations prevent it.

If data cleansing is managed outside of the source system (e.g. Syniti Migrate, 3rd Party Vendor, DCT), the necessary documentation must be produced and appended to this deliverable for sign-off.

ID	Criticality	Error Message/Report Description	Rule	Output	Source System

Conversion Process

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

Summarize High-Level Process. Include diagrams, where applicable. Include information supporting details of Extract, Transform and Load specific to the Data Object

Data Privacy and Sensitivity

Summarize Data Privacy and Sensitivity Requirements, if any

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 Description	Team Responsible

Selection Screen

If applicable, this section will give the details on any selection screen parameters, including the parameter type, that are required to be entered to ensure consistent data extracts.

Selection Ref Screen	Parameter Name	Selection Type	Requirement	Value to be entered/set

Data Collection Template (DCT)

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

<Object> DCT Rules

Field Name	Field Description	Rule

Extraction Dependencies

List the steps that need to occur before extraction can commence

Item #	Step Description	Team Responsible

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

1. Perform value mapping and data transformation rules.
   1. Legacy values are mapped to the to-be values (this could include a default value)
   2. Values are transformed according to the rules defined in Syniti Migrate
2. Prepare target-ready data in the structure and format that is required for loading via prescribed Load Tool. This step also produces the load data ready for business to perform Pre-load Data Validation

Transformation Run Sheet

Item #	Step Description	Team Responsible

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic

Transformation Mapping

Use the exact name and reference this section in the “Transformation rules” above

Mapping Table Name	Mapping Table Description

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible

Pre-Load Validation

Project Team

The following pre-load validations will be performed by the Project Team.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Business

The following pre-load validations will be performed by the business.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

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 Description	Team Responsible

Load Phase and Dependencies

Identify the phase as to “when” the load for this object will occur. <Pre-Cutover, Cutover, Post Cutover> and list the steps that need to occur before the load can commence

Configuration

List the Configurations required before loading can commence

Item #	Configuration Item

Conversion Objects

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

Error Handling

The table below depicts some possible system errors for this data object during data load. All data load error is to be logged as defect and managed within the Defect Management

Error Type	Error Description	Action Taken

Post-Load Validation

Project Team

The following post-load validations will be performed by the Project Team.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Business

The following post-load validations will be performed by the business.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Key Assumptions

• Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
• Data Object is in scope based on data design and any exception requested by business.

Any additional key assumptions.

See also

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log