Versions Compared

Old Version 89

changes.mady.by.user ERGUIZA-ext, Pinky Love

Saved on

compared with

New Version Current

changes.mady.by.user PUN-ext, Eddy

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: CR0438 - Active (JEST-INAC <> 'X')
Status

Page 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 BAGGA-ext, Abhishek 

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 Measuring Points (IMPTT-MPOBJ) linked to active Functional Locations (IFLOT-OBJNR) assigned to relevant plant (IFLOT-IWERK) in scope, which excludes the following status:
    1. Functional Location (IFLOT-TPLNR) with </Start CR0438> Active (JEST-INAC <> 'X') </End CR0438> System Status (JEST-STAT) Inactive "INAC"
    2. Functional Location (IFLOT-TPLNR) with </Start CR0438> Active (JEST-INAC <> 'X') </End CR0438> System Status (JEST-STAT) Deletion Flag "DLFL"
  2. All Measuring Points (IMPTT-MPOBJ) linked to active Equipment (EQUI-OBJNR) assigned to relevant plant (EQUI-IWERK) in scope, which excludes the following status:
    1. Equipment with </Start CR0438> Active (JEST-INAC <> 'X') </End CR0438> System Status (JEST-STAT) Inactive "INAC"
    2. Equipment with </Start CR0438> Active (JEST-INAC <> 'X') </End CR0438> System Status (JEST-STAT) Deletion Flag "DLFL"
    3. Equipment with System Status </Start CR0438> Active (JEST-STAT) INAC <> 'X') </End CR0438> System Status (JEST-STAT) In the warehouse "ESTO"
    4. Equipment with </Start CR0438> Active (JEST-INAC <> 'X') </End CR0438> System Status (JEST-STAT) Available "AVLB"
  • For the relevant plants in scope, refer to Value Mapping: Plant (Maintenance Plant = Yes)

The data from legacy system excludes:

  1. Measuring point without active Measurement Document (IMRG-POINT) created within the last 1 last 1 year (IMRG-ERDAT) 
    1. Active means without reversal indicator checked (IMRG-CANCL)
  2. Measuring Points which are inactive (IMPTT-INACT="X")


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


List of source systems and approximate number of records
SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

PF2, WP2DCTRelevant

Measuring Points will be

extracted from PF2 and WP2		6,000

S/4HANA

6,000
DCTMeasuring points for plants which do not have data existing from WP2 and PF2TBDS/4HANATBD

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)

TableFieldData ElementField DescriptionData TypeLengthRequirementIMPTTPOINTIMRC_POINTMeasuring PointCHAR12System GeneratedRIMR0MPOTYIMRC_MPOTYMeasuring Point ObjectCHAR3MandatoryEQUIEQUNREQUNREquipment NumberCHAR18ConditionalIFLOTTPLNRTPLNRFunctional LocationCHAR30ConditionalIMPTTMPTYPIMRC_MPTYPMeasuring Point CategoryCHAR1MandatoryIMPTTINDCTIMRC_INDCTCounter (Yes/No Indicator)CHAR1ConditionalIMPTTPSORTIMRC_PSORTPosition (Measuring Point Position)CHAR20MandatoryIMPTTPTTXTIMRC_PTTXTMeasuring Point DescriptionCHAR40MandatoryCABNATNAMATNAMCharacteristic Name (Link to Class/Char)CHAR30MandatoryIMPTTDECIMIMRC_DECIMNumber of Decimal PlacesINT5MandatoryIMPTTCODGRIMRC_CODGRCode GroupCHAR8ConditionalRIMR0MRMACIMRC_MRMACUpper Measurement Range Limit in Measurement Range UnitCHAR22ConditionalRIMR0MRMICIMRC_MRMICLower Measurement Range Limit in Measurement Range UnitCHAR22ConditionalIMPTTCJUMCIMRC_CJUMPCounter Over ReadingFLTP16ConditionalIMPTTPYEACIMRC_PYEARAnnual Counter ReadingFLTP16ConditionalRIMR0DESICIMRC_DESICMeasuring Point Target ValueCHAR22ConditionalIMPTTCDSUFIMRC_CDSUFIndicator: Valuation Code Sufficient for Measurmnt. DocumentCHAR1Conditional

2. Measuring Point (Characteristics Values Header)

TableFieldData ElementField DescriptionData TypeLengthRequirementKLAHKLARTKLASSENARTClass TypeCHAR3MandatoryINOB

OBTAB

TABELLEName of Database Table for ObjectCHAR30MandatoryKLAHCLASSKLASSE_DClass numberCHAR18MandatoryIMPTTPOINTIMRC_POINTMeasuring PointCHAR12

Mandatory

(Key to link to Measuring Point)

