WS: 09: Troubleshooting Posting Errors for General Ledger (G Type) Batches (P098012, P09800)
(Doc ID 1919736.1)
Last updated on NOVEMBER 22, 2019
Applies to:
JD Edwards World General Ledger - Version A7.3 cume 4 and laterInformation in this document applies to any platform.
Purpose
This document describes how to resolve posting issues for general ledger (G type) batches.
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 |
| Posting Edit Report (P09800)/(P09870 A9.4 and higher) |
| 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: Invalid Subledger and/or Subledger Type. |
| Issue 9: The Posting Edit report is blank |
| Issue 10: Invalid Business Unit or Non-Posting Business Unit |
| Issue 11: Invalid Company Number xxxxx |
| Batches with Balancing Problems Report (P098012)/(P09872 A9.4 and higher) |
| Issue 1: The post program is not running on a single-threaded job queue |
| General Troubleshooting |
| Issue 1: The Post program erroneously runs P51801 and P51802 or erroneously updates the Last Update fields on F0911 records. |
| References |