Dynamics 365 Supply Chain Management

Catch weight items cannot be assigned a unit of measure that has a precision level rather than 0 in the catch weight unit field.

It is important to remove this constraint and allow users to assign a unit of measurement that has rounding level.

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.

Issue Description:

Today there’s an inconsistency in how “best-before date” is evaluated for batch-controlled items:

• MRP/ATP validate shelf life based on the sales order ship date.
• Warehouse reservation (Release to warehouse or manual “Batch reservation”) validates against the requested receipt date.

This mismatch leads to practical issues: ATP can show availability, but when attempting to reserve, the Batch reservation dialog returns no selectable batches (blank grid) because the receipt date check is stricter than the ship date logic used by ATP/MRP. This creates confusion for users and blocks standard flows (especially FEFO/shelf-life scenarios with transport days or sellable days).

Proposed Idea:

Add a configurable parameter to control which date the reservation engine uses for best-before validation, so customers can align Warehouse reservation with their ATP/MRP logic.

Currently it´s not possible to use LP receive functionality on GIT orders even though it´s possible to receive and create an inbound load on a landed cost purchase order line. If this was enabled, warehouse operators could use the same receival process in the WMS app for registration of inbound goods regardless of the type of source document (since LP receive already supports both transfer orders and regular purchase orders).

Searching on hierarchy node is possible in D365SCM, but only on full names. We would like Microsoft to expand this functionality to also support partial matches.

This includes searching on standard forms like searching a sales category in the sales order lines, as well as in the new Unified pricing management functionality where category searching is needed for example in the Margin component price adjustments lines and trade agreement lines.

Limitation: In Pricing management module, we need to apply discount on sales order based an attribute named "Method of payment". But it is fetching from customer master, logically, it should fetch from sales table.

Logic: "Method of payment" changes frequently, so every time while creating sales order, will have to make changes in customer master to reflect in sales table.

In many cases we don't know which asset that is an issue. We've to create the work order and plan it to a worker. Then after some time we know which asset. Then its's of course to late.

It would be great to be able to only change the asset/location on the line.

Not change the job type, variant and trade.

The system should give us possibility to allocate voyage costs directly on vendor invoice journal without using "select voyage" functionality. All necessary fields to describe the voyage are on invoice journal line: Cost type code, Cost area and Reference. Thanks to this idea a user will be abble to assign voyage costs much more efficient and have all information about cost directly on vendor invoice journal lines.

Counting Reason Codes can be assigned to Adjustment and Movement journals but don't appear to be fully supported. For example:

• Offset Accounts specified against Counting Reason Code are used for Counting journals but not for Adjustment/Movement journals
• Counting Reason Code Policies (to enforce mandatory use of a code) apply to Counting journals but not to Adjustment/Movement journals
• Entities for Counting journals include Counting Reason Code field but those for Adjustment/Movement journals do not

There are no doubt other bits of functionality to which the above also applies. Since the Counting Reason Code field is available within the client for all three journal types, one would expect the functionality to be consistently supported for all three journal types.

When a purchase order is created from an approved purchase requisition line, the Approval status on the PO is set to "Approved" even when the Activate change management parameter is set to "Active" and an active Purchase order workflow configuration exists.

There was a previous Microsoft Idea that has been completed for this: https://experience.microsoftcrmportals.com/ideas/idea/?ideaid=1b8b981b-438f-e711-80c0-00155d7cd0b4

However, as confirmed by Microsoft, this is currently only active for customers that have the configuration key 'Public Sector' enabled.

Our customer in Industrial manufacturinghas has two distinct processes:

• The requisition process with an approval workflow which takes place "in the business" and where department managers can approve requisitions for their employees
• The second process takes place in the procurement department where buyers prepare the purchase orders and pricing and then submit the purchase orders for approval via a separate approval hierarchy with stepped signing limits.

The suggestion here is to open up this already developed feature outside of the Public Sector Configuration Key.