Purpose

The purpose of this document is to define the conversion approach to create Maintenance Plan and Item in S/4 HANA.

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



Conversion Scope

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

A Maintenance Plan is a scheduling framework that determines timing and frequency of preventive maintenance tasks.
Key features:
- Can include one or more maintenance items
- Drives the creation of maintenance calls (notifications/orders)
- Linked to a planning plant, which controls scheduling

A Maintenance Item specifies the actual task, technical object and a task list to be performed. It defines:
- The equipment, functional location, or object list to be maintained
- The task list describing detailed operations
Key features:
- Multiple items can be assigned to one plan
- Each item can have its own task list
- Enables tracking of maintenance history per object

The data from legacy system includes:

  1. Maintenance Plan (MPLA-WARPL) that has at least 1 relevant Maintenance Item (MPOS-WAPOS)
  2. Maintenance Items (MPOS-WAPOS) that has at least 1 valid task list based on Task List Relevancy Criteria (PLKO-PLNTY, PLKO-PLNNR, PLKO-PLNAL)
  3. Maintenance Items (MPOS-WAPOS) that has at least 1 relevant Functional Location (IFLOT-TPLNR) or Equipment (EQUI-EQUNR)
  4. Maintenance Items (MPOS-WAPOS) having Maintenance Planning Plant (MPOS-IWERK) in scope - Refer to Value Mapping: Plant (Maintenance Plant = Yes)

The data from legacy system excludes:

  1. Maintenance Plan (MPLA-WARPL) marked inactive (MPLA-LVORM) = 'X'
  2. Maintenance Items (MPOS-WAPOS) that are not assigned to Maintenance Plan (MPLA-WARPL)

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

Maintenance Plan:

Relevant Maintenance Plan will be extracted from PF2 and WP2

70,000

S/4HANA 

70,000

PF2, WP2

Maintenance Items:

Relevant Maintenance Item will be extracted from PF2 and WP2

74,000

S/4HANA 

74,000

DCT

Maintenance Plan and Maintenance Item for plants which do not have data existing from PF2 and WP2

TBD

S/4HANA 

TBD

Additional Information

Multi-language Requirement
Maintenance Plan description will be made available in English.
Multi language is supported for Maintenance Plan. Login via a different language will have its description displayed in the logon language if the language key is maintained in the Maintenance Plan.

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

TableFieldData ElementField DescriptionData TypeLengthRequirement
MPLAWARPLWARPLMaintenance PlanCHAR12

System

Key field

MPLAMPTYPMPTYPMaintenance plan categoryCHAR2Mandatory
MPLASTRATSTRATMaintenance strategyCHAR6Mandatory
MPLAWPTXTWPTXTMaintenance Plan TextCHAR40Mandatory
MPLAVSPOSVERSCHPLUSShift Factor for Late CompletionNUMC3Conditional
MPLATOPOSTOLERPLUSTolerance for Late Completion (%)NUMC3Conditional
MPLATONEGTOLERNEGTolerance for Early Completion (%)NUMC3Conditional
MPLAVSNEGVERSCHNEGShift Factor for Early CompletionNUMC3Conditional
MPLASFAKTSFAKTCycle modification factorDEC3(2)Conditional
MPLAFABKLFABKLFactory calendar keyCHAR2Conditional
MPLAHORIZHORIZONTCall horizon for maintenance plan callsNUMC3Mandatory
MPLAHORIZ_QUALIFIEREAM_CC_CALLHORIZON_QUALIFIERCalculation Type of Call HorizonCHAR1Mandatory
MPLAABRHOABRHOScheduling PeriodNUMC3Mandatory
MPLAHUNITHUNITUnit for Scheduling PeriodUNIT3Conditional
MPLACALL_CONFIRMCALL_CONFIRMOnly Create New Call Object After Completing PredecessorCHAR1Conditional
MPLASTADTSTADTStart dateDATS8Conditional
RMIPMZEITTIME_KNZIndicator for selection of time-based maintenanceCHAR1Conditional
MPLASTICHTERMKNZScheduling indicatorCHAR1Conditional
MPLAPLAN_SORTPLAN_SORTSort field for maintenance plansCHAR20Mandatory
MPLAENDDT_FOR_SCHEDEAM_ENDDT_FOR_SCHEDEnd Date for SchedulingDATS8Conditional
RMIPMTPLNRTPLNRFunctional LocationCHAR30Mandatory
RMIPMEQUNREQUNREquipment NumberCHAR18Conditional
RMIPMGEWRKGEWRKMain work Centre for maintenance tasksCHAR8Conditional
RMIPMPOINTIMRC_POINTMeasuring PointCHAR12Conditional

2.Maintenance Plan Long Text Header

TableFieldData ElementField DescriptionData TypeLengthRequirement
STXHTDOBJECTTDOBJECTTexts: application objectCHAR10

Mandatory

Key field

STXHTDNAMETDOBNAMENameCHAR70

Mandatory

Key field

STXH

TDID

TDID

Text IDCHAR4

Mandatory

Key field

STXHTDSPRASSPRASLanguage KeyLANG1

Mandatory

Key field

3.Maintenance Plan Long Text Line

TableFieldData ElementField DescriptionData TypeLengthRequirement
STXLRELIDSYCHAR02CHAR02 data element for SYSTCHAR2

Mandatory

Key field

STXLTDOBJECTTDOBJECTTexts: application objectCHAR10

Mandatory

Key field

STXLTDNAMETDOBNAMENameCHAR70

Mandatory

Key field

STXL

TDID

TDID

Text IDCHAR4

Mandatory

Key field

