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

Compare with Current View Page History

« Previous Version 68 Next »

Status

  Approved

Owner
Stakeholders

Purpose

The purpose of this document is to define the conversion approach to create Notification in S/4 HANA.

Legacy Plant Maintenance Notification is using a diverse range of formats across the different systems. There are instances where the same Notification is duplicated within and across sources, with informal words. This results in data inconsistency. As per SyWay design, EAM Notification will be standardized.


Conversion Scope

The scope of this document covers the approach for converting active Notification from Legacy Source Systems into S/4HANA.

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 (Status: Outstanding; In Process)
2. Assigned to relevant Functional and Equipment
3. Notifications having Maintenance Plant in scope

The data from legacy system excludes:
1. Notification with NOCO status
2. Open Notifications with Closed Work Orders

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

Reference: SyWay_Cleansing and Historical Scope - A2D


List of source systems and approximate number of records
SourceScope

Source Approx No. of Records

Target SystemTarget Approx No. of Records

PF2, WP2

An initial extract will be provided to business to evaluate.

Additional data/records may be required and these will be constructed via DCT.

Enrichment of in-scope data may be required and will be added via transformation rules (business/technical).

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

Long text and DIR are not covered in this document as they are defined as another data object.

Legal Requirement

Not Applicable

Special Requirements

Not Applicable


Target Design

EAM Notification Data strictly adheres to the Master Data Standard. The complete information of the key fields that hold the Class information follows the Master Data Standard document that is located here <include hyperlink>.

The technical design of the target for this conversion approach.

1.Notification Header

