Dynamics 365 Supply Chain Management

Currently, when a purchase order line is cancelled, any markups or charges that were previously associated with that line remain included in the purchase order totals. This leads to an incorrect total value, as the markup from a now-irrelevant (cancelled) line still contributes to the PO total calculation.

This behavior can cause confusion and inaccurate financial reporting, especially when users rely on the purchase order totals for cost validation or approval processes.

Expected Behavior:

When a purchase order line is cancelled, any markups or charges linked to that line should be automatically excluded from the purchase order totals, ensuring that the total value accurately reflects only the active lines.

Business Impact:

Prevents incorrect financial totals on purchase orders.

Reduces manual effort needed to review or remove markups after cancellations.

Improves accuracy and transparency for users handling large or complex POs with multiple lines and charges.

Incorrect Item number is reflected on Released product details after the creation of Production order/ SO/ Planned order after enabling the following features "Display product info in user's language" and "User specific product name and description" and activating Product information management parameters "Show specified language" and "Show user language" and defaulting a personalized View after adding new filed in the General fast tab in the Item card ex. “Created by” and “Created date and time”.

When performing 'Create items' to calculate average issues per month and standard deviation, the system in Dynamics 365 Supply Chain Management includes inventory transactions with the status Deducted and sold in the Issue status. Goods in transit records that are sold to the transit warehouse are included in this calculation

The inclusion of goods in transit in safety stock calculations is by-design in Dynamics 365. Safety stock is calculated using all historical issue transactions, which includes both external usage and internal inventory movements (such as goods in transit). The calculation logic is built to consider all inventory movements, including goods in transit.

Currently, there is no native configuration to exclude goods in transit from these calculations. 

The issue is that an inbound transaction is used when calculating safety stock. In real life that will mean to big safety levels, higher inventory value and potential lots of stock getting scrapped because there is no usage for it.

Appreciate if we can get this fixed by Microsoft.

Purchase requisition prepared by the worker has been approved by the correct manager in line with the correct hierarchy.

In the form "Purchase requisitions for all my reports" a manager should view only the PurchReq of his direct report.

On the contrary, we encountered an error since another manager can see the PurchReq of a worker who is not a worker of his team.

Digging deep, the current employee was once assigned to that manager in the past back in 2022

We have found a similar issue reported before in bug#967030

The workaround is to delete and adjust the data in the PURCHREQREQUISITIONERFILTER here we have 2 Main Columns ORIGINATOR (Manager), REQUISITIONER (Employee Reporting to Manager)

However, we are looking for a fix from Microsoft to adjust this as the mentioned above is only a workaround

When performing a full license plate movement using the Warehouse Management App or the FO emulator with “Full LP movement policy” set to “Automatically move full LP,” the inventory status does not update as expected. After the put operation, the inventory status remains unchanged instead of switching

Technical Description

System grouping does not group works properly if the user logs out of the mobile device after performing the Pick operations.

Root Cause

The context for system grouping only works when the end-to-end scenario (Pick and Put) is executed in one go. If the user logs out after completing the Pick step, the system loses the grouping context. As a result, it processes each work individually instead of as a group.

Resolution

Ensure that the full workflow (Pick and Put) is completed without logging out. Logging out breaks the grouping logic because the system cannot identify which works were previously grouped.

Reference

https://fix.lcs.dynamics.com/Issue/Details?bugId=1072268&dbType=3&qc=6d655d5353feccb1a85c8c4539430ca01d8f2c822d6d2ced329c6120f6c8015a

When creating quality associations for items using the same flexible sampling plan, it is not possible to select the initial level that applies to the quality association. It will be initialized to the first level within the quality association form. 

As a result, achieving different starting levels for different items requires creating multiple flexible sampling plans with the same configuration but different initial levels, which significantly increases data maintenance.

For companies that can leverage just a few flexible sampling setups for hundreds of items that are set up for quality associations, this is an issue at the time of cutover if those parts are on different inspection levels at the time of cutover. It would be helpful if a field were added to the quality association form and the Quality order creation policies V2 data entity that would allow initializing a specific level in a flexible sampling plan, only when the quality association has flexible sampling enabled.

Description

Currently, when using moving average costing in Dynamics 365 Supply Chain Management, applying markup percentage for intercompany (IC) pricing only works if the on-hand value is added to the receiving warehouse.

However, this behavior does not comply with accounting requirements, as the full cost must land in the external COGS on the original sales order. This creates a gap between operational setup and financial compliance.

Problem Statement

• Using markup percentage for IC pricing under moving average can lead to incorrect cost allocation.
• The full cost is not reflected in external COGS, violating accounting standards.
• Additionally, item sales tax group for charges does not follow the item’s tax group, making the solution less feasible.

Suggested Improvement

Introduce a system enhancement that:

1. Ensures markup percentage for IC pricing under moving average complies with accounting requirements by correctly posting full cost to external COGS.
2. Aligns item sales tax group for charges with the item’s tax group for consistency.
3. Provides clear warnings or validation messages when users configure markup percentage with moving average costing.

Reference

Current documentation suggests using charges for IC profit calculation:

“You can also use charges to add a profit to an intercompany sales order by defining the charge as an intercompany percentage…”

Recommendation: Add a caution note in documentation and system prompts when moving average is used with markup percentage.

Business Impact

• Prevents compliance issues with external COGS.
• Reduces manual adjustments and audit risks.
• Improves reliability of intercompany pricing and tax handling.

Introduce native support for inventory counting journals within the MHAX (Material Handling Equipment Interface) in Dynamics 365 Supply Chain Management. This enhancement would allow automated material handling systems to participate in inventory counting workflows, improving accuracy, reducing manual effort, and enabling real-time reconciliation.

Problem Statement

Currently, MHAX is limited to executing warehouse work such as picking, packing, and movement. It does not support inventory counting journals, which are essential for maintaining accurate stock levels. This gap forces warehouses to rely on manual processes or separate mobile devices for counting, creating inefficiencies and potential data mismatches.

Extend MHAX capabilities to include:

• Inbound counting events: Allow MH systems to report counted quantities directly to WMS.
• Outbound counting instructions: Enable WMS to send counting tasks to MH systems via MHAX.
• Event mapping: Introduce new MHAX event types for counting journal creation, update, and completion.
• Validation logic: Ensure counted quantities are reconciled against expected on-hand inventory.

The query responsible for calculating the summation is only triggered when the user changes the view, and not when simply opening the form, regardless of which view is set as default.