UMV_X_APPL_OBJ_USED_LIST SAP Function module

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

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

Pattern for FM UMV_X_APPL_OBJ_USED_LIST - UMV X APPL OBJ USED LIST

CALL FUNCTION 'UMV_X_APPL_OBJ_USED_LIST' "
  EXPORTING
*   i_orgunit =                 " umc_y_hr_orgunit
*   i_application =             " umc_y_application
*   i_appkey =                  " umc_y_appkey
    i_obj_type =                " umb_y_obj_type
    i_obj_key =                 " umb_y_obj_key
*   i_curper =                  " umb_y_curper
*   i_tarper =                  " umb_y_tarper
  IMPORTING
    et_vdtree =                 " umv_yt_vdtree
  EXCEPTIONS
    FAILED = 1                  "
    .  "  UMV_X_APPL_OBJ_USED_LIST

ABAP code example for Function Module UMV_X_APPL_OBJ_USED_LIST

The ABAP code below is a full code listing to execute function module UMV_X_APPL_OBJ_USED_LIST 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_et_vdtree  
 
 TYPE UMV_YT_VDTREE
.


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

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

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

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

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

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

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

CALL FUNCTION 'UMV_X_APPL_OBJ_USED_LIST'
  EXPORTING
*   i_orgunit =                  ld_i_orgunit
*   i_application =              ld_i_application
*   i_appkey =                   ld_i_appkey
    i_obj_type =                 ld_i_obj_type
    i_obj_key =                  ld_i_obj_key
*   i_curper =                   ld_i_curper
*   i_tarper =                   ld_i_tarper
  IMPORTING
    et_vdtree =                  ld_et_vdtree
  EXCEPTIONS
    FAILED =                     1
    .  "  UMV_X_APPL_OBJ_USED_LIST

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "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_et_vdtree
 
 TYPE UMV_YT_VDTREE ,
ld_i_orgunit
 
 TYPE UMC_Y_HR_ORGUNIT ,
ld_i_application
 
 TYPE UMC_Y_APPLICATION ,
ld_i_appkey
 
 TYPE UMC_Y_APPKEY ,
ld_i_obj_type
 
 TYPE UMB_Y_OBJ_TYPE ,
ld_i_obj_key
 
 TYPE UMB_Y_OBJ_KEY ,
ld_i_curper
 
 TYPE UMB_Y_CURPER ,
ld_i_tarper
 
 TYPE UMB_Y_TARPER .


ld_i_orgunit = 'Check type of data required'.
ld_i_application = 'Check type of data required'.
ld_i_appkey = 'Check type of data required'.
ld_i_obj_type = 'Check type of data required'.
ld_i_obj_key = 'Check type of data required'.
ld_i_curper = 'Check type of data required'.
ld_i_tarper = 'Check type of data required'.