AGIS FAQ

AGIS FAQ

Advanced Global Intercompany Systems FAQ [ID 975235.1]

--------------------------------------------------------------------------------


In this Document
Purpose
Questions and Answers
1. How to check whether the AGIS product is licensed or not ?
2. Are there any white papers on AGIS ?
3. Can you enter foreign currency transactions in AGIS ?
4. How does the AGIS system create AR Standard invoices and Credit memos in subledgers for AGIS transactions ?
5. Does AGIS support AME Supervisory level Approval process ?
7. What data gets populated in the Reference columns in the GL, AR, AP Interface tables for AGIS Transactions ?
8. Why does the Reconciliation Report not show TAD defined Clearing Accounts ?
9. Why do manual journals clearing Accounts lines appear on the AGIS Reconciliation report ?
10. Can the system automatically assign AR payment terms to an AGIS invoice ?
11. Are there any white papers on AGIS workflow Troubleshooting ?
12. Are there any white papers on AGIS Accounting Troubleshooting ?
References



--------------------------------------------------------------------------------



Applies to:
Oracle General Ledger - Version: 12 to 12.1.1 - Release: 12.0 to 12.1
Information in this document applies to any platform.

Purpose
The purpose of this document is to answer some basic questions about Advanced Global Intercompany System in Release 12.
More information can be obtained from the AGIS User Guide and associated whitepapers.

Questions and Answers
1. How to check whether the AGIS product is licensed or not ?
Please run the sql below to check whether the AGIS product is licensed or not

select owner_tag, name, licensed_flag
from wf_events
where name like 'oracle.apps.fun%';


select owner_tag, wf_process_type, licensed_flag
from wf_event_subscriptions
where wf_process_type like 'FUN%';


If the licensed_flag is 'N' then please refer the note below for making it licensed .
note /Note 454668.1 : AGIS - Initiator Transaction Status Changes To "Submitted" But The Recipient Cannot View Notification

2. Are there any white papers on AGIS ?
There is a whitepaper as well as a viewlet on AGIS. Refer to note /Note 418649.1 :Advanced Global Intercompany (AGIS) in Release 12 (R12) - Setup, Transaction Processing and Reports.

3. Can you enter foreign currency transactions in AGIS ?
Yes , you can enter foreign currency transactions in AGIS.
Please refer tonote / Note 755617.1 How to enter AGIS inter company transaction with foreign currency.

4. How does the AGIS system create AR Standard invoices and Credit memos in subledgers for AGIS transactions ?
AGIS will determine whether it is a standard invoice or Credit memo based on the initiator intercompany clearing Account after the recipient approves the transaction .

In the following scenario, an AR Standard invoice will get generated from AGIS :
If the Initiator intercompany Clearing line has either a positive debit or a negative credit amount, then the system will create a Standard invoice in AR.


In the following scenario, an AR Credit memo will get generated from AGIS :
If the Initiator Intercompany Clearing line has either a negative debit or a positive credit amount, then the system will create a credit memo in AR.

5. Does AGIS support AME Supervisory level Approval process ?
Yes , AGIS support AME supervisory level approval process .
Enhancement request ER 6995183 Implemented
6. In AGIS can you generate clearing accounts based on AGIS Transactions types ?
Yes, you can generate clearing accounts based on AGIS transactions types .
For more information please refer to the AGIS User Guide ->Default Accounts rules setup in Subledger accounting for intercompany
7. What data gets populated in the Reference columns in the GL, AR, AP Interface tables for AGIS Transactions ?

GL_INTERFACE
=============
From table GL_INTERFACE you can find the following


REFERENCE22 Stores FUN_TRX-BATCHES (BATCH_ID)
REFERENCE23 Stores FUN_TRX_HEADERS(TRX_ID)
REFERENCE24 Stores FUN_DIST_LINES(DIST_ID)


RA_INTERFACE_LINES_ALL
=======================
From table RA_INTERFACE_LINES_ALL you can find the following


INTERFACE_LINE_ATTRIBUTE1 Stores FUN_TRX_BATCHES(BATCH_ID)
INTERFACE_LINE_ATTRIBUTE2 Stores FUN_TRX_HEADERS(TRX_ID)
INTERFACE_LINE_ATTRIBUTE4 Stores AGIS Batch number


