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

Compare with Current View Page History

« Previous Version 35 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:

  1. All open Work Orders (AUFK-AUFNR) with System Status (JEST-STAT) = Created (CRTD) or Released (REL).
  2. Work Orders with System Status (JEST-STAT) = Technically Completed (TECO) and an open Purchase Order assigned that is not flagged as Final Invoice or Final Delivery
  3. Work Orders with Maintenance Plant (IFLOT-WERKS) in scope.
  4. Work Orders assigned to active legacy Functional Locations (IFLOT-TPLNR) and Equipment (EQUI-EQUNR)
  5. Work Orders generated from Maintenance Plan with Basic Start Date <= Business Continuity Date
  6. A. Work Orders with no open PO, with Basic Start later than 12 months prior of the Cutover date
    B. Work Orders with no open PO, with Basic End Date later than 2 Weeks prior of the Cutover date
    C. Work Orders with open PO, regardless of Basic Start/ Finish Date
     

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
  6. Sub-orders
  7. Work Orders with blank Basic End Date
  8. Work Orders with Order type maintained in Work Order Type Exclusion List
  9. Work Orders with System Status (JEST-STAT) <> Technically Completed (TECO) System Status and with a User Status maintained in the User Status Exclusion List

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


List of source systems and approximate number of records
SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

PF2, WP2

Relevant Work Orders will be extracted from PF2 and WP2

140,000

S/4HANA 

140,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.

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. 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 DateDATS8SystemSystemSystem
AFKOGLTRPGLTRPBasic Finish DateDATS8SystemSystemSystem
IFLOTTPLNRTPLNRTechnical Object (Functional Location)CHAR30MandatoryMandatoryMandatory
AFIHEQUNREQUNRTechnical Object (Equipment)CHAR18ConditionalConditionalConditional
AFIHBAUTLBAUTLAssemblyCHAR40ConditionalConditionalConditional
AFIHANLZUANLZUSystem ConditionCHAR1ConditionalConditionalConditional
AFIHQMNUMQMNUMAssigned NotificationCHAR12SystemSystemSystem
AFIHILARTILARTMaintenance Activity TypeCHAR3MandatoryMandatoryMandatory
AFIHREVNRREVNRMaintenance Event/ RevisionCHAR8ConditionalConditionalConditional
CRHDARBPLARBPLWork CenterCHAR8MandatoryMandatoryMandatory
CRHDWERKSWERKSWork Center PlantCHAR4MandatoryMandatoryMandatory
AFIHIWERKIWERKPlanning PlantCHAR80SystemSystemSystem
AFIHINGPRINGPRPlanner GroupCHAR80SystemSystemSystem
AUFKWERKSWERKSMaintenance PlantCHAR4SystemSystemSystem
ILOABEBERBEBERPlant SectionCHAR3SystemSystemSystem
ILOABUKRSBUKRSCompany CodeCHAR4SystemSystemSystem
ILOAPROIDPROIDWBS Element (Acc Assignment)CHAR8ConditionalConditionalConditional
ILOAKOSTLKOSTLCost CenterCHAR10MandatoryMandatoryConditional
AUFKKOSTVKOSTVResponsible Cost CenterCHAR10SystemSystemSystem
AUFKPSPELPSPELPlanning WBS ElementCHAR8SystemSystemSystem
AUFKSCOPESCOPEObject ClassCHAR2SystemSystemSystem
AUFKPRCTRPRCTRProfit CenterCHAR10SystemSystemSystem

 
2. Order Phase Control

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

S_PHASE_

CONTROL

EAMBLOCKER

CODE

EAMBLOCKER

CODE

Phase Control CodeCHAR4MandatoryMandatoryMandatory

S_PHASE_

CONTROL

CODEACTIVECODEACTIVESet Automatically IndicatorCHAR1SystemSystemSystem


3. Order Partner

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


4. Operation Data

