GLXJEENT: When Approving Journals Having Multiple Lines for the Same Code Combination, the Line Amount Is Used for Approval, Instead of Cumulating the Amounts for the Code Combination First
(Doc ID 2945677.1)
Last updated on MAY 04, 2023
Applies to:
Oracle General Ledger - Version 12.2 and laterInformation in this document applies to any platform.
GLXJEENT: Journal Entry Form
Symptoms
GLXJEENT: Journal Entry Form: a journal is created having multiple lines for the same code combination. Journal Approval with Approvals Management System (AME) integration is in place, using the Line Amount for approval.
It has been observed that each line is getting approved separately, instead of having the lines cumulated first and only the total go through the approval process. This affects the whole approval process as the incorrect amounts or approvers may be selected in the process.
The current behavior creates also a problem where the smaller amounts are set up to be skipped for approval; the users may intentionally break the amounts into smaller pieces/multiple lines to bypass the approval process.
EXAMPLE:
In this example, the expectation would be that the first three lines (100+100+100) would be cumulated and the approval process will be routed to the approver for the amount of 300. Instead, each line of 100 is evaluated for approval and discarded in case the approval limit is higher than 100. This basically allows a breach where the approval process can be skipped.
STEPS TO REPRODUCE:
- Under General Ledger Responsibility > Navigate to Journals > Enter > Find
- Create a new journal on this form GLXJEENT: Journal Entry by using the 'New Journal' button
- Enter a few lines having the same code combination on each line
- Enter any other lines as needed > Save
- Click on 'Approve' button
- See the journal is sending for approval each line separately, the lines using the same code combination are not netted to send one amount for approval
Changes
None
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 |