CUA role assignment issue LSMW/eCATT/CATT

[SAPSupport]

Hello,

I opened a case with SAP support previously about an issue when trying to assign roles to users massively via tools like LSMW or CATT.
You said in the case that the error comes from : "please have a look at note 1694357. Since SAP_BASIS 7.31 batch input (LSMW) and the classical CATT doesn't work for transaction SU01/SU10 any longer because of the used ALV grid control."

You suggested us to use the eCATT instead but I have the same issue. Which it might sound logical as it works on the same principle of TCD recording. Then I am not able to define role ACTGROUP as a variable.

Note 1 : as an alternative, I have tried to use LSMW with the idoc type USERCLONE07 but I cannot define the system (Partner number - EDPP1) as a variable. If any advice.

Note 2 : the SAP note talks about BAPI BAPI_USER_CHANGE. For role assignment within the CUA, could/should we use BAPI SUID_IDENTITY_SAVE_TO_DB with import parameter IT_USLA04_INSERT ?
I might create an eCATT or a LSWM from a BAPI/FM.

=> Could you please advice about this case ? As we will need to assign different roles to a lot of different users for a project. And we do not have specific client related program for this.


Thanks in advance,

------------------------------------------------------------------------------------------------------------------------------------------------
Learn more about the SAP Support user and program here.

[SAPSupport · Accepted solution]

Hello,

this has been asked already some times as far as I remember, short search returns for instance https://answers.sap.com/questions/209878/how-to-attach-the-role-by-using-lsmw-script-for-ba.html

First of all: eCatt is not supported for any productive use, as it is intended for testing only!!!!!!!!!!!

We do _not_ support any of such usage scenarios which you have mentioned.

Nevertheless: you need to mind these SAP notes:

1080977
1569029

Which explain the behavior on the roles tab of su01 and the solution for the recording.

But this shall be only a workaround, as you won't get any support from SAP side.

Regarding the BAPI_USER_CHANGE: you can't assign roles with that Bapi! This bapi-name was only mentioned as example in SAP note 1694357.
For assigning roles in a CUA central system the correct bapi is the BAPI_USER_LOCACTGROUPS_ASSIGN.

You mentioned the SUID_IDENTITY_SAVE_TO_DB: This is _no_ Bapi. This is normal function module , which is not released for customer usage!


Therefore I recommend, not to waste your time with LSMW or similar, but rather create a wrapper program which calls then the BAPI_USER_LOCACTGROUPS_ASSIGN to assign the roles in the CUA central system for the corresponding CUA child systems.
Take proper measures to manage the IDoc handling/resources for such mass changes.

Good luck,
Bernhard