STXLTDSPRASSPRASLanguage KeyLANG1

Mandatory

Key field

STXLCLUSTD_TAGTDFORMAT

Tag column

CHAR1

Mandatory

STXLROWCOUNTROWCOUNT

Row number

NUMC10Mandatory
STXLCLUSTD_LINETDLINE

Text Line

CHAR72Mandatory

Note:

  1. Long Text is not mandatory, only load when cleansed
  2. One Long Text Header must have at least 1 Long Text Line

4.Maintenance Item

TableFieldData ElementField DescriptionData TypeLengthRequirement
MPLAWARPLWARPLMaintenance PlanCHAR12

System

Link to MPLA

MPOSWAPOSWAPOSMaintenance itemCHAR16

System

Key field

MPOSWSTRASTRATMaintenance StrategyCHAR6Mandatory
MPOSPSTXTPOSTXTItem Short TextCHAR40Mandatory
MPOSAUARTAUFARTOrder TypeCHAR4Mandatory
MPOSPRIOKPRIOKPriorityCHAR1Mandatory
MPOSPLNTYPLNTYTask List TypeCHAR1Mandatory
MPOSPLNNRPLNNRKey for Task List GroupCHAR8Mandatory
MPOSPLNALPLNALGroup CounterCHAR2Mandatory
MPOSWPGRPINGRPMaintenance Planner GroupCHAR3Conditional
MPOSAPFKTAPFKTExecution factor for whole task listDEC3(0)Conditional
MPOSANLZUANLZUSystem ConditionCHAR1Conditional
MPOS

ILART

ILAMaintenance activity typeCHAR3Mandatory
RMIPM

TPLNR

TPLNRFunctional LocationCHAR30Mandatory
RMIPM

EQUNR

EQUNREquipment NumberCHAR18Conditional

Note: Each Maintenance Plan can have multiple Maintenance Items

5.Maintenance Item Long Text Header

TableFieldData ElementField DescriptionData TypeLengthRequirement
STXHTDOBJECTTDOBJECTTexts: application objectCHAR10Mandatory
STXHTDNAMETDOBNAMENameCHAR70Mandatory
STXH

TDID

TDID

Text IDCHAR4Mandatory
STXHTDSPRASSPRASLanguage KeyLANG1Mandatory

6.Maintenance Item Long Text Line

TableFieldData ElementField DescriptionData TypeLengthRequirement
STXLRELIDSYCHAR02CHAR02 data element for SYSTCHAR2

Mandatory

Key field

STXLTDOBJECTTDOBJECTTexts: application objectCHAR10

Mandatory

Key field

STXLTDNAMETDOBNAMENameCHAR70

Mandatory

Key field

STXL

TDID

TDID

Text IDCHAR4

Mandatory

Key field

STXLTDSPRASSPRASLanguage KeyLANG1

Mandatory

Key field

STXLCLUSTD_TAGTDFORMAT

Tag column

CHAR1

Mandatory

STXLROWCOUNTROWCOUNT

Row number

NUMC10Mandatory
STXLCLUSTD_LINETDLINE

Text Line

CHAR72Mandatory

Note:

  1. Long Text is not mandatory, only load when cleansed
  2. One Long Text Header must have at least 1 Long Text Line

7.Maintenance Item Object List

TableFieldData ElementField DescriptionData TypeLengthRequirement
OBJKOBKNROBJKNRObject list numberINT819

System

Key field

OBJKOBZAEOBJZAObject list countersINT410

System

Key field

OBJKSORTFOBSORTObject list sort fieldCHAR20Conditional
OBJKTPLNRTPLNRFunctional LocationCHAR30Conditional
OBJKEQUNREQUNREquipment NumberCHAR18Conditional

Note: Each Maintenance Item can have multiple Objects or no Object at all.

8.Maintenance Plan (Characteristics Values Header)

TableFieldData ElementField DescriptionData TypeLengthRequirement
KLAHKLARTKLASSENARTClass TypeCHAR3Mandatory
INOB

OBTAB

TABELLEName of Database Table for ObjectCHAR30Mandatory
KLAHCLASSKLASSE_DClass numberCHAR18Mandatory
INOBOBJEKCUOBNKey of ObjectCHAR90Mandatory
KLAHSTATUKLSTATUSClass StatusCHAR1Mandatory

9.Maintenance Plan (Characteristics Values Allocation)

TableFieldData ElementField DescriptionData TypeLengthRequirement
KLAHKLARTKLASSENARTClass TypeCHAR3Mandatory
INOB

OBTAB

TABELLEName of Database Table for ObjectCHAR30Mandatory
KLAHCLASSKLASSE_DClass numberCHAR18Mandatory
INOBOBJEKCUOBNKey of ObjectCHAR90Mandatory
CABNATNAMATNAMCharacteristic NameCHAR30Mandatory
AUSPATWRTATWRTCharacteristic ValueCHAR30Mandatory
KSMLPOSNRKPOSNRItem NumberCHAR3Mandatory

 Maintenance Plan and Item Data strictly adheres to the Master Data Standard. The complete information of the key fields that hold the Maintenance Plan information follows the Master Data Standard document that is located here.


Data Cleansing

IDCriticalityError Message/Report DescriptionRuleOutputSource System

1016-001

C1

Maintenance Plan-Description: Missing Description

Maintenance Plan Description is blank

Maintenance Plan, Description, Plant,   Description 

PF2, WP2

1016-002

C1

Maintenance Item-Task List: Invalid, Inactive or no Task List allocated to Maintenance Plan 

Maintenance Item as per Relevancy Criteria assigned with a Task List which does not belong below:
1. Task List as per Relevancy Criteria 

