After you have implemented SAP Notes 1648187 and 1704771, you can use the logical indexing of selected change document characteristics to significantly improve the response time of report RSUSR100N. You can use the report SUIM_CTRL_CHG_IDX to optimize access by transferring key characteristics for selected change document characteristics of the object classes PFCG and IDENTITY to the table SUIM_CHG_IDX.
If you select the checkbox “Indexing central change documents”, the report indexes all newly-added change documents up to the target date specified on the selection screen.
When you first run the report, the indexing can lead to a very long run time. Since the change documents are indexed in 10 daily parts, if the report terminates, it ensures consistency by starting processing after the last successfully processed part.
In particular after system activities such as client copies or system copies, building a complete index using the checkbox “Index before reset” is essential.
If you want to use the option “Take Archive Data Into Account”, you should execute the report SUIM_CTRL_CHG_IDX with the option “Indexing reloaded change documents” after every reload process. With this option, the time interval of the existing reloaded documents is taken into account. Specifying the date has no effect for this processing.
Caution: For reasons of consistency, all index information is deleted when resetting reloaded change documents. The index must be completely rebuilt after activities of this type.
For running operation, regular indexing of the documents (on a weekly, monthly, or quarterly basis) is useful. To do this, schedule the report as a job in a cycle that makes sense for your landscape.
Note: For reasons of consistency, the indexing cannot be performed for the current date, that is, you can index up to the previous day at most.
Since the table SUIM_CHG_IDX is very large and can be reconstructed from the existing document data, it is useful to empty the table before complete client or system copies. To do this, start the report with an empty date field and the option “First Reset Index”.
If you are unhappy with the run time of the change document evaluation despite the indexing, perform the indexing more frequently. If the indexing is already done on a daily basis, and the report takes too much time when searching for the current date, you need to perform a fundamental analysis of the quantity structure of all central change documents.
In this case, you need to create a suitable archiving concept to generally reduce the quantity of central change document data. SAP Note 1257133 describes the analysis process for this topic.
A suitable partial optimization exclusively for the change document objects PFCG and IDENTITY is currently not technically implementable.
