Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.

A Maintenance Strategy for an asset is established based on the Asset Management Plan, which outlines how the asset will be maintained throughout its lifecycle.
Syensqo defines both Preventive and Reactive Work Maintenance Strategies using a Maintenance Plans. 

A Maintenance Item is an Integrated master data object created with the Maintenance plan, These Maintenance Items are used to update technical object that requires maintenance, along with its associated Task List.
Maintenance Plans for Syensqo are defined with the Purpose of:

  • Preventive Plans - Used for Time Based and Condition based Preventive Maintenance with a defined Strategy
  • Shutdown Plans - Shutdown Plans with a Defined Strategy

Maintenance Plans and Items are TIER 3 Governed objects


Conversion Scope

The scope of this document covers the approach for converting 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 proactive maintenance tasks.

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 proactive schedule maintenance calls (notifications/orders)
- Linked to a planning plant, which controls scheduling

A A Maintenance Item specifies the actual taskresponsibilities, technical object and a task list to be performed. It defines:
- The equipment, functional location, or object list to be maintained
- The planner group and activity types
- 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 proactive 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
    • Type (PLKO-PLNTY
    , PLKO-PLNNR, PLKO-PLNAL)
    • ) can be any of: A - General Maintenance Task List; E - Equipment Task List; T - Task List for Functional Location
    • Task List Status (PLKO-STATU) can be any of: 2 - Released for Order; 3 - Released for Costing; 4 - Released (General)
    • Task List Usage (PLKO-VERWE) = "004"
  3. Maintenance Items (MPOS-WAPOS) that has at least 1 relevant Assembly (MARA-MATNR), active
    •  legacy Functional Location (IFLOT-TPLNR) - Source System Status (JEST-STAT) not (INAC or DLFL)  and </Start CR0438> (JEST-INAC <> 'X')  </End CR0438>OR
    •  legacy Equipment (EQUI-EQUNR)
    in reference object or Item in object list based on Assembly (MARA-MATNR), Functional Location (IFLOT-TPLNR) or Equipment (EQUI-EQUNR) relevancy
    • Source System Status (JEST-STAT) not (INAC or ESTO or AVLB) and </Start CR0438>(JEST-INAC <> 'X')  </End CR0438>
  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 Items assigned to assembly (MPOS-BAUTL) with no Functional Location or Equipment assigned will added to DCT as an equipment/sub-equipment by business.

The data from legacy system excludes:

  1. Maintenance Plan with delete system status </Start CR0438> (System Status TJ02T-TXT04 JEST-STAT = DLFL) and  (JEST-INAC <> 'X')  </End CR0438> Maintenance Plan (MPLA-WARPL) marked inactive (MPLA-LVORM) = 'X'
  2. Maintenance Items (MPOS-WAPOS) that are not assigned to Maintenance Plan (MPLA-WARPL)
  3. Maintenance Items assigned to assembly (MPOS-BAUTL) with no Functional Location or Equipment assigned will be excluded from ECC transformation

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

TPLNRFunctional Location
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 PeriodUNIT3ConditionalMandatory
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
RMIPMSTTAGMP_STTAGKey DateDATS8System
MPLAENDDT_FOR_SCHEDEAM_MPLAENDDT_FOR_SCHEDEAM_ENDDT_FOR_SCHEDEnd Date for SchedulingDATS8Conditional
RMIPM
POINT
TPLNR
IMRC_POINTMeasuring PointCHAR
30Mandatory
RMIPMEQUNREQUNREquipment NumberCHAR18Conditional
MPLALTKNZMPLTXLong Text IndicatorCHAR1System
RMIPMGEWRKGEWRKMain work Centre for maintenance tasksCHAR8Conditional
RMIPMWERGWWERGWPlant associated with Main Work Centre CHAR4System
12Conditional

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_LINETXLINETDLINE

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. Cycle definitions and Measing Points for Maintenance PlanMaintenance Item

TableFieldData ElementField DescriptionData TypeLengthRequirement
MMPT
MPLAWARPLWARPLMaintenance PlanCHAR12

System

Link to MPLA

MMPT
MPOS
NUMMER
WAPOS
DZAEHLERCounter in Control TablesNUMC
WAPOSMaintenance itemCHAR16
2

System

MMPTMMPT-PAK_TEXTTXZYKLUSText for maintenance package/cycle (time/performance)

Key field

MPOSPSTXTPOSTXTItem Short TextCHAR
30
40
System
Mandatory
MMPT
MPOS
POINT
AUART
IMRC_POINTMeasuring Point
AUFARTOrder TypeCHAR
12
4
Conditional
Mandatory
MMPT
MPOS
MMPT-ZYKL1DZYK_ZEITMaintenance cycleFLTP16(16)SystemMMPTMMPT-ZEIEHDZEIEHUnit for the performance of maintenance tasksUNIT3System

5.Maintenance Item

TableFieldData ElementField DescriptionData TypeLengthRequirementMPLAWARPLWARPLMaintenance PlanCHAR12SystemMPOSWAPOSWAPOSMaintenance itemCHAR16SystemMPOSWSTRASTRATMaintenance StrategyCHAR6MandatoryMPOSPSTXTPOSTXTItem Short TextCHAR40MandatoryMPOSIWERKIWERKMaintenance Planning PlantCHAR4SystemMPOSAUARTAUFARTOrder TypeCHAR4MandatoryMPOSPRIOKPRIOKPriorityCHAR1MandatoryMPOSPLNTYPLNTYTask List TypeCHAR1MandatoryMPOSPLNNRPLNNRKey for Task List GroupCHAR8MandatoryMPOSPLNALPLNALGroup CounterCHAR2MandatoryMPOSWPGRPINGRPMaintenance Planner GroupCHAR3ConditionalMPOSAPFKTAPFKTExecution factor for whole task listDEC3(0)ConditionalMPOSANLZUANLZUSystem ConditionCHAR1ConditionalMPOS

ILART

ILAMaintenance activity typeCHAR3MandatoryRMIPM

TPLNR

TPLNRFunctional LocationCHAR30MandatoryRMIPM

EQUNR

EQUNREquipment NumberCHAR18Conditional
PRIOKPRIOKPriorityCHAR1Mandatory
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
MPOS

IWERK

IWERKMaintenance Planning PlantCHAR4System
RMIPMGEWRKGEWRKMain work Centre for maintenance tasksCHAR8Conditional
RMIPMWERGWWERGWPlant associated with main work centerCHAR4System

Note: Each Maintenance 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

TDOBJECT
TableFieldData ElementField DescriptionData TypeLengthRequirement
STXL
RELIDSYCHAR02CHAR02 data element for SYSTCHAR2

Mandatory

Key field

STXLTDOBJECTTDOBJECTTexts: application TDOBJECTTexts: 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_LINETXLINETDLINE

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

Link to MPOS

OBJKOBKNROBJKNRObject list numberINT819

System

Key field

OBJKOBZAEOBJZAObject list countersINT410

System

Key field

OBJKSORTFWARPLOBSORTObject list sort fieldCHAR20Conditional
OBJKTPLNRTPLNRFunctional LocationCHAR30Conditional
OBJKEQUNREQUNREquipment NumberCHAR18Conditional

Note: Each Maintenance Item can have multiple Objects or no Object at all. Not applicable if both Functional Location and Equipment Number are blank.

8.Maintenance Plan (Characteristics Values Header)

TableFieldData ElementField DescriptionData TypeLengthRequirement
MPLAWARPLWARPLMaintenance PlanCHAR12

Link to MPLA

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

Link to MPLA

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

ItemOrder Type: Not "YA02"Maintenance Plan, Plant, Order TypeScheduling Indicator: Not blank, 1, 2 or 3Scheduling Indicator not blank, 1, 2 or 3 Plant, Scheduling IndicatorMaintenance Plan, Plant, Maintenance Item, AssemblyMaintenance Item, Plant, AssemblyMaintenance Plan, Plant, Technical Object, Task List, Strategy, Description 
IDCriticalityError Message/Report DescriptionRuleOutputSource System

1016-001

C1 C3

Info Report: Maintenance Plan-Maintenance Item: Invalid, Inactive or no maintenance item

Maintenance Plan as per Relevancy Criteria assigned with inactive or no Maintenance Items attached. 

Item: Assigned Equipment is not Active. These Maintenance Items are not relevant for migration.

Maintenance Plan with Maintenance Item assigned with an Equipment  that belong to the criteria below:

  • Equipment (Source System Status (JEST-STAT) and </Start CR0438> (JEST-INAC <> 'X')  </End CR0438> is any of these: INAC ESTO AVLB)

Maintenance Plan, Description, Maintenance Item, Item Short Text, Plant, Equipment Maintenance Plan, Plant,  Maintenance Item,  

PF2, WP2

1016-002

C1C3

Maintenance Plan-Description: Missing Description

Maintenance Plan Description is blank

Info Report: Maintenance Item: Assigned Functional Location is not Active. These Maintenance Items are not relevant for migration.

Maintenance Plan with Maintenance Item assigned with a Functional Location belong to the criteria below:

  • Functional Location (Source System Status (JEST-STAT) and </Start CR0438> (JEST-INAC <> 'X')  </End CR0438> is any of these: INAC DLFL)

Maintenance Plan, Description, Maintenance Item, Item Short Text, Plant, Functional LocationMaintenance Plan, Plant,   Description 

PF2, WP2

1016-003

C1C3

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

Info Report: Maintenance Item: Assigned Task List is not Active. These Maintenance Items are not relevant for migration.

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

  • Task List Type (PLKO-PLNTY) can be any of: A - General Maintenance Task List; E - Equipment Task List; T - Task List for Functional Location
  • Task List Status (PLKO-STATU) can be any of: 2 - Released for Order; 3 - Released for Costing; 4 - Released (General)
  • Task List Usage (PLKO-VERWE) = "004"

Maintenance Plan, Description, Maintenance Item, Item Short Text, Maintenance Plan, Plant, Task List 

PF2, WP2

1016-004

C1 C2

Maintenance Plan-Work Centre: Invalid, Inactive or no Work Centre assigned

Maintenance Item assigned with invalid or inactive Work Centre 

: 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 Plan, Description, Maintenance Item, Item Short Text, Plant, Functional Location, EquipmentMaintenance Plan, Plant, Work Centre 

PF2, WP2

1016-005

C1 

Maintenance PlanItem-Maintenance Strategy: Invalid, Inactive or no Maintenance Strategy assignedPriority: is blank

Maintenance Plan and Items as per Relevancy Criteria assigned with a Maintenance Strategy which does not belong below:
1. Maintenance Strategy as per Relevancy Criteria where the Priority is blank

Maintenance Plan, PlantDescription, Maintenance Strategy Item, Item Short Text, Plant, Priority

PF2, PF2, WP2

1016-006 C1

C1

Maintenance

Plan-

Sort field: is blank

Maintenance Plan and Items as per Relevancy Criteria where the Sort field is blank

Maintenance Plan, Description, Maintenance Item, Item Short Text, Plant, Sort field

 Order Type not "YA02"

PF2, WP2

1016-007C1

C2

Maintenance Plan-

Description: Informally deleted

Maintenance Plan and Items as per Relevancy Criteria where Description contains:

  1. DELETE
  2. DEL

Maintenance Plan,

Description

PF2, WP2

1016-008

C1C3

Info Report: Maintenance Plan-Measuring Point : Invalid or inactive Measuring Point linked to  

Maintenance Plan assigned with invalid or inactive Measuring Point

Maintenance Plan, Plant, Measuring Point 

PF2, WP2

1016-009

C1 

Maintenance Plan: Item is assigned to Assembly

Maintenance Plan linked to Item assigned to Assembly

: Long Text for cleansing

 Long Text for Manual Review.

Note: This is used to create Inclusion-Maintenance Plan Long Text Business will then select which Long Text are still relevant from Inclusion-Maintenance Plan Long Text.

Maintenance Plan, Description, Maintenance Plant, Language Key, Rownum, Long Text

PF2, WP2

1016-010009C1C3Info Report: Maintenance Item: Assigned to Assembly

Maintenance Item assigned to Assembly

Long Text for cleansing

 Long Text for Manual Review.

