Advanced Global Intercompany
Troubleshooting AGIS Accounting
Author:
AGIS Development
Creation Date: March 7, 2016
Last Updated:
March 7, 2016
Version:
1.0
Status:
Approver Name
Role
Date
Copyright  2016 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
12-Mar-2009
Manoj Kansal
1.0
Change Reference
1.2 Contributors
Contributor
Role
Position
Manoj Kansal
Applications Engineer
1.3 Reviewers
Name
Role
Position
Jacintha Mary
Dev Manager
Sr. Manager
Contents
Document Status
Oracle Confidential - For internal use only
Date Reviewed
Comments
Incorporated
Page ii of 20
Table of Contents
1.
2.
Contents ................................................................................................................. ii
1.1
Change Record ........................................................................................................................ ii
1.2
Contributors ............................................................................................................................ ii
1.3
Reviewers ................................................................................................................................ ii
Introduction ............................................................................................................4
2.1
Scope of the Document ........................................................................................................... 4
3.
Glossary ..................................................................................................................5
4.
AGIS Accounting Issues ........................................................................................6
4.1
Cannot Derive Intercompany rules with specific BSV ........................................................... 7
4.2
FUN_INTRA_RULE_NOT_ASSIGNED .............................................................................. 8
4.2.1
4.2.2
4.2.3
4.3
“Enable Intracompany Balancing” flag is not checked for the Ledger. ........................ 8
Balancing Segment Value not assigned to the Legal Entity ......................................... 8
Intracompany Rules are not defined ........................................................................... 10
Intercompany Balancing was unable to generate the intercompany account ........................ 12
4.3.1
4.3.2
4.3.3
Intercompany or Intracompany Balancing Rules are not defined ............................... 12
Intercompany or Intracompany Accounts are Not Valid ............................................ 14
Accounting Flexfield Setup is not correct ................................................................... 15
4.4
Error messages encountered while Create Accounting/Posting a GL Journal ...................... 16
4.5
FUN_INTRA_NO_CLEARING_BSV ................................................................................. 16
4.6 Value &VAL for the flexfield segment &SEGMENT does not exist in the value set
&SEGMENT .................................................................................................................................. 18
4.7
5.
Contents
FUN_INTRA_CLEAR_BSV_INVALID ............................................................................. 18
Bug Logging Guidelines ......................................................................................20
Oracle Confidential - For internal use only
Page iii of 20
2. Introduction
2.1 Scope of the Document
This document addresses the commonly encountered AGIS accounting setup issues and the steps
to identify and fix the problem.
Introduction
Oracle Confidential - For internal use only
Page 4 of 20
3. Glossary
Serial Number
Acronym Used
Meaning
1
2
3
4
5
BSV
LE
CCID
GL
AGIS
Balancing Segment Value
Legal Entity
Code Combination ID
General Ledger
Advanced Global Intercompany System
Glossary
Oracle Confidential - For internal use only
Page 5 of 20
4. AGIS Accounting Issues
This section lists the commonly encountered AGIS accounting related setup errors codes and the
resolution. Steps.
Error Message
Message Text
Debugging Steps
--
Cannot Derive Intercompany Rules with specific BSV
Section 4.1
FUN_INTRA_RULE_NOT_ASSIGNED
--
Section 4.2
FUN_INTER_BSV_NOT_ASSIGNED
--
Section 4.2
FUN_INTRA_CC_NOT_CREATED
Intercompany balancing was unable to generate the
intercompany account.
Section 4.3
FUN_INTER_PAY_NO_DEFAULT
Follow bug # 8397613 for missing error message.
Section 4.3
FUN_INTER_PAY_NOT_ASSIGNED
Follow bug # 8397613 for missing error message.
Section 4.3
FUN_INTER_PAY_NOT_VALID
Follow bug # 8397613 for missing error message.
Section 4.3
FUN_INTER_REC_NOT_ASSIGNED
Follow bug # 8397613 for missing error message.
Section 4.3
FUN_INTER_REC_NO_DEFAULT
Follow bug # 8397613 for missing error message.
Section 4.3
FUN_INTER_REC_NOT_VALID
Follow bug # 8397613 for missing error message.
Section 4.3
FUN_INTRA_CC_NOT_VALID
The Intercompany account generated by the
Intercompany Balancing Rules is invalid.
Section 4.3
FUN_INTRA_CC_NOT_ACTIVE
The Intercompany account generated by the
Intercompany Balancing Rules is not active.
Section 4.3
FUN_INTRA_NO_CLEARING_BSV
Follow bug # 8397613 for missing error message.
Section 4.5
FLEX-VALUE DOES NOT EXIST
Value &VALUE for the flexfield segment &SEGMENT
does not exist in the value set &VALUESET.
Section 4.6
FUN_INTRA_CLEAR_BSV_INVALID
The Balancing Segment Value used for the clearing
account is ineffective for the journal date.
Section 4.7
Logged bug # 8397613 for the missing Error Messages.
AGIS Accounting Issues
Oracle Confidential - For internal use only
Page 6 of 20
4.1 Cannot Derive Intercompany rules with specific BSV
While defining an Intracompany rule, like the one below, user encounters the following error: “The Intercompany Segment Value of the Debit Account selected does not match the Credit
Balancing Segment Value. Change the Credit Balancing Segment Value or the Debit Account's
Intercompany Segment.” (Ref Bug: 6841319. This is an Internal Bug and cannot be accessed
through metalink.)
Debit BSV Credit BSV
Debit Account
Credit Account
--------------------------------------------------------------------------------001
002
001.XXX.002
002.YYY.001
Cause
If the intercompany and balancing segment qualifiers are attached to the same segment on the
accounting flex field associated to the ledger,
Solution
Assign the Intercompany
accounting flex field.
and balancing segment qualifiers to different segments on the
Navigation
1.
To identify the intercompany and balancing segment of your accounting flex field, execute
the below query,
SELECT flex.id_flex_structure_code "Chart Of Accounts",
'BALANCING',
fun_bal_pkg.Get_segment_index(ledgers.chart_of_accounts_id,'
GL_BALANCING') "Balancing Segment",
'INTERCOMPANY',
fun_bal_pkg.Get_segment_index(ledgers.chart_of_accounts_id,
'GL_INTERCOMPANY') "IC Segmnet"
FROM gl_ledgers ledgers,
fnd_id_flex_structures flex
WHERE ledgers.ledger_id = <Ledger_ID>
AND flex.id_flex_num = ledgers.chart_of_accounts_id
AND flex.id_flex_code = 'GL#';
AGIS Accounting Issues
2.
If the Intercompany and the Balancing segment index’s are the same: follow thru the steps to
fix the issue.
3.
Responsibility  General Ledger
4.
Setup: Financials: Flexfields: Key  Segments.
5.
Query for the accounting flex field, returned by the query in step 1
6.
Unfreeze the accounting flex field and click on the segments button.
7.
Choose either the balancing or the intercompany segment and click on the “Flex field
Qualifiers” button.
8.
Deselect any one of the intercompany or balancing segment qualifier assigned to this
segment.
Oracle Confidential - For internal use only
Page 7 of 20
9.
Assign the deselected segment qualifier to any other segment in the accounting flex field.
10. Save the changes, freeze and compile the accounting flex field.
Open Issues
Bug 8338633 has been logged to prevent users from setting up the same qualifier against 2
segments for an accounting flex field. Please track bug for progress.
4.2 FUN_INTRA_RULE_NOT_ASSIGNED
Symptoms
User approves a transaction and the transaction ends with ‘Error’ status.
OR
On validating a Bank Account Transfer in Cash Management.
OR
On submitting the ‘Create accounting’ program or posting to General ledger.
Cause
There are multiple reasons this issue might occur. Please follow thru the steps below.
4.2.1 “Enable Intracompany Balancing” flag is not checked for the Ledger.
Solution
Select “Enabled Intracompany Balancing” flag for the Ledger.
Navigation
1.
Responsibility  General Ledger
2.
Setup: Financials: Accounting Setup Manager  Accounting Setups
3.
Search for the ledger and click on Update Accounting Options icon.
4.
Click on Update icon for “Define and update the journal processing options for your ledger.”
of the primary ledger.
5.
Click ‘Next’ or select ‘Ledger Options’.
6.
Ensure that the “Enable Intracompany Balancing” flag is checked.
4.2.2 Balancing Segment Value not assigned to the Legal Entity
The transacting and trading partner Balancing Segment Values are not attached to the legal entity.
Solution
AGIS Accounting Issues
Oracle Confidential - For internal use only
Page 8 of 20
Assign the Balancing Segment Values to the Legal Entity.
OR
Define the Intracompany rules under the “No Legal Entity Context”.
Navigation
1.
Responsibility  General Ledger responsibility.
2.
Setup: Financials: Accounting Setup Manager  Accounting Setups
3.
Search for the ledger and click on Update Accounting Options icon.
4.
On the table ‘Legal Entities’, check if the Balancing Segment Values involved in the
transaction is attached to the designated legal entity.
5.
If the Balancing Segment Values are not attached to the legal entity, click on “Update
Balancing Segment Values” icon for the legal entity.
6.
Assign the Balancing Segment Values to the legal entity.
7.
Please make sure the LE-BSV association is not end dated.
8.
If the user does not want to assign Balancing Segment Values to the legal entity, the
Balancing Segment Values are by default associated to the Ledger. Hence, the user must
define Intracompany rules for the ‘No Legal Entity’ context. Please see section 4.2.3
9.
Optional: - Below query can be used to find the BSV’s attached to a legal entity:
SELECT gllegalentitiesbsvseo.legal_entity_id,
gllegalentitiesbsvseo.flex_value_set_id,
gllegalentitiesbsvseo.flex_segment_value,
gllegalentitiesbsvseo.start_date,
gllegalentitiesbsvseo.end_date,
Decode(f.flex_value_set_id,NULL,
gl_ledgers_pkg.Get_bsv_desc('LE',
gllegalentitiesbsvseo.flex_value_set_id,
gllegalentitiesbsvseo.flex_segment_value),
f.description) description,
Decode((SELECT completion_status_code
FROM
gl_ledger_configurations
WHERE configuration_id =
(SELECT configuration_id
FROM
gl_ledger_config_details
WHERE object_id =c gllegalentitiesbsvseo.le
gal_entity_id
AND object_type_code = 'LEGAL_ENTITY'))
10.
AGIS Accounting Issues
,'CONFIRMED','N',
'Y') remove_enabled
FROM
gl_legal_entities_bsvs gllegalentitiesbsvseo,
fnd_flex_values_vl f
WHERE f.flex_value_set_id (+) = gllegalentitiesbsvseo.flex_v
alue_set_id
AND f.flex_value (+) = gllegalentitiesbsvseo.flex_segm
ent_value
AND gllegalentitiesbsvseo.legal_entity_id = <Legal
entity id>;
Oracle Confidential - For internal use only
Page 9 of 20
4.2.3 Intracompany Rules are not defined
Intracompany rules are not defined for the legal entity.
Solution
Defining Intracompany rules for the legal entity or “No Legal Entity Context”.
Navigation
1.
Responsibility  General Ledger responsibility.
2.
Setup: Financials: Accounting Setup Manager  Accounting Setups
3.
If the LE-BSV association is as expected, the Intracompany rules must be defined for the
legal entity for the appropriate Source and Category.
4.
If the user does not want to assign the BSV to a legal entity below steps must be performed
for ‘No Legal Entity’.
5.
Click on the update icon for Intracompany Balancing Rule.
6.
Click on define rules icon for the appropriate legal entity/No Legal entity Context.
7.
Check that a rule with correct source and category exists.
8.
If a rule does not exist please create one with appropriate source and category.
9.
It is always advised to have a default rule with Source ‘Other’ and Category ‘Other’.
10. If a rule already exists, click on the update icon for the rule.
11. Make sure the rule has a ‘Enabled status, and a intracompany rule with Debit BSV ‘All Other’
and credit BSV ‘All Other’ must be defined.
12. Optional:- Below query provides the template id for the rule if any exists:
SELECT NVL((SELECT opts.template_id
FROM fun_balance_options opts
WHERE opts.ledger_id
= <p_ledger_id>
AND Nvl(opts.le_id,-99) = Nvl(<p_le_id>,-99)
AND opts.je_source_name = <p_source_name>
AND opts.je_category_name = <p_category_name>
AND opts.status_flag
= 'Y'),
NVL((SELECT opts.template_id
FROM fun_balance_options opts
WHERE opts.ledger_id
= <p_ledger_id>
AND Nvl(opts.le_id,-99) = Nvl(<p_le_id>,-99)
AND opts.je_source_name = <p_source_name>
AND opts.je_category_name = 'Other'
AND opts.status_flag
= 'Y'),
NVL((SELECT opts.template_id
FROM fun_balance_options opts
WHERE opts.ledger_id
= <p_ledger_id>
AND Nvl(opts.le_id,-99) = Nvl(<p_le_id>,-99)
AGIS Accounting Issues
Oracle Confidential - For internal use only
Page 10 of 20
AND opts.je_source_name = 'Other'
AND opts.je_category_name = <p_category_name>
AND opts.status_flag
= 'Y'),
(SELECT opts.template_id
FROM fun_balance_options opts
WHERE opts.ledger_id
= <p_ledger_id>
AND Nvl(opts.le_id,-99) = Nvl(<p_le_id>,-99)
AND opts.je_source_name = 'Other'
AND opts.je_category_name = 'Other'
AND opts.status_flag
= 'Y')))) template_id
From Dual;
Where p_ledger_id = Ledger ID, p_le_id = Legal entity id,
p_source_name = Source name and p_category_name = Category name
13. Optional:- Below query will return all the rules defined for a template id:
SELECT balaccteo.template_id,
balaccteo.dr_bsv,
balaccteo.cr_bsv,
balaccteo.dr_ccid,
balaccteo.cr_ccid,
balaccteo.rowid
row_id,
balaccteo.object_version_number,
Decode(balaccteo.dr_bsv,
'OTHER1234567890123456789012345',meaning,
balaccteo.dr_bsv) dr_bsv_disp,
Decode(balaccteo.cr_bsv,
'OTHER1234567890123456789012345',meaning,
balaccteo.cr_bsv) cr_bsv_disp,
fun_trx_entry_util.Get_concatenated_account(balaccteo.d
r_ccid) dr_segments,
fun_trx_entry_util.Get_concatenated_account(balaccteo.c
r_ccid) cr_segments,
balaccteo.context,
balaccteo.attribute1,
balaccteo.attribute2,
balaccteo.attribute3,
balaccteo.attribute4,
balaccteo.attribute5,
balaccteo.attribute6,
balaccteo.attribute7,
balaccteo.attribute8,
balaccteo.attribute9,
balaccteo.attribute10,
balaccteo.attribute11,
balaccteo.attribute12,
balaccteo.attribute13,
balaccteo.attribute14,
balaccteo.attribute15
FROM
fun_balance_accounts balaccteo,
fnd_lookup_values
AGIS Accounting Issues
Oracle Confidential - For internal use only
Page 11 of 20
WHERE
lookup_type = 'FUN_INTRA_ACCT_ALL_OTHER'
AND view_application_id = 435
AND security_group_id = fnd_global.Lookup_security_grou
p(lookup_type,435)
AND language = Userenv('LANG')
AND template_id = <template id>;
4.3 Intercompany Balancing was unable to generate the intercompany account
Symptoms
User approves a transaction and the transaction ends with ‘Error’ status.
OR
On validating a Bank Account Transfer in Cash Management.
OR
On submitting the ‘Create accounting’ program or posting to General ledger.
Cause
The above issue occurs, when the intercompany balancing API is unable to generate the
intercompany or intracompany balancing accounts.
4.3.1 Intercompany or Intracompany Balancing Rules are not defined
Intercompany or Intracompany balancing rules are not defined for the legal entity.
Solution
Defining Intercompany and Intracompany balancing rules for the legal entity.
Navigation
AGIS Accounting Issues
1.
Responsibility  General Ledger responsibility.
2.
Setup: Financials: Accounting Setup Manager  Accounting Setups
3.
Search for the ledger and click on Update Accounting Options icon.
4.
Click on the Update icon for ‘Intercompany Accounts’.
5.
Click on the ‘Define Relationships’ icon for the legal entity.
6.
Make sure an Intercompany-balancing rule is defined for the Transacting legal entity,
Transacting BSV, Trading Partner legal entity and Trading partner BSV combination.
7.
It is always advised to define a default rule with Transacting BSV = ‘All Other’, Trading
partner LE = ‘All Other’ and Trading partner BSV = ‘All Other’. So, if no specific rules are
available the default rule is used for balancing.
8.
If the Intercompany accounts are defined, click on the define accounts icon for the appropriate
rule.
9.
Here for the Intercompany payables and receivables accounts the Start date and end date
should be between the gl date of the transaction.
Oracle Confidential - For internal use only
Page 12 of 20
10. If the Intercompany accounts are not available they should be defined.
11. Intercompany accounts setup should be done for both the transacting and trading partner legal
entity.
12. Follow section 4.2.3 to validate the intracompany rule setup.
13. Optional:- Below query returns the balancing ccid:
SELECT NVL( (SELECT ccid
FROM fun_inter_accounts accts
WHERE accts.ledger_id = p_ledger_id
AND accts.from_le_id = p_from_le_id
AND accts.to_le_id = p_to_le_id
AND accts.trans_bsv = p_from_bsv
AND accts.tp_bsv
= p_to_bsv
AND accts.type
= p_acct_type
AND accts.default_flag = 'Y'
AND (TRUNC(p_gl_date) BETWEEN TRUNC(NVL(accts.start_date, p_gl_date))
AND TRUNC(NVL(accts.end_date, p_gl_date)))),
NVL((SELECT ccid
FROM fun_inter_accounts accts
WHERE accts.ledger_id = p_ledger_id
AND accts.from_le_id = p_from_le_id
AND accts.to_le_id = p_to_le_id
AND accts.trans_bsv = p_from_bsv
AND accts.tp_bsv
= 'OTHER1234567890123456789012345'
AND accts.type
= p_acct_type
AND accts.default_flag = 'Y'
AND (TRUNC(p_gl_date) BETWEEN TRUNC(NVL(accts.start_date, p_gl_date))
AND TRUNC(NVL(accts.end_date, p_gl_date)))),
NVL((SELECT ccid
FROM fun_inter_accounts accts
WHERE accts.ledger_id = p_ledger_id
AND accts.from_le_id = p_from_le_id
AND accts.to_le_id = p_to_le_id
AND accts.trans_bsv = 'OTHER1234567890123456789012345'
AND accts.tp_bsv
= p_to_bsv
AND accts.type
= p_acct_type
AND accts.default_flag = 'Y'
AND (TRUNC(p_gl_date) BETWEEN TRUNC(NVL(accts.start_date, p_gl_date))
AND TRUNC(NVL(accts.end_date, p_gl_date)))),
NVL((SELECT ccid
FROM fun_inter_accounts accts
WHERE accts.ledger_id = p_ledger_id
AND accts.from_le_id = p_from_le_id
AND accts.to_le_id = p_to_le_id
AND accts.trans_bsv = 'OTHER1234567890123456789012345'
AND accts.tp_bsv
= 'OTHER1234567890123456789012345'
AND accts.type
= p_acct_type
AND accts.default_flag = 'Y'
AND (TRUNC(p_gl_date) BETWEEN TRUNC(NVL(accts.start_date, p_gl_date))
AND TRUNC(NVL(accts.end_date, p_gl_date)))),
(SELECT ccid
FROM fun_inter_accounts accts
WHERE accts.ledger_id = p_ledger_id
AND accts.from_le_id = p_from_le_id
AND accts.to_le_id = -99
AND accts.type
= p_acct_type
AND accts.default_flag = 'Y'
AND (TRUNC(p_gl_date) BETWEEN TRUNC(NVL(accts.start_date, p_gl_date))
AND TRUNC(NVL(accts.end_date, p_gl_date)))))))) ccid
AGIS Accounting Issues
Oracle Confidential - For internal use only
Page 13 of 20
From Dual;
Where p_ledger_id = Trans Ledger ID, p_from_le_id = Trans LE ID
p_from_bsv = Trans BSV, p_to_le_id = TP LE ID, p_to_bsv = TP BSV,
p_acct_type = ‘P’ for Payables and ‘R’ for Receivables and p_gl_date = GL Date for the
transaction
4.3.2 Intercompany or Intracompany Accounts are Not Valid
Intercompany or Intracompany balancing accounts are not valid.
Solution
Intercompany and Intracompany balancing accounts should comply with the following:
a.
Enabled flag should be checked.
b.
Posting flag should be checked.
c.
Transaction GL date should be between the start date and end date for the CCID.
d.
It should not be a summary account.
e.
It should not be a control account.
Navigation
1.
Note down all the accounts returned by the query in point 11 of section 4.3.1
2.
Use below query to fetch all the intracompany accounts:
SELECT NVL((SELECT DECODE (p_acct_type, 'D', accts.dr_ccid, 'C', cr_ccid)
FROM fun_balance_accounts accts
WHERE accts.template_id
= p_template_id
AND accts.dr_bsv
= p_dr_bsv
AND accts.cr_bsv
= p_cr_bsv),
NVL((SELECT DECODE (p_acct_type, 'D', accts.dr_ccid, 'C', cr_ccid)
FROM fun_balance_accounts accts
WHERE accts.template_id
= p_template_id
AND accts.dr_bsv
= p_dr_bsv
AND accts.cr_bsv
= 'OTHER1234567890123456789012345'),
NVL((SELECT DECODE (p_acct_type, 'D', accts.dr_ccid, 'C', cr_ccid)
FROM fun_balance_accounts accts
WHERE accts.template_id
= p_template_id
AND accts.dr_bsv
= 'OTHER1234567890123456789012345'
AND accts.cr_bsv
= p_cr_bsv),
(SELECT DECODE (p_acct_type, 'D', accts.dr_ccid, 'C', cr_ccid)
FROM fun_balance_accounts accts
WHERE accts.template_id
AGIS Accounting Issues
= p_template_id
AND accts.dr_bsv
= 'OTHER1234567890123456789012345'
AND accts.cr_bsv
= 'OTHER1234567890123456789012345')))) ccid
Oracle Confidential - For internal use only
Page 14 of 20
From Dual;
Where p_template_id = template id, p_dr_bsv = debit bsv, p_cr_bsv = credit bsv
and p_acct_type = ‘D’ for Debit Account and ‘C’ for Credit Account
3.
Responsibility  General Ledger.
4.
Setup: Accounts  Combinations.
5.
Search for the CCID’s as fetched in point 1 and 2.
6.
For all the above CCID’s the ‘Enabled Flag’ and ‘Posting Flag’ should be checked.
7.
The GL date for the transaction should between the Start date and End date for the CCID’s.
8.
The CCID’s must not be a summary account.
OR
9.
Optional: - Below query can be used to validate a ccid:
SELECT 'Valid account'
FROM GL_CODE_COMBINATIONS CC
WHERE <CC_ID> = CC.CODE_COMBINATION_ID
AND CC.DETAIL_POSTING_ALLOWED_FLAG = 'Y'
AND CC.ENABLED_FLAG = 'Y'
AND CC.SUMMARY_FLAG = 'N'
AND CC.TEMPLATE_ID IS NULL
AND (TRUNC(<GL_DATE>) BETWEEN
TRUNC(NVL(CC.START_DATE_ACTIVE,<GL_DATE>))
AND TRUNC(NVL(CC.END_DATE_ACTIVE,<GL_DATE>)))
AND NVL(CC.REFERENCE3, ‘N’) = ‘N’;
4.3.3 Accounting Flexfield Setup is not correct
Transacting BSV and Trading Partner BSV not available or are disabled in the Intercompany
segment or Balancing segment value set of the accounting flex field.
Solution
Transacting BSV and Trading Partner BSV should be available and enabled in the Intercompany
segment and Balancing segment value set of the accounting flex field.
Navigation
1.
Identify the Accounting Flexfield attached to the ledger and the Intercompany segment and
Balancing segments in the Accounting Flexfield using below Query:
SELECT flex.id_flex_structure_code "Chart Of Accounts",
'BALANCING',
fun_bal_pkg.Get_segment_index(ledgers.chart_of_accounts_id,'
GL_BALANCING') "Balancing Segment",
'INTERCOMPANY',
fun_bal_pkg.Get_segment_index(ledgers.chart_of_accounts_id,
'GL_INTERCOMPANY') "IC Segmnet"
FROM gl_ledgers ledgers,
fnd_id_flex_structures flex
WHERE ledgers.ledger_id = <Ledger_ID> AND
AGIS Accounting Issues
Oracle Confidential - For internal use only
Page 15 of 20
flex.id_flex_num = ledgers.chart_of_accounts_id AND
flex.id_flex_code = 'GL#';
2.
Responsibility  General Ledger
3.
Setup: Financials: Flexfields: Key  Values
4.
Search for the BSV in both Intercompany segment and balancing segment value set of the
accounting flex field.
5.
Check that the BSV’s are enabled.
4.4 Error messages encountered while Create Accounting/Posting a GL Journal
Symptoms
Following error code encountered while create accounting or posting a GL Journal:
1.
FUN_INTER_PAY_NO_DEFAULT
2.
FUN_INTER_PAY_NOT_ASSIGNED
3.
FUN_INTER_PAY_NOT_VALID
4.
FUN_INTER_REC_NOT_ASSIGNED
5.
FUN_INTER_REC_NO_DEFAULT
6.
FUN_INTER_REC_NOT_VALID
7.
FUN_INTRA_CC_NOT_VALID
8.
FUN_INTRA_CC_NOT_CREATED
9.
FUN_INTRA_CC_NOT_ACTIVE
Navigation
Follow steps as listed in Section 4.3
4.5
FUN_INTRA_NO_CLEARING_BSV
Symptoms
Following error code encountered while create accounting or posting a GL Journal:
FUN_INTRA_NO_CLEARING_BSV
Please note that the clearing BSV is not used for Intracompany transactions entered from AGIS
and is only used for manual journals entered from GL. (Ref bug: 7540087)
Cause
Above error occurs if the intracompany transaction requires a clearing BSV for balancing but the
balancing api cannot find one.
Solution
AGIS Accounting Issues
Oracle Confidential - For internal use only
Page 16 of 20
Clearing BSV should be defined for the Intracompany rule.
OR
A Clearing BSV should be entered while creating the GL Journal.
Navigation
AGIS Accounting Issues
1.
Responsibility  General Ledger.
2.
Setup: Financials: Accounting Setup Manager  Accounting Setups
3.
Search for the ledger and click on Update Accounting Options icon.
4.
Click on Update icon for ‘Intracompany Rules’.
5.
Click on define rules icon for the appropriate legal entity/No Legal entity Context.
6.
Click on update icon for the intracompany rule with appropriate source and category.
7.
Click on the Options tab.
8.
User can choose one of the following as the Default Option:
a.
Manually Entered Clearing Balancing Segment: user must enter a clearing BSV
while entering the GL Journal.
b.
Default Clearing Balancing Segment Value: user must enter a default BSV valid for
the selected legal entity context in the ‘Default Clearing Balancing Segment Value’
field.
c.
Default Rule: the default rule with Debit BSV ‘All Other’ and Credit BSV ‘All
Other’ will be used to balance the journal.
Oracle Confidential - For internal use only
Page 17 of 20
4.6 Value &VAL for the flexfield segment &SEGMENT does not exist in the value set &SEGMENT
Symptoms
On submitting the ‘Create accounting’ program or posting to General ledger.
Cause
A value does not exist or is not enabled in its corresponding segment value set in the Accounting
Flex field.
Solution
Segment value should be defined and enabled in the corresponding value set in the accounting flex
field.
Navigation
1.
Identify the Accounting Flexfield attached to the ledger and the Intercompany segment
and Balancing segments in the Accounting Flexfield using below Query:
SELECT flex.id_flex_structure_code "Chart Of Accounts",
'BALANCING',
fun_bal_pkg.Get_segment_index(ledgers.chart_of_accounts_id,'
GL_BALANCING') "Balancing Segment",
'INTERCOMPANY',
fun_bal_pkg.Get_segment_index(ledgers.chart_of_accounts_id,
'GL_INTERCOMPANY') "IC Segmnet"
FROM gl_ledgers ledgers,
fnd_id_flex_structures flex
WHERE ledgers.ledger_id = <Ledger_ID> AND
flex.id_flex_num = ledgers.chart_of_accounts_id AND
flex.id_flex_code = 'GL#';
4.7
2.
Responsibility  General Ledger.
3.
Setup: Financials: Flexfields: Key  Values
4.
Search for the value in the value set for the segment as in error.
5.
If the value does not exist, please define it in this value set.
6.
Check that the segment value is enabled.
FUN_INTRA_CLEAR_BSV_INVALID
Symptoms
Following error code encountered while create accounting or posting a GL Journal:
FUN_INTRA_CLEAR_BSV_INVALID
AGIS Accounting Issues
Oracle Confidential - For internal use only
Page 18 of 20
Please note that the clearing BSV is not used for Intracompany transactions entered from AGIS
and is only used for manual journals entered from GL. (Ref bug: 7540087)
Cause
The above error occurs if the clearing BSV used for balancing is not valid. Also, this only happens
if the balancing segment value option code for the ledger is ‘I’ (Specific).
The balancing segment value option code for a ledger can be either ‘A’ (All) or ‘I’ (Specific).
Where ‘A’ means there are no balancing segment values attached to the ledger or any of the legal
entities attached to the ledger. And hence all the balancing segment values available in the chart of
accounts attached to the ledger are valid.
But if user attaches any balancing segment value to the ledger or the legal entity, then only those
balancing segment values can be used in context of the ledger. And hence the balancing segment
value option code for the ledger is ‘I’.
Navigation
1.
Find the clearing balancing segment value used for the transaction.
2.
To find the same, please follow steps as in section 4.5.
3.
User below query to check if the clearing BSV is valid:
SELECT 'FUN_INTRA_CLEAR_BSV_INVALID'
FROM gl_ledgers ledger
WHERE ledger.ledger_id = <LEDGER_ID>
AND ledger.bal_seg_value_option_code = 'I'
AND NOT EXISTS (SELECT 'X'
FROM gl_ledger_le_bsv_specific_v gl_seg
WHERE gl_seg.ledger_id = <LEDGER_ID>
AND gl_seg.segment_value = <CLEARING_BSV>
AGIS Accounting Issues
Oracle Confidential - For internal use only
Page 19 of 20
5.
AND Trunc(<GL_DATE>) BETWEEN
Trunc(Nvl(gl_seg.start_date,<GL_DATE>)) AND
Trunc(Nvl(gl_seg.end_date,<GL_DATE>)));Bug Logging Guidelines
If the above does not help resolving the issues, please log a bug with following documents:
1) Screenshots of the transaction with all the distribution accounts.
2) Screenshots of the Accounting Flexfield Segments with Segment Qualifiers.
(i) For navigation follow Section 4.1
3) Screenshots of Legal entity - BSV associations.
(i) For navigation follow Section 4.2.2
4) Screenshots of Intercompany and Intracompany rules created.
(i)
For navigation follow Section 4.3.1
5) Screenshots of the Code Combinations used in the transaction.
(i) For navigation follow Section 4.3.2
6) Screenshots of the Valuesets for the segments in the Accounting Flexfield.
(i) For navigation follow Section 4.6
7) Output of the Create accounting report.
AND Trunc(<GL_DATE>) BETWEEN Trunc(Nvl(gl_seg.start_date,<GL_DATE>)) AND Trunc(Nvl(gl_seg.end_date,<GL_DATE>)));Bug Logging
Guidelines
Oracle Confidential - For internal use only
Page 20 of 20