Dynamics 365 Supply Chain Management

When an item is set to ‘Stopped’ at ‘Default order settings’ level, the creation of inventory transactions will be halted per the intentional implemented functionality.

However, while adding a line to a sales agreement, upon adding a new line, the system will not issue an Infolog per intent, unless a sales order is released from the sales agreement.

There are customers who would benefit from a change in the way the process is implemented, which would provide the option of triggering the Infolog, upon adding the sales agreement line, rather than when an inventory transaction is attempted to be created.

The current way the system is behavior is causing in many fast-operating businesses, disruptions, since, it is allowing users to create agreement lines, and only later notice the items added are for stopped products creating inefficiency by performing multiple steps e.g. removing the items and unnecessarily creating sales agreements. 

With the deprecated MRP we used the set up for minimum quantity with "Todays date" make the action messages for purchase orders always trying to advance order to todays date. Now going over to planning optimization this is no longer an option to use and therefor it is always set to "todays date + procurement time". This works fine for the planned orders suggested to fill up minimum quantity on the lead time but the action messages is not working as good. An example for this purchase order it is suggesting me to postpone the order even though I am just covering up my minimum quantity. For items with a really long lead time (1 year +) this is a real issue not knowing what we actually want to postpone or not.

I suggest that we could implement the same solution that was available in the deprecated MRP to allow that minimum is pegged towards todays date

We appreciate the concept of utilizing External Catalogs, but our business process does not use nor require Purchase Requisitions. We would prefer to have the capability to access External Catalogs directly from a Purchase Order so we could utilize the purpose/vision behind this functionality. Implementing a new process with additional workflows and configurations would add unnecessary steps and complicate our streamlined business process where our users are already accustomed to only using Purchase Orders.

With reference to LCS Issue 1025376 

When the customer account is set on hold using ‘Invoice’, no warning is triggered upon selecting the customer account from the list during the creation of the sales order.

This behavior is significantly impacting daily operations and has the potential to lead to revenue loss. A consistent method for handling warnings is highly desired, as it would greatly benefit many customers.

Hi Team,

I want to add this suggestion that system must provide the feature to edit the purchase order when it is in review status so that approving authorities can edit the purchase order

In DDMRP planning methodology, there is also the concept of a non-buffered part (think of make-to-order items). The same net flow equation is used and planned orders are only then generated where the net flow is negative (On-hand + on-order - qualified demand) < 0. The exception with non-buffered managed parts are that the net flow is not compared against the buffer (because there is no buffer).

In both Planning Optimization and MRP functionalities, if the formula ID of an approved planned production order within the frozen time fence is set to blank, the date will automatically shift outside the frozen time fence set in the coverage group.

For example, in the case of a manufactured item that has only one formula, when the formula master is updated, the formula ID of the approved planned production order is set to blank to update the formula to the latest version, and then the same formula ID is re-assigned. This causes the date to shift automatically, disrupting the plan. 

The behavior should be consistent when the formula ID is set to blank and when the formula ID is changed.

When installing an asset to a new functional location, the previous functional location installation is marked as expired (by design). Then, the error message pops up, attempting to delete the asset will fail as expired installations cannot be removed. 

In our customer case, there are a lot of assets already created and installed at different locations. Assets have to be deleted and recreated properly. There is no option to delete the assets if it was installed wrongly.

We setup reason code policy Mandatory for counting reason code type, however, when process cycle counting work in mobile device, if we click "Finished" button, it bypass the reason code for counting even reason code is set mandatory.

The counting journal posted successfully without reason code. Please consider to improve process in the future or remove "finished" button in next releases.

For inventory valuation method MAV (Moving average) currently D365 does not support inventory marking. In downstream AWMS processes this is causing an issue for cross docking of products. Can we please have this feature enabled to allow for cross docking of products whose valuation is MAV