BBP_READ_USER_SETTINGS SAP Function module

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

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

Pattern for FM BBP_READ_USER_SETTINGS - BBP READ USER SETTINGS

CALL FUNCTION 'BBP_READ_USER_SETTINGS' "
  EXPORTING
    i_action =                  " bbp_dus-action
*   i_uname =                   " bbp_dus-uname
*   i_db =                      " xfeld
*   i_like =                    " xfeld
  TABLES
    i_bbp_dus =                 " bbp_duscom
    .  "  BBP_READ_USER_SETTINGS

ABAP code example for Function Module BBP_READ_USER_SETTINGS

The ABAP code below is a full code listing to execute function module BBP_READ_USER_SETTINGS 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_i_bbp_dus  
 
 TYPE STANDARD TABLE OF BBP_DUSCOM,"TABLES PARAM
wa_i_bbp_dus
 
 LIKE LINE OF it_i_bbp_dus
.

 

SELECT single ACTION 
  FROM BBP_DUS 
  INTO @DATA(ld_i_action).

 

SELECT single UNAME 
  FROM BBP_DUS 
  INTO @DATA(ld_i_uname).


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

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

"populate fields of struture and append to itab
append wa_i_bbp_dus to it_i_bbp_dus.
.

CALL FUNCTION 'BBP_READ_USER_SETTINGS'
  EXPORTING
    i_action =                   ld_i_action
*   i_uname =                    ld_i_uname
*   i_db =                       ld_i_db
*   i_like =                     ld_i_like
  TABLES
    i_bbp_dus =                  it_i_bbp_dus
    .  "  BBP_READ_USER_SETTINGS

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_i_action
 
 TYPE BBP_DUS-ACTION ,
it_i_bbp_dus
 
 TYPE STANDARD TABLE OF BBP_DUSCOM ,
wa_i_bbp_dus
 
 LIKE LINE OF it_i_bbp_dus,
ld_i_uname
 
 TYPE BBP_DUS-UNAME ,
ld_i_db
 
 TYPE XFELD ,
ld_i_like
 
 TYPE XFELD .



SELECT single ACTION 
  FROM BBP_DUS 
  INTO ld_i_action.
 

"populate fields of struture and append to itab
append wa_i_bbp_dus to it_i_bbp_dus.

SELECT single UNAME 
  FROM BBP_DUS 
  INTO ld_i_uname.

ld_i_db = 'Check type of data required'.
ld_i_like = 'Check type of data required'.