SAP MEREP_FILTER Function Module for Fitering
MEREP_FILTER is a standard merep filter SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Fitering 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 merep filter FM, simply by entering the name MEREP_FILTER into the relevant SAP transaction such as SE37 or SE38.
Function Group: MEREP_RUNTIME
Program Name: SAPLMEREP_RUNTIME
Main Program: SAPLMEREP_RUNTIME
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MEREP_FILTER 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 'MEREP_FILTER'"Fitering.
EXPORTING
* SEARCHFLD1 = "
* SEARCHFLD2 = "
* SEARCHFLD3 = "
SCENARIO = "
MOBILE_GROUP = "
MBL_ID = "
* R3KEY = "
ME = "
IMPORTING
RESULT = "
CHANGING
SYNC_GENERIC = "
BADI_PARMS = "
IMPORTING Parameters details for MEREP_FILTER
SEARCHFLD1 -
Data type: MEREP_LOWOptional: Yes
Call by Reference: Yes
SEARCHFLD2 -
Data type: MEREP_LOWOptional: Yes
Call by Reference: Yes
SEARCHFLD3 -
Data type: MEREP_LOWOptional: Yes
Call by Reference: Yes
SCENARIO -
Data type: MEREP_SCENARIOOptional: No
Call by Reference: Yes
MOBILE_GROUP -
Data type: MEREP_GROUPOptional: No
Call by Reference: Yes
MBL_ID -
Data type: MEREP_MBL_IDOptional: No
Call by Reference: Yes
R3KEY -
Data type: MEREP_R3KEYSOptional: Yes
Call by Reference: Yes
ME -
Data type: MEREP_MEOptional: No
Call by Reference: Yes
EXPORTING Parameters details for MEREP_FILTER
RESULT -
Data type: MEREP_FLAGOptional: No
Call by Reference: Yes
CHANGING Parameters details for MEREP_FILTER
SYNC_GENERIC -
Data type: MEREP_SYNC_GENERICOptional: No
Call by Reference: Yes
BADI_PARMS -
Data type: MEREP_BADI_PARMSOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for MEREP_FILTER 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_result | TYPE MEREP_FLAG, " | |||
| lv_searchfld1 | TYPE MEREP_LOW, " | |||
| lv_sync_generic | TYPE MEREP_SYNC_GENERIC, " | |||
| lv_badi_parms | TYPE MEREP_BADI_PARMS, " | |||
| lv_searchfld2 | TYPE MEREP_LOW, " | |||
| lv_searchfld3 | TYPE MEREP_LOW, " | |||
| lv_scenario | TYPE MEREP_SCENARIO, " | |||
| lv_mobile_group | TYPE MEREP_GROUP, " | |||
| lv_mbl_id | TYPE MEREP_MBL_ID, " | |||
| lv_r3key | TYPE MEREP_R3KEYS, " | |||
| lv_me | TYPE MEREP_ME. " |
|   CALL FUNCTION 'MEREP_FILTER' "Fitering |
| EXPORTING | ||
| SEARCHFLD1 | = lv_searchfld1 | |
| SEARCHFLD2 | = lv_searchfld2 | |
| SEARCHFLD3 | = lv_searchfld3 | |
| SCENARIO | = lv_scenario | |
| MOBILE_GROUP | = lv_mobile_group | |
| MBL_ID | = lv_mbl_id | |
| R3KEY | = lv_r3key | |
| ME | = lv_me | |
| IMPORTING | ||
| RESULT | = lv_result | |
| CHANGING | ||
| SYNC_GENERIC | = lv_sync_generic | |
| BADI_PARMS | = lv_badi_parms | |
| . " MEREP_FILTER | ||
ABAP code using 7.40 inline data declarations to call FM MEREP_FILTER
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