SAP RM_PROT_CTY_FUTURE Function Module for message for FX Future









RM_PROT_CTY_FUTURE is a standard rm prot cty 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 cty future FM, simply by entering the name RM_PROT_CTY_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_CTY_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_CTY_FUTURE'"message for FX Future
EXPORTING
* I_LEVEL = 1 "Protokollebene
* I_TICK_VALUE = "
* I_TICK_SIZE = "
* I_THEORETICAL_PRICE = "Price of Unit- or Percentage-Quoted Security
* I_POS_SIZE = "Number of units for unit-quoted securities
* I_LINES = 1 "
I_COMM_ID = "Nominalbetrag
I_SEC_ID = "Security ID number
I_MATDATE = "Laufzeitende
I_SPOT_RATE = "Währung eingehende Seite
I_QUOTCURR = "Währung ausgehende Seite
I_PRESENT_VALUE = "NPV
* I_CTY_PRICE = "Price of Unit- or Percentage-Quoted Security
.



IMPORTING Parameters details for RM_PROT_CTY_FUTURE

I_LEVEL - Protokollebene

Data type: SPROT-LEVEL
Default: 1
Optional: Yes
Call by Reference: Yes

I_TICK_VALUE -

Data type: TI_BWTICK_COMMODITY
Optional: Yes
Call by Reference: Yes

I_TICK_SIZE -

Data type: TI_BETICK_COMMODITY
Optional: Yes
Call by Reference: Yes

I_THEORETICAL_PRICE - Price of Unit- or Percentage-Quoted Security

Data type: VVPKTKUR
Optional: Yes
Call by Reference: Yes

I_POS_SIZE - Number of units for unit-quoted securities

Data type: ASTUECK
Optional: Yes
Call by Reference: Yes

I_LINES -

Data type: I
Default: 1
Optional: No
Call by Reference: Yes

I_COMM_ID - Nominalbetrag

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

I_SEC_ID - Security ID number

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

I_MATDATE - Laufzeitende

Data type: VTVFGKO-DELFZ
Optional: No
Call by Reference: Yes

I_SPOT_RATE - Währung eingehende Seite

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

I_QUOTCURR - Währung ausgehende Seite

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

I_PRESENT_VALUE - NPV

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

I_CTY_PRICE - Price of Unit- or Percentage-Quoted Security

Data type: FTB_CTY_QUOTPRICE
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for RM_PROT_CTY_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_tick_value  TYPE TI_BWTICK_COMMODITY, "   
lv_i_tick_size  TYPE TI_BETICK_COMMODITY, "   
lv_i_theoretical_price  TYPE VVPKTKUR, "   
lv_i_pos_size  TYPE ASTUECK, "   
lv_i_lines  TYPE I, "   1
lv_i_comm_id  TYPE TRCO_COMM_ID, "   
lv_i_sec_id  TYPE VVRANLW, "   
lv_i_matdate  TYPE VTVFGKO-DELFZ, "   
lv_i_spot_rate  TYPE VVPKTKUR, "   
lv_i_quotcurr  TYPE TCR_CTY_QUOTCURR, "   
lv_i_present_value  TYPE F, "   
lv_i_cty_price  TYPE FTB_CTY_QUOTPRICE. "   

  CALL FUNCTION 'RM_PROT_CTY_FUTURE'  "message for FX Future
    EXPORTING
         I_LEVEL = lv_i_level
         I_TICK_VALUE = lv_i_tick_value
         I_TICK_SIZE = lv_i_tick_size
         I_THEORETICAL_PRICE = lv_i_theoretical_price
         I_POS_SIZE = lv_i_pos_size
         I_LINES = lv_i_lines
         I_COMM_ID = lv_i_comm_id
         I_SEC_ID = lv_i_sec_id
         I_MATDATE = lv_i_matdate
         I_SPOT_RATE = lv_i_spot_rate
         I_QUOTCURR = lv_i_quotcurr
         I_PRESENT_VALUE = lv_i_present_value
         I_CTY_PRICE = lv_i_cty_price
. " RM_PROT_CTY_FUTURE




ABAP code using 7.40 inline data declarations to call FM RM_PROT_CTY_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.
 
 
 
 
 
DATA(ld_i_lines) = 1.
 
 
 
"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!