SAP RM_COMPLEX_OPTION_UL_PREPARE Function Module for Check if UL is Suitable for Complex OTC Option









RM_COMPLEX_OPTION_UL_PREPARE is a standard rm complex option ul prepare SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check if UL is Suitable for Complex OTC Option 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 complex option ul prepare FM, simply by entering the name RM_COMPLEX_OPTION_UL_PREPARE into the relevant SAP transaction such as SE37 or SE38.

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



Function RM_COMPLEX_OPTION_UL_PREPARE 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_COMPLEX_OPTION_UL_PREPARE'"Check if UL is Suitable for Complex OTC Option
EXPORTING
I_MATURITY = "
I_OPT_OPTI = "
* I_PROTOCOL_LEVEL = 1 "

CHANGING
C_UL_FGET = "

TABLES
* C_ERROR_ITAB = "

EXCEPTIONS
INVALID_UNDERLYING = 1 INVALID_OPTION = 2
.



IMPORTING Parameters details for RM_COMPLEX_OPTION_UL_PREPARE

I_MATURITY -

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

I_OPT_OPTI -

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

I_PROTOCOL_LEVEL -

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

CHANGING Parameters details for RM_COMPLEX_OPTION_UL_PREPARE

C_UL_FGET -

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

TABLES Parameters details for RM_COMPLEX_OPTION_UL_PREPARE

C_ERROR_ITAB -

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

EXCEPTIONS details

INVALID_UNDERLYING -

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

INVALID_OPTION -

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

Copy and paste ABAP code example for RM_COMPLEX_OPTION_UL_PREPARE 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_c_ul_fget  TYPE TV1_FGET_TYP, "   
lv_i_maturity  TYPE SY-DATUM, "   
lt_c_error_itab  TYPE STANDARD TABLE OF BAPIERR, "   
lv_invalid_underlying  TYPE BAPIERR, "   
lv_i_opt_opti  TYPE TV0_OPTI_TYP, "   
lv_invalid_option  TYPE TV0_OPTI_TYP, "   
lv_i_protocol_level  TYPE TV0_OPTI_TYP. "   1

  CALL FUNCTION 'RM_COMPLEX_OPTION_UL_PREPARE'  "Check if UL is Suitable for Complex OTC Option
    EXPORTING
         I_MATURITY = lv_i_maturity
         I_OPT_OPTI = lv_i_opt_opti
         I_PROTOCOL_LEVEL = lv_i_protocol_level
    CHANGING
         C_UL_FGET = lv_c_ul_fget
    TABLES
         C_ERROR_ITAB = lt_c_error_itab
    EXCEPTIONS
        INVALID_UNDERLYING = 1
        INVALID_OPTION = 2
. " RM_COMPLEX_OPTION_UL_PREPARE




ABAP code using 7.40 inline data declarations to call FM RM_COMPLEX_OPTION_UL_PREPARE

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 DATUM FROM SY INTO @DATA(ld_i_maturity).
 
 
 
 
 
DATA(ld_i_protocol_level) = 1.
 


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!