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

Function FPM_GET_SEARCH 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 'FPM_GET_SEARCH'"Load of FPM Searches.
EXPORTING
IS_CONFIG = "Key Components of Configuration Tables
IV_APP_KEY = "
* IV_UNAME = SY-UNAME "User Name
IMPORTING
ET_SEARCH_IDS = "Table Type for Search Description/Id
IMPORTING Parameters details for FPM_GET_SEARCH
IS_CONFIG - Key Components of Configuration Tables
Data type: WDY_CONFIG_KEYOptional: No
Call by Reference: Yes
IV_APP_KEY -
Data type: STRINGOptional: No
Call by Reference: Yes
IV_UNAME - User Name
Data type: SYUNAMEDefault: SY-UNAME
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FPM_GET_SEARCH
ET_SEARCH_IDS - Table Type for Search Description/Id
Data type: FPMGB_T_SEARCH_IDSOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FPM_GET_SEARCH 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_is_config | TYPE WDY_CONFIG_KEY, " | |||
| lv_et_search_ids | TYPE FPMGB_T_SEARCH_IDS, " | |||
| lv_iv_app_key | TYPE STRING, " | |||
| lv_iv_uname | TYPE SYUNAME. " SY-UNAME |
|   CALL FUNCTION 'FPM_GET_SEARCH' "Load of FPM Searches |
| EXPORTING | ||
| IS_CONFIG | = lv_is_config | |
| IV_APP_KEY | = lv_iv_app_key | |
| IV_UNAME | = lv_iv_uname | |
| IMPORTING | ||
| ET_SEARCH_IDS | = lv_et_search_ids | |
| . " FPM_GET_SEARCH | ||
ABAP code using 7.40 inline data declarations to call FM FPM_GET_SEARCH
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.| DATA(ld_iv_uname) | = SY-UNAME. | |||
Search for further information about these or an SAP related objects