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

Compare with Current View Page History

« Previous Version 53 Next »

Status

  Approved

Owner
Stakeholders

WELENSKY-ext, Dave VILARES, ines LEIGHTON-ext, Dean PUN-ext, Eddy TEE-ext, Paul JOSHI-ext, Aditya Ayse Sarukan; Aurelia Stefanescu; [Syniti POD Lead]; [Syniti Consultant] 

Purpose

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

Legacy Plant Maintenance Characteristics is using a diverse range of formats across the different systems. There are instances where the same characteristics are duplicated within and across sources and with informal words. This results in data inconsistency. As per SyWay design, EAM Characteristics will be standardized.


Conversion Scope

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

Characteristics define a single custom field used to capture specific properties, attributes or values of an object. In SAP, Classes and Characteristics together form the “Classification System”.
For Syensqo, Characteristics will be used to record key attributes supporting reliability categorization and various analyses. It will be primarily used for information and reporting of attribute data across a large set of technical objects (e.g. Functional Location Structure). These Characteristics will be created centrally and assigned to relevant Classes.

From the current source systems’ perspective, Class and Characteristic concepts already exist (but in slightly different structure). Characteristic data and their allowed values are independently managed between PF2 and WP2. While these have been identified as source systems, a considerable amount of data construction will be required to support the production of data load sheets in the desired format.

While these systems serve as sources, extensive construction will be necessary to produce properly formatted data load sheets for S/4 HANA. 
The scope of this document covers the approach for converting active Characteristics from Legacy systems (PF2, WP2) and creation of New EAM Characteristics into S/4 HANA following the Characteristics Master Data Design Standard. 

The data from legacy system includes:

  1. Characteristics assigned to Classes with below Class Type
    • 001-Materials: PM Assembly (PF2, WP2)
    • 002-Equipment class (PF2, WP2)
    • 003-Functional location (PF2, WP2)
    • 018-Task list class (WP2)
    • 037-Measuring point (WP2)
  2. Characteristics assigned to Active Legacy Measuring Points
  3. Valid from [Current Date]
  4. Status = 1 (Released)

The data from legacy system excludes:

  1. Characteristics for Deletion (Deletion Indicator = X)

List of source systems and approximate number of records 

SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

PF2, WP2

Characteristics will be collected via DCT. An initial extract of the relevant Characteristics will be provided in google sheet format to assist business in decision making on including any relevant Characteristics from PF2 and WP2 as EAM Characteristics.

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

A review and standardization will be done across all characteristics in the DCT. 

6,500
6,500

Additional Information

Multi-language Requirement

EAM Characteristic description will be made available in English.
Multi language is supported for EAM Characteristics. Login via a different language will have its description displayed in the logon language if the language key is maintained in the Characteristics.

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

TableFieldData ElementField DescriptionData TypeLengthRequirement
CABNATNAMATNAMCharacteristic NameCHAR30Mandatory
CABNDATUVDATUVValid-From DateDATS8Mandatory
CABNATKLAATKLACharacteristics GroupCHAR10
CABNATMSTATMSTStatus of a characteristicCHAR1Mandatory
CABNATFORATFORData TypeCHAR4Mandatory
CABNANZSTANZSTNumber of CharactersINT25

Mandatory

(When Data Type = CURR, CHAR, NUM)

CABNANZDZANZDZNumber of Decimal PlacesINT25

Mandatory

(When Data Type = NUM)

CABNATKLEATKLECase SensitiveCHAR1

Mandatory

(When Data Type = CHAR)

CABNCURRENCYCURRENCYCurrency KeyCUKY1

Mandatory

(When Data Type = CURR)

CABNMSEHIMSEHIUnit of MeasureUNIT6

Mandatory

(When Data Type = NUM)

CABNATSCHATSCHValue with templateCHAR30

Mandatory

(When Data Type = CURR, CHAR, NUM)

CABNATDEXATDEXExponent Display FormatNUMC1

Mandatory

(When Data Type = NUM)

CABNATEINATEINSingle ValueCHAR1
CABNATAMEATAMEIndicator: More Than One Value Allowed for CharacteristicCHAR1
CABNATGLAATGLAIndicator: restrictable characteristicCHAR1
CABNATERFATERFEntry RequiredCHAR1
CABNATINTATINTInterval values allowedCHAR1
CABNATVORATVORValue with Plus or Minus SignCHAR1
CABNATSONATSONIndicator: Additional ValuesCHAR1


