Dynamics 365 Supply Chain Management

Actual Result

If the Lead time is 2 days and then a Purchase order is created on 15.04.2025 this means that the Requested ship date has to be on 17.02.2025 which is 2 days after the creation days as per the Lead time assignment. However, when a Purchase order is created on 16.04.2025 the system records the Requested ship date to be 17.04.2025 when it is supposed to be 18.04.2025. However, the system doesn’t recognize the Lead time. Same issue happens if 15.04.2025 is to be considered a closed day, this means that the creation of the Purchase order should be on 16.04.2025 and respectively the Requested ship date should be 18.04.2025, but it is recorded to be on 17.04.2025. For more clarification, if the Working hours on 15.04.2025 are between 08:00 AM and 02:00 PM and a Purchase order is to be created after the Working hours, this means that the system should create it on 16.04.2025 and therefore the Requested ship date is to be on 18.04.2025 instead of 17.05.2025.

Expected Result

If the Lead time is 2 days and then a Purchase order is created on 15.04.2025 this means that the Requested ship date has to be on 17.02.2025 which is 2 days after the creation days as per the Lead time assignment.

• When creating new trade agreements lines for two vendors and same item with purch.price type and another two trade agreements for the same two vendors and the same item with line.disc. type
• With creating a new PR with the selected items in the trade agreement, system select automatically the vendor who has the lower purchase price with neglecting the discount percentage, this ensures that any potential discounts are also considered when determining the most cost-effective option. 

Please refer to the example below for more details:

if we created four trade agreements lines:

1.For vendor 1001:

Price= 20.00

Discount= 50.00%

• As a result net amount for 1 each= 10 USD

2.For vendor 1002

Price= 15.00

Discount= 10.00%

• As a result net amount for 1 each= 13.5 USD

Actual Result

-       The system specified the cheaper vendor in purchase price with neglecting the discount percentage “vendor 1002” with net amount 13.50.

Expected Result

-       The system should put in consideration the total net amount and specify the cheaper price “vendor 1001” with net amount 10.00.

Lot inheritance values are updated when deferred RAF record is processed not when it is registered. 

The inventory registration process is crucial for fast-moving businesses because it allows inventory to be picked and shipped to customers quickly. Customers require deferred posting for performance reasons and batch attributes to ensure

documents like packing slips are posted correctly. Performance, in this context, refers to the speed at which reports are processed, and transactions are completed, enabling the inventory to be available for the next process as soon as possible.

It would be a great addition if the buffer status as well as the priority can be updated automatically AFTER a planned order is firmed.

Currently, we need to initiate a manual planning update on the item(s) after orders have been firmed.

According to the official DDMRP definition, qualified demand should only include actual (or firmed) demand. For instance an actual created sales order, transfer order or works order. Currently, even planned demand - based on the net requirements calculation - is included in the qualified demand calculation.

For DDMRP (decoupling) planning, the spike horizon is determined by the coverage time fence defined within the coverage group. However, we need the flexibility to configure the spike horizon at two levels:

• Default Level: It should default to the decoupled lead time of the item.
• Group Level: There should be an option to adjust (increase or decrease) the spike horizon at the coverage group level, ideally with a factor.

Using the coverage time fence for this purpose is not practical. Doing so would require us to create separate coverage groups—or buffer profiles—based on varying lead times, which adds unnecessary complexity. Additionally, this approach could result in excluding potential actual demand and receipts from consideration in the net flow calculation.

Hello,

In Version 10.0.31 I thin this "Source products and materials from multiple vendors using Planning Optimization" has been implemented.

It's an amazing functionality but it doesn't work at variant level. I mean that is not possible to specify different setup per product variant. D365 consider the same setup specified at product level for all the variants.

It would be great if 2 variants could have different multiple suppliers.

Thank you in advance for taking this in consideration.

automating invoice submissions for intercompany vendors through Vendor Portal, should be possible

When users are receiving on the warehouse mobile app. If they try to receive an item a second time or over receive an item after receiving the full quantity, they get this error message: "Product cannot be received. Please contact your supervisor"

This message is ambiguous, and it is not obvious to the warehouse worker the cause of the error. The error message should be changed to give them more specific action or information.

Currently users can only view master planning "net requirements" for one part at a time with calculated accumulated qtys after transactions.

I am suggesting the creation of a form within master planning that allows users to run the same style report for a list of item numbers or item allocation key to see net requirements data for hundreds to thousands of parts at once. This will allow production planners to understand what parts will causes production downtime when at a product line level instead of going part by part.