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

Compare with Current View Page History

« Previous Version 154 Next »

Purpose

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

A Work Order in SAP PM is a technical and financial document used to plan, execute, and settle maintenance tasks on technical objects. It acts as a detailed instruction, outlining tasks, required resources, parts, and schedules, while tracking costs, technical history, and compliance. 

Legacy Plant Maintenance Work order is using a diverse range of formats across the different systems. As per SyWay design, EAM Maintenance Work order will be standardized.


Conversion Scope

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

A work order in SAP is a formal document that authorises and tracks maintenance, repair, or production tasks within an organisation, containing essential details for effective task management. It is used to manage and document various tasks, including maintenance, repairs, and production activities. Key components of a work order include:

  • Work Description: Specific details of the task to be carried out
  • Equipment Details: Information about the asset or machinery requiring attention
  • Resources: Assignment of personnel, tools, and materials needed for task completion
  • Dates: Scheduled start and finish dates to manage timelines
  • Costing: Estimates for labour, materials, and other expenditures linked to budget accounts
  • Priority & Status: Indicates urgency and tracks progress (e.g., created, released, completed, closed)
  • Operations: Step-by-step instructions or tasks within the work order.


The data from legacy system includes:

  • All open Work Orders (AUFK-AUFNR) with System Status (JEST-STAT) = Created (CRTD) or Released (REL).
  • Work Orders (AUFK-AUFNR) with System Status (JEST-STAT) = Technically Completed (TECO) and relevant open Purchase Order (EKKN-EBELN) as defined in CNV-9045 Open Purchase Orders
  • Work Orders with Maintenance Plant (IFLOT-WERKS) existing in Value Mapping: Plant (Maintenance Plant = Yes).
  • Work Orders assigned to active legacy Functional Locations (IFLOT-TPLR) ** (System Status TJ02T-TXT04 <> INAC) or Equipment (EQUI-EQUNR)
  • Work Orders generated from Maintenance Plan with Basic Start Date (AFKO-GSTRP) <= Business Continuity Date
  • A. Work Orders with no open PO, with Basic Start Date (AFKO-GSTRP) later than X Period prior of the Migration / "Go-Live" Date (OTH_Migration_Date Relevant Values A2D (using Object ID "9005" and Field Name = "AFKO-GSTRP") - OTH_Migration_Date Relevant Values A2D (using Object ID "9005" and Field Name = "AFKO-GSTRP_PERIOD"))
    B. Work Orders with no open PO, with Basic End Date (AFKO-GLTRP) later than X Period prior of the Migration / "Go-Live" Date (OTH_Migration_Date Relevant Values A2D (using Object ID "9005" and Field Name = "AFKO-GLTRP") - OTH_Migration_Date Relevant Values A2D (using Object ID "9005" and Field Name = "AFKO-GLTRP_PERIOD"))
    C. Work Orders with open PO, regardless of Basic Start (AFKO-GSTRP)/ Finish Date (AFKO-GLTRP)

The data from legacy system excludes:

  1. Work Orders with System Status (JEST-STAT) = Technically Completed (TECO) that do not meet Inclusion Criteria #2
  2. Work Orders with System Status (JEST-STAT) = Deletion Flag (DLFL) status
  3. Work Orders with System Status (JEST-STAT) = Closed (CLSD) status
  4. Work Orders with System Status (JEST-STAT) = Not Completed/ Do Not Execute (NCMP) status
  5. Standing Work Orders (Value Mapping: Work Order Type, where Target WO Type = 'YA05').
  6. Work Orders (AUFK-AUFNR) which are Sub-orders (AFKO-MAUFNR <> '')
  7. Work Orders with blank Basic End Date (AFKO-GLTRP)
  8. Work Orders with Order type maintained in Work Order Type Exclusion List (EXC-Work Order Type)
  9. Work Orders with System Status (JEST-STAT) <> (TECO/ DLFL/ CLSD/ NCMP) and with a User Status maintained in the User Status Exclusion List (EXC-Work Order User Status)

List of Tables to extract for this object is maintained hereExtract 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 Work Orders will be extracted from PF2 and WP2

70,000

S/4HANA 

70,000

DCT

Work Orders for plants which do not have data existing from PF2 and WP2

TBD

S/4HANA 

TBD

Additional Information

Multi-language Requirement

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

Multi language is supported for Work Order Long Text. Login via a different language will have its Long Text displayed in the logon language if the language key is maintained in the Work Order.

Document Management

Refer to the KDD085 - Document Management in the SyWay Solution

Note: Documents attached to Equipment 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. Work Order Header

TableFieldData ElementField DescriptionData TypeLengthRequirement
YA01 (Reactive Maintenance)
Requirement
YA02 (Proactive Maintenance)
Requirement
YA03 (Project Order)
AUFKAUFNRAUFNROrder NumberCHAR12MandatoryMandatoryMandatory
AUFKAUARTAUARTOrder TypeCHAR4MandatoryMandatoryMandatory
AUFKKTEXTKTEXTDescriptionCHAR40MandatoryMandatoryMandatory
AFIHPRIOKPRIOKPriorityCHAR80MandatoryMandatoryMandatory
AFKOGSTRPGSTRPBasic Start DateDATS8MandatoryMandatoryMandatory
AFKOGSUZPGSUZPBasic Start TimeTIMS6MandatoryMandatoryMandatory
AFKOGLTRPGLTRPBasic Finish DateDATS8MandatoryMandatoryMandatory
AFKOGLUZPGLUZPBasic Finish TimeTIMS6MandatoryMandatoryMandatory
IFLOTTPLNRTPLNRFunctional LocationCHAR30MandatoryMandatoryMandatory
AFIHEQUNREQUNREquipmentCHAR18ConditionalConditionalConditional
AFIHQMNUMQMNUMAssigned NotificationCHAR12MandatoryMandatoryMandatory
AFIHREVNRREVNRMaintenance Event/ RevisionCHAR8ConditionalConditionalConditional
AFIHILARTILARTMaintenance Activity TypeCHAR3MandatoryMandatoryMandatory
CRHDARBPLARBPLWork CenterCHAR8MandatoryMandatoryMandatory
CRHDWERKSWERKSWork Center PlantCHAR4MandatoryMandatoryMandatory
AFIHIWERKIWERKPlanning PlantCHAR80MandatoryMandatoryMandatory
AFIHINGPRINGPRPlanner GroupCHAR80MandatoryMandatoryMandatory
AUFKWERKSWERKSMaintenance PlantCHAR4MandatoryMandatoryMandatory
ILOABEBERBEBERPlant SectionCHAR3MandatoryMandatoryMandatory
ILOABUKRSBUKRSCompany CodeCHAR4MandatoryMandatoryMandatory
ILOAPROIDPROIDWBS Element (Acc Assignment)CHAR8ConditionalConditionalConditional
ILOAKOSTLKOSTLCost CenterCHAR10MandatoryMandatoryConditional

 

2. Work Order Partner

TableFieldData ElementField DescriptionData TypeLengthRequirement
YA01 (Reactive Maintenance)
Requirement
YA02 (Proactive Maintenance)
Requirement
YA03 (Project Order)
AUFKAUFNRAUFNROrder NumberCHAR12MandatoryMandatoryMandatory
IHPAPARVWPARVWPartner FunctionCHAR2ConditionalConditionalConditional
IHPAPARNRPARNRPartnerCHAR12ConditionalConditionalConditional


3. Work Order Operation Data

TableFieldData ElementField DescriptionData TypeLengthRequirement
YA01 (Reactive Maintenance)
Requirement
YA02 (Proactive Maintenance)
Requirement
YA03 (Project Order)
AFVCAUFNRAUFNROrder NumberCHAR12MandatoryMandatoryMandatory
AFVCVORNRVORNROperation NumberCHAR4MandatoryMandatoryMandatory
AFVCLTXA1LTXA1Operation DescriptionCHAR40MandatoryMandatoryMandatory
CRHDARBPLARBPLWork CenterCHAR8MandatoryMandatoryMandatory
CRHDWERKSWERKSWork Center PlantCHAR4MandatoryMandatoryMandatory
AFVCPERNRPERNRPerson ResponsibleCHAR8ConditionalConditionalConditional
AFVCSTEUSSTEUSControl KeyCHAR4MandatoryMandatoryMandatory
AFVCSAKTOSAKTOCost ElementCHAR10ConditionalConditionalConditional
AFVCEKORGEKORGPurchasing OrganisationCHAR4ConditionalConditionalConditional
AFVCEKGRPEKGRPPurchasing GroupCHAR3ConditionalConditionalConditional
AFVCMATKLMATKLMaterial GroupCHAR9ConditionalConditionalConditional
AFVCANLZUANLZUSystem ConditionCHAR1ConditionalConditionalConditional
AFVCLARNTLARNTActivity TypeCHAR6ConditionalConditionalConditional
AFVVARBEIARBEIWorkNUMC7MandatoryMandatoryMandatory
AFVVARBEHARBEHWork UnitCHAR3MandatoryMandatoryMandatory
AFVCINDETINDETCalculation KeyCHAR1MandatoryMandatoryMandatory
AFVVDAUNODAUNODurationNUMC5MandatoryMandatoryMandatory
AFVVDAUNEDAUNEDuration UnitCHAR3MandatoryMandatoryMandatory
AFVCANZZLANZZLRequired CapacitiesNUMC3MandatoryMandatoryMandatory
AFVVEINSAEINSAStart ConstraintCHAR1ConditionalConditionalConditional
AFVVNTANFNTANFStart Constraint DateDATS8ConditionalConditionalConditional
AFVVNTANZNTANZStart Constraint TimeTIMS6ConditionalConditionalConditional
AFVVEINSEEINSEFinish ConstraintCHAR1ConditionalConditionalConditional
AFVVNTENDNTENDFinish Constraint DateDATS8ConditionalConditionalConditional
AFVVNTENZNTENZFinish Constraint TimeTIMS6ConditionalConditionalConditional
AFVVMGVRGMGVRGOperation QuantityNUMC13ConditionalConditionalConditional
AFVVMEINHMEINHOperation Quantity UnitCHAR3ConditionalConditionalConditional
AFVCPREISPREISPriceCHAR11ConditionalConditionalConditional
AFVCWAERSWAERSCurrencyCHAR5ConditionalConditionalConditional
AFVCPEINHPEINHPrice UnitNUMC5ConditionalConditionalConditional
AFVCLIFNRLIFNRVendorCHAR10ConditionalConditionalConditional
AFVCWEMPFWEMPFRecipientCHAR12ConditionalConditionalConditional
AFVCBEDNRBEDNRTracking NumberCHAR10ConditionalConditionalConditional
AFVCSORTLSORTLSort TermCHAR10ConditionalConditionalConditional
AFVCINFNRINFNRPurchasing Info RecordCHAR10ConditionalConditionalConditional
AFVCAFNAMAFNAMName of RequisitionerCHAR12ConditionalConditionalConditional
AFVCABLADABLADUnloading PointCHAR25ConditionalConditionalConditional
AFVVPLIFZPLIFZPlanned Delivery Time - DayNUMC3ConditionalConditionalConditional


 4. Work Order Operation Components

TableFieldData ElementField DescriptionData TypeLengthRequirement
YA01 (Reactive Maintenance)
Requirement
YA02 (Proactive Maintenance)
Requirement
YA03 (Project Order)
AFVCAUFNRAUFNROrder NumberCHAR12MandatoryMandatoryMandatory
AFVCVORNRVORNROperation NumberCHAR4MandatoryMandatoryMandatory
RESBPOSNRPOSNRItem Number of ReservationNUMC4MandatoryMandatoryMandatory
RESBMATNRMATNRMaterialCHAR18ConditionalConditionalConditional
RESBPOTX1POTX1DescriptionCHAR40SystemSystemSystem
RESBPOSTPPOSTPItem CategoryCHAR1MandatoryMandatoryMandatory
RESBBDMNGBDMNGRequirement QuantityNUMC13MandatoryMandatoryMandatory
RESBMEINSMEINSUnitCHAR3MandatoryMandatoryMandatory
RESBNO_DISPNO_DISPReservation Relevance / Generation of Purchase RequisitionCHAR1SystemSystemSystem
RESBWERKSWERKSPlantCHAR4ConditionalConditionalConditional
RESBBDTERBDTERRequirements DateDATS8ConditionalConditionalConditional
RESBLGORTLGORTStorage LocationCHAR4ConditionalConditionalConditional
RESBCHARGCHARGBatchCHAR10ConditionalConditionalConditional
RESBGPREISGPREISPriceNUMC15ConditionalConditionalConditional
RESBPEINHPEINHPrice UnitNUMC5ConditionalConditionalConditional
RESBWAERSWAERSCurrencyCHAR15ConditionalConditionalConditional
RSADDEKORGEKORGPurchasing OrganizationCHAR4ConditionalConditionalConditional
RESBEKGRPEKGRPPurchasing GroupCHAR3ConditionalConditionalConditional
RESBLIFNRLIFNRSupplierCHAR10ConditionalConditionalConditional
RESBINFNRINFNRPurchasing Info RecordCHAR10ConditionalConditionalConditional
RESBMATKLMATKLMaterial GroupCHAR9ConditionalConditionalConditional
RESBSAKNRSAKNRG/L AccountCHAR10ConditionalConditionalConditional
RESBWEMPFWEMPFGoods RecipientCHAR12ConditionalConditionalConditional
RESBABLADABLADUnloading PointCHAR25ConditionalConditionalConditional
RESBSTARTDATESTARTDATEService Performance Start DateDATS8ConditionalConditionalConditional
RESB

PERFORMANCE

PERIODSTARTTIME

PERFORMANCE

PERIODSTARTTIME

Service Performance Start Time (UTC)TIMS6ConditionalConditionalConditional
RESBENDDATEENDDATEService Performance End DateDATS8ConditionalConditionalConditional
RESB

PERFORMANCE

PERIODENDTIME

PERFORMANCE

PERIODENDTIME

Service Performance End Time (UTC)TIMS6ConditionalConditionalConditional
RESB

SERVICE

DURATION

SERVICE

DURATION

Duration of Lean ServiceNUMC5ConditionalConditionalConditional
RESB

SERVICE

DURATIONUNIT

SERVICE

DURATIONUNIT

Duration Unit for a Lean ServiceCHAR3ConditionalConditionalConditional
ESUHCOMMITMENTCOMMITMENTExpected ValueNUMC13ConditionalConditionalConditional
ESUHSUMLIMITSUMLIMITOverall LimitNUMC13ConditionalConditionalConditional


5. Work Order Operation Relationships

TableFieldData ElementField DescriptionData TypeLengthRequirement
YA01 (Reactive Maintenance)
Requirement
YA02 (Proactive Maintenance)
Requirement
YA03 (Project Order)
AFVCAUFNRAUFNROrder NumberCHAR12MandatoryMandatoryMandatory
AFVCVORNRVORNROperationCHAR4MandatoryMandatoryMandatory
AFVCAUFNRAUFNRAssigned OrderCHAR12MandatoryMandatoryMandatory
AFVCVORNRVORNRAssigned OperationCHAR4MandatoryMandatoryMandatory
AFABAOBARAOBARType of RelationshipCHAR2MandatoryMandatoryMandatory
AFABDAUERDAUERTime IntervalNUMC5ConditionalConditionalConditional
AFABZEINHZEINHUnitCHAR3ConditionalConditionalConditional


6. Work Order Object List

TableFieldData ElementField DescriptionData TypeLengthRequirement
YA01 (Reactive Maintenance)
Requirement
YA02 (Proactive Maintenance)
Requirement
YA03 (Project Order)
AUFKAUFNRAUFNROrder NumberCHAR12MandatoryMandatoryMandatory
OBJKSORTFSORTFSortCHAR20ConditionalConditionalConditional
IFLOTTPLNRTPLNRFunctional LocationCHAR30MandatoryMandatoryMandatory
OBJKEQUNREQUNREquipmentCHAR18ConditionalConditionalConditional
OBJKMATNRMATNRMaterialCHAR18ConditionalConditionalConditional
OBJKSERNRSERNRSerial NumberCHAR18ConditionalConditionalConditional
OBJKQMNUMQMNUMNotificationCHAR12MandatoryMandatoryMandatory
OBJKBAUTLBAUTLAssemblyCHAR18ConditionalConditionalConditional


 7. Work Order Confirmation

TableFieldData ElementField DescriptionData TypeLengthRequirement
YA01 (Reactive Maintenance)
Requirement
YA02 (Proactive Maintenance)
Requirement
YA03 (Project Order)
AUFKAUFNRAUFNROrder NumberCHAR12MandatoryMandatoryMandatory
AFVCVORNRVORNROperationCHAR4SystemSystemSystem
AFRUISMNWISMNWActual WorkNUMC7MandatoryMandatoryMandatory
AFRUAUERUAUERUFinal ConfirmationCHAR1ConditionalConditionalConditional
AFRUOFMNWOFMNWRemaining workNUMC7MandatoryMandatoryMandatory
AFRUISDDISDDWork Start DateDATS8MandatoryMandatoryMandatory
AFRUISDZISDZWork Start TimeTIMS6MandatoryMandatoryMandatory
AFRUIEDDIEDDWork Finish DateDATS8ConditionalConditionalConditional
AFRUIEDZIEDZWork Finish TimeTIMS6ConditionalConditionalConditional


8. Work Order Long Text Header

TableFieldData ElementField DescriptionData TypeLengthRequirement
YA01 (Reactive Maintenance)
Requirement
YA02 (Proactive Maintenance)
Requirement
YA03 (Project Order)
STXHTDOBJECTTDOBJECTTexts: application objectCHAR10MandatoryMandatoryMandatory
STXHTDNAMETDOBNAMENameCHAR70MandatoryMandatoryMandatory
STXH

TDID

TDID

Text IDCHAR4MandatoryMandatoryMandatory
STXHTDSPRASSPRASLanguage KeyLANG1MandatoryMandatoryMandatory


 9. Work Order Long Text Line

TableFieldData ElementField DescriptionData TypeLengthRequirement
YA01 (Reactive Maintenance)
Requirement
YA02 (Proactive Maintenance)
Requirement
YA03 (Project Order)
STXHTDOBJECTTDOBJECTTexts: application objectCHAR10MandatoryMandatoryMandatory
STXLTDNAMETDOBNAMENameCHAR70MandatoryMandatoryMandatory
STXL

TDID

TDID

Text IDCHAR4MandatoryMandatoryMandatory
STXLTDSPRASSPRASLanguage KeyLANG1MandatoryMandatoryMandatory
STXLTDFORMATTDFORMAT

Tag column

CHAR1

Mandatory

MandatoryMandatory
STXLROWCOUNTROWCOUNT

Row number

NUMC10MandatoryMandatoryMandatory
STXLTXLINETDLINE

Text Line

CHAR72MandatoryMandatoryMandatory


10. Work Order Operation Long Text Header

TableFieldData ElementField DescriptionData TypeLengthRequirement
YA01 (Reactive Maintenance)
Requirement
YA02 (Proactive Maintenance)
Requirement
YA03 (Project Order)
STXHTDOBJECTTDOBJECTTexts: application objectCHAR10MandatoryMandatoryMandatory
STXHTDNAMETDOBNAMENameCHAR70MandatoryMandatoryMandatory
STXH

TDID

TDID

Text IDCHAR4MandatoryMandatoryMandatory
STXHTDSPRASSPRASLanguage KeyLANG1MandatoryMandatoryMandatory


11. Work Order Operation Long Text Line

TableFieldData ElementField DescriptionData TypeLengthRequirement
YA01 (Reactive Maintenance)
Requirement
YA02 (Proactive Maintenance)
Requirement
YA03 (Project Order)
STXHTDOBJECTTDOBJECTTexts: application objectCHAR10MandatoryMandatoryMandatory
STXLTDNAMETDOBNAMENameCHAR70MandatoryMandatoryMandatory
STXL

TDID

TDID

Text IDCHAR4MandatoryMandatoryMandatory
STXLTDSPRASSPRASLanguage KeyLANG1MandatoryMandatoryMandatory
STXLTDFORMATTDFORMAT

Tag column

CHAR1

Mandatory

MandatoryMandatory
STXLROWCOUNTROWCOUNT

Row number

NUMC10MandatoryMandatoryMandatory
STXLTXLINETDLINE

Text Line

CHAR72MandatoryMandatoryMandatory



Data Cleansing

IDCriticalityError Message/Report DescriptionRuleOutputSource System
9005-001C1Open Work Order older than 1 month (based on Creation Date)Work Order (AFKO-AUFNR) based on the relevancy criteria and Creation date (AUFK-ERDAT) <= (Current Date - 30)Order No, Order Type, Plant, Description, Creation DatePF2, WP2
9005-002C1Open Priority Work Orders older than 2 weeks (based on Creation Date)

Work Order (AFKO-AUFNR) based on the relevancy criteria and Creation date (AUFK-ERDAT) <= (Current Date - 14) and Priority as list in the inclusion list (INC-Work Order Priority)

Order No, Order Type, Plant, Description, Operation/ Activity No, Creation DatePF2, WP2
9005-003C1Open Work Order with Blank Order DescriptionWork Order (AFKO-AUFNR) based on the relevancy criteria and Blank Short Text (AUFK-KTEXT = '')Order No, Order Type, PlantPF2, WP2
9005-004C1Open Work Order Operation with Blank Control KeyWork Order (AFKO-AUFNR) based on the relevancy criteria and Blank Control Key (AFVC-STEUS = '')Order No, Order Type, Plant, Description, Operation/ Activity NoPF2, WP2
9005-005C1Open Work Order with Blank Order Operation DescriptionWork Order (AFKO-AUFNR) based on the relevancy criteria and Blank Operation Short Text (AFVC-LTXA1 = '')Order No, Order Type, Plant, Description, Operation/ Activity NoPF2, WP2
9005-006C2Open Work Orders with unmapped Maintenance Revision

Work Order (AFKO-AUFNR) based on the relevancy criteria and Maintenance Revision (AFIH-REVNR) missing in Maintenance Planning Bucket mapping.

Note- Business to perform either of the below
a) removing the Revision from the WO, or
b) replanning the WO, or
c) creating a new revision for the WO

Order No, Order Type, Plant, Description, Maintenance RevisionPF2, WP2
9005-007C3Info Report: Open Work Orders with Open Purchase OrderWork Order (AFKO-AUFNR) based on the relevancy criteria having Purchase Order (EKKN-AUFNR is not Blank) and Purchase Order (EKKN-EBELN) which are Open as defined in CNV-9045 Open Purchase OrdersOrder No, Order Type, Plant, Description, Purchase Order No, Purchase Order ItemPF2, WP2
9005-008C3Info Report: Open Work Orders with Outstanding ReservationWork Order (AFKO-AUFNR) based on the relevancy criteria having Reservation (RESB-AUFNR is not Blank) and the Reservation is not deleted (RESB-XLOEK = '' ) and not flagged as final issue (RESB-KZEAR = '') and having outstanding quantity (RESB-BDMNG > RESB-ENMNG)Order No, Order Type, Plant, Description, Reservation No, Material No, Required Quantity, Withdrawal QuantityPF2, WP2
9005-009C3Info Report: Work Order not in scope for migration (not relevant)

Work Order (AFKO-AUFNR) based on the relevancy criteria (Exclusion)

Note: These Work Orders will not be not migrated

Order No, Order Type, Plant, DescriptionPF2, WP2
9005-010C3Info Report: Work Orders with Technically Completed (TECO) status that have external services assignedWork Order (AFKO-AUFNR) based on the relevancy criteria (Exclusion) and having Purchase Order (EKKN-AUFNR is not Blank) and Purchase Order (EKKN-EBELN) which are Open as defined in CNV-9045 Open Purchase Orders and having Service Items (EKPO-PSTYP = '9')Order No, Order Type, Plant, Description, Purchase Order, Purchase Order ItemPF2, WP2
9005-011C3Info Report: Open Work Orders with Functional Location and Assembly assigned and not EquipmentWork Order (AFKO-AUFNR) based on the relevancy criteria with (AFIH-ILOAN <>'') and (AFIH-EQUNR ='') and (AFIH-BAUTL <>'' and BAUTL not existing in Equipment Staging Mapping (OBJECT_ID))Order No, Order Type, Plant, Description, Functional Location, AssemblyPF2, WP2
9005-012C3Info Report: Open Work Orders without a Technical Object (Functional Location/ Equipment/ Assembly) assigned

Work Order (AFKO-AUFNR) based on the relevancy criteria with no Technical Object (Functional Location/ Equipment/ Assembly) assigned i,e (AFIH-ILOAN = '') and (AFIH-EQUNR = '') and (AFIH-BAUTL ='')

Note: These Work Orders will not be not migrated

Order No, Order Type, Plant, DescriptionPF2, WP2
9005-013C3Info Report: Open Work Orders with blank Basic End Date

Work Order (AFKO-AUFNR) based on the relevancy criteria with Basic End Date (AFKO-GLTRP) = '00000000'

Note: These Work Orders will not be not migrated

Order No, Order Type, Plant, Description, Basic Start Date, Basic End DatePF2, WP2
9005-01C3Info Report: Open Work Orders maintained as Sub Orders

Work Order (AFKO-AUFNR) based on the relevancy criteria for which Superior Order exists (AFKO-MAUFNR is not Blank)

Note: These Work Orders will not be not migrated

Order No, Order Type, Plant, DescriptionPF2, WP2

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

 

Conversion Process

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

The following represents the high-level process for Source System Extraction:

The following represents the high-level process for DCT:

Collection will be done manually in the Data Collection Template for sites not on SAP- PF2 or WP2 systems 


Data Privacy and Sensitivity

Not Applicable


Extraction

Extract data from a source into Advanced Data Migration and Management (ADMM). There are 2 possibilities:

  1. The data exists. connects to the source and loads the data into the repository. There are 3 methods: 
    1. Perform full data extraction from relevant tables in the source system(s).
    2. Perform extraction through the application layer.
    3. Only if ADMM cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
  2. The data does not exist (or cannot be converted from its current state). The data is manually collected by the business directly in the repository. This is to be conducted using DCT (Data Collection Template) in Advanced Data Migration and Management (ADMM).

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)

Target Ready Data Collection Template will be created for data with exception of some fields which require transformation as mentioned in the transformation rule. 

Note: All rules specified below should be documented as a tooltip in the DC Page.

Format:

  • Line 1: Mandatory / Conditional
  • Line 2: Remaining text

 

1. Work Order Header Data Construction Rules

Field NameField DescriptionRule
WERKSPlant

Mandatory.

Populate the Plant to which the Work Order is associated.

Allowed values: List from Value Mapping - Plant (where Maintenance Plant = Yes)

zLegacyAUFNRLegacy Order Number

Mandatory.

AUARTOrder Type

Mandatory.

Allowed values: 

YA01    Reactive Maintenance
YA02    Proactive Maintenance
YA03    Project Orders

KCHARDescription

Mandatory.

Populate with a meaningful Order Description. 

