Dynamics 365 Supply Chain Management

• Existing functionality is that a Vendor can upload a Purchase order Invoice via their workspace. If there is a Vendor invoice workflow configured Vendor will submit Invoice to Workflow.
• Under non-collaboration workspace scenarios the Vendor invoice workflow can be configured to auto post if the Matching process passes.
• However, if the Invoice is created in the Collaboration Workspace and submitted to workflow, the standard functionality does not behave in the same way and the matching fails and the AP Clerk must manually match and post the invoice.
• This was reported as bug but Microsoft state that the behaviour is by design. The rationale behind this design is that “it allows the Vendor the possibility of adjusting invoices even after their initial creation”.
• What is required by Dynamics customers is the introduction of a parameter or indicator that allows Vendors to specify whether the invoice is complete when they upload the invoice in the Collaboration Workspace. If this parameter is set to YES this signifies the Vendor has confirmed the Invoice is correct and the system will then automatically initiates the submission for the automatic matching process.

Standard costing calculation should reflect yield for phantom lines. Consumption is calculated correctly but standard cost calculation does not reflect yield other than 100%.

Microsoft Issue 760071 indicates that this is by design. It is not. It is a bug and needs to be fixed.

In the mobile device menu item indirect activity Register material consumption, there is currently no way to define Default data. E.g. it would be logical to set the machine location as a default location to consume from, or to set qty = 1 when you typically scan serial number items.

In the current D365 Finance and Operations Landed Cost Module, actual cost adjustments cannot be reallocated across remaining purchase orders if one is canceled after posting the vendor invoice journal. This requires users to cancel all related POs and restart the voyage, which is time-consuming and inefficient.

This idea proposes a Dynamic Cost Reallocation feature to automatically recalculate and redistribute landed costs (e.g., BAF, freight) across active POs when a PO is canceled or modified after initial cost posting. This feature would trigger a reallocation across remaining POs without needing a full voyage reset, saving time and enhancing accuracy in cost distribution.

Key Benefits:

• Operational Efficiency: Eliminates the need for full voyage cancellation, streamlining the adjustment process.
• Accurate Cost Allocation: Ensures that costs are dynamically reallocated only to active POs, reducing discrepancies.
• Enhanced Flexibility: Enables adjustments post-vendor invoice posting, supporting real-time cost accuracy and integrity.

This feature would provide a more flexible, user-friendly landed cost process in D365 FO, improving overall cost management and accuracy.

Catch weight items cannot be assigned a unit of measure that has a precision level rather than 0 in the catch weight unit field.

It is important to remove this constraint and allow users to assign a unit of measurement that has rounding level.

Currently it´s not possible to use LP receive functionality on GIT orders even though it´s possible to receive and create an inbound load on a landed cost purchase order line. If this was enabled, warehouse operators could use the same receival process in the WMS app for registration of inbound goods regardless of the type of source document (since LP receive already supports both transfer orders and regular purchase orders).

Scenario:

1. In the procurement and sourcing parameter > General > Calculate purchase order delivery date based on lead time and working days is "Yes".
2. When create a new purchase order, on the items where the Vendors do step up the trade agreement on the items with lead time plus the working days.
3. In the PO lines > Delivery fields lead time is always "0" and not updated from the trade agreement.

Expectation:

If the lead time is displayed, users will immediately know the lines Requested ship date taken how many days in calculation.

Business Justification:

The display of the lead time is able to view and immediately to know the lead time taken when purchase on the items. If the lead time is wrongly configured and users can immediate rectified and confirm with their buyer.

Searching on hierarchy node is possible in D365SCM, but only on full names. We would like Microsoft to expand this functionality to also support partial matches.

This includes searching on standard forms like searching a sales category in the sales order lines, as well as in the new Unified pricing management functionality where category searching is needed for example in the Margin component price adjustments lines and trade agreement lines.

In version 10.0.38 Microsoft made a feature where it is possible to report as finished batch orders with 0 good quantity for standard items for the following scenario:

When you planned to produce something. Maybe you started operation 10 and that failed and you stopped the order and operation 20 and 30 are not executed and thus you don't have any RAF output on the production order but you have spent time and material.

Another possible scenario is that you have 0 good quantity and only have bad quantity that you report as finished.

Moreover in both scenario's when you want to end the production order you receive the following error message:

Production: XXXX Missing report as finished quantity.



So, for both scenario's it would be nice to end the production order with a 0 good quantity.

Limitation: In Pricing management module, we need to apply discount on sales order based an attribute named "Method of payment". But it is fetching from customer master, logically, it should fetch from sales table.

Logic: "Method of payment" changes frequently, so every time while creating sales order, will have to make changes in customer master to reflect in sales table.