| Status | Approved |
|---|---|
| Owner | |
| Stakeholders |
Purpose
The purpose of this document is to define the conversion approach to create Notification in S/4 HANA.
A Notification is a structured record in SAP PM used to report, track, and manage maintenance issues or requests.
It acts as the starting point for most maintenance processes, ensuring that problems, inspections, or service requests are documented and communicated.
Legacy Plant Maintenance Notification is using a diverse range of formats across the different systems. 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.
In standard SAP functionality whenever an asset or its component is identified as having suffered a fault or malfunction, a maintenance notification is created to report the event and to request maintenance. The appropriate technical object (i.e. functional location or equipment) that represents the asset is referenced on that notification along with the suspected symptom and other information (e.g. priority, short / long description, date, reported by, breakdown indicator, etc.)
In general terms, a notification can be utilised in the following situations:
- Corrective Maintenance work identification - non-breakdown maintenance requests, in-service breakdowns, extra malfunctions uncovered during routine maintenance
- Activity reports during routine maintenance and inspections
- Work order execution and completion - recording of technical data such as failure/cause codes)
- Condition-based / predictive maintenance - creation of notifications when asset reaches an exceptional technical condition (e.g. measurements exceed or fall below a certain tolerance)
Besides capturing maintenance requests and providing a means to track outstanding faults/defects and their current rectification, notifications are also used to capture malfunction and failure data which is crucial for long-term asset reliability analysis.
The data from legacy system includes:
- All Notifications (all system status (TJ02T-TXT04)) with the following conditions:
- created date (QMEL-ERDAT) is greater than or equal to value defined in OTH_Migration_Date Relevant Values A2D - 6 months) within the 6 months (with or without WO assigned (QMEL-AUFNR))
- created date (QMEL-ERDAT) is lesser than or equal to value defined in OTH_Migration_Date Relevant Values A2D - 6 months) after 6 months (only if OPEN WO (JEST-STAT= CRTD or REL) is assigned (QMEL-AUFNR))
- Preventive Notifications (QMIH-WARPL is not blank) Generated from Maintenance Plans:
- Include Notifications that have OPEN Work Order (TJ02T-TXT04 = ORAS) assigned
- All Maintenance Notification Types (QMART where TQ80-QMTYP = '01')
- Notifications having Maintenance Plant (QMEL-ARBPLWERK) in scope - Refer to Value Mapping: Plant (Maintenance Plant = Yes)
The data from legacy system excludes:
- Notification with Source System Status Notification completed status (TJ02T-TXT04 = DLFL (flagged for Deletion), ARNB (Blocked for Archiving), NOCO (Completed))
- Notification (does not have TJ02T-TXT04 = ORAS) without WO assigned that are generated from the Maintenance Plan (QMIH-WARPL is not blank)
Note:
1. S4 Notification Type in scope: Y1 (Maintenance Request), Y2 (Proactive Work)
2. S4 Notification Type not in scope: Y3 (Project), Y4 (Refurbishment) and Y5 (Engineering Management of Change (MOC))
Historical Notification data related to Asset Performance Management (APM) Failure Curve Analytics (FCA), the data from legacy system includes Notifications with:
- FL / EQ with APM Relevant Technical Object Type (IFLOT-EQART / EQUI-EQART) (listed in OTH_Technical Object Type_APM)
- Maintenance Plant (QMEL-ARBPLWERK) with APM Relevant Plant (listed in OTH_Plant_APM)
- Created Date (QMEL-ERDAT) is greater than or equal to value defined in OTH_Migration_Date Relevant Values A2D - 2 years
- Catalog Assigned (Object Part (QMFE-OTGRP) / Damage Code (QMFE-FECOD) / Cause Code (QMUR-URCOD) / Activities (QMMA-MNCOD))
- Notification Status: NOCO
The data from legacy system excludes Notifications with:
- Notification Status: DLFL (flagged for Deletion), ARNB (Blocked for Archiving)
Note:
1. Notification will be created as NOCO in S4 if they are NOCO in legacy
2. To create Y2 for Preventive Notification (created from Maintenance Plan), Y1 for Corrective Notification
List of Tables to extract for this object is maintained here: Extract Table Register.
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
PF2, WP2 | Relevant open Notification will be extracted from PF2 and WP2 | 70,000 | S/4HANA | 70,000 |
PF2, WP2 | Historical Notification data related to Asset Performance Management (APM) | 160,000 | S/4HANA | 160,000 |
Additional Information
Multi-language Requirement
Notification short text does not have multi language support. Notification short text will be migrated using EN logon.
Multi language is supported for Notifiction Long Text. Login via a different language will have its Long Text displayed in the logon language if the language key is maintained in the Notification.
Document Management
Refer to the Document Management in the SyWay Solution.
Note: Documents attached to Notification 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.Notification Header
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement (Notif. Type Y1) | Requirement (Notif. Type Y2) |
|---|---|---|---|---|---|---|---|
| QMEL | QMNUM | QMNUM | Notification Number | CHAR | 12 | System | System |
| QMEL | QMART | QMART | Notification Type | CHAR | 2 | Mandatory | Mandatory |
| QMEL | QMTXT | QMTXT | Short Text | CHAR | 40 | Mandatory | Mandatory |
| QMEL | PRIOK | PRIOK | Priority | CHAR | 1 | Mandatory | Mandatory |
| QMEL | QMNAM | QMNAM | Name of Person Reporting Notification | CHAR | 12 | Mandatory | Mandatory |
| QMEL | STRMN | STRMN | Required Start Date | DATS | 8 | Mandatory | Mandatory |
| QMEL | STRUR | STRUR | Required Start Time | TIMS | 6 | Mandatory | Mandatory |
| QMEL | LTRMN | LTRMN | Required End Date | DATS | 8 | Mandatory | Mandatory |
| QMEL | LTRUR | LTRUR | Requested End Time | TIMS | 6 | Mandatory | Mandatory |
| QMEL | RBNR | RBNR | Catalog Profile | CHAR | 9 | Mandatory | Mandatory |
| QMEL | QMGRP | QMGRP | Code Group - Coding | CHAR | 8 | Mandatory | System |
| QMEL | QMCOD | QMCOD | Coding | CHAR | 4 | Mandatory | System |
| QMEL | ARBPL | LGWID | Object ID of the Work Center | NUMC | 8 | Mandatory | Mandatory |
| QMEL | ARBPLWERK | QARBPWERKS | Plant for Work Center | CHAR | 4 | Mandatory | Mandatory |
| QMIH | IWERK | IWERK | Maintenance Planning Plant | CHAR | 4 | Mandatory | Mandatory |
| QMIH | EQUNR | EQUNR | Equipment number | CHAR | 18 | Conditional | Conditional |
| IFLOT | TPLNR | TPLNR | Functional Location | CHAR | 30 | Conditional | Conditional |
| QMIH | MSAUS | MSAUS | Breakdown Indicator | CHAR | 1 | Conditional | Not used |
| QMIH | AUSVN | AUSVN | Start of Malfunction (Date) | DATS | 8 | Conditional | Not used |
| QMIH | AUSBS | AUSBS | End of Malfunction (Date) | DATS | 8 | Conditional | Not used |
| QMIH | AUZTV | AUZTV | Start of Malfunction (Time) | TIMS | 6 | Conditional | Not used |
| QMIH | AUZTB | AUZTB | End of Malfunction (Time) | TIMS | 6 | Conditional | Not used |
| QMIH | AUSWK | AUSWK | Effect on Operation | CHAR | 1 | Mandatory | Mandatory |
| QMIH | INGRP | INGRP | Planner Group for Customer Service and Plant Maintenance | CHAR | 3 | Mandatory | Mandatory |
| QMIH | DETECTIONCODEGROUP | DETECTIONCODEGROUP | Detection Method Group | CHAR | 8 | Conditional | Conditional |
| QMIH | DETECTIONCODE | DETECTIONCODE | Detection Method | CHAR | 4 | Conditional | Conditional |
| TJ02T | TXT04 | J_TXT04 | Individual status of an object (short form) | CHAR | 40 | Mandatory | Mandatory |
2.Notification Header Long Text Header
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement (Notif. Type Y1) | Requirement (Notif. Type Y2) |
|---|---|---|---|---|---|---|---|
| STXH | TDOBJECT | TDOBJECT | Texts: application object | CHAR | 10 | Mandatory | Mandatory |
| STXH | TDNAME | TDOBNAME | Name | CHAR | 70 | Mandatory | Mandatory |
| STXH | TDID | TDID | Text ID | CHAR | 4 | Mandatory | Mandatory |
| STXH | TDSPRAS | SPRAS | Language Key | LANG | 1 | Mandatory | Mandatory |
3.Notification Header Long Text Line
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement (Notif. Type Y1) | Requirement (Notif. Type Y2) |
|---|---|---|---|---|---|---|---|
| STXL | TDOBJECT | TDOBJECT | Texts: application object | CHAR | 10 | Mandatory | Mandatory |
| STXL | TDNAME | TDOBNAME | Name | CHAR | 70 | Mandatory | Mandatory |
| STXL | TDID | TDID | Text ID | CHAR | 4 | Mandatory | Mandatory |
| STXL | TDSPRAS | SPRAS | Language Key | LANG | 1 | Mandatory | Mandatory |
| STXL | CLUSTD_TAG | TDFORMAT | Tag column | CHAR | 1 | Mandatory | Mandatory |
| STXL | ROWCOUNT | ROWCOUNT | Row number | NUMC | 10 | Mandatory | Mandatory |
| STXL | TXLINE | TDLINE | Text Line | CHAR | 72 | Mandatory | Mandatory |
4.Notification Item
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement (Notif. Type Y1) | Requirement (Notif. Type Y2) |
|---|---|---|---|---|---|---|---|
| QMFE | QMNUM | QMNUM | Notification Number | CHAR | 12 | Mandatory | Mandatory |
| QMFE | FEGRP | FEGRP | Code Group - Problem | CHAR | 8 | Conditional | Conditional |
| QMFE | FECOD | FECOD | Problem or Damage Code | CHAR | 4 | Conditional | Conditional |
| QMFE | OTGRP | OTGRP | Code Group - Object Parts | CHAR | 8 | Conditional | Conditional |
| QMFE | OTEIL | OTEIL | Part of Object | CHAR | 4 | Conditional | Conditional |
| QMFE | ANZFEHLER | QANZFEHL4 | Number of Defects Found | INT4 | 10 | Conditional | Conditional |
Note:
- Each Notification Header can have many Notification Items
- Only extract the records with the highest FEVER and OTVER values
5.Notification Item Long Text Header
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement (Notif. Type Y1) | Requirement (Notif. Type Y2) |
|---|---|---|---|---|---|---|---|
| STXH | TDOBJECT | TDOBJECT | Texts: application object | CHAR | 10 | Mandatory | Mandatory |
| STXH | TDNAME | TDOBNAME | Name | CHAR | 70 | Mandatory | Mandatory |
| STXH | TDID | TDID | Text ID | CHAR | 4 | Mandatory | Mandatory |
| STXH | TDSPRAS | SPRAS | Language Key | LANG | 1 | Mandatory | Mandatory |
6.Notification Item Long Text Line
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement (Notif. Type Y1) | Requirement (Notif. Type Y2) |
|---|---|---|---|---|---|---|---|
| STXL | TDOBJECT | TDOBJECT | Texts: application object | CHAR | 10 | Mandatory | Mandatory |
| STXL | TDNAME | TDOBNAME | Name | CHAR | 70 | Mandatory | Mandatory |
| STXL | TDID | TDID | Text ID | CHAR | 4 | Mandatory | Mandatory |
| STXL | TDSPRAS | SPRAS | Language Key | LANG | 1 | Mandatory | Mandatory |
| STXL | CLUSTD_TAG | TDFORMAT | Tag column | CHAR | 1 | Mandatory | Mandatory |
| STXL | ROWCOUNT | ROWCOUNT | Row number | NUMC | 10 | Mandatory | Mandatory |
| STXL | TXLINE | TDLINE | Text Line | CHAR | 72 | Mandatory | Mandatory |
7. Notification Causes
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement (Notif. Type Y1) | Requirement (Notif. Type Y2) |
|---|---|---|---|---|---|---|---|
| QMUR | QMNUM | QMNUM | Notification Number | CHAR | 12 | System | System |
| QMUR | FENUM | FELFD | Item Number in Item Record | NUMC | 4 | System | System |
| QMUR | URNUM | URNUM | Sequential Number for Cause | NUMC | 4 | System | System |
| QMUR | URTXT | URSTX | Cause Text | CHAR | 40 | Conditional | Conditional |
| QMUR | URGRP | URGRP | Code Group - Causes | CHAR | 8 | Conditional | Conditional |
| QMUR | URCOD | URCOD | Cause Code | CHAR | 4 | Conditional | Conditional |
| QMUR | QURNUM | QURNUM | Sort Number for Cause | NUMC | 4 | Conditional | Conditional |
Note:
- Only extract the records with the highest URVER values
8.Notification Causes Long Text Header
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement (Notif. Type Y1) | Requirement (Notif. Type Y2) |
|---|---|---|---|---|---|---|---|
| STXH | TDOBJECT | TDOBJECT | Texts: application object | CHAR | 10 | Mandatory | Mandatory |
| STXH | TDNAME | TDOBNAME | Name | CHAR | 70 | Mandatory | Mandatory |
| STXH | TDID | TDID | Text ID | CHAR | 4 | Mandatory | Mandatory |
| STXH | TDSPRAS | SPRAS | Language Key | LANG | 1 | Mandatory | Mandatory |
9.Notification Causes Long Text Line
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement (Notif. Type Y1) | Requirement (Notif. Type Y2) |
|---|---|---|---|---|---|---|---|
| STXL | TDOBJECT | TDOBJECT | Texts: application object | CHAR | 10 | Mandatory | Mandatory |
| STXL | TDNAME | TDOBNAME | Name | CHAR | 70 | Mandatory | Mandatory |
| STXL | TDID | TDID | Text ID | CHAR | 4 | Mandatory | Mandatory |
| STXL | TDSPRAS | SPRAS | Language Key | LANG | 1 | Mandatory | Mandatory |
| STXL | CLUSTD_TAG | TDFORMAT | Tag column | CHAR | 1 | Mandatory | Mandatory |
| STXL | ROWCOUNT | ROWCOUNT | Row number | NUMC | 10 | Mandatory | Mandatory |
| STXL | TXLINE | TDLINE | Text Line | CHAR | 72 | Mandatory | Mandatory |
10.Notification Activity
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement (Notif. Type Y1) | Requirement (Notif. Type Y2) |
|---|---|---|---|---|---|---|---|
| QMMA | QMNUM | QMNUM | Notification Number | CHAR | 12 | System | System |
| QMMA | MANUM | AKNUM | Consecutive Number of Activity | NUMC | 4 | System | System |
| QMMA | MNGRP | MFGRP | Code Group - Activities | CHAR | 8 | Conditional | Conditional |
| QMMA | MNCOD | MFCOD | Activity Code | CHAR | 4 | Conditional | Conditional |
| QMMA | MATXT | MFTEXT | Activity Text | CHAR | 40 | Conditional | Conditional |
| QMMA | PSTER | PSTERMA | Start Date | DATS | 8 | Conditional | Conditional |
| QMMA | PETER | PETERMA | End Date | DATS | 8 | Conditional | Conditional |
| QMMA | INDTX | INDLTX | Object Long Text Available | CHAR | 1 | Conditional | Conditional |
| QMMA | PSTUR | PSTURMA | Start Time of Activity | TIMS | 6 | Conditional | Conditional |
| QMMA | PETUR | PETURMA | End Time of Activity | TIMS | 6 | Conditional | Conditional |
| QMMA | QMANUM | QMANUM | Sort Number for Activity | NUMC | 4 | Conditional | Conditional |
Note:
- Only extract the records with the highest MNVER values
11.Notification Activity Long Text Header
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement (Notif. Type Y1) | Requirement (Notif. Type Y2) |
|---|---|---|---|---|---|---|---|
| STXH | TDOBJECT | TDOBJECT | Texts: application object | CHAR | 10 | Mandatory | Mandatory |
| STXH | TDNAME | TDOBNAME | Name | CHAR | 70 | Mandatory | Mandatory |
| STXH | TDID | TDID | Text ID | CHAR | 4 | Mandatory | Mandatory |
| STXH | TDSPRAS | SPRAS | Language Key | LANG | 1 | Mandatory | Mandatory |
12.Notification Activity Long Text Line
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement (Notif. Type Y1) | Requirement (Notif. Type Y2) |
|---|---|---|---|---|---|---|---|
| STXL | TDOBJECT | TDOBJECT | Texts: application object | CHAR | 10 | Mandatory | Mandatory |
| STXL | TDNAME | TDOBNAME | Name | CHAR | 70 | Mandatory | Mandatory |
| STXL | TDID | TDID | Text ID | CHAR | 4 | Mandatory | Mandatory |
| STXL | TDSPRAS | SPRAS | Language Key | LANG | 1 | Mandatory | Mandatory |
| STXL | CLUSTD_TAG | TDFORMAT | Tag column | CHAR | 1 | Mandatory | Mandatory |
| STXL | ROWCOUNT | ROWCOUNT | Row number | NUMC | 10 | Mandatory | Mandatory |
| STXL | TXLINE | TDLINE | Text Line | CHAR | 72 | Mandatory | Mandatory |
Data Cleansing
| ID | Criticality | Error Message/Report Description | Rule | Output | Source System |
|---|---|---|---|---|---|
9004-001 | C2 | Code Group - Coding: Blank Code Group - Coding | Notification as per Relevancy Criteria assigned with blank Catalog Code Groups & Code | Notification Number, Short Text, Plant for Work Centre, Code Group - Coding | PF2, WP2 |
9004-002 | C2 | Code Group - Coding: Blank Code Group - Object Parts | Notification as per Relevancy Criteria assigned with blank Catalog Code Groups & Code | Notification Number, Short Text, Notification Item Short Text, Plant for Work Centre, Code Group - Object Parts | PF2, WP2 |
9004-003 | C2 | Code Group - Coding: Blank Code Group - Problems/Defects | Notification as per Relevancy Criteria assigned with blank Code Group - Problems/Defects | Notification Number, Short Text, Notification Item Short Text, Plant for Work Centre, Code Group - Problems/Defects | PF2, WP2 |
| 9004-004 | C2 | Code Group - Coding: Blank Code Group - Causes | Notification as per Relevancy Criteria assigned with blank Code Group - Causes | Notification Number, Item Number in Item Record, Sequential Number for Cause, Cause Text, Plant for Work Centre, Code Group - Causes | PF2, WP2 |
9004-005 | C2 | Code Group - Coding: Blank Code Group - Activities | Notification as per Relevancy Criteria assigned with blank Code Group -Activities | Notification Number, Consecutive Number of Activity, Short Text for Activity, Plant for Work Centre, Code Group - Activities | PF2, WP2 |
9004-006 | C2 | Open Notifications older than 3 months with No Work Order Assigned | Open Notifications older than 3 months with No Work Order Assigned (Status ORAS = Work Order Assigned) Note: Business to either assign a valid Work Order or close the Notification | Notification Number, Short Text, Plant for Work Centre, Notification Creation Date | PF2, WP2 |
| 9004-007 | C1 | Notifications Generated from Maintenance Plans Without Work Orders | Open Notifications Generated from Maintenance Plans with No Work Order Assigned (Status ORAS = Work Order Assigned) Note: These Notifications will not be not migrated. If these notifications are required for migration, a work order must be created | Notification Number, Short Text, Plant for Work Centre, Notification Creation Date | PF2, WP2 |
9004-008 | C2 | Notification with corrupted Work Order (not in PF2/WP2)
| Open Notifications assigned to Work Order which are not found in PF2/WP2 Note: Business to either assign a valid Work Order or close the Notification | Notification Number, Short Text, Plant for Work Centre, Notification Creation Date | PF2, WP2 |
9004-009 | C2 | Open Notification with CLSD/TECO Work Order
| Open Notifications assigned to Work Order with Status CLSD or TECO Note: Business to close the Notification if the work is completed | Notification Number, Short Text, Plant for Work Centre, Notification Creation Date | PF2, WP2 |
9004-010 | C1 | Notification relevant for APM not set to NOCO | Open Notification with no Work Order Assigned matching the criteria below:
Note: Business to either assign a valid Work Order or close the Notification | Notification Number, Short Text, Plant for Work Centre, Notification Creation Date | PF2, WP2 |
| 9004-011 | C2 | Planner Group: Blank Planner Group | Notification as per Relevancy Criteria with no Planner Group Assigned or Invalid Planner Group (T024I) | Notification Number, Short Text, Plant for Work Centre, Planner Group | PF2, WP2 |
| 9004-012 | C2 | Short Text contains Thai characters | Notification Short Text with Thai characters and need to be translated to English. Note: The language key for this report is EN | Notification Number, Short Text, Plant for Work Centre | PF2, WP2 |
| 9004-013 | C2 | Short Text: Blank Short Text | Notification Short Text must not be blank | Notification Number, Short Text, Plant for Work Centre | PF2, WP2 |
| 9004-014 | C1 | Priority: Blank Priority | Notification Priority is blank or not in config (T356) Note: If the Priority is left blank the it will be set to default value | Notification Number, Short Text, Plant for Work Centre, Priority | PF2, WP2 |
| 9004-015 | C2 | Required Start Date: Invalid or blank | Required Start Date must not be blank | Notification Number, Short Text, Plant for Work Centre, Required Start Date | PF2, WP2 |
| 9004-016 | C2 | Required Start Time: Invalid or blank | Required Required Start Time must not be blank | Notification Number, Short Text, Plant for Work Centre, Required Start Time | PF2, WP2 |
| 9004-017 | C2 | Required End Date: Invalid or blank | Required Required End Date must not be blank | Notification Number, Short Text, Plant for Work Centre, Required End Date | PF2, WP2 |
| 9004-018 | C2 | Requested End Time: invalid or blank | Required Requested End Time must not be blank | Notification Number, Short Text, Plant for Work Centre, Requested End Time | PF2, WP2 |
| 9004-019 | C2 | Effect on Operation: Blank Effect on Operation | Effect on Operation must not be blank | Notification Number, Short Text, Plant for Work Centre, Effect on Operation | PF2, WP2 |
| 9004-020 | C3 | Info Report: Catalog codes used by the legacy Notification Header and Item | List of Catalog codes used by the legacy Notification Header and Item | Notification Number, Short Text, Notification Item Short Text, Plant for Work Centre, Catalog Type - Coding, Code Group - Coding, Coding, Catalog Type - Problems/Defects, Code Group - Problem, Problem or Damage Code | PF2, WP2 |
| 9004-021 | C3 | Info Report: Catalog codes used by the legacy Notification Causes | List of Catalog codes used by the legacy Notification Causes | Notification Number, Item Number in Item Record, Sequential Number for Cause, Cause Text, Catalog Type - Problems/Defects, Code Group - Problem, Problem or Damage Code | PF2, WP2 |
| 9004-022 | C3 | Info Report: Catalog codes used by the legacy Notification Activity | List of Catalog codes used by the legacy Notification Activity | Notification Number, Consecutive Number of Activity, Short Text for Activity, Catalog Type - Activity, Code Group - Activity, Activity Code | 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:
Data Privacy and Sensitivity
Not Applicable
Extraction
Extract data from a source into ADMM. There are 2 possibilities:
- The data exists. ADMM connects to the source and loads the data into ADMM. There are 3 methods:
- Perform full data extraction from relevant tables in the source system(s).
- Perform extraction through the application layer.
- Only if ADMM 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 the repository. This is to be conducted using DCT (Data Collection Template) in Advanced Data Migration and Management (ADMM).
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
| Selection Ref Screen | Parameter Name | Selection Type | Requirement | Value to be entered/set |
|---|---|---|---|---|
| Not Applicable |
Data Collection Template (DCT)
Not applicable as data will be all extracted from the source systems.
Extraction Dependencies
| Item # | Step Description | Team Responsible |
|---|---|---|
| 1 | Not Applicable |
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 Advanced Data Migration and Management (ADMM)
- 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 | In dspMigrate, select the wave – S4/HANA – Plant Maintenance | Syniti |
| 2 | Go to Process Area Launch and Process the Object – Notification | Syniti |
| 3 | Review and Validate Error and Preload Reports | Syniti |
| 4 | Execute the transformation to prepare the target tables | Syniti |
| 5 | Validate data from pre-load and error reports | Business/Data owner |
| 6 | Generate load files | Syniti |
Transformation Rules
Note: Unless otherwise specified, the transformation rules applies to both Y1 and Y2 Notification Types
1.Notification Header Transformation Rule
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4HANA | QMEL | QMNUM | Notification Number | System (Internal numbering) |
| 2 | PF2, WP2 | QMEL | QMART | Notification Type | S/4HANA | QMEL | QMART | Notification Type |
|
| 3 | PF2, WP2 | QMEL | QMTXT | Short Text | S/4HANA | QMEL | QMTXT | Short Text |
|
| 4 | PF2, WP2 | QMEL | PRIOK | Priority | S/4HANA | QMEL | PRIOK | Priority |
|
| 5 | PF2, WP2 | QMEL | STRMN | Required Start Date | S/4HANA | QMEL | STRMN | Required Start Date |
|
| 6 | PF2, WP2 | QMEL | STRUR | Required Start Time | S/4HANA | QMEL | STRUR | Required Start Time |
|
| 7 | PF2, WP2 | QMEL | LTRMN | Required End Date | S/4HANA | QMEL | LTRMN | Required End Date |
|
| 8 | PF2, WP2 | QMEL | LTRUR | Requested End Time | S/4HANA | QMEL | LTRUR | Requested End Time |
Note: Required End Date and Requested End Time combination cannot be earlier than start date |
| 9 | PF2, WP2 | QMIH | EQUNR | Equipment Number | S/4HANA | QMEL | EQUNR | Equipment Number |
|
| 10 | PF2, WP2 | IFLOT | TPLNR | Functional Location | S/4HANA | QMEL | EQUNR | Equipment Number | Note: Transformation Rule for legacy EQUNR must run before this rule. This rule is for legacy Functional Locations which are converted to Equipment in S4
|
| 11 | PF2, WP2 | QMIH | BAUTL | Assembly | S/4HANA | QMEL | EQUNR | Equipment Number | Note: Transformation Rule for legacy EQUNR and legacy TPLNR to EQUNR must run before this rule. This rule is for legacy Assemblies which are converted to Equipment in S4
|
| 12 | PF2, WP2 | IFLOT | TPLNR | Functional Location | S/4HANA | IFLOT | TPLNR | Functional Location Label |
|
| 13 | - | - | - | - | S/4HANA | QMEL | RBNR | Catalog Profile |
Note: This field will not be used druing loading. Use this field for Pre Load and Post Load Validation. |
| 14 | PF2, WP2 | QMEL | QMGRP | Code Group - Coding | S/4HANA | QMEL | QMGRP | Code Group - Coding |
|
| 15 | PF2, WP2 | QMEL | QMCOD | Coding | S/4HANA | QMEL | QMCOD | Coding |
|
| 16 | - | - | - | - | S/4HANA | QMEL | ARBPL | Object ID of the Work Center |
|
| 17 | - | - | - | - | S/4HANA | QMEL | ARBPLWERK | Plant for Work Center |
|
| 18 | - | - | - | - | S/4HANA | QMIH | IWERK | Maintenance Planning Plant |
|
| 19 | PF2, WP2 | QMIH | MSAUS | Breakdown Indicator | S/4HANA | QMIH | MSAUS | Breakdown Indicator |
|
| 20 | PF2, WP2 | QMIH | AUSVN | Malfunct. Start Date | S/4HANA | QMIH | AUSVN | Malfunct. Start Date |
|
| 21 | PF2, WP2 | QMIH | AUZTV | Malfunct. Start Time | S/4HANA | QMIH | AUZTV | Malfunct. Start Time |
|
| 22 | PF2, WP2 | QMIH | AUSBS | Malfunct. End Date | S/4HANA | QMIH | AUSBS | Malfunct. End Date |
|
| 23 | PF2, WP2 | QMIH | AUZTB | Malfunct. End Time | S/4HANA | QMIH | AUZTB | Malfunct. End Time |
|
| 24 | PF2, WP2 | QMIH | AUSWK | Effect on Operation | S/4HANA | QMIH | AUSWK | Effect on Operation |
|
| 25 | - | - | - | - | S/4HANA | QMIH | INGRP | Planner Group |
|
| 26 | PF2, WP2 | QMIH | DETECTIONCODEGROUP | Detection Method Group | S/4HANA | QMIH | DETECTIONCODEGROUP | Detection Method Group | Derive the value as per Value Mapping: OTH_Migration_Date Relevant Values A2D (using Object ID "9004" and Field Name = "QMIH-DETECTIONCODEGROUP" |
| 27 | PF2, WP2 | QMIH | DETECTIONCODE | Detection Method | S/4HANA | QMIH | DETECTIONCODE | Detection Method | Derive the value as per Value Mapping: OTH_Migration_Date Relevant Values A2D (using Object ID "9004" and Field Name = "QMIH-DETECTIONCODE" |
| 28 | PF2, WP2 | TJ02T | TXT04 | Individual status of an object (short form) | S/4HANA | TJ02T | TXT04 | Individual status of an object (short form) | Derive all values from JEST |
Note: For rules that require default value from Parameters, derive the values from Syniti Construct > A2D - Others > Parameters
2.Notification Header Long Text Header Transformation Rule
| 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 "QMEL" |
| 2 | PF2, WP2 | QMEL | QMNUM | Notification Number | S/4HANA | STXH | TDNAME | Name | Value Mapping: Notification |
| 3 | - | - | - | S/4HANA | STXH | TDID | Text ID | Default to 'LTXT' | |
| 4 | PF2, WP2 | STXH | TDSPRAS | Language Key | S/4HANA | STXH | TDSPRAS | Language Key | Derive Language Key (T001W-SPRAS) from Table T001W where S4 ARBPLWERK (Plant for Work Center) = T001W-WERKS |
3.Notification Header Long Text Line Transformation Rule
| 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 "QMEL" |
| 2 | PF2, WP2 | QMEL | QMNUM | Notification Number | S/4HANA | STXL | TDNAME | Name | Value Mapping: Notification |
| 3 | - | - | - | - | S/4HANA | STXL | TDID | Text ID | Default to 'LTXT' |
| 4 | PF2, WP2 | STXL | TDSPRAS | Language Key | S/4HANA | STXL | TDSPRAS | Language Key | Derive Language Key (T001W-SPRAS) from Table T001W where S4 ARBPLWERK (Plant for Work Center) = T001W-WERKS |
| 5 | - | - | - | - | S/4HANA | STXL | CLUSTD_TAG | Tag column | Direct Mapping |
| 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 |
4.Notification Item Transformation Rule
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4HANA | QMFE | QMNUM | Notification Number | System (Internal numbering) |
| 2 | - | - | - | - | S/4HANA | QMFE | FENUM | Item Number in Item Record | System (Internal numbering) |
| 3 | PF2, WP2 | QMFE | FETXT | Notification Item Short Text | S/4HANA | QMFE | FETXT | Notification Item Short Text | Direct Mapping |
| 4 | PF2, WP2 | QMFE | FEGRP | Damage – Code Group | S/4HANA | QMFE | FEGRP | Damage – Code Group | Value Mapping: Catalog Code Group and Code |
| 5 | PF2, WP2 | QMFE | FECOD | Problem or Damage Code | S/4HANA | QMFE | FECOD | Problem or Damage Code | Value Mapping: Catalog Code Group and Code |
| 6 | PF2, WP2 | QMFE | OTGRP | Code Group - Object Parts | S/4HANA | QMFE | OTGRP | Code Group - Object Parts | Value Mapping: Catalog Code Group and Code |
| 7 | PF2, WP2 | QMFE | OTEIL | Part of Object | S/4HANA | QMFE | OTEIL | Part of Object | Value Mapping: Catalog Code Group and Code |
| 8 | PF2, WP2 | QMFE | ANZFEHLER | Number of Defects Found | S/4HANA | QMFE | ANZFEHLER | Number of Defects Found | Direct Mapping |
Note: Each Notification Header can have many Notification Items
5.Notification Item Long Text Header Transformation Rule
| 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 "QMFE" |
| 2 | - | - | - | - | S/4HANA | STXL | TDNAME | Name | New Notification Number + New Item Number in Item Record |
| 3 | - | - | - | - | S/4HANA | STXH | TDID | Text ID | Default to 'LTXT' |
| 4 | PF2, WP2 | STXH | TDSPRAS | Language Key | S/4HANA | STXH | TDSPRAS | Language Key | Derive Language Key (T001W-SPRAS) from Table T001W where S4 ARBPLWERK (Plant for Work Center) = T001W-WERKS |
6.Notification Item Long Text Line Transformation Rule
| 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 "QMFE" |
| 2 | - | - | - | - | S/4HANA | STXL | TDNAME | Name | New Notification Number + New Item Number in Item Record |
| 3 | - | - | - | - | S/4HANA | STXL | TDID | Text ID | Default to 'LTXT' |
| 4 | PF2, WP2 | STXL | TDSPRAS | Language Key | S/4HANA | STXL | TDSPRAS | Language Key | Derive Language Key (T001W-SPRAS) from Table T001W where S4 ARBPLWERK (Plant for Work Center) = T001W-WERKS |
| 5 | - | - | - | - | S/4HANA | STXL | CLUSTD_TAG | Tag column | Direct Mapping |
| 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 |
7. Notification Causes Transformation Rule
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4 HANA | QMUR | QMNUM | Notification Number | System (Internal numbering) |
| 2 | - | - | - | - | S/4HANA | QMUR | FENUM | Item Number in Item Record | System (Internal numbering) |
| 3 | - | - | - | - | S/4HANA | QMUR | URNUM | Sequential Number for Cause | System (Internal numbering) |
| 4 | PF2, WP2 | QMUR | URTXT | Cause Text | S/4HANA | QMUR | URTXT | Cause Text | Direct Mapping |
| 5 | PF2, WP2 | QMUR | URGRP | Code Group - Causes | S/4HANA | QMUR | URGRP | Code Group - Causes | Value Mapping: Catalog Code Group and Code |
| 6 | PF2, WP2 | QMUR | URCOD | Cause Code | S/4HANA | QMUR | URCOD | Cause Code | Value Mapping: Catalog Code Group and Code |
| 7 | PF2, WP2 | QMUR | QURNUM | Sort Number for Cause | S/4HANA | QMUR | QURNUM | Sort Number for Cause | Direct Mapping |
8.Notification Causes Long Text Header Transformation Rule
| 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 "QMUR" |
| 2 | - | - | - | - | S/4HANA | STXL | TDNAME | Name | New Notification Number + New Item Number in Item Record + New Sequential Number for Cause |
| 3 | - | - | - | - | S/4HANA | STXH | TDID | Text ID | Default to 'LTXT' |
| 4 | PF2, WP2 | STXH | TDSPRAS | Language Key | S/4HANA | STXH | TDSPRAS | Language Key | Derive Language Key (T001W-SPRAS) from Table T001W where S4 ARBPLWERK (Plant for Work Center) = T001W-WERKS |
9.Notification Causes Long Text Line Transformation Rule
| 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 "QMUR" |
| 2 | - | - | - | - | S/4HANA | STXL | TDNAME | Name | New Notification Number + New Item Number in Item Record + New Sequential Number for Cause |
| 3 | - | - | - | - | S/4HANA | STXL | TDID | Text ID | Default to 'LTXT' |
| 4 | PF2, WP2 | STXL | TDSPRAS | Language Key | S/4HANA | STXL | TDSPRAS | Language Key | Derive Language Key (T001W-SPRAS) from Table T001W where S4 ARBPLWERK (Plant for Work Center) = T001W-WERKS |
| 5 | - | - | - | - | S/4HANA | STXL | CLUSTD_TAG | Tag column | Direct Mapping |
| 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 |
10.Notification Activity Transformation Rule
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4HANA | QMMA | QMNUM | Notification Number | System (Internal numbering) |
| 2 | - | - | - | - | S/4HANA | QMMA | MANUM | Consecutive Number of Activity | System (Internal numbering) |
| 3 | PF2, WP2 | QMMA | URNUM | Sequential Number for Cause | S/4HANA | QMMA | URNUM | Sequential Number for Cause | Direct Mapping |
| 4 | PF2, WP2 | QMMA | MNGRP | Code Group - Activities | S/4HANA | QMMA | MNGRP | Code Group - Activities | Direct Mapping |
| 5 | PF2, WP2 | QMMA | MNCOD | Activity Code | S/4HANA | QMMA | MNCOD | Activity Code | Direct Mapping |
| 6 | PF2, WP2 | QMMA | MATXT | Activity Text | S/4HANA | QMMA | MATXT | Activity Text | Direct Mapping |
| 7 | PF2, WP2 | QMMA | PSTER | Start Date | S/4HANA | QMMA | PSTER | Start Date | Direct Mapping |
| 8 | PF2, WP2 | QMMA | PETER | End Date | S/4HANA | QMMA | PETER | End Date | Direct Mapping |
| 9 | PF2, WP2 | QMMA | PSTUR | Start Time of Activity | S/4HANA | QMMA | PSTUR | Start Time of Activity | Direct Mapping |
| 10 | PF2, WP2 | QMMA | PETUR | End Time of Activity | S/4HANA | QMMA | PETUR | End Time of Activity | Direct Mapping |
| 11 | PF2, WP2 | QMMA | QMANUM | Sort Number for Activity | S/4HANA | QMMA | QMANUM | Sort Number for Activity | Direct Mapping |
11.Notification Activity Long Text Header Transformation Rule
| 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 "QMMA" |
| 2 | - | - | - | - | S/4HANA | STXL | TDNAME | Name | New Notification Number + New Consecutive Number of Activity |
| 3 | - | - | - | - | S/4HANA | STXH | TDID | Text ID | Default to 'LTXT' |
| 4 | PF2, WP2 | STXH | TDSPRAS | Language Key | S/4HANA | STXH | TDSPRAS | Language Key | Derive Language Key (T001W-SPRAS) from Table T001W where S4 ARBPLWERK (Plant for Work Center) = T001W-WERKS |
12.Notification Activity Long Text Line Transformation Rule
| 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 "QMMA" |
| 2 | - | - | - | - | S/4HANA | STXL | TDNAME | Name | New Notification Number +New Consecutive Number of Activity |
| 3 | - | - | - | - | S/4HANA | STXL | TDID | Text ID | Default to 'LTXT' |
| 4 | PF2, WP2 | STXL | TDSPRAS | Language Key | S/4HANA | STXL | TDSPRAS | Language Key | Derive Language Key (T001W-SPRAS) from Table T001W where S4 ARBPLWERK (Plant for Work Center) = T001W-WERKS |
| 5 | - | - | - | - | S/4HANA | STXL | CLUSTD_TAG | Tag column | Direct Mapping |
| 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 |
List of Custom Target Reports for this object is maintained here: Conversion Specification - Custom Reports Register.
Transformation Mapping
| Mapping Table Name | Mapping Table Description |
|---|---|
Notification | Old to new Notification |
Notification Item | Old to new Notification Item |
Notification Causes | Old to new Notification Causes |
Notification Activity | Old to new Notification Activity |
Work Order | Old to new Old to new Work Order |
Maintenance Planner Group | Old to new Maintenance Planner Group |
Work Centre A2D | Old to new Work Centre |
Plant | Old to new Plant |
Equipment | Old to new Equipment |
Functional Location | Old to new Functional Location |
Priority | Old to new Priority |
Priority Type | Old to new Priority Type |
Catalog Code Group and Code | Old to new Catalog Code Group and Code |
Catalog Profile | Old to new Catalog Profile |
Effect of malfunction on the system | Old to new Effect of malfunction on the system |
OTH_Migration_Date Relevant Values A2D | Default values table |
Transformation Dependencies
List the steps that need to occur before transformation can commence
| Item # | Step Description | Team Responsible |
|---|---|---|
| 1 | Ensure all Transformation mappings are up to date. | SyWay 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 the source systems and/or the DCT is equal to the total number of records 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 the source systems and/or the DCT 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 the data in the load table/file is accurate as per endorsed transformation/mapping rules (and signed-off DCT data). |
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
- After load is complete, additional process is required to update the system status to Notification in process (TJ02T-TXT04 = NOPR)
- Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation
Additional process for all Historical Notification data related to Asset Performance Management (APM):
- once load is complete, additional process is required to close the Notification (TJ02T-TXT04 = NOCO)
Note: Special consideration needs to be taken on the time zone during load
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 reupload 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 7 if necessary. | SyWay Data team |
Load Phase and Dependencies
Cutover
Configuration
| Item # | Configuration Item |
|---|---|
| 1 | T001W-Plant |
| 2 | T024I-Maintenance Planner groups |
| 3 | T356-Priority |
| 4 | T356A-Priority type |
| 5 | T357A-Effect of malfunction on the system |
| 6 | T399I-Planning Plant |
| 7 | TQ15-Inspection catalog type index |
| 8 | TQ80-Notification Type |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
1002 | Equipment |
1003 | Functional Location |
1006 | Work Centre |
1007 | Catalog Code Groups & Codes |
1008 | Catalog Profile |
Error Handling
| Error Type | Error Description | Action Taken |
|---|---|---|
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 Centre | Expedite whether the master data is changed in the system |
Invalid Data | Invalid Catalog Code Groups & Codes | Expedite whether the master data is changed in the system |
Invalid Data | Invalid Catalog Profile | Expedite whether the master data is changed in the system |
Configuration | Invalid Plant | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Maintenance Planner groups | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Priority | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Priority type | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Effect of malfunction on the system | 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 Inspection catalog type index | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Notification Type | Engage Functional team to expedite and fix the error in the system |
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 Notification 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 Notification data in target S/4 HANA were loaded correctly via dspMigrate post load reports or standard reports from S/4 HANA. |
Key Assumptions
- Notification is in scope based on data design and any exception requested by business
- Data cleansing has met the required percentage threshold for the specified mock cycle and all preparation activities have been completed
- For legacy Notifications generated by maintenance plans, legacy links to plans will not be maintained
- No data enrichment is needed
- All mandatory fields will need to be cleansed at source, and if not cleansed, the value will be defaulted
- Work Order field will be updated when loading Work Order master data
- Based on discussion with the business - the User Status in legacy will not be migrated over to S4
- Work Order assigned to the NOCO Notification is not in scope for migration
- All Long Text will be migrated and defaulted to the language key of the plant
See also
Change log
Workflow history
| Title | Last Updated By | Updated | Status | |
|---|---|---|---|---|
| There are no pages at the moment. | ||||