How To Fix UJJ_EXCEPTION121 - Access denied to all rows of journal &1

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 121

• Message text: Access denied to all rows of journal &1

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_EXCEPTION121 - Access denied to all rows of journal &1 ?

  The SAP error message UJJ_EXCEPTION121 with the description "Access denied to all rows of journal &1" typically indicates that the user does not have the necessary authorizations to access the specified journal in the SAP system. This can occur in various contexts, such as when trying to view or manipulate journal entries in financial applications.
  Cause:
  
  Authorization Issues: The user lacks the required authorizations to access the journal specified by &1. This could be due to missing roles or permissions in the user's profile.
  Journal Configuration: The journal may be configured in such a way that it restricts access based on certain criteria (e.g., company code, user group).
  Data Privacy Settings: There may be data privacy settings in place that restrict access to certain data based on user roles.
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error to check for authorization failures. This will show you which authorization checks failed.
  Review the user's roles and authorizations in transaction code PFCG. Ensure that the user has the necessary roles assigned that include access to the journal in question.
  
  
  
  Adjust Authorizations:
  
  If the user lacks the necessary authorizations, you may need to adjust their roles or create a new role that includes the required permissions.
  Consult with your SAP security team or administrator to ensure that the user has the appropriate access rights.
  
  
  
  Review Journal Configuration:
  
  Check the configuration of the journal to ensure that it is set up correctly and that there are no restrictions that would prevent access for the user.
  Ensure that the journal is not restricted by company code or other criteria that the user does not meet.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to the specific journal and authorization issues. There may be specific notes or guidelines provided by SAP for handling such errors.
  
  
  
  Testing:
  
  After making changes to authorizations or configurations, have the user log out and log back in to test if the issue is resolved.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  SU53: Display Authorization Check
  PFCG: Role Maintenance
  
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  User Groups: Ensure that the user is part of the correct user groups that have access to the journal.
  
  If the issue persists after following these steps, it may be necessary to engage with SAP support for further assistance.