Dynamics 365 Supply Chain Management

In the work order default form, when selecting None from Update finished report on-line, the Feedback quantity validation options are greyed out.

Selection of None means that RAF is not created if the FINAL operation is completed. The Feedback quantity validation settings validate feedback quantities on ANY operation and therefore should still be available to be selected.

Customer use a combination of None and Feedback quantity validation and have to apply a workaround to change the parameter from None to Status to allow for the Feedback quantity validation settings to be editable.

when an item is in a Product lifecycle state which blocking PO / SO/ production order etc, the MRP system still create relative plan order in intercompany organziation, then give error when firm the plan order.

Error message: Firming Number: 25.PL.0243146 Item number: G2.05.T3.003.0 Company: LEM Europe GmbH Item G2.05.T3.003.0 is in the product lifecycle state CREATION for which the process Sales order is blocked.

but from the system point of view, a robust ERP system should not have this kinds of low level error

When a purchase order is confirmed and the user subsequently requests changes—updating information in the purchase order header and resubmitting it to the workflow—the system currently confirms the PO directly without generating a new purchase order confirmation journal number. This results in the confirmation journal number being skipped.

Business might have a scenario where one released product might be sold to different customers located in different countries.

Where as in standard D365 F&O we have got feature to add only one HS code per released product.

It will be really a nice to have feature if Multiple HSN code can be maintained for one released product.

Refer below table for better understanding.

Released Product HTS Code Country

Pump 84138100 CHINA

Pump 84133030 INDIA

Pump 8413.81.00.20 USA

In Dynamics 3D365, we noticed that when converting a Purchase Requisition (PR) to a Purchase Order (PO), the system automatically overrides the PR line’s Item Description with the description from the Released Product — if the PR line has an Item Number (catalog item).

This behavior is expected and ensures consistency across product-based transactions. However, it limits flexibility in business scenarios where procurement teams need to:

• Provide customized descriptions for specific orders (e.g., product variations, vendor-specific packaging, labeling, etc.).
• Capture unique notes or requirements per line that are intended to be passed on to the supplier via the PO.

At present, the only supported workaround is to use non-catalog items, which is not feasible for organizations that require item tracking, inventory integration, or vendor item references.

Proposed Enhancement:

Introduce a parameter or policy setting that allows organizations to choose whether to:

1. Retain the PR line description when creating the PO, or
2. Use the Released Product description (current behavior).

This could be:

• A toggle in Procurement and sourcing parameters, or
• An option in Purchase Order creation policies.

Business Impact:

• Provides flexibility for real-world procurement scenarios.
• Reduces need for customization just to control description flow.
• Helps users manage exceptions while still leveraging item-based requisitions.

Under Procurement and sourcing parameters > Price > Trade agreement Evaluation

remove the manual entry

Go back to Purchase order and when changing Delivery date, system will not prompt the update order lines for "update prices and discounts entered manually or by external document" for new Purchase Orders.

However, for old Purchase Orders, the prompt is still happening.

System should not prompt the "update prices and discounts entered manually or by external document" for both new Purchase Order and old Purchase Order

On account payable parameter, customer remove the manual entry by navigating to procurement and sourcing parameters > Prices > Trade agreement evaluation. However, the dialog which trigger the changing of price and discount will not appear for new purchase order only. The dialog will still prompt for the old purchase orders.

Microsoft decided to cancel the preview feature Rename item number.

https://learn.microsoft.com/en-us/dynamics365/supply-chain/get-started/removed-deprecated-features-scm-updates#rename-item-number-preview

Reason:

"The item number field is a primary key that is used across multiple systems. The (Preview) Rename item number feature allowed users to edit the item number field, but we found that the feature could cause data inconsistencies in multi-system and apps-integration scenarios, leading to data integrity and data corruption issues. The feature was previously in preview and was never made generally available for use in production environments."

Proposed idea:

Do not cancel this feature, because the reason above certainly does not apply to all customers. The existing preview was fine for many customers.

Instead of cancelling the feature, 1) add a clear warning message with the reason above, and 2) add a clear authorization or parameter on the user that grants the rename function only to users that know what they are doing.

A new extension of the "Rename item number" function is required to also rename the product number if the product has not already been released in other legal entities. With the functionality in preview 10.0.42 it is possible to rename only the item number.

When using deprecated MRP, firming planned production order using job scheduling results 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 costumers cannot use material check as a part of make to order process.