Understanding Outbound Interoperability for Forecast Management

You might send transactions that you create or change in JD Edwards EnterpriseOne Forecast Management to another system. For example, if the organization uses hand-held scanning devices, you can use interoperability transactions to update the database that the scanning devices use.

To process outbound interoperability in JD Edwards EnterpriseOne Forecast Management:

1. Specify a transaction type in the processing options of the Enter/Change Forecast program (P3460).

   We provide transaction type JDEFC for forecast transactions.

2. Enter or change a forecast record using the Enter/Change Forecast program.

   The JD Edwards EnterpriseOne Forecast Management system calls a business function that writes records to the Forecast Unedited Transactions table (F3460Z1). 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 F3460Z1 table 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 (universal batch engine) or function for the transaction type you specified in the processing options of the Enter/Change Forecast 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 or function 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 F3460Z1 table and processes that information.