Advanced Global Intercompany

Troubleshooting AGIS Workflow

Author: AGIS Development

Creation Date: September 5, 2019
Last Updated: September 5, 2019
File URL: http://files.oraclecorp.com/
Version: 1.1
Status: FINAL

Approver Name Role Date

Copyright  2019 Oracle Corporation

All Rights Reserved

This document is not a promise to deliver and may not be included as part of any contract.
1. Contents

1.1 Change Record

Date Author Version Change Reference

01-Feb-2009 Sanjeeva Rampure 1.0 Draft

10-Feb-2009 Jaicntha Mary 1.1 Modified Document to fit standards, modified contents, etc.

1.2 Contributors

Contributor Role Position

Jacintha Mary Development Manager

Sanjeeva Rampure Sr. Applications Engineer
Manoj kansal Applications Engineer

1.3 Reviewers

Name Role Position Document Status Date Reviewed Comments

Incorporated

Open and Closed Issues Page ii of 26

 Contents

1. Contents..................................................................................................................ii
1.1 Change Record.........................................................................................................................ii
1.2 Contributors..............................................................................................................................ii
1.3 Reviewers.................................................................................................................................ii
2. Introduction............................................................................................................4
2.1 Scope of the Document............................................................................................................4
3. AGIS........................................................................................................................5
3.1 Common Issues........................................................................................................................5
3.1.1 No Inbound Transactions found.....................................................................................5
3.1.2 ‘No Data Found’ Error on Inbound UI, when Approve/Reject a Transaction................5
3.1.3 Invalid Role Name.........................................................................................................8
3.1.4 ‘AME Contact’ Activity Error........................................................................................9
4. Workflow..............................................................................................................12
4.1 Managers/Listeners.................................................................................................................12
5. Approvals Management (AME).........................................................................15
5.1 Approvers Setup.....................................................................................................................15
5.1.1 Configuration...............................................................................................................15
5.1.2 Setup.............................................................................................................................16
5.1.3 Create Grant.................................................................................................................18
6. Logging AGIS/Workflow/AME Integration Issues...........................................21
6.1 Information Required.............................................................................................................21
7. AGIS Tables and Views.......................................................................................23
7.1 Tables..................................................................................................................................23
7.2 Views...................................................................................................................................24
8. Open and Closed Issues.......................................................................................25
8.1 Open Issues.............................................................................................................................25
8.2 Closed Issues..........................................................................................................................25

Open and Closed Issues Page iii of 26

2. Introduction

2.1 Scope of the Document

This document addresses the commonly encountered AGIS workflow issues and the steps to
identify and fix the problem. The issues listed here are mainly due to customer specific setup
data and requires user intervention to resolve the issue.

AGIS/AME cannot be fixed to prevent these issues, as these are setup specific errors.

Open and Closed Issues Page 4 of 26

3. AGIS

3.1 Common Issues

This section lists the commonly encountered AGIS issues related to workflow

3.1.1 No Inbound Transactions found

User has created an outbound batch from Intercompany super user and cannot find the batch in the
inbound UI. (E.g Bug 6077350)

Navigation (For debugging in AGIS)

(a) Check the AGIS Security setup. The user trying to see the inbound transactions must have
access to the recipient organization.
(b) Execute this query –
Select trxH.trx_id, trxH.trx_number, trxH.status
from fun_trx_headers trxH, fun_trx_batches trxB
Where trxB.batch_id = trxH.batch_id
and trxB.batch_number = '<Enter the batch number here>';
(c) If the status of the transaction is ‘SENT’, then there is an issue with the workflow process
Navigation (For debugging in Workflow)
(a) Login as User ‘SYSADMIN’
(b) Responsibility -> Workflow Administrator Web Applications -> Administrator Workflow ->
Status Monitor
(c) Search for the workflow with the following values -
Internal Name: FUN%
Item Key: <Batch Id%>
Note: Make sure that Workflow Owned By is “ All Employees and Users / Your
User” (Otherwise you will not be able to view any workflows).
(d) If there are no workflows found, the follow the steps listed in Section 4 (Workflow).

3.1.2 ‘No Data Found’ Error on Inbound UI, when Approve/Reject a Transaction.

Symptoms

The following error is thrown when the user clicks on Approve/Reject button in the inbound
transactions UI:
oracle.apps.fnd.framework.OAException: java.sql.SQLException: ORA-01403: no
data found.

Open and Closed Issues Page 5 of 26

 This error occurs either due to AGIS /Workflow setup issues.
