Dynamics 365 Supply Chain Management

If you perform a cost calculation for a standard cost version now, phantom items are expanded before the calculation, but when you perform a cost calculation for a planned cost version, phantom items are not expanded at the beginning, so results are different (indirect cost differ, for example).

Default financial Dimension given in the main account (Inventory loss and profit account) must be updated in the ledger account after doing the Inventory recalculation (Settlement). Subsequent inventory recalculation of a BOM Journal does not correctly transact to financial dimensions assigned in the BOM journal.

When the user is trying to make a new engineering product, the user will select a engineering product category. On the category an engineering release policy is defined. On the policy the template of the releases product is defined. Then on our template we defined a default configuration. But when creating the new engineering product the customer has the ability to select other configurations then the default one on the template. The result is that a wrong product variant is created and the default on the new item is not existing. Which is confusing.

Expectations:

• The system should not allow selecting a different configuration on a new engineering product from an existing engineering category when there’s a default configuration originally defaulted on it originally on the template.
• The dropdown menu "Configuration" on the new engineering product should show only the configuration created for the template associated with its category. 

Inventory Management>Common>Picking Workbench>Picking Session>Set Up Batch

The picking workbench offers some functionality over the "Generate picking list" process or posting a picking list directly from the sales order. However, the picking work bench has poor performance in comparison because the process is single threaded even when configured to run as a batch.

This can cause problems, particularly for retailers who typically have a large volume of orders and may not have staff working 24/7 to manually run follow on processes.

Adding multi threading could make the picking workbench a viable option for them.

The customer is using engineering change management to create items the only available types are formula and BOM, but if the customer wants to have a co-product, he should not use the engineering change management.

The only workaround for this issue is to have customization, but customer is looking for a standard solution.

If the Storage Dimension group of a product is WHS enabled, it is not possible to change site/warehouse in the batch reservation screen for SOs.

Currently it is only possible to search for batches which conform to customer specific batch attributes via a sales order, which requires site and warehouse dimensions to be specified. Without WHS enabled Storage dimensions and specified reservation hierarchy, the site and warehouse can be changed on the batch reservation pop up against the sales order line, however if it is enabled, this is not possible and the user loses stock visibility.

A solution which enables the user to search across multiple sites for batch which match the requirements of the customer is needed. Enabling customer batch attribute searches in a modified stock list screen, or via batch reservation on a sales order line, would prevent issues planning the fulfilment of demand when customer specific batch attributes are used.

Issue:

• While validating (pass or fail) a quality order having the "update inventory status" flag enabled, the system will modify quantity of another quality order when item's on-hand is against the same inventory dimension. Both quality orders are generated from distinct/unique production orders.

Idea:

• I think it would be good enhancement in the product to identify the referenced transactions (in this case production order) and update only the inventory status for the given related quality order.

Customer has extended at a customer our ItemIdBase data type from 20 to 60 characters.

It all goes fine within D365FO until we try to Release a sales order to the warehouse for an item number with a length of 60 characters.

However, as this is a platform kernel issue, PG concluded that it is less likely to be changed from code point of view.

Customer posted on Yammer to raise awareness in case multiple users can benefit from this additional functionality and we have raised this idea for the same to be tracked internally.

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.

When using the Purchase requisition workflow, if an approver requests change, after the orignator resubmit it, the workflow will be canceled and goes back from the beginning instead of going back to the approver who requested the change.

We suggest it goes back to the approval to save time wasted on this