Status
Owner	PUN-ext, Eddy
Stakeholders	ERGUIZA-ext, Pinky Love TEE-ext, Paul  JOSHI-ext, Aditya VILARES, ines LEIGHTON-ext, Dean LAKKAD-ext, Anirudh   STEFANESCU-ext, Aurelia  MOUSSA-ext, Eva HUSSAN-ext, Nishin

Purpose

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

Measuring point represents a physical or logical place at which a status or measurement is described. E.g. Temperature of the coolant or running hours of a motor.

Conversion Scope

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

At Syensqo, Measuring Points are used 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.

Syensqo primarily uses the following three types of Measuring Points:

1. Static Measuring Points
Static Measuring Points are used to capture snapshot values of an asset’s condition at a specific point in time. These readings represent parameters such as temperature, pressure, or vibration. The data collected through measurement documents enables trend analysis, which helps in assessing the health and performance of the asset.

Example: Monitoring equipment temperature over time.

2. Counter Measuring Points
Counter Measuring Points are used to capture the cumulative usage of an asset. These points incrementally track metrics such as operating hours, production cycles, or distance travelled. Measurement documents recorded at these points are often used to trigger maintenance plans based on usage, as per the maintenance strategy assigned to the asset.

Example: Tracking total operating hours of a motor.

3. Catalog Measuring Points
Catalog Measuring Points utilize predefined catalog codes to record qualitative or classified conditions observed during asset inspections. These codes represent specific condition statuses or fault categories. The selected catalog entry reflects the assessment of the asset’s condition, typically after a physical or visual check.

The data from legacy system includes:

1. All active Measuring Points (IMPTT-MPOBJ) linked to relevant Functional Locations (IFLOT-OBJNR)
2. All active Measuring Points (IMPTT-MPOBJ) linked to relevant Equipment (EQUI-OBJNR)

The data from legacy system excludes:

1. Measuring point without Measurement Document (IMRG-POINT) created within the last 1 year (IMRG-ERDAT) 
2. Measuring Points which are inactive (IMPTT-INACT='X')
3. Meausring Points where linked Functional Location:

• Is not Category A (IFLOT-FLTYP)

• Has active user status (JEST-INACT) as "Maintenance Not Allowed" (JEST-STAT, TJ30T-TXT30)

  
  

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

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	Relevant Measuring Points will be extracted from PF2 and WP2	6,000	S/4HANA	6,000
DCT	Measuring points for plants which do not have data existing from PF2 and PF2	TBD	S/4HANA	TBD

Additional Information

Multi-language Requirement

Measuring point object does not have multi language support. Description will be made available in the language required by the respective plant using EN logon.

Document Management

Not Applicable

Legal Requirement

Not Applicable

Special Requirements

Not Applicable

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.

1. Measuring Point (Main)

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
IMPTT	POINT	IMRC_POINT	Measuring Point	CHAR	12	System Generated
RIMR0	MPOTY	IMRC_MPOTY	Measuring Point Object	CHAR	3	Mandatory
EQUI	EQUNR	EQUNR	Equipment Number	CHAR	18	Conditional
IFLOT	TPLNR	TPLNR	Functional Location	CHAR	30	Conditional
IMPTT	MPTYP	IMRC_MPTYP	Measuring Point Category	CHAR	1	Mandatory
IMPTT	INDCT	IMRC_INDCT	Counter (Yes/No Indicator)	CHAR	1	Conditional
IMPTT	PSORT	IMRC_PSORT	Position (Measuring Point Position)	CHAR	20	Mandatory
IMPTT	PTTXT	IMRC_PTTXT	Measuring Point Description	CHAR	40	Mandatory
CABN	ATNAM	ATNAM	Characteristic Name (Link to Class/Char)	CHAR	30	Mandatory
IMPTT	DECIM	IMRC_DECIM	Number of Decimal Places	INT	5	Mandatory
IMPTT	CODGR	IMRC_CODGR	Code Group	CHAR	8	Conditional
RIMR0	MRMAC	IMRC_MRMAC	Upper Measurement Range Limit in Measurement Range Unit	CHAR	22	Conditional
RIMR0	MRMIC	IMRC_MRMIC	Lower Measurement Range Limit in Measurement Range Unit	CHAR	22	Conditional
IMPTT	CJUMC	IMRC_CJUMP	Counter Over Reading	FLTP	16	Conditional
IMPTT	PYEAC	IMRC_PYEAR	Annual Counter Reading	FLTP	16	Conditional
RIMR0	DESIC	IMRC_DESIC	Measuring Point Target Value	CHAR	22	Conditional
IMPTT	CDSUF	IMRC_CDSUF	Indicator: Valuation Code Sufficient for Measurmnt. Document	CHAR	1	Conditional

2. Measuring Point (Characteristics Values Header)

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
KLAH	KLART	KLASSENART	Class Type	CHAR	3	Mandatory
INOB	OBTAB	TABELLE	Name of Database Table for Object	CHAR	30	Mandatory
KLAH	CLASS	KLASSE_D	Class number	CHAR	18	Mandatory
IMPTT	POINT	IMRC_POINT	Measuring Point	CHAR	12	Mandatory
KLAH	STATU	KLSTATUS	Class Status	CHAR	1	Mandatory

4. Measuring Point (Characteristics Values Allocation)

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
KLAH	KLART	KLASSENART	Class Type	CHAR	3	Mandatory
INOB	OBTAB	TABELLE	Name of Database Table for Object	CHAR	30	Mandatory
KLAH	CLASS	KLASSE_D	Class number	CHAR	18	Mandatory
IMPTT	POINT	IMRC_POINT	Measuring Point	CHAR	12	Mandatory
CABN	ATNAM	ATNAM	Characteristic Name	CHAR	30	Mandatory
AUSP	ATWRT	ATWRT	Characteristic Value	CHAR	30	Mandatory
KSML	POSNR	KPOSNR	Item Number	CHAR	3	Mandatory

