Hello

I have a problem in Inventory control. There are 2 items that have diffrent Quantities on Hand and quantities in costing.
These items looks like they were received properly in Purchase Order. Inventory Control accout and GlL is now out of balance
How can i correct this?

Thank you

Huh? Quantities on hand and Quantities in Costing? Where are you referring to?

Hi Henry,

Run Day End in Order Entry and Purchase Orders. The quantities in the FIFO costing lots are not relieved until OE Day End is run, though the quantity on hand displayed in item inquiry are re-calculated based on the value of the 'Qty Shipped not Costed' value for the item.

You should find that after running Day End in OE, the quantities will match, and GL will be better, since it is Day End that generates the GL transactions.

Day end has done several times after this problem appear. I've also done data intergrity in PO an I/C.
I don't know what else do do

Hi Andrew,

When i go to Item inquiries w/ Sales & Cost - Quitities I see in Costing tab is dif from what i get if i go to Quantities tab
These problem's been there for about a month now

Hi Andrew

IC - Item iquiry with sales and Cost
If I go to Costing Tab the total quantities is not the same as the Qty on Hand when I go to Quantities Tab

Hi Henry,

What versions of Adagio Inventory and Order Entry are you using? Check the Help / About screens for the version and release date.

When you are on the Costing tab of Item Inquiry, are you looking at the 'Qty on hand' field to determine the Total quantity, or are you looking at the FIFO/LIFO costing lots at the bottom of this screen?

The Quantity on Hand value that is displayed on the Costing tab of 'Item Inquiry with Sales and Costs' is a calculated value, using the field value Qty on Hand minus the Qty Shipped Not Costed. If you use the Column Editor and include both of these fields as new columns, what do you see for an item that has a discrepancy? Since you indicated that you have run Day End Processing in OrderEntry, the Qty Shipped not Costed must be zero - if it is not then your data is corrupted.

If your items use FIFO or LIFO costing methods, you will see the 5 costing lots and the respective quantities and costs for each lot. These quantities will appear to be out of synch with the above calculated Qty on Hand if an item has been shipped in OE and not processed by Day End. This item will have a non-zero Qty Shipped not Costed and this value will be the difference.

On the Quantities tab of Item Inquiry with Sales and Costs, a different data file stores the different quantities for your locations. This includes on hand, on sales order, on purchase order and also qty shipped not costed. This grid cannot have the columns changed or added to, but the respective Qty shipped not costed values for each location must also be zero after Day End has been done, otherwise your data is corrupted. You or your Adagio consultant could look at this file with GridView to inspect the stored values.

Much older versions of Adagio OrderEntry had problems in recalculating these values when orders were deleted, and the current version works correctly, and the integrity check also finds and fixes the problems caused by this error.

Hello,
We use IC 8.1C & OE 8.1D an d we also PUrchase Order for Adagio

The Costing tab should also be updated after day end is done in POA, isn't it? I think this might be whenre the diff is coming from. There were some receipt where items were not updated in costing but were updated in Quantities. I thought it would correct itself after data integrity but it did not

All quantities are updated by Purchase Orders when posting the Receipt. Running Day End in PO is not necessary to update quantities.

If the sum of the quantities from all locations does not equal the quantity on hand for the item, there is no 'qty shipped not costed' values for the item or locations, and the integrity check does not find nor repair the difference, then the data is corrupt and needs to be repaired.

You probably want to get your Adagio consultant involved at this point.

Thank you