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

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

Source	Scope	Source Approx No. of Records	Target System	Target 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

Table	Field	Data Element	Field Description	Data Type	Length	Requirement YA01 (Reactive Maintenance)	Requirement YA02 (Proactive Maintenance)	Requirement YA03 (Project Order)
AUFK	AUFNR	AUFNR	Order Number	CHAR	12	Mandatory	Mandatory	Mandatory
AUFK	AUART	AUART	Order Type	CHAR	4	Mandatory	Mandatory	Mandatory
AUFK	KTEXT	KTEXT	Description	CHAR	40	Mandatory	Mandatory	Mandatory
AFIH	PRIOK	PRIOK	Priority	CHAR	80	Mandatory	Mandatory	Mandatory
AFKO	GSTRP	GSTRP	Basic Start Date	DATS	8	System	System	System
AFKO	GLTRP	GLTRP	Basic Finish Date	DATS	8	System	System	System
IFLOT	TPLNR	TPLNR	Functional Location	CHAR	30	Mandatory	Mandatory	Mandatory
AFIH	EQUNR	EQUNR	Equipment	CHAR	18	Conditional	Conditional	Conditional
AFIH	BAUTL	BAUTL	Assembly	CHAR	40	Conditional	Conditional	Conditional
AFIH	ANLZU	ANLZU	System Condition	CHAR	1	Conditional	Conditional	Conditional
AFIH	QMNUM	QMNUM	Assigned Notification	CHAR	12	System	System	System
AFIH	ILART	ILART	Maintenance Activity Type	CHAR	3	Mandatory	Mandatory	Mandatory
AFIH	REVNR	REVNR	Maintenance Event/ Revision	CHAR	8	Conditional	Conditional	Conditional
CRHD	ARBPL	ARBPL	Work Center	CHAR	8	Mandatory	Mandatory	Mandatory
CRHD	WERKS	WERKS	Work Center Plant	CHAR	4	Mandatory	Mandatory	Mandatory
AFIH	IWERK	IWERK	Planning Plant	CHAR	80	System	System	System
AFIH	INGPR	INGPR	Planner Group	CHAR	80	System	System	System
AUFK	WERKS	WERKS	Maintenance Plant	CHAR	4	System	System	System
ILOA	BEBER	BEBER	Plant Section	CHAR	3	System	System	System
ILOA	BUKRS	BUKRS	Company Code	CHAR	4	System	System	System
ILOA	PROID	PROID	WBS Element (Acc Assignment)	CHAR	8	Conditional	Conditional	Conditional
ILOA	KOSTL	KOSTL	Cost Center	CHAR	10	Mandatory	Mandatory	Conditional
AUFK	KOSTV	KOSTV	Responsible Cost Center	CHAR	10	System	System	System
AUFK	PSPEL	PSPEL	Planning WBS Element	CHAR	8	System	System	System
AUFK	SCOPE	SCOPE	Object Class	CHAR	2	System	System	System
AUFK	PRCTR	PRCTR	Profit Center	CHAR	10	System	System	System

 

2. Order Partner

Table	Field	Data Element	Field Description	Data Type	Length	Requirement YA01 (Reactive Maintenance)	Requirement YA02 (Proactive Maintenance)	Requirement YA03 (Project Order)
AUFK	AUFNR	AUFNR	Order Number	CHAR	12	Mandatory	Mandatory	Mandatory
IHPA	PARVW	PARVW	Partner Function	CHAR	2	Conditional	Conditional	Conditional
IHPA	PARNR	PARNR	Partner	CHAR	12	Conditional	Conditional	Conditional

3. Operation Data

Table	Field	Data Element	Field Description	Data Type	Length	Requirement YA01 (Reactive Maintenance)	Requirement YA02 (Proactive Maintenance)	Requirement YA03 (Project Order)
AFVC	AUFNR	AUFNR	Order Number	CHAR	12	Mandatory	Mandatory	Mandatory
AFVC	VORNR	VORNR	Operation Number	CHAR	4	System	System	System
AFVC	VORNR	VORNR	Sub-operation Number	CHAR	4	Conditional	Conditional	Conditional
AFVC	LTXA1	LTXA1	Operation Description	CHAR	40	Mandatory	Mandatory	Mandatory
CRHD	ARBPL	ARBPL	Work Center	CHAR	8	Mandatory	Mandatory	Mandatory
CRHD	WERKS	WERKS	Work Center Plant	CHAR	4	Mandatory	Mandatory	Mandatory
AFVC	PERNR	PERNR	Person Responsible	CHAR	8	Conditional	Conditional	Conditional
AFVC	STEUS	STEUS	Control Key	CHAR	4	Mandatory	Mandatory	Mandatory
AFVC	WAERS	WAERS	Currency	CHAR	5	System	System	System
AFVC	SAKTO	SAKTO	Cost Element	CHAR	10	Conditional	Conditional	Conditional
AFVC	EKORG	EKORG	Purchasing Organisation	CHAR	4	Conditional	Conditional	Conditional
AFVC	EKGRP	EKGRP	Purchasing Group	CHAR	3	Conditional	Conditional	Conditional
AFVC	MATKL	MATKL	Material Group	CHAR	9	Conditional	Conditional	Conditional
AFVC	ANLZU	ANLZU	System Condition	CHAR	1	Conditional	Conditional	Conditional
AFVC	LARNT	LARNT	Activity Type	CHAR	6	System	System	System
AFVV	ARBEI	ARBEI	Work	NUMC	7	Mandatory	Mandatory	Mandatory
AFVV	ARBEH	ARBEH	Work Unit	CHAR	3	System	System	System
AFVC	INDET	INDET	Calculation Key	CHAR	1	Mandatory	Mandatory	Mandatory
AFVV	DAUNO	DAUNO	Duration	NUMC	5	System	System	System
AFVV	DAUNE	DAUNE	Duration Unit	CHAR	3	System	System	System
AFVC	EQUNR	EQUNR	Technical Object (Equipment)	CHAR	18	System	System	System
AFVC	TPLNR	TPLNR	Technical Object (Functional Location)	CHAR	30	System	System	System
AFVC	PRZNT	PRZNT	Work Percentage - %	NUMC	3	System	System	System
AFVC	ISTRU	ISTRU	Assembly	CHAR	18	Conditional	Conditional	Conditional
AFVC	ANZZL	ANZZL	Required Capacities	NUMC	3	Mandatory	Mandatory	Mandatory
AFVC	MAINTOPEXECUTION PHASECODE	MAINTOPEXECUTION PHASECODE	Execution Stage	NUMC	10	System	System	System
AFVV	EINSA	EINSA	Start Constraint	CHAR	1	Conditional	Conditional	Conditional
AFVV	NTANF	NTANF	Start Constraint Date	DATS	8	Conditional	Conditional	Conditional
AFVV	NTANZ	NTANZ	Start Constraint Time	TIMS	6	Conditional	Conditional	Conditional
AFVV	EINSE	EINSE	Finish Constraint	CHAR	1	Conditional	Conditional	Conditional
AFVV	NTEND	NTEND	Finish Constraint Date	DATS	8	Conditional	Conditional	Conditional
AFVV	NTENZ	NTENZ	Finish Constraint Time	TIMS	6	Conditional	Conditional	Conditional
AFVV	MGVRG	MGVRG	Operation Quantity	NUMC	13	Conditional	Conditional	Conditional
AFVV	MEINH	MEINH	Unit	CHAR	80	Conditional	Conditional	Conditional
AFVC	PREIS	PREIS	Price	CHAR	11	Conditional	Conditional	Conditional
AFVC	PEINH	PEINH	Price Unit	NUMC	5	Conditional	Conditional	Conditional
AFVC	LIFNR	LIFNR	Vendor	CHAR	10	Conditional	Conditional	Conditional
AFVC	WEMPF	WEMPF	Recipient	CHAR	12	Conditional	Conditional	Conditional
AFVC	BEDNR	BEDNR	Tracking Number	CHAR	10	Conditional	Conditional	Conditional
AFVC	SORTL	SORTL	Sort Term	CHAR	10	Conditional	Conditional	Conditional
AFVC	INFNR	INFNR	Purchasing Info Record	CHAR	10	System	System	System
AFVC	AFNAM	AFNAM	Name of Requisitioner	CHAR	12	Conditional	Conditional	Conditional

 4. Operation Materials

