You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 127 Next »

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:

  1. All Open Notifications (Source System Status: Outstanding, In Process (TJ02T-TXT04 = OSNO or NOPR)
  2. Assigned to active legacy Functional Location (IFLOT-TPLNR) (Source System Status Not any of these: Inactive, Delete (TJ02T-TXT04 = INAC or DLFL))
  3. Assigned to active legacy Equipment (EQUI-EQUNR) (Source System Status Not any of these: Inactive, In the warehouse, Available (TJ02T-TXT04 = INAC, ESTO or AVLB)) 
  4. Notifications having Maintenance Plant (QMEL-ARBPLWERK) in scope - Refer to Value Mapping: Plant (Maintenance Plant = Yes)
  5. Closed Notifications associated to relevant Functional Locations and Equipment for the past 3 years, limited to specific Technical Object Type (listed in OTH_Technical Object Type_APM) and specific list of Maintenance Plants only (for APM Historical Data)

The data from legacy system excludes:

  1. Notification with Source System Status Notification completed status (TJ02T-TXT04 = NOCO)
  2. Open Notifications with closed Work Orders (AUFK-AUFNR) (Source System Status: Closed (TJ02T-TXT04 = CLSD))

    APM - Historical Data
    Closed Notifications associated to relevant Functional Locations and Equipment for the past 3 years, limited to specific Technical Object Type (listed in OTH_Technical Object Type_APM) and specific list of Maintenance Plants only

List of Tables to extract for this object is maintained here: Extract Table Register.


List of source systems and approximate number of records
SourceScope

Source Approx No. of Records

Target SystemTarget Approx No. of Records

PF2, WP2

Relevant Measurement Documents will be extracted from PF2 and WP2

110,000

S/4HANA

110,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

TableFieldData ElementField DescriptionData TypeLengthRequirement (Notif. Type Y1)Requirement (Notif. Type Y2)Requirement (Notif. Type Y3)Requirement (Notif. Type Y4)Requirement (Notif. Type Y5)
QMELQMNUMQMNUMNotification NumberCHAR12Mandatory MandatoryMandatoryMandatoryMandatory
QMELQMARTQMARTNotification TypeCHAR2Mandatory MandatoryMandatoryMandatoryMandatory
QMELQMTXTQMTXTShort TextCHAR40Mandatory MandatoryMandatoryMandatoryMandatory
QMELARTPRARTPRPriority Type CHAR2Mandatory MandatoryMandatoryMandatoryMandatory
QMELPRIOKPRIOKPriorityCHAR1Mandatory MandatoryMandatoryMandatoryMandatory
QMELERNAMERNAMReported ByCHAR12Mandatory MandatoryMandatoryMandatoryMandatory
QMELERDATERDATDate on Which Record Was CreatedDATS8Mandatory MandatoryMandatoryMandatoryMandatory
QMELAENAMAENAMName of Person Who Changed ObjectCHAR12ConditionalConditionalConditionalConditionalConditional
QMELAEDATAEDATChanged OnDATS8ConditionalConditionalConditionalConditionalConditional
QMELMZEITMZEITTime of NotificationTIMS6Mandatory MandatoryMandatoryMandatoryMandatory
QMELQMDATQMDATDate of NotificationDATS8Mandatory MandatoryMandatoryMandatoryMandatory
QMELQMNAMQMNAMName of Person Reporting NotificationCHAR12MandatoryConditionalMandatoryMandatoryMandatory
QMELSTRMNSTRMNRequired Start DateDATS8Mandatory MandatoryMandatoryMandatoryMandatory
QMELSTRURSTRURRequired Start TimeTIMS6Mandatory MandatoryMandatoryMandatoryMandatory
QMELLTRMNLTRMNRequired End DateDATS8Mandatory MandatoryMandatoryMandatoryMandatory
QMELLTRURLTRURRequested End TimeTIMS6Mandatory MandatoryMandatoryMandatoryMandatory
QMELAUFNRAUFNROrder NumberCHAR12ConditionalSystemConditionalConditionalNot used
QMELMATNRMATNRMaterial NumberCHAR18Not usedNot usedNot usedMandatoryNot used
QMELMATKLMATKLMaterial GroupCHAR9Not usedNot usedNot usedMandatoryNot used
QMELOBJNRQMOBJNRObject Number for Status ManagementCHAR22Mandatory MandatoryMandatoryMandatoryMandatory
QMELRBNRRBNRCatalog ProfileCHAR9Mandatory MandatoryMandatoryMandatoryMandatory
QMELRBNRIRBNRIOrigin of Notifications Catalog ProfileCHAR1Mandatory MandatoryMandatoryMandatoryMandatory
QMELINDTXINDLTXObject Long Text AvailableCHAR1ConditionalConditionalConditionalConditionalConditional
QMELKZMLAKZMLAPrimary language indicator for text segmentCHAR1Mandatory MandatoryMandatoryMandatoryMandatory
QMELHERKZHERKZOrigin of NotificationCHAR2Mandatory MandatoryMandatoryMandatoryMandatory
QMELBEZDTBEZDTNotification Reference DateDATS8Mandatory MandatoryMandatoryMandatoryMandatory
QMELBEZURBEZUR_DNotification Reference TimeTIMS6Mandatory MandatoryMandatoryMandatoryMandatory
QMELAEZEITAEZEITTime of ChangeTIMS6Mandatory MandatoryMandatoryMandatoryMandatory
QMELERZEITERZEITTime, at Which Record Was AddedTIMS6Mandatory MandatoryMandatoryMandatoryMandatory
QMELQMKATQMKATCatalog Type - CodingCHAR1Mandatory SystemMandatoryMandatoryMandatory
QMELQMGRPQMGRPCode Group - CodingCHAR8MandatorySystemMandatoryMandatoryMandatory
QMELQMCODQMCODCodingCHAR4MandatorySystemMandatoryMandatoryMandatory
QMELCROBJTYCR_OBJTYObject types of the CIM resourceCHAR2Mandatory MandatoryMandatory Not used Not used
QMELARBPLLGWIDObject ID of the Work CenterNUMC8Mandatory MandatoryMandatory Not used Not used
QMELARBPLWERKQARBPWERKSPlant for Work CenterCHAR4Mandatory MandatoryMandatory Not used Not used
QMELMGEINMGEINUnit of MeasureUNIT3Not usedNot usedNot usedMandatoryNot used
QMELSERIALNRGERNRSerial NumberCHAR18Not usedNot usedNot usedConditionalNot used
QMELTZONSOTZONSOTime Zone for NotificationCHAR6Mandatory MandatoryMandatoryMandatoryMandatory

PSP_NRPS_POSNRWBS ElementNUMC8Not usedNot usedMandatoryNot usedNot used
QMELPHASEQM_PHASENotification Processing PhaseCHAR1Mandatory MandatoryMandatory Not used Not used
QMIHIWERKIWERKMaintenance Planning PlantCHAR4Mandatory MandatoryMandatoryMandatoryMandatory
QMIHILOANILOANLocation and account assignment for technical objectCHAR12Mandatory MandatoryMandatoryMandatoryMandatory
 ILOAIILOAIILOA IndividualCHAR1Mandatory MandatoryMandatoryNot usedMandatory
QMIHEQUNREQUNREquipment numberCHAR18ConditionalConditionalConditionalNot usedConditional
QMIHBAUTLBAUTLAssemblyCHAR18Mandatory MandatoryMandatoryNot usedMandatory
ILOATPLNRTPLNRFunctional LocationCHAR30Mandatory    
QMIHMSAUSMSAUSBreakdown IndicatorCHAR1ConditionalNot usedNot usedNot usedNot used
QMIHAUSVNAUSVNStart of Malfunction (Date)DATS8ConditionalNot usedConditionalNot usedNot used
QMIHAUSBSAUSBSEnd of Malfunction (Date)DATS8ConditionalNot usedConditionalNot usedNot used
QMIHAUZTVAUZTVStart of Malfunction (Time)TIMS6ConditionalNot usedConditionalNot usedNot used
QMIHAUZTBAUZTBEnd of Malfunction (Time)TIMS6ConditionalNot usedConditionalNot usedNot used
QMIHAUSZTAUSZTBreakdown DurationFLTP16(16)ConditionalNot usedConditionalNot usedNot used
QMIHMAUEHMAUEHUnit for Breakdown DurationUNIT3ConditionalNot usedConditionalNot usedNot used
QMIHAUSWKAUSWKEffect on OperationCHAR1MandatoryMandatoryMandatoryNot usedConditional
QMIHINGRPINGRPPlanner Group for Customer Service and Plant MaintenanceCHAR3MandatoryMandatoryMandatoryMandatoryMandatory
QMIHWARPLWARPLMaintenance PlanCHAR12Not usedConditionalNot usedNot usedNot used
QMIHABNUMABNUMMaintenance Plan Call NumberINT410Not usedConditionalNot usedNot usedNot used
QMIHWAPOSWAPOSMaintenance itemCHAR16Not usedConditionalNot usedNot usedNot used
QMIHSCREENTYSCRTPScenario or Subscreen CategoryCHAR4MandatoryMandatoryMandatoryMandatoryMandatory
QMIHPLNTYPLNTYTask List TypeCHAR1Not usedConditionalNot usedNot usedNot used
QMIHPLNNRPLNNRKey for Task List GroupCHAR8Not usedConditionalNot usedNot usedNot used
QMIHPLNALPLNALGroup CounterCHAR2Not usedConditionalNot usedNot usedNot used

 2.Notification Header Long Text Header

TableFieldData ElementField DescriptionData TypeLengthRequirement (Notif. Type Y1)Requirement (Notif. Type Y2)Requirement (Notif. Type Y3)Requirement (Notif. Type Y4)Requirement (Notif. Type Y5)
STXHTDOBJECTTDOBJECTTexts: application objectCHAR10MandatoryMandatoryMandatoryMandatoryMandatory
STXHTDNAMETDOBNAMENameCHAR70MandatoryMandatoryMandatoryMandatoryMandatory
STXH

TDID

TDID

Text IDCHAR4MandatoryMandatoryMandatoryMandatoryMandatory
STXHTDSPRASSPRASLanguage KeyLANG1MandatoryMandatoryMandatoryMandatoryMandatory

3.Notification Header Long Text Line

TableFieldData ElementField DescriptionData TypeLengthRequirement (Notif. Type Y1)Requirement (Notif. Type Y2)Requirement (Notif. Type Y3)Requirement (Notif. Type Y4)Requirement (Notif. Type Y5)
STXLTDOBJECTTDOBJECTTexts: application objectCHAR10MandatoryMandatoryMandatoryMandatoryMandatory
STXLTDNAMETDOBNAMENameCHAR70MandatoryMandatoryMandatoryMandatoryMandatory
STXL

TDID

TDID

Text IDCHAR4MandatoryMandatoryMandatoryMandatoryMandatory
STXLTDSPRASSPRASLanguage KeyLANG1MandatoryMandatoryMandatoryMandatoryMandatory
STXLCLUSTD_TAGTDFORMAT

Tag column

CHAR1MandatoryMandatoryMandatoryMandatoryMandatory
STXLROWCOUNTROWCOUNT

Row number

NUMC10MandatoryMandatoryMandatoryMandatoryMandatory
STXLTXLINETDLINE

Text Line

CHAR72MandatoryMandatoryMandatoryMandatoryMandatory

4.Notification Item

TableFieldData ElementField DescriptionData TypeLengthRequirement (Notif. Type Y1)Requirement (Notif. Type Y2)Requirement (Notif. Type Y3)Requirement (Notif. Type Y4)Requirement (Notif. Type Y5)
QMFEQMNUMQMNUMNotification NumberCHAR12MandatoryMandatoryMandatoryMandatoryMandatory
QMFEFENUMFELFDItem Number in Item RecordNUMC4MandatoryConditionalConditionalConditionalConditional
QMFEERNAMERNAMName of Person who Created the ObjectCHAR12ConditionalConditionalConditionalConditionalConditional
QMFEERDATERDATDate on Which Record Was CreatedDATS8ConditionalConditionalConditionalConditionalConditional
QMFEAENAMAENAMName of Person Who Changed ObjectCHAR12ConditionalConditionalConditionalConditionalConditional
QMFEAEDATAEDATChanged OnDATS8ConditionalConditionalConditionalConditionalConditional
QMFEFETXTFETXTNotification Item Short TextCHAR40ConditionalConditionalConditionalConditionalConditional
QMFEFEKATFEKATCatalog Type - Problems/DefectsCHAR1ConditionalConditionalConditionalConditionalConditional
QMFEFEGRPFEGRPCode Group - ProblemCHAR8ConditionalConditionalConditionalConditionalConditional
QMFEFECODFECODProblem or Damage CodeCHAR4ConditionalConditionalConditionalConditionalConditional
QMFEFEVERQVERSNRVersion NumberCHAR6ConditionalConditionalConditionalConditionalConditional
QMFEOTKATOTKATCatalog Type - Object PartsCHAR1ConditionalConditionalConditionalConditionalConditional
QMFEOTGRPOTGRPCode Group - Object PartsCHAR8ConditionalConditionalConditionalConditionalConditional
QMFEOTEILOTEILPart of ObjectCHAR4ConditionalConditionalConditionalConditionalConditional
QMFEOTVERQVERSNRVersion NumberCHAR6ConditionalConditionalConditionalConditionalConditional
QMFEBAUTLBAUTLAssemblyCHAR18ConditionalConditionalConditionalConditionalConditional
QMFEINDTXINDLTXObject Long Text AvailableCHAR1ConditionalConditionalConditionalConditionalConditional
QMFEKZMLAKZMLAPrimary language indicator for text segmentCHAR1ConditionalConditionalConditionalConditionalConditional
QMFEERZEITERZEITTime, at Which Record Was AddedTIMS6ConditionalConditionalConditionalConditionalConditional
QMFEAEZEITAEZEITTime of ChangeTIMS6ConditionalConditionalConditionalConditionalConditional
QMFEANZFEHLERQANZFEHL4Number of Defects FoundINT410ConditionalConditionalConditionalConditionalConditional
QMFEAUTKZQAUTKZData Record Created with Function 'Create with Copy Model'CHAR1ConditionalConditionalConditionalConditionalConditional

Note: Each Notification Header can have many Notification Items

 5.Notification Item Long Text Header

TableFieldData ElementField DescriptionData TypeLengthRequirement (Notif. Type Y1)Requirement (Notif. Type Y2)Requirement (Notif. Type Y3)Requirement (Notif. Type Y4)Requirement (Notif. Type Y5)
STXHTDOBJECTTDOBJECTTexts: application objectCHAR10MandatoryMandatoryMandatoryMandatoryMandatory
STXHTDNAMETDOBNAMENameCHAR70MandatoryMandatoryMandatoryMandatoryMandatory
STXH

TDID

TDID

Text IDCHAR4MandatoryMandatoryMandatoryMandatoryMandatory
STXHTDSPRASSPRASLanguage KeyLANG1MandatoryMandatoryMandatoryMandatoryMandatory

6.Notification Item Long Text Line

TableFieldData ElementField DescriptionData TypeLengthRequirement (Notif. Type Y1)Requirement (Notif. Type Y2)Requirement (Notif. Type Y3)Requirement (Notif. Type Y4)Requirement (Notif. Type Y5)
STXLTDOBJECTTDOBJECTTexts: application objectCHAR10MandatoryMandatoryMandatoryMandatoryMandatory
STXLTDNAMETDOBNAMENameCHAR70MandatoryMandatoryMandatoryMandatoryMandatory
STXL

TDID

TDID

Text IDCHAR4MandatoryMandatoryMandatoryMandatoryMandatory
STXLTDSPRASSPRASLanguage KeyLANG1MandatoryMandatoryMandatoryMandatoryMandatory
STXLCLUSTD_TAGTDFORMAT

Tag column

CHAR1

Mandatory

MandatoryMandatoryMandatoryMandatory
STXLROWCOUNTROWCOUNT

Row number

NUMC10MandatoryMandatoryMandatoryMandatoryMandatory
STXLTXLINETDLINE

Text Line

CHAR72MandatoryMandatoryMandatoryMandatoryMandatory

 7. Notification - Causes

TableFieldData ElementField DescriptionData TypeLengthRequirement (Notif. Type Y1)Requirement (Notif. Type Y2)Requirement (Notif. Type Y3)Requirement (Notif. Type Y4)Requirement (Notif. Type Y5)
QMELQMNUMQMNUMNotification NumberCHAR12MandatoryMandatoryMandatoryMandatoryMandatory
QMURFENUMFELFDItem Number in Item RecordNUMC4MandatoryMandatoryMandatoryMandatoryMandatory
QMURURNUMURNUMSequential Number for CauseNUMC4MandatoryMandatoryMandatoryMandatoryMandatory
QMURERNAMERNAMName of Person who Created the ObjectCHAR12ConditionalConditionalConditionalConditionalConditional
QMURERDATERDATDate on Which Record Was CreatedDATS8ConditionalConditionalConditionalConditionalConditional
QMURAENAMAENAMName of Person Who Changed ObjectCHAR12ConditionalConditionalConditionalConditionalConditional
QMURAEDATAEDATChanged OnDATS8ConditionalConditionalConditionalConditionalConditional
QMUR

URTXT

URSTX

Cause Text

CHAR40ConditionalConditionalConditionalConditionalConditional
QMURURKATURKATCatalog Type - CausesCHAR1ConditionalConditionalConditionalConditionalConditional
QMUR

URGRP

URGRP

Code Group - Causes

CHAR8ConditionalConditionalConditionalConditionalConditional
QMUR

URCOD

URCOD

Cause Code

CHAR4ConditionalConditionalConditionalConditionalConditional
QMURURVERQVERSNRVersion NumberCHAR6ConditionalConditionalConditionalConditionalConditional

INDTXINDLTXObject Long Text AvailableCHAR1ConditionalConditionalConditionalConditionalConditional
QMURKZMLAKZMLAPrimary language indicator for text segmentCHAR1ConditionalConditionalConditionalConditionalConditional
QMURERZEITERZEITTime, at Which Record Was AddedTIMS6ConditionalConditionalConditionalConditionalConditional
QMURAEZEITAEZEITTime of ChangeTIMS6ConditionalConditionalConditionalConditionalConditional
QMURQURNUMQURNUMSort Number for CauseNUMC4ConditionalConditionalConditionalConditionalConditional
QMURAUTKZQAUTKZData Record Created with Function 'Create with Copy Model'CHAR1ConditionalConditionalConditionalConditionalConditional

 8. Notification - Task

TableFieldData ElementField DescriptionData TypeLengthRequirement (Notif. Type Y1)Requirement (Notif. Type Y2)Requirement (Notif. Type Y3)Requirement (Notif. Type Y4)Requirement (Notif. Type Y5)
QMELQMNUMQMNUMNotification NumberCHAR12Mandatory MandatoryMandatoryMandatoryMandatory
QMSMMANUMMANUMSequential Task NumberNUMC4ConditionalConditionalConditionalConditionalNot used
QMSMMNKATMAKATCatalog Type - TasksCHAR1ConditionalConditionalConditionalConditionalNot used
QMSMMNGRPMAGRPCode Group - TasksCHAR8ConditionalConditionalConditionalConditionalNot used
QMSMMNCODMNCODTask CodeCHAR4ConditionalConditionalConditionalConditionalNot used
QMSMMNVERQVERSNRVersion NumberCHAR6ConditionalConditionalConditionalConditionalNot used
QMSMFOLGEACTQMFOLACTFollow-Up Action for TaskCHAR8ConditionalConditionalConditionalConditionalNot used
QMSMFOLACTPROTQMFOAPROTLog for Follow-Up ActionCHAR1ConditionalConditionalConditionalConditionalNot used
QMSMMATXTMATXTShort Text for TaskCHAR40ConditionalConditionalConditionalConditionalNot used
QMSMERNAMERNAMName of Person who Created the ObjectCHAR12ConditionalConditionalConditionalConditionalNot used
QMSMERDATERDATDate on Which Record Was CreatedDATS8ConditionalConditionalConditionalConditionalNot used
QMSMAENAMAENAMName of Person Who Changed ObjectCHAR12ConditionalConditionalConditionalConditionalNot used
QMSMAEDATAEDATChanged OnDATS8ConditionalConditionalConditionalConditionalNot used
QMSMPSTERPSTERPlanned Start DateDATS8ConditionalConditionalConditionalConditionalNot used
QMSMPETERPETERPlanned finish dateDATS8ConditionalConditionalConditionalConditionalNot used
QMSMOBJNRQMOBJNRObject Number for Status ManagementCHAR22ConditionalConditionalConditionalConditionalNot used
QMSMINDTXINDLTXObject Long Text AvailableCHAR1ConditionalConditionalConditionalConditionalNot used
QMSMKZMLAKZMLAPrimary language indicator for text segmentCHAR1ConditionalConditionalConditionalConditionalNot used
QMSMPSTURPSTURPlanned Start Time for TaskTIMS6ConditionalConditionalConditionalConditionalNot used
QMSMPETURPETURPlanned Finish Time for TaskTIMS6ConditionalConditionalConditionalConditionalNot used
QMSMERLNAMQMSMERLNAMPerson Who Completed the TaskCHAR12ConditionalConditionalConditionalConditionalNot used
QMSMERLDATQMSMERLDATDate on Which the Task Was CompletedDATS8ConditionalConditionalConditionalConditionalNot used
QMSMERLZEITQMSMERLTIMTime at Which Task Was CompletedTIMS6ConditionalConditionalConditionalConditionalNot used
QMSMWDVDATQMSMWDVDATDate on Which Task Was ResubmittedDATS8ConditionalConditionalConditionalConditionalNot used
QMSMFENUMFELFDItem Number in Item RecordNUMC4ConditionalConditionalConditionalConditionalNot used
QMSMURNUMURNUMSequential Number for CauseNUMC4ConditionalConditionalConditionalConditionalNot used
QMSMERZEITERZEITTime, at Which Record Was AddedTIMS6ConditionalConditionalConditionalConditionalNot used
QMSMAEZEITAEZEITTime of ChangeTIMS6ConditionalConditionalConditionalConditionalNot used
QMSMPARVWQMSM_PARVWFunction of Person Responsible for TaskCHAR2ConditionalConditionalConditionalConditionalNot used
QMSMPARNRQMSM_PARNRPerson Responsible for Task (Partner Number)CHAR12ConditionalConditionalConditionalConditionalNot used
QMSMQSMNUMQSMNUMSort Number for TaskNUMC4ConditionalConditionalConditionalConditionalNot used
QMSMAUTKZQAUTKZData Record Created with Function 'Create with Copy Model'CHAR1ConditionalConditionalConditionalConditionalNot used
QMSMKZACTIONBOXQNKZACTIONBOXCreated Using Action BoxCHAR1ConditionalConditionalConditionalConditionalConditional

FUNKTIONQNFUNKTIONKeys for Function in Action BoxCHAR4ConditionalConditionalConditionalConditionalConditional

 9. Notification - Activity

TableFieldData ElementField DescriptionData TypeLengthRequirement (Notif. Type Y1)Requirement (Notif. Type Y2)Requirement (Notif. Type Y3)Requirement (Notif. Type Y4)Requirement (Notif. Type Y5)
QMELQMNUMQMNUMNotification NumberCHAR12Mandatory MandatoryMandatoryMandatoryMandatory
QMMAMANUMAKNUMConsecutive Number of ActivityNUMC4ConditionalConditionalConditionalConditionalConditional
QMMAFENUMFELFDItem Number in Item RecordNUMC4ConditionalConditionalConditionalConditionalConditional
QMMAURNUMURNUMSequential Number for CauseNUMC4ConditionalConditionalConditionalConditionalConditional
QMMAMNKATMFKATCatalog Type - ActivitiesCHAR1ConditionalConditionalConditionalConditionalConditional
QMMAMNGRPMFGRPCode Group - ActivitiesCHAR8ConditionalConditionalConditionalConditionalConditional
QMMAMNCODMFCODActivity CodeCHAR4ConditionalConditionalConditionalConditionalConditional
QMMAMNVERQVERSNRVersion NumberCHAR6ConditionalConditionalConditionalConditionalConditional
QMMAMATXTMFTEXTActivity TextCHAR40ConditionalConditionalConditionalConditionalConditional
QMMAERNAMERNAMName of Person who Created the ObjectCHAR12ConditionalConditionalConditionalConditionalConditional
QMMAERDATERDATDate on Which Record Was CreatedDATS8ConditionalConditionalConditionalConditionalConditional
QMMAAENAMAENAMName of Person Who Changed ObjectCHAR12ConditionalConditionalConditionalConditionalConditional
QMMAAEDATAEDATChanged OnDATS8ConditionalConditionalConditionalConditionalConditional
QMMAMAKLSMAKLSTask ClassCHAR18ConditionalConditionalConditionalConditionalConditional
QMMAKLAKZKLAKZIndicator: Classification existsCHAR1ConditionalConditionalConditionalConditionalConditional
QMMAPSTERPSTERMAStart DateDATS8ConditionalConditionalConditionalConditionalConditional
QMMAPETERPETERMAEnd DateDATS8ConditionalConditionalConditionalConditionalConditional
QMMAINDTXINDLTXObject Long Text AvailableCHAR1ConditionalConditionalConditionalConditionalConditional
QMMAKZMLAKZMLAPrimary language indicator for text segmentCHAR1ConditionalConditionalConditionalConditionalConditional
QMMAPSTURPSTURMAStart Time of ActivityTIMS6ConditionalConditionalConditionalConditionalConditional
QMMAPETURPETURMAEnd Time of ActivityTIMS6ConditionalConditionalConditionalConditionalConditional
QMMAERZEITERZEITTime, at Which Record Was AddedTIMS6ConditionalConditionalConditionalConditionalConditional
QMMAAEZEITAEZEITTime of ChangeTIMS6ConditionalConditionalConditionalConditionalConditional
QMMAQMANUMQMANUMSort Number for ActivityNUMC4ConditionalConditionalConditionalConditionalConditional
QMMAAUTKZQAUTKZData Record Created with Function 'Create with Copy Model'CHAR1ConditionalConditionalConditionalConditionalConditional
QMMAKZACTIONBOXQNKZACTIONBOXCreated Using Action BoxCHAR1ConditionalConditionalConditionalConditionalConditional
QMMAFUNKTIONQNFUNKTIONKeys for Function in Action BoxCHAR4ConditionalConditionalConditionalConditionalConditional



Data Cleansing

IDCriticalityError Message/Report DescriptionRuleOutputSource System

9004-001


C1 

Notification with assigned Functional Location which is not Relevant (as per Relevancy Criteria)

Notification as per Relevancy Criteria assigned with an Equipment / Functional which does not belong below:

  1. Functional Location as per Relevancy Criteria

Notification Number, Short Text, Plant for Work Centre, Functional Location

PF2, WP2

9004-002

C1 

Notification with assigned Equipment which is not Relevant (as per Relevancy Criteria)

Notification as per Relevancy Criteria assigned with an Equipment / Functional which does not belong below:

  1. Equipment as per Relevancy Criteria

Notification Number, Short Text, Plant for Work Centre, Equipment

 PF2, WP2

9004-003

C1

Catalog Code Groups: Invalid or Inactive Catalog Code Groups & Code linked to Notification

Notification as per Relevancy Criteria assigned with a Catalog Code Groups & Code does not belong below:
1. Catalog Code Groups & Code as per Relevancy Criteria

Notification Number, Short Text, Plant for Work Centre, Catalog Code Groups & Code

PF2, WP2

9004-004

C1

Maintenance Item: Invalid or Inactive Maintenance Item linked to Notification

Notification as per Relevancy Criteria assigned with a Maintenance Plan and Item does not belong below:
1. Maintenance Plan and Item as per Relevancy Criteria

Notification Number, Short Text, Plant for Work Centre, Maintenance Item

PF2, WP2

9004-005


C1

Revision: Invalid or Inactive Revision linked to Notification 

Notification as per Relevancy Criteria assigned with a Revision does not belong below:
1. Revision as per Relevancy Criteria 

Notification Number, Short Text, Plant for Work Centre, Revision

PF2, WP2

9004-006

C1


Work Centre: Invalid or Inactive Work Centre linked to Notification

Notification as per Relevancy Criteria assigned with a Work Centre does not belong below:
1. Work Centre as per Relevancy Criteria

Notification Number, Short Text, Plant for Work Centre, Work Centre 

PF2, WP2


9004-007

C2

Notification Creation Date: 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)