KLAHSTATUKLSTATUSClass StatusCHAR1Mandatory

3. Measuring Point (Characteristics Values Allocation)

TableFieldData ElementField DescriptionData TypeLengthRequirementKLAHKLARTKLASSENARTClass TypeCHAR3MandatoryINOB

OBTAB

TABELLEName of Database Table for ObjectCHAR30MandatoryKLAHCLASSKLASSE_DClass numberCHAR18MandatoryIMPTTPOINTIMRC_POINTMeasuring PointCHAR12

Mandatory

(Key to link to Measuring Point)

CABNATNAMATNAMCharacteristic NameCHAR30MandatoryAUSPATWRTATWRTCharacteristic ValueCHAR30MandatoryKSMLPOSNRKPOSNRItem NumberCHAR3Mandatory

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

IDCriticalityError Message/Report DescriptionRuleOutputSource System1012-001C1Missing Measuring Point DescriptionMeasuring Point as per Relevancy Criteria where there are blank Measuring Point Descriptions.Measuring Point, Description, PlantPF2, WP21012-002C1Missing Measuring Point PositionMeasuring Point as per Relevancy Criteria where there are blank Measuring Point Position.Measuring Point, Description, Plant, PositionPF2, WP21012-003C2Duplicate Measuring Point by same Technical Object, PositionMeasuring Point as per Relevancy Criteria where there is more than one Measuring Point with the same combination of Functional Location + Equipment + PositionMeasuring Point, Description, Plant, FL, EQ, PositionPF2, WP21012-004C3Info Report: Measuring Point which with latest Measurement Document that is older than 1 yearRetrieve the latest Measurement Document of the Measuring Point and list down all the Measuring points where the Measurement Document is older than 1 year. These Measuring Points will not be loaded unless there is a measuring point within 1 yearMeasuring Point, Description, Plant, FL, EQ, Measurement Document, Measurement Document DatePF2, WP21012-005Not ApplicableExternal Cleansing Report: Measuring Points not in SAP

Business to create the Measuring Points in legacy as part of this cleansing activity.

Note: This will be a business-led cleansing activity to be executed as part of the SyWay process.

No report development by ADMM

Not ApplicablePF2, WP2

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

collected via DCT. An initial extract of the relevant Measurement Documents will be provided in google sheet format to assist business in decision making on including any relevant Measuring Points from PF2 and WP2 as Measuring Points in S/4 HANA.

Any additional Measuring Points that need to be created to support the new design may be added in the DCT.

Please see an indication of what will be baselined from source systems below and what will be constructed in the DCT. 

Note: The decision to implement DCT only for Measuring Point and Measurement Document was based on the current business usage in SAP. The business has primarily been collecting relevant data outside of SAP. Additionally, it is not part of the current business process to create these Measuring Points and Measurement Documents in the system. Given that these two objects are not actively utilized and there are only a handful of Counter Based Maintenance Plans involved, the effort required to build the ETL process would not be justified at this time.

3,000

S/4HANA

3,000
DCTMeasuring points for plants which do not have data existing from WP2 and PF2TBDS/4HANATBD

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)

TableFieldData ElementField DescriptionData TypeLengthRequirement
IMPTTPOINTIMRC_POINTMeasuring PointCHAR12System Generated
IMPTTMPOTYIMRC_MPOTYMeasuring Point ObjectCHAR3Mandatory
EQUIEQUNREQUNREquipment NumberCHAR18Conditional
IFLOTTPLNRTPLNRFunctional LocationCHAR30Conditional
IMPTTMPTYPIMRC_MPTYPMeasuring Point CategoryCHAR1Mandatory
IMPTTINDCTIMRC_INDCTCounter (Yes/No Indicator)CHAR1Conditional
IMPTTPSORTIMRC_PSORTPosition (Measuring Point Position)CHAR20Mandatory
IMPTTPTTXTIMRC_PTTXTMeasuring Point DescriptionCHAR40Mandatory
CABNATNAMATNAMCharacteristic Name (Link to Class/Char)CHAR30Mandatory
IMPTTDECIMIMRC_DECIMNumber of Decimal PlacesINT5Mandatory
IMPTTCODGRIMRC_CODGRCode GroupCHAR8Conditional
IMPTTMRMAXIMRC_MRMAXUpper Measurement Range Limit in Measurement Range UnitCHAR22Conditional
IMPTTMRMINIMRC_MRMINLower Measurement Range Limit in Measurement Range UnitCHAR22Conditional
IMPTTCJUMCIMRC_CJUMPCounter Over ReadingFLTP16Conditional
IMPTTPYEACIMRC_PYEARAnnual Counter ReadingFLTP16Conditional
IMPTTDESIRIMRC_DESIRMeasuring Point Target ValueCHAR22Conditional
IMPTTCDSUFIMRC_CDSUFIndicator: Valuation Code Sufficient for Measurmnt. DocumentCHAR1Conditional


