SAP RM_DEVISEN_OPTION_BARWERT Function Module for NPV of FX Options: Methods 100, 101, 300, 310

Search SAP Function Modules

RM_DEVISEN_OPTION_BARWERT is a standard rm devisen option barwert SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NPV of FX Options: Methods 100, 101, 300, 310 processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.

See here to view full function module documentation and code listing for rm devisen option barwert FM, simply by entering the name RM_DEVISEN_OPTION_BARWERT into the relevant SAP transaction such as SE37 or SE38.

Function Group: RMDB
Program Name: SAPLRMDB
Main Program: SAPLRMDB
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RM_DEVISEN_OPTION_BARWERT pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.

CALL FUNCTION 'RM_DEVISEN_OPTION_BARWERT'"NPV of FX Options: Methods 100, 101, 300, 310
  EXPORTING
*  I_AKT_DATUM = SY-DATUM "Current Date
   I_RES_CURR =  "Display Currency
   I_GID_ROOT =  "
   I_METHODEN =  "Header Row of Method Table

 IMPORTING
   E_RESULT =  "Total NPV of Financial Transaction
   E_RESULT_TAB =  "NPV of Individual Cash Flows
   E_RESULT_OPT_TAB =  "

CHANGING
   C_TV1_FGET_TAB =  "

EXCEPTIONS
   NO_CALC = 1    MARKET_DATA_SPOT = 2    INVALID_DATA = 3 

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLRMDBC_001 RM: Enhancement in FO Derivation from BCA
EXIT_SAPLRMDBC_002 RM: Customer Exit Before Call of Characteristics Derivation
EXIT_SAPLRMDBC_003 RM: Customer Exit after Call of Characteristics Derivation

IMPORTING Parameters details for RM_DEVISEN_OPTION_BARWERT

I_AKT_DATUM - Current Date

Data type: SY-DATUM
Default: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_RES_CURR - Display Currency

Data type: VTVFGKO-SBWHR
Optional: No
Call by Reference: No ( called with pass by value option)

I_GID_ROOT -

Data type: TV1_KNOT_ID
Optional: No
Call by Reference: No ( called with pass by value option)

I_METHODEN - Header Row of Method Table

Data type: TVM_METH_TYP
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for RM_DEVISEN_OPTION_BARWERT

E_RESULT - Total NPV of Financial Transaction

Data type: TVM0_RESULT
Optional: No
Call by Reference: No ( called with pass by value option)

E_RESULT_TAB - NPV of Individual Cash Flows

Data type: TVM0_RESULT_TAB
Optional: No
Call by Reference: No ( called with pass by value option)

E_RESULT_OPT_TAB -

Data type: TVM0_RES_OPT_TAB
Optional: No
Call by Reference: No ( called with pass by value option)

CHANGING Parameters details for RM_DEVISEN_OPTION_BARWERT

C_TV1_FGET_TAB -

Data type: TV1_FGET_TAB
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NO_CALC - No NPV was calculated

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

MARKET_DATA_SPOT -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

INVALID_DATA -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for RM_DEVISEN_OPTION_BARWERT Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

ABAP code using 7.40 inline data declarations to call FM RM_DEVISEN_OPTION_BARWERT

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

Search for further information about these or an SAP related objects