TableFieldData ElementField DescriptionData TypeLengthRequirement
QMELQMNUMQMNUMNotification NumberCHAR12R
QMELQMARTQMARTNotification TypeCHAR2R
QMELQMTXTQMTXTShort TextCHAR40R
QMELARTPRARTPRPriority TypeCHAR2R
QMELPRIOKPRIOKPriorityCHAR1R
QMELERNAMERNAMName of Person who Created the ObjectCHAR12S
QMELERDATERDATDate on which the record was createdDATS8S
QMELAENAMAENAMName of person who changed objectCHAR12S
QMELAEDATAEDATDate of Last ChangeDATS8S
QMELMZEITMZEITTime of NotificationTIMS6S
QMELQMDATQMDATDate of NotificationDATS8R
QMELQMNAMQMNAMName of Person Reporting NotificationCHAR12S
QMELSTRMNSTRMNRequired start dateDATS8C
QMELSTRURSTRURRequired Start TimeTIMS6C
QMELLTRMNLTRMNRequired End DateDATS8C
QMELLTRURLTRURRequested End TimeTIMS6C
QMELWAERSWAERSCurrency KeyCUKY5NU
QMELAUFNRAUFNROrder NumberCHAR12C
QMELVERIDVERIDProduction VersionCHAR4NU
QMELRM_MATNRRM_MATNRMaterial number of the production versionCHAR40NU
QMELRM_WERKSRM_WERKSPlant of Production VersionCHAR4NU
QMELSA_AUFNRSA_AUFNRRun schedule header numberCHAR12NU
QMELMATNRMATNRMaterial NumberCHAR40C
QMELREVLVREVLVRevision levelCHAR2NU
QMELMATKLMATKLMaterial GroupCHAR9C
QMELPRDHAPRODH_DProduct hierarchyCHAR18C
QMELKZKRIKZKRIIndicator: Critical partCHAR1NU
QMELKZDKZKZDKZDocumentation required indicatorCHAR1C
QMELKUNUMQKUNUMAccount Number of CustomerCHAR10NU
QMELFEKNZFEKNZError Records ExistCHAR1C
QMELMAKNZMAKNZTask Records ExistCHAR1C
QMELOBJNRQMOBJNRObject Number for Status ManagementCHAR22R
QMELQMDABQMDABDate for Notification CompletionDATS8C
QMELQMZABQMZABCompletion Time of NotificationTIMS6C
QMELRBNRRBNRCatalog ProfileCHAR9R
QMELRBNRIRBNRIOrigin of Notifications Catalog ProfileCHAR1R
QMELINDTXINDLTXObject Long Text AvailableCHAR1C
QMELKZMLAKZMLAPrimary language indicator for text segmentCHAR1R
QMELHERKZHERKZOrigin of NotificationCHAR2R
QMELBEZDTBEZDTNotification Reference DateDATS8S
QMELBEZURBEZUR_DNotification Reference TimeTIMS6S
QMELLIFNUMLIFNUMSupplier Account NumberCHAR10C
QMELBUNAMEBUNAMEAuthor of a Q/PM NotificationCHAR12S
QMELVBELNKDAUFSales Order NumberCHAR10NU
QMELBSTNKBSTKDCustomer ReferenceCHAR35NU
QMELBSTDKBSTDKCustomer Reference DateDATS8NU
QMELSPARTSPARTDivisionCHAR2NU
QMELVKORGVKORGSales OrganizationCHAR4NU
QMELVTWEGVTWEGDistribution ChannelCHAR2NU
QMELADRNRCADNRAddresses: Address NumberCHAR10C
QMELAEZEITAEZEITTime of ChangeTIMS6S
QMELERZEITERZEITTime at Which Record Was AddedTIMS6S
QMELMAWERKQMAWERKSPlant for MaterialCHAR4C
QMELQMKATQMKATCatalog Type - CodingCHAR1C
QMELQMGRPQMGRPCode Group - CodingCHAR8C
QMELQMCODQMCODCodingCHAR4C
QMELAUSWIRKQSCENARIOKey for a ScenarioCHAR4NU
QMELTEILEVQTEILEVUsage of PartsCHAR4NU
QMELPRUEFLOSQPLOSInspection Lot NumberNUMC12NU
QMELCHARGCHARG_DBatch NumberCHAR10NU
QMELLGORTCHARGQLGORTCHARStorage Location of BatchCHAR4NU
QMELLICHNLICHNSupplier Batch NumberCHAR15NU
QMELHERSTELLERQLIFNRNumber of ManufacturerCHAR10NU
QMELEMATNREMATNMaterial number corresponding to manufacturer part numberCHAR40NU
QMELEKORGEKORGPurchasing organizationCHAR4C
QMELBKGRPBKGRPPurchasing GroupCHAR3C
QMELLGORTVORGQLGORTVORGStorage Location for Inspection Lot StockCHAR4NU
QMELFERTAUFNRFERTAUFNROrder Number (Production Order)CHAR12NU
QMELFERTAUFPLFERTAUFPLPlan Number for Operations in Order (Production Order)NUMC10NU
QMELEBELNEBELNPurchasing Document NumberCHAR10C
QMELEBELPQEBELPItem Number of Purchasing DocumentNUMC5NU
QMELMJAHRMJAHRMaterial Document YearNUMC4NU
QMELMBLNRMBLNRNumber of Material DocumentCHAR10NU
QMELMBLPOQMBLPOItem in Material DocumentNUMC4NU
QMELLS_KDAUFKDAUFSales Order NumberCHAR10NU
QMELLS_KDPOSPOSNRItem number of the SD documentNUMC6NU
QMELLS_VBELNVBELN_VLDeliveryCHAR10NU
QMELLS_POSNRQPOSNR_VLDelivery ItemNUMC6NU
QMELCROBJTYCR_OBJTYObject types of the CIM resourceCHAR2C
QMELARBPLLGWIDObject ID of the Work CenterNUMC8C
QMELARBPLWERKQARBPWERKSPlant for Work CenterCHAR4C
QMELFEARTQFEARTReport Type for Defects RecordingCHAR8NU
QMELPNLKNQLFNKNCurrent Node Number from Order CounterNUMC8NU
QMELMGEIGMGEIGDefective Quantity (Internal)QUAN13(3)NU
QMELMGFRDMGFRDDefective Quantity (External)QUAN13(3)NU
QMELMGEINMGEINUnit of MeasureUNIT3C
QMELBZMNGQBZMNGGeneral Reference QuantityQUAN13(3)NU
QMELRKMNGRKMNGComplaint QuantityQUAN13(3)NU
QMELRGMNGRGMNGReturn Delivery QuantityQUAN13(3)NU
QMELRKDATRKDATDate of Return DeliveryDATS8NU
QMELCOAUFNRCOAUFNROrder Number (QM Order)CHAR12NU
QMELQWRNUMQWRNUMReference Notification NumberCHAR12C
QMELREFNUMQMEXTNRExternal Reference NumberCHAR20NU
QMELKDMATMATNR_KUMaterial Number Used by CustomerCHAR35NU
QMELIDNLFIDNLFMaterial Number Used by SupplierCHAR35NU
QMELSERIALNRGERNRSerial NumberCHAR18NU
QMELKZLOESCHKZLOESCHDelete Data RecordCHAR1NU
QMELCVP_XBLCKCVP_XBLCKBusiness Purpose Completed FlagCHAR1
QMELPRODDATQPRODDATProduction DateDATS8NU
QMELDEVICEIDDEVICEIDAdditional Device DataCHAR40NU
QMELVKBURVKBURSales officeCHAR4NU
QMELVKGRPVKGRPSales groupCHAR3NU
QMELAUTKZQAUTKZData Record Created with Function 'Create with Copy Model'CHAR1NU
QMELBEDIDBEDIDID of the Capacity Requirements RecordNUMC12NU
QMELBEDZLCIM_COUNTInternal counterNUMC8NU
QMELPROFIL_TYPOTYPEObject TypeCHAR2NU
QMELPROFIL_IDOBJEKTIDObject IDNUMC8NU
QMELHANDLETSEGGUIDGlobally unique identifier (linked to time segment, etc)CHAR22C
QMELTSEGFLTSEGEXISTSTime segment existsCHAR1NU
QMELTSEGTPTSEGTEMPLATemplateCHAR10NU
QMELTZONSOTZONSOTime Zone for NotificationCHAR6C
QMELTZONIDTZONSMIDOrigin of Time Zone in NotificationCHAR1NU
QMELFUNKTIONQNFUNKTIONKeys for Function in Action BoxCHAR4NU
QMEL/SAPSMOSS/INSTN/SAPSMOSS/R3INSTNInstallation numberCHAR10
QMEL/SAPSMOSS/MNUMM/SAPSMOSS/MNUMMSAPNet notification numberNUMC24
QMEL/SAPSMOSS/OSSYS/SAPSMOSS/OSSYSOperating system and versionCHAR10
QMEL/SAPSMOSS/DBSYS/SAPSMOSS/DBSYSDatabase systemCHAR10
QMEL/SAPSMOSS/REL/SAPSMOSS/R3RELR/3 ReleaseCHAR10
QMEL/SAPSMOSS/COMP/SAPSMOSS/R3COMPAreaCHAR20
QMEL/SAPSMOSS/FRONT/SAPSMOSS/FRONTENDFrontendCHAR10
QMEL/SAPSMOSS/SYSTYP/SAPSMOSS/R3SYSTYPER/3 System typeCHAR1
QMEL/SAPSMOSS/ADDID/SAPSMOSS/R3ADDIDAdd-on IDCHAR10
QMEL/SAPSMOSS/ADDREL/SAPSMOSS/R3ADDRELAdd-On ReleaseCHAR10
QMEL/SAPSMOSS/TSTMP/SAPSMOSS/NSTSTMPSAPNet time stampNUMC14
QMEL/SAPSMOSS/STATUS/SAPSMOSS/STATUSStatus of R/3 notification in SAPNetCHAR1
QMEL/SAPSMOSS/ERDAT/SAPSMOSS/ERDATDate on which notification was completed at SAPDATS8
QMEL/SAPSMOSS/ERZEIT/SAPSMOSS/ERZEITTime when notification was completed at SAPTIMS6
QMEL/SAPSMOSS/SYSIDSYSYSIDName of SAP SystemCHAR8
QMEL/SAPSMOSS/MANDTSYMANDTClient IDCLNT3
QMELPSP_NRPS_POSNRWBS ElementNUMC8NU
QMELESTIMATED_COSTSPS_COSTSEstimated Costs for a ClaimCURR13(2)NU
QMELCLAIMED_COSTSCOSTS_CLAIMCosts ClaimedCURR13(2)NU
QMELRESULT_COSTSCOSTS_RESULTCosts AcceptedCURR13(2)NU
QMELCHANCEPS_CHANCEChance of Completing a ClaimNUMC2NU
QMELOPPONENTPS_OPPONENTPartner TypeCHAR2NU
QMELKALNRCK_KALNRCost Estimate Number for Cost Est. w/o Qty StructureNUMC12NU
QMELKALVARCK_KALVARCosting Variant for Postprocessing with Unit CostingCHAR4NU
QMELOBJNR_REALJ_OBJNR_REALObject Number of Real CO Account AssignmentCHAR22NU
QMELOBJNR_STATOBJNR_N1Auxiliary account assignment 1CHAR22NU
QMELDUMMY_QMEL_INCL_EEW_PSDUMMYDummy function in length 1CHAR1
QMELPHASEQM_PHASENotification Processing PhaseCHAR1NU
QMELCHANGEDDATETIMETZNTSTMPSUTC Time Stamp in Short Form (YYYYMMDDhhmmss)DEC15S
QMEL/ISDFPS/MHIO_ADDATEMHIO_ADDATCompletion Date for Call ObjectDATS8
QMEL/ISDFPS/MHIO_ADTIMEMHIO_ADUHRCompletion Time for Call ObjectTIMS6
QMEL/ISDFPS/USERMODEUSERMODScheduling determined by userCHAR1
QMEL/ISDFPS/OBJNRJ_OBJNRObject numberCHAR22NU
QMELLOGSYSTEMLOGSYSTEMLogical SystemCHAR10NU
QMEL/ISDFPS/MEQUI/ISDFPS/MEQUIMaster EquipmentCHAR18NU
QMELSHN_OBJTYCR_OBJTYObject types of the CIM resourceCHAR2NU
QMELSHN_OBJIDCR_OBJIDObject ID of the resourceNUMC8NU
QMELSHN_FUNCT_LOCTPLNRFunctional LocationCHAR30NU
QMELSHN_EQUIPMENTEQUNREquipment NumberCHAR18NU
QMELSHN_ORIGINCOCF_SRN_ORIGINOrigin or Use of Shift Note or ReportNUMC2NU
QMELUIIUII_CHAR72Unique Item IdentifierCHAR72NU