TableFieldData ElementField DescriptionData TypeLengthRequirement
YA01 (Reactive Maintenance)
Requirement
YA02 (Proactive Maintenance)
Requirement
YA03 (Project Order)
AFVCAUFNRAUFNROrder NumberCHAR12MandatoryMandatoryMandatory
AFVCVORNRVORNROperation NumberCHAR4SystemSystemSystem
AFVCVORNRVORNRSub-operation NumberCHAR4ConditionalConditionalConditional
AFVCLTXA1LTXA1Operation DescriptionCHAR40MandatoryMandatoryMandatory
CRHDARBPLARBPLWork CenterCHAR8MandatoryMandatoryMandatory
CRHDWERKSWERKSWork Center PlantCHAR4MandatoryMandatoryMandatory
AFVCPERNRPERNRPerson ResponsibleCHAR8ConditionalConditionalConditional
AFVCSTEUSSTEUSControl KeyCHAR4MandatoryMandatoryMandatory
AFVCWAERSWAERSCurrencyCHAR5SystemSystemSystem
AFVCSAKTOSAKTOCost ElementCHAR10ConditionalConditionalConditional
AFVCEKORGEKORGPurchasing OrganisationCHAR4ConditionalConditionalConditional
AFVCEKGRPEKGRPPurchasing GroupCHAR3ConditionalConditionalConditional
AFVCMATKLMATKLMaterial GroupCHAR9ConditionalConditionalConditional
AFVCANLZUANLZUSystem ConditionCHAR1ConditionalConditionalConditional
AFVCLARNTLARNTActivity TypeCHAR6SystemSystemSystem
AFVVARBEIARBEIWorkNUMC7MandatoryMandatoryMandatory
AFVVARBEHARBEHWork UnitCHAR3SystemSystemSystem
AFVCINDETINDETCalculation KeyCHAR1MandatoryMandatoryMandatory
AFVVDAUNODAUNODurationNUMC5SystemSystemSystem
AFVVDAUNEDAUNEDuration UnitCHAR3SystemSystemSystem
AFVCEQUNREQUNRTechnical Object (Equipment)CHAR18SystemSystemSystem
AFVCTPLNRTPLNRTechnical Object (Functional Location)CHAR30SystemSystemSystem
AFVCPRZNTPRZNTWork Percentage - %NUMC3SystemSystemSystem
AFVCISTRUISTRUAssemblyCHAR18ConditionalConditionalConditional
AFVCANZZLANZZLRequired CapacitiesNUMC3MandatoryMandatoryMandatory
AFVC

MAINTOPEXECUTION

PHASECODE

MAINTOPEXECUTION

PHASECODE

Execution StageNUMC10SystemSystemSystem
AFVVEINSAEINSAStart ConstraintCHAR1ConditionalConditionalConditional
AFVVNTANFNTANFStart Constraint DateDATS8ConditionalConditionalConditional
AFVVNTANZNTANZStart Constraint TimeTIMS6ConditionalConditionalConditional
AFVVEINSEEINSEFinish ConstraintCHAR1ConditionalConditionalConditional
AFVVNTENDNTENDFinish Constraint DateDATS8ConditionalConditionalConditional
AFVVNTENZNTENZFinish Constraint TimeTIMS6ConditionalConditionalConditional
AFVVMGVRGMGVRGOperation QuantityNUMC13ConditionalConditionalConditional
AFVVMEINHMEINHUnitCHAR80ConditionalConditionalConditional
AFVCPREISPREISPriceCHAR11ConditionalConditionalConditional
AFVCPEINHPEINHPrice UnitNUMC5ConditionalConditionalConditional
AFVCLIFNRLIFNRVendorCHAR10ConditionalConditionalConditional
AFVCWEMPFWEMPFRecipientCHAR12ConditionalConditionalConditional
AFVCBEDNRBEDNRTracking NumberCHAR10ConditionalConditionalConditional
AFVCSORTLSORTLSort TermCHAR10ConditionalConditionalConditional
AFVCINFNRINFNRPurchasing Info RecordCHAR10SystemSystemSystem
AFVCAFNAMAFNAMName of RequisitionerCHAR12ConditionalConditionalConditional


5. Operation Phase Control

TableFieldData ElementField DescriptionData TypeLengthRequirement
YA01 (Reactive Maintenance)
Requirement
YA02 (Proactive Maintenance)
Requirement
YA03 (Project Order)
AFVCAUFNRAUFNROrder NumberCHAR12MandatoryMandatoryMandatory
AFVCVORNRVORNROperation NumberCHAR4SystemSystemSystem
AFVCVORNRVORNRSuboperationCHAR4ConditionalConditionalConditional

S_OP_PHASE_

CONTROL

EAMBLOCKER

CODE

EAMBLOCKER

CODE

