| Status | |
|---|---|
| Owner | |
| Stakeholders |
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.
The data from legacy system includes:
- Maintenance Plan (MPLA-WARPL) which have at least 1 valid maintenance Item
- Maintenance Items (MPOS-WAPOS) that has at least 1 valid task list based on Task List relevancy
- Maintenance Items (MPOS-WAPOS) that has at least 1 relevant Material (MARA-MATNR), Functional Location (IFLO-TPLNR) or Equipment (EQUI-EQUNR) in reference object or Item in object list based on Material (MARA-MATNR), Functional Location (IFLO-TPLNR) or Equipment (EQUI-EQUNR) relevancy
The data from legacy system excludes:
- Maintenance Plan (MPLA-WARPL) marked for deletion (MPLA-LVORM) = 'X'
- 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.
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
PF2, WP2 | Maintenance Plan: An initial extract will be provided to business to evaluate. Additional data/records may be required and these will be constructed via DCT. Enrichment of in-scope data may be required and will be added via transformation rules (business/technical). | 70,000 | S/4HANA | 70,000 |
PF2, WP2 | Maintenance Items: An initial extract will be provided to business to evaluate. Additional data/records may be required and these will be constructed via DCT. Enrichment of in-scope data may be required and will be added via transformation rules (business/technical). | 74,000 | S/4HANA | 74,000 |
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
| 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 | Shift Factor for Late Completion | 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 |
Note: 1 Maintenance Plan can have multiple Maintenance Items
3.Cycle definitions and Measuring 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 Plan information follows the Master Data Standard document that is located here.
Data Cleansing
| ID | Criticality | Error Message/Report Description | Rule | Output | Source System |
|---|---|---|---|---|---|
1016-001 | C1 | Maintenance Plan-Maintenance Item: Invalid, Inactive or no maintenance item | Maintenance Plan as per Relevancy Criteria assigned with inactive or no Maintenance Items attached. | Maintenance Plan, Plant, Maintenance Item, | PF2, WP2 |
1016-002 | C1 | Maintenance Plan-Description: Missing Description | Maintenance Plan Description is blank | Maintenance Plan, Plant, Description | PF2, WP2 |
1016-003 | C2 | Maintenance Plan-Description: Descriptions with Informal Words | Maintenance Plan which contain Informal Words in the Maintenance Plan Description | Maintenance Plan, Plant, Description | PF2, WP2 |
1016-004 | C1 | Maintenance Plan-Task List: Invalid, Inactive or no Task List allocated to Maintenance Plan | Maintenance Plan as per Relevancy Criteria assigned with a Task List which does not belong below: | Maintenance Plan, Plant, Task List | PF2, WP2 |
1016-005 | C1 | Maintenance Plan-Work Centre: Invalid, Inactive or no Work Centre assigned | Maintenance Item assigned with invalid or inactive Work Centre | Maintenance Plan, Plant, Work Centre | PF2, WP2 |
1016-006 | C1 | Maintenance Plan-Maintenance Strategy: Invalid, Inactive or no Maintenance Strategy assigned | Maintenance Plan as per Relevancy Criteria assigned with a Maintenance Strategy which does not belong below: | Maintenance Plan, Plant, Maintenance Strategy | PF2, WP2 |
1016-007 | C1 | Maintenance Plan-Unit of Measure: UOM Missing / incorrect. | Maintenance Plan and Item as per Relevancy Criteria with no UoM Assigned or Invalid UoM (T006) | Maintenance Plan, Plant, Unit of Measure | PF2, WP2 |
1016-008 | C1 | Maintenance Plan-Authorization Group: Technical object authorization group incorrect. | Maintenance Plan and Item as per Relevancy Criteria with Invalid Authorization Group (T370F) | Maintenance Plan, Plant, Authorization Group | PF2, WP2 |
1016-009 | C1 | Maintenance Plan-Sort field: Blank or invalid Sort field | Maintenance Plan and Item as per Relevancy Criteria with Invalid Sort Field (T399G) | Maintenance Plan, Plant, Sort Field | PF2, WP2 |
1016-010 | C1 | Maintenance Plan: Invalid, Inactive or no Equipment or Functional Location assigned | Maintenance Plan as per Relevancy Criteria assigned with Equipment or Functional Location which does not belong below: | Maintenance Plan, Plant, Equipment, Functional Location | PF2, WP2 |
1016-011 | C1 | List of Maintenance Item under Maintenance Plan assigned to Invalid, Inactive or no Equipment or Functional Location | Maintenance Item as per Relevancy Criteria under Maintenance Plan assigned with Equipment or Functional Location which does not belong below: | Maintenance Plan, Plant, Equipment, Functional Location | PF2, WP2 |
1016-012 | C1 | Maintenance Plan-Characteristic: Invalid, Inactive or no Characteristic allocated | Maintenance Plan as per Relevancy Criteria assigned with a Characteristic which does not belong below: | Maintenance Plan, Plant, Characteristic | PF2, WP2 |
1016-013 | C1 | Maintenance Plan-Class: Invalid, Inactive or no Class allocated | Maintenance Plan as per Relevancy Criteria assigned with a Class which does not belong below: | Maintenance Plan, Plant, Class | PF2, WP2 |
1016-014 | C1 | Maintenance Item-Planning Plant: Planning Plant incorrect | Maintenance Plan and Item as per Relevancy Criteria with Invalid Plant (T001W) | Maintenance Plan, Plant, Planning Plant | PF2, WP2 |
1016-015 | C1 | 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-016 | C3 | 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. | Maintenance Plan, Plant, Technical Object, Task List, Strategy, Description | PF2, WP2 |
1016-017 | C1 | 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-018 | C1 | Maintenance Item-Planner Group: Invalid or no Planner Group | Maintenance Plan and Item as per Relevancy Criteria with no Planner Group Assigned or Invalid Planner Group (T024I) | Maintenance Item, Plant,Planner Group | PF2, WP2 |
1016-019 | C2 | Maintenance Item-Planning Plant: Planning Plant and Maintenance Plant are not the same | Maintenance Item as per Relevancy Criteria with Planning Plant <> Maintenance Plant | Maintenance Item, Plant, Planning Plant | PF2, WP2 |
1016-020 | C1 | Maintenance Item-Characteristic: Invalid, Inactive or no Characteristic allocated | Maintenance Plan as per Relevancy Criteria assigned with a Characteristic which does not belong below: | Maintenance Item, Plant, Characteristic | PF2, WP2 |
1016-021 | C1 | Maintenance Item-Class: Invalid, Inactive or no Class allocated | Maintenance Plan as per Relevancy Criteria assigned with a Class which does not belong below: | Maintenance Item, Plant, Class | 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:
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:
Collection will be done manually in the Data Collection Template for the following scenarios:
- For sites not on SAP-PF2 or WP2 systems
Data Privacy and Sensitivity
Not ApplicableExtraction
Extract data from a source into Syniti Migrate. There are 2 possibilities:
- The data exists. Syniti Migrate connects to the source and loads the data into Syniti Migrate. There are 3 methods:
- Perform full data extraction from relevant tables in the source system(s).
- Perform extraction through the application layer.
- Only if Syniti Migrate cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
- 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 Description | Team 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 Screen | Parameter Name | Selection Type | Requirement | Value to be entered/set |
|---|---|---|---|---|
| Not Applicable |
Data Collection Template (DCT)
Target Ready Data Collection Template will be created for Maintenance Plan and Item data with exception of some fields which require transformation as mentioned in the transformation rule.Maintenance Plan and Item DCT Rules
1.Maintenance Plan Data Construction Rules
| Field Name | Field Description | Rule |
|---|---|---|
| MPTYP | Maintenance Plan category | Must reference to active Maintenance Plan category in S4/HANA (T399W) |
STRAT | Maintenance strategy | Must reference to active Strategy (T351) Naming Convention as follows: XX_XXX E.g - 01_001 |
| WPTXT | Maintenance Plan Text | Free text. Maximum 40 Chars. |
HORIZ | Call horizon for maintenance plan calls | Mandatory. Numeric values only Note: Will default to 100 % if blank |
HORIZ_QUALIFIER | Calculation Type of Call Horizon | Mandatory. Note: Will default to "%" if blank |
ABRHO | Scheduling Period | Mandatory. Note: Will default to "3" if blank |
HUNIT | Unit in scheduling interval | Conditional. Note: Will default to "YR" if if blank and ABRHO is blank |
CALL_CONFIRM | Completion Requirement | Conditional. Allowed values: "X" or blank |
STADT | Start date | Conditional. Date formatted values only |
ZEIT | Time | Conditional. Allowed values: "X" or blank |
STICH | Time-Key Date | Conditional. Allowed values: "1", "2", "3", "4" or blank |
FBKL | Time-factory caldr | Conditional. Must reference config (TFACD) |
PLAN_SORT | Sort field for maintenance plans | Mandatory. Must reference to active Sort field in S4/HANA (T399G) Note: Groups Maintenance Plans based on below design principal: All Maintenance Plans of Inspection for 6M Inspection will be grouped with this Sort field. |
STTAG | Key Date | Conditional. Date formatted values only |
ENDDT_FOR_SCHED | End Date for Scheduling | Conditional. Date formatted values only |
| CLASS | Class number | Default to "EAM_9999" |
2.Maintenance Item Data Construction Rules
| Field Name | Field Description | Rule |
|---|---|---|
PSTXT | Item Short Text | Description shall be defined as Frequency + TOT + Asset Tag. |
| TPLNR | Functional Location | Mandatory. Must reference to active Functional Location in S4/HANA (IFLO) |
| EQUNR | Equipment Number | Conditional. Must reference to active Equipment Number in S4/HANA (EQUI) Can be Blank only if FLOC is updated. |
| AUFART | Order Type | Must reference to active Order Type in S4/HANA (T003O). Default to "YA02". |
| GEWERK | Main work center for maintenance tasks | Default to the value derived from the technical object Must reference active Work Centre (CRHD) |
| 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. |
| APFKT | Execution factor for whole task list | Note: Will default to to 1, if Data not provided by business |
| ANLZU | System Condition | Conditional |
| SORTF | Object list sort field | Sequential number starting 1 if data for Object List EQUIPMENT or FUNCTIONAL LOCATION is provided |
| WPGRP | Planner Group for Customer Service and Plant Maintenance | Conditional. 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). |
3.Cycle definitions and Measing Points Data Construction Rules
| Field Name | Field Description | Rule |
|---|---|---|
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. |
| 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
List the steps that need to occur before extraction can commence
| Item # | Step Description | Team Responsible |
|---|---|---|
| 1 | Ensure Syniti has the necessary connection and access to legacy servers | SyWay A2D Data Team |
| 2 | Ensure that the necessary cleansing activities in legacy sources are complete | SyWay A2D Data Team / Business |
| 3 | Ensure that create, change and deletion of master data is freeze in legacy Production system | Legacy IT |
| 4 | Relevancy Criteria for Characteristics | SyWay A2D Data Team |
| 5 | Relevancy Criteria for Class | SyWay A2D Data Team |
| 6 | Relevancy Criteria for Construction Type | SyWay A2D Data Team |
| 7 | Relevancy Criteria for Equipment | SyWay A2D Data Team |
| 8 | Relevancy Criteria for Functional Location | SyWay A2D Data Team |
| 9 | Relevancy Criteria for Maintenance Strategy | SyWay A2D Data Team |
| 10 | Relevancy Criteria for Measuring Point | SyWay A2D Data Team |
| 11 | Relevancy Criteria for Task List | SyWay A2D Data Team |
| 12 | Relevancy Criteria for Work Centre | SyWay A2D Data Team |
| 13 | Relevancy Criteria for Material Master | SyWay 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:
- Perform value mapping and data transformation rules.
- Legacy values are mapped to the to-be values (this could include a default value)
- Values are transformed according to the rules defined in Syniti Migrate
- 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 Description | Team Responsible |
|---|---|---|
| 1 | Obtain DCT Sign-off from Business | SyWay A2D Data Team |
| 2 | <Add steps from Syniti Migrate here> | Syniti |
| 3 | Review and Validate Error and Preload Reports | SyWay A2D Data Team |
| 4 | Generate Load Files | Syniti |
Transformation Rules
1.Maintenance Plan Transformation Rule (DCT)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4HANA | MPLA | WARPL | Maintenance Plan | System (Internal numbering) |
| 2 | DCT | MPLA | HORIZ | Call horizon for maintenance plan calls | S/4HANA | MPLA | HORIZ | Call horizon for maintenance plan calls | Direct mapping. If blank, default to "100" |
| 3 | DCT | MPLA | HORIZ_QUALIFIER | Calculation Type of Call Horizon | S/4HANA | MPLA | HORIZ_QUALIFIER | Calculation Type of Call Horizon | Direct mapping. If blank, default to "%" |
| 4 | DCT | MPLA | ABRHO | Scheduling Period | S/4HANA | MPLA | ABRHO | Scheduling Period | Direct mapping. If blank, default to "3YR" |
| 5 | DCT | MPLA | HUNIT | Unit in scheduling interval | S/4HANA | MPLA | HUNIT | Unit in scheduling interval | Direct mapping. If blank, default to "Yr" |
| 6 | DCT | MPLA | CALL_CONFIRM | Completion Requirement | S/4HANA | MPLA | CALL_CONFIRM | Completion Requirement | Direct mapping. |
| 7 | DCT | MPLA | STADT | Start date | S/4HANA | MPLA | STADT | Start date | Direct mapping. |
| 8 | DCT | TPMUS | ZEIT | Time | S/4HANA | TPMUS | ZEIT | Time | Direct mapping. |
| 9 | DCT | MPLA | TPLNR | Functional Location | S/4HANA | MPLA | TPLNR | Functional Location | Equipment field must be blank. System Generated if Equipment is Updated |
| 10 | DCT | MPLA | EQUNR | Equipment Number | S/4HANA | MPLA | EQUNR | Equipment Number | Can be Blank only if FLOC is updated. CT of the Equipment must match Task List CT |
| 11 | DCT | MPLA | MPTYP | Maintenance plan category | S/4HANA | MPLA | MPTYP | Maintenance plan category | Default to "PM" |
| 12 | DCT | MPLA | WPTXT | Maintenance Plan Text | S/4HANA | MPLA | WPTXT | Maintenance Plan Text | Maintenance Plan description must match Task list Description |
| 13 | DCT | MMPT | POINT | Measuring Point | S/4HANA | MMPT | POINT | Measuring Point | Updated if the first 2 Chars of the Strategy = 02. |
| 14 | DCT | MPLA | VSPOS | Shift Factor for Late Completion | S/4HANA | MPLA | VSPOS | Shift Factor for Late Completion | Default to 0 if Time based Maintenance Plan. Default to 100 if Performance based Maintenance Plan. |
| 15 | DCT | MPLA | TOPOS | Tolerance for Late Completion (%) | S/4HANA | MPLA | TOPOS | Tolerance for Late Completion (%) | Direct mapping. If blank, default to "10%" |
| 16 | DCT | MPLA | VSNEG | Shift Factor for Early Completion | S/4HANA | MPLA | VSNEG | Shift Factor for Early Completion | Default to 0 if Time based Maintenance Plan. Default to 100 if Performance based Maintenance Plan. |
| 17 | DCT | MPLA | TONEG | Tolerance for Early Completion (%) | S/4HANA | MPLA | TONEG | Tolerance for Early Completion (%) | Direct mapping. If blank, default to "10%" |
| 18 | DCT | MPLA | SFAKT | Cycle modification factor | S/4HANA | MPLA | SFAKT | Cycle modification factor | Direct mapping. If blank, default to "1" |
| 19 | DCT | MPLA | FABKL | Factory calendar key | S/4HANA | MPLA | FABKL | Factory calendar key | Direct mapping. |
| 20 | DCT | MPLA | CALL_CONFIRM | Completion Requirement | S/4HANA | MPLA | CALL_CONFIRM | Completion Requirement | Direct mapping. System Generated if Equipment is Updated |
| 21 | DCT | MPLA | STADT | Start date | S/4HANA | MPLA | STADT | Start date | Direct mapping |
| 22 | DCT | RMIPM | ZEIT | Indicator for selection of time-based maintenance | S/4HANA | RMIPM | ZEIT | Indicator for selection of time-based maintenance | If blank, default to "X" |
| 23 | DCT | KLAH | CLASS | Class number | S/4HANA | KLAH | CLASS | Class number | Default to "EAM_9999" |
2.Maintenance Item Transformation Rule (DCT)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4HANA | MPOS | WAPOS | Maintenance Item | System (Internal numbering) |
| 2 | PF2, WP2 | MPOS | WARPL | Maintenance Plan | S/4HANA | MPOS | WARPL | Maintenance Plan | Direct mapping |
| 3 | PF2, WP2 | MPOS | WPGRP | Maintenance Planner Group | S/4HANA | MPOS | WPGRP | Maintenance Planner Group | Update the value if provided by business. If no legacy data provided, default to the value derived from the technical object. |
| 4 | PF2, WP2 | MPOS | POSTXT | Item Short Text | S/4HANA | MPOS | POSTXT | Item Short Text | Description shall be defined as Frequency + TOT + Asset Tag |
| 5 | PF2, WP2 | MPOS | AUFART | Order Type | S/4HANA | MPOS | AUFART | Order Type | Default to "YA02" |
| 6 | PF2, WP2 | MPOS | PLNTY | TCA01 | |||||
| 7 | PF2, WP2 | MPOS | PLNNR | ||||||
| 8 | PF2, WP2 | MPOS | PLNAL | Group Counter | S/4HANA | MPOS | PLNAL | Group Counter | Group - Group Counter CT must be same as the Technical Object CT |
| 9 | PF2, WP2 | MPOS | APFKT | ||||||
| 10 | PF2, WP2 | MPOS | ANLZU | ||||||
| 11 | PF2, WP2 | MPOS | SORTF | ||||||
| 12 | PF2, WP2 | MPOS | WPGRP | ||||||
| 13 | |||||||||
| 14 | |||||||||
| 15 |
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 Name | Mapping Table Description |
|---|---|
| Informal Characters | List of Informal Characters and New Translation |
Maintenance Plan | Old to new Maintenance Plan |
Maintenance Strategy | Old to new Maintenance Strategy |
Material Number | Old to new Material Number |
Task List | Old to new Task List |
Assembly | Old to new Assembly |
Sort field | Old to new Sort field |
Functional Location | Old to new Functional Location |
Equipment Number | Old to new Equipment Number |
Maintenance item | Old to new Maintenance item |
Priority | Old to new Priority |
Task List | Old to new Task List |
Order Type | Old to new Order Type |
Planner Group | Old to new Planner Group |
Measuring Point | Old to new Measuring Point |
Unit of Measure | Old to new Unit of Measure |
Maintenance Planner Group | Old to Maintenance Planner Group |
Transformation Dependencies
List the steps that need to occur before transformation can commence| Item # | Step Description | Team Responsible |
|---|---|---|
| 1 | Ensure DCT tables completeness | SyWay A2D Data Team |
| 2 | Value Mappings are according to the latest design -<List of Value Mappings> | SyWay A2D Data Team |
Pre-Load Validation
Project Team
The following pre-load validations will be performed by the Project Team.Completeness
| Task | Action |
|---|---|
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
| Task | Action |
|---|---|
Conversion Accuracy | SyWay A2D Data Team to verify that all fields below meet pass the 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
| Task | Action |
|---|---|
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
| Task | Action |
|---|---|
Conversion Accuracy | Business Data Owner/s to verify that all fields below meet pass the checks:
|
Load
The load process includes:
- Execute the automated data load into target system using load tool or product the load file if the load must be done manually
- 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 Description | Team Responsible |
|---|---|---|
| 1 | Obtain DCT Sign-off from Business | SyWay A2D Data Team |
| 2 | Syniti will provide load file | Syniti |
| 3 | Go to <Load Tool> | SyWay A2D Data Team |
| 4 | Load 3 records for "Create Maintenance Plan" function (IP01) to validate if data is loaded successfully without errors | SyWay A2D Data Team |
| 5 | Proceed with full load if step 4 is validated | SyWay A2D Data Team |
| 6 | Validate few records loaded by accessing standard transactions from S/4HNA E.g. IP03 | SyWay A2D Data Team |
| 7 | Generate post load report if step 6 is validated | SyWay A2D Data Team |
Load Phase and Dependencies
Identify the phase as to “when” the load for this object will occur. <Pre-Cutover, Cutover, Post Cutover> and list the steps that need to occur before the load can commence
Configuration
List the Configurations required before loading can commence
| Item # | Configuration Item |
|---|---|
| 1 | Maintenance Plan Category |
| 2 | Maintenance Strategy |
| 3 | Maintenance Plan Sort Field details |
| 4 | Number Ranges for Work Plan & Item |
| 5 | System Condition |
| 6 | Priorities |
| 7 | Planning Plant |
| 8 | Order Type |
| 9 | Task List Type |
| 10 | Unit of Measure |
| 11 | Planner group |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
1002 | Equipment |
1003 | Functional Location |
1005 | Task List |
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 Type | Error Description | Action 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 Authorization Group | 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 Notification Type | 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
| Task | Action |
|---|---|
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
| Task | Action |
|---|---|
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
| Task | Action |
|---|---|
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
| Task | Action |
|---|---|
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.
- 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
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.