Maintenance Item, Item Short Text, Plant, Task List 

PF2, WP2

1016-003

C1 

Maintenance Plan: Duplicate Maintenance Plan by Technical Object

Maintenance Plan and Items as per Relevancy Criteria where there is more than Maintenance Plan assigned to the same Technical Object

Maintenance Item, Item Short Text, Plant, Technical Object

PF2, WP2

Note: List of Cleansing is maintained here: Conversion Specs Register (DCT & Cleansing Report)


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

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


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

Extract data from source system based on relevancy rule

SyWay 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 ScreenParameter NameSelection TypeRequirementValue to be entered/set
Not Applicable




Data Collection Template (DCT)

Target Ready Data Collection Template will be created for data with exception of some fields which require transformation as mentioned in the transformation rule. 

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.Maintenance Plan Data Construction Rules

Field NameField DescriptionRule
zLegacyWARPLLegacy Maintenance Plan

Mandatory.

Key field

STRAT

Maintenance strategy

Mandatory.

Must reference Strategy in Maintenance Strategy DCT.
Must be the same strategy as the Task List strategy.

TOPOSTolerance for Late Completion (%)

Conditional.

Numeric values only, values from 0 to 100

Note: Will default to "10" if blank

TONEGTolerance for Early Completion (%)

Conditional.

Numeric values only, values from 0 to 100

Note: Will default to "10" if blank

SFAKTCycle modification factor

Conditional.

Note: Will default to "1" if blank

FBKL

Time-factory caldr

Conditional.

Select from configuration (TFACD)

HORIZ

Call horizon for maintenance plan calls

Mandatory.

Numeric values only, values from 0 to 100

Note: Will default to "100" if blank

ABRHO

Scheduling Period

Mandatory.

Note: Will default to "3" if blank

HUNIT

Unit for Scheduling Period

Conditional.

Note: Will default to "YR" if blank

CALL_CONFIRM

Completion Requirement

Conditional.

Allowed values:

  1. "X" - checked
  2. blank - unchecked

STADT

Start date

Conditional.

All Date format should be DDMMYYYY

STICH

Scheduling indicator

Conditional.

If first 2 Chars of the Strategy <> " 02" (Performance-Based Strategy) then the allowed values:

  1. blank - Time
  2. "1" - Time - key date
  3. "2" - Time - factory calendar

If the first 2 Chars of the Strategy = "02" (Performance-Based Strategy) then allowed value:

  1.  "3" - Performance-based

PLAN_SORT

Sort field for maintenance plans

Mandatory.

Select from configuration (T399G)

Note: Group Maintenance Plans based on below design principal:
Frequency + Maintenance Activity
Each group (Sort Field) gets its own deadline monitoring variant.
Example: 
6M_INSP: Monthly Inspection

All Maintenance Plans of Inspection for 6M Inspection will be grouped with this Sort field.

POINT

Measuring Point

Conditional.

Must reference Measuring Point DCT.

Must not be blank if the first 2 Chars of the Strategy = "02" (Performance-Based Strategy)
Must be blank if the first 2 Chars of the Strategy <> " 02" (Performance-Based Strategy)

ENDDT_FOR_SCHED

End Date for Scheduling

Conditional.

All Date format should be DDMMYYYY.

Must be a date later than Start date (STADT).

Can be blank

2.Maintenance Plan Long Text Line Data Construction Rules

Field NameField DescriptionRule
zLegacyWARPLLegacy Maintenance Plan

Mandatory.

Key to link to Maintenance Plan

TDSPRASLanguage Key

Mandatory

Must be either one of the following: English(E) , French(F), Italian(I), Mandarin(1), Portuguese(including Brazilian Portuguese)(P), German(D) and Spanish(S)

WPTXT

Maintenance Plan Text

Mandatory.

Not editable

Note: This field is needed for clarity of Maintenance Plan

ROWCOUNT

Row number

Mandatory.

Must be unique and ascending sequential number

CLUSTD_LINE

Text Line

Mandatory

Free Text

3.Maintenance Item Data Construction Rules

Field NameField DescriptionRule
zLegacyWARPLLegacy Maintenance Plan

Mandatory.

Key to link to Maintenance Plan

zLegacyWAPOSLegacy Maintenance Item

Mandatory.

Key field

PSTXT

Item Short Text

Mandatory.

Free text.

Note: Description must be defined as Frequency + TOT + Asset Tag.

TPLNRFunctional Location

Mandatory.

Must reference Functional Location in Functional Location DCT.

Must not be blank if Equipment is blank.
CT of Functional Location must match Task List CT

EQUNREquipment Number

Conditional.

Must reference Equipment Number in Equipment DCT.

Must not be blank if Functional Location is blank.
CT of the Equipment must match Task List CT

GEWRKMain work center for maintenance tasks

Conditional.

Must reference Work Centre DCT.

Note: If blank, default to the Work Centre derived from Functional Location or Equipment

WPGRPMaintenance Planner Group

Conditional.

Select from configuration (T024I).

Default to the value derived from the technical object.

Update the value if provided by business (Takes Precedence).

PRIOKPriority

Mandatory.

Select from configuration (T356).

PLNNRKey for Task List Group

Mandatory.

Key for Task List Group + Group Counter: Should exist in Task List DCT

PLNALGroup Counter

Mandatory.

Key for Task List Group + Group Counter: Should exist in Task List DCT.

Task List CT shall be equal to the Technical Object CT.

APFKTExecution factor for whole task list

Conditional.

Note: Will default to to "1" if blank

ANLZUSystem Condition

Conditional.

Select from configuration (T357M) or can be blank

