Purpose
The purpose of this document is to define the conversion approach to create Maintenance Plan and Item in S/4 HANA.
Legacy Maintenance Plan and Item is using a diverse range of formats across the different systems. There are instances where the same Maintenance Plan and Item is duplicated within and across sources. This results in data inconsistency. As per SyWay design, EAM Maintenance Plan and Item will be standardized.
Conversion Scope
The scope of this document covers the approach for converting active Maintenance Plan and Item from Legacy Source Systems into S/4HANA following the Maintenance Plan and Item Master Data Design Standard.
A Maintenance Plan is a scheduling framework that determines timing and frequency of preventive maintenance tasks. It can be:
- Time-based (e.g., every 6 months)
- Performance-based (e.g., every 10,000 operating hours)
- Strategy-based, using predefined maintenance strategies
Key features:
- Can include one or more maintenance items
- Drives the creation of maintenance calls (notifications/orders)
- Linked to a planning plant, which controls scheduling
A Maintenance Item specifies the actual task, technical object, and optionally a task list to be performed. It defines:
- The equipment, functional location, or object list to be maintained
- The task list (optional) describing detailed operations
- The cycle and offset for scheduling (if not using strategy)
Key features:
- Multiple items can be assigned to one plan
- Each item can have its own cycle and task list
- Enables tracking of maintenance history per object
The data from legacy system includes:
- Maintenance Plan (MPLA-WARPL) that has at least 1 relevant Maintenance Item (MPOS-WAPOS)
- Maintenance Items (MPOS-WAPOS) that has at least 1 valid task list based on Task List Relevancy Criteria (PLKO-PLNTY, PLKO-PLNNR, PLKO-PLNAL) relevancy
- Maintenance Items (MPOS-WAPOS) that has at least 1 relevant Material (MARA-MATNR), Functional Location (IFLOT-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
- Maintenance Items (MPOS-WAPOS) having Planning Maintenance Plant (MPOS-IWERK) in scope - Refer to Value Mapping: Plant (Maintenance Plant = Yes)
The data from legacy system excludes:
- Maintenance Plan (MPLA-WARPL) marked inactive (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: Active Maintenance Plan will be extracted from PF2 and WP2 | 70,000 | S/4HANA | 70,000 |
PF2, WP2 | Maintenance Items: Active Maintenance Item will be extracted from PF2 and WP2 | 74,000 | S/4HANA | 74,000 |
DCT | Maintenance Plan and Maintenance Item for plants which do not have data existing from PF2 and WP2 | TBD | S/4HANA | TBD |
Additional Information
Multi-language Requirement
Maintenance Plan description will be made available in English.
Multi language is supported for Maintenance Plan. Login via a different language will have its description displayed in the logon language if the language key is maintained in the Maintenance Plan.
Document Management
Not Applicable
Legal Requirement
Not Applicable
Special Requirements
Not Applicable
Target Design
The technical design of the target for this conversion approach.
1.Maintenance Plan
| 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 |
| 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 |
| MPLA | LTKNZ | MPLTX | Long Text Indicator | CHAR | 1 | System |
| 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 | POINT | IMRC_POINT | Measuring Point | CHAR | 12 | Conditional |
2.Maintenance Plan Long Text Header
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| STXH | TDOBJECT | TDOBJECT | Texts: application object | CHAR | 10 | Mandatory |
| STXH | TDNAME | TDOBNAME | Name | CHAR | 70 | Mandatory |
| STXH | TDID | TDID | Text ID | CHAR | 4 | Mandatory |
| STXH | TDSPRAS | SPRAS | Language Key | LANG | 1 | Mandatory |
3.Maintenance Plan Long Text Line
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| STXL | TDOBJECT | TDOBJECT | Texts: application object | CHAR | 10 | Mandatory |
| STXL | TDNAME | TDOBNAME | Name | CHAR | 70 | Mandatory |
| STXL | TDID | TDID | Text ID | CHAR | 4 | Mandatory |
| STXL | TDSPRAS | SPRAS | Language Key | LANG | 1 | Mandatory |
| STXL | CLUSTD_TAG | TDFORMAT | Tag column | CHAR | 1 | Mandatory |
| STXL | ROWCOUNT | ROWCOUNT | Row number | NUMC | 10 | Mandatory |
| STXL | CLUSTD_LINE | TDLINE | Text Line | CHAR | 72 | Mandatory |
Note:
- Long Text is not mandatory, only load when there is data
- One Long Text Header must have at least 1 Long Text Line
4.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 | IWERK | IWERK | Maintenance Planning Plant | CHAR | 4 | System |
| MPOS | AUART | AUFART | Order Type | CHAR | 4 | Mandatory |
| MPOS | PRIOK | PRIOK | Priority | CHAR | 1 | Mandatory |
| 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 |
Note: Each Maintenance Plan can have multiple Maintenance Items
5.Maintenance Item Long Text Header
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| STXH | TDOBJECT | TDOBJECT | Texts: application object | CHAR | 10 | Mandatory |
| STXH | TDNAME | TDOBNAME | Name | CHAR | 70 | Mandatory |
| STXH | TDID | TDID | Text ID | CHAR | 4 | Mandatory |
| STXH | TDSPRAS | SPRAS | Language Key | LANG | 1 | Mandatory |
6.Maintenance Item Long Text Line
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| STXL | TDOBJECT | TDOBJECT | Texts: application object | CHAR | 10 | Mandatory |
| STXL | TDNAME | TDOBNAME | Name | CHAR | 70 | Mandatory |
| STXL | TDID | TDID | Text ID | CHAR | 4 | Mandatory |
| STXL | TDSPRAS | SPRAS | Language Key | LANG | 1 | Mandatory |
| STXL | CLUSTD_TAG | TDFORMAT | Tag column | CHAR | 1 | Mandatory |
| STXL | ROWCOUNT | ROWCOUNT | Row number | NUMC | 10 | Mandatory |
| STXL | CLUSTD_LINE | TDLINE | Text Line | CHAR | 72 | Mandatory |
Note:
- Long Text is not mandatory, only load when there is data
- One Long Text Header must have at least 1 Long Text Line
7.Maintenance Item Object List
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| OBJK | OBKNR | OBJKNR | Object list number | INT8 | 19 | System |
| OBJK | OBZAE | OBJZA | Object list counters | INT4 | 10 | System |
| OBJK | SORTF | WARPL | Object list sort field | CHAR | 20 | System |
| OBJK | TPLNR | TPLNR | Functional Location | CHAR | 30 | Conditional |
| OBJK | EQUNR | EQUNR | Equipment Number | CHAR | 18 | Conditional |
Note: Each Maintenance Item can have multiple Objects
8.Maintenance Plan (Characteristics Values Header)
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| KLAH | KLART | KLASSENART | Class Type | CHAR | 3 | Mandatory |
| INOB | OBTAB | TABELLE | Name of Database Table for Object | CHAR | 30 | Mandatory |
| KLAH | CLASS | KLASSE_D | Class number | CHAR | 18 | Mandatory |
| INOB | OBJEK | CUOBN | Key of Object | CHAR | 90 | Mandatory |
| KLAH | STATU | KLSTATUS | Class Status | CHAR | 1 | Mandatory |
9.Maintenance Plan (Characteristics Values Allocation)
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| KLAH | KLART | KLASSENART | Class Type | CHAR | 3 | Mandatory |
| INOB | OBTAB | TABELLE | Name of Database Table for Object | CHAR | 30 | Mandatory |
| KLAH | CLASS | KLASSE_D | Class number | CHAR | 18 | Mandatory |
| INOB | OBJEK | CUOBN | Key of Object | CHAR | 90 | Mandatory |
| CABN | ATNAM | ATNAM | Characteristic Name | CHAR | 30 | Mandatory |
| AUSP | ATWRT | ATWRT | Characteristic Value | CHAR | 30 | Mandatory |
| KSML | POSNR | KPOSNR | Item Number | CHAR | 3 | Mandatory |
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-Maintenance Plan Category: Not PM | Maintenance Plan Category not "PM" | Maintenance Plan, Plant, Maintenance Plan Category | PF2, WP2 |
1016-008 | C1 | Maintenance Plan-Order Type: Not "YA02" | Order Type not "YA02" | Maintenance Plan, Plant, Order Type | PF2, WP2 |
1016-009 | C1 | Maintenance Plan-Scheduling Indicator: Not blank, 1, 2 or 3 | Scheduling Indicator not blank, 1, 2 or 3 | Maintenance Plan, Plant, Scheduling Indicator | PF2, WP2 |
1016-010 | 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-011 | 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-012 | 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-013 | 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-014 | 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-015 | 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-016 | 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-017 | 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-018 | C3 | 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-019 | C1 | Maintenance Item: Duplicate Maintenance Plan Items by Technical Object, Task List, Strategy, Description | Maintenance Plan Items as per Relevancy Criteria where there is more than one Technical Object + Task List + Strategy + Description Combination. | Maintenance Plan, Plant, Technical Object, Task List, Strategy, Description | PF2, WP2 |
1016-020 | 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-021 | C2 | 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-022 | C1 | 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-023 | 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-024 | 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 |
1016-025 | C2 | Maintenance Plan-Status Profile: contains data but not mapped to any field for migration | Field contains data but not mapped to any field for migration | Maintenance Plan, Plant, Status Profile | PF2, WP2 |
1016-026 | C2 | Maintenance Plan-User Status: contains data but not mapped to any field for migration | Field contains data but not mapped to any field for migration | Maintenance Plan, Plant, User Status | PF2, WP2 |
1016-027 | C2 | Maintenance Item-Business Area: contains data but not mapped to any field for migration | Field contains data but not mapped to any field for migration | Maintenance Item, Plant, Business Area | PF2, WP2 |
1016-028 | C2 | Maintenance Item-Maintenance Activity Type: contains data but not mapped to any field for migration | Field contains data but not mapped to any field for migration | Maintenance Item, Plant, Maintenance Activity Type | PF2, WP2 |
1016-029 | C2 | Maintenance Item-Maintenance item category: contains data but not mapped to any field for migration | Field contains data but not mapped to any field for migration | Maintenance Item, Plant, Maintenance item category | PF2, WP2 |
1016-030 | C2 | Maintenance Item-Do Not Release Immediately: Item marked for Do Not Release | Field contains data but not mapped to any field for migration | Maintenance Item, Plant, Do Not Release Immediately | PF2, WP2 |
1016-031 | C2 | Maintenance Item-Revision for Plant Maintenance and Customer Service: contains data but not mapped to any field for migration | Field contains data but not mapped to any field for migration | Maintenance Item, Plant, Revision for Plant Maintenance and Customer Service | PF2, WP2 |
1016-032 | C2 | Maintenance Item-User Status: contains data but not mapped to any field for migration | Field contains data but not mapped to any field for migration | Maintenance Item, Plant, User Status | 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.
- The extracted report will be loaded into the required structure using the DCT.
- Standardization activities (including deduplication, standardization and additions) will be carried out within the DCT.
Delta Data Management: Initial collection will be done via the report and one-time load to the DCT will be performed. Any delta after the initial collection within the DCT will require business to take due diligence to ensure any subsequent delta cleansing is verified and aligned within the DCT.
Note: All rules specified below should be documented as a tooltip in the DC Page.
Format:
- Line 1: Mandatory / Conditional
- Line 2: Remaining text
1.Maintenance Plan Data Construction Rules
| Field Name | Field Description | Rule |
|---|---|---|
| zLegacyWARPL | Legacy Maintenance Plan | Mandatory. Key field |
WSTRA | Maintenance strategy | Mandatory. Must reference to active Strategy in Maintenance Strategy DCT. Naming Convention as follows: XX_XXX E.g - 01_001 |
| TOPOS | Tolerance for Late Completion (%) | Conditional. Numeric values only, values from 0 to 100 Note: Will default to "10" if blank |
| TONEG | Tolerance for Early Completion (%) | Conditional. Numeric values only, values from 0 to 100 Note: Will default to "10" if blank |
| SFAKT | Cycle modification factor | Conditional. Note: Will default to "1" if blank |
FBKL | Time-factory caldr | Conditional. Select from configuration (TFACD) |
HORIZ | Call horizon for maintenance plan calls | Mandatory. Numeric values only, values from 0 to 100 Note: Will default to "100" if blank |
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 for Scheduling Period | Conditional. Note: Will default to "YR" if blank |
CALL_CONFIRM | Completion Requirement | Conditional. Allowed values: "X" or blank |
STADT | Start date | Conditional. All Date format should be DDMMYYYY |
STICH | Scheduling indicator | Conditional. Allowed values: "1", "2" or blank |
PLAN_SORT | Sort field for maintenance plans | Mandatory. Select from configuration (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. |
POINT | Measuring Point | Conditional. Must reference to active Measuring Point in Measuring Point DCT. Must not be blank if the first 2 Chars of the Strategy = "02" Must be blank if the first 2 Chars of the Strategy <> " 02" |
ENDDT_FOR_SCHED | End Date for Scheduling | Conditional. All Date format should be DDMMYYYY |
2.Maintenance Plan Long Text Line Data Construction Rules
| Field Name | Field Description | Rule |
|---|---|---|
| zLegacyWARPL | Legacy Maintenance Plan | Mandatory. Key to link to Maintenance Plan |
| TDSPRAS | Language Key | Mandatory Must be either one of the following: English(E) , French(F), Italian(I), Mandarin(1), Portuguese(including Brazilian Portuguese)(P), German(D) and Spanish(S) |
| WPTXT | Maintenance Plan Text | Mandatory. Not editable Note: This field is needed for clarity of Maintenance Plan |
| ROWCOUNT | Row number | Mandatory. Must be unique and ascending sequential number |
| CLUSTD_LINE | Text Line | Mandatory Free Text |
3.Maintenance Item Data Construction Rules
| Field Name | Field Description | Rule |
|---|---|---|
| zLegacyWARPL | Legacy Maintenance Plan | Mandatory. Key to link to Maintenance Plan |
| zLegacyWAPOS | Legacy Maintenance Item | Mandatory. Key field |
PSTXT | Item Short Text | Mandatory. Free text. Note: Description must be defined as Frequency + TOT + Asset Tag. |
| TPLNR | Functional Location | Mandatory. Must reference to active Functional Location in Functional Location DCT |
| EQUNR | Equipment Number | Conditional. Must reference to active Equipment Number (EQUI) Can be Blank only if FLOC is updated. |
| GEWRK | Main work center for maintenance tasks | Conditional. Must reference active Work Centre (CRHD) Note: Will default to the value derived from the technical object, if blank |
| WPGRP | Planner Group for Customer Service and Plant Maintenance | Conditional. Select from configuration (T024I). Default to the value derived from the technical object. Update the value if provided by business (Takes Precedence). |
| PRIOK | Priority | Mandatory. Select from configuration (T356). |
| PLNTY | Task List Type | Mandatory. Must reference to active Task List Type in Task List Header DCT |
| PLNNR | Key for Task List Group | Mandatory. Must reference to active Key for Task List Group in Task List Header DCT |
| PLNAL | Group Counter | Mandatory. Must reference to active Group Counter in Task List Header DCT. Group - Group Counter CT shall be equal to the Technical Object CT. |
| APFKT | Execution factor for whole task list | Conditional. Note: Will default to to "1" if blank |
| ANLZU | System Condition | Conditional. Select from configuration (T357M) |
4.Maintenance Plan Long Text Line Data Construction Rules
| Field Name | Field Description | Rule |
|---|---|---|
| zLegacyWARPL | Legacy Maintenance Plan | Mandatory. Key to link to Maintenance Plan |
| zLegacyWAPOS | Legacy Maintenance Item | Mandatory. Key to link to Maintenance Item |
| TDSPRAS | Language Key | Mandatory Must be either one of the following: English(E) , French(F), Italian(I), Mandarin(1), Portuguese(including Brazilian Portuguese)(P), German(D) and Spanish(S) |
| KTEXT | Description | Mandatory. Not editable |
| ROWCOUNT | Row number | Mandatory. Must be unique and ascending sequential number |
| CLUSTD_LINE | Text Line | Mandatory Free Text |
5.Maintenance Item Object List Data Construction Rules
| Field Name | Field Description | Rule |
|---|---|---|
| zLegacyWARPL | Legacy Maintenance Plan | Mandatory. Key to link to Maintenance Plan |
| zLegacyWAPOS | Legacy Maintenance Item | Mandatory. Key field |
| SORTF | Object list sort field | Conditional. Must be unique and ascending sequential number starting from 1 |
| EQUNR | Equipment Number | Conditional. Must reference to active Equipment Number (EQUI) Can be Blank only if FLOC is updated. |
| TPLNR | Functional Location | Mandatory. Must reference to active Functional Location in Functional Location DCT |
6. Maintenance Plan Characteristic Data Construction Rules
| Field Name | Field Description | Rule |
|---|---|---|
| zLegacyWARPL | Legacy Maintenance Plan | Mandatory. Key to link to Maintenance Plan |
| ATNAM | Characteristic Name | Mandatory. Possible selection: "Allowed CT", "Discrete to the Asset" Characteristic Name and Class should exist in Characteristics DCT |
| ATWRT | Characteristic Value | Mandatory. If ATNAM = "Allowed CT" then input relevant Construction Type. If ATNAM = "Discrete to the Asset" then select "YES" or "NO" |
| POSNR | Item Number | Mandatory. Positive numeric values only. Must be unique and ascending sequential |
Extraction Dependencies
List the steps that need to occur before extraction can commence
| Item # | Step Description | Team Responsible |
|---|---|---|
| 1 | Relevancy Criteria for Equipment | SyWay A2D Data Team |
| 2 | Relevancy Criteria for Functional Location | SyWay A2D Data Team |
| 3 | Relevancy Criteria for Task List | SyWay A2D Data Team |
| 4 | 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 | In dspMigrate, select the wave – S4/HANA – Plant Maintenance | Syniti |
| 3 | Go to Process Area Launch and Process the Object – Task List | Syniti |
| 4 | Review and Validate Error and Preload Reports | Syniti |
| 5 | Execute the transformation to prepare the target tables | Syniti |
| 6 | Validate data from pre-load and error reports | Business |
| 7 | Generate load files | Syniti |
Transformation Rules
1.Maintenance Plan Transformation Rule (ECC)
| 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 | PF2, WP2 | MPLA | WARPL | Maintenance Plan | STAGING | MPLA | zLegacyWARPL | Legacy Maintenance Plan | Direct mapping. |
| 3 | - | - | - | - | S/4HANA | MPLA | MPTYP | Maintenance plan category | Default to "PM" |
| 4 | PF2, WP2 | MPLA | WSTRA | Maintenance Strategy | S/4HANA | MPLA | WSTRA | Maintenance Strategy | Value Mapping: Maintenance Strategy |
| 5 | PF2, WP2 | MPLA | WPTXT | Maintenance Plan Text | S/4HANA | MPLA | WPTXT | Maintenance Plan Text | Derive from assigned Task List Description |
| 6 | PF2, WP2 | MPLA | VSPOS | Shift Factor for Late Completion | S/4HANA | MPLA | VSPOS | Shift Factor for Late Completion | Default to 0 if Time based Maintenance Plan. Note: Check Maintenance Strategy design to differentiate between Time based and Performance based |
| 7 | PF2, WP2 | MPLA | TOPOS | Tolerance for Late Completion (%) | S/4HANA | MPLA | TOPOS | Tolerance for Late Completion (%) | Direct mapping. If blank, default to "10" |
| 8 | PF2, WP2 | MPLA | VSNEG | Shift Factor for Early Completion | S/4HANA | MPLA | VSNEG | Shift Factor for Early Completion | Default to 0 if Time based Maintenance Plan. Note: Check Maintenance Strategy design to differentiate between Time based and Performance based |
| 9 | PF2, WP2 | MPLA | TONEG | Tolerance for Early Completion (%) | S/4HANA | MPLA | TONEG | Tolerance for Early Completion (%) | Direct mapping. If blank, default to "10" |
| 10 | PF2, WP2 | MPLA | SFAKT | Cycle modification factor | S/4HANA | MPLA | SFAKT | Cycle modification factor | Direct mapping. If blank, default to "1" |
| 11 | PF2, WP2 | MPLA | FABKL | Factory calendar key | S/4HANA | MPLA | FABKL | Factory calendar key | Direct mapping. |
| 12 | PF2, WP2 | 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" |
| 13 | PF2, WP2 | MPLA | HORIZ_QUALIFIER | Calculation Type of Call Horizon | S/4HANA | MPLA | HORIZ_QUALIFIER | Calculation Type of Call Horizon | Direct mapping. If blank, default to "%" |
| 14 | PF2, WP2 | MPLA | ABRHO | Scheduling Period | S/4HANA | MPLA | ABRHO | Scheduling Period | Direct mapping. If blank, default to "3" |
| 15 | PF2, WP2 | MPLA | HUNIT | Unit for Scheduling period | S/4HANA | MPLA | HUNIT | Unit for Scheduling period | Direct mapping. If blank, default to "YR" |
| 16 | PF2, WP2 | MPLA | CALL_CONFIRM | Completion Requirement | S/4HANA | MPLA | CALL_CONFIRM | Completion Requirement | Direct mapping. |
| 17 | PF2, WP2 | MPLA | STADT | Start date | S/4HANA | MPLA | STADT | Start date | Direct mapping. |
| 18 | PF2, WP2 | MPLA | STICH | Scheduling indicator | S/4HANA | MPLA | STICH | Scheduling indicator | Direct Mapping. Default to "3" if Performance based Maintenance Plan. Note: Check Maintenance Strategy design to differentiate between Time based and Performance based |
| 19 | PF2, WP2 | MPLA | PLAN_SORT | Sort field for maintenance plans | S/4HANA | MPLA | PLAN_SORT | Sort field for maintenance plans | Value Mapping: Maintenance Plan Sort Field |
| 20 | PF2, WP2 | MMPT | POINT | Measuring Point | S/4HANA | MPLA | POINT | Measuring Point | Value Mapping: Measuring Point |
| 21 | PF2, WP2 | MPLA | ENDDT_FOR_SCHED | End Date for Scheduling | S/4HANA | MPLA | ENDDT_FOR_SCHED | End Date for Scheduling | Direct Mapping |
2.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 | zLegacyWARPL | Legacy Maintenance Plan | STAGING | MPLA | zLegacyWARPL | Legacy Maintenance Plan | Direct mapping. |
| 3 | - | - | - | - | S/4HANA | MPLA | MPTYP | Maintenance plan category | Default to "PM" |
| 4 | DCT | MPLA | WSTRA | Maintenance Strategy | S/4HANA | MPLA | WSTRA | Maintenance Strategy | Direct mapping. |
| 5 | DCT | MPLA | WPTXT | Maintenance Plan Text | S/4HANA | MPLA | WPTXT | Maintenance Plan Text | Derive from assigned Task List Description |
| 6 | 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. Note: Check Maintenance Strategy design to differentiate between Time based and Performance based |
| 7 | DCT | MPLA | TOPOS | Tolerance for Late Completion (%) | S/4HANA | MPLA | TOPOS | Tolerance for Late Completion (%) | Direct mapping. If blank, default to "10" |
| 8 | 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. Note: Check Maintenance Strategy design to differentiate between Time based and Performance based |
| 9 | DCT | MPLA | TONEG | Tolerance for Early Completion (%) | S/4HANA | MPLA | TONEG | Tolerance for Early Completion (%) | Direct mapping. If blank, default to "10" |
| 10 | DCT | MPLA | SFAKT | Cycle modification factor | S/4HANA | MPLA | SFAKT | Cycle modification factor | Direct mapping. If blank, default to "1" |
| 11 | DCT | MPLA | FABKL | Factory calendar key | S/4HANA | MPLA | FABKL | Factory calendar key | Direct mapping. |
| 12 | 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" |
| 13 | 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 "%" |
| 14 | DCT | MPLA | ABRHO | Scheduling Period | S/4HANA | MPLA | ABRHO | Scheduling Period | Direct mapping. If blank, default to "3" |
| 15 | DCT | MPLA | HUNIT | Unit for Scheduling period | S/4HANA | MPLA | HUNIT | Unit for Scheduling period | Direct mapping. If blank, default to "YR" |
| 16 | DCT | MPLA | CALL_CONFIRM | Completion Requirement | S/4HANA | MPLA | CALL_CONFIRM | Completion Requirement | Direct mapping. |
| 17 | DCT | MPLA | STADT | Start date | S/4HANA | MPLA | STADT | Start date | Direct mapping. |
| 18 | DCT | MPLA | STICH | Scheduling indicator | S/4HANA | MPLA | STICH | Scheduling indicator | Direct mapping. |
| 19 | DCT | MPLA | PLAN_SORT | Sort field for maintenance plans | S/4HANA | MPLA | PLAN_SORT | Sort field for maintenance plans | Direct Mapping |
| 20 | DCT | MMPT | POINT | Measuring Point | S/4HANA | MPLA | POINT | Measuring Point | Value Mapping: Measuring Point |
| 21 | DCT | MPLA | ENDDT_FOR_SCHED | End Date for Scheduling | S/4HANA | MPLA | ENDDT_FOR_SCHED | End Date for Scheduling | Direct Mapping |
3.Maintenance Plan Long Text Header Transformation Rule (ECC)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4HANA | STXL | TDOBJECT | Texts: application object | Default to "MPLA" |
| 2 | PF2, WP2 | MPLA | WARPL | Maintenance Plan | S/4HANA | STXL | TDNAME | Name | Value Mapping: Maintenance Plan |
| 3 | - | - | - | - | S/4HANA | STXL | TDID | Text ID | Default to 'LTXT' |
| 4 | PF2, WP2 | STXL | SPRAS | Language Key | S/4HANA | STXL | SPRAS | Language Key | Direct Mapping |
Note: Only the records marked as Cleansed in INC-MP Header Long Text will be migrated
4.Maintenance Plan Long Text Header 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 | STXL | TDOBJECT | Texts: application object | Default to "MPLA" |
| 2 | DCT | MPLA | zLegacyWARPL | Legacy Maintenance Plan | S/4HANA | STXL | TDNAME | Name | Value Mapping: Maintenance Plan |
| 3 | - | - | - | - | S/4HANA | STXL | TDID | Text ID | Default to 'LTXT' |
| 4 | DCT | STXL | SPRAS | Language Key | S/4HANA | STXL | SPRAS | Language Key | Direct Mapping |
5.Maintenance Plan Long Text Line Transformation Rule (ECC)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4HANA | STXL | TDOBJECT | Texts: application object | Default to "MPLA" |
| 2 | PF2, WP2 | MPLA | WARPL | Maintenance Plan | S/4HANA | STXL | TDNAME | Name | Value Mapping: Maintenance Plan |
| 3 | - | - | - | - | STXL | TDID | Text ID | Default to 'LTXT' | |
| 4 | PF2, WP2 | STXL | SPRAS | Language Key | S/4HANA | STXL | SPRAS | Language Key | Direct Mapping |
| 5 | - | - | - | - | S/4HANA | STXL | CLUSTD_TAG | Tag column | Default to "*" |
| 6 | PF2, WP2 | STXL | ROWCOUNT | Row number | S/4HANA | STXL | ROWCOUNT | Row number | Direct Mapping |
| 7 | PF2, WP2 | STXL | CLUSTD_LINE | Text Line | S/4HANA | STXL | CLUSTD_LINE | Text Line | Direct Mapping |
6.Maintenance Plan Long Text Line 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 | STXL | TDOBJECT | Texts: application object | Default to "MPLA" |
| 2 | DCT | MPLA | zLegacyWARPL | Legacy Maintenance Plan | S/4HANA | STXL | TDNAME | Name | Value Mapping: Maintenance Plan |
| 3 | - | - | - | - | S/4HANA | STXL | TDID | Text ID | Default to 'LTXT' |
| 4 | DCT | STXL | SPRAS | Language Key | S/4HANA | STXL | SPRAS | Language Key | Direct Mapping |
| 5 | - | - | - | - | S/4HANA | STXL | CLUSTD_TAG | Tag column | Default to "*" |
| 6 | DCT | STXL | ROWCOUNT | Row number | S/4HANA | STXL | ROWCOUNT | Row number | Direct Mapping |
| 7 | DCT | STXL | CLUSTD_LINE | Text Line | S/4HANA | STXL | CLUSTD_LINE | Text Line | Direct Mapping |
7.Maintenance Item Transformation Rule (ECC)
| 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 | STAGING | MPLA | zLegacyWARPL | Legacy Maintenance Plan | Direct mapping. |
| 3 | PF2, WP2 | MPOS | WAPOS | Maintenance Item | STAGING | MPLA | zLegacyWAPOS | Maintenance Item | Direct mapping |
| 4 | PF2, WP2 | MPOS | PSTXT | Item Short Text | S/4HANA | MPOS | PSTXT | Item Short Text | Direct mapping |
| 5 | PF2, WP2 | MPOS | TPLNR | Functional Location | S/4HANA | MPOS | TPLNR | Functional Location | Value Mapping: Functional Location |
| 6 | PF2, WP2 | MPOS | EQUNR | Equipment Number | S/4HANA | MPOS | EQUNR | Equipment Number | Value Mapping: Equipment Number |
| 7 | ENRICHMENT | ENR-Maintenance Item Assembly | zLegacyBAUTL | Assembly | S/4HANA | MPOS | EQUNR | Equipment Number | Value Mapping: Assembly and Construction Type |
| 8 | PF2, WP2 | MPOS | AUART | Order Type | S/4HANA | MPOS | AUART | Order Type | Value Mapping: Order Type |
| 9 | PF2, WP2 | MPOS | GEWRK | Main work center for maintenance tasks | MPOS | GEWRK | Main work center for maintenance tasks | Value Mapping: Work Centre If blank then Default to the value derived from the technical object | |
| 10 | PF2, WP2 | MPOS | PLNTY | Task List Type | S/4HANA | MPOS | PLNTY | Task List Type | Value Mapping: Task List Header |
| 11 | PF2, WP2 | MPOS | PLNNR | Key for Task List Group | S/4HANA | MPOS | PLNNR | Key for Task List Group | Value Mapping: Task List Header |
| 12 | PF2, WP2 | MPOS | PLNAL | Group Counter | S/4HANA | MPOS | PLNAL | Group Counter | Value Mapping: Task List Header |
| 13 | PF2, WP2 | MPOS | APFKT | Execution factor for whole task list | S/4HANA | MPOS | APFKT | Execution factor for whole task list | Direct mapping. If blank, default to "1" |
| 14 | PF2, WP2 | MPOS | ANLZU | System Condition | S/4HANA | MPOS | ANLZU | System Condition | Value Mapping: System Condition |
| 15 | PF2, WP2 | MPOS | WPGRP | Maintenance Planner Group | S/4HANA | MPOS | WPGRP | Maintenance Planner Group | Value Mapping: Maintenance Planner Group Default to the value derived from the technical object if blank |
8.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 | DCT | MPOS | zLegacyWARPL | Legacy Maintenance Plan | STAGING | MPLA | zLegacyWARPL | Legacy Maintenance Plan | Direct mapping. |
| 3 | DCT | MPOS | zLegacyWAPOS | Legacy Maintenance Item | STAGING | MPLA | zLegacyWAPOS | Maintenance Item | Direct mapping |
| 4 | DCT | MPOS | PSTXT | Item Short Text | S/4HANA | MPOS | PSTXT | Item Short Text | Direct mapping |
| 5 | DCT | MPOS | TPLNR | Functional Location | S/4HANA | MPOS | TPLNR | Functional Location | Value Mapping: Functional Location |
| 6 | DCT | MPOS | EQUNR | Equipment Number | S/4HANA | MPOS | EQUNR | Equipment Number | Value Mapping: Equipment Number |
| 7 | - | - | - | - | - | MPOS | AUART | Order Type | Default to "YA02" |
| 8 | DCT | MPOS | GEWRK | Main work center for maintenance tasks | S/4HANA | MPOS | GEWRK | Main work center for maintenance tasks | Value Mapping: Work Centre If blank then Default to the value derived from the technical object |
| 9 | DCT | MPOS | PLNTY | Task List Type | S/4HANA | MPOS | PLNTY | Task List Type | Value Mapping: Task List Header |
| 10 | DCT | MPOS | PLNNR | Key for Task List Group | S/4HANA | MPOS | PLNNR | Key for Task List Group | Value Mapping: Task List Header |
| 11 | DCT | MPOS | PLNAL | Group Counter | S/4HANA | MPOS | PLNAL | Group Counter | Value Mapping: Task List Header |
| 12 | DCT | MPOS | APFKT | Execution factor for whole task list | S/4HANA | MPOS | APFKT | Execution factor for whole task list | Direct mapping. If blank, default to "1" |
| 13 | DCT | MPOS | ANLZU | System Condition | S/4HANA | MPOS | ANLZU | System Condition | Direct mapping. |
| 14 | DCT | MPOS | WPGRP | Maintenance Planner Group | S/4HANA | MPOS | WPGRP | Maintenance Planner Group | Update the value if provided by business. Default to the value derived from the technical object if blank |
9.Maintenance Item Object List Transformation Rule (ECC)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | - | OBJK | OBKNR | Object list number | System (Internal numbering) |
| 2 | - | - | - | - | - | OBJK | OBZAE | Object list counters | System (Internal numbering) |
| 3 | - | - | - | - | - | OBJK | ILOAN | Location and account assignment for technical object | System (Internal numbering) |
| 4 | PF2, WP2 | OBJK | SORTF | Object list sort field | S/4HANA | OBJK | SORTF | Object list sort field | Direct mapping. |
| 5 | PF2, WP2 | OBJK | TPLNR | Functional Location | S/4HANA | OBJK | TPLNR | Functional Location | Value Mapping: Functional Location |
| 6 | PF2, WP2 | OBJK | EQUNR | Equipment Number | S/4HANA | OBJK | EQUNR | Equipment Number | Value Mapping: Equipment Number |
10.Maintenance Item Object List Transformation Rule (DCT)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | - | OBJK | OBKNR | Object list number | System (Internal numbering) |
| 2 | - | - | - | - | - | OBJK | OBZAE | Object list counters | System (Internal numbering) |
| 3 | - | - | - | - | - | OBJK | ILOAN | Location and account assignment for technical object | System (Internal numbering) |
| 4 | PF2, WP2 | OBJK | SORTF | Object list sort field | S/4HANA | OBJK | SORTF | Object list sort field | Direct mapping. |
| 5 | PF2, WP2 | OBJK | TPLNR | Functional Location | S/4HANA | OBJK | TPLNR | Functional Location | Value Mapping: Functional Location |
| 6 | PF2, WP2 | OBJK | EQUNR | Equipment Number | S/4HANA | OBJK | EQUNR | Equipment Number | Value Mapping: Equipment Number |
11.Maintenance Plan (Characteristics Values Header) (ECC)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4HANA | KLAH | KLART | Class Type | Default to "080" |
| 2 | - | - | - | - | S/4HANA | INOB | OBTAB | Name of Database Table for Object | Default to "MPLA" |
| 3 | - | - | - | - | S/4HANA | KLAH | CLASS | Class number | Default to "EAM_9999" |
| 4 | - | - | - | - | S/4HANA | INOB | OBJEK | Key of Object | Derive from Maintenance Plan Object Number |
| 5 | - | - | - | - | S/4HANA | KLAH | STATU | Class Status | Default to "1" |
12.Maintenance Plan (Characteristics Values Header) (DCT)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4HANA | KLAH | KLART | Class Type | Default to "080" |
| 2 | - | - | - | - | S/4HANA | INOB | OBTAB | Name of Database Table for Object | Default to "MPLA" |
| 3 | - | - | - | - | S/4HANA | KLAH | CLASS | Class number | Default to "EAM_9999" |
| 4 | - | - | - | - | S/4HANA | INOB | OBJEK | Key of Object | Derive from Maintenance Plan Object Number |
| 5 | - | - | - | - | S/4HANA | KLAH | STATU | Class Status | Default to "1" |
13.Maintenance Plan (Characteristics Values Allocation) (ECC)
| 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 | - | - | - | - | S/4HANA | KLAH | KLART | Class Type | Default to "018" |
| 3 | - | - | - | - | S/4HANA | INOB | OBTAB | Name of Database Table for Object | Default to "MPLA" |
| 4 | - | - | - | - | S/4HANA | KLAH | CLASS | Class number | Default to "EAM_9999" |
| 5 | - | - | - | - | S/4HANA | INOB | OBJEK | Key of Object | Derive from Maintenance Plan Object Number |
| 6 | - | - | - | - | S/4HANA | CABN | ATNAM | Characteristic Name | Direct Mapping |
| 7 | - | - | - | - | S/4HANA | AUSP | ATWRT | Characteristic Value | Direct Mapping |
| 8 | - | - | - | - | S/4HANA | KSML | POSNR | Item Number | Generate sequence number starting with 1 by order the record is created for each Key of Object |
14.Maintenance Plan (Characteristics Values Allocation) (DCT)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4HANA | KLAH | KLART | Class Type | Default to "018" |
| 2 | - | - | - | - | S/4HANA | INOB | OBTAB | Name of Database Table for Object | Default to "MPLA" |
| 3 | - | - | - | - | S/4HANA | KLAH | CLASS | Class number | Default to "EAM_9999" |
| 4 | - | - | - | - | S/4HANA | INOB | OBJEK | Key of Object | Derive from Maintenance Plan Object Number |
| 5 | - | - | - | - | S/4HANA | CABN | ATNAM | Characteristic Name | Direct Mapping |
| 6 | - | - | - | - | S/4HANA | AUSP | ATWRT | Characteristic Value | Direct Mapping |
| 7 | - | - | - | - | S/4HANA | KSML | POSNR | Item Number | Generate sequence number starting with 1 by order the record is created for each Key of Object |
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 |
|---|---|
Maintenance Plan | Old to new Maintenance Plan |
Maintenance Item | Old to new Maintenance Item |
Maintenance Strategy | Old to new Maintenance Strategy |
Functional Location | Old to new Functional Location |
Equipment Number | Old to new Equipment Number |
Material Number | Old to new Material Number |
Task List Header | Old to new Task List Header |
Measuring Point | Old to new Measuring Point |
Work Centre | Old to new Work Centre |
Assembly and Construction Type | Mapping of legacy Assembly / Construction Type to new Assembly / Construction Type |
Maintenance Plan Sort Field | Old to new Maintenance Plan Sort Field |
Priority | Old to new Priority |
Order Type | Old to new Order Type |
System Condition | Old to new System Condition |
Maintenance Planner Group | Old to new Maintenance Planner Group |
ENR-Maintenance Item Assembly | Enrichment to assign Assembly to Funtional Location or Equipment |
Transformation Dependencies
List the steps that need to occur before transformation can commence| Item # | Step Description | Team Responsible |
|---|---|---|
| 1 | Ensure DCT tables completeness | SyWay Data Team |
| 2 | Ensure all Transformation mappings are up to date. | SyWay Data Team |
Pre-Load Validation
Project Team
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 | Ensure Pre-load sign-offs are obtained. | SyWay Data team |
| 2 | Go to the load tool and select the correct load Program. | SyWay Data team |
| 3 | Proceed with Data load. | SyWay Data team |
| 4 | Validate few records loaded by accessing standard transactions | SyWay Data team |
| 5 | Generate the post load reports in the tool. | SyWay Data team |
| 6 | Log errors as defects, if any and address resolutions. Close defects. | SyWay Data team |
| 7 | Resolve defects by reupload and re-generate post load reports if necessary. | SyWay Data team |
| 8 | Business to validate the post load files as part of post-load validation, raise data defects or provide the post-load sign-off. | Business |
| 9 | Repeat steps 5 to 7 if necessary. | SyWay Data team |
Load Phase and Dependencies
Pre-Cutover
Configuration
List the Configurations required before loading can commence
| Item # | Configuration Item |
|---|---|
| 1 | T399W-Maintenance Plan Category |
| 2 | T024A-Planner Groups |
| 3 | T001W-Plant |
| 4 | T399I-Planning Plant |
| 5 | T357M-Machine operating condition |
| 6 | T353I-Activity Type |
| 7 | T356-Priority |
| 8 | TCA01-Task List Type |
| 9 | T003O-Order Type |
| 10 | T399G-Maintenance Plan Sort Field |
| 11 | TFACD-Factory Calendar Definition |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
1002 | Equipment |
1003 | Functional Location |
1005 | Task List |
1012 | Measuring Point |
1017 | Maintenance Strategy |
2019 | Materials - Basic Data View |
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 Maintenance Activity Type | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Priority | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Order Type | Engage Functional team to expedite and fix the error in the system |
Invalid Data | Invalid Maintenance Strategy | Expedite whether the master data is changed in the system |
Invalid Data | Invalid Work Centre | Expedite whether the master data is changed in the system |
Invalid Data | Invalid Task List | Expedite whether the master data is changed in the system |
Invalid Data | Invalid Functional Location | Expedite whether the master data is changed in the system |
Invalid Data | Invalid Equipment | Expedite whether the master data is changed in the system |
Post-Load Validation
Project Team
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.
- Data cleansing has met the required percentage threshold for the specified mock cycle and all preparation activities have been completed.
- Data entries in DCT are target-ready data unless a specific transformation rule is stated for that field in the transformation rules.
- Not all legacy Maintenance Plan and Item need to be mapped to S/4 HANA Maintenance Plan and Item. If any of the successor objects is dependent on a Maintenance Plan and Item field with no mapped values, this will be an enrichment activity or manual transformation for the successor object to derive the Maintenance Plan and Item.
See also
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.