How To Fix PZ690 - > Data on partner bank missing (ctry &, key &, acct &)

SAP Error Message - Details

• Message type: E = Error

• Message class: PZ - Messages: Payment program for payment requests

• Message number: 690

• Message text: > Data on partner bank missing (ctry &, key &, acct &)

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 PZ690 - > Data on partner bank missing (ctry &, key &, acct &) ?

  The SAP error message PZ690 indicates that there is missing data related to a partner bank in the system. This error typically arises when you are trying to process a transaction that requires bank details for a partner (such as a vendor or customer), but the necessary information is not available in the system.
  Cause:
  The error message "Data on partner bank missing (ctry &, key &, acct &)" suggests that the system is unable to find the required bank details for a specific partner due to one or more of the following reasons:
  
  Missing Bank Data: The partner (vendor or customer) does not have bank details maintained in the system.
  Incorrect Configuration: The bank details may be incorrectly configured or incomplete.
  Country-Specific Requirements: The country code, bank key, or account number may not be set up correctly or may be missing.
  Data Inconsistency: There may be inconsistencies in the data entered for the partner bank details.
  
  Solution:
  To resolve the PZ690 error, you can follow these steps:
  
  
  Check Partner Master Data:
  
  Go to the transaction code for maintaining vendor or customer master data (e.g., XK02 for vendors or FD02 for customers).
  Verify that the bank details are correctly maintained for the partner in question. Ensure that the country, bank key, and account number are filled in.
  
  
  
  Maintain Bank Details:
  
  If the bank details are missing, you will need to add them. Make sure to enter the correct country code, bank key, and account number.
  Ensure that the bank key is valid and corresponds to the correct bank in the system.
  
  
  
  Check Configuration:
  
  If you are an administrator, check the configuration settings for bank master data in the SAP system. Ensure that the necessary settings for the country and bank key are correctly configured.
  
  
  
  Data Consistency:
  
  Ensure that there are no inconsistencies in the data. For example, check if the bank key is valid and exists in the bank master data.
  
  
  
  Testing:
  
  After making the necessary changes, test the transaction again to see if the error persists.
  
  
  
  Related Information:
  
  
  Transaction Codes: 
  
  XK02 - Change Vendor
  FD02 - Change Customer
  FI01 - Create Bank Master Data
  FI02 - Change Bank Master Data
  
  
  
  Documentation: Refer to SAP Help documentation for more details on maintaining vendor and customer bank details.
  
  
  User Roles: Ensure that the user has the necessary authorizations to view and edit partner bank details.
  
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or refer to SAP Notes for any known issues related to this error message.