SAP RM_MM_UTIL_GET_CFUT_MP Function Module for Utility - Get Market Price for Commodity Future









RM_MM_UTIL_GET_CFUT_MP is a standard rm mm util get cfut mp SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Utility - Get Market Price for Commodity 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 mm util get cfut mp FM, simply by entering the name RM_MM_UTIL_GET_CFUT_MP into the relevant SAP transaction such as SE37 or SE38.

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



Function RM_MM_UTIL_GET_CFUT_MP 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_MM_UTIL_GET_CFUT_MP'"Utility - Get Market Price for Commodity Future
EXPORTING
IV_DATE = "
IS_FGET = "
IS_METHODE = "
IS_SHIFT_RULE = "Rule Structure for Simulation Analyses

IMPORTING
EV_MARKET_PRICE = "

EXCEPTIONS
NO_PV_CALCULATED = 1 MARKET_DATA_SPOT = 2 INVALID_DATA = 3 NO_VARIABLE_RATE = 4
.



IMPORTING Parameters details for RM_MM_UTIL_GET_CFUT_MP

IV_DATE -

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

IS_FGET -

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

IS_METHODE -

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

IS_SHIFT_RULE - Rule Structure for Simulation Analyses

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

EXPORTING Parameters details for RM_MM_UTIL_GET_CFUT_MP

EV_MARKET_PRICE -

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

EXCEPTIONS details

NO_PV_CALCULATED -

Data type:
Optional: No
Call by Reference: Yes

MARKET_DATA_SPOT -

Data type:
Optional: No
Call by Reference: Yes

INVALID_DATA -

Data type:
Optional: No
Call by Reference: Yes

NO_VARIABLE_RATE -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for RM_MM_UTIL_GET_CFUT_MP 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_iv_date  TYPE D, "   
lv_ev_market_price  TYPE F, "   
lv_no_pv_calculated  TYPE F, "   
lv_is_fget  TYPE TV1_FGET_TYP, "   
lv_market_data_spot  TYPE TV1_FGET_TYP, "   
lv_is_methode  TYPE TVM_METH_TYP, "   
lv_invalid_data  TYPE TVM_METH_TYP, "   
lv_is_shift_rule  TYPE JBRREG, "   
lv_no_variable_rate  TYPE JBRREG. "   

  CALL FUNCTION 'RM_MM_UTIL_GET_CFUT_MP'  "Utility - Get Market Price for Commodity Future
    EXPORTING
         IV_DATE = lv_iv_date
         IS_FGET = lv_is_fget
         IS_METHODE = lv_is_methode
         IS_SHIFT_RULE = lv_is_shift_rule
    IMPORTING
         EV_MARKET_PRICE = lv_ev_market_price
    EXCEPTIONS
        NO_PV_CALCULATED = 1
        MARKET_DATA_SPOT = 2
        INVALID_DATA = 3
        NO_VARIABLE_RATE = 4
. " RM_MM_UTIL_GET_CFUT_MP




ABAP code using 7.40 inline data declarations to call FM RM_MM_UTIL_GET_CFUT_MP

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



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!