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

Compare with Current View Page History

« Previous Version 4 Next »

Status

  Revision in Progress

OwnerMaytingsari Tjahjo
Stakeholders

Purpose

The purpose of this document is to define the conversion approach to migrate the balance of Capex WBS from legacy system to S/4HANA.


Conversion Scope

The scope of this document covers the approach for converting active Capex WBS element from Legacy Source Systems into S/4HANA.


Below are the list of AUC classes for SyWay:

  • Z1100 Intangible-AUC
  • Z1101 Intangible-R&I under construction
  • Z1300 Tangible-AUC

The data from legacy system includes:

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

Legacy systems

Project level exclusions based on following relevancy rules:

  1. All projects with an out-of-scope company code will not be migrated.
  2. All closed projects as at the end of the previous fiscal year will not be migrated.
  3. All projects marked for deletion as at the end of the previous fiscal year will not be migrated.
  4. All projects without relevant WBS elements will not be migrated.
  5. Projects marked as statistical will not be migrated. 

S/4HANA




Legacy systems
  1. Any WBS element that is not closed as at the end of the previous fiscal year will be migrated. After eliminating all closed WBS elements, the relevancy rule will look for any WBS element that is not marked for deletion as at the end of the previous fiscal year for migration.

Exceptions:

  • Any closed WBS element that exists within an open Project.
  • Any WBS element that is marked for deletion that exists in an open Project.
  • Any closed WBS element that is affected by an open Projects.



DCT

Where legal entities do not use SAP to record their projects, the DCT will be used to collect the WBS element data.

This will be used in conjunction with the PPM Item DCT to collect Projects that are not in legacy systems. There will be a creation of one WBS element to one Project Definition. 

TBCS/4HANATBC





Additional Information

Multi-language Requirement

N/A

Document Management

N/A

Legal Requirement

N/A

Special Requirements




Target Design

The technical design of the target for this conversion approach.

TableFieldData ElementField DescriptionData TypeLengthRequirement






















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

Extract master data from PF2 & WP2 based on the current relevancy rules. Tables to be addressed are as below:

PRPS (WBS elements)

JEST (Individual object status)


Data team


Selection Screen

Selection Ref ScreenParameter NameSelection TypeRequirementValue to be entered/set
N/A




Data Collection Template (DCT)

This data collection template will be used to collect WBS element master data relating to project master data that is not in SAP PF2 & WP2. 

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

PRPS-VERNR

Person Responsible

Person responsible for the project

PRPS-AKSTL

Requesting Cost Centre

Represents the cost center from where the activity is being performed.

PRPS-PRCTR

Profit Centre

An organizational unit representing accountability for Profit/Loss.

PRPS-PLAKZ

Planning Element

Select if Account Assignment key is selected.

PRPS-BELKZ

Account Assignment Element

Activation of this field enables postings and commitments to be made.

PRPS-FKOKR

Controlling Area

?

PRPS-PBUKR

Company Code

Designated Company Code.

PRPS-WERKS

Plant

Plant must be in table and be applicable to the Company Code above.

PRPS-FABKL

Factory Calendar

To be defaulted from Plant.

PRPS-SLWID

Field Key

Will default from Project Profile as per in PPM Items and Project Definition DCT 

PRPS-SCOPE

Object Class

Will default from Project Profile as per in PPM Items and Project Definition DCT 

PRPS-IMPRF

Investment Profile

Will default from Project Profile as per in PPM Items and Project Definition DCT 

PRPS-IZWEK

Investment Reason

Specifies the investment reason related to the project.

JEST-STAT

System Status

Standard SAP status controlling. Values are system-defined, mainly CRTD, REL, TECO.

JEST-STAT

User Status

?

DKOBR-EMPGE

Settlement Rules


Capture all settlement rules. Especially those where the WBS Element is in TECO phase. These will have Fixed Assets in the Settlement rule that needs to be mapped to the new S4 HANA fixed asset.

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. 4) Apr 20, 2026 10:20 GOTTIPATI-ext, Madhu
v. 129 Apr 20, 2026 10:15 GOTTIPATI-ext, Madhu
v. 128 Feb 17, 2026 13:45 GOTTIPATI-ext, Madhu
v. 127 Feb 17, 2026 10:29 GOTTIPATI-ext, Madhu
v. 126 Feb 17, 2026 10:28 GOTTIPATI-ext, Madhu
v. 125 Feb 16, 2026 22:42 GOTTIPATI-ext, Madhu
v. 124 Feb 11, 2026 15:58 GOTTIPATI-ext, Madhu
v. 123 Feb 11, 2026 15:56 GOTTIPATI-ext, Madhu
v. 122 Feb 11, 2026 15:55 GOTTIPATI-ext, Madhu
v. 121 Feb 11, 2026 15:39 GOTTIPATI-ext, Madhu

Go to Page History

Workflow history

Title Last Updated By Updated Status  
There are no pages at the moment.

  • No labels