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 (PLKO-ANDAT<= 3 years) (with relevant Maintenance Items assigned (MPOS-WAPOS) or Assigned to relevant Work Orders (AUFK-AUFNR)
- Task List Type (PLKO-PLNTY):
A - General Maintenance Task List
E - Equipment Task List
T - Task List for Functional Location - Assigned to active (Source System Status Not any of these: INAC DLFL) legacy Functional Location (IFLOT-TPLNR) if Task List Type (PLKO-PLNTY) = T
- Assigned to active (Source System Status Not any of these: INAC ESTO AVLB) legacy Equipment (EQUI-EQUNR) if Task List Type (PLKO-PLNTY) = E
- Has at least 1 operation (PLPO-PLNTY, PLPO-PLNNR, PLPO-VORNR)
- Status = Released ((PLKO-STATU) = "2" or "3" or "4")
- Task list having Maintenance Plant (PLKO-WERKS) in scope - Refer to Value Mapping: Plant (Maintenance Plant = Yes)
- Task List Usage (PLKO-VERWE) = "004"
- Task Lists in Inclusion-Task List (this will overwrite all other rules and make the Task List relevant)
- Task List Header Long Text in Inclusion-TL Header Long Text
- Task List Operation Long Text in Inclusion-TL Operation Long Text
The data from legacy system excludes:
- Task lists (PLKO-ANDAT) not used over 3 years. (Definition: No Active Maintenance Items Assigned (MPOS-WAPOS), No Open Work Orders (AUFK-AUFNR)
- Task lists With Deletion Indicator or marked for deletion. Tables to check for deletion indicator (PLKO-LOEKZ, PLAS-LOEKZ, PLPO-LOEKZ, PLMZ-LOEKZ, PLWP-LOEKZ) <> "X"
List of Tables to extract for this object is maintained here: Extract Table Register.
List of source systems and approximate number of records
| 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. Enrichment of in-scope data may be required and will be added via transformation rules. | 61,000 | S/4HANA | 61,000 |
DCT | Task List for plants which do not have data existing from PF2 and WP2 | TBD | S/4 HANA | TBD |
Additional Information
Multi-language Requirement
Task List description will be made available in English.
Multi language is supported for Task List. Login via a different language will have its description displayed in the logon language if the language key is maintained in the Task List.
Document Management
Refer to the KDD085 - Document Management in the SyWay Solution
Note: Documents attached to Task List will be migrated as part of 9104-EAM Attachments.
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 | Mandatory | |
| PLKO | DATUV | DATUV | Valid-From Date | DATS | 8 | Mandatory |
| PLKO | PROFIDNETZ | PROFID_STD | Profile | CHAR | 7 | Conditional |
| PLKO | KTEXT | PLANTEXT | Description | 40 | Mandatory | |
| PLKO | IWERK | IWERK | Planning Plant | CHAR | 4 | Mandatory |
| CRHD | ARBPL | ARBPL | Work Centre | 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 | Conditional | |
| PLKO | DELKZ | CP_DELKZ | Indicator: Delete completely in reorganization run | CHAR | 1 | Conditional |
2.Task List Header Long Text Header
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| STXH | TDOBJECT | TDOBJECT | Texts: application object | CHAR | 10 | Mandatory |
| STXH | TDNAME | TDOBNAME | Name | CHAR | 70 | Mandatory |
| STXH | TDID | TDID | Text ID | CHAR | 4 | Mandatory |
| STXH | TDSPRAS | SPRAS | Language Key | LANG | 1 | Mandatory |
3.Task List Header Long Text Line
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| STXL | TDOBJECT | TDOBJECT | Texts: application object | CHAR | 10 | Mandatory |
| STXL | TDNAME | TDOBNAME | Name | CHAR | 70 | Mandatory |
| STXL | TDID | TDID | Text ID | CHAR | 4 | Mandatory |
| STXL | TDSPRAS | SPRAS | Language Key | LANG | 1 | Mandatory |
| STXL | CLUSTD_TAG | TDFORMAT | Tag column | CHAR | 1 | Mandatory |
| STXL | ROWCOUNT | ROWCOUNT | Row number | NUMC | 10 | Mandatory |
| STXL | TXLINE | TDLINE | Text Line | CHAR | 72 | Mandatory |
Note:
- Long Text is not mandatory, only load when there is data
- One Long Text Header must have at least 1 Long Text Line
4.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 |
| PLKO | PLNAL | PLNAL | Group Counter | 2 | Mandatory | |
| PLPO | VORNR | VORNR | Activity Number | CHAR | 4 | Mandatory |
| PLPO | STEUS | STEUS | Control Key | CHAR | 4 | Conditional |
| PLPO | PLNKN | PLNKN | Number of the Task List Node | 8 | System key field | |
| PLPO | ZAEHL | CIM_COUNT | Internal counter | 8 | System Key field | |
| CRHD | ARBPL | ARBPL | Work Centre | NUMC | 8 | Mandatory |
| PLPO | WERKS | WERKS_D | Plant | 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 | 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) | Mandatory |
| PLPO | ANLZU | ANLZU | System Condition | CHAR | 1 | Conditional |
| PLPO | EXECUTION_STAGE | EAM_PREMAINPOST | PRE MAIN POST | CHAR | 10 | Mandatory |
| PLPO | BMVRG | BMVRG | Order Quantity | QUAN | 13(3) | Conditional |
| PLPO | BMEIH | BMEIH | Order Quantity Unit | UNIT | 3 | Conditional |
| 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 | Outline Agreement | CHAR | 10 | Conditional |
| PLPO | EBELP | EBELP | Item Number of Outline Agreement | NUMC | 5 | Conditional |
Note:
- Each Task List Header must have at least 1 operation
- Each Task List Header can have many operations
5.Task List Operation Long Text Header
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| STXH | TDOBJECT | TDOBJECT | Texts: application object | CHAR | 10 | Mandatory |
| STXH | TDNAME | TDOBNAME | Name | CHAR | 70 | Mandatory |
| STXH | TDID | TDID | Text ID | CHAR | 4 | Mandatory |
| STXH | TDSPRAS | SPRAS | Language Key | LANG | 1 | Mandatory |
6.Task List Operation Long Text Line
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| STXL | TDOBJECT | TDOBJECT | Texts: application object | CHAR | 10 | Mandatory |
| STXL | TDNAME | TDOBNAME | Name | CHAR | 70 | Mandatory |
| STXL | TDID | TDID | Text ID | CHAR | 4 | Mandatory |
| STXL | TDSPRAS | SPRAS | Language Key | LANG | 1 | Mandatory |
| STXL | CLUSTD_TAG | TDFORMAT | Tag column | CHAR | 1 | Mandatory |
| STXL | ROWCOUNT | ROWCOUNT | Row number | NUMC | 10 | Mandatory |
| STXL | TXLINE | TDLINE | Text Line | CHAR | 72 | Mandatory |
Note:
- Long Text is not mandatory, only load when there is data
- Each Long Text Header must have at least 1 Long Text Line
7.Task List Operation Lean Service
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| PLMZ | PLNTY | PLNTY | Task List Type | CHAR | 1 | Mandatory |
| PLMZ | PLNNR | PLNNR | Task List Key | CHAR | 8 | Mandatory |
| PLMZ | PLNAL | PLNAL | Group Counter | 2 | Mandatory | |
| PLPO | VORNR | VORNR | Activity Number | CHAR | 4 | Mandatory |
| STPO | IDNRK | IDNRK | Service Product Number | CHAR | 40 | Mandatory |
| PLMZ | IMENG | KMPMG | Service Base Quantity | 13 | Mandatory | |
| PLMZ | SERVICEDURATION | SERVICEDURATION | Service Duration | 5 | Conditional | |
| PLMZ | SERVICEDURATIONUNIT | SERVICEDURATIONUNIT | Service Duration Unit | 3 | Conditional |
Note: Each Task List Operation can have many lean services
8.Task List Component
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| PLMZ | PLNTY | PLNTY | Task List Type | CHAR | 1 | Mandatory |
| PLMZ | PLNNR | PLNNR | Task List Key | CHAR | 8 | Mandatory |
| PLMZ | PLNAL | PLNAL | Group Counter | 2 | Mandatory | |
| PLPO | VORNR | VORNR | Activity Number | CHAR | 4 | Mandatory |
| STPO | IDNRK | IDNRK | Material Number | CHAR | 40 | Mandatory |
| STPO | MENGE | KMPMG | Component Quantity | 1 | Mandatory | |
| PLMZ | RGEKZ | RGEKZ | Indicator: Backflush | 1 | Conditional | |
| PLMZ | DISP | DISP_PLUS_1 | Relevancy to Materials Planning/Generation of Purchase Req. | 1 | Conditional | |
| PLMZ | WERK_STL | WERKS_D | Plant | 4 | Mandatory | |
| PLMZ | LGORT | LGORT_RES | Storage Location | 4 | Conditional |
Note: Each Task List Operation can have many components
9.Task List 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 |
| PLPO | VORNR | VORNR | Activity Number | CHAR | 4 | Mandatory |
| PLWP | PLNAL | PLNAL | Group Counter | 2 | Mandatory | |
| PLWP | STRAT | STRAT | Maintenance Strategy | CHAR | 6 | Mandatory |
| PLWP | PAKET | PAKETZAEHL | Maintenance Package Number | NUMC | 2 | Mandatory |
Note: Only apply if Task List is assigned to a strategy
10.Task List (Characteristics Values Header)
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| KLAH | KLART | KLASSENART | Class Type | CHAR | 3 | Mandatory |
| INOB | OBTAB | TABELLE | Name of Database Table for Object | CHAR | 30 | Mandatory |
| KLAH | CLASS | KLASSE_D | Class number | CHAR | 18 | Mandatory |
| INOB | OBJEK | CUOBN | Key of Object | CHAR | 90 | Mandatory |
| KLAH | STATU | KLSTATUS | Class Status | CHAR | 1 | Mandatory |
11.Task List (Characteristics Values Allocation)
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| KLAH | KLART | KLASSENART | Class Type | CHAR | 3 | Mandatory |
| INOB | OBTAB | TABELLE | Name of Database Table for Object | CHAR | 30 | Mandatory |
| KLAH | CLASS | KLASSE_D | Class number | CHAR | 18 | Mandatory |
| INOB | OBJEK | CUOBN | Key of Object | CHAR | 90 | Mandatory |
| CABN | ATNAM | ATNAM | Characteristic Name | CHAR | 30 | Mandatory |
| AUSP | ATWRT | ATWRT | Characteristic Value | CHAR | 30 | Mandatory |
| KSML | POSNR | KPOSNR | Item Number | CHAR | 3 | Mandatory |
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-Description: Missing Task Lists Descriptions | Task List as per Relevancy Criteria where there are blank Task List Descriptions. | Task List Type, Key for Task List Group, Plant, Description | PF2, WP2 |
1005-002 | C3 | Info Report: TL Header: Long Text for cleansing | TL Header Long Text for Manual Review. Note: This is used to create Inclusion-TL Header Long Text. Business will then select which Long Text are still relevant from Inclusion-TL Header Long Text. | Task List Type, Key for Task List Group, Plant, Long Text | PF2, WP2 |
1005-003 | C1 | TL Header-Usage : Not 004 | Task List as per Relevancy Criteria meets all other criteria but does not have Usage 004 | Task List Type, Key for Task List Group, Plant, Usage | PF2, WP2 |
1005-004 | C1 | TL Header: Task lists not used within the last 3 years | Task List as per Relevancy Criteria but are not used within the last 3 years across: 1. Maintenance Items as per Relevancy Criteria 2. Work Order as per Relevancy Criteria Note: This will be used to create Inclusion-Task List. Business will then select Task List periodic plan that are still relevant for migration from Inclusion-Task List. | Task List Type, Key for Task List Group, Plant, Date Record Created On | PF2, WP2 |
1005-005 | C1 | TL Operation-Unit for Work: Not 'H' | Task List Operation (as per Relevancy Criteria) Unit for Work <> H. | Task List Type, Key for Task List Group, Activity Number, Plant, Unit for Work | PF2, WP2 |
| 1005-006 | C3 | Info Report: TL Operation: Long Text for cleansing | TL Operation Long Text for Manual Review. Note: This is used to create Inclusion-TL Operation Long Text. Business will then select which Long Text are still relevant from Inclusion-TL Operation Long Text. | Task List Type, Key for Task List Group, Activity Number, Plant, Long Text | PF2, WP2 |
| 1005-007 | C3 | Info Report: Task List not going to be migrated | Task List as per Relevancy Criteria but | Task List Type, Key for Task List Group, Plant, Equipment | PF2, WP2 |
| 1005-008 | Not Applicable | External Cleansing Report: Task Lists not in SAP | Business to create the Task Lists in legacy as part of this cleansing activity. Note: This will be a business-led cleansing activity to be executed as part of the SyWay process. No report development by ADMM | Not Applicable | PF2, WP2 |
Note: List of Cleansing is maintained here: Conversion Specs Register (DCT & Cleansing Report)
Conversion Process
The high-level process is represented by the diagram below:
Collection will be done manually in the Data Collection Template for the following scenarios:
- For sites not on SAP-PF2 or WP2 systems
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 |
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 Task List data with exception of some fields which require transformation as mentioned in the transformation rule.
- The extracted report will be loaded into the required structure using the DCT.
- Standardization activities (including deduplication, standardization and additions) will be carried out within the DCT.
Delta Data Management: Initial collection will be done via the report and one-time load to the DCT will be performed. Any delta after the initial collection within the DCT will require business to take due diligence to ensure any subsequent delta cleansing is verified and aligned within the DCT.
Note: All rules specified below should be documented as a tooltip in the DC Page.
Format:
Line 1: Mandatory / Conditional
Line 2: Remaining text
1.Task List Header Data Construction Rules
| Field Name | Field Description | Rule |
|---|---|---|
| zLegacyPLNNR | Legacy Task List Group | Mandatory. Key Field |
| zLegacyPLNAL | Legacy Group Counter | Mandatory. Key Field |
| PROFIDNETZ | Profile | PF2/WP2 data enrichment: Not used For new data construction: |
| KTEXT | Description | PF2/WP2 data enrichment: Not used For new data construction: Ensure that it does not include any of below characters: |
| IWERK | Planning Plant | PF2/WP2 data enrichment: Not used For new data construction: |
| ARBPL | Work Centre group with planning function | PF2/WP2 data enrichment: Not used For new data construction: |
| zLegacyWERKS | Legacy Plant | Mandatory. Must reference Value Mapping: Plant (Maintenance Plant = Yes) |
| VAGRP | Planner Group | PF2/WP2 data enrichment: Not used For new data construction: |
| ANLZU | System Condition | PF2/WP2 data enrichment: Not used For new data construction: Note: This field is integrated with PPDS scheduling. If user want to block production capacity, please select "0-not in operation"; Otherwise, user could select "1-in operation". |
| STRAT | Maintenance Strategy | PF2/WP2 data enrichment: Not used For new data construction: |
| ISTRU | Assembly | PF2/WP2 data enrichment: Mandatory. For new data construction: |
| A_REGULATORY | Regulatory | PF2/WP2 data enrichment: For new data construction: Note: Will default to "NO" if left blank |
| A_NATURE_OF_WORK | Nature of Work | PF2/WP2 data enrichment: For new data construction: |
2.Task List Header Long Text Line Data Construction Rules
| Field | Field Description | Rule |
|---|---|---|
| zLegacyPLNNR | Legacy Key for Task List Group | Mandatory. Key to link to Task List Header |
| zLegacyPLNAL | Legacy Group Counter | Mandatory. Key to link to Task List Header |
| zLegacyWERKS | Legacy Plant | Mandatory. Must reference Value Mapping: Plant (Maintenance Plant = Yes) |
| 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) |
| ROWCOUNT | Row number | Mandatory. Must be unique and ascending sequential number |
| TXLINE | Text Line | Mandatory Free Text |
3.Task List Operation Data Construction Rules
| Field Name | Field Description | Rule |
|---|---|---|
| zLegacyPLNNR | Legacy Task List Group | Mandatory. Key to link to Task List Header |
| zLegacyPLNAL | Legacy Group Counter | Mandatory. Key to link to Task List Header. Must be unique within the same zLegacyPLNNR. Eg: 01, 02 etc |
| zLegacyVORNR | Legacy Activity Number | Mandatory. Must be unique within the same zLegacyPLNNR Eg: 0010, 0020 etc |
| ARBPL | Work Centre | PF2/WP2 data enrichment: Not used For new data construction: |
| zLegacyWERKS | Legacy Plant | Mandatory. Must match the Plant of the associated Task List Header Must reference Value Mapping: Plant (Maintenance Plant = Yes) |
| LTXA1 | Operation Description | PF2/WP2 data enrichment: Not used For new data construction: |
| AUFKT | Execution Factor | PF2/WP2 data enrichment: Not used For new data construction: Note: Will be default to 1 if blank |
| ARBEI | Work Involved in the Activity | PF2/WP2 data enrichment: Not used For new data construction: |
| ANZZL | Number of Capacities Required | PF2/WP2 data enrichment: Not used For new data construction: |
| VERTN | Distr.cap.reqmts | PF2/WP2 data enrichment: Not used For new data construction: |
| ANLZU | System Condition | PF2/WP2 data enrichment: Not used For new data construction: Note: This field is integrated with PPDS scheduling. If user want to block production capacity, please select "0-not in operation"; Otherwise, user could select "1-in operation". |
| EXECUTION_STAGE | Execution Stage | PF2/WP2 data enrichment: Not used For new data construction: |
| BMVRG | Order Quantity | PF2/WP2 data enrichment: Not used For new data construction: |
| BMEIH | Order Quantity Unit | PF2/WP2 data enrichment: Not used For new data construction: |
| PLIFZ | Planned Delivery Time in Days | PF2/WP2 data enrichment: Not used For new data construction: |
| FRDLB | Indicator: External Processing Operation with Subcontracting | PF2/WP2 data enrichment: Not used For new data construction: |
| SAKTO | Cost Element | PF2/WP2 data enrichment: Not used For new data construction: |
| MATKL | Material Group | PF2/WP2 data enrichment: Not used For new data construction: |
| EKGRP | Purchasing Group | PF2/WP2 data enrichment: Not used For new data construction: |
| zLegacyLIFNR | Legacy Vendor | PF2/WP2 data enrichment: Not used For new data construction: |
| EKORG | Purchasing Organization | PF2/WP2 data enrichment: Not used For new data construction: |
| zLegacyEBELN | Legacy Outline Agreement | PF2/WP2 data enrichment: Not used For new data construction: |
| zLegacyEBELP | Legacy Purchasing Agreement Item | PF2/WP2 data enrichment: Not used For new data construction: |
4.Task List Operation Long Text Line Data Construction Rules
| Field | Field Description | Rule |
|---|---|---|
| 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 |
| zLegacyVORNR | Legacy Activity Number | Mandatory. Key to link to Task List Operation |
| zLegacyWERKS | Legacy Plant | Mandatory. Must reference Value Mapping: Plant (Maintenance Plant = Yes) |
| 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) |
| ROWCOUNT | Row number | Mandatory. Must be unique and ascending sequential number |
| TXLINE | Text Line | Mandatory. Free Text |
5.Task List Operation Lean Service Data Construction Rules
| Field Name | Field Description | Rule |
|---|---|---|
| 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. |
| zLegacyWERKS | Legacy Plant | Mandatory. Must reference Value Mapping: Plant (Maintenance Plant = Yes) |
| zLegacyIDNRK | Legacy Service Product Number | Mandatory.
Must reference active Material (MARA) which are extended to Plant (MARC) |
| IMENG | Service Base Quantity | Mandatory. Positive numeric values only |
| SERVICEDURATION | Service Duration | Conditional. If the user provides a value, accept it. If not, leave the field blank. Positive numeric values only |
| SERVICEDURATIONUNIT | Service Duration Unit | Conditional If the user provides a value, accept it. If not, leave the field blank. If not blank, must reference active Units of Measurement in config (T006-MSEHI) |
6.Task List Component Data Construction Rules
| Field Name | Field Description | Rule |
|---|---|---|
| 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 |
| zLegacyWERKS | Legacy Plant | Mandatory. Must reference Value Mapping: Plant (Maintenance Plant = Yes) |
| zLegacyIDNRK | Legacy Material Number | Mandatory.
Must reference active Material (MARA) which are extended to Plant (MARC) |
| IMENG | Component Quantity | |
| RGEKZ | Indicator: Backflush | |
| DISP | Relevancy to Materials Planning/Generation of Purchase Req. | |
| WERK_STL | Plant |
7.Task List Maintenance Package Data Construction Rules
| Field Name | Field Description | Rule |
|---|---|---|
| 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 |
| zLegacyWERKS | Legacy Plant | Mandatory. Must reference Value Mapping: Plant (Maintenance Plant = Yes) |
| PAKET | Maintenance Package Number | Mandatory. ) where STRAT= |
Note: The DCT above is only applicable when STRAT is not blank
8.Task List Class & Classification Data Construction Rules
a. Asset Specific Task List Characteristic
| Field Name | Field Description | Rule |
|---|---|---|
| zLegacyPLNNR | Legacy Task List Group | Mandatory. Key to link to Task List Header |
| zLegacyPLNAL | Legacy Group Counter | Mandatory. Key to link to Task List Header |
| zLegacyWERKS | Legacy Plant | Mandatory. Must reference Value Mapping: Plant (Maintenance Plant = Yes) |
| ATNAM | Characteristic Name | Allowed values:
|
| ATWRT | Characteristic Value | If ATNAM= "A_ASSET_SPEC_FL" then input relevant Functional Location. Eg.: Assigned Functional Location must exist in Functional Location DCT If ATNAM= "A_ASSET_SPEC_EQ" then input relevant Equipment Number Eg.: Assigned Equipment must exist in Equipment DCT |
| POSNR | Item Number | Mandatory. Positive numeric values only. Must be unique and ascending sequential |
9.Inclusion-Task List
| Field Name | Field Description | Rule |
|---|---|---|
| zLegacyPLNTY | Legacy Task List Type | Mandatory. Key to link to Task List Header |
| zLegacyPLNNR | Legacy Task List Group | Mandatory. Key to link to Task List Header |
| zLegacyPLNAL | Legacy Group Counter | Mandatory. Key to link to Task List Header |
| zLegacyWERKS | Legacy Plant | Mandatory |
Note: This is used to include Task lists not used within the last 3 years which are periodic plans. Only Task List which are added to this list will be considered as relevant for migration.
10.Inclusion-TL Header Long Text
| Field Name | Field Description | Rule |
|---|---|---|
| zLegacyPLNTY | Legacy Task List Type | Mandatory. Key to link to Task List Header |
| zLegacyPLNNR | Legacy Task List Group | Mandatory. Key to link to Task List Header |
| zLegacyPLNAL | Legacy Group Counter | Mandatory. Key to link to Task List Header |
| zLegacyWERKS | Legacy Plant | Mandatory |
| zLegacySPRAS | Legacy Language Key | Mandatory. Allowed values: |
Note: Only Long Texts that are added into this list will be migrated.
11.Inclusion-TL Operation Long Text
| Field Name | Field Description | Rule |
|---|---|---|
| zLegacyPLNTY | Legacy Task List Type | Mandatory. Key to link to Task List Header |
| zLegacyPLNNR | Legacy Task List Group | Mandatory. Key to link to Task List Header |
| zLegacyVORNR | Legacy Activity Number | Mandatory. Key to link to Task List Operation |
| zLegacyWERKS | Legacy Plant | Mandatory |
| zLegacySPRAS | Legacy Language Key | Mandatory. Allowed values: |
Note: Only Long Texts that are added into this list will be migrated.
Note: List of DCTs is maintained here: Conversion Specs Register (DCT & Cleansing Report)
Extraction Dependencies
List the steps that need to occur before extraction can commence
| Item # | Step Description | Team Responsible |
|---|---|---|
| 1 | Relevancy criteria for Equipment | SyWay A2D Data Team |
| 2 | Relevancy criteria for Functional Location | SyWay A2D Data Team |
| 3 | Relevancy criteria for Maintenance Plan and Item | SyWay A2D Data Team |
| 4 | Relevancy criteria for Work Order | SyWay A2D Data Team |
Transformation
The Target fields are mapped to the applicable Legacy field that will be its source, this is a 3-way activity involving the Business, Functional team and Data team. This identifies the transformation activity required to allow Syniti Migrate to make the data Target ready:
- Perform value mapping and data transformation rules.
- Legacy values are mapped to the to-be values (this could include a default value)
- Values are transformed according to the rules defined in Syniti Migrate
- Prepare target-ready data in the structure and format that is required for loading via prescribed Load Tool. This step also produces the load data ready for business to perform Pre-load Data Validation
Transformation Run Sheet
| Item # | Step Description | Team Responsible |
|---|---|---|
| 1 | Obtain DCT Sign-off from Business | SyWay A2D Data Team |
| 2 | In dspMigrate, select the wave – S4/HANA – Plant Maintenance | Syniti |
| 3 | Go to Process Area Launch and Process the Object – Task List | Syniti |
| 4 | Review and Validate Error and Preload Reports | Syniti |
| 5 | Execute the transformation to prepare the target tables | Syniti |
| 6 | Validate data from pre-load and error reports | Business |
| 7 | Generate load files | Syniti |
Transformation Rules
1.Task List Header Transformation Rule (ECC)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4HANA | PLKO | PLNTY | Task List Type | Default to "A" |
| 2 | PF2, WP2 | PLKO | PLNNR | Key for Task List Group | S/4HANA | PLKO | PLNNR | Key for Task List Group | System (Internal numbering) |
| 3 | PF2, WP2 | PLKO | PLNAL | Group Counter | S/4HANA | PLKO | PLNAL | Group Counter | Generate sequence number starting at 01 for each Key for Task List Group |
| 4 | PF2, WP2- | PLKO | ZAEHL | Internal counter | S/4HANA | PLKO | ZAEHL | Internal counter | System (Internal numbering) |
| 5 | - | - | - | - | S/4HANA | PLKO | DATUV | Valid-From Date | Derive the date as per Value Mapping: OTH_Migration_Date Relevant Values A2D (using Object ID "1005" and Field Name = "PLKO-DATUV". |
| 6 | PF2, WP2 | PLKO | PROFIDNETZ | Profile | S/4HANA | PLKO | PROFIDNETZ | Profile | Direct Mapping |
| 7 | PF2, WP2 | PLKO | KTEXT | Description | S/4HANA | PLKO | KTEXT | Description | Direct Mapping |
| 8 | PF2, WP2 | PLKO | IWERK | Planning Plant | S/4HANA | PLKO | IWERK | Planning Plant | Value Mapping: Plant (Maintenance Plant = Yes) |
| 9 | PF2, WP2 | CRHD | ARBPL | Work Centre | S/4HANA | PLKO | ARBPL | Work Centre | Value Mapping: Work Centre |
| 10 | PF2, WP2 | PLKO | WERKS | Plant | S/4HANA | PLKO | WERKS | Plant | Value Mapping: Plant (Maintenance Plant = Yes) |
| 11 | - | - | - | - | S/4HANA | PLKO | VERWE | Task List Usage | Default to "004" |
| 12 | PF2, WP2 | PLKO | VAGRP | Planner Group | S/4HANA | PLKO | VAGRP | Planner Group | Value Mapping: Planner Group |
| 13 | - | - | - | - | S/4HANA | PLKO | STATU | Overall Status | Default to "4" |
| 14 | PF2, WP2 | PLKO | ANLZU | System Condition | S/4HANA | PLKO | ANLZU | System Condition | Value Mapping: System Condition |
| 15 | PF2, WP2 | PLKO | STRAT | Maintenance Strategy | S/4HANA | PLKO | STRAT | Maintenance Strategy | Value Mapping: Maintenance Strategy |
| 16 | PF2, WP2 | PLKO | ISTRU | Assembly | S/4HANA | PLKO | ISTRU | Assembly | Value Mapping: Assembly and Construction Type Overwrite with DCT if provided (as part of enrichment) |
2.Task List Header Transformation Rule (DCT)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4HANA | PLKO | PLNTY | Task List Type | Default to "A" |
| 2 | DCT | PLKO | zLegacyPLNNR | Legacy Key for Task List Group | S/4HANA | PLKO | PLNNR | Key for Task List Group | System (Internal numbering) |
| 3 | DCT | PLKO | zLegacyPLNAL | Legacy Group Counter | S/4HANA | PLKO | PLNAL | Group Counter | Generate sequence number starting at 01 for each Key for Task List Group |
| 4 | - | - | - | - | S/4HANA | PLKO | ZAEHL | Internal counter | System (Internal numbering) |
| 5 | - | - | - | - | S/4HANA | PLKO | DATUV | Valid-From Date | Derive the date as per Value Mapping: OTH_Migration_Date Relevant Values A2D (using Object ID "1005" and Field Name = "PLKO-DATUV". |
| 6 | DCT | PLKO | PROFIDNETZ | Profile | S/4HANA | PLKO | PROFIDNETZ | Profile | Direct Mapping |
| 7 | DCT | PLKO | KTEXT | Description | S/4HANA | PLKO | KTEXT | Description | Direct Mapping |
| 8 | DCT | PLKO | IWERK | Planning Plant | S/4HANA | PLKO | IWERK | Planning Plant | Direct Mapping |
| 9 | DCT | PLKO | ARBPL | Work Centre | S/4HANA | PLKO | ARBPL | Work Centre | Direct Mapping |
| 10 | DCT | PLKO | WERKS | Plant | S/4HANA | PLPO | WERKS | Plant | Direct Mapping |
| 11 | - | - | - | - | S/4HANA | PLKO | VERWE | Task List Usage | Default to "004" |
| 12 | DCT | PLKO | VAGRP | Planner Group | S/4HANA | PLKO | VAGRP | Planner Group | Direct Mapping |
| 13 | - | - | - | - | S/4HANA | PLKO | STATU | Overall Status | Default to "4" |
| 14 | DCT | PLKO | ANLZU | System Condition | S/4HANA | PLKO | ANLZU | System Condition | Direct Mapping |
| 15 | DCT | PLKO | STRAT | Maintenance Strategy | S/4HANA | PLKO | STRAT | Maintenance Strategy | Direct Mapping |
| 16 | DCT | PLKO | ISTRU | Assembly | S/4HANA | PLKO | ISTRU | Assembly | Value Mapping: Assembly and Construction Type |
3.Task List Header Long Text Header Transformation Rule (ECC)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4HANA | STXL | TDOBJECT | Texts: application object | Default to "ROUTING" |
| 2 | - | - | - | - | S/4HANA | STXL | TDNAME | Name | Default to Client Number + Task List Type + Key for Task List Group + Group Counter + Counter Where: Character 1-3: Client Number (eg,: 100) Character 4: Task List Type (eg.: A) Character 5-12: Key for Task List Group (eg.: 00000001, 00000002) Character 13-14: Group Counter (eg.: 01, 02) Character 15-22: Counter (eg.: 00000001, 00000002) Example: "100A000000010100000001", "100A000000010200000002" |
| 3 | - | - | - | - | S/4HANA | STXL | TDID | Text ID | Default to 'PLKO' |
| 4 | PF2, WP2 | STXL | SPRAS | Language Key | S/4HANA | STXL | SPRAS | Language Key | Direct Mapping |
Note: Only the records marked as Cleansed in Inclusion-TL Header Long Text will be migrated
4.Task List Header Long Text Header Transformation Rule (DCT)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4HANA | STXH | TDOBJECT | Texts: application object | Default to 'ROUTING' |
| 2 | - | - | - | - | S/4HANA | STXH | TDNAME | Name | Default to Client Number + Task List Type + Key for Task List Group + Group Counter + Counter Where: Character 1-3: Client Number (eg,: 100) Character 4: Task List Type (eg.: A) Character 5-12: Key for Task List Group (eg.: 00000001, 00000002) Character 13-14: Group Counter (eg.: 01, 02) Character 15-22: Counter (eg.: 00000001, 00000002) Example: "100A000000010100000001", "100A000000010200000002" |
| 3 | - | - | - | - | S/4HANA | STXH | TDID | Text ID | Default to 'PLKO' |
| 4 | DCT | STXL | SPRAS | Language Key | S/4HANA | STXH | SPRAS | Language Key | Direct Mapping |
5.Task List Header Long Text Line Transformation Rule (ECC)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4HANA | STXL | TDOBJECT | Texts: application object | Default to "ROUTING" |
| 2 | - | - | - | - | S/4HANA | STXL | TDNAME | Name | Default to Client Number + Task List Type + Key for Task List Group + Group Counter + Counter Where: Character 1-3: Client Number (eg,: 100) Character 4: Task List Type (eg.: A) Character 5-12: Key for Task List Group (eg.: 00000001, 00000002) Character 13-14: Group Counter (eg.: 01, 02) Character 15-22: Counter (eg.: 00000001, 00000002) Example: "100A000000010100000001", "100A000000010200000002" |
| 3 | - | - | - | - | S/4HANA | STXL | TDID | Text ID | Default to 'PLKO' |
| 4 | PF2, WP2 | STXL | SPRAS | Language Key | S/4HANA | STXL | SPRAS | Language Key | Direct Mapping |
| 5 | - | - | - | - | S/4HANA | STXL | CLUSTD_TAG | Tag column | Default to "*" |
| 6 | PF2, WP2 | STXL | ROWCOUNT | Row number | S/4HANA | STXL | ROWCOUNT | Row number | Direct Mapping |
| 7 | PF2, WP2 | STXL | TXLINE | Text Line | S/4HANA | STXL | TXLINE | Text Line | Direct Mapping |
Note: Only the records marked as Cleansed in Inclusion-TL Header Long Text will be migrated
6.Task List Header Long Text Line Transformation Rule (DCT)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4HANA | STXL | TDOBJECT | Texts: application object | Default to 'ROUTING' |
| 2 | - | - | - | - | S/4HANA | STXL | TDNAME | Name | Default to Client Number + Task List Type + Key for Task List Group + Group Counter + Counter Where: Character 1-3: Client Number (eg,: 100) Character 4: Task List Type (eg.: A) Character 5-12: Key for Task List Group (eg.: 00000001, 00000002) Character 13-14: Group Counter (eg.: 01, 02) Character 15-22: Counter (eg.: 00000001, 00000002) Example: "100A000000010100000001", "100A000000010200000002" |
| 3 | - | - | - | - | S/4HANA | STXL | TDID | Text ID | Default to 'PLKO' |
| 4 | DCT | STXL | SPRAS | Language Key | S/4HANA | STXL | SPRAS | Language Key | Direct Mapping |
| 5 | - | - | - | - | S/4HANA | STXL | CLUSTD_TAG | Tag column | Default to "*" |
| 6 | DCT | STXL | ROWCOUNT | Row number | S/4HANA | STXL | ROWCOUNT | Row number | Direct Mapping |
| 7 | DCT | STXL | TXLINE | Text Line | S/4HANA | STXL | TXLINE | Text Line | Direct Mapping |
7.Task List Operation Transformation Rule (ECC)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | PF2, WP2 | PLPO | PLNTY | Task List Type | S/4HANA | PLPO | PLNTY | Task List Type | Default to "A" |
| 2 | PF2, WP2 | PLPO | PLNNR | Key for Task List Group | S/4HANA | PLPO | PLNNR | Key for Task List Group | System (Internal numbering) |
| 3 | PF2, WP2 | PLKO | PLNAL | Group Counter | S/4HANA | PLKO | PLNAL | Group Counter | Generate sequence number starting at 01 for each Key for Task List Group |
| 4 | PF2, WP2 | PLPO | VORNR | Activity Number | S/4HANA | PLPO | VORNR | Activity Number | System (Internal numbering) |
| 5 | PF2, WP2 | PLPO | PLNKN | Number of the task list node | S/4HANA | PLPO | PLNKN | Number of the task list node | System (Internal numbering) |
| 6 | PF2, WP2 | PLPO | ZAEHL | Internal counter | S/4HANA | PLPO | ZAEHL | Internal counter | System (Internal numbering) |
| 7 | PF2, WP2 | CRHD | ARBPL | Work Centre | S/4HANA | CRHD | ARBPL | Work Centre | Value Mapping: Work Centre |
| 8 | PF2, WP2 | PLKO | WERKS | Plant | S/4HANA | PLPO | WERKS | Plant | Value Mapping: Plant (Maintenance Plant = Yes) |
| 9 | - | - | - | - | S/4HANA | PLPO | STEUS | Control Key | Derive from CRHD-STEUS based on the associated Work Centre |
| 10 | PF2, WP2 | PLPO | LTXA1 | Operation Description | S/4HANA | PLPO | LTXA1 | Operation Description | Direct Mapping |
| 11 | PF2, WP2 | PLPO | ARBEI | Work Involved in the Activity | S/4HANA | PLPO | ARBEIT | Work Involved in the Activity | Direct Mapping |
| 12 | - | - | - | - | S/4HANA | PLPO | ARBEH | Unit for Work | Default to "H" |
| 13 | PF2, WP2 | PLPO | ANZZL | Number of Capacities Required | S/4HANA | PLPO | ANZZL | Number of Capacities Required | Direct Mapping |
| 14 | - | - | - | - | S/4HANA | PLPO | INDET | Key for calculation | Default to "1" |
| 15 | - | - | - | - | S/4HANA | PLPO | PRZNT | Work Percentage | Default to "100" |
| 16 | PF2, WP2 | PLPO | VERTL | Distribution function for capacity requirements | S/4HANA | PLPO | VERTL | Distribution function for capacity requirements | Direct Mapping |
| 17 | PF2, WP2 | PLPO | AUFKT | Execution Factor | S/4HANA | PLPO | AUFKT | Execution Factor | Direct Mapping. Default 1 if blank |
| 18 | PF2, WP2 | PLPO | ANLZU | System Condition | S/4HANA | PLPO | ANLZU | System Condition | Value Mapping: System Condition |
| 19 | - | - | - | - | S/4HANA | PLPO | EXECUTION_STAGE | PRE MAIN POST | Default to "MAIN" |
| 20 | PF2, WP2 | PLPO | BMVRG | Order Quantity | S/4HANA | PLPO | BMVRG | Order Quantity | Direct Mapping |
| 21 | PF2, WP2 | PLPO | BMEIH | Order Quantity Unit | S/4HANA | PLPO | BMEIH | Order Quantity Unit | Direct Mapping |
| 22 | PF2, WP2 | PLPO | PLIFZ | Planned Delivery Time in Days | S/4HANA | PLPO | PLIFZ | Planned Delivery Time in Days | Direct Mapping |
| 23 | PF2, WP2 | PLPO | FRDLB | Indicator: External Processing Operation with Subcontracting | S/4HANA | PLPO | FRDLB | Indicator: External Processing Operation with Subcontracting | Direct Mapping |
| 24 | PF2, WP2 | PLPO | SAKTO | Cost Element | S/4HANA | PLPO | SAKTO | Cost Element | Value Mapping: GL Account Mapping for Cost Element |
| 25 | PF2, WP2 | PLPO | MATKL | Material Group | S/4HANA | PLPO | MATKL | Material Group | Value Mapping: Material Group |
| 26 | PF2, WP2 | PLPO | EKGRP | Purchasing Group | S/4HANA | PLPO | EKGRP | Purchasing Group | Value Mapping: Purchasing Group |
| 27 | PF2, WP2 | PLPO | LIFNR | Vendor | S/4HANA | PLPO | LIFNR | Vendor | Value Mapping: Vendor Number |
| 28 | PF2, WP2 | PLPO | EKORG | Purchasing Organization | S/4HANA | PLPO | EKORG | Purchasing Organization | Value Mapping: Purchasing Organization |
8.Task List Operation Transformation Rule (DCT)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4HANA | PLPO | PLNTY | Task List Type | Default to "A" |
| 2 | DCT | PLPO | zLegacyPLNNR | Legacy Key for Task List Group | S/4HANA | PLPO | PLNNR | Key for Task List Group | System (Internal numbering) |
| 3 | DCT | PLPO | zLegacyPLNAL | Legacy Group Counter | S/4HANA | PLKO | PLNAL | Group Counter | Generate sequence number starting at 01 for each Key for Task List Group |
| 4 | DCT | PLPO | zLegacyVORNR | Legacy Activity Number | S/4HANA | PLPO | VORNR | Activity Number | System (Internal numbering) |
| 5 | DCT | PLPO | ARBPL | Work Centre | S/4HANA | CRHD | ARBPL | Work Centre | Direct Mapping |
| 6 | DCT | PLPO | WERKS | Plant | S/4HANA | PLPO | WERKS | Plant | Direct Mapping |
| 7 | - | - | - | - | S/4HANA | PLPO | STEUS | Control Key | Derive from CRHD-STEUS based on the associated Work Centre |
| 8 | DCT | PLPO | LTXA1 | Operation Description | S/4HANA | PLPO | LTXA1 | Operation Description | Direct Mapping |
| 9 | DCT | PLPO | ARBEI | Work Involved in the Activity | S/4HANA | PLPO | ARBEIT | Work Involved in the Activity | Direct Mapping |
| 10 | - | - | - | - | S/4HANA | PLPO | ARBEH | Unit for Work | Default to "H" |
| 11 | DCT | PLPO | ANZZL | Number of Capacities Required | S/4HANA | PLPO | ANZZL | Number of Capacities Required | Direct Mapping |
| 12 | - | - | - | - | S/4HANA | PLPO | INDET | Key for calculation | Default to "1" |
| 13 | - | - | - | - | S/4HANA | PLPO | PRZNT | Work Percentage | Default to "100" |
| 14 | DCT | PLPO | VERTL | Distribution function for capacity requirements | S/4HANA | PLPO | VERTL | Distribution function for capacity requirements | Direct Mapping |
| 15 | DCT | PLPO | AUFKT | Execution Factor | S/4HANA | PLPO | AUFKT | Execution Factor | Direct Mapping. Default 1 if blank |
| 16 | DCT | PLPO | ANLZU | System Condition | S/4HANA | PLPO | ANLZU | System Condition | Direct Mapping |
| 17 | - | - | - | - | S/4HANA | PLPO | EXECUTION_STAGE | PRE MAIN POST | If not blank then direct Mapping. If blank then default to "MAIN" |
| 18 | DCT | PLPO | BMVRG | Order Quantity | S/4HANA | PLPO | BMVRG | Order Quantity | Direct Mapping |
| 19 | DCT | PLPO | BMEIH | Order Quantity Unit | S/4HANA | PLPO | BMEIH | Order Quantity Unit | Direct Mapping |
| 20 | DCT | PLPO | PLIFZ | Planned Delivery Time in Days | S/4HANA | PLPO | PLIFZ | Planned Delivery Time in Days | Direct Mapping |
| 21 | DCT | PLPO | FRDLB | Indicator: External Processing Operation with Subcontracting | S/4HANA | PLPO | FRDLB | Indicator: External Processing Operation with Subcontracting | Direct Mapping |
| 22 | DCT | PLPO | SAKTO | Cost Element | S/4HANA | PLPO | SAKTO | Cost Element | Direct Mapping |
| 23 | DCT | PLPO | MATKL | Material Group | S/4HANA | PLPO | MATKL | Material Group | Direct Mapping |
| 24 | DCT | PLPO | EKGRP | Purchasing Group | S/4HANA | PLPO | EKGRP | Purchasing Group | Direct Mapping |
| 25 | DCT | PLPO | LIFNR | Vendor | S/4HANA | PLPO | LIFNR | Vendor | Value Mapping: Vendor Number |
| 26 | DCT | PLPO | EKORG | Purchasing Organization | S/4HANA | PLPO | EKORG | Purchasing Organization | Direct Mapping |
9.Task List Operation Transformation Rule (ECC) - Outline Agreement Update
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | PF2, WP2 | PLPO | PLNTY | Task List Type | S/4HANA | PLPO | PLNTY | Task List Type | Value Mapping: Task List Operation |
| 2 | PF2, WP2 | PLPO | PLNNR | Key for Task List Group | S/4HANA | PLPO | PLNNR | Key for Task List Group | Value Mapping: Task List Operation |
| 3 | PF2, WP2 | PLKO | PLNAL | Group Counter | S/4HANA | PLKO | PLNAL | Group Counter | Value Mapping: Task List Header |
| 4 | PF2, WP2 | PLPO | VORNR | Activity Number | S/4HANA | PLPO | VORNR | Activity Number | Value Mapping: Task List Operation |
| 5 | PF2, WP2 | PLPO | ZAEHL | Counter | S/4HANA | PLPO | ZAEHL | Counter | Value Mapping: Task List Operation |
| 6 | PF2, WP2 | PLPO | EBELN | Outline Agreement | S/4HANA | PLPO | EBELN | Outline Agreement | Value Mapping: Purchase Contracts |
| 7 | PF2, WP2 | PLPO | EBELP | Purchasing Agreement Item | S/4HANA | PLPO | EBELP | Purchasing Agreement Item | Value Mapping: Purchase Contracts |
10.Task List Operation Transformation Rule (DCT) - Outline Agreement Update
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | PLPO | zLegacyPLNTY | Legacy Task List Type | S/4HANA | PLPO | PLNTY | Task List Type | Value Mapping: Task List Operation |
| 2 | DCT | PLPO | zLegacyPLNNR | Legacy Key for Task List Group | S/4HANA | PLPO | PLNNR | Key for Task List Group | Value Mapping: Task List Operation |
| 3 | DCT | PLPO | zLegacyPLNAL | Legacy Group Counter | S/4HANA | PLPO | VORNR | Activity Number | Value Mapping: Task List Header |
| 4 | DCT | PLPO | zLegacyVORNR | Legacy Activity Number | S/4HANA | PLPO | ZAEHL | Counter | Value Mapping: Task List Operation |
| 5 | DCT | PLPO | zLegacyEBELN | Legacy Outline Agreement | S/4HANA | PLPO | EBELN | Outline Agreement | Value Mapping: Purchase Contracts |
| 6 | DCT | PLPO | zLegacyEBELP | Legacy Purchasing Agreement Item | S/4HANA | PLPO | EBELP | Purchasing Agreement Item | Value Mapping: Purchase Contracts |
11.Task List Operation Long Text Header Transformation Rule (ECC)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4HANA | STXH | TDOBJECT | Texts: application object | Default to "ROUTING" |
| 2 | PF2, WP2 | STXH | TDOBNAME | Name | S/4HANA | STXH | TDNAME | Name | Default to Client Number + PLNNR + PLNKN + ZAEHL Where: Character 1-3: Client Number (eg.: 100) Character 4: Task List Type (eg.: "A" Character 5-12: Key for Task List Group (eg.: 00000001, 00000002) Character 13-20: Number of the Task List Node (eg.: 00000001, 00000002) Character 21-28: Internal counter (eg.: 00000001, 00000002) Example: "100A000000010000000100000001" , "100A000000010000000200000002" |
| 3 | PF2, WP2 | STXH | TDID | Text ID | S/4HANA | STXH | TDID | Text ID | Default to "PLPO" |
| 4 | PF2, WP2 | STXH | SPRAS | Language Key | S/4HANA | STXH | SPRAS | Language Key | Direct Mapping |
Note: Only the records marked as Cleansed in Inclusion-TL Operation Long Text will be migrated
12.Task List Operation Long Text Header Transformation Rule (DCT)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4HANA | STXH | TDOBJECT | Texts: application object | Default to "ROUTING" |
| 2 | DCT | STXH | TDOBNAME | Name | S/4HANA | STXH | TDNAME | Name | Default to Client Number + PLNNR + PLNKN + ZAEHL Where: Character 1-3: Client Number (eg.: 100) Character 4: Task List Type (eg.: "A" Character 5-12: Key for Task List Group (eg.: 00000001, 00000002) Character 13-20: Number of the Task List Node (eg.: 00000001, 00000002) Character 21-28: Internal counter (eg.: 00000001, 00000002) Example: "100A000000010000000100000001" , "100A000000010000000200000002" |
| 3 | DCT | STXH | TDID | Text ID | S/4HANA | STXH | TDID | Text ID | Default to "PLPO" |
| 4 | DCT | STXH | SPRAS | Language Key | S/4HANA | STXH | SPRAS | Language Key | Direct Mapping |
13.Task List Operation Long Text Line Transformation Rule (ECC)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4HANA | STXL | TDOBJECT | Texts: application object | Default to "ROUTING" |
| 2 | - | - | - | - | S/4HANA | STXL | TDOBNAME | Name | Default to Client Number + PLNNR + PLNKN + ZAEHL Where: Character 1-3: Client Number (eg.: 100) Character 4: Task List Type (eg.: "A" Character 5-12: Key for Task List Group (eg.: 00000001, 00000002) Character 13-20: Number of the Task List Node (eg.: 00000001, 00000002) Character 21-28: Internal counter (eg.: 00000001, 00000002) Example: "100A000000010000000100000001" , "100A000000010000000200000002" |
| 3 | - | - | - | - | S/4HANA | STXL | TDID | Text ID | Default to "PLPO" |
| 4 | PF2, WP2 | STXL | SPRAS | Language Key | S/4HANA | STXL | SPRAS | Language Key | Direct Mapping |
| 5 | - | - | - | - | S/4HANA | STXL | CLUSTD_TAG | Tag column | Default to "*" |
| 6 | PF2, WP2 | STXL | ROWCOUNT | Row number | S/4HANA | STXL | ROWCOUNT | Row number | Direct Mapping |
| 7 | PF2, WP2 | STXL | TXLINE | Text Line | S/4HANA | STXL | TXLINE | Text Line | Direct Mapping |
Note: Only the records marked as Cleansed in Inclusion-TL Operation Long Text will be migrated
14.Task List Operation Long Text Line Transformation Rule (DCT)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4HANA | STXL | TDOBJECT | Texts: application object | Default to "ROUTING" |
| 2 | - | - | - | - | S/4HANA | STXL | TDOBNAME | Name | Default to Client Number + PLNNR + PLNKN + ZAEHL Where: Character 1-3: Client Number (eg.: 100) Character 4: Task List Type (eg.: "A" Character 5-12: Key for Task List Group (eg.: 00000001, 00000002) Character 13-20: Number of the Task List Node (eg.: 00000001, 00000002) Character 21-28: Internal counter (eg.: 00000001, 00000002) Example: 100A000000010000000100000001, 100A000000010000000200000002 |
| 3 | - | - | - | - | S/4HANA | STXL | TDID | Text ID | Default to "PLPO" |
| 4 | DCT | STXL | SPRAS | Language Key | S/4HANA | STXL | SPRAS | Language Key | Direct Mapping |
| 5 | - | - | - | - | S/4HANA | STXL | CLUSTD_TAG | Tag column | Default to "*" |
| 6 | DCT | STXL | ROWCOUNT | Row number | S/4HANA | STXL | ROWCOUNT | Row number | Direct Mapping |
| 7 | DCT | STXL | TXLINE | Text Line | S/4HANA | STXL | TXLINE | Text Line | Direct Mapping |
15.Task List Operation Lean Service Transformation Rule (ECC)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4HANA | PLMZ | PLNTY | Task List Type | Default to "A" |
| 2 | PF2, WP2 | PLMZ | PLNNR | Key for Task List Group | S/4HANA | PLMZ | PLNNR | Key for Task List Group | System (Internal numbering) |
| 3 | PF2, WP2 | PLPO | VORNR | Activity Number | S/4HANA | PLPO | VORNR | Activity Number | System (Internal numbering) |
| 4 | PF2, WP2 | PLMZ | PLNAL | Group Counter | S/4HANA | PLMZ | PLNAL | Group Counter | Generate sequence number starting at 01 for each Key for Task List Group |
| 5 | DCT | STPO | IDNRK | Service Product Number | S/4HANA | STPO | IDNRK | Service Product Number | Value Mapping: Material Master. |
| 6 | - | - | - | - | S/4HANA | PLMZ | IMENG | Component Quantity | Default to "1" |
| 7 | DCT | PLMZ | SERVICEDURATION | Service Duration | S/4HANA | PLMZ | SERVICEDURATION | Service Duration | Direct Mapping Overwrite with DCT if provided (as part of enrichment) |
| 8 | DCT | PLMZ | SERVICEDURATIONUNIT | Service Duration Unit | S/4HANA | PLMZ | SERVICEDURATIONUNIT | Service Duration Unit | Direct Mapping Overwrite with DCT if provided (as part of enrichment) |
Note:
Lean service is mandatory when:
1. Task List Operation is external service (PLPO-STEUS=T430-STEUS, T430-LIEF is not blank and T430-SERVICE is not blank)
2. Service Package with the following condition exists: PLPO-PACKNO=ESLL-PACKNO and ESLL-PACKAGE is not blank, get ESLL-SUB_PACKNO. Extract all data ESLL-SUB_PACKNO=ESLL-PACKNO
16.Task List Operation Lean Service Transformation Rule (DCT)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4HANA | PLMZ | PLNTY | Task List Type | Default to "A" |
| 2 | DCT | - | zLegacyPLNNR | Legacy Task List Group | S/4HANA | PLMZ | PLNNR | Key for Task List Group | System (Internal numbering) |
| 3 | DCT | - | zLegacyVORNR | Legacy Activity Number | S/4HANA | PLPO | VORNR | Activity Number | System (Internal numbering) |
| 4 | DCT | - | zLegacyPLNAL | Legacy Group Counter | S/4HANA | PLMZ | PLNAL | Group Counter | Generate sequence number starting at 01 for each Key for Task List Group |
| 5 | DCT | - | zLegacyIDNRK | Legacy Service Product Number | S/4HANA | STPO | IDNRK | Service Product Number | Value Mapping: Material Master. |
| 6 | - | - | - | - | S/4HANA | PLMZ | IMENG | Component Quantity | Default to "1" |
| 7 | DCT | - | SERVICEDURATION | Service Duration | S/4HANA | PLMZ | SERVICEDURATION | Service Duration | Direct Mapping |
| 8 | DCT | - | SERVICEDURATIONUNIT | Service Duration Unit | S/4HANA | PLMZ | SERVICEDURATIONUNIT | Service Duration Unit | Direct Mapping |
17.Task List Component Transformation Rule (ECC)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4HANA | PLMZ | PLNTY | Task List Type | Default to "A" |
| 2 | PF2, WP2 | PLMZ | PLNNR | Key for Task List Group | S/4HANA | PLMZ | PLNNR | Key for Task List Group | System (Internal numbering) |
| 3 | PF2, WP2 | PLMZ | PLNAL | Group Counter | S/4HANA | PLMZ | PLNAL | Group Counter | Generate sequence number starting at 01 for each Key for Task List Group |
| 4 | PF2, WP2 | PLPO | VORNR | Activity Number | S/4HANA | PLPO | VORNR | Activity Number | System (Internal numbering) |
| 5 | PF2, WP2 | STPO | IDNRK | Material Number | S/4HANA | STPO | IDNRK | Material Number | Value Mapping: Material Master. |
| 6 | PF2, WP2 | PLMZ | IMENG | Component Quantity | S/4HANA | PLMZ | IMENG | Component Quantity | Direct Mapping. |
| 7 | PF2, WP2 | PLMZ | IMEIN | Component Unit of Measure | S/4HANA | PLMZ | IMEIN | Component Unit of Measure | Value Mapping: Unit of Measure. |
| 8 | PF2, WP2 | PLMZ | RGEKZ | Indicator: Backflush | S/4HANA | PLMZ | RGEKZ | Indicator: Backflush | Direct Mapping |
| 9 | 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 |
| 10 | PF2, WP2 | PLMZ | WERK_STL | Plant | S/4HANA | PLMZ | WERK_STL | Plant | Value Mapping: Plant Mapping |
| 11 | PF2, WP2 | PLMZ | LGORT | Storage Location | S/4HANA | PLMZ | LGORT | Storage Location | If field Item Category = "N" then:
|
18.Task List Component Transformation Rule (DCT)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4HANA | PLMZ | PLNTY | Task List Type | Default to "A" |
| 2 | DCT | PLMZ | zLegacyPLNNR | Legacy Task List Group | S/4HANA | PLMZ | PLNNR | Key for Task List Group | System (Internal numbering) |
| 3 | DCT | PLMZ | zLegacyPLNAL | Legacy Group Counter | S/4HANA | PLMZ | PLNAL | Group Counter | Generate sequence number starting at 01 for each Key for Task List Group |
| 4 | DCT | PLMZ | zLegacyVORNR | Legacy Activity Number | S/4HANA | PLPO | VORNR | Activity Number | System (Internal numbering) |
| 5 | DCT | PLMZ | zLegacyIDNRK | Legacy Material Number | S/4HANA | STPO | IDNRK | Material Number | Value Mapping: Material Master. |
| 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 | Derive from MARA-MEINS where IDNRK=MARA-MATNR |
| 8 | DCT | PLMZ | RGEKZ | Indicator: Backflush | S/4HANA | PLMZ | RGEKZ | Indicator: Backflush | Direct Mapping |
| 9 | DCT | PLMZ | DISP | Relevancy to Materials Planning/Generation of Purchase Req. | S/4HANA | PLMZ | DISP | Relevancy to Materials Planning/Generation of Purchase Req. | Direct Mapping |
| 10 | DCT | PLMZ | WERK_STL | Plant | S/4HANA | PLMZ | WERK_STL | Plant | Direct Mapping |
| 11 | - | - | - | - | S/4HANA | PLMZ | LGORT | Storage Location |
19.Task List Package Transformation Rule (ECC)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4HANA | PLWP | PLNTY | Task List Type | Default to "A" |
| 2 | PF2, WP2 | PLWP | PLNNR | Key for Task List Group | S/4HANA | PLWP | PLNNR | Key for Task List Group | System (Internal numbering) |
| 3 | PF2, WP2 | PLWP | PLNAL | Group Counter | S/4HANA | PLWP | PLNAL | Group Counter | Generate sequence number starting at 01 for each Key for Task List Group |
| 4 | PF2, WP2 | PLPO | VORNR | Activity Number | S/4HANA | PLPO | VORNR | Activity Number | System (Internal numbering) |
| 5 | PF2, WP2 | PLWP | STRAT | Maintenance Strategy | S/4HANA | PLWP | STRAT | Maintenance Strategy | Value Mapping: Maintenance Strategy |
| 6 | PF2, WP2 | PLWP | PAKET | Maintenance Package Number | S/4HANA | PLWP | PAKET | Maintenance Package Number | Value Mapping: Maintenance Package |
20.Task List Package Transformation Rule (DCT)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4HANA | PLWP | PLNTY | Task List Type | Default to "A" |
| 2 | DCT | PLWP | zLegacyPLNNR | Legacy Task List Group | S/4HANA | PLWP | PLNNR | Key for Task List Group | System (Internal numbering) |
| 3 | DCT | PLWP | zLegacyPLNAL | Legacy Group Counter | S/4HANA | PLWP | PLNAL | Group Counter | Generate sequence number starting at 01 for each Key for Task List Group |
| 4 | DCT | PLWP | zLegacyVORNR | Legacy Activity Number | S/4HANA | PLPO | VORNR | Activity Number | System (Internal numbering) |
| 5 | DCT | PLWP | STRAT | Maintenance Strategy | S/4HANA | PLWP | STRAT | Maintenance Strategy | Direct Mapping |
| 6 | DCT | PLWP | PAKET | Maintenance Package Number | S/4HANA | PLWP | PAKET | Maintenance Package Number | Direct Mapping |
21.Task List (Characteristics Values Header)
a. Asset Specific Equipment/Asset Specific Task List - Characteristics Values Header (ECC)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4HANA | KLAH | KLART | Class Type | Default to "018" |
| 2 | - | - | - | - | S/4HANA | INOB | OBTAB | Name of Database Table for Object | Default to "PLKO" |
| 3 | - | - | - | - | S/4HANA | KLAH | CLASS | Class | Default to "EAM_9999" |
| 4 | - | - | - | - | S/4HANA | INOB | OBJEK | Key of Object | Default to PLNTY + PLNNR + PLNAL |
| 5 | - | - | - | - | S/4HANA | KLAH | STATU | Class Status | Default to "1" |
22.Task List (Characteristics Values Allocation)
a. Asset Specific Equipment - Characteristics Values Allocation (DCT)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4HANA | KLAH | KLART | Class Type | Default to "018" |
| 2 | - | - | - | - | S/4HANA | INOB | OBTAB | Name of Database Table for Object | Default to "PLKO" |
| 3 | - | - | - | - | S/4HANA | KLAH | CLASS | Class | Default to "EAM_9999" |
| 4 | - | - | - | - | S/4HANA | INOB | OBJEK | Key of Object | Default to PLNTY + PLNNR + PLNAL |
| 5 | - | - | - | - | S/4HANA | CABN | ATNAM | Characteristic Name | Value Mapping: Characteristic A2D where ATNAM = "A_ASSET_SPEC_EQ" |
| 6 | Asset Specific Task List Characteristic DCT | - | ATWRT | Characteristic Value | S/4HANA | AUSP | ATWRT | Characteristic Value | Value Mapping: Equipment |
| 7 | - | - | - | - | S/4HANA | KSML | POSNR | Item Number | Direct Mapping |
b. Asset Specific Equipment - Characteristics Values Allocation (ECC)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4HANA | KLAH | KLART | Class Type | Default to "018" |
| 2 | - | - | - | - | S/4HANA | INOB | OBTAB | Name of Database Table for Object | Default to "PLKO" |
| 3 | - | - | - | - | S/4HANA | KLAH | CLASS | Class | Default to "EAM_9999" |
| 4 | - | - | - | - | S/4HANA | INOB | OBJEK | Key of Object | Default to PLNTY + PLNNR + PLNAL |
| 5 | - | - | - | - | S/4HANA | CABN | ATNAM | Characteristic Name | Value Mapping: Characteristic A2D where ATNAM = "A_ASSET_SPEC_EQ" |
| 6 | PF2, WP2 | TAPL | TPLNR | Functional Location | S/4HANA | AUSP | ATWRT | Characteristic Value | If PLNTY = 'T' then Value Mapping: Equipment where New Equipment is not blank *Note: this field have 2 different source fields |
| 7 | PF2, WP2 | EAPL | EQUNR | Equipment Number | S/4HANA | AUSP | ATWRT | Characteristic Value | If PLNTY = 'E' then Value Mapping: Equipment *Note: this field have 2 different source fields |
| 8 | - | - | - | - | S/4HANA | KSML | POSNR | Item Number | Default to "001" |
Note: These rules apply only when PLKO-EQUNR is not blank
c. Asset Specific Functional Location - Characteristics Values Allocation (DCT)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4HANA | KLAH | KLART | Class Type | Default to "018" |
| 2 | - | - | - | - | S/4HANA | INOB | OBTAB | Name of Database Table for Object | Default to "PLKO" |
| 3 | - | - | - | - | S/4HANA | KLAH | CLASS | Class | Default to "EAM_9999" |
| 4 | - | - | - | - | S/4HANA | INOB | OBJEK | Key of Object | Default to PLNTY + PLNNR + PLNAL |
| 5 | - | - | - | - | S/4HANA | CABN | ATNAM | Characteristic Name | Value Mapping: Characteristic A2D where ATNAM = "A_ASSET_SPEC_FL" |
| 6 | Asset Specific Task List Characteristic DCT | - | ATWRT | Characteristic Value | S/4HANA | AUSP | ATWRT | Characteristic Value | Direct Mapping |
| 7 | - | - | - | - | S/4HANA | KSML | POSNR | Item Number | Direct Mapping |
d. Asset Specific Functional Location - Characteristics Values Allocation (ECC)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4HANA | KLAH | KLART | Class Type | Default to "018" |
| 2 | - | - | - | - | S/4HANA | INOB | OBTAB | Name of Database Table for Object | Default to "PLKO" |
| 3 | - | - | - | - | S/4HANA | KLAH | CLASS | Class | Default to "EAM_9999" |
| 4 | - | - | - | - | S/4HANA | INOB | OBJEK | Key of Object | Default to PLNTY + PLNNR + PLNAL |
| 5 | - | - | - | - | S/4HANA | CABN | ATNAM | Characteristic Name | Value Mapping: Characteristic A2D where ATNAM = "A_ASSET_SPEC_FL" |
| 6 | PF2, WP2 | TAPL | TPLNR | Functional Location | S/4HANA | AUSP | ATWRT | Characteristic Value | If PLNTY = 'T' then Value Mapping: Functional Location where New Functional Location is not blank |
| 7 | - | - | - | - | S/4HANA | KSML | POSNR | Item Number | Default to "001" |
Note: These rules apply only when PLKO-TPLNR is not blank
e. Old Task List No. - Characteristics Values Allocation (ECC)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4HANA | KLAH | KLART | Class Type | Default to "018" |
| 2 | - | - | - | - | S/4HANA | INOB | OBTAB | Name of Database Table for Object | Default to "PLKO" |
| 3 | - | - | - | - | S/4HANA | KLAH | CLASS | Class | Default to "EAM_9999" |
| 4 | - | - | - | - | S/4HANA | INOB | OBJEK | Key of Object | Default to PLNTY + PLNNR + PLNAL |
| 5 | PF2, WP2 | CABN | ATNAM | Characteristic Name | S/4HANA | CABN | ATNAM | Characteristic Name | Value Mapping: Characteristic A2D where ATNAM = "A_OLD_TASK_LIST_NO" |
| 6 | PF2, WP2 | AUSP | ATWRT | Characteristic Value | S/4HANA | AUSP | ATWRT | Characteristic Value | Default to Legacy PLNTY + "|" + Legacy PLNNR + "|" + Legacy PLNAL |
| 7 | - | - | - | - | S/4HANA | KSML | POSNR | Item Number | Default to "001" |
f. Regulatory - Characteristics Values Allocation (ECC and DCT)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4HANA | KLAH | KLART | Class Type | Default to "018" |
| 2 | - | - | - | - | S/4HANA | INOB | OBTAB | Name of Database Table for Object | Default to "PLKO" |
| 3 | - | - | - | - | S/4HANA | KLAH | CLASS | Class | Default to "EAM_9999" |
| 4 | - | - | - | - | S/4HANA | INOB | OBJEK | Key of Object | Default to PLNTY + PLNNR + PLNAL |
| 5 | DCT | - | ATNAM | Characteristic Name | S/4HANA | CABN | ATNAM | Characteristic Name | Value Mapping: Characteristic A2D where ATNAM = "A_REGULATORY" |
| 6 | DCT | - | A_REGULATORY | Regulatory | S/4HANA | AUSP | ATWRT | Characteristic Value | Direct Mapping Default to "NO" if blank |
| 7 | - | - | - | - | S/4HANA | KSML | POSNR | Item Number | Default to "001" |
g. Nature of Work - Characteristics Values Allocation (ECC and DCT)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4HANA | KLAH | KLART | Class Type | Default to "018" |
| 2 | - | - | - | - | S/4HANA | INOB | OBTAB | Name of Database Table for Object | Default to "PLKO" |
| 3 | - | - | - | - | S/4HANA | KLAH | CLASS | Class | Default to "EAM_9999" |
| 4 | - | - | - | - | S/4HANA | INOB | OBJEK | Key of Object | Default to PLNTY + PLNNR + PLNAL |
| 5 | - | - | - | - | S/4HANA | CABN | ATNAM | Characteristic Name | Value Mapping: Characteristic A2D where ATNAM = "A_NATURE_OF_WORK" |
| 6 | DCT | - | A_NATURE_OF_WORK | Nature of Work | S/4HANA | AUSP | ATWRT | Characteristic Value | Direct Mapping |
| 7 | - | - | - | - | S/4HANA | KSML | POSNR | Item Number | Default to "001" |
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 |
|---|---|
Task List | Old to new Task List Header |
Task List Operation | Old to new Task List Operation |
Functional Location | Old to new Functional Location |
Equipment Number | Old to new Equipment Number |
Characteristic A2D | Old to New Characteristic A2D |
Plant | Old to new Plant |
Planner Group | Old to new Planner Group |
Work Centre | Old to new Work Centre |
Maintenance Strategy | Old to new Maintenance Strategy |
Maintenance Package | Old to new Maintenance Package |
Material Master | Old to new Material Number |
Assembly and Construction Type | Mapping of legacy Assembly / Construction Type to new Assembly / Construction Type |
Unit of Measure | Old to New Unit of Measure |
System Condition | Old to new System Condition |
Purchasing Organization | Old to new Purchasing Organization |
Vendor Number | Old Vendor Code to New Vendor Code |
Purchasing Group | Old Purchasing Group to New Purchasing Group |
GL Account Mapping for Cost Element | Old to new Cost Elements |
List of Transformation Mappings with additional details is maintained here: Transformation Mappings
Transformation Dependencies
List the steps that need to occur before transformation can commence| Item # | Step Description | Team Responsible |
|---|---|---|
| 1 | Ensure DCT tables completeness | SyWay Data Team |
| 2 | Ensure all Transformation mappings are up to date. | SyWay Data Team |
Pre-Load Validation
Project Team
The following pre-load validations will be performed by the Project Team.Completeness
| Task | Action |
|---|---|
Verify Record Count | SyWay A2D Data Team to verify that the total number of relevant records from legacy systems and DCTs (if any) is equal to the total number of records in the Preload and Load Sheets. |
Verify Data Integrity | SyWay A2D Data Team to verify that the total number of Operations per Work Oder header extracted from legacy systems and DCTs (if any) should be equal to the total number of operations identified in the Preload and Load Sheets |
Accuracy
| Task | Action |
|---|---|
Conversion Accuracy | SyWay A2D Data Team to verify that all fields below meet pass the checks:
|
Review Error Reports | Review and correct the errors. Achieve a zero-error record count as much as possible. Raise defects for data remediated and requiring a correction in the source data. |
Business
The following pre-load validations will be performed by the business.Completeness
| Task | Action |
|---|---|
Verify Record Count | Business Data Owner/s to verify that the total number of relevant records from legacy systems and DCTs (if any) is equal to the total number of records in the Preload and Load Sheets. |
Accuracy
| Task | Action |
|---|---|
Conversion Accuracy | Business Data Owner/s to verify that all fields below meet pass the checks:
|
Load
The load process includes:
- Execute the automated data load into target system using load tool or product the load file if the load must be done manually
- Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation
Load Run Sheet
| Item # | Step Description | Team Responsible |
|---|---|---|
| 1 | Ensure Pre-load sign-offs are obtained. | SyWay Data team |
| 2 | Go to the load tool and select the correct load Program. | SyWay Data team |
| 3 | Proceed with Data load | SyWay Data team |
| 4 | Validate few records loaded by accessing standard transactions. | SyWay Data team |
| 5 | Generate the post load reports in the tool. | SyWay Data team |
| 6 | Log errors as defects, if any and address resolutions. Close defects. | SyWay Data team |
| 7 | Resolve defects by re-upload and re-generate post load reports if necessary. | SyWay Data team |
| 8 | Business to validate the post load files as part of post-load validation, raise data defects or provide the post-load sign-off. | Business |
| 9 | Repeat steps 5 to 8 if necessary. | SyWay Data team |
Load Phase and Dependencies
Pre-Cutover: 1005 Task List
Pre-Cutover: 1005a Long Text
Pre-Cutover: 1005b Class & Characteristic
Cutover: 1005c Outline Agreement Update
Note: A separate load program may need to be created for 1005a and 1005b if these become a risk to the actual cutover and need to be removed from the critical path. This will be evaluated post Mock 1
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 | T001L-Storage Locations |
| 2 | T001W-Plant |
| 3 | T006-Units of Measurement |
| 4 | T023-Material Group |
| 5 | T024-Purchasing Group |
| 6 | T024A-Planner Groups |
| 7 | T024E-Purchasing Organization |
| 8 | TQ72-Task List Status |
| 9 | T357M-Machine operating condition |
| 10 | T399I-Planning Plant |
| 11 | T411-Task List Usage |
| 12 | T412-Task list status |
| 13 | T418-Item Categories |
| 14 | T430-Control Key |
| 15 | T498-Distribution function |
| 16 | TCA01-Task list types |
| 17 | TCA41-Default values for standard networks and profiles |
| 18 | NRIV -Number Ranges for Task List Group |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
1001 | Bill of Material |
1002 | Equipment |
1003 | Functional Location |
1006 | Work Center |
1009 | Class |
1010 | Construction Types/Assemblies |
1015 | Characteristic |
1016 | Maintenance Plan and Item |
1017 | Maintenance Strategy (including Package) |
1067 | GL Account Operational CoA (incl. secondary CE) |
1081 | Activity Type Groups |
2019 | Material Master |
3018 | Vendors |
9045 | Open Purchase Order |
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 Storage Location | 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 Unit of Measure | 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 Group | Engage Functional team to expedite and fix the error in the system |
| Configuration | Invalid Planner Groups | Engage Functional team to expedite and fix the error in the system |
| Configuration | Invalid Purchasing Organization | Engage Functional team to expedite and fix the error in the system |
| Configuration | Invalid Task List Status | 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 Planning Plant | Engage Functional team to expedite and fix the error in the system |
| Configuration | Invalid Task List Usage | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Task list status | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Item Categories | Engage Functional team to expedite and fix the error in the system |
| Configuration | Invalid Control Key | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Distribution function | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Task list types | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Profile | Engage Functional team to expedite and fix the error in the system |
| Configuration | Invalid Number Ranges for Task List Group | Engage Functional team to expedite and fix the error in the system |
Invalid Data | Invalid Maintenance BOM | Expedite whether the master data is changed in the system |
Invalid Data | Invalid Equipment | Expedite whether the master data is changed in the system |
Invalid Data | Invalid Functional Location | Expedite whether the master data is changed in the system |
Invalid Data | Invalid Work Center | Expedite whether the master data is changed in the system |
Invalid Data | Invalid Class | Expedite whether the master data is changed in the system |
Invalid Data | Invalid Assemblies | Expedite whether the master data is changed in the system |
Invalid Data | Invalid Characteristic | Expedite whether the master data is changed in the system |
Invalid Data | Invalid Maintenance Plan | Expedite whether the master data is changed in the system |
Invalid Data | Invalid Maintenance Strategy | 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 Activity Type | 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 Vendor | Expedite whether the master data is changed in the system |
Invalid Data | Invalid Open Purchase Order | 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.
- Data cleansing has met the required percentage threshold for the specified mock cycle and all preparation activities have been completed
- Data entries in DCT are target-ready data unless a specific transformation rule is stated for that field in the transformation rules.
- sites which do not have legacy data in PF2 and WP2 will create new data using DCTs
- sites which need to use SAP while the project is still ongoing will create the data in PF2 or WP2
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.