Notification Number, Short Text, Plant for Work Centre, Notification Creation Date

PF2, WP2

9004-008

C1

Plant: Notification Plant incorrectNotification as per Relevancy Criteria with Invalid Plant (T001W)Notification Number, Short Text, Plant for Work Centre

PF2, WP2

9004-009

C1 

Planner Group: Invalid or no Planner Group linked to Notification

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-010

C2

Description: Notification contains Thai characters

Notification Description with Thai characters

Notification Number, Short Text, Plant for Work Centre

PF2, WP2

9004-011

C1

Notification with assembly only

Notification with assembly without Functional Location / Equipment

Notification Number, Short Text, Plant for Work Centre, Assembly

PF2, WP2

9004-012

C1

Notification for non asset level in legacy system

Notification assigned to non asset level Functional Location

Notification Number, Short Text, Plant for Work Centre, Functional Location

PF2, WP2

9004-013  

C2

Notification Short Text contain informal word

Notification Short Text contain informal word

Notification Number, Short Text, Plant for Work Centre

PF2, WP2

Note: List of Cleansing is maintained here: Conversion Specs Register (DCT & Cleansing Report)

Informal Words **

Group 1

Group 2

Group 3

Group 4

Group 5

*DNU

Delete

donot

Formerly

Old #

..

