Product configurator – Attribute-based sales prices
In Cumulative Update number 7 to Dynamics AX 2012 R2, we have introduced analternative to the cost-based sales prices in the Product configurator, namelyattribute-based sales prices. This new feature will allow you to build salesprice models with sales prices based on components and attributes rather than onthe physical bill of material and the route. You can build several sales pricemodels for a product configuration model.
Before you start building your price models, you must define a default currency. Thedefault currency is used when you build your sales price models. You can alsodecide whether you want to attach an Excel-based price breakdown to the orderor quotation lines. The price breakdown will enable you to share details withcustomers about how you arrived at a specific sales price for a configuredproduct. You can maintain these settings in the Product information management parameters.
With these properties in place, you are all set to start building your sales price models.Click the Price models action on the Action Pane in Product configuration models.
The Price models list opens.
After having added at least one entry to the list, you can click Edit to display the Pricemodel form. In the header of the form, you see the default currency and you can add new currencies for your price setup.
In the left pane you see all the components and user requirements of the product model.Each node in the product model tree can have one base-price expression and anoptional number of expression rules. An expression rule consists of a conditionand an expression and each expression rule covers a product option that helpscontrol the price of the product.
The example above has a base price of a static number of 900 and two expression rules. Thefirst rule sets the price for the cable according to the selected length. Thesecond rule deducts 110 from the price if the same color is applied to all components.
When you build your conditions and expressions, you have the same operators available asthose that are used for calculations in a product model. Moreover, the expression editor supports
both conditions and expressions.
Once you have specified a base price and a set of expression rules for one node, you canclick on another node to continue building your price model.
If you want to maintain your prices in several currencies, you can add new currencies by clickingthe plus icon on the Action Pane and then you can select from the list of available currencies in the system.
In the example below, EUR has been added as a currency. When a configurable product is sold, the system
checks if the prices have been set in the currency of the customer. If this is not the case, the default currency
is converted to the currency of the customer using the currency exchange rates in the sales company.
What you can observe immediately is that for each price element there are now two expressionfields:
Please observe that the condition field for the expression rules is “owned” by thedefault currency. This means that you cannot modify the condition for the newcurrency.
Also, you cannot add expression rules for an additional currency. To create expression rulesthat would be relevant only for a currency other than the default currency, youcan set the price expression for the default currency to zero. Then set theappropriate expression for the non-default currency.
To test how the sales prices behave in a configuration session, click Test on the Action Pane. The Configureline form opens and you can select attribute values and immediately see the impact on the price.
If you want to see how the total price, in this case 3,466.90 US Dollars, was calculated,you can click View price breakdown on the Action Pane. This will open Excel and display both the absolute
value and the contribution as a percentage for each active price element. If you have setthe Price breakdown parameter, this Excel sheet gets attached to the order or quotation line.
When your price models are in place, you must establish at least one selection criterionto pick up the price model when you configure to quote or to order. You buildthe selection criteria using the standard Dynamics AX SysQuery form.
To get started with this, click Price model criteria on the Action Pane in Product configuration models.
The Price model criteria list opens.
Enter a name and a description, then select which price model the query is related to,what order type it should be used for and its validity period. When you click Edit, the SysQuery form is
displayed showing the primary tables for the selected order type. In the example below,
the order type is Quotation type prospect.
You can add to the list of tables by right-clicking on the tables in the header. Under Fields
on the Range tab you can add and remove filtering options.
Once your queries are created, you need to place them in the proper order in the
Price model criteria list. At configuration time, the system starts looking from the top of the
list and uses the first query that matches the data on the quote or the order line. So if youplace a general query at the top of the list, this is the one that will be usedeven though there might be a query further down the list that targets the exactcustomer or prospect of the configuration. Use the Up and Down arrows to changethe order of the queries.
You can filter the Price model criteria list to view Valid, Expired, or All queries. Use the
View action to set the filter appropriately.
Queries for price model criteria can be duplicated. When you create a duplicate, you mustenter a new unique name and a start date.
When you click OK to save a new query, the expiredate of the query that you duplicated is set to the day before the selectedvalid from date.
In a combination with matching sales price models, the queries provide greatflexibility in targeting sales prices for particular customers, regions, periods,and other criteria. To create new sales price models, you can either duplicatean existing model or start from scratch.
The final step is to specify attribute-based sales prices for the product model version.Select Attribute based in the Pricing method field in the Versions form.