AGIS Should Not Allow Creation of Batches with Expired Balancing Segments Values (BSV) on Transaction Distribution Accounting (Doc ID 1945986.1)

Last updated on MARCH 25, 2016

Applies to:

Oracle Financials Common Modules - Version 12.1.3 and later
Oracle General Ledger - Version 12.1.3 and later
Information in this document applies to any platform.
AGIS transactions

Symptoms

You have Balancing Segment Values (BSV) that are end-dated in General Ledger at Legal Entity level.
However, the end-dated values are still available in the List of Values (LOV) for the accounting lines when you create an Advanced Global Intercompany System (AGIS) batch.
The batch can be saved, submitted and approved without any error message.
The intercompany accounts are generated using the valid BSV setup in the Intercompany rules, hence the end-dated BSV is balanced with the valid BSV.

Example:
active BSV = 08
end-dated BSV = 38 and 58
The system should only allow batches to be created for BSV 08, however it allows all 3 values.
The batch with distribution lines using BSV 38 is balanced with intercompany account with BSV 08 which is active which is wrong

It is expected that the system prevents the user from using BSVs that are end-dated.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms