RM_BDS_SAVE_SIMULATION_10 SAP Function module - BDS: Simulierte Barwertänderungen und VaR sichern

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

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

Pattern for FM RM_BDS_SAVE_SIMULATION_10 - RM BDS SAVE SIMULATION 10

CALL FUNCTION 'RM_BDS_SAVE_SIMULATION_10' "BDS: Simulierte Barwertänderungen und VaR sichern
  EXPORTING
    i_laufnr =                  " jbrbdslfn-laufnr  RDB: Laufnummer
    i_para =                    " jbrhsspari    Parameter für Auswertungen (Include)
    i_xguv =                    " c
    i_xvar =                    " c
    it_bar =                    " tvrm0_barw_tab
    it_pos =                    " tvrm0_deltagamma_tab
    it_guv =                    " tvrm0_guv10_tab
  EXCEPTIONS
    SAVE_ERROR = 1              "
    VAR_ERROR = 2               "
    NO_DATA = 3                 "
    .  "  RM_BDS_SAVE_SIMULATION_10

ABAP code example for Function Module RM_BDS_SAVE_SIMULATION_10

The ABAP code below is a full code listing to execute function module RM_BDS_SAVE_SIMULATION_10 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).

 

SELECT single LAUFNR 
  FROM JBRBDSLFN 
  INTO @DATA(ld_i_laufnr).


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

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

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

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

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

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

CALL FUNCTION 'RM_BDS_SAVE_SIMULATION_10'
  EXPORTING
    i_laufnr =                   ld_i_laufnr
    i_para =                     ld_i_para
    i_xguv =                     ld_i_xguv
    i_xvar =                     ld_i_xvar
    it_bar =                     ld_it_bar
    it_pos =                     ld_it_pos
    it_guv =                     ld_it_guv
  EXCEPTIONS
    SAVE_ERROR =                 1
    VAR_ERROR =                  2
    NO_DATA =                    3
    .  "  RM_BDS_SAVE_SIMULATION_10

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_i_laufnr
 
 TYPE JBRBDSLFN-LAUFNR ,
ld_i_para
 
 TYPE JBRHSSPARI ,
ld_i_xguv
 
 TYPE C ,
ld_i_xvar
 
 TYPE C ,
ld_it_bar
 
 TYPE TVRM0_BARW_TAB ,
ld_it_pos
 
 TYPE TVRM0_DELTAGAMMA_TAB ,
ld_it_guv
 
 TYPE TVRM0_GUV10_TAB .



SELECT single LAUFNR 
  FROM JBRBDSLFN 
  INTO ld_i_laufnr.

ld_i_para = 'Check type of data required'.
ld_i_xguv = 'Check type of data required'.
ld_i_xvar = 'Check type of data required'.
ld_it_bar = 'Check type of data required'.
ld_it_pos = 'Check type of data required'.
ld_it_guv = 'Check type of data required'.