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

Compare with Current View Page History

« Previous Version 46 Next »

Status

  Update in progress

Owner

PUN-ext, Eddy 

Stakeholders

ERGUIZA-ext, Pinky Love JOSHI-ext, Aditya TEE-ext, Paul LEIGHTON-ext, Dean MOUSSA-ext, Eva BAGGA-ext, Abhishek VILARES, ines Aurelia Stefanescu DUNNE-ext, Al 

Purpose

The purpose of this document is to define the conversion approach to create Measurement Document in S/4 HANA.

Measurement documents are used to record measurement readings on the condition of an equipment e.g. temperature. It is also used to record counter readings of an equipment e.g. Engine Running hours. This counter readings will be the trigger for maintenance plan to initiate maintenance and/or inspection work.


Conversion Scope

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

At Syensqo, Measurement Documents are created for Measuring Points to monitor the condition and usage of assets. They provide critical input to support condition-based and usage-based maintenance strategies. Measuring Points are created on either Functional Locations or Equipment, depending on the asset structure and monitoring requirement. The Measurement Documents are also a core component of Asset Performance Management (APM) used to monitor asset health, detect trends, and trigger condition-based or predictive maintenance actions.

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. For Measurement Documents related to APM, up to three years of historical data will be migrated from legacy systems to ensure seamless continuity in asset monitoring, trend analysis, and maintenance decision-making within the S/4 HANA.

The data from legacy system includes:

  1. Latest Measurement Document for relevant Measuring Point that is a counter (IMPTT-INDCT)
    1. where the Measurement Date (IMRG-IDATE) is before the Start Date of the linked Maintenance Plan Start for Time Based Plan
    2. where the Counter Reading (IMRG-CNTRR) is before the Start Counter Reading of the linked  Maintenance Plan for Counter Based Plan
  2. Measurement Document for associated relevant Measuring Points for Functional Locations and Equipment for the past 3 years (IMRG-IDATE), limited to:
    1. specific Technical Object Type (EQUI-EQART/IFLOT-EQART) based on Value Mapping: OTH_Technical Object Type_APM and

The data from legacy system excludes:

  1. Measuring Document with reversal indicator (IMRG-CANCL)
  2. Long Text for Measurement Document

List of Tables to extract for this object is maintained here: Extract Table Register.


Illustration of relevant Measurement Document for extraction (Point 1 of relevancy criteria):

Measuring PointMeasurement DocumentDateTimeCounter ReadingReversal Indicator
A100123 Feb 202610 am2010
A10021 Mar 20262 am2040
A10031 Mar 20264 am2050
A100425 Feb 20265 pm2020
A10052 Mar 20263 pm2060X
A100626 Feb 20264 pm2021X

 Based on the above sample data, the following scenario and conclusion apply:

ScenarioMaintenance Plan Start Date / Start CounterConclusionRationale
1Not provided (blank)

Measurement Document 003 is to be extracted

Latest date and time without reversal indicator
2Maintenance Plan Start Date = 27 February 2026Measurement Document 004 is to be extractedLatest date and time without reversal indicator, closest and before 27 February 2026
3Maintenance Plan Start Counter = 2025Measurement Document 004 is to be extractedLatest counter reading without reversal indicator, closest and before 2025


The following are not in scope for Measurement Document Conversion:

  1. Measurement Document Long Text
  2. Digital Local Indicators (eg Sensor Data available in Startek) as these will be mass created via Custom Development Program (ERP-582)


 List of source systems and approximate number of records

SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

PF2, WP2Relevant Measurement Documents will be extracted from PF2 and WP210,000

S/4HANA

10,000
DCTMeasurement Documents for plants which do not have data existing from PF2 and PF2TBDS/4HANATBD

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

Not Applicable


Target Design

The technical design of the target for this conversion approach.

TableFieldData ElementField DescriptionData TypeLengthRequirement
IMRGMDOCMIMRC_MDOCMMeasurement DocumentCHAR30Internal Number
IMRGPOINTIMRC_POINTMeasuring PointCHAR12Mandatory
IMRGIDATEIMRC_IDATEDate of the MeasurementDATS8Mandatory
IMRGITIMEIMRC_ITIMETime of MeasurementTIMS6Mandatory
IMRGMDTXTIMRC_MDTXTMeasurement Document TextCHAR40Conditional
IMRGMLANGSPRASLanguage KeyLANG1Conditional
IMRGCNTRRIMRC_CNTRRCounter Reading in SI UnitFLTP16Mandatory
IMRGREADGIMRC_READGMeasurement Reading/Total Counter Reading in SI UnitFLTP16Mandatory
IMRG

VLCOD

IMRC_VLCOD

Valuation Code

CHAR4Conditional


Data Cleansing

IDCriticalityError Message/Report DescriptionRuleOutputSource System
9002-001

C3

Info Report: Missing Measurement Document for Measuring Points assigned to Maintenance Plan


