Setup For Advanced Global Lntercompany System AGIS in Release 12 v2

Setup for Advanced Global
lntercompany System (AGIS)

in Release 12
Improved and republished by: Andreea Voicu
March 25, 2020 | Version 1.01

March 2007 | Version 1 – author: Pradeep Khot
Copyright © 2020, Oracle and/or its affiliates
Confidential: Public
PURPOSE STATEMENT
This document provides an overview of features and enhancements included in release R12. It is intended solely to help you
assess the business benefits of upgrading to R12 and to plan your I.T. projects.
DISCLAIMER
This document in any form, software or printed matter, contains proprietary information that is the exclusive property of
Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle software
license and service agreement, which has been executed and with which you agree to comply. This document and
information contained herein may not be disclosed, copied, reproduced or distributed to anyone outside Oracle without
prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any
contractual agreement with Oracle or its subsidiaries or affiliates.
This document is for informational purposes only and is intended solely to assist you in planning for the implementation
and upgrade of the product features described. It is not a commitment to deliver any material, code, or functionality, and
should not be relied upon in making purchasing decisions. The development, release, and timing of any features or
functionality described in this document remains at the sole discretion of Oracle.
Due to the nature of the product architecture, it may not be possible to safely include all features described in this document
without risking significant destabilization of the code.
DISCLAIMERS FOR PRE-RELEASE, PRE-GA PRODUCTS
The revenue recognition disclaimer on this page is required for any white paper that addresses future functionality or for
products that are not yet generally available (GA). If you are unsure whether your statement of direction needs the
disclaimer, read the revenue recognition policy. If you have further questions about your content and the disclaimer
requirements, e-mail REVREC_US@oracle.com.
The testing disclaimer in the copyright section on the last page (highlighted in yellow) is provided by the FCC for hardware
products. It must appear in the copyright section for all pre-release, pre-GA hardware products. Be sure to remove the
yellow highlighting before publishing. When the product becomes GA, update your collateral by removing the disclaimer
from the copyright section. If your product is already GA or if you are writing about a software product, delete the disclaimer
from the copyright section.
Important: If your product is not GA, then you cannot include any regulatory compliance information in the statement of
direction. Regulatory compliance information may be included for GA products only if you have completed all required
safety and emissions testing, and you have received the certificates issued by the testing organization.
1 WHITEPAPER | Document Setup for Advanced Global Intercompany (AGIS) in Release 12 (R12) |Version 1.00
Copyright © 2020, Oracle and/or its affiliates | Confidential: Public
Table of Contents
EXECUTIVE OVERVIEW ................................................................................................3
INTRODUCTION ............................................................................................................3
SCOPE............................................................................................................................3
OVERVIEW ................................................................................................................... 4
SCENARIO: DATA ELEMENTS .................................................................................... 5
PART ONE - AGIS SETUPS .......................................................................................... 6
ENVIRONMENTAL SETUP ...................................................................................................................................8
Defining Employees ....................................................................................................................................8
Define Users................................................................................................................................................. 11
Define Responsibilities ............................................................................................................................. 14
GENERAL LEDGER SETUP ................................................................................................................................ 16
Ledger’s Definition and Setups .............................................................................................................. 16
Intracompany Balancing Rules.............................................................................................................. 20
Intercompany Accounts ........................................................................................................................... 21
Relationships .............................................................................................................................................. 22
RECEIVABLES AND PAYABLES SETUP ......................................................................................................... 26
Receivables Setups................................................................................................................................... 26
Payables Setups ......................................................................................................................................... 31
AGIS SETUP........................................................................................................................................................... 33
Organizations ............................................................................................................................................ 34
Security and Assignments...................................................................................................................... 36
Transaction Types .................................................................................................................................... 40
System Options .......................................................................................................................................... 41
Receivables Assignments ....................................................................................................................... 42
Customer and Supplier Associations................................................................................................... 44
PART TWO - AGIS TRANSACTION PROCESSING .................................................... 54

PROCESSING TRANSACTIONS ........................................................................................................................55
Transaction Initiation............................................................................................................................... 56
Recipient Side ............................................................................................................................................ 66
Receivables – Processing Invoices........................................................................................................ 78
Payables – Processing Invoces .............................................................................................................. 95
PART THREE - AGIS REPORTS AND RECONCILIATION ......................................... 110

AGIS REPORTS AND RECONCILIATION ........................................................................................................ 111
TECHNICAL DETAILS .............................................................................................. 140

RELEVANT HTML PAGES .................................................................................................................................141
RELEVANT TABLES IN AGIS ........................................................................................................................... 142
USEFUL QUERIES .............................................................................................................................................. 143
OTHER FEATURES ................................................................................................... 144

WORKFLOW AND APPROVALS MANAGEMENT SYSTEM (AME) INTEGRATION ............................. 145
AGIS ACCOUNTING........................................................................................................................................... 147
TRANSACTIONS ACCOUNTS DERIVATION (TAD) FOR AGIS .................................................................148
KNOWN ISSUES ........................................................................................................149
EXECUTIVE OVERVIEW
The purpose of this document is to provide users an overview of Advanced Global Intercompany (AGIS) setup in Release 12.
This document is structured in three parts:
1. Setup - discusses the details of the setups required for usage of AGIS functionality
2. Transaction Processing - details about the processing of the transactions
3. Reports and Reconciliations - reports available in AGIS and reconciliation features
Find further other features, known issues, technical details related to AGIS and integrated products.
INTRODUCTION
AGIS is a vast improvement of the Global lntercompany System (GIS) functionality in General Ledger Release 11i.
- Interaction with subledgers facilitating invoicing using Receivables and Payables

- A brand new, ingenious and robust security model
- Facilitates transaction processing between different Legal Entities, under one or more Ledgers
- Completely operated from SSWA Pages (Web Pages) without any forms
SCOPE
The scope of this document is to help in understanding what are the setups required for using the AGIS functionality, how
the transactions are processed in AGIS, what are the reports available in AGIS.
The information provided in this whitepaper is relevant to Oracle Applications Release 12.
OVERVIEW
Part One on setups offers a broad view of how AGIS is setup in R12:
The setups are divided into four main parts:
1. Environment Setups
2. General Ledger (GL) Setups
3. Receivables (AR) and Payables (AP) Setups
4. Advanced Global lntercompany (AGIS) Setups
Part Two on Transaction Processing discusses the steps those are required for processing a transaction in AGIS
Transaction Processing in AGIS:

The summary of steps those are used for AGIS transaction processing is as follows:
1. Initiation of a transaction by an intercompany organization

2. Completion of accounting from the Initiator side
3. Completion of the accounting by the Recipient side
4. Approval of the transaction by the Recipient
If the Invoicing is opted for in transaction type setups, then,

