How To Fix BORGR564 - Inbound delivery &1 created and transferred to shipment &2

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 564

• Message text: Inbound delivery &1 created and transferred to 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 BORGR564 - Inbound delivery &1 created and transferred to shipment &2 ?

  The SAP error message BORGR564 typically indicates that there is an issue related to the creation and transfer of an inbound delivery to a shipment. This message is often encountered in the context of logistics and supply chain management within SAP systems, particularly when dealing with inbound deliveries and their integration with shipments.
  Cause:
  The error message BORGR564 can arise due to several reasons, including:
  
  Data Inconsistencies: There may be inconsistencies in the data related to the inbound delivery or shipment, such as missing or incorrect information.
  Configuration Issues: The system configuration for handling inbound deliveries and shipments may not be set up correctly.
  Authorization Issues: The user may not have the necessary authorizations to create or transfer the inbound delivery to the shipment.
  System Errors: There could be temporary system errors or issues with the SAP application that prevent the process from completing successfully.
  
  Solution:
  To resolve the BORGR564 error, you can take the following steps:
  
  Check Data Consistency: Verify that all required data for the inbound delivery and shipment is complete and accurate. This includes checking for missing fields or incorrect entries.
  Review Configuration: Ensure that the configuration settings for inbound deliveries and shipments are correctly set up in the SAP system. This may involve checking the relevant customizing settings in SPRO.
  Authorization Check: Confirm that the user has the necessary authorizations to perform the actions related to inbound deliveries and shipments. You may need to consult with your SAP security team.
  System Logs: Check the system logs (transaction SLG1) for any additional error messages or warnings that may provide more context about the issue.
  Reprocess the Delivery: If the error occurred during a batch process, try to reprocess the inbound delivery and shipment to see if the issue persists.
  Consult SAP Notes: Look for any relevant SAP Notes or documentation that may address this specific error message. SAP Notes often provide solutions or workarounds for known issues.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VL31N (Create Inbound Delivery) and VT01N (Create Shipment) to navigate the processes involved.
  SAP Help Portal: Utilize the SAP Help Portal for detailed documentation on inbound deliveries and shipments.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  If the issue persists after following these steps, it may be beneficial to involve your SAP support team or consult with SAP directly for further assistance.