What is the posting status (PSTGSTUS) in the PM10000 table?
10 = Transaction being entered for the first time before it has been saved by the used
20 = Saved but unposted transaction
30 = Transaction that is currently realtime posting
40 = Posted transaction
50 = Transactions that has encountered an error during posting
60 = Transaction that has been saved previously and has a status of 20 is now being edited by a user
70 = Transaction that has been posted previously in a recurring batch that still contains unposted transactions is now being edited by the user
Look in the SY00500 for the field BCHSTTUS and check it's value against the list below. It will give you a good idea of how far through the process your transactions were.
0 Available
1 Batch Posting
2 Batch Being Deleted
3 Batch Receiving Transactions
4 Batch Done Posting
5 Batch Being Printed
6 Batch Being Updated
7 Interrupted While Posting
8 Interrupted While Printing
9 Interrupted While Updating
10 Recurring Batch Errors / Transactions Did Not Post
11 Single Batch Error / Transactions Did Not Post
15 Error While Posting Computer Checks
20 Interrupted While Processing Computer Checks
25 Interrupted While Printing Computer Checks Align
30 Interrupted While Printing Computer Checks
35 Interrupted While Printing Computer Checks Align Before Reprint Computer Checks
40 Interrupted While Voiding Checks
45 Interrupted While Reprinting Checks
50 Interrupted While Processing Remittance Report
55 Interrupted While Processing Remittance Report Align
60 Interrupted While Printing Remittance Report
100 Processing Computer Checks
105 Check Align Being Printed Before Print Checks
110 Printing Computer Checks
115 Check Align Being Printed Before Reprint Checks
120 Voiding Computer Checks
125 Reprint Computer Checks
130 Remittance Report
135 Printing Remittance Align Form
140 Printing Remittance Form
Typically, there's nothing you can do to free it up except change it's status in the SY00500 table. I'm sure Soma's KB article has some other tips on how to free it up. It's likely your batch didn't update any of the transaction tables and you can just free it up, backup your database, and try again.
Kind regards,
Leslie
