How To Fix FKCHK368 - Check &1 is locked; check requested at the bank

SAP Error Message - Details

• Message type: E = Error

• Message class: FKCHK - Check Repository Messages

• Message number: 368

• Message text: Check &1 is locked; check requested at the bank

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 FKCHK368 - Check &1 is locked; check requested at the bank ?

  The SAP error message FKCHK368 indicates that a specific check (identified by the number &1) is locked, and the check requested at the bank cannot be processed due to this lock. This situation typically arises in the context of payment processing, particularly when dealing with checks in the SAP Financial Accounting (FI) module.
  Cause:
  
  Check Locking: The check may be locked because it is currently being processed by another user or transaction. This can happen if someone is trying to post or modify the check while another process is attempting to access it.
  Incomplete Processing: The check might be in a state of incomplete processing, such as being in a pending status or awaiting approval.
  Database Lock: There could be a database lock on the check record due to a transaction that has not been completed or has encountered an error.
  
  Solution:
  
  Check for Active Sessions: Verify if another user is currently processing the check. If so, you may need to wait until they complete their transaction.
  Transaction Monitoring: Use transaction codes like SM12 (to check for locks) and SM21 (to view system logs) to identify any active locks on the check. You can also check transaction codes like SE16 or SE11 to view the relevant database tables.
  Release Locks: If you find that a lock is no longer needed (for example, if a user has left a session open), you can manually release the lock using transaction SM12. However, be cautious when doing this to avoid data inconsistencies.
  Check Status: Ensure that the check is not in a pending or incomplete status. If it is, you may need to complete or cancel the previous transaction that is holding up the check.
  Consult Documentation: Review SAP documentation or consult with your SAP support team for specific guidance related to your system configuration and version.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  SM12: To view and manage locks.
  SM21: To check system logs for errors.
  FBZP: To configure payment methods and settings.
  
  
  User Roles: Ensure that users have the appropriate roles and authorizations to process checks and payments.
  SAP Notes: Check for any SAP Notes related to this error message for additional troubleshooting steps or patches that may resolve the issue.
  
  If the problem persists after following these steps, it may be necessary to escalate the issue to your SAP Basis or technical support team for further investigation.