Dynamics 365 Supply Chain Management

When creating work for replenishment, the put-away location is the same for two items, resulting in one pick/put work per item. This issue arises when creating multiple replenishments of the same items where the demand isn't for full pallets. Adjusting location stocking limits and changing the quantity per LP doesn't resolve the issue.

The strategy "Empty location with no incoming work" is not evaluated as part of the replenishment work creation. Consequently, the second replenishment work with the same put location is created.

Fix request number: 441273. Microsoft has evaluated this issue and determined it to be a feature limitation. A work item has been added to the product backlog to enhance the capabilities for this functionality.

Enhancing the replenishment work creation process to evaluate the "Empty location with no incoming work" strategy will improve efficiency and accuracy, benefiting customers by ensuring more reliable replenishment processes.

LCS: 441273

Confirmed ship date on intercompany sales order can't be updated using the Sales order lines V2 data entity

Without it, users need to do it manually which leads to process inefficiencies and utilization of users to the task that otherwise should be possible to be automated. This leads to additional cost to the business

The new feature of over picking during raw material picking ensures warehouse workers can support production in the best possible way. In addition, cluster picking is a useful way of working to ensure warehouse workers only visit a location once.

However, the over picking functionality is not available for cluster picking and provides a limitation and potential stop in using cluster picking. Please consider this idea and add full support for over picking during cluster picking.

When registering a production order for a single ItemID that includes multiple InventBatchIDs on one License Plate, the system creates multiple cross docking works. This causes inefficiencies, especially when there is one work template for cross docking with four steps (pick/put, pick/put). The current functionality does not accommodate processing with one License Plate created in production posting, leading to a fragmented workflow and operational challenges.

We propose an enhancement to allow the creation of a single work that accommodates multiple batches on one License Plate this can be by either a parameter or a setup on work templates to control whether work headers should be merged or split. 

If there's been any modification done to a "received" transfer order like removing a line, the status is changed to "created" and the line is removed. The customer doesn't want to apply security to the "remove" button as this is a labor intensive and time-consuming path for the registered user to apply the modifications for every time a modification has to be done. The customer wishes to have a "finalize" feature similar to the one available for purchase orders for transfer orders to keep them locked after the "received" status.

Trade allowance management helps companies manage sales promotion programs that offer "pay-for-performance" monetary rewards to customers that achieve volume and behavioral goals. The feature’s capabilities are designed for companies that focus on comprehensive promote-to-profit processes, from promotion fund budgeting and allocation, to allowance contract setup, to claims creation and processing, to payment processing, to promotion effectiveness analysis.

Unified pricing management currently does not support / work with Trade Allowance management. In other words, Trade Allowance Management behind the scenes still uses legacy trade agreements for Off-invoice discounts and legacy rebates for Billback discounts. Trade allowance management could benefit from the price attribute capability of Unified pricing and the enhanced capability of the new Rebate Management module. Unfied pricing can benefite from the fund analysis and promotion effectiveness analysis that Trade Allowance Management supports.

It is extremely difficult to explain to customers that these concepts do not play well together and are not "unified".

This is a feature gap that denies the customer from supporting his business scenario. He wants to the "Requester" to be the "First Approver" in the purchase order workflow. Currently, it is only allowed to choose the requester as the starting point for the hierarchy's approval, but he is unable to approve the workflow.

For example, in the Dynamics 365 Finance update from April 2024, there is a feature that allows the purchase order's requester to be added as the invoice approver in 10.0.39. This means that the requester can be involved in the approval process right from the beginning, ensuring that any discrepancies or issues are addressed promptly.

At the moment the favorites are sorted on alphabetical order.

It would be very nice when users can changes this manually by dropping and dragging their favorites (like in an internet browser).

Issue: In pricing management, in discount journal, there is a field where we can add discount posting account, but the issue is that account is not hitting in sales order invoice journal. It is fetching from item group only. So, this is a limitation if we need posting of each discount in ledger.

Idea: It will be feasible if discount journal accounts are reflected in invoice journals so that we will get the separate postings from each journal.

Need to provide the possibility to change the currency in the header of ‘Freight invoice details’ (Transportation Management > Enquiries and reports> Freight invoice details)

Currency comes from a Ledger configuration, and there is no way to change currency manually - the field is blocked for editing.

In a scenario when a company receives freight invoices in EUR but automatically, the currency field for new record filled in with USD it is needed to use a workaround to change the value. It is inconvenient when most quantities of freight invoices are not in LE currency.