Information about Saving Report Data 

The SAP Banking Risk Management application currently only offers limited possibilities for accessing the results of previous evaluations. As drilldown is used for reporting, the results can be stored within this tool as saved report data and can then be accessed using the same tool (see also Saving report data) There are certain limitations if this technique is used for the long-term storage of report data. The reason for this is that report data was originally intended for short-term storage only. The main purpose of this was to make the results of reports executed in background available for subsequent online analysis. The technique chosen and the management of saved report data are optimized for this purpose. Report data is stored in table COIX_DATA40. In Risk Management, table TRIX_DATA is also used for storing additional data. These are index tables, in which data exists in a packed form and as unstructured packets. This form both reduces the amount of data and achieves optimum speed of access.

Access time and the amount of data are further minimized because only the data required for the particular report in its current form is stored, that is only the characteristics and key figures selected. Therefore the system is unable to interpret saved report data after a change has been made to the report or to one of its subobjects (form, key figure). As report data is only valid for a limited time, it does not make sense to archive this data.

In order to avoid accessing data, which from a technical point of view is out-of-date, report data is deleted automatically if the drilldown detects an incompatible change to the report. This applies in particular when the report needs to be regenerated. The following actions lead to the generation of a report and hence trigger the deletion of repot data (except in the first case, when this only happens when the report is subsequently executed):

·       Manual generation from the test monitor (in Risk Management transaction JBWM)

·       Changes to the report, the form or a key figure used

·       Import of the report or of the form from another system or client. This still applies if an identical version is imported, and also if any reports and forms delivered by SAP are imported from client 000.

·       Changes to the data structure of the analysis structure, including reactivation of the data structure without any changes to the characteristics (this does not apply for the report types for what is known as structure reporting, which do not use the characteristics of the analysis structure directly).

·       Import of the analysis structure from another system (not in the case of structure reporting).

·       Any change to the structure (that corresponds to the respective report type) in the Data Dictionary, either brought about by direct modification or by an import. The name of this structure can be determined (field Line item file) in the test monitor (transaction JBWM) by entering the report type.

·       Change of SAP Core Release. The report is not necessarily regenerated when the add-on release is changed. However, the data structures can be changed by further development. After a release change, it is necessary to reactivate the analysis structure anyway. Therefore you will probably need to carry out a regeneration in this case too.

In some of the cases mentioned above, saved data can still be used even after the changes have been made (for example, in the case of manual generation or import of an unchanged report). In these cases, by using the test monitor, you can carry out generation without deleting report data and the data is still available afterwards.

On a very technical level, you can control or prevent the deletion of data in the ABAP Debugger. The variables C_DATA_ALL and C_DATA_DELTA have to be initial (blank) in function group KYP8, function module RKD_REORG_BY_FLAGS so that no data is deleted.

Some objects in the Risk Management application are used by the drilldown without being integrated with the management of saved report data. If changes are made to these objects, the report is not generated and no data is deleted. It can, however, lead to an incorrect display of saved results, in particular incorrect descriptions of portfolio hierarchy nodes. This applies for changes to the risk hierarchy and the portfolio hierarchy. You should delete any report data you no longer require.