1. Interoperability Fundamentals Implementation Guide
  2. Understanding Outbound Interoperability

Understanding Outbound Interoperability

You might need to send transactions that you create or change in the JD Edwards EnterpriseOne system to an external system. For example, you might need to send information about changes on a journal entry or a purchase order to an external system.

To enable outbound processing, you specify a transaction type in the processing options of the appropriate originating program or interoperability processing options program. Additionally, some entry programs enable you to specify a version of the Master Business Function Processing Options program that, in turn, enables you to specify a version of the Interoperability Processing Options program. You can differentiate outbound transactions by transaction type by creating multiple versions of the interoperability processing option programs. For example, you might want to differentiate vouchers that are generated by Procurement from vouchers that are generated manually.

Using the master business function for the type of transaction, the system creates a copy of the transaction and places it in the interface table where external systems can access it.

If a program modifies a transaction without going through the master business function, the system still sends a copy of the transaction to the interface table where external systems can access it.

The default outbound transaction is a copy of a transaction after you create or change it (an after image). With interoperability, you can also send a copy of each transaction as it was before you changed it (a before image). To control the type of image, you set a processing option on the appropriate interoperability processing options program.

Note: Creating and sending before images requires additional processing time.

The system places a copy of each transaction in the interface table (Z table) that corresponds to the type of transaction that you specify in the processing option. The system also adds a record to the Subsystem Job Master table (F986113).

To retrieve the data from the interface tables:

  1. Create a custom UBE (universal batch engine) or function to process the data from the interface tables in such a way that it can be used by the external system.

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

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

  3. 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 or function from the F0047 table. The Interoperability Generic Outbound Subsystem UBE program passes information about the transaction to the custom UBE or function. The custom UBE or function then retrieves the records from the interface tables and processes that information.