2. Characteristic Descriptions

TableFieldData ElementField DescriptionData TypeLengthRequirement
CABNATNAMATNAMCharacteristic NameCHAR30Mandatory
CABNTATBEZATBEZCharacteristic descriptionCHAR40Mandatory
CABNTSPRASSPRASLanguage Key (Characteristic Description)LANG1Mandatory

Note: Each Characteristic must have 1 entry for each language in scope: English, French, Italian, Mandarin, Brazilian, Portuguese, German and Spanish


3. Characteristic Restrictions to Class Types

TableFieldData ElementField DescriptionData TypeLengthRequirement
CABNATNAMATNAMCharacteristic NameCHAR30Mandatory
KSMLKLARTKLASSENARTClass Type03Mandatory

Note: One Characteristic should have at least one Class Type Restriction assigned.


4. Characteristic Values

TableFieldData ElementField DescriptionData TypeLengthRequirement
CABNATNAMATNAMCharacteristic NameCHAR30Mandatory
CAWNATWRTATWRTCharacteristic ValueCHAR30Mandatory
CAWNATSTDATSTDDefault valueCHAR1

Note: Construct Data Selection Value is to be defined for the Characteristic.


5. Characteristic Value Descriptions

TableFieldData ElementField DescriptionData TypeLengthRequirement
CABNATNAMATNAMCharacteristic NameCHAR30Mandatory
CAWNTSPRASSPRASLanguage Key (Characteristic Value Description)LANG1Mandatory
CAWNATWRTATWRTCharacteristic ValueCHAR30Mandatory
CAWNTATWTBATWTBCharacteristic Value DescriptionCHAR30Mandatory

Note: Each Characteristic Value must have 1 entry for each language in scope: English, French, Italian, Mandarin, Brazilian, Portuguese, German and Spanish


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


Data Cleansing

No data cleansing is required for Characteristics in the legacy systems. If any cleansing is deemed necessary, it will be performed outside of the systems.

As a result, the cleansed Characteristics data will be populated directly in the Data Collection Template (DCT).

IDCriticalityError Message/Report DescriptionRuleOutputSource System


Not Applicable



Conversion Process

The high-level process is represented by the diagram below:

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

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


Data Privacy and Sensitivity

Not Applicable


Extraction

  1. 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 Responsible
1Extract data from source system based on relevancy ruleSyWay Data Team
2Google 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 EAM Characteristics  data with exception of some fields which require transformation as mentioned in the transformation rule.

  1. The extracted report will be loaded into the required structure using the DCT.
  2. Standardization activities (including deduplication, standardization and additions)  will be carried out within the DCT.

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.

1. Characteristics DCT Rules

Field NameField DescriptionRule
ATNAMCharacteristic NameCharacteristics GroupMandatory.
  • If the characterMandatory.

    The naming convention for characteristics will follow the structure:
    EAM_ + Abbreviation 
    (For characteristics that are specific to a Measuring Point and intended for use only on that object, the characteristic name should start with “EAM_MPT + Abbreviation.)
    Abbreviation = should be meaningful to the end user.

    examples:
    EAM_MPT_RUN_HOURS

    EAM_PIPING_TYPEistic belongs to a group of similar characteristics, assign it to the appropriate characteristic group. Otherwise, leave the field blank
  • Must be a valid Characteristic Group (TCMG).
  • Characteristic Groups have the format <Group Code>_XXXX where Group Code is a 2 character field representing the functional group it relates to e.g. AM – Asset Management and XXXX is a 4 character abbreviation of the class the characteristics relate to.
    Char groups shall align with class groups.
DATUVValid-From Date

Conditional.

User must provide a value indicating when this characteristic will be valid for use. Otherwise, leave blank.

ATKLACharacteristics GroupIf the characteristic belongs to a group of similar characteristics, assign it to the appropriate characteristic group. Otherwise, leave the field blank
ATMSTStatus of a characteristic

Mandatory.

Non-Editable.

Allowed values:                        
0: In Preparation
1: Released
2: Locked

Default to ''1''

ATFORData Type

Mandatory

  • Character format (CHAR): for characteristic values that consist of a character string
  • Numeric format (NUM): for numeric characteristic values
  • Date format (DATE): for characteristic values that represent a date
  • Time format (TIME): for characteristic values that represent a time
  • Currency format (CURR): for characteristic values that are entered in a currency

