SAP FPM_LOAD_SEARCH Function Module for Load Saved Search









FPM_LOAD_SEARCH is a standard fpm load 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 Saved Search 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 load search FM, simply by entering the name FPM_LOAD_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_LOAD_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_LOAD_SEARCH'"Load Saved Search
  EXPORTING
   IS_SEARCH_ID =  "Structure of Search description/id
   IS_CONFIG =  "Key Components of Configuration Tables
   IV_APP_KEY =  "
*  IV_UNAME = SY-UNAME "User Name

 IMPORTING
   ET_SEARCH_CRITERIA =  "Search criteria for GUIBB Search (internal)
   EV_MAX_NUM_RESULT =  "GUIBB SEARCH: Number of Rows in Result List
   ET_GROUP_STATE =  "Select Options: Table Type of WDR_SO_S_GROUP_STATE
   EV_SHOW_ALL_RESULTS =  "Replacement for Real Boolean Type: 'X' == True '' == False
   EV_NOTHING_FOUND =  "Replacement for Real Boolean Type: 'X' == True '' == False
.



IMPORTING Parameters details for FPM_LOAD_SEARCH

IS_SEARCH_ID - Structure of Search description/id

Data type: FPMGB_S_SEARCH_IDS
Optional: No
Call by Reference: Yes

IS_CONFIG - Key Components of Configuration Tables

Data type: WDY_CONFIG_KEY
Optional: No
Call by Reference: Yes

IV_APP_KEY -

Data type: STRING
Optional: No
Call by Reference: Yes

IV_UNAME - User Name

Data type: SYUNAME
Default: SY-UNAME
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for FPM_LOAD_SEARCH

ET_SEARCH_CRITERIA - Search criteria for GUIBB Search (internal)

Data type: FPMGB_T_SEARCH_CRITERIA_INT
Optional: No
Call by Reference: Yes

EV_MAX_NUM_RESULT - GUIBB SEARCH: Number of Rows in Result List

Data type: FPMGB_SEARCH_RESULT_NUM_ROWS
Optional: No
Call by Reference: Yes

ET_GROUP_STATE - Select Options: Table Type of WDR_SO_S_GROUP_STATE

Data type: WDR_SO_T_GROUP_STATE
Optional: No
Call by Reference: Yes

EV_SHOW_ALL_RESULTS - Replacement for Real Boolean Type: 'X' == True '' == False

Data type: WDY_BOOLEAN
Optional: No
Call by Reference: Yes

EV_NOTHING_FOUND - Replacement for Real Boolean Type: 'X' == True '' == False

Data type: WDY_BOOLEAN
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FPM_LOAD_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_search_id  TYPE FPMGB_S_SEARCH_IDS, "   
lv_et_search_criteria  TYPE FPMGB_T_SEARCH_CRITERIA_INT, "   
lv_is_config  TYPE WDY_CONFIG_KEY, "   
lv_ev_max_num_result  TYPE FPMGB_SEARCH_RESULT_NUM_ROWS, "   
lv_iv_app_key  TYPE STRING, "   
lv_et_group_state  TYPE WDR_SO_T_GROUP_STATE, "   
lv_iv_uname  TYPE SYUNAME, "   SY-UNAME
lv_ev_show_all_results  TYPE WDY_BOOLEAN, "   
lv_ev_nothing_found  TYPE WDY_BOOLEAN. "   

  CALL FUNCTION 'FPM_LOAD_SEARCH'  "Load Saved Search
    EXPORTING
         IS_SEARCH_ID = lv_is_search_id
         IS_CONFIG = lv_is_config
         IV_APP_KEY = lv_iv_app_key
         IV_UNAME = lv_iv_uname
    IMPORTING
         ET_SEARCH_CRITERIA = lv_et_search_criteria
         EV_MAX_NUM_RESULT = lv_ev_max_num_result
         ET_GROUP_STATE = lv_et_group_state
         EV_SHOW_ALL_RESULTS = lv_ev_show_all_results
         EV_NOTHING_FOUND = lv_ev_nothing_found
. " FPM_LOAD_SEARCH




ABAP code using 7.40 inline data declarations to call FM FPM_LOAD_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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!