Status

Page Status

Owner

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

This document defines the conversion approach to create Work Orders 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 serves as a detailed set of instructions, outlining tasks, required resources, parts, and schedules, while tracking costs, technical history, and compliance.

Legacy Plant Maintenance Work Orders use diverse formats across different systems. In line with the SyWay design, EAM Maintenance Work Orders will be standardized.

Conversion Scope

This document covers the approach for converting active Work Orders from legacy source systems into S/4HANA.

A work order in SAP is a formal document that authorizes and tracks maintenance, repair, or production tasks within an organization It contains essential details for effective task management and 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: Personnel, tools, and materials assigned for task completion.
Dates: Scheduled start and finish dates for timeline management.
Costing: Estimates for labour, materials, and other expenditures linked to budget accounts.
Priority & Status: Urgency level and progress tracking (e.g., created, released, completed, closed).
Operations: Step-by-step instructions or sub-tasks within the Work Order.

The data from legacy system includes:

All open Work Orders (AUFK-AUFNR) with Active (JEST-INAC <> 'X') System Status (JEST-STAT) = Created (CRTD) or Released (REL).
Work Orders (AUFK-AUFNR) with with Active (JEST-INAC <> 'X') System Status (JEST-STAT) = Technically Completed (TECO) and relevant open Purchase Order (EKKN-EBELN) as defined in CNV-9045 Open Purchase Orders
Work Orders (AUFK-AUFNR) with Maintenance Plant (AUFK-WERKS) existing in Value Mapping: Plant (Maintenance Plant = Yes).
Work Orders (AUFK-AUFNR) assigned to active legacy Functional Locations (IFLOT-TPLR) ** (Active (JEST-INAC <> 'X') System Status TJ02T-TXT04 <> INAC or DLFL) or Equipment (EQUI-EQUNR) ** (Active (JEST-INAC <> 'X') System Status TJ02T-TXT04 <> INAC or DLFL or ESTO or AVLB)
Work Orders (AUFK-AUFNR) generated from Maintenance Plan (AFIH-WARPL) with Basic Start Date (AFKO-GSTRP) <= Business Continuity Cutoff Date OTH_Migration_Date Relevant Values A2D (using Object ID "9001" and Field Name = "MHIS-NPLDA")
Work Orders (AUFK-AUFNR) linked to Notifications (AFIH-QMNUM) generated from Maintenance Plan (QMIH-WARPL) with Basic Start Date (AFKO-GSTRP) <= Business Continuity Cutoff Date OTH_Migration_Date Relevant Values A2D (using Object ID "9001" and Field Name = "MHIS-NPLDA")
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)

~~Logic for checking PO (Purchase Order) assigned to Work Order~~ -

~~Step~~	~~Table~~	~~Field(s)~~	~~Logic~~
1	~~AUFK / AFIH~~	~~AUFK-AUFNR = AFIH-AUFNR~~	~~Identify PM Work Order~~
2	~~EKKN~~	~~EKKN-AUFNR = AUFK-AUFNR~~	~~Find PO account assignment against the Work Order~~
3	~~EKPO~~	~~EKPO-EBELN = EKKN-EBELN and EKPO-EBELP = EKKN-EBELP~~	~~Get PO item~~
4	~~EKKO~~	~~EKKO-EBELN = EKPO-EBELN~~	~~Get PO header~~

~~Check if the PO (Purchase Order) is Open using~~-
~~EKPO-LOEKZ = space "Not deleted"~~
~~AND EKPO-ELIKZ = space "Final delivery / delivery completed not set"~~
~~AND EKPO-EREKZ = space "Final invoice not set"~~

The data from legacy system excludes:

Work Orders (AUFK-AUFNR) with Active (JEST-INAC <> 'X') System Status (JEST-STAT) = Technically Completed (TECO) that do not meet Inclusion Criteria #2
Work Orders(AUFK-AUFNR) with Active (JEST-INAC <> 'X') System Status (JEST-STAT) = Deletion Flag (DLFL) status
Work Orders (AUFK-AUFNR) with Active (JEST-INAC <> 'X') System Status (JEST-STAT) = Closed (CLSD) status
Work Orders (AUFK-AUFNR) with Active (JEST-INAC <> 'X') System Status (JEST-STAT) = Not Completed/ Do Not Execute (NCMP) status
Standing Work Orders (Value Mapping: Work Order Type, where Target WO Type = 'YA05').
Work Orders (AUFK-AUFNR) which are Sub-orders (AFKO-MAUFNR <> '')
Work Orders (AUFK-AUFNR) with blank Basic End Date (AFKO-GLTRP)
Work Orders (AUFK-AUFNR) with Order type (AUFK-AUART) maintained in Work Order Type Exclusion List (EXC-Work Order Type)
Work Orders (AUFK-AUFNR) with Active (JEST-INAC <> 'X') 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 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	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

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	Mandatory	Mandatory	Mandatory
AFKO	GSUZP	GSUZP	Basic Start Time	TIMS	6	Mandatory	Mandatory	Mandatory
AFKO	GLTRP	GLTRP	Basic Finish Date	DATS	8	Mandatory	Mandatory	Mandatory
AFKO	GLUZP	GLUZP	Basic Finish Time	TIMS	6	Mandatory	Mandatory	Mandatory
IFLOT	TPLNR	TPLNR	Functional Location	CHAR	30	Mandatory	Mandatory	Mandatory
AFIH	EQUNR	EQUNR	Equipment	CHAR	18	Conditional	Conditional	Conditional
AFIH	QMNUM	QMNUM	Assigned Notification	CHAR	12	Mandatory	Mandatory	Mandatory
AFIH	REVNR	REVNR	Maintenance Event/ Revision	CHAR	8	Conditional	Conditional	Conditional
AFIH	ILART	ILART	Maintenance Activity Type	CHAR	3	Mandatory	Mandatory	Mandatory
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	Mandatory	Mandatory	Mandatory
AFIH	INGPR	INGPR	Planner Group	CHAR	80	Mandatory	Mandatory	Mandatory
AUFK	WERKS	WERKS	Maintenance Plant	CHAR	4	Mandatory	Mandatory	Mandatory
ILOA	BEBER	BEBER	Plant Section	CHAR	3	Mandatory	Mandatory	Mandatory
ILOA	BUKRS	BUKRS	Company Code	CHAR	4	Mandatory	Mandatory	Mandatory
ILOA	PROID	PROID	WBS Element (Acc Assignment)	CHAR	8	Conditional	Conditional	Conditional
ILOA	KOSTL	KOSTL	Cost Center	CHAR	10	Mandatory	Mandatory	Conditional

2. Work Order Operation Data

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 Number	CHAR	4	Mandatory	Mandatory	Mandatory
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	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	Conditional	Conditional	Conditional
AFVV	ARBEI	ARBEI	Work	NUMC	7	Mandatory	Mandatory	Mandatory
AFVV	ARBEH	ARBEH	Work Unit	CHAR	3	Mandatory	Mandatory	Mandatory
AFVC	INDET	INDET	Calculation Key	CHAR	1	Mandatory	Mandatory	Mandatory
AFVV	DAUNO	DAUNO	Duration	NUMC	5	Mandatory	Mandatory	Mandatory
AFVV	DAUNE	DAUNE	Duration Unit	CHAR	3	Mandatory	Mandatory	Mandatory
AFVC	ANZZL	ANZZL	Required Capacities	NUMC	3	Mandatory	Mandatory	Mandatory
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	Operation Quantity Unit	CHAR	3	Conditional	Conditional	Conditional
AFVC	PREIS	PREIS	Price	CHAR	11	Conditional	Conditional	Conditional
AFVC	WAERS	WAERS	Currency	CHAR	5	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	Conditional	Conditional	Conditional
AFVC	AFNAM	AFNAM	Name of Requisitioner	CHAR	12	Conditional	Conditional	Conditional
AFVC	ABLAD	ABLAD	Unloading Point	CHAR	25	Conditional	Conditional	Conditional
AFVV	PLIFZ	PLIFZ	Planned Delivery Time - Day	NUMC	3	Conditional	Conditional	Conditional
AFVC	NO_DISP	NO_DISP	Reservation Relevance / Generation of Purchase Requisition	CHAR	1	Conditional	Conditional	Conditional

