SAP Function Modules

IQM_BI_EXTRACT_REQUEST SAP Function module - Template: Transaction Data Transfer







IQM_BI_EXTRACT_REQUEST 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 IQM_BI_EXTRACT_REQUEST into the relevant SAP transaction such as SE37 or SE80.

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


Pattern for FM IQM_BI_EXTRACT_REQUEST - IQM BI EXTRACT REQUEST





CALL FUNCTION 'IQM_BI_EXTRACT_REQUEST' "Template: Transaction Data Transfer
  EXPORTING
    i_requnr =                  " srsc_s_if_simple-requnr  Request Number: ID for a Data Request
*   i_dsource =                 " srsc_s_if_simple-dsource  InfoSource Name
*   i_maxsize =                 " srsc_s_if_simple-maxsize  Maximum Number of Lines in Output Table
*   i_initflag =                " srsc_s_if_simple-initflag  Initialization 'X' or Data Transfer ' '
*   i_read_only =               " srsc_s_if_simple-readonly
*   i_remote_call = SBIWA_C_FLAG_OFF  " sbiwa_flag  Indicator: Remote Call from BW
* TABLES
*   i_t_select =                " srsc_s_if_simple-t_select  Selection Criteria
*   i_t_fields =                " srsc_s_if_simple-t_fields  Field List for SELECT
*   e_t_data =                  " rsiqmx_request  Output Table for Fixed InfoSource
  EXCEPTIONS
    NO_MORE_DATA = 1            "               Data Was Completely Transferred
    ERROR_PASSED_TO_MESS_HANDLER = 2  "         Exit Due to Error; Message in Message Handler
    .  "  IQM_BI_EXTRACT_REQUEST

ABAP code example for Function Module IQM_BI_EXTRACT_REQUEST





The ABAP code below is a full code listing to execute function module IQM_BI_EXTRACT_REQUEST 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:
it_i_t_select  TYPE STANDARD TABLE OF SRSC_S_IF_SIMPLE-T_SELECT,"TABLES PARAM
wa_i_t_select  LIKE LINE OF it_i_t_select ,
it_i_t_fields  TYPE STANDARD TABLE OF SRSC_S_IF_SIMPLE-T_FIELDS,"TABLES PARAM
wa_i_t_fields  LIKE LINE OF it_i_t_fields ,
it_e_t_data  TYPE STANDARD TABLE OF RSIQMX_REQUEST,"TABLES PARAM
wa_e_t_data  LIKE LINE OF it_e_t_data .


DATA(ld_i_requnr) = some text here

DATA(ld_i_dsource) = some text here

DATA(ld_i_maxsize) = some text here

DATA(ld_i_initflag) = some text here

DATA(ld_i_read_only) = some text here
DATA(ld_i_remote_call) = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_i_t_select to it_i_t_select.

"populate fields of struture and append to itab
append wa_i_t_fields to it_i_t_fields.

"populate fields of struture and append to itab
append wa_e_t_data to it_e_t_data. . CALL FUNCTION 'IQM_BI_EXTRACT_REQUEST' EXPORTING i_requnr = ld_i_requnr * i_dsource = ld_i_dsource * i_maxsize = ld_i_maxsize * i_initflag = ld_i_initflag * i_read_only = ld_i_read_only * i_remote_call = ld_i_remote_call * TABLES * i_t_select = it_i_t_select * i_t_fields = it_i_t_fields * e_t_data = it_e_t_data EXCEPTIONS NO_MORE_DATA = 1 ERROR_PASSED_TO_MESS_HANDLER = 2 . " IQM_BI_EXTRACT_REQUEST
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 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_i_requnr  TYPE SRSC_S_IF_SIMPLE-REQUNR ,
it_i_t_select  TYPE STANDARD TABLE OF SRSC_S_IF_SIMPLE-T_SELECT ,
wa_i_t_select  LIKE LINE OF it_i_t_select,
ld_i_dsource  TYPE SRSC_S_IF_SIMPLE-DSOURCE ,
it_i_t_fields  TYPE STANDARD TABLE OF SRSC_S_IF_SIMPLE-T_FIELDS ,
wa_i_t_fields  LIKE LINE OF it_i_t_fields,
ld_i_maxsize  TYPE SRSC_S_IF_SIMPLE-MAXSIZE ,
it_e_t_data  TYPE STANDARD TABLE OF RSIQMX_REQUEST ,
wa_e_t_data  LIKE LINE OF it_e_t_data,
ld_i_initflag  TYPE SRSC_S_IF_SIMPLE-INITFLAG ,
ld_i_read_only  TYPE SRSC_S_IF_SIMPLE-READONLY ,
ld_i_remote_call  TYPE SBIWA_FLAG .


ld_i_requnr = some text here

"populate fields of struture and append to itab
append wa_i_t_select to it_i_t_select.

ld_i_dsource = some text here

"populate fields of struture and append to itab
append wa_i_t_fields to it_i_t_fields.

ld_i_maxsize = some text here

"populate fields of struture and append to itab
append wa_e_t_data to it_e_t_data.

ld_i_initflag = some text here

ld_i_read_only = some text here
ld_i_remote_call = '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 IQM_BI_EXTRACT_REQUEST or its description.