SAP RM_PROT_FX_FUTURE Function Module for message for FX Future









RM_PROT_FX_FUTURE is a standard rm prot fx future SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for message for FX Future 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 prot fx future FM, simply by entering the name RM_PROT_FX_FUTURE into the relevant SAP transaction such as SE37 or SE38.

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



Function RM_PROT_FX_FUTURE 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_PROT_FX_FUTURE'"message for FX Future
EXPORTING
* I_LEVEL = 1 "Protokollebene
I_FOREIGN_RATE = "
I_SPOT_RATE = "Umrechnungskurs
I_FWD_RATE = "Geldkurs im Marktrisiko (preisnotiert)
I_PRESENT_VALUE = "NPV
* I_LINES = 1 "
I_PRINCIPAL = "Nominalbetrag
I_INC_CURR = "Währung eingehende Seite
I_OUT_CURR = "Währung ausgehende Seite
I_TXN_CURR = "Währung Nominalbetrag
I_DEALDATE = "Laufzeitbeginn
I_MATDATE = "Laufzeitende
I_DOMESTIC_RATE = "
.



IMPORTING Parameters details for RM_PROT_FX_FUTURE

I_LEVEL - Protokollebene

Data type: SPROT-LEVEL
Default: 1
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_FOREIGN_RATE -

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

I_SPOT_RATE - Umrechnungskurs

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

I_FWD_RATE - Geldkurs im Marktrisiko (preisnotiert)

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

I_PRESENT_VALUE - NPV

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

I_LINES -

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

I_PRINCIPAL - Nominalbetrag

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

I_INC_CURR - Währung eingehende Seite

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

I_OUT_CURR - Währung ausgehende Seite

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

I_TXN_CURR - Währung Nominalbetrag

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

I_DEALDATE - Laufzeitbeginn

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

I_MATDATE - Laufzeitende

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

I_DOMESTIC_RATE -

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

Copy and paste ABAP code example for RM_PROT_FX_FUTURE 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.

DATA:
lv_i_level  TYPE SPROT-LEVEL, "   1
lv_i_foreign_rate  TYPE F, "   
lv_i_spot_rate  TYPE TCURR-UKURS, "   
lv_i_fwd_rate  TYPE KALKU-KURSGE, "   
lv_i_present_value  TYPE F, "   
lv_i_lines  TYPE I, "   1
lv_i_principal  TYPE VTVFGKO-BNOMINAL, "   
lv_i_inc_curr  TYPE VTVFGKO-WGSCHFT2, "   
lv_i_out_curr  TYPE VTVFGKO-WGSCHFT1, "   
lv_i_txn_curr  TYPE VTVFGKO08-SNOMWHR, "   
lv_i_dealdate  TYPE VTVFGKO-DBLFZ, "   
lv_i_matdate  TYPE VTVFGKO-DELFZ, "   
lv_i_domestic_rate  TYPE F. "   

  CALL FUNCTION 'RM_PROT_FX_FUTURE'  "message for FX Future
    EXPORTING
         I_LEVEL = lv_i_level
         I_FOREIGN_RATE = lv_i_foreign_rate
         I_SPOT_RATE = lv_i_spot_rate
         I_FWD_RATE = lv_i_fwd_rate
         I_PRESENT_VALUE = lv_i_present_value
         I_LINES = lv_i_lines
         I_PRINCIPAL = lv_i_principal
         I_INC_CURR = lv_i_inc_curr
         I_OUT_CURR = lv_i_out_curr
         I_TXN_CURR = lv_i_txn_curr
         I_DEALDATE = lv_i_dealdate
         I_MATDATE = lv_i_matdate
         I_DOMESTIC_RATE = lv_i_domestic_rate
. " RM_PROT_FX_FUTURE




ABAP code using 7.40 inline data declarations to call FM RM_PROT_FX_FUTURE

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.

"SELECT single LEVEL FROM SPROT INTO @DATA(ld_i_level).
DATA(ld_i_level) = 1.
 
 
"SELECT single UKURS FROM TCURR INTO @DATA(ld_i_spot_rate).
 
"SELECT single KURSGE FROM KALKU INTO @DATA(ld_i_fwd_rate).
 
 
DATA(ld_i_lines) = 1.
 
"SELECT single BNOMINAL FROM VTVFGKO INTO @DATA(ld_i_principal).
 
"SELECT single WGSCHFT2 FROM VTVFGKO INTO @DATA(ld_i_inc_curr).
 
"SELECT single WGSCHFT1 FROM VTVFGKO INTO @DATA(ld_i_out_curr).
 
"SELECT single SNOMWHR FROM VTVFGKO08 INTO @DATA(ld_i_txn_curr).
 
"SELECT single DBLFZ FROM VTVFGKO INTO @DATA(ld_i_dealdate).
 
"SELECT single DELFZ FROM VTVFGKO INTO @DATA(ld_i_matdate).
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!