Phase Control CodeCHAR4SystemSystemSystem

S_OP_PHASE_

CONTROL

CODEACTIVECODEACTIVESet Automatically IndicatorCHAR1SystemSystemSystem


 6. Operation Materials

TableFieldData ElementField DescriptionData TypeLengthRequirement
YA01 (Reactive Maintenance)
Requirement
YA02 (Proactive Maintenance)
Requirement
YA03 (Project Order)
AFVCAUFNRAUFNROrder NumberCHAR12MandatoryMandatoryMandatory
AFVCVORNRVORNROperation NumberCHAR4SystemSystemSystem
AFVCVORNRVORNRSuboperationCHAR4ConditionalConditionalConditional
RESBPOSNRPOSNRItem Number of ReservationNUMC4SystemSystemSystem
RESBMATNRMATNRMaterialCHAR18ConditionalConditionalConditional
RESBPOTX1POTX1DescriptionCHAR40SystemSystemSystem
RESBPOSTPPOSTPItem CategoryCHAR1SystemSystemSystem
RESBBDMNGBDMNGQuantityNUMC13ConditionalConditionalConditional
RESBMEINSMEINSUnitCHAR3SystemSystemSystem
RESBNO_DISPNO_DISPReservation/Purc. ReqCHAR1SystemSystemSystem
RESBWERKSWERKSPlantCHAR4SystemSystemSystem
RESBBDTERBDTERRequirements DateDATS8ConditionalConditionalConditional
RESBLGORTLGORTStorage LocationCHAR4ConditionalConditionalConditional
RESBCHARGCHARGBatchCHAR10ConditionalConditionalConditional
RESBGPREISGPREISPriceNUMC15ConditionalConditionalConditional
RESBPEINHPEINHPrice UnitNUMC5ConditionalConditionalConditional
RESBWAERSWAERSCurrencyCHAR15SystemSystemSystem
RSADDEKORGEKORGPurchasing OrganizationCHAR4ConditionalConditionalConditional
RESBEKGRPEKGRPPurchasing GroupCHAR3ConditionalConditionalConditional
RESBLIFNRLIFNRSupplierCHAR10ConditionalConditionalConditional
RESBINFNRINFNRPurchasing Info RecordCHAR10SystemSystemSystem
RESBMATKLMATKLMaterial GroupCHAR9SystemSystemSystem
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


7. Operation Relationships

TableFieldData ElementField DescriptionData TypeLengthRequirement
YA01 (Reactive Maintenance)
Requirement
YA02 (Proactive Maintenance)
Requirement
YA03 (Project Order)
AFVCAUFNRAUFNROrder NumberCHAR12MandatoryMandatoryMandatory
AFVCVORNRVORNROperationCHAR4ConditionalConditionalConditional
AFVCAUFNRAUFNRAssigned OrderCHAR12ConditionalConditionalConditional
AFVCVORNRVORNRAssigned OperationCHAR4ConditionalConditionalConditional
AFABVORNCVORNCSuccessor IndicatorCHAR1ConditionalConditionalConditional
AFABAOBARAOBARType of RelationshipCHAR2ConditionalConditionalConditional
AFABDAUERDAUERTime IntervalNUMC5ConditionalConditionalConditional
AFABZEINHZEINHUnitCHAR3ConditionalConditionalConditional
AFABPRZNTPRZNTTime Interval %NUMC3ConditionalConditionalConditional
AFABPROVGPROVGTime Interval KeyCHAR1ConditionalConditionalConditional
AFABKALIDKALIDFactory CalendarCHAR2ConditionalConditionalConditional
CRHDARBPLARBPLWork CenterCHAR8ConditionalConditionalConditional
CRHDWERKSWERKSPlantCHAR4ConditionalConditionalConditional


8. Order Object List

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


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


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


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


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


