Status	Approved
Owner	TEE-ext, Paul
Stakeholders	ERGUIZA-ext, Pinky Love PUN-ext, Eddy JOSHI-ext, Aditya VILARES, ines LEIGHTON-ext, Dean @STEFANESCU-ext, Aurelia MOUSSA-ext, Eva HEARD-ext, Kevin YUE-ext, Betty

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:
1. 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))
2. 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 Generated from Maintenance Plans:
1. Include Notifications that have OPEN Work Order (QMEL-AUFNR) 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

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 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 / Damage Code / Cause Code / Activities / Tasks)
Notification Status: NOCO

The data from legacy system excludes Notifications with:

Notification Status: DLFL (flagged for Deletion), ARNB (Blocked for Archiving)
Work Order assigned to the NOCO Notification is not in scope for migration

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.

List of source systems and approximate number of records

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 does not have multi language support. Notification text will be migrated using EN logon.

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	Mandatory	Mandatory
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	ERNAM	ERNAM	Reported By	CHAR	12	Mandatory	Mandatory
QMEL	ERDAT	ERDAT	Date on Which Record Was Created	DATS	8	Mandatory	Mandatory
QMEL	AENAM	AENAM	Name of Person Who Changed Object	CHAR	12	Conditional	Conditional
QMEL	AEDAT	AEDAT	Changed On	DATS	8	Conditional	Conditional
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	INDTX	INDLTX	Object Long Text Available	CHAR	1	Conditional	Conditional
QMEL	QMKAT	QMKAT	Catalog Type - Coding	CHAR	1	Mandatory	System
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
QMEL	TZONSO	TZONSO	Time Zone for Notification	CHAR	6	Mandatory	Mandatory
QMEL	PHASE	QM_PHASE	Notification Processing Phase	CHAR	1	Mandatory	Mandatory
QMIH	IWERK	IWERK	Maintenance Planning Plant	CHAR	4	Mandatory	Mandatory
QMIH	ILOAI	ILOAI	ILOA Individual	CHAR	1	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	AUSZT	AUSZT	Breakdown Duration	FLTP	16(16)	Conditional	Not used
QMIH	MAUEH	MAUEH	Unit for Breakdown Duration	UNIT	3	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	REVNR	REVNI	Planning Bucket	CHAR	8	Conditional	Conditional
QMIH	SCREENTY	SCRTP	Scenario or Subscreen Category	CHAR	4	Mandatory	Mandatory
QMIH	DETECTIONCATALOG	DETECTIONCATALOG	Detection Method Profile	CHAR	2	Conditional	Conditional
QMIH	DETECTIONCODEGROUP	DETECTIONCODEGROUP	Detection Method Group	CHAR	8	Conditional	Conditional
QMIH	DETECTIONCODE	DETECTIONCODE	Detection Method	CHAR	4	Conditional	Conditional
QMIH	MAINTNOTIFOVRLPROCPHASE	MAINTNOTIFOVRLPROCPHASE	Process Phase	CHAR	2	Conditional	Conditional
QMIH	MAINTNOTIFOVRLPROCSUBPHASE	MAINTNOTIFOVRLPROCSUBPHASE	Process Subphase	CHAR	4	Conditional	Conditional
QMEL	AUFNR	AUFNR	Order Number	CHAR	12	System*	System*
QMIH	WARPL	WARPL	Maintenance Plan	CHAR	12	System*	System*

Note: Fields with System* are used in Transformation Rule logic

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	FENUM	FELFD	Item Number in Item Record	NUMC	4	Mandatory	Mandatory
QMFE	ERNAM	ERNAM	Name of Person who Created the Object	CHAR	12	Conditional	Conditional
QMFE	ERDAT	ERDAT	Date on Which Record Was Created	DATS	8	Conditional	Conditional
QMFE	AENAM	AENAM	Name of Person Who Changed Object	CHAR	12	Conditional	Conditional
QMFE	AEDAT	AEDAT	Changed On	DATS	8	Conditional	Conditional
QMFE	FETXT	FETXT	Notification Item Short Text	CHAR	40	Conditional	Conditional
QMFE	FEKAT	FEKAT	Catalog Type - Problems/Defects	CHAR	1	Conditional	Conditional
QMFE	FEGRP	FEGRP	Code Group - Problem	CHAR	8	Conditional	Conditional
QMFE	FECOD	FECOD	Problem or Damage Code	CHAR	4	Conditional	Conditional
QMFE	FEVER	QVERSNR	Version Number	CHAR	6	Conditional	Conditional
QMFE	OTKAT	OTKAT	Catalog Type - Object Parts	CHAR	1	Conditional	Conditional
QMFE	OTGRP	OTGRP	Code Group - Object Parts	CHAR	8	Conditional	Conditional
QMFE	OTEIL	OTEIL	Part of Object	CHAR	4	Conditional	Conditional
QMFE	OTVER	QVERSNR	Version Number	CHAR	6	Conditional	Conditional
QMFE	INDTX	INDLTX	Object Long Text Available	CHAR	1	Conditional	Conditional
QMFE	KZMLA	KZMLA	Primary language indicator for text segment	CHAR	1	Conditional	Conditional
QMFE	ERZEIT	ERZEIT	Time, at Which Record Was Added	TIMS	6	Conditional	Conditional
QMFE	AEZEIT	AEZEIT	Time of Change	TIMS	6	Conditional	Conditional
QMFE	ANZFEHLER	QANZFEHL4	Number of Defects Found	INT4	10	Conditional	Conditional
QMFE	AUTKZ	QAUTKZ	Data Record Created with Function 'Create with Copy Model'	CHAR	1	Conditional	Conditional