Navigation (In AGIS for Debugging)
(a) Responsibility -> Intercompany Super User -> Setup -> Security
(b) Query the recipient Organization
(c) Check if the options 'Send Approval Notification' and 'Access to Transactions' have been
checked for at least one user.
(d) You can also execute the following query, to check: -
select * from wf_local_user_roles role where role.role_name like
'FUN_ADHOC_RECI_||<trx_id>';
If the query returns “No Rows”, then the UI will return a no data found error.
(e) Enable the options for atleast one user to prevent this issue for future transactions.
(f) Users cannot approve or reject the transactions from AGIS, for transactions that were created
before this error was fixed. Users have to use workflow ‘Status Monitor’ to approve the
transactions. If you are unable to approve, follow the steps listed below.
Patch Availability
To prevent this error in the future, apply patch: 6998219:R12.FUN.A, which will validate the
security tab setup during the batch creation. The one-off can be applied on top of any RUP.This
has been fixed on RUP6 and later releases.

Navigation (Workflow)

(a) Login as User ‘SYSADMIN’

(b) Responsibility -> Workflow Administrator Web Applications -> Administrator Workflow ->
Status Monitor
(e) Search for the workflow with the following values -
Internal Name: FUN%
Item Key: <Batch Id%>
Note: Make sure that Workflow Owned By is “ All Employees and Users / Your
User” (Otherwise you will not be able to view any workflows).
(f) If there are any workflows with a status of ‘Error’, navigate through the workflow
diagram/error message to understand the issue.
(g) If the workflow gives the below error message or similar, it is due to AME setup. Check if the
Administrator approver user is active (not endated). Please follow the AME setup steps listed
in Section 5 (AME), to know the Administrator approver (or) follow step h
3120: Activity 'FUNRMAIN/139677' has no performer.
3120: Activity 'FUNIMAIN/139677' has no performer.
(h) Execute the below query.
declare
l_transaction_type VARCHAR2(30);
l_ame_admin_rec ame_util.approverRecord2;
begin
l_transaction_type := 'FUN_IC_INIT_TRX';
ame_api2.getAdminApprover(

Open and Closed Issues Page 6 of 26

 applicationIdIn => 435,
transactionTypeIn => l_transaction_type,
adminApproverOut => l_ame_admin_rec);

dbms_output.put_line('l_ame_admin_rec.name :: '||l_ame_admin_rec.name);
End;

Patch Availability
We are evaluating if a valid error message can be displayed during rejecting/approving a
transaction. Please track Bug 8264262 for progress.

Click here

Open and Closed Issues Page 7 of 26

 3.1.3 Invalid Role Name

Users will encounter the following error message, on the click of the Approve/Reject button in the
inbound batches UI. (e.g. Bug: 7160173):

Oracle.apps.fnd.framework.OAException: java.sql.SQLException: ORA-20002:

396: Invalid role name 'FUN_ADHOC_RECI_136436'
ORA-06512: at "APPS.FUN_RECIPIENT_WF", line 1782
ORA-06512: at line 1

Open and Closed Issues Page 8 of 26

 OR
oracle.apps.fnd.framework.OAException: java.sql.SQLException: ORA-20002:
396: Invalid role name 'FUN_ADHOC_RECI_'
ORA-06512: at "APPS.FUN_RECIPIENT_WF", line 1782
ORA-06512: at line 1

Solution
Apply patch: 7160173:R12.FUN.A. The one-off can be applied on top of any RUP.This has been
fixed on RUP6 and later releases.

3.1.4 ‘AME Contact’ Activity Error

Symptoms

Online transfer to GL does not work even if the system option 'Transfer Transactions to General
Ledger' is set to 'Online':

Navigation (Debugging)

(a) The Organization can have multiple approvers defined under the AGIS security tab and it is
required that all users/Person who can approve/reject a transaction are associated to an Active
User/Person.
(b) Execute this query to get details on the approvers, users , active dates, persons, active
dates,etc for a given transaction–
SELECT distinct fu.employee_id PERSON_ID,
p.PARTY_NAME PERSON_NAME,
pap.EFFECTIVE_START_DATE PERSON_START_DATE,
pap.EFFECTIVE_END_DATE PERSON_END_DATE,

Open and Closed Issues Page 9 of 26

 fu.USER_ID USER_ID,