2.Notification Item

TableFieldData ElementField DescriptionData TypeLengthRequirement
QMFEQMNUMQMNUMNotification NumberCHAR12
QMFEFENUMFELFDItem Number in Item RecordNUMC4
QMFECATEGORYQDEFCATEGORYDefect CategoryCHAR2S
QMFEERNAMERNAMName of Person who Created the ObjectCHAR12S
QMFEERDATERDATDate on which the record was createdDATS8S
QMFEAENAMAENAMName of person who changed objectCHAR12 S
QMFEAEDATAEDATDate of Last ChangeDATS8
QMFEFETXTFETXTNotification Item Short TextCHAR40
QMFEFEKATFEKATCatalog Type - Problems/DefectsCHAR1
QMFEFEGRPFEGRPCode Group - ProblemCHAR8
QMFEFECODFECODProblem or Damage CodeCHAR4
QMFEFEVERQVERSNRVersion NumberCHAR6
QMFEOTKATOTKATCatalog Type - Object PartsCHAR1
QMFEOTGRPOTGRPCode Group - Object PartsCHAR8
QMFEOTEILOTEILPart of ObjectCHAR4
QMFEOTVERQVERSNRVersion NumberCHAR6
QMFEINITIALCAUSECATURKATCatalog Type - CausesCHAR1
QMFEINITIALCAUSEGROUPURGRPCode Group - CausesCHAR8
QMFEINITIALCAUSECODEURCODCause CodeCHAR4
QMFEINITIALCAUSECODEVERQVERSNRVersion NumberCHAR6
QMFEBAUTLBAUTLAssemblyCHAR40
QMFEEBORTEBORTInstallation Point for SubitemCHAR20
QMFEINDTXINDLTXObject Long Text AvailableCHAR1
QMFEKZMLAKZMLAPrimary language indicator for text segmentCHAR1
QMFEERZEITERZEITTime at Which Record Was AddedTIMS6
QMFEAEZEITAEZEITTime of ChangeTIMS6
QMFEKZORGKZORGOriginating DefectCHAR1
QMFEWDFEHWDFEHRepetitive DefectCHAR1
QMFEFEQKLASQFEHLKLASDefect ClassCHAR2
QMFEFCOAUFNRQCOAUFNROrder Number (CO Order) for ItemCHAR12
QMFEFMGFRDQMGFRDDefective Quantity for Item (External)QUAN13(3)
QMFEFMGEIGQMGEIGDefective Quantity for Item (Internal)QUAN13(3)
QMFEFMGEINQMGEINUnit of Measure for ItemUNIT3
QMFEANZFEHLERQANZFEHL4Number of Defects FoundINT410
QMFEFEHLBEWQFEHLBEWDefect ValuationFLTP16(16)
QMFEUNITFLBEWQUNITFLBEWUnit for Defect ValuationUNIT3
QMFEFEARTQFEARTReport Type for Defects RecordingCHAR8
QMFEFERTAUFNRFERTAUFNROrder Number (Production Order)CHAR12
QMFEFERTAUFPLFERTAUFPLPlan Number for Operations in Order (Production Order)NUMC10
QMFEPNLKNQLFNKNCurrent Node Number from Order CounterNUMC8
QMFEMERKNRQMERKNRPInspection Characteristic NumberNUMC4
QMFEPROBENRQPROBENRInspection Sample NumberNUMC6
QMFEPHYNRQPHYSPRNRMaterial Sample NumberCHAR12
QMFEPRUEFLINRQPRUEFLINRSingle-Unit Number for the Unit to Be InspectedCHAR18
QMFECROBJTYCR_OBJTYObject types of the CIM resourceCHAR2
QMFEARBPLLGWIDObject ID of the Work CenterNUMC8
QMFEARBPLWERKQARBPWERKSPlant for Work CenterCHAR4
QMFEFENUMORGQFENUMORGNumber of Original Item to Which Reference Is MadeNUMC4
QMFEKZSYSFEQKZSYSFESystematic DefectCHAR1
QMFEKZLOESCHKZLOESCHDelete Data RecordCHAR1
QMFEPOSNRQLFDPOSSort Number for ItemNUMC4
QMFEHERPOSQMFEHERKOrigin of Item RecordCHAR1
QMFEAUTKZQAUTKZData Record Created with Function 'Create with Copy Model'CHAR1
QMFEMATNRMATNRMaterial NumberCHAR40
QMFEWERKSWERKS_DPlantCHAR4
QMFEEKORGEKORGPurchasing organizationCHAR4
QMFEINFNRINFNRNumber of purchasing info recordCHAR10
QMFEKOSTLKOSTLCost CenterCHAR10
QMFELSTARLSTARActivity TypeCHAR6
QMFEPRZNRCO_PRZNRBusiness ProcessCHAR12
QMFEMENGEQMGPOSDefective Quantity for Item (Internal)QUAN13(3)
QMFEEQUNREQUNREquipment NumberCHAR18
QMFETPLNRTPLNRFunctional LocationCHAR30
QMFEPRUEFLOSQPLOSInspection Lot NumberNUMC12
QMFECHARGCHARG_DBatch NumberCHAR10
QMFEOA_IDMPE_OA_IDIdentifies an Operation ActivityINT819
QMFEOA_VERSION_NOMPE_OA_VERSION_NONumber of an Operation Actiivity VersionINT410
QMFEDEFREFNUMQDEFREFNUMDefect KeyCHAR12
QMFERBNRRBNRCatalog ProfileCHAR9
QMFECHANGEDDATETIMETZNTSTMPSUTC Time Stamp in Short Form (YYYYMMDDhhmmss)DEC15
QMFESTATLCYCLEQDEFLCYCLESTATDefect StatusCHAR2
QMFESTATPANALYSISQDEFPANASTATProblem AnalysisCHAR2
QMFEEXTREFNUMQEXTREFNUMExternal Reference NumberCHAR40
QMFEISAUTOCREATEDQISDEFECTCREATEDAUTOMATICALLYDefect Created AutomaticallyCHAR1
QMFEINTERNALIDQDEFECTINTERNALIDInternal Defect IDCHAR12
QMFEREPUSERQFREPUSERNotification Item Reported ByCHAR12
QMFEREPONDATEQFREPONDATENotification Item Reported OnDATS8
QMFEREPATTIMEQFREPATTIMENotification Item Reported AtTIMS6
QMFEDUMMY_QMFE_INCL_EEW_PSDUMMYDummy function in length 1CHAR1

