2393253 - Performance in HCM reports

You have created a customized report based on a HCM data source like Employee Times or Time Accounts. You have followed the instructions in the knowledge base article 1701636 - How to make the Time Series variable for Employee Times or Time Accounts reports? and are using the key date rather than the time series, in order to show variable periods of time. You notice however that your report has a bad performance or even results in time outs, with error messages such as:

Report cannot be opened; report an case.

TREX-ERROR (2626)

TREX-ERROR ocurred

1. Open your report from the assgined work center.
2. For the Key Date variable, enter a value.
3. Click on Go.

The report will either load for a long time, or result in an error.

The Time Series provides not only a restriction on the time frame, but also a characteristic structure. It automatically restricts the data according to the time series.

When you remove it and add the Key Date instead, this automatic restriction is also removed. This means that the report will take longer to load the data.

When using the key date, it will not be possible to call the same amount of data as the time series displays. For example, when you use the Employee Times: Yearly report, you can show data for the last 4 years. If you have a large amount of time postings in your system however, it will not be possible to display 4 years of data without using the time series. In that case, it may be necessary to reduce the time period to a few months (the exact time period that can be called depends on the report view, as well as other selection parameters).

KBA , key date , employee times , AP-RC-ANA , C4C, ByD, Travel: Analytics Tools & Frameworks , How To