Dynamics 365 Supply Chain Management

When the accounting currency, reporting currency and PO line currency is different, there are two voucher transaction for posting type of: purchase expenditure for product when post purchase order invoice and the value is not 0. Customer needs to manually adjust the general ledger.

This issue has been logged in Issue 838716 and currently is a design limitation. We will continue to track this issue and monitor if other customers are impacted. Please help Vote if you have the same requirement, we will improve our products and services.

We would like for the fields "created by" to document the username or name of the person who did the posting. We've noticed that it's almost always empty in the inventory transactions.

It will very much help if we get the needed data filled into this field for further audit, tracking, verifiability, evaluation and visibility.

The current Inventory statuses for the Warehouse Management System is restrictive and presents several problems for customers. These statuses only provide a choice of two which is either fully blocked or unblocked. These statuses should be like Batch statuses providing the ability to define actions based upon user defined actions such as what actions should be blocked and which actions should not be blocked. Also, like batch statuses a user should be able to define when nettable and when not.

Business Need:

A customer of our company utilises product configurations to differentiate characteristics of our products, with each configuration being sold in different regions. Each region has its own regulatory requirements, which necessitate different shelf life periods for the same product based on country legislation. Currently, Microsoft Dynamics lacks the capability to manage shelf life periods at the released product variant level, which poses a significant challenge for compliance with varying regional regulations.

Proposed Solution:

We propose the implementation of a feature that allows for the management of shelf life periods within the released product variant master data. This enhancement would enable businesses to efficiently comply with diverse regional regulations without resorting to costly customisations.

Business Impact:

The absence of this feature represents a substantial gap in our operations and could potentially lead to brand damage if end customers perceive that Microsoft Dynamics lacks essential features for regulatory compliance. Implementing this feature would not only streamline operations but also enhance the appeal of Microsoft Dynamics as a comprehensive ERP solution for businesses with complex regulatory needs.

Conclusion:

We believe that prioritising this feature in future updates will significantly benefit businesses and strengthen Microsoft Dynamics' position in the market. We appreciate your consideration of this request and look forward to seeing this enhancement in future releases.

Now in 10.0.44, we have the possibilty to generate a quality order for a transfer order. However we can not select the warehouse for which the quality order should be executed. So for example, if you set up a quality order with an invent type "Receive transfer order", You will have quality order in every warehouse of your site.

Let's imagine a company with several warehouses ( production, distribution, storage).Generally, we want a quality order only for a limited case.

I opened a ticket to MS. But they provide the usual answer : "By design only a site level is supported".

The Inventory management module supports workflow on several different types of Inventory journal.

Inventory journal workflow adds an approval step; journals cannot be posted until they have been Approved. After a journal has been approved, the journal can be posted.

Wouldn't it be good if approved Inventory journals were posted automatically?!

Perhaps a new element could be added to the Inventory workflow designer which can trigger the inventory journal posting class. This way, users could configure each inventory journal workflow to automatically post, or not, as required.

When creating new rows in Sales Orders and Sales Quotations with 30+ lines, the system exhibits unexpected behavior:

1. If a row is added in the middle of the existing set of rows, the newly created empty row "jumps". As a result, the user must wait a few seconds for the empty row to return to its intended position before filling it in.
2. If a row is added at the end of the existing set, a second "ghost" empty row briefly appears for a few seconds before disappearing, after which the user can enter data into the new row.

Since the target audience for Dynamics 365 Finance/Supply Chain Management consists of large or very large companies, where Sales Orders and Sales Quotations with fewer than 30 rows are more the exception than the rule, the current design limitations significantly slow down users' work with Sales Orders and Sales Quotations and leading to additional data entry errors. It also forces users to manually split large orders into smaller ones to reduce the frequency of these "jumping" issues.

According to most users, a system like Dynamics 365 Finance/Supply Chain Management should be capable of handling large Sales Orders and Sales Quotations (300+ rows) without "jumps".

 The piece picking confirmation does not check the batch number during GS1 scan. The current process asks for first scanning the batch number then the item number (if you have only one batch at the location, the batch is not requested. D365 considers that you must pick the batch at the location, if your stock is not correct, you may have a batch number error). During the scan of the item number, the batch number (application identifier 10) is ignored. The current process enable to scan a GS1 code with a batch number not present at the location. This process can lead to send physically a batch number and to have another batch picked in D365 (tracking, delivery note and invoice are wrong).

My suggestion is to first ask the item number. We can have two different situations :

1. The user is not using a GS1 bar code (or the bar code does not contain the batch number) : In this case, we need to ask for the batch number. This batch number must be picked in D365.
2. The user is using a GS1 bar code that contains a batch number : In this case we got all the information. The batch number scan must be picked in D365.

This suggestion should also work if piece picking confirmation is disabled.

The current process is very limited and does not enable medical/food industries (and more) to work with the warehouse management module without any risk. The current process can have a big impact on business. 

Trade allowance management helps companies manage sales promotion programs that offer "pay-for-performance" monetary rewards to customers that achieve volume and behavioral goals. The feature’s capabilities are designed for companies that focus on comprehensive promote-to-profit processes, from promotion fund budgeting and allocation, to allowance contract setup, to claims creation and processing, to payment processing, to promotion effectiveness analysis.

Unified pricing management currently does not support / work with Trade Allowance management. In other words, Trade Allowance Management behind the scenes still uses legacy trade agreements for Off-invoice discounts and legacy rebates for Billback discounts. Trade allowance management could benefit from the price attribute capability of Unified pricing and the enhanced capability of the new Rebate Management module. Unfied pricing can benefite from the fund analysis and promotion effectiveness analysis that Trade Allowance Management supports.

It is extremely difficult to explain to customers that these concepts do not play well together and are not "unified".

In regard to the new features which is addressed to be a very useful feature that was added to the Product information parameters

(Display product info in user's language & User specific product name and description)

The issue here is that the users should be having an Admin privilege or manager privilege to be able to use this feature, moreover this will be more useful to be used by all product information and its relatives over the User interface.

Hence, it will be appreciated this is considered to be added over the User options > Preferences page so all users would be able to adjust it based on the preferred language.