1/3/2020 Document 1546975.

1
Copyright (c) 2020, Oracle. All rights reserved. Oracle Confidential.

R12: AP: How to resolve Create Accounting Errors in Payables Due to Invoice or Payment
Accounts Having the Wrong BSV? (Doc ID 1546975.1)

In this Document

Goal
Solution
References

APPLIES TO:

Oracle Payables - Version 12.0.0 and later

Information in this document applies to any platform.

GOAL

How to resolve the following Create Accounting errors in Payables due to invoice/payment accounts having wrong BSV.
Errors like:

MESSAGE_NUMBER: 0

MESSAGE_NAME: XLA_INTRA_RULE_NOT_ASSIGNED

MESSAGE_TEXT: The subledger journal entry does not balance by balancing segment and there is no Intracompany Balancing
Rule defined
for the ledger &LEDGER_NAME, source &SOURCE_NAME and journal category &JE_CATEGORY. The ledger option
Intracompany Balancing is enabled,
but no balancing rules are defined for the ledger. Please update the journal entry setups for the application accounting
definition so that
the journal entry balances by balancing segment, or define a cross-entity balancing rule for the ledger.

MESSAGE_NUMBER: 0

MESSAGE_NAME: XLA_INTER_BSV_NOT_ASSIGNED

MESSAGE_TEXT: The subledger journal entry contains lines with balancing segment values that are not assigned to any legal
entity.
Unassigned balancing segments cannot be used to balance a subledger journal entry with balancing segments already
assigned to a legal entity.
Either update the balancing segment value assignments for the ledger &LEDGER_NAME or update the balancing segment
values used on the subledger journal entry.

MESSAGE_NUMBER: 95277

MESSAGE_NAME: XLA_AP_IC_POST_FLAG_OFF

MESSAGE_TEXT: The subledger journal entry does not balance by balancing segment and the ledger option Balance Cross-
Entity Journals
is not enabled for the ledger &LEDGER_NAME. Please update the balancing segment values for each line so that they balance
or enable
the Balance Cross-Entity Journals option for the ledger &LEDGER_NAME.

MESSAGE_NUMBER: 95311

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=jx09ubkg0_4&id=1546975.1 1/3
1/3/2020 Document 1546975.1

MESSAGE_NAME: XLA_AP_INVALD_BAL_SEG

MESSAGE_TEXT: The &SEGMENT_NAME segment value for the account code combination &ACCOUNT_VALUE specified in line
&LINE_NUM is not assigned
to the ledger &LEDGER_NAME. Please update the &SEGMENT_NAME segment value assignments for the ledger in the
Accounting Configuration page
or use another &SEGMENT_NAME segment value.

SOLUTION

Solution Options:

Solution Option 1: Change the account.

If the error is occurring for an invoice distribution or liability account entered with an incorrect BSV, you may be able to
change the account. Review the Payables User’s Guide "Invoices Adjustment Chart" to see if the Liability account should be
updatable. Review the Payables User's Guide "Invoice Distribution Adjustment Chart" to see if the invoice distribution account
should be updatable. You can also review the same in Doc Id 1300685.1. To update the Liability account, use Folder > Show
Field to show the Liability Account in the invoice header. To update the invoice distribution, you have to select the line with
the distribution you want to update, and then click on Distributions from there if you want to update a validated distribution.
If the invoice is paid, you must also have the "Allow Update to paid Invoices" option enabled.

If the error is for Payment cash or cash clearing accounting and the bank account cash or cash clearing account has a wrong
BSV, see Doc Id 456360.1 for details on how to update the bank account cash or cash clearing account.

Note: If the Adjustment charts show that the account should be able to be updated, but the field is greyed out, try
changing the status of the invoice to "Needs Revalidation". You can do that by selecting a line already entered and then
click on Distributions. After that, you just need to make a change like clear out account/amount and then put same
account/amount back. Or add a zero dollar distribution. Those actions should make the status change to "Needs
Revalidation".

Solution Option 2: Enable Automatic Offsets/Pooled accounts to avoid creating inter/intra company scenarios. See Oracle
Payables User's Guide or Note 134117.1 for more details on Automatic Offsets/Pooled accounts.

Solution Option 3: Complete intra/inter company setup.

You can do specific setup for the BSVs involved or create a generic "all other" setup to process the accounting.
Here are the documents needed to complete specific or generic inter/intra company setup:

1. Oracle® Financials Implementation Guide

2. Note 463472.1 - FAQ-Intracompany Balancing in Release 12
3. Note 579930.1 - Intracompany Balancing In Release 12
4. Note 604441.1 - Setting Up Intracompany And Intercompany Accounting - An Example

For generic setup, focus on the Doc Id 604441.1 "Set up Intracompany Balancing Rules " section.
You can disable the setup after the accounting is created, but it is recommend to leave enabled in case of future BSV user
entry errors.

Note: If you completed intra/inter company setup and are still getting errors. Run the Create Accounting Analyzer from
Doc Id 1665706.1 to troubleshoot your intra/inter company setup.

Solution Option 4: If invalid BSV combination is due to bug 7531219, apply solution from GDF Doc Id 1272440.1 to
update/change the account.

Solution Option 5: You have entered wrong BSV combination that includes one or more BSVs assigned to the Ledger and one
or more BSVs assigned to an LE. The BSV assignments done at the Ledger level must be removed and same BSV must be
assigned at LE level. Solution Option 3 must also be completed. The BSV LE assignment can be end dated if needed.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=jx09ubkg0_4&id=1546975.1 2/3
1/3/2020 Document 1546975.1

Solution Option 6: If no accounting has been created for the invoice and the invoice is cancelled or could be cancelled, the
solution from Doc Id 2197818.1 may be an option. The solution from that document will allow you select an Action for
cancelled invoices that have no accounting created to 'Set Accounting Events to No Action'. Meaning no accounting is needed
and none will be created. Review the document for more details and make sure you test the solution before migrating to
PROD.

Prevention Options:

Prevention Option 1: Setup Security rules to prevent wrong combination of BSVs from being entered.

Prevention Option 2: Assign BSVs to the LE. It is not mandatory to assign a BSV to ledger or LE. If BSVs are assigned to the
ledger/LE, the invoice workbench validates BSVs entered against the BSVs assigned to the Ledger/LE.

Note: Assign balancing segment values to ledgers if you want to use specific values to represent non-legal entity related
transactions, such as adjustments. If you use legal entities, you must assign balancing segment values to all legal entities
before you can assign values to the ledger. It is not recommended to have BSVs assigned to a ledger if you have BSVs
assigned to LEs. Do all BSV assignment at Legal Entity level or Ledger level.

Prevention Option 3: Make sure patch for bug 7531219 is applied to make sure BSVs entered on the invoice workbench are
correctly validated.

REFERENCES

NOTE:1300685.1 - R12.1 / R12.2: Invoice and Invoice Distribution Adjustment Charts - Explains what Fields can be Adjusted
on an Invoice and when the System Prevents Update
Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=jx09ubkg0_4&id=1546975.1 3/3