ILARTMaintenance Activity Type

Select from configuration (T353I)  

Note: The Maintenance Activity Type shall be updated based on the activities defined in the associated Task List of the Maintenance Item.

4.Maintenance Item Long Text Line Data Construction Rules

Field NameField DescriptionRule
zLegacyWARPLLegacy Maintenance Plan

Mandatory.

Key to link to Maintenance Plan

zLegacyWAPOSLegacy Maintenance Item

Mandatory.

Key to link to Maintenance Item

TDSPRASLanguage Key

Mandatory

Must be either one of the following: English(E) , French(F), Italian(I), Mandarin(1), Portuguese(including Brazilian Portuguese)(P), German(D) and Spanish(S)

KTEXT

Description

Mandatory.

Not editable

ROWCOUNT

Row number

Mandatory.

Must be unique and ascending sequential number

CLUSTD_LINE

Text Line

Mandatory

Free Text

5.Maintenance Item Object List Data Construction Rules

Field NameField DescriptionRule
zLegacyWARPLLegacy Maintenance Plan

Mandatory.

Key to link to Maintenance Plan

zLegacyWAPOSLegacy Maintenance Item

Mandatory.

Key field

SORTFObject list sort field

Conditional.

Must be unique and ascending sequential number starting from 1

EQUNREquipment Number

Conditional.

Must reference Equipment Number in Equipment DCT.

TPLNRFunctional Location

Conditional.

Must reference Functional Location in Functional Location DCT

6. Maintenance Plan Characteristic Data Construction Rules

Field NameField DescriptionRule
zLegacyWARPLLegacy Maintenance Plan

Mandatory.

Key to link to Maintenance Plan

ATNAMCharacteristic Name

Mandatory.

Possible selection: "Allowed CT", "Discrete to the Asset"

Characteristic Name and Class should exist in Characteristics DCT

ATWRT
Characteristic Value

Mandatory.

If ATNAM = "Allowed CT" then input relevant Construction Type.
Eg.: Assigned Construction Type must exist in Construction Type DCT

If ATNAM = "Discrete to the Asset" then select "YES" or "NO"

POSNRItem Number

Mandatory.

Positive numeric values only.

Must be unique and ascending sequential


Extraction Dependencies

List the steps that need to occur before extraction can commence

Item #Step DescriptionTeam Responsible
1Relevancy Criteria for EquipmentSyWay A2D Data Team
2Relevancy Criteria for Functional LocationSyWay A2D Data Team
3Relevancy Criteria for Task ListSyWay A2D Data Team
4Relevancy Criteria for Assembly / Construction TypeSyWay 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 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 DescriptionTeam Responsible
1

Obtain DCT Sign-off from Business

SyWay A2D Data Team

2

In dspMigrate, select the wave – S4/HANA – Plant Maintenance

Syniti

3

Go to Process Area Launch and Process the Object – Maintenance Plan and Item

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.Maintenance Plan Transformation Rule (ECC)

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1----S/4HANAMPLAWARPLMaintenance PlanSystem (Internal numbering)
2PF2, WP2MPLAWARPLMaintenance PlanSTAGINGMPLAzLegacyWARPLLegacy Maintenance PlanDirect mapping.
3----S/4HANAMPLAMPTYPMaintenance plan categoryDefault to "PM"
4PF2, WP2MPLASTRATMaintenance StrategyS/4HANAMPLASTRATMaintenance Strategy

Value Mapping: Maintenance Strategy

5----S/4HANAMPLAWPTXTMaintenance Plan TextDerive from assigned Task List Description
6----S/4HANAMPLAVSPOSShift Factor for Late Completion

Default to 0 if Time based Maintenance Plan.
Default to 100 if Performance based Maintenance Plan.

Refer to the Notes below for definition of Time-Based and Performance-Based Strategy

7PF2, WP2MPLATOPOSTolerance for Late Completion (%)S/4HANAMPLATOPOSTolerance for Late Completion (%)

Direct mapping.

If blank, default

to "10"
8----S/4HANAMPLAVSNEGShift Factor for Early Completion

Default to 0 if Time based Maintenance Plan.
Default to 100 if Performance based Maintenance Plan.

Refer to the Notes below for definition of Time-Based and Performance-Based Strategy

9PF2, WP2MPLATONEGTolerance for Early Completion (%)S/4HANAMPLATONEGTolerance for Early Completion (%)

Direct mapping.

If blank, default

to "10"

10PF2, WP2MPLASFAKTCycle modification factorS/4HANAMPLASFAKTCycle modification factor

Direct mapping.

If blank, default to "1" 

11PF2, WP2MPLAFABKLFactory calendar keyS/4HANAMPLAFABKLFactory calendar key

Direct mapping.

12PF2, WP2MPLAHORIZCall horizon for maintenance plan callsS/4HANAMPLAHORIZCall horizon for maintenance plan calls

Direct mapping.

If blank, default to "100"

13----S/4HANAMPLAHORIZ_QUALIFIER Calculation Type of Call Horizon

Default to "%"

14PF2, WP2MPLAABRHOScheduling PeriodS/4HANAMPLAABRHOScheduling Period

Direct mapping.

If blank, default to "3"

15PF2, WP2MPLAHUNITUnit for Scheduling periodS/4HANAMPLAHUNITUnit for Scheduling period

Direct mapping.

If blank, default to "YR"

16PF2, WP2MPLA

CALL_CONFIRM

Completion RequirementS/4HANAMPLA

CALL_CONFIRM

Completion Requirement

Direct mapping.

17PF2, WP2MPLA

STADT

Start dateS/4HANAMPLA

STADT    