Note: This is used to create Inclusion-Maintenance Item Long Text Business will then select which Long Text are still relevant from Inclusion-Maintenance Item Long Text.

Maintenance Item, Description, Maintenance Plant, Language Key, Rownum, Long TextPF2, WP2
1016-011010

C1 

Maintenance Item: Duplicate Maintenance Plan Items by Technical Object, Task List, Strategy, Description 

Maintenance Plan Items as per Relevancy Criteria where there is more than one Technical Object + Task List + Strategy + Description Combination. 

C2

Maintenance Items assigned to assembly only

Maintenance Items assigned to assembly with no Functional Location or Equipment assigned.

Note: This is a list of Maintenance Items for business to create in DCT as enrichment activity.

Maintenance Item, Description, PlantPF2, WP2
1016-012011C1

Maintenance Item-Maintenance Plan: Invalid, inactive or no Maintenance Plans linked

Maintenance Item as per Relevancy Criteria assigned with blank or inactive Maintenance Plan attached. 

Maintenance Item, Plant, Maintenance Plan 

PF2, WP2

1016-013

C1

Maintenance Item-Planning Plant: Planning Plant and Maintenance Plant are not the sameMaintenance Item as per Relevancy Criteria with Planning Plant <> Maintenance PlantMaintenance Item, Plant, Planning Plant

PF2, WP2

Not Applicable

External Cleansing Report: Maintenance Plan not in SAP

Business to create the Maintenance Plans 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 Applicable

PF2, WP2

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

Image Modified

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

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

WSTRASTRAT

Maintenance strategy

Mandatory.

Must reference to active Strategy 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

FBKLFABKL

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

ConditionalMandatory.

Note: Will default to "YR" if blank

CALL_CONFIRM

Completion Requirement

Conditional.

Allowed values:

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

STADT

Start date

Conditional.

All Date format should be DDMMYYYY

STICH

Scheduling indicator

Conditional.

Allowed values: "1", "2" or blank

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

PLAN_SORT

Sort field for maintenance plans

Mandatory.

Select from configuration (T399G)

Note: Groups 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 to active Measuring Point from Source or in 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.

Can be blank

Note: End Date must always be later than Start date

CHAR_DISCRETE_TO_ASSET

Discrete to the Asset Characteristic

Mandatory.

Allowed values: "YES" or "NO"

Note: Will default to "NO" in left 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_LINETXLINE

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 to active category "A" Functional Location with a CT in Active Functional Location from Source or in Functional Location DCTDCT.

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

EQUNREquipment Number

Conditional.

Must reference to active Equipment Number from Source or in in Equipment DCT.

Can be Blank only if FLOC is updated.
Valid Entry if Must not be blank if Functional Location is blank.
CT of the Equipment = must match Task List CT

IWERKPlanning Plant

Mandatory.

Must reference Value Mapping: Plant (Maintenance Plant = Yes)

GEWRKMain work center for maintenance tasks

Conditional.

Must reference Work Centre DCT.

Note: Will If blank, default to to the value Work Centre derived from the technical object, if blankEquipment. If Equipment is blank then default to the Work Centre derived from Functional Location.

WERGWPlant associated with main work center

Mandatory.

Must reference Value Mapping: Plant (Maintenance Plant = Yes)

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)Note: If blank, default to Planner Group derived from Equipment. If Equipment is blank then default to Planner Group derived from Functional Location.

PRIOKPriority

Mandatory.

Select from configuration (T356).

PLNTYPLNNRKey for Task List TypeGroup

Mandatory.

Must reference to active Key for Task List TypeGroup + Group Counter: Should exist in Task List Header  DCT.

PLNNRKey for Task List Group

Mandatory.

Must reference to active Key for Task List Group in Task List Header DCTTask List CT must be the same as the Technical Object CT.
All Maintenance Items under the same Maintenance Plan must be assigned to the same Task List

PLNALGroup Counter

Mandatory.

Must reference to active Group Counter in Task List Header DCT.

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

Task List CT must be the same as Group - Group Counter CT shall be equal to the Technical Object CT.
All Maintenance Items under the same Maintenance Plan must be assigned to the same Task List

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 by the business 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_LINETXLINE

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

SORTFzOBZAEObject list counters

Mandatory.

Key field

SORTFObject list sort field

Conditional.

Must be unique and ascending sequential number starting from 1

EQUNREquipment Number

Conditional.

Must reference to active Equipment Number (EQUI)Can be Blank only if FLOC is updated.
Valid Entry if CT of the Equipment = Task List CT
Equipment Number in Equipment DCT.

TPLNRFunctional Location

MandatoryConditional.

Must reference to active category "A" Functional Location in Functional with a CT in Functional Location DCT

6.Inclusion-Maintenance Plan Characteristic Long Text Data Construction Rules

Characteristic Name

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

Characteristic Name and Class should exist in Characteristics DCT

Field NameField DescriptionRule
zLegacyWARPLLegacy Maintenance Plan

Mandatory.

Key to link to Maintenance Plan

ATNAM
zLegacySPRASLegacy Language Key

Mandatory.

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

Item #Step DescriptionTeam Responsible1Relevancy Criteria for EquipmentSyWay A2D Data Team2Relevancy Criteria for Functional LocationSyWay A2D Data Team3Relevancy Criteria for Task ListSyWay A2D Data Team4Relevancy Criteria for Assembly / Construction TypeSyWay A2D Data Team

Allowed values:
1. "E" - English
2. "F" - French
3. "1" - Mandarin/Simplified Chinese
4. "I' - Italian
5. "P" - Portuguese/Brazilian
6. "D" - German
7. "S" - Spanish

zLegacyWERKSLegacy Plant

Mandatory

Note: Only Long Texts that are this list will be migrated.

7.Inclusion-Maintenance Item Long Text Data Construction Rules

Field NameField DescriptionRule
zLegacyWAPOSLegacy Maintenance Plan

Mandatory.

Key to link to Maintenance Item

zLegacySPRASLegacy Language Key

Mandatory.

Allowed values:
1. "E" - English
2. "F" - French
3. "1" - Mandarin/Simplified Chinese
4. "I' - Italian
5. "P" - Portuguese/Brazilian
6. "D" - German
7. "S" - Spanish

