FVD_API_OB_CT_GET_CO_VERS SAP Function module

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

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

Pattern for FM FVD_API_OB_CT_GET_CO_VERS - FVD API OB CT GET CO VERS

CALL FUNCTION 'FVD_API_OB_CT_GET_CO_VERS' "
  EXPORTING
    i_str_condtab_key =         " rficos_contab_key
    i_readtext = 'X'            " boole_d
    i_langu = SY-LANGU          " sylangu
*   i_log_handle =              " balloghndl
  IMPORTING
    e_str_cot =                 " vdcot
    e_str_cott =                " vdcott
    e_tab_cot_ver =             " trty_vdcot_ver
  EXCEPTIONS
    NOTICE_OCCURED = 1          "
    ERROR_OCCURED = 2           "
    .  "  FVD_API_OB_CT_GET_CO_VERS

ABAP code example for Function Module FVD_API_OB_CT_GET_CO_VERS

The ABAP code below is a full code listing to execute function module FVD_API_OB_CT_GET_CO_VERS 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_str_cot  
 
 TYPE VDCOT
,
ld_e_str_cott  
 
 TYPE VDCOTT
,
ld_e_tab_cot_ver  
 
 TYPE TRTY_VDCOT_VER
.


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

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

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

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

CALL FUNCTION 'FVD_API_OB_CT_GET_CO_VERS'
  EXPORTING
    i_str_condtab_key =          ld_i_str_condtab_key
    i_readtext =                 ld_i_readtext
    i_langu =                    ld_i_langu
*   i_log_handle =               ld_i_log_handle
  IMPORTING
    e_str_cot =                  ld_e_str_cot
    e_str_cott =                 ld_e_str_cott
    e_tab_cot_ver =              ld_e_tab_cot_ver
  EXCEPTIONS
    NOTICE_OCCURED =             1
    ERROR_OCCURED =              2
    .  "  FVD_API_OB_CT_GET_CO_VERS

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
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_str_cot
 
 TYPE VDCOT ,
ld_i_str_condtab_key
 
 TYPE RFICOS_CONTAB_KEY ,
ld_e_str_cott
 
 TYPE VDCOTT ,
ld_i_readtext
 
 TYPE BOOLE_D ,
ld_e_tab_cot_ver
 
 TYPE TRTY_VDCOT_VER ,
ld_i_langu
 
 TYPE SYLANGU ,
ld_i_log_handle
 
 TYPE BALLOGHNDL .


ld_i_str_condtab_key = 'Check type of data required'.
ld_i_readtext = 'Check type of data required'.
ld_i_langu = 'Check type of data required'.
ld_i_log_handle = 'Check type of data required'.