Status
Owner	PUN-ext, Eddy
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 Measurement Document in S/4 HANA.

Summarise how the data is currently utilized and set up in the legacy system/s and how object is intended to be represented in S/4, and any other relevant information

Conversion Scope

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

The approach is to migrate the last Measurement Document for each active Measuring Point which is driving the active Maintenance Plans and Items in order to start the Maintenance Plan in S/4 HANA with the objective to continue with the cycle.

The data from legacy system includes:

1. Relevant measuring point that is a counter will have its latest measurement document without reversal indicator migrated to S/4HANA for business continuity to capture new measuring readings based on its last reading, facilitating the trigger of maintenance plan.
2. If the Measuring Point is assigned to an ACTIVE Maintenance Plan, it must have valid and relevant Measurement Document to be migrated
3. Historical Data for associated active Measuring Points for active Functional Locations and Equipment for the past 3 years, limited to specific Technical Object Type (list to be confirmed in Mapping Table).

The data from legacy system excludes:

1. Measuring Document with reversal indicator

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
PF2, WP2	Last Reading of Measurement Documents will be extracted from PF1 and WP1	6,000	S/4HANA	6,000
PF2, WP2	Historical Measurement Documents will be extracted from PF1 and WP1	nnn	S/4HANA	nnn
DCT	Measurement Documents for plants which do not have data existing from PF2 and PF2	nnn	S/4HANA	nnn
DCT	Historical Measurement Documents for plants which do not have data existing from PF2 and PF2	nnn	S/4HANA	nnn

Additional Information

Multi-language Requirement

Measurement document does not have multi language support. Measurement document text will be migrated using EN logon.

Document Management

Not Applicable

Legal Requirement

Not Applicable

Special Requirements

Target Design

With Functional input, document the technical design of the target fields that are in the scope of this document.

The technical design of the target for this conversion approach.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
IMRG	MDOCM		Measurement Document	CHAR	30	Internal Number
IMRG	POINT		Measuring Point	CHAR	12	Mandatory
IMRG	IDATE		Date of the Measurement	DATS	8	Mandatory
IMRG	ITIME		Time of Measurement	TIMS	6	Mandatory
IMRG	MDTXT		Measurement Document Text	CHAR	40	Optional
IMRG	MLANG		Language Key	LANG	1	Mandatory
IMRG	CNTRR		Counter Reading in SI Unit	FLTP	16	Mandatory
IMRG	READG		Measurement Reading/Total Counter Reading in SI Unit	FLTP	16	Mandatory

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
9002-001	C3	Missing Measurement Document for Measuring Points assigned to Maintenance Plan	If the Measuring Point is assigned to an ACTIVE Maintenance Plan, it must have valid and relevant Measurement Documents. This is the pre-requisite for Start PM Plan.	All key fields	PF2, WP2

Conversion Process

The high-level process is represented by the diagrams below.

The following represents the high-level process for Source System Extraction:

The following represents the high-level process for DCT:

Data Privacy and Sensitivity

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
1	Extract data from source system based on relevancy rule	Data Team
2	Google Sheet report pre-populated with PF2 and WP2 information to be generated based on relevancy criteria.	Data Team

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
Not Applicable

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
MDOCM	Measurement Document
POINT	Measuring Point	Must be an existing Measuring Point
IDATE	Date of the Measurement	Valid Date in the past, within 1 year from now
ITIME	Time of Measurement	Valid Time
MDTXT	Measurement Document Text	No Illegal Characters
MLANG	Language Key	EN
CNTRR	Counter Reading in SI Unit	Counter reading cannot be 0 Counter Reading cannot be greater than overflow reading of Measuring Point
READG	Measurement Reading/Total Counter Reading in SI Unit	Total Counter Reading cannot be 0

Extraction Dependencies

List the steps that need to occur before extraction can commence

