How To Fix GZ671 - Elimination of IC profit and loss: FS items in use by another user

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 671

• Message text: Elimination of IC profit and loss: FS items in use 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 GZ671 - Elimination of IC profit and loss: FS items in use by another user ?

  The SAP error message GZ671, which states "Elimination of IC profit and loss: FS items in use by another user," typically occurs in the context of intercompany (IC) profit and loss elimination processes. This error indicates that the financial statement (FS) items you are trying to process are currently being accessed or locked by another user, preventing your transaction from proceeding.
  Cause:
  
  Concurrent Access: Another user is currently processing or has locked the financial statement items you are trying to work with.
  Session Lock: The system may have a session lock on the FS items due to a previous transaction that has not been completed or has been left open.
  Long-running Transactions: If a transaction takes a long time to process, it can lead to locks on the relevant data.
  
  Solution:
  
  Check User Sessions: Identify if another user is currently working on the same financial statement items. You can use transaction codes like SM12 (to view locks) or SM20 (to check user activity) to see if there are any active sessions that are locking the items.
  Wait and Retry: If another user is working on the items, you may need to wait until they complete their transaction and release the lock.
  Terminate Locks: If you have the necessary authorizations, you can terminate the session that is holding the lock using transaction SM12. However, this should be done with caution and ideally after consulting with the user or your IT team.
  Check for Background Jobs: Sometimes, background jobs may also hold locks. Check if there are any background jobs running that might be affecting the FS items.
  System Restart: In rare cases, if the issue persists and is affecting multiple users, a system restart may be necessary to clear any lingering locks.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like SM12 (to view and manage locks), SM21 (to view system logs), and SM37 (to monitor background jobs).
  User Communication: Ensure good communication among users to avoid conflicts when working on shared financial statement items.
  Documentation: Review SAP documentation or consult with your SAP support team for specific configurations or settings that might be causing frequent locking issues.
  
  If the problem persists after trying the above solutions, it may be beneficial to reach out to your SAP support team for further assistance, as they can provide more detailed insights based on your specific system configuration and usage patterns.