SAP Function Modules

FVDS_IMP_CMS_GET_OBJECT_DATA SAP Function module - Object Data







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

Associated Function Group: FVDS_IMP_CMS
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM FVDS_IMP_CMS_GET_OBJECT_DATA - FVDS IMP CMS GET OBJECT DATA





CALL FUNCTION 'FVDS_IMP_CMS_GET_OBJECT_DATA' "Object Data
* EXPORTING
*   i_tab_vdhobj_key =          " trty_vdhobj_key  Table Type for Key Collateral Objects
*   i_robjnr =                  " robjnr        Collateral Object Number
*   i_tab_vdarl_key =           " trty_vdarl_key  Table Type for Key VDARL
*   i_sobjkat =                 " sobjkat       Object class with regard to the collat. sec. type
*   i_flg_complete_table =      " boole_d       Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
*   i_tab_vigbuch_key =         " trty_sgrundb  Table Type for Key Land Regstries
*   i_sobjart =                 " sobjart       Object Type
*   i_rklammer =                " vvrobjstm     Object master number
*   i_bukrs =                   " bukrs         Company Code
*   i_ranl =                    " ranl          Contract Number
*   i_tab_robjnr =              " trty_vdhobj_key  Table Type for Key Collateral Objects
*   i_flg_address =             " boole_d       Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
*   i_tab_rsicher =             " trty_rsicher  Table Type for the Collateral Key
*   i_sgrundb =                 " sgrundb       Land Register Number
*   i_xgbamt =                  " xgbamt        Land registry ID
*   i_xgbvon =                  " xgbvon        Land Register District
*   i_nbandnr =                 " nbandnr       Land register volume number
*   i_nblattnr =                " nblattnr      Land register page number
*   i_jeigenr = SPACE           " jeigenr       Individual right indicator
*   i_tab_vigba3_key =          " trty_sgrundb  Table Type for Land Register Key
*   i_tab_nrdarleh =            " trty_ndarleh  Table Type for Section 3 of Land Register
*   i_tab_vigbuch =             " trty_vigbuch_key  Land Registry Key Fields
  IMPORTING
    e_vdhobj =                  " vdhobj        Collateral Objects
    e_tab_vdhobj =              " trty_vdhobj   Table Type for Table VDHOBJ (Collateral Object)
    e_tab_vdarlobj =            " trty_vdarlobj  Table Type Objects   VDARLOBJ
    e_address =                 " szadr_addr1_complete
    e_tab_vdhgrpf =             " trty_vdhgrpf  Table Type for Table VDHGRPF
    e_vigbuch =                 " vigbuch       Land Register
    e_tab_vigbuch =             " trty_vigbuch  Table Type for Table VIGBUCH
    e_tab_vigbstd =             " trty_vigbstd  Table Type for Table VIGBSTD
    e_tab_vigba3 =              " trty_vigba3   Table Type for Table VIGBA3
  EXCEPTIONS
    CMS_NOT_ACTIV = 1           "
    DATA_NOT_FOUND = 2          "
    NO_VALID_PARAMETERS = 3     "
    .  "  FVDS_IMP_CMS_GET_OBJECT_DATA

ABAP code example for Function Module FVDS_IMP_CMS_GET_OBJECT_DATA





The ABAP code below is a full code listing to execute function module FVDS_IMP_CMS_GET_OBJECT_DATA 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_vdhobj  TYPE VDHOBJ ,
ld_e_tab_vdhobj  TYPE TRTY_VDHOBJ ,
ld_e_tab_vdarlobj  TYPE TRTY_VDARLOBJ ,
ld_e_address  TYPE SZADR_ADDR1_COMPLETE ,
ld_e_tab_vdhgrpf  TYPE TRTY_VDHGRPF ,
ld_e_vigbuch  TYPE VIGBUCH ,
ld_e_tab_vigbuch  TYPE TRTY_VIGBUCH ,
ld_e_tab_vigbstd  TYPE TRTY_VIGBSTD ,
ld_e_tab_vigba3  TYPE TRTY_VIGBA3 .

