Costing version setup (form) [AX 2012]

Updated: February 4, 2014

Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

Click Inventory management > Setup > Costing > Costing versions.

Use this form to define a costing version that will contain a set of cost data and to maintain the data. A costing type indicates whether a costing version will contain standard costs or planned costs, which then constrains how cost data will be entered and calculated. After a costing version has been defined, the form provides a starting point for maintaining cost data. Data maintenance includes entering item cost records for purchased items, entering cost records for cost categories that are used in production, calculating item cost records for manufactured items, activating cost records, and copying item cost records to a costing version.

An alternative form is labeled Costing version maintenance. The Costing version maintenance form only supports the maintenance of cost data that is associated with unblocked costing versions, and does not support the creation of a new costing version or the definition of its policies. The Costing version maintenance form is the preferred form for data maintenance purposes.

A costing version can also contain content about an item's purchase prices or sales prices, but this information only applies to calculations of a manufactured item's sales price by way of the Calculation form.

A standard costing environment could define one costing version that contains the standard costs for the current period, and define additional costing versions for future periods. The costing version for the current period standard costs would only contain active costs, and the blocking policies would prevent the entry of pending costs and the activation of pending costs. The active standard costs will be used for valuing inventory transactions.

An actual costing environment could define one costing version that contains planned costs. The costing version for these planned costs would only contain active costs, and the blocking policies would prevent the entry of pending costs and the activation of pending costs. The active planned costs will be used for valuing certain types of inventory transactions, such as an inventory adjustment, transfer, or cycle count, when actual costs have not yet been recorded.

The following tables provide descriptions for the controls in this form.

Tab

Description

Overview

Display the costing versions, the costing version type, and the blocking policies.

General

Display information for a selected costing version.

Recording

Display the validity date, site and content for a selected costing version.

Calculation

Display the calculation restrictions for a selected costing version.

Button

Description

Price

Maintain cost data about items or cost categories (for routing operations).

Copy to

Copy item cost data to the pending costs of another costing version.

Print

Print a report about item prices or cost category prices.

Activate

Activate the pending costs for items in the costing version.

Calculation

Calculate pending costs for manufactured items in the costing version.

Field

Description

Costing type

Select whether cost data in the costing version reflects standard costs or planned costs.

Version

Define the costing version identification.

Name

Define the costing version description.

Block

Select whether pending costs in the costing version can be maintained, deleted, and calculated.

Block activation

Select whether pending costs in the costing version can be activated.

Last activation

A system-maintained date that shows the last date any cost data was activated.

Last update

A system-maintained date that shows the last date any cost data was entered.

From date

The from-date will be used as the default from date when entering a cost record in the costing version. The from-date will also be the mandated calculation date when initiating BOM calculations involving the costing version. Leave the field blank to allow the entry of any calculation date.

Site

The site will be used as the default site when entering a cost record in the costing version, and entry of a different site will be prevented. The site will also be the mandated site when initiating BOM calculations involving the costing version. Leave the field blank to allow the entry of any site.

Recording restriction

Select whether recording restrictions will be enforced about charges and rounding. The recording restrictions about charges must be enforced for a costing version with a type of standard costs. The restrictions can be optionally enforced for a costing version with a type of planned costs.

Incl. in unit price

Select whether charges for an item will be included in the item's cost.

Round off

Select whether calculated costs for a manufactured item will be rounded to the decimal precision of the company's local currency.

Purchase price

Allow purchase price records about items to be added to the costing version.

Cost price

Allow cost records about items, cost categories, and indirect costs to be added to the costing version.

Sales price

Allow sales price records about items to be added and calculated in the costing version.

Restrict calculation

Select whether restrictions about BOM calculation policies will be enforced. The calculation restrictions must be enforced for a costing version with a type of standard costs. The restrictions can be optionally enforced for a costing version with a type of planned costs.

Cost price model

Select the source of a component's cost data that is used by BOM calculations. The source can be the item cost records in a costing version. The source can also be the source of cost data identified by the BOM calculation group that is assigned to each component item. Standard costing requires a costing version source.

Fallback principle

Use a fallback status of none when you use a one-version approach to cost data updates.

Use the other fallback options when the costing version represents the incremental cost updates in a two-version approach. The option indicates the alternate source of cost data if it does not exist in the costing version. An alternate source includes either the active costs (regardless of costing version) or a specified costing version.

Fallback costing version

Select the costing version when you use a fallback principle of another costing version.

Profit-setting

Select the set of price-setting percentages that will be used as a default when initiating a BOM calculation involving the costing version. The profit-setting percentages are used to calculate a suggested sales price

Explosion mode

Select how costs will be calculated for manufactured items.


Announcements: To see known issues and recent fixes, use Issue search in Microsoft Dynamics Lifecycle Services (LCS).

Community Additions

Show: