|Oracle Advanced Global Intercompany System User's Guide|
Part Number E12794-04
This chapter covers the following topics:
You can import intercompany transactions from external applications using the Open Interface tables and WebADI.
See Importing Intercompany Using Open Interface and Intercompany WebADI Integration
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:
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.
Run the Intercompany Import Program.
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.
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.
|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.
Intercompany Open Interface Tables
WebADI enables you to enter transactions in a spreadsheet application and upload them into AGIS. The advantages of using WebADI for entering intercompany transactions are:
You only need a browser and spreadsheet application such as Excel in your desktop to run WebADI.
You can enter transactions in a transaction entry worksheet in a spreadsheet that is similar to the transaction entry page in Intercompany.
You can define a spreadsheet specific to intercompany transactions and use powerful spreadsheet features.
For example, you can define formulae for allocation entries in the spreadsheet. You can save, manage the transaction entry worksheet and upload it later, regardless of being connected to AGIS. You can also define a spreadsheet to define intercompany templates for modifying and uploading repeatedly (for recurring transactions).
You can quickly enter intercompany journal lines by copying and pasting journal lines, then performing incremental modifications in the spreadsheet worksheet.
You can validate accounts by enforcing security and cross validation rules.
You can use the following items in the WebADI menu in the spreadsheet:
Upload Journal: Select this option to choose the upload parameters.
List of Values: Select this option to invoke a List of Values when entering transactions.
To import transactions, you must first create the spreadsheet document in Oracle WebADI: Create Document page and later upload the transactions.
The spreadsheet document created using WebADI has predefined formats for entering Intercompany transactions.
To create a spreadsheet document:
Navigate to the WebADI page.
Select Create Document from the Navigation menu.
Specify the WebADI settings by selecting the Viewer. The Viewer is the spreadsheet application you must choose to create the document.
Select the Intercompany - Single Batch Entry Integrator. WebADI Integrator is the application that integrates with various Oracle Applications.
Select the Intercompany - Single Batch Entry Layout.
Note: You can create new layouts or modify the seeded layouts available in Intercompany.
Review the selections and click Create Document.
On clicking Create Document, the spreadsheet application opens with the defined spreadsheet where you can enter transactions.
After entering the transactions, you must upload the transactions to Intercompany.
To upload the transactions:
Click Upload Journal on the WebADI menu and specify the upload parameters.
The transactions are uploaded into the Intercompany Interface tables.
Submit the Intercompany Open Interface program to import the transactions into Intercompany.
WebADI Spreadsheets, Oracle Financial Consolidation Hub User's Guide
You should be able to purge the rejected intercompany transactions from the AGIS interface tables to remove the redundant data.
When you run the Intercompany Import program, the program validates intercompany transactions imported from external source applications and a status of “Accepted” or “Rejected” is assigned to intercompany batches, headers and lines. The accepted intercompany transaction batches become transaction records, however, rejected intercompany transaction batches remain in the AGIS interface tables. These rejected intercompany transactions occupy a lot of space in the database, leading to detrimental impact on performance for both online and background processing. You can purge the rejected intercompany transactions from the AGIS interface tables to remove the redundant data with the help of the Purge Rejected Intercompany Transactions concurrent program. The system lets you view the transactions before purging.
The Purge Rejected Intercompany Transactions program is based on the parameters entered to purge all rejected intercompany batches for a given source and group ID. When the import status for some intercompany headers and lines are rejected and some accepted, the overall status for the related intercompany batch is “Rejected” and therefore the whole batch can be deleted, including all headers and lines.
A log file is generated after you run the Purge Rejected Intercompany Transactions program with debug messages.
A report is generated after you run the Purge Rejected Intercompany Transactions program having information about the rejected intercompany batches that were purged or previewed. If you run the program with the preview mode set to Yes, then the report will be named as “Purge Rejected Intercompany Transactions Preview Report”. If you run the program with the preview mode set to No, then the report will be named as “Purge Rejected Intercompany Transactions Execution Report”.
Copyright © 2005, 2010, Oracle and/or its affiliates. All rights reserved.