Understanding Outbound Interoperability for Inventory Management

To fully cover the information requirements of an enterprise, companies sometimes use products from different software and hardware providers. For example, some companies use the JD Edwards EnterpriseOne Inventory Management system for most inventory functions and use hand-held scanning devices to physically count their inventory.

Interoperability among products is essential to successfully implementing the enterprise solution. Full interoperability among systems results in a flow of data among products that is seamless to the user. The JD Edwards EnterpriseOne JD Edwards EnterpriseOne Interoperability function provides an interface that eases the exchange of transactions with external systems.

You can send transactions to an external system from these programs in Inventory Management:

Originating Program	Transaction Type	Transaction Table	Extraction Program
Item Master (P4101) Item Branch/Plant (P41026)	JDEITEM	F4101 Item Master Unedited Transaction Table (F4101Z1) F4101 Detail Item Master Unedited Transaction (F4101Z1A)	N/A
Item Master Cost Revisions (P4105)	JDEIC	Unedited Transaction Table - Item Cost (F4105Z1)	N/A
Inventory Issues (P4112)	852	EDI Product Activity Data Header – Outbound (F47126) EDI Product Activity Data Detail – Outbound (F47127)	N/A
Inventory Transfers (P4113)	852	EDI Product Activity Data Header – Outbound (F47126) EDI Product Activity Data Detail – Outbound (F47127)	Item Location Extraction (R41021ZX) Note: You run this outbound extraction program 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.
Inventory Adjustments (P4114)	852	EDI Product Activity Data Header – Outbound (F47126) EDI Product Activity Data Detail – Outbound (F47127)	N/A
Item Reclassifications (P4116)	852	EDI Product Activity Data Header – Outbound (F47126) EDI Product Activity Data Detail – Outbound (F47127)	N/A
Cycle Count Update (R41413)	JDECYCLE	F4141 Cycle Count Unedited Transaction Table (F4141Z1)	N/A
Item Location Extraction (R41021ZX)	N/A	Item Location Unedited Transaction File (F41021Z1)	N/A

To create outbound transactions, you must specify the appropriate transaction type in the related processing option. The system places a copy of the transaction in the interface table for that type of transaction. For example, when you run Cycle Count Update with the Interoperability processing option turned on, the system places a copy of updated cycle count data in the F4141Z1 table. The data is then available for an external system to use.

Important: The process detailed here is an example of a typical outbound process and uses the JDEITEM transaction type as an example. For other transaction types, the unedited transaction tables are different.

To process outbound interoperability in Inventory Management:

Specify a transaction type in the processing options of the originating programs.
Enter or change an item record in one of the originating programs.
The JD Edwards EnterpriseOne Inventory Management system calls a master business function that writes records to the F4101 Item Master Unedited Transaction Table (F4101Z1) and the F4101 Detail Item Master Unedited Transaction table (F4101Z1A). 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 F4101Z1 and F4101Z1A 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 F4101Z1 and F4101Z1A tables and processes that information.