Dynamics 365 Supply Chain Management

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.

A common requirement is to be able to create sales prices that is negotiated as Net prices. I.e. a price where no other discounts should be applied on an order line. The way to handle it today (Pricing Management) is to create a Trade agreement price AND a Discount of calculation type "Unit price" and concurrency = "Exclusive". This is to cumbersome to manage and is prone to errors. It also doesn´t cover tiered prices.

An idea is to set a flag on a Trade agreement line, "Allow discounts" = No, and if that lines is fetched on an order, no discounts should be applied. If yes, discounts are applied as per standard behaviour.

The WIP balance on production orders, that have been reported as finished, will end up being the total amount of the variances that will be booked when the production order is ended. Ideally a user would see this amount prior to ending the production orders so that any needed corrections could be done prior to ending. The business case would be a user has a filtered view of all production orders in reported as finished status: and prior to ending them could sort by the WIP value in descending order to see which production orders need research. It is simply not feasible to pull up each production order and select the WIP valuation individually. In a standard cost situation, reporting a finished quantity will book inventory at standard and remove WIP at that same amount. So, any value remaining in WIP prior to ending the production order will end up being booked as variance. Seeing this amount ahead of time can point out errors in reporting, bad standards etc.

When using sales trade agreements (without enabling pricing management features) it is possible to define a price unit !=1, to manage decimals beyond two digits. 

E.g., if a price unit is 1000 and the price is 1234,56, unit prices on the sales order line will be calculated as 1,23456 for a single unit (even if it will only be shown with rounded values and two decimals). 

After enabling Pricing management features, this option to control the decimals no longer works. It is still possible to define the price unit !=1, but this is not recognized in the price calculation nor the unit price applied on the sales order line. 

Making Pricing management (and Unified pricing) compatible with price unit !=1 is needed for low value items. Also, it is a functionality which is highly used in SCM pricing.

As the price engine already calculates with more than 2 decimals (for discounts etc.), it should be an option to also consider more than 2 decimals for sales trade agreements as well.

If this is not updated, it could be a significant regression in pricing functionality and may deter customers from selecting the new pricing management/unified pricing features.

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

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.

Below issue is dicsussed as high prio with Microsoft and it was forwarded after several discussions to the idea portal.

During production report as finished it is possibile to scan a quantiy with more then 15 digits and with some specific item cost resulting in a extensive inventory transaction. This amount of this transaction is to big for the system to calculate. This resulting in a imbalance of the general ledger. The system creates an debit transaction different then the credit transaction. which causes the imbalance.

This imbalance of the general ledger resulting in a corrupt general ledger which can not be fixed by Microsoft. Resulting in the only solution to execute a restore back in time on a go live environment. This to make sure that the system integrity is

Our proposal is that all transactions causing an inventory imbalance should be avoided at all possibile ways. Meaning a blocking error should be triggered in cases an imbalance is occuring.

We are Microsoft Partners working All-Star Marketing group to Implement the following: Dynamics Finance; Dynamics SCM, IOM, and Inventory Visibility. There has been a request for embedding the Inventory Visibility app into the main dashboard in Dyn 365 Fin and SCM. I tried a couple approaches. Add the Power App and Web page. Both ways did not seem to work. I would like to suggest an idea of embedding the IV App into Dyn Fin and SCM.

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

The current behavior is that when "Count non-discountable items towards threshold" is enabled, it will include those items towards threshold qualification which are added to the discount line section as "Include", but have been either marked as "Prevent all discounts" (Under Commerce tab of Released products) or have another Exclusive or Best price discount applied.

The above behavior is according to Issue 449997 that can be found in LCS.

Proposed behavior: this parameter should allow for items that aren't included to count towards the threshold as well. (or a separate parameter) To allow for more scenarios to be applied in the system.