Dynamics 365 Supply Chain Management

There is a need of introducing a dedicated contact flag for Supplier Communication Agent correspondence on the vendor master.

This additional configuration field will allow users to designate a specific email address for automated communications initiated by the agent.

The feedback from the key users is that they are not always using the primary email address for this delayed purchase orders communication.

Based on feedback from key users currently adopting the Supplier Communication Agent, there is a need to improve the format in which Purchase Order (PO) details are shared via email.

Users have expressed a preference for receiving PO information as a file attachment rather than embedded in the email body.

To address this, we propose enabling the option to include PO details as an attached document—either in PDF or Excel format—containing selected/preconfigured fields from the purchase orders.

On the picking or transfer process the screen requires the scanning of a license plate AND a location. This is a two-scan process that is wasteful. The system already knows where the license plate is currently located. The first scan of the LP should show the current location and not require an additional scan. Then the second scan should simply be the destination location since the LP is already known from the first scan.

The root cause is the absence of standard workflow functionality for certain forms (All cases, All sales orders, Quality orders) in the current D365 Finance and Operations version 10.0.44. This lack of built-in workflow support forces the customer to use customized workflows that trigger security permission errors during execution.

We need to generate a report or extract details from system to get information on Created by, Created date and time, Disabled by, Disabled date and time for a particular USER ID.

Issue Description:

When a purchase order is partially received, the user proceeds to cancel the remainder of the unreceived quantity. After the cancellation is completed, the purchase order (PO) status correctly changes to Received in the system (previously it was showing as Open order, but upon cancelling the remaining quantity, the status updates to Received).

However, in the Vendor Collaboration Portal, under the Open confirmed purchase order section, the PO is still displayed with the status Open order, even though in the system the PO is already marked as Received.

Expected Result:

The Vendor Collaboration Portal should reflect the correct PO status (Received) once the remainder is cancelled and the PO is fully closed.

Actual Result:

The Vendor Collaboration Portal continues to display the PO as Open order under the Open confirmed purchase order section, leading to inconsistency between system status and vendor portal status.

Just like the functionality 'Outbound shipment processing policy' there is a need to control that partial work is not created for a production order.

Current functionality on the production order with Release to warehouse 'Require full reservation' is not sufficient, even though inventory might be available for reservation on the warehouse, the location directive is setup to not create work for specific locations.

When reporting as finished from a Production Order, the 'Accept error' flag is turned off by default. This is consistent with the settings in:

• Production control > Setup > Production order defaults

As a result, the Report as finished journal also has the flag turned off.

However, when reporting as finished via:

• Time and attendance registration > Feedback, or
• Production Floor Execution (PFE)

…the 'Accept error' flag is automatically set to true in the Route card journal, even though there is no explicit setup available to control this behavior.

Introduce a configurable parameter or setting to control the default value of the 'Accept error' flag when reporting as finished via Time and Attendance and PFE, similar to the existing setup for standard production orders.

This report is prepared for internal and external audit purposes to track Purchase Order (PO) numbers that have not been used or appear to be skipped. The issue arises when users create a PO and subsequently cancel or delete the entry. In such cases, the PO number may be skipped, and it becomes unclear whether the skipped PO number will be reused or permanently removed from the system.

The objective of this report is to identify and document all PO numbers that were generated but not used, in order to ensure transparency and traceability in the procurement process.

Ability to import vendor catalogs using OData/ DMF.

We have many vendors supplying our customer specific catalogs via their API. It would be good to have the capability to automate the vendors catalog import process. Currently in D365, the catalog import process is manual, where the users have to manually upload the CMR file from the UI. As we have many vendor catalogs, it is a full person's job.

In our requirement, we want to build a functionality in our middleware where we will call the vendor's API, convert the catalog data into CMR format, and then push the data into D365 via OData/ DMF. Later the workflow would kick in to approve/ reject/ update the products. This process will remove the steps to manually upload the CMR file.