AGIS User Guide

Oracle Advanced Global Intercompany System
User's Guide Release 12.1

Part No. E12794-04
August 2010
Oracle Advanced Global Intercompany System User's Guide, Release 12.1 Part No. E12794-04 Copyright 2005, 2010, Oracle and/or its affiliates. All rights reserved. Primary Author: Gustavus Kundahl Contributing Author: Ramasubramanian Balasundaram, Gail D'Aloisio, David Haimes, Julianna Litwin, Bidisha Silveira, Ljiljana Sinjeri Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065. This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications. This software and documentation may provide access to or information on content, products and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third party content, products and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third party content, products or services.

Contents
Send Us Your Comments Preface 1 Intercompany Setup

Introduction............................................................................................................................... 1-1 Setting up AGIS........................................................................................................................ 1-2 Intercompany Accounting Pages......................................................................................... 1-2 Intercompany Accounts Pages...................................................................................... 1-2 Common Intercompany Accounts Fields................................................................1-2 Intercompany Accounts Search Page...................................................................... 1-3 Create Intercompany Accounts Pages.....................................................................1-3 Define Accounts Page............................................................................................. 1-3 Update Intercompany Accounts............................................................................. 1-3 Balancing Accounts Search Page................................................................................... 1-3 Create Intracompany Balancing Rules Page.................................................................. 1-3 Intercompany Organizations Pages..................................................................................... 1-6 View Intercompany Organization Page........................................................................ 1-6 Intercompany Security Pages............................................................................................... 1-7 Intercompany Organization Assignments Page............................................................ 1-7 Intercompany Transaction Types Pages.............................................................................. 1-7 Creating Intercompany Transaction Types Page........................................................... 1-8 Intercompany Periods Pages................................................................................................ 1-8 Control Period Statuses Page.........................................................................................1-8 Review Open Transactions Page................................................................................... 1-8 Intercompany Invoicing Options Pages............................................................................... 1-9 Receivables Assignments Page...................................................................................... 1-9
iii
Customer Supplier Associations................................................................................... 1-9 Customer and Supplier Association Page............................................................. 1-10 Trading Partners Page...........................................................................................1-10 Intercompany System Options........................................................................................... 1-11 Approvals Management Setup for Intercompany..............................................................1-12 Default Accounts Rules Setup In Subledger Accounting for Intercompany...................... 1-13
Intercompany Transaction Processing

Intercompany Home Page......................................................................................................... 2-1 Intercompany Transaction Page................................................................................................ 2-1 Outbound Transactions Page............................................................................................... 2-2 Inbound Transactions Page.................................................................................................. 2-4 Intercompany Batch Numbering Sequence.............................................................................. 2-4 Workflow Notifications............................................................................................................ 2-5 Transferring Transactions to General Ledger.......................................................................... 2-5 Transferring Transactions to Receivables and Payables.......................................................... 2-7
Importing Intercompany Transactions

Importing Transactions............................................................................................................. 3-1 Importing Intercompany Using Open Interface...................................................................3-1 Intercompany Open Interface Tables.............................................................................3-2 Running the Intercompany Import Program................................................................. 3-2 Importing Intercompany Transactions Using WebADI....................................................... 3-3 Oracle WebADI: Create Document Page....................................................................... 3-4 Purge Rejected Intercompany Transactions......................................................................... 3-5
Intercompany Reporting
Reports....................................................................................................................................... 4-1
Intercompany Open Interface Tables

Open Interface Tables............................................................................................................... A-1
Index
iv

Send Us Your Comments
Oracle Advanced Global Intercompany System User's Guide, Release 12.1
Part No. E12794-04
Oracle welcomes customers' comments and suggestions on the quality and usefulness of this document. Your feedback is important, and helps us to best meet your needs as a user of our products. For example: Are the implementation steps correct and complete? Did you understand the context of the procedures? Did you find any errors in the information? Does the structure of the information help you with your tasks? Do you need different information or graphics? If so, where, and in what format? Are the examples correct? Do you need more examples?
If you find any errors or have any other suggestions for improvement, then please tell us your name, the name of the company who has licensed our products, the title and part number of the documentation and the chapter, section, and page number (if available). Note: Before sending us your comments, you might like to check that you have the latest version of the document and if any concerns are already addressed. To do this, access the new Oracle E-Business Suite Release Online Documentation CD available on My Oracle Support and www.oracle.com. It contains the most current Documentation Library plus all documents revised or released recently. Send your comments to us using the electronic mail address: appsdoc_us@oracle.com Please give your name, address, electronic mail address, and telephone number (optional). If you need assistance with Oracle software, then please contact your support representative or Oracle Support Services. If you require training or instruction in using Oracle software, then please contact your Oracle local office and inquire about our Oracle University offerings. A list of Oracle offices is available on our Web site at www.oracle.com.

Preface
Intended Audience
Welcome to Release 12.1 of the Oracle Advanced Global Intercompany System User's Guide. This guide assumes you have a working knowledge of the following: The principles and customary practices of your business area. Computer desktop application usage and terminology
If you have never used Oracle Applications, we suggest you attend one or more of the Oracle Applications training classes available through Oracle University. See Related Information Sources on page viii for more Oracle E-Business Suite product information.
Deaf/Hard of Hearing Access to Oracle Support Services

To reach Oracle Support Services, use a telecommunications relay service (TRS) to call Oracle Support at 1.800.223.1711. An Oracle Support Services engineer will handle technical issues and provide customer support according to the Oracle service request process. Information about TRS is available at http://www.fcc.gov/cgb/consumerfacts/trs.html, and a list of phone numbers is available at http://www.fcc.gov/cgb/dro/trsphonebk.html.
Documentation Accessibility
Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and
vii
Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/.
Accessibility of Code Examples in Documentation

Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.
Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.
Structure
1 Intercompany Setup 2 Intercompany Transaction Processing 3 Importing Intercompany Transactions 4 Intercompany Reporting A Intercompany Open Interface Tables
Related Information Sources

