SUSR_USER_EXTID_SET SAP Function module

SUSR_USER_EXTID_SET is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name SUSR_USER_EXTID_SET into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SUSO
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM SUSR_USER_EXTID_SET - SUSR USER EXTID SET

CALL FUNCTION 'SUSR_USER_EXTID_SET' "
  EXPORTING
    if_bname =                  " xubname       User name in user master record
*   if_replace =                " flag
    if_type =                   " extid_type    External ID Type
    it_extid =                  " extid_opt     Table with External IDs
  EXCEPTIONS
    USER_NOT_FOUND = 1          "               User Not Found
    EMPTY_EXTID = 2             "
    NO_AUTHORITY = 3            "               No Authorization
    LOCK_FAILURE = 4            "               Lock errors
    HASH_ERROR = 5              "
    HASH_CONFLICT = 6           "               Hash conflict:
    DB_ERROR = 7                "               Database Error
    RULEBASED_CERTMAPPING = 8   "
    .  "  SUSR_USER_EXTID_SET

ABAP code example for Function Module SUSR_USER_EXTID_SET

The ABAP code below is a full code listing to execute function module SUSR_USER_EXTID_SET including all data declarations. The code uses the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the original method of declaring data variables up front. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8).

DATA(ld_if_bname) = 'Check type of data required'.

DATA(ld_if_replace) = 'Check type of data required'.

DATA(ld_if_type) = 'Check type of data required'.

DATA(ld_it_extid) = 'Check type of data required'.
.

CALL FUNCTION 'SUSR_USER_EXTID_SET'
  EXPORTING
    if_bname =                   ld_if_bname
*   if_replace =                 ld_if_replace
    if_type =                    ld_if_type
    it_extid =                   ld_it_extid
  EXCEPTIONS
    USER_NOT_FOUND =             1
    EMPTY_EXTID =                2
    NO_AUTHORITY =               3
    LOCK_FAILURE =               4
    HASH_ERROR =                 5
    HASH_CONFLICT =              6
    DB_ERROR =                   7
    RULEBASED_CERTMAPPING =      8
    .  "  SUSR_USER_EXTID_SET

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 5. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 6. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 7. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 8. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_if_bname
 
 TYPE XUBNAME ,
ld_if_replace
 
 TYPE FLAG ,
ld_if_type
 
 TYPE EXTID_TYPE ,
ld_it_extid
 
 TYPE EXTID_OPT .


ld_if_bname = 'Check type of data required'.
ld_if_replace = 'Check type of data required'.
ld_if_type = 'Check type of data required'.
ld_it_extid = 'Check type of data required'.