RM_INITIALIZE_BUFFER SAP Function module - Initialisierung des Marktdatenpuffers

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

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

Pattern for FM RM_INITIALIZE_BUFFER - RM INITIALIZE BUFFER

CALL FUNCTION 'RM_INITIALIZE_BUFFER' "Initialisierung des Marktdatenpuffers
* EXPORTING
*   aktdatum = SY-DATUM         " vtv_para-tvaktdat  Current Date is Saved in Buffer
*   gueldatum =                 " d
*   auswt = '01'                " atvmo-auswt
*   i_atsyc =                   " atsyc
*   mittel =                    " c
*   i_force_init = ABAP_TRUE    " abap_bool     ABAP_FALSE=Only if necessary
* TABLES
*   e_bapierr =                 " bapierr
  EXCEPTIONS
    DEFAULT_YIELDCURVE_MISSING = 1  "           Default Curve Missing
    .  "  RM_INITIALIZE_BUFFER

ABAP code example for Function Module RM_INITIALIZE_BUFFER

The ABAP code below is a full code listing to execute function module RM_INITIALIZE_BUFFER 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:
it_e_bapierr  
 
 TYPE STANDARD TABLE OF BAPIERR,"TABLES PARAM
wa_e_bapierr
 
 LIKE LINE OF it_e_bapierr
.



DATA(ld_aktdatum) = 20210129

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

SELECT single AUSWT 
  FROM ATVMO 
  INTO @DATA(ld_auswt).


DATA(ld_i_atsyc) = '20210129'.

DATA(ld_mittel) = '20210129'.

DATA(ld_i_force_init) = '20210129'.
 

"populate fields of struture and append to itab
append wa_e_bapierr to it_e_bapierr.
.

CALL FUNCTION 'RM_INITIALIZE_BUFFER'
* EXPORTING
*   aktdatum =                   ld_aktdatum
*   gueldatum =                  ld_gueldatum
*   auswt =                      ld_auswt
*   i_atsyc =                    ld_i_atsyc
*   mittel =                     ld_mittel
*   i_force_init =               ld_i_force_init
* TABLES
*   e_bapierr =                  it_e_bapierr
  EXCEPTIONS
    DEFAULT_YIELDCURVE_MISSING =    1
    .  "  RM_INITIALIZE_BUFFER

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_aktdatum
 
 TYPE VTV_PARA-TVAKTDAT ,
it_e_bapierr
 
 TYPE STANDARD TABLE OF BAPIERR ,
wa_e_bapierr
 
 LIKE LINE OF it_e_bapierr,
ld_gueldatum
 
 TYPE D ,
ld_auswt
 
 TYPE ATVMO-AUSWT ,
ld_i_atsyc
 
 TYPE ATSYC ,
ld_mittel
 
 TYPE C ,
ld_i_force_init
 
 TYPE ABAP_BOOL .



ld_aktdatum = 20210129 

"populate fields of struture and append to itab
append wa_e_bapierr to it_e_bapierr.
ld_gueldatum = '20210129'.

SELECT single AUSWT 
  FROM ATVMO 
  INTO ld_auswt.

ld_i_atsyc = '20210129'.
ld_mittel = '20210129'.
ld_i_force_init = '20210129'.