This document is included on the Oracle Applications Document Library, which is supplied in the Release 12 DVD Pack. You can download soft-copy documentation as PDF files from the Oracle Technology Network at http://otn.oracle.com/documentation, or you can purchase hard-copy documentation from the Oracle Store at http://oraclestore.oracle.com. The Oracle E-Business Suite Documentation Library Release 12 contains the latest information, including any documents that have changed significantly between releases. If substantial changes to this book are necessary, a revised version will be made available on the online documentation CD on My Oracle Support. If this guide refers you to other Oracle Applications documentation, use only the Release 12 versions of those guides. Online Documentation All Oracle Applications documentation is available online (HTML or PDF). PDF - PDF documentation is available for download from the Oracle Technology Network at http://otn.oracle.com/documentation.
viii
Online Help - Online help patches (HTML) are available on My Oracle Support. My Oracle Support Knowledge Browser - The My Oracle Support Knowledge Browser lets you browse the knowledge base, from a single product page, to find all documents for that product area. Use the Knowledge Browser to search for release-specific information, such as FAQs, recent patches, alerts, white papers, troubleshooting tips, and other archived documents. Oracle eBusiness Suite Electronic Technical Reference Manuals - Each Electronic Technical Reference Manual (eTRM) contains database diagrams and a detailed description of database tables, forms, reports, and programs for a specific Oracle Applications product. This information helps you convert data from your existing applications and integrate Oracle Applications data with non-Oracle applications, and write custom reports for Oracle Applications products. Oracle eTRM is available on My Oracle Support.
Related Guides You should have the following related books on hand. Depending on the requirements of your particular installation, you may also need additional manuals or guides. Oracle E-Business Suite Installation Guide: Using Rapid Install: This guide provides information about using the Rapid Install utility to install Oracle Applications Release 12, or as a part of an upgrade from Release 11i to Release 12. Discusses Standard and Express installations, fresh or Vision Demo database installations, as well as techstack and product upgrades. Oracle Applications Upgrade Guide: Release 11i to Release 12: This guide provides information for DBAs and Applications Specialists who are responsible for upgrading a Release 11i Oracle Applications system (techstack and products) to Release 12. In addition to information about applying the upgrade driver, it outlines pre-upgrade steps and post-upgrade steps, and provides descriptions of product-specific functional changes and suggestions for verifying the upgrade and reducing downtime. Oracle Applications Patching Procedures: This guide describes how to patch the Oracle Applications file system and database using AutoPatch, and how to use other patching-related tools like AD Merge Patch, OAM Patch Wizard, and OAM Registered Flagged Files. Describes patch types and structure, and outlines some of the most commonly used patching procedures. Part of Maintaining Oracle Applications, a 3-book set that also includes Oracle E-Business Suite Maintenance Utilities and Oracle E-Business Suite Maintenance Procedures. Oracle E-Business Suite Maintenance Utilities: This guide describes how to run utilities, such as AD Administration and AD Controller, used to maintain the Oracle Applications file system and database. Outlines the actions performed by these utilities, such as monitoring parallel processes, generating Applications files, and maintaining Applications database entities. Part of
ix
Maintaining Oracle Applications, a 3-book set that also includes Oracle Applications Patching Procedures and Oracle E-Business Suite Maintenance Procedures. Oracle E-Business Suite Maintenance Procedures: This guide describes how to use AD maintenance utilities to complete tasks such as compiling invalid objects, managing parallel processing jobs, and maintaining snapshot information. Part of Maintaining Oracle Applications, a 3-book set that also includes Oracle Applications Patching Procedures and Oracle E-Business Suite Maintenance Utilities. Oracle E-Business Suite System Administrator's Guide Documentation Set: This documentation set provides planning and reference information for the Oracle Applications System Administrator. Oracle E-Business Suite System Administrator's Guide- Configuration contains information on system configuration steps, including defining concurrent programs and managers, enabling Oracle Applications Manager features, and setting up printers and online help. Oracle E-Business Suite System Administrator's Guide- Maintenance provides information for frequent tasks such as monitoring your system with Oracle Applications Manager, administering Oracle E-Business Suite Secure Enterprise Search, managing concurrent managers and reports, using diagnostic utilities including logging, managing profile options, and using alerts. Oracle E-Business Suite System Administrator's Guide- Security describes User Management, data security, function security, auditing, and security configurations. Oracle E-Business Suite User's Guide: This guide explains how to navigate, enter data, query, and run reports using the user interface (UI) of Oracle Applications. This guide also includes information on setting user profiles, as well as running and reviewing concurrent requests. Oracle E-Business Suite Diagnostics User's Guide: This manual contains information on implementing, administering, and developing diagnostics tests in the Oracle E-Business Suite Diagnostics framework. Oracle E-Business Suite Integrated SOA Gateway User's Guide: This guide describes the high level service enablement process, explaining how users can browse and view the integration interface definitions and services residing in Oracle Integration Repository. Oracle E-Business Suite Integrated SOA Gateway Implementation Guide: This guide explains how integration repository administrators can manage and administer the service enablement process (based on the service-oriented architecture) for both native packaged public integration interfaces and composite services (BPEL type). It also describes how to invoke Web services from Oracle E-Business Suite by employing the Oracle Workflow Business Event System; how to manage Web service security; and how to monitor SOAP messages. Oracle E-Business Suite Integrated SOA Gateway Developer's Guide: This guide describes how system integration developers can perform end-to-end service
integration activities. These include orchestrating discrete Web services into meaningful end-to-end business processes using business process execution language (BPEL), and deploying BPEL processes at run time. It also explains in detail how to invoke Web services using the Service Invocation Framework. This includes defining Web service invocation metadata, invoking Web services, managing errors, and testing the Web service invocation. Oracle Financials and Oracle Procurement Functional Upgrade Guide: Release 11i to Release 12: This guides provides detailed information about the functional impacts of upgrading Oracle Financials and Oracle Procurement products from Release 11i to Release 12. This guide supplements the Oracle Applications Upgrade Guide: Release 11i to Release 12. Oracle Financials Concepts Guide: This guide describes the fundamental concepts of Oracle Financials. The guide is intended to introduce readers to the concepts used in the applications, and help them compare their real world business, organization, and processes to those used in the applications. Oracle Financials Implementation Guide: This guide provides information on how to implement the Oracle Financials E-Business Suite. It guides you through setting up your organizations, including legal entities, and their accounting, using the Accounting setup Manager. It covers intercompany accounting and sequencing of accounting entries, and it provides examples. Oracle Financial Consolidation Hub User Guide: This guide describes how to set up, maintain, and troubleshoot Oracle Financial Consolidation Hub. It describes setting up entities, categories, consolidation methods, consolidation rules, intercompany rules, calendar maps, translation, consolidation hierarchies, analytical reporting, and the Excel add-in. The guide also includes chapters on submitting data, running consolidations, accounting for acquisitions and disposals, integrating with Internal Controls Manager and WebADI spreadsheets. Oracle General Ledger Implementation Guide: This guide provides information on how to implement Oracle General Ledger. Use this guide to understand the implementation steps required for application use, including how to set up Accounting Flexfields, Accounts, and Calendars. Oracle General Ledger Reference Guide This guide provides detailed information about setting up General Ledger Profile Options and Applications Desktop Integrator (ADI) Profile Options. Oracle General Ledger User's Guide: This guide provides information on how to use Oracle General Ledger. Use this guide to learn how to create and maintain ledgers, ledger currencies, budgets, and journal entries. This guide also includes information about running financial reports.
xi
Oracle Payables User Guide: This guide describes how to use Oracle Payables to create invoices and make payments. In addition, it describes how to enter and manage suppliers, import invoices using the Payables open interface, manage purchase order and receipt matching, apply holds to invoices, and validate invoices. It contains information on managing expense reporting, procurement cards, and credit cards. This guide also explains the accounting for Payables transactions. Oracle Receivables User Guide: This guide provides you with information on how to use Oracle Receivables. Use this guide to learn how to create and maintain transactions and bills receivable, enter and apply receipts, enter customer information, and manage revenue. This guide also includes information about accounting in Receivables. Use the Standard Navigation Paths appendix to find out how to access each Receivables window. Oracle Human Resources Management Systems Approvals Management Implementation Guide: Use Oracle Approvals Management (AME) to define the approval rules that determine the approval processes for Oracle applications. Oracle Subledger Accounting Implementation Guide: This guide provides setup information for Oracle Subledger Accounting features, including the Accounting Methods Builder. You can use the Accounting Methods Builder to create and modify the setup for subledger journal lines and application accounting definitions for Oracle subledger applications. This guide also discusses the reports available in Oracle Subledger Accounting and describes how to inquire on subledger journal entries. Oracle Financials Glossary: The glossary includes definitions of common terms that are shared by all Oracle Financials products. In some cases, there may be different definitions of the same term for different Financials products. If you are unsure of the meaning of a term you see in an Oracle Financials guide, please refer to the glossary for clarification. You can find the glossary in the online help or in the Oracle Financials Implementation Guide. Oracle Trading Community Architecture User Guide: This guide describes the Oracle Trading Community Architecture (TCA) and how to use features from the Trading Community Manager responsibility to create, update, enrich, and cleanse the data in the TCA Registry. It also describes how to use Resource Manager to define and manage resources. Oracle Web Applications Desktop Integrator Implementation and Administration Guide Oracle Web ADI brings Oracle E-Business Suite functionality to a spreadsheet where familiar data entry and modeling techniques can be used to complete Oracle E-Business Suite tasks. You can create formatted spreadsheets on your desktop that allow you to
xii
download, view, edit, and create Oracle E-Business Suite data that you can then upload. Use this guide to implement Oracle Web ADI and for information on defining mappings, layouts, style sheets, and other setup options. Oracle Workflow User's Guide This guide describes how users can view and respond to workflow notifications and monitor the progress of their workflow processes. Oracle Workflow API Reference This guide describes the APIs provided for developers and administrators to access Oracle Workflow. Oracle XML Publisher Administration and Developer's Guide Oracle XML Publisher is a template-based reporting solution that merges XML data with templates in RTF or PDF format to produce a variety of outputs to meet a variety of business needs. Outputs include: PDF, HTML, Excel, RTF, and eText (for EDI and EFT transactions). Oracle XML Publisher can be used to generate reports based on existing E-Business Suite report data, or you can use Oracle XML Publisher's data extraction engine to build your own queries. Oracle XML Publisher also provides a robust set of APIs to manage delivery of your reports via e-mail, fax, secure FTP, printer, WebDav, and more. This guide describes how to set up and administer Oracle XML Publisher as well as how to use the Application Programming Interface to build custom solutions.
Integration Repository
The Oracle Integration Repository is a compilation of information about the service endpoints exposed by the Oracle E-Business Suite of applications. It provides a complete catalog of Oracle E-Business Suite's business service interfaces. The tool lets users easily discover and deploy the appropriate business service interface for integration with any system, application, or business partner. The Oracle Integration Repository is shipped as part of the E-Business Suite. As your instance is patched, the repository is automatically updated with content appropriate for the precise revisions of interfaces in your environment.
Do Not Use Database Tools to Modify Oracle E-Business Suite Data

