How To Fix UJJ_EXCEPTION124 - Cannot clear journals because some journals are posted or locked

SAP Error Message - Details

• Message type: E = Error

• Message class: UJJ_EXCEPTION - BPC: Message Class for UJJ Exception

• Message number: 124

• Message text: Cannot clear journals because some journals are posted or locked

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 UJJ_EXCEPTION124 - Cannot clear journals because some journals are posted or locked ?

  The SAP error message UJJ_EXCEPTION124 indicates that there are issues with clearing journals due to some journals being either posted or locked. This typically occurs in the context of financial transactions, particularly when trying to clear or reconcile journal entries in the system.
  Causes:
  
  Posted Journals: Some journal entries may have already been posted to the general ledger, which prevents them from being cleared.
  Locked Journals: Journals may be locked due to various reasons, such as being in use by another user, being part of a closed period, or being locked for adjustments.
  Open Periods: The financial period may be open for posting, but certain entries are still locked for clearing.
  Authorization Issues: The user may not have the necessary permissions to clear certain journals.
  
  Solutions:
  
  Check Journal Status: Review the status of the journals you are trying to clear. Ensure that they are not posted or locked. You can do this by navigating to the relevant transaction codes (e.g., FB03 for displaying documents).
  Unlock Journals: If journals are locked, determine the reason for the lock. If they are locked by another user, you may need to wait until they are released. If they are locked due to period closing, you may need to consult with your finance team to unlock them.
  Reconcile Entries: Ensure that all entries that need to be cleared are reconciled and that there are no discrepancies.
  Check Authorization: Verify that you have the necessary permissions to perform the clearing operation. If not, contact your SAP administrator to obtain the required access.
  Consult Documentation: Refer to SAP documentation or your organization's internal guidelines for clearing journals to ensure compliance with procedures.
  Use Transaction Codes: Utilize transaction codes like F.13 (Automatic Clearing) or F.12 (Manual Clearing) to manage clearing processes effectively.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FB03 (Display Document), FBL1N (Vendor Line Item Display), FBL3N (G/L Account Line Item Display), and FBL5N (Customer Line Item Display).
  SAP Notes: Check for any SAP Notes related to this error message for specific patches or updates that may address the issue.
  User Forums: Engage with SAP community forums or user groups for additional insights and solutions from other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, it may be beneficial to escalate the issue to your SAP support team for further investigation.