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

Compare with Current View Page History

« Previous Version 3 Next »

Status

  In Progress

Owner

TEE-ext, Paul 

Stakeholders

Purpose

The purpose of this document is to define the conversion approach to create Product Resource & Tools in S/4 HANA.

Legacy Plant Production Resources & Tools is using a diverse range of formats across the different systems. There are instances where the same Production Resources & Tools is duplicated within and across sources, with informal words. This results in data inconsistency. As per SyWay design, EAM Maintenance Production Resources & Tools will be standardized.


Conversion Scope

The scope of this document covers the approach for converting active Production Resources & Tools from Legacy Source Systems into S/4HANA following the Production Resources & Tools Master Data Design Standard.


The data from legacy system includes:

  1. PRT Category: E-Equipment, P-Measuring Point, Not Marked for Deletion (Tcode: CF03 (All from Selection list)

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, WP2

An initial extract will be provided to business to evaluate.

Additional data/records may be required and these will be constructed via DCT.

Enrichment of in-scope data may be required and will be added via transformation rules (business/technical).

2

S/4HANA

2

Additional Information

Multi-language Requirement

Document Management

Long text and DIR are not covered in this document as they are defined as another data object.

Legal Requirement

Not Applicable

Special Requirements

Not Applicable




Target Design

The technical design of the target for this conversion approach.

TableFieldData ElementField DescriptionData TypeLengthRequirement






















Data Cleansing

IDCriticalityError Message/Report DescriptionRuleOutputSource System

1018-001

C1

Invalid or Inactive Material linked to Production Resources & Tools

Production Resources & Tools as per Relevancy Criteria assigned with a Material which does not belong below:
1. Material Master (S2P) as per Relevancy Criteria

Material

PF2, WP2

1018-002

C1

Invalid or Inactive Document Info Record linked to Production Resources & Tools

Production Resources & Tools as per Relevancy Criteria assigned with a Document Info Record which does not belong below:
1. Document Info Record as per Relevancy Criteria

Document Info Record

PF2, WP2

1018-003

C1

Production Resources & Tools UOM Missing / incorrect.

Production Resources & Tools as per Relevancy Criteria with no UoM Assigned or Invalid UoM (T006)

Unit of Measure

PF2, WP2

1018-004

C1




PF2, WP2

Informal Words **

Group 1

Group 2

Group 3

Group 4

Group 5

*DNU

Delete

donot

Formerly

Old #

..

Deletion

DONT USE

From

Old[ ]

/

DELISTED

DON'T USE

Incorrect

PLEASE USE

?

Discontinued

Dup Use

Invalid

Pls Use

@

Disposable

DUPLICATE

New

Previously

^

DNU

-DUPLICATE

NOT ACTIVE

Replace

+

Do Not

DUPLICATION

not in use

Replaced

++

Do Not Re

Duplicidad

Not Used

RESERVED

£

Do Not Sell

Duplikat

NOT VALID

Retired

Defective

Do Not Use

Former

Obsolete

ZZDEL


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 data from source system based on relevancy rule

SyWay Data Team

2

Google Sheet report pre-populated with PF2 and WP2 information to be generated based on relevancy criteria.

SyWay Data Team


Selection Screen

Selection Ref ScreenParameter NameSelection TypeRequirementValue to be entered/set
Not Applicable



















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.

Production Resources & Tools DCT Rules

Field NameField DescriptionRule












Extraction Dependencies

Item #Step DescriptionTeam Responsible

1

Ensure Syniti has the necessary connection and access to legacy servers


Data

2

Ensure that the necessary cleansing activities in legacy sources are complete

Data / Business

3

Ensure that create, change and deletion of master data is freeze in legacy Production system

Legacy IT


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

1

Obtain DCT Sign-off from Business

SyWay A2D Data Team

2

<Add steps from Syniti Migrate here>

SyWay A2D Data Team

3

Review and Validate Error and Preload Reports

SyWay A2D Data Team

4

Generate Load Files

SyWay A2D Data Team


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

1

Ensure DCT tables completeness

SyWay A2D Data Team

2

Value Mappings are according to the latest design -<List of Value Mappings>

SyWay A2D Data Team


Pre-Load Validation

Project Team

Completeness

TaskAction

Verify Record Count

SyWay A2D Data Team to verify that the total number of relevant records from legacy systems and DCTs (if any) is equal to the total number of records in the Preload and Load Sheets.

Verify Data Integrity

SyWay A2D Data Team to verify that the total number of Operations per Work Oder header extracted from legacy systems and DCTs (if any) should be equal to the total number of operations identified in the Preload and Load Sheets


Accuracy

TaskAction

Conversion Accuracy

SyWay A2D 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 data.


Business

Completeness

TaskAction

Verify Record Count

Business Data Owner/s to verify that the total number of relevant records from legacy systems and DCTs (if any) 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 fields below meet pass the checks:

  1. Mandatory Fields

  2. Field and Value Mapping Correctness

  3. Null Checks

  4. Text Length Checks


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

Syniti will provide load file

Syniti











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

Verify Count

SyWay A2D Data Team to verify the record count created in target S/4 HANA by accessing post load reports in dspMigrate 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

SyWay A2D Data Team to verify that the Work order data in target S/4 HANA were loaded correctly via dspMigrate post load reports or standard reports from S/4 HANA.


Business

Completeness

TaskAction

Verify Count

Download Post Load Reports from dspMigrate and verify that the record count loaded in the target S/4 HANA is the same count as of the endorsed load file.


Accuracy

TaskAction

Conversion Accuracy

Verify that the EAM Work order data in target S/4 HANA were loaded correctly via dspMigrate post load reports or standard reports from S/4 HANA.


Key Assumptions

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

  • All data cleansing and preparation has been completed.


See also

Change log

Version Published Changed By Comment
CURRENT (v. 3) Jul 10, 2025 13:00 TEE-ext, Paul
v. 4 Jul 10, 2025 11:39 TEE-ext, Paul
v. 3 Jul 08, 2025 12:23 TEE-ext, Paul
v. 2 Jul 08, 2025 12:22 TEE-ext, Paul
v. 1 Jun 10, 2025 12:48 TEE-ext, Paul

Workflow history

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

  • No labels