zLegacyWERKSLegacy Plant

Mandatory

Note: Only Long Texts that are this list will be migrated.

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

Extraction Dependencies

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


Transformation

The

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 Responsible1

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

    1. the rules defined in
  1. 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
1PF2, WP2MPLAWARPLMaintenance PlanS/4HANAMPLAWARPLMaintenance PlanSystem (Internal numbering)
2----S/4HANAMPLAMPTYPMaintenance plan categoryDefault to "PM"
3PF2, WP2MPLASTRATMaintenance StrategyS/4HANAMPLASTRATMaintenance Strategy

Value Mapping: Maintenance Strategy

4PF2, WP2PLKOKTEXTDescriptionS/4HANAMPLAWPTXTMaintenance Plan TextDirect mapping
5

Transformation Rules

1.Maintenance Plan Transformation Rule (ECC)

1

If blank, default to "1" 

Completion Requirement
Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
----S/4HANAMPLA
WARPLMaintenance PlanSystem (Internal numbering)
VSPOSShift 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

62PF2, WP2MPLAWARPLMaintenance PlanTOPOSTolerance for Late Completion (%)S/4HANASTAGINGMPLAzLegacyWARPLTOPOSTolerance for Late Completion (%)Legacy Maintenance Plan

Direct mapping.

If blank, default

to "10"
73----S/4HANAMPLAMPTYPMaintenance plan categoryDefault to "PM"VSNEGShift 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

84PF2, WP2MPLAWSTRATONEGTolerance for Early Completion (%)Maintenance StrategyS/4HANAMPLAWSTRAMaintenance Strategy

Value Mapping: Maintenance Strategy

TONEGTolerance for Early Completion (%)

Direct mapping.

If blank, default

to "10"

9PF2, WP2MPLASFAKTCycle modification factor5----S/4HANAMPLASFAKTWPTXTMaintenance Plan TextDerive from assigned Task List Description6---Cycle modification factor

Direct mapping.

If blank, default to "1" 

10PF2, WP2MPLAFABKLFactory calendar key-S/4HANAMPLAFABKLFactory calendar key

If STICH = "1" or "2" then Value Mapping: Factory Calendar Definition, otherwise default to blank

11VSPOSShift Factor for Late Completion

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

Note: Check DD-FUN-050 Master Data Standard_1017-Maintenance Strategy to differentiate between Time based and Performance based

7PF2, WP2MPLATOPOSHORIZTolerance for Late Completion (%)Call horizon for maintenance plan callsS/4HANAMPLATOPOSHORIZTolerance for Late Completion (%)Call horizon for maintenance plan calls

Direct mapping.

If blank, default to "

10

100"

812----S/4HANAMPLAVSNEGShift Factor for Early Completion

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

Note: Check DD-FUN-050 Master Data Standard_1017-Maintenance Strategy to differentiate between Time based and Performance based

HORIZ_QUALIFIER Calculation Type of Call Horizon

Default to "%"

13PF2, WP2MPLAABRHOScheduling PeriodS/4HANAMPLAABRHOScheduling Period

Direct mapping.

If blank, default to "3"

149PF2, WP2MPLATONEGHUNITTolerance for Early Completion (%)Unit for Scheduling periodS/4HANAMPLATONEGHUNITTolerance for Early Completion (%)Unit for Scheduling period

Direct mapping.

If blank, default to "10YR"

1015PF2, WP2MPLASFAKT

CALL_CONFIRM

Completion RequirementCycle modification factorS/4HANAMPLASFAKT

CALL_CONFIRM

Completion RequirementCycle modification factor

Direct mapping.

16PF2, WP2MPLA

STADT

Start dateS/4HANAMPLA

STADT    

Start date

Default to blank

1711PF2, WP2MPLAFABKL

STICH

Scheduling indicatorFactory calendar keyS/4HANAMPLAFABKLFactory calendar key

Direct mapping.

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

1812PF2, WP2MPLAHORIZ

PLAN_SORT

Sort field Call horizon for maintenance plan callsplans

S/4HANA

MPLAHORIZCall horizon for maintenance plan calls

Direct mapping.

If blank, default to "100"

PLAN_SORT

Sort field for maintenance plans

Value Mapping: Maintenance Plan Sort Field

19PF2, WP2RMIPM

POINT

Measuring Point13----

S/4HANA

MPLARMIPMHORIZ_QUALIFIER Calculation Type of Call Horizon

Default to "%"

POINT

Measuring Point

Value Mapping: Measuring Point

2014PF2, WP2MPLAABRHO

ENDDT_FOR_SCHED

End Date for SchedulingScheduling Period

S/4HANA

MPLAABRHOScheduling 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

ENDDT_FOR_SCHED

End Date for Scheduling

Direct Mapping

Notes: 

  1. If STICH = blank, 1 or 2 then Strategy is Time-Based 
  2. If STICH 3 then Strategy is Performance-Based

2.Maintenance Plan Transformation Rule (DCT)

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTMPLAzLegacyWARPLLegacy Maintenance PlanS/4HANAMPLA

CALL_CONFIRM

Completion Requirement

Direct mapping.
Default blank if Equipment is not blank

WARPLMaintenance PlanSystem (Internal numbering)
2----
17PF2, WP2MPLA

STADT

Start date
S/4HANAMPLA

STADT    

Start date

Direct mapping.

18
MPTYPMaintenance plan categoryDefault to "PM"
3DCT
PF2, WP2
MPLA
STICH
STRAT
Scheduling indicator
Maintenance StrategyS/4HANAMPLA

STICH

Scheduling indicator

Direct Mapping.

Default to "3" if Performance based Maintenance Plan.

Note: Check Maintenance Strategy design to differentiate between Time based and Performance based

STRATMaintenance Strategy

Direct mapping.

4----
19PF2, WP2MPLA

PLAN_SORT

Sort field for maintenance plans
S/4HANAMPLA

PLAN_SORT

Sort field for maintenance plans

Value Mapping: Maintenance Plan Sort Field

WPTXTMaintenance Plan TextDerive from assigned Task List Header Description
5----
20PF2, WP2MMPT