3. Work Order Operation Components

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 Number	CHAR	4	Mandatory	Mandatory	Mandatory
RESB	POSNR	POSNR	Item Number of Reservation	NUMC	4	Mandatory	Mandatory	Mandatory
RESB	MATNR	MATNR	Material	CHAR	18	Conditional	Conditional	Conditional
RESB	POTX1	POTX1	Description	CHAR	40	Conditional	Conditional	Conditional
RESB	POSTP	POSTP	Item Category	CHAR	1	Mandatory	Mandatory	Mandatory
RESB	BDMNG	BDMNG	Requirement Quantity	NUMC	13	Mandatory	Mandatory	Mandatory
RESB	MEINS	MEINS	Unit	CHAR	3	Mandatory	Mandatory	Mandatory
RESB	NO_DISP	NO_DISP	Reservation Relevance / Generation of Purchase Requisition	CHAR	1	Conditional	Conditional	Conditional
RESB	WERKS	WERKS	Plant	CHAR	4	Conditional	Conditional	Conditional
RESB	BDTER	BDTER	Requirements Date	DATS	8	Conditional	Conditional	Conditional
RESB	KZMPF	KZMPF	Manual Reqmt Date Indicator	CHAR	1	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,2	Conditional	Conditional	Conditional
RESB	PEINH	PEINH	Price Unit	NUMC	5	Conditional	Conditional	Conditional
RESB	WAERS	WAERS	Currency	CHAR	155	Conditional	Conditional	Conditional
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	Conditional	Conditional	Conditional
RESB	MATKL	MATKL	Material Group	CHAR	9	Conditional	Conditional	Conditional
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

4. Work Order Operation Relationships

Table	Field	Data Element	Field Description	Data Type	Length	Requirement YA01 (Reactive Maintenance)	Requirement YA02 (Proactive Maintenance)	Requirement YA03 (Project Order)
AUFK	AUFNR	AUFNR	Predecessor Order Number	CHAR	12	Mandatory	Mandatory	Mandatory
AFVC	VORNR	VORNR	Predecessor Operation	CHAR	4	Mandatory	Mandatory	Mandatory
AUFK	AUFNR	AUFNR	Successor Order Number	CHAR	12	Mandatory	Mandatory	Mandatory
AFVC	VORNR	VORNR	Successor Operation	CHAR	4	Mandatory	Mandatory	Mandatory
AFAB	AOBAR	AOBAR	Type of Relationship	CHAR	2	Mandatory	Mandatory	Mandatory
AFAB	DAUER	DAUER	Time Interval	NUMC	5	Conditional	Conditional	Conditional
AFAB	ZEINH	ZEINH	Unit	CHAR	3	Conditional	Conditional	Conditional

5. Work 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	CHAR	10	Mandatory	Mandatory	Mandatory
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

6. Work 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	Mandatory	Mandatory	Mandatory
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

7. Work Order Operation Capacity Requirement

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 Number	CHAR	4	Mandatory	Mandatory	Mandatory
KBED	ARBID	ARBID	Work Centre ID	CHAR	8	Mandatory	Mandatory	Mandatory
KBED	SPLIT	SPLIT	Split Number	CHAR	3	Mandatory	Mandatory	Mandatory
KBED	PERNR	PERNR	Personnel Number	CHAR	8	Mandatory	Mandatory	Mandatory
KBEZ	ARBEI	ARBEI	Work	NUMC	7	Mandatory	Mandatory	Mandatory
KBEZ	ARBEH	ARBEH	Unit of Work	CHAR	3	Mandatory	Mandatory	Mandatory
KBEZ	DAUNO	DAUNO	Normal Duration	NUMC	5	Mandatory	Mandatory	Mandatory
KBEZ	DAUNE	DAUNE	Normal duration unit	CHAR	3	Mandatory	Mandatory	Mandatory

8. Work 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. Work 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. Work Order 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. Work Order 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

ID

Criticality

Error Message/Report Description

Rule

Output

Source System

9005-001

C1

Open 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)

Note: Business to perform either of the below
a) Set Work Order Status to Technically Completed (TECO); or
b) Change Basic Start/ End date to a future date if still needed.

Order No, Order Type, Plant, Description, Creation Date

PF2, WP2

9005-002

C1

Open 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)

Note: Business to Set Work Order Status to Technically Completed (TECO).

Order No, Order Type, Plant, Description, Operation/ Activity No, Creation Date

PF2, WP2

