How To Fix PG356 - Report & is currently being processed

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 356

• Message text: Report & 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 PG356 - Report & is currently being processed ?

  The SAP error message PG356, which states "Report & is currently being processed," typically occurs when a user attempts to execute a report that is already running in the background or is being processed by another user. This can happen in various SAP modules, particularly in reporting transactions.
  Cause:
  
  Concurrent Execution: The report is already being executed by another user or in another session.
  Background Job: The report may be scheduled as a background job and is currently in progress.
  Long-Running Reports: Some reports take a significant amount of time to process, leading to this message if another attempt is made to run the same report.
  
  Solution:
  
  Wait and Retry: If the report is running, wait for it to complete and then try executing it again.
  Check Background Jobs: 
  
  Go to transaction code SM37 to check the status of background jobs.
  Look for the report in question and see if it is still running or has completed.
  
  
  Identify User Sessions: 
  
  Use transaction code SM04 to see if another user is executing the report.
  If you have the necessary permissions, you can ask the user to cancel their job if it is taking too long.
  
  
  Job Management: If the report is scheduled as a background job, you can manage it through transaction SM37. You can also delete or cancel jobs if necessary.
  System Performance: If reports are frequently taking too long, consider reviewing system performance or optimizing the report for better efficiency.
  
  Related Information:
  
  Transaction Codes:
  
  SM37: Monitor background jobs.
  SM04: User sessions overview.
  SE38: Execute reports.
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to the specific report you are trying to run.
  Documentation: Review the documentation for the specific report to understand its execution time and any known limitations.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or technical support for further investigation.