RE: Purchasing - Recurring Batch Error Edit Required
Hi mhernley86,
With a non-check batch, the error is likely caused by work records stuck in the PM10000 table. What usually occurs is that the transactions do post to the OPEN tables, but the batch and WORK records are not cleaned up properly due to an interruption. However, deleting the batch is not advised as that removes the Key record (can be recreate using Check Links) and Distribution records (cannot be recreated) for the documents and would leave orphaned transaction data in the tables, and disconnected journals if the documents posted to the General Ledger as well.
Without a full review of the batch and transaction data, I can't provide specific guidance on how to correct the issue, but typically the solution is to remove the duplicate PM10000 records and the batch header from the SY00500 using SQL statements, but there may be other issues to correct as well like incorrect document status or no GL records. Of course, we would always do this in a TEST company first to verify the results. To provide a specific and accurate solution, we'd need to review the status of the data in many different tables, such as looking at the document status in the PM00400 Key Master, checking if everything posted through to the PM20000 Open Transaction table, and if the GL records were created.
Fixing data damage like this is not a service we can provide do outside of a support case, but we'd be happy to take a look if you do open a case.
Please let me know if there are any other questions regarding this issue!
Share
Report
All responses (
Answers (
292,234