9005-003

C1

Open Work Order with Blank Order Description

Work Order (AFKO-AUFNR) based on the relevancy criteria and Blank Short Text (AUFK-KTEXT = '')
Note: Business to Set appropriate Work Order description

Order No, Order Type, Plant

PF2, WP2

9005-004

C1

Open Work Order Operation with Blank Control Key

Work Order (AFKO-AUFNR) based on the relevancy criteria and Blank Control Key (AFVC-STEUS = '')

Note: Business to Set appropriate Work Order Operation Control Key

Order No, Order Type, Plant, Description, Operation/ Activity No

PF2, WP2

9005-005

C1

Open Work Order with Blank Order Operation Description

Work Order (AFKO-AUFNR) based on the relevancy criteria and Blank Operation Short Text (AFVC-LTXA1 = '')

Note: Business to Set appropriate Work Order Operation description

Order No, Order Type, Plant, Description, Operation/ Activity No

PF2, WP2

~~9005-006~~

C1

~~Completed Work Orders with Open Purchase Order and without any Reference Object (Functional Location/ Equipment assigned)~~

Work Order (AFKO-AUFNR)with System Status (JEST-STAT) 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 with no Technical Object (Functional Location/ Equipment/ Assembly) assigned on the WO header i,e (AFIH-ILOAN = '') and (AFIH-EQUNR = '') and (AFIH-BAUTL ='').

Note: Business to perform the below
a) Reverse TECO status for these Work Order
b) Populate the Functional Location/ Equipment on the WO Header
c) Complete (TECO) the Work Order

~~If not cleansed, these would have to be dealt after Go-Live.~~

~~Order No, Order Type, Plant, Description~~

~~PF2, WP2~~

9005-007

C1

Release Work Orders with Operations having Blank value maintained for any of the below fields -

Work
Duration
No of Capacities

Work Order (AFKO-AUFNR)with System Status (JEST-STAT) = 'REL' and having Operation with any of the below fields with Blank value
-Work
-Duration
-No of Capacities

Note: Business to Set required values for the above Work Order Operation fields

Order No, Order Type, Plant, Description, Operation/ Activity No, Calculation Key, Work, Duration, No of Capacities

PF2, WP2

~~9005-008~~

C1

~~Open Work Orders with Basic Start Date in future and not having any PO assigned~~

Work Orders with no open PO, with Basic Start Date (AFKO-GSTRP) later than the Migration / "Go-Live" Date (OTH_Migration_Date Relevant Values A2D (using Object ID "9005" and Field Name = "AFKO-GSTRP") and Priority (AFIH-PRIOK) existing in the below list -

~~Source~~	~~PriorityType~~	~~Priority~~	~~Priority~~
~~PF2~~	Z1	6	~~For next shutdown~~
~~PF2~~	Z5	6	~~Next shutdown~~
~~PF2~~	Z5	8	~~Turnaround 1YR~~
~~PF2~~	Z6	5	~~For next shutdown~~
~~WP2~~	ZP	5	~~For next shutdown~~

Note: Business to create PO in source, otherwise these orders will not be migrated

~~Order No, Order Type, Plant, Description, Creation Date, Basic Start Date~~

~~PF2, WP2~~

009~~9005-~~

C3

~~Info Report: Open Work Orders with External Operations/ Externally procured material but no Purchase Order existing~~

Open Work Orders with External Operations i.e where Operation Control Key (AFVC-STEUS) has External Processing Flag (T430-LIEF) <> '' and no Purchase Order existing (Check relevancy section for logic to find PO assigned to WO).

~~Note: These Work Orders Component line items will not be not migrated~~

~~Order No, Order Type, Plant, Description, Operation, Component, Component Description, System Status~~

~~PF2, WP2~~

~~9005-010~~

C3

~~Info Report: Open Work Orders with Open Purchase Order~~

~~Work 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 Orders~~

~~Order No, Order Type, Plant, Description, Purchase Order No, Purchase Order Item~~

~~PF2, WP2~~

9005-011

C3

Info Report: Open Work Orders with Outstanding Reservation

Work 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)

Note: Business to check for the scenarios and cleanse accordingly -
- Component no longer needed (wrong material / quantity / duplicate)
- Full qty already issued but reservation not “completed”
- Partial issue done, remainder will NOT be issued
- Order is TECO/closed but reservation/PR not marked for deletion
- Components in order but RESB still shows entries

Order No, Order Type, Plant, Description, Reservation No, Material No, Required Quantity, Withdrawal Quantity

PF2, WP2

9005-012

C3

Info 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, Description

PF2, WP2

~~9005-013~~

C3

~~Info Report: Open Work Orders that have external services assigned and PO existing~~

Work 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 Orders and having Service Items (EKPO-PSTYP = '9')

~~Order No, Order Type, Plant, Description, Purchase Order, Purchase Order Item~~

~~PF2, WP2~~

9005-014

C3

Info Report: Open Work Orders with Functional Location and Assembly assigned and not Equipment

Work 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, Assembly

PF2, WP2

9005-015

C3

Info 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, Description

PF2, WP2

9005-016

C3

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

PF2, WP2

9005-017

C3

Info 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, Description

PF2, WP2

9005-018

C3

Info Report: Open Work Order with Materials assigned to Object List

Work Order (AFKO-AUFNR) based on the relevancy criteria for which Object List contains Materials (OBJK-MATNR).

Note: These Work Orders Object List entries will not be not migrated

Order No, Order Type, Plant, Description, Material, Material Description

PF2, WP2

9005-019

C3

Info Report: Open Refurbishment Work Orders

Work Order (AFKO-AUFNR) based on the relevancy criteria having Order Type (AUFK-AUART) = 'ZPM4'

Note: These Work Orders will not be not migrated

Order No, Order Type, Plant, Description

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:

The data exists. connects to the source and loads the data into the repository. There are 3 methods:

Perform full data extraction from relevant tables in the source system(s).
Perform extraction through the application layer.
Only if ADMM cannot connect to the source, data is loaded to the repository from the provided source system extract/report.

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 Description	Team Responsible
1	Extract data from source system based on relevancy rule	SyWay Data Team

Selection Screen

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 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 Name	Field Description	Rule
WERKS	Plant	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.
AUART	Order Type	Mandatory. Allowed values: YA01 Reactive Maintenance YA02 Proactive Maintenance YA03 Project Orders
KCHAR	Description	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
PRIOK	Priority	Mandatory. Needs to be selected from value list (T356).
GSTRP	Basic Start Date	Mandatory. Populate the Work Order planned start date in YYYYMMDD format.
GSUZP	Basic Start Time	Mandatory. Populate the Work Order planned start time in HHMMSS format.
GLTRP	Basic End Date	Mandatory. Populate the Work Order planned end date in HHMMSS format.
GLUZP	Basic End Time	Mandatory. Populate the Work Order planned end time in HHMMSS format.
TPLNR	Functional Location	Mandatory. Populate the Functional Location associated to the asset. Value must exist in Functional Location DCT.
EQUNR	Equipment	Conditional. Populate if the Asset being maintained is an Equipment. Otherwise, leave the field blank. Value must exist in Equipment DCT.
ILART	Maintenance Activity Type	Mandatory. Needs to be selected from value list (T353I) where ILART starting with M (M01, M02...)
PROID	WBS Element (Acc Assignment)	Conditional. Populate only for Project Work Orders Should be a valid WBS Element (S4)

2. Work Order Operation Data Construction Rules

