Dynamics 365 Supply Chain Management

When enabling the parameter "Expected receipt" on an Inventory blocking record, ATP immediately considers the inventory as available. However this can be restricted by the "Expected date".

Just like any other supply order, the delivery date (expected date) should be honored within ATP calculation

Add a new Data Entity in the Data Management addressed to import the 'Configuration Rules' within the Bill of Materials (BOM).

Send a push message to the worker or a group of workers, all or active only workers in the (new WMSv4) app

This would allow the warehouse manager to request a few workers to finish the current pick work in Pickzone 1 and move over to Pickzone 2, or to announce that there is a celebration in the cantine.

The message should be signaled by a sign (red circle with number of messages) in the top right, like in many apps incl. the yammer viva engage app)

It should be displayed in each screen (not only the start screen or menu), also when the user is executing a work.

The worker can press on the symbol to view the message(s).

https://www.yammer.com/dynamicsaxfeedbackprograms/threads/3217059061481472

Unexpected Quantity and Substitution variance is generated on the Production orders when using Resource groups on the route.

The Resource requirement for the route operation is set for a resource group. The standard cost is calculated considering the resource group as the resource (Item/Resource column)

When the production order is scheduled, the actual resource (which is part of the resource group) that will be performing the operation is suggested. Therefore, the realized cost for the production order is based on the consumption of the routing operation performed by the actual resource.

When ending the production order the system incorrectly calculates Quantity and Substitution variance due to the fact that the standard cost calculation includes resource group while the realized cost includes the actual resource.

Given that the resource group and the resource have the same cost categories configured, the system shouldn't provide any variance in this scenario.

When posting production order for item with costing method is standard cost, and production order has error quantity which will be scrapped the cost of error quantity is posted to quantity variance account not to the assigned scrap account.

The production performance and efficiency might be distorted, and the quality issues might be hidden.

Production Quantity variance posting account is being used instead.

Required: to get the error quantity cost to be posted in Scrap account assigned.

Actually, it is only possible to add costs, create voyages, and use the different features of Landed costs module regarding the purchase process.

However, a lot of our customers ask us to be able to add costs, create voyage, tracking goods and record 3rd parties invoices regarding the sales process.

Indeed, the cost price of the item will not be impacted but it will be easier to see the margin and it'll improve transportation follow-up on sales side a lot.

Finally, the landed cost features, if replicated on sales side, is way more easy to use than transportation management module for outbound transportation when customer does not track routes and rates.

When we enable the new feature Price management in version 33, then a new menu item – Complete - appears on the sales order detail form. The sales order header is then created with label set to “Do not process = Yes”.

The sales order needs to be “Complete” before you can run Order confirmation, Packing slip, etc, or Release to Warehouse. And then you need to use Modify if you need to change or add more lines.

Schedule maintenance works for workers only from the chosen maintenance worker group, when it exists.

Nowadays, when scheduling a work order that has a maintenance worker group filled in in the header, the system does not respect the group of employees and schedules the work for employees outside of the group. 

Our client has standard item coverage and warehouse item settings for product templates which they would like to be inherited to the newly created items.

Currently they would have to create a released product and separately update the item coverage and warehouse item settings. It would ease some of their work if there is a parameter which can enable this functionality.

Thanks!

Current Limitation:

In D365FO, the only way to control automatic cycle count approval is through parameters set at the worker level. This approach is too broad and fails to account for the varying financial impact of discrepancies across different products. High-value items, for example, should be handled with much greater scrutiny than low-value items.

Proposed Enhancement:

Add functionality to set cycle count approval parameters at the released product or product variant level. This would allow businesses to define specific thresholds for automatic approval based on both quantity and value deviations tailored to each item.

Why This Matters:

• Critical Risk Management: High-value items should not be automatically approved if even minor discrepancies occur. Allowing item-level control ensures that these items are flagged for manual review, reducing financial risk.
• Operational Efficiency: For low-value items, automatic approval of minor deviations can streamline operations, freeing up resources to focus on more critical areas.
• Flexibility and Precision: Businesses can fine-tune their cycle count processes, aligning them more closely with the financial significance of their inventory, leading to more accurate and reliable inventory management.

Call to Action:

Implementing this feature would greatly enhance the control and efficiency of inventory management in D365FO, making it a valuable addition for all users. By allowing item-specific parameters, we can better manage risks, optimize resources, and improve overall accuracy in the cycle count process.