SAP ISU_ESMON_COUNT_BUSOBJ_MSGS Function Module for count business objects and messages
ISU_ESMON_COUNT_BUSOBJ_MSGS is a standard isu esmon count busobj msgs SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for count business objects and messages 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 isu esmon count busobj msgs FM, simply by entering the name ISU_ESMON_COUNT_BUSOBJ_MSGS into the relevant SAP transaction such as SE37 or SE38.
Function Group: ESMONITORING_DBPROCESS
Program Name: SAPLESMONITORING_DBPROCESS
Main Program: SAPLESMONITORING_DBPROCESS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function ISU_ESMON_COUNT_BUSOBJ_MSGS 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 'ISU_ESMON_COUNT_BUSOBJ_MSGS'"count business objects and messages.
IMPORTING
EV_USER = "R/3 System, user logon name
EV_DATE = "Date and time, current (application server) date
TABLES
IT_MESSAGES = "Monitoring Mass Run: Log Summary According to Intervals
ET_OUTPUT_INT = "Strucutre to process data for output interval level
ET_MSGEO = "Monitoring Mass Run: Messages from Application Log
ET_MSGWO = "Monitoring Mass Run: Messages from Application Log
ET_MSGSO = "Monitoring Mass Run: Messages from Application Log
ET_MSGIM = "Monitoring Mass Run: Messages from Application Log
ET_MSGWM = "Monitoring Mass Run: Messages from Application Log
ET_MSGEM = "Monitoring Mass Run: Messages from Application Log
EXPORTING Parameters details for ISU_ESMON_COUNT_BUSOBJ_MSGS
EV_USER - R/3 System, user logon name
Data type: SY-UNAMEOptional: No
Call by Reference: Yes
EV_DATE - Date and time, current (application server) date
Data type: SY-DATUMOptional: No
Call by Reference: Yes
TABLES Parameters details for ISU_ESMON_COUNT_BUSOBJ_MSGS
IT_MESSAGES - Monitoring Mass Run: Log Summary According to Intervals
Data type: ESMON_LOGSUMMARYOptional: No
Call by Reference: Yes
ET_OUTPUT_INT - Strucutre to process data for output interval level
Data type: ESMON_OUTPUT_INTOptional: No
Call by Reference: Yes
ET_MSGEO - Monitoring Mass Run: Messages from Application Log
Data type: ESMON_MSGSUMMARYOptional: No
Call by Reference: Yes
ET_MSGWO - Monitoring Mass Run: Messages from Application Log
Data type: ESMON_MSGSUMMARYOptional: No
Call by Reference: Yes
ET_MSGSO - Monitoring Mass Run: Messages from Application Log
Data type: ESMON_MSGSUMMARYOptional: No
Call by Reference: Yes
ET_MSGIM - Monitoring Mass Run: Messages from Application Log
Data type: ESMON_MSGSUMMARYOptional: No
Call by Reference: Yes
ET_MSGWM - Monitoring Mass Run: Messages from Application Log
Data type: ESMON_MSGSUMMARYOptional: No
Call by Reference: Yes
ET_MSGEM - Monitoring Mass Run: Messages from Application Log
Data type: ESMON_MSGSUMMARYOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISU_ESMON_COUNT_BUSOBJ_MSGS 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_ev_user | TYPE SY-UNAME, " | |||
| lt_it_messages | TYPE STANDARD TABLE OF ESMON_LOGSUMMARY, " | |||
| lv_ev_date | TYPE SY-DATUM, " | |||
| lt_et_output_int | TYPE STANDARD TABLE OF ESMON_OUTPUT_INT, " | |||
| lt_et_msgeo | TYPE STANDARD TABLE OF ESMON_MSGSUMMARY, " | |||
| lt_et_msgwo | TYPE STANDARD TABLE OF ESMON_MSGSUMMARY, " | |||
| lt_et_msgso | TYPE STANDARD TABLE OF ESMON_MSGSUMMARY, " | |||
| lt_et_msgim | TYPE STANDARD TABLE OF ESMON_MSGSUMMARY, " | |||
| lt_et_msgwm | TYPE STANDARD TABLE OF ESMON_MSGSUMMARY, " | |||
| lt_et_msgem | TYPE STANDARD TABLE OF ESMON_MSGSUMMARY. " |
| CALL FUNCTION 'ISU_ESMON_COUNT_BUSOBJ_MSGS' "count business objects and messages |
| IMPORTING | ||
| EV_USER | = lv_ev_user | |
| EV_DATE | = lv_ev_date | |
| TABLES | ||
| IT_MESSAGES | = lt_it_messages | |
| ET_OUTPUT_INT | = lt_et_output_int | |
| ET_MSGEO | = lt_et_msgeo | |
| ET_MSGWO | = lt_et_msgwo | |
| ET_MSGSO | = lt_et_msgso | |
| ET_MSGIM | = lt_et_msgim | |
| ET_MSGWM | = lt_et_msgwm | |
| ET_MSGEM | = lt_et_msgem | |
| . " ISU_ESMON_COUNT_BUSOBJ_MSGS | ||
ABAP code using 7.40 inline data declarations to call FM ISU_ESMON_COUNT_BUSOBJ_MSGS
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 UNAME FROM SY INTO @DATA(ld_ev_user). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_ev_date). | ||||
Search for further information about these or an SAP related objects