Field Name	Field Description	Rule
WERKS	Plant	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. Must exist in Order Header DCT.
zLegacyVORNR	Legacy 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.
LTXA1	Operation 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
PERNR	Person Responsible	Conditional Populate the Personnel Number of the person responsible/assigned to perform the operation. Value must be an active Person Responsible.
STEUS	Control Key	Mandatory. Populate appropriate Control Key based on the how the operation is to be processed (internal/external, etc.). Needs to be selected fromValue List (T430) with pattern 'PMXX'
SAKTO	Cost Element	Conditional. Populate the Cost posting account for external services/materials depending on process. Should be a valid Cost Element (S4)
EKORG	Purchasing Organisation	Conditional. Populate Purchasing org responsible for procurement activities. Needs to be selected from value list (T024E)
EKGRP	Purchasing Group	Conditional. Populate Buyer/group responsible for procurement. Needs to be selected from value list (T024)
MATKL	Material Group	Conditional. Populate Material Group for the required Materials/ Services. Needs to be selected from value list (T023)
ANLZU	System Condition	Conditional. Populate Condition of the System/ Asset during the maintenance activity. Needs to be selected from value list (T375M)
DAUNO	Duration	Mandatory. Populate duration to perform the activity.
ANZZL	Required Capacities	Mandatory. Populate the number of required capacities to perform the activity. Must be an integer value. Cannot be 0.
EINSA	Start 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 - 1 - Must start on 2 - Cannot start before 3 - Cannot start later 5 - Start from resource planning
NTANF	Start 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.
NTANZ	Start Constraint Time	Conditional. Time for the constrained start Populate only if EINSA and NTANF is populated. Otherwise, leave the field blank. Time Format HHMMSS.
EINSE	Finish 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 - 1 - Must finish on 2 - Cannot finish before 3 - Finish not later 4 - Finish from confirmation
NTEND	Finish 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.
NTENZ	Finish 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.
MGVRG	Operation 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.
MEINH	Unit	Conditional. Populate only if MGVRG is populated. Otherwise, leave the field blank. Needs to be selected from value list (T006)
PREIS	Price	Conditional. Populate price amount only if the Operation is externally procured / service-related. Otherwise, leave the field blank. Numeric value only. Cannot be negative.
PEINH	Price 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.
LIFNR	Vendor	Conditional. Populate external vendor for the external service/ material if information exist. Otherwise, leave the field blank. Value must exist in Vendor DCT
WEMPF	Recipient	Conditional. Populate Goods recipient name for purchasing documents if information exists. Otherwise, leave the field blank.
BEDNR	Tracking Number	Conditional. Populate tracking number for PR/PO creation if information exists. Otherwise, leave the field blank.
SORTL	Sort Term	Conditional. Populate sort term for the procurement scenario if information exists. Otherwise, leave the field blank.
AFNAM	Name of Requisitioner	Conditional. Populate name of the Person requesting procurement if information exists. Otherwise, leave the field blank.
NO_DISP	Reservation Relevance / Generation of Purchase Requisition	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. Note~~: This will be set to 1 (Never) if the Purchase Order exist for the Operation.~~

3. Work Order Operation Components Data Construction Rules

Field Name

Field Description

Rule

WERKS

Plant

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

zLegacyVORNR

Legacy Operation Number

Mandatory.

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

POSNR

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

MATNR

Material

Conditional

Populate with legacy Material number for the component line.

Value must exist in Material Master Basic view DCT

POTX1

Description

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

POSTP

Item Category

Mandatory.

Populate a valid component item category from the below.

Item Category	Description	Procurement Via
L	Stock Item	Inventory
N	Non-Stock Item	Purchase Req
E	Enhanced Limit	Purchase Req

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

BDMNG

Quantity

Mandatory.

Populate Component quantity requested for the component line.

MEINS

Unit

Mandatory.

Populate if BDMNG is populated.

Needs to be selected from value list (T006)

NO_DISP

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

~~Note: This will be set to 1 (Never) if the Purchase Order exist for the Component.~~

BDTER

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

KZMPF

Manual Reqmt Date Indicator

Conditional

Populate Maintenance of Requirement Date Flag from the below list.

'' = NO
'X' = YES

LGORT

Storage Location

Conditional

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

Needs to be selected from value list (T001L) specifc to the Plant (WERKS) for which the data is being populated.

GPREIS

Price

Conditional

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

PEINH

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

WAERS

Currency

Conditional

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

Needs to be selected from value list (TCURC)

EKORG

Purchasing Organisation

Conditional.

Populate Purchasing org responsible for procurement activities.

Needs to be selected from value list (T024E)

EKGRP

Purchasing Group

Conditional.

Populate Buyer/group responsible for procurement.

Needs to be selected from value list (T024)

LIFNR

Supplier

Conditional.

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

Value must exist in Value Mapping: Vendor Number

INFNR

Purchasing 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

MATKL

Material Group

Conditional.

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

Needs to be selected from value list (T023)

SAKNR

G/L Account

Conditional

Populate G/L account as required for account assignment.

Value must exist in Value Mapping: GL Account

WEMPF

Goods Recipient

Conditional

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

ABLAD

Unloading Point

Conditional

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

STARTDATE

Service Performance Start Date

Conditional