Start date

Direct mapping.

18PF2, WP2MPLA

STICH

Scheduling indicatorS/4HANAMPLA

STICH

Scheduling indicator

Direct Mapping.

Default to "3" if Performance based Maintenance Plan.

Refer to the Notes below for definition of Time-Based and Performance-Based Strategy

19PF2, WP2MPLA

PLAN_SORT

Sort field for maintenance plans

S/4HANA

MPLA

PLAN_SORT

Sort field for maintenance plans

Value Mapping: Maintenance Plan Sort Field

20PF2, WP2MMPT

POINT

Measuring Point

S/4HANA

MPLA

POINT

Measuring Point

Value Mapping: Measuring Point

21PF2, WP2MPLA

ENDDT_FOR_SCHED

End Date for Scheduling

S/4HANA

MPLA

ENDDT_FOR_SCHED

End Date for Scheduling

Direct Mapping

Notes: 

  1. If first 2 characters of the Strategy <> "02" then Strategy is Time-Based 
  2. If first 2 characters of the Strategy = "02"  then Strategy is Performance-Based

2.Maintenance Plan Transformation Rule (DCT)

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1----S/4HANAMPLAWARPLMaintenance PlanSystem (Internal numbering)
2DCTMPLAzLegacyWARPLLegacy Maintenance PlanSTAGINGMPLAzLegacyWARPLLegacy Maintenance PlanDirect mapping.
3----S/4HANAMPLAMPTYPMaintenance plan categoryDefault to "PM"
4DCTMPLASTRATMaintenance StrategyS/4HANAMPLASTRATMaintenance Strategy

Direct mapping.

5----S/4HANAMPLAWPTXTMaintenance Plan TextDerive from assigned Task List Description
6----S/4HANAMPLAVSPOSShift Factor for Late Completion

Default to 0 if Time based Maintenance Plan.
Default to 100 if Performance based Maintenance Plan.

Refer to the Notes below for definition of Time-Based and Performance-Based Strategy

7DCTMPLATOPOSTolerance for Late Completion (%)S/4HANAMPLATOPOSTolerance for Late Completion (%)

Direct mapping.

If blank, default

to "10"
8----S/4HANAMPLAVSNEGShift Factor for Early Completion

Default to 0 if Time based Maintenance Plan.
Default to 100 if Performance based Maintenance Plan.

Refer to the Notes below for definition of Time-Based and Performance-Based Strategy

9DCTMPLATONEGTolerance for Early Completion (%)S/4HANAMPLATONEGTolerance for Early Completion (%)

Direct mapping.

If blank, default

to "10"

10DCTMPLASFAKTCycle modification factorS/4HANAMPLASFAKTCycle modification factor

Direct mapping.

If blank, default to "1" 

11DCTMPLAFABKLFactory calendar keyS/4HANAMPLAFABKLFactory calendar key

Direct mapping.

12DCTMPLAHORIZCall horizon for maintenance plan callsS/4HANAMPLAHORIZCall horizon for maintenance plan calls

Direct mapping.

If blank, default to "100"

13----S/4HANAMPLAHORIZ_QUALIFIER Calculation Type of Call Horizon

Default to "%"

14DCTMPLAABRHOScheduling PeriodS/4HANAMPLAABRHOScheduling Period

Direct mapping.

If blank, default to "3"

15DCTMPLAHUNITUnit for Scheduling periodS/4HANAMPLAHUNITUnit for Scheduling period

Direct mapping.

If blank, default to "YR"

16DCTMPLA

CALL_CONFIRM

Completion RequirementS/4HANAMPLA

CALL_CONFIRM

Completion Requirement

Direct mapping.

17DCTMPLA

STADT

Start dateS/4HANAMPLA

STADT    

Start date

Direct mapping.

18DCTMPLA

STICH

Scheduling indicatorS/4HANAMPLA

STICH

Scheduling indicator

Direct mapping.

19DCTMPLA

PLAN_SORT

Sort field for maintenance plans

S/4HANA

MPLA

PLAN_SORT

Sort field for maintenance plans

Direct Mapping

20DCTMMPT

POINT

Measuring Point

S/4HANA

MPLA

POINT

Measuring Point

Value Mapping: Measuring Point

21DCTMPLA

ENDDT_FOR_SCHED

End Date for Scheduling

S/4HANA

MPLA

ENDDT_FOR_SCHED

End Date for Scheduling

Direct Mapping

Notes: 

  1. If first 2 Characters of the Strategy <> " 02" then it is Time-Based Strategy
  2. If first 2 Characters of the Strategy = "02"  then it is Performance-Based Strategy

3.Maintenance Plan Long Text Header Transformation Rule (ECC)

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1----S/4HANA STXLTDOBJECTTexts: application objectDefault to "MPLA"
2PF2, WP2MPLAWARPLMaintenance PlanS/4HANASTXLTDNAMEName

Value Mapping: Maintenance Plan

3----S/4HANA STXL

TDID

Text IDDefault to "LTXT"
4PF2, WP2STXLSPRASLanguage KeyS/4HANA STXLSPRASLanguage KeyDirect Mapping

Note: Only the records marked as Cleansed in INC-Maintenance Plan Long Text will be migrated

4.Maintenance Plan Long Text Header Transformation Rule (DCT)

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1----S/4HANA STXLTDOBJECTTexts: application objectDefault to "MPLA"
2DCTMPLAzLegacyWARPLLegacy Maintenance PlanS/4HANASTXLTDNAMEName

Value Mapping: Maintenance Plan

3----S/4HANA STXL

TDID

