How To Fix BORGR602 - &1 inbound deliveries created; not possible to transfer all to shpt &2

SAP Error Message - Details

• Message type: E = Error

• Message class: BORGR - Messages Multi-Level Goods Receipt

• Message number: 602

• Message text: &1 inbound deliveries created; not possible to transfer all to shpt &2

What causes this issue?

Inbound deliveries were created. Some of the inbound deliveries are not
relevant for transport and thus were not transferred to the shipment.

System Response

The inbound deliveries that are not relevant for shipment were not
assigned to the shipment.

How to fix this error?

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message BORGR602 - &1 inbound deliveries created; not possible to transfer all to shpt &2 ?

  The SAP error message BORGR602 indicates that there are inbound deliveries that have been created, but not all of them can be transferred to the shipment specified. This error typically arises in the context of logistics and transportation management within SAP, particularly when dealing with inbound deliveries and their association with shipments.
  Cause:
  The error can occur due to several reasons, including:
  
  
  Mismatch in Delivery and Shipment Data: The inbound deliveries may not match the criteria required for the shipment, such as delivery dates, quantities, or other relevant parameters.
  
  
  Status Issues: Some of the inbound deliveries may be in a status that does not allow them to be transferred to the shipment (e.g., they may be blocked or not fully processed).
  
  
  Configuration Issues: There may be configuration settings in the system that prevent certain deliveries from being included in a shipment.
  
  
  Quantity Discrepancies: The total quantity of goods in the inbound deliveries may exceed the capacity or the expected quantity for the shipment.
  
  
  Missing Master Data: Required master data (like material master, vendor master, etc.) may be incomplete or incorrect, leading to issues in processing.
  
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Delivery and Shipment Details: Review the details of the inbound deliveries and the shipment to ensure they match. Look for discrepancies in dates, quantities, or other relevant fields.
  
  
  Review Status of Deliveries: Check the status of each inbound delivery. Ensure that they are all in a status that allows them to be transferred to the shipment.
  
  
  Adjust Quantities: If there are quantity discrepancies, adjust the quantities in the inbound deliveries or the shipment as necessary.
  
  
  Check Configuration Settings: Review the configuration settings related to inbound deliveries and shipments in your SAP system. Ensure that they are set up correctly to allow for the transfer of deliveries.
  
  
  Consult Logs and Messages: Look at the application logs or messages for more detailed information about why the transfer is failing. This can provide insights into specific issues that need to be addressed.
  
  
  Contact Support: If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting SAP documentation for further assistance.
  
  
  Related Information:
  
  Transaction Codes: You may want to use transaction codes like VL31N (Create Inbound Delivery) or VL32N (Change Inbound Delivery) to review and manage inbound deliveries.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Documentation: Refer to SAP Help documentation for detailed information on inbound deliveries and shipment processing.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.