My Oracle Support Banner

Running Revaluation Does Not Detect Hierarchy Changes Used In The Revaluation Condition (Doc ID 2383044.1)

Last updated on APRIL 12, 2018

Applies to:

Oracle Fusion General Ledger Cloud Service - Version 11.12.1.0.0 and later
Oracle Fusion General Ledger - Version 11.1.10.0.0 and later
Information in this document applies to any platform.

Symptoms

On :  11.12.1.0.0 version, Capture Transactions-Define Allocations and Period Entries

When running the revaluation process, the journal generated still uses an OLD child company value that was removed from the parent used in the revaluation rule.

Example:
Old hierarchy had companies 7827 and 7828 under the ABC parent.
This hierarchy was updated via DRM and the child 7827 was moved out leaving only 7828 under ABC.
When the revaluation process is run the journal lines still uses the 7827 even though it is no longer a child of ABC.


It is expected that the Revaluation journal created does not use the company 7827 since is no longer a child of ABC and the journal created uses the company 7828

STEPS
-----------------------
1. Setup a revaluation rule using the condition:
COA: YZX, Conversion Rate Type: PeriodEnd, Income Statement Account Basis: YTD
Condition: Company is last descendant of ABC AND Account Equals to 1111111

2. Have initially 2 children under ABC:  7827 and 7828 in the hierarchy used to revaluation and linked to the Company segment

3. Remove one of the children from ABC

4. Run Online Flattening and Audit

5. Run revaluation and still company value 7827 is picked up when it should not.


Changes

Move children from one parent to another.

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.