SAP RS_DME_RFC_UI_GET_FCODE_PARAMS Function Module for launch workbench/model details

Search SAP Function Modules

RS_DME_RFC_UI_GET_FCODE_PARAMS is a standard rs dme rfc ui get fcode params SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for launch workbench/model details 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 fcode params FM, simply by entering the name RS_DME_RFC_UI_GET_FCODE_PARAMS 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_FCODE_PARAMS 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_FCODE_PARAMS'"launch workbench/model details
  EXPORTING
   I_MODEL =  "Analytical Model
   I_ENGINE =  "Analytical service
   I_FCODE =  "Screens, function code triggered by PAI

TABLES
   I_T_CONN_INFO =  "Table type of connection parameters
*  E_T_RETURN =  "Return Parameter
   E_T_PARAM_META =  "Fcode parameters metadata

.

IMPORTING Parameters details for RS_DME_RFC_UI_GET_FCODE_PARAMS

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_FCODE - Screens, function code triggered by PAI

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

TABLES Parameters details for RS_DME_RFC_UI_GET_FCODE_PARAMS

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: No ( called with pass by value option)

E_T_PARAM_META - Fcode parameters metadata

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

Copy and paste ABAP code example for RS_DME_RFC_UI_GET_FCODE_PARAMS 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.

ABAP code using 7.40 inline data declarations to call FM RS_DME_RFC_UI_GET_FCODE_PARAMS

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