SAP Function Modules

LSO_SE_QUERY_D SAP Function module







LSO_SE_QUERY_D is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name LSO_SE_QUERY_D into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: LSO_HRTEM00SEARCH_API
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM LSO_SE_QUERY_D - LSO SE QUERY D





CALL FUNCTION 'LSO_SE_QUERY_D' "
  EXPORTING
*   search_langu = SY-LANGU     " spras
*   search_plvar = SPACE        " plvar
    search_name = '*'           " seark
    search_text = '*'           " c
*   search_begda = '19000101'   " begdatum
*   search_endda = '99991231'   " enddatum
*   ev_tform =                  " lso_tform_c
*   ev_prereqguid =             " hrguid
*   ev_qualifguid =             " hrguid
*   ev_targetguid =             " hrguid
*   ev_categoryguid =           " hrguid
*   hit_from = 1                " i
*   hit_to = 20                 " i
*   verbose = SPACE             " flag
  IMPORTING
    hit_count =                 " sretgstruc-numofhit
  TABLES
    hitlist =                   " hrvsm_hit_e
*   out_documents =             " sretresdoc
*   out_docattributes =         " sretdcatvl
  EXCEPTIONS
    INVALID_QUERY = 1           "
    SERVER_NOT_REACHED = 2      "
    INDEX_NOT_ACTIVE = 3        "
    QUERY_ERROR = 4             "
    NOTHING_FOUND = 5           "
    INTERNAL_ERROR = 6          "
    .  "  LSO_SE_QUERY_D

ABAP code example for Function Module LSO_SE_QUERY_D





The ABAP code below is a full code listing to execute function module LSO_SE_QUERY_D including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_hit_count  TYPE SRETGSTRUC-NUMOFHIT ,
it_hitlist  TYPE STANDARD TABLE OF HRVSM_HIT_E,"TABLES PARAM
wa_hitlist  LIKE LINE OF it_hitlist ,
it_out_documents  TYPE STANDARD TABLE OF SRETRESDOC,"TABLES PARAM
wa_out_documents  LIKE LINE OF it_out_documents ,
it_out_docattributes  TYPE STANDARD TABLE OF SRETDCATVL,"TABLES PARAM
wa_out_docattributes  LIKE LINE OF it_out_docattributes .

DATA(ld_search_langu) = 'Check type of data required'.
DATA(ld_search_plvar) = 'Check type of data required'.
DATA(ld_search_name) = 'Check type of data required'.
DATA(ld_search_text) = 'Check type of data required'.
DATA(ld_search_begda) = 'Check type of data required'.
DATA(ld_search_endda) = 'Check type of data required'.
DATA(ld_ev_tform) = 'Check type of data required'.
DATA(ld_ev_prereqguid) = 'Check type of data required'.
DATA(ld_ev_qualifguid) = 'Check type of data required'.
DATA(ld_ev_targetguid) = 'Check type of data required'.
DATA(ld_ev_categoryguid) = 'Check type of data required'.
DATA(ld_hit_from) = 'Check type of data required'.
DATA(ld_hit_to) = 'Check type of data required'.
DATA(ld_verbose) = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_hitlist to it_hitlist.

"populate fields of struture and append to itab
append wa_out_documents to it_out_documents.

"populate fields of struture and append to itab
append wa_out_docattributes to it_out_docattributes. . CALL FUNCTION 'LSO_SE_QUERY_D' EXPORTING * search_langu = ld_search_langu * search_plvar = ld_search_plvar search_name = ld_search_name search_text = ld_search_text * search_begda = ld_search_begda * search_endda = ld_search_endda * ev_tform = ld_ev_tform * ev_prereqguid = ld_ev_prereqguid * ev_qualifguid = ld_ev_qualifguid * ev_targetguid = ld_ev_targetguid * ev_categoryguid = ld_ev_categoryguid * hit_from = ld_hit_from * hit_to = ld_hit_to * verbose = ld_verbose IMPORTING hit_count = ld_hit_count TABLES hitlist = it_hitlist * out_documents = it_out_documents * out_docattributes = it_out_docattributes EXCEPTIONS INVALID_QUERY = 1 SERVER_NOT_REACHED = 2 INDEX_NOT_ACTIVE = 3 QUERY_ERROR = 4 NOTHING_FOUND = 5 INTERNAL_ERROR = 6 . " LSO_SE_QUERY_D
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 2. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 3. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 4. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 5. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 6. "Exception "Add code for exception here ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:
ld_hit_count  TYPE SRETGSTRUC-NUMOFHIT ,
ld_search_langu  TYPE SPRAS ,
it_hitlist  TYPE STANDARD TABLE OF HRVSM_HIT_E ,
wa_hitlist  LIKE LINE OF it_hitlist,
ld_search_plvar  TYPE PLVAR ,
it_out_documents  TYPE STANDARD TABLE OF SRETRESDOC ,
wa_out_documents  LIKE LINE OF it_out_documents,
ld_search_name  TYPE SEARK ,
it_out_docattributes  TYPE STANDARD TABLE OF SRETDCATVL ,
wa_out_docattributes  LIKE LINE OF it_out_docattributes,
ld_search_text  TYPE C ,
ld_search_begda  TYPE BEGDATUM ,
ld_search_endda  TYPE ENDDATUM ,
ld_ev_tform  TYPE LSO_TFORM_C ,
ld_ev_prereqguid  TYPE HRGUID ,
ld_ev_qualifguid  TYPE HRGUID ,
ld_ev_targetguid  TYPE HRGUID ,
ld_ev_categoryguid  TYPE HRGUID ,
ld_hit_from  TYPE I ,
ld_hit_to  TYPE I ,
ld_verbose  TYPE FLAG .

ld_search_langu = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_hitlist to it_hitlist.
ld_search_plvar = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_out_documents to it_out_documents.
ld_search_name = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_out_docattributes to it_out_docattributes.
ld_search_text = 'Check type of data required'.
ld_search_begda = 'Check type of data required'.
ld_search_endda = 'Check type of data required'.
ld_ev_tform = 'Check type of data required'.
ld_ev_prereqguid = 'Check type of data required'.
ld_ev_qualifguid = 'Check type of data required'.
ld_ev_targetguid = 'Check type of data required'.
ld_ev_categoryguid = 'Check type of data required'.
ld_hit_from = 'Check type of data required'.
ld_hit_to = 'Check type of data required'.
ld_verbose = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name LSO_SE_QUERY_D or its description.