InventoryValue
Updated
On-hand stock value by item. A receipt raises quantity and amount. A net issue writes both down by the cost taken off the layers. The cut is the item, not the cell.
| Kind | Accumulation register |
| Module | Costing |
| Menu | Costing → Registers → Inventory value |
Dimensions and resources#
| Name | |
|---|---|
| Analytic | Item → Item, required |
| Resource | Value |
| Resource | Qty |
There are no schema dimensions. The Item analytic is required. The register is not double-entry. It allows a negative balance. A cell, lot, or expiry-date slice is not in the product: the cut is the item only.
Qty here is the quantity that carries cost, in the item's base unit. Stock is physical on-hand by cell. A transfer between cells does not move this register.
The delivered layout Inventory value by item groups by item and has Non-zero balance on, so a row whose closing Qty and closing Value are both zero is left out.
Written by#
PurchaseOrder on Received raises it from the receipt lines. A surplus on StockAdjustment or StockCount raises it at the current average, or at the planned unit when there are no layers.
A net stock issue writes it down: SalesRealization, GoodsIssue, PurchaseReturn, a shortage on StockAdjustment or StockCount, and component consumption on ProductionOrder. The amount is what ItemCostFifo gave up. StockTransfer nets to zero and does not write this register.
When ProductionOrder is Finished, the product layer is opened and this register is raised by that amount.
How the issue amount is chosen is Costing method. Costing has no document of its own: value follows receipts, issues, and production.