Dynamics 365 Supply Chain Management

Currently, Planning optimization is not supporting the scenario where we have 3 parallel operations (one primary and 2 secondary), where resource assigned for primary operation has limited capacity associated to it and formula assigned on operation is Capacity while the resources associated to secondary operations have unlimited capacity.

When such situation is found, Planning optimization is generating error like "Capacity could not be found” during scheduling.

Same scenario works under legacy Master planning engine.

Scenario has been raised to Planning product group (under https://fix.lcs.dynamics.com/Issue/Details?bugId=1029575&dbType=3) and it has been deemed as being a gap in the current design of Planning optimization engine.

Below steps can be used to validate the scenario:

1. Navigate to Working time templates. Create new working time template = 1113 and set following time shifts:

Monday: From 06:00 to 24:00

Tuesday to Friday: From 00:00 to 24:00

Saturday: From 00:00 to 06:00 (Closed for pickup = Yes)

Sunday: Closed for pickup = Yes.

2. Navigate to Calendars form. Create new calendar = 1113 and calculate working times based on working time template = 1113.

3. Navigate to Route groups. Create new route group = 1113_std with Setup time = Yes and Run time = Yes under Estimation and costing. Check Activation for all job types, check Job scheduling and Working times for Setup, Process and Transport job types and check Capacity for Setup and Process job types.

- Then, created new route group = 1113_sec with Setup time = Yes and Run time = Yes under Estimation and costing and under Automatic route consumption. Also, check Report operation as finished = Yes. Check Activation, Working times and Capacity for Setup and Process job types. Note that Job scheduling is NOT checked.

4. Navigate to Resources form. Create new resource = 1113_Tool with Type = Tool, route group = 1113_std, Setup category = Polishing, Run time category = Polishing, Quantity category = Polishing. Set Capacity unit = Strokes/hour, Capacity = 3480, Batch capacity = 80. Set Finite capacity = No, Calendar = 1113 and assign resource to resource group = 1110.

- Next, still on Resources, create new resource = 1113_Mach with Type = Machine, route group = 1113_sec, Setup category = Polishing, Run time category = Polishing, Quantity category = Polishing. Set Finite capacity = No, Calendar = 1113 and assign resource to resource group = 1110.

- Next, still on Resources form, select resource = 1113 and update route group = 1113_sec, Finite capacity = No and Calendar = 1113.

- Then, click on Resource group = 1110 and, on Resource groups from, for selected resource group = 1110, assign calendar = 1113.

5. Navigate to Coverage groups form. Create new coverage group = Period45 with coverage code = period, coverage period = 45, coverage time fence = 365, negative days = 365, positive days = 365, BOM explosion time fence = 365, Capacity scheduling time fence = 365.

6. Navigate to Master plans form. Update StaticPlan and set Scheduling method = Job scheduling, Finite capacity = No. Set Coverage = Yes (365 days), Explosion = Yes (365 days) and Capacity = yes (365 days).

7. Navigate to Released product details. Create new item number = gs1113 with item model group =FIFO, item group = AudioRM, storage dimension = SiteWH, tracking dimension None. Under Plan fast-tab, set Coverage group = Period45.

8. For newly created item number gs1113, go to menu Plan – Default order setting. Set Default order type = production and, under Inventory fast tab, set Min. order quantity = 2000 and standard order quantity = 2000.

9. For newly created item number gs1113, go to menu Engineer – Route and create new route and route version with name = gs1113 on Site = 1. Add operations as follows:

- Oper. No. 10 – Primary, Operation = Assembly, Route group = 1113_std. Under Setup tab, set Formula = Capacity, Factor = 18. Under Times tab, set Setup time = 1.5 and Run time = 1 for Process quantity = 1. Under Resource requirements, set Requirement type = Resource and assign resource 1113_Tool.

- Oper. No 10 – Secondary 1, Operation = Finishing, Route group = 1113_sec. Under Resource requirements, set Requirement type = Resource and assign resource 1113_Mach (accept resource defaults).

- Oper. No. 10 – Secondary 2, Operation = Packing, Route group = 1113_sec. Under Resource requirements, set Requirement type = Resource and assign resource 1113 (accept resource defaults).

- Approve and activate the route version.

10. Navigate to All sales orders form. Create new sales order for customer account = US-001, on Site = 1, Warehouse = 11. Delivery date control = None. On Sales line, add item number = gs1113, quantity = 2000.

11. After saving the sales order, go to sales line menu Product and supply – Net requirements. On Net requirements from, submit Planning optimization for item gs1113 under StaticPlan.

12. Planning process will complete with an error.

After making a line change due to invalid data, the item number field loses focus when creating a new sales order line using the down arrow key, even if it is the first column in the grid.

As a workaround, we can use the Shift+Tab key combination, which allows us to move back in the row and return to the first column without having to use the mouse.

But it is very convenient to do this for every line when you have many and many lin to create for a same sales order.

Should be nice to correct this behavior.

Thanks a lot

Enhance the standard Purchase Requisition workflow in Dynamics, which currently has “Draft,” “In Review,” and “Approved” stages, by adding an intermediate “In Approval” stage. This new stage would provide clearer visibility into the exact phase of the workflow, distinguishing requests that are under review from those awaiting final approval.

Idea:  

Implement an additional status called “In Approval” after “In Review.” This distinct stage will help users quickly identify whether a PR is still being evaluated or has moved on to final sign-off. It would reduce the need for manual checks in workflow history, offering better transparency for teams involved in the purchase process.

At the moment it is not possible to use the new quality management for warehouse processes feature and logics for ALL delivery terms that requiere Landed Cost.

That means that for the most import purchases it is not possible to work with warehouse work for quality inspections as the typical delivery term is FOB and not DDP.

In my case the customer has 80% FOB and 20% DDP and the main warehouse is internal and not an external logistic system. Without making Goods-In-Transit-Orders possible for quality mangement for warehouse processes the oranisation of taking away the sampling quantity and all the sampling plans is not supported by the system and has to be done manually. So the quality management provided by dynamics365 doesn't make sense at all for a warehouse with warehouse work.

Sales order processing and inquiry tiles are not updating correctly, leading to confusion in order visibility.

The issue arises from mixing up delayed orders, based on customer-requested shipping dates, with backorders, based on the confirmed delivery dates.

The only fix for this is to create a separate tile for backorder lines, though this solution is time-consuming

.

Currently API for the price engine is based on the Commerce CSU-API, meaning customers needs to deploy the CSU-based API. This requires customers to buy the expensive commerce CSU license, which has no added value to the customer other than getting their calculated prices to an external service.

I have lost a very promising client because of this and I expect others have similar experiences, based on some comments I have read in the community.

One major issue we faced during the implementation of D365 SCM for pharmaceutical companies was that when the order quantity and location quantity are the same, D365 automatically picks all items without requiring a scan.

Due to human error, the wrong item might be present in the location. If the system skips scanning, the picker may pull the wrong item into the trolley and move it to packing.

Work confirmation doesn't help in this case, as it introduces additional scanning steps, which can significantly impact efficiency.

Therefore, it would be beneficial to have a parameter or setting that enforces scanning of all items, even when the order and location quantities match.

Found similar issue in LCS 812693

The "Safety Level of Invoiced Order" parameter, when locked in Company X, is inadvertently affecting the creation of intercompany (IC) orders and sales orders in Company Y. This results in orders in Company Y being locked as well, preventing necessary changes and updates.

Users can currently change local settings like font size and button scale in the WHS App at any time. Some set the font size to 400%, making the app unusable, then run to IT or key users for help. This causes unnecessary support overhead and breaks UI consistency.

Request:

Add a system setting to lock or disable the local Settings menu in the app per user or device. This would enforce centrally defined settings from the “Mobile Device User Settings” in D365.

Impact:

• Less support burden
• Standardized UI across devices
• Fewer user-induced issues

During a reduction period, master planning considers sales orders that have been delivered or invoiced in the past, but it does not take into account forecast lines that lie in the past. This leads to incorrect demand calculations during the reduction period. The following example illustrates this issue more clearly:

The forecast period is set to one month, while the reduction period is configured to three months. If the forecast for the first month lies in the past, the forecasted demand for that month is no longer considered in the planning. However, sales orders that previously reduced this forecast are still active in the second month and now reduce the forecast of that month — as if the forecast for the first month had never existed.

In my opinion, forecast lines in the past that still fall within the reduction period should be considered for reduction.