Dynamics 365 Supply Chain Management

In reference to fix request ID "1044123", users expect the system to stop generating Planned POs once the full requested quantity has been delivered and received across POs, even if the delivery was split across multiple lines.

Additionally, the replenishment request needs to remain linked to all related POs and stop triggering further planning once completed.

For various planning processes it is needed, that for a specific coverage dimension, it is possible to define a priotized list of allowed values.

Example: Inventory Status:

Assume you have Inventory Statuses for product quality:

Q3 - Highest quality

Q2 - Medium quality

Q1 - Low quality

BL - In review

RJ - Rejected - to be returned.

Depending on the customer Requirement, it should be possible to fullfill a customer demand for Q2 with quality Q2 or Q3 (In that sequence).

A customer demand for Q1 should be fulfilled with Q1 - Q2 - or Q3 (In that sequence)

So it should be possible for every dimension value used in an issue transaction what receipt or inventory transactions are allowed to be pegged and in what sequence that pegging should happen (similar to the plan groups, but specific to a dimension).

This should also work for product dimensions, warehouse and eventually Owner or Batch-Number.

Batch CTP is confirming dates when no capacity is found on a lower level of a multilevel BOM. MRP calculation however is correctly calculating:

• error after MRP run 'no capacity could be found'
• Planned order: route job = 'no'.

To make Batch CTP work in this structure the confirmed date cannot be set if on a lower level no capacity is found.

Request: Change Batch CTP to take all MRP calculations correctly into consideration to confirm sales order lines.

Currently the Action fields (Actions, Actions messages, Action days) just available on Planned Order level,

Request for the same fields to be available in Purchase Order level in Supply Schedule form.

When raw materials are stored in silos, often a new batch is filled into a silo without the silo completely empty. For traceability, this results in a mix of batches (what may be one solution to solve the scenario: create a new merged batch.

The other solution would be to allow to create tracking references on consumption for more than one Batch at a time.

This also applies to scenarios where a production line may be provisioned with material from multiple batches at the same time.

In a way, this could be solved with a concept of "staged batches" on a specific location, that create more than one traceability reference on consumption.

In many cases, the traceability to a vendor related material is not done with Batch or serial references, but basically by using other Vendor references for traceability:

• Purchase order number
• Delivery note number (Receipt ID in Dynamics)
• Shipment ID
• Invoice number
• Vendor package ID / Handling unit ID / Container- ID
• Obviously, an important reference to track is the delivery date.

If no batch or serial number is defined or tracked, those references are the preferred references to track back to the Vendor traceability. The Vendor might also provide additional tracking references in an ASN or in an As-build-BOM Report that are NOT used as inventory dimensions in Dynamics, but should be registered in the Tracking solution.

It should be possible to:

• Export of additional purchase references to the traceability solution
• View and analyze traceability based on those document / reference types
• Import additional references to the traceability model that are NOT registered in Dynamics directly.

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.

The customer is using item substitutions (plan groups) on formulas that consist of two lines, each with its own priority. The primary and secondary formula item have corresponding item coverage setup that replenish demand with planned purchase orders at warehouse 12 and transfer this demand to warehouse 13. However, when planning is run with demand at warehouse 13 the system completely ignores plan group setup. It covers the demand with on-hand inventory and replenishes the remaining quantity only for the item with priority 1, without considering the on-hand inventory for the item with priority 2. However, if the demand is for warehouse 12 (where no transfer is required), the item substitutions work as expected, and the on-hand inventory for the item with priority 2 is considered.

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.

When using deprecated MRP, firming planned production order using job scheduling results in automatic BOM explosion and thus running material check works as expected.

However, when running Planning optimization, firming planned production order using job scheduling doesn't explode the BOM and thus running material check can't find anything to show.

That update makes customers cannot use material check as a part of make to order process.