Default User Parameters in SAP SOLUTION MANAGER 7.1

[Former Member]

Hi,

I want some default parameters automatically be assigned to new users when they are created instead of manually adding every time in su01 transaction code. Do you know how to configure this?

SAP SOLUTION MANAGER 7.1

SAP_BASIS

702

0012

SAPKB70212

SAP Basis Component

I try settings in SSM_CUST for user-exit Z_USERS_TRANSFER and SAP_USERS_TRANSFER, but it's don't work.

Thank you.

[Former Member]

Until 7.02 it is not working because of your code (you must post your code). As of 7.31 it will not work because SAP has replaced them with BADIs (those exits are simply ignored).

Cheers,

Julius

[Former Member]

Code function module runs in SAP EHP 1 for SAP Solution Manager 7.0 SAP_BASIS 701.

In SAP SOLUTION MANAGER 7.1 SAP_BASIS 702 function module is ignored. it can be seen if you set a breakpoint in the function module.

FUNCTION CREATE_USER_HR_INFO.

*"--------------------------------------------------------------------

*"*"Локальный интерфейс:

*"--------------------------------------------------------------------

DATA: su01_mode(5) type c.

field-symbols: <BNAME> like USR02-BNAME.

field-symbols: <ACCNT> like BAPILOGOND-ACCNT.

field-symbols: <CLASS> like USLOGOND-CLASS.

field-symbols: <FUNCTION> like ADDR3_DATA-FUNCTION.

field-symbols: <DEPARTMENT> like ADDR3_DATA-DEPARTMENT.

field-symbols: <su01_mode> like su01_mode.

DATA hr_rfc TYPE STANDARD TABLE OF ZSTR_HR_PERSON_INFO WITH HEADER LINE. " инф-ция о польз-лях, получаемая из HR по RFC

DATA : sys_msg(80) TYPE c,

         indx TYPE i.

DATA ADDRESS LIKE TABLE OF BAPIADDR3 WITH HEADER LINE.

DATA ADDRESSX LIKE TABLE OF BAPIADDR3X WITH HEADER LINE.

DATA DEFAULTS LIKE TABLE OF BAPIDEFAUL WITH HEADER LINE.

DATA DEFAULTSX LIKE TABLE OF BAPIDEFAX WITH HEADER LINE.

DATA LOGONDATA LIKE STANDARD TABLE OF BAPILOGOND WITH HEADER LINE.

DATA LOGONDATAX LIKE STANDARD TABLE OF BAPILOGONX WITH HEADER LINE.

DATA RETURN LIKE STANDARD TABLE OF BAPIRET2.

DATA res_lines TYPE i VALUE 0.

assign ('(SAPLSUU5)g_ok_start') to <su01_mode>.

if sy-subrc = 4.

   exit.

ENDIF.

*<su01_mode> will have the following values: create = "CREA", change = "CHAN", and delete = "DELE"

*  DATA mes TYPE string.

*  mes = sy-subrc.

*  CONCATENATE 'sy-subrc' mes into mes separated by SPACE .

*  MESSAGE mes TYPE 'I'.

if <su01_mode> = 'CREA'.

   assign ('(SAPLSUU5)USLOGOND-ACCNT') to <ACCNT>.

   assign ('(SAPLSUU5)USR02-BNAME') to <BNAME>.

   assign ('(SAPLSUU5)USLOGOND-CLASS') to <CLASS>.

   assign ('(SAPLSUU5)ADDR3_DATA-FUNCTION') to <FUNCTION>.

   assign ('(SAPLSUU5)ADDR3_DATA-DEPARTMENT') to <DEPARTMENT>.

   hr_rfc-PERNR = <ACCNT>.

   APPEND hr_rfc.

   CALL FUNCTION 'GET_HR_PERSON_INFO' DESTINATION 'PHRCLNT200_HR'

     TABLES

       PERSON_INFO       =  hr_rfc

     EXCEPTIONS

       SYSTEM_FAILURE = 1 MESSAGE sys_msg

       COMMUNICATION_FAILURE = 2 MESSAGE sys_msg

       .

DESCRIBE TABLE hr_rfc LINES res_lines.

*если по табельному номеру нашлись данные - заполняю ими структуры