Table	Field	Data Element	Field Description	Data Type	Length	Requirement YA01 (Reactive Maintenance)	Requirement YA02 (Proactive Maintenance)	Requirement YA03 (Project Order)
AFVC	AUFNR	AUFNR	Order Number	CHAR	12	Mandatory	Mandatory	Mandatory
AFVC	VORNR	VORNR	Operation Number	CHAR	4	System	System	System
AFVC	VORNR	VORNR	Suboperation	CHAR	4	Conditional	Conditional	Conditional
RESB	POSNR	POSNR	Item Number of Reservation	NUMC	4	System	System	System
RESB	MATNR	MATNR	Material	CHAR	18	Conditional	Conditional	Conditional
RESB	POTX1	POTX1	Description	CHAR	40	System	System	System
RESB	POSTP	POSTP	Item Category	CHAR	1	System	System	System
RESB	BDMNG	BDMNG	Quantity	NUMC	13	Conditional	Conditional	Conditional
RESB	MEINS	MEINS	Unit	CHAR	3	System	System	System
RESB	NO_DISP	NO_DISP	Reservation/Purc. Req	CHAR	1	System	System	System
RESB	WERKS	WERKS	Plant	CHAR	4	System	System	System
RESB	BDTER	BDTER	Requirements Date	DATS	8	Conditional	Conditional	Conditional
RESB	LGORT	LGORT	Storage Location	CHAR	4	Conditional	Conditional	Conditional
RESB	CHARG	CHARG	Batch	CHAR	10	Conditional	Conditional	Conditional
RESB	GPREIS	GPREIS	Price	NUMC	15	Conditional	Conditional	Conditional
RESB	PEINH	PEINH	Price Unit	NUMC	5	Conditional	Conditional	Conditional
RESB	WAERS	WAERS	Currency	CHAR	15	System	System	System
RSADD	EKORG	EKORG	Purchasing Organization	CHAR	4	Conditional	Conditional	Conditional
RESB	EKGRP	EKGRP	Purchasing Group	CHAR	3	Conditional	Conditional	Conditional
RESB	LIFNR	LIFNR	Supplier	CHAR	10	Conditional	Conditional	Conditional
RESB	INFNR	INFNR	Purchasing Info Record	CHAR	10	System	System	System
RESB	MATKL	MATKL	Material Group	CHAR	9	System	System	System
RESB	SAKNR	SAKNR	G/L Account	CHAR	10	Conditional	Conditional	Conditional
RESB	WEMPF	WEMPF	Goods Recipient	CHAR	12	Conditional	Conditional	Conditional
RESB	ABLAD	ABLAD	Unloading Point	CHAR	25	Conditional	Conditional	Conditional
RESB	STARTDATE	STARTDATE	Service Performance Start Date	DATS	8	Conditional	Conditional	Conditional
RESB	PERFORMANCE PERIODSTARTTIME	PERFORMANCE PERIODSTARTTIME	Service Performance Start Time (UTC)	TIMS	6	Conditional	Conditional	Conditional
RESB	ENDDATE	ENDDATE	Service Performance End Date	DATS	8	Conditional	Conditional	Conditional
RESB	PERFORMANCE PERIODENDTIME	PERFORMANCE PERIODENDTIME	Service Performance End Time (UTC)	TIMS	6	Conditional	Conditional	Conditional
RESB	SERVICE DURATION	SERVICE DURATION	Duration of Lean Service	NUMC	5	Conditional	Conditional	Conditional
RESB	SERVICE DURATIONUNIT	SERVICE DURATIONUNIT	Duration Unit for a Lean Service	CHAR	3	Conditional	Conditional	Conditional
ESUH	COMMITMENT	COMMITMENT	Expected Value	NUMC	13	Conditional	Conditional	Conditional
ESUH	SUMLIMIT	SUMLIMIT	Overall Limit	NUMC	13	Conditional	Conditional	Conditional

5. Operation Relationships