Text IDDefault to "LTXT"
4DCTSTXLSPRASLanguage KeyS/4HANA STXLSPRASLanguage KeyDirect Mapping

5.Maintenance Plan Long Text Line Transformation Rule (ECC)

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1----S/4HANA STXLRELIDCHAR02 data element for SYSTDefault to "TX"
2----S/4HANA STXLTDOBJECTTexts: application objectDefault to "MPLA"
3PF2, WP2MPLAWARPLMaintenance PlanS/4HANASTXLTDNAMEName

Value Mapping: Maintenance Plan

4-----STXL

TDID

Text IDDefault to "LTXT"
5PF2, WP2STXLSPRASLanguage KeyS/4HANA STXLSPRASLanguage KeyDirect Mapping
6----S/4HANA STXLCLUSTD_TAGTag columnDefault to "*"
7PF2, WP2STXLROWCOUNT

Row number

S/4HANA STXLROWCOUNT

Row number

Direct Mapping
8PF2, WP2STXLCLUSTD_LINEText LineS/4HANA STXLCLUSTD_LINEText LineDirect Mapping

Note: Only the records marked as Cleansed in INC-Maintenance Item Long Text will be migrated

6.Maintenance Plan Long Text Line Transformation Rule (DCT)

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1----S/4HANA STXLRELIDCHAR02 data element for SYSTDefault to "TX"
2----S/4HANA STXLTDOBJECTTexts: application objectDefault to "MPLA"
3DCTMPLAzLegacyWARPLLegacy Maintenance PlanS/4HANASTXLTDNAMEName

Value Mapping: Maintenance Plan

4----S/4HANA STXL

TDID

Text IDDefault to "LTXT"
5DCTSTXLSPRASLanguage KeyS/4HANA STXLSPRASLanguage KeyDirect Mapping
6----S/4HANA STXLCLUSTD_TAGTag columnDefault to "*"
7DCTSTXLROWCOUNT

Row number

S/4HANA STXLROWCOUNT

Row number

Direct Mapping
8DCTSTXLCLUSTD_LINEText LineS/4HANA STXLCLUSTD_LINEText LineDirect Mapping

 7.Maintenance Item Transformation Rule (ECC)

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1----S/4HANAMPOSWAPOSMaintenance ItemSystem (Internal numbering)
2PF2, WP2MPOSWARPLMaintenance PlanSTAGINGMPLAzLegacyWARPLLegacy Maintenance PlanDirect mapping.
3PF2, WP2MPOSWAPOSMaintenance ItemSTAGINGMPLAzLegacyWAPOSMaintenance ItemDirect mapping
4PF2, WP2MPOS

PSTXT

Item Short Text

S/4HANA 

MPOS

PSTXT

Item Short Text

Direct mapping

5PF2, WP2MPOSTPLNRFunctional LocationS/4HANAMPOSTPLNRFunctional Location

Value Mapping: Functional Location

6PF2, WP2MPOSTPLNRFunctional LocationS/4HANAMPOSEQUNREquipment NumberValue Mapping: Functional Location where New Equipment is not blank
7PF2, WP2MPOSEQUNREquipment NumberS/4HANAMPOSEQUNREquipment NumberValue Mapping: Equipment Number
8ENRICHMENTENR-Maintenance Item AssemblyzLegacyBAUTLAssemblyS/4HANAMPOSEQUNREquipment NumberValue Mapping: Assembly and Construction Type
9PF2, WP2MPOSAUARTOrder TypeS/4HANAMPOSAUARTOrder Type

Default to "YA02"

10PF2, WP2MPOSGEWRK Main work center for maintenance tasks
MPOSGEWRK Main work center for maintenance tasks

Value Mapping: Work Centre

If blank then Default to the value derived from the technical object

11PF2, WP2MPOSPLNTYTask List TypeS/4HANA MPOSPLNTYTask List TypeValue Mapping: Task List Header
12PF2, WP2MPOSPLNNRKey for Task List Group

S/4HANA 

MPOSPLNNRKey for Task List GroupValue Mapping: Task List Header
13PF2, WP2MPOSPLNALGroup CounterS/4HANA MPOSPLNALGroup CounterValue Mapping: Task List Header
14PF2, WP2MPOSAPFKTExecution factor for whole task listS/4HANAMPOSAPFKTExecution factor for whole task list

Direct mapping.

If blank, default to "1" 

15PF2, WP2MPOSANLZUSystem ConditionS/4HANA MPOSANLZUSystem ConditionValue Mapping: System Condition
16PF2, WP2MPOSWPGRP

Maintenance Planner Group

S/4HANA MPOSWPGRP

Maintenance Planner Group

Value Mapping: Maintenance Planner Group

Default to the value derived from the technical object if blank

17PF2, WP2MPOSILARTMaintenance Activity TypeS/4HANA MPOSILARTMaintenance Activity Type

Value Mapping: Maintenance activity types

8.Maintenance Item Transformation Rule (DCT)

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1----S/4HANAMPOSWAPOSMaintenance ItemSystem (Internal numbering)
2DCTMPOSzLegacyWARPLLegacy Maintenance PlanSTAGINGMPLAzLegacyWARPLLegacy Maintenance PlanDirect mapping.
3DCTMPOSzLegacyWAPOSLegacy Maintenance ItemSTAGINGMPLAzLegacyWAPOSMaintenance ItemDirect mapping
4DCTMPOS

PSTXT

Item Short Text

S/4HANA 

MPOS

PSTXT

Item Short Text

Direct mapping

5DCTMPOSTPLNRFunctional LocationS/4HANAMPOSTPLNRFunctional Location

Value Mapping: Functional Location

