E1: 09: Troubleshooting Indexed Allocations (P09121/R093021)
(Doc ID 1467571.1)
Last updated on JULY 25, 2023
Applies to:
JD Edwards EnterpriseOne General Ledger - Version XE and laterInformation in this document applies to any platform.
Purpose
This document has been created to assist customers on troubleshooting the different scenarios, causes and resolutions for issues related to processing of Indexed Allocations.
Troubleshooting Steps
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
| Purpose |
| Troubleshooting Steps |
| Overview |
| Tables |
| Error Messages |
| a. Error 1838: No Records Selected |
| b. Error 2059: Stop Date Before G/L Date |
| c. Error 065M: Thru date before allocation G/L date |
| d. Error 036S: Zero Amount - No record written |
| e. Error 0069: Posting Edit Code Does Not Allow Entry |
| f. Error 463D: Account Restricted To Adjustment Entries |
| g. Error 2759: Ledger Type Invalid |
| h. Error 160Z: Cannot update balances for LT xx (where xx is Ledger Type). |
| i. Error 09VOID: Voided Doc Available For Inquiry Only |
| j. Error 078I: Fetch from table F0025 failed |
| Scenarios |
| Question 1: Why is the allocation not working for certain document types? |
| Question 2: What setup must be followed for the multi-tiered allocation functionality to work correctly? |
| Question 3: Why does P09121 throw error "Unit Ledger Type Is Invalid" for allocation setup from AU to AU ledger type? |
| Question 4: Why do I get data from prior months after I reset the G/L date in P09121 post running the allocation? |
| Additional Information |
| References |