Ensure use of a valid data type

ANZSTNumber of Characters

Conditional.

This field must be filled, when Data Type chosen '' CURR, CHAR, NUM'' 
Maximum value=30 for CHAR
Maximum value=15 for CURR
Maximum value=15 for NUM

ANZDZNumber of Decimal Places

Conditional.

This field can be filled when the Data Type is set to NUM. 
When 'CURR' is chosen, the field is automatically populated based on the selected currency.

ATKLECase Sensitive

Conditional.

Indicator (check box).

This field can to be filled, when Data Type chosen CHAR.

CURRENCYCurrency Key

Conditional.

This needs to be filled, when data type chosen CURR.

MSEHIUnit of Measure

Conditional.

This can be filled, when data type chosen NUM

ATSCHValue with template

Conditional.

This can be filled, when data type chosen CHAR, NUM, CURR

ATDEXExponent Display Format

Conditional.

Allowed values:              
0: No exponent
1: Standard
2: Exponent entered
3: Scientific exponent

This can to be filled, when data type chosen NUM

ATEINSingle Value

Conditional.

Indicator (check box).

Select this option if only a single value is allowed for the characteristic. If ‘Single Value’ is selected, the indicator ‘More Than One Value Allowed for Characteristic’ cannot be chosen.

ATAMEIndicator: More Than One Value Allowed for Characteristic

Conditional.

Indicator (check box).

Select this option if multiple value is allowed for the characteristic. If ‘More Than One Value Allowed for Characteristic’ is selected, the indicator ‘Single Value’ cannot be chosen. 

ATGLAIndicator: restrictable characteristic

Conditional.

Indicator (check box).

This can be marked, when data type chosen CHAR, CURR, DATE, NUM, TIME
This field can be selected only if the ‘More Than One Value’ indicator is marked.

ATERFEntry Required

Conditional.

Indicator (check box).

This can be marked, when data type chosen CHAR, CURR, DATE, NUM, TIME

ATINTInterval values allowed

Conditional.

Indicator (check box).

This can be marked, when data type chosen CURR, DATE, NUM, TIME

ATVORValue with Plus or Minus Sign

Conditional.

Indicator (check box).

This can be marked, when data type chosen CURR, NUM

ATSONIndicator: Additional Values

Conditional.

Indicator (check box).

Once the language key is selected, the description field should be filled in the corresponding language.

2. Characteristic Description DCT Rules

Field NameField DescriptionRule
ATNAMCharacteristic Name


ATBEZCharacteristic description

Mandatory.

  • The description should correspond to the Language Key provided.
  • Characteristic description should be in Title Case
  • Duplicate descriptions will not be allowed
SPRASLanguage Key (Characteristic Description)

Mandatory.

  • The selected Language Key must correspond to the description provided.
  • Language shall be English, French, Italian, Mandarin, Brazilian Portuguese, German and Spanish

 3. Characteristic Restrictions to Class Types DCT Rules

Field NameField DescriptionRule
ATNAMCharacteristic Name

Mandatory.

Should exist in Characteristics DCT Rules

KLASSENARTClass Type

Mandatory.

The following values apply to A2D;
001 - Material Class
002 - Equipment Class
003 - Functional Location
017 - Document Management
018 - Task List Class
037 - Measuring Point  Class
080 - Maintenance Plans Class

4. Characteristic Value DCT Rules

Field NameField DescriptionRule
ATNAMCharacteristic Name

Mandatory.

Should exist in Characteristics DCT Rules

ATWRTCharacteristic Value

Conditional.

If the characteristic has character format (CHAR), this field contains a single character string.
If values in time format (TIME) must have the format HH:MM:SS. The separators are set automatically.
Example:  112855  --> 11:28:55
If the values in date format (DATE) must have the format DD.MM.YYYY. The separators are set automatically.
Example: 110100  --> 11.01.2000

ATSTDDefault value

Conditional.

Indicator (check box).

If the business selects this checkbox for a value, it shall be marked; otherwise, it shall remain blank.

 5. Characteristic Value Description DCT Rules

Field NameField DescriptionRule
ATNAMCharacteristic Name

Mandatory.

Should exist in Characteristics DCT Rules

ATWRTCharacteristic Value

Mandatory.

Should exist in Characteristic Value DCT Rules

