ntercompany Open Interface Tables

Intercompany transactions from the external source populate the following

Intercompany Interface tables:

• FUN_INTERFACE_CONTROLS, which groups the data imported in each run.

• FUN_INTERFACE_BATCHES, which stores batch information.

• FUN_INTERFACE_HEADERS, which stores information about the transaction

header for each recipient.

• FUN_INTERFACE_DIST_LINES, which stores distributions for initiator and

recipient.

Running the Intercompany Import Program

Run the Intercompany Import Program in the Schedule Requests page to import the
Intercompany transactions from Interface tables to Intercompany tables. Before
importing, the transactions are validated by the Transaction API.
On successful completion of the import program, an import execution report is printed
which lists the status of the transactions being imported.
The following table describes selected fields in the Intercompany Import Program.

Parameters Description

Source Specify the application source.

Group Enter the Group ID.

Send Transactions Enter Yes to send the transactions as initiator transactions and
start the recipient workflow. Print Rejected Only Specify No if you want to print all the
transactions in the report.
Debug Helps you to query, rectify and re-import rejected transactions.
Successful transactions are purged from the interface tables.

You can import intercompany transactions from external applications using the Open
Interface tables and WebADI.

Importing Intercompany Using Open Interface

You can import intercompany transactions from third party software or Oracle SQL
Loaders into AGIS.
Before you import, ensure the data format in the external source and the Intercompany
Interface tables are the same.
The following figure displays the importing process an external source to
Intercompany:

1. Upload transactions into the Intercompany Interface tables.

While uploading the transactions to the Intercompany Interface tables, you must
ensure the following:

• Columns specified Not Null must contain data.

• Columns specified Required must contain data when importing the

transactions to AGIS.

• Columns specified Conditionally Required must contain a value if a

dependent column has values.

• Columns specified Optional need not contain data. However, the transactions
are rejected if the data fails the validation.

2. Run the Intercompany Import Program