How To Fix BORGR560 - Inbound delivery &1 was removed from shipment &2

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 560

• Message text: Inbound delivery &1 was removed from shipment &2

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message BORGR560 - Inbound delivery &1 was removed from shipment &2 ?

  The SAP error message BORGR560 indicates that an inbound delivery has been removed from a shipment. This can occur in the context of logistics and transportation management within the SAP system. Here’s a breakdown of the potential causes, solutions, and related information for this error:
  Causes:
  
  Manual Removal: The inbound delivery may have been manually removed from the shipment by a user.
  System Configuration: There may be configuration settings in the shipment processing that automatically remove certain inbound deliveries based on specific criteria.
  Status Changes: Changes in the status of the inbound delivery or shipment (e.g., cancellation, completion) can lead to the removal of the delivery from the shipment.
  Data Inconsistencies: There may be inconsistencies in the data related to the inbound delivery or shipment, such as missing or incorrect information.
  Business Rules: Certain business rules or workflows may dictate that an inbound delivery cannot remain in a shipment under specific conditions.
  
  Solutions:
  
  Check Shipment and Delivery Status: Review the status of both the shipment and the inbound delivery to ensure they are in the correct state for processing.
  Review Change Logs: Check the change logs to see if there were any recent changes made to the shipment or inbound delivery that could have triggered the removal.
  Reassign the Inbound Delivery: If the removal was unintentional, you may need to reassign the inbound delivery back to the shipment.
  Consult Configuration Settings: Review the configuration settings in the SAP system related to shipment processing to ensure they align with your business processes.
  Error Handling Procedures: Implement error handling procedures to manage situations where deliveries are removed unexpectedly, including notifications to relevant personnel.
  Contact SAP Support: If the issue persists and cannot be resolved through standard procedures, consider reaching out to SAP support for further assistance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VL01N (Create Outbound Delivery), VL02N (Change Outbound Delivery), and VT01N (Create Shipment) to manage deliveries and shipments effectively.
  Documentation: Review SAP documentation and help resources for specific details on handling inbound deliveries and shipments.
  User Training: Ensure that users involved in logistics and shipment processing are adequately trained on the system to minimize errors.
  
  By addressing the underlying causes and following the suggested solutions, you should be able to resolve the BORGR560 error and prevent it from occurring in the future.