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, with informal words. 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.

Maintenance Plan from legacy system is relevant if:

1. have at least 1 valid maintenance Item

Maintenance Plan from legacy system is not relevant if:

1. Maintenance plan marked for deletion

Maintenance Item within each maintenance plan is considered relevant if:

1. It has at least 1 relevant material, FL or Equipment in ref object or item in object list based on material, FL and Equipment relevancy
2. At least 1 valid task list based on task list relevancy

Object list within each relevant maintenance item will only include FL and Equipment that is relevant based on FL and Equipment Relevancy.

Additional Information

Multi-language Requirement

Multi language is supported for Maintenance plan and item. Login via a different language will have its description displayed in the logon language if the language key is maintained in the Maintenance plan and item.

Document Management

Long text and DIR are not covered in this document as they are defined as another data object.

Legal Requirement

Not Applicable

Special Requirements

Not Applicable

Target Design

The technical design of the target for this conversion approach.

1. Maintenance Header

   Table	Field	Data Element	Field Description	Data Type	Length	Requirement
   MPLA	WARPL	WARPL	Maintenance Plan	CHAR	12	System
   MPLA	MPTYP	MPTYP	Maintenance plan category	CHAR	2	Mandatory
   MPLA	STRAT	STRAT	Maintenance strategy	CHAR	6	Mandatory
   MPLA	WPTXT	WPTXT	Maintenance Plan Text	CHAR	40	Mandatory
   MPLA	VSPOS	VERSCHPLUS		NUMC	3	Conditional
   MPLA	TOPOS	TOLERPLUS	Tolerance for Late Completion (%)	NUMC	3	Conditional
   MPLA	TONEG	TOLERNEG	Tolerance for Early Completion (%)	NUMC	3	Conditional
   MPLA	VSNEG	VERSCHNEG	Shift Factor for Early Completion	NUMC	3	Conditional
   MPLA	SFAKT	SFAKT	Cycle modification factor	DEC	3(2)	Conditional
   MPLA	FABKL	FABKL	Factory calendar key	CHAR	2	Conditional
   MPLA	HORIZ	HORIZONT	Call horizon for maintenance plan calls	NUMC	3	Mandatory
   MPLA	HORIZ_QUALIFIER	EAM_CC_CALLHORIZON_QUALIFIER	Calculation Type of Call Horizon	CHAR	1	Mandatory
   MPLA	ABRHO	ABRHO	Scheduling Period	NUMC	3	Mandatory
   MPLA	HUNIT	HUNIT	Unit for Scheduling Period	UNIT	3	Conditional
   MPLA	CALL_CONFIRM	CALL_CONFIRM	Only Create New Call Object After Completing Predecessor	CHAR	1	Conditional
   MPLA	STADT	STADT	Start date	DATS	8	Conditional
   RMIPM	ZEIT	TIME_KNZ	Indicator for selection of time-based maintenance	CHAR	1	Conditional
   MPLA	STICH	TERMKNZ	Scheduling indicator	CHAR	1	Conditional
   MPLA	PLAN_SORT	PLAN_SORT	Sort field for maintenance plans	CHAR	20	Mandatory
   MPLA	BEGRU	IAUTG	Technical object authorization group	CHAR	4	Not Used
   RMIPM	STTAG	MP_STTAG	Key Date	DATS	8	Conditional
   MPLA	ENDDT_FOR_SCHED	EAM_ENDDT_FOR_SCHED	End Date for Scheduling	DATS	8	Conditional
   MPLA	TPLNR	TPLNR	Functional Location	CHAR	30	Mandatory
   MPLA	EQUNR	EQUNR	Equipment Number	CHAR	18	Conditional
   RMIPM	GEWERK	GEWRK	Main work Centre for maintenance tasks	CHAR	8	System
   RMIPM	WERGW	WERGW	Plant associated with Main Work Centre	CHAR	4	System
   RMIPM	OFFS1	WOFFS1	Maintenance package offset	CHAR	22	Not Used
   RMIPM	MEHRFACH_Z	MEHRFACH_Z	Multiple counter plan	CHAR	1	Not Used
   RMIPM	WSET	WSET	Cycle set for multiple counter plan	CHAR	6	Not Used
   MITEM_OBJLIST_D	EQUIPMENT	EQUNR	Equipment Number	CHAR	18	Conditional
   MITEM_OBJLIST_D	FUNCTIONALLOCATION	TPLNR_UNCONVERTED	Functional location	CHAR	30	Conditional
   KLAH	CLASS	KLASSE_D	Class number	CHAR	18	Mandatory

