Had an instance where a SOP clerk created an invoice from an order and then posted it directly (i.e. not via a batch) She was able to print it but then could not go back into Sales Transaction Entry as GP claimed there was a transaction that had not completed. As it was a "posted invoice" I did not want to just delete the invoice form SOP10100 and SOP10200 and clear SY00500 and have her start again as I did not what had occurred and how far GP had gone in the posting process before it hung. After many days of deleting the stuck batch in SY00500 each morning I found a script that allowed me to search the entire database for my SOP Number. It also brought up some JE numbers and DEX_ID numbers that were identical (another reason to use Alpha Numeric for sop numbers). I satisfied myself that the process had not hit any historical or posting tables and also showed me what work tables the invoice had hit. Basically it only was in SOP10100 and SOP10200 plus tax and udf tables in the work tables.
I found that the BCHSOURC field only allows certain values. The proper value for that type of transaction is 'Sales Entry' however in my SOP10100.BCHSOURC record for the messed up invoice it was '*Sales Entry'. Where the star came from I have no idea. After checking my tax tables to make sure that the information was correct and all items were accounted for I did a sql update to remove the star on the SOP10100.BCHSOURC record for the SOPNUMBE record of the invoice. I was then able to open the invoice as an open and not posted transaction. I saved the invoice to a newly created batch and then posted the batch. The posting routine gave me a distribution record that was spot on. Of course I would also recommend doing this first on a sample or backup copy first and the usual rules about directly editing the database via sql apply. Hope this helps someone from spending way too many hours over what should be a relatively easy solution.
*This post is locked for comments
I have the same question (0)
