Chloe Do

Hello Microsoft Team,

I would like to share an idea to enhance user experience with Dynamics 365 SCM ERP. This idea involves automatically triggering Planning Optimization after a Sales Order (SO) is created or updated. As a user of this function since the classic master planning days, I find it inconvenient to manually run master planning for each item after creating or updating the quantity in a sales order. Sometimes, an SO contains multiple items, which makes this process time-consuming.

While it's possible to run all items by batch in the master planning module, this can also be slow.

It would be great if you could develop this automatic trigger function, as it is a common feature in other software.

Thank you!

The user input and validate Quality order with wrong batch number and they need to back to reopen quality order and Edit test results and Validate again. But they could not validate the quality order again because of the error: “You cannot block xxxx items. Only xxxxx items are available on the inventory for item xxxxxx”.

This is “bug” from using “Reopen” function on a closed quality order. It needs to be fixed. There are too many wrong quality orders and each quality order contains many test group lines – in short, there are too many input to create a new quality order. Please reconsider your solution.

I am setting up an environment in my company in Dynamics 365 Finance & Operations, and I found that it is impossible to modify the layout of the sale quotation/ sale order/ sale invoice.

I hope Microsoft can develop this function in the future, so that we can modify the template of the sale quotation/ sale order/ sale invoice in our own way.

Hi All, I have multiple Replenishment Template Lines to update, Could you please develop a function which helps users to do bulk update the Select Product details, rather than having to manually go into each one to update.

Thanking you!

The standard catch weight design helps prevent weight changes after registration.

For us, we set the catch weight during production and keep it the same for all movements afterward.

We use the standard CatchWeight item handling policy by setting the Outbound weight variance method to "Restrict weight variance" and the Movement weight capturing method to "Not capture."

With these settings, we expect the weight to remain constant during movements and picking processes. Therefore, the reservation and release processes should follow this rule when determining the catch weight allocation method.

Based on our settings, we do not expect the weight to change or need confirmation during reservation and picking.

However, the "Catch weight item handling policies" only work if the quantity is picked using a mobile device, not manually.

We expect the catch weight item handling policies to apply to all methods for completing inbound, picking, and outbound processes.

Even if we were not using the warehouse scanner function and were picking entirely through the client, the handling policies should still apply.