How To Fix BORGR586 - Inbound delivery cannot be saved; there are still messages

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 586

• Message text: Inbound delivery cannot be saved; there are still messages

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 BORGR586 - Inbound delivery cannot be saved; there are still messages ?

  The SAP error message BORGR586 indicates that an inbound delivery cannot be saved because there are still messages that need to be processed. This typically occurs in the context of handling inbound deliveries in the SAP system, particularly when using the EDI (Electronic Data Interchange) or IDoc (Intermediate Document) interfaces.
  Cause:
  The error is usually caused by one of the following reasons:
  
  Unprocessed Messages: There are messages related to the inbound delivery that have not been processed or acknowledged. This could be due to errors in the message processing or simply that the messages are still in a queue.
  Message Status: The status of the messages may not allow the inbound delivery to be saved. For example, if there are errors in the messages that need to be resolved first.
  Configuration Issues: There may be configuration issues in the message processing settings or in the EDI/IDoc setup that prevent the messages from being processed correctly.
  
  Solution:
  To resolve the error, you can follow these steps:
  
  
  Check Message Status:
  
  Go to transaction WE02 or WE05 to view the IDocs and check the status of the messages related to the inbound delivery.
  Look for any error messages or statuses that indicate why the messages are not processed.
  
  
  
  Process or Correct Messages:
  
  If there are errors in the messages, you will need to correct them. This may involve fixing data issues or reprocessing the IDocs.
  If the messages are in a "waiting" status, you may need to trigger the processing manually.
  
  
  
  Review Configuration:
  
  Check the configuration settings for the inbound delivery processing and the message handling in the relevant modules (e.g., MM, SD).
  Ensure that the necessary settings for EDI/IDoc processing are correctly configured.
  
  
  
  Consult Logs:
  
  Review the application logs (transaction SLG1) for any additional information related to the error. This can provide insights into what went wrong during the message processing.
  
  
  
  Re-attempt Saving:
  
  After addressing the issues with the messages, try to save the inbound delivery again.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VL31N (Create Inbound Delivery), WE02/WE05 (IDoc Monitoring), and SLG1 (Application Log).
  SAP Notes: Check for any SAP Notes related to this error message for specific patches or updates that may address known issues.
  Documentation: Review SAP documentation on inbound delivery processing and message handling for best practices and troubleshooting tips.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or reach out to SAP support for further assistance.