How To Fix FKKID_MSG090 - Confirmation headers with document number &1 are locked by user &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FKKID_MSG - Messages for FI-CA Loc. Cross-Country

• Message number: 090

• Message text: Confirmation headers with document number &1 are locked by user &2

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 FKKID_MSG090 - Confirmation headers with document number &1 are locked by user &2 ?

  The SAP error message FKKID_MSG090 indicates that confirmation headers with a specific document number are locked by a user. This typically occurs in the context of the SAP Contract Accounts Receivable and Payable (FI-CA) module, where certain documents may be locked for editing or processing by another user.
  Cause:
  
  User Lock: The document is currently being processed or edited by another user, which prevents other users from making changes to it.
  Transaction in Progress: A transaction related to the document is still in progress, leading to a lock.
  System Error: Occasionally, system errors or inconsistencies can lead to locks that do not release properly.
  
  Solution:
  
  Wait and Retry: If the document is locked by another user, the simplest solution is to wait until that user has completed their work and released the lock.
  Identify the Locking User: Use transaction code SM12 to check for locks. You can search for the document number and see which user has locked it. If necessary, you can contact that user to understand the situation.
  Release the Lock: If you have the necessary authorizations and it is appropriate to do so, you can manually release the lock in transaction SM12. Be cautious with this approach, as it may disrupt the work of the user who has the lock.
  Check for Background Jobs: Sometimes, background jobs may hold locks. Check transaction SM37 to see if any jobs are running that might be related to the document.
  System Restart: In rare cases, a system restart may be required to clear persistent locks, but this should be done with caution and typically involves coordination with your SAP Basis team.
  
  Related Information:
  
  Transaction Codes:
  
  SM12: To view and manage locks.
  SM37: To check background jobs.
  SE11: To check the data dictionary for the relevant tables if needed.
  
  
  Documentation: Refer to SAP Help documentation for more details on locking mechanisms in SAP and best practices for handling locks.
  User Training: Ensure that users are trained on how to properly release documents and avoid unnecessary locks.
  
  If the issue persists after trying the above solutions, it may be necessary to consult with your SAP Basis team or SAP support for further investigation.