CostingSettings
Updated
Company-wide costing flags. The method values every stock issue. One row: the menu opens the card for editing. There is no list and no delete.
| Kind | Dictionary |
| Module | Costing |
| Menu | Costing → Settings → Costing settings |
| Singleton | yes |
Fields#
| Field | Caption | Points at |
|---|---|---|
ID |
ID | number sequence |
ValuationMethod |
Costing method | CostingMethodKind |
CostingMethod |
Costing method (AVG/FIFO) | string, 128, hidden |
RoundCosts |
Round costs | boolean |
StandardPriceType |
Standard cost price type | PriceType |
ID comes from CostingSettingsSeq, which starts at 1 and steps by 1. None of the fields is required.
Costing method is Not set, FIFO, or Weighted average. Save writes FIFO or AVG into the hidden string. Not set does not erase a stored code. An empty code, and a missing row, both value the next issue as FIFO. The method is read when the issue is posted.
Round costs off leaves the issue amount as the layers gave it. On rounds that amount to 2 decimal places, midpoint away from zero.
Empty Standard cost price type uses the oldest active Base type with direction Internal. That type is the planned unit price. Issues still take cost from ItemCostFifo layers.
How an issue is valued, and how to read Inventory value, is Costing method.
LIFO is not in the product. The method is company-wide; there is no method per item or per store. Changing the method does not rewrite issues already posted. Costing has no document of its own; value follows receipts and issues.
Hierarchy#
This dictionary is not hierarchical.
Who references this#
No object stores a CostingSettings field. The issue driver on Stock reads Costing method and Round costs. Planned unit cost reads Standard cost price type.
There are no commands. This dictionary writes no register.