R13.19D : Why do allocation rules from old instance still appear after environment clone ?
(Doc ID 2646684.1)
Last updated on MARCH 12, 2021
Applies to:
Oracle Fusion General Ledger Cloud Service - Version 11.13.19.10.0 to 11.13.19.10.0 [Release 1.0]Information in this document applies to any platform.
Symptoms
On : 11.13.19.10.0 version, Capture Transactions-Define Allocations and Period Entries
ACTUAL BEHAVIOR
---------------
User notices allocation rules from old instance still appear after environment clone.
EXPECTED BEHAVIOR
-----------------------
Allocation rules from old instance should not be visible after P2T/Environment refresh/Clone.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. User performed the necessary steps required for Cube after P2T/Environment refresh/clone per note :
What Are The Steps Required for the Cube, FR Reports and Allocations After a P2T? (Doc ID 2104933.1)
2. General Accounting > Journals--Tasks> Generate General Ledger Allocation Process
3. Notice the old allocation rules are still available
Changes
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 |