Table	Field	Data Element	Field Description	Data Type	Length	Requirement YA01 (Reactive Maintenance)	Requirement YA02 (Proactive Maintenance)	Requirement YA03 (Project Order)
AFVC	AUFNR	AUFNR	Order Number	CHAR	12	Mandatory	Mandatory	Mandatory
AFVC	VORNR	VORNR	Operation	CHAR	4	Conditional	Conditional	Conditional
AFVC	AUFNR	AUFNR	Assigned Order	CHAR	12	Conditional	Conditional	Conditional
AFVC	VORNR	VORNR	Assigned Operation	CHAR	4	Conditional	Conditional	Conditional
AFAB	VORNC	VORNC	Successor Indicator	CHAR	1	Conditional	Conditional	Conditional
AFAB	AOBAR	AOBAR	Type of Relationship	CHAR	2	Conditional	Conditional	Conditional
AFAB	DAUER	DAUER	Time Interval	NUMC	5	Conditional	Conditional	Conditional
AFAB	ZEINH	ZEINH	Unit	CHAR	3	Conditional	Conditional	Conditional
AFAB	PRZNT	PRZNT	Time Interval %	NUMC	3	Conditional	Conditional	Conditional
AFAB	PROVG	PROVG	Time Interval Key	CHAR	1	Conditional	Conditional	Conditional
AFAB	KALID	KALID	Factory Calendar	CHAR	2	Conditional	Conditional	Conditional
CRHD	ARBPL	ARBPL	Work Center	CHAR	8	Conditional	Conditional	Conditional
CRHD	WERKS	WERKS	Plant	CHAR	4	Conditional	Conditional	Conditional

6. Order Object List

Table	Field	Data Element	Field Description	Data Type	Length	Requirement YA01 (Reactive Maintenance)	Requirement YA02 (Proactive Maintenance)	Requirement YA03 (Project Order)
AUFK	AUFNR	AUFNR	Order Number	CHAR	12	Mandatory	Mandatory	Mandatory
OBJK	OBZAE	OBZAE	Counter	NUMC	10	System	System	System
OBJK	SORTF	SORTF	Sort	CHAR	20	Conditional	Conditional	Conditional
IFLOT	TPLNR	TPLNR	Functional Location	CHAR	30	Mandatory	Mandatory	Mandatory
OBJK	EQUNR	EQUNR	Equipment	CHAR	18	Conditional	Conditional	Conditional
OBJK	MATNR	MATNR	Material	CHAR	18	Conditional	Conditional	Conditional
OBJK	QMNUM	QMNUM	Notification	CHAR	12	Mandatory	Mandatory	Mandatory
OBJK	BAUTL	BAUTL	Assembly	CHAR	18	Conditional	Conditional	Conditional

 7. Order Confirmation

Table	Field	Data Element	Field Description	Data Type	Length	Requirement YA01 (Reactive Maintenance)	Requirement YA02 (Proactive Maintenance)	Requirement YA03 (Project Order)
AUFK	AUFNR	AUFNR	Order Number	CHAR	12	Mandatory	Mandatory	Mandatory
AFVC	VORNR	VORNR	Operation	CHAR	4	System	System	System
AFRU	ISMNW	ISMNW	Actual Work	NUMC	7	Mandatory	Mandatory	Mandatory
AFRU	AUERU	AUERU	Final Confirmation	CHAR	1	Conditional	Conditional	Conditional
AFRU	OFMNW	OFMNW	Remaining work	NUMC	7	Mandatory	Mandatory	Mandatory
AFRU	ISDD	ISDD	Work Start Date	DATS	8	Mandatory	Mandatory	Mandatory
AFRU	ISDZ	ISDZ	Work Start Time	TIMS	6	Mandatory	Mandatory	Mandatory
AFRU	IEDD	IEDD	Work Finish Date	DATS	8	Conditional	Conditional	Conditional
AFRU	IEDZ	IEDZ	Work Finish Time	TIMS	6	Conditional	Conditional	Conditional

8. Order Long Text Header

Table	Field	Data Element	Field Description	Data Type	Length	Requirement YA01 (Reactive Maintenance)	Requirement YA02 (Proactive Maintenance)	Requirement YA03 (Project Order)
STXH	TDOBJECT	TDOBJECT	Texts: application object	CHAR	10	Mandatory	Mandatory	Mandatory
STXH	TDNAME	TDOBNAME	Name	CHAR	70	Mandatory	Mandatory	Mandatory
STXH	TDID	TDID	Text ID	CHAR	4	Mandatory	Mandatory	Mandatory
STXH	TDSPRAS	SPRAS	Language Key	LANG	1	Mandatory	Mandatory	Mandatory

 9. Order Long Text Line

Table	Field	Data Element	Field Description	Data Type	Length	Requirement YA01 (Reactive Maintenance)	Requirement YA02 (Proactive Maintenance)	Requirement YA03 (Project Order)
STXH	TDOBJECT	TDOBJECT	Texts: application object	CHAR	10	Mandatory	Mandatory	Mandatory
STXL	TDNAME	TDOBNAME	Name	CHAR	70	Mandatory	Mandatory	Mandatory
STXL	TDID	TDID	Text ID	CHAR	4	Mandatory	Mandatory	Mandatory
STXL	TDSPRAS	SPRAS	Language Key	LANG	1	Mandatory	Mandatory	Mandatory
STXL	TDFORMAT	TDFORMAT	Tag column	CHAR	1	Mandatory	Mandatory	Mandatory
STXL	ROWCOUNT	ROWCOUNT	Row number	NUMC	10	Mandatory	Mandatory	Mandatory
STXL	TXLINE	TDLINE	Text Line	CHAR	72	Mandatory	Mandatory	Mandatory

10. Operation Long Text Header

Table	Field	Data Element	Field Description	Data Type	Length	Requirement YA01 (Reactive Maintenance)	Requirement YA02 (Proactive Maintenance)	Requirement YA03 (Project Order)
STXH	TDOBJECT	TDOBJECT	Texts: application object	CHAR	10	Mandatory	Mandatory	Mandatory
STXH	TDNAME	TDOBNAME	Name	CHAR	70	Mandatory	Mandatory	Mandatory
STXH	TDID	TDID	Text ID	CHAR	4	Mandatory	Mandatory	Mandatory
STXH	TDSPRAS	SPRAS	Language Key	LANG	1	Mandatory	Mandatory	Mandatory

11. Operation Long Text Line

Table	Field	Data Element	Field Description	Data Type	Length	Requirement YA01 (Reactive Maintenance)	Requirement YA02 (Proactive Maintenance)	Requirement YA03 (Project Order)
STXH	TDOBJECT	TDOBJECT	Texts: application object	CHAR	10	Mandatory	Mandatory	Mandatory
STXL	TDNAME	TDOBNAME	Name	CHAR	70	Mandatory	Mandatory	Mandatory
STXL	TDID	TDID	Text ID	CHAR	4	Mandatory	Mandatory	Mandatory
STXL	TDSPRAS	SPRAS	Language Key	LANG	1	Mandatory	Mandatory	Mandatory
STXL	TDFORMAT	TDFORMAT	Tag column	CHAR	1	Mandatory	Mandatory	Mandatory
STXL	ROWCOUNT	ROWCOUNT	Row number	NUMC	10	Mandatory	Mandatory	Mandatory
STXL	TXLINE	TDLINE	Text Line	CHAR	72	Mandatory	Mandatory	Mandatory

Data Cleansing

All data cleansing should take place in the data source system as defined in this document, unless system limitations prevent it.

If data cleansing is managed outside of the source system (e.g. Syniti Migrate, 3rd Party Vendor, DCT), the necessary documentation must be produced and appended to this deliverable for sign-off.

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
9005-001	C1	Orders with Invalid Reference Object or Object List	For 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, Equipment	PF2, WP2
9005-002	C1	Order Operations with Invalid Reference Object	For Operations of relevant Work Order the Functional Location or Equipment must be relevant.	Order No, Order Type, Operation No, Plant, Description, Functional Location, Equipment	PF2, WP2
9005-003	C1	Work Orders with blank Basic End Date	All Work Orders in Legacy must have Basic End Date populated	Order No, Order Type, Plant, Description, Basic Start Date, Basic End Date	PF2, WP2
9005-004	C2	Orders with Deleted Maintenance Plans	For an open and relevant Work Order, the assigned Maintenance Plan should not be flagged for deletion.	Order No, Order Type, Plant, Description, Maintenance Plan No	PF2, WP2
9005-005	C2	Order Operation with Invalid Component	For 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 Description	PF2, WP2
9005-006	C2	Work Orders maintained as Sub Orders	No Sub Orders should exist in Legacy	Order No, Order Type, Plant, Description	PF2, WP2
9005-007	C2	Project Work Orders with Invalid WBS assigned	In-scope Project Work Orders must have valid WBS assignments	Order No, Order Type, Plant, Description, WBS	PF2, WP2
9005-008	C3	Info Report: Order not in scope for migration (not relevant)	All Work Orders the are not relevant as per the exclusion scope	Order No, Order Type, Plant, Description	PF2, WP2
9005-009	C3	Open Purchase Order	For 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 Description	PF2, WP2
9005-010	C3	Outstanding Reservation	For an open and relevant Work Order, flag error if there is still open Reservation	Order No, Order Type, Plant, Reservation No	PF2, WP2

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

 

Conversion Process

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

 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

Data Privacy and Sensitivity

Not Applicable

Extraction

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

1. The data exists. Syniti Migrate connects to the source and loads the data into Syniti Migrate. 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 Syniti Migrate; 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 Syniti Migrate. This is to be conducted using DCT (Data Collection Template) in Syniti Migrate

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

Extraction Run Sheet

Req #	Requirement Description	Team Responsible
1	Extract data from source system based on relevancy rule	SyWay Data Team
2	Apply relevancy on extracted data	SyWay Data Team
3	Google Sheet report pre-populated with PF2 and WP2 information to be generated based on relevancy criteria.	SyWay Data Team

Selection Screen

If applicable, this section will give the details on any selection screen parameters, including the parameter type, that are required to be entered to ensure consistent data extracts.

Selection Ref Screen	Parameter Name	Selection Type	Requirement	Value to be entered/set
Not Applicable

Data Collection Template (DCT)

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

1. The extracted report will be loaded into the required structure using the DCT.
2. Standardization activities (including deduplication, standardization and additions)  will be carried out within the DCT.

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. Order Header Data Construction Rules

Field Name	Field Description	Rule
zLegacyAUFNR	Legacy Order Number	Mandatory. Key field
AUART	Order Type	Mandatory. Allowed values:  YA01    Reactive Maintenance YA02    Proactive Maintenance YA03    Project Orders
KCHAR	Description	Mandatory. Populate 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
PRIOK	Priority	Mandatory. Allowed values from T356 to be populated
TPLNR	Functional Location	Mandatory. Populate with the legacy Functional Location assigned to the order. Value must exist in Functional Location mapping.
EQUNR	Equipment	Conditional. Populate with the legacy Equipment assigned to the order. Value must exist in Equipment Mapping.
BAUTL	Assembly	Conditional. Populate if information exists. Otherwise, leave the field blank.
ANLZU	System Condition	Conditional.  Allowed values from T357M to be populated
ILART	Maintenance Activity Type	Mandatory. Allowed values from T353I to be populated
REVNR	Maintenance Event / Revision	Conditional. Populate values if required from Maintenance Bucket - Maintenance Event DCT.
PROID	WBS Element (Acc Assignment)	Conditional. Populate only for Project Work Orders  Should exist in either WBS Element Number mapping or WBS DCT.

 

2. Order Partner Data Construction Rules

Field Name	Field Description	Rule
zLegacyAUFNR	Legacy Order Number	Mandatory. Key to link to Work Order
PARVW	Partner Function	Conditional Allowed values from TPAR to be populated
PARNR	Partner	Conditional Populate the Partner number for the required Partner Function

2. Order Operation Data Construction Rules