SPRASLanguage Key (Characteristic Value Description)

Mandatory.

  • The selected Language Key must correspond to the description provided.
  • Language shall be English, French, Italian, Mandarin, Brazilian Portuguese, German and Spanish
ATWTBCharacteristic Value Description

Mandatory.

  • The description should correspond to the Language Key provided.
  • Duplicate descriptions will not be allowed


Extraction Dependencies

Item #Step DescriptionTeam Responsible
1Relevancy Criteria for Functional LocationSyWay A2D Data Team
2Relevancy Criteria for EquipmentSyWay A2D Data Team
3Relevancy Criteria for Measuring PointsSyWay A2D 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

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

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

SyWay Data Team


Transformation Rules

1. Characteristics

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTCABNATNAMCharacteristic NameS/4 HanaCABNATNAMCharacteristic Name

Direct Mapping

A Global Value Mapping (Characteristic A2D) will be created to reference old PM Characteristics.

2DCTCABNDATUVValid-From DateS/4 HanaCABNDATUVValid-From Date

If has value in DCT, Direct Mapping.

If blank, default to Creation Date.

3DCTCABNATKLACharacteristics GroupS/4 HanaCABNATKLACharacteristics GroupDirect Mapping
4DCTCABNATMSTStatus of a characteristicS/4 HanaCABNATMSTStatus of a characteristicDirect Mapping
5DCTCABNATFORData TypeS/4 HanaCABNATFORData TypeDirect Mapping
6DCTCABNANZSTNumber of CharactersS/4 HanaCABNANZSTNumber of CharactersDirect Mapping
7DCTCABNANZDZNumber of Decimal PlacesS/4 HanaCABNANZDZNumber of Decimal PlacesDirect Mapping
8DCTCABNATKLECase SensitiveS/4 HanaCABNATKLECase SensitiveDirect Mapping
9DCTCABNCURRENCYCurrency KeyS/4 HanaCABNCURRENCYCurrency KeyDirect Mapping
10DCTCABNMSEHIUnit of MeasureS/4 HanaCABNMSEHIUnit of MeasureDirect Mapping
11DCTCABNATSCHValue with templateS/4 HanaCABNATSCHValue with templateDirect Mapping
12DCTCABNATDEXExponent Display FormatS/4 HanaCABNATDEXExponent Display FormatDirect Mapping
13DCTCABNATEINSingle ValueS/4 HanaCABNATEINSingle ValueDirect Mapping
14DCTCABNATAMEIndicator: More Than One Value Allowed for CharacteristicS/4 HanaCABNATAMEIndicator: More Than One Value Allowed for CharacteristicDirect Mapping
15DCTCABNATGLAIndicator: restrictable characteristicS/4 HanaCABNATGLAIndicator: restrictable characteristicDirect Mapping
16DCTCABNATERFEntry RequiredS/4 HanaCABNATERFEntry RequiredDirect Mapping
17DCTCABNATINTInterval values allowedS/4 HanaCABNATINTInterval values allowedDirect Mapping
18DCTCABNATVORValue with Plus or Minus SignS/4 HanaCABNATVORValue with Plus or Minus SignDirect Mapping
19DCTCABNATSONIndicator: Additional ValuesS/4 HanaCABNATSONIndicator: Additional ValuesDirect Mapping

2. Characteristic Descriptions

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTCABNATNAMCharacteristic NameS/4 HanaCABNATNAMCharacteristic Name

Direct Mapping

2DCTCABNTATBEZCharacteristic descriptionS/4 HanaCABNTATBEZCharacteristic description

Direct Mapping

Value Mapping: OTH_Informal Words and OTH_Invalid Characters
Review the value mappings for the presence of informal words or invalid characters.
If any are identified, replace them with the appropriate standardized values as specified in the mappings.

3DCTCABNTSPRASLanguage Key (Characteristic Description)S/4 HanaCABNTSPRASLanguage Key (Characteristic Description)Direct Mapping

3. Characteristic Descriptions

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTCABNATNAMCharacteristic NameS/4 HanaCABNATNAMCharacteristic Name

Direct Mapping

2DCTKSMLKLARTClass TypeS/4 HanaKSMLKLARTClass TypeDirect Mapping

4. Characteristic Values

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTCABNATNAMCharacteristic NameS/4 HanaCABNATNAMCharacteristic Name

Direct Mapping