Oracle STRONGLY RECOMMENDS that you never use SQL*Plus, Oracle Data Browser, database triggers, or any other tool to modify Oracle E-Business Suite data unless otherwise instructed. Oracle provides powerful tools you can use to create, store, change, retrieve, and maintain information in an Oracle database. But if you use Oracle tools such as SQL*Plus to modify Oracle E-Business Suite data, you risk destroying the integrity of your data and you lose the ability to audit changes to your data. Because Oracle E-Business Suite tables are interrelated, any change you make using an
xiii
Oracle E-Business Suite form can update many tables at once. But when you modify Oracle E-Business Suite data using anything other than Oracle E-Business Suite, you may change a row in one table without making corresponding changes in related tables. If your tables get out of synchronization with each other, you risk retrieving erroneous information and you risk unpredictable results throughout Oracle E-Business Suite. When you use Oracle E-Business Suite to modify your data, Oracle E-Business Suite automatically checks that your changes are valid. Oracle E-Business Suite also keeps track of who changes information. If you enter information into database tables using database tools, you may store invalid information. You also lose the ability to track who has changed your information because SQL*Plus and other database tools do not keep a record of changes.
xiv
1
Intercompany Setup
This chapter covers the following topics: Introduction Setting up AGIS
Introduction
Advanced Global Intercompany System (AGIS) enables you to create, settle and reconcile intercompany transactions. Intercompany transactions are transactions that occur between two related legal entities in an enterprise or between groups in the same legal entity. Transactions that occur between two legal entities are called intercompany transactions and transactions that occur between two groups within one legal entity are called intracompany transactions. The balances of the intercompany transactions must be eliminated or adjusted when preparing the consolidated financial statement, or it might result in overstated financial results, which in turn might lead to legal repercussions against the enterprise. Intercompany transactions can be identified and eliminated by the use of specific accounts to book these transactions. Defining these accounts allows you to book transactions that are identified as intercompany transactions in the specific accounts. These accounts must be defined as a part of the General Ledger setup process. Before you start working on AGIS, you must setup the following: Complete the Accounting Setup Manager to set up General Ledger and legal entities Set up AGIS
Note: AGIS is referred to as Intercompany in this document.
Intercompany Setup 1-1
Related Topics
Creating Accounting Setups, Oracle Financials Implementation Guide Intercompany and Intracompany Balancing, Oracle Financials Implementation Guide
Setting up AGIS
Intercompany transactions must be processed in a consistent, systematic way across the enterprise. Use the Intercompany Setup tab to define the processing rules at the enterprise level.
Intercompany Accounting Pages

This section describes the Intercompany Accounting page.
Intercompany Accounts Pages

This section describes key Intercompany accounting setup pages. Common Intercompany Accounts Fields This section describes some of the common fields used in the Intercompany accounts setup pages.
Transacting Legal Entity
The legal entity with the transacting (from) perspective in the intercompany trading relationship. The legal entity from which the intercompany transaction is initiated. Choose the transacting legal entity from the list of values.
Transacting Ledger
The ledger with the transacting (from) perspective in the intercompany trading relationship. You can choose any ledger that is mapped to the transacting legal entity, including both primary and secondary ledgers, since intercompany accounts can be defined for both primary and secondary ledgers.
Transacting Balancing Segment Value
The balancing segment value for the transacting (from) perspective for which intercompany accounts are defined. The list of values displays all the balancing segment values in the transacting ledger to which the transacting legal entity is mapped.
Trading Partner Legal Entity
The legal entity with the trading partner (to) perspective in the intercompany trading relationship. Choose the trading partner legal entity from the list of values. The list of values shows all legal entities to which you have access to and the value All Other.
Trading Partner Ledger
The ledger with the trading partner (to) perspective in the intercompany trading relationship.
1-2 Oracle Advanced Global Intercompany System User's Guide
Trading Partner Balancing Segment Value
The balancing segment value for the trading partner (to) perspective for which intercompany accounts are defined. The list of values displays all the balancing segment values in the trading partner ledger to which the trading partner legal entity is mapped. Intercompany Accounts Search Page Use this page to query, create, and update intercompany accounts. To update intercompany accounts, query the trading legal entity and transacting ledger and click Update, or choose Create Accounts to create a new Intercompany account. Create Intercompany Accounts Pages This page is the first step in creating a new intercompany account. To access the Define Accounts page, click the Define Accounts icon. Define Accounts Page Use this page to define Intercompany Receivables and Payables accounts. For each of these account types you must define at least one account.
Use for Balancing
Use this field to select an account to be used as the balancing account in subledgers and intercompany General Ledger journals. Update Intercompany Accounts This page is similar to the Create Intercompany Accounts page and allows you to update existing intercompany accounts.
View Reciprocal Accounts
Clicking this button displays the accounts used by the Trading Partner (to) Legal Entity and Trading Partner (to) Balancing Segment Value to book intercompany transactions with the Transacting (from) Legal Entity and Transacting (from) Balancing Segment Value. This button is inactive if the Trading Partner Legal Entity or Balancing Segment Value does not have reciprocal intercompany accounts defined, or if the Trading Partner Legal Entity resides on another applications instance, or if the value is All Other.
Balancing Accounts Search Page

Use this page to query, create, or update intracompany balancing rules. To update a balancing rule, query the rule and select the rule from the results table. Choose the Create Rule button to create a new intracompany balancing rule.
Create Intracompany Balancing Rules Page

Use this page to create new balancing rules. Before creating a new rule, you should query the rule on this page to ensure the rule does not already exist.
Selected Fields Ledger: Enter the ledger for which to define balancing rules. The list of values displays all the ledgers to which you have access and indicates whether the ledger is primary or secondary. The ledgers available here come from the Data Access Set assigned to your responsibility. The list of values displays only ledgers that are assigned to complete configurations in Accounting Setup Manager and that have the Enable Intracompany Balancing Journals check box checked on the Update Ledger: Ledger Options page. Status: This field indicates whether the rule is enabled or disabled. Additional Information Context: This field allows you to enter the context for the Intracompany Rule Descriptive flexfield. The information entered is only for your reference.
Balancing Details Tab
Debit Balancing Segment: This field represents the debit (party recording receivable) balancing segment value. The list of values shows all of the balancing segment values allowed by your security profile. For each ledger-legal entity-source-category combination, there must be the default rule All Other-All Other. Credit Balancing Segment: This field represents the credit (party recording payable) balancing segment value. The list of values shows all of the balancing segment values allowed by your security profile. For each ledger-legal entity-source-category combination, there must be the default rule All Other-All Other. Debit Account: This is the balancing account that the debit balancing segment value uses to balance when trading with the credit balancing segment value. For balancing segment value - balancing segment value rules where values are explicitly chosen, the balancing account you choose is used exactly. However, when you select the value All Other, the Balancing API determines and substitutes the correct balancing and intercompany segment values at the time of balancing. For example, if you enter an account code combination 01.4000.02, it actually means xx.4000.yy, where xx is the balancing segment value of the debit balancing segment value on the journal and yy is the balancing segment value of the credit balancing segment value on the journal. The Balancing API substitutes these values during balancing. Credit Account: This is the balancing account that the credit balancing segment value uses to balance when trading with the debit balancing segment value. For balancing segment value - balancing segment value rules where values are explicitly chosen, the balancing account you choose is used exactly. However, when you select the value All Other, the Balancing API determines and substitutes the correct balancing segment value at the time of balancing. For example, if you enter and account code combination 02.2000.01, it actually means xx.2000.yy, where xx is the balancing segment value of the credit balancing segment value on the journal and yy is the balancing segment value of the debit balancing segment value on the journal. The Balancing API substitutes these values during balancing.
Options Tab
Level of Summarization: Summary Net: If you select Summary Net, the Balancing API summarizes the debits and credits for each balancing segment value on the journal, determines the overall net debit or net credit for each balancing segment value, balances using the net amounts for each balancing segment value, and produces a summary balancing line for each balancing segment value. When processing in Summary Net mode, the Balancing API retains the differences in exchange rates for lines with the same balancing segment value. Negative debits are interpreted as positive credits and negative credits as positive debits, because each balancing segment value is summarized. Summary Net is the default. Detail: If you select Detail, each line on the journal is balanced individually and a balancing line is generated for each line on the journal. For lines with negative amounts (debits or credits), the sign of each original line is retained in the balancing line.
Clearing Balancing Segment Value Usage: Use for All Journals: This option specifies that a clearing balancing segment value will be used for all types of journals. You can enter a clearing balancing segment value at the journal header level (in General Ledger only), or the default clearing balancing segment value will be used if no value is manually entered. This option is the default. Use for Many-to-Many Journals Only: This option specifies that a clearing balancing segment value should be used only to clear many-to-many journals. You can enter a clearing balancing segment value at the journal header level (in General Ledger only), or the default clearing balancing segment value will be used if no value is manually entered.
Default Options: Default options include specifying clearing options in case a clearing company should be used but none can be determined for the journal. Default Clearing Balancing Segment Value: If no clearing company is specified for the journal, use the default clearing company. The list of values for the Default Clearing Balancing Segment Value is restricted to those that are mapped to the legal entity. If you choose the Default Clearing Balancing Segment Value, you need to enter a clearing balancing segment value. Manually Entered Clearing Balancing Segment Value: If no clearing company is specified for the journal then an error occurs. This option should not be used with journals coming from subledgers because the clearing company cannot be specified in Subledger Accounting.
Default Rule: This option can be used with either Detail or Summary Net level balancing. The Default Rule is the rule defined for All Other-All Other. When this option is specified, balancing lines are built using the All Other-All Other rule, ignoring all the other rules defined in the Balancing Rules subtab.
Note: This option is not available if you set the Clearing Balancing
Segment Value Usage to Use for All Journals. This option is available only if you set the Clearing Balancing Segment Value Usage to Use for Many-to-Many Journals.
Intercompany Organizations Pages

