Troubleshooting Shipment Confirmation Errors in Dynamics 365: Items Not Picked

Table of Contents

Error code: LoadNotPickedAndMovedToFinalShippingLocation

Symptoms¶

When attempting to confirm a shipment within Dynamics 365 Supply Chain Management, users may encounter a specific error message that prevents the process from completing successfully. This error indicates a problem with the physical movement or recording of items intended for shipment. The system displays the following message:

Some of the items that are needed for load %1 have not yet been picked and moved to the final shipping location.

This critical error halts the shipment confirmation process for the specified load (%1), meaning the goods cannot be officially marked as shipped, potentially delaying logistics and billing processes. The error message clearly points to a discrepancy between the system’s expectation for the load’s contents and their actual status and location within the warehouse. Understanding the root cause of this discrepancy is key to resolving the issue and enabling successful shipment confirmation.

Understanding the Warehouse Process Context¶

Before delving into the causes and resolutions, it’s helpful to understand the standard warehouse flow that precedes shipment confirmation in Dynamics 365. Typically, sales or transfer orders are released to the warehouse, generating waves and then work orders. Warehouse workers use mobile devices to perform picking tasks, moving inventory from storage locations to a staging or packing area. After picking, items are often consolidated, packed (if applicable), and then moved to a final shipping location, such as a loading dock or designated bay.

The system tracks the status of the work and the physical location of the inventory throughout these steps. Shipment confirmation is the final step before invoicing and physically dispatching the goods, and it relies on the system confirming that all items required for the load are correctly picked, accounted for, and positioned at the designated final shipping location, ready for departure. Any deviation from this expected state triggers the error message.

Cause¶

The error LoadNotPickedAndMovedToFinalShippingLocation fundamentally occurs because the system’s check during shipment confirmation determines that one or more conditions related to the required items’ picking and final location status have not been met for the load in question. Several specific conditions can lead to this state, often stemming from incomplete warehouse processes or incorrect system configurations. Identifying the exact cause is crucial for applying the correct resolution.

One primary cause is that the warehouse work associated with the load lines has not been fully completed. This means the required items might still be in their original storage locations, in a staging area, or in transit, but they have not yet been recorded as arriving at the designated final shipping location. Incomplete work could be due to various reasons, including missed steps by warehouse staff, technical issues with mobile devices, or work being partially completed but not finalized in the system.

Another common reason relates to quantity discrepancies. Even if work is marked as complete, the system validates that the quantity of items physically picked and moved matches the quantity specified on the load line and the associated work. If the picked quantity recorded in the system does not equal the quantity required by the work or the load line, the shipment confirmation will fail. This mismatch could arise from picking errors, short picks that were not properly handled, or data entry errors during the picking process.

Finally, a less obvious but significant cause can be a misconfiguration within the warehouse setup, specifically regarding location directives and wave template containerization. If a location directive is incorrectly set up to designate a packing location as the final shipping location when automated containerization is in use via a wave template, this can lead to issues. While items might be moved to the packing location as part of the containerization process, this location might not be recognized by the system as the final shipping point required for shipment confirmation, or the process flow is interrupted at this point. This configuration conflict creates a logical block, preventing the load from being confirmed even if items are physically moved as expected by the current setup.

Resolution¶

Addressing the LoadNotPickedAndMovedToFinalShippingLocation error requires investigating the specific state of the load and its associated work and inventory. The resolution involves either correcting the physical or system state to match the expected conditions or, in cases of configuration issues, correcting the setup and reprocessing the affected orders. There are two primary approaches to resolve this issue, depending on the underlying cause identified.

The first approach focuses on verifying and correcting the status of the existing warehouse work and inventory movement. This involves reviewing the load lines, checking the status of the related work IDs, and ensuring that all items have been recorded as picked and moved to the final shipping location with the correct quantities. This is the most common resolution if the issue is due to incomplete physical processing or data recording errors in the warehouse.

