How To Fix FKK_ID135 - Prenotification Lot must be closed when BankKey doesnot exist is selected

SAP Error Message - Details

• Message type: E = Error

• Message class: FKK_ID - Message class for FI-CA country specific development

• Message number: 135

• Message text: Prenotification Lot must be closed when BankKey doesnot exist is selected

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 FKK_ID135 - Prenotification Lot must be closed when BankKey doesnot exist is selected ?

  The SAP error message FKK_ID135 typically occurs in the context of the Contract Accounts Receivable and Payable (FI-CA) module when dealing with prenotifications for bank transfers. This error indicates that a prenotification lot must be closed when a specific bank key does not exist.
  Cause:
  The error arises due to the following reasons:
  
  Bank Key Configuration: The bank key specified in the prenotification lot does not exist in the system. This could be due to incorrect data entry or the bank key not being set up in the system.
  Open Prenotification Lot: The prenotification lot is still open, and the system requires it to be closed before proceeding with further actions.
  Data Inconsistency: There may be inconsistencies in the data related to the prenotification lot or the bank details.
  
  Solution:
  To resolve the error, you can follow these steps:
  
  
  Check Bank Key:
  
  Verify that the bank key specified in the prenotification lot exists in the system. You can do this by navigating to the relevant configuration or master data transaction (e.g., FI12 for bank master data).
  If the bank key does not exist, you will need to create it or correct the entry in the prenotification lot.
  
  
  
  Close the Prenotification Lot:
  
  If the prenotification lot is open, you need to close it. This can typically be done through the transaction code related to prenotification processing (e.g., FPAYM or FPL9).
  Ensure that all necessary transactions related to the prenotification lot are completed before closing it.
  
  
  
  Review Configuration:
  
  Check the configuration settings for bank transfers and prenotifications in the system. Ensure that all necessary settings are correctly configured.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for specific guidance on handling prenotification lots and bank keys.
  
  
  
  Contact Support:
  
  If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FI12 (Bank Master Data), FPAYM (Payment Lot Processing), and FPL9 (Payment Lot Display).
  SAP Notes: Check for any SAP Notes related to this error message for additional insights or patches that may address the issue.
  Documentation: Review the SAP Help Portal for detailed information on managing prenotifications and bank keys in the FI-CA module.
  
  By following these steps, you should be able to identify the cause of the error and implement the necessary solutions to resolve it.