Dynamics 365 Supply Chain Management

Type Vendor: When creating a PO and link a quality order to it. When creating a Non-conformance from the quality order. It doesn't show the non-conformance through Inquiries > Non conformances on the quality order form.

Type Internal: It works well, and it shows the non-conformance linked to it.

When checking the Inventory management > Inquiries and report > Quality management > Non conformances, the non-conformance related will be there.

Expectations: to have all Non-conformance vendor type related to the quality order shows on the form list when going to Inquiries > Non conformances on the quality order form.

While splitting a purchase order line while registration system acts as expected and creates proper quality orders upon the item sampling set up.

However, when we do the splitting and receipt from item arrival, system does deal with each line we split as a separate entity and creates a quality order for each entry/registration line.

Given the current roles in the system warehouse team doesn't have access to the PO therefore, obligated to receive it from Item arrival. which leads to in correct quality orders generated even through item sampling is set up correctly.

On Loads form, Action pane, there is the Reverse work functionality.

This functionality works fine when there is only one Work Id linked to a Load line.

If more than one Work IDs were created for a Load line (due to work template/business requirements), Reverse work functionality returns the following error:

Cannot reverse work because loads have already been picked for the sales line. Use Reduce picked quantity instead of reversing the entire load.

Use reduce picked quantity line by line in large organizations is not an option as there might be many many lines on a load.

Right now, a company's employee has to first re-submit a PO to the VCP, for a vendor user to be able to make changes to a PO.

In our projects business process, after initial confirmation, it is usual that a vendor makes updates to the expected (ex factory) delivery date and /or actual quantity to be shipped.

These changes should be reviewed by company employee, just like with changes for first submitted po.

nice to have: allow to set by vendor, if the vendor is allowed to submit changes to already confirmed PO's.

suggestion: tie in this change with the existing Supplier Communication Agent procedures, where an employee has to review the suggested PO changes from vendor emails.

Hello

On the Warehouse app, when receiving an item, the "Put" Location is suggested based on the Location directive actions (mostly based on the Zones, and the product filter codes).

For instance: if we want an item that has a Product Filter code = "Toxic", we can set up a Location directive action to go to a Location in the "Toxic" Zone.

During the Receiving process on the warehouse app, when using the "Location Override" button, the user can change the suggested Location by manually entering a Location of his choice... without any control of this location

The challenge is to allow the user to manually change the suggested location with another location with the same logic (same Zone).

For instance: make sure the user manually enters a Location in the same "Toxic" Zone instead of entering a location in another zone.

The idea would be to add a logic on the "Location override", on this location (with a control on the zone based on the Product filter code)

Please Vote for me :-)

As of now, D365 F&O does not support automatic transfer of comments made during the purchase order (PO) workflow to the individual PO lines workflow. This creates a disconnect between high-level approval context and line-level execution details.

Potential Benefits of Implementing This Feature

1. Improved Traceability and Auditability

Transferring comments ensures that approver rationale and instructions are preserved at the line level. This is especially useful when:

Multiple approvers are involved.

Specific line items require justification or special handling.

Auditors or reviewers need to understand the decision-making trail.

2. Enhanced Collaboration Across Teams

Procurement, finance, and operations teams often work on different parts of the PO lifecycle. Line-level visibility into workflow comments would:

Reduce back-and-forth communication.

Clarify expectations for each line item.

Help downstream users (e.g., receiving or invoicing teams) understand context without needing to access the full workflow history.

3. Better Exception Handling

If a PO line is flagged for special treatment (e.g., expedited delivery, vendor negotiation), having the comment visible directly on the line:

Alerts the responsible team immediately.

Reduces the risk of overlooking critical instructions.

Supports faster resolution of issues.

4. Support for Custom Workflows and Automation

For organizations using Power Automate or custom workflow logic, transferring comments could:

Enable automated routing based on comment content.

Trigger conditional logic (e.g., flagging lines with specific keywords).

Improve integration with external systems or reporting tools.

5. Consistency Between Header and Line-Level Decisions

In cases where PO lines are processed or approved separately, having the original workflow comments ensures:

Decisions made at the header level are consistently applied.

Reduces misalignment between what was approved and what is executed.

When registering Sales order there is used Item list with high number of items.

For some products if there were changed Min qty and/ or Multiply qty in Default order settings there are presented info messages like bellow:

1.You have specified a quantity of 1.00. The minimum allowed quantity is 20.00.Do you want to use 20.00 instead?

2.The order quantity must be a multiple of 12.00. Do you want to round up the order quantity to 24.00?

There is missing info about ItemId

Request:

Please add affected ItemId as a parameter presented in both info messages.

It will help to identify which items are affected.

-Vendors not populating in purchase requisition line when a released product is selected

-We do not get the vendor list to select from even after using allow all vendors, assigning procurement category at item level and also defining the trade agreement.

-Partner wants to be able to see the vendor list to select from when entering item with procurement category in Purchase Requisition Line.

-If we default a vendor at item master level vendor automatically pops up upon selecting an Item with procurement category, but this does not work for partner as they procure material from multiple vendors.

Create a feature to view the "Explosion" for all lines within a sales order or project item requirements in a single view.

This feature would allow users to see all order/project requirements and expected delays within a single view that could be exported and shared with procurement and production staff for expediting requirements. Clicking through hundreds or thousands of item requirements lines to understand project/order requirements is not feasible.

Title:

Enable Expiry Date Input for Auto Batch Number Group in Mobile Device Receiving

Description:

Currently, the system automatically populates the batch number when receiving items on a mobile device, and the expiration date is not required if the batch number group is set to auto batch. However, some customers have expressed the need to input an expiry date even when the batch number is auto-generated. This feature would enhance the flexibility and usability of the system for customers who need to track expiration dates for their inventory.

Problem Statement:

Customers need the ability to input an expiry date when receiving items on a mobile device, even when the batch number is automatically generated. The current system does not allow this, which can lead to challenges in inventory management and tracking for customers who rely on expiration dates.

Proposed Solution:

Introduce a feature that allows users to input an expiry date when receiving items on a mobile device, even if the batch number group is set to auto batch. This feature should be optional and configurable, so customers can choose whether or not to use it based on their specific needs.

Benefits:

• Improved inventory management and tracking for customers who need to monitor expiration dates.
• Increased flexibility and usability of the system.
• Enhanced customer satisfaction by addressing a common pain point.

Use Case:

A customer receives a shipment of perishable goods on a mobile device. The system automatically generates a batch number, but the customer also needs to input an expiry date to ensure proper inventory management. With the proposed feature, the customer can easily input the expiry date, improving their ability to track and manage their inventory.