SAP RM_COMPLEX_SEC_TYPE_UL_DETERM Function Module for Determination of an Underlying FGET for a Complex Class









RM_COMPLEX_SEC_TYPE_UL_DETERM is a standard rm complex sec type ul determ SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determination of an Underlying FGET for a Complex Class 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 sec type ul determ FM, simply by entering the name RM_COMPLEX_SEC_TYPE_UL_DETERM 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_SEC_TYPE_UL_DETERM 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_SEC_TYPE_UL_DETERM'"Determination of an Underlying FGET for a Complex Class
EXPORTING
I_GID_ROOT = "
I_CSEC_FGET_TAB = "
* I_PROTOCOL_LEVEL = 1 "

IMPORTING
E_CSEC_SEC_UL_FGET = "

TABLES
* C_ERROR_ITAB = "

EXCEPTIONS
INVALID_DATA = 1
.



IMPORTING Parameters details for RM_COMPLEX_SEC_TYPE_UL_DETERM

I_GID_ROOT -

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

I_CSEC_FGET_TAB -

Data type: TV1_FGET_TAB
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)

EXPORTING Parameters details for RM_COMPLEX_SEC_TYPE_UL_DETERM

E_CSEC_SEC_UL_FGET -

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

TABLES Parameters details for RM_COMPLEX_SEC_TYPE_UL_DETERM

C_ERROR_ITAB -

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

EXCEPTIONS details

INVALID_DATA -

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

Copy and paste ABAP code example for RM_COMPLEX_SEC_TYPE_UL_DETERM 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_gid_root  TYPE TV1_KNOT_ID, "   
lt_c_error_itab  TYPE STANDARD TABLE OF BAPIERR, "   
lv_invalid_data  TYPE BAPIERR, "   
lv_e_csec_sec_ul_fget  TYPE TV1_FGET_TYP, "   
lv_i_csec_fget_tab  TYPE TV1_FGET_TAB, "   
lv_i_protocol_level  TYPE TV1_FGET_TAB. "   1

  CALL FUNCTION 'RM_COMPLEX_SEC_TYPE_UL_DETERM'  "Determination of an Underlying FGET for a Complex Class
    EXPORTING
         I_GID_ROOT = lv_i_gid_root
         I_CSEC_FGET_TAB = lv_i_csec_fget_tab
         I_PROTOCOL_LEVEL = lv_i_protocol_level
    IMPORTING
         E_CSEC_SEC_UL_FGET = lv_e_csec_sec_ul_fget
    TABLES
         C_ERROR_ITAB = lt_c_error_itab
    EXCEPTIONS
        INVALID_DATA = 1
. " RM_COMPLEX_SEC_TYPE_UL_DETERM




ABAP code using 7.40 inline data declarations to call FM RM_COMPLEX_SEC_TYPE_UL_DETERM

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.

 
 
 
 
 
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!