SAP FCOM_MET_UI_CALL_SCREEN Function Module for Call Screen









FCOM_MET_UI_CALL_SCREEN is a standard fcom met ui call screen SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Call Screen 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 fcom met ui call screen FM, simply by entering the name FCOM_MET_UI_CALL_SCREEN into the relevant SAP transaction such as SE37 or SE38.

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



Function FCOM_MET_UI_CALL_SCREEN 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 'FCOM_MET_UI_CALL_SCREEN'"Call Screen
EXPORTING
IV_DYNNR = "Number of the following screen
* IS_DIALOG_POS = "
.



IMPORTING Parameters details for FCOM_MET_UI_CALL_SCREEN

IV_DYNNR - Number of the following screen

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

IS_DIALOG_POS -

Data type: IF_FCOM_MET_CONTROLLER=>TY_S_DIALOG_POS
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for FCOM_MET_UI_CALL_SCREEN 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_dynnr  TYPE DYNNR, "   
lv_is_dialog_pos  TYPE IF_FCOM_MET_CONTROLLER=>TY_S_DIALOG_POS. "   

  CALL FUNCTION 'FCOM_MET_UI_CALL_SCREEN'  "Call Screen
    EXPORTING
         IV_DYNNR = lv_iv_dynnr
         IS_DIALOG_POS = lv_is_dialog_pos
. " FCOM_MET_UI_CALL_SCREEN




ABAP code using 7.40 inline data declarations to call FM FCOM_MET_UI_CALL_SCREEN

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!