POINT

Measuring Point
S/4HANAMPLA

POINT

Measuring Point

Value Mapping: Measuring Point

VSPOSShift 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

6DCTMPLATOPOSTolerance for Late Completion (%)
21PF2, WP2MPLA

ENDDT_FOR_SCHED

End Date for Scheduling
S/4HANAMPLA

ENDDT_FOR_SCHED

End Date for Scheduling

Direct Mapping

2.Maintenance Plan Transformation Rule (DCT)

13
TOPOSTolerance for Late Completion (%)

Direct mapping.

If blank, default

to "10"
7----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

8DCTMPLATONEGTolerance for Early Completion (%)
Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1----S/4HANAMPLAWARPLMaintenance PlanSystem (Internal numbering)TONEGTolerance for Early Completion (%)

Direct mapping.

If blank, default

to "10"

92DCTMPLAzLegacyWARPLLegacy Maintenance PlanSFAKTCycle modification factorS/4HANASTAGINGMPLAzLegacyWARPLSFAKTCycle modification factorLegacy Maintenance Plan

Direct mapping.

If blank, default to "1" 

10DCTMPLAFABKLFactory calendar key3----S/4HANAMPLAMPTYPMaintenance plan categoryDefault to "PM"FABKLFactory calendar key

Direct mapping.

114DCTMPLAWSTRAHORIZCall horizon for maintenance plan callsMaintenance StrategyS/4HANAMPLAWSTRAHORIZCall horizon for maintenance plan callsMaintenance Strategy

Direct mapping.

If blank, default to "100"

125----S/4HANAMPLAWPTXTMaintenance Plan TextDerive from assigned Task List Description6-HORIZ_QUALIFIER Calculation Type of Call Horizon

Default to "%"

13DCTMPLAABRHOScheduling Period---S/4HANAMPLAVSPOSShift Factor for Late Completion

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

Note: Check Maintenance Strategy design to differentiate between Time based and Performance based

ABRHOScheduling Period

Direct mapping.

If blank, default to "3"

147DCTMPLATOPOSHUNITTolerance for Late Completion (%)Unit for Scheduling periodS/4HANAMPLATOPOSHUNITTolerance for Late Completion (%)Unit for Scheduling period

Direct mapping.

If blank, default to "

10

YR"

815-DCT-MPLA-

CALL_CONFIRM

Completion Requirement-S/4HANAMPLAVSNEGShift Factor for Early Completion

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

Note: Check Maintenance Strategy design to differentiate between Time based and Performance based

CALL_CONFIRM

Completion Requirement

Direct mapping.

16DCTMPLA

STADT

Start dateS/4HANAMPLA

STADT    

Start date

Direct mapping.

179DCTMPLATONEG

STICH

Scheduling indicatorTolerance for Early Completion (%)S/4HANAMPLATONEG

STICH

Scheduling indicatorTolerance for Early Completion (%)

Direct mapping.

If blank, default

to "10"

1018DCTMPLASFAKT

PLAN_SORT

Sort field for maintenance plansCycle modification factor

S/4HANA

MPLASFAKTCycle modification factor

Direct mapping.

If blank, default to "1" 

PLAN_SORT

Sort field for maintenance plans

Direct Mapping

19DCTRMIPM

POINT

Measuring Point

S/4HANA

RMIPM

POINT

Measuring Point

Value Mapping: Measuring Point

2011DCTMPLAFABKL

ENDDT_FOR_SCHED

End Date for SchedulingFactory calendar key

S/4HANA

MPLAFABKLFactory calendar key

Direct mapping.

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

Direct mapping.

If blank, default to "100"

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
4HANA 
MPLA
STXL
HORIZ_QUALIFIER Calculation Type of Call Horizon

Default to "%"

14DCTMPLAABRHOScheduling Period
TDOBJECTTexts: application objectDefault to "MPLA"
2PF2, WP2MPLAWARPLMaintenance PlanS/4HANA
MPLA
STXL
ABRHO
TDNAME
Scheduling 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.
Default blank if Equipment is not blank

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

Name

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 3.Maintenance Plan Long Text Header 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"
2
3PF2, WP2MPLAWARPLMaintenance PlanS/4HANASTXLTDNAMEName

Value Mapping: Maintenance Plan

3
4----
S/4HANA 
-STXL

TDID

Text IDDefault to
'
"LTXT
'
"
4
5PF2, WP2
STXLSPRASLanguage 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)

STXLSPRASLanguage KeyS/4HANA STXLSPRASLanguage KeyDirect Mapping
6
Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic1
----S/4HANA STXL
TDOBJECTTexts: application object
CLUSTD_TAGTag columnDefault to "
MPLA
*"
2
7
DCT
PF2, WP2
MPLA
STXL
zLegacyWARPLLegacy Maintenance Plan
ROWCOUNT

Row number

S/
4HANA
4HANA STXL
TDNAME
ROWCOUNT
Name

Row number

Value
Direct Mapping
: Maintenance Plan
3
8
-
PF2, WP2
-
STXL
-
TXLINE
-
Text LineS/4HANA STXL
TDID
TXLINEText
IDDefault to 'LTXT'4DCTSTXLSPRASLanguage KeyS/4HANA STXLSPRASLanguage KeyDirect Mapping
LineDirect Mapping

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

65.Maintenance Plan Long Text Line Transformation Rule (ECCDCT)

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

Value Mapping: Maintenance Plan

3----STXL

TDID

Text IDDefault to 'LTXT'
RELIDCHAR02 data element for SYSTDefault to "TX"
2
4PF2, WP2STXLSPRASLanguage KeyS/4HANA STXLSPRASLanguage KeyDirect Mapping5
----S/4HANA STXL
CLUSTD_TAGTag column
TDOBJECTTexts: application objectDefault to "
*
MPLA"
6
3
PF2, WP2
DCT
STXL
MPLA
ROWCOUNTRow number
zLegacyWARPLLegacy Maintenance PlanS/
4HANA 
4HANASTXL
ROWCOUNT
TDNAME
Row number
Name
Direct

Value Mapping: Maintenance Plan

