SAP ICLE_EVENT_FMOD2_MC Function Module for









ICLE_EVENT_FMOD2_MC is a standard icle event fmod2 mc SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 icle event fmod2 mc FM, simply by entering the name ICLE_EVENT_FMOD2_MC into the relevant SAP transaction such as SE37 or SE38.

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



Function ICLE_EVENT_FMOD2_MC 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 'ICLE_EVENT_FMOD2_MC'"
EXPORTING
FLDGR = "
IN_STATUS = "

IMPORTING
OUT_STATUS = "
.



IMPORTING Parameters details for ICLE_EVENT_FMOD2_MC

FLDGR -

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

IN_STATUS -

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

EXPORTING Parameters details for ICLE_EVENT_FMOD2_MC

OUT_STATUS -

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

Copy and paste ABAP code example for ICLE_EVENT_FMOD2_MC 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_fldgr  TYPE TBZ3W-FLDGR, "   
lv_out_status  TYPE BUS000FLDS-FLDSTAT, "   
lv_in_status  TYPE BUS000FLDS-FLDSTAT. "   

  CALL FUNCTION 'ICLE_EVENT_FMOD2_MC'  "
    EXPORTING
         FLDGR = lv_fldgr
         IN_STATUS = lv_in_status
    IMPORTING
         OUT_STATUS = lv_out_status
. " ICLE_EVENT_FMOD2_MC




ABAP code using 7.40 inline data declarations to call FM ICLE_EVENT_FMOD2_MC

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 FLDGR FROM TBZ3W INTO @DATA(ld_fldgr).
 
"SELECT single FLDSTAT FROM BUS000FLDS INTO @DATA(ld_out_status).
 
"SELECT single FLDSTAT FROM BUS000FLDS INTO @DATA(ld_in_status).
 


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!