SAP ME_DISPLAY_COUNT Function Module for
ME_DISPLAY_COUNT is a standard me display count 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 me display count FM, simply by entering the name ME_DISPLAY_COUNT into the relevant SAP transaction such as SE37 or SE38.
Function Group: ME_CENTRAL_TRACING
Program Name: SAPLME_CENTRAL_TRACING
Main Program: SAPLME_CENTRAL_TRACING
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ME_DISPLAY_COUNT 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 'ME_DISPLAY_COUNT'".
EXPORTING
I_COUNT_SEL = "
I_COUNT_REAL = "
I_MINUS_FILTER = "
* I_FLAG = ' ' "
EXCEPTIONS
ERROR = 1
IMPORTING Parameters details for ME_DISPLAY_COUNT
I_COUNT_SEL -
Data type: IOptional: No
Call by Reference: Yes
I_COUNT_REAL -
Data type: IOptional: No
Call by Reference: Yes
I_MINUS_FILTER -
Data type: IOptional: No
Call by Reference: Yes
I_FLAG -
Data type: BOOLE-BOOLEDefault: ' '
Optional: Yes
Call by Reference: Yes
EXCEPTIONS details
ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ME_DISPLAY_COUNT 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_error | TYPE STRING, " | |||
| lv_i_count_sel | TYPE I, " | |||
| lv_i_count_real | TYPE I, " | |||
| lv_i_minus_filter | TYPE I, " | |||
| lv_i_flag | TYPE BOOLE-BOOLE. " ' ' |
|   CALL FUNCTION 'ME_DISPLAY_COUNT' " |
| EXPORTING | ||
| I_COUNT_SEL | = lv_i_count_sel | |
| I_COUNT_REAL | = lv_i_count_real | |
| I_MINUS_FILTER | = lv_i_minus_filter | |
| I_FLAG | = lv_i_flag | |
| EXCEPTIONS | ||
| ERROR = 1 | ||
| . " ME_DISPLAY_COUNT | ||
ABAP code using 7.40 inline data declarations to call FM ME_DISPLAY_COUNT
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 BOOLE FROM BOOLE INTO @DATA(ld_i_flag). | ||||
| DATA(ld_i_flag) | = ' '. | |||
Search for further information about these or an SAP related objects