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:

   1. Is not Category A (IFLOT-FLTYP)

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

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

The technical design of the target for this conversion approach.

1. Measuring Point (Main)

2. Measuring Point (Characteristics Values Header)

4. Measuring Point (Characteristics Values Allocation)

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

Note:

1. Where the Plant is required in the output, retrieve the planning plant of the linked object:
   1. Functional Location (IFLOT-IWERK)
   2. Equipment (EQUI-IWERK)
2. List of Cleansing is maintained here: Conversion Specs Register (DCT & Cleansing Report)

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

Selection Screen

Data Collection Template (DCT)

DCT Rules

Extraction Dependencies

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

Transformation Rules

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

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

Load Phase and Dependencies

Pre-Cutover

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

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.

See also

Change log

Workflow history