How To Fix BORGR644 - Inbound delivery displayed is not consistent for GR; Save first

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 644

• Message text: Inbound delivery displayed is not consistent for GR; Save first

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 BORGR644 - Inbound delivery displayed is not consistent for GR; Save first ?

  The SAP error message BORGR644 typically indicates that there is an inconsistency in the inbound delivery data when trying to perform a goods receipt (GR). This error usually arises when the system detects that the inbound delivery has not been saved or is in an incomplete state, which prevents the goods receipt from being processed.
  Cause:
  
  Incomplete Inbound Delivery: The inbound delivery may not have been fully saved or may be missing required information.
  Status Issues: The status of the inbound delivery might not allow for a goods receipt to be processed (e.g., it might be in a "not yet processed" state).
  Data Locking: There could be a data locking issue where another transaction is currently processing the inbound delivery.
  User Authorization: The user may not have the necessary authorizations to perform the goods receipt for the specific inbound delivery.
  
  Solution:
  
  Save the Inbound Delivery: Ensure that the inbound delivery is saved properly. Go to the inbound delivery document and check if all required fields are filled out. Save the document before attempting to perform the goods receipt.
  Check Status: Verify the status of the inbound delivery. It should be in a state that allows for goods receipt processing. If it is not, you may need to change its status or complete any missing steps.
  Review Data: Check for any missing or incorrect data in the inbound delivery. Ensure that all necessary information is provided and correct.
  Release Locks: If there is a data locking issue, wait for the other transaction to complete or check with your system administrator to release any locks.
  Authorization Check: Ensure that you have the necessary permissions to perform the goods receipt for the inbound delivery. If not, contact your SAP administrator to obtain the required authorizations.
  
  Related Information:
  
  Transaction Codes: You can use transaction codes like VL31N (Create Inbound Delivery) or VL32N (Change Inbound Delivery) to manage inbound deliveries.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Documentation: Refer to SAP documentation for detailed information on inbound deliveries and goods receipts to understand the process better.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or refer to SAP community forums for further assistance.