Deletion

DONT USE

From

Old[ ]

/

DELISTED

DON'T USE

Incorrect

PLEASE USE

?

Discontinued

Dup Use

Invalid

Pls Use

@

Disposable

DUPLICATE

New

Previously

^

DNU

-DUPLICATE

NOT ACTIVE

Replace

+

Do Not

DUPLICATION

not in use

Replaced

++

Do Not Re

Duplicidad

Not Used

RESERVED

£

Do Not Sell

Duplikat

NOT VALID

Retired

Defective

Do Not Use

Former

Obsolete

ZZDEL


Conversion Process

The high-level process is represented by the diagram below:

For sites that are not on SAP-PF2 and WP2 systems, collection will be done manually in the data collection template.


Data Privacy and Sensitivity


Extraction

Extract data from a source into . There are 2 possibilities:

  1. The data exists. connects to the source and loads the data into . 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  cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
  2. The data does not exist (or cannot be converted from its current state). The data is manually collected by the business directly in . This is to be conducted using DCT (Data Collection Template) in

The agreed Relevancy criteria is applied to the extracted records to identify the records that are applicable for the Target loads

Extraction Run Sheet

Req #Requirement DescriptionTeam Responsible
1Extract data from source system based on relevancy ruleSyWay Data Team


Selection Screen

