Resolving the Unable to load the data entry form as the number of data entry cells exceeded the threshold Error

Oracle Enterprise Performance Management Cloud uses a number of governor thresholds to ensure optimum performance. Oracle Hyperion Planning displays the Unable to load the data entry form as the number of data entry cells exceeded the threshold message and prevent you from loading data into the form if it exceeds the data entry cell threshold. This threshold, which ensures the availability of EPM Cloud while running large queries, cannot be raised. Such forms are too large to be run in Oracle Smart View for Office.

These options are available to avoid the Unable to load the data entry form as the number of data entry cells exceeded the threshold error:

  • Suppress missing blocks in the affected form.
  • Redesign the form.

    Because Planning is used for planning and budgeting, the initial goal should be to not use forms for reporting purposes or data mining. It is a mistake to try and use Planning as a way to hunt for data.

    It is quite likely that business users know the specific location of the data slice allowing them to narrow the scope of the form by moving the largest row or column dimension to the page. Designing and maintaining a form that looks everywhere for a specific data slice is easier, but is not optimal. Forms should be designed for a specific business purpose and should focus on a select slice of the overall data for the portion of the budget that is being worked on at the time. This concept of designing forms provides better security access control to slices of data.

    For example, assume that iDescendants of DimA and DimB are added as rows and there are 1000 members in each dimension, which means you are starting with one million rows. If four columns are present in this form, this form has a cell count of four million. To reduce form size, you can create a form with one of these dimensions, preferably, the largest sparse dimension (for example, DimA), as the anchor dimension. The redesigned form is then based on the number of members in DimA. The other dimension (DimB) remains in the row, which means that you have 1000 rows in the form. If you use the page dimension to toggle between available members in DimA and analyze and budget accordingly, you will not run a query on four million cells.

  • Reduce or clear empty block

    While the cell count does not include missing blocks, it includes empty blocks (blocks without data). You should clear empty blocks if they are not needed for allocation purposes. You can clear empty blocks using Oracle Hyperion Calculation Manager. You can do this also by exporting level0 data, then clearing all data, then importing level0 data, and then running aggregation.