SAP IQAPI_QCALL_EXTR Function Module for









IQAPI_QCALL_EXTR is a standard iqapi qcall extr SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 iqapi qcall extr FM, simply by entering the name IQAPI_QCALL_EXTR into the relevant SAP transaction such as SE37 or SE38.

Function Group: IQAPI_QUERY_CALL
Program Name: SAPLIQAPI_QUERY_CALL
Main Program: SAPLIQAPI_QUERY_CALL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function IQAPI_QCALL_EXTR 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 'IQAPI_QCALL_EXTR'"
EXPORTING
* QUERY = "Query name
* OLD_QID = "
* EXTR_OPTIONS = "
* PACK_OPTIONS = "
* DATA_OPTIONS = "
* VARIANT = "Variant name
* FILTER = "Filter

IMPORTING
USED_VARIANT = "
DREF = "Reference to Data Table
DTAB = "
DNORM = "
DSTREAM = "Character flow
DSTRING = "Character string

EXCEPTIONS
ILLEGAL_INPUT = 1 INTERNAL_ERROR = 2 FUNCTION_NOT_POSSIBLE = 3 NO_DATA = 4 NO_AUTHORIZATION = 5
.



IMPORTING Parameters details for IQAPI_QCALL_EXTR

QUERY - Query name

Data type: IQQNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

OLD_QID -

Data type: AQLQID
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXTR_OPTIONS -

Data type: IQLEXTROPT
Optional: Yes
Call by Reference: No ( called with pass by value option)

PACK_OPTIONS -

Data type: IQLPACKOPT
Optional: Yes
Call by Reference: No ( called with pass by value option)

DATA_OPTIONS -

Data type: IQLDATAOPT
Optional: Yes
Call by Reference: No ( called with pass by value option)

VARIANT - Variant name

Data type: VARIANT
Optional: Yes
Call by Reference: No ( called with pass by value option)

FILTER - Filter

Data type: IQTFILTER
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for IQAPI_QCALL_EXTR

USED_VARIANT -

Data type: VARIANT
Optional: No
Call by Reference: No ( called with pass by value option)

DREF - Reference to Data Table

Data type: DATA
Optional: No
Call by Reference: No ( called with pass by value option)

DTAB -

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

DNORM -

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

DSTREAM - Character flow

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

DSTRING - Character string

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

EXCEPTIONS details

ILLEGAL_INPUT -

Data type:
Optional: No
Call by Reference: Yes

INTERNAL_ERROR - Internal Error

Data type:
Optional: No
Call by Reference: Yes

FUNCTION_NOT_POSSIBLE -

Data type:
Optional: No
Call by Reference: Yes

NO_DATA -

Data type:
Optional: No
Call by Reference: Yes

NO_AUTHORIZATION -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for IQAPI_QCALL_EXTR 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_query  TYPE IQQNAME, "   
lv_used_variant  TYPE VARIANT, "   
lv_illegal_input  TYPE VARIANT, "   
lv_dref  TYPE DATA, "   
lv_old_qid  TYPE AQLQID, "   
lv_internal_error  TYPE AQLQID, "   
lv_dtab  TYPE TABLE, "   
lv_extr_options  TYPE IQLEXTROPT, "   
lv_function_not_possible  TYPE IQLEXTROPT, "   
lv_dnorm  TYPE IQTDNORM, "   
lv_no_data  TYPE IQTDNORM, "   
lv_pack_options  TYPE IQLPACKOPT, "   
lv_dstream  TYPE IQTSTREAM, "   
lv_data_options  TYPE IQLDATAOPT, "   
lv_no_authorization  TYPE IQLDATAOPT, "   
lv_dstring  TYPE STRING, "   
lv_variant  TYPE VARIANT, "   
lv_filter  TYPE IQTFILTER. "   

  CALL FUNCTION 'IQAPI_QCALL_EXTR'  "
    EXPORTING
         QUERY = lv_query
         OLD_QID = lv_old_qid
         EXTR_OPTIONS = lv_extr_options
         PACK_OPTIONS = lv_pack_options
         DATA_OPTIONS = lv_data_options
         VARIANT = lv_variant
         FILTER = lv_filter
    IMPORTING
         USED_VARIANT = lv_used_variant
         DREF = lv_dref
         DTAB = lv_dtab
         DNORM = lv_dnorm
         DSTREAM = lv_dstream
         DSTRING = lv_dstring
    EXCEPTIONS
        ILLEGAL_INPUT = 1
        INTERNAL_ERROR = 2
        FUNCTION_NOT_POSSIBLE = 3
        NO_DATA = 4
        NO_AUTHORIZATION = 5
. " IQAPI_QCALL_EXTR




ABAP code using 7.40 inline data declarations to call FM IQAPI_QCALL_EXTR

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



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!