SAP Knowledge Base Article - Public

1926357 - Error message when running report: Report Cannot be Opened / Failed to Open Report

Symptom

You are trying to run a report/data source in the web browser and receive one of the following error message after the report loaded for some time:

  • 'Report cannot be opened; report an incident.'
  • 'Report cannot be opened. (KBA:1926357)'
  • 'Failed to open report "Internal Server Error" - open an incident.'

In such an Incident, no report data is displayed and you can only close the report screen. Sometimes other error messages are possible; you will find them in the See Also section.

Environment

  • SAP Business ByDesign
  • SAP Cloud for Customer

Reproducing the Issue

  1. Go to the respective work center, to the reports list.
  2. Open the report you would like to run.
  3. Set the variables as required and click Go.

You will get one of the above messages.

Cause

This error can be raised in the following circumstances:

  1. The number of records or fields that is requested in the report is too high.
  2. The report is running out of memory due to the number of records that are processed in combination with the modeling of the custom data source / report.
  3. The report is running for too long and results in a time-out.
  4. The report and data source contain a reference to an extension field, however the extension field was deleted from the system.

In custom reports, the time-out can also be caused by the design of the underlying data source. With custom objects in particular, it is not uncommon that the report works fine for a while, but as the data volume in the system increases overall, you may run into this error message.

Resolution

  1. The easiest way to avoid the dump is to reduce the amount of records with a selection on some variables in the report (Edit Selection tab). For example, if a report crashes when selecting data for a full year, try to run it in two packages (one package for the first half of the year and one package for the second half). 
  2. We strongly recommend to check the modeling of the custom data source and the report. We have compiled a list of best practices in the KBA 2366796 - Best Practices for Modeling Data Sources and Reports - Performance. Please review these and compare against the modeling of your data source and report.
  3. In most Incidents, this also needs to be corrected by limiting the report selection and / or optimizing the modeling of the data source and report. In a few Incidents, this may happen because there is another job running in the system that uses the system resources at the time. In that Incident, you can restart the report with the same selections and it will run through.
  4. Please ensure that all extension fields that were referenced in this report / data source are available. You will find the references to the extension fields in the data source documentation: Go to the Design Data Sources work center view and search for your data source. Click the magnifying glass icon in the Documentation tab.    

Other tips and recommendations:

  • With custom objects in particular, it is not uncommon that the report works fine for a while, but as the data volume in the system increases overall, you may run into this error message. Please review the best practices and optimize the data source and report where possible: KBA 2366796 - Best Practices for Modeling Data Sources and Reports - Performance
  • Use the Download function to save the data source in CSV format as it uses less memory (via Download > Data Source in CSV format)
  • Avoid using the Start Options to immediately start the report
  • In some Incidents, sending the report via broadcast can avoid the error. In the broadcast settings, you also have the option to zip the report attachment, which will additionally help to improve performance.

See Also

A large data volume in the report / data source can also trigger other error messages, such as:

  • 'An exception with the type CX_SY_OPEN_SQL_DB occurred, but was neither handled locally, nor declared in a RAISING clause'
  • 'The range of the statement to be passed to the database is too wide'

2366796 - Best Practices for Modeling and Handling Data Sources and Reports - Performance

Keywords

Report cannot be opened, Report an Incident, analytics, time out, report, data source, crash, report error, exception with the type CX_SY_OPEN_SQL_DB occurred, RAISING clause, range of the statement to be passed to the database is too wide, internal server error, failed to open report, AP-RC-ANA, opening, Time Acounts: Monthly, too many fields, , KBA , report an incident , report cannot be opened , der bericht - interner serverfehler- kon , cl_mdrs_mdav_rt_data_fsi=>read_internal , AP-RC-ANA , C4C, ByD, Travel: Analytics Tools & Frameworks , How To

Product

SAP Business ByDesign all versions ; SAP Cloud for Customer add-ins all versions ; SAP Cloud for Customer core applications all versions