| Status | Lead Approval |
|---|---|
| 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.
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
- 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). | 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
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
Task List Data strictly adheres to the Master Data Standard. The complete information of the key fields that hold the Maintenance plan and item information follows the Master Data Standard document that is located here .
The technical design of the target for this conversion approach.
| 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 |
| MPLA | STRAT | STRAT | Maintenance strategy | CHAR | 6 | R |
| RMIPM | MEHRFACH_Z | MEHRFACH_Z | Multiple counter plan | CHAR | 1 | NU |
| RMIPM | WSET | WSET | Cycle set for multiple counter plan | CHAR | 6 | NU |
| MPLA | WPTXT | WPTXT | Maintenance Plan Text | CHAR | 40 | R |
| MPLA | VSPOS | VERSCHPLUS | NUMC | 3 | C | |
| MPLA | TOPOS | TOLERPLUS | Tolerance for Late Completion (%) | NUMC | 3 | C |
| MPLA | TONEG | TOLERNEG | Tolerance for Early Completion (%) | NUMC | 3 | C |
| MPLA | VSNEG | VERSCHNEG | Shift Factor for Early Completion | NUMC | 3 | C |
| MPLA | SFAKT | SFAKT | Cycle modification factor | DEC | 3(2) | C |
| MPLA | FABKL | FABKL | Factory calendar key | CHAR | 2 | NU |
| 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 | HUNIT | HUNIT | Unit in scheduling interval | UNIT | 3 | C |
| MPLA | CALL_CONFIRM | CALL_CONFIRM | Only Create New Call Object After Completing Predecessor | CHAR | 1 | C |
| MPLA | STADT | STADT | Start date | DATS | 8 | C |
| RMIPM | ZEIT | TIME_KNZ | Indicator for selection of time-based maintenance | CHAR | 1 | C |
| MPLA | STICH | TERMKNZ | Scheduling indicator | CHAR | 1 | C |
| MPLA | PLAN_SORT | PLAN_SORT | Sort field for maintenance plans | CHAR | 20 | R |
| MPLA | BEGRU | IAUTG | Technical object authorization group | CHAR | 4 | NU |
| RMIPM | STTAG | MP_STTAG | Key Date | DATS | 8 | C |
| MPLA | ENDDT_FOR_SCHED | EAM_ENDDT_FOR_SCHED | End Date for Scheduling | DATS | 8(0) | C |
| MPOS | WAPOS | WAPOS | Maintenance item | CHAR | 16(0) | S |
| MPOS | PSTXT | POSTXT | Item Short Text | CHAR | 40(0) | R |
| MPLA | TPLNR | TPLNR | Functional Location | CHAR | 30 | R |
| MPLA | EQUNR | EQUNR | Equipment Number | CHAR | 18 | C |
| MPOS | BAUTL | BAUTL | Assembly | CHAR | 40(0) | NU |
| MPOS | IWERK | IWERK | Maintenance Planning Plant | CHAR | 4(0) | S |
| MPOS | AUART | AUFART | Order Type | CHAR | 4(0) | R |
| RMIPM | GEWERK | GEWRK | Main work center for maintenance tasks | CHAR | 8 | S |
| RMIPM | WERGW | WERGW | Plant associated with main work center | CHAR | 4 | S |
| MPOS | PRIOK | PRIOK | Priority | CHAR | 1(0) | R |
| MPOS | GSBER | GSBER | Business Area | CHAR | 4(0) | NU |
| MPOS | PLNTY | PLNTY | Task List Type | CHAR | 1(0) | R |
| MPOS | PLNNR | PLNNR | Key for Task List Group | CHAR | 8(0) | R |
| MPOS | PLNAL | PLNAL | Group Counter | CHAR | 2(0) | R |
| MPOS | WPGRP | INGRP | Planner Group for Customer Service and Plant Maintenance | CHAR | 3 | (waiting for confirmation in MDS) |
| MPOS | APFKT | APFKT | Execution factor for whole task list | DEC | 3(0) | C |
| MPOS | ANLZU | ANLZU | System Condition | CHAR | 1(0) | C |
| MPOS | SERIALNR | GERNR | Serial Number | CHAR | 18 | NU |
| MPOS | SERMAT | MATNR | Material Number | CHAR | 40(0) | NU |
| RMIPM | OFFS1 | WOFFS1 | Maintenance package offset | CHAR | 22 | NU |
| RMIPM | PAK_TEXT | TXZYKLUS | Text for maintenance package/cycle (time/performance) | CHAR | 30 | NU |
| MMPT | POINT | IMRC_POINT | Measuring Point | CHAR | 12 | C |
| MMPT | ZYKL1 | DZYK_ZEIT | Maintenance package cycle/offset | FLTP | 16(16) | S |
| MMPT | ZEIEH | DZEIEH | Unit for the performance of maintenance tasks | UNIT | 3 | S |
| MITEM_OBJLIST_D | EQUIPMENT | EQUNR | Equipment Number | CHAR | 18(0) | C |
| MITEM_OBJLIST_D | FUNCTIONALLOCATION | Functional location | TPLNR_UNCONVERTED | CHAR | 30(0) | C |
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 Item as 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 |
|---|---|---|---|---|
| ; |
|
|
|
|
| : |
|
|
|
|
| :: |
|
|
|
|
| ? | ||||
| / |
|
|
|
|
| @ |
|
|
|
|
| & |
|
|
|
|
| = |
|
|
|
|
| + |
|
|
|
|
| $ |
|
|
|
|
| % | ||||
| | | ||||
| [ | ||||
| ] | ||||
| " |
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 . There are 2 possibilities:
- The data exists. connects to the source and loads the data into . 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
| 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 | Must reference to active Maintenance Plan category in S4/HANA (T399W) |
| MPLA-WPTXT | Maintenance Plan text | 40 Char text |
MPLA-STRAT | Maintenance strategy | Must be a valid strategy. Must be the same strategy as the task list strategy |
MPLA-HORIZ_QUALIFIER | Calculation Type of Call Horizon | Default to "% " if blank |
MPLA-ABRHO | Scheduling Period | Default to "3" YR, if blank |
MPLA-HUNIT | Unit in scheduling interval | Default to "YR" if if blank and ABRHO is blank |
MPLA-PLAN_SORT | Sort field for maintenance plans | Must reference to active Sort field for maintenance plans in S4/HANA (T399G) |
MPOS-PSTXT | Item Short Text | Description shall be defined as Frequency + TOT + Asset Tag |
MPLA-TPLNR | Functional Location | Must reference to active Functional Location in S4/HANA (IFLO) |
| MPLA-EQUNR | Equipment Number | Must reference to active Equipment Number in S4/HANA (EQUI) Can be Blank only if FLOC is updated. |
| MPOS-AUFART | Order Type | Must reference to active Order Type in S4/HANA (T003O). Default to YA02 |
| MPOS-PRIOK | Priority | Must reference to active Priority in S4/HANA (T356) |
| MPOS-PLNTY | Task List Type | Must reference to active Task List Type Task List Type (TCA01) |
| MPOS-PLNNR | Key for Task List Group | Must reference to active Key for Task List Group in S4/HANA (PLKO) |
| MPOS-PLNAL | Group Counter | Group - Group Counter CT shall be equal to the Technical Object CT. |
RMIPM-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. |
Extraction Dependencies
| 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 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
- 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 |
|---|---|---|---|---|---|---|---|---|---|
| 1 | PF2, WP2 | MPLA | HORIZ_QUALIFIER | Calculation Type of Call Horizon | S/4HANA | MPLA | HORIZ_QUALIFIER | Calculation Type of Call Horizon | If no legacy data provided, default to "%" |
| 2 | PF2, WP2 | MPLA | ABRHO | Scheduling Period | S/4HANA | MPLA | ABRHO | Scheduling Period | If no legacy data provided, default to "3YR" |
| 3 | PF2, WP2 | MPLA | HUNIT | Unit in scheduling interval | S/4HANA | MPLA | HUNIT | Unit in scheduling interval | If no legacy data provided, default to "Yr" |
| 4 | PF2, WP2 | MPLA | TPLNR | Functional Location | S/4HANA | MPLA | TPLNR | Functional Location | Equipment field must be blank. System Generated if Equipment is Updated |
| 5 | PF2, WP2 | 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 |
| 6 | PF2, WP2 | MPOS | PLNAL | Group Counter | S/4HANA | MPOS | PLNAL | Group Counter | Group - Group Counter CT must be same as the Technical Object CT |
| 7 | PF2, WP2 | MPOS | POSTXT | Item Short Text | S/4HANA | MPOS | POSTXT | Item Short Text | Description shall be defined as Frequency + TOT + Asset Tag |
| 8 | PF2, WP2 | MPLA | MPTYP | Maintenance plan category | S/4HANA | MPLA | MPTYP | Maintenance plan category | Default to "PM" |
| 9 | PF2, WP2 | MPLA | WPTXT | Maintenance Plan Text | S/4HANA | MPLA | WPTXT | Maintenance Plan Text | Maintenance Plan description must match Task list Description |
| 10 | PF2, WP2 | MPOS | AUFART | Order Type | S/4HANA | MPOS | AUFART | Order Type | Default to "YA02" |
| 11 | PF2, WP2 | MMPT | POINT | Measuring Point | S/4HANA | MMPT | POINT | Measuring Point | Updated if the first 2 Chars of the Strategy = 02. |
| 12 | PF2, WP2 | MPLA | VSPOS | Shift Factor for Late Completion | S/4HANA | MPLA | VSPOS | Shift Factor for Late Completion | If no legacy data provided, default to "0" |
| 13 | PF2, WP2 | MPLA | TOPOS | Tolerance for Late Completion (%) | S/4HANA | MPLA | TOPOS | Tolerance for Late Completion (%) | If no legacy data provided, default to "10%" |
| 14 | PF2, WP2 | MPLA | VSNEG | Shift Factor for Early Completion | S/4HANA | MPLA | VSNEG | Shift Factor for Early Completion | If no legacy data provided, default to '0" |
| 15 | PF2, WP2 | MPLA | TONEG | Tolerance for Early Completion (%) | S/4HANA | MPLA | TONEG | Tolerance for Early Completion (%) | If no legacy data provided, default to "10%" |
| 16 | PF2, WP2 | MPLA | SFAKT | Cycle modification factor | S/4HANA | MPLA | SFAKT | Cycle modification factor | If no legacy data provided, default to "1" |
| 17 | PF2, WP2 | MPLA | CALL_CONFIRM | Only Create New Call Object After Completing Predecessor | S/4HANA | MPLA | CALL_CONFIRM | Only Create New Call Object After Completing Predecessor | If no legacy data provided, default to blank. System Generated if Equipment is Updated |
| 18 | PF2, WP2 | MPLA | STADT | Start date | S/4HANA | MPLA | STADT | Start date | If no legacy data provided, default to blank |
| 19 | PF2, WP2 | RMIPM | ZEIT | Indicator for selection of time-based maintenance | S/4HANA | RMIPM | ZEIT | Indicator for selection of time-based maintenance | If no legacy data provided, default to "X" |
Transformation Mapping
| 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
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
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
Configuration
| Item # | Configuration Item |
|---|---|
1 | T399W - Maintenance plan category |
2 | T351 - Maintenance strategy |
3 | T399G - Maintenance Plan Sort Field details |
4 | Number Ranges for Work Plan & Item |
5 | T357M - System Condition |
6 | T356 - Priorities details |
7 | T399I - Maintenance Planning Plants |
8 | T003O - Order Types details |
9 | T001W - Plants/Branches details |
10 | TCA01 - Task List Type |
11 | T006 - Units of Measurement details |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
1002 | EQUI - Equipment |
1003 | IFLO - Functional Location |
1005 | PLKO - Task List |
1012 | IMPTT - Measuring point |
1017 | T351 - Maintenance Strategy |
Error Handling
| 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
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
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
Change log
Workflow history
| Title | Last Updated By | Updated | Status | |
|---|---|---|---|---|
| There are no pages at the moment. | ||||