Dynamics 365 Supply Chain Management

Hi,

I would like to draw your attention to an issue regarding the master plan. When an item is categorized under the coverage group "Priority Coverage with Re-Order Point" in the planned order screen, the system fails to display the Re-order point source of Pegging reference.

Furthermore, upon activating the "Strict safety stock pegging for Planning Optimization," within the feature Management, the system fails to display the Re-order point source of Pegging reference. I kindly request that you address this requirement and implement it in the next version at your earliest convenience.

Regards,

Anand Ashok

Mob : +91 9003225525

It is proposed to add a "Delete All Planned Orders" functionality to Planning Optimization, similar to the feature available in the old MRP. This enhancement would address business scenarios where users create planned orders for one item and subsequently need to generate new planned orders for another item.

Currently, users must manually select and delete the old planned orders, which is time-consuming, particularly when dealing with a large volume of planned orders. Additionally, manual deletions may increase the risk of conflicts or errors in situations where no relationships exist between the planned orders.

The old MRP's "Delete All Planned Orders" feature was highly efficient and time-saving in such scenarios. Bringing this functionality to Planning Optimization would provide users with a practical and streamlined solution, reducing manual effort and improving overall efficiency.

Hello everybody,

I suggest a improved net requirement screen:

• View of all items, not only 1 item
• quick filters and functions to filter on specific transactions, like demand forecast, sales order etc.
• Functionality to include/exclude specific transaction types from calculation. For example only include purchase orders, but not planned purchase orders. Or even more specific, confirmed purchase orders.
• It would be helpful to have the historical demand/transactions available in this screen too. So you can compare future demand with historical demand. Historical demand could be summarized and displayed using the period templates.

It would be very nice if a functionality is added to show the demand coming from demand forecast, even if the forecast is on a higher level. E.g.: Forecast for sales item is exploded into 5 levels. On level 5 you have the raw material that you have to purchase. It would be great if the forecast demand is exploded and displayed on every level.

I am looking forward to your feedback.

Best regards,

Ben

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.

Today all forecasting is at the product and dimension level.

For retail industry the merchandise planning begins at the category level and then to stores and then products.

Idea here is to leverage the product category hierarchy and build forecasting there with the ability to break down using a seasonality to product level.

second part to that is using the actual sales history for allocation to stores or sites/ warehouses.

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.

In the legacy master planning engine, Issue Margin parameter is explicitly visible in the net requirements screen: Requirement Date is shown & treated as Requested Date minus Issue Margin for Sales Orders or Demand Forecast.

In Planning Optimization, even though the engine calculates the Requirement Date the same way, in the Net Requirements screen Requirement Date is shown equal to Requested Date.

This complicates the end user interpretation of master planning calculation with seemeingly no good reason. Can we please have the Requirement Date displayed correctly in Planning Optimization, when Issue Margin is maintained?

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 current visibility of request for quotations in the item requirements page and actions for purchase orders page show a wrong reference as Purchase order this must be corrected.

The "apply action" action button also gives the error that a Purchase order with reference XXXXX not found

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.