| Status | Revision in Progress |
|---|---|
| Owner | |
| Stakeholders |
Purpose
The purpose of this document is to define the conversion approach to create Work Order in S/4 HANA.
Legacy Plant Maintenance Work order 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 Work Order from Legacy Source Systems into S/4HANA following the Work Order Master Data Design Standard.
The data from legacy system includes:
- Open Work Orders - Outstanding; In Process (Historical for Selected Equipment Type)
The data from legacy system excludes:
- Open Work Order older than 1 month (based on Creation Date)
Exception:
Orders with Technically Completed (TECO) status that have external services assigned – to be manually reviewed by the Business
- Open Priority Work Orders older than 2 weeks (based on Creation Date)
- Work order with user status DUPL or CANC
| 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). | 131137 | S/4HANA | 131137 |
Additional Information
Multi-language Requirement
Notification and Work Order do not have multi language support. Work Order and Notification text will be migrated using EN logon.
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
Target Design
EAM Maintenance Work Order 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.
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
Data Cleansing
| ID | Criticality | Error Message/Report Description | Rule | Output | Source System |
|---|---|---|---|---|---|
9005-001 | C1 | Invalid or Inactive Equipment or Functional Location linked to Work Order | Work Order as per Relevancy Criteria assigned with an Equipment / Functional which does not belong below: The criteria for this report includes all Work Orders with system status not CRTD and not TECO | Equipment, Functional Location | PF1, WP1 |
9005-002 | C1 | Invalid or Inactive Activity Type linked to Work Order | Work Order as per Relevancy Criteria assigned with an Activity Type which does not belong below: | Activity Type | PF1, WP1 |
9005-003 | C1 | Invalid or Inactive Business Partner (Employee Personnel) linked to Work Order | Work Order as per Relevancy Criteria assigned with a Business Partner (Employee Personnel) which does not belong below: | Business Partner (Employee) | PF1, WP1 |
9005-004 | C1 | Invalid or Inactive Cost Centre linked to Work Order | Work Order as per Relevancy Criteria assigned with a Cost Centre which does not belong below: | Cost Centre | PF1, WP1 |
9005-005 | C1 | Invalid or Inactive Maintenance Item linked to Work Order | Work Order as per Relevancy Criteria assigned with a Maintenance Plan and Item which does not belong below: | Maintenance Item | PF1, WP1 |
9005-006 | C1 | Invalid or Inactive Material linked to Work Order | Work Order as per Relevancy Criteria assigned with a Material which does not belong below: | Material | PF1, WP1 |
9005-007 | C1 | Invalid or Inactive Notification linked to Work Order | Work Order as per Relevancy Criteria assigned with a Notification which does not belong below: | Notification | PF1, WP1 |
9005-008 | C1 | Invalid or Inactive Production Resources & Tool linked to Work Order | Work Order as per Relevancy Criteria assigned with a Production Resources & Tool which does not belong below: | Production Resources & Tool | PF1, WP1 |
9005-009 | C1 | Invalid or Inactive Profit Centre linked to Work Order | Work Order as per Relevancy Criteria assigned with a Profit Centre which does not belong below: | Profit Centre | PF1, WP1 |
9005-010 | C1 | Invalid or Inactive Revision linked to Work Order | Work Order as per Relevancy Criteria assigned with a Revision which does not belong below: | Revision | PF1, WP1 |
9005-011 | C1 | Invalid or Inactive Standard Text linked to Work Order | Work Order as per Relevancy Criteria assigned with a Standard Text which does not belong below: | Standard Text | PF1, WP1 |
9005-012 | C1 | Invalid or Inactive Task List linked to Work Order | Work Order as per Relevancy Criteria assigned with a Task List which does not belong below: | Task List | PF1, WP1 |
9005-013 | C1 | Invalid or Inactive WBS linked to Work Order | Work Order as per Relevancy Criteria assigned with a WBS which does not belong below: | Work Breakdown Structure | PF1, WP1 |
9005-014 | C1 | Invalid or Inactive Work Centre linked to Work Order | Work Order as per Relevancy Criteria assigned with a Work Centre which does not belong below: | Work Centre | PF1, WP1 |
9005-015 | C1 | Invalid, Inactive or no Fixed Asset linked to Work Order | Work Order as per Relevancy Criteria assigned with a Fixed Asset which does not belong below: | Fixed Asset | PF1, WP1 |
9005-016 | C1 | Work Orders technically completed but with Open Commitments (POs not closed, Open reservations, Open PR) | TBD | Work Order, Status | PF1, WP1 |
9005-017 | C2 | Open Work Orders older than 12 months | Open Work Orders older than 12 months | Creation Date, Status | PF1, WP1 |
9005-018 | C2 | Open Priority Work Orders older than 3 months | Open Work Orders older than 3 months with Priority as follows: | Creation Date, Status, Priority | PF1, WP1 |
9005-019 | C1 | Notification Storage Location incorrect. | Notificationas per Relevancy Criteria with Invalid Storage Location (T001L) | Storage Location | PF1, WP1 |
9005-020 | C1 | Work Order UOM Missing / incorrect. | Work Order as per Relevancy Criteria with no UoM Assigned or Invalid UoM (T006) | Unit of Measure | PF1, WP1 |
9005-021 | C1 | Work Order Purchasing Groups incorrect. | Work Order as per Relevancy Criteria with Invalid Purchasing Group (T024) | Purchasing Group | PF1, WP1 |
9005-022 | C1 | Work Order Purchasing Organization incorrect. | Work Order as per Relevancy Criteria with Invalid Purchasing Organization (T024E) | Purchasing Organization | PF1, WP1 |
9005-023 | C2 | Work Order Planning Plant and Maintenance Plant are not the same. | Work Order as per Relevancy Criteria with Planning Plant <> Maintenance Plant | Maintenance Plant, Planning Plant | PF1, WP1 |
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:
Data Privacy and Sensitivity
Extraction
Extract data from a source into . There are 2 possibilities:
- The data exists. connects to the source and loads the data into . There are 3 methods:
- Perform full data extraction from relevant tables in the source system(s).
- Perform extraction through the application layer.
- Only if ; 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 . This is to be conducted using DCT (Data Collection Template) in
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 |
|---|---|---|
Selection Screen
| Selection Ref Screen | Parameter Name | Selection Type | Requirement | Value to be entered/set |
|---|---|---|---|---|
Data Collection Template (DCT)
Target Ready Data Collection Template will be created for data with exception of some fields which require transformation as mentioned in the transformation rule.DCT Rules
| Field Name | Field Description | Rule |
|---|---|---|
Extraction Dependencies
| Item # | Step Description | Team Responsible |
|---|---|---|
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 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
- 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 |
|---|---|---|
Transformation Rules
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
Transformation Mapping
| Mapping Table Name | Mapping Table Description |
|---|---|
Transformation Dependencies
List the steps that need to occur before transformation can commence| Item # | Step Description | Team Responsible |
|---|---|---|
Pre-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
Accuracy
| Task | Action |
|---|---|
Business
Completeness
| Task | Action |
|---|---|
Accuracy
| Task | Action |
|---|---|
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 |
|---|---|---|
Load Phase and Dependencies
Configuration
| Item # | Configuration Item |
|---|---|
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
| list the exact title of the conversion object of only the immediate predecessor – this will then confirm the DDD (Data Dependency Diagram) | |
Error Handling
| Error Type | Error Description | Action Taken |
|---|---|---|
Post-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
Accuracy
| Task | Action |
|---|---|
Business
Completeness
| Task | Action |
|---|---|
Accuracy
| Task | Action |
|---|---|
Key Assumptions
- Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
- is in scope based on data design and any exception requested by business.
See also
Change log
Workflow history
| Title | Last Updated By | Updated | Status | |
|---|---|---|---|---|
| There are no pages at the moment. | ||||