SAP IDOC_DATA_APPLY_FILTER_VALUES Function Module for
IDOC_DATA_APPLY_FILTER_VALUES is a standard idoc data apply filter values 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 idoc data apply filter values FM, simply by entering the name IDOC_DATA_APPLY_FILTER_VALUES into the relevant SAP transaction such as SE37 or SE38.
Function Group: BD11
Program Name: SAPLBD11
Main Program: SAPLBD11
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function IDOC_DATA_APPLY_FILTER_VALUES 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 'IDOC_DATA_APPLY_FILTER_VALUES'".
EXPORTING
CONDITION_BLOCKS = "
MESSAGE_TYPE = "
RECEIVER = "
BASIC_TYPE = "
EXTENSION_TYPE = "
IMPORTING
CHANGE_PROTOCOL = "
IDOC_CHANGED = "
TABLES
IDOC_DATA = "
EXCEPTIONS
ALE_SERVICES_NOT_APPLIED = 1 SERIOUS_PROBLEM_OCCURED = 2 NO_DATA_RECORDS_LEFT = 3
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLBD11_001 User Exit for IDoc Version Change
IMPORTING Parameters details for IDOC_DATA_APPLY_FILTER_VALUES
CONDITION_BLOCKS -
Data type: BD11_CONDITION_BLOCK_TABOptional: No
Call by Reference: No ( called with pass by value option)
MESSAGE_TYPE -
Data type: EDIDC-MESTYPOptional: No
Call by Reference: No ( called with pass by value option)
RECEIVER -
Data type: TBD05-RCVSYSTEMOptional: No
Call by Reference: No ( called with pass by value option)
BASIC_TYPE -
Data type: EDIDC-IDOCTPOptional: No
Call by Reference: No ( called with pass by value option)
EXTENSION_TYPE -
Data type: EDIDC-CIMTYPOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for IDOC_DATA_APPLY_FILTER_VALUES
CHANGE_PROTOCOL -
Data type: BD11_CHANGE_PROTOCOL_TABOptional: No
Call by Reference: Yes
IDOC_CHANGED -
Data type: BDIPARAM-BOOLEANOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for IDOC_DATA_APPLY_FILTER_VALUES
IDOC_DATA -
Data type: EDIDDOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ALE_SERVICES_NOT_APPLIED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SERIOUS_PROBLEM_OCCURED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_DATA_RECORDS_LEFT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for IDOC_DATA_APPLY_FILTER_VALUES 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: | ||||
| lt_idoc_data | TYPE STANDARD TABLE OF EDIDD, " | |||
| lv_change_protocol | TYPE BD11_CHANGE_PROTOCOL_TAB, " | |||
| lv_condition_blocks | TYPE BD11_CONDITION_BLOCK_TAB, " | |||
| lv_ale_services_not_applied | TYPE BD11_CONDITION_BLOCK_TAB, " | |||
| lv_idoc_changed | TYPE BDIPARAM-BOOLEAN, " | |||
| lv_message_type | TYPE EDIDC-MESTYP, " | |||
| lv_serious_problem_occured | TYPE EDIDC, " | |||
| lv_receiver | TYPE TBD05-RCVSYSTEM, " | |||
| lv_no_data_records_left | TYPE TBD05, " | |||
| lv_basic_type | TYPE EDIDC-IDOCTP, " | |||
| lv_extension_type | TYPE EDIDC-CIMTYP. " |
|   CALL FUNCTION 'IDOC_DATA_APPLY_FILTER_VALUES' " |
| EXPORTING | ||
| CONDITION_BLOCKS | = lv_condition_blocks | |
| MESSAGE_TYPE | = lv_message_type | |
| RECEIVER | = lv_receiver | |
| BASIC_TYPE | = lv_basic_type | |
| EXTENSION_TYPE | = lv_extension_type | |
| IMPORTING | ||
| CHANGE_PROTOCOL | = lv_change_protocol | |
| IDOC_CHANGED | = lv_idoc_changed | |
| TABLES | ||
| IDOC_DATA | = lt_idoc_data | |
| EXCEPTIONS | ||
| ALE_SERVICES_NOT_APPLIED = 1 | ||
| SERIOUS_PROBLEM_OCCURED = 2 | ||
| NO_DATA_RECORDS_LEFT = 3 | ||
| . " IDOC_DATA_APPLY_FILTER_VALUES | ||
ABAP code using 7.40 inline data declarations to call FM IDOC_DATA_APPLY_FILTER_VALUES
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 BOOLEAN FROM BDIPARAM INTO @DATA(ld_idoc_changed). | ||||
| "SELECT single MESTYP FROM EDIDC INTO @DATA(ld_message_type). | ||||
| "SELECT single RCVSYSTEM FROM TBD05 INTO @DATA(ld_receiver). | ||||
| "SELECT single IDOCTP FROM EDIDC INTO @DATA(ld_basic_type). | ||||
| "SELECT single CIMTYP FROM EDIDC INTO @DATA(ld_extension_type). | ||||
Search for further information about these or an SAP related objects