Dynamics 365 Supply Chain Management

When the "Item substitution" feature is enabled and items are assigned substitution priorities, Master Planning is designed to always favor the higher-priority item's open purchase orders—even if the lower-priority item has an open purchase order with an earlier receipt date that aligns better with the production order’s requirement.

This behavior is by design, based strictly on item priority. However, introducing a control that allows the system to consider the earliest available receipt date—regardless of item priority—would significantly improve inventory utilization. Such flexibility would enable customers to fulfill production demand more efficiently, reduce wait times, and make better use of available supply.

The preview panel on attachment form is too small for reviewer. And the size cannot zoom in or out from user interface. It takes more inconvenience to business process.

Return order lines that are flagged as credit only do not show up on any report that be sent to a customer for confirmation.

They are on the customer invoice, however Sales order invoicing is typically done via batch and not handled by Customer Service workers that would be handling returns.

The "Return order" and "Acknowledgement" report that is shipped out of the box. But those reports are designed to represent physical inventory expected and physical inventory received. They exclude lines marked as "Credit only"

When using the Purchase requisition workflow, if an approver requests change, after the orignator resubmit it, the workflow will be canceled and goes back from the beginning instead of going back to the approver who requested the change.

We suggest it goes back to the approval to save time wasted on this

Now in 10.0.44, we have the possibilty to generate a quality order for a transfer order. However we can not select the warehouse for which the quality order should be executed. So for example, if you set up a quality order with an invent type "Receive transfer order", You will have quality order in every warehouse of your site.

Let's imagine a company with several warehouses ( production, distribution, storage).Generally, we want a quality order only for a limited case.

I opened a ticket to MS. But they provide the usual answer : "By design only a site level is supported".

Current documentation Inventory marking documentation (Inventory marking - Supply Chain Management | Dynamics 365 | Microsoft Learn) indicates the functionality is default "on" as long as the system is running Supply Chain Management 10.0.36 or later. However, it does not mention costing methodologies disabling the functionality (see Moving average - Supply Chain Management | Dynamics 365 | Microsoft Learn). This should be cross-referenced in the Inventory marking documentation to allow consideration of this limitation.

Hi all,

we use product variants with versions. We need a feature that helps us consume on-hand inventory of older versions, before consuming and/or planning the new version.

Example: We have a bom with component ABC001. ABC001 has the version 002. Our bom already has the new version 003, but we want to make sure that we consume the older version 002.

With planning optimization there is a feature "Item substitution for bill of materials in Planning optimization". The problem is, that we have to put the priority to the older version. Master planning then makes sure that production use the older on-hand inventory. That is great.

But.... with prioritizing the older version in the bill of material, master planning creates planned orders for the old version.

So what we need is a feature that helps us consume the old version, but won´t create planned orders for the old version.

Unfortunately there is no possibility to switch the version of the item of a planned purchase order. If we block purchasing the old version and manually create purchase orders for the new version, net requirement does not show any pegging demand.

#Summary:

Reduce the number of clicks and pop-ups required to delete sales orders in the Sales and Marketing module, while still preserving an option for batch processing and safe data handling.

#Description:

Currently, the process for deleting sales orders in Sales and Marketing → Period tasks → Cleanup → Delete sales orders involves several steps:

1. Selecting the relevant sales order(s) based on search criteria or filters.  
2. Clicking “Batch” and enabling batch processing.  
3. Clicking “Confirm deletion.”  
4. Responding to an additional pop-up confirmation.

This multiple-step approach can be time-consuming, especially for users performing frequent or large-scale cleanups.

#Proposed Idea:

• Combine the “Batch” and “Confirm deletion” steps into a single prompt that clearly explains the potential impact of deleting the selected sales orders.  
• Where an extra confirmation pop-up exists, consider merging it into this single prompt or making it optional, based on user or administrator preferences.

#Summary:

Reduce the number of clicks and pop-ups required to delete sales orders in the Sales and Marketing module, while still preserving an option for batch processing and safe data handling.Summary:

Reduce the number of clicks and pop-ups required to delete sales orders in the Sales and Marketing module, while still preserving an option for batch processing and safe data handling.

#Description:

Currently, the process for deleting sales orders in Sales and Marketing → Period tasks → Cleanup → Delete sales orders involves several steps:

1. Selecting the relevant sales order(s) based on search criteria or filters.  
2. Clicking “Batch” and enabling batch processing.  
3. Clicking “Confirm deletion.”  
4. Responding to an additional pop-up confirmation.

This multiple-step approach can be time-consuming, especially for users performing frequent or large-scale cleanups.

#Proposed Idea:

• Combine the “Batch” and “Confirm deletion” steps into a single prompt that clearly explains the potential impact of deleting the selected sales orders.  
• Where an extra confirmation pop-up exists, consider merging it into this single prompt or making it optional, based on user or administrator preferences.

The current session logoff functionality introduced via the Work User Access Policy in D365 SCM does not fully support the "User and password" authentication method on mobile devices. This creates a security loophole and usability challenge, especially for industries like Pharma where strict access control is mandated by regulations such as 21 CFR Part 11.

There are two authentication methods for mobile devices:

1. Device Code Authentication – One-time login with a device account, followed by warehouse worker login.
2. User and Password Authentication – Requires login with a Dynamics user account, followed by a second login with a warehouse worker account (often automated via Default User).

The session logoff currently only affects the second login (warehouse worker), not the primary user login. This leads to:

• Security Risk: After session timeout, users can cancel the warehouse login and reconnect, automatically regaining access via the still-active primary login.
• Compliance Gap: This violates regulatory requirements for access control and auditability for companies like Pharma Companies
• Usability Issue: Users are forced to re-enter warehouse credentials they may not know, while the actual user session remains active.

Proposal:

• Extend session logoff to also terminate the main user session when using User & Password authentication.
• Ensure that after timeout, users must re-authenticate with their Dynamics credentials.
• Prevent automatic re-login if the session has expired.

This change would close a security loophole, support compliance, and make the preferred authentication method more practical for real-world use.