Deferred processing of manual inventory movement
This article describes how to use deferred processing of manual inventory movement in Microsoft Dynamics 365 Supply Chain Management.
Deferred processing lets warehouse workers continue to do other work while a put operation is processed in the background. Deferred processing is useful when the server can have occasional or unplanned increases in processing time, and the increased processing time might affect worker productivity. The Inventory movement work type has now been added to the set of work types that this feature supports.
Background processing is achieved by using the Process warehouse app events feature.
To make this feature available, turn on the following features in feature management. You must turn them on in this order:
- Organization-wide work blocking
(As of Supply Chain Management version 10.0.21, this feature is mandatory and can't be turned off.) - Process warehouse app events
(As of Supply Chain Management version 10.0.25, this feature is turned on by default. As of Supply Chain Management version 10.0.29, this feature is mandatory and can't be turned off.) - Deferred put operations
(As of Supply Chain Management version 10.0.29, this feature is mandatory and can't be turned off.) - Deferred processing of manual inventory movement operation
(As of Supply Chain Management version 10.0.25, this feature is mandatory and can't be turned off.)
To use deferred processing, you must set up and use a work processing policy. For deferred put processing, the Deferred processing of warehouse work feature supports the following work types: Sales order, Transfer order issue, and Replenishment. The Deferred processing of manual inventory movement operation features adds a new work type: Inventory movement.
To set up a work processing policy, follow these steps.
Go to Warehouse management > Setup > Work > Work processing policies.
Either select an existing policy in the list, or create a new policy by selecting New on the Action Pane. The header of every policy has the following fields:
- Work processing policy name – The name of the work processing policy.
- Description – A description of the work processing policy.
On the Processing rules FastTab, set up the collection of rules that the policy will apply. Use the buttons on the toolbar to add or remove rules as you require. For each rule, set the following fields:
- Work order type – Select the work type that the policy applies to.
- Operation – Select the operation that the policy is used to process. If you selected Inventory movement in the Work order type field, you don't have to set this field, because both pick operations and put operations are processed as a single event.
- Work processing method – Select the method that is used to process the work line. If you select Immediate, the behavior resembles the behavior when no work processing policies are used to process the line. If you select Deferred, the system will apply deferred processing that uses the batch framework.
- Deferred processing threshold – If you set this field to 0 (zero), there is no threshold. In this case, the Deferred processing method is used if possible. If the specific threshold calculation is below the threshold, the Immediate method is used. Otherwise, the Deferred method is used if possible. 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, you ensure that 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 field is set to Deferred.
- Deferred processing batch group – Specify the batch group that is used for processing. If you selected Inventory movement in the Work order type field, you don't have to set this field, because the batch group is selected in the Process warehouse app events dialog box.
For details about how to assign a work creation policy, see Deferred processing of warehouse work.
To use the Deferred processing of manual inventory movement operation process, set up a scheduled batch job.
- Go to Warehouse management > Periodic tasks > Process warehouse app events.
- In the Process warehouse app events dialog box, on the Run in background FastTab, set the Batch processing option to Yes.
- Select Recurrence, and set up a run schedule that meets the requirements of your business.
- Select OK in each dialog box.
You can view the event queue and event messages that the warehouse app generates by going to Warehouse management > Enquiries and reports > Mobile device logs > Warehouse app events.
The Inventory movement event messages will have a status of Queued when they are first created. This status indicates that the Process warehouse app events batch job will pick up the event messages and process them. When the status is updated to Completed, all the related events are deleted from the queue.
All the Inventory movement events are accumulated under one collection per event type and warehouse.
The batch job will process the warehouse app events according to the recurrence that is set up in the Process warehouse app events dialog box. Therefore, until a message is processed, you can find the warehouse ID by looking in the Identifier field.
The details of the message contain the details of the movement (for example, the "from" and "to" locations).
Learn more in Warehouse app event processing.
For details about how to configure the mobile device menu to skip the deferred processing policy, see Deferred processing of warehouse work.
For details about the impact on closed work dates, see Deferred processing of warehouse work.