Using the standard cost model in AX 2009, all receipts and issues are valued at the active cost. Costs are maintained in the item price form, which is available using the Price button from the item form.
A few things to note when looking at the new price/cost form:
1. Price type - 3 price types are available for use
a. Cost - This is your standard cost
b. Purchase price - Will be used as a default on purchase orders
c. Sales price - Will be used as a default on sales orders
2. Version - Costing versions were introduced to provide a way to maintain planned costs. They can be used to plan for future standards and for simulation purposes. Activation of costs/prices can take place at the item level, or can be done for multiple records on the version itself.
3. Site/Item dimensions - Costs can be maintained per site. Site is an inventory dimension, intended to be used for separate physical locations within a single company. Cost calculations do not cross site. An item should have a cost set up at every site where it will be consumed.
4. Activation Date - The most recently activated cost is used, and all history is maintained. Activation of a standard cost cannot be backdated.
5. Pending Prices tab - Anything not yet activated is pending.
Data Model - In AX 2009, the new and old data models run in parallel:
Existing Data model
New Data model
Below is an illustration of how the two data models will work together:
1. ItemA has a standard cost of $100 per unit
2. I created a purchase order line for the item, quantity 1, with a price of $110, and post the packing slip
a. The voucher for this posting is as follows:
$100 - purchase, packing slip
$10 - purchase price variance
-$110 - purchase, packing slip offset
b. The existing data model will result in an inventTrans record with costAmountPhysical = $100 and an inventSettlement record with costAmountAdjustment = -$10
c. The new data model results in an entry to inventCostTrans. The record will have no cost information because we assume the current active cost is used. OnHandQty and AccruedQty (received not invoiced) are updated with the quantity of 1. There is also a record created in inventCostTransVariance with a cost amount = $10.00.
3. I posted the invoice with a new purchase price of $120 per unit
Posting the invoice results in the following voucher:
-$100 - purchase, packing slip
$110 - purchase, packing slip offset
$100 - Purchase, receipt
$10 - Purchase price variance
$120 - Vendor Balance
The inventTrans record is updated with a costAmountPosted of $120 and inventSettlement will have two new records:
InventCostTrans has a new entry with costTransState = Financial. Note that the Accrued quantity represents the quantity change in Received not yet invoiced, which now nets to zero when looking at the two records.
InventCostTransVariance also has a new entry to reflect the additional $10 change in price on the PO line:
4. The standard cost for the item is changed to $130 per unit
The voucher for the revaluation looks like this:
i. -$30.00 - Inventory Cost Revaluation
ii. $30.00 - Purchase, receipt
InventTrans now has a costAmountAdjustment of $10, and there is a new inventSettlement record with an adjustment of $30. To this point, the inventory value was $100, so this settlement brings the value in line with the new activated cost.
inventCostTrans has two new entries and inventCostTransVariance has 1.
Newly introduced variances will capture any difference between an item's standard cost and the actual cost. Here's a breakdown of the new variances:
When executing Inventory close in Microsoft Dynamic AX 2009, the system will check whether the item is Standard cost based or not. If the item is standard cost based, the system will created a new record in the table InventCostTransSum. This is the only interaction standard cost based items have with the Inventory close job.
I was reviewing the GL voucher transactions related to an Item Price Activation. I noticed that there are transactions with "Inventory cost revaluation" posting type besause of the price activation. However, what I'm confused of is that there are some transactions with the "Rounding variance" posting type, though they are completely settled.
What might be the cause?
Thanks in advance.
I have been having an issue with std items not getting financailly settled in the inventtrans. The items have been produced and ended, packed and invoiced. I assumed that would 'settle' the transactions.
I also see a lot of rounding variances on manty of my transactions and I never can explain them to the user.
hi, can you explain how to do revaluation on standard cost
I have a scenario where Cost Change Variance is occurring in a BOM Journal. Additionally I see error message: "A critical error has occurred in function InventCostMovement.checkVariance"
The BOM Journal contains no inter-site movements. Have I missed something?