| Status | |
|---|---|
| Owner | |
| Stakeholders | The business stakeholders involved in making, reviewing, and endorsing this decision. Type @ to mention people by name |
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.
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) – to be manually reviewed by the Business
- Task lists With Deletion Indicator or marked for deletion
- Task list having Plant (PLKO-WERKS) not in scope
| 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 |
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
Task List Data strictly adheres to the Master Data Standard. The complete information of the key fields that hold the Class information follows the Master Data Standard document that is located here <include hyperlink>.
The technical design of the target for this conversion approach.
- Task List Header - PLKO
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| PLKO | PLNTY | PLNTY | Task List Type | CHAR | 1 | R |
| PLKO | PLNNR | PLNNR | Key for Task List Group | CHAR | 8 | R |
| PLKO | PLNAL | PLNAL | Group Counter | 2 | R | |
| EAPL | EQUNR | EQUNR | Equipment Number | 18 | R* | |
| TAPL | TPLNR | TPLNR | Functional Location | 30 | R* | |
| PLKO | DATUV | DATUV | Valid-From Date | DATS | 8 | R |
| PLKO | KTEXT | PLANTEXT | Description | 40 | R | |
| PLKO | WERKS | WERKS_D | Planning Plant | CHAR | 4 | R |
| PLKO | ARBID | IGEWERK | Work center group with planning function | NUMC | 8 | R |
| PLKO | VERWE | PLN_VERWE | Task List Usage | CHAR | 3 | R |
| PLKO | VAGRP | VAGRP | Planner Group | CHAR | 3 | R |
| PLKO | STATU | PLNST | Overall Status | CHAR | 3 | R |
| PLKO | ANLZU | ANLZU | System Condition | CHAR | 1 | C |
| PLKO | STRAT | STRAT | Maintenance Strategy | 6 | R | |
| PLKO | ISTRU | ISTRU | Assembly | 40 | R | |
| PLKO | ADPSP | ADDCOMPARE_CORE | Reference Element PM/PS | 40 | NU | |
| PLKO | DELKZ | CP_DELKZ | Indicator: Delete completely in reorganization run | CHAR | 1 | C |
| PLKO | SLWBEZ | QSLWBEZ | Identifier for Inspection Point Field Combination | CHAR | 3 | NU |
| PLKO | EXTNUM | QEXTNUM | External Numbering of Units to Be Inspected | CHAR | 1 | NU |
* 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 | R |
| PLPO | PLNNR | PLNNR | Key for Task List Group | CHAR | 8 | R |
| PLPO | VORNR | VORNR | Activity Number | CHAR | 4 | S |
| PLMZ | GP_UVORN | GP_UVORN | Suboperation | CHAR | 4 | NU |
| PLPO | ARBID | OBJEKTID | Work Center | NUMC | 8 | R |
| PLPO | WERKS | WERKS_D | Plant | CHAR | 4 | R |
| PLPO | STEUS | STEUS | Control Key | CHAR | 4 | R |
| PLPO | LTXA1 | LTXA1 | Operation Description | CHAR | 40 | R |
| PLPO | ARBEI | ARBEIT | Work Involved in the Activity | QUAN | 7(1) | R |
| PLPO | ARBEH | ARBEITE | Unit for Work | UNIT | 3 | R |
| PLPO | ANZZL | ANZKAP | Number of Capacities Required | INT1 | 3 | R |
| PLPO | DAUNO | DAUNOR | Normal Duration of the Activity | QUAN | 5(1) | S |
| PLPO | DAUNE | DAUNORE | Normal Duration/Unit (ISO Format) | UNIT | 3 | S |
| PLPO | INDET | INDET | Key for calculation | CHAR | 1 | R |
| PLPO | PRZNT | APROZENT | Work Percentage | INT1 | 3 | C |
| PLPO | VERTL | VERTEILUNG | Distribution function for capacity requirements | CHAR | 2 | C |
| PLPO | AUFKT | AFAKT | Execution Factor | DEC | 3(0) | C |
| PLPO | LAR01 | LSTAR | Activity Type | CHAR | 6 | S |
| PLPO | KTSCH | KTSCH | Standard Text Key | CHAR | 7 | NU |
| PLPO | ISTRU | ISTRU | Assembly | CHAR | 40 | NU |
| PLPO | LOANZ | LOHNANZ | Number of Time Tickets | DEC | 3(0) | NU |
| PLPO | LOGRP | LOHNGRP | Wage Group | CHAR | 3 | NU |
| PLPO | LOART | LOHNART | Wage type | CHAR | 4 | NU |
| PLPO | QUALF | QUALF | Suitability | CHAR | 2 | NU |
| PLPO | KZLGF | KZLGF | Indicator: Lot-Size-Independent External Processing | CHAR | 1 | NU |
| PLPO | ANLZU | ANLZU | System Condition | CHAR | 1 | C |
| PLPO | EXECUTION_STAGE | EAM_PREMAINPOST | PRE MAIN POST | CHAR | 10 | C |
| PLPO | BMVRG | BMVRG | Order Quantity | QUAN | 13(3) | C |
| PLPO | BMEIH | BMEIH | Order Quantity Unit | UNIT | 3 | C |
| PLPO | PREIS | IPREI | Price Per Unit | 11(2) | S | |
| PLPO | WAERS | WAERS | Currency | CUKY | 5 | S |
| PLPO | PEINH | EPEIN | Unit for Price | DEC | 5(0) | S |
| PLPO | PLIFZ | PLIFZ | Planned Delivery Time in Days | DEC | 3(0) | C |
| PLPO | FRDLB | CO_FRDLB | Indicator: External Processing Operation with Subcontracting | CHAR | 1 | C |
| PLPO | SAKTO | KSTAR | Cost Element | CHAR | 10 | C |
| PLPO | MATKL | MATKL | Material Group | CHAR | 9 | C |
| PLPO | EKGRP | VG_EKGRP | Purchasing Group | CHAR | 3 | C |
| PLPO | LIFNR | LIFNR | Vendor | CHAR | 10 | C |
| PLPO | EKORG | EKORG | Purchasing Organization | CHAR | 4 | C |
| PLPO | EBELN | EBELN | Purchasing Agreement | CHAR | 10 | C |
| PLPO | EBELP | EBELP | Purchasing Agreement Item | NUMC | 5 | C |
| PLPO | SORTL | SORTI | Sort Term | CHAR | 10 | NU |
| PLPO | INFNR | INFNR | Purchasing Info Record | CHAR | 10 | S |
| ESLL | SRVPOS | ASNUM | Activity Number | CHAR | 18 | C |
| ESLL | MENGE | MENGEV | Quantity with Sign | QUAN | 13(3) | C |
| ESLL | MEINS | MEINS | Base Unit of Measure | UNIT | 3 | C |
3. Task List Component
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| PLMZ | PLNNR | PLNNR | Task List Key | CHAR | 8 | R |
| PLMZ | VORNR | VORNR | Activity Number | CHAR | 4 | S |
| STPO | IDNRK | IDNRK | Material Number | CHAR | 40 | C |
| STPO | MENGE | KMPMG | Component Quantity | 1 | C | |
| STPO | MEINS | KMPME | Component Unit of Measure | 3 | C | |
| PLMZ | RGEKZ | RGEKZ | Indicator: Backflush | 1 | C | |
| PLMZ | DISP | DISP_PLUS_1 | Relevancy to Materials Planning/Generation of Purchase Req. | 1 | C | |
| STPO | POTX1 | POTX1 | BOM Item Text (Line 1) | 40 | S | |
| STPO | POSTP | POSTP | Item category (bill of material) | 1 | C | |
| STPO | BEIKZ | BEIKZ | Material Provision Indicator | 1 | NU | |
| PLMZ | WERK_STL | WERKS_D | Plant | 4 | C | |
| STPO | EKGRP | EKGRP | Purchasing Group | 3 | C | |
| STPO | EKORG | EKORG | Purchasing Organization | 4 | C | |
| STPO | PREIS | CPREI | Price | 11 | NU | |
| STPO | WAERS | WAERS | Currency Key | 5 | S | |
| STPO | PEINH | PEINH | Price unit | 5 | S | |
| STPO | MATKL | MATKL | Material Group | 9 | S | |
| STPO | LGORT | CSLGO | Issue Location for Production Order | 4 | C | |
| STPO | LIFNR | LIFNR | Account Number of Supplier | 10 | C | |
| MARC | WEBAZ | WEBAZ | Goods receipt processing time in days | 3 | S | |
| PLMZ | RECIPIENT_LOCATION_CODE | RECIPIENT_LOCATION_CODE | Recipient location code | 15 | NU |
4. Maintenance Package
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| PLWP | PLNTY | PLNTY | Task List Type | CHAR | 1 | R |
| PLWP | PLNNR | PLNNR | Task List Key | CHAR | 8 | R |
| PLWP | PLNAL | PLNAL | Group Counter | 2 | R | |
| PLWP | PLNKN | PLNKN | Number of the Task List Node | 8 | R | |
| PLWP | STRAT | STRAT | Maintenance Strategy | CHAR | 6 | R |
| PLWP | PAKET | PAKETZAEHL | Maintenance Package Number | NUMC | 2 | R |
| T351X | KZYK1 | KTEXTZYK | Short text for the maintenance cycle (time/performance) | CHAR | 2 | R |
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: | 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 inactive or no Task List Operations attached. | 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: | Class Task List as per Relevancy Criteria assigned with a Class which does not belong below: | 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, Inactive or no Production Resources & Tool allocated to Task List component | Task List as per Relevancy Criteria assigned with a Production Resources & Tool which does not belong below: | Production Resources & Tool | PF2, WP2 |
1005-008 | 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-009 | 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-010 | C1 | Active task list components allocated to inactive tsk list operation | Task List Component as per Relevancy Criteria assigned with no or inactive Task List Operations attached. | Task List Component | PF2, WP2 |
1005-011 | C2 | 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-012 | 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-013 | C1 | Invalid, Inactive or no Work Centres linked to Task List | Task List as per Relevancy Criteria assigned with a Work Centre which does not belong below: | Work Centre | PF2, WP2 |
1005-014 | C1 | Missing Task Lists Descriptions | Task List as per Relevancy Criteria where there are blank Task ListDescriptions. | Task List Description | PF2, WP2 |
1005-015 | C2 | Task Lists Descriptions with Informal Words | Task Lists Description | Task List as per Relevancy Criteria which contain [Informal Words] in the Task List Description | PF2, WP2 |
1005-016 | C1 | Task List Plant incorrect. | Task List as per Relevancy Criteria with Invalid Plant (T001W) | Plant | PF2, WP2 |
1005-017 | 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.Task List DCT Rules
| Field Name | Field Description | Rule |
|---|---|---|
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 | Data / 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 | <Add steps from Syniti Migrate here> | SyWay A2D Data Team |
3 | Review and Validate Error and Preload Reports | SyWay A2D Data Team |
4 | Generate Load Files | SyWay A2D Data Team |
Transformation Rules
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | PF2, WP2 | PLKO | PLNTY | Task List Type | S/4HANA | PLKO | PLNTY | Task List Type | Direct Mapping A-General Maintenance Task List |
| 2 | PF2, WP2 | PLKO | PLNNR | Key for Task List Group | S/4HANA | PLKO | PLNNR | Key for Task List Group | Direct Mapping |
| 3 | PF2, WP2 | EAPL | EQUNR | Equipment Number | S/4HANA | EAPL | EQUNR | Equipment Number | Direct Mapping |
| 4 | PF2, WP2 | TAPL | TPLNR | Functional Location | S/4HANA | TAPL | TPLNR | Functional Location | Direct Mapping |
| 5 | PF2, WP2 | PLKO | DATUV | Valid-From Date | S/4HANA | PLKO | DATUV | Valid-From Date | Default value equals to data creation data (Current Date). |
| 6 | PF2, WP2 | PLKO | KTEXT | Description | S/4HANA | PLKO | KTEXT | Description | Direct Mapping. Restrict use of special characters. For list of restricted characters, refer to Appendix SR No 1 in : DD-FUN- 050 Master Data Standard_Functional Location |
| 7 | PF2, WP2 | PLKO | WERKS | Planning Plant | S/4HANA | PLKO | WERKS | Planning Plant | Direct Mapping |
| 8 | PF2, WP2 | PLKO | ARBID | Work center group with planning function | S/4HANA | PLKO | ARBID | Work center 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 |
| PF2, WP2 | PLPO | PLNTY | Task List Type | S/4HANA | PLKO | PLNTY | Task List Type | Direct Mapping A-General Maintenance Task List | |
| PF2, WP2 | PLPO | PLNNR | Key for Task List Group | S/4HANA | PLKO | PLNNR | Key for Task List Group | Direct Mapping | |
| PF2, WP2 | PLPO | VORNR | Activity Number | S/4HANA | PLKO | VORNR | Activity Number | Direct Mapping | |
| 15 | PF2, WP2 | PLPO | ARBID | Work Center | S/4HANA | PLKO | ARBID | Work Center | Default to PLKO-ARBID |
| 16 | PF2, WP2 | PLPO | WERKS | Plant | S/4HANA | PLKO | WERKS | Plant | Default to PLKO-WERKS |
| 17 | PF2, WP2 | PLPO | STEUS | Control Key | S/4HANA | PLKO | STEUS | Control Key | Direct Mapping |
| 18 | PF2, WP2 | PLPO | LTXA1 | Operation Description | S/4HANA | PLKO | 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 |
| 19 | PF2, WP2 | PLPO | ARBEIT | Work Involved in the Activity | S/4HANA | PLKO | ARBEIT | Work Involved in the Activity | Direct Mapping |
| 20 | PF2, WP2 | PLPO | ARBEH | Unit for Work | S/4HANA | PLKO | ARBEH | Unit for Work | Default to "H" |
| 21 | PF2, WP2 | PLPO | ANZZL | Number of Capacities Required | S/4HANA | PLKO | ANZZL | Number of Capacities Required | Direct Mapping |
| 22 | PF2, WP2 | PLPO | INDET | Key for calculation | S/4HANA | PLKO | INDET | Key for calculation | Default to "1" |
| 23 | PF2, WP2 | PLPO | PRZNT | Work Percentage | S/4HANA | PLKO | PRZNT | Work Percentage | Default to "100" |
| VERTL | Distribution function for capacity requirements | VERTL | Distribution function for capacity requirements | Leave blank | |||||
| AUFKT | Execution Factor | AUFKT | Execution Factor | Direct Mapping | |||||
Transformation Mapping
Use the exact name and reference this section in the “Transformation rules” above| Mapping Table Name | Mapping Table Description |
|---|---|
Inclusion - Task List | Task List inclusion list |
IFLOT | Functional Locations |
EQUI | Equipment |
CRHD | Work Centres |
CSKU | Cost Centre |
Transformation Dependencies
List the steps that need to occur before transformation can commence| Item # | Step Description | Team Responsible |
|---|---|---|
1 | Ensure DCT tables completeness | SyWay A2D Data Team |
2 | Value Mappings are according to the latest design -<List of Value Mappings> | SyWay A2D Data Team |
Pre-Load Validation
Project Team
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 | Syniti will provide load file | 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 | Planning Plants |
| 2 | Maintenance Plants |
| 3 | Number Ranges for Task List Groups |
| 4 | Task List Planner Groups |
| 5 | System Condition |
| 6 | Purchasing Group and Purchasing Organization |
| 7 | Material Group |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
1003 | Functional location |
1002 | Equipment |
1016 | Maintenance plan and item |
1017 | Maintenance Strategies & Packages |
Construction Types/ Assemblies | |
| Documents/DIR |
2019 | Material Master |
| Vendors |
| Service Masters |
| Cost Element |
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 |
|---|---|---|
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.