| Status | e |
|---|---|
| Owner | |
| Stakeholders | The business stakeholders involved in making, reviewing, and endorsing this decision. Type @ to mention people by name |
Purpose
The purpose of this document is to define the conversion approach to create Maintenance Plan and Item in S/4 HANA.
Legacy Plant Maintenance 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:
- have at least 1 valid maintenance Item
Maintenance Plan from legacy system is not relevant if:
- Maintenance plan marked for deletion
Maintenance Item within each maintenance plan is considered relevant if:
- 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; and
- 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.
| 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). | 69,594 | S/4HANA | 69,594 |
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). | 73,310 | S/4HANA | 73,310 |
Additional Information
Multi-language Requirement
EAM Class description will be made available in English.
Multi language is supported for EAM Class. Login via a different language will have its description displayed in the logon language if the language key is maintained in the Class.
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
Task List 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>.
The technical design of the target for this conversion approach.
MPLA - Maintenance Header
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| MPLA | WARPL | WARPL | Maintenance Plan | CHAR | 12 | S |
| MPLA | MPTYP | MPTYP | Maintenance plan category | CHAR | 2 | R. Must exist in T399W |
| MPLA | STRAT | STRAT | Maintenance strategy | CHAR | 6 | R. Must exist in T351 |
| MPLA | WPTXT | WPTXT | Maintenance Plan Text | CHAR | 40 | R |
| MPLA | VSPOS | VERSCHPLUS | Shift Factor for Late Completion | NUMC | 3 | O |
| MPLA | TOPOS | TOLERPLUS | Tolerance for Late Completion (%) | NUMC | 3 | O |
| MPLA | VSNEG | VERSCHNEG | Shift Factor for Early Completion | NUMC | 3 | O |
| MPLA | SFAKT | SFAKT | Cycle modification factor | DEC | 3(2) | O |
| MPLA | FABKL | FABKL | Factory calendar key | CHAR | 2 | O, Must exist in TFACD |
| MPLA | HORIZ | HORIZONT | Call horizon for maintenance plan calls | NUMC | 3 | R |
| MPLA | HORIZ_QUALIFIER | EAM_CC_CALLHORIZON_QUALIFIER | Calculation Type of Call Horizon | CHAR | 1 | R |
| MPLA | ABRHO | ABRHO | Scheduling Period | NUMC | 3 | R |
| MPLA | CALL_CONFIRM | CALL_CONFIRM | Only Create New Call Object After Completing Predecessor | CHAR | 1 | O |
| MPLA | STADT | STADT | Start date | DATS | 8 | O |
| MPLA | STICH | TERMKNZ | Scheduling indicator | CHAR | 1 | O |
| MPLA | PLAN_SORT | PLAN_SORT | Sort field for maintenance plans | CHAR | 20 | R. Must exist in T399G |
| MPLA | BEGRU | IAUTG | Technical object authorization group | CHAR | 4 | NU. |
| MPLA | AEKNZ | AEKNZ | Change indicator | CHAR | 1 | |
| MPLA | ERSDT | EDATUM | Date of creation | DATS | 8 | |
| MPLA | ERNAM | ERNAM | Name of Person who Created the Object | CHAR | 12 | |
| MPLA | AEDAT | AEDAT | Changed On | DATS | 8 | |
| MPLA | AENAM | AENAM | Name of Person Who Changed Object | CHAR | 12 | |
| MPLA | ERKNZ | ERKNZ | Creation indicator | CHAR | 1 | |
| MPLA | EQUNR | EQUNR | Equipment Number | CHAR | 18 | Must exist in EQUI |
| MPLA | TPLNR | TPLNR | Functional Location | CHAR | 30 | Must exist in IFLO |
| MPLA | KUNUM | KUNUM | Customer Number | CHAR | 10 | Must exist in KNA1 |
| MPLA | LTKNZ | MPLTX | Long Text Indicator | CHAR | 1 | |
| MPLA | LVORM | ABSTOP | Indicator: maintenance plan locked against calls | CHAR | 1 | |
| MPLA | ANZPS | ANZMPOS | Number of maintenance items in the maintenance plan | NUMC | 4 | |
| MPLA | ABNUM | ABNUM | Maintenance Plan Call Number | INT4 | 10 | |
| MPLA | LANGU | MPLANGU | Language key of the long text | LANG | 1 | Must exist to T002 |
| MPLA | TONEG | TOLERNEG | Tolerance for Early Completion (%) | NUMC | 3 | |
| MPLA | TGOON | TGON | Scheduling to reoccur when lead float reached | NUMC | 3 | |
| MPLA | HORIZ_DAYS | HORIZONT | Call horizon for maintenance plan calls | NUMC | 3 | |
| MPLA | ANDOR | ANDOR | Indicator for OR or AND link | CHAR | 1 | |
| MPLA | KNAUT | KNZABR | Reserved | CHAR | 1 | |
| MPLA | OBJNR | J_OBJNR | Object number | CHAR | 22 | Must exist in ONR00 |
| MPLA | HUNIT | HUNIT | Unit in scheduling interval | UNIT | 3 | Must exist in T006 |
| MPLA | SZAEH | SZAEHC | Start counter reading | CHAR | 22 | |
| MPLA | PUFFP | PUFF_VORL | Lead Float in Days | NUMC | 3 | |
| MPLA | PUFFN | PUFF_NACHL | Follow-up float in days | NUMC | 3 | |
| MPLA | START_DATE | DATE_START | Start Date for Scheduling | DATS | 8 | |
| MPLA | START_TIME | TIME_START | Start Time for Scheduling | TIMS | 6 | |
| MPLA | CALL_UPDATE_IND | IND_CALL_UPDATE | Indicator for Adapting Basic Dates of Call Object | CHAR | 1 | |
| MPLA | IND_MPLA_API | IND_MPLA_API | Maintenance Plan Was Created/Changed by API | CHAR | 2 | |
| MPLA | MCP_SF | MCP_SF | Shift Factor for Multiple Counter Plan | CHAR | 1 |
MPOS - Maintenance Item
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| MPOS | MANDT | MANDT | Client | CLNT | 3(0) | Must exist in T000 |
| MPOS | WAPOS | WAPOS | Maintenance item | CHAR | 16(0) | |
| MPOS | WARPL | WARPL | Maintenance Plan | CHAR | 12(0) | Must exist in MPLA |
| MPOS | WSTRA | STRAT | Maintenance Strategy | CHAR | 6(0) | Must exist in T351 |
| MPOS | WPPOS | WPPOS | Item in the maintenance plan | NUMC | 4(0) | |
| MPOS | PSTXT | POSTXT | Item Short Text | CHAR | 40(0) | |
| MPOS | EQUNR | EQUNR | Equipment Number | CHAR | 18(0) | Must exist in EQUI |
| MPOS | OBKNR | OBJKNR | Object list number | INT8 | 19(0) | |
| MPOS | ERKNZ | ERKNZ | Creation Indicator | CHAR | 1(0) | |
| MPOS | AEKNZ | AEKNZ | Change indicator | CHAR | 1(0) | |
| MPOS | ERNAM | ERNAM | Name of Person who Created the Object | CHAR | 12(0) | |
| MPOS | ERSDT | EDATUM | Date of creation | DATS | 8(0) | |
| MPOS | AEDAT | AEDAT | Date of Last Change | DATS | 8(0) | |
| MPOS | AENAM | AENAM | Name of person who changed object | CHAR | 12(0) | |
| MPOS | PLNTY | PLNTY | Task List Type | CHAR | 1(0) | Must exist in TCA01 |
| MPOS | PLNNR | PLNNR | Key for Task List Group | CHAR | 8(0) | |
| MPOS | PLNAL | PLNAL | Group Counter | CHAR | 2(0) | |
| MPOS | STATUS | MPSTAT | Maintenance Item Status | CHAR | 1(0) | |
| MPOS | LTKNZ | MPLTX | Long Text Indicator | CHAR | 1(0) | |
| MPOS | WPGRP | INGRP | Planner Group for Customer Service and Plant Maintenance | CHAR | 3(0) | Must exist in T024I |
| MPOS | OBJTY | CR_OBJTY | Object types of the CIM resource | CHAR | 2(0) | |
| MPOS | GEWRK | LGWID | Object ID of the Work Center | NUMC | 8(0) | Must exist in CRID |
| MPOS | IWERK | IWERK | Maintenance Planning Plant | CHAR | 4(0) | Must exist in T399I |
| MPOS | LANGU | MPLANGU | Language key of the long text | LANG | 1(0) | |
| MPOS | ILOAN | ILOAN | Location and account assignment for technical object | CHAR | 12(0) | Must exist in ILOA |
| MPOS | ILOAI | ILOAI | ILOA Individual | CHAR | 1(0) | |
| MPOS | LAUFN | LAUFN | Order number | CHAR | 12(0) | Must exist in AUFK |
| MPOS | BAUTL | BAUTL | Assembly | CHAR | 40(0) | Must exist in MARA |
| MPOS | ANLZU | ANLZU | System Condition | CHAR | 1(0) | |
| MPOS | AUART | AUFART | Order Type | CHAR | 4(0) | Must exist in T003O |
| MPOS | INACT | INACT | Indicator that maintenance item is inactive | CHAR | 1(0) | |
| MPOS | ILART | ILA | Maintenance activity type | CHAR | 3(0) | Must exist in T353I |
| MPOS | GSBER | GSBER | Business Area | CHAR | 4(0) | Must exist in TGSB |
| MPOS | OBJNR | J_OBJNR | Object number | CHAR | 22(0) | Must exist in ONR00 |
| MPOS | IND_ABRVO | IND_ABRVO | Indicator showing settlement rule maintained | CHAR | 1(0) | |
| MPOS | PSPEL | PS_PSP_PNR | Work Breakdown Structure Element (WBS Element) | NUMC | 8(0) | |
| MPOS | STD_NETZ | PLNNR | Key for Task List Group | CHAR | 8(0) | |
| MPOS | STD_AVO | PLNKN | Number of the Task List Node | NUMC | 8(0) | |
| MPOS | KDAUF | VBELN_VA | Sales Document | CHAR | 10(0) | |
| MPOS | KDPOS | POSNR_VA | Sales Document Item | NUMC | 6(0) | |
| MPOS | MITYP | MITYP | Maintenance item category | CHAR | 2(0) | Must exist in T399P |
| MPOS | BSTNR | BSTNR | Purchase order number | CHAR | 10(0) | |
| MPOS | BSTPO | BSTPO | Purchase order item number | NUMC | 5(0) | |
| MPOS | PACKNO | PACKNO | Package number | NUMC | 10(0) | |
| MPOS | NETPR | NETPR | Net Price | CURR | 11(2) | |
| MPOS | WAERS | WAERS | Currency Key | CUKY | 5(0) | Must exist in TCURC |
| MPOS | SAKTO | KSTAR | Cost Element | CHAR | 10(0) | |
| MPOS | AUFNR | ILOM_ORDST | Settlement order | CHAR | 12(0) | |
| MPOS | APFKT | APFKT | Execution factor for whole task list | DEC | 3(0) | |
| MPOS | SCRRENTY | SCREENTY | SCREEN TYPE: for order-order category (see domain) | CHAR | 4(0) | |
| MPOS | SERIALNR | GERNR | Serial Number | CHAR | 18(0) | |
| MPOS | SERMAT | MATNR | Material Number | CHAR | 40(0) | Must exist in MARA |
| MPOS | DEVICEID | DEVICEID | Additional Device Data | CHAR | 40(0) | |
| MPOS | QMNUM | QMNUM | Notification Number | CHAR | 12(0) | Must exist in QMEL |
| MPOS | QMART | QMART | Notification Type | CHAR | 2(0) | Must exist in TQ80 |
| MPOS | LBLNI | LBLNI | Entry Sheet Number | CHAR | 10(0) | |
| MPOS | TASK_DETERMINE | TASK_DETERMINE | Automatic task determination in the notification | CHAR | 1(0) | |
| MPOS | PRIOK | PRIOK | Priority | CHAR | 1(0) | Must exist in T356 |
| MPOS | QMKAT | QMKAT | Catalog Type - Coding | CHAR | 1(0) | |
| MPOS | QMGRP | QMGRP | Code Group - Coding | CHAR | 8(0) | |
| MPOS | QMCOD | QMCOD | Coding | CHAR | 4(0) | |
| MPOS | PHYNR | QPHYSPRNR | Material Sample Number | CHAR | 12(0) | |
| MPOS | ART | QPART | Inspection Type | CHAR | 8(0) | |
| MPOS | PRUEFLOS | QPLOS | Inspection Lot Number | NUMC | 12(0) | |
| MPOS | TSTMP_BW | TSTMP_BW_EXT | Time Stamp for BI Delta Extraction | DEC | 16(0) | |
| MPOS | NO_AUFRELKZ | NO_AUFRELKZ | Do Not Release Immediately | CHAR | 1(0) | |
| MPOS | DESNUM | /CUM/DESNUM | CU: Design Number | CHAR | 12(0) | Assigned to domain |
| MPOS | CYCLESEQIND | CYCLESETSEQ | Cycle Set Sequence | NUMC | 2(0) | |
| MPOS | ADPSP | ADDCOMPARE_CORE | Reference Element PM/PS | CHAR | 40(0) | |
| MPOS | IND_MPOS_API | IND_MPOS_API | Maintenance Item Was Created/Changed by API | CHAR | 2(0) | |
| MPOS | RBNR | RBNR | Catalog Profile | CHAR | 9(0) | Must exist in T352C |
| MPOS | RBNRI | EAM_RBNRI_MITEM | Origin of catalog profile | CHAR | 1(0) |
MMPT - Cycle definitions and Measing Points for Maintenance Plan details
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| MMPT | MANDT | MANDT | Client | CLNT | 3 | Must exist in T000 |
| MMPT | WARPL | WARPL | Maintenance Plan | CHAR | 12 | Must exist in MPLA |
| MMPT | NUMMER | DZAEHLER | Counter in control tables | NUMC | 2 | |
| MMPT | OPERATOR | PM_VERGL | Comparison operator for maint. package cycle duration | CHAR | 2 | |
| MMPT | ZYKL1 | DZYK_ZEIT | Maintenance package cycle/offset | FLTP | 16(16) | |
| MMPT | ZEIEH | DZEIEH | Unit for the performance of maintenance tasks | UNIT | 3 | Must exist in T006 |
| MMPT | PAK_TEXT | TXZYKLUS | Text for maintenance package/cycle (time/performance) | CHAR | 30 | |
| MMPT | LANGU | MLANG | Primary language for object texts | LANG | 1 | Must exist in T002 |
| MMPT | POINT | IMRC_POINT | Measuring Point | CHAR | 12 | Must exist in IMPTT |
| MMPT | OFFSET | DZYK_OFFZT | Start offset of a time-based maintenance package | FLTP | 16(16) | |
| MMPT | INAKTIV | INAKT_TERM | Indicator: event scheduling inactive | CHAR | 1 | |
| MMPT | NZAEH | NZAEH | Next planned counter reading | FLTP | 16(16) | |
| MMPT | ZAEHL | PAKETZAEHL | Maintenance Package Number | NUMC | 2 | Must exist in T351P |
| MMPT | KTEXTYZK | KTEXTZYK | Short text for the maintenance cycle (time/performance) | CHAR | 2 | |
| MMPT | CYCLESEQIND | CYCLESETSEQ | Cycle Set Sequence | NUMC | 2 | |
| MMPT | SETREPEATIND | IND_SET_REPEAT | Repeat Factor for Cycle Set Sequence | NUMC | 2 |
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>.
| ID | Criticality | Error Message/Report Description | Rule | Output | Source System |
|---|---|---|---|---|---|
1016-001 | C1 | Invalid, Inactive or no maintenance item attached to Maintenance Plan | Maintenance Plan as per Relevancy Criteria assigned with inactive or no Maintenance Items attached. | Maintenance Item | PF2, WP2 |
1016-002 | C1 | 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: | Task List | PF2, WP2 |
1016-003 | C2 | Active maintenance plans not triggered | TBD | Maintenance Plan Status | PF2, WP2 |
1016-004 | C3 | 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. | Technical Object, Task List, Strategy, Description | PF2, WP2 |
1016-005 | C1 | Invalid, Inactive or no Characteristic allocated to Maintenance Plan | Maintenance Plan as per Relevancy Criteria assigned with a Characteristic which does not belong below: | Characteristic | PF2, WP2 |
1016-006 | C1 | Invalid, Inactive or no Class allocated to Maintenance Plan | Maintenance Plan as per Relevancy Criteria assigned with a Class which does not belong below: | Class | PF2, WP2 |
1016-007 | C1 | Invalid, Inactive or no Equipment or Functional Location allocated to Maintenance Plan | Maintenance Plan as per Relevancy Criteria assigned with an Equipment or Functional Location which does not belong below: | Equipment, Functional Location | PF2, WP2 |
1016-008 | C1 | Invalid, Inactive or no Maintenance Strategy allocated to Maintenance Plan | Maintenance Plan as per Relevancy Criteria assigned with a Maintenance Strategy which does not belong below: | Maintenance Strategy | PF2, WP2 |
1016-009 | C1 | Invalid, Inactive or no Work Centres linked to Maintenance Plans | Maintenance Plan as per Relevancy Criteria assigned with a Work Centre which does not belong below: | Work Centre | PF2, WP2 |
1016-010 | C1 | Invalid, Inactive or no Maintenance Plans linked to Maintenance Items | Maintenance Item as per Relevancy Criteria assigned with no or inactive Maintenance Plan attached. | Maintenance Plan | PF2, WP2 |
1016-011 | C1 | Invalid or Inactive Measuring Point linked to Maintenance Plan | Maintenance Plan as per Relevancy Criteria assigned with a Measuring Point which does not belong below: | Measuring Point | PF2, WP2 |
1016-012 | C1 | Missing Maintenance Plan Descriptions | Task List as per Relevancy Criteria where there are blank Task ListDescriptions. | Maintenance Plan Description | PF2, WP2 |
1016-013 | C2 | Maintenance Plan Descriptions with Informal Words | Maintenance Plan as per Relevancy Criteria which contain [Informal Words] in the Maintenance Plan Description | Maintenance Plan Description | PF2, WP2 |
1016-014 | C1 | Maintenance Plan and Item Plant incorrect. | Maintenance Plan and Item as per Relevancy Criteria with Invalid Plant (T001W) | Plant | PF2, WP2 |
1016-015 | C1 | Maintenance Plan and Item UOM Missing / incorrect. | Maintenance Plan and Item as per Relevancy Criteria with no UoM Assigned or Invalid UoM (T006) | Unit of Measure | PF2, WP2 |
1016-016 | C1 | Invalid or no Planner Group linked to Maintenance Plan and Item | Maintenance Plan and Itemas per Relevancy Criteria with no Planner Group Assigned or Invalid Planner Group (T024I) | Planner Group | PF2, WP2 |
1016-017 | C1 | Maintenance Plan and Item Technical object authorization group incorrect. | Maintenance Plan and Item as per Relevancy Criteria with Invalid Authorization Group (T370F) | Authorization Group | PF2, WP2 |
1016-018 | C2 | Functional Item Planning Plant and Maintenance Plant are not the same. | Maintenance Item as per Relevancy Criteria with Planning Plant <> Maintenance Plant | Maintenance Plant, Planning Plant | PF2, WP2 |
Informal Words **
Group 1 | Group 2 | Group 3 | Group 4 | Group 5 |
|---|---|---|---|---|
*DNU | Delete | donot | Formerly | Old # |
.. | Deletion | DONT USE | From | Old[ ] |
/ | DELISTED | DON'T USE | Incorrect | PLEASE USE |
? | Discontinued | Dup Use | Invalid | Pls Use |
@ | Disposable | DUPLICATE | New | Previously |
^ | DNU | -DUPLICATE | NOT ACTIVE | Replace |
+ | Do Not | DUPLICATION | not in use | Replaced |
++ | Do Not Re | Duplicidad | Not Used | RESERVED |
£ | Do Not Sell | Duplikat | NOT VALID | Retired |
Defective | Do Not Use | Former | Obsolete | ZZDEL |
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
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 |
2 | Google Sheet report pre-populated with WP2 and WP2 information to be generated based on relevancy criteria. | 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
| Field Name | Field Description | Rule |
|---|---|---|
| ZHIS-WARPL | LEGACY MAINTENANCE PLAN | Reference information from WP2, WP2 |
| MPLA-WARPL | MAINTENANCE PLAN | Running number NNNNNNNN to NNNNNNNN for Maintenance Plan Category = XXX. |
| MPLA-MPTYP | MAINTENANCE PLAN CATEGORY | |
| MPLA-WPTXT | MAINTENANCE PLAN TEXT | 40 Char text |
MPLA-WSTRA | MAINTENANCE STRATEGY | Must be a valid strategy if not blank. Must be the same strategy as the task list strategy |
RMIPM-WSET | CYCLE SET | Drop down List (T351-STRAT where ANZP1 is blank) Must be blank for non Multi Counter (Scheduling Indicator is not 4) |
RMIPM-POINT | COUNTER | Must be blank for the following conditions:
|
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 | Data |
2 | Ensure that the necessary cleansing activities in legacy sources are complete | Data / Business |
3 | Ensure that create, change and deletion of master data is freeze in legacy Production system | Legacy IT |
| 4 | Extraction of Equipment, Functional Location and Task list completed based on relevancy rule | Business |
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 | In dspMigrate, select the wave –R3 S/HANA – Plant Maintenance | Syniti |
3 | Go to Process Area Launch and Process the Object – Maintenance Plan | Syniti |
4 | Execute the transformation to prepare the target ttMPLA, ttMPOS, ttOBJK, ttMMPT | Syniti |
5 | Review and Validate Error and Preload Reports | SyWay A2D Data Team |
6 | Generate Load Files | Syniti |
Transformation Rules
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
Transformation Mapping
Use the exact name and reference this section in the “Transformation rules” above| Mapping Table Name | Mapping Table Description |
|---|---|
xtSTRAT | Xref for maintenance strategy. Fields: zLegacySTRAT, zLegacyKTEXT, STRAT, KTEXT |
xtPOINT | Xref for measuring point. Fields: zLegacyPOINT, zLegacyPTTXT, POINT, PTTXT |
xtMATNR | Xref for material number. Fields: zLegacyMATNR, MATNR |
xtPLNNR | xref for task list. Fields: zLegacyPLNNR, PLNNR |
Assembly | Legacy Assembly XREF table |
xtTPLNR | Xref for functional location. Fields: zLegacyTPLNR, TPLNR |
xtEQUNR | Xref for equipment number. Fields: zLegacyEQUNR, EQUNR |
xtARBPL | Xref for Work Centre. Fields: zLegacyARBPL, ARBPL |
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 | Syniti will provide load file | Syniti |
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 | Planning Plants |
2 | Maintenance Plants |
3 | Number Ranges for Work Plan & Item |
4 | Sort Fields for Work Plans |
5 | Authorization Groups |
6 | System Condition |
7 | Order Type |
8 | Order Type Priority |
9 | Planner Groups |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
1002 | Equipment |
1003 | Functional location |
1005 | Task List |
1012 | Measuring point |
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 | SyWay A2D Data Team to verify that the Work order 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 Work order 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.