After defining intercompany accounts, you must create organizations and assign them to the legal entities to process intercompany transactions. Intercompany allows you to define organizations for your diverse business needs. Once defined, intercompany organizations represent the initiators and recipients in Intercompany. An initiator is an organization that initiates a transaction event with another organization. A recipient is an organization that receives a transaction from the initiator. The Trading Community Architecture (TCA) data model is used to define intercompany organizations. Each organization created in Intercompany is classified as Intercompany in the TCA model. Use the Intercompany Organizations page to search for an existing organization or create a new organization. You can either create a new organization or assign a legal entity as an intercompany organization. You can disable intercompany organizations by searching for an organization and updating the Enabled field to No.
Note: When you create an new organization, it must be assigned to a
legal entity. When you assign a legal entity as an organization, it must be assigned to itself. Additionally, you must associate the organizations with an operating unit if invoices are required for the transactions.
View Intercompany Organization Page

Each intercompany organization is assigned to one or many contacts. The contacts are defined as parties of type Person and assigned to intercompany organizations. Click the Organization Name to view the Contact Information for an intercompany organization.
Related Topics Introduction to Oracle Trading Community Architecture, Oracle Trading Community Architecture User Guide Intercompany Transaction Types Pages, page 1-7 Receivables Assignments Page, page 1-9
Intercompany Security Pages

Intercompany has a flexible security model because users need to enter transactions for different organizations that are assigned to numerous organizations belonging to different legal entities. Users can access organizations through a single responsibility. The responsibilities available to intercompany users are the following: Intercompany Super User: Full access to intercompany transaction pages and setup pages. Intercompany User: Full access to intercompany transaction pages, but only view access to setup pages.
Use the Security tab to assign a user to an organization.
Intercompany Organization Assignments Page

Use the Intercompany Organization Assignments page to search for and update an organization assignment, or to create new assignments. Access to Transactions Select this option to allow the user access to the transactions of the organization the user is assigned to. Send Approval Notification Select this option if you want the user assigned to the organization to receive approval notifications.
Intercompany Transaction Types Pages

In AGIS, you can define transaction types to manage intercompany transactions, which are shared across all the intercompany organizations. Transaction types help you in setting up the processing rules for all transactions, which must be processed in a systematic way following the same rules across the enterprise. Examples of processing rules that can be set for a transaction type are transactions that require invoice and transactions that must be auto approved or manually approved.
Tip: Create a transaction type only if the seeded transaction type is not
sufficient for your operations.
Creating Intercompany Transaction Types Page

This section describes the Intercompany Transaction Types page. Use the Transaction Types page to search for and update a transaction type or create a new transaction type. Selected Fields in the Create Transaction Types Page
Invoicing
If a legal entity requires an invoice, an invoice is created regardless of the option selected for a transaction type. If a legal entity does not require an invoice, an invoice is created only when Required is selected. Select Required to create invoices.
Manual Approval
Select Required to specify transaction types that require recipients' approval.

Note: Recipients cannot reject transactions when Manual Approval is
set to Not Required because transactions submitted by the initiator are processed as approved.
Intercompany Periods Pages

The period status functionality provides you with a central point to control the timing of intercompany transaction processing independent of the General Ledger, Receivables and Payables through the Intercompany Periods page. You must define the intercompany calendar before changing Intercompany Periods. See Defining Intercompany Calendar, page 1-12.
Note: This setup is optional. Use Periods tab to control the period status
per transaction type.
Control Period Statuses Page

Intercompany transactions are recorded and accounted for in an open period. Use the Open/Close Intercompany Period Status pages to search for a period and open or close the period for a transaction. Optionally, you can close a period for all transactions.
Review Open Transactions Page

When you want to close a period with open transactions, you must sweep the transactions to another period. In the Control Period Statuses page, click the number in Open Transactions to navigate to the Review Open Transactions page. Use the Review
Open Transactions page to review and sweep the transactions to another period.
Intercompany Invoicing Options Pages

It is a legal requirement, in some countries, to create invoices when intercompany transactions are transferred to Payables and Receivables. To create invoices in Payables and Receivables, customers and suppliers must be set up and associated to the transacting organizations. The Invoicing Options tab is a central point for setting up appropriate customer and supplier information between legal entities, operating units, and organizations. The Receivables Assignments and Customer and Supplier Associations subtabs in the Invoicing Options tab are prerequisites for setting up intercompany invoicing options.
Note: If your business requirement does not require you to create
invoices, you need not use the Invoicing Options tab.
Receivables Assignments Page

If an invoice is required for intercompany transactions, you must associate intercompany organizations with operating units and then assign the intercompany transaction types with Receivables transaction types for each operating unit. Use the Receivables Assignments page to search for operating units and update or create assignments for operating units. Selected Fields in the Receivables Assignments Page
Operating Unit
Lists the operating units that are associated with an active intercompany organization.
Receivables Transaction Type
You can either select the seeded Receivables Transaction Type Intercompany or create a Receivables Transaction Type, or choose existing Receivables Transaction Types.
Receivables Memo Line
You can either select the seeded Receivables Memo Line Global Intercompany or choose an existing Receivables Standard Memo Line.
Customer Supplier Associations

You can create the following two types of associations in Intercompany: Customer association: When a legal entity is represented in another legal entity as a customer, the represented legal entity has a customer association. Supplier association: When a legal entity is represented in another legal entity as a supplier, the represented legal entity has a supplier association.
The above associations denote how legal entities are represented in other legal entities.
For example, if legal entity A has a supplier association with legal entity B, it means that in legal entity B, legal entity A is set up as a supplier that creates a Payables invoice. Setting up customer supplier associations between legal entities eliminates the need to create duplicate entities for each organization within a legal entity. You can set up an association at the following levels: Legal entity level Operating unit level Organization level
Tip: It is better to establish an association at the legal entity level
because the association assigned at a legal entity level automatically defaults to the organization in it.
Customer and Supplier Association Page Use the Customer and Supplier Association page to create customer and supplier association. You can create an association by: Selecting the trading partners Adding a Customer or Supplier Name and a Bill-to or Pay-to Location to the organization party or selecting an existing Customer or Supplier Account and Bill-to or Pay-to Location
Selected Fields in Customer and Supplier Association Page Supplier Site
Enter the site name for the chosen supplier. This field can only be used when the supplier is entered.
Customer Account Location
Enter the site name for the chosen customer. This field can only be used when the customer is entered. Trading Partners Page A trading partner is an organization in a corporate enterprise wherein transactions are processed. Use this page to determine if an association exists between two organizations. The Initiator/Recipient Organization can be a legal entity, an operating unit, or an organization.
Fields in the Legal Entity Customers and Suppliers Page Initiator Organization
The supplier initiating the transaction.
Recipient Organization
The customer receiving the transaction.
Intercompany System Options

Intercompany system options help you to manage intercompany transactions across the enterprise. By defining these options at the enterprise level, you can minimize disputes, decrease processing time and cut administrative costs. For example, if the companies in an enterprise use the same currency for all transactions, it ensures that the transactions are posted in the same currency, which in turn, simplifies reconciliation.
Note: Before setting up intercompany system options, you must decide
how to process Intercompany transactions. You must decide whether to enforce an enterprise-wide currency or allow Intercompany transactions in local currencies, allow recipients to reject intercompany transactions, what minimum amount of transactions should be processed, and so forth.
Use the Intercompany System Options page to set enterprise level settings to govern the behavior of the Intercompany system and determine how transactions are processed.
Note: Changing system options does not affect transactions already in
progress. It affects new transactions only.
Intercompany Batch Numbering

In AGIS, all transactions are numbered sequentially. Use this option to manually or automatically number intercompany transactions. See Defining Document Sequences, Oracle System Administrators User Guide
Intercompany Transaction Currency

Use this option to specify a default currency on transactions. If you do not specify a currency for this option, you can select a currency while entering a transaction. However, if you specify a currency, it defaults in the Create Batch: Header and Transactions page and cannot be changed.
Minimum Transaction Amount

Use this option to set the minimum intercompany transaction amount. The minimum transaction amount affects all intercompany transactions. The minimum transaction amount is validated against the amount in the transaction line.
Note: Before setting the minimum transaction amount, you must first
set the transaction currency.
Minimum Transaction Amount Currency

This option is required if you enter a minimum transaction amount but do not define the intercompany transaction currency.
Intercompany Conversion Rate Type

Use this option to specify the conversion rate type for converting foreign currency transactions to the equivalent ledger currency.
Note: You cannot have user defined conversion rates in intercompany
transactions.
Allow Recipients to Reject Transactions

Use this option to specify whether the recipients of intercompany transactions can reject transactions.
Transfer Transactions to General Ledger

You can transfer transactions to General Ledger online (when they reach Approved status) or in batch mode. If batch mode is selected, you must run the concurrent program.
Transferring Transactions to Payables and Receivables

You can transfer transactions to Payables and Receivables online (when they reach Approved status) or in batch mode. If batch mode is selected, you must run the concurrent program.
Intercompany Calendar
Use this option to define an intercompany calendar to control intercompany periods.
Approvals Management Setup for Intercompany

