Dynamics 365 Supply Chain Management

A customer that we work with has a great amount of sales orders going out each day and the confirmed receipt dates are used to communicate when the end customer can expect their delivery. To generate a confirmed receipt date, the ATP or CTP for planning optimization delivery date control methods are used, depending on the item settings.

However, when an item is set up with delivery date control = CTP for planning optimization, there is a big chance it will cause issues for certain end customers based on the below scenario:

SCENARIO

Available on hand: 43 pcs for item A (No ordered or on order transactions at the time). Item A is a BOM component.

ORDER #1

Created: 20241107

Requested ship date: 20241201 (future requested date)

Requested receipt date: 20241201 (0 days of transport lead time, this doesn´t really matter)

Quantity: 43 pcs for item B (Item A is included in the BOM)

After running the CTP for planning optimization, the confirmed ship date will be 20241201 since the available on-hand fulfill the required quantity.

ORDER #2

Created: 20241107

Requested ship date: 20241107 (today´s date, as soon as possible)

Requested receipt date: 20241107 (0 days of transport lead time, this doesn´t really matter)

Quantity: 10 pcs for item B

After running the CTP for planning optimization, the confirmed ship date will be 20241107 since the requirement date on order #2 is before the requirement date on order #1, even though order #1 is created before. A planned purchase order is then created to fulfill the remaining quantity for order #1. That means in theory that order #1, which we promised to the customer at 20241201, no longer can be promised on that date because the planned purchase order might take longer time to purchase and receive, and the MRP will suggest a potential delay for order #1.

The idea

It would be valuable if the CTP for planning optimization can respect the created date and time of the order line or ultimately respect when an order line has a confirmed delivery date. In the above case, such an improvement would mean that the quantity for order #1 is protected since the stock is allocated to the order line prior to order #2.

The above described scenario is for sure causing a negative impact for a customer that is placing a sales order well in advance, or basically any future requested date. The promised date to the customer might not be fulfilled since the system is generating new proposals based on the requirement dates with the current functionality.

The back button is a systematic feature and cannot be manipulated in terms of placement—whether at the top or bottom of the mobile menu items. While the system allows customization for the order of custom made mobile device menu items, it does not include the ability to reorder the back button.

This can be challenging for businesses with extensive lists of mobile device menu items, as workers may need to scroll down on their PDAs to access the back button and navigate to the previous screen.

This would be a great feature to let the business decide where they want to place the default back button.

Currently forecast planning is not supported with planning optimization.

This leads to no possibility to exclude safety stock from planning and the ability to build Sales and Operation Plan.

We have a specific requirement regarding the inventory aging report functionality in Dynamics 365.

Currently, the system displays the age of inventory items per warehouse. However, when an item is transferred to a different warehouse, the aging of the item gets reset.

Our requirement is that the aging of the item should not reset upon warehouse transfer. The aging should continue to be based on the original receipt date — that is, the date when the item first arrived or was purchased by the company.

We are considering using the Product Receipt Date or the Physical Receipt Date from the original purchase order as the reference for inventory aging.

When using the GIT order process merging Procurement & sourcing and Landed cost, the business process should be as the following:

1. The PO is created for a batch tracked item, approved and confirmed
2. Delivery term has the "Goods in transit management" toggle enabled
3. The voyage is created and the PO line added to the shipping container.
4. The PO invoice is posted before the goods are received, therefore the GIT order is created.
5. In the industry, the batch number is still unknown as the goods are not received yet
6. Currently, there is a error generated by d365FO when doing so therefore the invoice cannot be posted
7. The GIT order is received
8. The vendor invoice journal for the voyage is posted.

In Step number 3, D365 should allow the business to post the PO invoice without a batch order as it is still unknown for the business. The batch number will become known when the GIT order is received.

The Idea is to have D365FO handle to post the PO invoice without the batch number as per the business process of the industry is even when using the Primary stocking field on the tracking dimension group.