2. Maintenance Item

   Table	Field	Data Element	Field Description	Data Type	Length	Requirement
   MPLA	WARPL	WARPL	Maintenance Plan	CHAR	12	System
   MPOS	WAPOS	WAPOS	Maintenance item	CHAR	16	System
   MPOS	PSTXT	POSTXT	Item Short Text	CHAR	40	Mandatory
   MPOS	BAUTL	BAUTL	Assembly	CHAR	40	Not Used
   MPOS	IWERK	IWERK	Maintenance Planning Plant	CHAR	4	System
   MPOS	AUART	AUFART	Order Type	CHAR	4	Mandatory
   MPOS	PRIOK	PRIOK	Priority	CHAR	1	Mandatory
   MPOS	GSBER	GSBER	Business Area	CHAR	4	Not Used
   MPOS	PLNTY	PLNTY	Task List Type	CHAR	1	Mandatory
   MPOS	PLNNR	PLNNR	Key for Task List Group	CHAR	8	Mandatory
   MPOS	PLNAL	PLNAL	Group Counter	CHAR	2	Mandatory
   MPOS	WPGRP	INGRP	Planner Group for Customer Service and Plant Maintenance	CHAR	3	Conditional
   MPOS	APFKT	APFKT	Execution factor for whole task list	DEC	3(0)	Conditional
   MPOS	ANLZU	ANLZU	System Condition	CHAR	1	Conditional
   MPOS	SERIALNR	GERNR	Serial Number	CHAR	18	Not Used
   MPOS	SERMAT	MATNR	Material Number	CHAR	40	Not Used

3. Cycle definitions and Measing Points for Maintenance Plan

   Table	Field	Data Element	Field Description	Data Type	Length	Requirement
   MPLA	WARPL	WARPL	Maintenance Plan	CHAR	12	System
   MMPT	PAK_TEXT	TXZYKLUS	Text for maintenance package/cycle (time/performance)	CHAR	30	System
   MMPT	POINT	IMRC_POINT	Measuring Point	CHAR	12	Conditional
   MMPT	ZYKL1	DZYK_ZEIT	Maintenance package cycle/offset	FLTP	16(16)	System
   MMPT	ZEIEH	DZEIEH	Unit for the performance of maintenance tasks	UNIT	3	System

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

Data Cleansing

Work Order Data strictly adheres to the Master Data Standard. The complete information of the key fields that hold the Class information follows the Master Data Standard document that is located here <include hyperlink>.

Informal Words **

Conversion Process

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

For sites that are not on SAP-PF2 and WP2 systems, collection will be done manually in the data collection template.

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

Data Privacy and Sensitivity

Extraction

Extract data from a source into . There are 2 possibilities:

1. The data exists. connects to the source and loads the data into . There are 3 methods:
   1. Perform full data extraction from relevant tables in the source system(s).
   2. Perform extraction through the application layer.
   3. Only if Syniti Migrate cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
2. The data does not exist (or cannot be converted from its current state).  The data is manually collected by the business directly in Syniti Migrate. This is to be conducted using DCT (Data Collection Template) in Syniti Migrate

The agreed Relevancy criteria is applied to the extracted records to identify the records that are applicable for the Target loads

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

Maintenance Plan and Item DCT Rules

