SAP Function Modules

MCS_EVENT_GENERATE SAP Function module







MCS_EVENT_GENERATE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name MCS_EVENT_GENERATE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: MCSE
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM MCS_EVENT_GENERATE - MCS EVENT GENERATE





CALL FUNCTION 'MCS_EVENT_GENERATE' "
  EXPORTING
    i_zeitp =                   " dmcse-zeitp   Event
    i_kappl =                   " dmcse-kappl   Application
    i_zptxt =                   " dmcse-zptxt   Short text for event
    i_cstru =                   " dmcse-cstru   Communication structure
  EXCEPTIONS
    EVENT_EXIST = 1             "               The event already exists
    ERRORS_FOUND = 2            "               Errors occurred, check log!
    TRANSPORT_ERROR = 3         "               Error in transport handling
    .  "  MCS_EVENT_GENERATE

ABAP code example for Function Module MCS_EVENT_GENERATE





The ABAP code below is a full code listing to execute function module MCS_EVENT_GENERATE including all data declarations. The code uses 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 original method of declaring data variables up front. 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).



DATA(ld_i_zeitp) = some text here

DATA(ld_i_kappl) = some text here

DATA(ld_i_zptxt) = some text here

DATA(ld_i_cstru) = some text here . CALL FUNCTION 'MCS_EVENT_GENERATE' EXPORTING i_zeitp = ld_i_zeitp i_kappl = ld_i_kappl i_zptxt = ld_i_zptxt i_cstru = ld_i_cstru EXCEPTIONS EVENT_EXIST = 1 ERRORS_FOUND = 2 TRANSPORT_ERROR = 3 . " MCS_EVENT_GENERATE
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 2. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 3. "Exception "Add code for exception here ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:
ld_i_zeitp  TYPE DMCSE-ZEITP ,
ld_i_kappl  TYPE DMCSE-KAPPL ,
ld_i_zptxt  TYPE DMCSE-ZPTXT ,
ld_i_cstru  TYPE DMCSE-CSTRU .


ld_i_zeitp = some text here

ld_i_kappl = some text here

ld_i_zptxt = some text here

ld_i_cstru = some text here

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name MCS_EVENT_GENERATE or its description.