T-code SUIM taking much more time for generating output for profie change.

[Former Member]

Hi All

We want to extract report for profile addition and deletion for Users in ECC 6. While executing the the t-code SUIM it is taking much more time (taking more than 20 hrs). This problem is coming after patch application

Please give the solution/Suggest to minimize the time taken in report generation.

Thanks-

Guru Prasad Dwivedi

[Former Member]

Hi,

Please check the inputs when u execute the t code i.e., u want a particular period of time or else whole changes what they done up to now.

One more thing after completion of patches did u run SGEN...?

Please execute the t-code SICK all are fine or not.

Regards,

Anil

[guilherme_deoliveira]

Hello Prasad,

The reason for the performance trouble is a new feature regarding the user change documents. Since note 874850 and 1015043 you will get a more complete overview about the changes regarding a user.

The disadvantage of that new feature is, that in some customer system usage scenario, the performance is very poor. That's the case, if the central change documents are intensivly used also by other applications and the tables CDPOS, CDHDR, ... contains a very big count of rows. Unfortunatly the user change documents can not be searched by the key columns of the central change docs. - so the bad response time can explained.

What now ... ?

There are some work arounds to get the change documents on faster way.

1st. - You can get the former report output and performance if you

would use the report RSUSR100 instead of the new RSUSR100N in

separate mode.

2nd. - If you want to use the new report RSUSR100N directly and only

want to get the information about the traditional topics

(content of USH* tables) you should only mark the search areas

on the tabstrip 'user attributes') to get a better performance.

- furthermore limit the date range, if possible

3rd. - You should regulary (monthly) archive the user relevant documents

for PFCG and IDENTITY from the central change documents.

As per our note 1079207 chapter 3 you can reload that archives

into more selective tables.

The selection for change documents will be rather faster over

reloaded archived documents than the documents in the

central change documents tables.

Best Regards,

Guilherme de Oliveira.

[Former Member]

Hi Guilherme,

We are using report RSUSR100 still response is too slow.

Thanks-

Guru Prasad Dwivedi