The second approach is necessary when the problem stems from a configuration error, particularly the misuse of a packing location as a final shipping destination in conjunction with automated containerization. This requires canceling the incorrectly created work, correcting the location directive configuration, and then rereleasing the load to generate new work instructions that direct items to the correct final shipping location. This method is more complex but essential for resolving the underlying setup problem.

Resolution 1: Review Your Load Lines and Make Sure That All the Related Work Has Been Completed at the Final Shipping Location, and That the Quantities Match¶

This procedure guides you through verifying the status of warehouse work and the quantities associated with a specific load, which is often the solution for incomplete physical processing or recording errors. It involves navigating through the system to check the details of the load and its linked work orders. Ensuring every required item has a corresponding completed work line indicating movement to the final shipping location, and that the quantity matches the demand, is critical.

Begin by accessing the load details. Navigate to Warehouse management > Loads > All loads. Locate and select the specific load for which you are unable to confirm the shipment. This provides a central point to investigate all items and processes linked to that particular outbound collection of goods.

Once the load is selected, examine the Load lines FastTab. Each line on this FastTab represents an item or a set of items included in the load from the original sales or transfer order lines. Pay close attention to the details on each load line, particularly the quantity fields. Note the value displayed in the Work created quantity field for the relevant load lines; this indicates the total quantity for which the system created picking work.

Next, you need to investigate the actual warehouse work associated with these load lines. On the Action Pane, located on the Loads tab within the Related information group, select the Work option. This action will display a list of all warehouse work IDs that were generated for the selected load. Review each work ID linked to the load lines in question. For each work ID, verify that its status is Completed. More importantly, examine the details of the work lines within each work ID (often found by clicking on the Work ID). Ensure that the final “Put” step for the required items directs them to and is completed at the designated final shipping location (e.g., a specific dock door or staging bay configured as the final shipping location type).

Crucially, cross-reference the quantity on the completed work lines with the Work created quantity noted from the load line. The quantity recorded as “Picked” and “Put” on the completed work should match the quantity required by the load line. If the work is completed but the quantities don’t match (e.g., due to a short pick), you may need to investigate why the full quantity wasn’t picked or consider adjusting the load quantity if the shortage is legitimate and cannot be fulfilled. Repeat this verification process for every load line on the affected load. All load lines must have corresponding completed work at the final shipping location with matching quantities before the shipment can be confirmed.

Resolution 2: Cancel the Work IDs That Have Been Created With the Packing Location as the Final Shipping Location, Reconfigure the Location Directive, and Rerelease the Load¶

This resolution path is specifically designed for situations where the error is caused by a system configuration issue, particularly when automated containerization is used with a location directive incorrectly configured to use a packing location as the final put location. This process involves correcting the setup and then reprocessing the order to generate correct work instructions.

The first step in this process is to cancel the existing, incorrect warehouse work. Since the current work IDs likely direct items to the wrong final location (the packing location), they need to be removed so that new, correct work can be generated. Navigate to Warehouse management > Periodic tasks > Clean up > Cancel work. This utility allows you to cancel warehouse work based on specific criteria.

In the Cancel work dialog box that appears, you need to specify the work IDs that were generated for the load in question and are associated with the incorrect put location. You can enter specific work IDs in the Work ID field. It’s important to note that the system allows you to cancel work that has a Work status of Open, In progress, Canceled, Combined, or Closed. While you might primarily be dealing with work that is Open or In progress but stuck, the tool’s flexibility allows for cleaning up various work states if necessary. Select OK after entering the relevant work ID(s). The system will prompt you to confirm the action; select Yes to proceed with canceling the work. Repeat this step for all work IDs associated with the problematic load lines that were generated with the incorrect final put location.