Note: Each Notification Header can have many Notification Items

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	Mandatory	Mandatory
QMUR	FENUM	FELFD	Item Number in Item Record	NUMC	4	Mandatory	Mandatory
QMUR	URNUM	URNUM	Sequential Number for Cause	NUMC	4	Mandatory	Mandatory
QMUR	ERNAM	ERNAM	Name of Person who Created the Object	CHAR	12	Conditional	Conditional
QMUR	ERDAT	ERDAT	Date on Which Record Was Created	DATS	8	Conditional	Conditional
QMUR	AENAM	AENAM	Name of Person Who Changed Object	CHAR	12	Conditional	Conditional
QMUR	AEDAT	AEDAT	Changed On	DATS	8	Conditional	Conditional
QMUR	URTXT	URSTX	Cause Text	CHAR	40	Conditional	Conditional
QMUR	URKAT	URKAT	Catalog Type - Causes	CHAR	1	Conditional	Conditional
QMUR	URGRP	URGRP	Code Group - Causes	CHAR	8	Conditional	Conditional
QMUR	URCOD	URCOD	Cause Code	CHAR	4	Conditional	Conditional
QMUR	URVER	QVERSNR	Version Number	CHAR	6	Conditional	Conditional
QMUR	INDTX	INDLTX	Object Long Text Available	CHAR	1	Conditional	Conditional
QMUR	KZMLA	KZMLA	Primary language indicator for text segment	CHAR	1	Conditional	Conditional
QMUR	ERZEIT	ERZEIT	Time, at Which Record Was Added	TIMS	6	Conditional	Conditional
QMUR	AEZEIT	AEZEIT	Time of Change	TIMS	6	Conditional	Conditional
QMUR	QURNUM	QURNUM	Sort Number for Cause	NUMC	4	Conditional	Conditional
QMUR	AUTKZ	QAUTKZ	Data Record Created with Function 'Create with Copy Model'	CHAR	1	Conditional	Conditional

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 Task

Table	Field	Data Element	Field Description	Data Type	Length	Requirement (Notif. Type Y1)	Requirement (Notif. Type Y2)
QMSM	QMNUM	QMNUM	Notification Number	CHAR	12	Mandatory	Mandatory
QMSM	MANUM	MANUM	Sequential Task Number	NUMC	4	Conditional	Conditional
QMSM	MNKAT	MAKAT	Catalog Type - Tasks	CHAR	1	Conditional	Conditional
QMSM	MNGRP	MAGRP	Code Group - Tasks	CHAR	8	Conditional	Conditional
QMSM	MNCOD	MNCOD	Task Code	CHAR	4	Conditional	Conditional
QMSM	MNVER	QVERSNR	Version Number	CHAR	6	Conditional	Conditional
QMSM	FOLGEACT	QMFOLACT	Follow-Up Action for Task	CHAR	8	Conditional	Conditional
QMSM	FOLACTPROT	QMFOAPROT	Log for Follow-Up Action	CHAR	1	Conditional	Conditional
QMSM	MATXT	MATXT	Short Text for Task	CHAR	40	Conditional	Conditional
QMSM	ERNAM	ERNAM	Name of Person who Created the Object	CHAR	12	Conditional	Conditional
QMSM	ERDAT	ERDAT	Date on Which Record Was Created	DATS	8	Conditional	Conditional
QMSM	AENAM	AENAM	Name of Person Who Changed Object	CHAR	12	Conditional	Conditional
QMSM	AEDAT	AEDAT	Changed On	DATS	8	Conditional	Conditional
QMSM	PSTER	PSTER	Planned Start Date	DATS	8	Conditional	Conditional
QMSM	PETER	PETER	Planned finish date	DATS	8	Conditional	Conditional
QMSM	INDTX	INDLTX	Object Long Text Available	CHAR	1	Conditional	Conditional
QMSM	KZMLA	KZMLA	Primary language indicator for text segment	CHAR	1	Conditional	Conditional
QMSM	PSTUR	PSTUR	Planned Start Time for Task	TIMS	6	Conditional	Conditional
QMSM	PETUR	PETUR	Planned Finish Time for Task	TIMS	6	Conditional	Conditional
QMSM	ERLNAM	QMSMERLNAM	Person Who Completed the Task	CHAR	12	Conditional	Conditional
QMSM	ERLDAT	QMSMERLDAT	Date on Which the Task Was Completed	DATS	8	Conditional	Conditional
QMSM	ERLZEIT	QMSMERLTIM	Time at Which Task Was Completed	TIMS	6	Conditional	Conditional
QMSM	WDVDAT	QMSMWDVDAT	Date on Which Task Was Resubmitted	DATS	8	Conditional	Conditional
QMSM	FENUM	FELFD	Item Number in Item Record	NUMC	4	Conditional	Conditional
QMSM	URNUM	URNUM	Sequential Number for Cause	NUMC	4	Conditional	Conditional
QMSM	ERZEIT	ERZEIT	Time, at Which Record Was Added	TIMS	6	Conditional	Conditional
QMSM	AEZEIT	AEZEIT	Time of Change	TIMS	6	Conditional	Conditional
QMSM	PARVW	QMSM_PARVW	Function of Person Responsible for Task	CHAR	2	Conditional	Conditional
QMSM	PARNR	QMSM_PARNR	Person Responsible for Task (Partner Number)	CHAR	12	Conditional	Conditional
QMSM	QSMNUM	QSMNUM	Sort Number for Task	NUMC	4	Conditional	Conditional
QMSM	AUTKZ	QAUTKZ	Data Record Created with Function 'Create with Copy Model'	CHAR	1	Conditional	Conditional
QMSM	KZACTIONBOX	QNKZACTIONBOX	Created Using Action Box	CHAR	1	Conditional	Conditional
QMSM	FUNKTION	QNFUNKTION	Keys for Function in Action Box	CHAR	4	Conditional	Conditional

