Status	Update in progress
Owner
Stakeholders

Purpose

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

Conversion Scope

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

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:

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.
If the Measuring Point is assigned to an ACTIVE Maintenance Plan, it must have valid and relevant Measurement Document to be migrated
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).

The data from legacy system excludes:

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	6000	S/4HANA	6000
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

N/A

Legal Requirement

N/A

Special Requirements

Target Design

The technical design of the target for this conversion approach.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement

Data Cleansing

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 . There are 2 possibilities:

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

Selection Ref Screen	Parameter Name	Selection Type	Requirement	Value to be entered/set
N/A

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 Name	Field Description	Rule
N/A

Extraction Dependencies

Item #	Step Description	Team Responsible
1	Measuring points need to be extracted first with their respective relevancy rules applied before measurement document data can be extracted referencing to the relevant measuring point.	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:

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

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic

Transformation Mapping

Mapping Table Name	Mapping Table Description

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

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

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:

Execute the automated data load into target system using load tool or product the load file if the load must be done manually
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

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

Configuration

Item #	Configuration Item
N/A

Conversion Objects

Object #	Preceding Object Conversion Approach
1012	Measuring Point

Error Handling

Error Type	Error Description	Action Taken
Invalid Data	Invalid Measuring point	Expedite whether the master data is available in the system

Post-Load Validation

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 Measuring Point data in target S/4 HANA were loaded correctly via dspMigrate post load reports or standard reports from S/4 HANA.

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 Measuring Point 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.

Change log

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

Apr 23, 2026	Actor	Type	Activity	Version
Update in progress	PUN-ext, Eddy	Comment	commented 7:06 am updated
Update in progress	PUN-ext, Eddy	State	changed state to Update in progress at 7:06 am	v145
Lead Approval	PUN-ext, Eddy	Edit	updated the page at 7:06 am
Apr 22, 2026
	MOUSSA-ext, Eva	State	changed expiry date to '29 Apr, 2026 02:46 pm' at 2:46 pm
	MOUSSA-ext, Eva	State	changed state to Lead Approval at 2:46 pm	v144
Tech Review of Updates	MOUSSA-ext, Eva	State	gave Minor change approval at 2:46 pm
Tech Review of Updates	MOUSSA-ext, Eva	State	changed state to Tech Review of Updates at 2:46 pm	v144
Update in progress	MOUSSA-ext, Eva	Comment	commented 2:31 pm to be removed related to PDM-1591

Workflow history

Space shortcuts

Page tree

CNV-9002 Measurement Document

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

Data Cleansing

Conversion Process

Data Privacy and Sensitivity

Extraction

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

Extraction Dependencies

Transformation

Transformation Run Sheet

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

Load Run Sheet

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

See also

Change log

Workflow history