Dynamics 365 Supply Chain Management

Customers reported an issue where inventory marking is automatically applied to a virtual inventory transaction when creating a PO from Purchase Requisition or manually from the All Purchase Orders page. Unlike the first scenario (creating a PO from an SO), where the marking can be manually unmarked and reassigned to another PO, this second scenario does not allow manual unmarking. Attempting to unmark results in the following error:

"Manual marking is not allowed because the inventory transaction is linked to a virtual inventory transaction."

Customer Configuration & Context:

• Project module: Not used
• Item requirement: Not used
• Setup: Customer only creates a Project ID and Contract ID
• Business Impact: Prevents users from manually managing inventory marking as needed, leading to operational inefficiencies.

Investigation Findings:

• The issue is reproducible in standard D365 FnO.
• The FIN team confirmed that this behavior is by design, but they could not provide further details on the logic behind it.
• There is limited documentation on this specific scenario, making it difficult to confirm whether this is the expected system behavior or a potential enhancement area.

Request for Clarification:

1. Can you confirm why marking is enforced automatically in this scenario and cannot be unmarked?
2. What system logic drives this behavior when no Item requirement or Project module is used?
3. Is this behavior expected, or should it be considered for improvement in a future release?

We would appreciate any insights or guidance you can provide

The user input and validate Quality order with wrong batch number and they need to back to reopen quality order and Edit test results and Validate again. But they could not validate the quality order again because of the error: “You cannot block xxxx items. Only xxxxx items are available on the inventory for item xxxxxx”.

This is “bug” from using “Reopen” function on a closed quality order. It needs to be fixed. There are too many wrong quality orders and each quality order contains many test group lines – in short, there are too many input to create a new quality order. Please reconsider your solution.

It is not possible to enter items in quotations or sales orders via the product search (product name) if the product name is longer than 20 characters and several products start with the same product name. This will result in the wrong product being entered in the quotations and sales order lines. However, it is possible for items with more than 20 characters to be created as a product.

There is no Engineering Change Management (ECM) category to choose, which is odd, but this should fall under that category.

Currently engineering product categories are designed to only apply to a portion of the item master because they can only be created with a production type of BOM or Formula. The means that any co/by-product that is output on a formula cannot be engineering controlled, because they would have production types of Co-product or By-product. This means the following functionality cannot be utilized on an entire item master. (Listed on the Feature Overview from the MS documentation)

• Product versioning
• Enhanced product release functionality that lets you maintain product master data in one legal entity (the engineering company) and publish the fully configured released product to other legal entities
• Rules for validating that required information is entered before a product version is activated (readiness checks)
• Improved product lifecycle management through fine-grained control over when a released product can be used in specific business processes
• Engineering change requests that are supported by workflows
• Engineering change orders that are supported by workflows

In Bom lines, two fields InventStatusID and WMSLocationId can be edited via frontend UI but at the time of bulk update using DMF (Data Management Framework) or Excel Add-In,stops at staging, target feilds is not updated

Reason:For a new customer, during migration or bulk data upload , this causes a problem.  

When we create a Condition assessment registration on an Asset form, it shows all the templates, not the only ones for that specific Asset type.

More details: ISSUE 776334

Currently, if two products are assigned to Serial number groups that call the same Number sequence, and Production orders are created concurrently (either manually or by Firming planned orders), the system can enter a "race" condition where non-sequential Serial numbers are issued to each order.

For example, Order A is issued Serial numbers 1, 2, 4, 6; Order B is issued Serial numbers 3, 5, 7, 8.

The race condition usually occurs on large-quantity orders due to longer processing times; large quantities also make it more challenging to identify where the non-sequential discrepancies occur.

The concern is for traceability, especially in regulated industries. Non-sequential Serial numbers for a group of products (particularly those originating from the same Prod order) could lead to labeling errors and documentation discrepancies, especially when the ERP must interface (directly or indirectly) with external systems like a lasermarker that would etch the serial number on the product.

Microsoft indicates that the limitation is due to the way the system generates transaction numbers from number sequences. A solution could be implemented via the Tracking number group module to limit the impact, as opposed to directly in the Number sequences module which has wider systemic exposure.

I have noticed that SalesOrderHeaderV2Entity got deprecated and released new entity SalesOrderHeaderV3Entity when upgraded the version from 10.0.35 to 10.0.36. All of sudden post upgrading to 10.0.36 import and export operations not working on Sales order headers v2. Looking forward for Microsoft to take up notice of this request and provide a fresh new document detail lists of data entities marked as obsolete on every new Finance and operations release version.

SysQueryRangeUtil methods as they are described here:

https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/fin-ops/get-started/advanced-filtering-query-options do not cover the customer requirements. The customer wants to filter for example all orders to be release to warehouse for the next comming 3 hours. WIthin the standard filter options this is not there.

In my scenario I want to setup query and filters for different filters and batch job to be able to filter and select based on time windows

At this moment there is only the option to do this by days and not per hour or minutes.

Below the missing options within the current standard

• (HourRange(-5,0))
• (MinuteRange(-5,0))

This would be a great added value to have these options within the standard advanced filter oprtions.

Having multiple product receipts and linked Quality orders generated for a PO line, D365 doesn't allow to register supplier's invoice against a product receipt for which the Quality order is already passed.

Example: For a PO with a line qty of 100, there are 4 product receipts, and 4 corresponding Quality orders open against them. When for the first receipt the quality order is passed and while other quality orders are still open, D365 doesn't allow to register a supplier's invoice against that product receipt.