Item #	Step Description	Team Responsible
1	Only measurement documents linked to relevant measuring points should be extracted.	Data Team

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
1	Ensure all mapping tables are up to date.	Syniti
2	In dspMigrate, select the wave –R3 S4/HANA – Plant Maintenance	Syniti
3	Go to Process Area Launch and Process the Object – Measurement Documents	Syniti
4	Review and Validate Error and Preload Reports	Syniti
5	Execute the transformation to prepare the target tables	Syniti
6	Validate data from pre-load and invalid reports by region	Business/Data owner
7	Generate export(load) file (If load tool is not dspIntergrate)	Data Team

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	PF2/WP2/DCT	IMRG	POINT	Measuring Point	S/4 HANA	IMRG	POINT	Measuring Point	Legacy measuring point to S/4 measuring point based on measuring point XREF mapping table.
2	PF2/WP2/DCT	IMRG	IDATE	Date of the Measurement	S/4 HANA	IMRG	IDATE	Date of the Measurement	Move from Source to S/4 HANA
3	PF2/WP2/DCT	IMRG	ITIME	Time of Measurement	S/4 HANA	IMRG	ITIME	Time of Measurement	Move from Source to S/4 HANA
4	PF2/WP2/DCT	IMRG	MDTXT	Measurement Document Text	S/4 HANA	IMRG	MDTXT	Measurement Document Text	Move from Source to S/4 HANA
5					S/4 HANA	IMRG	MLANG	Language Key	EN
6	PF2/WP2/DCT	IMRG	CNTRR	Counter Reading in SI Unit	S/4 HANA	IMRG	CNTRR	Counter Reading in SI Unit	If total Counter Reading and Counter Reading is the same (IMRG-READG=IMRG-CNTRR): Move from PE1 to S/4 HANA. Floating point conversion to apply for loading, including conversion to/from SI unit. Consider the unit from the Measuring Point characteristics and compare against table T006 for conversion. Counter reading cannot be 0 Counter Reading cannot be greater than overflow reading of Measuring Point If total Counter Reading and Counter Reading is not the same (IMRG-READG<>IMRG-CNTRR) – Counter Replacement Scenario Move from PE1 to S/4 HANA. Floating point conversion to apply for loading, including conversion to/from SI unit. Consider the unit from the Measuring Point characteristics and compare against table T006 for conversion.
7	PF2/WP2/DCT	IMRG	READG	Measurement Reading/Total Counter Reading in SI Unit	S/4 HANA	IMRG	READG	Measurement Reading/Total Counter Reading in SI Unit	Move from PE1 to S/4 HANA. Floating point conversion to apply for loading, including conversion to/from SI unit. Consider the unit from the Measuring Point characteristics and compare against table T006 for conversion. This step can be achieved by setting the total counter reading externally upon counter replacement. Total Counter Reading cannot be 0

Transformation Mapping

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

Mapping Table Name	Mapping Table Description
TOT Mapping	Mapping table with list of Technical Object Type for FL/EQ to be included in scope for Historical Data
	Legacy Measuring Point XREF mapping table

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
1.	Measuring point XREF table should be available after measuring point loaded.	Data Team

Pre-Load Validation

Project Team

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

Completeness

Task	Action
Verify Record Count	Data team to verify that the total number of relevant records from the source systems is equal to the total number of records in the Preload and Load Sheets.

Accuracy

Task	Action
Conversion Accuracy	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

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

Completeness

Task	Action
Verify Record Count	Business team to verify that the total number of relevant records from the source systems is equal to the total number of records in the Preload and Load Sheets.

Accuracy

Task	Action
Conversion Accuracy	Business  to verify that all the data in the load table/file is accurate as per endorsed transformation/mapping rules (and signed-off 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 Description	Team Responsible

Load Phase and Dependencies

1. Relevant Measurement Document is loaded as part of Cutover phase.
2. All Historical Data for Measurement Document is loaded as part of Pre-Cutover phase once Master Data Loaded

Configuration

List the Configurations required before loading can commence

Item #	Configuration Item
Not Applicable

Conversion Objects

Object #	Preceding Object Conversion Approach
1012	Measuring Point

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
Invalid Data	Invalid Measurement Document	Expedite whether the master data is available in the system

Post-Load Validation

Project Team

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

Completeness

Task	Action
Verify Count	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

Task	Action
Conversion Accuracy	Data team to verify that the Measurement Document data in target S/4 HANA were loaded correctly via dspMigrate post load reports or standard reports from S/4 HANA.

Business

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

Completeness

Task	Action
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

Task	Action
Conversion Accuracy	Verify that the Measurement Document 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 for Measuring Point is up to date as on the date of documenting this conversion approach and data load. 
• Measurement Document 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

Workflow history