SAP CON_GET_IMPORT_MAPPING_FILTER Function Module for Consent Administration: Get Import Mapping Filter
CON_GET_IMPORT_MAPPING_FILTER is a standard con get import mapping 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 Consent Administration: Get Import Mapping Filter 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 con get import mapping filter FM, simply by entering the name CON_GET_IMPORT_MAPPING_FILTER into the relevant SAP transaction such as SE37 or SE38.
Function Group: CONSENT_INBOUND
Program Name: SAPLCONSENT_INBOUND
Main Program: SAPLCONSENT_INBOUND
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CON_GET_IMPORT_MAPPING_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 'CON_GET_IMPORT_MAPPING_FILTER'"Consent Administration: Get Import Mapping Filter.
IMPORTING
ET_VALUE = "
EXPORTING Parameters details for CON_GET_IMPORT_MAPPING_FILTER
ET_VALUE -
Data type: VRM_VALUESOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CON_GET_IMPORT_MAPPING_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_et_value | TYPE VRM_VALUES. " |
|   CALL FUNCTION 'CON_GET_IMPORT_MAPPING_FILTER' "Consent Administration: Get Import Mapping Filter |
| IMPORTING | ||
| ET_VALUE | = lv_et_value | |
| . " CON_GET_IMPORT_MAPPING_FILTER | ||
ABAP code using 7.40 inline data declarations to call FM CON_GET_IMPORT_MAPPING_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