How To Fix GJ864 - No Bank/Account Details Found for Company &, Partner &

SAP Error Message - Details

• Message type: E = Error

• Message class: GJ - Joint Venture Accounting

• Message number: 864

• Message text: No Bank/Account Details Found for Company &, Partner &

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 GJ864 - No Bank/Account Details Found for Company &, Partner & ?

  The SAP error message GJ864 "No Bank/Account Details Found for Company &, Partner &" typically occurs when the system is unable to find the bank account details for a specified company code and partner (which could be a vendor, customer, or business partner). This can happen in various scenarios, such as during payment processing, vendor invoice entry, or when trying to execute a transaction that requires bank details.
  Causes:
  
  Missing Bank Details: The most common cause is that the bank account information has not been maintained for the specified company code and partner.
  Incorrect Partner or Company Code: The specified partner or company code may be incorrect or not exist in the system.
  Data Inconsistency: There may be inconsistencies in the master data, such as the partner not being properly linked to the company code.
  Authorization Issues: The user may not have the necessary authorizations to view or access the bank details for the specified partner.
  
  Solutions:
  
  
  Maintain Bank Details:
  
  Go to the relevant transaction (e.g., vendor master data maintenance using transaction code XK02 for vendors or BP for business partners).
  Ensure that the bank account details are correctly entered for the specified company code and partner.
  Check that the bank account is active and not marked for deletion.
  
  
  
  Verify Partner and Company Code:
  
  Double-check the partner ID and company code you are using in the transaction to ensure they are correct.
  Use transaction codes like SE16 or SE11 to view the relevant tables (e.g., LFBK for vendor bank details) to confirm the existence of the data.
  
  
  
  Check Data Consistency:
  
  Ensure that the partner is properly linked to the company code in the master data.
  If necessary, reassign the partner to the correct company code.
  
  
  
  Authorization Check:
  
  Verify that the user has the necessary authorizations to access the bank details for the specified partner.
  Consult with your SAP security team if you suspect authorization issues.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or help files for additional context on the error message and related transactions.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  XK02 - Change Vendor
  BP - Business Partner Maintenance
  SE16 - Data Browser
  SE11 - Data Dictionary
  
  
  Tables:
  
  LFBK - Vendor Bank Details
  KNA1 - General Data in Customer Master
  LFA1 - Vendor Master (General Section)
  
  
  
  If the issue persists after checking the above points, it may be beneficial to consult with your SAP support team or refer to SAP Notes for any known issues or patches related to this error message.