SU01 parameters

[Former Member]

Can we export SU01 parameters from one system and import to another system from table level. Like we do RFC export and import as part of refresh.

Both systems have same user master and same number of users.

I am just wondering if exporting and importing the parameters table(USR05) would do the job or are there any integration dependencies with other tables that i need to address. Any thoughts are appreciated.

Regards

Kalyan

[Laszlo_B]

Hello Kalyan,

I know my answer won't solve this question but if it is regular that user data needs to be exported to other systems, you might want to try CUA (Central User Administration).

When CUA is used, the user data needs to be set only in one system (the "central system"), and it will be easily exported to the "child systems". I am not completely sure whether this is valid for SU01 parameters (table USR05) too, but if there are sandbox/test systems available to try the CUA solution, it worth a shot.

Best regards,

Laszlo

[former_member200428]

Hi Kalyan

SU01 parameters are itself included in UMR(User Master Record) for a particular user, We can export the parameters by using the Client Export option available in SAP.

Execute the Tcode SCC8-select the profile SAP_USER and transport it, so that the entire list of users present in a particular system gets transported.

Hope this helps your query.

[Former Member]

correct me if I am wrong, as I get it, your question is about modifying the USR05 directly without going through application, correct?

Options:

Help from ABAP developer with simple BDC program on SU10 will suffice for your requirements.

Benefit:

1. standard way, should be safe even with changing of release or support package.

2. trail looks good, not modifying the SAP tables directly.

Disadvantage:

needs ABAP knowledge and a bit overhead in processing.

ST05 trace when doing SU01 to get what you want to know, then proceed with your current idea:

Benefit:

loading is faster.

Disadvantage:

1. not safe, current conclusion may not applied for the next release or SP( change of code ).

2. directly modifying SAP table without going through application level or SAP Notes instruction is generally a bad idea. not sure about the audit opinion if this get tracked.

IMHO, the first is better, less trouble in the future

GUI Scripting is also a possible option if it is enabled in your system.