AP_INVOICES_INTERFACE
=====================
From table AP_INVOICES_INTERFACE you can find the following


INVOICE_NUM Stores FUN_TRX_HEADERS (AR_INVOICE_NUMBER)
GROUP_ID Stores FUN_TRX_HEADERS (TRX_ID)


AP_INVOICE_LINES_INTERFACE
==========================
From table AP_INVOICE_LINES_INTERFACE you can find the following


LINE_NUMBER Stores FUN_DIST_LINES(DIST_ID)

8. Why does the Reconciliation Report not show TAD defined Clearing Accounts ?
Currently the Reconciliation report fetches the reconciliation clearing Accounts information based on the table ''fun_inter_accounts_addl'' (This table was introduced in 12.1.1 onwards. Prior to 12.1.1, clearing accounts were obtained from the table ''fun_inter_accounts'').
So TAD defined Clearing Accounts information would not be stored in any of these tables. Hence, TAD Clearing accounts will not appear in the reconciliation report .

9. Why do manual journals clearing Accounts lines appear on the AGIS Reconciliation report ?
If any manual journal has been posted to the Intercompany Clearing Accounts, then those transactions will appear on the AGIS Reconciliation report .

10. Can the system automatically assign AR payment terms to an AGIS invoice ?
Yes, the system automatically assigns AR payment terms to an AGIS invoice in the following order:
1. Customer bill-to site level
2. Customer account level
3. Customer level transaction type
4. Default value '4'


For credit memos the payment term is always ''Null''
11. Are there any white papers on AGIS workflow Troubleshooting ?
Please refer to Note 785167.1 Advanced Global Intercompany Troubleshooting AGIS Workflow Whitepaper.

12. Are there any white papers on AGIS Accounting Troubleshooting ?
Please refer to Note 813397.1 Troubleshooting AGIS Accounting.



References
NOTE:418649.1 - Advanced Global Intercompany (AGIS) in Release 12 (R12) - Setup, Transaction Processing and Reports
NOTE:454668.1 - AGIS - Initiator Transaction Status Changes To "Submitted" But The Recipient Cannot View Notification
NOTE:755617.1 - How to enter AGIS intercompany transaction with foreign currency
NOTE:785167.1 - Advanced Global Intercompany Troubleshooting AGIS Workflow White Paper
NOTE:813397.1 - Troubleshooting AGIS Accounting

Related



--------------------------------------------------------------------------------
Products
--------------------------------------------------------------------------------

Oracle E-Business Suite > Financial Management > Financial Control and Reporting > Oracle General Ledger
Keywords
--------------------------------------------------------------------------------
RA_INTERFACE_LINES_ALL; GL_INTERFACE; AP_INVOICE_LINES_INTERFACE; AP_INVOICES_INTERFACE; AGIS; RECONCILIATION REPORT; INTERCOMPANY; REPORT

R12 Methodology - OUM

R12 Methodology - OUM

http://atawaynt.ar.ataway.com/OUM/METHOD/OM40/OUM_E_6.3/OUM/OUM_HOME.HTM

OUM (Oracle Unified Method is new methodology to implement Oracle projects)
No more AIM Methodology.

OUM:  Oracle Unified Method

It has 5 phases.

Inception à Requirement Gathering and risk analysis

The overriding goal of the Inception phase is to have concurrence among all stakeholders on the

lifecycle objectives for the project. Therefore, the Inception phase is critical for all projects because

the scope of the effort, high-level requirements, and significant risks must be understood before the

project can proceed.

Eloboration à Design

The overriding goal of the Inception phase is to have concurrence among all stakeholders on the

lifecycle objectives for the project. Therefore, the Inception phase is critical for all projects because

the scope of the effort, high-level requirements, and significant risks must be understood before the

project can proceed.

Construction à Build

The goal of the Construction phase is to take the solution from detailed requirements models, through

configuration of standard packaged software functionality, development and testing of custom

components, and integration to a system that is ready for a first release that goes into production, often

a limited release and often called a beta release. In short, complete the development of the application

system, validate that all components fit together, and prepare the system for the acceptance test and

deployment.

Transition à Moving solution to production

The goal of the Transition phase is to take the completed solution from installation onto the

production system through the acceptance test to launch of the live application, open, and ready for

business. Validate that the system is tested systematically and is available for end users. During this

phase, the new system is accepted by the client organization, the organization is made ready for the

new system, and the system is put into production and, if the new system replaces an old one, a

smooth cutover to the new application is provided.

Production  à Opearating Production system

The goal of the Production phase is to operate the newly developed system, assess the success of the

system, and monitor and address system issues. This includes monitoring the system and acting

appropriately to maintain continued operation; measuring system performance; operating and

maintaining supporting systems; responding to help requests, error reports and feature requests by

users; and managing the applicable change control process so that defects and new features may be

prioritized and assigned to future releases and put into a plan for future enhancements.

Documents:

AN100 (AN à Analysis) à Functional Specification Document (MD050 Replacement)

DS140 (DS à Design Specification) è Technical Design Document (MD070 Replacement)

T020 (Unit Test Plan Document)

Refer below screen shot for details.

Assign AME Roles and Responsibilities

Assign AME Roles and Responsibilities

1. Navigate to User Management Responsibility->Users and search for the user to whom you wish to grant AME roles. (Can navigate from any user which has Security Administrator Role or from SYSADMIN user).

2. Click on Update icon across the user name and in the update user page, click on Assign Role button.

3. Search for “Approval%” and select the Roles: Approvals Management Administrator & Approvals Management Business Analyst.

4. Specify justification and relevant dates for the newly assigned roles, and click Apply to assign the roles to the user.

Grant Transaction Type Access to Users

1. Navigate to Functional Administrator->Security->Grants and click on Create Grants button.

2. Create a grant with the following information:

• Name
• Grantee Type = ALL User
• Object = AME Transaction Types

You can also set Grantee Type as Specific User and set the your user name as Grantee

3. Click Next button and select the Object Data Context as All Rows.

4. Click Next to define the object parameters and Select Set as AME Calling Applications

5. Click Next, review the setups and then Finish the process

Create new transaction Type

1. Navigate to Approvals Management Administrator responsibility->Admin Dashboard and click on Create Transaction Type button(Responsibility will be available because of the roles assigned)

We are going to create new transaction type in reference with seeded Purchase Requisition Approval transaction type.

2. Select the application and enter Transaction Type key & Transaction Type Name.Then Click Next button.

3. In the drop down,select Line Item and click on Go button.Another row for Line Item will be created.

Change the order number to 2 and then enter the SQL query in Query window.Click on Validate button and click on Apply button.

4. Click Next button and enter the details as in below screenshot.(Click Validate button after entering each query).

5. Click Next and then Finish button.

AME Setup

1. Navigate to Approvals Management Business Analyst Responsibility->Business Analyst Dashboard (Responsibility will be available because of the role assigned)

2. Use the Transaction Type LOV to search and select the transaction type.We are using the newly created transaction type “GOV Purchase Requisition Approval“.

Seeded Transaction types available for Purchase Requisitions are Purchase Requisition Approval, Internal Requisition Approval and Requester Change Order Approval.

Attributes:

1. Select Attributes icon and click on Use Existing Attribute.

2. Under Search, select options as in below screenshot.After selecting REQUISITION_TOTAL and click on continue.

3. Select usage type as Dynamic. Enter the query,validate and click finish.

4. Similarly add ITEM_CATEGORY attribute also.

5 Also add below mentioned Attributes as its required for selecting some basic Action types

• TRANSACTION_REQUESTOR_PERSON_ID(Required for Supervisory level Action Type)

• ALLOW_EMPTY_APPROVAL_GROUPS(Required for approval-group chain of authority Action Type)

Condition:

1. Click on Conditions icon under setup tab.By default there are some conditions available.Still we can create new condition by clicking Create button.

2. Select the Attribute,enter the String value/Requisition Total and then click Apply button.

• Condition for ITEM_CATEGORY

• Condition for REQUISITION_TOTAL

• Another condition for REQUISITION_TOTAL

3. You can see the newly created condition along with existing conditions

Action Types:

1. Click on Action Types icon under setup tab and then click on “Use Existing Action Type” button.

2. Select below mentioned types and click on Continue Button.

• Supervisory level
• approval-group chain of authority

3. Then click Finish button.

Approver Groups:

1. Click on Approver Groups icon under setup tab and then click on Create button.

2. Enter the Group Name,Description,Order Number and select the Voting method.Also add the approvers and click apply button.

3. Similarly create the remaining Approval Groups.

Rules Setup:

1. Click on Rules Tab and then on Create button.

2. Enter the Rule Name,select the Rule Type and click on Next button.

3. Add the Conditions using the Add Conditions button and click next button.

4. Click on Add Actions button to add actions,click next and then Finish.

5. Similarly create all rules.

• AME_MANAGER

• AME_CATEGORY

Enable AME for Requisition Approval

1. Navigate to Purchasing Super User->Setup->Purchasing->Document Types

2. Click update button against Purchase Requisition Document Type

3. Assign newly created transaction type to Approval Transaction Type

Testing

• Requisition with total amount 900 USD (Less than 10000 USD)

• Requisition with total amount 13500 USD(Greater than 10000 USD and less than 1000000 USD)

• Requisition with total amount 1000 USD and using category “204.53”

AME Configuration setup - Oracle EBS R12

Standard Transaction Types available in oracle EBS for payables

• OIE Expenses Report –                  APEX 
•  Payables Hold Resolution –           APHLD 
•  Payables Invoice Approval –         APINV

Components for Approval Management Engine 

      Approval management uses these components within the approval rules

• Attribute: - Define the attributes to fetch the business facts for a specific transactions e.g. Item Category, transaction total amount, Expenses type etc. 
• Conditions: - Define conditions to evaluate attributes within rules. If all the conditions in rule are true then the rule is active e.g. Item Category = IT Hardware, Total Transaction Cost = USD 10000 etc. 
• Action Type: - Enable action type to specify the action to take if a rule is active for a transaction e.g. Supervisory level – Require approvals up to the first two supervisors 
• Approver Groups: - Define Approver group to contain approver’s who are usually members of peer such as payroll and exp. Department

Approval Rules

Approval group determine the approvers or FYI (for your information) notifications recipient required for business transaction.

AME Process

Basic Installation required for AME

Install AME >> Setup AME Security >> Setup user profile 

Install AME

AME’s installation routines and administration feature determine which application can use AME. Installation and administration are typically jobs for a technical specialist

Setup AME Security

Attach the predefined roles to a user or a group of user. AME uses role based function to provide user access to AME functions.

Setup user access as follows

• Login as Administrator 
• Select the user management responsibility 
• Select the user page 
• Search for user to whom you wish to grant AME roles 
• Click on update button. In the user update page we can see the user details along with roles assigned to that user 
• Click on Assign role and assign the following roles – Each of the five predefined roles has a specific set of functional grants

6.1   Approvals Management Administrator

6.2   Approvals Management Analysts

6.3   Approvals Management System Viewer

6.4   Approvals Management System Administrator

                  6.5   Approvals Management Process Owner 

•  Select the roles from the resulting list and click apply button

Once we assign the any of the five roles to user, we indirectly assigning AME responsibilities to user. Grant access to user. As AME restricts the access to Transaction Type using data security. We can assign grant user access to the transaction type using grants page. Setup user access as follows

1. Login as Administrator
2. Select the Functional Administrator responsibility 
3. Select the Grants TAB 
4. Click on Create Grant Tab 
5. Select the specific user as grantee type 
6.  Select the user as grantee key

·         Select AME Transaction Type as objects

1.       All rows – This grants access to all the transaction types to user

2.       Instance – This grant access to specific transaction type specified by following parameters “ FND_APPLICATION_ID = Application id

TRANSACTION_TYPE_ID = Unique transaction type of the AME transaction type with in the application

3.       Instance Set – This grant access to multiple transaction type specified by following parameters

Use predefined instance set AME Transaction Type instance set. Next page select FND_APPLICATION_ID as parameter1 and TRANSACTION_TYPE_ID as parameter2.

·         Next page select AME Calling Application as the permission set

·         Review and Finish 

Setup Profile option

AME: Installed

Set up Approval process

Ø  Plan your approval process

Ø  Identify business cases

Ø  Identify the components of the approval process

Ø   Plan a test case for business

Implement the Approval Process

             Ø  Implement Transaction Type      

             Ø  Configure Transaction Type           

             Ø  Create Item class usage

             Ø  Create Attributes

             Ø  Create Conditions

             Ø  Create Approval Groups

             Ø  Identify action type

             Ø  Define Approval Rules

             Ø  Test approval rules

Additional Tasks

• Create Custom transactions type 
•  Configure oracle application to use AME