• Reversing posted rebate management transactions

    Allowing users to reverse/cancel the Rebate management "posted" transactions. just like the cancel provision option.

  • Intercompany Posting through two different countries

    Customer is not able to post the intercompany Purchase order invoice with the three-way matching policy active due to difference of Tax calculation over the two companies.

    It happened to be having an Intercompany trade between two different countries that each one has its own tax calculations.

    for example:

    Country A: have tax 15%

    Country B: have tax for 13%

    Creating an Intercompany trade between the aforementioned two countries with cause an error for the Invoice posting, while activating the three-way matching.

  • Intercompany chain discount disappears when confirmed dates are entered into Intercompany Sales order.

    When updating a delivery date on the Sales Order in the production company, the discounts given on the original sales order in the sales company is erased.


    The code has an exception when intercompany chain is involved. The prompt is dependent on the fields SYSTEMENTRYCHANGEPOLICY and/or MANUALENTRYCHANGEPOLICY. If one of these two fields are set on the sales line, then if the confirmed delivery date on SO is updated, then you are prompted for behaviour concerning price and discount. These fields are not copied in the intercompany chain and therefore the fields are only set on the original sales order - not on the intercompany order.


  • Trade agreement price calculation for child lines

    Big customers always have a trade agreement for the selling Items, based on the amount you will gain a special discount. The main purpose of this Idea is to have the trade agreements of sub-items (child lines) to inherit the correct item price from the trade agreement to the sales order calculation.

    I would like also to refer to the BUG Details for issue 488226 (dynamics.com)

  • Requested Receipt and Shipment date for ECOM orders.

    The system is addressed to be having the intended behavior of calculation for B2C orders Details for issue 530125 (dynamics.com)


    However, using this method of calculation such as the normal Sales order processing calculation methods to consider the Requested Receipt and Shipment date into calculations.


    This will be addressed as a valuable addon to the system for businesses that always using Ecommerce orders.

  • Issues with rounding when decimal precision of 4 is used on BOM line and released qty = qty of on-hand

    On our production orders we receive imports from an CAD software into the BOMs of Level 1 Production Orders. The information we receive is not per price produced but the complete quantity calculated in CAD for all pieces together. 


    The goods needed for producing the level 1 Production orders are produced very individual – this is why we are using “Pegged Supply” in order to create Level 2 Production Orders.

    Level 1 Production Orders are reported as finished with split quantities because we need a License Plate Label for each piece produced in Level 1. As we don’t want to post material consumption of Items produced in Level 2 manually this should happen automatically when reporting Level 1 Production orders as finished – however this does often not work because of these issues.


    Please note that this issue is reproducible when decimal precision on Unit m3 is set to 4 and not the default of 2.


    This have been addressed to be as "By design" based on this LCS link Details for issue 843403 (dynamics.com).


    Tested to extend the decimal and did not even fix the issue and kept showing discrepancies in the complete quantity calculated in CAD for all pieces together.


    Please consider this for a fix in the future as this is mandatory for all types of business that works with real state industries.