5. Processing of the Invoice from Receivables (for the Initiator Subsidiary side)
6. Processing of the Invoice in Payables (for the Recipient Subsidiary side)
Part Three discusses the reports in AGIS and reconciliation feature in AGIS
Reports and Reconciliations in AGIS:
- Standard Reports available in AGIS
- Reconciliation feature in AGIS
Find further other features, known issues, technical details related to AGIS and integrated products.
SCENARIO: DATA ELEMENTS
The setup steps are explained in the subsequent sections, from start to finish.
The details of the example that is used in this session assume as follows:
- Initiator Subsidiary: ‘ACE Singapore lntercompany Organization‘.

This organization is a part of the ‘ACE Singapore Legal Entity‘. The legal entity uses only ‘01’ balancing segment value. The
user that is having access to the lnitiator Subsidiary is called 'ACE_S'.
- Recipient Subsidiary:
‘ACE Japan IC Org‘. This is a part of ‘ACE Japan Legal Entity‘. The legal entity uses only '02‘ balancing segment value. The
user that is having access to the Recipient Subsidiary is called ‘ACE_J’.
Note that in this example both the Legal Entity are attached to the same ledger called 'ACE Ledger Good‘. Also two
intercompany organizations from part of a single Security Profile.
That means the Payables and Receivables transactions can be handled from a single Payables and Receivables responsibility
each. Both the users access the same responsibilities for Payables and Receivables.
PART ONE - AGIS SETUPS
The information provided is designed to help get a good understanding of AGIS functionality.
It is divided as follows:
1. Setup
2. Transactions
3. Reports and Reconciliation
Setup has been divided into four parts:

1. Environmental Setup
2. General Ledger setup
3. Receivables and Payables Setup
4. AGIS Setup
Assumptions:
One Ledger called ACE Ledger.
Two Legal Entities (LE’s) under that ledger, called ACE Japan and ACE Singapore.
Two Operating Units-ACE Japan Operating Unit and ACE Singapore Operating Unit respectively.
Note that setting up Receivables responsibility is mandatory for using the invoicing functionality. Also for setting up
Receivables, it is mandatory that Inventory Organizations are created as well.
The transactions in this example are assumed to be happening from ‘ACE Singapore' to ‘ACE Japan‘.
Since this is between two LE’s, it qualifies for being an AGIS transaction.
For these two entities create two Employees : ACE, Japan and ACE, Singapore
Two Users: ACE_S and ACE_J
Create responsibility for Receivables.
As mentioned above, in order to use invoicing options, setting up of the Receivables side is mandatory. Use of Operating
Units will also become mandatory.
In AGIS, also setup two lntercompany Organizations called:
1. ACE Singapore lntercompany Organization and

2. ACE Japan IC Org.
All these setups are explained henceforth with the help of step-by-step screenshots with navigations and explanations.
ENVIRONMENTAL SETUP
Defining Employees
This starts with defining Employees in HRMS. These employee definitions are used later on in Security Setup for AGIS.
Navigation: Human Resources Responsibility: People > Enter and Maintain
Define an employee called ‘ACE, Singapore‘. This person will be attached to the user initiating the transaction in AGIS. In this
example the transaction gets initiated by ACE Singapore.
Note that when a transaction is created by ACE Singapore to be transferred to ACE Japan, ‘ACE Singapore‘ is lnitiator of
transaction and ‘ACE Japan is Receipient of transaction.
Define employee for the recipient intercompany organization (ACE Japan) as well:
Define Users
Navigation: System Administrator Responsibility: Security > User> Define
Created user named 'ACE_S'.
Note the Person attached to this user (ACE, Singapore) is now the contact person for Initiator Organization.
Notice the responsibilities attached to the user:
1. lntercompany Super User

2. lntercompany User
These are two seeded responsibilities for AGIS. ‘Intercomany Super User’ responsibility allows to create all the AGIS setups
and transactions as well.
’lntercompany User‘ Responsibility is used to process transactions only, with no access to setups.
Very important: the user name should not include spaces. Also the email address must exist for notifications to be sent.
Make sure you define the user correctly.
Created the new user named 'ACE_J'.
This user is assigned to employee 'ACE.Japan'. This user is the contact for the recipient organization (ACE Japan).
Define Responsibilities
Create responsibility for General Ledger:
Create Responsibility for Receivables as well.
Note that for using the invoicing feature in AGIS it is mandatory that the Receivables responsibility has been created and
setup correctly, for both the Operating Units (OUs). Unless the Receivables is set up for both OUs, the AGIS transaction
processing will not go through at all.
The required setups to be done from AR side have been explained later on.
Now, Environmental Setups are ready.
GENERAL LEDGER SETUP
Ledger’s Definition and Setups
Next step is to create the Ledger which will be used in AGIS.

If relevant ledger setups are already in place, then these steps can be skipped.
The Ledger definition is done through Accounting Setup Manager (ASM) in GL responsibility. The relevant setups for Ledger
definition is explained in the next pages.
Navigation: General Ledger Responsibility: Setup > Financials > Accounting Setup Manager > Accounting Setups
Ensure that the relevant Legal Entities are assigned to the Ledger.
In this example the relevant Legal Entities are
1. ACE Japan Legal Entity and
2. ACE Singapore Legal Entity
The name of the ledger is ACE Ledger good. Note that the Balancing Segment Values have been assigned as and when
Legal Entities were created.
Operating Units
Get into the Operating Units part in ASM to ensure that the relevant Operating Units are created and assigned as well.
Note that for using the invoicing functionality in AGIS, setting up of the Operating Units is mandatory.
In the current example, two Operating Units have been created and added:
1. ACE Singapore Operating Unit and
2. ACE Japan Operating Unit
So what is covered so far is assignment of Legal Entities and Operating Units to Ledger.
Intracompany Balancing Rules
The next step would be to define lntra-company Balancing Rules. Option to define intra-company rules would be visible only
if lntracompany Balancing option is enabled for the concerned Ledger. GL now provides flexibility to define the lntracompany
Balancing Rules, Legal Entities-wise. So one can have different lntracompany Balancing Rules for different Legal Entities.
Note: This option, lntracompany balancing was known as lntercompany Balancing in Release 11i.
Click on ‘Define Rules’ button for ‘ACE Singapore Legal Entity‘ and enter the rules for this Legal Entity.
Intercompany Accounts
Further create the relationship setups and accounts definition for the Intercompany Accounts.
Here, relationships between multiple entities is defined.
Relationships
Under Intercompany Accounts link, there is a link called ‘Define Relationships’, where one can create the relationships
between various Legal Entities. This is the place where GL is notified of ‘from where’ and ‘to where’ the transactions are
going to flow.
Define the relationships both ways, for the ACE Singapore Legal Entity to ACE Japan Legal Entity and from ACE Japan Legal
Entity to ACE Singapore Legal Entity.
Define the Relationship here. There are two parties in a relationship.
The first one is Transacting Entity and the second one is Trading Partner Entity.
So in the example,
Transacting Legal Entity is ACE Singapore Legal Entity
Trading Partner Legal Entity is ACE Japan Legal Entity
Note that the relationship can be defined between individual/multiple Balancing Segment Values of the Transacting and
Trading entities.
There is nothing defined for the ACE Japan Legal Entity, since the transaction flow is from ACE Singapore to ACE Japan only
and not the other way round.
So far, the following setups have been completed for the ledger:
1] Ledger Setup
2] Subledger Accounting Setups
3] Operating Unit Setup
4] lntracompany Balancing Rules setup
5] lntercompany Accounts setup
Note that the Balancing Segment Value assignments can be done at the Legal Entity Level or at the Ledger Level depending
on the business requirement.
This completes the second part of the setup, GL setup.

These steps were performed:
1] Ledger Creation
2] Legal Entities creation, Balancing Segment Value assignment
3] Assignment of Legal Entities to the Ledger
3] Operating Units creation and assignment to the Ledger
4] Definition of lntracompany Accounting Rules
5| Definition or lntercompany Relationship definitions and respective accounts definition
These are all the mandatory setups to be done from GL side (from Accounting Setup Manager).
RECEIVABLES AND PAYABLES SETUP
Receivables Setups
The next setup takes place in Receivables. Without Receivables being setup, AGIS will not work properly for invoicing.
Log on to Receivables Responsibility that was created initially and assigned to the User setting up the AGIS.
This is a brief explanation on how Receivables is setup in R12 (rather similar to what it was in Release 11i).
1] Pre-requisite for setting up Receivables is the existence of lnventory Organization which is linked to the Operating Unit that
will be used in Receivables. So ensure that for the Operating Units, Inventory Organizations are defined. The relevant details
like Accounting Information and Receiving Information is required to be filled in for the Inventory Organization Classification
in organization definition form.
Navigation: HR responsibility: Work Structures > Organization > Description
2] Next step is the creation of Security Profiles which are defined at the following:
Navigation: HR responsibility: Security > Profile
3] After defining the Security Profile, run the ‘Security List Maintenance‘ program from the HR responsibility.
4] Setup the following profile options at the Receivables Responsibility Level:

- MO: Operating Unit
- MO: Default Operating Unit
- MO: Security Profile
Note: if MO: Security Profile is defined, then MO: Operating Unit profile becomes redundant.
Navigation: System Administrator Responsibility: Profile > System
5] Add the Order Management menu, (Menu name ONT_SUPER_USER) to the receivables menu for ease of use, there are
some important setups in that menu as well.
6] Go to the Parameters Values form, Query for both the Operating Units and ensure that the Item Validation Organization is
entered.
This LOV does not show anything if the Inventory Organization is not setup.
Navigation: Receivables Responsibility: OM > Setup> System Parameters > Values
7] Now complete the System Options for Receivables. Note that this is a crucial step for AGIS. If this is not done for any of
the participating Operating Units then the setup can not be completed at all in AGIS.
Navigation: Setup > System > System Options
8] From the System Administrator Responsibility run the request ‘Replicate Seed Data‘; this needs to be run for the
Operating Units individually.
Navigation: System Administrator: View > Requests > Submit Single Request
Ensure that System Options for Receivables have been completed for all the operating units to be used in AGIS.
Navigation: Receivables Responsibility: Setup > System > System Options
Note here that for both the operating units to be used in the AGIS example, the ‘System Options Defined‘ column shows as
‘Yes’. This confirms that the required setup is completed from Receivables side.
Now login back to the Receivables responsibility and check in the transactions form if the LOV appears correctly for the
operating units or not. If the form is not showing any error and the ‘Batch Sources‘ LOV is appearing with the OU name(s)
that means the responsibility has been setup correctly.
Navigation: Receivables Responsibility: Transactions > Transactions
Note that here both the OUs are appearing in the LOV since the security profile has been set like that. User can always have
one OU - one responsibility kind of setup as well.
Payables Setups
In a similar way, Payables needs to be setup too. The recepient subsidiary will have this invoice transferred to Payables.
Hence note the following brief explanation of how Payables is setup in R12 (rather similar to Release 11i).
1] Create a responsibility for Payables and assign this responsibility to the user
Navigation: System Administrator Responsibility: Security > Responsibility
Navigation: System Administrator Responsibility: Security > User
2] Note the requirement to create a security profile and set the same profile options as set for Receivables. The security
profiles are defined at the following navigation.
Navigation: HR responsibility: Security > Profile
3] After definition of Security Profile, run the ‘Security List Maintenance‘ program from the HR responsibility itself.
4] Setup following profile options at the Payables Responsibility Level.

- MO: Operating Unit
- MO: Default Operating Unit
- MO: Security Profile
Navigation: System Administrator Responsibility: Profile > System
5] Once this is done, login back to the Payables new responsibility. Now setup the Financial Options and Payables Options.
Navigation: Payables Responsibility: Setup -> Options -> Financial Options
Navigation: Payables Responsibility: Setup -> Options -> Payables Options
Navigation: Payables Responsibility: Setup -> Options -> Payables System Setup
Note that while setting up the Financial Options, there is a LOV for OU that pops up. This will show only the relevant OUs as
per the Security Profile that was setup in step 4. Select the OU from the LOV and click on New, then complete the form details.
This is required to be done for all the OUs for which user intends to use the Payables Responsibility (in this example twice,
once for Japan and once for Singapore).
The same applies to Payables Options. Select the OU from LOV and click on Find and complete all the tabs in the form.
6] Now navigate to the Invoice Workbench and see that the LOV for OU is appearing correctly. It should only show relevant
information.
Further define a supplier and ensure that this OU(s) is/are attached to the new supplier as Pay Site(s), otherwise this new
supplier may not appear in invoice workbench at all.
So far, the following setup steps have been completed:
A. Environment Setup
B. GL Setups (Accounting Setup Manager Setups)

1. Ledger Creation
2. Legal Entities creation, Balancing Segment value assignment
3. Assignment of LegaI Entities to the Ledger
4. Operating Units creation and assignment to the Ledger
5. Definition of Intracompany Accounting Rules
6. Definition of lntercompany Relationship definitions and respective account definition
C. Receivables and Payables Responsibility Setups