Ensure that it does not include any of below characters: 

;        Semi-colon
:        Colon
::        Double Colon
?        Question Mark
/        Forward Slash
@        At sign
&        Ampersand
=        Equal Sign
+        Plus Sign
$        Dollar Sign
%        Percent
|        Vertical Bar
[]        Left or Right Square Bracket
"        Double Quotes

PRIOKPriority

Mandatory.

Needs to be selected from value list (T356).

GSTRPBasic Start Date

Mandatory.

Populate the Work Order planned start date in YYYYMMDD format. 

GSUZPBasic Start Time

Mandatory.

Populate the Work Order planned start time in HHMMSS format. 

GLTRPBasic End Date

Mandatory.

Populate the Work Order planned end date in HHMMSS format. 

GLUZPBasic End Time

Mandatory.

Populate the Work Order planned end time in HHMMSS format. 

TPLNRFunctional Location

Mandatory.

Populate the Functional Location associated to the asset.

Value must exist in Functional Location DCT. 

EQUNREquipment

Conditional.

Populate if the Asset being maintained is an Equipment. Otherwise, leave the field blank.

Value must exist in Equipment DCT.

QMNUMAssigned Notification

Mandatory.

Populate the Notification number registering the issue. 

Value must exist in Notification DCT.

ILARTMaintenance Activity Type

Mandatory.

Allowed Values:

M01    INSPECT
M02    TEST
M03    CALIBRATE
M04    PRELIMINARY STUDIES
M05    COMMISSION
M06    CLEAN
M07    DEMOLISH
M08    REPAIR
M09    REPLACE
M10    LUBRICATE
M11    INSTALL
M12    FABRICATE
M13    INSULATE
M14    RESET
M15    SERVICE
M16    MODIFY

PROIDWBS Element (Acc Assignment)

Conditional.

  • Populate only for Project Work Orders 
  • Should exist in either WBS Element Number mapping or WBS DCT.

 

2. Work Order Operation Data Construction Rules

Field NameField DescriptionRule
WERKSPlant

Mandatory.

Populate the Plant to which the Work Order is associated.

Allowed values: List from Value Mapping - Plant where Maintenance Plant = Yes

zLegacyAUFNRLegacy Order Number

Mandatory.

Key to link to Work Order. Must exist in Order Header DCT.

zLegacyVORNRLegacy Operation Number

Mandatory.

Sequence number that uniquely identifies an operation in the order.

Populate in increments of 10 (e.g., 0010, 0020, 0030) for multiple operations. 

LTXA1Operation Description

Mandatory.

Populate with a meaningful description for the Work Order Operation.

;        Semi-colon
:        Colon
::        Double Colon
?        Question Mark
/        Forward Slash
@        At sign
&        Ampersand
=        Equal Sign
+        Plus Sign
$        Dollar Sign
%        Percent
|        Vertical Bar
[]        Left or Right Square Bracket
"        Double Quotes

PERNRPerson Responsible

Conditional

Populate the Personnel Number of the person responsible/assigned to perform the operation.

Must be a valid PERNR in HR master data (i.e exists in PA0001)

STEUSControl Key

Mandatory.

Populate appropriate Control Key based on the how the operation is to be processed (internal/external, etc.).

Needs to be selected from Value List (T430) with pattern 'PMXX'

SAKTOCost Element

Conditional.

Populate the Cost posting account for external services/materials depending on process.

Needs to be selected from value list (CSKA)

EKORGPurchasing Organisation

Conditional.

Populate Purchasing org responsible for procurement activities.

Needs to be selected from value list (T024E)

EKGRPPurchasing Group

Conditional.

Populate Buyer/group responsible for procurement.

Needs to be selected from value list (T024)

MATKLMaterial Group

Conditional.

Populate Material Group for the required Materials/ Services. 

Needs to be selected from value list (T023)

ANLZUSystem Condition

Conditional.

Populate Condition of the System/ Asset during the maintenance activity. 

Needs to be selected from value list (T375M)

ARBEIWork

Mandatory.

Populate effort (e.g., labour hours) for the Operation (as per routing / order operation unit standards).

Numeric value only. Cannot be 0. 

INDETCalculation Key

Mandatory.

Allowed values: Select from the below list - 

Maintain manually
Calculate duration
Calculate work
Calculate number of capacities

DAUNODuration

Conditional.

Populate in information exists. 

ANZZLRequired CapacitiesMandatory. Must be an integer value. Cannot be 0.
EINSAStart Constraint

Conditional.

Populate only if Start Constraint logic is used to be used for scheduling in target. Otherwise, leave the field blank.

Allowed values: Select from the below list - 

Must start on
Cannot start before
Cannot start later
Start from resource planning

NTANFStart Constraint Date

Conditional.

Date on which the constrained start is required. 

Populate only if EINSA is populated. Otherwise, leave the field blank.

Date Format DDMMYYYY.

NTANZStart Constraint Time

Conditional.

Time for the constrained start

Populate only if EINSA and NTANF is populated. Otherwise, leave the field blank. 

Time Format HHMMSS. 

EINSEFinish Constraint

Conditional. Populate only if Finish Constraint logic is to be used for scheduling in target. Otherwise, leave the field blank.

Allowed values: Select from the below list - 

Must finish on
Cannot finish before
Finish not later
Finish from confirmation

NTENDFinish Constraint Date

Conditional.

Date on which the constrained finish is required.

Populate only if EINSE is populated. Valid Date. Otherwise, leave the field blank.

Date Format DDMMYYYY. 

NTENZFinish Constraint Time

Conditional.

Time for the constrained finish.

Populate only if EINSE and NTEND is populated. Valid Time. Otherwise, leave the field blank.

Time Format HHMMSS.

MGVRGOperation Quantity

Conditional.

Populate only if the Operation is quantity-based (e.g., service quantity) in the target design. Otherwise, leave the field blank.

Numeric value only. Cannot be 0.

MEINHUnit

Conditional.

Populate only if MGVRG is populated. Otherwise, leave the field blank.

Needs to be selected from value list (T006)

PREISPrice

Conditional.

Populate price amount only if the Operation is externally procured / service-related. Otherwise, leave the field blank.

Numeric value only. Cannot be negative. 

PEINHPrice Unit

Conditional.

Number of units to which the price refers. 

Populate only if PREIS is populated. Otherwise, leave the field blank.

Must be an integer value. Cannot be 0. 

LIFNRVendor

Conditional.

Populate external vendor for the external service/ material if information exist. Otherwise, leave the field blank.

Value must exist in Value Mapping: Vendor Number 

WEMPFRecipient

Conditional.

Populate Goods recipient name for purchasing documents if information exists. Otherwise, leave the field blank.

BEDNRTracking Number

Conditional.

Populate tracking number for PR/PO creation if information exists. Otherwise, leave the field blank.

SORTLSort Term

Conditional.

Populate sort term for the procurement scenario if information exists. Otherwise, leave the field blank.

AFNAMName of Requisitioner

Conditional.

Populate name of the Person requesting procurement if information exists. Otherwise, leave the field blank.


3. Work Order Operation Components Data Construction Rules  

Field NameField DescriptionRule
WERKSPlant

Mandatory.

Populate the Plant to which the Work Order is associated.

Allowed values: List from Value Mapping - Plant where Maintenance Plant = Yes

zLegacyAUFNRLegacy Order Number

Mandatory.

Key to link to Work Order

zLegacyVORNRLegacy Operation Number

Mandatory.

Key to link to Work Order Operation. Key to link to Work Order. Must exist in Order Operation DCT.

POSNRItem Number of Reservation

Mandatory.

Sequence number that uniquely identifies Component assigned in the Order Operation.

Populate in increments of 10 (e.g., 0010, 0020, 0030) for multiple Materials. 

MATNRMaterial

Conditional

Populate with legacy Material number for the component line.

Value must exist in Value Mapping: Material Master

POTX1Description

Conditional

Populate with a meaningful description for the component line item.

  • If Material Master exists (MATNR populated), leave blank
  • If Free-text material/service (no MATNR), populate from legacy component/PR/PO line description if existing
POSTPItem Category

Mandatory.

Populate a valid component item category from the below. 

Item CategoryDescriptionProcurement Via
LStock ItemInventory
NNon-Stock ItemPurchase Req
TText ItemPurchase Req
EEnhanced LimitPurchase Req

Note - If populating data for a lean service, the values could only be "N" (Non-stock) or "E" (Enhanced Limit).

BDMNGQuantity

Mandatory.

Populate Component quantity requested for the component line.

MEINSUnit

Mandatory.

Populate if BDMNG is populated.

Needs to be selected from value list (T006)

NO_DISPReservation Relevance / Generation of Purchase Requisition

Mandatory.

Populate from the below value list as applicable. 

  • 1 (Never): Reservations/PRs are not created automatically. Requires manual intervention to initiate procurement.
  • 2 (From Release): Reservations/PRs are generated only when the maintenance order is released (system status REL). This is the most common setting to prevent procurement for planned, but not yet approved, work.
  • 3 (Immediately): Reservations for stock items (Item Cat 'L') are created immediately upon saving the order, or PRs for non-stock items (Item Cat 'N') are generated instantly, regardless of order release.
