WS: 03: Troubleshooting Posting Errors in Accounts Receivable (P098012, P09800)
(Doc ID 1510152.1)
Last updated on JULY 07, 2021
Applies to:JD Edwards World Accounts Receivable - Version A7.3 cume 4 and later
Information in this document applies to any platform.
To describe how to correct errors on the Batches with Balancing Problems report (P098012) and the Posting Edit Report (P09800) as a result of posting Accounts Receivable batches.
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
|Posting Edit Report (P09800)|
|Issue 1: Intercompany account not set up in Account Master file|
|Issue 2: Batch not approved for posting or not authorized to post this batch|
|Issue 3: Account not set up in Account Master file or invalid model account|
|Issue 4: Automatic Accounting Instruction is not set up in F0012|
|Issue 5: Intercompany settlements detected|
|Issue 6: G/L date is PBCO, and PBCO posting is not allowed|
|Issue 7: Invalid Subledger and/or Subledger Type|
|Issue 8: The Posting Edit report is blank|
|Issue 9: G/L date within batch is out of balance|
|Issue 10: Ledger type and document type must be valid codes in User Defined Codes|
|Issue 11: There is a difference between the amount on the Batch Header Screen and the amount on the Cash Receipts Journal Review Screen and the difference is the amount of a receipt that was deleted from the batch. Is the batch out of balance now?|
|Batches with Balancing Problems Report (P098012)|
|Issue 1: The invoice amount (F0311) does not balance to the G/L distribution amount (F0911).|
|Issue 2: An invoice (F0311) record is missing.|
|Issue 3: The transaction has taxes and the tax rate area changed between the time the transaction was entered and the time it was posted.|
|Issue 4: A receipt batch is out-of-balance|
|Issue 5: The post program is not running in a single-threaded job queue|
|Issue 6: CA Ledger is out of balance|
|Issue 1: The Post program erroneously runs P51801 and P51802 or erroneously updates the Last Update fields on F0911 records|