SubLedger Accounting Issue: Adjustment That is Approved is Showing as Non-Postable in XLA Tables
(Doc ID 1622445.1)
Last updated on APRIL 03, 2025
Applies to:
Oracle Receivables - Version 12.0.0 to 12.1.3 [Release 12.0 to 12.1]Information in this document applies to any platform.
Adjustment that is Approved is showing as Non-Postable in XLA Tables
Symptoms
An Adjustment, that is set to Approved, is showing as NON-Postable in the XLA tables and will not process to the General Ledger.
Steps to Reproduce:
Responsibility: Receivables
1. Create an Invoice
Navigation: Transactions > Transactions
Generated Invoice Number: 13400 for 106.00 dollars. (CTID: 778791)
2. Set Approval Limits for User
Navigation: Setup > Transaction > Approval Limits
Set User limit to -5.00 dollars, so that when an Adjustment is generated, it is in Pending status.
Example: LEPHILLI Currency USD Type Adjustment: Limit -5.00 to 5.00 dollars
3. Make an Adjustment on the Invoice
Navigation: Transactions > Transactions > Query Invoice generated in Step 1
Go To: Actions> Adjust
Enter in Adjustment: 43563 for -15.00 dollars (ADJID 65282)
Adjustment will go to Pending status
4. Review the Adjustment
Navigation: Control > Adjustments > Approve Adjustments
Click Find to Query Adjustment Number 43563 (ADJID 65282) to ensure this is in Waiting Approval
5. Set the User LEPHILLI limits back to -50.00 to 50 dollars
Navigation: Setup > Transaction > Approval Limits
LEPHILLI Currency USD Type Adjustment: Limit -50.00 to 50.00 dollars
6. Both User A and User B have limits Greater than the Adjustment Generated.
Both are accessing the Adjustment 43563 via the Approve Adjustments form.
Navigation: Control > Adjustments > Approve Adjustments Form
7. User A Rejects Adjustment
This sets the status to Rejected and event is in N Non-postable.
8. Now, User B that is still in the form and Approves the same Adjustment
This sets the Adjustment status to Approved, but the event is set to N Non-Postable
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 |
1. Bug Summary |
2. Fixed Files |
3. Recommended Patches |
4. Solution Steps |
5. Identify Possible Data Corruption |
Still Have Questions? |
References |