WERKSPlant

Conditional

Populate the component plant.

Allowed values: List from Value Mapping - Plant where Maintenance Plant = Yes

BDTERRequirements Date

Conditional

Populate the date on which the requested quantity of material is required.

If populating this field ensure the Manual Maintenance of Requirement Date is set as 'X' (Yes).

Date Format DDMMYYYY. 

KZMPFManual Reqmt Date Indicator

Conditional

Populate Maintenance of Requirement Date Flag from the below list.

'' = NO
'X' = YES

LGORTStorage Location

Conditional

Populate legacy Storage Location from where stock is planned to be issued. 

Value must exist in Value Mapping: Storage Location

CHARGBatch

Conditional

Populate legacy batch if material is batch-managed. Otherwise, leave the field blank.

Value must exist in Value Mapping: Batch Class 023

GPREISPrice

Conditional

Populate price for the external component/service line as applicable.

PEINHPrice Unit

Conditional

Populate Number of units to which the price refers.

Example
If 10 gallons of gasoline cost $12.00, the price unit is 10.

Populate only if GPREIS is populated. Otherwise, leave the field blank.

Must be an integer value. Cannot be 0. 

WAERSCurrency

Conditional

Populate the currency key for the component price. Must be maintained if GPREIS is populated.

Needs to be selected from value list (TCURC)

EKORGPurchasing Organisation

Conditional.

Populate Purchasing org responsible for procurement activities.

Needs to be selected from value list (T024E)

EKGRPPurchasing Group

Conditional.

Populate Buyer/group responsible for procurement.

Needs to be selected from value list (T024)

LIFNRSupplier

Conditional.

Populate external vendor for the service/ material if information exist. Otherwise, leave the field blank.

Value must exist in Value Mapping: Vendor Number 

INFNRPurchasing Info Record

Conditional.

Populate Number of purchasing info record if information exists. Otherwise, leave the field blank.

Value must exist in Value Mapping: Purchasing Info Record Number

MATKLMaterial Group

Conditional.

Populate Material Group if information exists. Otherwise, leave the field blank.

Value must exist in Value Mapping: Material Group

SAKNRG/L Account

Conditional

Populate G/L account as required for account assignment.

Value must exist in Value Mapping: GL Account

WEMPFGoods Recipient

Conditional

Populate Goods recipient name for purchasing documents if information exists. Otherwise, leave the field blank.

ABLADUnloading Point

Conditional

Populate unloading point if information exists. Otherwise, leave the field blank.

STARTDATEService Performance Start Date

Conditional

To be populated for Lean Service Component Only. 

Populate performance start date of the Lean Service item. Leave blank if KZMPF (Manual Reqmt Date Indicator) = ''

Date Format DDMMYYYY.

PERFORMANCE
PERIODSTARTTIME
Service Performance Start Time (UTC)

Conditional

To be populated for Lean Service Component Only. 

Populate the start time of the lean service. Only populate if STARTDATE is maintained, else leave blank.

Time Format HHMMSS.

ENDDATEService Performance End Date

Conditional

To be populated for Lean Service Component Only. 

Populate performance start end of the Lean Service item. Leave blank if KZMPF (Manual Reqmt Date Indicator) = ''

Date Format DDMMYYYY.

PERFORMANCE
PERIODENDTIME
Service Performance End Time (UTC)

Conditional

To be populated for Lean Service Component Only. 

Populate the end time of the lean service. Only populate if ENDDATE is maintained, else leave blank.

Time Format HHMMSS.

SERVICE
DURATION
Duration of Lean Service

Conditional

To be populated for Lean Service Component Only. 

Populate the duration value of the Lean Service. Leave blank if Component is not a Lean Service.

SERVICE
DURATIONUNIT
Duration Unit for a Lean Service

Conditional

To be populated for Lean Service Component Only. 

Populate Lean Service duration unit (e.g., Hour, Day).

Needs to be selected from value list (T006)

COMMITMENTExpected Value

Conditional

Populate expected value for the Lean Service.

The value must be maintained, if the item category "E" (= Enhanced Limit) has been set for the item (lean service).

Please make sure, that this value is less than or equal to the overall limit.

SUMLIMITOverall Limit

Conditional

Populate maximum expenditure value for the Lean Service. 

The value must be maintained (mandatory), if the item category "E" (= Enhanced Limit) has been set for the item (lean service).

Please ensure, that this value is greater than or equal to the expected value.


4. Work Order Operation Relationships Data Construction Rules  

Field NameField DescriptionRule
WERKSPlant

Mandatory.

Populate the Plant to which the Work Order is associated.

Allowed values: List from Value Mapping - Plant where Maintenance Plant = Yes

zLegacyAUFNR

Legacy Order Number (Successor)

Mandatory.

Populate with the successor order number to which the successor operation belongs.

VORNRSuccessor Operation Number

Mandatory.

Populate with the successor operation number within the successor order.

zLegacyAUFNRLegacy Order Number (Predecessor)Populate with the legacy predecessor order number to which the predecessor operation belongs.
VORNRPredecessor Operation Number

Mandatory.

Populate with the legacy predecessor operation number within the predecessor order.

AOBARType of Relationship

Mandatory.

Populate relationship type between predecessor and successor operations as required the below list. 

FS - Finish-to-Start

SS - Start-to-Start

FF - Finish-to-Finish

SF - Start-to-Finish

DAUERTime Interval

Conditional.

Populate lag/lead (positive/negative) duration value between operations.

ZEINHUnit

Conditional.

Populate duration unit (e.g., Hour, Day) only when DAUER has been populated. 

Allowed values from T006 to be populated


5. Work Order Object List Data Construction Rules  

Field NameField DescriptionRule
WERKSPlant

Mandatory.

Populate the Plant to which the Work Order is associated.

Allowed values: List from Value Mapping - Plant where Maintenance Plant = Yes

zLegacyAUFNRLegacy Order Number

Mandatory.

Key to link to Work Order

OBZAECounter

Mandatory.

Populate with a sequential counter per AUFNR representing each object list item (e.g., 0001, 0002…).

SORTFSort

Conditional

Populate a sort key to control grouping of object list items (e.g., by object type, priority, hierarchy). Else leave blank.

TPLNRFunctional Location

Mandatory.

Populate with the legacy Functional Location assigned to the order.

Value must exist in Functional Location mapping. 

EQUNREquipment

Conditional.

Populate with the legacy Equipment assigned to the order.

Value must exist in Equipment Mapping. 

MATNRMaterial

Conditional

Populate with the legacy Material assigned to the order.

Value must exist in Material Master Mapping. 

BAUTLAssembly

Conditional.

Populate if information exists. Otherwise, leave the field blank.


6. Work Order Confirmation Data Construction Rules  

Field NameField DescriptionRule
WERKSPlant

Mandatory.

Populate the Plant to which the Work Order is associated.

Allowed values: List from Value Mapping - Plant where Maintenance Plant = Yes

zLegacyAUFNR

Legacy Order Number

Mandatory.

Key to link to Work Order

VORNR

Operation Number

Mandatory.

Key to link to Work Order Operation

ISMNWActual Work

Mandatory.

Populate the actual work quantity confirmed for the operation (e.g., labour hours).

AUERUFinal Confirmation

Conditional.

Populate ‘X’ when the operation is to be marked finally confirmed (no more confirmations expected). Else blank.

OFMNWRemaining work

Mandatory.

Populate remaining work still expected for the operation after this confirmation. If operation finally confirmed, set to 0 (or blank per design).

ISDDWork Start Date

Mandatory.

Populate the actual work start date for the confirmation.

ISDZWork Start Time

Mandatory.

Populate actual work start time for the confirmation.

IEDDWork Finish Date

Conditional.

Populate the actual work finish date for the confirmation.

IEDZWork Finish Time

Conditional.

Populate actual work finish time for the confirmation.


7. Work Order Long Text Line Data Construction Rules  

Field NameField DescriptionRule
WERKSPlant

Mandatory.

Populate the Plant to which the Work Order is associated.

Allowed values: List from Value Mapping - Plant where Maintenance Plant = Yes

zLegacyAUFNR

Legacy Order Number

Mandatory.

Key to link to Work Order

ROWCOUNT

Row number

Mandatory.

Must be unique and ascending sequential number

TDSPRASLanguage Key

Mandatory.

Must be either one of the following: English(E) , French(F), Italian(I), Mandarin(1), Portuguese(including Brazilian Portuguese)(P), German(D) and Spanish(S)

TXLINE

Text Line

Conditional.

Free Text. Blanks are allowed


8. Work Order Operation Long Text Line Data Construction Rules 

Field NameField DescriptionRule
WERKSPlant

Mandatory.

Populate the Plant to which the Work Order is associated.

Allowed values: List from Value Mapping - Plant where Maintenance Plant = Yes

zLegacyAUFNR

Legacy Order Number

Mandatory.

Key to link to Work Order

VORNR

Operation Number

Mandatory.

Key to link to Work Order Operation

ROWCOUNT

Row number

Mandatory.

Must be unique and ascending sequential number

TDSPRASLanguage Key

Mandatory.

Must be either one of the following: English(E) , French(F), Italian(I), Mandarin(1), Portuguese(including Brazilian Portuguese)(P), German(D) and Spanish(S)

TXLINE

Text Line

Conditional.

Free Text. Blanks are allowed

Extraction Dependencies

Item #Step DescriptionTeam Responsible

1

Not Applicable



Transformation

The Target fields are mapped to the applicable Legacy field that will be its source, this is a 3-way activity involving the Business, Functional team and Data team.  This identifies the transformation activity required to allow ADMM 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 – 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 error reports

Business/Data owner

7

Generate load files

Syniti


Transformation Rules

Note: Unless otherwise specified, the transformation rules applies to YA01, YA02 and YA03 Order Types

1.  Work Order Header Transformation Rule (ECC)

Rule #Source SystemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget Description

Transformation Logic

1----S/4 HANAAUFKAUFNROrder Number

System (Internal numbering)

2PF2, WP2AUFKAUARTOrder TypeS/4 HANAAUFKAUARTOrder TypeDerive as per Value Mapping: Work Order Type
3PF2, WP2AUFKKCHARDescriptionS/4 HANAAUFKKCHARDescriptionDirect Mapping
4PF2, WP2AFIHPRIOKPriorityS/4 HANAAFIHPRIOKPriorityDirect Mapping
5PF2, WP2AFKOGSTRPBasic Start DateS/4 HANAAFKOGSTRPBasic Start DateDirect Mapping
6PF2, WP2AFKOGSUZPBasic Start TimeS/4 HANAAFKOGSUZPBasic Start TimeDirect Mapping
7PF2, WP2AFKOGLTRPBasic End DateS/4 HANAAFKOGLTRPBasic End DateDirect Mapping
8PF2, WP2AFKOGLUZPBasic End TimeS/4 HANAAFKOGLUZPBasic End TimeDirect Mapping
9PF2, WP2IFLOTTPLNRFunctional LocationS/4 HANAIFLOTTPLNRFunctional LocationDerive as per Value Mapping: Functional Location
10PF2, WP2AFIHEQUNREquipmentS/4 HANAAFIHEQUNREquipmentDerive as per Value Mapping: Equipment
11PF2, WP2AFIHQMNUMAssigned NotificationS/4 HANAAFIHQMNUMAssigned NotificationDerive as per Value Mapping: Notification
12PF2, WP2AFIHREVNRMaintenance Event/ RevisionS/4 HANAAFIHREVNRMaintenance Event/ RevisionDefault to blank
13PF2, WP2AFIHILARTMaintenance Activity TypeS/4 HANAAFIHILARTMaintenance Activity TypeDerive as per Value Mapping: Maintenance Activity Type
14----S/4 HANACRHDARBPLWork Center
  1. If EQUNR is not blank then derive from S4 EQUZ-GEWRK (Use logic EQUZ-GEWRK = CRHD-GEWRK to get CRHD-ARBPL)
  2. If EQUNR is blank then derive from S4 IFLOT-GEWRK (Use logic IFLOT-GEWRK = CRHD-GEWRK to get CRHD-ARBPL)
15----S/4 HANACRHDWERKSWork Center PlantDerive the CRHD-WERKS from the derived CRHD-ARBPL value
16----S/4 HANAAFIHIWERKPlanning Plant
  1. If EQUNR is not blank then derive from S4 EQUZ-IWERK
  2. If EQUNR is blank then derive from S4 IFLOT-IWERK
17----S/4 HANAAFIHINGPRPlanner group
  1. If EQUNR is not blank then derive from S4 EQUZ-INGRP
  2. If EQUNR is blank then derive from S4 IFLOT-INGRP
18----S/4 HANAAUFKWERKSMaintenance Plant

Copy from IWERK (Planning Plant)

19----S/4 HANAILOABEBERPlant Section
  1. If EQUNR is not blank then derive from S4 ILOA-BEBER (Use logic EQUZ-ILOAN = ILOA-ILOAN)
  2. If EQUNR is blank then derive from S4 ILOA-BEBER (Use logic IFLOT-ILOAN = ILOA-ILOAN)
20----S/4 HANAILOABUKRSCompany Code
  1. If EQUNR is not blank then derive from S4 ILOA-BUKRS (Use logic EQUZ-ILOAN = ILOA-ILOAN)
  2. If EQUNR is blank then derive from S4 ILOA-BUKRS (Use logic IFLOT-ILOAN = ILOA-ILOAN)
21PF2, WP2ILOAPROIDWBS Element (Acc Assignment)S/4 HANAILOAPROIDWBS Element (Acc Assignment)

If Legacy PROID exists in either of the below ADMM Deployment Prep reports with ILOA-PROID = Report-POSID, where Report-ZACTIVE_PROJECT_OPEN_CLOSED = 'OPEN' and Report-ZACTIVE= 'TRUE'

-I2M_ECC_SAPWP2_WBS_REPORT
-I2M_ECC_SAPPF2_WBS_REPORT

then derive using Value Mapping : WBS Element Number. Else default to blank

22----S/4 HANAILOAKOSTLCost Center

If Legacy PROID doesn't exists as per the rule mentioned above, then derive Cost Centre from -

  1. If EQUNR is not blank then derive from S4 ILOA-KOSTL (Use logic EQUZ-ILOAN = ILOA-ILOAN)
  2. If EQUNR is blank then derive from S4 ILOA-KOSTL (Use logic IFLOT-ILOAN = ILOA-ILOAN)


2.  Work Order Header Transformation Rule (DCT)

Rule #Source SystemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget Description

Transformation Logic

1DCTAUFKzLegacyAUFNRLegacy Order NumberS/4 HANAAUFKAUFNROrder Number

System (Internal numbering)

2DCTAUFKAUARTOrder TypeS/4 HANAAUFKAUARTOrder TypeDirect Mapping
3DCTAUFKKCHARDescriptionS/4 HANAAUFKKCHARDescriptionDirect Mapping
4DCTAFIHPRIOKPriorityS/4 HANAAFIHPRIOKPriorityDirect Mapping
5DCTAFKOGSTRPBasic Start DateS/4 HANAAFKOGSTRPBasic Start DateDirect Mapping
6DCTAFKOGSUZPBasic Start TimeS/4 HANAAFKOGSUZPBasic Start TimeDirect Mapping
7DCTAFKOGLTRPBasic End DateS/4 HANAAFKOGLTRPBasic End DateDirect Mapping
8DCTAFKOGLUZPBasic End TimeS/4 HANAAFKOGLUZPBasic End TimeDirect Mapping
9DCTIFLOTTPLNRFunctional LocationS/4 HANAIFLOTTPLNRFunctional LocationDirect Mapping
10DCTAFIHEQUNREquipmentS/4 HANAAFIHEQUNREquipmentDirect Mapping
11DCTAFIHQMNUMAssigned NotificationS/4 HANAAFIHQMNUMAssigned NotificationDirect Mapping
12----S/4 HANAAFIHREVNRMaintenance Event/ RevisionDefault to blank
13----S/4 HANAAFIHILARTMaintenance Activity TypeDirect Mapping
14----S/4 HANACRHDARBPLWork Center
  1. If EQUNR is not blank then derive from S4 EQUZ-GEWRK (Use logic EQUZ-GEWRK = CRHD-GEWRK to get CRHD-ARBPL)
  2. If EQUNR is blank then derive from S4 IFLOT-GEWRK (Use logic IFLOT-GEWRK = CRHD-GEWRK to get CRHD-ARBPL)
15----S/4 HANACRHDWERKSWork Center PlantDerive the S4 CRHD-WERKS from the derived S4 CRHD-ARBPL value
16----S/4 HANAAFIHIWERKPlanning Plant
  1. If EQUNR is not blank then derive from S4 EQUZ-IWERK
  2. If EQUNR is blank then derive from S4 IFLOT-IWERK
17----S/4 HANAAFIHINGPRPlanner group
  1. If EQUNR is not blank then derive from S4 EQUZ-INGRP
  2. If EQUNR is blank then derive from S4 IFLOT-INGRP
18----S/4 HANAAUFKWERKSMaintenance Plant

Copy from IWERK (Planning Plant)

19----S/4 HANAILOABEBERPlant Section
  1. If EQUNR is not blank then derive from S4 ILOA-BEBER (Use logic EQUZ-ILOAN = ILOA-ILOAN)
  2. If EQUNR is blank then derive from S4 ILOA-BEBER (Use logic IFLOT-ILOAN = ILOA-ILOAN)
20----S/4 HANAILOABUKRSCompany Code
  1. If EQUNR is not blank then derive from S4 ILOA-BUKRS (Use logic EQUZ-ILOAN = ILOA-ILOAN)
  2. If EQUNR is blank then derive from S4 ILOA-BUKRS (Use logic IFLOT-ILOAN = ILOA-ILOAN)
21DCTILOAPROIDWBS Element (Acc Assignment)S/4 HANAILOAPROIDWBS Element (Acc Assignment)

Direct mapping for Order Type (AUART) = 'YA03', Else Default to blank

22-ILOAKOSTLCost CenterS/4 HANAILOAKOSTLCost Center

