| Status | Approved |
|---|---|
| Owner | |
| Stakeholders |
Purpose
The purpose of this document is to define the conversion approach to create Notification in S/4 HANA.
Legacy Plant Maintenance Notification is using a diverse range of formats across the different systems. There are instances where the same Notification is duplicated within and across sources, with informal words. This results in data inconsistency. As per SyWay design, EAM Notification will be standardized.
Conversion Scope
The scope of this document covers the approach for converting active Notification from Legacy Source Systems into S/4HANA following the Notification Master Data Design Standard.
The data from legacy system includes:
- Open Notifications - Outstanding; In Process (Historical for Selected Equipment Type)
- APM specific: Completed/Closed Notifications for Active Functional Locations and Equipment with Item Codes.
The data from legacy system excludes:
- Open Notifications older than 3 months (based on Creation Date) with no Work Order assigned
| 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). | 103918 | S/4HANA | 103918 |
Additional Information
Multi-language Requirement
Notification does 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
Not Applicable
Target Design
EAM Notification 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 |
|---|---|---|---|---|---|
9004-001 | C1 | Invalid or Inactive Equipment or Functional Location linked to Notification | Notification as per Relevancy Criteria assigned with an Equipment / Functional which does not belong below: | Equipment, Functional Location | PF1, WP1 |
9004-002 | C1 | Invalid or Inactive Business Partner (Customer) linked to Notification | Notification as per Relevancy Criteria assigned with a Business Partner (Customer) does not belong below: | Business Partner (Customer) | PF1, WP1 |
9004-003 | C1 | Invalid or Inactive Catalog Code Groups & Code linked to Notification | Notification as per Relevancy Criteria assigned with a Catalog Code Groups & Code does not belong below: | Catalog Code Groups & Code | PF1, WP1 |
9004-004 | C1 | Invalid or Inactive Characteristics linked to Notification | Notification as per Relevancy Criteria assigned with a Characteristic does not belong below: | Characteristic | PF1, WP1 |
9004-005 | C1 | Invalid or Inactive Class linked to Notification | Notification as per Relevancy Criteria assigned with a Class does not belong below: | Class | PF1, WP1 |
9004-006 | C1 | Invalid or Inactive Document Info Record linked to Notification | Notification as per Relevancy Criteria assigned with a Document Info Record does not belong below: | Document Info Record | PF1, WP1 |
9004-007 | C1 | Invalid or Inactive Maintenance Item linked to Notification | Notification as per Relevancy Criteria assigned with a Maintenance Plan and Item does not belong below: | Maintenance Item | PF1, WP1 |
9004-008 | C1 | Invalid or Inactive Revision linked to Notification | Notification as per Relevancy Criteria assigned with a Revision does not belong below: | Revision | PF1, WP1 |
9004-009 | C1 | Invalid or Inactive Work Centre linked to Notification | Notification as per Relevancy Criteria assigned with a Work Centre does not belong below: | Work Centre | PF1, WP1 |
9004-010 | C2 | Open Notifications older than 6 months with No Work Order Assigned | Open Notifications older than 6 months with No Work Order Assigned* Status ORAS = Work Order Assigned | Notification Creation Date | PF1, WP1 |
9004-011 | C1 | Notification Company Code incorrect | Notificationas per Relevancy Criteria with Invalid Company Code (T001) | Company Code, Company Code | PF1, WP1 |
9004-012 | C1 | Invalid or no Planner Group linked to Notification | Notification as per Relevancy Criteria with no Planner Group Assigned or Invalid Planner Group (T024I) | Planner Group | PF1, WP1 |
9004-013 | C1 | Notification Location incorrect. | Notification as per Relevancy Criteria with Invalid Location (T499S) | Location | PF1, WP1 |
9004-014 | C2 | Notification Planning Plant and Maintenance Plant are not the same. | Notification 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:
For sites that are not on SAP-PF2 and WP2 systems, collection will be done manually in the data collection template.
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 |
|---|---|---|
| 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
| 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 Notification data with exception of some fields which require transformation as mentioned in the transformation rule.Notification DCT Rules
| Field Name | Field Description | Rule |
|---|---|---|
Extraction Dependencies
| 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 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 |
|---|---|---|
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 |
|---|---|---|---|---|---|---|---|---|---|
Transformation Mapping
| Mapping Table Name | Mapping Table Description |
|---|---|
AUFK | Work order |
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
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
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
Configuration
| Item # | Configuration Item |
|---|---|
1003 | Functional location |
1002 | Equipment |
1005 | Tasklist |
1016 | Mantenance plan and 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 |
|---|---|
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
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.
- Notification is in scope based on data design and any exception requested by business.
- All data cleansing and preparation has been completed.
- Only valid Legacy outstanding Work Orders that have been supplied by the CIT in the Identified List of Work Order will be converted
See also
Change log
Workflow history
| Title | Last Updated By | Updated | Status | |
|---|---|---|---|---|
| There are no pages at the moment. | ||||