deepaksachdeva
5th December 2006, 17:13
Hi,
While doing confirm shipment for the released outbound, the system is stucking up and throwing following error message .
Can not confirm shipment #number, corrupt inventory detected in warehouse #warehouse, location , item #Item,
Please suggest.
Deepak
rams141
5th December 2006, 21:08
We can clear corrupt inventory using whcor0200m000, in Baan 5c. I am not sure if this session is available in LN.
you can try this, if its available.
deepaksachdeva
6th December 2006, 12:28
After running this session, the error is still coming.
With regards
Deepak
nidyar
9th December 2006, 12:30
There should be total 5 inventory tables for Inventory:
1. Item
2. Lot
3. Location
4. Warehouse
5. Planned Inventory transactions.
Condition is Inventory on hand, Inventory on Order, Inventory Allocated and Inventory Blocked for a given item should be same in all the tables. If it is different, BaaN Usually gives this kinda error message. This situation will come when you have a conversion factor such that the transaction goes into too many digits after decimal. Also if the server date is modified be someone (Which is a CRIME) same situation may occur.
There is a solution available somewhere in BaaN site. you can modify the inventory to match all the tables through GTM. Try to get the inventory tables list.
Good Luck
deepaksachdeva
9th December 2006, 12:34
Hi nidyar,
Thanks for your feedback, the problem was resolved by correcting records in whinr140 and whinr150 tables for ERP LN 6.1
the allocation was a problem.
Lots of thanks to you for addressing additional info.
With regards
Deepak
There should be total 5 inventory tables for Inventory:
1. Item
2. Lot
3. Location
4. Warehouse
5. Planned Inventory transactions.
Condition is Inventory on hand, Inventory on Order, Inventory Allocated and Inventory Blocked for a given item should be same in all the tables. If it is different, BaaN Usually gives this kinda error message. This situation will come when you have a conversion factor such that the transaction goes into too many digits after decimal. Also if the server date is modified be someone (Which is a CRIME) same situation may occur.
There is a solution available somewhere in BaaN site. you can modify the inventory to match all the tables through GTM. Try to get the inventory tables list.
Good Luck
nidyar
9th December 2006, 12:35
By the way I believe that you have run the session whcor0200m000 in the update mode.
deepaksachdeva
9th December 2006, 12:37
By the way I believe that you have run the session whcor0200m000 in the update mode.
no, i have corrected thru GTM.
Regards
Deepak