If Legacy PROID doesn't exists as per the rule mentioned above, then derive Cost Centre from -

  1. If EQUNR is not blank then derive from S4 ILOA-KOSTL (Use logic EQUZ-ILOAN = ILOA-ILOAN)
  2. If EQUNR is blank then derive from S4 ILOA-KOSTL (Use logic IFLOT-ILOAN = ILOA-ILOAN)


3.  Work Order Operation Transformation Rule (ECC)

Rule #Source SystemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget Description

Transformation Logic

1----S/4 HANAAFVCAUFNROrder Number

System (Internal numbering)

2PF2, WP2AFVCVORNRLegacy Operation/ActivityS/4 HANAAFVCVORNROperation/ActivityDIrect Mapping
3PF2, WP2AFVCLTXA1Operation DescriptionS/4 HANAAFVCLTXA1Operation DescriptionDIrect Mapping
4PF2, WP2CRHDARBPLWork CenterS/4 HANACRHDARBPLWork CenterDerive as per Value Mapping: Work Centre A2D
5PF2, WP2CRHDWERKSWork Center PlantS/4 HANACRHDWERKSWork Center PlantDerive the S4 CRHD-WERKS from the derived S4 CRHD-ARBPL value
6PF2, WP2AFVCPERNRPerson ResponsibleS/4 HANAAFVCPERNRPerson Responsible

Derive as per Value Mapping: Employee Personnel.

7PF2, WP2AFVCSTEUSControl KeyS/4 HANAAFVCSTEUSControl Key

Derive as per Value Mapping: Work Order Operation Control Type

8PF2, WP2AFVCSAKTOCost ElementS/4 HANAAFVCSAKTOCost Element

Derive as per Value Mapping: GL Account

9PF2, WP2AFVCEKORGPurchasing OrganizationS/4 HANAAFVCEKORGPurchasing Organisation

Derive as per Value Mapping: Purchasing Organization

10PF2, WP2AFVCEKGRPPurchasing GroupS/4 HANAAFVCEKGRPPurchasing Group

Derive as per Value Mapping: Purchasing Group

11PF2, WP2AFVCMATKLMaterial GroupS/4 HANAAFVCMATKLMaterial GroupDerive as per Value Mapping: Material Group
12PF2, WP2AFVCANLZUSystem ConditionS/4 HANAAFVCANLZUSystem ConditionDerive as per Value Mapping: Work Order System Condition
13PF2, WP2AFVCLARNTActivity TypeS/4 HANAAFVCLARNTActivity TypeDerive Activity Type (CRCO-LSTAR) from Target Work Centre (CRHD-ARBPL)
14PF2, WP2AFVVARBEIWorkS/4 HANAAFVVARBEIWorkDIrect Mapping
15PF2, WP2AFVVARBEHWork UnitS/4 HANAAFVVARBEHWork UnitDIrect Mapping
16PF2, WP2AFVCINDETCalculation KeyS/4 HANAAFVCINDETCalculation KeyDIrect Mapping
17PF2, WP2AFVVDAUNODurationS/4 HANAAFVVDAUNODurationDIrect Mapping
18PF2, WP2AFVVDAUNEDuration UnitS/4 HANAAFVVDAUNEDuration UnitDIrect Mapping
19PF2, WP2AFVCANZZLRequired CapacitiesS/4 HANAAFVCANZZLRequired CapacitiesDIrect Mapping
20PF2, WP2AFVVEINSAStart ConstraintS/4 HANAAFVVEINSAStart ConstraintDIrect Mapping
21PF2, WP2AFVVNTANFStart Constraint DateS/4 HANAAFVVNTANFStart Constraint DateDIrect Mapping
22PF2, WP2AFVVNTANZStart Constraint TimeS/4 HANAAFVVNTANZStart Constraint TimeDIrect Mapping
23PF2, WP2AFVVEINSEFinish ConstraintS/4 HANAAFVVEINSEFinish ConstraintDIrect Mapping
24PF2, WP2AFVVNTENDFinish Constraint DateS/4 HANAAFVVNTENDFinish Constraint DateDIrect Mapping
25PF2, WP2AFVVNTENZFinish Constraint TimeS/4 HANAAFVVNTENZFinish Constraint TimeDIrect Mapping
26PF2, WP2AFVVMGVRGOperation QuantityS/4 HANAAFVVMGVRGOperation QuantityDIrect Mapping
27PF2, WP2AFVVMEINHOperation Quantity UnitS/4 HANAAFVVMEINHOperation Quantity UnitDIrect Mapping
28PF2, WP2AFVCPREISPriceS/4 HANAAFVCPREISPriceDIrect Mapping
29PF2, WP2AFVCWAERSCurrencyS/4 HANAAFVCWAERSCurrencyDIrect Mapping
30PF2, WP2AFVCPEINHPrice UnitS/4 HANAAFVCPEINHPrice UnitDIrect Mapping
31PF2, WP2AFVCLIFNRVendorS/4 HANAAFVCLIFNRVendorDerive as per Value Mapping: Vendor Number
34PF2, WP2AFVCWEMPFRecipientS/4 HANAAFVCWEMPFRecipientDIrect Mapping
35PF2, WP2AFVCBEDNRTracking NumberS/4 HANAAFVCBEDNRTracking NumberDIrect Mapping
36PF2, WP2AFVCSORTLSort TermS/4 HANAAFVCSORTLSort TermDIrect Mapping
37PF2, WP2AFVCINFNRPurchasing Info RecordS/4 HANAAFVCINFNRPurchasing Info RecordDerive as per Value Mapping: Purchasing Info Record Number
38PF2, WP2AFVCAFNAMName of RequisitionerS/4 HANAAFVCAFNAMName of RequisitionerDIrect Mapping
39PF2, WP2AFVCABLADUnloading PointS/4 HANAAFVCABLADUnloading PointDIrect Mapping
40PF2, WP2AFVVPLIFZPlanned Delivery Time - DayS/4 HANAAFVVPLIFZPlanned Delivery Time - DayDIrect Mapping


4.  Work Order Operation Transformation Rule (DCT)

Rule #Source SystemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget Description

Transformation Logic

1DCTAFVCzLegacyAUFNRLegacy Order NumberS/4 HANAAFVCAUFNROrder Number

DIrect Mapping

2DCTAFVCzLegacyVORNRLegacy Operation/ActivityS/4 HANAAFVCVORNROperation/ActivityDIrect Mapping
3DCTAFVCLTXA1Operation DescriptionS/4 HANAAFVCLTXA1Operation DescriptionDIrect Mapping
4DCTCRHDARBPLWork CenterS/4 HANACRHDARBPLWork CenterDIrect Mapping
5DCTCRHDWERKSWork Center PlantS/4 HANACRHDWERKSWork Center PlantDIrect Mapping
6DCTAFVCPERNRPerson ResponsibleS/4 HANAAFVCPERNRPerson Responsible

DIrect Mapping

7DCTAFVCSTEUSControl KeyS/4 HANAAFVCSTEUSControl Key

DIrect Mapping

8DCTAFVCSAKTOCost ElementS/4 HANAAFVCSAKTOCost Element

DIrect Mapping

9DCTAFVCEKORGPurchasing OrganizationS/4 HANAAFVCEKORGPurchasing Organisation

DIrect Mapping

10DCTAFVCEKGRPPurchasing GroupS/4 HANAAFVCEKGRPPurchasing Group

DIrect Mapping

11DCTAFVCMATKLMaterial GroupS/4 HANAAFVCMATKLMaterial GroupDIrect Mapping
12DCTAFVCANLZUSystem ConditionS/4 HANAAFVCANLZUSystem ConditionDIrect Mapping
13DCTAFVCLARNTActivity TypeS/4 HANAAFVCLARNTActivity TypeDIrect Mapping
14DCTAFVVARBEIWorkS/4 HANAAFVVARBEIWorkDIrect Mapping
15DCTAFVVARBEHWork UnitS/4 HANAAFVVARBEHWork UnitDIrect Mapping
16DCTAFVCINDETCalculation KeyS/4 HANAAFVCINDETCalculation KeyDIrect Mapping
17DCTAFVVDAUNODurationS/4 HANAAFVVDAUNODurationDIrect Mapping
18DCTAFVVDAUNEDuration UnitS/4 HANAAFVVDAUNEDuration UnitDIrect Mapping
19DCTAFVCANZZLRequired CapacitiesS/4 HANAAFVCANZZLRequired CapacitiesDIrect Mapping
20DCTAFVVEINSAStart ConstraintS/4 HANAAFVVEINSAStart ConstraintDIrect Mapping
21DCTAFVVNTANFStart Constraint DateS/4 HANAAFVVNTANFStart Constraint DateDIrect Mapping
22DCTAFVVNTANZStart Constraint TimeS/4 HANAAFVVNTANZStart Constraint TimeDIrect Mapping
23DCTAFVVEINSEFinish ConstraintS/4 HANAAFVVEINSEFinish ConstraintDIrect Mapping
24DCTAFVVNTENDFinish Constraint DateS/4 HANAAFVVNTENDFinish Constraint DateDIrect Mapping
25DCTAFVVNTENZFinish Constraint TimeS/4 HANAAFVVNTENZFinish Constraint TimeDIrect Mapping
26DCTAFVVMGVRGOperation QuantityS/4 HANAAFVVMGVRGOperation QuantityDIrect Mapping
27DCTAFVVMEINHOperation Quantity UnitS/4 HANAAFVVMEINHOperation Quantity UnitDIrect Mapping
28DCTAFVCPREISPriceS/4 HANAAFVCPREISPriceDIrect Mapping
29DCTAFVCWAERSCurrencyS/4 HANAAFVCWAERSCurrencyDIrect Mapping
30DCTAFVCPEINHPrice UnitS/4 HANAAFVCPEINHPrice UnitDIrect Mapping
31DCTAFVCLIFNRVendorS/4 HANAAFVCLIFNRVendorDIrect Mapping
34DCTAFVCWEMPFRecipientS/4 HANAAFVCWEMPFRecipientDIrect Mapping
35DCTAFVCBEDNRTracking NumberS/4 HANAAFVCBEDNRTracking NumberDIrect Mapping
36DCTAFVCSORTLSort TermS/4 HANAAFVCSORTLSort TermDIrect Mapping
37DCTAFVCINFNRPurchasing Info RecordS/4 HANAAFVCINFNRPurchasing Info RecordDIrect Mapping
38DCTAFVCAFNAMName of RequisitionerS/4 HANAAFVCAFNAMName of RequisitionerDIrect Mapping
39DCTAFVCABLADUnloading PointS/4 HANAAFVCABLADUnloading PointDIrect Mapping
40DCTAFVVPLIFZPlanned Delivery Time - DayS/4 HANAAFVVPLIFZPlanned Delivery Time - DayDIrect Mapping


