FVD_CHARGE_API_GETLIST SAP Function module - API Get List

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

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

Pattern for FM FVD_CHARGE_API_GETLIST - FVD CHARGE API GETLIST

CALL FUNCTION 'FVD_CHARGE_API_GETLIST' "API Get List
  EXPORTING
    i_bukrs =                   " vdarl-bukrs   Company Code
    i_ranl =                    " vdarl-ranl    Contract Number
    i_rbo =                     " rbo           Business operation number (loans)
  IMPORTING
    e_tab_rcharge =             " trty_rcharge  Interface Structure and Control Data Charges
    e_tab_bapierr =             " bapierr_t     Table Types for Error Handling
    e_s_rcharge =               " rcharge       Interface Structure and Control Data Charges
  EXCEPTIONS
    FATAL_ERROR = 1             "
    .  "  FVD_CHARGE_API_GETLIST

ABAP code example for Function Module FVD_CHARGE_API_GETLIST

The ABAP code below is a full code listing to execute function module FVD_CHARGE_API_GETLIST 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_rcharge  
 
 TYPE TRTY_RCHARGE
,
ld_e_tab_bapierr  
 
 TYPE BAPIERR_T
,
ld_e_s_rcharge  
 
 TYPE RCHARGE
.

 

SELECT single BUKRS 
  FROM VDARL 
  INTO @DATA(ld_i_bukrs).

 

SELECT single RANL 
  FROM VDARL 
  INTO @DATA(ld_i_ranl).


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

CALL FUNCTION 'FVD_CHARGE_API_GETLIST'
  EXPORTING
    i_bukrs =                    ld_i_bukrs
    i_ranl =                     ld_i_ranl
    i_rbo =                      ld_i_rbo
  IMPORTING
    e_tab_rcharge =              ld_e_tab_rcharge
    e_tab_bapierr =              ld_e_tab_bapierr
    e_s_rcharge =                ld_e_s_rcharge
  EXCEPTIONS
    FATAL_ERROR =                1
    .  "  FVD_CHARGE_API_GETLIST

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_e_tab_rcharge
 
 TYPE TRTY_RCHARGE ,
ld_i_bukrs
 
 TYPE VDARL-BUKRS ,
ld_e_tab_bapierr
 
 TYPE BAPIERR_T ,
ld_i_ranl
 
 TYPE VDARL-RANL ,
ld_e_s_rcharge
 
 TYPE RCHARGE ,
ld_i_rbo
 
 TYPE RBO .



SELECT single BUKRS 
  FROM VDARL 
  INTO ld_i_bukrs.


SELECT single RANL 
  FROM VDARL 
  INTO ld_i_ranl.

ld_i_rbo = 'Check type of data required'.