Further continue with AGIS Setup.
AGIS SETUP
The responsibity to be used for definding AGIS Setup is ‘lntercompany Super User’ Responsibility.
Organizations
The first step is Organizations definition. These are the organizations that will be used by AGIS.
Navigation: lntercompany Super User: Setup > Organizations
Create two organizations which are to be used in transactions processing in AGIS.
Note that the Enabled Flag for these organizations should be ‘Yes’. This flag indicates that the organization has been enabled
for Intercompany transactions. Whitout this, processing of the transactions in those organizations, through AGIS, is not
possible.
First Organization that is created is called ‘ACE Japan IC Org’
The second organization that is created is called ‘ACE Singapore IC Org’
Security and Assignments
Security definition refers to which user/person will have access to which and how many Intercompany Organizations.
Navigation: Intercompany Super User Responsibility: Setup > Security
See the LOV that appears for the field Person Name.
Notice that the User Names and Person names as per definition in the Users form in System Administrator is appearing here.
This is how the assignment is done.
Query the user ACE_J and create an assignment for Intercompany Organization ‘ACE Japan IC Org’:
Note:
At least one user for both the Initiator and Recipient organization has to have the options 'Send Approval Notification' and
'Access to Transactions' checked in order for the batches to be approved.
On the same lines, for the user ‘ACE_S’, access to ‘ACE Singapore IC Org’ is given.
Transaction Types
Next step is creation of Transaction Type(s). Note that if invoices are required to be generated for the AGIS transaction, this is
defined here. If the ‘invoicing’ is set to 'Required‘ then Receivables and Payables setups are Mandatory for invoicing purposes.
Navigation: Intercompany Super User: Setup > Transaction Type
System Options
Navigation: lntercompany Super User: Setup > System Options
Note that if you intend to use separate calendar in AGIS and not the same one as used in GL, then you can define this here.
If a calendar is defined in System Options, then the period statuses can be controlled based on Transaction Types as well.
The period opening and closing is done in Periods Tab.
Receivables Assignments
The next step is Invoicing Options with a menu structured as:
1] Receivables Assignments
2] Customer and Supplier Associations
Navigation: Intercompany Super User: Setup > Invoicing Options
Example setup for the Receivables Assignment:
Operating Unit: ACE Singapore Operating Unit.
Notice the Receivables Transaction Type and Receivables Memo lines can be linked only if Receivables setups are complete.
If those setups are not complete then the LOV will not appear. The values appearing there ‘lntercompany’ and ‘Global
lntercompany’ respectively are new seeded values in Receivables. These have been specifically seeded in Receivables for AGIS.
Customer and Supplier Associations
Next step is definition of Customer and Supplier Associations. There are two tabs in the setup.
1] Customer / Supplier Associations tab to define the associations
2] Trading Partners tab to review the earlier created associations
Navigation: Intercompany Super User : Setup > Invoicing Options
Click on the ‘Create Customer Association' to define a relationship.
An example of how a relationship is defined:
The top portion shows the From entity (ln this case it is Singapore) and the bottom portion shows the complete list to select
from; in this case we select Japan.
The second step in the creation of customer association is selection of the ‘Customer’ and entering a 'Bill to Site’ for the
customer. Note that both are Mandatory.
Once the association is created, there is a message that appears at the top of the screen 'Customer Association was saved
successfully’ and at the end of the screen you can see and query the new customer association that was just now created.
In the same manner, relationship from Japan to Singapore is also defined.
Remember that when the ‘Bill to Site' field is entered, the same site name can not be used over and over again. If the same
site name is used then the above error message appears, ‘Location already exists for this business purpose and customer‘.
Enter a new value for the 'Bill to Site’ and click on 'Finish'.
At the end of the Customer Association creation, the following is what appears on the screen.
These 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.
In the same manner the Supplier relationship also has to be created since the transaction is going to be received by ACE
Japan from ACE Singapore.
Now that the relationships have been defined, query them in the Trading Partners tab and confirm your setups:
Notice that ‘Usage’ shows as ‘Initiator’ for the ACE Singapore Intercompany Organization:
Now everything is set for entering transactions in AGIS.
Summary of the AGIS Setup steps:
1. Environmental Setups
a. Employee Definition
b. User Definition
c. GL and AR responsibility definition and assignment to the users
2. GL Setups (Accounting Setup Manager Setups)

a. Ledger Creation
b. Legal Entities creation, Balancing Segment Value assignment
c. Assignment of Legal Entities to the Ledger
d. Operating Units creation and assignment to the Ledger
e. Definition of Intracompany Accounting Rules
f. Definition of lntercompany Relationship definitions and respective account definition.
3. Receivables and Payables Responsibility Setups
4. AGIS Setups
a. Organization Creation
b. Security Setup for users
c. Transaction Type creation
d. Period Control (Optional)
e. Invoicing Options - Receivables Assignments
f. Invoicing Options – Customer/Supplier Association Definition
g. Defining System Options
PART TWO - AGIS TRANSACTION PROCESSING
PROCESSING TRANSACTIONS
Further let’s see how to process an AGIS transaction. As mentioned previously, an AGIS transaction is basically a transaction
between two separate Legal Entities.
The summary of steps used for AGIS transaction processing is as follows:
1] Initiation of a transaction by an intercompany organization
2] Completion of accounting from the Initiator side
3] Completion of the accounting by the Recipient side
4] Approval of the transaction by the Recipient
lf the Invoicing is opted for, in transaction type setups, then,

5] Processing of the Invoice from Receivables (for the Initiator Subsidiary side)
6] Processing of the Invoice in Payables (for the Recipient Subsidiary side)
At this stage, the AGIS part of the transaction processing finishes. The next step would be the accounting for those invoices
and transferring of the invoices to General Ledger.
Restating, the details of the example that is used in this whitepaper are:
- Initiator Subsidiary- ‘ACE Singapore Intercompany Organization‘. This organization is a part of the ‘ACE Singapore
Legal Entity‘. This Legal Entity uses only '01 ' balancing segment value. The user that is having access to the Initiator
Subsidiary is calledd 'ACE_S'.
- Recipient Subsidiary- 'ACE Japan IC Org‘. This is a part of 'ACE Japan Legal Entity‘. This Legal Entity uses only ‘02’
balancing segment value. The user that is having access to the Recipient Subsidiary is called 'ACE_J'.
Note that in this example both the Legal Entity are attached to the same ledger called ‘ACE Ledger’. Also two
intercompany organizations form part of a single Security Profile. So that means the Payables and Receivables part
of the transactions can be handled from a single Payables and Receivables responsibility each. Both the users
access the same responsibilities for Payables and Receivables.
Note also that for this example, Transfer transactions to subledgers is defined to Online Mode.
Transaction Initiation
The first step for processing of transaction in AGIS is Initiation of the transaction.
ln the example the transaction is initiated by the User ACE_S - who is having access to the Initiator Subsidiary named ‘ACE
Singapore lntercompany Organization’.
AGIS Transaction is entered using lntercompany User or lntercompany Super User Responsibility.
Navigation: lntercompany (Super) User: Transaction > Outbound
Transactions Page in the Advanced Global lntercompany System is divided into two pans. Outbound and Inbound.
The Initiator Subsidiary Organization uses the Outbound Part.

The Recipient Subsidiary Organization uses Inbound Part.
This is the query and create outbound transactions page.
Click on ‘Create’ button to initiate an intercompany transaction.
Create button will open a data entry page. This is very similar to Enter Journals form.
This is the Header Part of the Outbound Transactions Page
lmportant fields on this page are:

- Transaction Type
- lnitiator
- GL Date
- Currency
This is the Transactions portion of the Outbound Transactions Page.
List of the Recipient along with the Debit and/or Credit is entered here. One can initiate a transaction to more that
one recipient Subsidiary Organization by entering in different Transaction Number.
Once the Recipient Name and Debit/Credit is entered, click on ‘Continue’.
That Opens the Create Batch: Distributions page. This page is used to complete the accounting from the
Initiator side. Select the Transactions Line for which the accounting effect is to be given and then click on
‘Add Lines’ button.
Enter the Code Combination and debit and/or credit effects from the Initiator Side. This will complete the accounting
from the Initiator side. Once this is done, click on 'Submit' button.
Completion of transaction will return to the Transactions Outbound main page. Here query the transaction that was just
entered and review the status of the transaction.
Query the batch number 68, observe the details and status.
When the transaction is just entered and the Initiator side accounting part is not completed, the status of the batch remains
as ‘New’.
With this the Initiation part of the AGIS transaction is complete. Now go to the Recipient side to complete the accounting
part too.
Recipient Side
In this example, the recipient user is called ACE_J and the recipient organization is called ‘ACE Japan IC Org‘.
The processing of the AGIS transaction in the Recipient Organization is done at:
Navigation: lntercompany (Super) User: Transaction > Inbound
Review the status of the transaction, it appears as 'Received’. This indicates that the transaction has just been received from
some other lntercompany Organization.
Click on ‘Update Transaction‘ link on the line to complete the Recipient accounting.
This will open the Transaction Information page and it will allow the Recipient accounting to be completed, the same way
Initiator accounting was done.
Click on ‘Add Line’ button at the bottom of the screen to add the Recipient accounting details.
Once the Code Combination and Debit/Credit details are entered, the transaction can be approved by clicking on 'Approve'
button. Note that for this transaction type the Approval is set to ‘Required’ hence the approval has to be done manually.
Otherwise the transaction will be automatically approved on completion of the Recipient Accounting part.
Once the transaction is approved by the Recipient lntercompany Organization after entering the Recipient side accounting,
the status of the transaction changes to ‘Transferred to Receivables‘
Once the status has changed to ‘Transferred to Receivables‘, the invoice information gets populated in table
RA_INTERFACE_LINES_ALL.
Notice that the BATCH_SOURCE_NAME is ‘Global Intercompany'.
The CUST_TRX_TYPE_NAME is 'Intercompany'
The Transaction Type setup shows that the invoicing has been set to ‘Required‘, that means the Invoices will get created in
Payables and Receivables.
Manual Approval is set to ‘Required’ that means the transactions will have to be approved explicitly and will not get
approved automatically.
Note that if in the System Options area ‘Transfer’ is set to Online, there is no need to run ‘Transfer to Payables’ and ‘Transfer
to Receivables’ programs. Then instead of using concurrent requests the workflow will be used to populate the interface tables.
lf this option is set to ‘Batch’ then the data will be transferred to Payables and Receivables interfaces on running of these
requests only.
Receivables – Processing Invoices
Now the steps in the AGIS are completed. The next thing to do is to process the invoices in Receivables.
For that go to Receivables responsibility.
Navigation: Receivables Responsibility: Interfaces > Autolnvoice
This triggers the 'AutoInvoice Master Program‘. It is the main program for importing the data from the Receivables Interface
table (RA_INTERFACE_LINES_ALL) and creates an invoice.
The important mandatory parameters for this request are:
1. Organization - ‘ACE Singapore Operating Unit‘ (OU)

2. Invoice Source - ‘Global intercompany'. This would always remain same, it is a seeded value
3. Default Date
Note that the AutoInvoice Master Program triggers ‘AutoInvoice Import Program’:
Once the requests are completed normally then review the output of the Autolnvoice Import Program.
This output file gives the information needed on the details and number of invoices processed in the run.
Selected Interface Line: 1 and successfully processed.

Interface Distributions: 2 rows selected and successfully processed.
Scroll down in the AutoInvoice Execution Report and the number of invoices processed are shown, along with the numer of
interface lines and number of distributions lines.
Once the program has completed normally and Execution Report shows that the invoices have been imported, query the
invoice in the Transactions form.
Navigation: Receivables Responsibility: Transactions > Transactions
Note that once the AutoInvoice has completed successfully the line in the FUN_TRX_HEADERS table is updated and it also
raises a business event oracle.apps.ar.batch.AutoInvoice.run which is used by Payables to create interface lines in Payables
interface table (AP_INVOICES_INTERFACE)
Note that in the same table the AR_INVOICE_NUMBER field is now appearing as updated. This indicates that the Receivables
side processing is complete.
The invoice can be queried in the Transactions form in Receivables:
Click on ‘Lines’ button to see the line details of the invoice.
Click on ‘Distributions‘ button to see the details of the distribution.
Once the Receivables side processing is completed, login to ACE_S (Initiator user) to see the transaction status in AGIS.
Navigation lntercompany (Super) User: Transaction > Outbound
Query the batch by number, the status is now appearing as ‘Complete’
As mentioned at the beginning of this chaper, Processing transactions, Transfer transactions is set to Online for the example
used in this whitepaper.
See below in which step the batch’ status is changed to “Complete” when transfer transaction is set to Online or Batch Mode.
Transfer the transactions in Online mode:

1. The user must approve the transaction.
2. The initiator workflow transfers the intercompany transaction details to the Receivables Interface tables and the
transaction status changes to Transferred to Receivables.
3. Run the Receivables AutoInvoice Program.
4. 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.
5. Run the Payables Open Interface Program.
Transfer the transactions in Batch mode:

1. The user must approve the transaction.
2. Run the Transfer Intercompany Transactions to Receivables.
3. The transaction status changes to Transferred to Receivables.
4. Run the Receivables AutoInvoice Program.
On successful completion of the Receivables AutoInvoice Program, the invoice number is updated on the
intercompany transaction.
5. Run the Transfer Intercompany Transactions to Payables.
6. The transaction status changes to Complete.
7. Run the Payables Open Interface Program.
Payables – Processing Invoces
As mentioned before the Autolnvoice program in Receivables will create the business event which will populate the data in
Payables interface table (AP_INVOICES_INTERFACE)
Notice the INVOlCE_NUM is the same number as it was in Receivables:
Some of the important fields that get populated in Payables interface:
Notice that the org_id has also been populated.
7352 is the org_id for ‘ACE Japan IC Org‘, this is the Recipient lntercompany Organization.
Now login to the Recipient login (in the example ACE_J), this is necessary to complete the processing from Payables side.
To review the current status of the transaction.
Navigation: lntercompany (Super) User: Transaction > lnbound
Query for the transaction and the status appears as ‘Complete’
Login to Payables Responsibility. The name of the conurrent request to be run for importing transactions from Payables
interface to create invoice is named ‘Payables Open Interface Import‘
The important parameters of this request are:
- Operating Unit (this would be the Operating Unit of the Recipient lntercompany Organization)
- Source (this is a seeded value called ‘Global lntercompany’)
Run the request with these parameters.
The Output file of this program is called ‘Payables Open Interface Import Report’.
Notice the important fields in this report.
- Supplier
- Invoice Number
- Invoice Date
- Invoice Currency and Amount
Navigate to Invoice Workbench.
Navigation: Payables Responsibility: Invoices > Entry > Invoices
Query the invoice that was created by the Import Request in Payables.
Notice the status of the invoice is still ‘Never Validated’ and Accounted – ‘Unprocessed’.
Click on ‘All Distributions’ to see the distributions for the invoice.
Distribution lines:
The summary of steps used for AGIS transaction processing is as follows:
1] Initiation of a transaction by an intercompany organization

