Dynamics 365 Supply Chain Management

Currently, the quantity per license plate has to be specified upfront as a Product unit conversion and added to the Unit sequence group.

For many projects (I know of 5 customers in my own company) the quantity per LP is unknown at the time of receiving as different vendors may send different packaging formats.

Here are two real-world examples:

• Customer has 5kg bags, 20kg bags, 25kg bags of powder sent from different suppliers on different pallet configurations. One LP per pallet.
• Another customer has 10pcs 12pcs or 15pcs per carton, with cartons on a pallet. Each carton may or may not require a separate LP. (Generally if more than 10 cartons received then a single LP per pallet). The customer also needs to print a label for each carton.

In both cases it is the warehouse worker that "discovers" the packing format.

Idea:

• Add a new (3rd) option named "User specified quantity" to "Licence plate grouping policy". When this option is selected the user will be prompted to enter the quantity per LP.
• Add a tick-box for all receiving flows named "Request number of labels". When this option is selected the user will be prompted to enter the number of labels per LP.

We should be able to specify the number of labels to print per LP. This will allow the correct number of labels to be printed for each license plate.

e.g.

• 25 cartons of 12 pcs on a pallet
• User enters 300 pcs / LP
• User enters 25 labels / LP

Please also refer to this Yammer conversation.

https://www.yammer.com/dynamicsaxfeedbackprograms/threads/2536302012276736

ATP shows purchase order receipts as available the day of receipt, but for some companies the receipts are usually not ready the day of arrival. It would be great to have ATP take into account the Receipt margin. Currently master planning takes into account receipt margin, but ATP dates do not.

Issue margin is not ideal because it adds a margin to all supply, not only to purchase orders.

This has been discussed in the dynamics community: https://community.dynamics.com/ax/f/33/t/150422

The planning optimization does not consider item different units; therefore, it does not fetch the correct trade agreement price for the requirements planned orders.

In conclusion, the planning optimization does not respect unit conversion.

For instance, if we have 3 trade agreements for one product A:

Product A, 1 PCS, 10 EUR

Product A, 1 VP10, 95 EUR (VP10 = 10 PCS)

Product A, 1 VP20, 180 EUR (VP20 = 20 PCS)

now I would like the MRP to suggest me the best price. 

Setting is set

- look for Trade Agreement

- find the best price

- also the unit conversions are in place.

I create a sales order with 10 pieces

Run the planning optimization.

it suggests me to buy 10 PCS for 100 EUR.

I would imagine that the MRP would find the agreement with unit VP10 and suggest me to order them for 95.

Currently the only filters on input for Planning Optimization are related to which items should be included in the planning run or whether the forecast should be included (plan filters, runtime filters, coverage groups, etc.) but some businesses have scenarios in addition where they want to exclude certain data from being included. For example, a particular sales order or set of orders, certain forecast lines, or other criteria that may be specific to a business or industry.

In classic master planning, this is something that can be customized, but Planning Optimization only supports extensions for post-processing (Planning Optimization extensibility - Supply Chain Management | Dynamics 365 | Microsoft Learn). It would help more users adopt Planning Optimization if there was either a framework for doing more unique input filters or the ability to migrate their extensions to be compatible with Planning Optimization.

Standard D365 does not allow the Correct button on the Purchase order product receipt, once the Product receipt is posted.

The only workaround is to cancel the product receipt which includes moving the products back to the receipt location first. That is very time consuming and complex since after the cancelation you need to receive every product all over again to correct the mistake.

The idea is to enable the Correct button to Product receipts when Warehouse management processes are used, like it works for a regular non warehouse management Purchase order product receipt.

Photo capture option on the warehouse management app

Purpose:

With the mobile device, take a photo of a work exception (damaged product, location blocked etc.) or any other phenomena in the warehouse and attach this photo as a file to the work exception, work line or the current source order line.

Proposed solution:

In the Warehouse management app, add a new button that can be used for uploading a photo taken by this mobile device.

This option could be configurable in the mobile device menu item.

I suggested this some years ago in Yammer, but can not find an idea.

Also refer to the Yammer post of Luca Ganz.

https://www.yammer.com/dynamicsaxfeedbackprograms/threads/2533552878583808

Thank you for your feedback. Currently this is not in our roadmap; however, we are tracking it and if we get more feedback and votes, we may consider it in the future.

Sincerely,

Roger Sa

PM, Microsoft

A customer that we work with has a great amount of sales orders going out each day and the confirmed receipt dates are used to communicate when the end customer can expect their delivery. To generate a confirmed receipt date, the ATP or CTP for planning optimization delivery date control methods are used, depending on the item settings.

However, when an item is set up with delivery date control = CTP for planning optimization, there is a big chance it will cause issues for certain end customers based on the below scenario:

SCENARIO

Available on hand: 43 pcs for item A (No ordered or on order transactions at the time). Item A is a BOM component.

ORDER #1

Created: 20241107

Requested ship date: 20241201 (future requested date)

Requested receipt date: 20241201 (0 days of transport lead time, this doesn´t really matter)

Quantity: 43 pcs for item B (Item A is included in the BOM)

After running the CTP for planning optimization, the confirmed ship date will be 20241201 since the available on-hand fulfill the required quantity.

ORDER #2

Created: 20241107

Requested ship date: 20241107 (today´s date, as soon as possible)

Requested receipt date: 20241107 (0 days of transport lead time, this doesn´t really matter)

Quantity: 10 pcs for item B

After running the CTP for planning optimization, the confirmed ship date will be 20241107 since the requirement date on order #2 is before the requirement date on order #1, even though order #1 is created before. A planned purchase order is then created to fulfill the remaining quantity for order #1. That means in theory that order #1, which we promised to the customer at 20241201, no longer can be promised on that date because the planned purchase order might take longer time to purchase and receive, and the MRP will suggest a potential delay for order #1.

The idea

It would be valuable if the CTP for planning optimization can respect the created date and time of the order line or ultimately respect when an order line has a confirmed delivery date. In the above case, such an improvement would mean that the quantity for order #1 is protected since the stock is allocated to the order line prior to order #2.

The above described scenario is for sure causing a negative impact for a customer that is placing a sales order well in advance, or basically any future requested date. The promised date to the customer might not be fulfilled since the system is generating new proposals based on the requirement dates with the current functionality.

You define an attribute of type decimal and sets up limit for this attribute. You then use the attribute type in a product model because you want this value in the configuration dialogue to be delimited by the limits. But these limits are not used, so the user can type any value in the field. So my suggestion is to enable these limits either by looking up in the model or secondary give posiibility to define some limits on the attribute in the model.