13. 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-001C1Orders with Invalid Reference Object or Object ListFor an open and relevant Work Order the Functional Location or Equipment (including those in the object list) must be relevant.Order No, Order Type, Plant, Description, Functional Location, EquipmentPF2, WP2
9005-002C1Order Operations with Invalid Reference ObjectFor Operations of relevant Work Order the Functional Location or Equipment must be relevant.Order No, Order Type, Operation No, Plant, Description, Functional Location, EquipmentPF2, WP2
9005-003C1Work Orders with blank Basic End DateAll Work Orders in Legacy must have Basic End Date populatedOrder No, Order Type, Plant, Description, Basic Start Date, Basic End DatePF2, WP2
9005-004C2Orders with Deleted PlansFor an open and relevant Work Order, the assigned Maintenance Plan should not be flagged for deletion.Order No, Order Type, Plant, Description, Maintenance Plan NoPF2, WP2
9005-005C2Order Operation with Invalid ComponentFor operation of an open and relevant Work Order, component (which is not free text material) must only be assigned with valid indirect materials.Order No, Order Type, Operation No, Plant, Material No, Material DescriptionPF2, WP2
9005-006C2Work Orders maintained as Sub OrdersNo Sub Orders should exist in LegacyOrder No, Order Type, Plant, DescriptionPF2, WP2
9005-007C2Project Work Orders with Invalid WBS assignedIn-scope Project Work Orders must have valid WBS assignmentsOrder No, Order Type, Plant, Description, WBSPF2, WP2
9005-008C3Info Report: Order not in scope for migration (not relevant)All Work Orders the are not relevant as per the exclusion scopeOrder No, Order Type, Plant, DescriptionPF2, WP2
9005-009C3Open Purchase OrderFor an open and relevant Work Order, flag error if there is still open Purchase Order.Order No, Order Type, Plant, Purchase Requisition, Purchase Order, Material No, Material DescriptionPF2, WP2
9005-010C3Outstanding ReservationFor an open and relevant Work Order, flag error if there is still open ReservationOrder No, Order Type, Plant, Reservation NoPF2, 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:

 1. Source = PF2/WP2:

2. Source = DCT

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

DCT.png


Data Privacy and Sensitivity

Not Applicable


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
2Apply relevancy on extracted dataSyWay Data Team
3Google Sheet report pre-populated with PF2 and WP2 information to be generated based on relevancy criteria. SyWay 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 Work Order data with exception of some fields which require transformation as mentioned in the transformation rule.

Work Order DCT Rules

  1. AUFK - Work Order main table
Field NameField DescriptionRule
AUFNROrder Number


AUARTOrder Type


KTEXTDescription
LONG_TEXTLong Text
PPRIOPriority
SDATERequired Start Date
BASICSTARTRequired Start Time
FINISH_DATERequired End Date
BASIC_FINRequired End Time
LACD_DATEFinal Due Date
FUNCT_LOCTechnical Object (Functional Location)
EQUIPMENTTechnical Object (Equipment)
ASSEMBLYAssembly
SYSTCONDSystem Condition
NOTIF_NOAssigned Notification
PMACTTYPEMaintenance Activity Type
MN_WK_CTRWork Center
PLANTWork Center Plant
PLANPLANTPlanning Plant
PLANGROUPPlangroup
LOC_WK_CTRProduction Work Center
MAINTPLANTMaintenance Plant
LOCATIONLocation
MAINTROOMRoom
PLSECTNPlant Section
LOC_COMP_CODECompany Code
LOC_WBS_ELEMWBS Element (Acc Assignment)
COSTCENTERCost Center
RESPCCTRResponsible Cost Center
WBS_ELEMPlanning WBS Element
OBJECTCLASSObject Class
PROFIT_CTRProfit Center


       2. AFKO- Work Order header table