2] Completion of accounting from the Initiator side
3] Completion of the accounting by the Recipient side
4] Approval of the transaction by the Recipient
If the Invoicing is opted for, in the transaction type setup then,

5] Processing of the Invoice from Receivables (for the Initiator Subsidiary side)
6] Processing of the Invoice in Payables (for the Recipient subsidiary side)
At this stage, the AGIS part of the transaction processing finishes. The next step would be the accounting for those invoices
and transferring of the invoices to General Ledger.
PART THREE - AGIS REPORTS AND RECONCILIATION
AGIS REPORTS AND RECONCILIATION
The following three reports are available in AGIS.

 Oracle Intercompany Transaction Summary Report (FUNSRPT)
 Oracle Intercompany Account Details Report (FUNARPT)
 Intercompany Reconciliation Report (FUNRCNRPT)
The reports can be run from lntercompany Responsibility.
Navigation: Requests > Schedule
The following two reports work like ordinary reports. The third report works in a different fashion. There is a data collection
request for that, after that the report can be run.
 Oracle lntercompany Transaction Summary Report
 Oracle lntercompany Account Details Report
Notice that the application name is now Financials Common Modules.
Request submission is a web page based, seven-step operation.
Select the first report ‘Oracle Intercompany Transaction Summary Report’ as step one.
Parameters for the Oracle lntercompany Transaction Summary Report are shown here.
The only mandatory parameter for this report is Batch Type. There are three possible values for it: Inbound, Outbound, Both.
Users can see the Inbound and/or Outbound AGIS transactions based on some additional criteria like Initiator, Recipient,
transaction date, status etc.
The concurrent requests can be scheduled or submitted immediately in this step.
Notice that at this stage there is a Template mentioned. For Oracle Intercompany Transaction Summary Report, the default
template is called FUNSRPT.
The output can be seen in multiple formats as listed in the LOV. This includes Excel, HTML, PDF.
It is possible to trigger notifications to specified users listed in the step. So once the request is completed and based on the
status of the request, recipients listed here will be notified regarding the status of the request.
Further select the printing options.
Review the summary of options as they were selected in the earlier steps and then the request can be submitted.
Now a concurrent request ID is shown. Click on the ‘OK’ button will open the Request Monitoring page.
See the current status of the request:
Click on ‘Output’ icon to review the output file:
Now the output is shown in PDF format as selected in the report submission window.
This report shows all the relevant parameter along with lot of other transaction level details such as initiator, batch number,
transaction type, date, status, recipient, amounts, status and invoice number.
In the request monitor screen click on ‘Details’ icon and then click on ‘View Log file’ to check the log file.
Oracle Intercompany Transaction Summary Report has the short name of FUNSRPT.
Other report available is Oracle Intercompany Acount Details Report
There are various parameters available for this report. But the mandatory one is the batch type.
Another report available is Intercompany Reconciliation Report.
For this one in particular, before running, a data extraction program is submitted from the same navigation.
Request > Schedule
There are again various parameters for this report as well. The Transacting Ledger ad Transacting GL period are the
mandatory ones.
Note down the request ID generated on the submission of the request.
Once the request submission is complete navigate to Intercompany Super User > Reconciliation
Now enter the request ID of the request that was submitted for data extraction in the Request ID field.
There are some options to be selected including the template and the format of the report. Then click on ‘Run’.
In the bottom area of the screen the report is shown.
To take the output in a different file click on the ‘Export’ button.
The report shows the details of the transacting and trading Legal Entity, currency, intercompany receivables and payables
balances in GL as well.
There are different formats available for generation of the report.
TECHNICAL DETAILS
RELEVANT HTML PAGES
HTML Page Name Function Name

BalAcctsSearchPG FUN_BAL_ACCTS_SEARCH
InterMaintSearchPG FUN_INTER_MAINT_SEARCH
IntraBalMaintSearchPG FUN_INTRA_BAL_MAINT_SEARCH
CustSuppLESearchPG FUN_SETUP_CUSTSUPP_SEARCH
PartySearchPG FUN_SETUP_PARTY_SEARCH
ClosedPeriodStatusPG FUN_SETUP_PER_STATUS_CLOSE
OpenPeriodStatusPG FUN_SETUP_PER_STATUS_OPEN
AssignSearchPG FUN_SETUP_SECURITY_SEARCH
ViewSystemOptionsPG FUN_SETUP_SYSOPT_VIEW
TrxTypeSearchPG FUN_SETUP_TRXTYPE_SEARCH
TrxTypeMapSearchPG FUN_SETUP_TRXTYPEMAP_SEARCH
InSearchPG FUN_TRX_ENTRY_IN_SEARCH
OutSearchPG FUN_TRX_ENTRY_OUT_SEARCH
HomePG FUN_USER_HOME_PAGE
ReconciliationSearchSumPG FUN_INTERCO_RECONCILIATION
RELEVANT TABLES IN AGIS
Name Feature Area

FUN_SYSTEM_OPTIONS Intercompany System Options
FUN_BALANCE_OPTIONS Intracompany Balancing Options
FUN_BALANCE_ACCOUNTS Intracompany Balancing Accounts
FUN_INTER_ACCOUNTS Intercompany Accounts
FUN_TRX_ACCT_DEFINITIONS Intercompany Subledger Transaction Account Definition
FUN_TRADE_RELATIONS Intercompany Trading Relations
FUN_CUSTOMER_MAPS Intercompany Customer Mappings
FUN_SUPPLIER_MAPS Intercompany Supplier Mappings
FUN_TRX_TYPES_B Intercompany Transaction Types
FUN_TRX_TYPES_TL Intercompany Transaction Types
FUN_TRX_TYPE_AR_MAPS Intercompany Transaction Type Receivables Mappings
FUN_TRX_BATCHES Intercompany Transaction Batches
FUN_TRX_HEADERS Intercompany Transaction Headers
FUN_TRX_LINES Intercompany Transaction Lines
FUN_DIST_LINES Intercompany Distribution Lines
FUN_BATCH_DISTS Intercompany Batch Distributions
FUN_INTERFACE_CONTROLS Intercompany Interface Controls
FUN_INTERFACE_BATCHES Intercompany Interface Batches
FUN_INTERFACE_HEADERS Intercompany Interface Headers
FUN_INTERFACE_DIST_LINES Intercompany Interface Distribution Lines
FUN_INTERFACE_BATCHDISTS Intercompany Interface Batch Distributions
FUN_INTERFACE_REJECTIONS Intercompany Interface Rejections
FUN_SUBSIDIARY_PARTY_MAPPINGS Upgraded mapping between GIS Subsidiaries and Intercompany Organizations
USEFUL QUERIES
Identify the batch id based in the AGIS batch number
select batch_id from fun_trx_batches where batch_number = '&batch_number'
Queries to check all the details related to an AGIS batch
select * from fun_trx_batches where batch_number = '&batch_number'
select * from fun_trx_headers where batch_id in (select distinct batch_id from fun_trx_batches where
batch_number = '&batch_number')
select * from fun_trx_lines where trx_id in (select distinct trx_id from fun_trx_headers where
batch_id in (select distinct batch_id from fun_trx_batches where batch_number = '&batch_number'))
select * from fun_dist_lines where trx_id in (select distinct trx_id from fun_trx_headers
where batch_id in (select distinct batch_id from fun_trx_batches where batch_number = '&batch_number'))
OTHER FEATURES
WORKFLOW AND APPROVALS MANAGEMENT SYSTEM (AME) INTEGRATION
While processing AGIS transactions the workflow is intensively used. Specific listeners are accessed for various purposes,
notifications are sent to the users at different stages and so on.
Besides the generic information we present below as relevant for this whitepaper, please consider reviewing also these
dedicated whitepapers in:
(Doc ID 785167.1) Advanced Global Intercompany Troubleshooting AGIS Workflow White Paper
(Doc ID 1371982.1) Approvals Management Engine (AME) Usage and Setup in AGIS
The main workflows specific to AGIS are:
Workflow Name Feature Area