Selection Ref ScreenParameter NameSelection TypeRequirementValue to be entered/set
Not Applicable




Data Collection Template (DCT)

No DCT will be used for Notification.

Notification DCT Rules

Field NameField DescriptionRule

Not applicable



 Extraction Dependencies

Item #Step DescriptionTeam Responsible
1Relevancy Criteria for Catalog Profile

SyWay A2D Data Team

2Relevancy Criteria for Catalog Code Groups & Codes

SyWay A2D Data Team

3Relevancy Criteria for Characteristics

SyWay A2D Data Team

4Relevancy Criteria for Class

SyWay A2D Data Team

5Relevancy Criteria for Construction Type

SyWay A2D Data Team

6Relevancy Criteria for Equipment

SyWay A2D Data Team

7Relevancy Criteria for Functional Location

SyWay A2D Data Team

8Relevancy Criteria for Maintenance Plan and Item

SyWay A2D Data Team

9Relevancy Criteria for Revision

SyWay A2D Data Team

10Relevancy Criteria for Task List

SyWay A2D Data Team

11Relevancy Criteria for Work Centre

SyWay A2D Data Team


Transformation

The Target fields are mapped to the applicable Legacy field that will be its source, this is a 3-way activity involving the Business, Functional team and Data team.  This identifies the transformation activity required to allow to make the data Target ready:

  1. Perform value mapping and data transformation rules. 
    1. Legacy values are mapped to the to-be values (this could include a default value)
    2. Values are transformed according to the rules defined in Advanced Data Migration and Management (ADMM)
  2. 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 DescriptionTeam Responsible
