You might need to send to another system transactions that you create or change in Shop Floor Management. For example, if the organization uses handheld scanning devices, you can use interoperability transactions to update the database used by the scanning devices.

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

Originating Program

Transaction Type

EDI Outbound Interface Table

Extraction Program

Enter/Change Order (P48013)

JDEWO

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: Work Order Transaction Type

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: Work Order Transaction Type

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 Parts Detail (P17730)

JDEII (Inventory Issues)

Outbound Work Order Parts List (F3111Z1)

N/A

Work Order Parts Detail (P17730)

JDEPL (WO Parts List Transactions)

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 (F47001) to identify the interface tables to populate based on the transaction type you specify in the processing options.

The system creates the outbound transaction in EDI format. External systems can process the transactions using standard EDI processing, including extraction.

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

10.1.1.1 Work Order Parts Detail

To process outbound interoperability for work order parts detail transactions:

Specify a transaction type in the processing options of the Work Order Parts Detail program (P17730).

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

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.

Use the Data Export Controls program (P0047) to specify the custom UBE or function for the transaction type you specified in the processing options of the originating program.

The system stores this information in the Data Export Control table (F0047).

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. The custom UBE then retrieves the records from the F4801Z1 and F3111Z1A tables and processes that information.

10.1.2 Prerequisite

Define the data export controls for the type of outbound transaction. The system uses data export controls to determine the batch programs or business processes that third parties supply for use in processing transactions.

10.1.3 Setting Selected Processing Options for Originating Programs

This section lists only the processing options that are specific to outbound interoperability. These processing options are used for the following programs:

Enter/Change Order (P48013)

Enter/Change Rate Schedule (P3109)

Order Processing (R31410)

Inventory Issues (P31113)

Hours and Quantities Update (R31422)

Work Order Completions (P31114)

Work Order Parts Detail (P17730)

Transaction Type

Specify the transaction type for the interoperability transaction. If you leave this processing option blank, the outbound interoperability is not performed.

Before Image

Specify whether the system creates a record of the image before it was changed, in addition to a record of the transaction after the change. The system creates these records in the unedited transaction table when outbound interoperability processing is enabled. Values are:

Blank: Write the record only after it has been changed; do not write a before image record.

1: Write two records: one before the image is changed and one after the image is changed.

This section provides an overview of reviewing and revising interoperability transactions for Shop Floor Management, lists the forms used to review and revise interoperability transactions for Shop Floor Management, and discusses how to:

Set processing options for Inbound Work Order Inquiry (P4801Z1).

Set processing options for Inbound Hours and Quantity Inquiry (P31122Z1).

Running one of the transaction processes, such as the Inbound Work Order Inquiry (P4801Z1), often identifies one or more inbound transactions that contain invalid transactions. For example, a work order might have an invalid item number. In that case, the program cannot add that work order to the Work Order Master table (F4801). Instead, the program sends an error message to the Employee Work Center program (P012501), which indicates the transaction number for the transaction in error.

Use the inbound inquiry programs to review and revise inbound transactions, as well as to add, change, or delete transactions that contain errors. Then run the transaction process again. Continue to make corrections and rerun the transaction process until the program runs without errors.

Processing options enable you to specify the default processing for programs and reports.

10.3.7.1 Display

1. Default View mode.

Specify a value to indicate how the system displays the records. Values are:

1: The system displays the unprocessed records.

2: The system displays all successfully processed records.

3: The system displays all unsuccessfully processed records.

2. Enter the Direction Indicator value.

Specify a code that indicates whether the transaction is inbound or outbound. Values are:

1: Inbound Records

2: Outbound Records

10.3.7.2 Defaults

Transaction Type

Enter the transaction type for new Kanban transactions. If you leave this processing option blank, the system uses JDEKNB.

10.3.7.3 Process

Inbound Subsystem UBE

Enter the name of the inbound subsystem UBE to call to process inbound transactions. If you leave this processing option blank, the system uses R30161Z1I.

Version of Inbound UBE

Specify a version of the inbound subsystem UBE. If you leave this processing option blank, the system uses XJDE0001.

10.4 Purging Interoperability Transactions for Shop Floor Management

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

10.4.1 Understanding Purging Interoperability Transactions

When data becomes obsolete or you need more disk space, you can 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:

Interoperability Work Order Purge (R4801Z1P)

Inbound Hours and Quantity Purge (R31122Z1)

Inbound Inventory Issues Purge (R3111Z1P)

Inbound Completion Purge (R4801Z1)

Inbound Super Backflush Purge (R3112Z1P)

Inbound Kanban Purge (R30161Z1P)

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 you purge cycle count transactions, you can set the processing option to print only the records that are in error. Otherwise, the program prints all records that are deleted.

10.4.2 Purging Interoperability Transactions

To purge inbound or outbound work order transactions, select Shop Floor Management Interoperability (G31311), Interoperability Work Order Purge.