FUNMULTI.wft Intercompany Multiple System Integration
FUNIMAIN.wft Intercompany Initiator Main Processing
FUNRTVAL.wft Intercompany Recipient Validation
FUNRMAIN.wft Intercompany Recipient Main Processing
FUNGLINT.wft Intercompany integration with General Ledger
FUNARINT.wft Intercompany integration with Receivables
FUNAPINT.wft Intercompany integration with Payables
Workflow Approval – Oracle Approvals Management

If intercompany transactions require manual approval, then the list of approvers is obtained as set up in Oracle Approvals
Management. The following table lists the two seeded default rules that generate the list of approvers or contacts based on
the security assignments for the Organization.
Transaction Type Name Default Approval Rule Default Approval Group Description
Default rule for Initiator FUN Initiator Approval Group Users who receive FYI notifications.
FUN Initiator Intercompany Intercompany Transaction
Transaction
Default rule for Recipient FUN Recipient Approval Group Users who are approvers.
FUN Recipient Intercompany Intercompany Transaction
Transaction
Useful Queries Related to Workflow:
Verify the status of the relevant listeners; they should be in RUNNING status
set pagesize 400

set linesize 120
set pagesize 50
column COMPONENT_NAME format a45
column STARTUP_MODE format a15
column COMPONENT_STATUS format a15
select fsc.COMPONENT_NAME,fsc.STARTUP_MODE,fsc.COMPONENT_STATUS
from APPS.FND_CONCURRENT_QUEUES_VL fcq, fnd_svc_components fsc
where fsc.concurrent_queue_id = fcq.concurrent_queue_id(+)
order by COMPONENT_STATUS, STARTUP_MODE, COMPONENT_NAME;
Check the items ending with exception;

you may also check in this table the ACTIVITY_STATUS = ERROR
select * from WF_ITEM_ACTIVITY_STATUSES

where item_key like 'batch_id%'and activity_result_code='#EXCEPTION'
From the above, get the ITEM_TYPE and ITEM_KEY and use them to run these sqls which
provide item’s very detailed information for diagnose purposes.
wfstat.sql ($FND_TOP/sql/wfstat.sql)
wfstatus.sql ($FND_TOP/sql/wfstatus.sql)
AGIS ACCOUNTING
AGIS accounting generated either by setups of specific intercompany accounts, rules, automatically derived through
Transaction Accounts Definition (TAD) and so on - may generate errors or raise specific concerns with the users.
Besides the generic information we present below as relevant for this whitepaper, please consider reviewing also this
dedicated whitepaper in:
(Doc ID 579930.1) Intracompany Balancing In Release 12
The most common AGIS processing errors are:

Error Message Message Text
FUN_INTRA_CC_NOT_CREATED Intercompany balancing was unable to generate the
intercompany account
FUN_INTER_PAY_NO_DEFAULT There is no default Intercompany Payables account available as
the Multiple Legal Entity Balancing Account for the From and To
legal entities, &FROM_LE_ID and &TO_LE_ID.
FUN_INTER_PAY_NOT_ASSIGNED No Intercompany Payables account has been selected as the
Multiple Legal Entity Balancing Account for the From and To
legal entities &FROM_LE_ID and &TO_LE_ID
FUN_INTER_PAY_NOT_VALID The Intercompany Payables account &ACCOUNT_VALUE defined
for the From and To legal entities &FROM_LE_ID and
&TO_LE_ID is not valid
FUN_INTER_REC_NOT_ASSIGNED There are no Intercompany Receivables accounts defined for the
From and To legal entities, &FROM_LE_ID and &TO_LE_ID.
FUN_INTER_REC_NO_DEFAULT There is no default Intercompany Receivables account available
as the Multiple Legal Entity Balancing Account for the From and
To legal entities, &FROM_LE_ID and &TO_LE_ID
FUN_INTER_REC_NOT_VALID The Intercompany Receivables account &ACCOUNT_VALUE
defined for the From and To legal entities, &FROM_LE_ID and
&TO_LE_ID is not valid
FUN_INTRA_CC_NOT_VALID The Intercompany account generated by the Intercompany
Balancing Rules is invalid
FUN_INTRA_CC_NOT_ACTIVE The Intercompany account generated by the Intercompany
Balancing Rules is not active
FUN_INTRA_NO_CLEARING_BSV The Clearing Option for the Balancing Rule used by the ledger
&LEDGER_NAME, Source &SOURCE_NAME, Category
&JE_CATEGORY and Legal Entity &LE_ID is not valid. The
Clearing Option "Enter Manually On All Journals" is not
permitted for processing subledger journal entries
FLEX-VALUE DOES NOT EXIST Value &VALUE for the flexfield segment &SEGMENT does not
exist in the value set &VALUESET
FUN_INTRA_CLEAR_BSV_INVALID The Balancing Segment Value used for the clearing account is
ineffective for the journal date
For each, please identify debugging tips in:

(Doc ID 813397.1) How To Troubleshoot AGIS Accounting
TRANSACTIONS ACCOUNTS DERIVATION (TAD) FOR AGIS
Transaction Account Definition (TAD) rules, if defined, are called to default initiator and recipient distribution accounts for
each transaction. They can be used to create the Clearing Accounts too based on the Intercompany Organization or the
Transaction Type.
Besides the generic information we present below as relevant for this whitepaper, please consider reviewing also these
dedicated whitepapers in:
(Doc ID 2606043.2) R12: GL: Transaction Accounting Definition(TAD) Video Series
(Doc ID 1322237.1) AGIS: Transaction Account Derivation (TAD) - Usage and Setup
How are Intercompany Accounts Derived when both AGIS setups and TAD rules exist?
There are certain rules of precedence that apply, as following:

