FVDS_IMP_CMS_GET_CORR_DATA SAP Function module - Correspondence Data

FVDS_IMP_CMS_GET_CORR_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_CORR_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

Pattern for FM FVDS_IMP_CMS_GET_CORR_DATA - FVDS IMP CMS GET CORR DATA

CALL FUNCTION 'FVDS_IMP_CMS_GET_CORR_DATA' "Correspondence Data
* EXPORTING
*   i_bukrs =                   " bukrs         Company Code
*   i_ranl =                    " ranl          Contract Number
  IMPORTING
    e_tab_obj_hdr =             " cms_re_tab_obj_hdr_map_get  Details for Object Header
    e_tab_obj_addr =            " cms_re_tab_addr_get_mlt
    e_tab_obj_secb =            " cms_tab_main_lr_secb_map_get
    e_tab_obj_sec2 =            " cms_tab_main_lr_sec2_map_get
    e_tab_obj_prt =             " cms_re_tab_obj_prt_map_get
    e_tab_obj_main =            " cms_re_tab_obj_main_map_get
    .  "  FVDS_IMP_CMS_GET_CORR_DATA

ABAP code example for Function Module FVDS_IMP_CMS_GET_CORR_DATA

The ABAP code below is a full code listing to execute function module FVDS_IMP_CMS_GET_CORR_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_tab_obj_hdr  
 
 TYPE CMS_RE_TAB_OBJ_HDR_MAP_GET
,
ld_e_tab_obj_addr  
 
 TYPE CMS_RE_TAB_ADDR_GET_MLT
,
ld_e_tab_obj_secb  
 
 TYPE CMS_TAB_MAIN_LR_SECB_MAP_GET
,
ld_e_tab_obj_sec2  
 
 TYPE CMS_TAB_MAIN_LR_SEC2_MAP_GET
,
ld_e_tab_obj_prt  
 
 TYPE CMS_RE_TAB_OBJ_PRT_MAP_GET
,
ld_e_tab_obj_main  
 
 TYPE CMS_RE_TAB_OBJ_MAIN_MAP_GET
.


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

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

CALL FUNCTION 'FVDS_IMP_CMS_GET_CORR_DATA'
* EXPORTING
*   i_bukrs =                    ld_i_bukrs
*   i_ranl =                     ld_i_ranl
  IMPORTING
    e_tab_obj_hdr =              ld_e_tab_obj_hdr
    e_tab_obj_addr =             ld_e_tab_obj_addr
    e_tab_obj_secb =             ld_e_tab_obj_secb
    e_tab_obj_sec2 =             ld_e_tab_obj_sec2
    e_tab_obj_prt =              ld_e_tab_obj_prt
    e_tab_obj_main =             ld_e_tab_obj_main
    .  "  FVDS_IMP_CMS_GET_CORR_DATA

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_tab_obj_hdr
 
 TYPE CMS_RE_TAB_OBJ_HDR_MAP_GET ,
ld_i_bukrs
 
 TYPE BUKRS ,
ld_e_tab_obj_addr
 
 TYPE CMS_RE_TAB_ADDR_GET_MLT ,
ld_i_ranl
 
 TYPE RANL ,
ld_e_tab_obj_secb
 
 TYPE CMS_TAB_MAIN_LR_SECB_MAP_GET ,
ld_e_tab_obj_sec2
 
 TYPE CMS_TAB_MAIN_LR_SEC2_MAP_GET ,
ld_e_tab_obj_prt
 
 TYPE CMS_RE_TAB_OBJ_PRT_MAP_GET ,
ld_e_tab_obj_main
 
 TYPE CMS_RE_TAB_OBJ_MAIN_MAP_GET .


ld_i_bukrs = 'Check type of data required'.
ld_i_ranl = 'Check type of data required'.