How To Fix GZ673 - Consolidation versions are being processed by another user

SAP Error Message - Details

• Message type: E = Error

• Message class: GZ - Message class for FI-LC

• Message number: 673

• Message text: Consolidation versions are being processed by another user

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 GZ673 - Consolidation versions are being processed by another user ?

  The SAP error message GZ673, which states "Consolidation versions are being processed by another user," typically occurs in the context of SAP's Financial Consolidation module. This error indicates that the consolidation version you are trying to access or modify is currently locked by another user, preventing you from making changes or running processes on it.
  Cause:
  
  Concurrent Access: Another user is currently working on the same consolidation version, which locks it for other users to prevent data inconsistencies.
  Session Timeout: A previous session may not have been properly closed, leaving the version locked.
  System Configuration: The system may be configured to allow only one user to access a particular consolidation version at a time.
  
  Solution:
  
  Wait and Retry: If another user is working on the version, the simplest solution is to wait until they finish and then try again.
  Identify the User: If you have the necessary permissions, you can check which user is currently accessing the consolidation version. This can often be done through transaction codes like SM04 (User Overview) or SM12 (Lock Entries).
  Release the Lock: If you determine that the lock is no longer valid (e.g., the user has logged off unexpectedly), you may need to release the lock manually using transaction SM12. However, this should be done with caution and ideally with the knowledge of the user who was working on it.
  Check for Background Jobs: Sometimes, background jobs may also lock the consolidation version. Check if any jobs are running that might be causing the lock.
  Consult with IT Support: If the issue persists, it may be necessary to consult with your IT support team or SAP Basis team to investigate further.
  
  Related Information:
  
  User Locking Mechanism: SAP uses a locking mechanism to ensure data integrity. Understanding how this works can help in troubleshooting similar issues in the future.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  SM04: User Overview
  SM12: Lock Entries
  SM21: System Log
  
  
  Documentation: Refer to SAP Help documentation for more details on consolidation processes and user management.
  Best Practices: Implement best practices for user sessions and data access to minimize locking issues, such as proper session management and communication among users.
  
  By following these steps, you should be able to resolve the GZ673 error and continue with your consolidation tasks.