Nothing worked, the batch would keep getting put back into recovery.
https://community.dynamics.com/forums/thread/details/?threadid=a10e43ba-d335-4719-bbbc-495d8061ea4f
RE: Purchasing Batch Posting Interrupted
This seems to have worked. For future readers, here's a summary of what I ultimately did:
1) Kicked everyone out and took a backup of the database
2) Deleted the batch entirely from SY00500.
3) Deleted from PM10000 the three documents that had made it into PM20000 already.
4) Confirmed that in PM00400 the DCSTATUS for those three documents was set to 2.
5) Deleted the one document that was only in PM1000. I deleted it in both PM1000 and PM00400.
After that, the messed up batch was gone, and we were able to void or apply the three open documents left sitting in PM2000.
Thanks again for the help!
-----------------------------------------------------------------------------------------------------
- Log into one machine as sa, run an inventory reconcile on everything
- Log onto another machine as another user and run batchrecovery WHILE the reconcile is running on the first machine
- For some reason, it stops trying to access the lot table, and just recovers the batch correctly.
Associated errors:
Transaction not completed at initiating scripts exit, implicitly rolled back.
Unhandled database exception:
A remove operation on table 'IV_Lot_MSTR' failed because the record couldn't be locked.
Other scripts to use
--Make "posted" transactions available
select PSTGSTUS,BACHNUMB ,* from sop10100 where pstgstus > 0
UPDATE SOP10100 SET PSTGSTUS = 0 where PSTGSTUS =12
UPDATE SOP10100 SET PSTGSTUS = 0 where PSTGSTUS =14
select * from sy00500 where BCHSTTUS > 0 and BCHSOURC = 'sales entry'
update sy00500 set BCHSTTUS = 0, MKDTOPST = 0 where BCHSTTUS > 0 and BCHSOURC = 'sales entry'
update iv10001 set unitcost =12.75 where itemnmbr = 'cdrom'
No comments:
Post a Comment