3.Quality Notification - Messages

TableFieldData ElementField DescriptionData TypeLengthRequirement
QMIHQMNUMQMNUMNotification NumberCHAR12
QMIHIWERKIWERKMaintenance Planning PlantCHAR4
QMIHILOANILOANLocation and account assignment for technical objectCHAR12
QMIHILOAIILOAIILOA IndividualCHAR1
QMIHEQUNREQUNREquipment NumberCHAR18
QMIHBAUTLBAUTLAssemblyCHAR40
QMIHEBORTEBORTInstallation Point for SubitemCHAR20
QMIHMSAUSMSAUSBreakdown IndicatorCHAR1
QMIHAUSVNAUSVNStart of Malfunction (Date)DATS8
QMIHAUSBSAUSBSEnd of Malfunction (Date)DATS8
QMIHAUZTVAUZTVStart of Malfunction (Time)TIMS6
QMIHAUZTBAUZTBEnd of Malfunction (Time)TIMS6
QMIHAUSZTAUSZTBreakdown DurationFLTP16(16)
QMIHMAUEHMAUEHUnit for Breakdown DurationUNIT3
QMIHBTPLNBTPLNFunctional Location AffectedCHAR30
QMIHBEQUIBEQUIEquipment AffectedCHAR18
QMIHAUSWKAUSWKEffect on OperationCHAR1
QMIHVERFVVERFVAvailability Before MalfunctionNUMC3
QMIHVERFNVERFNAvailability After MalfunctionNUMC3
QMIHVERFMVERFMAvailability After Completion of TaskNUMC3
QMIHANLZVANLZVSystem Condition Before MalfunctionCHAR1
QMIHANLZNANLZNSystem Condition After MalfunctionCHAR1
QMIHANLZEANLZESystem Condition After Completion of TaskCHAR1
QMIHINSPKINSPKName of Person Responsible for Technical InspectionCHAR12
QMIHDATANDATANDate of Technical InspectionDATS8
QMIHINGRPINGRPPlanner Group for Customer Service and Plant MaintenanceCHAR3
QMIHWARPLWARPLMaintenance PlanCHAR12
QMIHABNUMABNUMMaintenance Plan Call NumberINT410
QMIHWAPOSWAPOSMaintenance itemCHAR16
QMIHKDAUFVBELN_VASales DocumentCHAR10
QMIHKDPOSPOSNR_VASales Document ItemNUMC6
QMIHSCREENTYSCRTPScenario or Subscreen CategoryCHAR4
QMIHPLNTYPLNTYTask List TypeCHAR1
QMIHPLNNRPLNNRKey for Task List GroupCHAR8
QMIHPLNALPLNALGroup CounterCHAR2
QMIHREVNRREVNIRevision for Plant Maintenance and Customer ServiceCHAR8
QMIHLOC_DESCPM_LOC_DESCPM: Description of Current LocationCHAR50
QMIHILARTILAMaintenance activity typeCHAR3
QMIHZAEHLCIM_COUNTInternal counterNUMC8
QMIHPAMS_PTSTFPAMS_PTSTFPlanned Time Stamp (from)DEC15
QMIHPAMS_PTSTTPAMS_PTSTTPlanned Time Stamp (to)DEC15
QMIHPAMS_ATSTFPAMS_ATSTFActual Start TimeDEC15
QMIHPAMS_ATSTTPAMS_ATSTTActual End TimeDEC15
QMIHPAMS_POOLPAMS_POOLPAM PoolCHAR8
QMIHPAMS_KOSTLKOSTLCost CenterCHAR10
QMIHPAMS_AUFNRAUFNROrder NumberCHAR12
QMIHPAMS_PROIDPS_PSP_PNRWork Breakdown Structure Element (WBS Element)NUMC8
QMIHPAMS_KOKRSKOKRSControlling AreaCHAR4