Measuring Point Data strictly adheres to the Master Data Standard. The complete information of the key fields that hold the Measuring Point information follows the Master Data Standard document that is located here.

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
1012-001	C1	Missing Measuring Point Description	Measuring Point as per Relevancy Criteria where there are blank Measuring Point Descriptions.	Measuring Point, Description, Plant	PF2, WP2
1012-002	C1	Missing Measuring Point Position	Measuring Point as per Relevancy Criteria where there are blank Measuring Point Position.
1012-004	C1	Invalid or Inactive Catalog Code Groups & Code linked to Measuring Point	Measuring Point as per Relevancy Criteria assigned with a Catalog Code Groups & Code which does not belong below: 1. Catalog Code Groups & Codes as per Relevancy Criteria	Measuring Point, Catalog Code Group, Catalog Code	PF2, WP2
1012-005	C1	Invalid or Inactive Construction Type linked to Measuring Point	Measuring Point as per Relevancy Criteria assigned with a Construction Type which does not belong below: 1. Construction Type as per Relevancy Criteria	Measuring Point, Construction Type	PF2, WP2
1012-006	C1	Invalid or Inactive Characteristic linked to Measuring Point	Measuring Point as per Relevancy Criteria assigned with a Characteristic which does not belong below: 1. Characteristic as per Relevancy Criteria	Measuring Point, Characteristic	PF2, WP2
1012-007	C1	Invalid or Inactive Class linked to Measuring Point	Measuring Point as per Relevancy Criteria assigned with a Class which does not belong below: 1. Class as per Relevancy Criteria	Measuring Point, Class	PF2, WP2
1012-009	C1	Invalid, Inactive or no Maintenance Plans linked to Measuring Point	Measuring Point as per Relevancy Criteria with no Maintenance Plan Linked or with a Maintenance Plan which does not belong below: 1. Maintenance Plan as per Relevancy Criteria	Measuring Point, Maintenance Plan, Maintenance Plan Status	PF2, WP2
1012-010	C3	Duplicate Measuring Point by same Technical Object, Position, Description, Char and Type	Measuring Point as per Relevancy Criteria where there is more than one Technical Object + Position + Description + Char + Type Combination. > double check with MDS	Measuring Point, FL, EQ, Position, Description, Characteristics, Type	PF2, WP2
1012-011	C1	Measuring Point Technical object authorization group incorrect.	Measuring Point as per Relevancy Criteria with Invalid Authorization Group (T370F)	Measuring Point, Authorisation Group	PF2, WP2
1012-012	C1	Measuring Point UOM Missing / incorrect.	Measuring Point as per Relevancy Criteria with no UoM Assigned or Invalid UoM (T006)	Measuring Point, UOM	PF2, WP2
1012-013	C2	Measuring Point which with latest Measurement Document that is older than 1 year	Retrieve the latest Measurement Document of the Measuring Point and list down all the Measuring points where the Measurement Document is older than 1 year	Measuring Point, FL / EQ, Description, Measurement Document, Measurement Document Date	PF2, WP2

Note: Where the Plant is required in the output, retrieve the planning plant of the linked object:

• Functional Location
• Equipment

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

Summarize Data Privacy and Sensitivity Requirements, if any

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 Measuring Point data with exception of some fields which require transformation as mentioned in the transformation rule.

<Object> DCT Rules

Field Name	Field Description	Rule

Extraction Dependencies

List the steps that need to occur before extraction can commence

Item #	Step Description	Team Responsible
1	Only Measuring Points linked to relevant Functional Location and Equipment 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 – Measuring Point	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

Transformation Mapping

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

Mapping Table Name	Mapping Table Description
Characteristic Name	Characteristic Name XREF mapping table
Measuring Point	Legacy Measuring Point XREF mapping table
Code Group	Code Group mapping table
Functional Location and Equipment	Legacy Functional Location and Equipment XREF mapping table
Equipment	Legacy Equipment XREF mapping table

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible

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

Sequence of load:

1. All Measuring points are created with no transfer reading.
2. After the Measuring Points are loaded successfully then the Measuring Point transfer reading is loaded.

Measuring point without transfer reading need to be loaded before measuring point with transfer reading.

For Legacy measuring point, XREF table generated from the first load for measuring point without transfer reading need to be used in the second load to transform the legacy measuring point to the SyWAY measuring point number for transfer reading.

Load Run Sheet

Item #	Step Description	Team Responsible

Load Phase and Dependencies

Pre-Cutover

Configuration

List the Configurations required before loading can commence

Item #	Configuration Item
1	Measuring point category
2	Units of Measurement
3	Class Types
4	Technical Object Type

Conversion Objects

Object #	Preceding Object Conversion Approach
1003	Functional Location
1002	Equipment
1009	Class
1015	Characteristics
1007	Catalog Code and Code Group
1010	Construction Type

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
Configuration	Invalid measuring point category	Engage Functional team to expedite and fix the error in the system
Configuration	Invalid measuring point characteristic	Engage Functional team to expedite and fix the error in the system
Configuration	Invalid measuring point code group	Engage Functional team to expedite and fix the error in the system
Invalid Data	Invalid Functional Location	Expedite whether the master data is available in the system
Invalid Data	Invalid Equipment	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 Measuring Point 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 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 is up to date as on the date of documenting this conversion approach and data load. 
• Measuring Point is in scope based on data design and any exception requested by business.
• Mapping values for characteristic and code group must be available for direct transform of legacy measuring point to new measuring point.
• Data cleansing has met the required percentage threshold for the specified mock cycle and all preparation activities have been completed.

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