If the Measuring Point is assigned to an relevant Maintenance Plan, it must have valid and relevant Measurement Documents.


This is the pre-requisite for Start PM Plan.

Maintenance Plan, Maintenance Plan Text, Measuring Point, Measuring Point DescriptionPF2, 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:

Collection will be done manually in the Data Collection Template for the following scenarios:

  • For sites not on SAP-PF2 or WP2 systems 

Data Privacy and Sensitivity

Not Applicable.


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 inSyniti Migrate. This is to be conducted using DCT (Data Collection Template) inSyniti 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 DescriptionTeam Responsible
1Extract data from source system based on relevancy ruleData 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.

DCT Rules

Field NameField DescriptionRule
MDOCMMeasurement DocumentMust be unique
POINTMeasuring PointMust be an existing Measuring Point
IDATEDate of the MeasurementValid Date in the past, within 1 year from now
ITIMETime of MeasurementValid Time
MDTXTMeasurement Document TextNo Illegal Characters
MLANGLanguage KeyDefault "EN"
CNTRRCounter Reading in SI Unit

Counter reading cannot be 0

Counter Reading cannot be greater than overflow reading of Measuring Point

READGMeasurement Reading/Total Counter Reading in SI UnitTotal Counter Reading cannot be 0



Extraction Dependencies

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

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 Document

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 systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1PF2/WP2/DCT

IMRG

POINT

Measuring Point

S/4 HANA

IMRG

POINT

Measuring Point

Value Mapping: Measuring Point

Use POINT to map from old to new Measuring Point


2PF2/WP2/DCT

IMRG

IDATE

Date of the Measurement

S/4 HANA

IMRG

IDATE

Date of the Measurement

Direct Mapping

3PF2/WP2/DCT

IMRG

ITIME

Time of Measurement

S/4 HANA

IMRG

ITIME

Time of Measurement

Direct Mapping

4PF2/WP2/DCT

IMRG

MDTXT

Measurement Document Text

S/4 HANA

IMRG

MDTXT

Measurement Document Text

Direct Mapping

5



S/4 HANA

IMRGMLANG

Language Key

Default to "EN"

6PF2/WP2/DCTIMRG

CNTRR

Counter Reading in SI Unit

S/4 HANAIMRG

CNTRR

Counter Reading in SI Unit

If total Counter Reading and Counter Reading is the same (IMRG-READG=IMRG-CNTRR):

Direct Mapping

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.


Validation Rule: Counter reading cannot be 0


Validation Rule: 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


Direct Mapping.

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.


7PF2/WP2/DCTIMRG

READG

Measurement Reading/Total Counter Reading in SI Unit

S/4 HANAIMRG

READG

Measurement Reading/Total Counter Reading in SI Unit

Direct Mapping.

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.


Validation Rule: Total Counter Reading cannot be 0

Transformation Mapping

Mapping Table NameMapping Table Description

 

OTH_Technical Object Type_APM


List of Functional Location and Equipment TOTs required for migrating historical Measurement Documents and Notifications


Measuring Point

Mapping of legacy Measuring Point to new Measuring Point





Transformation Dependencies

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

1.      

Measuring point XREF table should be available after measuring point loaded.

Data Team











Pre-Load Validation

Project Team

Completeness

TaskAction

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

TaskAction

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

Completeness

TaskAction

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

TaskAction

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 DescriptionTeam 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

Item #Configuration Item
1Language Key




Conversion Objects

Object #Preceding Object Conversion Approach
1012Measuring Point




Error Handling

Error TypeError DescriptionAction Taken

Invalid Data

Invalid Measurement Document

Expedite whether the master data is available in the system








Post-Load Validation

Project Team

Completeness

TaskAction

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

TaskAction

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

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 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.
  • Data cleansing has met the required percentage threshold for the specified mock cycle and all preparation activities have been completed.


See also

Change log

Version Published Changed By Comment
CURRENT (v. 46) Apr 23, 2026 07:06 PUN-ext, Eddy
v. 144 Apr 07, 2026 16:51 PUN-ext, Eddy
v. 143 Apr 06, 2026 10:45 PUN-ext, Eddy
v. 142 Mar 17, 2026 10:15 PUN-ext, Eddy CR0282-Update in Relevancy Criteria: 1. The logic used to identify APM-related Measurement Documents needs to be revised so that the relevancy assessment does not depend on S/4 data.
v. 141 Mar 17, 2026 10:12 PUN-ext, Eddy
v. 140 Mar 12, 2026 09:41 PUN-ext, Eddy
v. 139 Mar 12, 2026 09:40 PUN-ext, Eddy
v. 138 Mar 12, 2026 09:39 PUN-ext, Eddy
v. 137 Mar 12, 2026 09:34 PUN-ext, Eddy CR0282
v. 136 Dec 18, 2025 11:44 PUN-ext, Eddy

Go to Page History

Workflow history

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

  • No labels