if res_lines > 0.

   LOOP at hr_rfc.

     DEFAULTS-KOSTL = hr_rfc-PLANS.

     DEFAULTSX-KOSTL = 'X'.

     if hr_rfc-GESCH = '1'.

       ADDRESS-TITLE_P = 'Господин'.

     else.

       ADDRESS-TITLE_P = 'Госпожа'.

     ENDIF.

     SPLIT hr_rfc-ENAME AT space

                         INTO ADDRESS-LASTNAME

                              ADDRESS-FIRSTNAME

                              ADDRESS-MIDDLENAME.

     if <FUNCTION> = ''.

       ADDRESS-FUNCTION = hr_rfc-FUNCTION.

       ELSE.

         ADDRESS-FUNCTION = <FUNCTION>.

     ENDIF.

     if <DEPARTMENT> = ''.

       ADDRESS-DEPARTMENT = hr_rfc-STEXT.

       ELSE.

         ADDRESS-DEPARTMENT = <DEPARTMENT>.

     ENDIF.

     ADDRESSX-TITLE_P = 'X'.

     ADDRESSX-LASTNAME = 'X'.

     ADDRESSX-FIRSTNAME = 'X'.

     ADDRESSX-MIDDLENAME = 'X'.

     ADDRESSX-FUNCTION = 'X'.

     ADDRESSX-DEPARTMENT = 'X'.

   ENDLOOP.

endif.

   DEFAULTS-LANGU = 8.

   DEFAULTS-DCPFM = 'Y'.

   DEFAULTS-SPLD = 'LOCL'.

   DEFAULTS-SPDB = 'G'.

   DEFAULTS-SPDA = 'D'.

   APPEND DEFAULTS to DEFAULTS.

   DEFAULTSX-LANGU = 'X'.

   DEFAULTSX-DCPFM = 'X'.

   DEFAULTSX-SPLD = 'X'.

   DEFAULTSX-SPDB = 'X'.

   DEFAULTSX-SPDA = 'X'.

   APPEND DEFAULTSX.

   ADDRESS-NAMEFORMAT = '03'.

   ADDRESS-NAMCOUNTRY = 'UA'.

   APPEND ADDRESS to ADDRESS.

   ADDRESSX-NAMEFORMAT = 'X'.

   ADDRESSX-NAMCOUNTRY = 'X'.

   APPEND ADDRESSX.

   LOGONDATA-GLTGV = sy-datum.

   LOGONDATA-GLTGB = '99991231'.

   LOGONDATA-TZONE = 'EET'.

   if <CLASS> = ''.

     LOGONDATA-CLASS = 'END_USER'.

     ELSE.

       LOGONDATA-CLASS = <CLASS>.

   ENDIF.

   APPEND LOGONDATA.

   LOGONDATAX-GLTGV = 'X'.

   LOGONDATAX-GLTGB = 'X'.

   LOGONDATAX-CLASS = 'X'.

   LOGONDATAX-TZONE = 'X'.

   APPEND LOGONDATAX.

   CALL FUNCTION 'BAPI_USER_CHANGE'

     EXPORTING

       USERNAME = <BNAME>

       ADDRESS       =  ADDRESS

       ADDRESSX       =  ADDRESSX

       DEFAULTS     =  DEFAULTS

       DEFAULTSX     =  DEFAULTSX

       LOGONDATA   = LOGONDATA

       LOGONDATAX   = LOGONDATAX

     TABLES

       RETURN        = RETURN

       .

*  DATA mes TYPE string.

*  mes = sy-subrc.

*  CONCATENATE 'sy-subrc' mes into mes separated by SPACE .

*  MESSAGE mes TYPE 'I'.

ENDIF.

*ENDIF.

ENDFUNCTION.

[Former Member]

You are trying to change a user which does has not been created yet? Perhaps if you react to the message of the return then you will see that.

Anyway, the parameters are a tables parameter of the BAPI and you are not importing any data into the table. You are only populating defaults and logon and address data...

I think I am a bit closer now to understanding now why SAP deprecated these exits... 🙂 Have you seen the new BADIs? (Class SUID_IDENTITY). But you are ina fix on SOLMAN as you cannot go to higher than 7.02 at the moment...  😞

Cheers,

Julius

[pmuschick]

Just a question / hint - Why not use template users with predefined settings?

And, if you are willing to put in some development: Why not develop a report which distributes parameters in general even for users who are already created / or for parameters which have to be changed. This should be far more flexible for future changes.

[Former Member]

Templates are not suitable.

Function module, the text of which the post above, provides a report that fills all the required fields. This report should only be run when a user is created.