SAP RS_DME_RFC_UI_GET_F1 Function Module for handle f1 help request









RS_DME_RFC_UI_GET_F1 is a standard rs dme rfc ui get f1 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for handle f1 help request 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 rs dme rfc ui get f1 FM, simply by entering the name RS_DME_RFC_UI_GET_F1 into the relevant SAP transaction such as SE37 or SE38.

Function Group: RS_DME_RFC_UI
Program Name: SAPLRS_DME_RFC_UI
Main Program: SAPLRS_DME_RFC_UI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function RS_DME_RFC_UI_GET_F1 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 'RS_DME_RFC_UI_GET_F1'"handle f1 help request
  EXPORTING
   I_MODEL =  "Analytical Model
   I_ENGINE =  "Analytical service
   I_FIELD =  "Name of a Screen Element
*  I_SCREEN_ID =  "id of the screen
*  I_VALUE =  "value at the screen field

 IMPORTING
   E_OUTPUT_TYPE =  "0-none 1-url 2-text 3-exe 4-dataelement
   E_URL =  "document url
   E_DATA_ELEMENT_NAME =  "Data element (semantic domain)
   E_EXE_NAME =  "Path and executable name
   E_EXE_PARAM =  "Parameter for the executable

TABLES
   I_T_CONN_INFO =  "Table type of connection parameters
*  E_T_RETURN =  "Return Parameter
*  E_T_TEXT =  "html/texts
.



IMPORTING Parameters details for RS_DME_RFC_UI_GET_F1

I_MODEL - Analytical Model

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

I_ENGINE - Analytical service

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

I_FIELD - Name of a Screen Element

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

I_SCREEN_ID - id of the screen

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

I_VALUE - value at the screen field

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

EXPORTING Parameters details for RS_DME_RFC_UI_GET_F1

E_OUTPUT_TYPE - 0-none 1-url 2-text 3-exe 4-dataelement

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

E_URL - document url

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

E_DATA_ELEMENT_NAME - Data element (semantic domain)

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

E_EXE_NAME - Path and executable name

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

E_EXE_PARAM - Parameter for the executable

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

TABLES Parameters details for RS_DME_RFC_UI_GET_F1

I_T_CONN_INFO - Table type of connection parameters

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

E_T_RETURN - Return Parameter

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

E_T_TEXT - html/texts

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

Copy and paste ABAP code example for RS_DME_RFC_UI_GET_F1 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_model  TYPE RSDMEM_MODEL, "   
lv_e_output_type  TYPE CHAR1, "   
lt_i_t_conn_info  TYPE STANDARD TABLE OF RSDMEM_TH_CONN_PAR, "   
lv_e_url  TYPE STRING, "   
lv_i_engine  TYPE RSDMEM_ANALYTICAL_SERVICE, "   
lt_e_t_return  TYPE STANDARD TABLE OF BAPIRET2_T, "   
lv_i_field  TYPE SCRFNAME, "   
lt_e_t_text  TYPE STANDARD TABLE OF W3HTMLTAB, "   
lv_e_data_element_name  TYPE ROLLNAME, "   
lv_e_exe_name  TYPE STRING, "   
lv_i_screen_id  TYPE RSDMEM_ATTR_VAL64, "   
lv_i_value  TYPE STRING, "   
lv_e_exe_param  TYPE STRING. "   

  CALL FUNCTION 'RS_DME_RFC_UI_GET_F1'  "handle f1 help request
    EXPORTING
         I_MODEL = lv_i_model
         I_ENGINE = lv_i_engine
         I_FIELD = lv_i_field
         I_SCREEN_ID = lv_i_screen_id
         I_VALUE = lv_i_value
    IMPORTING
         E_OUTPUT_TYPE = lv_e_output_type
         E_URL = lv_e_url
         E_DATA_ELEMENT_NAME = lv_e_data_element_name
         E_EXE_NAME = lv_e_exe_name
         E_EXE_PARAM = lv_e_exe_param
    TABLES
         I_T_CONN_INFO = lt_i_t_conn_info
         E_T_RETURN = lt_e_t_return
         E_T_TEXT = lt_e_t_text
. " RS_DME_RFC_UI_GET_F1




ABAP code using 7.40 inline data declarations to call FM RS_DME_RFC_UI_GET_F1

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!