2. Measuring Point (Characteristics Values Header)

TableFieldData ElementField DescriptionData TypeLengthRequirement
KLAHKLARTKLASSENARTClass TypeCHAR3Mandatory
INOB

OBTAB

TABELLEName of Database Table for ObjectCHAR30Mandatory
KLAHCLASSKLASSE_DClass numberCHAR18Mandatory
IMPTTPOINTIMRC_POINTMeasuring PointCHAR12

Mandatory

(Key to link to Measuring Point)

KLAHSTATUKLSTATUSClass StatusCHAR1Mandatory


3. Measuring Point (Characteristics Values Allocation)

TableFieldData ElementField DescriptionData TypeLengthRequirement
KLAHKLARTKLASSENARTClass TypeCHAR3Mandatory
INOB

OBTAB

TABELLEName of Database Table for ObjectCHAR30Mandatory
KLAHCLASSKLASSE_DClass numberCHAR18Mandatory
IMPTTPOINTIMRC_POINTMeasuring PointCHAR12

Mandatory

(Key to link to Measuring Point)

CABNATNAMATNAMCharacteristic NameCHAR30Mandatory
AUSPATWRTATWRTCharacteristic ValueCHAR30Mandatory
AUSPPOSNRKPOSNRItem NumberCHAR3Mandatory


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

IDCriticalityError Message/Report DescriptionRuleOutputSource System
1012-001C3Info Report: Duplicate Measuring Point by same Technical Object, Position

Measuring Point as per Relevancy Criteria where there is more than one Measuring Point with the same combination of:

a) FL Measuring Point = FL + Position

b) EQ Measuring Point = EQ + Position 

Measuring Point, Description, Plant, FL, EQ, PositionPF2, WP2
1012-002C3Info Report: Measuring Point which with latest Measurement Document that is older than 1 yearRetrieve the latest active Measurement Document of the Measuring Point and list down all the Measuring points where the Measurement Document is older than 1 year. These Measuring Points will not be loaded unless there is an active measurement document within 1 yearMeasuring Point, Description, Plant, FL, EQ, Measurement Document, Measurement Document DatePF2, WP2

Note:

  1. Where the Plant is required in the output, retrieve the maintenance 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 diagram below:

Image Added

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

  • For sites not on SAP-PF2 or WP2 systems 
  • For Measuring Points that need to be created to support the to-be design

Data Privacy and Sensitivity

Not Applicable


Extraction

Extract data from a source into Advanced Data Migration and Management (ADMM). There are 2 possibilities:

  1. The data exists. ADMM connects to the source and loads the data into ADMM. 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 ADMM 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 ADMM. This is to be conducted using DCT (Data Collection Template) in ADMM.

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 ruleSyWay Data Team
2

Google Sheet report pre-populated with PF2 and WP2 information to be generated based on relevancy criteria. 

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

Delta Data Management: Initial collection will be done via the report and one-time load to the DCT will be performed. Any delta after the initial collection within the DCT will require business to take due diligence to ensure any subsequent delta cleansing is verified and aligned within the DCT.

Note: All rules specified below should be documented as a tooltip in the DC Page.

Format:

  • Line 1: Mandatory / Conditional
  • Line 2: Remaining text


1. Measuring Point Data Construction Rules

Field NameField DescriptionRule
ZLEGACYPOINTLegacy Measuring Point Number

Mandatory

Staging identifier used to uniquely define a Measuring Point.

MPOTYMeasuring Point Object

Mandatory

Allowed values:

IEQ: Equipment

IFL: Functional Location

POINT_OBJECTMeasuring Point Technical Object

Mandatory

If Measuring Point Object = IEQ, enter legacy Equipment

For non WP2/PF2, value must exist in Equipment DCT

If Measuring Point Object = IFL, for WP2/PF2, enter legacy FL

If Measuring Point Object = IFL, for non WP2/PF2, enter Category A Functional Location that does not have status "Maintenance Not Allowed"  

For non WP2/PF2, value must exist in Functional Location DCT

INDCTCounter (Yes/No Indicator)

Conditional

Checkbox

X = Yes

Blank = No

PSORTPosition (Measuring Point Position)

Mandatory

Measuring Position for the given Technical Object shall be always Unique.

PTTXTMeasuring Point Description

Mandatory

Follow convention: Characteristic Description + Asset Tag.

ATNAMCharacteristic Name

Mandatory

Allowed values:

  1. Characteristic assigned to Char Group MP_GNRL - Asset Parameter General
  2. Must exist in Characteristics DCT
CODGRCode Group

Conditional

A Code Group with Naming convention U-XX-XX created for Catalog "3" - Usage Decision shall be used, must exist in Code Group DCT.

MRMAXUpper Measurement Range Limit in Measurement Range Unit

Conditional

Only numeric values allowed.

Updated only if Counter is not checked.

MRMINLower Measurement Range Limit in Measurement Range Unit

Conditional

Only numeric values allowed.

Updated only if Counter is not checked.

CJUMCCounter Over Reading

Conditional

Updated if Counter is checked. Leave blank if Counter is not checked.

PYEACAnnual Counter Reading

Conditional

Updated if Counter is checked. Leave blank if Counter is not checked.

Annual counter cannot be more than 8760 Hr or 365 Days or 1 Year based on the unit of the characterisrics. 

DESIRMeasuring Point Target Value

Conditional

Only numeric values allowed.

Updated if Counter is not checked. Leave blank if Counter is checked.

CDSUFIndicator: Valuation Code Sufficient for Measurmnt. Document

Conditional

Checkbox

X = Yes

Blank = No

Can be updated only if Code Group is populated. Must be blank if Code Group is empty.

CHAR_DISCRETE_TO_ASSET


Discrete to the Asset Characteristic

Mandatory

Allowed values: Yes/No

Note: If blank, will be defaulted to "No"

Extraction Dependencies

Item #Step DescriptionTeam Responsible

Not Applicable



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

Obtain DCT Sign-off from Business.

SyWay Data Team

2

In dspMigrate, select the wave – 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 error reports

Business / Data owner

7

Generate load files

Syniti


Transformation Rules

1. Measuring Point (Main

Conversion Process

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

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

Image Removed

The following represents the high-level process for DCT:

Image Removed

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

Req #Requirement DescriptionTeam Responsible1Extract data from source system based on relevancy ruleSyWay Data Team

Selection Screen

Selection Ref ScreenParameter NameSelection TypeRequirementValue to be entered/setNot 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.

Delta Data Management: Initial collection will be done via the report and one-time load to the DCT will be performed. Any delta after the initial collection within the DCT will require business to take due diligence to ensure any subsequent delta cleansing is verified and aligned within the DCT.

Note: All rules specified below should be documented as a tooltip in the DC Page.

Format:

  • Line 1: Mandatory / Conditional
  • Line 2: Remaining text

1. Measuring Point Data Construction Rules

Field NameField DescriptionRuleZLEGACYPOINTLegacy Measuring Point Number

Mandatory

Staging identifier used to uniquely define a Measuring Point.

MPOTYMeasuring Point Object

Mandatory

Allowed values:

IEQ: Equipment

IFL: Functional Location

POINT_OBJECTMeasuring Point Technical Object

Mandatory

If Measuring Point Object = IEQ, enter legacy Equipment

> Value must exist in Equipment DCT

If Measuring Point Object = IFL, enter Category A Functional Location 

> Value must exist in Functional Location DCT

INDCTCounter (Yes/No Indicator)

Conditional

Checkbox

X = Yes

Blank = No

PSORTPosition (Measuring Point Position)

Mandatory

Measuring Position for the given Technical Object shall be always Unique.

PTTXTMeasuring Point Description

Mandatory

Follow convention: Characteristic Description + Asset Tag.

ATNAMCharacteristic Name

Mandatory

Allowed values:

  1. Characteristic assigned to Char Group MP_GNRL - Asset Parameter General
  2. Must exist in Characteristics DCT
CODGRCode Group

Conditional

A Code Group with Naming convention U-XX-XX created for Catalog "3" - Usage Decision shall be used, must exist in Code Group DCT.

MRMACUpper Measurement Range Limit in Measurement Range Unit

Conditional

Only numeric values allowed.

Updated only if Counter is not checked.

MRMICLower Measurement Range Limit in Measurement Range Unit

Conditional

Only numeric values allowed.

Updated only if Counter is not checked.

CJUMCCounter Over Reading

Conditional

Updated if Counter is checked. Leave blank if Counter is not checked.

PYEACAnnual Counter Reading

Conditional

Updated if Counter is checked. Leave blank if Counter is not checked.

Annual counter cannot be more than 8760 Hr or 365 Days or 1 Year based on the unit of the characterisrics. 

DESICMeasuring Point Target Value

Conditional

Only numeric values allowed.

Updated if Counter is checked. Leave blank if Counter is not checked.

CDSUFIndicator: Valuation Code Sufficient for Measurmnt. Document

Conditional

Checkbox

X = Yes

Blank = No

Can be updated only if Code Group is populated. Must be blank if Code Group is empty.

CHAR_DISCRETE_TO_ASSET

Discrete to the Asset Characteristic

Mandatory

Allowed values: Yes/No

Note: If blank, will be defaulted to "No"

Extraction Dependencies

Item #Step DescriptionTeam ResponsibleNot Applicable

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

Obtain DCT Sign-off from Business.

SyWay Data Team

2

In dspMigrate, select the wave – 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 error reports

Business / Data owner

7

Generate load files

Syniti

Transformation Rules

1. Measuring Point (Main) - DCT

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic1DCT-ZLEGACYPOINTLegacy Measuring Point Number----Key for Measuring Point Load2DCTIMPTTMPOTYMeasuring Point ObjectS/4 HANAIMPTTMPOTYMeasuring Point ObjectDirect Mapping3DCT-POINT_OBJECTMeasuring Point Technical ObjectS/4 HANAIMPTTEQUNREquipment Number

Value Mapping: Equipment Number where MPOTY= "IEQ"

4DCT-POINT_OBJECTMeasuring Point Technical ObjectS/4 HANAIMPTTTPLNRFunctional LocationValue Mapping: Functional Location where MPOTY= "IFL"5DCTIMPTTMPTYPMeasuring Point CategoryS/4 HANAIMPTTMPTYPMeasuring Point CategoryDefault to "M"6DCTIMPTTINDCTCounter (Yes/No Indicator)S/4 HANAIMPTTINDCTCounter (Yes/No Indicator)Direct Mapping7DCTIMPTTPSORTPosition (Measuring Point Position)S/4 HANAIMPTTPSORTPosition (Measuring Point Position)Direct Mapping8DCTIMPTTPTTXTMeasuring Point DescriptionS/4 HANAIMPTTPTTXTMeasuring Point DescriptionDirect Mapping9DCTIMPTTATNAMCharacteristic Name (Link to Class/Char)S/4 HANAIMPTTATNAMCharacteristic NameValue Mapping: Characteristic A2D10DCTIMPTTDECIMNumber of Decimal PlacesS/4 HANAIMPTTDECIMNumber of Decimal PlacesDefault to "3"11DCTIMPTTCODGRCode GroupS/4 HANAIMPTTCODGRCode GroupDirect Mapping12DCTIMPTTMRMACUpper Measurement Range Limit in Measurement Range UnitS/4 HANAIMPTTMRMACUpper Measurement Range Limit in Measurement Range UnitDirect Mapping13DCTIMPTTMRMICLower Measurement Range Limit in Measurement Range UnitS/4 HANAIMPTTMRMICLower Measurement Range Limit in Measurement Range UnitDirect Mapping14DCTIMPTTCJUMCCounter Over ReadingS/4 HANAIMPTTCJUMCCounter Over ReadingDirect Mapping15DCTIMPTTPYEACAnnual Counter ReadingS/4 HANAIMPTTPYEACAnnual Counter ReadingDirect Mapping16DCTIMPTTDESICMeasuring Point Target ValueS/4 HANAIMPTTDESICMeasuring Point Target ValueDirect Mapping17DCTIMPTTCDSUFIndicator: Valuation Code Sufficient for Measurmnt. DocumentS/4 HANAIMPTTCDSUFIndicator: Valuation Code Sufficient for Measurmnt. DocumentDirect Mapping

2. Measuring Point (Main) - ECC

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic1PF2, WP2IMPTTPOINTMeasuring Point----Key for Measuring Point Load2----S/4 HANAIMPTTMPOTYMeasuring Point Object

If EQUI-EQUNR is not blank, then "IEQ"

If IFLOT-TPLNR is not blank, then "IFL"

3PF2, WP2
  1. EQUI
  2. IFLOT
  1. EQUNR
  2. TPLNR
  1. Equipment
  2. Functional Location
S/4 HANAEQUIEQUNREquipment Number

Value Mapping: Equipment Number

Note: There is possibility that the legacy Functional Location is migrating to S/4 HANA Equipment.

4PF2, WP2IFLOTTPLNRFunctional LocationS/4 HANAIFLOTTPLNRFunctional Location

Value Mapping: Functional Location

There is possibility that the legacy Functional Location is migrating to S/4 HANA Equipment. This is indicated by the field "New Technical Object" in the Mapping Table. In this case, ensure that the transformation is performed from Functional Location to Equipment for IMPTT-EQUNR

5PF2, WP2IMPTTMPTYPMeasuring Point CategoryS/4 HANAIMPTTMPTYPMeasuring Point CategoryDefault to "M"6PF2, WP2IMPTTINDCTCounter (Yes/No Indicator)S/4 HANAIMPTTINDCTCounter (Yes/No Indicator)Direct Mapping7PF2, WP2IMPTTPSORTPosition (Measuring Point Position)S/4 HANAIMPTTPSORTPosition (Measuring Point Position)Direct Mapping8PF2, WP2IMPTTPTTXTMeasuring Point DescriptionS/4 HANAIMPTTPTTXTMeasuring Point Description

Direct Mapping

Overwrite with DCT if provided (as part of enrichment)

9PF2, WP2CABNATNAMCharacteristic NameS/4 HANACABNATNAMCharacteristic Name

Value Mapping: Characteristic A2D

Overwrite with DCT if provided (as part of enrichment)

10PF2, WP2IMPTTDECIMNumber of Decimal PlacesS/4 HANAIMPTTDECIMNumber of Decimal PlacesDefault to "3"11PF2, WP2IMPTTCODGRCode GroupS/4 HANAIMPTTCODGRCode Group

Value Mapping: Catalog Code Group and Code where New Catalog = "3"

Overwrite with DCT if provided (as part of enrichment)

12PF2, WP2RIMR0MRMACUpper Measurement Range Limit in Measurement Range UnitS/4 HANARIMR0MRMACUpper Measurement Range Limit in Measurement Range UnitDirect Mapping13PF2, WP2RIMR0MRMICLower Measurement Range Limit in Measurement Range UnitS/4 HANARIMR0MRMICLower Measurement Range Limit in Measurement Range UnitDirect Mapping14PF2, WP2IMPTTCJUMCCounter Over ReadingS/4 HANAIMPTTCJUMCCounter Over ReadingDirect Mapping15PF2, WP2IMPTTPYEACAnnual Counter ReadingS/4 HANAIMPTTPYEACAnnual Counter ReadingDirect Mapping16PF2, WP2RIMR0DESICMeasuring Point Target ValueS/4 HANARIMR0DESICMeasuring Point Target ValueDirect Mapping17PF2, WP2IMPTTCDSUFIndicator: Valuation Code Sufficient for Measurmnt. DocumentS/4 HANAIMPTTCDSUFIndicator: Valuation Code Sufficient for Measurmnt. DocumentDirect Mapping

3. Measuring Point (Characteristics Values Header) - DCT

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCT-ZLEGACYPOINTLegacy Measuring Point Number---
--
-Key for Measuring Point Load
2DCTIMPTTMPOTYMeasuring Point Object
-
S/4 HANA
KLAHKLARTClass TypeDefault to "037"2---
IMPTTMPOTYMeasuring Point Object

If target IMPTT.EQUNR has value, then “IEQ”

If target IMPTT.TPLNR has value, then “IFL”

3DCT-POINT_OBJECTMeasuring Point Technical Object
-
S/4 HANA
INOB
IMPTT
OBTABName of Database Table for ObjectDefault to "IMPTT"3--
EQUNREquipment Number

Value Mapping: Equipment Number where MPOTY= "IEQ"

Note: There is possibility that the legacy Functional Location is migrating to S/4 HANA Equipment. If that is the case:

Value Mapping: Equipment Number where MPOTY= "IFL

--S/4 HANAKLAHCLASSClass numberDefault to "EAM_9999

"

4DCT-
ZLEGACYPOINT
POINT_OBJECT
Legacy
Measuring Point
Number
Technical ObjectS/4 HANAIMPTT
POINT
TPLNR
Measuring Point
Functional Location

Value Mapping:

Measuring Point5----S/4 HANAKLAHSTATUClass StatusDefault to "1"

4. Measuring Point (Characteristics Values Header) - ECC

Functional Location where MPOTY= "IFL"

Note: There is possibility that the legacy Functional Location is migrating to S/4 HANA Equipment. This is indicated by the field "New Technical Object" in the Mapping Table. In this case, ensure that the transformation is performed from Functional Location to Equipment for IMPTT-EQUNR

5DCTIMPTTMPTYPMeasuring Point CategoryS/4 HANAIMPTTMPTYPMeasuring Point CategoryDefault to "M"
6DCTIMPTTINDCTCounter (Yes/No Indicator)
Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic1----
S/4 HANA
KLAH
IMPTT
KLARTClass TypeDefault to "037"2---
INDCTCounter (Yes/No Indicator)Direct Mapping
7DCTIMPTTPSORTPosition (Measuring Point Position)
-
S/4 HANA
INOB
IMPTT
OBTABName of Database Table for ObjectDefault to "IMPTT"3---
PSORTPosition (Measuring Point Position)Direct Mapping
8DCTIMPTTPTTXTMeasuring Point Description
-
S/4 HANA
KLAH
IMPTT
CLASSClass number

Default to "EAM_9999"

4PF2, WP2
PTTXTMeasuring Point DescriptionDirect Mapping
9DCTIMPTT
POINT
ATNAMCharacteristic Name (Link to Class/Char)
Measuring Point
S/4 HANAIMPTT
POINT
ATNAM
Measuring Point
Characteristic NameValue Mapping:
Measuring Point
Characteristic A2D
5
10
-
DCT
-
IMPTT
-
DECIMNumber of Decimal Places
-
S/4 HANA
KLAH
IMPTT
STATUClass Status
DECIMNumber of Decimal PlacesDefault to "
1Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic1----
3"

5. Measuring Point (Characteristics Values Allocation) - DCT 

11DCTIMPTTCODGRCode Group
S/4 HANA
KLAH
IMPTT
KLART
CODGR
Class TypeDefault to "037"2---
Code GroupDirect Mapping
12DCTIMPTTMRMAXUpper Measurement Range Limit in Measurement Range Unit
-
S/4 HANA
INOB
IMPTT
OBTABName of Database Table for ObjectDefault to "IMPTT"3---
MRMAXUpper Measurement Range Limit in Measurement Range UnitDirect Mapping
13DCTIMPTTMRMINLower Measurement Range Limit in Measurement Range Unit
-
S/4 HANA
KLAHCLASSClass number

Default to "EAM_9999"

IMPTTMRMINLower Measurement Range Limit in Measurement Range UnitDirect Mapping
14
4
DCT
-
IMPTT
ZLEGACYPOINTLegacy Measuring Point Number
CJUMCCounter Over ReadingS/4 HANAIMPTT
POINTMeasuring PointValue Mapping: Measuring Point5---
CJUMCCounter Over ReadingDirect Mapping
15DCTIMPTTPYEACAnnual Counter Reading
-
S/4 HANA
CABN
IMPTT
ATNAMCharacteristic NameValue Mapping: A2D Characteristics based on value A_DISCRETE_TO_ASSET6
PYEACAnnual Counter ReadingDirect Mapping
16DCT
-CHAR_DISCRETE_TO_ASSETDiscrete to the Asset Characteristic
IMPTTDESIRMeasuring Point Target ValueS/4 HANA
AUSP
IMPTT
ATWRT
DESIR
Characteristic
Measuring Point Target ValueDirect Mapping

If Blank, default to "No"

17DCTIMPTTCDSUFIndicator: Valuation Code Sufficient for Measurmnt. Document
7---
S/4 HANAIMPTT
KSMLPOSNRItem NumberDerive from SAP based on Characteristics Name and Class Number

UNION

CDSUFIndicator: Valuation Code Sufficient for Measurmnt. DocumentDirect Mapping

2. Measuring Point (Characteristics Values Header) - DCT

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1----S/4 HANAKLAHKLARTClass TypeDefault to "037"
2----S/4 HANAINOBOBTABName of Database Table for ObjectDefault to "IMPTT"
3----S/4 HANAKLAHCLASSClass number

Default to "EAM_9999"

4DCT-ZLEGACYPOINTLegacy Measuring Point NumberS/4 HANAIMPTTPOINTMeasuring PointValue Mapping: Measuring Point
5----S/4 HANACABNATNAMCharacteristic NameValue Mapping: A2D Characteristics based on value A_ALLOWED_CT
Legacy Measuring Point Number6DCT-CHAR_DISCRETE_TO_ASSETDiscrete to the Asset CharacteristicS/4 HANAAUSPATWRTCharacteristic Value

If CHAR_DISCRETE_TO_ASSET = "Yes", then leave blank

If CHAR_DISCRETE_TO_ASSET = "No" or blank, then derive value from Construction Type field (EQUI-SUBMT or IFLOT-SUBMT) of POINT_OBJECT.

IMPTTPOINTMeasuring PointValue Mapping: Measuring Point
5-7---S/4 HANAKSMLPOSNRItem NumberDerive from SAP based on Characteristics Name and Class NumberKLAHSTATUClass StatusDefault to "1"

36. Measuring Point (Characteristics Values Allocation) - ECCDCT 

(A_DISCRETE_TO_ASSET)

if provided (as part of enrichment)KSML
Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1----S/4 HANAKLAHKLARTClass TypeDefault to "037"
2----S/4 HANAINOBOBTABName of Database Table for ObjectDefault to "IMPTT"
3----S/4 HANAKLAHCLASSClass number

Default to "EAM_9999"

4PF2, WP2DCTIMPTT-POINTZLEGACYPOINTLegacy Measuring Point NumberS/4 HANAIMPTTPOINTMeasuring PointValue Mapping: Measuring Point
5----S/4 HANACABNATNAMCharacteristic NameValue Mapping: A2D Characteristics based on value A_DISCRETE_TO_ASSET
6DCT-CHAR_DISCRETE_TO_ASSETDiscrete to the Asset CharacteristicS/4 HANAAUSPATWRTCharacteristic Value

Direct Mapping

If Blank, default to "No"

7---
S/4 HANA
AUSPPOSNRItem Number
Derive from SAP based on Characteristics Name and Class Number
Default to "001"

UNION

(A_ALLOWED_CT)UNION

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1----S/4 HANAKLAHKLARTClass TypeDefault to "037"
2----S/4 HANAINOBOBTABName of Database Table for ObjectDefault to "IMPTT"
3----S/4 HANAKLAHCLASSClass number

Default to "EAM_9999"

4PF2, WP2DCTIMPTT-POINTZLEGACYPOINTLegacy Measuring Point NumberS/4 HANAIMPTTPOINTMeasuring PointValue Mapping: Measuring Point
5----S/4 HANACABNATNAMCharacteristic NameValue Mapping: A2D Characteristics based on value A_ALLOWED_CT
6----S/4 HANAAUSPATWRTCharacteristic Value

If CHAR_DISCRETE_TO_ASSET (from DCT) = "Yes", then leave blank

If CHAR_DISCRETE_TO_ASSET (from DCT) = "No" or blank, then derive value from Construction Type field (EQUI-SUBMT or IFLOT-SUBMT) of POINT_OBJECT.

7---
S/4 HANAKSMLAUSPPOSNRItem NumberDerive from SAP based on Characteristics Name and Class NumberDefault to "001"

List of Custom Target Reports for this object is maintained here: Conversion Specification - Custom Reports Register. 

Transformation Mapping

Mapping Table NameMapping Table Description

Plant

Old Plant to New Plant

Characteristic A2D

Old to New Characteristic A2D

Measuring Point

Legacy Measuring Point XREF mapping table

Note: New Measuring Point available post Load of Data

Catalog Code Group and Code

Mapping of legacy Catalog Code Group and Code to S/4 HANA Catalog Code Group and Code

Functional Location

Mapping of legacy Functional Location to new Functional Location

Equipment Number

Mapping of legacy Equipment to new Equipment

ENR_Measuring Point Discrete to Asset

Enrichment for Measuring Point Discrete to Asset Characteristics

ENR_Measuring Point Description

Enrichment for Measuring Point Description

ENR_Measuring Point Characteristic

Enrichment for Measuring Point Characteristic

Functional Location

Mapping of legacy Functional Location to new Functional Location

ENR_Measuring Point Code Group

Enrichment for Measuring Point Code Group


List of Transformation Mappings with additional details is maintained here: Transformation Mappings.

Transformation Dependencies

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

1

Ensure DCT tables completeness

SyWay Data Team

2

Ensure all Transformation mappings are up to date.

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

Ensure Pre-load sign-offs are obtained.

SyWay Data team

2

Go to the load tool and select the correct load Program.

SyWay Data team

3

Proceed with Data load.

SyWay Data team

4

Validate few records loaded by accessing standard transactions

SyWay Data team

5

Generate the post load reports in the tool.

SyWay Data team

6

Log errors as defects, if any and address resolutions. Close defects.

SyWay Data team

7

Resolve defects by reupload and re-generate post load reports if necessary.

SyWay Data team

8

Business to validate the post load files as part of post-load validation, raise data defects or provide the post-load sign-off.

Business

9

Repeat steps 5 to 7 if necessary.

SyWay Data team

Load Phase and Dependencies

Pre-Cutover

9

Repeat steps 5 to 7 if necessary.

SyWay Data team


Load Phase and Dependencies

Pre-Cutover 1012 - Measuring Point

Pre-Cutover: 1012a - Measuring Point Characteristics Assignment

Note: A separate load program may need to be created for 1012a if this becomes a risk to the actual cutover and need to be removed from the critical path. This will be evaluated post Mock 1

Configuration

Item #Configuration Item

1

T370P-Measuring Point Category

2

TCLA-Class Types

3

T370O-Measuring Point Object

Conversion Objects

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

Error Handling

Error TypeError DescriptionAction Taken

Configuration

Invalid measuring point categoryMeasuring Point Category

Engage Functional team to expedite and fix the error in the system

Configuration


Invalid measuring point Class TypeMeasuring Point Class Type

Engage Functional team to expedite and fix the error in the system

Configuration


Invalid Measuring Point Object

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

Invalid DataInvalid Class

Expedite whether the master data is available in the system

Invalid Data

Invalid Characteristics

Expedite whether the master data is available in the system

Invalid Data

Invalid Catalog Code and Code Group

Expedite whether the master data is available in the system

Invalid DataInvalid Construction Type

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

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 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. 
  • Data cleansing has met the required percentage threshold for the specified mock cycle and all preparation activities have been completed.
  • Data entries in DCT are target-ready data unless a specific transformation rule is stated for that field in the transformation rules.


See also

Change log

Change History
limit10

Workflow history

Workflow Report
parent@self
hideheadertrue
typeapprovals