| Status | |
|---|---|
| Owner | |
| Stakeholders | WELENSKY-ext, Dave ERGUIZA-ext, Pinky Love VILARES, ines LEIGHTON-ext, Dean Betty Yue; Aurelia Stefanescu ; [Syniti POD Lead]; [Syniti Consultant] |
Purpose
The purpose of this document is to define the conversion approach to create Task List in S/4 HANA.
Legacy Plant Maintenance Task list is using a diverse range of formats across the different systems. There are instances where the same Work order is duplicated within and/or across sources, with informal words. This results in data inconsistency. As per SyWay design, EAM Maintenance Work order 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 on or after July 1, 2024
- 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
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)
Exceptions:
- Task lists used as part of a periodic plan (e.g., every X period) – exclude all Task List in this criteria unless added to INC-Task List by Business (to be manually reviewed by the Business)
- Task lists With Deletion Indicator or marked for deletion. Check the following tables for delete indicators:
- PLKO-LOEKZ = 'X'
- PLPO-LOEKZ = 'X'
- PLAS-LOEKZ = 'X'
- PLMZ-LOEKZ = 'X'
- PLWP-LOEKZ = 'X'
- Task list having Plant (PLKO-WERKS) not in scope
Reference: SyWay_Cleansing and Historical Scope - A2D
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
PF2, WP2 | An initial extract will be provided to business to evaluate. Additional data/records may be required and these will be constructed via DCT. Enrichment of in-scope data may be required and will be added via transformation rules (business/technical). | 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. Maintenance Plan and Item long texts will also be migrated as List Operation long texts. | 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
Long text and DIR are not covered in this document as they are defined as another data object.
Legal Requirement
Not Applicable
Special Requirements
Not Applicable
Target Design
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 | |
| EAPL | EQUNR | EQUNR | Equipment Number | 18 | Mandatory | |
| TAPL | TPLNR | TPLNR | Functional Location | 30 | Mandatory | |
| PLKO | DATUV | DATUV | Valid-From Date | DATS | 8 | Mandatory |
| PLKO | KTEXT | PLANTEXT | Description | 40 | Mandatory | |
| PLKO | WERKS | WERKS_D | Plant | CHAR | 4 | Mandatory |
| PLKO | ARBID | IGEWERK | Work Centre group with planning function | NUMC | 8 | 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 |
* 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 | 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 |
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 | PREIS | CPREI | Price | 11 | Not Used | |
| STPO | WAERS | WAERS | Currency Key | 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 | Invalid, Inactive or no Material allocated to Task List component | Task List as per Relevancy Criteria assigned with a Material which does not belong below: 1. Material Master (S2P) as per Relevancy Criteria | Material | PF2, WP2 |
1005-002 | C1 | Invalid, Inactive or no Operations attached to Active Task List Header | Task List as per Relevancy Criteria assigned with a Material which does not belong below: | Task List Operation | PF2, WP2 |
1005-003 | C2 | Task lists not used within the last 3 years | Task List as per Relevancy Criteria but are note used across below: | Task List | PF2, WP2 |
1005-004 | C1 | Invalid, Inactive or no Class allocated to Task List component | Task List as per Relevancy Criteria assigned with a Class which does not belong below: 1. Class as per Relevancy Criteria | Class | PF2, WP2 |
1005-005 | C1 | Invalid, Inactive or no Characteristic allocated to Task List component | Task List as per Relevancy Criteria assigned with a Characteristic which does not belong below: | Characteristic | PF2, WP2 |
1005-006 | C1 | Invalid, Inactive or no Construction Type allocated to Task List component | Task List as per Relevancy Criteria assigned with a Construction Type which does not belong below: | Construction Type | PF2, WP2 |
1005-007 | C1 | Invalid or Inactive Bill of Material linked to Task List | Task List as per Relevancy Criteria assigned with a Bill of Material which does not belong below: | Bill of Material | PF2, WP2 |
1005-008 | C1 | 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-009 | C1 | 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-010 | C1 | Invalid or inactive Business Partner (Vendor) linked to Task List | Task List as per Relevancy Criteria assigned with a Material BOM which does not belong below: | Business Partner (Vendor) | PF2, WP2 |
1005-011 | C1 | Invalid or inactive Maintenance Strategy linked to Task List | Task List as per Relevancy Criteria assigned with a Maintenance Strategy which does not belong below: | Maintenance Strategy | PF2, WP2 |
1005-012 | C1 | Invalid, Inactive or no Work Centres linked to Task List Header | Task List as per Relevancy Criteria assigned with a Work Centre which does not belong below: | Work Centre | PF2, WP2 |
1005-013 | C1 | Missing Task Lists Descriptions | Task List as per Relevancy Criteria where there are blank Task List Descriptions. | Task List Description | PF2, WP2 |
1005-014 | C2 | 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-015 | C1 | Task List Plant incorrect | Task List as per Relevancy Criteria with Invalid Plant (T001W) | Plant | PF2, WP2 |
| 1005-016 | C1 | Task List Controlling Areas incorrect | Task List as per Relevancy Criteria with Invalid Controlling Areas (TKA01) | Controlling Area | PF2, WP2 |
Informal Words **
Group 1 | Group 2 | Group 3 | Group 4 | Group 5 |
|---|---|---|---|---|
*DNU | Delete | donot | Formerly | Old # |
.. | Deletion | DONT USE | From | Old[ ] |
/ | DELISTED | DON'T USE | Incorrect | PLEASE USE |
? | Discontinued | Dup Use | Invalid | Pls Use |
@ | Disposable | DUPLICATE | New | Previously |
^ | DNU | -DUPLICATE | NOT ACTIVE | Replace |
+ | Do Not | DUPLICATION | not in use | Replaced |
++ | Do Not Re | Duplicidad | Not Used | RESERVED |
£ | Do Not Sell | Duplikat | NOT VALID | Retired |
Defective | Do Not Use | Former | Obsolete | ZZDEL |
Conversion Process
The high-level process is represented by the diagram below:
For sites that are not on SAP-PF2 and WP2 systems, collection will be done manually in the data collection template.
The high-level process for DCT is represented by the diagram below:
Data Privacy and Sensitivity
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 DCT Rule
| Field Name | Field Description | Rule |
|---|---|---|
| zLegacyPLNTY | Legacy Task List Type | Key field. Select one of the following: A = General TL, E = Equipment, T = Functional Location |
| zLegacyPLNNR | Legacy Task List Group | |
| zLegacyPLNAL | Legacy Group Counter | Key field. Must be ascending sequential within the TLGRP. Eg: 01, 02 etc |
| zLegacyEQUNR | Legacy Equipment Number | |
| zLegacyPLNNR | Legacy Functional Location | |
| PLNTY | Task List Type | Key field. Select one of the following: A = General TL, E = Equipment, T = Functional Location |
| PLNNR | Task List Group | Key field. When PLNTY = A input PLNNR When PLNTY = E input EQUNR When PLNTY = T input TPLNR |
| PLNAL | Group Counter | Key field. Must be ascending sequential within the TLGRP. Eg: 01, 02 etc |
| EQUNR | Equipment Number | Mandatory if zLegacyPLNTY = 'E' |
| TPLNR | Functional Location | Mandatory if zLegacyPLNTY = 'T' |
| DATUV | Valid-From Date | Default to current date |
| KTEXT | Description | Must not be blank. 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 | Must not be blank. Must reference active plant in config (T001W) |
| ARBPL | Work Centre group with planning function | Must not be blank. If PLNTY = A then select manually. Must reference active Work Centre (CRHD) |
| VERWE | Task List Usage | Default to "004" |
| VAGRP | Planner Group | Must not be blank. If PLNTY = A then select manually. Must reference active Planner Group in config (T024A) |
| STATU | Overall Status | Must not be blank. Must reference active Task List Status in config (T412) |
| ANLZU | System Condition | Must reference active Machine Operating Condition in config (T357M). Comments/Special handling notes: |
| STRAT | Maintenance Strategy | Must reference active Maintenance Strategy in config (T351) |
| ISTRU | Assembly | Must not be blank. Must reference active Material (MARA) which are extended to Plant |
| DELKZ | Indicator: Delete completely in reorganization run | Possible values: "X" or blank. "X" to mark record for deletion |
2.Task List Operation DCT Rule
| Field Name | Field Description | Rule |
|---|---|---|
| PLNTY | Task List Type | Key field. Key to link to Task List Header |
| TLGRP | Task List Group | Key field. Key to link to Task List Header |
| PLNAL | Group Counter | Key field. Key to link to Task List Header |
| VORNR | Activity Number | Key field. Must be ascending sequential. Eg: 0010, 0020 etc |
| ARBPL | Work Centre | Must not be blank. Must match the Work Centre of the associated Task List Header |
| PLNKN | Number of the Task List Node | Key field. Must be ascending sequential. Eg: 00000001, 00000002 etc This field is used to link to Long Text |
| ZAEHL | Internal counter | Key field. Must be ascending sequential. Eg: 00000001, 00000002 etc This field is used to link to Long Text |
| WERKS | Plant | Must not be blank. Must match the Plant of the associated Task List Header Must reference active plant in config (T001W) |
| STEUS | Control Key | Must not be blank. Default to CRHD-STEUS Must reference active Control Key in config (T430) |
| LTXA1 | Operation Description | Must not be blank. 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 | |
| ARBEI | Work Involved in the Activity | Must not be blank. |
| ARBEH | Unit for Work | Default to "H" |
| ANZZL | Number of Capacities Required | Must not be blank. |
| INDET | Key for calculation | Default to "1" |
| PRZNT | Work Percentage | Default to "100" |
| VERTN | Distr.cap.reqmts | Must reference active Distribution Function in config (TC29) |
| ANLZU | System Condition | Must reference active Machine operating condition in config (T357M). Comments/Special handling notes: |
| EXECUTION_STAGE | PRE MAIN POST | Default to "MAIN" |
| BMVRG | Order Quantity | If the Control Key is "External", this field is required. Otherwise, leave blank. (External: PLPO-STEUS=T430-STEUS, T430-LIEF is not blank) |
| BMEIH | Order Quantity Unit | If the Control Key is "External", this field is required. Otherwise, leave blank. Must reference active Units of Measurement in config (T006) |
| PLIFZ | Planned Delivery Time in Days | If the Control Key is "External", this field is optional. Otherwise, leave blank. (External: PLPO-STEUS=T430-STEUS, T430-LIEF is not blank) |
| FRDLB | Indicator: External Processing Operation with Subcontracting | If the Control Key is "External", this field is optional. Otherwise, leave blank. (External: PLPO-STEUS=T430-STEUS, T430-LIEF is not blank) |
| SAKTO | Cost Element | If the Control Key is "External", this field is required. Otherwise, leave blank. (External: PLPO-STEUS=T430-STEUS, T430-LIEF is not blank) |
| MATKL | Material Group | If the Control Key is "External", this field is required. Otherwise, leave blank. (External: PLPO-STEUS=T430-STEUS, T430-LIEF is not blank) |
| EKGRP | Purchasing Group | If the Control Key is "External", this field is required. Otherwise, leave blank. Must reference active Purchasing Groups in config (T024) |
| LIFNR | Vendor | If the Control Key is "External", this field is optional. Otherwise, leave blank. Must reference active Vendor (LFA1) |
| EKORG | Purchasing Organization | If the Control Key is "External", this field is required. Otherwise, leave blank. Must reference active Purchasing Organizations in config (T024E) |
| EBELN | Purchasing Agreement | 1st If the operation control key is "External", this field is available. Otherwise, leave this field non editable. (External: PLPO-STEUS=T430-STEUS, T430-LIEF is not blank) 2nd If the "Lean Service" function is activated, this field is generated by system. Otherwise, not used this field. (Lean Service Activate: PLPO-WERKS=T399X-WERKS, T399X-PROCMTINTEGRATIONSCENARIO=M ) |
| EBELP | Purchasing Agreement Item | 1st If the operation control key is "External", this field is available. Otherwise, leave this field non editable. (External: PLPO-STEUS=T430-STEUS, T430-LIEF is not blank) 2nd If the "Lean Service" function is activated, this field is generated by system. Otherwise, not used this field. (Lean Service Activate: PLPO-WERKS=T399X-WERKS, T399X-PROCMTINTEGRATIONSCENARIO=M ) |
3.Task List Operation Long Text Header DCT Rule
| Field Name | Field Description | Rule |
|---|---|---|
| PLNTY | Task List Type | Non-Editable Key to link to Task List Operation Direct Mapping from Key to link to Task List Operation Long Text Line: PLNTY field |
| TLGRP | Key for Task List Group | Non-Editable Key to link to Task List Operation Direct Mapping from Key to link to Task List Operation Long Text Line: TLGRP field |
| PLNAL | Group Counter | Key field. Key to link to Task List Operation Direct Mapping from Key to link to Task List Operation Long Text Line: PLNAL field |
| VORNR | Activity Number | Non-Editable Key to link to Task List Operation Direct Mapping from Key to link to Task List Operation Long Text Line: VORNR field |
| TDOBJECT | Texts: application object | Non-Editable Direct Mapping from Task List Operation Long Text Line: TDOBJECT field |
| PLNKN | Number of the Task List Node | Mandatory. Direct Mapping from Task List Operation Long Text Line: PLNKN field |
| ZAEHL | Internal counter | Mandatory. Direct Mapping from Task List Operation Long Text Line: ZAEHL field |
| TDNAME | Name | Non-Editable Direct Mapping from Task List Operation Long Text Line: TDNAME field |
TDID | Text ID | Non-Editable Direct Mapping from Task List Operation Long Text Line: TDID field |
| TDID | Language Key | Non-Editable Direct Mapping from Task List Operation Long Text Line: TDID field |
4.Task List Operation Long Text Line DCT Rule
| Field | Field Description | Rule |
|---|---|---|
| PLNTY | Task List Type | Mandatory. Key to link to Task List Operation |
| TLGRP | Key for Task List Group | Mandatory. Key to link to Task List Operation |
| PLNAL | Group Counter | Key field. Key to link to Task List Operation |
| VORNR | Activity Number | Mandatory. Key to link to Task List Operation |
| TDOBJECT | Texts: application object | Non-Editable Default to "ROUTING" |
| PLNKN | Number of the Task List Node | Mandatory. Key to link to Task List Operation |
| ZAEHL | Internal counter | Mandatory. Key to link to Task List Operation |
| TDNAME | Name | Non-Editable (Derived upon save) Character 1-3: Direct Mapping to Client Number (eg 100) Character 4: Direct Mapping to PLNTY (eg A) Character 5-12: Direct Mapping to TLGRP (eg 00000001, 00000002) Character 13-20: Direct Mapping to PLNKN (eg 00000001, 00000002) Sample: "100A000000010000000100000001" , "100A000000010000000200000002" |
TDID | Text ID | Non-Editable Default to "LTXT" |
| TDSPRAS | Language Key | Mandatory Must be either one of the following: English, French, Italian, Mandarin, Brazilian, Portuguese, German and Spanish |
| CLUSTD_TAG | Tag column | Mandatory Free Text |
| CLUSTD_LINE | Text Line | Mandatory Free Text |
5.Task List Operation Lean Service DCT Rule
| Field Name | Field Description | Rule |
|---|---|---|
| PLNTY | Task List Type | Mandatory. Key to link to Task List Operation |
| TLGRP | Task List Group | Key field. Key to link to Task List Operation |
| PLNAL | Group Counter | Key field. Key to link to Task List Operation |
| VORNR | Activity Number | Key field. Key to link to Task List Operation |
| IDNRK | Material Number | Key field. Must reference active Material (MARA) which are extended to Plant 1st If the operation control key is "External", this field is available. Otherwise, leave this field non editable. |
| MAKTX | Material description | Automatically populated |
| POSTP | Item category (bill of material) | 1st If the operation control key is "External", this field is available. Otherwise, leave this field non editable. |
| IMENG | Component Quantity | 1st If the operation control key is "External", this field is available. Otherwise, leave this field non editable. |
| SERVICEDURATION | Service Duration | 1st If the operation control key is "External", this field is available. Otherwise, leave this field non editable. |
| SERVICEDURATIONUNIT | Service Duration Unit | 1st If the operation control key is "External", this field is available. Otherwise, leave this field non editable. (External: PLPO-STEUS=T430-STEUS, T430-LIEF is not blank) 2nd If the "Lean Service" function is activated, this field is available. Otherwise, not used this field. (Lean Service Activate: PLPO-WERKS=T399X-WERKS, T399X-PROCMTINTEGRATIONSCENARIO=M ) If the user provides a value, accept it. If not, leave the field blank. |
6.Task List Component DCT Rule
| Field Name | Field Description | Rule |
|---|---|---|
| TLGRP | Task List Group | Key field. Key to link to Task List Operation |
| PLNAL | Group Counter | Key field. Key to link to Task List Operation |
| VORNR | Activity Number | Key field. Key to link to Task List Operation |
| IDNRK | Material Number | Key field. 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 |
7.Maintenance Package DCT Rule
| Field Name | Field Description | Rule |
|---|---|---|
| TLGRP | Task List Group | Key field. Key to link to Task List Operation |
| PLNAL | Group Counter | Key field. Key to link to Task List Operation |
| VORNR | Activity Number | Key field. Key to link to Task List Operation |
| STRAT | Maintenance Strategy | Non Editable. Direct Mapping from Task List Header: STRAT field |
| PAKET | Maintenance Package Number | Must not be blank. ) |
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 |
|
| 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 | Direct Mapping |
| 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 | 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 |
| 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 | PLPO | PLNTY | Task List Type | S/4HANA | PLPO | PLNTY | Task List Type | Direct Mapping |
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 |
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 | Syniti will provide load file | Syniti |
| 3 | Go to <Load Tool> | SyWay A2D Data Team/Syniti |
| 4 | Load 3 records for Maintenance Strategy for function (IA01, IA02, IA05) to validate if data is loaded successfully without errors | SyWay A2D Data Team/Syniti |
| 5 | Proceed with full load if step 4 is validated | SyWay A2D Data Team/Syniti |
| 6 | Validate few records loaded by accessing standard transactions from S/4HNA E.g. IA03, IA04, IA07 | SyWay A2D Data Team/Syniti |
| 7 | Generate post load report if step 6 is validated | SyWay A2D Data Team/Syniti |
Load Phase and Dependencies
Identify the phase as to “when” the load for this object will occur. <Pre-Cutover, Cutover, Post Cutover> and list the steps that need to occur before the load can commence
Configuration
List the Configurations required before loading can commence
| Item # | Configuration Item |
|---|---|
| 1 | 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 |
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 |
2016 | Service Master |
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.