CBIF_LIB01_SET_PARAMETERS SAP Function module

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

Associated Function Group: CBIF_LIB01
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM CBIF_LIB01_SET_PARAMETERS - CBIF LIB01 SET PARAMETERS

CALL FUNCTION 'CBIF_LIB01_SET_PARAMETERS' "
  EXPORTING
    i_pid_1 =                   " char20
    i_field_1 =                 " char200
*   i_pid_2 =                   " char20
*   i_field_2 =                 " char200
*   i_pid_3 =                   " char20
*   i_field_3 =                 " char200
*   i_pid_4 =                   " char20
*   i_field_4 =                 " char200
    .  "  CBIF_LIB01_SET_PARAMETERS

ABAP code example for Function Module CBIF_LIB01_SET_PARAMETERS

The ABAP code below is a full code listing to execute function module CBIF_LIB01_SET_PARAMETERS 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_i_pid_1) = 'Check type of data required'.

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

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

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

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

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

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

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

CALL FUNCTION 'CBIF_LIB01_SET_PARAMETERS'
  EXPORTING
    i_pid_1 =                    ld_i_pid_1
    i_field_1 =                  ld_i_field_1
*   i_pid_2 =                    ld_i_pid_2
*   i_field_2 =                  ld_i_field_2
*   i_pid_3 =                    ld_i_pid_3
*   i_field_3 =                  ld_i_field_3
*   i_pid_4 =                    ld_i_pid_4
*   i_field_4 =                  ld_i_field_4
    .  "  CBIF_LIB01_SET_PARAMETERS

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_pid_1
 
 TYPE CHAR20 ,
ld_i_field_1
 
 TYPE CHAR200 ,
ld_i_pid_2
 
 TYPE CHAR20 ,
ld_i_field_2
 
 TYPE CHAR200 ,
ld_i_pid_3
 
 TYPE CHAR20 ,
ld_i_field_3
 
 TYPE CHAR200 ,
ld_i_pid_4
 
 TYPE CHAR20 ,
ld_i_field_4
 
 TYPE CHAR200 .


ld_i_pid_1 = 'Check type of data required'.
ld_i_field_1 = 'Check type of data required'.
ld_i_pid_2 = 'Check type of data required'.
ld_i_field_2 = 'Check type of data required'.
ld_i_pid_3 = 'Check type of data required'.
ld_i_field_3 = 'Check type of data required'.
ld_i_pid_4 = 'Check type of data required'.
ld_i_field_4 = 'Check type of data required'.