7
4
PF2, WP2
-
STXL
-
CLUSTD_LINE
--
Text Line
S/4HANA STXL
CLUSTD_LINE

TDID

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

1Texts: application objectMPLAMPLALegacy Maintenance Plan-
IDDefault to "LTXT"
5DCTSTXLSPRASLanguage KeyS/4HANA STXLSPRASLanguage KeyDirect Mapping
6
Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
----S/4HANA STXL
TDOBJECT
CLUSTD_TAGTag columnDefault to "
*"
27DCTSTXLzLegacyWARPLROWCOUNT

Row number

S/4HANA4HANA STXLTDNAMEROWCOUNTName

Row number

Value Direct Mapping: Maintenance Plan
38DCT-STXL-TXLINE-Text LineS/4HANA STXLTDIDTXLINEText IDDefault to 'LTXT'
4DCTSTXLSPRASLanguage KeyS/4HANA STXLSPRASLanguage KeyDirect Mapping
5----S/4HANA STXLCLUSTD_TAGTag columnDefault to "*"
6DCTSTXLROWCOUNT

Row number

S/4HANA STXLROWCOUNT

Row number

Direct Mapping
7DCTSTXLCLUSTD_LINEText LineS/4HANA STXLCLUSTD_LINEText LineDirect Mapping

 7.Maintenance Item Transformation Rule (ECC)

LineDirect Mapping

 7.Maintenance Item Transformation Rule (ECC)

WARPLFunctional LocationFunctional LocationMPOSEQUNREquipment NumberMPOSEquipment Number Equipment Number
Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1PF2, WP2MPOSWAPOSMaintenance ItemS/4HANAMPOSWAPOSMaintenance ItemSystem (Internal numbering)
2PF2, WP2MPOSWARPLMaintenance PlanS/4HANAMPLAWARPLLegacy Maintenance PlanValue Mapping: Maintenance Plan
3PF2, WP2MPOS

PSTXT

Item Short Text

S/4HANA 

MPOS

PSTXT

Item Short Text

Direct mapping

4PF2, WP2MPOSTPLNRFunctional LocationS/4HANAMPOSTPLNRFunctional Location

Value Mapping: Functional Location

5PF2, WP2MPOSTPLNRFunctional LocationS/4HANAMPOSEQUNREquipment NumberValue Mapping: Functional Location where New Equipment is not blank
6
Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1----S/4HANAMPOSWAPOSMaintenance ItemSystem (Internal numbering)
2PF2, WP2MPOSEQUNRMaintenance PlanSTAGINGMPLAzLegacyWARPLLegacy Maintenance PlanDirect mapping.Equipment NumberS/4HANAMPOSEQUNREquipment NumberValue Mapping: Equipment Number
73PF2, WP2MPOSIWERKWAPOSMaintenance ItemSTAGINGMPLAzLegacyWAPOSMaintenance ItemDirect mappingPlanning PlantS/4HANAMPOSIWERKPlanning Plant

Value Mapping: Plant (Maintenance Plant = Yes)

84PF2, WP2MPOS

PSTXT

AUARTOrder TypeItem Short TextS/4HANA 4HANAMPOS

PSTXT

Item Short Text

Direct mapping

AUARTOrder Type

Default to "YA02"

95PF2, WP2MPOSTPLNRGEWRK Main work center for maintenance tasksS/4HANAMPOSTPLNRGEWRK Main work center for maintenance tasks

Value Mapping: Work Centre

If blank then:
1. default to Work Centre derived from Equipment
2. If Equipment is blank then default to the Work Centre derived from Functional Location

610PF2, WP2CRHDWERKSPlantS/4HANARMIPMEQUNRWERGWPlant associated with main work center

Value Mapping:

7ENRICHMENTENR-Maintenance Item AssemblyzLegacyBAUTLAssemblyS/4HANAMPOSEQUNREquipment NumberValue Mapping: Assembly and Construction Type

Plant (Maintenance Plant = Yes)

118PF2, WP2MPOSAUARTWPGRP

Maintenance Planner Group

Order Type

S/4HANA4HANA MPOSWPGRP

Maintenance Planner Group

Value Mapping: Maintenance Planner Group

If blank then:
1. default to Planner Group derived from Equipment
2. If Equipment is blank then default to the Planner Group derived from Functional Location

12AUARTOrder Type

Value Mapping: Order Type

9PF2, WP2MPOSGEWRK PRIOKPriorityS/4HANAMain work center for maintenance tasksMPOSGEWRK PRIOKPriorityMain work center for maintenance tasksValue Mapping: Work Centre

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

Priority
1310PF2, WP2MPOSPLNTYTask List TypeS/4HANA MPOSPLNTYTask List TypeValue Mapping: Task List Header
1114PF2, WP2MPOSPLNNRKey for Task List Group

S/4HANA 

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

Direct mapping.

If blank, default to "1" 

1417PF2, WP2MPOSANLZUSystem ConditionS/4HANA MPOSANLZUSystem ConditionValue Mapping: System Condition
1518PF2, WP2DCTMPOSWPGRP

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

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

Value Mapping: Maintenance activity typesDirect mapping from DCT (as part of enrichment)

8.Maintenance Item Transformation Rule (DCT)

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1
-
DCT
-
MPOS
-
zLegacyWAPOS
-
Legacy Maintenance ItemS/4HANAMPOSWAPOSMaintenance ItemSystem (Internal numbering)
2DCTMPOSzLegacyWARPLLegacy Maintenance Plan
STAGING
S/4HANA MPLA
zLegacyWARPL
WARPL
Legacy
Maintenance Plan
Direct mapping.
Value Mapping: Maintenance Plan
3
3DCTMPOSzLegacyWAPOSLegacy Maintenance ItemSTAGINGMPLAzLegacyWAPOSMaintenance ItemDirect mapping4
DCTMPOS

PSTXT

Item Short Text

S/4HANA 

MPOS

PSTXT

Item Short Text

Direct

mapping5DCTMPOSTPLNRFunctional LocationS/4HANAMPOSTPLNRFunctional LocationValue

Mapping

: Functional Location