Field NameField DescriptionRule
AUFNROrder Number
GLTRPBasic finish date
GSTRPBasic Start Date
FTRMSScheduled release date
GLTRSScheduled finish
GSTRSScheduled start
GSTRIActual start date
GETRIConfirmed Order Finish Date
GLTRIActual finish date
FTRMIActual release date
FTRMPPlanned release date
RSNUMNumber of Reservation/Dependent Requirement
GASMGTotal scrap quantity in the order
GAMNGTotal order quantity
GMEINBase Unit of Measure
PLNBEZMaterial Number
PLNTYTask List Type
PLNNRKey for Task List Group
PLNAWApplication of the task list
PLNALGroup Counter
PVERWTask list usage
PLAUFDate for routing transfer
PLSVBTo lot size
PLNMETask list unit of measure
PLSVNFrom Lot Size
PDATVValid-From Date
PAENRChange Number
PLGRPResponsible planner group/department
LODIVLot size divisor
STLTYBOM category
STLBEZMaterial Number
STLSTBOM status
STLNRBill of material
SDATVValid-From Date
SBMNGBase quantity
SBMEHBase Unit of Measure
SAENRChange Number
STLALAlternative BOM
STLANBOM Usage
SLSVNFrom Lot Size
SLSBSTo Lot Size
AUFLDDate of BOM Explosion/Routing Transfer
DISPOMRP controller for the order
AUFPLRouting number of operations in the order
FEVORProduction Supervisor
FHORIScheduling Margin Key for Floats
TERKZScheduling type
REDKZReduction indicator for scheduling
APRIOOrder priority
NTZUESuperior network number
VORUESuperior activity
PROFIDNetwork profile
VORGZFloat before production (in days)
SICHZFloat after production (in days)
FREIZRelease period (in days)
UPTERIndicator: Change to Scheduled Dates
BEDIDID of the capacity requirements record
PRONRProject definition
ZAEHLInternal counter
MZAEHLInternal counter
ZKRIZCounter for additional criteria
PRUEFLOSInspection Lot Number
KLVARPCosting variant for planned costs
KLVARICosting variant for actual costs
RGEKZIndicator: Backflushing for order
PLARTBasis for scheduling
FLG_AOBIndicator: relationships
FLG_ARBEIIndicator: Default value work is relevant
GLTPPFinish date (forecast)
GSTPPForecast start date
GLTPSScheduled forecast finish
GSTPSScheduled forecast start
FTRPSScheduled release date (forecast)
RDKZPReduction indicator for scheduling (forecast)
TRKZPScheduling type (forecast)
RUECKCompletion confirmation number for the operation
RMZHLInternal counter
IGMNGYield confirmed from order confirmation
RATIDID of the capacity requirements record
GROIDID of the capacity requirements record
CUOBJConfiguration (internal object number)
GLUZSScheduled finish time
GSUZSScheduled Start (Time)
REVLVRevision Level
RSHTYObject types of the CIM resource
RSHIDObject ID of the resource
RSNTYObject types of the CIM resource
RSNIDObject ID of the resource
NAUTERMIndicator: Do not schedule automatically
NAUCOSTIndicator: Do not cost automatically
STUFELevel (in multi-level BOM explosions)
WEGXXPath (for multi-level BOM explosions)
VWEGXPath (for multi-level BOM explosions)
ARSNRNumber of Reservation/Dependent Requirement
ARSPSOrder Item Number
MAUFNRNumber of superior order
LKNOTLeft node in collective order
RKNOTRight node of a collective order
PRODNETIndicator: Order is part of collective order
IASMGScrap confirmed for order
ABARBConfirmation: Degree of processing
AUFNTNumber of superior network
AUFPTRouting number of operations in the order
APLZTGeneral counter for order
NO_DISPEffective for Materials Planning
CSPLITApportionment Structure
AENNRChange Number
CY_SEQNRSeq. number order
BREAKSIndicator: Scheduling allowing for breaks
VORGZ_TRMScheduled float before production in days
SICHZ_TRMScheduled float after production in days
TRMDTDate of the last scheduling
GLUZPBasic finish (time)
GSUZPBasic start time
GSUZIActual start time
GEUZIConfirmed order finish (time)
GLUPPForecast finish (time)
GSUPPForecast start (time)
GLUPSScheduled forecast finish time
GSUPSScheduled start time (Forecast)
CHSCHSearch procedure for batch determination
KAPT_VORGZFloat (bef. production) remaining after finite scheduling
KAPT_SICHZRemaining float after finite scheduling
LEAD_AUFNRLeading order in current processing
PNETSTARTDOutline start of collective network (date)
PNETSTARTTStart time of a collective order
PNETENDDOutline finish of collective order (date)
PNETENDTOutline finish time
KBEDInd: do not create capacity requirements
KKALKRIndicator: Components will not be costed
SFCPFProduction Scheduling Profile
RMNGATotal confirmed rework quantity
GSBTROverall commitment date
VFMNGCommitted quantity for order acc. to ATP check components
NOPCOSTDo not calculate planned costs for order
NETZKONTIndicator for the account assignment of a network(hdr/act.)
ATRKZRequest ID
OBJTYPEChange indicator
CH_PROCProcess that has lead to the change of an object
KAPVERSAVersion of Available Capacity
COLORDPROCCollective order with/without automatic goods movement
KZERBIndicator: Project summarization via master data charact.
CONF_KEYIdentical object
ST_ARBIDObject ID
VSNMR_VSales document version number
TERHWScheduling note from order scheduling
SPLSTATStatus of an order in a split hierarchy
COSTUPDCosts are updated
MAX_GAMNGMaximum Value of Total Order Quantity After Distribution
MES_ROUTINGIDKey of a Routing from an ME System
.INCLU--AP

