How To Fix UJJ_EXCEPTION058 - Incoherence between journal ids and group id for group &1

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 058

• Message text: Incoherence between journal ids and group id for group &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_EXCEPTION058 - Incoherence between journal ids and group id for group &1 ?

  The SAP error message UJJ_EXCEPTION058 indicates an inconsistency between journal IDs and group IDs in the context of financial postings or journal entries. This error typically arises in the Universal Journal (ACDOCA) when there is a mismatch between the journal entries and the group accounting settings.
  Cause:
  
  
  Inconsistent Data: The journal entries may have been created or modified in a way that does not align with the group accounting settings. This can happen if:
  
  Journal entries are posted with incorrect group IDs.
  There are changes in the configuration of group accounting that have not been reflected in the journal entries.
  Data migration issues where journal entries were not properly aligned with the group IDs.
  
  
  
  Configuration Issues: There may be issues in the configuration of the group accounting settings in the system, leading to discrepancies.
  
  
  Custom Developments: If there are custom programs or enhancements that manipulate journal entries, they may not be handling group IDs correctly.
  
  
  Solution:
  
  
  Check Journal Entries: Review the journal entries that are causing the error. Ensure that the journal IDs correspond correctly to the group IDs. You can do this by:
  
  Using transaction codes like FB03 (Display Document) to view the journal entries.
  Checking the group ID associated with each journal entry.
  
  
  
  Review Configuration: Verify the configuration settings for group accounting in the system. Ensure that the settings are correctly aligned with the journal entries being posted.
  
  
  Data Consistency Check: Run consistency checks on the financial data to identify any discrepancies. This can often be done using standard SAP reports or tools.
  
  
  Repost Journal Entries: If necessary, you may need to reverse and repost the journal entries with the correct group IDs.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to this error message for any specific guidance or patches that may address the issue.
  
  
  Contact SAP Support: If the issue persists and cannot be resolved through the above steps, consider reaching out to SAP support for further assistance.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FB03 (Display Document), FB08 (Reverse Document), and OB52 (Open/Close Posting Periods).
  SAP Notes: Check for any SAP Notes that may address this specific error or provide additional troubleshooting steps.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.