4.Quality Notification - Causes

TableFieldData ElementField DescriptionData TypeLengthRequirement
QMURQMNUMQMNUMNotification NumberCHAR12
QMURFENUMFELFDItem Number in Item RecordNUMC4
QMURURNUMURNUMSequential Number for CauseNUMC4
QMURERNAMERNAMName of Person who Created the ObjectCHAR12
QMURERDATERDATDate on which the record was createdDATS8
QMURAENAMAENAMName of person who changed objectCHAR12
QMURAEDATAEDATDate of Last ChangeDATS8
QMURURTXTURSTXCause TextCHAR40
QMURURKATURKATCatalog Type - CausesCHAR1
QMURURGRPURGRPCode Group - CausesCHAR8
QMURURCODURCODCause CodeCHAR4
QMURURVERQVERSNRVersion NumberCHAR6
QMURINDTXINDLTXObject Long Text AvailableCHAR1
QMURKZMLAKZMLAPrimary language indicator for text segmentCHAR1
QMURERZEITERZEITTime at Which Record Was AddedTIMS6
QMURAEZEITAEZEITTime of ChangeTIMS6
QMURVUKATQVUKATCatalog Type - Party ResponsibleCHAR1
QMURVUGRPQVUGRPCode Group - Party ResponsibleCHAR8
QMURVUCODQVUCODCode for Party ResponsibleCHAR4
QMURPARVWQMUR_PARVWFunction for Party ResponsibleCHAR2
QMURPARNRQMUR_PARNRParty Responsible for Cause (Partner Number)CHAR12
QMURBAUTLQMUR_BAUTLCause AssemblyCHAR40
QMURURMENGEQURMNGQuantityQUAN13(3)
QMURURMGEINQMGEINUnit of Measure for ItemUNIT3
QMURKZLOESCHKZLOESCHDelete Data RecordCHAR1
QMURQURNUMQURNUMSort Number for CauseNUMC4
QMURAUTKZQAUTKZData Record Created with Function 'Create with Copy Model'CHAR1
QMURDUMMY_QMUR_INCL_EEW_PSDUMMYDummy function in length 1CHAR1
QMURROOTCAUSEEAM_ROOT_CAUSERoot CauseCHAR1
QMURCHANGEDDATETIMETZNTSTMPSUTC Time Stamp in Short Form (YYYYMMDDhhmmss)DEC15
QMURINVOLVPERCQN8D_INVOLVPERCInvolvment in PercentageNUMC3

5.Quality Notification - Tasks

TableFieldData ElementField DescriptionData TypeLengthRequirement
QMSMQMNUMQMNUMNotification NumberCHAR12
QMSMMANUMMANUMSequential Task NumberNUMC4
QMSMMNKATMAKATCatalog Type - TasksCHAR1
QMSMMNGRPMAGRPCode Group - TasksCHAR8
QMSMMNCODMNCODTask CodeCHAR4
QMSMMNVERQVERSNRVersion NumberCHAR6
QMSMFOLGEACTQMFOLACTFollow-Up Action for TaskCHAR8
QMSMFOLACTPROTQMFOAPROTLog for Follow-Up ActionCHAR1
QMSMMATXTMATXTShort Text for TaskCHAR40
QMSMERNAMERNAMName of Person who Created the ObjectCHAR12
QMSMERDATERDATDate on which the record was createdDATS8
QMSMAENAMAENAMName of person who changed objectCHAR12
QMSMAEDATAEDATDate of Last ChangeDATS8
QMSMPSTERPSTERPlanned Start DateDATS8
QMSMPETERPETERPlanned Finish DateDATS8
QMSMOBJNRQMOBJNRObject Number for Status ManagementCHAR22
QMSMINDTXINDLTXObject Long Text AvailableCHAR1
QMSMKZMLAKZMLAPrimary language indicator for text segmentCHAR1
QMSMPSTURPSTURPlanned Start Time for TaskTIMS6
QMSMPETURPETURPlanned Finish Time for TaskTIMS6
QMSMERLNAMQMSMERLNAMPerson Who Completed the TaskCHAR12
QMSMERLDATQMSMERLDATDate on Which the Task Was CompletedDATS8
QMSMERLZEITQMSMERLTIMTime at Which Task Was CompletedTIMS6
QMSMWDVDATQMSMWDVDATDate on Which Task Was ResubmittedDATS8
QMSMFENUMFELFDItem Number in Item RecordNUMC4
QMSMURNUMURNUMSequential Number for CauseNUMC4
QMSMERZEITERZEITTime at Which Record Was AddedTIMS6
QMSMAEZEITAEZEITTime of ChangeTIMS6
QMSMPARVWQMSM_PARVWFunction of Person Responsible for TaskCHAR2
QMSMPARNRQMSM_PARNRPerson Responsible for Task (Partner Number)CHAR12
QMSMMMENGEQSMMNGQuantityQUAN13(3)
QMSMMMGEINQMGEINUnit of Measure for ItemUNIT3
QMSMBAUTLQMSM_BAUTLAssembly Affected by the TaskCHAR40
QMSMKZLOESCHKZLOESCHDelete Data RecordCHAR1
QMSMQSMNUMQSMNUMSort Number for TaskNUMC4
QMSMAUTKZQAUTKZData Record Created with Function 'Create with Copy Model'CHAR1
QMSMHANDLETSEGGUIDGlobally unique identifier (linked to time segment, etc)CHAR22
QMSMTSEGFLTSEGEXISTSTime segment existsCHAR1
QMSMTSEGTPTSEGTEMPLATemplateCHAR10
QMSMTZONSOTZONSOTime Zone for NotificationCHAR6
QMSMTZONSMTZONSMTime Zone for TaskCHAR6
QMSMTZONIDTZONSMIDOrigin of Time Zone in NotificationCHAR1
QMSMDUMMY_QMSM_INCL_EEW_PSDUMMYDummy function in length 1CHAR1
QMSMKZACTIONBOXQNKZACTIONBOXCreated Using Action BoxCHAR1
QMSMFUNKTIONQNFUNKTIONKeys for Function in Action BoxCHAR4
QMSM/SAPSMOSS/NOTE/SAPSMOSS/NOTENote numberNUMC7
QMSM/SAPSMOSS/REPORT/SAPSMOSS/MEMOREPORTNote created byCHAR35
QMSM/SAPSMOSS/MTSTMP/SAPSMOSS/MEMOTSTMPTime stamp (date + time)NUMC14
QMSMABC_TEMPLABC_TEMPLTemplateCHAR10
QMSMTASKTYPEQTSKTYPETask TypeCHAR2
QMSMDEFECTINTERNALIDQDEFECTINTERNALIDInternal Defect IDCHAR12
QMSMTASKORIGINQTASKORIGINQuality Task OriginCHAR2
QMSMPROCESSORQTSKPROCQuality Task ProcessorCHAR10
QMSMCHANGEDDATETIMETZNTSTMPSUTC Time Stamp in Short Form (YYYYMMDDhhmmss)DEC15
QMSMSTATLCYCLEQTSKLCYCLESTATQuality Task StatusCHAR2
QMSMSTATACYCLEQTSKACYCLESTATQuality Task Archiving StatusCHAR2
QMSMSTATFOAQTSKFOASTATQuality Task Follow-Up Action StatusCHAR2
QMSMWDVZEITQMSMWDVTIMTime at Which Task Was ResubmittedTIMS6
QMSMEFFECTPERCQN8D_EFFECTPERCEffect in PercentageNUMC3
QMSMEFFECTTEXTQN8D_EFFECTTEXTEffect TextCHAR40

