How To Fix PG357 - Screen & is currently being processed

SAP Error Message - Details

• Message type: E = Error

• Message class: PG - Error Messages for Master Data Programs

• Message number: 357

• Message text: Screen & is currently being processed

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 PG357 - Screen & is currently being processed ?

  The SAP error message PG357 typically indicates that a particular screen or transaction is currently being processed by another user or session. This can happen in various scenarios, such as when a user tries to access a transaction that is already open or when a background job is running that locks the screen.
  Cause:
  
  Concurrent Access: Another user is currently using the same transaction or screen.
  Session Lock: The transaction is locked due to a previous session that has not been completed or has not been properly closed.
  Background Job: A background job is running that is using the same resources or data.
  System Performance Issues: High system load or performance issues may cause delays in processing, leading to this message.
  
  Solution:
  
  Wait and Retry: If the screen is being processed by another user, wait for them to complete their transaction and then try again.
  Check Active Sessions: Use transaction code SM04 to check active user sessions. If you find a session that is stuck or not responding, you may need to contact the user or your system administrator to resolve it.
  Transaction Lock Release: If you have the necessary permissions, you can use transaction code SM12 to check for and release any locks that may be causing the issue.
  System Monitoring: Use transaction codes like SM37 to monitor background jobs and see if any jobs are causing the lock.
  Log Off and Log Back In: Sometimes, simply logging off and back into the SAP system can resolve session-related issues.
  Contact Support: If the issue persists, it may be necessary to contact your SAP support team for further assistance.
  
  Related Information:
  
  Transaction Codes:
  
  SM04: User Overview
  SM12: Lock Entries
  SM37: Job Monitoring
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  System Performance: Regularly monitor system performance to prevent issues related to high load or resource contention.
  
  If you continue to experience issues, it may be beneficial to gather more specific details about the context in which the error occurs and consult with your SAP Basis team or support for a deeper investigation.