How To Fix /STMC/CR_LOG117 - Screen '&1' (&2) is still used by '&3' (&4)

SAP Error Message - Details

• Message type: E = Error

• Message class: /STMC/CR_LOG -

• Message number: 117

• Message text: Screen '&1' (&2) is still used by '&3' (&4)

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 /STMC/CR_LOG117 - Screen '&1' (&2) is still used by '&3' (&4) ?

  The SAP error message /STMC/CR_LOG117 indicates that a specific screen (identified by the parameters &1 and &2) is still being used by a particular user (identified by &3 and &4). This typically occurs in the context of SAP's Change Request Management (ChaRM) or Transport Management System (TMS), where certain screens or transactions may be locked or in use by another user, preventing changes or actions from being performed.
  Cause:
  
  Screen Locking: The screen is currently being accessed or modified by another user, which prevents other users from making changes or performing actions on that screen.
  Session Management: The user may have an active session that is not properly closed, leading to the screen being marked as in use.
  Transport Requests: If the screen is part of a transport request, it may be locked until the transport is completed or released.
  
  Solution:
  
  Identify the User: Check who is currently using the screen. You can use transaction codes like SM04 (User Overview) or AL08 (Global User Overview) to see active sessions and identify the user holding the lock.
  Communicate with the User: If possible, contact the user who is using the screen and ask them to log off or close the session that is holding the lock.
  Terminate Session: If the user is not available or cannot close the session, an administrator can terminate the session using transaction SM04 or SM12 (to delete locks).
  Wait and Retry: If the screen is being used for a legitimate purpose, you may need to wait until the user has finished their work and then try again.
  Check for Background Jobs: Sometimes, background jobs may also hold locks. Check transaction SM37 to see if there are any jobs that might be using the screen.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like SM04, SM12, SM37, and AL08 for user and session management.
  Lock Management: Understanding how SAP handles locks and sessions can help in troubleshooting similar issues in the future.
  Documentation: Refer to SAP documentation or support notes related to Change Request Management and Transport Management for more detailed guidance on handling locks and errors.
  
  If the issue persists after trying the above solutions, it may be necessary to consult with your SAP Basis team or SAP support for further assistance.