Dynamics 365 Supply Chain Management

Problem:

In warehouse operations, discrepancies often arise when physical product movements do not align with systematic records. A specific challenge is when workers complete work orders on mobile devices without physically visiting the required locations to perform the steps.

Solution:

Introduce a configuration control requiring warehouse workers to scan thebarcode during work order confirmations.

Implementing a process requiring operators to confirm their physical presence, such as by scanning location barcodes, can help ensure accuracy. This measure reduces errors, enforces operational discipline, and enhances the reliability of recorded data against actual activities in the warehouse.

Typing would serve as a fallback option when barcodes are missing or damaged, with control over this behavior managed through configurable settings. This ensures operational flexibility while maintaining a standard validation process.

Current Limitation:

In D365FO, when creating a Sales Return Order, there is no functionality to print a receipts list like there is for standard Sales Orders. This gap presents challenges for warehouse workers who need to know exactly what goods are returning and when, especially if they do not have access to the D365FO client. Without this list, there is limited visibility into the expected returns, which can lead to inefficiencies in the return process.

Proposed Enhancement:

Add a standard SSRS report for Sales Return Orders that generates a receipts list similar to the one available for standard Sales Orders. This report should be configurable in Print Management to allow for printing when a return order is created. This would provide warehouse workers and other personnel with a clear, standardized document to identify and process incoming goods.

Why This Matters:

• Improved Visibility: By having a receipts list for Sales Return Orders, warehouse workers can anticipate incoming items and ensure they are prepared for the returns, improving operational efficiency.
• Enhanced Process Efficiency: With the report being included in Print Management, the warehouse team can operate more independently, reducing the need for access to the D365FO client and enabling faster return processing.
• Consistency in Documentation: A standardized receipts list for both Sales Orders and Sales Return Orders will ensure consistency in how incoming and outgoing goods are managed, reducing the risk of confusion or errors.

Call to Action:

Implementing this feature would provide much-needed visibility into Sales Return Orders, enhancing operational workflows, reducing delays, and supporting accurate goods identification. This functionality would be a valuable addition for any organization managing returns, improving warehouse efficiency and overall return order management.

Large trading companies with several legal entities often trade with one and the same customer or supplier across several legal entities. These business relationships have various types of rebate, royalty or deduction agreements on both the customer and supplier side, which are based on the total amount of all sales and/or purchases across all customer accounts and/or vendor accounts across all legal entities. These deals can be settled both cumulatively against a central invoice account and against the respective invoice account of the legal entity. Therefore, a global rebate management is required to enable deals to be settled across all legal entities.

An Idea could be the implementation of a third rebate type "across legal entities" that allows the selection of multiple legal entities per line in the rebate management line setup.

It isn't feasible to link a purchase order to a sales order in any setup except for the direct delivery setup. The linkage appears on the "Item Reference" and "Reference Number" tabs found in the sales order lines and this linkage is done automatically by the system once a sales order is created. This forces the clients to always choose the direct delivery set up in order to have the leverage to link a purchase order to a sales order. Moreover, if the customer then tries to remove an already linked purchase order and choose a different one, the system will not allow this action. In case of high sales demands, this process can be very labor intensive as the customer is then tied to cancel the sales orders all together and re-link them to new purchase orders.

We propose a feature that aims to restricts the registration or receipt of items with close expiry dates. This improvement aims to prevent losses due to expired products. Our suggestion involves adding a feature that restricts the registration or receipt of items with imminent expiry dates.

Upon receiving or registering items, the system validates their expiry dates. If an item’s expiry date is within a specified threshold (e.g., 30 days), an alert triggers to the vendor for example to restrict registering it.

By doing so, we can prevent losses resulting from expired products. Implementing this feature will proactively manage inventory, reduce waste, and maintain product quality for users.

It would be nice that in the mobile work order app it becomes possible that a worker can mark work order jobs as ‘checked’. When marked as ‘checked’ the jobs should grey-out so that workers easily can see which jobs they have done on a work order. This is especially helpful when having a lot of jobs on one single work order. 

Currently, Dynamics 365 Warehouse Management does not offer a feature to reassign clusters to another user. This limitation causes significant disruptions when an employee, assigned to a cluster, leaves for the day or forgets to complete the task. The current workaround involves resetting the employee's work user password in D365, then using a handheld scanner to pass the cluster so another employee can start the Cluster ID. This process is cumbersome and inefficient.

I propose a new functionality within Dynamics 365 to streamline this process. The system should allow administrators or managers to:

1. Remove an Employee from an Assigned Cluster: This feature would enable the removal of an employee from a cluster, making it available for reassignment. This ensures the fulfillment process continues smoothly without depending on a single user’s availability.
2. Reassign a Cluster to Another User: This functionality would allow for the direct reassignment of a cluster to another user, enabling the new user to pick up and complete the tasks without any interruptions.

Benefits:

• Improved Operational Efficiency: By allowing clusters to be reassigned seamlessly, the warehouse team can maintain continuous operations and avoid bottlenecks.
• Enhanced Customer Service: Minimizing delays in the fulfillment process leads to better customer satisfaction as orders are processed and delivered on time.
• Greater Flexibility: This feature provides teams with the flexibility to adapt to unexpected changes, such as an employee’s sudden unavailability.

Implementing these enhancements will significantly improve the overall efficiency and responsiveness of warehouse management operations in Dynamics 365.

Thank you for considering this enhancement to further empower our warehouse management capabilities.

Provided a function, that it is able to change the status of issue of sales order line, and inventory, when the issue is connected to " not chargeable" Item requirements This is the standard scenario of Fixed Price project, where it is possible to invoice only on-account transaction and not sales order (item requirement).

The goal is to perform also in a right way the inventory evaluation.

When the vendor submits an application via the vendor portal, and it is rejected for a specific reason, the customer's data (e.g. e-mail address) remains stored in the system. once the vendor has made improvements (e.g. requested certification), it cannot re-register in the system, as this data is still stored in the prospective vendor request.

I propose to allow the vendor to modify his application by reopening the form, if the change requested option is selected in the vendor request workflow, and to allow him to post his application again once the modifications have been made.

Currently, in order to filter for non-open Non conformances, it is necessary to set the "Closed" filter to "Yes" and the status to anything other than "Refused." This filter cannot be set by users in the form, and when generating BI statistics, explaining this becomes quite convoluted.

It wouldn't be challenging to ensure that when a nonconformity is rejected, the "Closed" checkbox is also marked.

In conclusion, it would be advantageous to implement this minor change to facilitate the differentiation between open and closed Non conformances.