![]() ![]() If you require the ability to enter, maintain, and view unit amounts with a maximum precision of six decimal points, you must extend the decimal point precision of the UnitAmountCur, UnitAmountMST, and CostPriceNonMonetary extended data types. Since the vast majority of production runs are for a quantity that has historically proven to be most efficient, this is an effective means of also managing decimal precision.īy default, unit amounts including prices, line discount amounts, and line charge amounts are maintained with a maximum of two decimals. On the route, the Process quantity serves the same function, to allow for decimal precision by utilizing the process quantity. Again, this allows for greater precision and more accurate calculations as the values to the left of the decimal are not rounded. Microsoft dynamics finance series#In production, decimal precision beyond 4 decimals can be accommodated using the per series in the Bill of materials. Using this approach, the systems costing engine can function as designed. For example, if you consume this item in a Bill of material for 1005 finished items, the system will calculate as follows: 1005 x 362.63 = 364,443.15/1000 = 364.44. In addition, when this item is used to produce other items, the cost calculation will also use the digits to the left of the decimal to appropriately calculate and then round the 2 digits to the right of the decimal. Upon receipt of the material, the journal is posted to record the material receipt to the ledger appropriately. When entering a Purchase order for 1000 bulbs, the system will calculate as follows: (362.63/1000) x 1000 = 362.63. Notice that the item is still inventoried in individual units for each. On the released product details, the Purchase price set up would look like this: To accommodate the need for 5 decimals, use a Price quantity of 1000 and enter the price as $362.63. By default, the price quantity is 1, but this can be adjusted on the released product details for the Purchase order price, Sales order price, and Cost price or on the Purchase order line, Sales order line, or invoice.įor example, the price of a bulb is $0.36263 each. This field is intended to be used to specify the quantity for a specific price. On the released product is the Price quantity field. In fact, the functional approach allows for any level of decimal precision. There is a standard Dynamics feature intended to accommodate the need for decimal precision greater than 2. Functional Approach to Decimal Precision Price Unitīy default, the decimal precision displayed within Dynamics 365 Finance is 2. What may save a few keystrokes in one area may actually cause issues in another, as extending the decimal places for pricing will display in all areas of the system. Additionally, all areas of the business should be involved in the decision. In reviewing your options, please consider that using standard functionality eases your ability to test and accept future updates. ![]() As a best practice, you should always prefer to utilize the standard functionality for decimal precision. The options for managing the display of decimals within Dynamics 365 Finance and Supply Chain should be carefully considered. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |