Editor: Denis Conway

Introduction

In the relentless pursuit of streamlining warehouse operations and empowering organizations to achieve more, perfecting the receiving process is a cornerstone. This blog post delves into the transformative role of Dynamics 365 SCM Warehouse Management’s feature “Deferred Processing”, a strategic framework designed to increase operational efficiency by effectively deferring work creation, allowing rapid registration of incoming inventory without waiting for each put-away work to be generated.  

The Supermarket Analogy 

Imagine you are at the checkout in your favourite supermarket. Each customer who visits the store needs to pay for their groceries. Today, most of us usually pay using our debit or credit card, which transfers money from our account to the supermarket’s account. But what if you had to wait for your bank transfer to go through and the supermarket to receive their money before they could move on to the next customer and you could exit the store? That would be tedious, right? 

Fortunately, in the world of dynamics warehousing, the process is not as exhaustive. We don’t wait long for work to be created in the receiving or inventory movement process, but we still need to wait a couple of seconds for it.  
The waiting time is a consequence of the various database calls needed for a process in the warehouse system to take place, such as inventory on-hand-updates when receiving.  
That’s where the deferred processing feature comes into play. Deferred processing creates work in the background, allowing the warehouse worker managing the process to continue without interruptions. It assures the user that “work will be created, but it will be done in the background, so that you don’t have to wait” and can continue receiving other items. 

Referring to the earlier paragraph with the supermarket example, the deferred processing allows the cashier and the customer to consider the transfer of money for groceries as complete and processed, even though the real transaction has not taken place yet. In our warehouse system, the process works in an equivalent way. We are told work has been completed and we are allowed to continue in our inventory movement or receiving process, but in fact the work creation has just been deferred to be processed in the background.  

Warehouse Scenarios: Regular vs. Deferred Receiving 

In a warehouse scenario, the main difference between using deferred processing for deferred receiving and regular receiving can best be explained using a fictional scenario. Let’s imagine a load entering the warehouse holding multiple purchase orders. 

Scenario 1: Regular Receiving 

In this scenario, the warehouse worker(s) responsible for the receiving process scans the license plate or the items for each order. The worker(s) might need to wait a brief time for the related work to be created based on complexity of put-away configuration logic (in this case, work creation will be moving items in the purchase order from receiving area to its “Put” location in the warehouse) before continuing with the next item. This process is usually fast for the majority of the put-away cases, but in some cases, due to a more complex set of put-away rules, waiting time could be experienced. Even though customers only wait a brief time for each, the waiting time adds up, leading to more idle time for the worker. This situation can be avoided by using deferred processing described in scenario 2.  

Scenario 2: Using Deferred Processing for Receiving 

In this scenario, we use the deferred receiving feature that is used when put-away rules inside WMS configuration are complex and might result in slight waiting time on WMA powered devices during put-away work creation. The warehouse worker responsible for managing the inbound receiving scans license plate/items for each order, and as we are using deferred processing, the put-away work that is created from that receiving inventory is processed in the background, releasing workers to continue to scan without interruptions. The work is processed in the background, but in the eyes of the warehouse worker, the work can be considered done and completed. This allows the warehouse worker to spend less time on completing the same amount of work. 

Configuration of deferred warehouse work processing 

In the picture below, users can get a hint of what the configuration process looks like. On this page, users select the work order type that the policy is applied to, which type of operation that is processed by using the policy, and the method that is used to process the work line. If the method is set to Immediate, the behavior resembles the behavior when no work processing policies are used to process the line. If the method is set to Deferred, deferred processing that uses the batch framework is used. 

A value of 0 (zero) indicates that there is no threshold. In this case, deferred processing is used if it can be used. If the specific threshold calculation is below the threshold, the Immediate method is used. Otherwise, the Deferred method is used if it can be used. For sales and transfer-related work, the threshold is calculated as the number of associated source load lines that are being processed for the work. For replenishment work, the threshold is calculated as the number of work lines that are being replenished by the work. By setting a threshold of, for example, 5 for sales, smaller works that have fewer than five initial source load lines won’t use deferred processing, but larger works will use it. The threshold has an effect only if the work processing method is set to Deferred. 

Implementation and Supported Processes

This feature is available for these ways of receiving into your warehouse:

• Purchase order item receiving.
• Purchase order line receiving.
• Transfer order item receiving.
• Transfer order line receiving.
• Load item receiving.
• License plate receiving.

For deferred put-away processing, the following work order types are supported:

• Sales orders.
• Transfer order issues.
• Replenishment orders.

Application of Deferred processing:

In cases where warehouse workers are experiencing slight waiting time on each received item, due to system figuring out where that item should be placed, and processing is slowing down the inventory registration for the worker, deferred processing is an answer.

Conclusion

Deferred processing enables high productivity on inbound docks even in situations where put-away logic is complex, and processing consumes unnecessary time. Deferred receiving empowers workers to effectively handle incoming inventory regardless of length of work creation. It’s a powerful tool for supporting productivity and preventing unnecessary delays.

By deferring work creation and processing it in the background, we allow warehouse workers to focus on their tasks without interruptions.
Ultimately, Deferred processing is not just a feature, but a strategic framework that empowers organizations to achieve more, making it an excellent tool in the modern warehouse operations landscape. It enables customers to keep productivity high in any circumstances and with any put-away configurations.

If it is needed for you, embrace Deferred processing, and let your warehouse operations reach new heights of success.

Get started with Dynamics 365

Drive more efficiency, reduce costs, and create a hyperconnected business that links people, data, and processes across your organization—enabling every team to quickly adapt and innovate.

Business Applications | Microsoft Dynamics 365

Join our Yammer Group:

Welcome to join Yammer group at: Dynamics 365 and Power Platform Preview Programs : Dynamics AX WHS TMS  

Learn more:

Mixed license plate receiving – Supply Chain Management | Dynamics 365 | Microsoft Learn

Deferred processing of warehouse work – Supply Chain Management | Dynamics 365 | Microsoft Learn

Deferred processing of manual inventory movement – Supply Chain Management | Dynamics 365 | Microsoft Learn

Deferred processing of warehouse work – Supply Chain Management | Dynamics 365 | Microsoft Learn

Deferred processing of manual inventory movement – Supply Chain Management | Dynamics 365 | Microsoft Learn

The post Unleashing the Power of Deferred processing receiving in Dynamics 365 SCM (supply chain management) Warehouse Management  appeared first on Microsoft Dynamics 365 Blog.

Field service management is a complex process that requires seamless coordination among technicians, customers, equipment, and suppliers. To address these complexities, we have introduced two new capabilities in Dynamics 365 Field Service to make this easier.

The first capability, Complete Work Order by Status, allows field service organizations to use a booking status to indicate if further work is required to complete a work order. This feature gives technicians the flexibility to indicate when additional work is needed on a work order, streamlining the process for field service teams to gain better insight into the tasks required to fulfill a work order.

The second capability, Complete Booking While Preserving End-Time, ensures that when a booking is marked as completed by someone other than the assigned resource, the end-time value will no longer automatically update to the current timestamp. Instead, it will retain the end-time value of the booking. This helps ensure accuracy and consistency in the record-keeping process.

These features aim to optimize service delivery, reduce costs, and enhance customer satisfaction. Now, let’s explore each feature in greater detail.

Complete Work Order by Status

Why is it needed?

In the Field Service industry, it’s not uncommon that what begins as a routine service request can morph into a complex task, requiring multiple follow-up visits to finalize a work order.

Consider a scenario where a commercial building is experiencing recurrent refrigerant leaks from its rooftop HVAC unit. Typically, these leaks are addressed by replacing a worn-out seal. However, upon closer examination, it becomes evident that the evaporator coil is corroded and requires replacement. This insight only emerges once the field service technician arrives on site. Typically, when this occurs, technicians find themselves without the required parts for immediate repairs. This results in the need to contact suppliers, procure necessary parts, and schedule follow-up visits—unforeseen tasks not factored into the initial work order creation. In this scenario, the technician would close the booking while still needing to acknowledge the need for a follow-up visit to complete the work order.

Previously, field service teams encountered challenges in accurately reflecting this information without implementing custom logic. However, with the introduction of the “Complete Work Order by Status” feature, these unexpected visits can now be effortlessly marked as requiring follow-up by utilizing a booking status to indicate the need for further work to fulfill the work order.

How it works?

To configure this feature, administrators should access the Resources section within Dynamics 365 Field Service. Navigate to Booking settings and choose Booking Status. Here, administrators can either select an existing completed status or create a new one. Next, administrators should navigate to the Field Service tab within the selected booking status. Within the “Field Service Status” dropdown, update the “Status Completes Work Order” toggle to “off”.

Upon adjusting this setting, technicians can utilize the newly configured booking status to indicate both the completion of a booking and the need for follow-up work on the associated work order. This adjustment optimizes the workflow for field service teams and enhances their understanding of the tasks necessary for work order fulfillment.

Complete Booking while preserving ‘End Time’

Why is it needed?

Field Service technicians are the backbone, tirelessly striving to meet deadlines, resolve customer issues, and ensure tasks are completed promptly. However, amidst their hectic schedules, oversights may arise, such as neglecting to mark a job as “completed” once finished. In such cases, dispatchers or field service managers step in to manually update the booking status on behalf of the technician.

For example, a dispatcher schedules a repair job from 1:00 PM to 2:00 PM. Despite an unforeseen delay, the technician completes the task at 2:00 PM but forgets to update the booking status to “completed.”

The dispatcher later notices the oversight and manually marks the booking as completed at 9:00 AM the following day.

Previously, this would inaccurately reflect a job duration of 19 hours, with the end time value set to 9:00 AM. With the implementation of the new “Complete bookings while preserving end-time” logic, when a user other than the assigned resource updates the booking to complete on behalf of the technician, the original end-time value of 2:00 PM is maintained.

How it works?

Exciting update: No setup is needed! When a booking is marked as completed by someone other than the assigned resource, the end-time value will no longer automatically update to the current timestamp. Instead, it will retain the end-time value prior to completion. This ensures accuracy and consistency in the record-keeping process.

We’re eagerly anticipating your experience with these new updates! Feel free to share your thoughts with us.

Share Your Feedback for Continuous Improvement

These new capabilities for Dynamics 365 Field Service are designed to simplify tasks for technicians and empower field service teams with enhanced tracking abilities for work orders and bookings. These advancements offer precision and efficiency, driving improvements in service quality, cost reduction, and customer satisfaction.

Explore more on Dynamics 365 Field Service documentation and share your feedback within the Field Service product or via our ideas portal. Your input drives continuous improvement for enhanced operational performance.

The post Optimize Service Delivery with improved booking capabilities in Dynamics 365 Field Service appeared first on Microsoft Dynamics 365 Blog.

Editor Denis Conway

Introduction

In the relentless pursuit of customer-centric excellence, optimizing our return process emerges as a pivotal strategy for both customer satisfaction and operational prowess. This blog exploration delves into Dynamics 365 SCM Warehouse Management’s transformative role in enhancing customer return receiving process, showcasing a strategic framework that promises elevated customer experience and operational efficiencies.

Elevating Standard Processes

In the traditional realm of return management, the issuance of a Return Material Authorization (RMA) order has been the cornerstone. This process, while effective, faces challenges in scenarios where the reason for return is not immediately apparent. Our executive journey begins with understanding the standard RMA process and its limitations.

This current sales return approach with RMA order, while effective in many respects, introduces potential delays and customer frustration due to its structured and sometimes rigid procedures. The complexity of documentation, especially in unplanned return scenarios, coupled with communication gaps and limited automation, poses challenges. Additionally, as businesses scale, the classic RMA order process may face scalability concerns, raising questions about its ability to efficiently handle increased volumes of return requests. Addressing these limitations is crucial for executives aiming to optimize return management processes, enhance customer satisfaction, and ensure operational resilience. The previous return system does not support the creation of return labels that is a must have for many industries, such as e-commerce. 

Enhanced processes in customer return receiving

In the innovative landscape of our enhanced customer return receiving process within Dynamics 365 SCM, the traditional requirement for a pre-existing Return Material Authorization (RMA) order has been reimagined. In the new way of enhanced customer return process, we can pre-generate return data, create return labels that can be shipped in a shipment and used for seamless return of items. If items need to be returned, customers now have the flexibility to initiate returns seamlessly through two distinct scenarios: the ‘Blind Return’ and ‘Return Details,’ eliminating the upfront necessity of an RMA order.

Blind Return Scenario: In the ‘Blind Return’ scenario, customers can initiate return requests without disclosing specific details initially. We will still need to have a customer number to assign (it can be a dummy customer) to the return order and the item numbers, but we do not need to have an issued return order number. This approach caters to situations where the reason for return may not be immediately apparent or where customers prefer a swift and straightforward process. By bypassing the need for upfront details, this streamlined approach accelerates the return initiation phase, enhancing the overall customer experience.

Return Details Scenario: Alternatively, the ‘Return Details’ scenario allows customers to provide comprehensive information about the return from the outset. This more structured approach is ideal for situations where a detailed explanation of the reason for return, return until date or additional information is available. It facilitates smoother and more informed return processing, using pre-generated RMA-number included on the return labels, enabling the receiving team to address customer needs with precision and efficiency.

Crucially, what sets this enhanced process apart is the automation that follows these customer-initiated returns. In the subsequent stages, the system intelligently generates the necessary RMA order automatically in the background. The post-return generation of the RMA order streamlines the process, combining customer convenience with the structured documentation needed for efficient internal processing. As we evolve in our commitment to customer-centric operations, this innovative approach sets the stage for a more agile, responsive, and efficient return management process. In the image below, we can see an illustration of the return receiving process:  

Conclusion

In the executive suite, strategic decisions are paramount. The enhanced customer return receiving process in Dynamics 365 SCM Warehouse Management is not merely a feature; it’s a strategic tool that aligns our organization with the demands of modern business. As we navigate the complexities of customer interactions and operational excellence, let us leverage this innovation to propel our brand into the forefront of customer-centric leadership.

More details

Learning article can be found at:
Sales returns – Supply Chain Management | Dynamics 365 | Microsoft Learn,
Receive unannounced sales returns – Supply Chain Management | Dynamics 365 | Microsoft Learn.

Welcome to join Yammer group at: Dynamics 365 and Power Platform Preview Programs : Dynamics AX WHS TMS

The post Elevating Customer Returns receiving experience with Dynamics 365 SCM Warehouse Management  appeared first on Microsoft Dynamics 365 Blog.