fu.USER_NAME USER_NAME,
fu.START_DATE USER_START_DATE,
fu.END_DATE USER_END_DATE
FROM hz_parties p,
fnd_user fu,
fun_trx_headers ftrx,
hz_relationships hzr,
hz_org_contacts hc,
hz_org_contact_roles hcr,
PER_ALL_PEOPLE_F PAP
WHERE p.party_type = 'PERSON'
AND p.party_id = hzr.subject_id
AND hzr.object_id = ftrx.initiator_id
AND hzr.relationship_code = 'CONTACT_OF'
AND hzr.relationship_type = 'CONTACT'
AND hzr.directional_flag = 'F'
AND hzr.subject_table_name = 'HZ_PARTIES'
AND hzr.object_table_name = 'HZ_PARTIES'
AND hzr.subject_type = 'PERSON'
AND hc.party_relationship_id = hzr.relationship_id
AND hcr.org_contact_id = hc.org_contact_id
AND hcr.role_type = 'INTERCOMPANY_CONTACT_FOR'
AND fu.person_party_id = p.party_id
AND sysdate BETWEEN
nvl(hzr.start_date, sysdate -1)
AND nvl(hzr.end_date, sysdate + 1)
AND ftrx.trx_id = <trx_id>
AND hzr.ADDITIONAL_INFORMATION1 = 'Y'
AND sysdate BETWEEN
nvl(fu.start_date, sysdate -1)
AND nvl(fu.end_date, sysdate + 1)
AND PAP.PERSON_ID=FU.EMPLOYEE_ID(+)
AND P.PARTY_ID=PAP.PARTY_ID
ORDER BY PERSON_NAME, USER_NAME;

(c) If any of the users are end dated, then they have to be made active.
(g) Responsibility -> System Administrator-> Security: User -> Define
(h) Query the user and update the effective dates.
(i) If any of the associated perrson is end dated, they have to be made active.

Open and Closed Issues Page 10 of 26

 (j) Responsibility -> Human Resources -> People -> Enter and Maintain
(k) Query the Person and update the dates.

Patch Availability
Please track Bug 8264739 for progress.

Open and Closed Issues Page 11 of 26

4. Workflow

4.1 Managers/Listeners
One of the commonly encountered AGIS issue is related to workflow. This section lists the steps
that will help resolve the AGIS workflow setup related issues.

Navigation – Is Workflow Running?

(a) Responsibility ->Workflow Administrator Web Applications -> Oracle Applications Manager
--> Workflow Manager
(b) Notification Mailers  Check all the components in this region.
(c) Agent Listeners  Check all the components in this region
(d) If any of the listener components are not in ‘Running’ status, then stop and start the listeners.

Navigation – Workflow Listeners

Open and Closed Issues Page 12 of 26

Open and Closed Issues Page 13 of 26
 (e) If all the listeners are running as expected, then follow the next set of steps to check licenses.

Workflow Licenses
(a) To check licenses, execute the following query
select we.name, wes.wf_process_type, wes.wf_process_name,
wes.licensed_flag
from wf_events we, wf_event_subscriptions wes
where we.guid = wes.event_filter_guid
and wes.wf_process_type like 'FUN%';
For AGIS workflow to work as expected the value in the field licensed_flag must be ‘Y’.
(b) If the value in the licensed_flag is ‘N’, then execute the below query.
select app.APPLICATION_SHORT_NAME,
prod.status
from fnd_product_installations prod,
fnd_application app
where app.application_id = prod.application_id
and app.APPLICATION_SHORT_NAME = 'FUN';
(c) If the value in the status field is ‘I’ or ‘S’, then submit the concurrent program, ‘Synchronize
Product License and Workflow BES License’. This program synchronizes (sets/resets) the
license flag on all Events/Subscriptions based on the product license settings.
(d) If status is NOT ‘I’ or ‘S’, then follow the metalink note: Note 351453.1 (Replace the Product
code FPA with FUN).
(e) Execute the concurrent program, ‘Synchronize Product License and Workflow BES License’.
(f) Execute the query in step a, and check for the value of the field licensed_flag, it must be ‘Y’.
(g) If the licensed_flag is NOT ‘Y’, then follow metalink NOTE: 430588.1(application_id = 435)
(h) Repeat steps e-f.

Open and Closed Issues Page 14 of 26

5. Approvals Management (AME)

AGIS Applications supports a list of approvers who can approve /reject transactions. If an
exception arises, during the approval/rejection process, it is required that an administrator
approver be set up in AME.
This section lists the steps to setup Administrator approver.

5.1 Approvers Setup

5.1.1 Configuration

(a) Responsibility -> Approvals Management Administrator

(b) Click on the ‘Configuration Variables’, found on the right hand side of the page.

(c) The default value recomended for ‘Administrator Approver’ is ‘SYSADMIN’.

(d) If you see a different value, choose ‘SYSADMIN’ from the LOV and click on the ‘Apply
Button’

Open and Closed Issues Page 15 of 26

 5.1.2 Setup

(a) Responsibility -> User Management

(b) Enter ‘SYSADMIN’ for the field ‘User Name’ and click ‘Go’.
(c) Click on the ‘Update Icon’ on the results row.

