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

Compare with Current View Page History

Version 1 Next »

Status

 In Progress

OwnerNADAR-ext, Parvati 
Stakeholders

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


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:


List of source systems and approximate number of records
SourceScope

Source Approx No. of Records

Target SystemTarget 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

Document Management

As per CNV-1025

Legal Requirement

Special Requirements



Target Design


The technical design of the target for this conversion approach.

TableFieldData ElementField DescriptionData TypeLengthRequirement
PROJPSPIDPS_PSPIDProject definition24
PROJPOST1PS_POST1Description40
PROJSTSPRPS_STSPRWBS status profile8
PROJVERNRPS_VERNRNo. of Person Resp.NUM8


PROJASTNRPS_ASTNRApplicant no.25


PROJVBUKRPS_VBUKRCompany code4


PROJVKOKRPS_VKOKRControlling area4


PROJ


PRCTRPRCTRProfit CenterCHAR10


PROJPWHIEPS_PWHIEProject Currency5


PROJPLFAZPS_PLFAZ_CHGStart dateDATS8


PROJPLSEZ

PS_PLSEZ_CHG

Finish dateDATS8


PROJWERKSWERKS_DPlant4


PROJ

KALIDFABKLFactory Calendar2


PROJPROFLPROFIDPROJProject Profile7


PROJBPROFBP_BPROFILBudget Profile6


PROJBESTAPS_BESTANDProject stock1


PROJ-XSTAT

PS_XSTAT

Statistical1


PROJPPROF

BP_PPROFIL

Planning Profile6


PROJPLINTPLINTIntegrated Planning1


PROJFUNC_AREAFKBERFunctional Area16


PROJZLEGACYID
Legacy Project ID
































Data Cleansing

IDCriticalityError Message/Report DescriptionRuleOutputSource System


























Conversion Process

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


Data Privacy and Sensitivity


Extraction

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

  1. The data exists. connects to the source and loads the data into . 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 ; 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 . This is to be conducted using DCT (Data Collection Template) in

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













Selection Screen

Selection Ref ScreenParameter NameSelection TypeRequirementValue to be entered/set





















Data Collection Template (DCT)

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

DCT Rules

Field NameField DescriptionRule












Extraction Dependencies

Item #Step DescriptionTeam 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 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
  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 DescriptionTeam Responsible













Transformation Rules

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









































Transformation Mapping

Mapping Table NameMapping Table Description








Transformation Dependencies

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













Pre-Load Validation

Project Team

Completeness

TaskAction





Accuracy

TaskAction





Business

Completeness

TaskAction





Accuracy

TaskAction





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













Load Phase and Dependencies

Configuration

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

Error TypeError DescriptionAction Taken










Post-Load Validation

Project Team

Completeness

TaskAction





Accuracy

TaskAction





Business

Completeness

TaskAction





Accuracy

TaskAction





Key Assumptions

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


See also

Change log

Version Published Changed By Comment
CURRENT (v. 1) 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