Hi All,
I was reviewing my closed batches and realized that a batch that I had previously closed and posted reverted back to closed. I have a printout of the posting report that I ran when I originally posted the batch, but now its become un-posted and I haven't touched it since i posted it. The posting number is #6381. Now, when I run the posting report for this number, it shows up empty. Any suggestions? Should I re-post the batch-- even though I've done the rifs and JSAs with reference to the posting number 6381?
Please help.
Carol Jackson
Associate Administrator
Norfolk Chamber Music Festival
Hi Carol,
At what point in the posting process did you print the posting report? Does it say "pre-post" next to the batch number on the report?
We've run across this when we print the posting report before clicking the "Complete Posting" button in Batch Administrator, and then fail to actually click the Complete Posting button. The posting number is not valid after that if someone else goes in to post a batch a messes up the numbering.
Is this the problem you encountered?
-Michael
Hi Michael,
Thanks for the quick response... unfortunately the batch was posted. I've checked the printout and it doesn't mention anything about Pre-Post
Have you talked to any of your IT staff? It is possible to unpost via the back end. Is it possible someone else found a problem with that post and requested that it be intentionally unposted, perhaps so some change could be made after which it would be reposted?
Since you're seeing that batch with a "closed" instead of posted status and your post report does not say pre-post, I am guessing this is not the case, but just in case I'll mention: we've often seen instances where someone closes the window after printing the post report without hitting "complete posting", as Michael said, but even if the post-er then goes back immediately and clicks complete posting, the post no from the report will be invalid. Someone else doesn't need to post anything else in between. The actual post_no will be up one number. We've often encountered situations where the actual post_no is 1 number higher than what the post report turned in says because of that scenario.