6DCTMPOSEQUNREquipment NumberS/4HANAMPOSEQUNREquipment NumberValue Mapping: Equipment Number
7-----MPOSAUARTOrder TypeDefault to "YA02"
8DCTMPOSGEWRK Main work center for maintenance tasksS/4HANAMPOSGEWRK Main work center for maintenance tasks

Value Mapping: Work Centre

If blank then Default to the value derived from the technical object

9DCTMPOSPLNTYTask List TypeS/4HANA MPOSPLNTYTask List TypeValue Mapping: Task List Header
10DCTMPOSPLNNRKey for Task List Group

S/4HANA 

MPOSPLNNRKey for Task List GroupValue Mapping: Task List Header
11DCTMPOSPLNALGroup CounterS/4HANA MPOSPLNALGroup CounterValue Mapping: Task List Header
12DCTMPOSAPFKTExecution factor for whole task listS/4HANAMPOSAPFKTExecution factor for whole task list

Direct mapping.

If blank, default to "1" 

13DCTMPOSANLZUSystem ConditionS/4HANA MPOSANLZUSystem ConditionDirect mapping.
14DCTMPOSWPGRP

Maintenance Planner Group

S/4HANA MPOSWPGRP

Maintenance Planner Group

Update the value if provided by business.

Default to the value derived from the technical object if blank

15DCTMPOSILARTMaintenance Activity TypeS/4HANA MPOSILARTMaintenance Activity Type

Direct mapping

9.Maintenance Item Object List Transformation Rule (ECC)

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1-----OBJKOBKNRObject list numberSystem (Internal numbering)
2-----OBJKOBZAEObject list countersSystem (Internal numbering)
3-----OBJK

ILOAN

Location and account assignment for technical objectSystem (Internal numbering)
4PF2, WP2OBJKSORTFObject list sort fieldS/4HANAOBJKSORTFObject list sort fieldDirect mapping.
5PF2, WP2OBJKTPLNRFunctional LocationS/4HANAOBJKTPLNRFunctional LocationValue Mapping: Functional Location
6PF2, WP2OBJKEQUNREquipment NumberS/4HANAOBJKEQUNREquipment NumberValue Mapping: Equipment Number

10.Maintenance Item Object List Transformation Rule (DCT)

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1-----OBJKOBKNRObject list numberSystem (Internal numbering)
2-----OBJKOBZAEObject list countersSystem (Internal numbering)
3-----OBJK

ILOAN

Location and account assignment for technical objectSystem (Internal numbering)
4PF2, WP2OBJKSORTFObject list sort fieldS/4HANAOBJKSORTFObject list sort fieldDirect mapping.
5PF2, WP2OBJKTPLNRFunctional LocationS/4HANAOBJKTPLNRFunctional LocationValue Mapping: Functional Location
6PF2, WP2OBJKEQUNREquipment NumberS/4HANAOBJKEQUNREquipment NumberValue Mapping: Equipment Number

11.Maintenance Plan (Characteristics Values Header) (ECC)

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1----S/4HANAKLAHKLARTClass TypeDefault to "080"
2----S/4HANAINOB

OBTAB

Name of Database Table for ObjectDefault to "MPLA"
3----S/4HANAKLAHCLASSClass number

Default to "EAM_9999"

4----S/4HANAINOBOBJEKKey of ObjectDerive from Maintenance Plan Object Number
5----S/4HANAKLAHSTATUClass StatusDefault to "1"

12.Maintenance Plan (Characteristics Values Header) (DCT)

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1----S/4HANAKLAHKLARTClass TypeDefault to "080"
2----S/4HANAINOB

OBTAB

Name of Database Table for ObjectDefault to "MPLA"
3----S/4HANAKLAHCLASSClass number

Default to "EAM_9999"

4----S/4HANAINOBOBJEKKey of ObjectDerive from Maintenance Plan Object Number
5----S/4HANAKLAHSTATUClass StatusDefault to "1"

 13.Maintenance Plan (Characteristics Values Allocation) (ECC)

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1----S/4HANAMPLAWARPLMaintenance PlanSystem (Internal numbering)
2----S/4HANAKLAHKLARTClass TypeDefault to "018"
3----S/4HANAINOB

OBTAB

Name of Database Table for ObjectDefault to "MPLA"
4----S/4HANAKLAHCLASSClass number

Default to "EAM_9999"

5----S/4HANAINOBOBJEKKey of ObjectDerive from Maintenance Plan Object Number
6ENRICHMENTENR-Maintenance Plan Characteristic-Characteristic NameS/4HANACABNATNAMCharacteristic NameDirect Mapping
7ENRICHMENTENR-Maintenance Plan Characteristic-Characteristic ValueS/4HANAAUSPATWRTCharacteristic ValueDirect Mapping
8ENRICHMENTENR-Maintenance Plan Characteristic-Item NumberS/4HANAKSMLPOSNRItem NumberDirect Mapping

14.Maintenance Plan (Characteristics Values Allocation) (DCT)

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1----S/4HANAKLAHKLARTClass TypeDefault to "018"
2----S/4HANAINOB

OBTAB

Name of Database Table for ObjectDefault to "MPLA"
3----S/4HANAKLAHCLASSClass number

Default to "EAM_9999"

4----S/4HANAINOBOBJEKKey of ObjectDerive from Maintenance Plan Object Number
5DCTCABNATNAMCharacteristic NameS/4HANACABNATNAMCharacteristic NameDirect Mapping
6DCTAUSPATWRTCharacteristic ValueS/4HANAAUSPATWRTCharacteristic ValueDirect Mapping
7----S/4HANAKSMLPOSNRItem NumberGenerate sequence number starting with 1 by order the record is created for each Key of Object

15.Maintenance Plan (Default Characteristics Values Allocation - Regulatory) (ECC and DCT)

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1----S/4HANAKLAHKLARTClass TypeDefault to "018"
2----S/4HANAINOB

OBTAB

Name of Database Table for ObjectDefault to "MPLA"
3----S/4HANAKLAHCLASSClass number

Default to "EAM_9999"

4----S/4HANAINOBOBJEKKey of ObjectDerive from Maintenance Plan Object Number
5----S/4HANACABNATNAMCharacteristic NameDefault to "Regulatory"
6----S/4HANAAUSPATWRTCharacteristic ValueDerive from Task List Header "Regulatory" Characteristic Value
7----S/4HANAKSMLPOSNRItem NumberGenerate sequence number starting with 1 by order the record is created for each Key of Object

Note: Each Maintenance Plan can have only 1 Regulatory characteristic

16.Maintenance Plan (Default Characteristics Values Allocation - Nature of Work) (ECC and DCT)

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1----S/4HANAKLAHKLARTClass TypeDefault to "018"
2----S/4HANAINOB

OBTAB

Name of Database Table for ObjectDefault to "MPLA"
3----S/4HANAKLAHCLASSClass number

Default to "EAM_9999"

4----S/4HANAINOBOBJEKKey of ObjectDerive from Maintenance Plan Object Number
5----S/4HANACABNATNAMCharacteristic NameDefault to "Nature of Work"
6----S/4HANAAUSPATWRTCharacteristic ValueDerive from Task List Header "Nature of Work" Characteristic Value
7----S/4HANAKSMLPOSNRItem NumberGenerate sequence number starting with 1 by order the record is created for each Key of Object

Note: Each Maintenance Plan can have only 1 Nature of Work characteristic

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

Transformation Mapping

Use the exact name and reference this section in the “Transformation rules” above
Mapping Table NameMapping Table Description

Maintenance Plan

Old to new Maintenance Plan

Maintenance Item

Old to new Maintenance Item

Maintenance Strategy

Old to new Maintenance Strategy

Functional Location

Old to new Functional Location

Equipment Number

Old to new Equipment Number

Material Number

Old to new Material Number

Task List Header

Old to new Task List Header

Measuring Point

Old to new Measuring Point

Work Centre

Old to new Work Centre

Assembly and Construction Type

Mapping of legacy Assembly / Construction Type to new Assembly / Construction Type

Maintenance Plan Sort Field

Old to new Maintenance Plan Sort Field

Priority

Old to new Priority

Order Type

Old to new Order Type

System Condition

Old to new System Condition

Maintenance Planner Group

Old to new Maintenance Planner Group

ENR-Maintenance Item Assembly

Enrichment to assign Assembly to Functional Location or Equipment

INC-Maintenance Plan Long Text

Maintenance Plan Long Text inclusion list

INC-Maintenance Item Long Text

Maintenance Item Long Text inclusion list

ENR-Maintenance Plan Characteristic

Enrichment to assign characteristics to Maintenance Plan

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

The following pre-load validations will be performed by the Project Team.

Completeness

TaskAction

Verify Record Count

SyWay A2D Data Team to verify that the total number of relevant records from legacy systems and DCTs (if any) is equal to the total number of records in the Preload and Load Sheets.

Verify Data Integrity

SyWay A2D Data Team to verify that the total number of Operations per Work Oder header extracted from legacy systems and DCTs (if any) should be equal to the total number of operations identified 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 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

TaskAction

Verify Record Count

Business Data Owner/s to verify that the total number of relevant records from legacy systems and DCTs (if any) is equal to the total number of records in the Preload and Load Sheets.


Accuracy

TaskAction

Conversion Accuracy

Business Data Owner/s 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


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

Configuration

List the Configurations required before loading can commence

Item #Configuration Item
1

T399W-Maintenance Plan Category

2

T024A-Planner Groups

3

T356-Priority

4

T003O-Order Type

5

T399G-Maintenance Plan Sort Field

6

TFACD-Factory Calendar Definition

7

T353I-Maintenance activity types

Conversion Objects

Object #Preceding Object Conversion Approach

1002

Equipment

1003

Functional Location

1005

Task List 

1006

Work Centre

1009

Class

1012

Measuring Point

1015

Characteristic

1017

Maintenance Strategy

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 TypeError DescriptionAction Taken

Configuration

Invalid Maintenance Plan Category

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

Configuration

Invalid Planner Group

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

Configuration

Invalid Plant

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

Configuration

Invalid Planning Plant

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

Configuration

Invalid System Condition

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

Configuration

Invalid Maintenance Activity Type

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

Configuration

Invalid Priority

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

Configuration

Invalid Order Type

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

Invalid Data

Invalid Maintenance Strategy

Expedite whether the master data is changed in the system

Invalid Data

Invalid Work Centre

Expedite whether the master data is changed in the system

Invalid Data

Invalid Task List

Expedite whether the master data is changed in the system

Invalid Data

Invalid Functional Location

Expedite whether the master data is changed in the system

Invalid Data

Invalid Equipment

Expedite whether the master data is changed in the system


Post-Load Validation

Project Team

The following post-load validations will be performed by the 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

Verify that the Maintenance plan 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

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 Maintenance plan 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.
  • Not all legacy Maintenance Plan and Item need to be mapped to S/4 HANA Maintenance Plan and Item. If any of the successor objects is dependent on a Maintenance Plan and Item field with no mapped values, this will be an enrichment activity or manual transformation for the successor object to derive the Maintenance Plan and Item.


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