11.Notification Task 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 Task 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

13.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	Mandatory	Mandatory
QMMA	MANUM	AKNUM	Consecutive Number of Activity	NUMC	4	Conditional	Conditional
QMMA	URNUM	URNUM	Sequential Number for Cause	NUMC	4	Conditional	Conditional
QMMA	MNKAT	MFKAT	Catalog Type - Activities	CHAR	1	Conditional	Conditional
QMMA	MNGRP	MFGRP	Code Group - Activities	CHAR	8	Conditional	Conditional
QMMA	MNCOD	MFCOD	Activity Code	CHAR	4	Conditional	Conditional
QMMA	MNVER	QVERSNR	Version Number	CHAR	6	Conditional	Conditional
QMMA	MATXT	MFTEXT	Activity Text	CHAR	40	Conditional	Conditional
QMMA	ERNAM	ERNAM	Name of Person who Created the Object	CHAR	12	Conditional	Conditional
QMMA	ERDAT	ERDAT	Date on Which Record Was Created	DATS	8	Conditional	Conditional
QMMA	AENAM	AENAM	Name of Person Who Changed Object	CHAR	12	Conditional	Conditional
QMMA	AEDAT	AEDAT	Changed On	DATS	8	Conditional	Conditional
QMMA	MAKLS	MAKLS	Task Class	CHAR	18	Conditional	Conditional
QMMA	KLAKZ	KLAKZ	Indicator: Classification exists	CHAR	1	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	KZMLA	KZMLA	Primary language indicator for text segment	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	ERZEIT	ERZEIT	Time, at Which Record Was Added	TIMS	6	Conditional	Conditional
QMMA	AEZEIT	AEZEIT	Time of Change	TIMS	6	Conditional	Conditional
QMMA	QMANUM	QMANUM	Sort Number for Activity	NUMC	4	Conditional	Conditional
QMMA	AUTKZ	QAUTKZ	Data Record Created with Function 'Create with Copy Model'	CHAR	1	Conditional	Conditional
QMMA	KZACTIONBOX	QNKZACTIONBOX	Created Using Action Box	CHAR	1	Conditional	Conditional
QMMA	FUNKTION	QNFUNKTION	Keys for Function in Action Box	CHAR	4	Conditional	Conditional

14.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

