How To Fix VO053 - Shipment &1 is not included because delivery &2 does not fit

SAP Error Message - Details

• Message type: E = Error

• Message class: VO - W&S: Rough workload forecast + picking wave

• Message number: 053

• Message text: Shipment &1 is not included because delivery &2 does not fit

What causes this issue?

The delivery is not selected to be included or has a status that
prevents it from being included:
Picking started
Warehouse Management started
Goods issue complete

System Response

Wave creation does not include the <ZH>entire</> shipment.

How to fix this error?

Check the shipment/delivery and decide what you should do depending on
the situation.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message VO053 - Shipment &1 is not included because delivery &2 does not fit ?

  Certainly! Here's a detailed explanation for the SAP error message:
  
  SAP Error Message:
  VO053 Shipment &1 is not included because delivery &2 does not fit
  
  Meaning / Cause:
  This error occurs during shipment processing in SAP Logistics Execution (LE) when you try to include a delivery (&2) into a shipment (&1), but the system finds that the delivery does not "fit" into the shipment. The term "does not fit" means that the delivery does not meet certain criteria or conditions required for inclusion in the shipment.
  Common reasons why a delivery might not fit into a shipment include:
  
  Incompatible Shipping Point: The delivery's shipping point differs from the shipment's shipping point.
  Different Transportation Planning Dates: The delivery's planned goods issue date or transportation date does not match the shipment's date.
  Different Route or Transportation Zone: The delivery's route or transportation zone is different from the shipment's.
  Incompatible Shipping Conditions: The delivery has shipping conditions that conflict with the shipment.
  Different Ship-To Party or Customer: The delivery is for a different customer or ship-to party than the shipment.
  Different Transportation Group: The delivery's transportation group does not match the shipment's.
  Delivery already assigned to another shipment: The delivery is already included in another shipment document.
  Shipment type or status restrictions: The shipment type or status may restrict adding certain deliveries.
  
  
  Where it occurs:
  
  When manually adding deliveries to a shipment in transaction VT02N (Change Shipment) or VT01N (Create Shipment).
  During automatic shipment building or shipment proposal.
  When using shipment APIs or batch jobs that assign deliveries to shipments.
  
  
  How to Analyze:
  
  Check Shipment and Delivery Data:
  
  Compare the shipment header data and the delivery header data for shipping point, route, transportation group, ship-to party, and dates.
  
  
  Check Shipment and Delivery Status:
  
  Ensure the delivery is not already assigned to another shipment.
  Check if the shipment is in a status that allows adding deliveries.
  
  
  Check Customizing:
  
  Review the shipment determination and shipment building rules in SPRO under Logistics Execution ? Shipping ? Basic Shipping Functions ? Shipment ? Shipment Building.
  
  
  Check User Exits or Enhancements:
  
  Sometimes custom logic in user exits or BADIs can restrict delivery inclusion.
  
  
  
  
  Solution / How to Fix:
  
  Ensure Matching Shipping Point: Make sure the delivery and shipment have the same shipping point.
  Align Dates: Adjust the delivery's planned goods issue date or transportation date to match the shipment.
  Check Route and Transportation Group: Ensure these match between delivery and shipment.
  Check Customer and Ship-To Party: Confirm they are the same.
  Remove Delivery from Other Shipments: If the delivery is assigned elsewhere, remove it first.
  Use Correct Shipment Type: Verify the shipment type allows adding the delivery.
  Adjust Shipment Building Rules: If automatic shipment building is used, adjust the rules to allow the delivery.
  Check for Custom Code: Review and adjust any custom logic that might block the inclusion.
  
  
  Additional Information:
  
  Transaction Codes:  
  
  VT01N – Create Shipment  
  VT02N – Change Shipment  
  VT03N – Display Shipment  
  VL01N / VL02N – Create/Change Delivery  
  
  
  SAP Notes:  
  
  Check SAP Notes related to shipment building and delivery assignment for your SAP version.
  
  
  Debugging:  
  
  If standard checks do not reveal the cause, debugging the shipment inclusion logic (function modules like LE_SHIPMENT_ADD_DELIVERY) can help.
  
  
  Documentation:  
  
  SAP Help Portal: Shipment Building and Delivery Processing  
  SAP Logistics Execution (LE) module documentation.
  
  
  
  
  If you provide the shipment number (&1) and delivery number (&2), you can check the specific data for those documents to identify the mismatch.
  
  Summary:
  
  The error VO053 means the delivery cannot be included in the shipment because key shipment and delivery attributes do not match or violate shipment building rules. Aligning these attributes or adjusting shipment building rules/custom code will resolve the issue.