To derive approvers and users to whom transactions related notifications must be sent, Intercompany uses Oracle Approvals Management System (AME). There are two default rules seeded in AME that builds the list of approvers and users based on the contacts defined for the intercompany organization. The default rules are: Default rule for Initiator Intercompany Transaction: Users who receive FYI notifications.
Default rule for Recipient Intercompany Transaction: Users who are approvers.
Default Accounts Rules Setup In Subledger Accounting for Intercompany

AGIS transactions must be consistent in distributing the expense amounts to the appropriate distribution accounts. Distribution accounts are account combination that appears in the transaction entry pages when you create an intercompany batch. The distributed accounts must be defined for each ledger and are generated as defined in the Subledger Accounting Transaction Account Builder (SLA TAB). The following must be setup in the SLA TAB to generate the default distribution account combination: Transaction Account Type: This classifies the distribution accounts that are generated for intercompany transactions. The following are the seeded intercompany transaction account types: AGIS Initiator Intercompany Distribution Account: For defaulting initiator distribution accounts AGIS Recipient Distribution Account: For defaulting recipient distribution accounts
Account Derivation Rules: Allows you to derive accounting flexfield combinations or individual transactions, based on source, constants, mapping sets, and conditions. Transaction Account Definition: Allows you to assign the account derivation rules to the transaction account types. For intercompany transactions the Transaction Account Definition (TAD) is assigned to a ledger.
Note: You cannot create a new transaction account type. You can only
create a new Transaction Account Definition in AGIS.
Before creating a new Transaction Account Definition, ensure that the following are defined: Legal entities and primary ledger Trading partners Intercompany accounts
To create a new Transaction Account Definition:

1. 2.
Log in to Subledger Accounting using the SLA responsibility. Create accounting derivation rules using the Account Derivation Rules window.
3.
Create the TAD and assign the account derivation rules to the transaction account definition. Log in to General Ledger using the GL responsibility and assign the TAD to the ledger.
Note: A default account is assigned when you create a new TAD to
4.
generate the intercompany distribution accounts. This default account is generated whenever the account derivation rule satisfies none of the specified conditions.
Related Topics
Creating Account Derivation Rules, Oracle Subledger Accounting Implementation Guide Creating Transaction Account Definitions, Oracle Subledger Accounting Implementation Guide
Example of Setting Default Account Rules

This section explains creating a new TAD with the help of an example. A TAD can be set up in two ways: A single balancing segment value mapped to one legal entity. Multiple balancing segment values mapped to one legal entity.
This example uses the Vision Enterprise setup that has two charts of accounts namely US Ledger and Euro Ledger, each for the Vision Corporation ledger and the Vision Europe ledger. The following comprises the Ledger: Vision Corporation:
Balancing Segment Value 01 02 03 Legal Entity Vision West Vision East Vision East Intercompany Organization Vision SFO Vision Boston Vision Jersey
The following comprises the Ledger: Vision Europe:
Balancing Segment Value 10 11
Legal Entity Vision France Vision Germany
Intercompany Organization Vision Paris Vision Frankfurt
Single Balancing Segment Value mapped to a Legal Entity

When a single balancing segment value is mapped to a legal entity , the initiator and recipient balancing segment values are the Source in the Transaction Account Builder to obtain the distribution accounts. The initiator and recipient balancing segment values are identified through the From and To legal entity when entering the transactions. Assume that Vision SFO of Vision West (balancing segment value 01) in the US Ledger chart of accounts is the initiator and Vision Paris of Vision France (balancing segment value 10) in the Euro Ledger chart of accounts is the recipient. To generate the default distribution accounts you must define the account derivation rules for the initiator and distributor transaction account types, which are the following: Balancing Segment Value Natural Account Segment Other Segments
Based on the rule for each segment a default initiator and recipient distribution account is generated when entering the transactions. Generating the Initiator Distribution Account Use the Account Derivation Rules window to create account derivation rules for generating the initiator distribution account. The following table describes the account derivation rule for the initiator balancing segment value.
Priority Value Type Value Override Segment Value Type Value
Source
Initiator BSV
The following table describes the account derivation rule for the initiator natural account.
Priority
Value Type
Value
Override Segment
Value Type
Value
1 Condition
Constant
2100

Value Type Constant

Value Allocation
Source Transaction Type
Operator =
The following table describes the account derivation rule for initiator other segments.
Constant
000
Using the Transaction Account Definitions page, assign the above created rules to the appropriate transaction account type as shown in the following table to create a TAD to generate the initiator distribution account of US Ledger.
Transaction Account Type Balancing Segment Value Natural Account Segment Other Segments Account Derivation Rule Initiator BSV Rule Initiator Distribution Account Rule Initiator Other Segment Rule
Generating the Recipient Distribution Account Using the Account Derivation Rules window, create account derivation rules to generate the recipient distribution account. The following table describes the account derivation rule for the recipient balancing segment value.
Priority
Value Type
Value
Override Segment
Value Type
Value
Source
Recipient BSV
The following table describes the account derivation rule for the recipient natural account.
1 Condition
Constant
2100

Value Type Constant

Value Allocation
Operator =
The following table describes the account derivation rule for recipient other segments.
Constant
000
Using the Transaction Account Definitions page, assign the above created rules to the appropriate transaction account type as shown in the following table to create a TAD to generate the recipient distribution account of Euro Ledger.
Transaction Account Type Balancing Segment Value Natural Account Segment Other Segments Account Derivation Rule Recipient BSV Rule Recipient Distribution Account Rule Recipient Other Segment Rule
Multiple Balancing Segment Values mapped to a Legal Entity

When two or more balancing segment values are mapped to a legal entity, you must determine the balancing segment value that must be used as the initiator distribution of the initiator legal entity by defining mapping sets. Mapping sets must be defined before creating account derivation rules for each intercompany organization. Assume that Vision Boston (balancing segment value 02) of Vision East in the US Ledger chart of accounts is the initiator and Vision Paris of Vision France (balancing segment value 10) in the Euro Ledger chart of accounts is the recipient. To generate the default distribution accounts you must first define mapping sets to assign Vision Boston as the initiator distribution to derive a value and then define the account derivation rules for the initiator and distributor transaction account types. A default initiator and recipient distribution account is generated when entering the transactions based on the rules defined. Defining Mapping Sets The following is the initiator mapping set to derive the balancing segment value from the intercompany organization.
Value Type Input Input Value Vision SFO Vision Boston Vision Jersey Output Value 01 02 03 Effective From Effective To
The following is the recipient mapping set.

Value Type Input Input Value Vision Paris Vision Frankfurt Output Value 10 11 Effective From Effective To
Generating the Initiator Distribution Account Use the Account Derivation Rules window to create account derivation rules for generating the initiator distribution account. The following table describes the account derivation rule for the initiator balancing segment value.
Priority 1
Value Type Mapping Set
Value Balancing segment value derived from intercompany organization <Mapping Set Name>
Segment Natural Account Segment
Input Source Initiator
The following table describes the account derivation rule for the initiator natural account.
1 Condition
Constant
2100

Value Type Constant

Value Allocation
Operator =
The following table describes the account derivation rule for initiator other segments.
Constant
000
Using the Transaction Account Definitions page, assign the above created rules to the appropriate transaction account type as shown in the following table to create a TAD to generate the initiator distribution account of US Ledger.
Transaction Account Type Balancing Segment Value Account Derivation Rule Initiator BSV Rule
Transaction Account Type Natural Account Segment Other Segments
Account Derivation Rule Initiator Distribution Account Rule Initiator Other Segment Rule
Generating the Recipient Distribution Account Use the Account Derivation Rules window to create account derivation rules for generating the recipient distribution account. The following table describes the account derivation rule for the recipient balancing segment value.
Priority 1 Value Type Mapping Set Value Balancing segment value derived from intercompany organization <Mapping Set Name> Segment Natural Account Segment Input Source Recipient
The following table describes the account derivation rule for the recipient natural account.
1 Condition
Constant
2100

Value Type Constant

Value Allocation
Operator =
The following table describes the account derivation rule for the recipient other segments.
Priority
Value Type
Value
Override Segment
Value Type
Value
Constant
000
Using the Transaction Account Definitions page, assign the above created rules to the appropriate transaction account type as shown in the following table to create a TAD to generate the recipient distribution account of Euro Ledger.
Transaction Account Type Balancing Segment Value Natural Account Segment Other Segments Account Derivation Rule Recipient BSV Rule Recipient Distribution Account Rule Recipient Other Segment Rule
2
Intercompany Transaction Processing
This chapter covers the following topics: Intercompany Home Page Intercompany Transaction Page Intercompany Batch Numbering Sequence Workflow Notifications Transferring Transactions to General Ledger Transferring Transactions to Receivables and Payables
Intercompany Home Page

Use the Intercompany Home and Transaction pages to receive, respond to, and initiate intercompany transactions for multiple recipients. The transactions that you receive are inbound transactions and the transactions that you initiate are outbound transactions. The Intercompany Home displays the most recent transactions that require your intervention. This page displays a summary of your open notifications, and a list of five most recently received transactions. On the Home page, you can search transactions by Inbound or Outbound Batch Number, or navigate to the Create Batch page to create an intercompany transaction. The Intercompany Transaction pages enables you to enter transactions addressed to multiple recipients thereby speeding up data entry and simplifying management of intercompany allocations.
Intercompany Transaction Page

