Dynamics 365 Supply Chain Management

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.

Currently forecast planning is not supported with planning optimization.

This leads to no possibility to exclude safety stock from planning and the ability to build Sales and Operation Plan.

This idea is dedicated to ISV solutions, and try to repair a lake of extension of planning optimization, related with custom dimensions. We loss functionalities, compared to legacy planning.

Context : use of a custom tracking dimension (added by ISV). In the tracking dimension group, check the standard "Coverage plan by dimension" for this dimension.

Actual behavior :

Planning optimization generates new planned production order, with a custom dimension value driven by "Coverage plan by dimension". Fine.

Based on active Item BOM version, derived requirements are calculated. In those derived requirements, the custom dimension is an empty value. In the legacy planning, extension is possible, and we can initiate the value as required by business logic.

Our request : In the tracking dimension group, for custom dimensions only, add a checkbox "Planning Inheritance".

Behavior : When calculating new derived requirements, the custom dimension value is to be inherited from header to lines.

Technically speaking, inheritance flows : ReqPo => ReqTrans.

Remark : such a checkbox is relevant with custom tracking dimensions only, and irrelevant with standard tracking dimensions like serial or batches. It could remain hidden in the standard form, and be displayed only through ISV extension.

Given the design limitations of the current solution related to Intercompany return orders, we propose enhancing the current management by enabling the automatic inheritance of the RMA number from the sales order once it is generated by the system.

The process to be managed includes the following steps:

1. Creation of an Intercompany purchase return order by Company A without entering the RMA Number.
2. Automatic creation of the Intercompany sales return order by Company B (the system will generate the RMA Number).
3. Automatic update of the RMA Number on the Intercompany return order of Company A.

We would like to see the item number instead of item name in the pop-up related to “number” on the net requirement.

When you generate a Production order, under the Number column, you can hover on the number and a tooltip message appears showing Production Number and Item name.

We would like to be able to change in this tooltip to include any records we want - like product number -.

The existing standard "Supply Forecast Entity" is a read only entity.

A data entity is required to import supply forecast to superseed current only available process to copy and paste supply forecast directly in D365 screen.

Such process is used in the context of managing procurement of raw materials for configurated items for example.

Sequencing is not working for planned production orders with production routes that contain resource operations in parallel.

Actual result:

Currently when run planning optimization, planning optimization will always include safety stock quantities, transfer requirement (Doesn't have any option to disable in master plan set up)

Therefore, after execution, planned order will include the safety stock quantity, transfer requirement quantity and demand forecast quantity in the required quantity.

Expectation:

We would like planning optimization to generate planned order required quantity for the demand forecast quantity only.

We need to have master plan's set up or parameter to exclude safety stock quantity, required transaction quantity, so that we can see the planned order result for the demand forecast quantity only.

Business requirement and impact:

Business operates primarily on a make-to-stock basis and has limited raw material storage, often only covering 1-2 days. Our replenishment and site teams depend on forecast visibility of raw material usage to notify suppliers accurately, aligning with production needs and storage constraints. Currently, the settings are incorrectly inflating short-term raw material requirements, impairing visibility and the replenishment officer's ability to estimate the necessary raw materials accurately.

The result planned order of planning optimization impacting replenishment team and the ability to foresee the required quantity for multiple operation sites.

By design:

When using operation scheduling, master planning will plan capacity according to the calendar of the primary resource group. It will not take into account any calendar nor capacity of the secondary operation. It books the secondary operation at the same time than the primary. Note that this can result in scheduling the production order in a closed calendar or in a time when the secondary operation is not available (calendar closed or no capacity).

When using job scheduling master planning take into account both the capacity and calendar of the primary and secondary operations to schedule the order. Calendars for both resources of the operations must be open and with available capacity for the order to be scheduled.

The idea is to have the same possibility for operation scheduling as for job scheduling.

In the quotation confirmation dialog, the user removes the quotation lines that the customer did not want and confirms the rest of the quotation

• Master planning generates purchase proposals for confirmed quotations (with a success percentage higher then 80) in case not all quotation lines have been transferred into a sales order.
• If quotation lines with inventory transactions exist for a confirmed quotation, there is no way to correct the issue except by deleting the quotation.
• 

Expected Result

1. We would expect that the inventory transaction is removed for all sales quotation lines after confirmation, since it is not possible to confirm/ cancel the sales quotation lines that were not confirmed.