How To Fix BORGR086 - Purchasing document & & determined from summarized JIT call item(s)

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 086

• Message text: Purchasing document & & determined from summarized JIT call item(s)

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 BORGR086 - Purchasing document & & determined from summarized JIT call item(s) ?

  The SAP error message BORGR086 typically occurs in the context of Just-In-Time (JIT) delivery processes, particularly when dealing with purchasing documents. This error indicates that there is an issue with the purchasing document that has been determined from the summarized JIT call item(s). Here’s a breakdown of the potential causes, solutions, and related information for this error:
  Causes:
  
  Missing or Incorrect Purchasing Document: The purchasing document that is supposed to be linked to the JIT call item may be missing or incorrectly specified.
  Inconsistent Data: There may be inconsistencies in the data between the JIT call items and the purchasing document.
  JIT Configuration Issues: The configuration settings for JIT in the system may not be set up correctly, leading to issues in document determination.
  Document Status: The purchasing document may be in a status that does not allow it to be processed (e.g., blocked, deleted, or completed).
  Authorization Issues: The user may not have the necessary authorizations to access or process the purchasing document.
  
  Solutions:
  
  Check Purchasing Document: Verify that the purchasing document exists and is correctly specified in the system. Ensure that it is active and not blocked or deleted.
  Review JIT Call Items: Examine the JIT call items to ensure that they are correctly configured and that there are no discrepancies in the data.
  Configuration Review: Check the JIT configuration settings in the system to ensure they are set up correctly. This may involve reviewing the settings in the customizing transaction (SPRO).
  Document Status Check: Ensure that the purchasing document is in a valid status for processing. If it is blocked or completed, you may need to take appropriate actions to unblock or reactivate it.
  Authorization Check: Ensure that the user has the necessary authorizations to access and process the purchasing document. This may involve checking user roles and permissions.
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes such as ME23N (Display Purchase Order) or ME2N (Purchase Orders by PO Number) to investigate the purchasing document.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance on troubleshooting.
  Documentation: Review SAP documentation related to JIT processes and purchasing document management for further insights.
  
  If the issue persists after checking these areas, it may be beneficial to consult with your SAP support team or refer to SAP community forums for additional assistance.