3023597 - Report execution fails with the error "cannot allocate enough memory" in the logs

Symptom

An error occurs when executing a report online. System logs captured by Support show: "cannot allocate enough memory".
An error occurs when previewing the report. System logs also show: "cannot allocate enough memory".
When executed offline, the report completes with status "Failed" and the Job Details contain the message:Error encountered in executing the query: cannot allocate enough memory.
Error getting query preview
Error rendering list report component

Environment

SAP SuccessFactors HCM Suite

Reproducing the Issue

Navigate to Report Center
Execute or preview the report a Table or Canvas report
You'll face an error

Cause

Report execution in SuccessFactors depends on several factors, and these conditions can evolve over time. As a result, reports that previously ran successfully may begin to fail even without any direct configuration change. The memory allocation error may occur due to one or a combination of the following:

Growth in overall data volume, such as additional employee records, history, or transactional data.
RBP complexity can impact report execution. This is not only related to the growing amount of data a user can access, but also to the additional time the system requires to process each role, group, and access criteria assigned to the user before determining what data can be returned.
Large report datasets, including high data volume or multiple joined entities.
Complex report logic, filters, calculated fields, or queries requiring significant processing.
The system’s data-processing workload at the time of execution.

As these factors grow or become more complex, the report may begin requiring more memory or processing time than the system can allocate during execution.

Resolution

You can try the following adjustments, which may help the report complete successfully:

Reduce the number of selected objects and fields.
Apply additional filters to narrow the data set (for example, by date range or organizational criteria).
Simplify the report logic, such as removing calculated columns, reducing complex formulas, or applying more restrictive date filters.
Try scheduling the report for offline execution during non‑business hours, when overall system activity tends to be lower.

Please note:

The volume of data retrieved, the RBP complexity / configuration, and the overall report design are configuration‑related areas. These areas fall outside the scope of SAP Product Support, meaning Support cannot adjust, redesign, or optimize report logic, structure, or permission setups. If any adjustments are needed, customers are welcome to review these elements internally or work with an implementation partner, who can provide guidance on tailoring the report design to best support their business needs. For additional guidance on recommended practices and known limitations, you may also refer to KBA 2418819 – Reports Best Practices & Restrictions for Table and Canvas Reports.
Table and Canvas reports are built on a legacy reporting framework, which does not include built‑in guardrails to prevent overly complex designs. As data volume, permission structures, and report logic grow over time, these reports may reach system limits and encounter performance or memory‑related errors. For more scalable and reliable reporting scenarios, SAP encourages customers to consider Story Reports, which are based on a modern analytics foundation and include guardrails to help prevent designs that can lead to performance issues. You can find the official Story Reports guide here: Story Reports Documentation – SAP Help Portal

Keywords

Report failed, Error encountered executing the query, cannot allocate enough memory, Ad Hoc Report, Table Report, Detailed Reporting, Advanced Reporting, Canvas, ORD

, KBA , LOD-SF-ANA , Analytics & Reporting (Ad Hoc, YouCalc, ORD) , Problem

Product

SAP SuccessFactors HCM Suite all versions