E1: 31: EDI Importing Work Orders into JDE and Updating WO Status, Parts Lists & Routings
(Doc ID 629428.1)
Last updated on NOVEMBER 13, 2024
Applies to:
JD Edwards EnterpriseOne EDI - Version XE and laterJD Edwards EnterpriseOne Shop Floor Control - Version XE and later
JD Edwards EnterpriseOne Service Management - Version 8.11 Base and later
Information in this document applies to any platform.
P48013 - Manufacturing Work Order Processing, P4801Z1 - Outbound Work Order Revisions, P31111 - Work Order Inventory Issues, P3112 - Work Order Routing
P3411 - MRP/MPS Detail Message Revisions, R3411 - MRP/MPS Detail Message Processing
Goal
This document is part of an Information Center - to see other documents related to Shop Floor Control, please use the links provided below: Information Center: JD Edwards EnterpriseOne Shop Floor Control > Information Center: Using JD Edwards EnterpriseOne Shop Floor Control > Note 629428.1This document explains what the Outbound Work Order Revisions application (P4801Z1) is used for. It also provides details on the supported / not supported inbound interoperability processes, affecting mainly the work order header inbound interoperability transactions, along with a workaround for converting legacy data to JDE for manufacturing and service orders. For detailed information on interoperability refer to online implementation guide 9.2 JD Edwards EnterpriseOne Applications Data Interface for Electronic Data Interchange Implementation Guide.
- The system only supports outbound interoperability of Manufacturing Work Orders using P48013, interoperability processing option tab.
- Outbound interoperability is not supported for Equipment (P48201/P13700/ P13714) or Service work orders (P17714/P48201/P90CD002/P90CD020).
- The Outbound Work Order Header file (F4801Z1), Outbound Work Order Parts List (F3111Z1) file and Outbound Work Order Routings (F3112Z1) table are only used for outbound interoperability transactions as far as Work Order Header details, Work Order Parts Lists and Work Order Routings are concerned.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |
Overview |
Work Around - Creating WO Header details through interoperability transaction |
How to update the WO Header details, WO Parts Lists and WO Routings through batch input |
References |