5.  Work Order Operation Component Transformation Rule (ECC)

Rule #Source SystemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget Description

Transformation Logic

1----S/4 HANAAFVCAUFNROrder Number

System (Internal numbering)

2PF2, WP2AFVCVORNROperation NumberS/4 HANAAFVCVORNROperation NumberDIrect Mapping
3PF2, WP2RESBPOSNRItem Number of ReservationS/4 HANARESBPOSNRItem Number of ReservationDIrect Mapping
4PF2, WP2RESBMATNRMaterialS/4 HANARESBMATNRMaterialDerive as per Value Mapping: Material Master
5PF2, WP2RESBPOTX1DescriptionS/4 HANARESBPOTX1DescriptionDirect Mapping is MATNR is Blank. Else default to Blank
6PF2, WP2RESBPOSTPItem CategoryS/4 HANARESBPOSTPItem Category
7PF2, WP2RESBBDMNGRequirement QuantityS/4 HANARESBBDMNGRequirement Quantity
8PF2, WP2RESBMEINSUnitS/4 HANARESBMEINSUnit
9PF2, WP2RESBNO_DISPReservation Relevance / Generation of Purchase RequisitionS/4 HANARESBNO_DISPReservation Relevance / Generation of Purchase Requisition
10PF2, WP2RESBWERKSPlantS/4 HANARESBWERKSPlant
11PF2, WP2RESBBDTERRequirements DateS/4 HANARESBBDTERRequirements Date
12PF2, WP2RESBKZMPFManual Reqmt Date IndicatorS/4 HANARESBKZMPFManual Reqmt Date Indicator
13PF2, WP2RESBLGORTStorage LocationS/4 HANARESBLGORTStorage Location
14PF2, WP2RESBCHARGBatchS/4 HANARESBCHARGBatch
15PF2, WP2RESBGPREISPriceS/4 HANARESBGPREISPrice
16PF2, WP2RESBPEINHPrice UnitS/4 HANARESBPEINHPrice Unit
17PF2, WP2RESBWAERSCurrencyS/4 HANARESBWAERSCurrency
18PF2, WP2RSADDEKORGPurchasing OrganizationS/4 HANARSADDEKORGPurchasing Organization
19PF2, WP2RESBEKGRPPurchasing GroupS/4 HANARESBEKGRPPurchasing Group
20PF2, WP2RESBLIFNRSupplierS/4 HANARESBLIFNRSupplier
21PF2, WP2RESBINFNRPurchasing Info RecordS/4 HANARESBINFNRPurchasing Info Record
22PF2, WP2RESBMATKLMaterial GroupS/4 HANARESBMATKLMaterial Group
23PF2, WP2RESBSAKNRG/L AccountS/4 HANARESBSAKNRG/L Account
24PF2, WP2RESBWEMPFGoods RecipientS/4 HANARESBWEMPFGoods Recipient
25PF2, WP2RESBABLADUnloading PointS/4 HANARESBABLADUnloading Point
26PF2, WP2RESBSTARTDATEService Performance Start DateS/4 HANARESBSTARTDATEService Performance Start Date
27PF2, WP2RESBPERFORMANCEPERIODSTARTTIMEService Performance Start Time (UTC)S/4 HANARESBPERFORMANCEPERIODSTARTTIMEService Performance Start Time (UTC)
28PF2, WP2RESBENDDATEService Performance End DateS/4 HANARESBENDDATEService Performance End Date
29PF2, WP2RESBPERFORMANCEPERIODENDTIMEService Performance End Time (UTC)S/4 HANARESBPERFORMANCEPERIODENDTIMEService Performance End Time (UTC)
30PF2, WP2RESBSERVICEDURATIONDuration of Lean ServiceS/4 HANARESBSERVICEDURATIONDuration of Lean Service
31PF2, WP2RESBSERVICEDURATIONUNITDuration Unit for a Lean ServiceS/4 HANARESBSERVICEDURATIONUNITDuration Unit for a Lean Service
32PF2, WP2ESUHCOMMITMENTExpected ValueS/4 HANAESUHCOMMITMENTExpected Value
33PF2, WP2ESUHSUMLIMITOverall LimitS/4 HANAESUHSUMLIMITOverall Limit


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

Transformation Mapping

Mapping Table NameMapping Table Description

IFLOT

Functional Locations

T003O

Order Type & Priority

TQ80

Notification Type

EQUI

Equipment

CRHD

Work Centres

CSKU

Cost Centre

xtTPLNR

Xref for functional location. Fields: zLegacyTPLNR, TPLNR

xtEQUNR

Xref for equipment number. Fields: zLegacyEQUNR, EQUNR

xtARBPL

Xref for Work Centre. Fields: zLegacyARBPL, ARBPL

Purchase Order Number

EBELN_PURCH: Old Purchase Order number to New Purchase Order number

Transformation Dependencies

List the steps that need to occur before transformation can commence
Item #Step DescriptionTeam Responsible
1Ensure DCT tables completenessSyWay A2D Data Team
2Value Mappings are according to the latest design - <List of Value Mappings>SyWay 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 AccuracyBusiness 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

Obtain DCT Sign-off from Business

SyWay A2D Data Team

2Syniti will provide load fileSyniti
3Go to <Load Tool>SyWay A2D Data Team/Syniti
4Load 3 records for Work Order for function (IW31) to validate if data is loaded successfully without errorsSyWay A2D Data Team/Syniti
5Proceed with full load if step 4 is validatedSyWay A2D Data Team/Syniti
6Validate few records loaded by accessing standard transactions from S/4HNA E.g. IW39SyWay A2D Data Team/Syniti
7Generate post load report if step 6 is validatedSyWay A2D Data Team/Syniti


Load Phase and Dependencies

Configuration

Item #Configuration Item
1

Order Type

Conversion Objects

Object #Preceding Object Conversion Approach

9003

Revision

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)

Expedite 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 Order 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

Verify that the Reference Functional Location 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 Reference Functional Location data in target S/4 HANA were loaded correctly via dspMigrate post load reports or standard reports from S/4 HANA.


Key Assumptions

  • Data 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
  • No data enrichment is needed
  • Based on discussion with the business - the User Status in legacy will not be migrated over to S4
  • All Long Text will be migrated and defaulted to the language key of the plant
  • Notification missing for legacy open Work Orders will be migrated and assigned to the respective target Work Orders. The Notification for this scenario will be migrated with header information copied from the Target Work Orders


See also

Change log

Version Published Changed By Comment
CURRENT (v. 154) Apr 29, 2026 13:34 ERGUIZA-ext, Pinky Love
v. 357 Apr 29, 2026 10:38 ERGUIZA-ext, Pinky Love
v. 356 Apr 29, 2026 10:32 ERGUIZA-ext, Pinky Love
v. 355 Apr 29, 2026 10:29 ERGUIZA-ext, Pinky Love
v. 354 Apr 29, 2026 05:58 ERGUIZA-ext, Pinky Love
v. 353 Apr 27, 2026 08:22 ERGUIZA-ext, Pinky Love
v. 352 Apr 27, 2026 08:19 ERGUIZA-ext, Pinky Love
v. 351 Apr 27, 2026 08:19 ERGUIZA-ext, Pinky Love
v. 350 Apr 27, 2026 08:18 ERGUIZA-ext, Pinky Love
v. 349 Apr 27, 2026 08:16 ERGUIZA-ext, Pinky Love

Go to Page History

Workflow history

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

  • No labels