(d) Click on the ‘Assign Roles’ button on the results row.

Open and Closed Issues Page 16 of 26

 (e) In the search field for ‘Roles and Responsibilities’, search for ‘Approval%’
(f) Click ‘Select All’ on the returned values.
(g) Click on the ‘Select’ Button.

(h) For each of the Role, enter a Justification and an ‘Active From’ date. Ensure that the ‘Active
From’ date is an old prior date.

Open and Closed Issues Page 17 of 26

 (i) After entering the above for all the roles, click on ‘Apply’.

5.1.3 Create Grant

(a) Responsibility -> Functional Administrator

(b) Click on ‘Create Grant’

(c) Enter the following information

Name: Enter the name required – AGIS Transactions (example)
Effective From Date – The effective from date must be lesser than prior date.
Grant Type – Choose the value of ‘Specific User’ from the LOV
Grantee - Select ‘ESPPO’ from the LOV (this is the Grantee name for SYSADMIN)
Object - Select ‘AME Transaction Types’ from the LOV
(d) Click on ‘Next’.

Open and Closed Issues Page 18 of 26

 (e) Under ‘Data Context Type’, select ‘All Rows’ from the LOV.
(f) Click ‘Next’.

(g) Under ‘Set’, select ‘AME Calling Applications’ from the LOV
(h) Click on ‘Next’

Open and Closed Issues Page 19 of 26

 (i) Click on ‘Finish’.

Open and Closed Issues Page 20 of 26

Open and Closed Issues Page 21 of 26
6. Logging AGIS/Workflow/AME Integration Issues.

If you encounter AGIS/Workflow/AME Integration issues, which have not been addressed in this
document, please log a bug with the following information.

6.1 Information Required

Provide the screen shots of the workflows:

Open and Closed Issues Page 22 of 26

Open and Closed Issues Page 23 of 26
7. AGIS Tables and Views
7.1 Tables
Table Name
FUN_SYSTEM_OPTIONS
FUN_BALANCE_OPTIONS
FUN_BALANCE_ACCOUNTS
FUN_INTER_ACCOUNTS
FUN_INTER_ACCOUNTS_ADDL
FUN_TRX_ACCT_DEFINITIONS
FUN_TRADE_RELATIONS
FUN_CUSTOMER_MAPS
FUN_SUPPLIER_MAPS
FUN_TRX_TYPES_B
FUN_TRX_TYPES_TL
FUN_TRX_TYPE_AR_MAPS
FUN_TRX_BATCHES
FUN_TRX_HEADERS
FUN_TRX_LINES
FUN_DIST_LINES
FUN_BATCH_DISTS
FUN_INTERFACE_CONTROLS
FUN_INTERFACE_BATCHES
FUN_INTERFACE_HEADERS
FUN_INTERFACE_DIST_LINES
FUN_INTERFACE_BATCHDISTS
FUN_INTERFACE_REJECTIONS
FUN_SUBSIDIARY_PARTY_MAPPINGS Upgraded mapping between GIS
Subsidiaries and Intercompany
Open and Closed Issues
Feature Area
Intercompany System Options
Intracompany Balancing Options
Intracompany Balancing Accounts
Intercompany Accounts that are used in the
accounting setup.
Intercompany Accounts that are generated
after switching the BSVs
Intercompany SubLedger Transaction
Account Definition
Intercompany Trading Relations
Intercompany Customer Mappings
Intercompany Supplier Mappings
Intercompany Transaction Types
Intercompany Transaction Types
Intercompany Transaction Type Receivables
Mappings
Intercompany Transaction Batches
Intercompany Transaction Headers
Intercompany Transaction Lines
Intercompany Distribution Lines
Intercompany Batch Distributions
Intercompany Interface Controls
Intercompany Interface Batches
Intercompany Interface Headers
Intercompany Interface Distribution Lines
Intercompany Interface Batch Distributions
Intercompany Interface Rejections
Page 24 of 26
 Table Name Feature Area
Organizations.

7.2 Views

View Name Feature Area

FUN_TRX_TYPE_VL Transaction Types

FUN_INTER_ACCOUNTS_V Union of
FUN_INTER_ACCOUNTS and
FUN_INTER_ACCOUNTS_ADDL

Open and Closed Issues Page 25 of 26

8. Open and Closed Issues

8.1 Open Issues

Number Description Date Raised Priority Owner Action Target Date

1.

2.

3.
Priority: H= High; M=Medium, L=Low

8.2 Closed Issues

Number Description Date Raised Priority Owner Resolution Date Closed

Priority: H= High; M=Medium, L=Low

Open and Closed Issues Page 26 of 26