| Status | 008 |
|---|---|
| Owner | |
| Stakeholders |
Purpose
The purpose of this document is to define the conversion approach to create Task List in S/4 HANA.
A Maintenance Task List in SAP PM is a predefined set of maintenance activities that can be reused across multiple work orders and maintenance plans. It standardizes recurring tasks, improves planning efficiency, and ensures consistency in execution.
Legacy Plant Maintenance Task list is using a diverse range of formats across the different systems. There are instances where the same Task list is duplicated within and/or across sources, with informal words. This results in data inconsistency. As per SyWay design, EAM Maintenance Task list will be standardized.
Conversion Scope
The scope of this document covers the approach for converting active Task List from Legacy Source Systems into S/4HANA following the Task List Master Data Design Standard.
SAP PM task lists are reusable templates that define the sequence of maintenance activities for equipment, functional locations, or general processes. They standardize maintenance operations by grouping operations, durations, and materials into a single master record. Task lists enhance consistency, simplify planning, and speed up order creation.
The data from legacy system includes:
- Task lists created (PLKO-ANDAT) on or after July 1, 2024 OR Task lists used within the past 3 years (with Active Maintenance Items Assigned or Open Notifications or Open Work Orders)
- Task List Type:
A - General Maintenance Task List
E - Equipment Task List
T - Task List for Functional Location - Assigned to a relevant Functional Location if its type T(Functional Location)
- Assigned to a relevant Equipment if its type E (Equipment)
- Has at least 1 operation
- Status = Released (PLKO-STATU = 2, 3, 4)
- Task list having Maintenance Plant (PLKO-WERKS) in scope - Refer to Value Mapping: Plant (Maintenance Plant = Yes)
- Task Lists in the Value Mapping: INC-Task List (What it contains: Task lists that have not been used in over 3 years (criteria: no active maintenance items assigned, no open notifications, and no open work orders) but are still part of a periodic plan (e.g., recurring every X period).
The data from legacy system excludes:
- Task lists not used over 3 years. (Definition: No Active Maintenance Items Assigned, No Open Notifications, No Open Work Orders)
- Task lists With Deletion Indicator or marked for deletion. Tables to check for deletion indicator (LOEKZ='X'): PLKO, PLAS, PLPO, PLMZ
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
PF2, WP2 | Active Task Lists will be extracted from PF2 and WP2 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 | 61,000 | S/4HANA | 61,000 |
DCT | Long texts for selected sites for non-PF2/WP2 Task List Operation will be populated as target ready values in DCT. | TBD | S/4 HANA | TBD |
Additional Information
Multi-language Requirement
Task List header and operation description does not support multi Language. Any change to the description text via any logon language will overwrite the existing description. Description text can be view in any logon language.
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.Task List Header
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| PLKO | PLNTY | PLNTY | Task List Type | CHAR | 1 | Mandatory |
| PLKO | PLNNR | PLNNR | Key for Task List Group | CHAR | 8 | Mandatory |
| PLKO | PLNAL | PLNAL | Group Counter | 2 | System | |
| PLKO | DATUV | DATUV | Valid-From Date | DATS | 8 | Mandatory |
| EAPL | EQUNR | EQUNR | Equipment Number | 18 | Mandatory | |
| TAPL | TPLNR | TPLNR | Functional Location | 30 | Mandatory | |
| PLKO | PROFIDNETZ | PROFID_STD | Profile | CHAR | 7 | Conditional |
| PLKO | KTEXT | PLANTEXT | Description | 40 | Mandatory | |
| PLKO | IWERK | IWERK | Planning Plant | CHAR | 4 | Mandatory |
| PLKO | ARBID | IGEWERK | Work Centre group with planning function | NUMC | 8 | Mandatory |
| PLKO | WERKS | WERKS_D | Plant | CHAR | 4 | Mandatory |
| PLKO | VERWE | PLN_VERWE | Task List Usage | CHAR | 3 | Mandatory |
| PLKO | VAGRP | VAGRP | Planner Group | CHAR | 3 | Mandatory |
| PLKO | STATU | PLNST | Overall Status | CHAR | 3 | Mandatory |
| PLKO | ANLZU | ANLZU | System Condition | CHAR | 1 | Conditional |
| PLKO | STRAT | STRAT | Maintenance Strategy | 6 | Conditional | |
| PLKO | ISTRU | ISTRU | Assembly | 40 | Mandatory | |
| PLKO | DELKZ | CP_DELKZ | Indicator: Delete completely in reorganization run | CHAR | 1 | Conditional |
| PLKO | PLNNR_ALT | CP_PLNNR_A | Old number | CHAR | 20 | Conditional |
| PLKO | ARBTY | CR_OBJTY | Object types of the CIM resource | CHAR | 2 | System |
| PLKO | FLG_CHK | FLG_CHKED | Ind: Task list was submitted for consistency check | CHAR | 1 | System |
* EQUNR/TPLNR- Select the appropriate field depending on technical object
2.Task List Operation
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| PLPO | PLNTY | PLNTY | Task List Type | CHAR | 1 | Mandatory |
| PLPO | PLNNR | PLNNR | Key for Task List Group | CHAR | 8 | Mandatory |
| PLPO | VORNR | VORNR | Activity Number | CHAR | 4 | Mandatory |
| PLPO | PLNKN | PLNKN | Number of the Task List Node | 8 | System | |
| PLPO | ZAEHL | PLNKN | Internal counter | 8 | System | |
| PLPO | ARBID | OBJEKTID | Work Centre | NUMC | 8 | Mandatory |
| PLPO | WERKS | WERKS_D | Plant | CHAR | 4 | Mandatory |
| PLPO | STEUS | STEUS | Control Key | CHAR | 4 | Mandatory |
| PLPO | LTXA1 | LTXA1 | Operation Description | CHAR | 40 | Mandatory |
| PLPO | TXTSP | SPRAS | Language Key | LANG | 1 | System |
| PLPO | ARBEI | ARBEIT | Work Involved in the Activity | QUAN | 7(1) | Mandatory |
| PLPO | ARBEH | ARBEITE | Unit for Work | UNIT | 3 | Mandatory |
| PLPO | ANZZL | ANZKAP | Number of Capacities Required | INT1 | 3 | Mandatory |
| PLPO | DAUNO | DAUNOR | Normal Duration of the Activity | QUAN | 5(1) | System |
| PLPO | DAUNE | DAUNORE | Normal Duration/Unit (ISO Format) | UNIT | 3 | System |
| PLPO | INDET | INDET | Key for calculation | CHAR | 1 | Mandatory |
| PLPO | PRZNT | APROZENT | Work Percentage | INT1 | 3 | Conditional |
| PLPO | VERTN | CR_VERTN | Distr.cap.reqmts (plant maint.,process order, network) | CHAR | 8 | Conditional |
| PLPO | AUFKT | AFAKT | Execution Factor | DEC | 3(0) | Conditional |
| PLPO | LARNT | LSTAR | Activity Type | CHAR | 6 | System |
| PLPO | ANLZU | ANLZU | System Condition | CHAR | 1 | Conditional |
| PLPO | EXECUTION_STAGE | EAM_PREMAINPOST | PRE MAIN POST | CHAR | 10 | Conditional |
| PLPO | BMVRG | BMVRG | Order Quantity | QUAN | 13(3) | Conditional |
| PLPO | BMEIH | BMEIH | Order Quantity Unit | UNIT | 3 | Conditional |
| PLPO | PREIS | IPREI | Price Per Unit | 11(2) | System | |
| PLPO | WAERS | WAERS | Currency | CUKY | 5 | System |
| PLPO | PEINH | EPEIN | Unit for Price | DEC | 5(0) | System |
| PLPO | PLIFZ | PLIFZ | Planned Delivery Time in Days | DEC | 3(0) | Conditional |
| PLPO | FRDLB | CO_FRDLB | Indicator: External Processing Operation with Subcontracting | CHAR | 1 | Conditional |
| PLPO | SAKTO | KSTAR | Cost Element | CHAR | 10 | Conditional |
| PLPO | MATKL | MATKL | Material Group | CHAR | 9 | Conditional |
| PLPO | EKGRP | VG_EKGRP | Purchasing Group | CHAR | 3 | Conditional |
| PLPO | LIFNR | LIFNR | Vendor | CHAR | 10 | Conditional |
| PLPO | EKORG | EKORG | Purchasing Organization | CHAR | 4 | Conditional |
| PLPO | EBELN | EBELN | Purchasing Agreement | CHAR | 10 | Conditional |
| PLPO | EBELP | EBELP | Purchasing Agreement Item | NUMC | 5 | Conditional |
| PLPO | INFNR | INFNR | Purchasing Info Record | CHAR | 10 | System |
| PLPO | ESOKZ | ESOKZ | Purchasing info record category | CHAR | 1 | System |
| PLPO | PACKNO | PACKNO | Package number | NUMC | 10 | System |
| PLPO | BUKRS | BUKRS | Company Code | CHAR | 4 | System |
| PLPO | KALID | WFCID | Factory Calendar | CHAR | 2 | System |
| PLPO | PLNKN | PLNKN | Node | NUMC | 8 | System |
| PLPO | ZAEHL | CIM_COUNT | Internal Counter | NUMC | 8 | System |
3.Task List Operation Long Text Header
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| PLPO | PLNTY | PLNTY | Task List Type | CHAR | 1 | Mandatory |
| PLPO | PLNNR | PLNNR | Key for Task List Group | CHAR | 8 | Mandatory |
| PLPO | VORNR | VORNR | Activity Number | CHAR | 4 | Mandatory |
| PLPO | PLNKN | PLNKN | Number of the Task List Node | 8 | System | |
| PLPO | ZAEHL | PLNKN | Internal counter | 8 | System | |
| 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 |
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.Task List Operation Long Text Line
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| PLPO | PLNTY | PLNTY | Task List Type | CHAR | 1 | Mandatory |
| PLPO | PLNNR | PLNNR | Key for Task List Group | CHAR | 8 | Mandatory |
| PLPO | VORNR | VORNR | Activity Number | CHAR | 4 | Mandatory |
| PLPO | PLNKN | PLNKN | Number of the Task List Node | 8 | System | |
| PLPO | ZAEHL | PLNKN | Internal counter | 8 | System | |
| 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 |
| STXL | CLUSTD_TAG | TDFORMAT | Tag column | CHAR | 1 | Mandatory |
| STXL | CLUSTD_LINE | TDLINE | Text Line | CHAR | 72 | Mandatory |
5.Task List Operation Lean Service
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| STPO | IDNRK | IDNRK | Material Number | CHAR | 40 | Conditional |
| MAKT | MAKTX | MAKTX | Material description | CHAR | 40 | System |
| STPO | POSTP | POSTP | Item category (bill of material) | 1 | Conditional | |
| PLMZ | WERK_STL | WERKS_D | Plant | 4 | System | |
| PLMZ | IMENG | KMPMG | Component Quantity | 13 | Conditional | |
| PLMZ | IMEIN | KMPME | Component Unit of Measure | 3 | System | |
| PLMZ | SERVICEDURATION | SERVICEDURATION | Service Duration | 5 | Conditional | |
| PLMZ | SERVICEDURATIONUNIT | SERVICEDURATIONUNIT | Service Duration Unit | 3 | Conditional | |
| STPO | EKORG | EKORG | Purchasing Organization | 4 | System | |
| STPO | EKGRP | EKGRP | Purchasing Group | 3 | System | |
| STPO | MATKL | MATKL | Material Group | 9 | System |
6.Task List Component
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| PLMZ | PLNNR | PLNNR | Task List Key | CHAR | 8 | Mandatory |
| PLMZ | VORNR | VORNR | Activity Number | CHAR | 4 | System |
| PLPO | PLNKN | PLNKN | Number of the Task List Node | 8 | Mandatory | |
| STPO | IDNRK | IDNRK | Material Number | CHAR | 40 | Conditional |
| STPO | MENGE | KMPMG | Component Quantity | 1 | Conditional | |
| STPO | MEINS | KMPME | Component Unit of Measure | 3 | Conditional | |
| PLMZ | RGEKZ | RGEKZ | Indicator: Backflush | 1 | Conditional | |
| PLMZ | DISP | DISP_PLUS_1 | Relevancy to Materials Planning/Generation of Purchase Req. | 1 | Conditional | |
| STPO | POTX1 | POTX1 | BOM Item Text (Line 1) | 40 | System | |
| PLMZ | STLTY_W | STLTY | BOM category | 1 | Conditional | |
| PLMZ | WERK_STL | WERKS_D | Plant | 4 | Conditional | |
| STPO | EKGRP | EKGRP | Purchasing Group | 3 | Conditional | |
| STPO | EKORG | EKORG | Purchasing Organization | 4 | Conditional | |
| STPO | WAERS | WAERS | Currency Keya | 5 | System | |
| STPO | PEINH | PEINH | Price unit | 5 | System | |
| STPO | MATKL | MATKL | Material Group | 9 | System | |
| PLMZ | LGORT | LGORT_RES | Issue Location for Production Order | 4 | Conditional | |
| STPO | LIFNR | LIFNR | Account Number of Supplier | 10 | Conditional | |
| MARC | WEBAZ | WEBAZ | Goods receipt processing time in days | 3 | System |
7.Maintenance Package
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| PLWP | PLNTY | PLNTY | Task List Type | CHAR | 1 | Mandatory |
| PLWP | PLNNR | PLNNR | Task List Key | CHAR | 8 | Mandatory |
| PLWP | PLNAL | PLNAL | Group Counter | 2 | Mandatory | |
| PLWP | PLNKN | PLNKN | Number of the Task List Node | 8 | Mandatory | |
| PLWP | STRAT | STRAT | Maintenance Strategy | CHAR | 6 | Mandatory |
| PLWP | PAKET | PAKETZAEHL | Maintenance Package Number | NUMC | 2 | Mandatory |
| T351X | KZYK1 | KTEXTZYK | Short text for the maintenance cycle (time/performance) | CHAR | 2 | Mandatory |
Task List Data strictly adheres to the Master Data Standard. The complete information of the key fields that hold the Task List information follows the Master Data Standard document that is located here.
Data Cleansing
All data cleansing should take place in the data source system as defined in this document, unless system limitations prevent it.
If data cleansing is managed outside of the source system (e.g. Syniti Migrate, 3rd Party Vendor, DCT), the necessary documentation must be produced and appended to this deliverable for sign-off.
| ID | Criticality | Error Message/Report Description | Rule | Output | Source System |
|---|---|---|---|---|---|
1005-001 | C1 | TL Header: Invalid, Inactive or no Operations attached to Active Task List Header | Task List Header as per Relevancy Criteria assigned with no or inactive Task List Operation attached. | Task List Operation | PF2, WP2 |
1005-002 | C2 | TL Header: Task lists not used within the last 3 years | Task List as per Relevancy Criteria but are not used across: | Task List | PF2, WP2 |
1005-003 | C1 | TL Header-Description: Missing Task Lists Descriptions | Task List as per Relevancy Criteria where there are blank Task List Descriptions. | Task List Description | PF2, WP2 |
1005-004 | C2 | TL Header-Description: Task Lists Descriptions with Informal Words | Task List as per Relevancy Criteria which contain Informal Words in the Task List Description | Task List Description | PF2, WP2 |
1005-005 | C1 | TL Header-Status: Created but not released | TL Header STATU <> 2, 3, 4 | Status | PF2, WP2 |
1005-006 | C1 | TL Header-Valid-From Date: Valid-From Date is in the future | TL Header Valid-From Date > current date | Valid-From Date | PF2, WP2 |
1005-007 | C1 | TL Header-Work Centre: Invalid, Inactive or no Work Centres | Task List as per Relevancy Criteria assigned with a Work Centre which does not belong below: | Work Centre | PF2, WP2 |
1005-008 | C1 | TL Header-Work Centre: Not mapped to new Work Centre | Task List as per Relevancy Criteria assigned with a Work Centre which is not mapped to new Work Centre | Work Centre | |
1005-009 | C1 | TL Operation: Active Task List Operations allocated to inactive Task List Headers | Task List Operation as per Relevancy Criteria assigned with no or inactive Task List Headers attached. | Task List Operation | PF2, WP2 |
1005-010 | C1 | TL Operation-Work Centre: Invalid, Inactive or no Work Centres | ask List as per Relevancy Criteria assigned with a Work Centre which does not belong below: 1. Work Centre as per Relevancy Criteria | Work Centre | PF2, WP2 |
1005-011 | C1 | TL Operation-Work Centre: Not mapped to new Work Centre | Task List as per Relevancy Criteria assigned with a Work Centre which is not mapped to new Work Centre | Work Centre | |
1005-012 | C1 | TL Operation: Active Task List Components allocated to inactive Task List Operation | Task List Component as per Relevancy Criteria assigned with no or inactive Task List Operations attached. | Task List Component | PF2, WP2 |
1005-013 | C1 | TL Operation-Vendor: Invalid or inactive Business Partner (Vendor) linked to Task List | Task List as per Relevancy Criteria assigned with a Business Partner (Vendor) which does not belong below: | Business Partner (Vendor) | PF2, WP2 |
1005-014 | C1 | TL Component-Material: Invalid, Inactive or no Material allocated | Task List as per Relevancy Criteria assigned with a Material which does not belong below: 1. Material Master (S2P) as per Relevancy Criteria | Material Number | PF2, WP2 |
1005-015 | C1 | TL Component-Construction Type: Invalid, Inactive or no Construction Type allocated | Task List as per Relevancy Criteria assigned with a Construction Type which does not belong below: | Construction Type | PF2, WP2 |
Conversion Process
The high-level process 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 - Remove if not applicable
- For new classes that need to be created to support the to-be design
The high-level process for DCT is represented by the diagram below:
Data Privacy and Sensitivity
Summarize Data Privacy and Sensitivity Requirements, if anyExtraction
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 PF2 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 Data Object data with exception of some fields which require transformation as mentioned in the transformation rule.1.Task List Header Data Construction Rules
| Field Name | Field Description | Rule |
|---|---|---|
| zLegacyPLNTY | Legacy Task List Type | Mandatory. Select one of the following: A = General TL, E = Equipment, T = Functional Location |
| zLegacyPLNNR | Legacy Task List Group | Mandatory. When PLNTY = A input PLNNR When PLNTY = E input EQUNR When PLNTY = T input TPLNR |
| zLegacyPLNAL | Legacy Group Counter | Mandatory. Must be ascending sequential within the TLGRP. Eg: 01, 02 etc |
| zLegacyEQUNR | Legacy Equipment Number | Mandatory if zLegacyPLNTY = 'E' |
| zLegacyTPLNR | Legacy Functional Location | Mandatory if zLegacyPLNTY = 'T' |
| PROFIDNETZ | Profile | Select profile to assign profile to task list else leave this field blank. Must reference active TCA41-PROFIDNETZ |
| KTEXT | Description | Mandatory. Restrict use of special characters. For list of restricted characters, refer to Appendix SR No 1 in : DD-FUN- 050 Master Data Standard_Functional Location |
| WERKS | Plant | Mandatory. Must reference active plant in config (T001W) |
| ARBPL | Work Centre group with planning function | Mandatory. If PLNTY = A then select manually. Must reference active Work Centre (CRHD) |
| VAGRP | Planner Group | Mandatory. If PLNTY = A then select manually. Must reference active Planner Group in config (T024A) |
| STATU | Overall Status | Mandatory. Must reference active Task List Status in config (T412) |
| ANLZU | System Condition | Conditional. Must reference active Machine Operating Condition in config (T357M). Comments/Special handling notes: |
| STRAT | Maintenance Strategy | Conditional. Must reference active Maintenance Strategy in config (T351) |
| ISTRU | Assembly | Mandatory. Must reference active Material (MARA) which are extended to Plant (MARC) |
| DELKZ | Indicator: Delete completely in reorganization run | Conditional. Possible values: "X" or blank. "X" to mark record for deletion |
2.Task List Operation Data Construction Rules
Definition:
- External - (PLPO-STEUS=T430-STEUS, T430-LIEF is not blank)
- Lean Service - (PLPO-STEUS=T430-STEUS, T430-SERVICE is not blank)
| Field Name | Field Description | Rule |
|---|---|---|
| zLegacyPLNTY | Legacy Task List Type | Mandatory. Select one of the following: A = General TL, E = Equipment, T = Functional Location |
| zLegacyPLNNR | Legacy Task List Group | Mandatory. |
| zLegacyPLNAL | Legacy Group Counter | Mandatory. Must be ascending sequential within the same zLegacyPLNNR starting with "01". Eg: 01, 02 etc |
| zLegacyPLNKN | Number of the Task List Node | Mandatory. Must be ascending sequential within the same zLegacyPLNNR starting with "00000001". Eg: 00000001, 00000002 etc This field is used to link to Long Text |
| zLegacyZAEHL | Internal counter | Mandatory. Must be ascending sequential within the same zLegacyPLNNR starting with "00000001". Eg: 00000001, 00000002 etc This field is used to link to Long Text |
| zLegacyVORNR | Legacy Activity Number | Mandatory. Must be ascending sequential within the same zLegacyPLNNR starting with "0010" Eg: 0010, 0020 etc |
| ARBPL | Work Centre | Mandatory. |
| WERKS | Plant | Mandatory. Must match the Plant of the associated Task List Header Must reference active plant in config (T001W) |
| STEUS | Control Key | Mandatory. Default to CRHD-STEUS Must reference active Control Key in config (T430) |
| LTXA1 | Operation Description | Mandatory. Restrict use of special characters. For list of restricted characters, refer to Appendix SR No 1 in : DD-FUN- 050 Master Data Standard_Functional Location |
| AUFKT | Execution Factor | Conditional. Numeric values only |
| ARBEI | Work Involved in the Activity | Mandatory. |
| ANZZL | Number of Capacities Required | Mandatory. Numeric values only |
| VERTN | Distr.cap.reqmts | Conditional. Must reference active Distribution Function in config (TC29) |
| ANLZU | System Condition | Conditional. Must reference active Machine operating condition in config (T357M). Comments/Special handling notes: |
| EXECUTION_STAGE | PRE MAIN POST | Conditional. Free text. If blank then default to "MAIN" in Transformation Rules |
| BMVRG | Order Quantity | Conditional. If the Control Key is "External", this field is required. Otherwise, leave blank. |
| BMEIH | Order Quantity Unit | Conditional. If the Control Key is "External", this field is required. Otherwise, leave blank. If not blank, must reference active Units of Measurement in config (T006) |
| PLIFZ | Planned Delivery Time in Days | Conditional. If the Control Key is "External", this field is optional. Otherwise, leave blank. |
| FRDLB | Indicator: External Processing Operation with Subcontracting | Conditional. If the Control Key is "External", this field is optional. Otherwise, leave blank. |
| SAKTO | Cost Element | Conditional. If the Control Key is "External", this field is required. Otherwise, leave blank. |
| MATKL | Material Group | Conditional. If the Control Key is "External", this field is required. Otherwise, leave blank. |
| EKGRP | Purchasing Group | Conditional. If the Control Key is "External", this field is required. Otherwise, leave blank. If not blank, must reference active Purchasing Groups in config (T024) |
| LIFNR | Vendor | Conditional. If the Control Key is "External", this field is optional. Otherwise, leave blank. If not blank, must reference active Vendor (LFA1) |
| EKORG | Purchasing Organization | Conditional. If the Control Key is "External", this field is required. Otherwise, leave blank. If not blank, must reference active Purchasing Organizations in config (T024E) |
| EBELN | Purchasing Agreement | Conditional. 1st If the operation control key is "External", this field is available. Otherwise, leave this field non editable. If the user provides a value, accept it. If not, leave the field blank. If not blank, must reference active Purchasing Document Item (EKPO-EBELN) |
| EBELP | Purchasing Agreement Item | Conditional. 1st If the operation control key is "External", this field is available. Otherwise, leave this field non editable. If the user provides a value, accept it. If not, leave the field blank. If not blank, must reference active Purchasing Document Item (EKPO-EBELP) |
3.Task List Operation Long Text Line Data Construction Rules
| Field | Field Description | Rule |
|---|---|---|
| zLegacyPLNTY | Legacy Task List Type | Mandatory. Key to link to Task List Operation |
| zLegacyPLNNR | Legacy Key for Task List Group | Mandatory. Key to link to Task List Operation |
| zLegacyPLNAL | Legacy Group Counter | Mandatory. Key to link to Task List Operation |
| zLegacyPLNKN | Number of the Task List Node | Mandatory. Key to link to Task List Operation |
| zLegacyZAEHL | Internal counter | Mandatory. Key to link to Task List Operation |
| zLegacyVORNR | Legacy Activity Number | Mandatory. Key to link to Task List Operation |
| 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) |
| CLUSTD_TAG | Tag column | Mandatory Free Text |
| CLUSTD_LINE | Text Line | Mandatory Free Text |
4.Task List Operation Lean Service Data Construction Rules
Note: If the Task List Operation Control Key is "External" AND "Lean Service" function is activated then Lean Service is mandatory.
Definition:
- External - (PLPO-STEUS=T430-STEUS, T430-LIEF is not blank)
- Lean Service - (PLPO-STEUS=T430-STEUS, T430-SERVICE is not blank)
| Field Name | Field Description | Rule |
|---|---|---|
| zLegacyPLNTY | Legacy Task List Type | Mandatory. Key to link to Task List Operation |
| zLegacyPLNNR | Legacy Task List Group | Mandatory. Key to link to Task List Operation |
| zLegacyPLNAL | Legacy Group Counter | Mandatory. Key to link to Task List Operation |
| zLegacyVORNR | Legacy Activity Number | Mandatory. Key to link to Task List Operation |
| IDNRK | Material Number | Mandatory. Must reference active Material (MARA) which are extended to Plant |
| MAKTX | Material description | Automatically populated |
| IMENG | Component Quantity | If the user provides a value, accept it. If not, leave the field blank. |
| SERVICEDURATION | Service Duration | If the user provides a value, accept it. If not, leave the field blank. |
| SERVICEDURATIONUNIT | Service Duration Unit | If the user provides a value, accept it. If not, leave the field blank. |
5.Task List Component Data Construction Rules
| Field Name | Field Description | Rule |
|---|---|---|
| zLegacyPLNTY | Legacy Task List Type | Mandatory. Key to link to Task List Operation |
| zLegacyPLNNR | Legacy Task List Group | Mandatory. Key to link to Task List Operation |
| zLegacyPLNAL | Legacy Group Counter | Mandatory. Key to link to Task List Operation |
| zLegacyVORNR | Legacy Activity Number | Mandatory. Key to link to Task List Operation |
| IDNRK | Material Number | Mandatory. Must reference active Material (MARA) which are extended to Plant |
| MENGE | Component Quantity | Positive numeric values only |
| MEINS | Component Unit of Measure | |
| RGEKZ | Indicator: Backflush |
6.Maintenance Package Data Construction Rules
| Field Name | Field Description | Rule |
|---|---|---|
| zLegacyPLNTY | Legacy Task List Type | Mandatory. Key to link to Task List Operation |
| zLegacyPLNNR | Legacy Task List Group | Mandatory. Key to link to Task List Operation |
| zLegacyPLNAL | Legacy Group Counter | Mandatory. Key to link to Task List Operation |
| zLegacyVORNR | Legacy Activity Number | Mandatory. Key to link to Task List Operation |
| STRAT | Maintenance Strategy | Non Editable. Direct Mapping from Task List Header: STRAT field |
| PAKET | Maintenance Package Number | Mandatory. ) |
KZYK1 | Short text for the maintenance cycle (time/performance) | ). |
Extraction Dependencies
List the steps that need to occur before extraction can commence
| Item # | Step Description | Team Responsible |
|---|---|---|
| 1 | Ensure Syniti has the necessary connection and access to legacy servers | SyWay A2D Data Team |
| 2 | Ensure that the necessary cleansing activities in legacy sources are complete | SyWay A2D Data Team / Business |
| 3 | Ensure that create, change and deletion of master data is freeze in legacy Production system | Legacy IT |
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/Data owner |
| 7 | Generate load files | SyWay Data Team |
Transformation Rules
1.Task List Header Transformation Rule
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | PF2, WP2 | PLKO | PLNTY | Task List Type | S/4HANA | PLKO | PLNTY | Task List Type | Direct Mapping A-General Maintenance Task List |
| 2 | PF2, WP2 | PLKO | PLNNR | Key for Task List Group | S/4HANA | PLKO | PLNNR | Key for Task List Group | Direct Mapping |
| 3 | PF2, WP2 | EAPL | EQUNR | Equipment Number | S/4HANA | EAPL | EQUNR | Equipment Number | Direct Mapping |
| 4 | PF2, WP2 | TAPL | TPLNR | Functional Location | S/4HANA | TAPL | TPLNR | Functional Location | Direct Mapping |
| 5 | PF2, WP2 | PLKO | DATUV | Valid-From Date | S/4HANA | PLKO | DATUV | Valid-From Date | Default to current date |
| 6 | PF2, WP2 | PLKO | KTEXT | Description | S/4HANA | PLKO | KTEXT | Description | Direct Mapping. Restrict use of special characters. For list of restricted characters, refer to Appendix SR No 1 in : DD-FUN- 050 Master Data Standard_Functional Location |
| 7 | PF2, WP2 | PLKO | WERKS | Planning Plant | S/4HANA | PLKO | WERKS | Planning Plant | Direct Mapping |
| 8 | PF2, WP2 | PLKO | ARBID | Work Centre group with planning function | S/4HANA | PLKO | ARBID | Work Centre group with planning function | Direct Mapping |
| 9 | PF2, WP2 | PLKO | VERWE | Task List Usage | S/4HANA | PLKO | VERWE | Task List Usage | Default to "004" |
| 10 | PF2, WP2 | PLKO | VAGRP | Planner Group | S/4HANA | PLKO | VAGRP | Planner Group | Direct Mapping |
| 11 | PF2, WP2 | PLKO | STATU | Overall Status | S/4HANA | PLKO | STATU | Overall Status | Direct Mapping |
| 12 | PF2, WP2 | PLKO | ANLZU | System Condition | S/4HANA | PLKO | ANLZU | System Condition | Direct Mapping |
| 13 | PF2, WP2 | PLKO | STRAT | Maintenance Strategy | S/4HANA | PLKO | STRAT | Maintenance Strategy | Direct Mapping |
| 14 | PF2, WP2 | PLKO | ISTRU | Assembly | S/4HANA | PLKO | ISTRU | Assembly | Direct Mapping |
| 15 | PF2, WP2 | PLPO | PLNTY | Task List Type | S/4HANA | PLPO | PLNTY | Task List Type | Direct Mapping A-General Maintenance Task List |
| 16 | PF2, WP2 | PLPO | PLNNR | Key for Task List Group | S/4HANA | PLPO | PLNNR | Key for Task List Group | Direct Mapping |
| 17 | PF2, WP2 | PLPO | VORNR | Activity Number | S/4HANA | PLPO | VORNR | Activity Number | Direct Mapping |
| 18 | PF2, WP2 | PLKO | ARBID | Work Centre | S/4HANA | PLPO | ARBID | Work Centre | Default to PLKO-ARBID |
| 19 | PF2, WP2 | PLKO | WERKS | Plant | S/4HANA | PLPO | WERKS | Plant | Default to PLKO-WERKS |
| 20 | |||||||||
| 21 | PF2, WP2 | ESLL | SRVPOS | Activity Number | S/4HANA | ESLL | SRVPOS | Activity Number | Direct Mapping |
| 22 | PF2, WP2 | ESLL | MENGE | Quantity with Sign | S/4HANA | ESLL | MENGE | Quantity with Sign | Direct Mapping |
| 23 | PF2, WP2 | ESLL | MEINS | Base Unit of Measure | S/4HANA | ESLL | MEINS | Base Unit of Measure | Direct Mapping |
| 24 | PF2, WP2 | PLMZ | PLNNR | Task List Key | S/4HANA | PLMZ | PLNNR | Task List Key | Direct Mapping |
| 25 | PF2, WP2 | PLMZ | VORNR | Activity Number | S/4HANA | PLMZ | VORNR | Activity Number | Direct Mapping |
| 26 | PF2, WP2 | PLMZ | GP_MATNR | Material Number | S/4HANA | PLMZ | GP_MATNR | Material Number | Direct Mapping |
| 27 | PF2, WP2 | PLMZ | IMENG | Component Quantity | S/4HANA | PLMZ | IMENG | Component Quantity | Direct Mapping |
| 28 | PF2, WP2 | PLMZ | IMEIN | Component Unit of Measure | S/4HANA | PLMZ | IMEIN | Component Unit of Measure | Direct Mapping |
| 29 | PF2, WP2 | PLMZ | RGEKZ | Indicator: Backflush | S/4HANA | PLMZ | RGEKZ | Indicator: Backflush | Direct Mapping |
| 30 | PF2, WP2 | PLMZ | DISP | Relevancy to Materials Planning/Generation of Purchase Req. | S/4HANA | PLMZ | DISP | Relevancy to Materials Planning/Generation of Purchase Req. | Direct Mapping |
| 31 | PF2, WP2 | PLMZ | STLTY_W | BOM category | S/4HANA | PLMZ | STLTY_W | BOM category | Direct Mapping |
| 32 | PF2, WP2 | PLMZ | WERK_STL | Plant | S/4HANA | PLMZ | WERK_STL | Plant | Direct Mapping |
| 33 | PF2, WP2 | STPO | EKGRP | Purchasing Group | S/4HANA | STPO | EKGRP | Purchasing Group | Direct Mapping |
| 34 | PF2, WP2 | STPO | EKORG | Purchasing Organization | S/4HANA | STPO | EKORG | Purchasing Organization | Direct Mapping |
| 35 | PF2, WP2 | PLMZ | LGORT | Issue Location for Production Order | S/4HANA | PLMZ | LGORT | Issue Location for Production Order | Default to MARC-LGPRO |
| 36 | PF2, WP2 | STPO | LIFNR | Account Number of Supplier | S/4HANA | STPO | LIFNR | Account Number of Supplier | Direct Mapping |
| 37 | PF2, WP2 | PLWP | PLNTY | Task List Type | S/4HANA | PLWP | PLNTY | Task List Type | Direct Mapping |
| 38 | PF2, WP2 | PLWP | PLNNR | Task List Key | S/4HANA | PLWP | PLNNR | Task List Key | Direct Mapping |
| 39 | PF2, WP2 | PLWP | PLNAL | Group Counter | S/4HANA | PLWP | PLNAL | Group Counter | Direct Mapping |
| 40 | PF2, WP2 | PLWP | PLNKN | Number of the Task List Node | S/4HANA | PLWP | PLNKN | Number of the Task List Node | Direct Mapping |
| 41 | PF2, WP2 | PLWP | STRAT | Maintenance Strategy | S/4HANA | PLWP | STRAT | Maintenance Strategy | Direct Mapping |
| 42 | PF2, WP2 | PLWP | PAKET | Maintenance Package Number | S/4HANA | PLWP | PAKET | Maintenance Package Number | Direct Mapping |
| 43 | PF2, WP2 | T351X | KZYK1 | Short text for the maintenance cycle (time/performance) | S/4HANA | T351X | KZYK1 | Short text for the maintenance cycle (time/performance) | Direct Mapping |
2.Task List Operation
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | PF2, WP2 | PLPO | STEUS | Control Key | S/4HANA | PLPO | STEUS | Control Key | Direct Mapping |
| 2 | PF2, WP2 | PLPO | LTXA1 | Operation Description | S/4HANA | PLPO | LTXA1 | Operation Description | Direct Mapping. Restrict use of special characters. For list of restricted characters, refer to Appendix SR No 1 in : DD-FUN- 050 Master Data Standard_Functional Location |
| 3 | PF2, WP2 | PLPO | ARBEI | Work Involved in the Activity | S/4HANA | PLPO | ARBEIT | Work Involved in the Activity | Direct Mapping |
| 4 | PF2, WP2 | PLPO | ARBEH | Unit for Work | S/4HANA | PLPO | ARBEH | Unit for Work | Default to "H" |
| 5 | PF2, WP2 | PLPO | ANZZL | Number of Capacities Required | S/4HANA | PLPO | ANZZL | Number of Capacities Required | Direct Mapping |
| 6 | PF2, WP2 | PLPO | INDET | Key for calculation | S/4HANA | PLPO | INDET | Key for calculation | Default to "1" |
| 7 | PF2, WP2 | PLPO | PRZNT | Work Percentage | S/4HANA | PLPO | PRZNT | Work Percentage | Default to "100" |
| 8 | PF2, WP2 | PLPO | VERTL | Distribution function for capacity requirements | S/4HANA | PLPO | VERTL | Distribution function for capacity requirements | Direct Mapping |
| 9 | PF2, WP2 | PLPO | AUFKT | Execution Factor | S/4HANA | PLPO | AUFKT | Execution Factor | Direct Mapping |
| 10 | PF2, WP2 | PLPO | ANLZU | System Condition | S/4HANA | PLPO | ANLZU | System Condition | Direct Mapping |
| 11 | PF2, WP2 | PLPO | EXECUTION_STAGE | PRE MAIN POST | S/4HANA | PLPO | EXECUTION_STAGE | PRE MAIN POST | Direct Mapping. Default to "MAIN" if blank |
| 12 | PF2, WP2 | PLPO | BMVRG | Order Quantity | S/4HANA | PLPO | BMVRG | Order Quantity | Direct Mapping |
| 13 | PF2, WP2 | PLPO | BMEIH | Order Quantity Unit | S/4HANA | PLPO | BMEIH | Order Quantity Unit | Direct Mapping |
| 14 | PF2, WP2 | PLPO | PLIFZ | Planned Delivery Time in Days | S/4HANA | PLPO | PLIFZ | Planned Delivery Time in Days | Direct Mapping |
| 15 | PF2, WP2 | PLPO | FRDLB | Indicator: External Processing Operation with Subcontracting | S/4HANA | PLPO | FRDLB | Indicator: External Processing Operation with Subcontracting | Direct Mapping |
| 16 | PF2, WP2 | PLPO | SAKTO | Cost Element | S/4HANA | PLPO | SAKTO | Cost Element | Direct Mapping |
| 17 | PF2, WP2 | PLPO | MATKL | Material Group | S/4HANA | PLPO | MATKL | Material Group | Direct Mapping |
| 18 | PF2, WP2 | PLPO | EKGRP | Purchasing Group | S/4HANA | PLPO | EKGRP | Purchasing Group | Direct Mapping |
| 19 | PF2, WP2 | PLPO | LIFNR | Vendor | S/4HANA | PLPO | LIFNR | Vendor | Direct Mapping |
| 20 | PF2, WP2 | PLPO | EKORG | Purchasing Organization | S/4HANA | PLPO | EKORG | Purchasing Organization | Direct Mapping |
| 21 | PF2, WP2 | PLPO | EBELN | Purchasing Agreement | S/4HANA | PLPO | EBELN | Purchasing Agreement | Direct Mapping |
| 22 | PF2, WP2 | PLPO | EBELP | Purchasing Agreement Item | S/4HANA | PLPO | EBELP | Purchasing Agreement Item | Direct Mapping |
3.Task List Operation Long Text Header
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | PLPO | PLNTY | Task List Type | S/4HANA | PLPO | PLNTY | Task List Type | Direct Mapping |
| 2 | DCT | PLPO | PLNNR | Key for Task List Group | S/4HANA | PLPO | PLNNR | Key for Task List Group | Direct Mapping |
| 3 | DCT | PLPO | VORNR | Activity Number | S/4HANA | PLPO | VORNR | Activity Number | Direct Mapping |
| 4 | DCT | STXH | TDOBJECT | Texts: application object | S/4HANA | STXH | TDOBJECT | Texts: application object | Direct Mapping |
| 5 | DCT | STXH | TDOBNAME | Name | S/4HANA | STXH | TDOBNAME | Name | Direct Mapping |
| 6 | DCT | STXH | TDID | Text ID | S/4HANA | STXH | TDID | Text ID | Direct Mapping |
| 7 | DCT | STXH | SPRAS | Language Key | S/4HANA | STXH | SPRAS | Language Key | Direct Mapping |
4.Task List Operation Long Text Line
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | PLPO | PLNTY | Task List Type | S/4HANA | PLPO | PLNTY | Task List Type | Direct Mapping |
| 2 | DCT | PLPO | PLNNR | Key for Task List Group | S/4HANA | PLPO | PLNNR | Key for Task List Group | Direct Mapping |
| 3 | DCT | PLPO | VORNR | Activity Number | S/4HANA | PLPO | VORNR | Activity Number | Direct Mapping |
| 4 | DCT | STXH | TDOBJECT | Texts: application object | S/4HANA | STXH | TDOBJECT | Texts: application object | Default to 'ROUTING' |
| 5 | DCT | STXH | TDOBNAME | Name | S/4HANA | STXH | TDOBNAME | Name | Character 1-3: Direct Mapping to Client Number (eg 100) Character 4: Direct Mapping to zLegacyPLNTY (eg A, E or T) Character 5-12: Direct Mapping to zLegacyPLNNR (eg 00000001, 00000002) Character 13-20: Direct Mapping to zLegacyPLNKN (eg 00000001, 00000002) Character 21-28: Direct Mapping to zLegacyZAEHL (eg 00000001, 00000002) Example: "100A000000010000000100000001" , "100A000000010000000200000002" |
| 6 | DCT | STXH | TDID | Text ID | S/4HANA | STXH | TDID | Text ID | Default to 'LTXT' |
| 7 | DCT | STXH | SPRAS | Language Key | S/4HANA | STXH | SPRAS | Language Key | Direct Mapping |
| 8 | DCT | STXL | CLUSTD_TAG | Tag column | S/4HANA | STXL | CLUSTD_TAG | Tag column | Direct Mapping |
| 9 | DCT | STXL | CLUSTD_LINE | Text Line | S/4HANA | STXL | CLUSTD_LINE | Text Line | Direct Mapping |
5.Task List Operation Lean Service
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | zLegacyPLNTY | S/4HANA | zLegacyPLNTY | Direct Mapping | ||||
| 2 | DCT | zLegacyPLNNR | S/4HANA | zLegacyPLNNR | Direct Mapping | ||||
| 3 | DCT | zLegacyPLNAL | S/4HANA | zLegacyPLNAL | Direct Mapping | ||||
| 4 | DCT | zLegacyVORNR | S/4HANA | zLegacyVORNR | Direct Mapping | ||||
| 5 | DCT | STPO | IDNRK | S/4HANA | STPO | IDNRK | Direct Mapping | ||
| 6 | DCT | MAKT | MAKTX | S/4HANA | MAKT | MAKTX | Direct Mapping | ||
| 7 | - | - | - | - | S/4HANA | STPO | POSTP | Default to 'N' | |
| 8 | DCT | PLMZ | IMENG | S/4HANA | PLMZ | IMENG | Direct Mapping | ||
| 9 | DCT | PLMZ | SERVICEDURATION | S/4HANA | PLMZ | SERVICEDURATION | Direct Mapping | ||
| 10 | DCT | PLMZ | SERVICEDURATIONUNIT | S/4HANA | PLMZ | SERVICEDURATIONUNIT | Direct Mapping |
6.Task List Component
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | zLegacyPLNTY | Legacy Task List Type | S/4HANA | PLPO | PLNTY | Task List Type | Direct Mapping | ||
| 2 | zLegacyPLNNR | Legacy Task List Group | S/4HANA | PLPO | Direct Mapping | ||||
| 3 | zLegacyPLNAL | Legacy Group Counter | S/4HANA | PLPO | Direct Mapping | ||||
| 4 | zLegacyVORNR | Legacy Activity Number | S/4HANA | PLPO | Direct Mapping | ||||
| 5 | DCT | STPO | IDNRK | Material Number | S/4HANA | STPO | IDNRK | Material Number | Direct Mapping |
| 6 | DCT | PLMZ | IMENG | Component Quantity | S/4HANA | PLMZ | IMENG | Component Quantity | Direct Mapping |
| 7 | DCT | PLMZ | IMEIN | Component Unit of Measure | S/4HANA | PLMZ | IMEIN | Component Unit of Measure | Direct Mapping |
| 8 | - | - | - | - | S/4HANA | PLMZ | RGEKZ | Indicator: Backflush |
List of Custom Target Reports for this object is maintained here: Conversion Specification - Custom Reports Register.
Transformation Mapping
Use the exact name and reference this section in the “Transformation rules” above| Mapping Table Name | Mapping Table Description |
|---|---|
| Informal Characters | List of Informal Characters and New Translation |
INC-Task List | Task List inclusion list |
ENR-Task List Operation Lean Service | Task List Operation Lean Service enrichment to assign service details |
Functional Location | Old to new Functional Location |
Equipment Number | Old to new Equipment Number |
Maintenance item | Old to new Maintenance item |
Plant | Old to new Plant |
Work Centre | Old to new Work Centre |
Cost Centre | Old to new Cost Centre |
Maintenance Plan | Old to new Maintenance Plan |
Maintenance Strategy | Old to new Maintenance Strategy |
Maintenance Package | Old to new Maintenance Package |
Material Number | Old to new Material Number |
Transformation Dependencies
List the steps that need to occur before transformation can commence| Item # | Step Description | Team Responsible |
|---|---|---|
| 1 | Ensure DCT tables completeness | Syniti |
| 2 | Ensure all Transformation mappings are up to date. | Syniti |
Pre-Load Validation
Project Team
The following pre-load validations will be performed by the Project Team.Completeness
| Task | Action |
|---|---|
Verify Record Count | SyWay A2D Data Team to verify that the total number of relevant records from legacy systems and DCTs (if any) is equal to the total number of records in the Preload and Load Sheets. |
Verify Data Integrity | SyWay A2D Data Team to verify that the total number of Operations per Work Oder header extracted from legacy systems and DCTs (if any) should be equal to the total number of operations identified in the Preload and Load Sheets |
Accuracy
| Task | Action |
|---|---|
Conversion Accuracy | SyWay A2D Data Team to verify that all fields below meet pass the checks:
|
Review Error Reports | Review and correct the errors. Achieve a zero-error record count as much as possible. Raise defects for data remediated and requiring a correction in the source data. |
Business
The following pre-load validations will be performed by the business.Completeness
| Task | Action |
|---|---|
Verify Record Count | Business Data Owner/s to verify that the total number of relevant records from legacy systems and DCTs (if any) is equal to the total number of records in the Preload and Load Sheets. |
Accuracy
| Task | Action |
|---|---|
Conversion Accuracy | Business Data Owner/s to verify that all fields below meet pass the checks:
|
Load
The load process includes:
- Execute the automated data load into target system using load tool or product the load file if the load must be done manually
- Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation
Load Run Sheet
| Item # | Step Description | Team Responsible |
|---|---|---|
| 1 | Obtain DCT Sign-off from Business | SyWay A2D Data Team |
| 2 | Ensure Pre-load sign-offs are obtained | SyWay A2D Data Team |
| 3 | Proceed with Data load. | SyWay A2D Data Team |
| 4 | Validate few records loaded by accessing standard transactions. | SyWay A2D Data Team |
| 5 | Generate the post load reports in the tool. | SyWay A2D Data Team |
| 6 | Log errors as defects, if any and address resolutions. Close defects. | SyWay A2D Data Team |
| 7 | Generate post load report if step 6 is validated | SyWay A2D 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 A2D Data Team |
Load Phase and Dependencies
Identify the phase as to “when” the load for this object will occur. <Pre-Cutover, Cutover, Post Cutover> and list the steps that need to occur before the load can commence
Configuration
List the Configurations required before loading can commence
| Item # | Configuration Item |
|---|---|
| 1 | T399I-Planning Plant |
| 2 | T001W-Plant |
| 3 | NRIV -Number Ranges for Task List Group |
| 4 | T416-Task List Usage |
| 5 | T0241-Planner Groups |
| 6 | TQ72-Task List Status |
| 7 | T357M-System Condition |
| 8 | T430-Control Key |
| 9 | T006-Unit of Measure |
| 10 | T498-Distribution function |
| 11 | CSLA-Activity Type |
| 12 | CSKA-Cost Element |
| 13 | T024-Purchasing Group |
| 14 | T023-Material Group |
| 15 | LFA1-Supplier |
| 16 | T024E-Purchasing Organization |
| 17 | T430-Operation/Activity control key |
| 18 | T399X-Parameters dependent on order type |
| 19 | TCA41-Default values for standard networks and profiles |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
1001 | Bill of Material |
1002 | Equipment |
1003 | Functional Location |
1010 | Construction Types/Assemblies |
1011 | Documents/DIR |
1016 | Maintenance Plan and Item |
1017 | Maintenance Strategy |
2019 | Material Master |
3018 | Vendors |
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 Control Key | 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 Purchasing Group | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Material Group | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Purchasing Org | 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 Activity Type | Expedite whether the master data is changed in the system |
Invalid Data | Invalid Assembly | 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 Material Number | Expedite whether the master data is changed in the system |
Invalid Data | Invalid Service Number | Expedite whether the master data is changed in the system |
Invalid Data | Invalid Cost Element | Expedite whether the master data is changed in the system |
Invalid Data | Invalid Vendor | Expedite whether the master data is changed in the system |
Invalid Data | Invalid Outline Agreement | Expedite whether the master data is changed in the system |
Invalid Data | Invalid Maintenance BOM | 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.
- Task List is in scope based on data design and any exception requested by business.
- All data cleansing and preparation has been completed.
Any additional key assumptions.
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.