DATA(ld_i_tab_vdhobj_key) = 'Check type of data required'.
DATA(ld_i_robjnr) = 'Check type of data required'.
DATA(ld_i_tab_vdarl_key) = 'Check type of data required'.
DATA(ld_i_sobjkat) = 'Check type of data required'.
DATA(ld_i_flg_complete_table) = 'Check type of data required'.
DATA(ld_i_tab_vigbuch_key) = 'Check type of data required'.
DATA(ld_i_sobjart) = 'Check type of data required'.
DATA(ld_i_rklammer) = 'Check type of data required'.
DATA(ld_i_bukrs) = 'Check type of data required'.
DATA(ld_i_ranl) = 'Check type of data required'.
DATA(ld_i_tab_robjnr) = 'Check type of data required'.
DATA(ld_i_flg_address) = 'Check type of data required'.
DATA(ld_i_tab_rsicher) = 'Check type of data required'.
DATA(ld_i_sgrundb) = 'Check type of data required'.
DATA(ld_i_xgbamt) = 'Check type of data required'.
DATA(ld_i_xgbvon) = 'Check type of data required'.
DATA(ld_i_nbandnr) = 'Check type of data required'.
DATA(ld_i_nblattnr) = 'Check type of data required'.
DATA(ld_i_jeigenr) = 'Check type of data required'.
DATA(ld_i_tab_vigba3_key) = 'Check type of data required'.
DATA(ld_i_tab_nrdarleh) = 'Check type of data required'.
DATA(ld_i_tab_vigbuch) = 'Check type of data required'. . CALL FUNCTION 'FVDS_IMP_CMS_GET_OBJECT_DATA' * EXPORTING * i_tab_vdhobj_key = ld_i_tab_vdhobj_key * i_robjnr = ld_i_robjnr * i_tab_vdarl_key = ld_i_tab_vdarl_key * i_sobjkat = ld_i_sobjkat * i_flg_complete_table = ld_i_flg_complete_table * i_tab_vigbuch_key = ld_i_tab_vigbuch_key * i_sobjart = ld_i_sobjart * i_rklammer = ld_i_rklammer * i_bukrs = ld_i_bukrs * i_ranl = ld_i_ranl * i_tab_robjnr = ld_i_tab_robjnr * i_flg_address = ld_i_flg_address * i_tab_rsicher = ld_i_tab_rsicher * i_sgrundb = ld_i_sgrundb * i_xgbamt = ld_i_xgbamt * i_xgbvon = ld_i_xgbvon * i_nbandnr = ld_i_nbandnr * i_nblattnr = ld_i_nblattnr * i_jeigenr = ld_i_jeigenr * i_tab_vigba3_key = ld_i_tab_vigba3_key * i_tab_nrdarleh = ld_i_tab_nrdarleh * i_tab_vigbuch = ld_i_tab_vigbuch IMPORTING e_vdhobj = ld_e_vdhobj e_tab_vdhobj = ld_e_tab_vdhobj e_tab_vdarlobj = ld_e_tab_vdarlobj e_address = ld_e_address e_tab_vdhgrpf = ld_e_tab_vdhgrpf e_vigbuch = ld_e_vigbuch e_tab_vigbuch = ld_e_tab_vigbuch e_tab_vigbstd = ld_e_tab_vigbstd e_tab_vigba3 = ld_e_tab_vigba3 EXCEPTIONS CMS_NOT_ACTIV = 1 DATA_NOT_FOUND = 2 NO_VALID_PARAMETERS = 3 . " FVDS_IMP_CMS_GET_OBJECT_DATA
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 2. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 3. "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_e_vdhobj  TYPE VDHOBJ ,
ld_i_tab_vdhobj_key  TYPE TRTY_VDHOBJ_KEY ,
ld_e_tab_vdhobj  TYPE TRTY_VDHOBJ ,
ld_i_robjnr  TYPE ROBJNR ,
ld_e_tab_vdarlobj  TYPE TRTY_VDARLOBJ ,
ld_i_tab_vdarl_key  TYPE TRTY_VDARL_KEY ,
ld_e_address  TYPE SZADR_ADDR1_COMPLETE ,
ld_i_sobjkat  TYPE SOBJKAT ,
ld_e_tab_vdhgrpf  TYPE TRTY_VDHGRPF ,
ld_i_flg_complete_table  TYPE BOOLE_D ,
ld_e_vigbuch  TYPE VIGBUCH ,
ld_i_tab_vigbuch_key  TYPE TRTY_SGRUNDB ,
ld_e_tab_vigbuch  TYPE TRTY_VIGBUCH ,
ld_i_sobjart  TYPE SOBJART ,
ld_i_rklammer  TYPE VVROBJSTM ,
ld_e_tab_vigbstd  TYPE TRTY_VIGBSTD ,
ld_i_bukrs  TYPE BUKRS ,
ld_e_tab_vigba3  TYPE TRTY_VIGBA3 ,
ld_i_ranl  TYPE RANL ,
ld_i_tab_robjnr  TYPE TRTY_VDHOBJ_KEY ,
ld_i_flg_address  TYPE BOOLE_D ,
ld_i_tab_rsicher  TYPE TRTY_RSICHER ,
ld_i_sgrundb  TYPE SGRUNDB ,
ld_i_xgbamt  TYPE XGBAMT ,
ld_i_xgbvon  TYPE XGBVON ,
ld_i_nbandnr  TYPE NBANDNR ,
ld_i_nblattnr  TYPE NBLATTNR ,
ld_i_jeigenr  TYPE JEIGENR ,
ld_i_tab_vigba3_key  TYPE TRTY_SGRUNDB ,
ld_i_tab_nrdarleh  TYPE TRTY_NDARLEH ,
ld_i_tab_vigbuch  TYPE TRTY_VIGBUCH_KEY .

ld_i_tab_vdhobj_key = 'Check type of data required'.
ld_i_robjnr = 'Check type of data required'.
ld_i_tab_vdarl_key = 'Check type of data required'.
ld_i_sobjkat = 'Check type of data required'.
ld_i_flg_complete_table = 'Check type of data required'.
ld_i_tab_vigbuch_key = 'Check type of data required'.
ld_i_sobjart = 'Check type of data required'.
ld_i_rklammer = 'Check type of data required'.
ld_i_bukrs = 'Check type of data required'.
ld_i_ranl = 'Check type of data required'.
ld_i_tab_robjnr = 'Check type of data required'.
ld_i_flg_address = 'Check type of data required'.
ld_i_tab_rsicher = 'Check type of data required'.
ld_i_sgrundb = 'Check type of data required'.
ld_i_xgbamt = 'Check type of data required'.
ld_i_xgbvon = 'Check type of data required'.
ld_i_nbandnr = 'Check type of data required'.
ld_i_nblattnr = 'Check type of data required'.
ld_i_jeigenr = 'Check type of data required'.
ld_i_tab_vigba3_key = 'Check type of data required'.
ld_i_tab_nrdarleh = 'Check type of data required'.
ld_i_tab_vigbuch = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name FVDS_IMP_CMS_GET_OBJECT_DATA or its description.