Dynamics 365 Supply Chain Management

The current session logoff functionality introduced via the Work User Access Policy in D365 SCM does not fully support the "User and password" authentication method on mobile devices. This creates a security loophole and usability challenge, especially for industries like Pharma where strict access control is mandated by regulations such as 21 CFR Part 11.

There are two authentication methods for mobile devices:

1. Device Code Authentication – One-time login with a device account, followed by warehouse worker login.
2. User and Password Authentication – Requires login with a Dynamics user account, followed by a second login with a warehouse worker account (often automated via Default User).

The session logoff currently only affects the second login (warehouse worker), not the primary user login. This leads to:

• Security Risk: After session timeout, users can cancel the warehouse login and reconnect, automatically regaining access via the still-active primary login.
• Compliance Gap: This violates regulatory requirements for access control and auditability for companies like Pharma Companies
• Usability Issue: Users are forced to re-enter warehouse credentials they may not know, while the actual user session remains active.

Proposal:

• Extend session logoff to also terminate the main user session when using User & Password authentication.
• Ensure that after timeout, users must re-authenticate with their Dynamics credentials.
• Prevent automatic re-login if the session has expired.

This change would close a security loophole, support compliance, and make the preferred authentication method more practical for real-world use.

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

With the current logic of planning optimization there is a gap for the firming of manual created planned (batch)orders. Those will not get exploded after firming.

As the production order is created in status sheduled you would expect planning arranged the explosion of the phanom items but it did not.

From that point you can decide to 're-schedule' The production order. Only the outcome is completely different on quantity/processing time aswell secondary planned resourced. Therefore this order must be deleted and recreated via masterplanning or created manually.

This proces has a big chance of making mistakes and therefore the proposed workaround (re-run the masterplan for every manually created order is very tricky.

Idea: Always explode items of type phantom during firming the planned batch order while using planning optimization.

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.

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.

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.

When the accounting currency, reporting currency and PO line currency is different, there are two voucher transaction for posting type of: purchase expenditure for product when post purchase order invoice and the value is not 0. Customer needs to manually adjust the general ledger.

This issue has been logged in Issue 838716 and currently is a design limitation. We will continue to track this issue and monitor if other customers are impacted. Please help Vote if you have the same requirement, we will improve our products and services.