1

Obtain DCT Sign-off from Business.

SyWay Data Team

2

In dspMigrate, select the wave – S4/HANA – Plant Maintenance

Syniti

3

Go to Process Area Launch and Process the Object – Notification

Syniti

4

Review and Validate Error and Preload Reports

Syniti

5

Execute the transformation to prepare the target tables

Syniti

6

Validate data from pre-load and error reports

Business/Data owner

7

Generate load files

Syniti


Transformation Rules

1.Notification Header Transformation Rule

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1

PF2, WP2 

QMEL

QMNUM

Notification Number

S/4 HANA

QMEL

QMNUM

Notification Number

System (Internal numbering).

2

PF2, WP2 

QMEL

AUFNR

Order Number

S/4 HANA

QMEL

AUFNR

Order Number

Value Mapping: Work Order

3PF2, WP2QMELQMARTNotification TypeS/4 HANAQMELQMARTNotification TypeValue Mapping: Notification Type
4PF2, WP2QMELQMTXTShort TextS/4 HANAQMELQMTXTShort TextDirect Mapping.
Only if notification does not exist for PM01 Work Order, default to: Work Order Description
5PF2, WP2QMELEQUNREquipment NumberS/4 HANAQMELEQUNREquipment Number

If not blank then Value Mapping: Equipment Number

If blank or cannot be mapped, and if linked to Work Order, then use Work Order value.

6PF2, WP2QMELTPLNRFunctional LocationS/4 HANAIFLOTPLNRFunctional Location Label

Default to blank if Equipment is not blank.

If not blank then Value Mapping: Functional Location.

If blank or cannot be mapped, and if linked to Work Order, then use Work Order value.

7PF2, WP2QMIHINGRPPlanner GroupS/4 HANAVIQMLINGRPPlanner Group

Value Mapping: Planner Group

If blank or cannot be mapped, and if linked to Work Order, then use Work Order value.

8PF2, WP2CRHDARBPLWork CentreS/4 HANACRHDARBPLWork Centre

Value Mapping: Work Centre

9PF2, WP2CRHDWERKSWork Centre plantS/4 HANACRHDWERKSWork Centre plant

Value Mapping: Plant (Maintenance Plant = Yes)

10PF2, WP2QMELQMDATNotification DateS/4 HANAQMELQMDATNotification DateDirect Mapping.
If notification does not exist for PM01 Work Order, default to: Work Order Basic Start Date
11PF2, WP2QMELMZEITNotification TimeS/4 HANAQMELMZEITNotification TimeDirect Mapping.
Only if notification does not exist for PM01 Work Order, default to: 00:00:00
12PF2, WP2QMELERNAMReported ByS/4 HANAQMELERNAMReported ByDirect Mapping.
Only if notification does not exist for PM01 Work Order, default to: Migration User ID (Name)
13PF2, WP2QMELSTRMNRequired Start DateS/4 HANAQMELSTRMNRequired Start DateIf STRMN is blank, and if linked to Work Order, then use Work Order value for both start and end date
If End Date is earlier than Start Date, then default both Start and End Date from Work Order.
If Start Date is before 2 years prior to go live date, then default both Start and End Date from Work Order.
14PF2, WP2QMELLTRMNRequired End DateS/4 HANAQMELLTRMNRequired End DateIf LTRMN is blank, and if linked to Work Order, then use Work Order value for both start and end date
If End Date is earlier than Start Date, then default both Start and End Date from Work Order
If End Date is before 2 years prior to go live date, then default both Start and End Date from Work Order.
If LTRMN is blank and not linked to Work Order, copy Start Date into End Date.
Validation Rule: End Date cannot be earlier than start date
15PF2, WP2QMELPRIOKPriorityS/4 HANAQMELPRIOKPriority

Value Mapping: Priority

Only if notification does not exist for PM01 Work Order, default to: Low

16PF2, WP2QMELQMGRPCode GroupS/4 HANAQMELQMGRPCode GroupDirect Mapping.
17PF2, WP2QMELQMCODCodingS/4 HANAQMELQMCODCodingDirect Mapping.
18PF2, WP2QMELRBNRCatalog ProfileS/4 HANAQMELRBNRCatalog ProfileDerive from Functional Location
19----


Issue PermitIf Notification is assigned to Work Order then default to “X”.
20PF2, WP2QMIHILARTMaintenance Activity TypeS/4 HANAQMIHILARTMaintenance Activity TypeDerive from AFIH-ILART
21PF2, WP2

QMIH

MSAUSBreakdown IndicatorS/4 HANA

QMIH

MSAUSBreakdown IndicatorDirect Mapping.
22PF2, WP2

QMIH

AUSVNMalfunct. Start DateS/4 HANA

QMIH

AUSVNMalfunct. Start DateDirect Mapping.
23PF2, WP2

QMIH

AUZTVMalfunct. Start TimeS/4 HANA

QMIH

AUZTVMalfunct. Start TimeDirect Mapping.
24PF2, WP2

QMIH

AUSBSMalfunct. End DateS/4 HANA

QMIH

AUSBSMalfunct. End DateDirect Mapping.
25PF2, WP2

QMIH

AUZTBMalfunct. End TimeS/4 HANA

QMIH

AUZTBMalfunct. End TimeDirect Mapping.
26PF2, WP2

QMIH

AUSZTBreakdown DurationS/4 HANA

QMIH

AUSZTBreakdown DurationDirect Mapping.
27PF2, WP2

QMIH

MAUEHBreakdown UnitS/4 HANA

QMIH

MAUEHBreakdown UnitDirect Mapping.

 2.Notification Header Long Text Header Transformation Rule

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1----S/4HANA STXHTDOBJECTTexts: application objectDefault to "QMEL"
2PF2, WP2 

QMEL

QMNUM

Notification NumberS/4HANA STXHTDNAMEName

Value Mapping: Notification

3
---S/4HANA STXH

TDID

Text IDDefault to 'LTXT'
4PF2, WP2STXHSPRASLanguage KeyS/4HANA STXHSPRASLanguage KeyDirect Mapping

 3.Notification Header Long Text Line Transformation Rule 

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1----S/4HANA STXLTDOBJECTTexts: application objectDefault to "QMEL"
2PF2, WP2 

QMEL

QMNUM

Notification NumberS/4HANA STXLTDNAMEName

Value Mapping: Notification

3----S/4HANA STXL

TDID

Text IDDefault to 'LTXT'
4PF2, WP2STXLSPRASLanguage KeyS/4HANA STXLSPRASLanguage KeyDirect Mapping
5----S/4HANA STXLCLUSTD_TAGTag columnDefault to "*"
6PF2, WP2STXLROWCOUNT

Row number

S/4HANA STXLROWCOUNT

Row number

Direct Mapping
7PF2, WP2STXLTXLINEText LineS/4HANA STXLTXLINEText LineDirect Mapping

 4.Notification Item Transformation Rule 

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1

PF2, WP2 

QMFE

QMNUM

Notification Number

S/4 HANA

QMEL

QMNUM

Notification Number

System (Internal numbering).

2PF2, WP2QMFEIWERKMaintenance Planning PlantS/4 HANAVIQMLWERKMaintenance Planning PlantDefault to Planning Plant from reference technical object.
3PF2, WP2QMFEARBPLObject ID for Work CentreS/4 HANAQMFEARBPLObject ID for Work Centre

Value Mapping: Work Centre

If blank or cannot be mapped:

  1. If linked to Work Order, then use Work Order value
  2. If not linked to Work Order, then derive the Main Work Centre from the first 4 character of the mapped work Centre
  3. Otherwise, then default to technical object Work Centre.
4

PF2, WP2 

QMFE

OTGRP

Code Group - Object Parts

S/4 HANA

QMFE

OTGRP

Code Group - Object Parts

Value Mapping: Catalog Code Group and Code

5PF2, WP2QMFE

OTEIL

Part of Object

S/4 HANAQMFE

OTEIL

Part of Object

Value Mapping: Catalog Code Group and Code

6PF2, WP2QMFE

FEGRP

Damage – Code Group

S/4 HANAQMFE

FEGRP

Damage – Code Group

Value Mapping: Catalog Code Group and Code

7

PF2, WP2 

QMFE

FECOD

Problem or Damage Code

S/4 HANA

QMFE

FECOD

Problem or Damage Code

Direct Mapping

8PF2, WP2QMFE

FETXT

Notification Item Short Text

S/4 HANAQMFE

FETXT

Notification Item Short Text

Direct Mapping

Note: Each Notification Header can have many Notification Items

 5.Notification Item Long Text Header Transformation Rule

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1----S/4HANA STXHTDOBJECTTexts: application objectDefault to "QMFE"
2PF2, WP2 

QMEL

QMNUM

Notification NumberS/4HANA STXHTDNAMEName

Value Mapping: Notification

3----S/4HANA STXH

TDID

Text IDDefault to 'LTXT'
4PF2, WP2STXHSPRASLanguage KeyS/4HANA STXHSPRASLanguage KeyDirect Mapping
5----S/4HANA STXHCLUSTD_TAGTag columnDefault to "*"
6PF2, WP2STXHROWCOUNT

Row number

S/4HANA STXHROWCOUNT

Row number

Direct Mapping
7PF2, WP2STXHTXLINEText LineS/4HANA STXHTXLINEText LineDirect Mapping

 6.Notification Item Long Text Line Transformation Rule

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1----S/4HANA STXLTDOBJECTTexts: application objectDefault to "QMFE"
2PF2, WP2 

QMEL

QMNUM

Notification NumberS/4HANA STXLTDNAMEName

Value Mapping: Notification

3----S/4HANA STXL

TDID

Text IDDefault to 'LTXT'
4PF2, WP2STXLSPRASLanguage KeyS/4HANA STXLSPRASLanguage KeyDirect Mapping
5----S/4HANA STXLCLUSTD_TAGTag columnDefault to "*"
6PF2, WP2STXLROWCOUNT

Row number

S/4HANA STXLROWCOUNT

Row number

Direct Mapping
7PF2, WP2STXLTXLINEText LineS/4HANA STXLTXLINEText LineDirect Mapping

 7. Notification - Causes Transformation Rule

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1

PF2, WP2 

QMUR

QMNUM

Notification Number

S/4 HANA

QMUR

QMNUM

Notification Number

System (Internal numbering)

2PF2, WP2 QMURQMNUMNotification NumberS/4HANA QMURQMNUMNotification NumberSystem (Internal numbering)
3

PF2, WP2 

QMURFENUMItem Number in Item RecordS/4HANA QMURFENUMItem Number in Item RecordSystem (Internal numbering)
4PF2, WP2 QMURURNUMSequential Number for CauseS/4HANA QMURURNUMSequential Number for CauseSystem (Internal numbering)
5

PF2, WP2 

QMURERNAMName of Person who Created the ObjectS/4HANA QMURERNAMName of Person who Created the ObjectDirect Mapping
6PF2, WP2 QMURERDATDate on Which Record Was CreatedS/4HANA QMURERDATDate on Which Record Was CreatedDirect Mapping
7

PF2, WP2 

QMURAENAMName of Person Who Changed ObjectS/4HANA QMURAENAMName of Person Who Changed ObjectDirect Mapping
8PF2, WP2 QMURAEDATChanged OnS/4HANA QMURAEDATChanged OnDirect Mapping
9

PF2, WP2 

QMUR

URTXT

Cause Text

S/4HANA QMUR

URTXT

Cause Text

Direct Mapping
10PF2, WP2 QMURURKATCatalog Type - CausesS/4HANA QMURURKATCatalog Type - CausesValue Mapping: Catalog Code Group and Code
11

PF2, WP2 

QMUR

URGRP

Code Group - Causes

S/4HANA QMUR

URGRP

Code Group - Causes

Value Mapping: Catalog Code Group and Code
12PF2, WP2 QMUR

URCOD

Cause Code

S/4HANA QMUR

URCOD

Cause Code

Value Mapping: Catalog Code Group and Code
13

PF2, WP2 

QMURURVERVersion NumberS/4HANA QMURURVERVersion NumberDirect Mapping
14PF2, WP2 QMURINDTXObject Long Text AvailableS/4HANA QMURINDTXObject Long Text AvailableDirect Mapping
15

PF2, WP2 

QMURKZMLAPrimary language indicator for text segmentS/4HANA QMURKZMLAPrimary language indicator for text segmentDirect Mapping
16

PF2, WP2 

QMURERZEITTime, at Which Record Was AddedS/4HANA QMURERZEITTime, at Which Record Was AddedDirect Mapping
17PF2, WP2 QMURAEZEITTime of ChangeS/4HANA QMURAEZEITTime of ChangeDirect Mapping
18

PF2, WP2 

QMURQURNUMSort Number for CauseS/4HANA QMURQURNUMSort Number for CauseDirect Mapping
19PF2, WP2 QMURAUTKZData Record Created with Function 'Create with Copy Model'S/4HANA QMURAUTKZData Record Created with Function 'Create with Copy Model'Direct Mapping

 8. Notification - Task Transformation Rule

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1

PF2, WP2 

QMSMQMNUMNotification NumberS/4HANAQMSMQMNUMNotification NumberSystem (Internal numbering)
2

PF2, WP2 

QMSMMANUMSequential Task NumberS/4HANA QMSMMANUMSequential Task NumberSystem (Internal numbering)
3PF2, WP2 QMSMMNKATCatalog Type - TasksS/4HANA QMSMMNKATCatalog Type - TasksDirect Mapping
4

PF2, WP2 

QMSMMNGRPCode Group - TasksS/4HANA QMSMMNGRPCode Group - TasksDirect Mapping
5PF2, WP2 QMSMMNCODTask CodeS/4HANA QMSMMNCODTask CodeDirect Mapping
6

PF2, WP2 

QMSMMNVERVersion NumberS/4HANA QMSMMNVERVersion NumberDirect Mapping
7

PF2, WP2 

QMSMFOLGEACTFollow-Up Action for TaskS/4HANA QMSMFOLGEACTFollow-Up Action for TaskDirect Mapping
8PF2, WP2 QMSMFOLACTPROTLog for Follow-Up ActionS/4HANA QMSMFOLACTPROTLog for Follow-Up ActionDirect Mapping
9

PF2, WP2 

QMSMMATXTShort Text for TaskS/4HANA QMSMMATXTShort Text for TaskDirect Mapping
10PF2, WP2 QMSMERNAMName of Person who Created the ObjectS/4HANA QMSMERNAMName of Person who Created the ObjectDirect Mapping
11

PF2, WP2 

QMSMERDATDate on Which Record Was CreatedS/4HANA QMSMERDATDate on Which Record Was CreatedDirect Mapping
12

PF2, WP2 

QMSMAENAMName of Person Who Changed ObjectS/4HANA QMSMAENAMName of Person Who Changed ObjectDirect Mapping
13PF2, WP2 QMSMAEDATChanged OnS/4HANA QMSMAEDATChanged OnDirect Mapping
14

PF2, WP2 

QMSMPSTERPlanned Start DateS/4HANA QMSMPSTERPlanned Start DateDirect Mapping
15PF2, WP2 QMSMPETERPlanned finish dateS/4HANA QMSMPETERPlanned finish dateDirect Mapping
16

PF2, WP2 

QMSMOBJNRObject Number for Status ManagementS/4HANA QMSMOBJNRObject Number for Status ManagementDirect Mapping
17

PF2, WP2 

QMSMINDTXObject Long Text AvailableS/4HANA QMSMINDTXObject Long Text AvailableDirect Mapping
18PF2, WP2 QMSMKZMLAPrimary language indicator for text segmentS/4HANA QMSMKZMLAPrimary language indicator for text segmentDirect Mapping
19

PF2, WP2 

QMSMPSTURPlanned Start Time for TaskS/4HANA QMSMPSTURPlanned Start Time for TaskDirect Mapping
20PF2, WP2 QMSMPETURPlanned Finish Time for TaskS/4HANA QMSMPETURPlanned Finish Time for TaskDirect Mapping
21

PF2, WP2 

QMSMERLNAMPerson Who Completed the TaskS/4HANA QMSMERLNAMPerson Who Completed the TaskDirect Mapping
22

PF2, WP2 

QMSMERLDATDate on Which the Task Was CompletedS/4HANA QMSMERLDATDate on Which the Task Was CompletedDirect Mapping
23PF2, WP2 QMSMERLZEITTime at Which Task Was CompletedS/4HANA QMSMERLZEITTime at Which Task Was CompletedDirect Mapping
24

PF2, WP2 

QMSMWDVDATDate on Which Task Was ResubmittedS/4HANA QMSMWDVDATDate on Which Task Was ResubmittedDirect Mapping
25PF2, WP2 QMSMFENUMItem Number in Item RecordS/4HANA QMSMFENUMItem Number in Item RecordDirect Mapping
26

PF2, WP2 

QMSMURNUMSequential Number for CauseS/4HANA QMSMURNUMSequential Number for CauseDirect Mapping
27

PF2, WP2 

QMSMERZEITTime, at Which Record Was AddedS/4HANA QMSMERZEITTime, at Which Record Was AddedDirect Mapping
28PF2, WP2 QMSMAEZEITTime of ChangeS/4HANA QMSMAEZEITTime of ChangeDirect Mapping
29

PF2, WP2 

QMSMPARVWFunction of Person Responsible for TaskS/4HANA QMSMPARVWFunction of Person Responsible for TaskDirect Mapping
30

PF2, WP2 

QMSMPARNRPerson Responsible for Task (Partner Number)S/4HANA QMSMPARNRPerson Responsible for Task (Partner Number)Direct Mapping
31

PF2, WP2 

QMSMQSMNUMSort Number for TaskS/4HANA QMSMQSMNUMSort Number for TaskDirect Mapping
32PF2, WP2 QMSMAUTKZData Record Created with Function 'Create with Copy Model'S/4HANA QMSMAUTKZData Record Created with Function 'Create with Copy Model'Direct Mapping
33

PF2, WP2 

QMSMKZACTIONBOXCreated Using Action BoxS/4HANA QMSMKZACTIONBOXCreated Using Action BoxDirect Mapping
34PF2, WP2 QMSMFUNKTIONKeys for Function in Action BoxS/4HANA QMSMFUNKTIONKeys for Function in Action BoxDirect Mapping

 9. Notification - Activity Transformation Rule

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1

PF2, WP2 

QMMAQMNUMNotification NumberS/4HANA QMMAQMNUMNotification NumberSystem (Internal numbering)
2PF2, WP2 QMMAMANUMConsecutive Number of ActivityS/4HANA QMMAMANUMConsecutive Number of ActivitySystem (Internal numbering)
3

PF2, WP2 

QMMAFENUMItem Number in Item RecordS/4HANA QMMAFENUMItem Number in Item RecordDirect Mapping
4PF2, WP2 QMMAURNUMSequential Number for CauseS/4HANA QMMAURNUMSequential Number for CauseDirect Mapping
5

PF2, WP2 

QMMAMNKATCatalog Type - ActivitiesS/4HANA QMMAMNKATCatalog Type - ActivitiesDirect Mapping
6PF2, WP2 QMMAMNGRPCode Group - ActivitiesS/4HANA QMMAMNGRPCode Group - ActivitiesDirect Mapping
7

PF2, WP2 

QMMAMNCODActivity CodeS/4HANA QMMAMNCODActivity CodeDirect Mapping
8PF2, WP2 QMMAMNVERVersion NumberS/4HANA QMMAMNVERVersion NumberDirect Mapping
9

PF2, WP2 

QMMAMATXTActivity TextS/4HANA QMMAMATXTActivity TextDirect Mapping
10PF2, WP2 QMMAERNAMName of Person who Created the ObjectS/4HANA QMMAERNAMName of Person who Created the ObjectDirect Mapping
11

PF2, WP2 

QMMAERDATDate on Which Record Was CreatedS/4HANA QMMAERDATDate on Which Record Was CreatedDirect Mapping
12PF2, WP2 QMMAAENAMName of Person Who Changed ObjectS/4HANA QMMAAENAMName of Person Who Changed ObjectDirect Mapping
13

PF2, WP2 

QMMAAEDATChanged OnS/4HANA QMMAAEDATChanged OnDirect Mapping
14PF2, WP2 QMMAMAKLSTask ClassS/4HANA QMMAMAKLSTask ClassDirect Mapping
15

PF2, WP2 

QMMAKLAKZIndicator: Classification existsS/4HANA QMMAKLAKZIndicator: Classification existsDirect Mapping
16PF2, WP2 QMMAPSTERStart DateS/4HANA QMMAPSTERStart DateDirect Mapping
17

PF2, WP2 

QMMAPETEREnd DateS/4HANA QMMAPETEREnd DateDirect Mapping
18PF2, WP2 QMMAINDTXObject Long Text AvailableS/4HANA QMMAINDTXObject Long Text AvailableDirect Mapping
19

PF2, WP2 

QMMAKZMLAPrimary language indicator for text segmentS/4HANA QMMAKZMLAPrimary language indicator for text segmentDirect Mapping
20PF2, WP2 QMMAPSTURStart Time of ActivityS/4HANA QMMAPSTURStart Time of ActivityDirect Mapping
21

PF2, WP2 

QMMAPETUREnd Time of ActivityS/4HANA QMMAPETUREnd Time of ActivityDirect Mapping
22PF2, WP2 QMMAERZEITTime, at Which Record Was AddedS/4HANA QMMAERZEITTime, at Which Record Was AddedDirect Mapping
23

PF2, WP2 

QMMAAEZEITTime of ChangeS/4HANA QMMAAEZEITTime of ChangeDirect Mapping
24

PF2, WP2 

QMMAQMANUMSort Number for ActivityS/4HANA QMMAQMANUMSort Number for ActivityDirect Mapping
25PF2, WP2 QMMAAUTKZData Record Created with Function 'Create with Copy Model'S/4HANA QMMAAUTKZData Record Created with Function 'Create with Copy Model'Direct Mapping
26

PF2, WP2 

QMMAKZACTIONBOXCreated Using Action BoxS/4HANA QMMAKZACTIONBOXCreated Using Action BoxDirect Mapping
27PF2, WP2 QMMAFUNKTIONKeys for Function in Action BoxS/4HANA QMMAFUNKTIONKeys for Function in Action BoxDirect Mapping

List of Custom Target Reports for this object is maintained here: Conversion Specification - Custom Reports Register.

Transformation Mapping

Mapping Table NameMapping Table Description

Work Order

Old to new Work Order

Planner Group

Old to new Planner Group

Work Centre

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

Catalog Code Group and Code

Old to new Catalog Code Group and Code

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #Step DescriptionTeam Responsible
1

Ensure DCT tables completeness

SyWay Data Team

2

Ensure all Transformation mappings are up to date.

SyWay Data Team



Pre-Load Validation

Project Team

Completeness

TaskAction

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

TaskAction

Conversion Accuracy

SyWay A2D Data Team to verify that all fields below meet pass the checks:

  1. Mandatory Fields
  2. Field and Value Mapping Correctness
  3. Null Checks
  4. 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

TaskAction

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

TaskAction

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:

  1. Execute the automated data load into target system using load tool or product the load file if the load must be done manually
  2. Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation

Load Run Sheet

Item #Step DescriptionTeam 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

PostCutover

Configuration

Item #Configuration Item
1Notification Type
2Priority
3Maintenance Activity Type

Conversion Objects

Object #Preceding Object Conversion Approach

1002

Equipment

1003

Functional Location

1006

Work Centre

1010

Assembly

Error Handling

Error TypeError DescriptionAction Taken

Invalid Data

Invalid data (Based on master data)

Check whether the master data is available in the system

Invalid Data

Invalid data (Based on non master data)

Review and analyses the errors. Take necessary action to correct the data if possible.

Configuration

Invalid Notification Type

Engage Functional team to expedite and fix the error in the system


Post-Load Validation

Project Team

Completeness

TaskAction

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

TaskAction

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

TaskAction

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

TaskAction

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.


See also

Change log

Version Published Changed By Comment
CURRENT (v. 127) 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.

  • No labels