| 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 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). | 101641 | S/4HANA | 101641 |
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
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 |
|---|---|---|---|---|---|
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.
The high-level process for DCT is represented by the diagram below:
Data Privacy and Sensitivity
Generally Available Information which would not cause particular harm if people outside SyenSqo were to see it, but which should, nevertheless, be kept safe and not disclosed to third parties in an unrestricted way.
Extraction
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 Notification data with exception of some fields which require transformation as mentioned in the transformation rule.Notification DCT Rules
| Field Name | Field Description | Rule |
|---|---|---|
| zLegacyQMNUM | Legacy Notification Number | Conditional: Legacy Class Number if comes from PF2 or WP2 Legacy Notification Number: For reference only |
| zLegacyQMTXT | Legacy Short Text | Conditional: Legacy Class Number if comes from PF2 or WP2 Legacy Short Text: For reference only |
| QMNUM | Notification Number | Mandatory. Ensure no duplicate. |
| QMART | Notification Type | Values must exist in TQ80 |
| QMTXT | Short Text | Mandatory.
|
| ARTPR | Priority Type | Values must exist in T356A |
| PRIOK | Priority | Values must exist in T356 |
| ERNAM | Name of Person who Created the Object | |
| ERDAT | Date on which the record was created | |
| AENAM | Name of person who changed object | |
| AEDAT | Date of Last Change | |
| MZEIT | Time of Notification | |
| QMDAT | Date of Notification | |
| QMNAM | Name of Person Reporting Notification | |
| STRMN | Required start date | |
| STRUR | Required Start Time | |
| LTRMN | Required End Date | |
| LTRUR | Requested End Time | |
| WAERS | Currency Key | Values must exist in TCURC |
| AUFNR | Order Number | Values must exist in AUFK |
| VERID | Production Version | Values must exist in MKAL |
| RM_MATNR | Material number of the production version | Values must exist in MKAL |
| RM_WERKS | Plant of Production Version | Values must exist in MKAL |
| SA_AUFNR | Run schedule header number | Values must exist in SAFK |
| MATNR | Material Number | Values must exist in MARA |
| REVLV | Revision level | |
| MATKL | Material Group | Values must exist in T023 |
| PRDHA | Product hierarchy | Values must exist in T179 |
| KZKRI | Indicator: Critical part | |
| KZDKZ | Documentation required indicator | |
| KUNUM | Account Number of Customer | Values must exist in KNA1 |
| FEKNZ | Error Records Exist | |
| MAKNZ | Task Records Exist | |
| OBJNR | Object Number for Status Management | Values must exist in ONR00 |
| QMDAB | Date for Notification Completion | |
| QMZAB | Completion Time of Notification | |
| RBNR | Catalog Profile | Values must exist in T352B |
| RBNRI | Origin of Notifications Catalog Profile | |
| INDTX | Object Long Text Available | |
| KZMLA | Primary language indicator for text segment | |
| HERKZ | Origin of Notification | |
| BEZDT | Notification Reference Date | |
| BEZUR | Notification Reference Time | |
| LIFNUM | Supplier Account Number | Values must exist in LFA1 |
| BUNAME | Author of a Q/PM Notification | |
| VBELN | Sales Order Number | Values must exist in VBAK |
| BSTNK | Customer Reference | |
| BSTDK | Customer Reference Date | |
| SPART | Division | Values must exist in TSPA |
| VKORG | Sales Organization | Values must exist in TVKO |
| VTWEG | Distribution Channel | Values must exist in TVTW |
| ADRNR | Addresses: Address Number | |
| AEZEIT | Time of Change | |
| ERZEIT | Time at Which Record Was Added | |
| MAWERK | Plant for Material | Values must exist in T001W |
| QMKAT | Catalog Type - Coding | Values must exist in TQ15 |
| QMGRP | Code Group - Coding | Values must exist in QPGR |
| QMCOD | Coding | |
| AUSWIRK | Key for a Scenario | Values must exist in TQ81 |
| TEILEV | Usage of Parts | Values must exist in TQ81V |
| PRUEFLOS | Inspection Lot Number | Values must exist in QALS |
| CHARG | Batch Number | Values must exist in MCH1 |
| LGORTCHARG | Storage Location of Batch | Values must exist in T001L |
| LICHN | Supplier Batch Number | |
| HERSTELLER | Number of Manufacturer | Values must exist in LFA1 |
| EMATNR | Material number corresponding to manufacturer part number | Values must exist in MARA |
| EKORG | Purchasing organization | Values must exist in T024E |
| BKGRP | Purchasing Group | Values must exist in T024 |
| LGORTVORG | Storage Location for Inspection Lot Stock | Values must exist in T001L |
| FERTAUFNR | Order Number (Production Order) | Values must exist in AUFK |
| FERTAUFPL | Plan Number for Operations in Order (Production Order) | |
| EBELN | Purchasing Document Number | Values must exist in EKKO |
| EBELP | Item Number of Purchasing Document | Values must exist in EKPO |
| MJAHR | Material Document Year | |
| MBLNR | Number of Material Document | |
| MBLPO | Item in Material Document | |
| LS_KDAUF | Sales Order Number | Values must exist in VBAK |
| LS_KDPOS | Item number of the SD document | Values must exist in VBAP |
| LS_VBELN | Delivery | Values must exist in LIKP |
| LS_POSNR | Delivery Item | Values must exist in LIPS |
| CROBJTY | Object types of the CIM resource | |
| ARBPL | Object ID of the Work Center | Values must exist in CRID |
| ARBPLWERK | Plant for Work Center | Values must exist in T001W |
| FEART | Report Type for Defects Recording | Values must exist in TQ86 |
| PNLKN | Current Node Number from Order Counter | |
| MGEIG | Defective Quantity (Internal) | |
| MGFRD | Defective Quantity (External) | |
| MGEIN | Unit of Measure | Values must exist in T006 |
| BZMNG | General Reference Quantity | |
| RKMNG | Complaint Quantity | |
| RGMNG | Return Delivery Quantity | |
| RKDAT | Date of Return Delivery | |
| COAUFNR | Order Number (QM Order) | Values must exist in AUFK |
| QWRNUM | Reference Notification Number | Values must exist in QMEL |
| REFNUM | External Reference Number | |
| KDMAT | Material Number Used by Customer | |
| IDNLF | Material Number Used by Supplier | |
| SERIALNR | Serial Number | |
| KZLOESCH | Delete Data Record | |
| CVP_XBLCK | Business Purpose Completed Flag | |
| PRODDAT | Production Date | |
| DEVICEID | Additional Device Data | |
| VKBUR | Sales office | Values must exist in TVKBZ |
| VKGRP | Sales group | Values must exist in TVBVK |
| AUTKZ | Data Record Created with Function 'Create with Copy Model' | |
| BEDID | ID of the Capacity Requirements Record | |
| BEDZL | Internal counter | |
| PROFIL_TYP | Object Type | |
| PROFIL_ID | Object ID | |
| HANDLE | Globally unique identifier (linked to time segment, etc) | |
| TSEGFL | Time segment exists | |
| TSEGTP | Template | Values must exist in TTSEGTPLH |
| TZONSO | Time Zone for Notification | Values must exist in TTZZ |
| TZONID | Origin of Time Zone in Notification | |
| FUNKTION | Keys for Function in Action Box | |
| /SAPSMOSS/INSTN | Installation number | |
| /SAPSMOSS/MNUMM | SAPNet notification number | |
| /SAPSMOSS/OSSYS | Operating system and version | |
| /SAPSMOSS/DBSYS | Database system | |
| /SAPSMOSS/REL | R/3 Release | |
| /SAPSMOSS/COMP | Area | |
| /SAPSMOSS/FRONT | Frontend | |
| /SAPSMOSS/SYSTYP | R/3 System type | |
| /SAPSMOSS/ADDID | Add-on ID | |
| /SAPSMOSS/ADDREL | Add-On Release | |
| /SAPSMOSS/TSTMP | SAPNet time stamp | |
| /SAPSMOSS/STATUS | Status of R/3 notification in SAPNet | |
| /SAPSMOSS/ERDAT | Date on which notification was completed at SAP | |
| /SAPSMOSS/ERZEIT | Time when notification was completed at SAP | |
| /SAPSMOSS/SYSID | Name of SAP System | |
| /SAPSMOSS/MANDT | Client ID | |
| PSP_NR | WBS Element | |
| ESTIMATED_COSTS | Estimated Costs for a Claim | |
| CLAIMED_COSTS | Costs Claimed | |
| RESULT_COSTS | Costs Accepted | |
| CHANCE | Chance of Completing a Claim | |
| OPPONENT | Partner Type | |
| KALNR | Cost Estimate Number for Cost Est. w/o Qty Structure | |
| KALVAR | Costing Variant for Postprocessing with Unit Costing | |
| OBJNR_REAL | Object Number of Real CO Account Assignment | Values must exist in ONR00 |
| OBJNR_STAT | Auxiliary account assignment 1 | Values must exist in ONR00 |
| DUMMY_QMEL_INCL_EEW_PS | Dummy function in length 1 | |
| PHASE | Notification Processing Phase | |
| CHANGEDDATETIME | UTC Time Stamp in Short Form (YYYYMMDDhhmmss) | |
| .INCLU--AP | ||
| /ISDFPS/MHIO_ADDATE | Completion Date for Call Object | |
| /ISDFPS/MHIO_ADTIME | Completion Time for Call Object | |
| /ISDFPS/USERMODE | Scheduling determined by user | |
| .INCLU--AP | ||
| /ISDFPS/OBJNR | Object number | |
| LOGSYSTEM | Logical System | |
| /ISDFPS/MEQUI | Master Equipment | |
| .INCLU--AP | ||
| SHN_OBJTY | Object types of the CIM resource | |
| SHN_OBJID | Object ID of the resource | |
| SHN_FUNCT_LOC | Functional Location | |
| SHN_EQUIPMENT | Equipment Number | |
| SHN_ORIGIN | Origin or Use of Shift Note or Report | |
| .INCLU--AP | ||
| UII | Unique Item Identifier |
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 |
4 | Following Master Data need to be extracted first with their respective relevancy rules applied before Notification and Work Order can be extracted referencing to the relevant master data:
| 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 | Ensure all mapping tables are up to date. | Syniti |
3 | In dspMigrate, select the wave –R3 S4/HANA – Plant Maintenance | Syniti |
4 | Go to Process Area Launch and Process the Object – Work Order | Syniti |
5 | Review and Validate Error and Preload Reports | Syniti |
6 | Execute the transformation to prepare the target tables | Syniti |
7 | Validate data from pre-load and invalid reports by region | Business/Data owner |
8 | Generate export(load) file (If load tool is not dspIntergrate) | 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
Use the exact name and reference this section in the “Transformation rules” above| 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
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 |
|---|---|
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
1003 | Functional Location |
1002 | Equipment |
1005 | Task List |
| 1008 | Catalog Profile |
1016 | Maintenance Plan and Item |
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.
- 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
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.