## Processing Interoperability for Forecast Management

This chapter discusses how to:

- Process outbound interoperability for Forecast Management.

- Process inbound interoperability for Forecast Management.

- Review and revise interoperability transactions for Forecast Management.

- Purge interoperability transactions for Forecast Management.

### Processing Outbound Interoperability for Forecast Management

This section provides an overview of the outbound interoperability for Forecast Management, lists a prerequisite, and discusses how to set selected processing options for the Enter/Change Forecast program (P3460).

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

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

See Setting Up Data Export Controls.

#### Setting Selected Processing Options for Enter/Change Forecast (P3460)

This section lists only the processing options for the Enter/Change Forecast program (P3460) that are specific to outbound interoperability.

Interop

You use these processing options to set up outbound interoperability.

1. Enter the Transaction Type for processing outbound interoperability transactions | Specify the transaction type for the interoperability transaction. If you leave this processing option blank, the outbound interoperability is not performed. Note. We provide transaction type JDEFC for forecast transactions.
2. Enter a '1' to write before images for outbound change transactions. If left blank, only after images will be written. | Specify whether the system creates a record of the forecast transaction before it was changed, in addition to a record of the forecast transaction after the change. The system creates these records in the Forecast Unedited Transactions table (F3460Z1) when outbound interoperability processing is enabled. Values are: Blank: Write the forecast transaction record only after it has been changed; do not write a before image record. 1: Write two forecast transaction records: one before the forecast transaction is changed and one after the forecast transaction is changed.

### Processing Inbound Interoperability for Forecast Management

This section provides an overview of inbound interoperability for Forecast Management, lists prerequisites, and discusses how to run the Forecast Inbound Processor.

#### Understanding Inbound Interoperability for Forecast Management

You might receive forecast transactions from a third-party system and need to import them into Forecast Management. The third-party system is responsible for mapping the data into a flat file.

You run the Inbound Flat File Conversion program (R47002C) to copy the data from the flat file to the Forecast Unedited Transactions table (F3460Z1) if you have set up a flat file cross-reference to this table.

Note. We provide transaction type JDEFC for forecast transactions.

You run the Forecast Inbound Processor program (R3460Z1I) to copy the information from the unedited transaction table to the Forecast File table (F3460).

#### Prerequisites

Before you complete the tasks in this section:

- Set up flat file cross-references.

  See Setting Up the Flat File Cross-Reference.

- Run the Inbound Flat File Conversion program (R47002C).

  See Running the Inbound Flat File Conversion Program (R47002C).

#### Running the Forecast Inbound Processor

Select Forecast Interoperability (G36301), Process Inbound Forecast Transactions.

### Reviewing and Revising Interoperability Transactions for Forecast Management

This section provides an overview of reviewing and revising interoperability transactions for Forecast Management and lists the forms used to review and revise interoperability transactions for Forecast Management.

#### Understanding Reviewing and Revising Interoperability Transactions for Forecast Management

Running a transaction process, such as Forecast Inbound Processor (R3460Z1I), often identifies one or more inbound transactions that contain invalid transactions. The Forecast Inbound Processor program identifies the invalid transaction and sends an error message to the Work Center (P012501). The error message indicates the transaction number for the transaction in error.

You can use the Forecast Transactions Revisions program (P3460Z1) to review and revise inbound transactions. You can add, change, or delete transactions containing errors and then run the transaction process again. Continue to make corrections and rerun the transaction process until the program runs without errors.

#### Forms Used to Review and Revise Interoperability Transactions for Forecast Management

Form Name | FormID | Navigation | Usage
Work With Forecast Batches | W3460Z1A | Forecast Interoperability (G36301), Forecast Transaction Revisions | Review inbound transactions.
Forecast Transaction Revision | W3460Z1B | Select a record and click Select on the Work With Forecast Batches form. | Revise a transaction. After you correct the errors identified by the Forecast Inbound Processor (R3460Z1I), run the transaction process again.

### Purging Interoperability Transactions for Forecast Management

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

#### Understanding Purging Interoperability Transactions

When data becomes obsolete or when you need more disk space, you can use the Purge Forecast Transactions program (R3460Z1P) to remove data from the Forecast Unedited Transactions table (F3460Z1).

The Purge Forecast Transactions program purges both inbound and outbound transactions.

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.

See JD Edwards EnterpriseOne Tools 8.98 Interoperability Guide.

#### Purging Interoperability Transactions

Select Forecast Interoperability (G36301), Purge Forecast Transactions.