1. Maintenance Plan Header - MPLA

   Field Name	Field Description	Rule
   WARPL	Maintenance Plan	Running number NNNNNNNN to NNNNNNNN for Maintenance Plan Category = XXX.
   MPTYP	Maintenance Plan category	Must reference to active Maintenance Plan category in S4/HANA (T399W)
   WPTXT	Maintenance Plan text	40 Char text
   STRAT	Maintenance strategy	Must reference to active strategy. Must be the same strategy as the task list strategy Naming Convention as follows: XX_XXX E.g - 01_001
   HORIZ_QUALIFIER	Calculation Type of Call Horizon	Default to "% " if blank
   ABRHO	Scheduling Period	Default to "3" if blank
   HUNIT	Unit in scheduling interval	Default to "YR" if if blank and ABRHO is blank
   PLAN_SORT	Sort field for maintenance plans	Must reference to active Sort field in S4/HANA (T399G) Groups 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.
   TPLNR	Functional Location	Must reference to active Functional Location in S4/HANA (IFLO)
   EQUNR	Equipment Number	Must reference to active Equipment Number in S4/HANA (EQUI) Can be Blank only if FLOC is updated. Valid Entry if CT of the Equipment = Task List CT
   CLASS	Class number	Default to "9999"

2. Maintenance Plan Items

   Field Name	Field Description	Rule
   WARPL	Maintenance Plan	Must reference to active Maintenance Plan (MPLA).
   WAPOS	Maintenance item
   PSTXT	Item Short Text	Description shall be defined as Frequency + TOT + Asset Tag.
   PRIOK	Priority	Must reference to active Priority in S4/HANA (T356).
   PLNTY	Task List Type	Must reference to active Task List Type Task List Type in S4/HANA (TCA01).
   PLNNR	Key for Task List Group	Must reference to active Key for Task List Group in S4/HANA (PLKO).
   PLNAL	Group Counter	Group - Group Counter CT shall be equal to the Technical Object CT.
   AUFART	Order Type	Must reference to active Order Type in S4/HANA (T003O). Default to "YA02".
   WPGRP	Planner Group for Customer Service and Plant Maintenance	Must reference to active Maintenance Planner Group in S4/HANA (T024I). Default to the value derived from the technical object. Update the value if provided by business (Takes Precedence).
   APFKT	Execution factor for whole task list
   ANLZU	System Condition
   POINT	Measuring Point	Must reference to active Measuring Point in S4/HANA (IMPTT). Must not be blank if the first 2 Chars of the Strategy = 02.

3. Cycle definitions and Measing Points for Maintenance Plan

   Field Name	Field Description	Rule
   WARPL	Maintenance Plan	Must reference to active Maintenance Plan in S4/HANA (MPLA).
   NUMMER	Counter in control tables
   POINT	Measuring Point
   ZEIEH	Unit for the performance of maintenance tasks	Must reference to active Unit of Measure (T006).
   ZYKL1	Maintenance package cycle/offset
   PAK_TEXT	Text for maintenance package/cycle (time/performance)	System
   LANGU	Primary language for object texts
   OFFSET	Start offset of a time-based maintenance package
   CYCLESEQIND	Cycle Set Sequence
   SETREPEATIND	Repeat Factor for Cycle Set Sequence

Extraction Dependencies

Transformation

The Target fields are mapped to the applicable Legacy field that will be its source, this is a 3-way activity involving the Business, Functional team and Data team. This identifies the transformation activity required to allow to make the data Target ready:

1. Perform value mapping and data transformation rules.
   1. Legacy values are mapped to the to-be values (this could include a default value)
   2. Values are transformed according to the rules defined in
2. Prepare target-ready data in the structure and format that is required for loading via prescribed Load Tool. This step also produces the load data ready for business to perform Pre-load Data Validation

Transformation Run Sheet

Transformation Rules

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

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

The load process includes:

1. Execute the automated data load into target system using load tool or product the load file if the load must be done manually
2. Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation

Load Run Sheet

Load Phase and Dependencies

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

• Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
• Maintenance Plan and Item is in scope based on data design and any exception requested by business.
• All data cleansing and preparation has been completed.
• Maintenance Plan collection timeline are the same as Equipment and Functional Location collection. Maintenance Plan collection needs to go hand in hand with equipment and functional location collection. Drop down for equipment and functional location in the maintenance plan DCT relies on the input in equipment and functional location DCT.
• All Maintenance Plans and Items mapped to valid Technical Objects in S/4 HANA

See also

Change log

Workflow history