ADPSPPM/PS Reference Element
RMANRSales and Distribution Document Number
POSNR_RMAItem number of the SD document
POSNV_RMAItem number of the SD document
CFB_MAXLZMaximum Storage Period
CFB_LZEIHUnit for maximum storage period
CFB_ADTDAYSAdditional Days
CFB_DATOFMDate of Manufacture
CFB_BBDPIBest-Before Date (BBD)/ Shelf Life Expiration Date (SLED)
OIHANTYPExcise Duty Handling Type
.INCLU--AP

MILL_RATIOFactor for Quantity-Based Settlement
.INCLU--AP

BMEINSBase Unit of Measure
BMENGEBase quantity
MILL_OC_ZUSKZCombination Indicator


       3. AFVC - Work Order operation table

Field NameField DescriptionRule
AUFPLRouting number of operations in the order
APLZLGeneral counter for order
PLNFLSequence
PLNKNNumber of the task list node
PLNALGroup Counter
PLNTYTask List Type
VINTVIncrement between referenced operations
PLNNRKey for Task List Group
ZAEHLInternal counter
VORNROperation/Activity Number
STEUSControl key
ARBIDObject ID of the resource
PDESTPrinter for shop papers
WERKSPlant
KTSCHStandard text key
LTXA1Operation short text
LTXA2Second line of the description
TXTSPLanguage Key
VPLTYType of the referenced task list
VPLNRGroup of the referenced task list
VPLALGroup counter of the referenced task list
VPLFLReferenced sequence in routing
VGWTSStandard value key
LAR01Activity Type
LAR02Activity Type
LAR03Activity Type
LAR04Activity Type
LAR05Activity Type
LAR06Activity Type
ZERMAType of standard value calculation
ZGDATDate when the standard value was calculated
ZCODEReference number for standard value code
ZULNRBasis for standard value calculation
LOANZNumber of Time Tickets
LOARTWage Type
RSANZNumber of confirmation slips
QUALFSuitability
ANZMANumber of employees
RFGRPSetup group category
RFSCHSetup group key
RASCHSetup Type Key
AUFAKScrap factor
LOGRPWage group
UEMUSRequired overlapping
UEKANOptional overlapping
FLIESIndicator: continuous flow production
SPMUSRequired splitting
SPLIMMaximum number of splits
ABLIPKZIndicator: simultaneous teardown and wait
RSTRAReduction strategy per operation/activity
SUMNRNode number of the superior operation
SORTLSort Term for Non-Stock Info Records
LIFNRAccount Number of Vendor or Creditor
PREISPrice
PEINHPrice Unit
SAKTOCost Element
WAERSCurrency Key
INFNRNumber of Purchasing Info Record
ESOKZPurchasing info record category
EKORGPurchasing Organization
EKGRPPurchasing group for external processing
KZLGFIndicator: fixed lot external processing
KZWRTFIndicator: Fixed price for external processing
MATKLMaterial Group
DDEHNIndicator: flexible duration
ANZZLNumber of capacities required
PRZNTWork percentage
MLSTNUsage
PPRIOPriority
BUKRSCompany Code
ANFKORequesting cost center
ANFKOKRSControlling area of the requesting cost center
INDETKey for calculation
LARNTActivity Type
PRKSTCosts in the activity
APLFLSequence
RUECKCompletion confirmation number for the operation
RMZHLConfirmation counter
PROJNWork breakdown structure element (WBS element)
OBJNRObject number
SPANZActual number of splits
BEDIDID of the capacity requirements record
BEDZLInternal counter
BANFNPurchase requisition number
BNFPOItem number of the purchase requisition in the order
LEK01Indicator: No remaining activity expected
LEK02Indicator: No remaining activity expected
LEK03Indicator: No remaining activity expected
LEK04Indicator: No remaining activity expected
LEK05Indicator: No remaining activity expected
LEK06Indicator: No remaining activity expected
SELKZSelection indicator for costing line items
KALIDFactory Calendar
FRSPEarliest possible activity / Latest possible activity
STDKNNode of operation within reference operation set
ANLZUSyst.Condition
ISTRUAssembly
ISTTYBOM category
ISTNRBill of material
ISTKNBOM item node number
ISTPOInternal counter
IUPOZSubitem Number
EBORTInstallation Point for Subitem
VERTLDistr.cap.reqmts (plant maint.,process order, network)
LEKNWIndicator: No Remaining Work Expected
NPRIOPriority
PVZKNGeneral counter for order
PHFLGIndicator: Phase
PHSEQControl Recipe Destination
KNOBJNumber of Object with Assigned Dependencies
ERFSICHTRecording View
QPPKTABSFlow Variants for Inspection Point Completion
OTYPEObject Type
OBJEKTIDObject ID
QLKAPARCapacity category
RSTUFReduction level which reduces operation lead time
NPTXTKYInternal text number (12-character)
SUBSYSSubsystem Identifier for QM Subsystem Interface
PSPNRStandard WBS element
PACKNOPackage number
TXJCDTax Jurisdiction
SCOPEObject Class
GSBERBusiness Area
PRCTRProfit Center
NO_DISPEffective for Materials Planning
QKZPRZEITInterval = Time (Time-Related)
QKZZTMG1Quantity Confirmation for Each Partial Lot
QKZPRMENGCreation Cycle = Quantity (Quantity-Reference)
QKZPRFREIInterval Without Reference to Time or Quantity
KZFEATIndicator Is Not Used Currently
QKZTLSBESTOperation with Stock-Related Partial Lot Assignment
AENNRChange Number
CUOBJ_ARBConfiguration (internal object number)
EVGEWAggregation weight for POC (PS progress)
ARBIIActual operating resources object identification
WERKIActual plant
CY_SEQNRVSequence number operation
KAPT_PUFFROperation floats after finite scheduling (in seconds)
EBELNPurchasing Document Number
EBELPItem Number of Purchasing Document
WEMPFGoods Recipient/Ship-To Party
ABLADUnloading Point
CLASFInd.: Take Activity Into Account for Project Summarization
FRUNVIndicator: External procurement data incomplete
ZSCHLOverhead key
KALSMCosting Sheet
SCHED_ENDInd.: Purchase requisition at activity finish date
NETZKONTIndicator for the account assignment of a network(hdr/act.)
OWAERObject currency for network activity
AFNAMName of Requisitioner/Requester
BEDNRRequirement Tracking Number
KZFIXIndicator: Purchasing info record data are fixed
PERNRPersonnel number
FRDLBIndicator: Externally processed op. with subcontracting
QPARTInspection Type
LOEKZDeletion flag
WKURSExchange Rate
PROD_ACTIndicator: Activity is a production activity
FPLNRBilling plan number / invoicing plan number
OBJTYPEChange indicator
CH_PROCProcess that has lead to the change of an object
KLVARCosting Variant
KALNRCost Estimate Number for Cost Est. w/o Qty Structure
FORDNFramework Order
FORDPItem of framework order
MAT_PRKSTMaterial planning in networks: primary costs
PRZ01Business Process
RFPNTReference point for BOM transfer
FUNC_AREAFunctional Area
TECHSParameter Variant/Standard Variant
ADPSPReference Element PM/PS
RFIPPNTReference Point for Relationship Between iPPE and PS
MES_OPERIDKey of an Operation from an ME System
MES_STEPIDKey of a Step in a Routing (SAP ME)
.INCLU--AP