2DCTCAWNATWRTCharacteristic ValueS/4 HanaCAWNATWRTCharacteristic ValueDirect Mapping
3DCTCAWNATSTDDefault valueS/4 HanaCAWNATSTDDefault valueDirect Mapping

5. Characteristic Value Descriptions

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTCABNATNAMCharacteristic NameS/4 HanaCABNATNAMCharacteristic Name

Direct Mapping

2DCTCAWNTSPRASLanguage Key (Characteristic Value Description)S/4 HanaCAWNTSPRASLanguage Key (Characteristic Value Description)Direct Mapping
3DCTCAWNATWRTCharacteristic ValueS/4 HanaCAWNATWRTCharacteristic ValueDirect Mapping
4DCTCAWNTATWTBCharacteristic Value DescriptionS/4 HanaCAWNTATWTBCharacteristic Value Description

Direct Mapping

Value Mapping: OTH_Informal Words and OTH_Invalid Characters
Review the value mappings for the presence of informal words or invalid characters.
If any are identified, replace them with the appropriate standardized values as specified in the mappings.

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

Transformation Mapping

Mapping Table NameMapping Table Description
Characteristic A2DCharacteristic A2D
OTH_Informal WordsList of Informal Words and the words used to replace
OTH_Informal CharactersList of Informal Characters 

Transformation Dependencies

List the steps that need to occur before transformation can commence
Item #Step DescriptionTeam Responsible
1Ensure DCT tables completenessSyniti
2Ensure all Transformation mappings are up to date.Syniti


Pre-Load Validation

Project Team

Completeness

TaskAction
Verify Record CountSyWay A2D Data Team to verify that the total number of relevant records from the  DCT is equal to the total number of records in the Preload and Load Sheets.

Accuracy

TaskAction
Conversion Accuracy

SyWay A2D 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 ReportsReview 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 CountBusiness Data Owner/s to verify that the total number of relevant records from the the DCT is equal to the total number of records in the Preload and Load Sheets.

Accuracy

TaskAction
Conversion AccuracyBusiness Data Owner/s to verify that all the data in the load table/file is accurate as per endorsed transformation/mapping rules (and signed-off DCT 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 re-upload 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

Configuration

Item #Configuration Item
1T002-Language Keys
2T006-Units of Measurement
3TCMG-Characteristic Group
4TCMS-Characteristic Status

Conversion Objects

Object #Preceding Object Conversion Approach
Not Applicable

Error Handling

Error TypeError DescriptionAction Taken
Configuration

Invalid Language Key

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

Configuration

Invalid Units of Measurement

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

Configuration

Invalid Characteristic Group

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

Configuration

Invalid Characteristic Status

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


Post-Load Validation

Project Team

Completeness

TaskAction

Verify Count

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

SyWay A2D Data Team to verify that the EAM Characteristics 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 EAM Characteristics 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. (If applicable for Cleansing)
  • Data entries in DCT are target-ready data unless a specific transformation rule is stated for that field in the transformation rules.
  • Not all legacy Plant Maintenance (PM) Characteristics need to be mapped to S/4 HANA PM Characteristics. If any of the successor objects is dependent on a PM Characteristic field with no mapped values, this will be an enrichment activity or manual transformation for the successor object to derive the PM Characteristic.


See also

Change log

Version Published Changed By Comment
CURRENT (v. 53) Mar 17, 2026 07:56 ERGUIZA-ext, Pinky Love
v. 141 Dec 10, 2025 15:40 ERGUIZA-ext, Pinky Love
v. 140 Dec 10, 2025 15:22 ERGUIZA-ext, Pinky Love
v. 139 Nov 13, 2025 12:14 ERGUIZA-ext, Pinky Love
v. 138 Nov 13, 2025 12:10 ERGUIZA-ext, Pinky Love
v. 137 Nov 13, 2025 12:01 ERGUIZA-ext, Pinky Love
v. 136 Nov 13, 2025 11:50 ERGUIZA-ext, Pinky Love
v. 135 Nov 04, 2025 14:35 ERGUIZA-ext, Pinky Love Consolidation of Char Values from 3 fields to 1 DCT Field
v. 134 Nov 04, 2025 14:30 ERGUIZA-ext, Pinky Love
v. 133 Nov 04, 2025 14:11 ERGUIZA-ext, Pinky Love

Go to Page History

Workflow history

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

  • No labels