15.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	Catalog Type - Coding: Blank Catalog Type - Coding	Notification as per Relevancy Criteria assigned with blank Catalog Type - Coding	Notification Number, Short Text, Plant for Work Centre, Catalog Type - Coding	PF2, WP2
9004-002	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-003	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-004	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-005	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-006	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-007	C1	Notification relevant for APM not set to NOCO	Open Notification with no Work Order Assigned matching the criteria below: FL / EQ with APM Relevant Technical Object Type (IFLOT-EQART / EQUI-EQART) (listed in OTH_Technical Object Type_APM) Maintenance Plant 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 / Damage Code / Cause Code / Activities / Tasks) 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-008	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-009	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-010	C2	Short Text: Blank Short Text	Notification Short Text must not be blank	Notification Number, Short Text, Plant for Work Centre	PF2, WP2
9004-011	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-012	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-013	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-014	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-015	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-016	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-017	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-018	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-019	C3	Info Report: Catalog codes used by the legacy Notification Task	List of Catalog codes used by the legacy Notification Task	Notification Number, Sequential Task Number, Short Text for Task, Catalog Type - Tasks, Code Group - Tasks, Task Code	PF2, WP2
9004-020	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 Task, Catalog Type - Tasks, Code Group - Tasks, Task 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:
1. Perform full data extraction from relevant tables in the source system(s).
2. Perform extraction through the application layer.
3. 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	Value Mapping: Notification Type
3	PF2, WP2	QMEL	QMTXT	Short Text	S/4HANA	QMEL	QMTXT	Short Text	If not blank then Direct Mapping. If blank then default to: Work Order Description If not linked to Work Order then derive the value as per Value Mapping: OTH_Migration_Date Relevant Values A2D (using Object ID "9004" and Field Name = "QMEL-QMTXT".
4	PF2, WP2	QMEL	PRIOK	Priority	S/4HANA	QMEL	PRIOK	Priority	Value Mapping: Priority If blank derive the value as per Value Mapping: OTH_Migration_Date Relevant Values A2D (using Object ID "9004" and Field Name = "QMEL-PRIOK".
5	PF2, WP2	QMEL	ERNAM	Reported By	S/4HANA	QMEL	ERNAM	Reported By	Direct Mapping. If blank derive the value as per Value Mapping: OTH_Migration_Date Relevant Values A2D (using Object ID "9004" and Field Name = "QMEL-ERNAM".
6	PF2, WP2	QMEL	ERDAT	Date on Which Record Was Created	S/4HANA	QMEL	ERDAT	Date on Which Record Was Created	Direct Mapping.
7	PF2, WP2	QMEL	AENAM	Name of Person Who Changed Object	S/4HANA	QMEL	AENAM	Name of Person Who Changed Object	Direct Mapping.
8	PF2, WP2	QMEL	AEDAT	Changed On	S/4HANA	QMEL	AEDAT	Changed On	Direct Mapping.
9	PF2, WP2	QMEL	MZEIT	Notification Time	S/4HANA	QMEL	MZEIT	Notification Time	Direct Mapping. If blank default to: 00:00:00
10	PF2, WP2	QMEL	STRMN	Required Start Date	S/4HANA	QMEL	STRMN	Required Start Date	If not blank then Direct Mapping If blank and is: linked to Work Order then use Work Order value for Required Start Date If not linked to Work Order then derive the value as per Value Mapping: OTH_Migration_Date Relevant Values A2D (using Object ID "9004" and Field Name = "QMEL-STRMN". If Required End Date is earlier than Required Start Date, then default both Required End Date and Requested End Time from Work Order.
11	PF2, WP2	QMEL	STRUR	Required Start Time	S/4HANA	QMEL	STRUR	Required Start Time	If not blank then Direct Mapping If blank and is: linked to Work Order then use Work Order value for Required Start Date If not linked to Work Order then derive the value as per Value Mapping: OTH_Migration_Date Relevant Values A2D (using Object ID "9004" and Field Name = "QMEL-STRUR". If Required End Date and Requested End Time combination is earlier than Required Start Date, then default both Required End Date and Requested End Time from Work Order.
12	PF2, WP2	QMEL	LTRMN	Required End Date	S/4HANA	QMEL	LTRMN	Required End Date	If not blank then Direct Mapping If blank and is: linked to Work Order then use Work Order value for Required End Date not linked to Work Order then default to Required Start Date If Required End Date is earlier than Required Start Date, then default both Start and End Date from Work Order Note: Required End Date cannot be earlier than start date
13	PF2, WP2	QMEL	LTRUR	Requested End Time	S/4HANA	QMEL	LTRUR	Requested End Time	If not blank then Direct Mapping If blank and is: linked to Work Order then use Work Order value for Requested End Time not linked to Work Order then default Required Start Time If Required End Date and Requested End Time combination is earlier than Required Start Date, then default both Start and End Date from Work Order Note: Required End Date and Requested End Time combination cannot be earlier than start date
14	PF2, WP2	QMIH	EQUNR	Equipment Number	S/4HANA	QMEL	EQUNR	Equipment Number	If not blank, Use Value Mapping: Equipment If blank and the Notification is linked to a Work Order, derive the Equipment from the Work Order, Use Value Mapping: Equipment for the new EQUNR
15	PF2, WP2	IFLOT	TPLNR	Functional Location	S/4HANA	QMEL	EQUNR	Equipment Number	If new EQUNR is blank then: Value Mapping: Equipment If blank and the Notification is linked to a Work Order, derive the Equipment from the Work Order, Use Value Mapping: Equipment for the new EQUNR Note: Transformation Rule for legacy EQUNR must run before this rule
16	PF2, WP2	IFLOT	TPLNR	Functional Location	S/4HANA	IFLOT	TPLNR	Functional Location Label	If Equipment is not blank then default to blank. If new Equipment is blank: use Value Mapping: Functional Location. If blank and the Notification is linked to a Work Order, derive the Functional Location from the Work Order, Use Value Mapping: Functional Location for the new Functional Location
17
18
19	PF2, WP2	-	RBNR	Catalog Profile	S/4HANA	QMEL	RBNR	Catalog Profile	If Equipment is not blank then, derive the new Catalog Profile of the Assembly assigned to the Equipment If Equipment is blank then, derive the new Catalog Profile of the Assembly assigned to the Functional Location If still blank then derive the value as per Value Mapping: OTH_Migration_Date Relevant Values A2D (using Object ID "9004" and Field Name = "QMEL-RBNR"
20	PF2, WP2	QMEL	INDTX	Object Long Text Available	S/4HANA	QMEL	INDTX	Object Long Text Available	Direct Mapping
21	PF2, WP2	QMEL	QMKAT	Catalog Type - Coding	S/4HANA	QMEL	QMKAT	Catalog Type - Coding	Value Mapping: Catalog Code Group and Code If blank then derive the value as per Value Mapping: OTH_Migration_Date Relevant Values A2D (using Object ID "9004" and Field Name = "QMEL-QMKAT"
22	PF2, WP2	QMEL	QMGRP	Code Group - Coding	S/4HANA	QMEL	QMGRP	Code Group - Coding	Value Mapping: Catalog Code Group and Code If blank then derive the value as per Value Mapping: OTH_Migration_Date Relevant Values A2D (using Object ID "9004" and Field Name = "QMEL-QMGRP"
23	PF2, WP2	QMEL	QMCOD	Coding	S/4HANA	QMEL	QMCOD	Coding	Value Mapping: Catalog Code Group and Code If blank then derive the value as per Value Mapping: OTH_Migration_Date Relevant Values A2D (using Object ID "9004" and Field Name = "QMEL-QMCOD"
24	-	-	-	-	S/4HANA	QMEL	ARBPL	Object ID of the Work Center	If EQUNR is not blank then use EQUI-ARBPL and Value Mapping: Work Centre. If EQUNR is blank then use use IFLOT-ARBPL and Value Mapping: Work Centre. If still blank and the Notification is linked to a Work Order, derive the Work Centre from the Work Order and Value Mapping: Work Centre.
25	-	-	-	-	S/4HANA	QMEL	ARBPLWERK	Plant for Work Center	If EQUNR is not blank then use EQUI-WERK and Value Mapping: Plant (Maintenance Plant = Yes) If EQUNR is blank then use IFLOT-WERK and Value Mapping: Plant (Maintenance Plant = Yes) If still blank then derive the value as per Value Mapping: OTH_Migration_Date Relevant Values A2D (using Object ID "9004" and Field Name = "QMEL-ARBPLWERK"
26	PF2, WP2	QMEL	TZONSO	Time Zone for Notification	S/4HANA	QMEL	TZONSO	Time Zone for Notification	Direct Mapping
27	PF2, WP2	QMEL	PHASE	Notification Processing Phase	S/4HANA	QMEL	PHASE	Notification Processing Phase	Direct Mapping
28	-	-	-	-	S/4HANA	QMIH	IWERK	Maintenance Planning Plant	If EQUNR is not blank then use EQUI-IWERK and Value Mapping: Plant (Maintenance Plant = Yes) If EQUNR is not blank then use IFLOT-IWERK: If still blank then derive the value as per Value Mapping: OTH_Migration_Date Relevant Values A2D (using Object ID "9004" and Field Name = "QMEL-IWERK"
29	PF2, WP2	QMIH	MSAUS	Breakdown Indicator	S/4HANA	QMIH	MSAUS	Breakdown Indicator	If QMART = "Y1' then Direct Mapping If QMART = "Y2' then default to blank
30	PF2, WP2	QMIH	AUSVN	Malfunct. Start Date	S/4HANA	QMIH	AUSVN	Malfunct. Start Date	If QMART = "Y1' then Direct Mapping If QMART = "Y2' then default to blank
31	PF2, WP2	QMIH	AUZTV	Malfunct. Start Time	S/4HANA	QMIH	AUZTV	Malfunct. Start Time	If QMART = "Y1' then Direct Mapping If QMART = "Y2' then default to blank
32	PF2, WP2	QMIH	AUSBS	Malfunct. End Date	S/4HANA	QMIH	AUSBS	Malfunct. End Date	If QMART = "Y1' then Direct Mapping If QMART = "Y2' then default to blank
33	PF2, WP2	QMIH	AUZTB	Malfunct. End Time	S/4HANA	QMIH	AUZTB	Malfunct. End Time	If QMART = "Y1' then Direct Mapping If QMART = "Y2' then default to blank
34	PF2, WP2	QMIH	AUSZT	Breakdown Duration	S/4HANA	QMIH	AUSZT	Breakdown Duration	If QMART = "Y1' then Direct Mapping If QMART = "Y2' then default to blank
35	PF2, WP2	QMIH	MAUEH	Breakdown Unit	S/4HANA	QMIH	MAUEH	Breakdown Unit	If QMART = "Y1' then Direct Mapping If QMART = "Y2' then default to blank
36	PF2, WP2	QMIH	AUSWK	Effect on Operation	S/4HANA	QMIH	AUSWK	Effect on Operation	Value Mapping: Effect of malfunction on the system If blank then derive the value as per Value Mapping: OTH_Migration_Date Relevant Values A2D (using Object ID "9004" and Field Name = "QMEL-AUSWK"
37	PF2, WP2	-	INGRP	Planner Group	S/4HANA	QMIH	INGRP	Planner Group	If EQUNR is not blank then use EQUZ-INGRP for the rules below, else use IFLOT-INGRP: Value Mapping: Maintenance Planner Group If blank or cannot be mapped, and if linked to Work Order, then Value Mapping: Maintenance Planner Group from Work Order. If still blank then derive the value as per Value Mapping: OTH_Migration_Date Relevant Values A2D (using Object ID "9004" and Field Name = "QMEL-INGRP"
38	PF2, WP2	QMIH	REVNR	Planning Bucket	S/4HANA	QMIH	REVNR	Planning Bucket	Value Mapping: Maintenance Planning Bucket
39	PF2, WP2	QMIH	DETECTIONCATALOG	Detection Method Profile	S/4HANA	QMIH	DETECTIONCATALOG	Detection Method Profile	Derive the value as per Value Mapping: OTH_Migration_Date Relevant Values A2D (using Object ID "9004" and Field Name = "QMEL-DETECTIONCATALOG"
40	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 = "QMEL-DETECTIONCODEGROUP"
41	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 = "QMEL-DETECTIONCODE"
42	PF2, WP2	QMIH	MAINTNOTIFOVRLPROCPHASE	Process Phase	S/4HANA	QMIH	MAINTNOTIFOVRLPROCPHASE	Process Phase	Value Mapping to phases. Dependent on the Notif Type and Notif Status
43	PF2, WP2	QMIH	MAINTNOTIFOVRLPROCSUBPHASE	Process Subphase	S/4HANA	QMIH	MAINTNOTIFOVRLPROCSUBPHASE	Process Subphase	Value Mapping to phases. Dependent on the Notif Type and Notif Status

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	Direct Mapping

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	Direct Mapping
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	ERNAM	Reported By	S/4HANA	QMFE	ERNAM	Reported By	Direct Mapping. If blank default to Migration User ID (Name)
4	PF2, WP2	QMFE	ERDAT	Date on Which Record Was Created	S/4HANA	QMFE	ERDAT	Date on Which Record Was Created	Direct Mapping
5	PF2, WP2	QMFE	AENAM	Name of Person Who Changed Object	S/4HANA	QMFE	AENAM	Name of Person Who Changed Object	Direct Mapping
6	PF2, WP2	QMFE	AEDAT	Changed On	S/4HANA	QMFE	AEDAT	Changed On	Direct Mapping
7	PF2, WP2	QMFE	FETXT	Notification Item Short Text	S/4HANA	QMFE	FETXT	Notification Item Short Text	Direct Mapping
8	PF2, WP2	QMFE	FEKAT	Catalog Type - Problems/Defects	S/4HANA	QMFE	FEKAT	Catalog Type - Problems/Defects	Value Mapping: Catalog Code Group and Code
9	PF2, WP2	QMFE	FEGRP	Damage – Code Group	S/4HANA	QMFE	FEGRP	Damage – Code Group	Value Mapping: Catalog Code Group and Code
10	PF2, WP2	QMFE	FECOD	Problem or Damage Code	S/4HANA	QMFE	FECOD	Problem or Damage Code	Value Mapping: Catalog Code Group and Code
11	PF2, WP2	QMFE	FEVER	Version Number	S/4HANA	QMFE	FEVER	Version Number	Direct Mapping
12	PF2, WP2	QMFE	OTKAT	Catalog Type - Object Parts	S/4HANA	QMFE	OTKAT	Catalog Type - Object Parts	Value Mapping: Catalog Code Group and Code
13	PF2, WP2	QMFE	OTGRP	Code Group - Object Parts	S/4HANA	QMFE	OTGRP	Code Group - Object Parts	Value Mapping: Catalog Code Group and Code
14	PF2, WP2	QMFE	OTEIL	Part of Object	S/4HANA	QMFE	OTEIL	Part of Object	Value Mapping: Catalog Code Group and Code
15	PF2, WP2	QMFE	OTVER	Version Number	S/4HANA	QMFE	OTVER	Version Number	Direct Mapping
16	PF2, WP2	QMFE	INDTX	Object Long Text Available	S/4HANA	QMFE	INDTX	Object Long Text Available	Direct Mapping
17	PF2, WP2	QMFE	KZMLA	Primary language indicator for text segment	S/4HANA	QMFE	KZMLA	Primary language indicator for text segment	Direct Mapping
18	PF2, WP2	QMFE	ERZEIT	Time, at Which Record Was Added	S/4HANA	QMFE	ERZEIT	Time, at Which Record Was Added	Direct Mapping
19	PF2, WP2	QMFE	AEZEIT	Time of Change	S/4HANA	QMFE	AEZEIT	Time of Change	Direct Mapping
20	PF2, WP2	QMFE	ANZFEHLER	Number of Defects Found	S/4HANA	QMFE	ANZFEHLER	Number of Defects Found	Direct Mapping
21	PF2, WP2	QMFE	AUTKZ	Data Record Created with Function 'Create with Copy Model'	S/4HANA	QMFE	AUTKZ	Data Record Created with Function 'Create with Copy Model'	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	Direct Mapping

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	Direct Mapping
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	ERNAM	Name of Person who Created the Object	S/4HANA	QMUR	ERNAM	Name of Person who Created the Object	Direct Mapping. If blank default to Migration User ID (Name)
5	PF2, WP2	QMUR	ERDAT	Date on Which Record Was Created	S/4HANA	QMUR	ERDAT	Date on Which Record Was Created	Direct Mapping
6	PF2, WP2	QMUR	AENAM	Name of Person Who Changed Object	S/4HANA	QMUR	AENAM	Name of Person Who Changed Object	Direct Mapping
7	PF2, WP2	QMUR	AEDAT	Changed On	S/4HANA	QMUR	AEDAT	Changed On	Direct Mapping
8	PF2, WP2	QMUR	URTXT	Cause Text	S/4HANA	QMUR	URTXT	Cause Text	Direct Mapping
9	PF2, WP2	QMUR	URKAT	Catalog Type - Causes	S/4HANA	QMUR	URKAT	Catalog Type - Causes	Value Mapping: Catalog Code Group and Code
10	PF2, WP2	QMUR	URGRP	Code Group - Causes	S/4HANA	QMUR	URGRP	Code Group - Causes	Value Mapping: Catalog Code Group and Code
11	PF2, WP2	QMUR	URCOD	Cause Code	S/4HANA	QMUR	URCOD	Cause Code	Value Mapping: Catalog Code Group and Code
12	PF2, WP2	QMUR	URVER	Version Number	S/4HANA	QMUR	URVER	Version Number	Direct Mapping
13	PF2, WP2	QMUR	INDTX	Object Long Text Available	S/4HANA	QMUR	INDTX	Object Long Text Available	Direct Mapping
14	PF2, WP2	QMUR	KZMLA	Primary language indicator for text segment	S/4HANA	QMUR	KZMLA	Primary language indicator for text segment	Direct Mapping
15	PF2, WP2	QMUR	ERZEIT	Time, at Which Record Was Added	S/4HANA	QMUR	ERZEIT	Time, at Which Record Was Added	Direct Mapping
16	PF2, WP2	QMUR	AEZEIT	Time of Change	S/4HANA	QMUR	AEZEIT	Time of Change	Direct Mapping
17	PF2, WP2	QMUR	QURNUM	Sort Number for Cause	S/4HANA	QMUR	QURNUM	Sort Number for Cause	Direct Mapping
18	PF2, WP2	QMUR	AUTKZ	Data Record Created with Function 'Create with Copy Model'	S/4HANA	QMUR	AUTKZ	Data Record Created with Function 'Create with Copy Model'	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	Direct Mapping

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	Direct Mapping
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 Task Transformation Rule

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	-	-	-	-	S/4HANA	QMSM	QMNUM	Notification Number	System (Internal numbering)
2	-	-	-	-	S/4HANA	QMSM	MANUM	Sequential Task Number	System (Internal numbering)
3	PF2, WP2	QMSM	MNKAT	Catalog Type - Tasks	S/4HANA	QMSM	MNKAT	Catalog Type - Tasks	Direct Mapping
4	PF2, WP2	QMSM	MNGRP	Code Group - Tasks	S/4HANA	QMSM	MNGRP	Code Group - Tasks	Direct Mapping
5	PF2, WP2	QMSM	MNCOD	Task Code	S/4HANA	QMSM	MNCOD	Task Code	Direct Mapping
6	PF2, WP2	QMSM	MNVER	Version Number	S/4HANA	QMSM	MNVER	Version Number	Direct Mapping
7	PF2, WP2	QMSM	FOLGEACT	Follow-Up Action for Task	S/4HANA	QMSM	FOLGEACT	Follow-Up Action for Task	Direct Mapping
8	PF2, WP2	QMSM	FOLACTPROT	Log for Follow-Up Action	S/4HANA	QMSM	FOLACTPROT	Log for Follow-Up Action	Direct Mapping
9	PF2, WP2	QMSM	MATXT	Short Text for Task	S/4HANA	QMSM	MATXT	Short Text for Task	Direct Mapping
10	PF2, WP2	QMSM	ERNAM	Name of Person who Created the Object	S/4HANA	QMSM	ERNAM	Name of Person who Created the Object	Direct Mapping. If blank default to Migration User ID (Name)
11	PF2, WP2	QMSM	ERDAT	Date on Which Record Was Created	S/4HANA	QMSM	ERDAT	Date on Which Record Was Created	Direct Mapping
12	PF2, WP2	QMSM	AENAM	Name of Person Who Changed Object	S/4HANA	QMSM	AENAM	Name of Person Who Changed Object	Direct Mapping
13	PF2, WP2	QMSM	AEDAT	Changed On	S/4HANA	QMSM	AEDAT	Changed On	Direct Mapping
14	PF2, WP2	QMSM	PSTER	Planned Start Date	S/4HANA	QMSM	PSTER	Planned Start Date	Direct Mapping
15	PF2, WP2	QMSM	PETER	Planned finish date	S/4HANA	QMSM	PETER	Planned finish date	Direct Mapping
16	PF2, WP2	QMSM	INDTX	Object Long Text Available	S/4HANA	QMSM	INDTX	Object Long Text Available	Direct Mapping
17	PF2, WP2	QMSM	KZMLA	Primary language indicator for text segment	S/4HANA	QMSM	KZMLA	Primary language indicator for text segment	Direct Mapping
18	PF2, WP2	QMSM	PSTUR	Planned Start Time for Task	S/4HANA	QMSM	PSTUR	Planned Start Time for Task	Direct Mapping
19	PF2, WP2	QMSM	PETUR	Planned Finish Time for Task	S/4HANA	QMSM	PETUR	Planned Finish Time for Task	Direct Mapping
20	PF2, WP2	QMSM	ERLNAM	Person Who Completed the Task	S/4HANA	QMSM	ERLNAM	Person Who Completed the Task	Direct Mapping
21	PF2, WP2	QMSM	ERLDAT	Date on Which the Task Was Completed	S/4HANA	QMSM	ERLDAT	Date on Which the Task Was Completed	Direct Mapping
22	PF2, WP2	QMSM	ERLZEIT	Time at Which Task Was Completed	S/4HANA	QMSM	ERLZEIT	Time at Which Task Was Completed	Direct Mapping
23	PF2, WP2	QMSM	WDVDAT	Date on Which Task Was Resubmitted	S/4HANA	QMSM	WDVDAT	Date on Which Task Was Resubmitted	Direct Mapping
24	PF2, WP2	QMSM	FENUM	Item Number in Item Record	S/4HANA	QMSM	FENUM	Item Number in Item Record	Direct Mapping
25	PF2, WP2	QMSM	URNUM	Sequential Number for Cause	S/4HANA	QMSM	URNUM	Sequential Number for Cause	Direct Mapping
26	PF2, WP2	QMSM	ERZEIT	Time, at Which Record Was Added	S/4HANA	QMSM	ERZEIT	Time, at Which Record Was Added	Direct Mapping
27	PF2, WP2	QMSM	AEZEIT	Time of Change	S/4HANA	QMSM	AEZEIT	Time of Change	Direct Mapping
28	PF2, WP2	QMSM	PARVW	Function of Person Responsible for Task	S/4HANA	QMSM	PARVW	Function of Person Responsible for Task	Direct Mapping
29	PF2, WP2	QMSM	PARNR	Person Responsible for Task (Partner Number)	S/4HANA	QMSM	PARNR	Person Responsible for Task (Partner Number)	Direct Mapping
30	PF2, WP2	QMSM	QSMNUM	Sort Number for Task	S/4HANA	QMSM	QSMNUM	Sort Number for Task	Direct Mapping
31	PF2, WP2	QMSM	AUTKZ	Data Record Created with Function 'Create with Copy Model'	S/4HANA	QMSM	AUTKZ	Data Record Created with Function 'Create with Copy Model'	Direct Mapping
32	PF2, WP2	QMSM	KZACTIONBOX	Created Using Action Box	S/4HANA	QMSM	KZACTIONBOX	Created Using Action Box	Direct Mapping
33	PF2, WP2	QMSM	FUNKTION	Keys for Function in Action Box	S/4HANA	QMSM	FUNKTION	Keys for Function in Action Box	Direct Mapping

11.Notification Task 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 "QMSM"
2	-	-	-	-	S/4HANA	STXL	TDNAME	Name	New Notification Number + New Sequential Task Number
3	-	-	-	-	S/4HANA	STXH	TDID	Text ID	Default to 'LTXT'
4	PF2, WP2	STXH	TDSPRAS	Language Key	S/4HANA	STXH	TDSPRAS	Language Key	Direct Mapping

12.Notification Task 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 "QMSM"
2	-	-	-	-	S/4HANA	STXL	TDNAME	Name	New Notification Number + New Sequential Task Number
3	-	-	-	-	S/4HANA	STXL	TDID	Text ID	Default to 'LTXT'
4	PF2, WP2	STXL	TDSPRAS	Language Key	S/4HANA	STXL	TDSPRAS	Language Key	Direct Mapping
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

13.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	MNKAT	Catalog Type - Activities	S/4HANA	QMMA	MNKAT	Catalog Type - Activities	Direct Mapping
5	PF2, WP2	QMMA	MNGRP	Code Group - Activities	S/4HANA	QMMA	MNGRP	Code Group - Activities	Direct Mapping
6	PF2, WP2	QMMA	MNCOD	Activity Code	S/4HANA	QMMA	MNCOD	Activity Code	Direct Mapping
7	PF2, WP2	QMMA	MNVER	Version Number	S/4HANA	QMMA	MNVER	Version Number	Direct Mapping
8	PF2, WP2	QMMA	MATXT	Activity Text	S/4HANA	QMMA	MATXT	Activity Text	Direct Mapping
9	PF2, WP2	QMMA	ERNAM	Name of Person who Created the Object	S/4HANA	QMMA	ERNAM	Name of Person who Created the Object	Direct Mapping. If blank default to Migration User ID (Name)
10	PF2, WP2	QMMA	ERDAT	Date on Which Record Was Created	S/4HANA	QMMA	ERDAT	Date on Which Record Was Created	Direct Mapping
11	PF2, WP2	QMMA	AENAM	Name of Person Who Changed Object	S/4HANA	QMMA	AENAM	Name of Person Who Changed Object	Direct Mapping
12	PF2, WP2	QMMA	AEDAT	Changed On	S/4HANA	QMMA	AEDAT	Changed On	Direct Mapping
13	PF2, WP2	QMMA	MAKLS	Task Class	S/4HANA	QMMA	MAKLS	Task Class	Direct Mapping
14	PF2, WP2	QMMA	KLAKZ	Indicator: Classification exists	S/4HANA	QMMA	KLAKZ	Indicator: Classification exists	Direct Mapping
15	PF2, WP2	QMMA	PSTER	Start Date	S/4HANA	QMMA	PSTER	Start Date	Direct Mapping
16	PF2, WP2	QMMA	PETER	End Date	S/4HANA	QMMA	PETER	End Date	Direct Mapping
17	PF2, WP2	QMMA	INDTX	Object Long Text Available	S/4HANA	QMMA	INDTX	Object Long Text Available	Direct Mapping
18	PF2, WP2	QMMA	KZMLA	Primary language indicator for text segment	S/4HANA	QMMA	KZMLA	Primary language indicator for text segment	Direct Mapping
19	PF2, WP2	QMMA	PSTUR	Start Time of Activity	S/4HANA	QMMA	PSTUR	Start Time of Activity	Direct Mapping
20	PF2, WP2	QMMA	PETUR	End Time of Activity	S/4HANA	QMMA	PETUR	End Time of Activity	Direct Mapping
21	PF2, WP2	QMMA	ERZEIT	Time, at Which Record Was Added	S/4HANA	QMMA	ERZEIT	Time, at Which Record Was Added	Direct Mapping
22	PF2, WP2	QMMA	AEZEIT	Time of Change	S/4HANA	QMMA	AEZEIT	Time of Change	Direct Mapping
23	PF2, WP2	QMMA	QMANUM	Sort Number for Activity	S/4HANA	QMMA	QMANUM	Sort Number for Activity	Direct Mapping
24	PF2, WP2	QMMA	AUTKZ	Data Record Created with Function 'Create with Copy Model'	S/4HANA	QMMA	AUTKZ	Data Record Created with Function 'Create with Copy Model'	Direct Mapping
25	PF2, WP2	QMMA	KZACTIONBOX	Created Using Action Box	S/4HANA	QMMA	KZACTIONBOX	Created Using Action Box	Direct Mapping
26	PF2, WP2	QMMA	FUNKTION	Keys for Function in Action Box	S/4HANA	QMMA	FUNKTION	Keys for Function in Action Box	Direct Mapping

14.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	Direct Mapping

15.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	Direct Mapping
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
Notification Type	Old to new Notification Type
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:

Mandatory Fields
Field and Value Mapping Correctness
Null Checks
Text Length 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
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)

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	T024I-Planner groups
2	T356-Priority
3	T356A-Priority type
4	T357A-Effect of malfunction on the system
5	TQ15-Inspection catalog type index
6	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
9101	Maintenance Planning Bucket

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
Invalid Data	Invalid Maintenance Planning Bucket	Expedite whether the master data is changed in the system
Configuration	Invalid Planner groups	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
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 Inspection catalog type index	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

Change log

Version	Published	Changed By
CURRENT (v. 337)	Apr 24, 2026 12:25	PUN-ext, Eddy
v. 450	Apr 20, 2026 08:57	ERGUIZA-ext, Pinky Love
v. 449	Apr 20, 2026 08:25	ERGUIZA-ext, Pinky Love
v. 448	Apr 17, 2026 04:28	ERGUIZA-ext, Pinky Love
v. 447	Apr 06, 2026 15:46	PUN-ext, Eddy
v. 446	Apr 02, 2026 13:44	ERGUIZA-ext, Pinky Love
v. 445	Feb 10, 2026 06:54	TEE-ext, Paul
v. 444	Feb 10, 2026 06:52	TEE-ext, Paul
v. 443	Feb 09, 2026 15:23	TEE-ext, Paul
v. 442	Feb 09, 2026 15:20	TEE-ext, Paul

Go to Page History

Workflow history

Title	Last Updated By	Updated	Status
There are no pages at the moment.

Apr 27, 2026	Actor	Type	Activity	Version
Approved	MOUSSA-ext, Eva	State	changed state to Approved at 9:11 am	v451
Revision under Review	MOUSSA-ext, Eva	State	gave Minor change approval at 9:11 am v. 445 CR0438 approved
Revision under Review	MOUSSA-ext, Eva	State	changed state to Revision under Review at 9:11 am v. 445 CR0438 approved	v451
Apr 24, 2026
Revision in Progress	MOUSSA-ext, Eva	Comment	commented 2:03 pm Related to APM Jira PDM-1591
	PUN-ext, Eddy	Edit	updated the page at 12:25 pm
Apr 22, 2026
	HEARD-ext, Kevin	Comment	commented 2:09 pm and MOC Notifications.
	HEARD-ext, Kevin	Comment	commented 2:08 pm Should we rather call out the Notifications as they are? Reactive, Proactive, Project, Refurb & MOC? Keep what is there but add the above too.

Workflow history

Space shortcuts

Page tree

CNV-9004 Notification

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Notification does not have multi language support. Notification text will be migrated using EN logon.

Document Management

Refer to the Document Management in the SyWay Solution.

Target Design

Data Cleansing

Conversion Process

Extraction

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

Transformation

Transformation Run Sheet

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

Load Run Sheet

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

See also

Change log

Workflow history