"Item
exists on Purchase Order Processing transaction and could not be updated."
We need to check this because if they are un checked and you run the process to move the PO’s to History they will be removed and no longer be available.
Once this process is run and all the PO’s are in history for the item that you would want to change the decimal places then run the below process to change the decimal places.
This happens when you try to change the
decimal places for an item and the item exists on a PO. If the PO is closed or
cancelled also it gives this error.
Resolution:
In order to do this the first step is to
move all the PO’s to History and in order to do this you need to check the
Setup in the Purchase Order Processing and see if the below fields are check
marked.
We need to check this because if they are un checked and you run the process to move the PO’s to History they will be removed and no longer be available.
Below is the Process to remove the PO’s to History.
GoTo Microsoft Dynamics GP-->Tools-->Routines-->Purchasing-->Remove
Completed Purchase Orders
Once this process is run and all the PO’s are in history for the item that you would want to change the decimal places then run the below process to change the decimal places.
GoTo Microsoft Dynamics GPàToolsàUtilitiesàInventoryàChange
Decimal Places
-----------------------------------------------------------------------------------------------------------------------
PSTL Tools Inventory Reconciliation
Item Reconciler allows you to reconcile Inventory. The Reconciler’s function is the same as the reconcile functions built into Microsoft Dynamics GP with one exception: only those items that need reconciling will be reconciled using Professional Services Tools Library. This can increase performance if all items don’t need to be reconciled.
PSTL Tools Inventory Reconciliation
Item Reconciler allows you to reconcile Inventory. The Reconciler’s function is the same as the reconcile functions built into Microsoft Dynamics GP with one exception: only those items that need reconciling will be reconciled using Professional Services Tools Library. This can increase performance if all items don’t need to be reconciled.
------------------------------------------------------------------------------------------------------------------------
Where MKDTOPST = 1
(Query to Update the Batch Status and the Marked to post columns to 0)
Begin Tran
Update SY00500
Set MKDTOPST = 0, BCHSTTUS = 0
Where MKDTOPST = 1
Rollback Tran
(Query to check if any records exists for the batch in the table)
Select * from DYNAMICS..SY00800
Delete from DYNAMICS..SY00800
Rollback Tran
(Query to delete any records that exists in this table for the stuck batches)
Begin Tran
Delete from DYNAMICS..SY00801
Rollback Tran
Once the above queries are run then the stuck batches are released and the user was able to repost the batches.
Releasing Stuck Batches While POSTING
In
order to resolve the stuck batch problem run the following queries on the
Company database and DYNAMICS database, please see below for the queries.
(Query to
select the batches that are stuck)
Select * from SY00500Where MKDTOPST = 1
(Query to Update the Batch Status and the Marked to post columns to 0)
Begin Tran
Update SY00500
Set MKDTOPST = 0, BCHSTTUS = 0
Where MKDTOPST = 1
Rollback Tran
(Query to check if any records exists for the batch in the table)
Select * from DYNAMICS..SY00800
(Query to
delete any records that exists in this table for the batches with problems)
Once this is run it will clear all the records and the batches should be fine.
Begin TranDelete from DYNAMICS..SY00800
Rollback Tran
(Query to
Check if any batch records exists in this table)
Select * from DYNAMICS..SY00801(Query to delete any records that exists in this table for the stuck batches)
Begin Tran
Delete from DYNAMICS..SY00801
Rollback Tran
Once the above queries are run then the stuck batches are released and the user was able to repost the batches.
No comments:
Post a Comment