R4801Z1X & R4801Z1P Outbound Interoperability for Shop Floor Management

Purpose of Document

Purpose

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 1323732.1

This document provides answers to possible questions regarding Outbound Interoperability process as well as an overview on Purging Interoperability Transactions details for Shop Floor Management.

Scope

Advanced Users of the Shop Floor Control module may find this document useful.

Details

Overview

This note is to explain possible queries occurring when dealing with Outbound Work Order Header File (F4801Z1) that can be used for sending transactions to an external system. Currently, outbound can be fulfilled through interoperability, EDI, Business Service or Custom Table Conversion.

To have a better understanding, the Shop Floor Management below tables and relationships has to be understood in advance:

Files created for extraction (F4801Z1, F3111Z1 and F3112Z1) that can be used for outbound process:

The fact the table Outbound Work Order Header File (F4801Z1) can be used for multiple purposes, may cause some confusion. Except Inbound Order Completion, this file will be used for outbound whether it is finalized to extract or intermediate. If needed, this table can be used to audit purposes because if forcing a certain system to do so it will write UB (Update Before) and UA (Update After) images whenever data from Work Order Master File (F4801) gets changed.

Understanding Outbound Interoperability for Shop Floor Management

The need may arise to send to other systems, transactions that are created or changed in Shop Floor Management. For example, if the organization uses hand held scanning devices, the interoperability transactions could be used to update the database accessed by the scanning devices.

This table lists the JD Edwards EnterpriseOne Shop Floor Management programs from which transactions could be send to an external system:

Originating ProgramTransaction TypeEDI Outbound Interface TableExtraction Program
Enter/Change Order (P48013) JDEWO - Work Order Transaction Type Outbound Work Order Header (F4801Z1) Outbound Work Order Extraction (R4801Z1X)
Enter/Change Rate Schedule (P3109) JDEWO Outbound Work Order Header (F4801Z1) Outbound Work Order Extraction (R4801Z1X)
Order Processing (R31410) JDEWO
JDEPL - Parts List Transaction Type
JDERTG - Routing Instructions Transaction Type		 Outbound Work Order Header (F4801Z1)

Warranty Claim / Supplier Recovery processing (F3111Z2)		 Outbound Work Order Extraction (R4801Z1X)

Outbound Supplier Recovery Processing (R174801Z2O)
Inventory Issues (P31113) JDEII - Inventory Issue Transaction Type
JDEWO		 Outbound Work Order Header interface (F4801Z1) Outbound Work Order Extraction (R4801Z1X)
Hours and Quantities
Update (R31422)		 JDEWO Outbound Work Order Header interface (F4801Z1) Outbound Work Order Extraction (R4801Z1X)
Work Order Completions
(P31114)		 JDEWO Outbound Work Order Header interface (F4801Z1) Outbound Work Order Extraction (R4801Z1X)
Work Order Time Entry (P311221) N/A N/A This application has parameter for interoperability it is not meant for. Refer to P31225.
For further details on this, refer Bug 12560829 - P311221/Outbound to F31122Z1.[This section is not visible to customers.]
Manufacturing Scheduling Workbench (P31225) JDEWO Outbound Work Order Header interface (F4801Z1) Outbound Work Order Extraction (R4801Z1X)
Work Order Parts Detail
(P17730)		 JDEII (Inventory Issues) Outbound Work Order Parts List (F3111Z1) N/A
Work Order Parts Detail
(P17730)		 JDEPL Outbound Work Order Header (F4801Z1)
Outbound Work Order Parts List (F3111Z1)		 N/A


To create outbound transactions, specify the appropriate transaction type in the processing options for these programs. The system places a copy of the transaction in the interface table for that type of transaction. The system uses the Flat File Cross-Reference Table (F47002) to identify the interface tables to populate based on the transaction type specified in the processing options.

F47002 - Flat File Cross-Reference Table (Outbound only)

File NameTYTN: Type -TransactionDRIN: Direction IndicatorEDTY: Type Record
F4801Z1 JDECMP - Work Order Completion Transaction Type
JDEPL
JDERTG
JDEWO		 2 - Outbound 1 - Header
F3111Z1 JDEPL 2 - Outbound 2 - Detail
F3112Z1 JDERTG 2 - Outbound 2 - Detail


The system creates the outbound transaction in EDI format. External systems can process the transactions using standard EDI processing, including extraction.
Run outbound extraction programs to retrieve data from the outbound transaction tables and create a flat file if one does not exist, or to append to an existing flat file. Every field is written from the EDI interface tables to the flat file.

Work Order Parts List Detail

To process outbound interoperability for work order parts detail transactions:

1.  Specify a transaction type in the processing options of the Work Order Parts Detail program (P17730).
2.  Enter or change a record in this originating program. The system calls a master business function that writes records to the Outbound Work Order Header table (F4801Z1) and the Outbound Work Order Parts List table (F3111Z1). The same master business function calls a special subsystem API that sends a message to the subsystem kernel running on the server. The subsystem kernel adds a record to the Subsystem Job Master table (F986113).
3.  Create a custom UBE or function to process the data from the F4801Z1 and F3111Z1 tables in such a way that it can be used by the external system.
4.  Use the Data Export Controls program (P0047) to specify the custom UBE or function for the transaction type specified in the processing options of the originating program. The system stores this information in the Data Export Control table (F0047).
5.  Run the Interoperability Generic Outbound Subsystem UBE program (R00460).

The Interoperability Generic Outbound Subsystem UBE program fetches the F986113 record and retrieves the name and version of the custom UBE from the F0047 table. The Interoperability Generic Outbound Subsystem UBE program passes information about the order to the custom UBE. Then, using the custom UBE, retrieve the records from the F4801Z1 and F3111Z1A tables and process that information.

Purging Interoperability Transactions for Shop Floor Management

This section provides an overview of purging interoperability transactions and discusses how to purge interoperability transactions.

Understanding Purging Interoperability Transactions
When data becomes obsolete or more disk space is required, use purge programs to remove data from interface tables.
The interoperability menu contains options for purging transactions. Use one of these purge programs to remove data from the corresponding interface tables:

For records in the Processing Log table (F0046) that are marked as processed, the program purges the associated transactions in the corresponding interoperability tables, as well as the records in the F0046 table. If the records in the F0046 table are not marked as processed, the program does not purge any records.

When purging cycle count transactions, set the processing option to print only the records that are in error. Otherwise, the program prints all records that are deleted.

Frequently Asked Questions

Question 1.   What is the purpose of Outbound Work Order Header file (F4801Z1)?

Answer 1.   If it is necessary to notify, add or update the work order, the data can be populated into F4801Z1 by setting the relevant transaction type in the processing option you are working with. In case the daily business does not specifically require, do not specify any transaction type in the processing options of each Interop tab. Doing this may cause waste of resources due to additional routine to write Z1 table.

Question 2.   Can the transaction type can be any type?

Answer 2.   The transaction type has to be meaningful. Choose proper transaction type and review whether transaction type defined has valid reference table from F47002 (or P47002). For example, when running Work Order Completion (P31114), set the value 'JDECMP' because Target File for this transaction is F4801Z1.

Question 3.   Why does the outbound interoperability process not work for some types of transactions?

Answer 3.  For each type of transaction, a record must be added in P47002 referencing the transaction type and the Z-file.

Example:
If the Transaction Type processing option in the Interop tab, behind the WO Completions (P31114) is populated with a value (e.g. JDECMP), then, whenever a completion occurs with this version of P31114, a record is expected to be written to the corresponding Z-file (in this case, F4801Z1). Reviewing F4801Z1 for JDECMP records, notice that no records exist in this table.

This issue is due to a missing setup in Flat File Cross-Reference (P47002). Using this example, a record should be added in P47002 for:

See BUG 10999175 - 'F4801Z1 Not Populated' that references the same functionality.[This section is not visible to customers.]

Question 4.  Why is there no data from F3111Z1 and F3112Z1, even though transaction type is defined as 'JDECMP' in P31114?

Answer 4.  Two tables will be populated in running Outbound Work Order Extraction (R4801Z1X). Currently this UBE can be submitted either through Subsystem Job or manually, depending on the processing option set behind P31114.

Question 5.   What is the setup to have R4801Z1X run through Subsystem?

Answer 5.   Set processing option value 1 for below parameter behind P31114, for example.
Call Outbound Subsystem: 1 = Call outbound subsystem:
When wanting to submit R4801Z1X manually, this value can be set to blank.

A detailed example can be found on E1:31: R00460 Implementing Work Order Extraction in P48013 (JDEWO) - Document 1342363.1 .

Question 6.   How can it be verify if Outbound Work Order Extraction (R4801Z1X) is triggered and running?

Answer 6.   Actual job triggered is R00460. Make sure that Subsystem Job Master (P986113) has a running job of R00460. R00460 is universal purpose for outbound transaction which is calling R4801Z1X.

Question 7.  Why did the Interoperability Work Order Purge (R4801Z1P) not purge any data from F4801Z1?

Answer 7.   This application will delete only files successfully processed. Alternatively R4801Z1 can be used. Upon using it, take extra care as there is no validation logic for deletion / purge.