Once the incorrect work has been canceled, the next critical step is to correct the underlying configuration issue. This involves modifying the location directive that incorrectly specifies the packing location as the final put location when automated containerization is in use. Navigate to Warehouse management > Setup > Location directives. Location directives are fundamental rules that guide the system in determining where inventory should be placed or picked from. You need to identify the specific location directive that is being used for the outbound process (typically Sales orders) in conjunction with your wave template and containerization setup.

In the list of location directives, filter or search for the directive that is relevant to sales orders and likely being used by the wave template for this process. Select the appropriate location directive. On the Location Directive Actions FastTab, select Edit query. This opens the query editor for the directive actions, allowing you to define the criteria for the target put location. Within the query editor dialog, go to the Range tab. Look for a row where the Field is set to Location profile. This range is often used to filter the possible put locations based on their profile. Verify the Criteria field for this row. If it is set to a location profile that has a Location type of Packing, and this is occurring when automated containerization is directing to the final put location, this is the source of the misconfiguration. You need to adjust the Criteria field to ensure that it directs the final put step to a location profile that represents a true shipping or staging location, not a packing location, in scenarios where containerization is used to determine the final put. Save the changes to the location directive query and the directive itself.

After correcting the location directive configuration, you must now generate new, correct warehouse work for the load. This is achieved by rereleasing the load. Go back to the load details (Warehouse management > Loads > All loads), select the load you were working with, and use the option to release it to the warehouse again. This action will trigger the wave process and the creation of new work IDs based on the corrected location directive setup. These new work IDs should now properly direct the warehouse workers to move the items from their pick locations (or potentially from the packing location, depending on your exact process flow) to the correct final shipping location. Once this new work is generated and successfully completed by the warehouse staff, moving the items to the proper final shipping location, you should then be able to confirm the shipment without encountering the LoadNotPickedAndMovedToFinalShippingLocation error.

Preventing Future Errors¶

Preventing the LoadNotPickedAndMovedToFinalShippingLocation error relies on a combination of accurate system configuration, well-defined warehouse processes, and proper execution by warehouse staff. Regularly reviewing and validating your location directive configurations, especially those used in conjunction with wave templates and advanced features like containerization, is paramount. Ensure that the intended workflow (picking -> staging -> packing -> shipping or picking -> packing -> shipping) is accurately reflected in your system setup, and that final shipping locations are correctly defined and used in directives for the final put steps.

Provide comprehensive training to warehouse personnel on using the mobile device and following the prescribed picking and put-away procedures. Emphasize the importance of accurately recording quantities and completing all steps of the warehouse work. Implement procedures for handling exceptions like short picks or damaged goods, ensuring these are recorded correctly in the system to prevent quantity mismatches. Utilizing warehouse performance metrics can help identify potential bottlenecks or areas where errors frequently occur, allowing for proactive intervention and training adjustments.

Consider implementing a staging location if your current process involves picking directly to packing and then expecting confirmation from there. A staging location often serves as an intermediate point before the final shipping location, providing a buffer and a clearer distinction in the system’s tracking between packed goods and goods ready for shipment. Consistent adherence to defined processes and periodic system audits of warehouse configurations are key strategies to minimize the occurrence of this and similar warehouse execution errors.

Conclusion¶

The LoadNotPickedAndMovedToFinalShippingLocation error in Dynamics 365 is a common hurdle during shipment confirmation, signaling that required items haven’t been properly picked and moved to their final outbound location according to system records. Whether the cause is incomplete physical processing, quantity discrepancies, or a critical configuration flaw involving location directives and packing locations, understanding the underlying issue is the first step to resolution. By diligently reviewing load details, verifying work completion and quantities, or by correcting misconfigured location directives and reprocessing work, users can overcome this error. Implementing robust training and regular configuration audits serves as the best defense against its recurrence, ensuring smoother, more reliable warehouse operations and timely shipment confirmations.

Have you encountered this error in your Dynamics 365 implementation? What specific steps or checks did you find most effective in diagnosing and resolving the issue? Share your experiences and tips in the comments below!