Currently it is not supported to post the PO invoice without a batch number when using the "Primary stocking" in the Tracking dimension group, but this should change. Please see the following issue:

Details for issue 665089

https://fix.lcs.dynamics.com/Issue/Details?bugId=665089&dbType=3&qc=b887d63067ed02496f7a950f3351e23191b586c7e41760b40afcb0b134534962

ISSUE:

When using the mobile device menu items mode indirect and activity code: data inquiry, you can make list pages (CARDS) on nearly every table ind D365F&O with filters. Enabling warehouse workers to have very intuitive approach to warehouse operations and start up of different work processes based on the lists. The list has a force since they do not give any limitations as to what fields can be displayed on the CARD - just they are on the table or method() . Adding mobile device steps and detours to the data inquiry can kick of the process of different work and later returning to the list / Cards and kick of yet other work. Unfortunately when returning to the list this is not refresh with the query that is actually saved on the mobile device menu items on entry. Meaning you need to leave the list and go back to the menu and back again to have the list refresh and see what is yet left to do.

IMPACT:

The refreshing the data inquiry list after processing work gives the user two extra keystrokes / mouse click that they need to do to manually refresh the list of Cards, sometimes even reentering parts of the filter. Thereby having an impact of workers daily productivity. There is a great deal of gain on time and cost savings of having this done automatically.

IDEA:

Making a parameter on the mobile device step on the BRING BACK step where the query can be set to be refreshed or not. Of course it should be possible even if there is no setup done on the return BRING BACK to the start menu.

Hope this will idea will be considered.

Thank you for your time.

Best regards

Tom Schrader Poulsen

If a unit from the unit of measure table and a corresponding unit conversion is removed from D365, a warning message appears next time Planning optimization is executed, saying “Could not find unit of measure with id ********”. That does only happen if the unit and unit conversion we're processed before in at least one Planning optimization run. This warning message can cause confusion, as the missing unit of measure is no longer used. Planning optimization should therefore only process those units of measure and unit conversions that still actually exist in the unit of measuretable.

Extend the Price tree, Price attributes, Discounts, Charges, Trade agreements, Base price determination etc. to the Procurement and sourcing Module for Vendors and Purchase prices.

Current setup:

Using Advanced Warehouse Management with Mobile Device

Using Quality Management

Issue: When we create a Sales Order for a part that we purchase to resell, a planned purchase order is generated. The planned purchase order is firmed to a Purchase Order. When the item is received, a quality order is generated. The user completes the quality check but cannot "Validate" the quality order because the system throws the error of unavailable inventory. This issue is due to the original sales order having the same inventory reserved ("Ordered reserved").

Microsoft said their engineering team triaged the bug and determined it was an issue but could not fix it via hotfix. It is a design limitation and will require a change in the underlying design which they cannot take on at this time.

The only way around this is to manually unreserve the inventory on the Sales Order (which quality doesn't have access to do), Validate the Quality Order and then re-reserve the inventory on the Sales Order. This is very time consuming and has to involve multiple users.

Using the Inventory Visibility Service (IVS) API's, we would like to be able to request a view of the stock quantities in a different unit than the default 'Inventory unit'.

In Dynamics, you're able to view stock information in any desired unit (through i.e.: mi=InventOnHandItem), but this functionality is missing in the IVS.

Further context:

We sell items as separate pieces as well as by the box and each item has an item specific conversion 'Pcs' <-> 'Box'.

For our web shop we want to be able to give an indication of the stock ("Plenty of stock", "Limited availability", "Out of Stock", ...) depending on the chosen sales unit. As such, we would like to be able to retrieve the stock through IVS in the "Box" unit when the customers selects x boxes:

• ... > 100 boxes : Plenty of Stock
• 100 >= ... >= 1 boxes : Limited availability
• 0 boxes : Out of stock

At the moment we need to do 2 API calls to get the stock information and then another to get the unit conversions and finally do the calculation ourselves. So having this functionality would eliminate the need of the second API call and the calculations.