BBP_USER_VENDOR_CREATE SAP Function module

BBP_USER_VENDOR_CREATE 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 BBP_USER_VENDOR_CREATE into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM BBP_USER_VENDOR_CREATE - BBP USER VENDOR CREATE

CALL FUNCTION 'BBP_USER_VENDOR_CREATE' "
  EXPORTING
    username =                  " bapibname-bapibname
    password =                  " bapipwd
    tpid =                      " smum_tpid
    logon_data =                " bapilogond
    address =                   " bapiaddr3
*   defaults =                  " bapidefaul
  TABLES
    return =                    " bapiret2
    .  "  BBP_USER_VENDOR_CREATE

ABAP code example for Function Module BBP_USER_VENDOR_CREATE

The ABAP code below is a full code listing to execute function module BBP_USER_VENDOR_CREATE 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:
it_return  
 
 TYPE STANDARD TABLE OF BAPIRET2,"TABLES PARAM
wa_return
 
 LIKE LINE OF it_return
.



DATA(ld_username) = some text here

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

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

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

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

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

"populate fields of struture and append to itab
append wa_return to it_return.
.

CALL FUNCTION 'BBP_USER_VENDOR_CREATE'
  EXPORTING
    username =                   ld_username
    password =                   ld_password
    tpid =                       ld_tpid
    logon_data =                 ld_logon_data
    address =                    ld_address
*   defaults =                   ld_defaults
  TABLES
    return =                     it_return
    .  "  BBP_USER_VENDOR_CREATE

IF SY-SUBRC EQ 0.
  "All OK
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_username
 
 TYPE BAPIBNAME-BAPIBNAME ,
it_return
 
 TYPE STANDARD TABLE OF BAPIRET2 ,
wa_return
 
 LIKE LINE OF it_return,
ld_password
 
 TYPE BAPIPWD ,
ld_tpid
 
 TYPE SMUM_TPID ,
ld_logon_data
 
 TYPE BAPILOGOND ,
ld_address
 
 TYPE BAPIADDR3 ,
ld_defaults
 
 TYPE BAPIDEFAUL .



ld_username = some text here 

"populate fields of struture and append to itab
append wa_return to it_return.
ld_password = 'Check type of data required'.
ld_tpid = 'Check type of data required'.
ld_logon_data = 'Check type of data required'.
ld_address = 'Check type of data required'.
ld_defaults = 'Check type of data required'.