6
4DCT
MPOSEQUNREquipment Number
S/4HANA
MPOS
TPLNRFunctional LocationS/4HANA
EQUNREquipment NumberValue Mapping: Equipment Number7-----
MPOS
AUART
TPLNR
Order TypeDefault to "YA02"8
Functional Location

Direct Mapping

5DCTMPOS
GEWRK 
EQUNREquipment Number
Main work center for maintenance tasks
S/4HANAMPOS
GEWRK 
EQUNREquipment Number
Main work center for maintenance tasks
Value Mapping:
Work Centre

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

Equipment Number
6
9
DCTMPOS
PLNTY
IWERKPlanning Plant
Task List Type
S/
4HANA 
4HANAMPOS
PLNTYTask List TypeValue Mapping: Task List Header
IWERKPlanning Plant

Direct Mapping

7-----MPOSAUARTOrder TypeDefault to "YA02"
8
10DCTMPOSPLNNRKey for Task List Group

S/4HANA 

MPOSPLNNRKey for Task List GroupValue Mapping: Task List Header11
DCTMPOS
PLNAL
GEWRK Main work centre for maintenance tasks
Group Counter
S/
4HANA 
4HANAMPOS
PLNALGroup CounterValue Mapping: Task List Header
GEWRK Main work centre for maintenance tasks

Direct Mapping.

If blank then:
1. default to Work Centre derived from Equipment
2. If Equipment is blank then default to the Work Centre derived from Functional Location

9
12
DCTMPOS
APFKT
WERGWPlant associated with main work center
Execution factor for whole task list
S/4HANA
MPOS
RMIPM
APFKTExecution factor for whole task list

Direct mapping.

If blank, default to "1" 

WERGWPlant associated with main work center

Direct Mapping

10
13
DCTMPOS
ANLZU
PRIOK
System Condition
PriorityS/
4HANA 
4HANAMPOS
ANLZU
PRIOK
System Condition
PriorityDirect
mapping.
Mapping
14
11DCTMPOSWPGRP

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 Logic1-----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 Location6PF2, WP2OBJKEQUNREquipment NumberS/4HANAOBJKEQUNREquipment NumberValue Mapping: Equipment Number

Direct Mapping.

If blank then:
1. default to Planner Group derived from Equipment
2. If Equipment is blank then default to the Planner Group derived from Functional Location

12DCTMPOSPLNTYTask List TypeS/4HANA MPOSPLNTYTask List TypeValue Mapping: Task List Header
13DCTMPOSPLNNRKey for Task List Group

S/4HANA 

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

Direct Mapping.

If blank, default to "1" 

16DCTMPOSANLZUSystem ConditionS/4HANA MPOSANLZUSystem ConditionDirect Mapping.
17DCTMPOSILARTMaintenance Activity TypeS/4HANA MPOSILARTMaintenance Activity Type

Direct Mapping

910.Maintenance Item Object List Transformation Rule (DCTECC)

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1PF2, WP2MPOSzLegacyWAPOSLegacy Maintenance Item----

Value Mapping: Maintenance Plan

Note: This will be used as part of pre-load report

2----S/4HANAOBJKOBKNRObject list numberSystem (Internal numbering)
23-----S/4HANAOBJKOBZAEObject list countersSystem (Internal numbering)
34-----S/4HANAOBJK

ILOAN

Location and account assignment for technical objectSystem (Internal numbering)
45PF2, WP2OBJKSORTFObject list sort fieldS/4HANAOBJKSORTFObject list sort fieldDirect mappingMapping.
56PF2, WP2OBJKTPLNRFunctional LocationS/4HANAOBJKTPLNRFunctional LocationValue Mapping: Functional Location: Functional Location
7PF2, WP2OBJKTPLNRFunctional LocationS/4HANAOBJKEQUNREquipment NumberValue Mapping: Functional Location where New Equipment is not blank
86PF2, WP2OBJKEQUNREquipment NumberS/4HANAOBJKEQUNREquipment NumberValue Mapping: Equipment Number

1110.Maintenance Plan (Characteristics Values Header) (ECCItem Object List Transformation Rule (DCT)

KLAHINOBOBTAB3KLAH-INOB-STATU
Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTMPOSzLegacyWAPOSLegacy Maintenance Item----

Value Mapping: Maintenance Plan

Note: This will be used as part of pre-load report

2----S/4HANA-OBJKKLARTClass TypeDefault to "080"OBKNRObject list numberSystem (Internal numbering)
32----S/4HANA-OBJKOBZAEName of Database Table for ObjectDefault to "MPLA"Object list countersSystem (Internal numbering)
4-----OBJK

ILOAN

Location and account assignment for technical objectSystem (Internal numbering)
5DCTOBJKSORTFObject list sort fieldS/4HANAOBJKCLASSClass number

Default to "EAM_9999"

4---SORTFObject list sort fieldDirect Mapping.
6DCTOBJKTPLNRFunctional LocationS/4HANAOBJKOBJEKKey of ObjectDerive from Maintenance Plan Object Number5---TPLNRFunctional LocationDirect Mapping.
7DCTOBJKEQUNREquipment NumberS/4HANAKLAHOBJKEQUNRClass StatusDefault to "1"Equipment NumberValue Mapping: Equipment Number

11.Maintenance Plan 12.Maintenance Plan (Characteristics Values Header) (ECC and DCT)

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1PF2, WP2MPLAzLegacyWARPLLegacy Maintenance Plan----

Value Mapping: Maintenance Plan

Note: This will be used as part of pre-load report

2----S/4HANAKLAHKLARTClass TypeDefault to "080"
23----S/4HANAINOB

OBTAB

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

Default to "EAM_9999"

45----S/4HANAINOBOBJEKKey of ObjectDerive from Maintenance Plan Object Number

Value Mapping: Maintenance Plan 

Note: Use mapping table Maintenance Plan to get New Object Number (OBJNR)

65----S/4HANAKLAHSTATUClass StatusDefault to "1"

 1312.Maintenance Plan (Default Characteristics Values Allocation - Allowed CT) (ECC and DCT)

-Maintenance Plan CharacteristicMaintenance Plan Characteristic
Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1PF2, WP2, DCTMPLAzLegacyWARPLLegacy Maintenance Plan----S/4HANAMPLAWARPLMaintenance Plan

Value Mapping: Maintenance Plan

Note: This will be used as part of pre-load report

System (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---PF2, WP2, DCTMPLAzLegacyWARPLLegacy Maintenance PlanS/4HANAINOBOBJEKKey of Object

Value Mapping: Maintenance Plan.

Derive from

Note: Use mapping table

Maintenance Plan to get New Object Number (OBJNR)

6ENRICHMENT-ENR--Characteristic Name-S/4HANACABNATNAMCharacteristic NameDirect Mapping

Value Mapping: Characteristic A2D where ATNAM = "A_ALLOWED_CT"

7ENRICHMENT-ENR--Characteristic Value-S/4HANAAUSPATWRTCharacteristic ValueDirect MappingATWRTCharacteristic Value

If A_DISCRETE_TO_ASSET = "YES" then blank.

If A_DISCRETE_TO_ASSET = "NO" then
1. default to CT derived from Equipment
2. If Equipment is blank then default to the CT derived from Functional Location

8----8ENRICHMENTENR-Maintenance Plan Characteristic-Item NumberS/4HANAKSMLPOSNRItem NumberDirect Mapping

Default to "001'

Note: Each Maintenance Plan can have only 1 Allowed CT characteristic

1314.Maintenance Plan (Default Characteristics Values Allocation - Discrete to the Asset) (ECC and DCT)

-
Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation LogicFieldTarget DescriptionTransformation Logic
1PF2, WP2, DCTMPLAzLegacyWARPLLegacy Maintenance Plan----

Value Mapping: Maintenance Plan

Note: This will be used as part of pre-load report

21----S/4HANAKLAHKLARTClass TypeDefault to "018"
23----S/4HANAINOB

OBTAB

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

Default to "EAM_9999"

4---
5PF2, WP2, DCTMPLAzLegacyWARPLLegacy Maintenance PlanS/4HANAINOBOBJEKKey of ObjectDerive from Maintenance Plan Object Number

Value Mapping: Maintenance Plan.

Note: Use mapping table Maintenance Plan to get New Object Number (OBJNR)

6----5DCTCABNATNAMCharacteristic NameS/4HANACABNATNAMCharacteristic NameDirect Mapping

Value Mapping: Characteristic A2D where ATNAM = "A_DISCRETE_TO_ASSET" 

76DCTAUSPATWRT-CHAR_DISCRETE_TO_ASSETDiscrete to the Asset CharacteristicCharacteristic ValueS/4HANAAUSPATWRTCharacteristic ValueDirect MappingCharacteristic Value

Direct Mapping from DCT (as part of enrichment)

If not "YES" then default to "NO"

87----S/4HANAKSMLPOSNRItem NumberGenerate sequence number starting with 1 by order the record is created for each Key of ObjectDefault to "001"

Note: Each Maintenance Plan can have only 1 Discrete to the Assetcharacteristic

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

-
Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1PF2, WP2, DCTMPLAzLegacyWARPLLegacy Maintenance Plan----

Value Mapping: Maintenance Plan

Note: This will be used as part of pre-load report

2----S/4HANAKLAHKLARTClass TypeDefault to "018"
23----S/4HANAINOB

OBTAB

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

Default to "EAM_9999"

4---
5PF2, WP2, DCTMPLAzLegacyWARPLLegacy Maintenance PlanS/4HANAINOBOBJEKKey of Object

Value Mapping: Maintenance Plan.

Derive from

Note: Use mapping table

Maintenance Plan to get New Object Number (OBJNR)

56----S/4HANACABNATNAMCharacteristic NameDefault to "Regulatory"

Value Mapping: Characteristic A2D where ATNAM = "A_REGULATORY" 

76----S/4HANAAUSPATWRTCharacteristic Value

Derive from Task List Header Data Construction "

Regulatory" Characteristic Value
7----S/4HANAKSMLPOSNRItem NumberGenerate sequence number starting with 1 by order the record is created for each Key of Object

A_REGULATORY" Characteristic Value

8----S/4HANAKSMLPOSNRItem NumberDefault to "001"

 Note:

  1. Each Maintenance Plan can have only 1 Regulatory characteristic
  2. To link Maintenance Plan to Task List Header Data Construction, join MPOS-PLNTY, MPOS-PLNNR, MPOS-PLNAL to PLKO-PLNTY, PLKO-PLNNR, PLKO-PLNAL

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

-
Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1PF2, WP2, DCTMPLAzLegacyWARPLLegacy Maintenance Plan----

Value Mapping: Maintenance Plan

Note: This will be used as part of pre-load report

2----S/4HANAKLAHKLARTClass TypeDefault to "018"
23----S/4HANAINOB

OBTAB

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

Default to "EAM_9999"

4---
5PF2, WP2, DCTMPLAzLegacyWARPLLegacy Maintenance PlanS/4HANAINOBOBJEKKey of ObjectDerive from Maintenance Plan Object Number

Value Mapping: Maintenance Plan.

Note: Use mapping table Maintenance Plan to get New Object Number (OBJNR)

65----S/4HANACABNATNAMCharacteristic NameDefault to "Nature of Work"

Value Mapping: Characteristic A2D where ATNAM = "A_NATURE_OF_WORK" 

76----S/4HANAAUSPATWRTCharacteristic Value

Derive from Task List Header

"Nature of Work

Data Construction "A_NATURE_OF_WORK" Characteristic Value

78----S/4HANAKSMLPOSNRItem NumberGenerate sequence number starting with 1 by order the record is created for each Key of ObjectDefault to "001"

 Note:

  1. Each Maintenance Plan can have only 1 Nature of Work characteristic
  2. To link Maintenance Plan to Task List Header Data Construction, join MPOS-PLNTY, MPOS-PLNNR, MPOS-PLNAL to PLKO-PLNTY, PLKO-PLNNR, PLKO-PLNAL


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

Transformation Mapping

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

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

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

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

Class1010

Assembly / Construction Type

1012

Measuring Point

1015

Characteristic

1017

Maintenance Strategy

2019

Materials - Basic Data View

Error Handling

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

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

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

Change log

Change History
limit10

Workflow history

Workflow Report
parent@self
hideheadertrue
typeapprovals