Field Name	Field Description	Rule
AUFNR	Legacy Order Number	Mandatory. Must be an existing legacy Work Order in Work Order Header DCT (AUFNR).
VORNR	Operation Number	Mandatory. Operation identifier for the given Work Order. Must be unique within the same AUFNR. Must be an integer / numeric value (no special characters).
VORNR	Suboperation Number	Conditional. Populate only if Suboperations are maintained in the legacy source. Must be unique within the same AUFNR + Parent Operation (as per legacy design). Otherwise, leave the field blank.
LTXA1	Operation Description	Mandatory. Populate a meaningful description for the Operation. 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
ARBPL	Work Center	Mandatory. Populate with the performing Work Center for the Operation. Value must exist in Work Center DCT. Work Center must follow naming convention defined in Work Center DCT (e.g., SXXXXNNN / EXXXXNNN / TXXXXNNN).
WERKS	Work Center Plant	Mandatory. Populate the Plant linked to the referenced Work Center (ARBPL). Allowed values: List from Value Mapping – Plant where Maintenance Plant = Yes. Must align to the Plant of the referenced Work Center.
PERNR	Person Responsible	Conditional. Populate only if Person Responsible is maintained for the performing Work Center / Operation in legacy. Must be a valid Person Responsible. Needs to be selected from value list (TC24). Otherwise, leave the field blank.
STEUS	Control Key	Mandatory. Allowed values: Needs to be selected from value list (Control Key configuration) as per target design. Must be a valid Control Key configured in SAP PM/CS.
SAKTO	Cost Element	Conditional. Populate only if the Operation is costed using a Cost Element in legacy (or required for external services). Allowed values: List from Value Mapping – Cost Element (Legacy → Target). Must be a valid G/L / Cost Element in target. Otherwise, leave the field blank.
EKORG	Purchasing Organization	Conditional. Populate only if the Operation is externally procured / service-related and purchasing data is required. Must be a valid Purchasing Organization (configuration table e.g., T024E). Otherwise, leave the field blank.
EKGRP	Purchasing Group	Conditional. Populate only if the Operation is externally procured / service-related and purchasing data is required. Must be a valid Purchasing Group (T024). Otherwise, leave the field blank.
MATKL	Material Group	Conditional. Populate only if Material Group is required for the Operation procurement / service. Must be a valid Material Group in target (e.g., T023). Otherwise, leave the field blank.
ANLZU	System Condition	Conditional. Populate only if System Condition is available at Operation level in legacy (or derived from Header if your design applies). Allowed values: List from Value Mapping – System Condition (Legacy → Target). Otherwise, leave the field blank.
ARBEI	Work	Mandatory. Numeric value only. Cannot be 0. Represents effort for the Operation (as per routing / order operation unit standards).
INDET	Calculation Key	Mandatory. Allowed values: Needs to be selected from value list (Calculation Key configuration). Must be a valid Calculation Key for capacity calculation in target.
ISTRU	Assembly	Conditional. Populate only if Assembly is maintained for the Operation in legacy. Allowed values: List from Value Mapping – Assembly (Legacy → Target), or must exist in the relevant Assembly construct (as defined by the program). Otherwise, leave the field blank.
ANZZL	Required Capacities	Mandatory. Must be an integer value. Cannot be 0.
EINSA	Start Constraint	Conditional. Populate only if Start Constraint logic is used for scheduling in target. Allowed values: Needs to be selected from value list (Start Constraint codes as per target configuration). Otherwise, leave the field blank.
NTANF	Start Constraint Date	Conditional. Populate only if EINSA is populated. Valid Date. Date Format DDMMYYYY. Otherwise, leave the field blank.
NTANZ	Start Constraint Time	Conditional. Populate only if EINSA is populated and time-level scheduling is required. Valid Time. Time Format HHMMSS. Otherwise, leave the field blank.
EINSE	Finish Constraint	Conditional. Populate only if Finish Constraint logic is used for scheduling in target. Allowed values: Needs to be selected from value list (Finish Constraint codes as per target configuration). Otherwise, leave the field blank.
NTEND	Finish Constraint Date	Conditional. Populate only if EINSE is populated. Valid Date. Date Format DDMMYYYY. Otherwise, leave the field blank.
NTENZ	Finish Constraint Time	Conditional. Populate only if EINSE is populated and time-level scheduling is required. Valid Time. Time Format HHMMSS. Otherwise, leave the field blank.
MGVRG	Operation Quantity	Conditional. Populate only if the Operation is quantity-based (e.g., service quantity) in the target design. Numeric value only. Cannot be 0. Otherwise, leave the field blank.
MEINH	Unit	Conditional. Populate only if MGVRG is populated. Must be a valid Unit of Measure in target (e.g., T006). Otherwise, leave the field blank.
PREIS	Price	Conditional. Populate only if the Operation is externally procured / service-related and price is maintained in legacy. Numeric value only. Cannot be negative. Otherwise, leave the field blank.
PEINH	Price Unit	Conditional. Populate only if PREIS is populated. Must be an integer value. Cannot be 0. Otherwise, leave the field blank.
LIFNR	Vendor	Conditional. Populate only if external vendor is assigned for the Operation. Must exist in Vendor / Business Partner DCT (as per target vendor model). Otherwise, leave the field blank.
WEMPF	Recipient	Conditional. Populate only if recipient is maintained for purchasing documents created from this Operation. Free text permitted as per target design. Otherwise, leave the field blank.
BEDNR	Tracking Number	Conditional. Populate only if a tracking number is maintained in legacy for PR/PO creation. Otherwise, leave the field blank.
SORTL	Sort Term	Conditional. Populate only if sort term is maintained in legacy for the vendor / procurement scenario. Otherwise, leave the field blank.
AFNAM	Name of Requisitioner	Conditional. Populate only if requisitioner name is maintained in legacy for PR/PO creation. Must be a valid person/user naming convention as per project standards (if defined). Otherwise, leave the field blank.

  

