UPC_VARIABLE_REQUEST SAP Function module - Popup for entering the restriction of the variable

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

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

Pattern for FM UPC_VARIABLE_REQUEST - UPC VARIABLE REQUEST

CALL FUNCTION 'UPC_VARIABLE_REQUEST' "Popup for entering the restriction of the variable
  EXPORTING
    i_area =                    " upc_y_area    Planning Area
    i_variable =                " upc_y_variable  Variable
*   i_always =                  " boole_d       Also in the case when the restriction is not missing
*   i_sel_check = 'X'           " boole_d       Check selection for validity
  IMPORTING
    e_canceled =                " char1         Single-Character Flag
    .  "  UPC_VARIABLE_REQUEST

ABAP code example for Function Module UPC_VARIABLE_REQUEST

The ABAP code below is a full code listing to execute function module UPC_VARIABLE_REQUEST 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_e_canceled  
 
 TYPE CHAR1
.


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

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

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

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

CALL FUNCTION 'UPC_VARIABLE_REQUEST'
  EXPORTING
    i_area =                     ld_i_area
    i_variable =                 ld_i_variable
*   i_always =                   ld_i_always
*   i_sel_check =                ld_i_sel_check
  IMPORTING
    e_canceled =                 ld_e_canceled
    .  "  UPC_VARIABLE_REQUEST

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_e_canceled
 
 TYPE CHAR1 ,
ld_i_area
 
 TYPE UPC_Y_AREA ,
ld_i_variable
 
 TYPE UPC_Y_VARIABLE ,
ld_i_always
 
 TYPE BOOLE_D ,
ld_i_sel_check
 
 TYPE BOOLE_D .


ld_i_area = 'Check type of data required'.
ld_i_variable = 'Check type of data required'.
ld_i_always = 'Check type of data required'.
ld_i_sel_check = 'Check type of data required'.