• If TAD setup is valid, it will be used for accounts derivation
• If TAD exists but it generates invalid accounts, then further the balancing code combination will be derived from
AGIS setups defined in Accounting Setup Manager as shown previously
• If TAD does not exist, the AGIS setups will be used directly
• In order to test your TAD setup, do not define AGIS rules / accounts so in case of failure error will be thrown
KNOWN ISSUES
1. Issue: Errors Deriving intercompany Accounts
AGIS: Outbound Batch XX, Transaction 1 Encountered Errors Deriving Intercompany Accounts when using
Intercompany Segment. (Doc ID 2211526.1)
Resolution:
Define the value in the valueset of intercompany Segment (Setup-Financials-Flexfields-Key-Values )
2. Issue: AGIS Batch Status is XFR_AR and the Receivables Invoice is not Created (Doc ID 2609918.1)
Running the following query shows that the intercompany data exists in the AR interface table RA_INTERFACE_LINES_ALL:
select * from RA_INTERFACE_LINES_ALL raa ,FUN_TRX_BATCHES bat
where raa.INTERFACE_LINE_ATTRIBUTE1=bat.BATCH_ID
and bat.BATCH_ID in ('&AGIS_Batch_ID');
Resolution:
Monitor and verify that the RAXTRX: Autoinvoice Import Program has completed with success; confirm that the data in the
RA_INTERFACE_LINES_ALL table has been imported successfully afterwards.
3. Issue: You have encountered an unexpected error. Please contact System Administrator for Assistance
R12 AGIS: Error Approving Intercompany Transaction, java.sql.SQLException: ORA-01403, ORA-06512: at
"APPS.FUN_RECIPIENT_WF" (Doc ID 1496940.1)
Resolution:
Bounce workflow manager and concurrent manager every time you make changes to TAD (Transaction Account Definition).
This is caused by making changes to TAD (Transaction Account Definition) and not following that by bouncing the workflow
manager and concurrent manager.
4. Issue: Transaction status error without any other hints
Run wfstatus.sql . RECI_WF_KEY is populated for the Transaction in FUN_TRX_HEADERS

Error message: Complete the accounting distribution for the recipient'
Agis Batch Throws 'Error: Complete the accounting distribution for the recipient' (Doc ID 1542210.1)
Resolution:
Review the user definition, this should include valid information and Email address. Agis is integrated with Workflow and
also with AME (Approvals Management Engine) for the approvals. The email address is needed in the process.
5. Issue: Intercompany organization cannot be used by an user due below error
Resolution:
Intercompany Organizations would be available from the date they are created.
If the intercompany organization is created on 11-Dec-16, then the organization would be available for transaction entry from
the GL date 11th Dec'16. In certain cases, the start date can be alerted using the fix given in the below note:
Note 1294328.1: R12: AGIS: The Recipient Organization For Transaction Number 1 Does Not Match the GL Date
General Ledger Blog – Direct Link
General Ledger Community – Direct Link
CONNECT WITH US
Call +1.800.ORACLE1 or visit oracle.com.
Outside North America, find your local office at oracle.com/contact.
blogs.oracle.com facebook.com/oracle twitter.com/oracle
Copyright © 2020, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the contents hereof are subject to change without
notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties
and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are formed
either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without
our prior written permission.
This device has not been authorized as required by the rules of the Federal Communications Commission. This device is not, and may not be, offered for sale or lease, or sold or
leased, until authorization is obtained.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of
SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered
trademark of The Open Group. 0120
White Paper Setup for Advanced Global Intercompany (AGIS) in Release 12 (R12)
April, 2020

Setup For Advanced Global Lntercompany System AGIS in Release 12 v2

Uploaded by

Document Information

Original Title

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

Setup For Advanced Global Lntercompany System AGIS in Release 12 v2

Uploaded by

Copyright:

Available Formats

Setup for Advanced Global

lntercompany System (AGIS)

Improved and republished by: Andreea Voicu

March 25, 2020 | Version 1.01

DISCLAIMERS FOR PRE-RELEASE, PRE-GA PRODUCTS

PART TWO - AGIS TRANSACTION PROCESSING .................................................... 54

PART THREE - AGIS REPORTS AND RECONCILIATION ......................................... 110

TECHNICAL DETAILS .............................................................................................. 140

OTHER FEATURES ................................................................................................... 144

KNOWN ISSUES ........................................................................................................149

- Interaction with subledgers facilitating invoicing using Receivables and Payables

The setups are divided into four main parts:

Transaction Processing in AGIS:

1. Initiation of a transaction by an intercompany organization

If the Invoicing is opted for in transaction type setups, then,

- Initiator Subsidiary: ‘ACE Singapore lntercompany Organization‘.

Setup has been divided into four parts:

In AGIS, also setup two lntercompany Organizations called:

1. ACE Singapore lntercompany Organization and

Notice the responsibilities attached to the user:

1. lntercompany Super User

Create responsibility for General Ledger:

Now, Environmental Setups are ready.

Ledger’s Definition and Setups

Next step is to create the Ledger which will be used in AGIS.

This completes the second part of the setup, GL setup.

Navigation: HR responsibility: Work Structures > Organization > Description

4] Setup the following proﬁle options at the Receivables Responsibility Level:

Navigation: Receivables Responsibility: Transactions > Transactions

4] Setup following proﬁle options at the Payables Responsibility Level.

B. GL Setups (Accounting Setup Manager Setups)

C. Receivables and Payables Responsibility Setups

Navigation: lntercompany Super User: Setup > Organizations

The second organization that is created is called ‘ACE Singapore IC Org’

Navigation: Intercompany Super User: Setup > Transaction Type

Navigation: lntercompany Super User: Setup > System Options

The next step is Invoicing Options with a menu structured as:

Navigation: Intercompany Super User: Setup > Invoicing Options

Navigation: Intercompany Super User : Setup > Invoicing Options

Now everything is set for entering transactions in AGIS.

2. GL Setups (Accounting Setup Manager Setups)

3. Receivables and Payables Responsibility Setups

lf the Invoicing is opted for, in transaction type setups, then,

The Initiator Subsidiary Organization uses the Outbound Part.

lmportant ﬁelds on this page are:

Once the Recipient Name and Debit/Credit is entered, click on ‘Continue’.

Navigation: lntercompany (Super) User: Transaction > Inbound

Notice that the BATCH_SOURCE_NAME is ‘Global Intercompany'.

1. Organization - ‘ACE Singapore Operating Unit‘ (OU)

Selected Interface Line: 1 and successfully processed.

Navigation: Receivables Responsibility: Transactions > Transactions

Transfer the transactions in Online mode:

Transfer the transactions in Batch mode:

Notice the INVOlCE_NUM is the same number as it was in Receivables:

1] Initiation of a transaction by an intercompany organization

If the Invoicing is opted for, in the transaction type setup then,

The following three reports are available in AGIS.

The reports can be run from lntercompany Responsibility.

Navigation: Requests > Schedule

Notice that the application name is now Financials Common Modules.

HTML Page Name Function Name

Name Feature Area

FUN_SUBSIDIARY_PARTY_MAPPINGS Upgraded mapping between GIS Subsidiaries and Intercompany Organizations