Diagnosis
First the Reporting Agent tries to find a precalculation that exactlycorresponds to the parameterization that resulted from the request URL.
However it could be that there is no precalculation available for it.

System Response
In this case, the system tries to find other precalculations thatcontain the request defined by the URL. The other availablecharacteristics that are not in the drilldown are tested for theirsuitability. If a fitting selection is found it can be used as an answerto the user's request.
Since most of the time there is no clear correct selection, the resultcan sometimes be different (as described above).

Procedure
Calling the advanced precalculation search can have the followingcauses:
- A control query was used for precalculation; the parameters thatresulted were not considered in the calling URL. To obtain a correct URLcall the transaction RSRAPS (Reporting Agent Page Store) and navigate toa precalculated package to the Index.htm file. Here you will find acorrect URL for the current detail document as a comment.
- There is no precalculation in the logon language for the current user.
- You are asking for a user-specific precalculation but there are onlyprecalculations that were created for other users; in this case, eithera general precalculation (not user-specific) must be performed or thecurrent user has to be added to the precalculation.
- An additional parameterization is provided in the calling URL (such asuser-exit variables), that has neither been defined by the control querynor by the variable screen of the Web template used duringprecalculation as the key for the Reporting Agent.
- A user was given authorization later or added to an authorized rolelater or something similar - but there is not current calculation forthis user, which means he cannot yet be recognized as being authorized.
- There really is no suitable precalculation.

Procedure for System Administration
Perform the appropriate, correct calculation.