Unexpected Behavior on Changing Segment Qualifier 'Control Account' - Y/N, N/Y in the Same Session
(Doc ID 1578763.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle General Ledger - Version 12.0.0 to 12.1.3 [Release 12.0 to 12.1]
Information in this document applies to any platform.
Per standard functionality, changing an account qualifier (eg. Control Account qualifier) should be accompanied by running concurrent program 'Inherit Segment Value Attributes' to reflect the qualifier changes in the account code combinations.
The users performed a few tests changing Control Account qualifier in the same session without running 'Inherit Segment Value Attributes' program and noticed the behavior is weird.
See below an example of test-case for changing Control Account qualifier at segment value level(remember the code combinations are not updated with the qualifier change until 'Inherit Segment Value Attributes' program is submitted). The same would reproduce for changes of other segment value qualifiers. Tests results may be slightly different depending on the changes made, because the segment value setup is validated at the time the value is selected for usage, while the code combinations might only be validated at save/post processes.
1. Current setup: Control Account qualifier - account segment value: Yes (Y) / code combinations level: Yes (Y).
This combination allows no manual GL journal entries as Control Accounts should not be used in GL journals.
2. Change the qualifier at account level=N, save, check that 'Compile value set hierarchies' was run and completed
3. Run the Inheritance program and make sure it ends fine.
At this point check the qualifier at segment value=N and code combination level=N. GL journal entry is possible.
4. Change the qualifier at account level from N to Y, save, make sure the concurrent 'Compile value set hierarchies' ends fine.
At this point check the qualifier at segment value=Y and at code combination level=N.
The user is unable to create manual journal in GL now. This is normal behavior as the account segment value is showing Control Account hence it should not be used in journals.
5. Change the qualifier at account level from Y to N, save, make sure the concurrent 'Compile value set hierarchies' ends fine
At this point check the qualifier at segment value=N and at code combination level=N.Basically we should be back at step3 here.
The user is unable to create manual journal in GL now which is unexpected because both the account and code combination are not set as Control Accounts.
6. Noticed that if the application is closed and the user logs back in, the same setup in step5 works and allows a journal entry in GL.
Changes for segment qualifier performed without running the Inheritance program.
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|