Announcements
2,035
We have a PMTRX batch in a printing status in the GL. However, there is no batch in payables with the same batch # (PMTRX00005295). Trying to figure out how this happens....does anyone have any suggestions? Thanks!
*This post is locked for comments
when was the last time you ran check links?
I'd ponder running against the financial and the company series.
make a back up before you do any check links in case something is removed by check links that you need.
as to a utility? I've not heard of anything. Typically you would want the hung transaction to post and the manual JE to reverse to maintain the drill back integrity of the system. I suppose you could use query analyzer to remove the offending records, but getting all the right tables could prove tricky and who knows if anything lingers around if you miss a table when it comes time to run the year end close or another check links finds something and brings the transaction back.
yes - I'm finding that this transaction actually took place in Nov in AP. It looks like the batch has been hanging there in GL10000 but the user went and manually made a JE to post the amounts in the GL. The batch still hangs.
The header part is still in GL10000 but GL10001 does not have the detail/line items.
Is there a utility I should run to remove it from the GL10000? (for audit trail purposes)
ruling out the obvious then we move to more off the wall answers. Do you have users that would use oddball batch id's like PMTRX?
does the last user (LASTUSER) or who posted (USWHPSTD) fields have values in them on the GL10000 table that you can see the batch in? That will lead you at least to which user appears to be hung since the batch is stuck in printing.
hi Deanne
the pmtrx number will be the audit trail code from A/P. Go to the reports - purchasing - posting journals and plug that number including the pmtrx into the transaction journal report.
you should get back a transaction that as Frank implies was posted in the subledger with no batch and therefore is no longer in the a/p subledger to post.
the printing status usually indicates a stuck / hung user. Once the user logs back into that same company they will be prompted to complete processing.
ian
Your posting settings for payables transactions must be set to "Post To" and not "Post Through" GL. Therefore, that batch ID is created from a single PM transaction that was posted in payables.
#1
Almas Mahfooz
3
User Group Leader
Share
Report
All responses (
Answers (