6.Quality Notification - Activities

TableFieldData ElementField DescriptionData TypeLengthRequirement
QMMAQMNUMQMNUMNotification NumberCHAR12
QMMAMANUMAKNUMConsecutive Number of ActivityNUMC4
QMMAFENUMFELFDItem Number in Item RecordNUMC4
QMMAURNUMURNUMSequential Number for CauseNUMC4
QMMAMNKATMFKATCatalog Type - ActivitiesCHAR1
QMMAMNGRPMFGRPCode Group - ActivitiesCHAR8
QMMAMNCODMFCODActivity CodeCHAR4
QMMAMNVERQVERSNRVersion NumberCHAR6
QMMAMATXTMFTEXTActivity TextCHAR40
QMMAERNAMERNAMName of Person who Created the ObjectCHAR12
QMMAERDATERDATDate on which the record was createdDATS8
QMMAAENAMAENAMName of person who changed objectCHAR12
QMMAAEDATAEDATDate of Last ChangeDATS8
QMMAMAKLSMAKLSTask ClassCHAR18
QMMAKLAKZKLAKZIndicator: Classification existsCHAR1
QMMAPSTERPSTERMAActivity Start DateDATS8
QMMAPETERPETERMAActivity End DateDATS8
QMMAINDTXINDLTXObject Long Text AvailableCHAR1
QMMAKZMLAKZMLAPrimary language indicator for text segmentCHAR1
QMMAMNGFAMNGFAQuantity Factor for ActivitiesNUMC3
QMMAPSTURPSTURMAStart Time of ActivityTIMS6
QMMAPETURPETURMAEnd Time of ActivityTIMS6
QMMAERZEITERZEITTime at Which Record Was AddedTIMS6
QMMAAEZEITAEZEITTime of ChangeTIMS6
QMMAKZLOESCHKZLOESCHDelete Data RecordCHAR1
QMMAQMANUMQMANUMSort Number for ActivityNUMC4
QMMAAUTKZQAUTKZData Record Created with Function 'Create with Copy Model'CHAR1
QMMAKZACTIONBOXQNKZACTIONBOXCreated Using Action BoxCHAR1
QMMAFUNKTIONQNFUNKTIONKeys for Function in Action BoxCHAR4
QMMACHANGEDDATETIMETZNTSTMPSUTC Time Stamp in Short Form (YYYYMMDDhhmmss)DEC15
QMMADUMMY_QMMA_INCL_EEW_PSDUMMYDummy function in length 1CHAR1



Data Cleansing

IDCriticalityError Message/Report DescriptionRuleOutputSource System

9004-001


C1 

Invalid or Inactive Equipment or Functional Location linked to Notification

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

Equipment, Functional Location

PF2, WP2

9004-002

C1

Business Partner: Invalid  or Inactive Business Partner (Customer) linked to Notification

Notification as per Relevancy Criteria assigned with a Business Partner (Customer) does not belong below:
1. Business Partner FLCU01 (SD) as per Relevancy Criteria

Business Partner (Customer) 

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

Catalog Code Groups & Code

PF2, WP2

9004-004

C1


Characteristic: Invalid or Inactive Characteristics linked to Notification

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

Characteristic 

PF2, WP2

9004-005


C1 

Class: Invalid or Inactive Class linked to Notification

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

Class 

PF2, WP2

9004-006

C1

Document Info Record: Invalid  or Inactive Document Info Record linked to Notification

Notification as per Relevancy Criteria assigned with a Document Info Record does not belong below:
1. Document Info Record as per Relevancy Criteria

Document Info Record 

PF2, WP2

9004-007

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

Maintenance Item

PF2, WP2

9004-008

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 

Revision

PF2, WP2

9004-009

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

Work Centre 

PF2, WP2


9004-010

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 Creation Date

PF2, WP2

9004-011

C1

Company Code: Notification Company Code incorrect

Notification as per Relevancy Criteria with Invalid Company Code (T001) 

Company Code

PF2, WP2

9004-012 

C1

Plant: Notification Plant incorrect.Notification as per Relevancy Criteria with Invalid Plant (T001W)Plant

PF2, WP2

9004-013

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) 

Planner Group 

PF2, WP2

9004-014

C1 Plant: Notification Plant Section incorrect.Notification as per Relevancy Criteria with Invalid Plant Section (T357)PlantPF2, WP2

9004-014

C1 

Location: Notification Location incorrect. 

Notification as per Relevancy Criteria with Invalid Location (T499S) 

Location 

PF2, WP2

9004-015

C2

Maintenance Plant: Notification  Planning Plant and Maintenance Plant are not the same.

Notification as per Relevancy Criteria with Planning Plant <> Maintenance Plant

Maintenance Plant, Planning Plant

PF2, WP2

9004-016

C2

Description: Notification contains Thai characters

Notification Description with Thai characters

Description

PF2, WP2

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

1

Ensure that create, change and deletion of master data is freeze in legacy Production system 

Legacy IT 

2

Relevancy Criteria for Catalog Profile

SyWay A2D Data Team

3

Relevancy Criteria for Catalog Code Groups & Codes

SyWay A2D Data Team

4

Relevancy Criteria for Characteristics

SyWay A2D Data Team

5

Relevancy Criteria for Class

SyWay A2D Data Team

6

Relevancy Criteria for Construction Type

SyWay A2D Data Team

7

Relevancy Criteria for Document Info Record

SyWay A2D Data Team

8

Relevancy Criteria for Equipment

SyWay A2D Data Team

9

Relevancy Criteria for Functional Location

SyWay A2D Data Team

10

Relevancy Criteria for Maintenance Plan and Item

SyWay A2D Data Team

11

Relevancy Criteria for Revision

SyWay A2D Data Team

12

Relevancy Criteria for Task List

SyWay A2D Data Team

13

Relevancy Criteria for Work Centre

SyWay A2D Data Team

14Relevancy Criteria for Cost CentreSyWay A2D Data Team
15Relevancy Criteria for Employee MasterSyWay A2D Data Team
16Relevancy Criteria for Work Breakdown StructureSyWay A2D Data Team
17Relevancy Criteria for Material MasterSyWay A2D Data Team
18Relevancy Criteria for Business Partner (Customer)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 Syniti Migrate
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 Syniti Migrate
  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

Ensure all mapping tables are up to date.

Syniti

2

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

Syniti

3

Go to Process Area Launch and Process the Object – Work Order

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 invalid reports by region 

Business/Data owner

7

Generate export(load) file (If load tool is not dspIntegrate)

SyWay A2D Data Team


Transformation Rules

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

Notification will be created based on internal number. The load file will be blank but after loading, this number is retrieved for XREF generation.

2

PF2, WP2 

QMEL

AUFNR

Order Number

S/4 HANA

QMEL

AUFNR

Order Number

Based on the design for load program,  Notification creation is separate from the Work Order. 

Blank for Standalone Notification

3PF2, WP2QMELQMARTNotification TypeS/4 HANAQMELQMARTNotification TypeIf Notification is assigned to Work Order:
Order PM01: Notification Type M1 if Breakdown Indicator is blank, Notification Type M2 if Breakdown Indicator is assigned
Order PM02: M3
If Notification is not assigned to Work Order:
Notification Type M1 if Breakdown Indicator is blank
Notification Type M2 if Breakdown Indicator is assigned
Only if notification does not exist for PM01 Work Order, default to: M1
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

Value Mapping: Equipment Number
Use EQUNR to map from old to new Equipment Number

If not blank, Transform based on mapping table for Equipment.
Error if cannot be mapped.
If blank, and if linked to Work Order, then use Work Order value.

6PF2, WP2QMELTPLNRFunctional LocationS/4 HANAIFLOTPLNRFunctional Location Label

Value Mapping: Functional Location
Use TPLNR to map from old to new Functional Location

If not blank, Transform based on mapping table for Functional Location
Error if cannot be mapped.
If blank OR INVALID / ERROR / CANNOT BE MAPPED,, and if linked to Work Order, then use Work Order value.

Transform to blank if Equipment is not blank   

 (Rationale – the FL will be defaulted from EQ during loading) 

 7PF2, WP2QMIHINGRPPlanner GroupS/4 HANAVIQMLINGRPPlanner Group

Value Mapping: Planner Group
Use INGRP to map from old to new Planner Group

Transform based on mapping table Planner Group.
Error if cannot be mapped.
If blank OR INVALID / ERROR / CANNOT BE MAPPED,, and if linked to Work Order, then use Work Order value.
For Turnaround Work Order, Planner Group to be assigned to “TA1” in Work Order and Assigned Notification

8PF2, WP2QMFEIWERKMaintenance Planning PlantS/4 HANAVIQMLWERKMaintenance Planning PlantDefault to Planning Plant from reference technical object.
9PF2, WP2QMFEARBPLObject ID for Work CentreS/4 HANA

Object ID for Work CentreThis field is derived based on the ARBPL Object ID for the Work Centre. Perform the steps:
Transform based on mapping table for Work Centre.
Only map Main Work Centre.
If blank or cannot be mapped, and if linked to Work Order, then use Work Order value.
If not linked to Work Order, then derive the Main Work Centre from the first 4 character of the mapped work Centre. If error, then default to technical object Work Centre.
Error if cannot be mapped.
10PF2, WP2CRHDARBPLWork CentreS/4 HANACRHDARBPLWork Centre

Value Mapping: [Mapping Name]
Use ARBPL to map from old to new Work Centre

11PF2, WP2CRHDWERKSWork Centre plantS/4 HANACRHDWERKSWork Centre plant

Value Mapping: [Mapping Name]
Use WERKS to map from old to new Work Centre plant based on S/4 HANA mapped value of ARBPL