/CUM/CUGUIDUUID in X form (binary)
.INCLU--AP

/ISDFPS/OBJNRObject number
.INCLU--AP

AFVC_STATUSStatus Combination
.INCLU--AP

MILL_OC_AUFNR_MONumber of Combined Order
.INCLU--AP

WTY_INDWarranty indicator
TPLNRFunctional Location
EQUNREquipment Number
.INCLU--AP

CPD_UPDATTime Stamp


       4. AFIH - Work Order maintenance order header

Field NameField DescriptionRule
AUFNROrder Number
ARTPRPriority Type
PRIOKPriority
EQUNREquipment Number
BAUTLAssembly
ILOANLocation and account assignment for technical object
ILOAIILOA Individual
ANLZUSyst.Condition
IWERKMaintenance Planning Plant
INGPRPlanner Group for Customer Service and Plant Maintenance
APGRPResponsible planner group/department
PM_OBJTYObject Type of CIM Resources for Work Center
GEWRKObject ID of the Work Center
KUNUMCustomer Number
ANINGName of Person Reponsible for System
GAUZTPlanned downtime in hours
GAUEHUnit for Breakdown Duration
ANLBDDate until which the system is available
ANLVDDate from which the system is available
ANLBZTime until which the system is available
ANLVZTime from Which System is Available
INSPKName of Person Responsible for Technical Inspection
DATANDate of Technical Inspection
WARPLMaintenance Plan
ABNUMMaintenance Plan Call Number
WAPOSMaintenance item
LAUFNOrder number
OBKNRObject list number
REVNRRevision for Plant Maintenance and Customer Service
ADDATPM Order: Reference Date
ADUHRTime of Reference Date
IPHASMaintenance Processing Phase
ILARTMaintenance activity type
QMNUMNotification No
HISDAPM request: History date
AKKNZOrder Category Indicator Plant Maintenance
PLKNZMaintenance order planning indicator
SERIALNRSerial Number
SERMATMaterial Number
DEVICEIDAdditional Device Data
SCREENTYScenario or Subscreen Category
ADPSPReference Element PM/PS
RSUPGUpgrade Order Indicator
.INCLU--AP

