Dynamics 365 Supply Chain Management

Currently to enable the "Use license plate tracking" setting on a location profile, we must to empty the location quantities and close all financial transactions using the locations in the location profile to be modified. This mean all purchase order and sales order must be invoiced, all production order must be eneded.

For an organization that has outstanding work, it is very complex because it is not possible to stop production lines, and it is very difficult to ask suppliers to send all invoices.

Description of the Issue:

When approving a price-based, invoice-attached deduction from the Deduction Workbench, the Item Sales Tax Group is not populated on the resulting free text invoice—only the Sales Tax Group is. This occurs specifically when an invoice is attached during deduction creation and does not happen if no invoice is attached. 

According to feedback on issue 1036561, the underlying reason is that Free Text Invoices are not inherently tied to the item-level data that Sales Orders use. Therefore, attaching an invoice during deduction creation does not carry over the item tax metadata to the Free Text Invoice. The deduction logic treats this scenario as a financial claim, not a product or item-based transaction, so it bypasses Item Sales Tax Group population.

Idea:

It would be valuable to reintroduce or provide the capability to select and maintain the Item Sales Tax Group on the Free Text Invoice even when an invoice is attached during the deduction approval process. This could be implemented as a dropdown or selection option that becomes available (or remains available) in the deduction approval process, ensuring the Item Sales Tax Group is not lost and avoid manual entry of the sales tax group.

Customer configured the Plan group and Priorities for Formula/BOM version lines of a finished good item (FG) in a way that Priority 1 item does not have on-hand while others have. Via Demand forecasting a Planned batch order for the FG is created and after running the derived requirements, the system is generating the Planned batch order for the Priority 1 Formula/BOM line item without consuming available on-hand quantity of Priority 2 or Priority 3 Formula/BOM line items.

Many customers are suffering from the same issue. Kindly reconsider the outcome on the LCS.

In the current version ( .44 ) the system allows total discounts in sales together with UPM, but applies them only if the total discount group of the sales order header ( or sales quotation ) match the total discount of the customer master data. If I change the group on the sales order header ( or sales quotation ) , the system does not apply any discount. What must be valid is only the total discount group that I have at the customer order level.

Bring in mandatory "item", "site" & "warehouse" & "location" selection, with override check box on the "location" to affect all available inventory in all of the locations for that "site" & "warehouse".

I would consider including pulling in the site & warehouse off the "worker record" if only one, or validating entry based on "worker" record and "allowed warehouses". Also ensure a "batch log" is maintained for this process, as it appears it currently does not

Other tickets have requested to allow for a quantity choice under this menu, this could be incorporated into this change.

Please note in my opinion the current "Periodic" menu "Warehouse management inventory status change" is very poorly controlled and an extremely dangerous menu if misused accidentally or otherwise. There is very little application of it in its current raw format, that any company would ever use. Further, in the event a user missed selecting an item or location in the query, all stock of all items in all locations will be picked up by this menu and the status of stock changed. The complexity increases if other stocks already exist at the selected "to status".

The recovery from such an event is enormous, complex and not provided for by Microsoft current design and reporting,

I recommend if changes are not to be made above, it be disabled/remove or a specific "security privilege" be provided to remove from staff access

The app is not operating consistently that some variants are displayed in POS, but not in Power Apps.

Hence, MS might enhance the logic on On-hand mobile app that ensure that all the data are presented.

Customer has been using the Inventory On-hand Mobile App in D365 SCM for a year. It works well, but they're facing performance issues when loading items with many variants (size, color, style...) both in App and POS.

The loading time is significantly delayed (40-50s), which affects user experience.

Therefore, FnO might need to improve the logic of the Inventory On-hand Mobile App that make the loading time reduce to 5-7s for items having several variants (around 12,000 variants).

AXUTIL is an utility provided by Microsoft to generate the license for ISV solutions. In 2023 there was a change across the globe that providing PFX file containing the certificate and key is a security threat and hence the providers stopped providing PFX file. Instead, they started by uploading the certificate and private key in to Azure Key Vault, to be safest and with no options to export the file.

License generation Azure pipelines created to pass the pfx file started failing once the pfx file validity was expired. This has caused a major problem as the Azure Key vault integration with AXUTIL has not been incorporated. Now ISV solution can not generate the license as AXUTIL was never designed / nor updated to access from Azure Key Vault and expects PFX file which is not available to pass that to AXUTIL. This is a dead lock situation.

-> Currently, when confirmed ship date in sales order line details are filled in, confirmed receipt date field will be auto-populated based on the calculations.

But when confirmed ship date field is getting cleared by the user, confirmed receipt date is not getting cleared automatically and it stays which makes user to manually clear it.

Users have to manually clear it otherwise it is getting calculated in MRP calculations.

Along with it, these date fields are not linked with each other in Purchase return order process as well.

When broker contract is set up with an amount type of "Quantity", the system does not convert units of measure correctly when sales lines are entered in a different unit. As a result, broker commission fees on sales orders are calculated based solely on the entered quantity, without validating the unit of measure. This leads to incorrect commission charges being applied, even when they should not.