There are two distinct flows for the Intercompany transaction entry and processing: an outbound transaction flow, and an inbound transaction flow. These flows are implemented in the Transactions pages as tabs: Outbound and Inbound. The Outbound
Intercompany Transaction Processing 2-1
tab provides all the functions an initiator of an intercompany transaction can perform. The inbound tab provides all the functions a recipient of the transaction can perform.
Outbound Transactions Page

Use the Outbound Batches page to create intercompany transactions in batch mode, submit them to the recipients for approval. Additionally, you can search, personalize views, create, and update batches. You can personalize and create new views. You can create a batch for organizations you can access and include any number of recipients in the batch. Creating a batch is a two-step process: Enter the batch header and transactions. Enter the batch expense or revenue distributions.
Create Batch: Header and Transactions Page

Use the Create Batch: Header and Transactions page to enter the details listed in the following table:
Field Batch Number Description You can edit this field if you set the batch numbering to Manual in the System Options tab. The list of values includes organizations you can access. Defaults to the system date. Displays the new or original batch number when a batch is reversed. Sum of all the recipient debits and credits. Sum of all the recipient transaction amounts. Calculates the total amount of all transactions and updates the Batch Actual Amount and Amount Difference. It also recalculates the total debit and credit transaction amounts.
Initiator GL Date Reversal Reference
Control Amount Actual Amount Recalculate Amounts
Create Batch: Distributions Page

Use the Create Batch: Distributions page to enter distributions lines for the
Intercompany transaction details that you created. The distribution lines are entered depending on the option selected for Distribution mode in the previous page. If you selected the Automatic distribution mode while entering the batch header and transactions, then the distributions that you enter are prorated later across all transactions. When submitting the batch, these distributions are prorated based on the number of recipient transactions.
Note: The amounts are prorated across transactions and not across
recipients because a batch can contain many transactions for the same recipient.
If Manual distribution mode is selected, then the initiator can enter the distributions manually using the Initiator Accounting tab. Optionally, using the Recipient Account tab, the initiator can enter recipient accounting regardless of the access privileges to the recipient. The recipient accounting need not balance since the recipients may make adjustments. The Transaction Account Builder in Subledger Accounting is called to default initiator and recipient distribution accounts for each transaction. You can enter the distribution accounts manually in the Outbound Distribution page if these rules are not been set up in Subledger Accounting. The initiator receivables account and the recipient payables account are generated automatically after the transaction has been approved.
Recalling Batches and Transactions

Use the Outbound Batches page to recall a batch and update the transactions. To recall a batch and all its transactions, query the batch and click Recall. To recall individual transactions in a batch, click Update against the transaction and select the Recall option from the Action list in the Update Batch: <batch number> page. You can only recall a batch or transaction that you submitted to the recipient for approval.
Reversing Batches and Transactions

Use the Outbound Batches page to reverse a batch. To reverse a batch, query the batch and click Reverse. To reverse individual transactions in a batch, click Update against the transaction and select the Reverse option from the Action list in the Update Batch: <batch number> page. You can reverse a batch or a transaction that is approved or complete. When you reverse a transaction you must select the appropriate reversal method: Switch Debit/Credit or Change Sign.
Related Topics
Intercompany Security Pages, page 1-7 Intercompany Batch Numbering, page 2-4 Default Accounts Rules Setup In Subledger Accounting for Intercompany, page 1-13
Inbound Transactions Page

Use the Inbound Transactions page to search, personalize views, update, and view the transactions that you received.
Update Transactions Page

Use the Update Transactions page to enter transaction descriptions, enter rejection reasons, update recipient distributions if autoaccounting rules are not defined, and approve and reject transactions. The transaction cannot be rejected if the Allow Recipient to Reject Transactions? option is set to No in the Intercompany System Options page of the Intercompany Setup tab .
Note: The updates can be carried out only when the transaction is in
Received status. A user must be set up as a contact for the recipient organization to approve and reject transactions.
Intercompany Batch Numbering Sequence

Intercompany batch number is a unique control number for intercompany batches that are controlled by a numbering mechanism as selected in the Intercompany System Options page of the Intercompany Setup tab. You select the numbering mechanism in the System Options page of the Intercompany Setup tab. If you select System Generated, then the application generates a batch number while creating a batch. If you select Manual, then you maintain a series of numbers and manually record the batch number when creating a batch. The initial sequence number is one. The batch number type is database sequence. Database sequence is a sequence version associated with the batch numbering. Database sequence ensures that the system-generated batch number is unique and, thus, not validated. Manual batch numbers are validated for uniqueness in the context of the database instance, and initiator combination when creating the transaction.
Related Topics
Accounting and Reporting Sequencing, Oracle Financials Implementation Guide
Workflow Notifications
The initiator and recipient workflow automate transaction processing by performing validations and notifying the status of the transactions at intervals to the initiator and the recipient. When transactions do not pass the validations in the initiator and recipient workflow, the application sends notifications to the appropriate users. You respond to the notification in the Notification Details page. A user must be set up as a contact of the Initiator or Recipient organization to receive notifications.
Related Topics
Intercompany Security Pages, page 1-7
Transferring Transactions to General Ledger

Intercompany transactions that do not need invoices are directly transferred to General Ledger once approved. Before you transfer the transactions, ensure the following: The transfer options are set in the Setup tab The corresponding period in general ledger is open The transaction status is approved The exchange rate exists between the intercompany and general ledger currency if they are different The transaction date is specified for calculating the exchange rate
The workflow process transfers the intercompany transactions depending on the options set in the System Options page of the Intercompany Setup tab. If you select Online mode, then no intervention is necessary, the initiator and recipient workflow transfers transactions on approval. If you select Batch mode, then you must run the concurrent request to transfer the transactions or schedule the concurrent request.
Note: On successful transfer, the transaction status changes to
Transferred to Initiator GL or Transferred to Recipient GL respectively for the initiator and recipient workflows. The Batch and Transaction status is set to Complete once the transactions are transferred to both initiator and recipient ledgers.
Intercompany only populates an interface table in General Ledger for intercompany transactions. After Intercompany transfers the transactions to the GL Interface tables, you must run or schedule the GL Journal Import concurrent program to import these journals into General Ledger for both the Online and Batch mode. The actual posting of the transactions into the appropriate General Ledger accounting tables is performed separately by the GL Posting process after the journals are imported into General Ledger.
Schedule Requests Page

Use the Transfer Intercompany Transactions To General Ledger program in the Schedule Request page to transfer or schedule and transfer the transactions to General Ledger in batch mode. The following table explains the parameters for this program.
Note: The program transfers all transactions irrespective of the
intercompany organizations assigned to the user who schedules the request.
Parameter GL Date From GL Date To Ledger From Ledger To Legal Entity From Legal Entity To Intercompany Organization From Intercompany Organization To Run Journal Import
Description Specify the General Ledger start date of the transactions. Specify the General Ledger end date of the transactions. Select the starting ledger from the list of values. Select the closing ledger from the list of values. Select the top legal entity from the list of values. Enter the bottom legal entity from the list of values. Enter the top Intercompany organization from the list of values. Enter the bottom Intercompany organization from the list of values. Select Yes to run the GL Journal Import process.
Parameter Create Summary Journals
Description Select this option if you want to create the journal entries in summary format in general ledger.
Concurrent Program Execution Report

After transferring the transactions, the application generates a report displaying the transactions that were transferred General Ledger and their status.
Related Topics
Opening and Closing Accounting Periods, Oracle General Ledger Implementation Guide System Options Page, page 1-11 Running Reports and Programs, Oracle Applications User's Guide
Transferring Transactions to Receivables and Payables

The initiator workflow transfers the intercompany transactions to Receivables to create invoices as required by legal or business requirements. After creating the invoices, Receivables updates the intercompany transactions with the invoice numbers and passes the number to the recipient workflow, which updates and transfers the transaction to Payables. Before you transfer the transactions, ensure the following: Transfer options are set in the System Options page of the Intercompany Setup tab. Receivables Transaction Type, Receivables Memo Line are mapped to intercompany transactions in the Invoicing Options subtab. Customer and supplier associations are defined in the Invoicing Options subtab. Transaction status is approved. Transaction date is specified for calculating the exchange rate.
The application transfers the transactions to Receivables and Payables depending on the options set in the System Options page of the Intercompany Setup tab. Execute the following steps to transfer the transactions in Online and Batch modes. To transfer the transactions in Online mode:
1.
The user must approve the transaction.
The initiator workflow transfers the intercompany transaction details to the Receivables Interface tables and the transaction status changes to Transferred to Receivables.
2.
Run the Receivables AutoInvoice Program or schedule it to run at regular intervals. On successful completion of the Receivables AutoInvoice Program, the invoice number is updated on the Intercompany transaction and the recipient workflow transfers the intercompany transaction details to Payables Interface tables and the transaction status changes to Complete.
3.
Run the Payables Open Interface Program or schedule it to run at regular intervals.
To transfer the transactions in Batch mode:

1. 2.
The user must approve the transaction. Run the Transfer Intercompany Transactions to Receivables or schedule it to run at regular intervals. The transaction status changes to Transferred to Receivables.
3.
Run the Receivables AutoInvoice Program or schedule it to run at regular intervals. On successful completion of the Receivables AutoInvoice Program, the invoice number is updated on the intercompany transaction.
4.
Run the Transfer Intercompany Transactions to Payables or schedule it to run at regular intervals. The transaction status changes to Complete.
5.
Run the Payables Open Interface Program or schedule it to run at regular intervals.
Schedule Requests Page

Use the Transfer Intercompany Transactions To Receivables and Transfer Intercompany Transactions To Payables programs in the Schedule Request page to transfer or schedule and transfer the transactions in batch mode.
Note: The program transfers all transactions irrespective of the
intercompany organizations assigned to the user who schedules the request.
For each option in the Schedule Request page, if a value is not supplied, the request runs for all the values for that option. The value Yes in the Submit AR Auto Invoice and the Submit Payables Import automatically runs the respective import processes.
Concurrent Program Execution Report

After transferring the transactions, the application generates a report displaying the transactions that were transferred to Receivables and Payables and their status.
Related Topics
Entering Transactions, Oracle Receivables User Guide Running AutoInvoice, Oracle Receivables User Guide Payables Open Interface Import Program, Oracle Payables User's Guide System Options Page, page 1-11 Running Reports and Programs, Oracle Applications User's Guide
3
Importing Intercompany Transactions
This chapter covers the following topics: Importing Transactions
Importing Transactions
You can import intercompany transactions from external applications using the Open Interface tables and WebADI. See Importing Intercompany Using Open Interface, page 3-1 and Intercompany WebADI Integration, page 3-3
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.
Importing Intercompany Transactions 3-1
Columns specified Optional need not contain data. However, the transactions are rejected if the data fails the validation.
2.
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.
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 Source Group Description Specify the application source. Enter the Group ID.
Parameters Send Transactions
Description Enter Yes to send the transactions as initiator transactions and start the recipient workflow. Specify No if you want to print all the transactions in the report. Helps you to query, rectify and re-import rejected transactions.
Print Rejected Only
Debug
Successful transactions are purged from the interface tables. Related Topics Intercompany Open Interface Tables, page A-1
Importing Intercompany Transactions Using WebADI

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.
Oracle WebADI: Create Document Page

To import transactions, you must first create the spreadsheet document in Oracle WebADI: Create Document page and later upload the transactions. Create Spreadsheet Document The spreadsheet document created using WebADI has predefined formats for entering Intercompany transactions. To create a spreadsheet document:
1. 2. 3.
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
4.
5.
available in Intercompany.
6.
Review the selections and click Create Document.
On clicking Create Document, the spreadsheet application opens with the defined spreadsheet where you can enter transactions. Upload Transactions After entering the transactions, you must upload the transactions to Intercompany. To upload the transactions:
1.
Click Upload Journal on the WebADI menu and specify the upload parameters. The transactions are uploaded into the Intercompany Interface tables.
2.
Submit the Intercompany Open Interface program to import the transactions into Intercompany.
Related Topics WebADI Spreadsheets, Oracle Financial Consolidation Hub User's Guide
Purge Rejected Intercompany Transactions

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.
Purge Rejected Intercompany Transactions Execution Report

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".
4
Intercompany Reporting
This chapter covers the following topics: Reports
Reports
Advanced Global Intercompany System provides extensive reports that help you in reviewing and reconciling transactions reports. Intercompany reports are built using Oracle XML Publisher technology. Oracle XML Publisher enables you to easily change the layout and publishing format of the reports thus allowing you to customize the reports to suite your requirements. The reports available in Intercompany are: Oracle Intercompany Transaction Summary Report Oracle Intercompany Account Details Report Intercompany Reconciliation Report
Navigate to the Schedule Requests page to run the reports.

Note: For each parameter, the list of values displays the options
associated with the user running the report. If no option is selected, then the report is generated for all the options in the list of values.
Oracle Intercompany Transaction Summary Report

The Intercompany Transaction Summary report includes all appropriate transaction columns. This report provides information about intercompany transaction lines grouped by outbound and inbound transactions. You can customize this report for one or more intercompany organizations. Specifically, use this report to find if a period contains open transactions in it by listing the transactions for a particular batch or transaction status. The following table explains selected parameters of the report.
Intercompany Reporting 4-1
Parameter Recipient
Description The recipients you select represent the recipients for outbound transactions. If the batch type is outbound, the transaction status displays initiator transactions or vice versa. The invoicing rule for outbound and inbound transactions. Displays Receivables or Payables for outbound and inbound transactions respectively, if invoices are required. Otherwise, it is General Ledger. As invoice numbers are similar for initiator and recipient transactions, depending on the option selected for Batch Type, the initiator and recipient transactions, or both are displayed in the report.
Transaction Status
Destination
AR/AP Invoice Number
Oracle Intercompany Account Details Report

The Intercompany Account Details report provides information about accounting details (outbound and inbound transactions) of intercompany transactions. Outbound transaction accounts include initiator distribution and initiator receivables accounting. Inbound transaction accounts include recipient distribution and recipient payables accounting. The following table explains selected parameters of the report.
Parameter Transacting Legal Entity Description This field is displayed if the Initiator From and Initiator To are the same legal entity. Displays the primary or secondary ledger of the selected legal entity. This field is displayed if the Recipient From and Recipient To are the same legal entity. If Liability or Asset is selected, the report displays intercompany receivables accounts and intercompany payable accounts. If Expense or Revenue is selected, the report displays distribution accounts.
Transaction Ledger
Trading Partner Legal Entity
Account Type
Intercompany Reconciliation Report

Reconciliation is the process of ensuring an intercompany transaction is accounted in Receivables for the initiator legal entity and Payables for the recipient legal entity. The Intercompany reconciliation report enables you to check any discrepancies or missing transactions.
Tip: Setting up unique intercompany accounts for each relationship
between a transacting and trading legal entity simplifies the reconciliation.
To run the reconciliation report:

1.
Submit the concurrent request Intercompany Reconciliation Data Extract Program. This program gathers all the transactional data.
2.
Navigate to the Reconciliation tab and select the ID of the concurrent request that was run in step 1. Choose the template to display the results. Drill down using the links provided in the report for detailed information.
3. 4.
The following table explains selected parameters of the Intercompany Reconciliation Data Extract Program.
Parameter Transaction Ledger Transacting Legal Entity Transacting GL Period Description The ledger of the initiator organization. The legal entity of the initiator organization. The GL period in the transacting ledger for which the report is run. The ledger of the recipient organization. The legal entity of the initiator organization. GL period in the trading ledger. The currency in which the sum of the GL Balances must be displayed.
Trading Ledger Trading Legal Entity Trading GL Period Additional Currency
Intercompany Reporting 4-3
Parameter Conversion Type Conversion Date
Description This field is mandatory if Additional Currency is entered. If Additional Currency is entered and a conversion data is not entered, the default is the System date.
Related Topics
Using the Concurrent Manager to Generate Your Custom Output, Oracle XML Publisher User's Guide Running Reports and Programs, Oracle Applications User's Guide
A
This appendix covers the following topics: Open Interface Tables
Open Interface Tables

This appendix describes the tables and columns of Intercompany Open Interface tables.
FUN_INTERFACE_CONTROLS Table
The following table describes selected fields in the FUN_ INTERFACE_CONTROLS table.
Column Name Group_id Source Description Based on the sequence fun_interface_controls_s. Free text to identify the source of the external system from which records are imported.
Note: Source and Group_ID form the unique key.
Request_id Date_Processed
Updated by the Import process. Updated by the Import process.
FUN_INTERFACE_BATCHES Table
The following table describes selected fields in the FUN_INTERFACE_BATCHES table.
Intercompany Open Interface Tables A-1
Column Name Source
Description Enter text to identify the external system source from which records are imported. This value must match with the Source column in the fun_interface_controls table. Logical grouping of the batches. This value must match with the Group_id column in the fun_interface_controls table. Based on the sequence fun_trx_batches_s. Unique for an initiator. The ID of the intercompany organization that initiated the batch. You must provide either the initiator ID or the initiator name. The name of the party. You must provide either the initiator ID or the initiator name. The initiator legal entity. If you do not enter a value, the From_Le_id is derived from the initiator_id column by the Import process. The name of the initiator legal entity. If you do not enter a value, the From_Le_Name is derived from the initiator_id column by the Import process. If you do not enter a value, the From_Ledger_id is derived from the From_Le_Id by the Import process. Enter an amount to indicate the amount the batch total should be.
Group_id
Batch_id Batch_Number Initiator_id
Initiator_Name
From_Le_id
From_Le_Name
From_Ledger_Id
Control_Total
Note: This column is used as a placeholder and it is NOT

the total of all the transaction amounts in the batch.
Running_Total_Cr
The sum of all the transaction credit amounts in the batch.
Note: A batch must have all credits or all debit amounts. It

