| Status | Revision in Progress |
|---|---|
| Owner | |
| Stakeholders |
Purpose
The purpose of this document is to define the conversion approach to create Work Order in S/4 HANA.
A Work Order in SAP PM is a technical and financial document used to plan, execute, and settle maintenance tasks on technical objects. It acts as a detailed instruction, outlining tasks, required resources, parts, and schedules, while tracking costs, technical history, and compliance.
Legacy Plant Maintenance Work order is using a diverse range of formats across the different systems. As per SyWay design, EAM Maintenance Work order will be standardized.
Conversion Scope
The scope of this document covers the approach for converting active Work Order from Legacy Source Systems into S/4HANA.
A work order in SAP is a formal document that authorises and tracks maintenance, repair, or production tasks within an organisation, containing essential details for effective task management. It is used to manage and document various tasks, including maintenance, repairs, and production activities. Key components of a work order include:
- Work Description: Specific details of the task to be carried out
- Equipment Details: Information about the asset or machinery requiring attention
- Resources: Assignment of personnel, tools, and materials needed for task completion
- Dates: Scheduled start and finish dates to manage timelines
- Costing: Estimates for labour, materials, and other expenditures linked to budget accounts
- Priority & Status: Indicates urgency and tracks progress (e.g., created, released, completed, closed)
- Operations: Step-by-step instructions or tasks within the work order.
The data from legacy system includes:
- All open Work Orders (AUFK-AUFNR) with System Status (JEST-STAT) = Created (CRTD) or Released (REL).
- Work Orders with System Status (JEST-STAT) = Technically Completed (TECO) and an open Purchase Order assigned that is not flagged as Final Invoice or Final Delivery
- Work Orders with Maintenance Plant (IFLOT-WERKS) in scope.
- Work Orders assigned to active legacy Functional Locations (IFLOT-TPLNR) and Equipment (EQUI-EQUNR)
- 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:
- Work Orders with System Status (JEST-STAT) = Technically Completed (TECO) that do not meet Inclusion Criteria #2
- Work Orders with System Status (JEST-STAT) = Deletion Flag (DLFL) status
- Work Orders with System Status (JEST-STAT) = Closed (CLSD) status
- Work Orders with System Status (JEST-STAT) = Not Completed/ Do Not Execute (NCMP) status
- Standing Work Orders
- Sub-orders
- Work Orders with blank Basic End Date
- Work Orders with Order type maintained in Work Order Type Exclusion List
- Work Orders with System Status (JEST-STAT) <> Technically Completed (TECO) System Status and with a User Status maintained in the User Status Exclusion List
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
PF2, WP2 | An initial extract will be provided to business to evaluate. Additional data/records may be required and these will be constructed via DCT. Enrichment of in-scope data may be required and will be added via transformation rules (business/technical). | 140,000 | S/4HANA | 140,000 |
Additional Information
Multi-language Requirement
Work Order does not have multi language support. Work Order and Notification text will be migrated using EN logon.
Document Management
Long text and DIR are not covered in this document as they are defined as another data object.
Legal Requirement
Not Applicable
Special Requirements
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) |
|---|---|---|---|---|---|---|---|---|
| S_HEADER | ORDERID | ORDERID | Order Number | Text | 80 | Mandatory | Mandatory | Mandatory |
| S_HEADER | ORDER_TYPE | ORDER_TYPE | Order Type | Text | 80 | Mandatory | Mandatory | Mandatory |
| S_HEADER | SHORT_TEXT | SHORT_TEXT | Description | Text | 40 | Mandatory | Mandatory | Mandatory |
| S_HEADER | LONG_TEXT | LONG_TEXT | Long Text | Text | unrestricted | Optional | Optional | Optional |
| S_HEADER | PRIORITY | PRIORITY | Priority | Text | 80 | Mandatory | Mandatory | Mandatory |
| S_HEADER | START_DATE | START_DATE | Required Start Date | Date | System | System | System | |
| S_HEADER | BASICSTART | BASICSTART | Required Start Time | Time | System | System | System | |
| S_HEADER | FINISH_DATE | FINISH_DATE | Required End Date | Date | System | System | System | |
| S_HEADER | BASIC_FIN | BASIC_FIN | Required End Time | Time | System | System | System | |
| S_HEADER | LACD_DATE | LACD_DATE | Final Due Date | Date | System | System | System | |
| S_HEADER | FUNCT_LOC | FUNCT_LOC | Technical Object (Functional Location) | Text | 80 | Mandatory | Mandatory | Mandatory |
| S_HEADER | EQUIPMENT | EQUIPMENT | Technical Object (Equipment) | Text | 80 | Optional | Optional | Optional |
| S_HEADER | ASSEMBLY | ASSEMBLY | Assembly | Text | 80 | Optional | Optional | Optional |
| S_HEADER | SYSTCOND | SYSTCOND | System Condition | Text | 80 | Optional | Optional | Optional |
| S_HEADER | NOTIF_NO | NOTIF_NO | Assigned Notification | Text | 80 | System | System | System |
| S_HEADER | PMACTTYPE | PMACTTYPE | Maintenance Activity Type | Text | 80 | Mandatory | Mandatory | Mandatory |
| S_HEADER | MN_WK_CTR | MN_WK_CTR | Work Center | Text | 80 | Mandatory | Mandatory | Mandatory |
| S_HEADER | PLANT | PLANT | Work Center Plant | Text | 80 | Mandatory | Mandatory | Mandatory |
| S_HEADER | PLANPLANT | PLANPLANT | Planning Plant | Text | 80 | System | System | System |
| S_HEADER | PLANGROUP | PLANGROUP | Plangroup | Text | 80 | System | System | System |
| S_HEADER | LOC_WK_CTR | LOC_WK_CTR | Production Work Center | Text | 80 | System | System | System |
| S_HEADER | MAINTPLANT | MAINTPLANT | Maintenance Plant | Text | 80 | System | System | System |
| S_HEADER | LOCATION | LOCATION | Location | Text | 80 | N/A | N/A | N/A |
| S_HEADER | MAINTROOM | MAINTROOM | Room | Text | 8 | System | System | System |
| S_HEADER | PLSECTN | PLSECTN | Plant Section | Text | 80 | System | System | System |
| S_HEADER | LOC_COMP_CODE | LOC_COMP_CODE | Company Code | Text | 80 | System | System | System |
| S_HEADER | LOC_WBS_ELEM | LOC_WBS_ELEM | WBS Element (Acc Assignment) | Text | 80 | N/A | N/A | Conditional |
| S_HEADER | COSTCENTER | COSTCENTER | Cost Center | Text | 80 | Mandatory | Mandatory | Conditional |
| S_HEADER | RESPCCTR | RESPCCTR | Responsible Cost Center | Text | 80 | System | System | System |
| S_HEADER | WBS_ELEM | WBS_ELEM | Planning WBS Element | Text | 80 | System | System | System |
| S_HEADER | OBJECTCLASS | OBJECTCLASS | Object Class | Text | 80 | System | System | System |
| S_HEADER | PROFIT_CTR | PROFIT_CTR | Profit Center | Text | 80 | System | System | System |
2. Order Phase Control
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement YA01 (Reactive Maintenance) | Requirement YA02 (Proactive Maintenance) | Requirement YA03 (Project Order) |
|---|---|---|---|---|---|---|---|---|
| S_HEADER | ORDERID | ORDERID | Order Number | Text | 80 | Mandatory | Mandatory | Mandatory |
Data Cleansing
| ID | Criticality | Error Message/Report Description | Rule | Output | Source System |
|---|---|---|---|---|---|
9005-001 | C1 | Invalid or Inactive Equipment or Functional Location linked to Work Order | Work Order as per Relevancy Criteria assigned with an Equipment / Functional which does not belong below: The criteria for this report includes all Work Orders with system status not CRTD and not TECO | Equipment, Functional Location | PF2, WP2 |
9005-002 | C1 | Invalid or Inactive Activity Type linked to Work Order | Work Order as per Relevancy Criteria assigned with an Activity Type which does not belong below: | Activity Type | PF2, WP2 |
9005-003 | C1 | Invalid or Inactive Business Partner (Employee Personnel) linked to Work Order | Work Order as per Relevancy Criteria assigned with a Business Partner (Employee Personnel) which does not belong below: | Business Partner (Employee) | PF2, WP2 |
9005-004 | C1 | Invalid or Inactive Cost Centre linked to Work Order | Work Order as per Relevancy Criteria assigned with a Cost Centre which does not belong below: | Cost Centre | PF2, WP2 |
9005-005 | C1 | Invalid or Inactive Maintenance Item linked to Work Order | Work Order as per Relevancy Criteria assigned with a Maintenance Plan and Item which does not belong below: | Maintenance Item | PF2, WP2 |
9005-006 | C1 | Invalid or Inactive Material linked to Work Order | Work Order as per Relevancy Criteria assigned with a Material which does not belong below: | Material | PF2, WP2 |
9005-007 | C1 | Invalid or Inactive Notification linked to Work Order | Work Order as per Relevancy Criteria assigned with a Notification which does not belong below: | Notification | PF2, WP2 |
9005-008 | C1 | Invalid or Inactive Production Resources & Tool linked to Work Order | Work Order as per Relevancy Criteria assigned with a Production Resources & Tool which does not belong below: | Production Resources & Tool | PF2, WP2 |
9005-009 | C1 | Invalid or Inactive Profit Centre linked to Work Order | Work Order as per Relevancy Criteria assigned with a Profit Centre which does not belong below: | Profit Centre | PF2, WP2 |
9005-010 | C1 | Invalid or Inactive Revision linked to Work Order | Work Order as per Relevancy Criteria assigned with a Revision which does not belong below: | Revision | PF2, WP2 |
9005-011 | C1 | Invalid or Inactive Standard Text linked to Work Order | Work Order as per Relevancy Criteria assigned with a Standard Text which does not belong below: | Standard Text | PF2, WP2 |
9005-012 | C1 | Invalid or Inactive Task List linked to Work Order | Work Order as per Relevancy Criteria assigned with a Task List which does not belong below: | Task List | PF2, WP2 |
9005-013 | C1 | Invalid or Inactive WBS linked to Work Order | Work Order as per Relevancy Criteria assigned with a WBS which does not belong below: | Work Breakdown Structure | PF2, WP2 |
9005-014 | C1 | Invalid or Inactive Work Centre linked to Work Order | Work Order as per Relevancy Criteria assigned with a Work Centre which does not belong below: | Work Centre | PF2, WP2 |
9005-015 | C1 | Invalid, Inactive or no Fixed Asset linked to Work Order | Work Order as per Relevancy Criteria assigned with a Fixed Asset which does not belong below: | Fixed Asset | PF2, WP2 |
9005-016 | C1 | Work Orders technically completed but with Open Commitments (POs not closed, Open reservations, Open PR) | TBD | Work Order, Status | PF2, WP2 |
9005-017 | C2 | Open Work Orders older than 1 month | Open Work Orders older than 12 months | Creation Date, Status | PF2, WP2 |
9005-018 | C2 | Open Priority Work Orders older than 2 weeks | Open Work Orders older than 3 months with Priority as follows: | Creation Date, Status, Priority | PF2, WP2 |
9005-019 | C1 | Notification Storage Location incorrect. | Notificationas per Relevancy Criteria with Invalid Storage Location (T001L) | Storage Location | PF2, WP2 |
9005-020 | C1 | Work Order Plant incorrect. | Work Order as per Relevancy Criteria with Invalid Plant (T001W) | Plant | PF2, WP2 |
9005-021 | C1 | Work Order UOM Missing / incorrect. | Work Order as per Relevancy Criteria with no UoM Assigned or Invalid UoM (T006) | Unit of Measure | PF2, WP2 |
9005-022 | C1 | Work Order Purchasing Groups incorrect. | Work Order as per Relevancy Criteria with Invalid Purchasing Group (T024) | Purchasing Group | PF2, WP2 |
9005-023 | C1 | Work Order Purchasing Organization incorrect. | Work Order as per Relevancy Criteria with Invalid Purchasing Organization (T024E) | Purchasing Organization | PF2, WP2 |
9005-023 | C2 | Work Order Planning Plant and Maintenance Plant are not the same. | Work Order as per Relevancy Criteria with Planning Plant <> Maintenance Plant | Maintenance Plant, Planning Plant | PF2, WP2 |
9005-024 | C2 | Work Order Description contains Thai characters | Work Order Description contains Thai characters | Description | PF2, WP2 |
For reference: SyWay_Cleansing and Historical Scope - A2D
Informal Words **
Group 1 | Group 2 | Group 3 | Group 4 | Group 5 |
|---|---|---|---|---|
*DNU | Delete | donot | Formerly | Old # |
.. | Deletion | DONT USE | From | Old[ ] |
/ | DELISTED | DON'T USE | Incorrect | PLEASE USE |
? | Discontinued | Dup Use | Invalid | Pls Use |
@ | Disposable | DUPLICATE | New | Previously |
^ | DNU | -DUPLICATE | NOT ACTIVE | Replace |
+ | Do Not | DUPLICATION | not in use | Replaced |
++ | Do Not Re | Duplicidad | Not Used | RESERVED |
£ | Do Not Sell | Duplikat | NOT VALID | Retired |
Defective | Do Not Use | Former | Obsolete | ZZDEL |
Conversion Process
Conversion will involve both Source System Extraction as well as using DCT (Data Collection Template) -
The high-level process for Source System Extraction is represented by the diagram below:
For sites that are not on SAP-PF2 and WP2 systems, collection will be done manually in the data collection template.
The high-level process for DCT is represented by the diagram below:
Data Privacy and Sensitivity
Extraction
Extract data from a source into . There are 2 possibilities:
- The data exists. connects to the source and loads the data into . There are 3 methods:
- Perform full data extraction from relevant tables in the source system(s).
- Perform extraction through the application layer.
- Only if ; 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 . 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 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
| 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 data with exception of some fields which require transformation as mentioned in the transformation rule.Work Order DCT Rules
- AUFK - Work Order main table
| Field Name | Field Description | Rule |
|---|---|---|
| AUFNR | Order Number | |
| AUART | Order Type | |
| KTEXT | Description | |
| LONG_TEXT | Long Text | |
| PPRIO | Priority | |
| SDATE | Required Start Date | |
| BASICSTART | Required Start Time | |
| FINISH_DATE | Required End Date | |
| BASIC_FIN | Required End Time | |
| LACD_DATE | Final Due Date | |
| FUNCT_LOC | Technical Object (Functional Location) | |
| EQUIPMENT | Technical Object (Equipment) | |
| ASSEMBLY | Assembly | |
| SYSTCOND | System Condition | |
| NOTIF_NO | Assigned Notification | |
| PMACTTYPE | Maintenance Activity Type | |
| MN_WK_CTR | Work Center | |
| PLANT | Work Center Plant | |
| PLANPLANT | Planning Plant | |
| PLANGROUP | Plangroup | |
| LOC_WK_CTR | Production Work Center | |
| MAINTPLANT | Maintenance Plant | |
| LOCATION | Location | |
| MAINTROOM | Room | |
| PLSECTN | Plant Section | |
| LOC_COMP_CODE | Company Code | |
| LOC_WBS_ELEM | WBS Element (Acc Assignment) | |
| COSTCENTER | Cost Center | |
| RESPCCTR | Responsible Cost Center | |
| WBS_ELEM | Planning WBS Element | |
| OBJECTCLASS | Object Class | |
| PROFIT_CTR | Profit Center |
2. AFKO- Work Order header table
| Field Name | Field Description | Rule |
|---|---|---|
| AUFNR | Order Number | |
| GLTRP | Basic finish date | |
| GSTRP | Basic Start Date | |
| FTRMS | Scheduled release date | |
| GLTRS | Scheduled finish | |
| GSTRS | Scheduled start | |
| GSTRI | Actual start date | |
| GETRI | Confirmed Order Finish Date | |
| GLTRI | Actual finish date | |
| FTRMI | Actual release date | |
| FTRMP | Planned release date | |
| RSNUM | Number of Reservation/Dependent Requirement | |
| GASMG | Total scrap quantity in the order | |
| GAMNG | Total order quantity | |
| GMEIN | Base Unit of Measure | |
| PLNBEZ | Material Number | |
| PLNTY | Task List Type | |
| PLNNR | Key for Task List Group | |
| PLNAW | Application of the task list | |
| PLNAL | Group Counter | |
| PVERW | Task list usage | |
| PLAUF | Date for routing transfer | |
| PLSVB | To lot size | |
| PLNME | Task list unit of measure | |
| PLSVN | From Lot Size | |
| PDATV | Valid-From Date | |
| PAENR | Change Number | |
| PLGRP | Responsible planner group/department | |
| LODIV | Lot size divisor | |
| STLTY | BOM category | |
| STLBEZ | Material Number | |
| STLST | BOM status | |
| STLNR | Bill of material | |
| SDATV | Valid-From Date | |
| SBMNG | Base quantity | |
| SBMEH | Base Unit of Measure | |
| SAENR | Change Number | |
| STLAL | Alternative BOM | |
| STLAN | BOM Usage | |
| SLSVN | From Lot Size | |
| SLSBS | To Lot Size | |
| AUFLD | Date of BOM Explosion/Routing Transfer | |
| DISPO | MRP controller for the order | |
| AUFPL | Routing number of operations in the order | |
| FEVOR | Production Supervisor | |
| FHORI | Scheduling Margin Key for Floats | |
| TERKZ | Scheduling type | |
| REDKZ | Reduction indicator for scheduling | |
| APRIO | Order priority | |
| NTZUE | Superior network number | |
| VORUE | Superior activity | |
| PROFID | Network profile | |
| VORGZ | Float before production (in days) | |
| SICHZ | Float after production (in days) | |
| FREIZ | Release period (in days) | |
| UPTER | Indicator: Change to Scheduled Dates | |
| BEDID | ID of the capacity requirements record | |
| PRONR | Project definition | |
| ZAEHL | Internal counter | |
| MZAEHL | Internal counter | |
| ZKRIZ | Counter for additional criteria | |
| PRUEFLOS | Inspection Lot Number | |
| KLVARP | Costing variant for planned costs | |
| KLVARI | Costing variant for actual costs | |
| RGEKZ | Indicator: Backflushing for order | |
| PLART | Basis for scheduling | |
| FLG_AOB | Indicator: relationships | |
| FLG_ARBEI | Indicator: Default value work is relevant | |
| GLTPP | Finish date (forecast) | |
| GSTPP | Forecast start date | |
| GLTPS | Scheduled forecast finish | |
| GSTPS | Scheduled forecast start | |
| FTRPS | Scheduled release date (forecast) | |
| RDKZP | Reduction indicator for scheduling (forecast) | |
| TRKZP | Scheduling type (forecast) | |
| RUECK | Completion confirmation number for the operation | |
| RMZHL | Internal counter | |
| IGMNG | Yield confirmed from order confirmation | |
| RATID | ID of the capacity requirements record | |
| GROID | ID of the capacity requirements record | |
| CUOBJ | Configuration (internal object number) | |
| GLUZS | Scheduled finish time | |
| GSUZS | Scheduled Start (Time) | |
| REVLV | Revision Level | |
| RSHTY | Object types of the CIM resource | |
| RSHID | Object ID of the resource | |
| RSNTY | Object types of the CIM resource | |
| RSNID | Object ID of the resource | |
| NAUTERM | Indicator: Do not schedule automatically | |
| NAUCOST | Indicator: Do not cost automatically | |
| STUFE | Level (in multi-level BOM explosions) | |
| WEGXX | Path (for multi-level BOM explosions) | |
| VWEGX | Path (for multi-level BOM explosions) | |
| ARSNR | Number of Reservation/Dependent Requirement | |
| ARSPS | Order Item Number | |
| MAUFNR | Number of superior order | |
| LKNOT | Left node in collective order | |
| RKNOT | Right node of a collective order | |
| PRODNET | Indicator: Order is part of collective order | |
| IASMG | Scrap confirmed for order | |
| ABARB | Confirmation: Degree of processing | |
| AUFNT | Number of superior network | |
| AUFPT | Routing number of operations in the order | |
| APLZT | General counter for order | |
| NO_DISP | Effective for Materials Planning | |
| CSPLIT | Apportionment Structure | |
| AENNR | Change Number | |
| CY_SEQNR | Seq. number order | |
| BREAKS | Indicator: Scheduling allowing for breaks | |
| VORGZ_TRM | Scheduled float before production in days | |
| SICHZ_TRM | Scheduled float after production in days | |
| TRMDT | Date of the last scheduling | |
| GLUZP | Basic finish (time) | |
| GSUZP | Basic start time | |
| GSUZI | Actual start time | |
| GEUZI | Confirmed order finish (time) | |
| GLUPP | Forecast finish (time) | |
| GSUPP | Forecast start (time) | |
| GLUPS | Scheduled forecast finish time | |
| GSUPS | Scheduled start time (Forecast) | |
| CHSCH | Search procedure for batch determination | |
| KAPT_VORGZ | Float (bef. production) remaining after finite scheduling | |
| KAPT_SICHZ | Remaining float after finite scheduling | |
| LEAD_AUFNR | Leading order in current processing | |
| PNETSTARTD | Outline start of collective network (date) | |
| PNETSTARTT | Start time of a collective order | |
| PNETENDD | Outline finish of collective order (date) | |
| PNETENDT | Outline finish time | |
| KBED | Ind: do not create capacity requirements | |
| KKALKR | Indicator: Components will not be costed | |
| SFCPF | Production Scheduling Profile | |
| RMNGA | Total confirmed rework quantity | |
| GSBTR | Overall commitment date | |
| VFMNG | Committed quantity for order acc. to ATP check components | |
| NOPCOST | Do not calculate planned costs for order | |
| NETZKONT | Indicator for the account assignment of a network(hdr/act.) | |
| ATRKZ | Request ID | |
| OBJTYPE | Change indicator | |
| CH_PROC | Process that has lead to the change of an object | |
| KAPVERSA | Version of Available Capacity | |
| COLORDPROC | Collective order with/without automatic goods movement | |
| KZERB | Indicator: Project summarization via master data charact. | |
| CONF_KEY | Identical object | |
| ST_ARBID | Object ID | |
| VSNMR_V | Sales document version number | |
| TERHW | Scheduling note from order scheduling | |
| SPLSTAT | Status of an order in a split hierarchy | |
| COSTUPD | Costs are updated | |
| MAX_GAMNG | Maximum Value of Total Order Quantity After Distribution | |
| MES_ROUTINGID | Key of a Routing from an ME System | |
| .INCLU--AP | ||
| ADPSP | PM/PS Reference Element | |
| RMANR | Sales and Distribution Document Number | |
| POSNR_RMA | Item number of the SD document | |
| POSNV_RMA | Item number of the SD document | |
| CFB_MAXLZ | Maximum Storage Period | |
| CFB_LZEIH | Unit for maximum storage period | |
| CFB_ADTDAYS | Additional Days | |
| CFB_DATOFM | Date of Manufacture | |
| CFB_BBDPI | Best-Before Date (BBD)/ Shelf Life Expiration Date (SLED) | |
| OIHANTYP | Excise Duty Handling Type | |
| .INCLU--AP | ||
| MILL_RATIO | Factor for Quantity-Based Settlement | |
| .INCLU--AP | ||
| BMEINS | Base Unit of Measure | |
| BMENGE | Base quantity | |
| MILL_OC_ZUSKZ | Combination Indicator |
3. AFVC - Work Order operation table
| Field Name | Field Description | Rule |
|---|---|---|
| AUFPL | Routing number of operations in the order | |
| APLZL | General counter for order | |
| PLNFL | Sequence | |
| PLNKN | Number of the task list node | |
| PLNAL | Group Counter | |
| PLNTY | Task List Type | |
| VINTV | Increment between referenced operations | |
| PLNNR | Key for Task List Group | |
| ZAEHL | Internal counter | |
| VORNR | Operation/Activity Number | |
| STEUS | Control key | |
| ARBID | Object ID of the resource | |
| PDEST | Printer for shop papers | |
| WERKS | Plant | |
| KTSCH | Standard text key | |
| LTXA1 | Operation short text | |
| LTXA2 | Second line of the description | |
| TXTSP | Language Key | |
| VPLTY | Type of the referenced task list | |
| VPLNR | Group of the referenced task list | |
| VPLAL | Group counter of the referenced task list | |
| VPLFL | Referenced sequence in routing | |
| VGWTS | Standard value key | |
| LAR01 | Activity Type | |
| LAR02 | Activity Type | |
| LAR03 | Activity Type | |
| LAR04 | Activity Type | |
| LAR05 | Activity Type | |
| LAR06 | Activity Type | |
| ZERMA | Type of standard value calculation | |
| ZGDAT | Date when the standard value was calculated | |
| ZCODE | Reference number for standard value code | |
| ZULNR | Basis for standard value calculation | |
| LOANZ | Number of Time Tickets | |
| LOART | Wage Type | |
| RSANZ | Number of confirmation slips | |
| QUALF | Suitability | |
| ANZMA | Number of employees | |
| RFGRP | Setup group category | |
| RFSCH | Setup group key | |
| RASCH | Setup Type Key | |
| AUFAK | Scrap factor | |
| LOGRP | Wage group | |
| UEMUS | Required overlapping | |
| UEKAN | Optional overlapping | |
| FLIES | Indicator: continuous flow production | |
| SPMUS | Required splitting | |
| SPLIM | Maximum number of splits | |
| ABLIPKZ | Indicator: simultaneous teardown and wait | |
| RSTRA | Reduction strategy per operation/activity | |
| SUMNR | Node number of the superior operation | |
| SORTL | Sort Term for Non-Stock Info Records | |
| LIFNR | Account Number of Vendor or Creditor | |
| PREIS | Price | |
| PEINH | Price Unit | |
| SAKTO | Cost Element | |
| WAERS | Currency Key | |
| INFNR | Number of Purchasing Info Record | |
| ESOKZ | Purchasing info record category | |
| EKORG | Purchasing Organization | |
| EKGRP | Purchasing group for external processing | |
| KZLGF | Indicator: fixed lot external processing | |
| KZWRTF | Indicator: Fixed price for external processing | |
| MATKL | Material Group | |
| DDEHN | Indicator: flexible duration | |
| ANZZL | Number of capacities required | |
| PRZNT | Work percentage | |
| MLSTN | Usage | |
| PPRIO | Priority | |
| BUKRS | Company Code | |
| ANFKO | Requesting cost center | |
| ANFKOKRS | Controlling area of the requesting cost center | |
| INDET | Key for calculation | |
| LARNT | Activity Type | |
| PRKST | Costs in the activity | |
| APLFL | Sequence | |
| RUECK | Completion confirmation number for the operation | |
| RMZHL | Confirmation counter | |
| PROJN | Work breakdown structure element (WBS element) | |
| OBJNR | Object number | |
| SPANZ | Actual number of splits | |
| BEDID | ID of the capacity requirements record | |
| BEDZL | Internal counter | |
| BANFN | Purchase requisition number | |
| BNFPO | Item number of the purchase requisition in the order | |
| LEK01 | Indicator: No remaining activity expected | |
| LEK02 | Indicator: No remaining activity expected | |
| LEK03 | Indicator: No remaining activity expected | |
| LEK04 | Indicator: No remaining activity expected | |
| LEK05 | Indicator: No remaining activity expected | |
| LEK06 | Indicator: No remaining activity expected | |
| SELKZ | Selection indicator for costing line items | |
| KALID | Factory Calendar | |
| FRSP | Earliest possible activity / Latest possible activity | |
| STDKN | Node of operation within reference operation set | |
| ANLZU | Syst.Condition | |
| ISTRU | Assembly | |
| ISTTY | BOM category | |
| ISTNR | Bill of material | |
| ISTKN | BOM item node number | |
| ISTPO | Internal counter | |
| IUPOZ | Subitem Number | |
| EBORT | Installation Point for Subitem | |
| VERTL | Distr.cap.reqmts (plant maint.,process order, network) | |
| LEKNW | Indicator: No Remaining Work Expected | |
| NPRIO | Priority | |
| PVZKN | General counter for order | |
| PHFLG | Indicator: Phase | |
| PHSEQ | Control Recipe Destination | |
| KNOBJ | Number of Object with Assigned Dependencies | |
| ERFSICHT | Recording View | |
| QPPKTABS | Flow Variants for Inspection Point Completion | |
| OTYPE | Object Type | |
| OBJEKTID | Object ID | |
| QLKAPAR | Capacity category | |
| RSTUF | Reduction level which reduces operation lead time | |
| NPTXTKY | Internal text number (12-character) | |
| SUBSYS | Subsystem Identifier for QM Subsystem Interface | |
| PSPNR | Standard WBS element | |
| PACKNO | Package number | |
| TXJCD | Tax Jurisdiction | |
| SCOPE | Object Class | |
| GSBER | Business Area | |
| PRCTR | Profit Center | |
| NO_DISP | Effective for Materials Planning | |
| QKZPRZEIT | Interval = Time (Time-Related) | |
| QKZZTMG1 | Quantity Confirmation for Each Partial Lot | |
| QKZPRMENG | Creation Cycle = Quantity (Quantity-Reference) | |
| QKZPRFREI | Interval Without Reference to Time or Quantity | |
| KZFEAT | Indicator Is Not Used Currently | |
| QKZTLSBEST | Operation with Stock-Related Partial Lot Assignment | |
| AENNR | Change Number | |
| CUOBJ_ARB | Configuration (internal object number) | |
| EVGEW | Aggregation weight for POC (PS progress) | |
| ARBII | Actual operating resources object identification | |
| WERKI | Actual plant | |
| CY_SEQNRV | Sequence number operation | |
| KAPT_PUFFR | Operation floats after finite scheduling (in seconds) | |
| EBELN | Purchasing Document Number | |
| EBELP | Item Number of Purchasing Document | |
| WEMPF | Goods Recipient/Ship-To Party | |
| ABLAD | Unloading Point | |
| CLASF | Ind.: Take Activity Into Account for Project Summarization | |
| FRUNV | Indicator: External procurement data incomplete | |
| ZSCHL | Overhead key | |
| KALSM | Costing Sheet | |
| SCHED_END | Ind.: Purchase requisition at activity finish date | |
| NETZKONT | Indicator for the account assignment of a network(hdr/act.) | |
| OWAER | Object currency for network activity | |
| AFNAM | Name of Requisitioner/Requester | |
| BEDNR | Requirement Tracking Number | |
| KZFIX | Indicator: Purchasing info record data are fixed | |
| PERNR | Personnel number | |
| FRDLB | Indicator: Externally processed op. with subcontracting | |
| QPART | Inspection Type | |
| LOEKZ | Deletion flag | |
| WKURS | Exchange Rate | |
| PROD_ACT | Indicator: Activity is a production activity | |
| FPLNR | Billing plan number / invoicing plan number | |
| OBJTYPE | Change indicator | |
| CH_PROC | Process that has lead to the change of an object | |
| KLVAR | Costing Variant | |
| KALNR | Cost Estimate Number for Cost Est. w/o Qty Structure | |
| FORDN | Framework Order | |
| FORDP | Item of framework order | |
| MAT_PRKST | Material planning in networks: primary costs | |
| PRZ01 | Business Process | |
| RFPNT | Reference point for BOM transfer | |
| FUNC_AREA | Functional Area | |
| TECHS | Parameter Variant/Standard Variant | |
| ADPSP | Reference Element PM/PS | |
| RFIPPNT | Reference Point for Relationship Between iPPE and PS | |
| MES_OPERID | Key of an Operation from an ME System | |
| MES_STEPID | Key of a Step in a Routing (SAP ME) | |
| .INCLU--AP | ||
| /CUM/CUGUID | UUID in X form (binary) | |
| .INCLU--AP | ||
| /ISDFPS/OBJNR | Object number | |
| .INCLU--AP | ||
| AFVC_STATUS | Status Combination | |
| .INCLU--AP | ||
| MILL_OC_AUFNR_MO | Number of Combined Order | |
| .INCLU--AP | ||
| WTY_IND | Warranty indicator | |
| TPLNR | Functional Location | |
| EQUNR | Equipment Number | |
| .INCLU--AP | ||
| CPD_UPDAT | Time Stamp |
4. AFIH - Work Order maintenance order header
| Field Name | Field Description | Rule |
|---|---|---|
| AUFNR | Order Number | |
| ARTPR | Priority Type | |
| PRIOK | Priority | |
| EQUNR | Equipment Number | |
| BAUTL | Assembly | |
| ILOAN | Location and account assignment for technical object | |
| ILOAI | ILOA Individual | |
| ANLZU | Syst.Condition | |
| IWERK | Maintenance Planning Plant | |
| INGPR | Planner Group for Customer Service and Plant Maintenance | |
| APGRP | Responsible planner group/department | |
| PM_OBJTY | Object Type of CIM Resources for Work Center | |
| GEWRK | Object ID of the Work Center | |
| KUNUM | Customer Number | |
| ANING | Name of Person Reponsible for System | |
| GAUZT | Planned downtime in hours | |
| GAUEH | Unit for Breakdown Duration | |
| ANLBD | Date until which the system is available | |
| ANLVD | Date from which the system is available | |
| ANLBZ | Time until which the system is available | |
| ANLVZ | Time from Which System is Available | |
| INSPK | Name of Person Responsible for Technical Inspection | |
| DATAN | Date of Technical Inspection | |
| WARPL | Maintenance Plan | |
| ABNUM | Maintenance Plan Call Number | |
| WAPOS | Maintenance item | |
| LAUFN | Order number | |
| OBKNR | Object list number | |
| REVNR | Revision for Plant Maintenance and Customer Service | |
| ADDAT | PM Order: Reference Date | |
| ADUHR | Time of Reference Date | |
| IPHAS | Maintenance Processing Phase | |
| ILART | Maintenance activity type | |
| QMNUM | Notification No | |
| HISDA | PM request: History date | |
| AKKNZ | Order Category Indicator Plant Maintenance | |
| PLKNZ | Maintenance order planning indicator | |
| SERIALNR | Serial Number | |
| SERMAT | Material Number | |
| DEVICEID | Additional Device Data | |
| SCREENTY | Scenario or Subscreen Category | |
| ADPSP | Reference Element PM/PS | |
| RSUPG | Upgrade Order Indicator | |
| .INCLU--AP | ||
| /ISDFPS/OBJNR | Object number | |
| /ISDFPS/MEQUI | Master Equipment | |
| .INCLU--AP | ||
| UII | Unique Item Identifier | |
| .INCLU--AP | ||
| ORCOD | PM/CS Order Code Indicating Rotable Process | |
| PRMAN | CMC: Priority Manually Changed | |
| PRVAL | Priority for PM/CS Orders | |
| TWTDE | CMC: Use Minimum or Standard TWT from PP Matrix | |
| MSTCK | Single-Character Indicator |
Extraction Dependencies
| 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 to make the data Target ready:
- Perform value mapping and data transformation rules.
- Legacy values are mapped to the to-be values (this could include a default value)
- Values are transformed according to the rules defined in
- 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
| 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
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:
|
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
| 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:
- Execute the automated data load into target system using load tool or product the load file if the load must be done manually
- 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
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 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
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
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).
See also
Change log
Workflow history
| Title | Last Updated By | Updated | Status | |
|---|---|---|---|---|
| There are no pages at the moment. | ||||