Extraction Dependencies

List the steps that need to occur before extraction can commence

Item #	Step Description	Team 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 Syniti Migrate to make the data Target ready:

1. Perform value mapping and data transformation rules.
   1. Legacy values are mapped to the to-be values (this could include a default value)
   2. Values are transformed according to the rules defined in Syniti Migrate
2. Prepare target-ready data in the structure and format that is required for loading via prescribed Load Tool. This step also produces the load data ready for business to perform Pre-load Data Validation

Transformation Run Sheet

Item #	Step Description	Team Responsible
1	Obtain DCT Sign-off from Business	SyWay A2D Data Team
2	<Add steps from Syniti Migrate here>	SyWay A2D Data Team
3	Review and Validate Error and Preload Reports	SyWay A2D Data Team
4	Generate Load Files	SyWay A2D Data Team

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1
2
3
4

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

Transformation Mapping

Use the exact name and reference this section in the “Transformation rules” above

Mapping Table Name	Mapping 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 Description	Team Responsible
1	Ensure DCT tables completeness	SyWay A2D Data Team
2	Value Mappings are according to the latest design - <List of Value Mappings>	SyWay A2D Data Team

Pre-Load Validation

Project Team

The following pre-load validations will be performed by the Project Team.

Completeness

Task	Action
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

Task	Action
Conversion Accuracy	SyWay A2D Data Team to verify that all fields below meet pass the checks: Mandatory Fields Field and Value Mapping Correctness Null Checks Text Length Checks
Review Error Reports	Review and correct the errors. Achieve a zero-error record count as much as possible. Raise defects for data remediated and requiring a correction in the source data.

Business

The following pre-load validations will be performed by the business.

Completeness

Task	Action
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

Task	Action
Conversion Accuracy	Business Data Owner/s to verify that all the data in the load table/file is accurate as per endorsed transformation/mapping rules (and signed-off DCT data).

Load

The load process includes:

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 Description	Team Responsible
1	Obtain DCT Sign-off from Business	SyWay A2D Data Team
2	Syniti will provide load file	Syniti
3	Go to <Load Tool>	SyWay A2D Data Team/Syniti
4	Load 3 records for Work Order for function (IW31) to validate if data is loaded successfully without errors	SyWay A2D Data Team/Syniti
5	Proceed with full load if step 4 is validated	SyWay A2D Data Team/Syniti
6	Validate few records loaded by accessing standard transactions from S/4HNA E.g. IW39	SyWay A2D Data Team/Syniti
7	Generate post load report if step 6 is validated	SyWay A2D Data Team/Syniti

Load Phase and Dependencies

Identify the phase as to “when” the load for this object will occur. <Pre-Cutover, Cutover, Post Cutover> and list the steps that need to occur before the load can commence

Configuration

List the Configurations required before loading can commence

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

The table below depicts some possible system errors for this data object during data load. All data load error is to be logged as defect and managed within the Defect Management

Error Type	Error Description	Action 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

The following post-load validations will be performed by the Project Team.

Completeness

Task	Action
Verify Count	SyWay A2D Data Team to verify the record count created in target S/4 HANA by accessing post load reports in dspMigrate or standard reports from S/4 HANA.
Verify Logs	Check if there is data that failed to load and perform the necessary actions (e.g. register as post load issue or attempt to load the record again, etc.).

Accuracy

Task	Action
Conversion Accuracy	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

The following post-load validations will be performed by the business.

Completeness

Task	Action
Verify Count	Download Post Load Reports from dspMigrate and verify that the record count loaded in the target S/4 HANA is the same count as of the endorsed load file.

Accuracy

Task	Action
Conversion Accuracy	Verify that the 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).

Any additional key assumptions.

See also

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log

Workflow history