Journal Approval Workflow Not Routing Correctly For Users based on job level hierarchy
Last updated on MARCH 12, 2018
Applies to:Oracle Fusion General Ledger Cloud Service - Version 220.127.116.11.0 and later
Oracle Fusion General Ledger - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
We notice that the journals are not routing correctly for users who report to the top participant as per the approval workflow rule.
Illustrating below with example:
User xxx reports to DS who is JE Managing Director
User YYYY reports to SP and SP Reports to DS.
As per the approval rule, top participant is JE Managing Director. For journals <100K; journal should be routed for approval only to one level (immediate Manager). This is flowing correctly for all the users other than those who reports to the JE MD.
So when YYYY submits a JE <100K; its routing to SP correctly; however when user xxx submits a journals This is happening with journals of all approval categories-- <100K, Journals between 100K – 1M & Journals between 1M- 7.5M.
The journals with category >7.5 M is flowing correctly (Only to DS and stops after that).
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