12PF2, WP2QMELQMDATNotification DateS/4 HANAQMELQMDATNotification DateDirect Mapping.
Only if notification does not exist for PM01 Work Order, default to: Work Order Basic Start Date
13PF2, WP2QMELMZEITNotification TimeS/4 HANAQMELMZEITNotification TimeDirect Mapping.
Only if notification does not exist for PM01 Work Order, default to:00:00:00
14PF2, WP2QMELERNAMReported ByS/4 HANAQMELERNAMReported ByDirect Mapping.
Only if notification does not exist for PM01 Work Order, default to: Migration User ID (Name)
15PF2, 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.
16PF2, 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
17PF2, WP2QMELPRIOKPriorityS/4 HANAQMELPRIOKPriority

Value Mapping: [Mapping Name]
Use PRIOK to map from old to new Priority.

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

18PF2, WP2QMELQMGRPCode GroupS/4 HANAQMELQMGRPCode GroupFor Notification Type - 
M1: Default to: PMOTH00
M2: Default to: PMBRD00
M3: Default to: PMOTH00
19PF2, WP2QMELQMCODCodingS/4 HANAQMELQMCODCodingFor Notification Type - 
M1: Default to: 0009
M2: Default to: 0099
M3: Default to: 0099
20PF2, WP2QMELRBNRCatalog ProfileS/4 HANAQMELRBNRCatalog ProfileCatalogue Profile to be derived from the Functional Location
21PF2, WP2N/AN/AIssue Permit


Issue PermitTransform – if Notification is assigned to Work Order, then “X”.
22PF2, WP2QMIHILARTMaintenance Activity TypeS/4 HANAQMIHILARTMaintenance Activity TypeFollow Work Order ILART.
If Work Order ILART is blank, default to COR.
23PF2, WP2QMIHREVNRRevisionS/4 HANAQMIHREVNRRevisionDo not transform – just display the legacy revision
24PF2, WP2

QMIH

MSAUSBreakdown IndicatorS/4 HANA

Breakdown IndicatorDirect Mapping.
25PF2, WP2

QMIH

AUSVNMalfunct. Start DateS/4 HANA

Malfunct. Start DateDirect Mapping.
26PF2, WP2

QMIH

AUZTVMalfunct. Start TimeS/4 HANA

Malfunct. Start TimeDirect Mapping.
27PF2, WP2

QMIH

AUSBSMalfunct. End DateS/4 HANA

Malfunct. End DateDirect Mapping.
28PF2, WP2

QMIH

AUZTBMalfunct. End TimeS/4 HANA

Malfunct. End TimeDirect Mapping.
29PF2, WP2

QMIH

AUSZTBreakdown DurationS/4 HANA

Breakdown DurationDirect Mapping.
30PF2, WP2

QMIH

MAUEHBreakdown UnitS/4 HANA

Breakdown UnitDirect 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

Revision

Cross Reference table for Revision

Work Centre

Old to new Work Centre

Equipment

Old to new Equipment

Functional Location

Old to new Functional Location

WBS Element

Old to new WBS Element

Cost Centre

Old to new Cost Centre

Profit Centre

Old to new Profit Centre

Vendor

Old to new Vendor

Material Master

Old to new Material Number

Assembly

Old to new Assembly

Outline Agreement

Cross Reference table for Outline Agreement

GL Account

Old to new GL Account

Purchasing Info Record Number

Old to new Purchasing Info Record Number

Transformation Dependencies

List the steps that need to occur before transformation can commence
Item #Step DescriptionTeam Responsible

1

Ensure DCT tables completeness

SyWay A2D Data Team

2

All XREF tables specified in the mapping table section should be available.

SyWay A2D Data Team

3AUFK - Work Order tables must be loaded

 SyWay A2D Data Team

4MKAL - Production Versions of Material table must be loaded

 SyWay A2D Data Team

5SAFK - CIM Resource - Entities details table must be loadedSyWay A2D Data Team
6MARA - General Material Data details table must be loadedSyWay A2D Data Team
7KNA1 - General Data in Customer Master details must be loadedSyWay A2D Data Team
8ONR00 - General Object Number details must be loadedSyWay A2D Data Team
9LFA1 - Vendor Master (General Section) details must be loadedSyWay A2D Data Team
10VBAK - Sales Document: Header Data detailsSyWay A2D Data Team
11QPGR - Inspection catalog code groups detailsSyWay A2D Data Team
12QALS - Inspection lot record detailsSyWay A2D Data Team
13EKKO - Purchasing Document Header detailsSyWay A2D Data Team
14EKPO - Purchasing Document Item detailsSyWay A2D Data Team
15VBAP - Sales Document: Item Data detailsSyWay A2D Data Team
16LIKP - SD Document: Delivery Header Data detailsSyWay A2D Data Team
17LIPS - SD document: Delivery: Item data detailsSyWay A2D Data Team
18CRID  - CIM Resource - Entities detailsSyWay A2D 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 legacy systems and DCTs (if any) is equal to the total number of records in the Preload and Load Sheets.

Verify Data Integrity

SyWay A2D Data Team to verify that the total number of Operations per Work Oder header extracted from legacy systems and DCTs (if any) should be equal to the total number of operations identified in the Preload and Load Sheets


Accuracy

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 legacy systems and DCTs (if any) 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 fields below meet pass the checks:

  1. Mandatory Fields
  2. Field and Value Mapping Correctness
  3. Null Checks
  4. Text Length Checks


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

Syniti will provide load file

Syniti


Load Phase and Dependencies

Configuration

Item #Configuration Item
1Notification Type

Conversion Objects

Object #Preceding Object Conversion Approach

1030

Work Centre

1002

Equipment

1003

Functional Location

1026

WBS - CAPEX, OPEX, Statistical

1074

Cost Centre

1073

Profit Centre

3018

Vendor

2019

Material

1010

Assembly

1094

Purchase Info Records (Including Pricing Conditions)

1067

GL Account Operational CoA (incl. secondary CE)

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. 68) 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