/ISDFPS/OBJNRObject number
/ISDFPS/MEQUIMaster Equipment
.INCLU--AP

UIIUnique Item Identifier
.INCLU--AP

ORCODPM/CS Order Code Indicating Rotable Process
PRMANCMC: Priority Manually Changed
PRVALPriority for PM/CS Orders
TWTDECMC: Use Minimum or Standard TWT from PP Matrix
MSTCKSingle-Character Indicator


Extraction Dependencies

Item #Step DescriptionTeam Responsible

1

Ensure Syniti has the necessary connection and access to legacy servers 

SyWay A2D Data Team

2

Ensure that the necessary cleansing activities in legacy sources are complete 

SyWay A2D Data Team / Business 

3

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

Legacy IT 

4

Equipment and Functional Location Master Data need to be first with their respective relevancy rules applied before Work Order can be extracted 

SyWay A2D Data Team


Transformation

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

  1. Perform value mapping and data transformation rules.
    1. Legacy values are mapped to the to-be values (this could include a default value)
    2. Values are transformed according to the rules defined in
  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
1Obtain DCT Sign-off from BusinessSyWay A2D Data Team
2<Add steps from Syniti Migrate here>SyWay A2D Data Team
3Review and Validate Error and Preload ReportsSyWay A2D Data Team
4

Generate Load Files

SyWay A2D Data Team


Transformation Rules

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








2








3








4








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.
  • All data cleansing and preparation has been completed.
  • Only valid Legacy outstanding Work Orders that have been supplied by the CIT in the Identified List of Work Order will be converted
  • All Work Orders will be forward scheduled and outstanding (not TECO), as the cut off day for Work Orders will be seven days prior to the Legacy system close date, and be valid “work” (i.e. not used as a PO generation point for items such as travel, payment reminders, etc).


See also

Change log

Version Published Changed By Comment
CURRENT (v. 35) May 05, 2026 11:25 ERGUIZA-ext, Pinky Love
v. 366 May 05, 2026 10:54 ERGUIZA-ext, Pinky Love PDM-1838: Updated as per Unit Test- Data Type for SERVICEDURATION, COMMITMENT and SUMLIMIT
v. 365 May 05, 2026 10:53 ERGUIZA-ext, Pinky Love
v. 364 May 05, 2026 10:51 ERGUIZA-ext, Pinky Love
v. 363 May 05, 2026 10:39 ERGUIZA-ext, Pinky Love PDM-1837: Updated as per Unit Test- Data Type from CHAR 11 to CURR 11, 2
v. 362 May 05, 2026 10:39 ERGUIZA-ext, Pinky Love
v. 361 May 05, 2026 10:25 ERGUIZA-ext, Pinky Love PDM-1835: Updated as per Unit Test- Renamed KCHAR to KTEXT
v. 360 May 05, 2026 10:25 ERGUIZA-ext, Pinky Love
v. 359 May 05, 2026 10:23 ERGUIZA-ext, Pinky Love
v. 358 Apr 29, 2026 13:34 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