Cross Validation Rule Wrongly Applies when Accounting Code Combination Does Not Exist
(Doc ID 2449177.1)
Last updated on JULY 07, 2020
Applies to:Oracle Application Object Library - Version 12.2 and later
Oracle General Ledger - Version 12.2 and later
Information in this document applies to any platform.
On a recently migrated instance (from 12.1.3 to 12.2.7) several account combinations cannot be created due to cross validation rules being applied incorrectly. The cross validation rule should not block these code combinations because they are not affected by the rule.
In version 12.1.3 the same exact cross validation rule does exist, was not modified for several years, and it does not block the same code combinations from being created.
If the rule is deactivated another active rule is applied, even though it is also not applicable.
If all cross validation rules are deactivated, then the combination is created. Then if all rules are activated again the same issue happens as before.
Tried to compile the Accounting flexfields without any results.
Migrated instance from 12.1.3 to 12.2.7
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document