Tuesday, April 11, 2017

Dynamics GP - Stuck SOP documents - This order has already been posted

https://community.dynamics.com/gp/b/gplearn/archive/2009/12/14/sop-34-this-document-has-been-posted-34-error-38-resolution

----------------------------------------------------------------------
--Check which tables have data
----------------------------------------------------------------------
select * from sop10100 where sopnumbe = '11746'
select * from sop30200 where sopnumbe = '11746'
select * from sop30300 where sopnumbe = '11746'
------------------------------------------------------------------------
--If the transaction is not in the GL, it did not post
------------------------------------------------------------------------
select * from gl10000 where DTAControlNum = '11746'
select * from gl20000 where orctrnum = '11746'
select * from gl30000 where ORCTRNUM = '11746'
------------------------------------------------------------------------

Sometimes, when an sop transaction gets stuck or corrupted, you may not be able to reopen it.

Ensure that you update the CUSTNMBR, BACHNUMB and BCHSOURC fields to allow the transaction to be visible in the SOP lookup menu.


update sop10100 set custnmbr = 'AARON001',BACHNUMB = 'RECOVER', bchsourc = 'Sales Entry' where sopnumbe = 'ORD001'

No comments:

Post a Comment