Purchase orders (PO) derived from an “item requirement” sales order (e.g. through the MRP) are excluded from the project committed cost. It is only if the Item requirement is set to yes in the Cost commitment parameters, then the system starts recording committed cost from this pair SO-PO. An "Item requirement", however, is committed into the project budget as soon as the SO line has been created. From the standpoint of my customer, this is too early: 1) An item requirement sales order is created to initiate the R&D work on the equipment. The cost is not fully known yet, as the product BOM has not been fully developed and we may not have decided yet between procurement or own manufacturing. 2) A planned PO is prepared by the MRP, but not approved: there is no commitment yet, as a planned order is an artifact on the planning mechanism in D365FO and may be amended or cancelled in many ways. 3) A planned PO is converted into a real PO. We are getting close, but the ultimate price and delivery date has not been promised yet by the supplier. 4) The PO is confirmed. There is a signed agreement with the supplier, the cost is now committed. The logic should be reversed: if there is an item requirement sales order with a PO coverage, take the PO for the cost commitment and the SO delivery for the ultimate budget consumption. We can make this behavior dependent on the project management parameter Create item requirement. It if is set to No, apply the above modified logic. If it is set to yes, use the standard business logic.

Under Review
Ideas Administrator

Thank you for the suggestion! This has been added to our roadmap and will be considered for a future release.


Kim Nelson

Program Manager, Project management and accounting