How To Fix PRF_CNTRL_MSG104 - Record &1 is already locked in FI. Please unlock & proceed


SAP Error Message - Details

  • Message type: E = Error

  • Message class: PRF_CNTRL_MSG - Message Class for control messages of PRF

  • Message number: 104

  • Message text: Record &1 is already locked in FI. Please unlock & proceed

  • Show details Hide details


  • 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 PRF_CNTRL_MSG104 - Record &1 is already locked in FI. Please unlock & proceed ?

    The SAP error message PRF_CNTRL_MSG104 indicates that a specific record (identified by &1) is currently locked in the Financial Accounting (FI) module. This typically occurs when another user or process is currently accessing or modifying the record, preventing you from making changes or processing transactions that involve that record.

    Cause:

    1. Concurrent Access: Another user or session is currently editing or processing the same record.
    2. Unfinished Transactions: A previous transaction that involved the record was not completed properly, leaving it in a locked state.
    3. Background Jobs: A background job may be running that is accessing the same record.
    4. System Errors: Sometimes, system errors or crashes can leave records in a locked state.

    Solution:

    1. Identify the Lock:

      • Use transaction code SM12 to check for locks on the record. You can search for the user or the specific record that is locked.
      • Look for the user ID that has locked the record and the transaction that is causing the lock.
    2. Unlock the Record:

      • If you have the necessary authorizations, you can manually unlock the record in transaction SM12. Be cautious when doing this, as it may disrupt another user's work.
      • If the lock is due to a user session that is no longer active, you can delete the lock entry.
    3. Wait and Retry:

      • If the lock is due to another user actively working on the record, it may be best to wait until they have completed their work and then retry your transaction.
    4. Check for Background Jobs:

      • Use transaction SM37 to check if there are any background jobs that might be locking the record. If you find any, you may need to wait for them to complete or contact the responsible person.
    5. Contact Support:

      • If you are unable to resolve the issue, consider reaching out to your SAP support team or system administrator for assistance.

    Related Information:

    • Transaction Codes:

      • SM12: Display and manage lock entries.
      • SM37: Monitor background jobs.
      • SE11: Data dictionary to check the structure of the table related to the locked record.
    • User Communication: If you find that another user is locking the record, communicate with them to understand their needs and coordinate access.

    • Documentation: Review SAP documentation or notes related to locking mechanisms in FI to understand how locks are managed and best practices for avoiding conflicts.

    By following these steps, you should be able to resolve the PRF_CNTRL_MSG104 error and proceed with your work in SAP.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant