Understanding Outbound Interoperability for Sales Order Management

You might send transactions you create or change in Sales Order Management to an external system. For example, if the organization sends order acknowledgements to customers, you can use Interoperability transactions to convey order and price information.

To process outbound interoperability in Sales Order Management:

1. Specify a transaction type in the processing options of these programs:

   • Sales Order Entry (P4210)

   • Shipment Confirmation (P4205)

2. Enter or change a sales order or shipment confirmation using the Sales Order Entry program (P42101).

   The JD Edwards EnterpriseOne Sales Order system calls a business function that writes records to the Sales Order Header Unedited Transaction File table (F4201Z1) and the Sales Order Detail Unedited Transaction File table (F4211Z1). The same business function calls a special subsystem API (application program interface) 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 F4201Z1 and F4211Z1 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 you 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. The custom UBE then retrieves the records from the F4201Z1 and F4211Z1 tables and processes that information.