GP Document Locked by Accellos Warehouse Unable to …

Working in GP Dynamics with the Accellos One warehouse management (WMS)  integration will change the way GP interacts with inventory as the WMS becomes the “parent” of your inventory. As with most parent / child relationships the parent dictates what happens with the child. In this case, any GP document that deals with inventory is directly tied to the WMS. That being said I have come across two common errors that will lock a document in “no-man’s land” and leave the GP end-user stuck and frustrated. The fix is rather easy for your typical GP / WMS administrator. Below are the two errors I have run across the most:

1. GP document locked by warehouse unable to edit.
2. GP document locked by warehouse unable to post.

Both of these errors stem for the same root cause. GP thinks that the WMS has the documents in use therefore locking them by design to keep inventory straight. In most cases, your typical WMS dispatcher can unlock the documents for your GP end-user and everyone moves about their day. However, there are a few cases where the WMS shows the document “released” and GP shows the document as “locked”. This is the error that I will address in the fix below.

Step 1. 
Query the GP table SY00801 table to determine what USERID has the document locked. 9 times out of 10 you will find that the USERID is associated with the USERID that is running the integration piece that syncs GP to the WMS. Use the query below to find out:

select userid, rsrcid from sy00801

The userid column will show which GP user is tied to the document.
The rsrcid column will show a document this is open.

If the “locked” document in question is tied to the GP user that syncs the WMS integration proceed to step 2.

Step 2:
Alert the appropriate personnel within your company that you will be disconnecting the GP to WMS integration piece for a few minutes. This is important because disconnecting the sync will stop all flows between GP and the WMS and will open up the chances of inventory count error under certain circumstances.

Step 3:
Shut down the GP to WMS integration. In our case its called OpsCore by Blue Moon.

Step 4:
Log the GP user directly tied to the GP to WMS integration out of GP and shut down the GP instance on the computer running GP.

Step 5:
Query the GP table sy00801 as you did in step 1. I have typically seen that the USERID still shows logged in and attached to the “locked” document.

Step 6:
Relaunch GP and login as the user that is tied to the integration.

Step 7:
Query the GP table sy00801 as you did in step 1. I have typically seen that the USERID still shows logged in and attached to the “locked” document.

Step 8:
Restart the GP to WMS integration and give it time to resync GP to the WMS and run all queued transactions.
** At this point the document will typically release **

Step 9:
Query the GP table sy00801 as you did in step 1. At this point the USERID will not be associated with the “locked” document.

Step 10:
Access the documents that needed to be edited or posted.