Modify SNC Name

[Former Member]

Hi All,

I was wondering, is there a Function Module or BAPI to change the SNC name of a user?

Many Thanks,

Colm

[former_member194669]

How about this?

  CALL FUNCTION 'BAPI_USER_CHANGE'
         EXPORTING
            username = v_bname       "User 
           snc           = wa_snc   "<<<<
           sncx        = wa_sncx  " <<<<
          TABLES
           return       = t_return.

a®

[Former Member]

Hi Ars,

Thanks for the quick reply, you're solution nearly worked perfectly but not exactly.

Bear with me if you will:

Goto SU01

Enter a Username

Display

Click SNC tab

In the section:

"Other R/3 users with SNC names of same Value" you're code correctly changed the value for the client ran my program in. However it did not change it for the other clients.

So I ran the program in every client we have and in the section "Other R/3 users with SNC names of same Value" the values were changed for every client but if I look back at the "SNC data" section the "SNC name" still shows the old value.

Thanks for your help, any more would be greatly appreciated.

Colm

[Former Member]

Hi Colm,

You might want to try using FMs from the function group SNCB

E.g. SNC_USER_CHANGE since these functions are purely for SNC modification.

Regards,

Aditya

[Former Member]

Aditya,

Thank you for your suggestion. When I just used the SNC_USER_CHANGE there was no affect to the SNC name. However if I call BAPI_USER_CHANGE and then call SNC_USER_CHANGE the user name is changed in both "SNC data" and "Other R/3 users with SNC names of same value".

This is great, however I noticed one further place!

If I open my SAP Logon Pad and Double Click on DEV I am brought to the SAP SSO Logon Screen where I can select the client that I wish to logon to. On this screen there is a section called "SNC name" and in that section there is a value called "R/3 user" and that user name still contains the old SNC name.

Does anyone know where I can change this value!?

Many Thanks Again,

Colm

[Former Member]

Turns out that was the value that was being pulled in from our Active Directory so everything is working correctly. Thanks again for all the help, realistically both of you solved the problem but I'll give the full points to the one who got in there first!