cannot have both.
A-2 Oracle Advanced Global Intercompany System User's Guide
Column Name Running_Total_Dr
Description The sum of all the transaction credit amounts in the batch.
Note: A batch must have all credits or all debit amounts. It

cannot have both.
Currency_Code
The batch currency. Transactions in a batch must be in the same currency. Enter the exchange rate if the batch is not in the currency specified by the initiator. The description that is passed to the general ledger or receivables of the initiator as the journal or invoice description. The transaction type of this batch. All transactions in a batch must be the same. You must enter a value for either the trx_type_id or trx_type_name or trx_type_code.
Exchange_Rate_Type
Description
Trx_Type_Id
Trx_Type_Name
Name of the transaction. You must enter a value for either the trx_type_id or trx_type_name or trx_type_code.
Trx_Type_Code
Transaction type code of this batch. All transactions in a batch must be of the same type. You must enter a value for either the trx_type_id or trx_type_name or trx_type_code.
Gl_Date Batch_Date Reject_Allow_Flag From_recurring_batch_id
The General Ledger date of the batch. The date the batch is entered. Indicates whether the transactions in this batch can be rejected. Used for transactions upgraded from Global Intercompany System. The import program populates the import status. The status is Accepted or Rejected.
Import_Status_Code
FUN_INTERFACE_HEADERS Table
The following table describes selected fields in the FUN_INTERFACE_HEADERS table.
Field Trx_id Trx_Number Recipient_id Description Based on the sequence FUN_TRX_HEADERS_S. Unique transaction number. The ID of the intercompany organization that is the recipient of this transaction. You must either provide the recipient_id or recipient_name. Recipient_Name The name of the party. You must either provide the recipient_id or recipient_name. To_Le_id The recipient legal entity. If you do not enter a value, the To_Le_id is derived from the Recipient_id by the Import process. The recipient ledger ID. If you do not enter a value, the To_Ledger_Id is derived from the To_Le_id by the Import process. The name of the recipient legal entity. The batch ID. Y indicates an invoice is required for the transaction. N indicates that the transaction must be sent to General Ledger. This field is validated and derived by the import process based on the setup. Used for transactions upgraded from the Global Intercompany System. Validates if the initiator is present in the same instance. Validates if the recipient is present in the same instance.
To_Ledger_Id
To_Le_Name Batch_id Invoicing_Rule_Flag
From_Recurring_Trx_Id
Initiator_Instance_Flag Recipient_Instance_Flag
A-4 Oracle Advanced Global Intercompany System User's Guide
Field Description
Description The description that is used for the recipient's General Ledger transactions and Payables invoices. The import program populates the import status. The status is Accepted or Rejected.
Import_Status_Code
FUN_INTERFACE_DIST_LINES Table
The following table describes selected fields in the FUN_INTERFACE_DIST_LINES table.
Field Trx_id Dist_id Party_id Party_Type_Flag Description The Trx_Id from fun_interface_headers. Based on the sequence FUN_INTERFACE_DIST_LINES_S. The initiator or recipient ID. The initiator distributions will have party_type_flag as I and the recipient distributions will have party_type_flag as R. Must have the value L. The import program populates the import status. The status is Accepted or Rejected.
Dist_Type_Flag Import_Status_Code
Note: The initiator distributions will have party_type_flag as I, and the
dist_type_flag as L and the recipient distributions will have party_type_flag as R, and the dist_type_flag as L.

Index
A
AGIS Initiator Intercompany Distribution Account, 1-13 AGIS Recipient Distribution Account, 1-13 assign organizations, 1-7 association customer, 1-9, 1-10 supplier, 1-9, 1-10 derive approvers, 1-12 Detail, 1-5 distribution account, 1-13 distributions account default, 1-13
G
GL Journal Import concurrent program, 2-5
B
Balancing Details Tab, 1-4 Credit Account, 1-4 Credit Balancing Segment, 1-4 Debit Account, 1-4 Debit Balancing Segment, 1-4 batch creation, 2-2 batch numbering, 1-11 Bill-to Location, 1-10
I
Intercompany and Intracompany Balancing Overview, 1-1 Intercompany batch number, 2-4 Intercompany Calendar, 1-12 Intercompany super user, 1-7 Intercompany User, 1-7 Invoicing, 1-8
M C
conversion rate type, 1-12 Customer Account, 1-10 customer account location, 1-10 Customer Name, 1-10 Manually Entered Clearing Balancing Segment Value, 1-5 minimum transaction amount, 1-11 minimum transaction amount currency, 1-12
O D
Default Clearing Balancing Segment Value, 1-5 Default rule Initiator Intercompany Transaction, 1-12 Recipient Intercompany Transaction, 1-12 open interface tables, 3-1 Options Tab, 1-4 Clearing Balancing Segment Value Usage, 1-5 Default Options, 1-5 Level of Summarization, 1-4
Index-1
organization initiator, 1-10 recipient, 1-10
P
Page Home, 2-1 Setup, 1-2 Transaction, 2-1 Payables Open Interface Program, 2-8 Pay-to Location, 1-10 periods close, 1-8 open transactions, 1-8 open, 1-8 period status, 1-8
R
Receivables AutoInvoice Program, 2-8 Receivables Memo Line, 1-9 Receivables Transaction Type, 1-9 report Intercompany Account Details, 4-2 Intercompany Reconciliation, 4-3 Intercompany Transaction Summary, 4-1
System Options, 1-11 Transaction Types, 1-7 trading partner, 1-10 Trading Partner Balancing Segment Value, 1-3 Trading Partner Ledger, 1-2 Trading Partner Legal Entity, 1-2 Transacting Balancing Segment Value, 1-2 Transacting Ledger, 1-2 Transacting Legal Entity, 1-2 transaction currency, 1-11 transaction flow inbound, 2-1 outbound, 2-1 transactions access, 1-7 allow recipients to reject, 1-12 transfer to General Ledger, 1-12 Payables, 1-12 Receivables, 1-12 Transaction Types, 1-7
U
Use for All Journals, 1-5 Use for Balancing, 1-3 Use for Many-to-Many Journals Only, 1-5 Using Default Rule, 1-6
S
SLA responsibility, 1-13 Subledger Accounting Transaction Account Builder, 1-13 Account Derivation Rules, 1-13 Transaction Account Definition, 1-13 Transaction Account Type, 1-13 Summary Net, 1-5 Supplier Account, 1-10 Supplier Name, 1-10 supplier site, 1-10
V
View Reciprocal Accounts, 1-3
W
WebADI, 3-1 workflow initiator, 2-5 recipient, 2-5
T
Tab Accounting, 1-2 Invoicing Options, 1-9 Organizations, 1-6 Periods, 1-8 Security, 1-7
Index-2

AGIS User Guide

Uploaded by

Document Informationclick to expand document information

Document Informationclick to expand document information

Copyright:

Available Formats

AGIS User Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AGIS User Guide

Uploaded by

Copyright:

Available Formats

Oracle Advanced Global Intercompany System

User's Guide Release 12.1

Send Us Your Comments Preface 1 Intercompany Setup

Intercompany Transaction Processing

Importing Intercompany Transactions

Intercompany Open Interface Tables

Deaf/Hard of Hearing Access to Oracle Support Services

Accessibility of Code Examples in Documentation

Accessibility of Links to External Web Sites in Documentation

Related Information Sources

Do Not Use Database Tools to Modify Oracle E-Business Suite Data

Intercompany Setup 1-1

Intercompany Accounting Pages

Intercompany Accounts Pages

1-2 Oracle Advanced Global Intercompany System User's Guide

Trading Partner Balancing Segment Value

Balancing Accounts Search Page

Create Intracompany Balancing Rules Page

Intercompany Setup 1-3

1-4 Oracle Advanced Global Intercompany System User's Guide

Intercompany Setup 1-5

Intercompany Organizations Pages

View Intercompany Organization Page

1-6 Oracle Advanced Global Intercompany System User's Guide

Intercompany Security Pages

Use the Security tab to assign a user to an organization.

Intercompany Organization Assignments Page

Intercompany Transaction Types Pages

Intercompany Setup 1-7

sufficient for your operations.

Creating Intercompany Transaction Types Page

Select Required to specify transaction types that require recipients' approval.

Intercompany Periods Pages

per transaction type.

Control Period Statuses Page

Review Open Transactions Page

1-8 Oracle Advanced Global Intercompany System User's Guide

Intercompany Invoicing Options Pages

invoices, you need not use the Invoicing Options tab.

Receivables Assignments Page

Customer Supplier Associations

Intercompany Setup 1-9

Selected Fields in Customer and Supplier Association Page Supplier Site

The supplier initiating the transaction.

1-10 Oracle Advanced Global Intercompany System User's Guide

The customer receiving the transaction.

Intercompany System Options

progress. It affects new transactions only.

Intercompany Batch Numbering

Intercompany Transaction Currency

Minimum Transaction Amount

Intercompany Setup 1-11

set the transaction currency.

Minimum Transaction Amount Currency

Intercompany Conversion Rate Type

Allow Recipients to Reject Transactions

Transfer Transactions to General Ledger

Transferring Transactions to Payables and Receivables