SAP QUERY_GET_OPERATION Function Module for
QUERY_GET_OPERATION is a standard query get operation 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 query get operation FM, simply by entering the name QUERY_GET_OPERATION into the relevant SAP transaction such as SE37 or SE38.
Function Group: SVIX
Program Name: SAPLSVIX
Main Program: SAPLSVIX
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function QUERY_GET_OPERATION 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 'QUERY_GET_OPERATION'".
EXPORTING
TABLE = "Name of Strucktur in the DDIC
TABLES
EXCLUDE_FIELDS = "Fields which should be excluded
EXCEPTIONS
CANCELLED_BY_USER = 1 NO_VALID_FIELDS = 2 TABLE_NOT_FOUND = 3
IMPORTING Parameters details for QUERY_GET_OPERATION
TABLE - Name of Strucktur in the DDIC
Data type: OCUS-TABLEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for QUERY_GET_OPERATION
EXCLUDE_FIELDS - Fields which should be excluded
Data type: VIMEXCLFLDOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
CANCELLED_BY_USER - Abnormal termination of dialog by
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_VALID_FIELDS - no fields allowed for query function available
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TABLE_NOT_FOUND - Strucktur not known in the DDIC
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for QUERY_GET_OPERATION 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_table | TYPE OCUS-TABLE, " | |||
lt_exclude_fields | TYPE STANDARD TABLE OF VIMEXCLFLD, " | |||
lv_cancelled_by_user | TYPE VIMEXCLFLD, " | |||
lv_no_valid_fields | TYPE VIMEXCLFLD, " | |||
lv_table_not_found | TYPE VIMEXCLFLD. " |
  CALL FUNCTION 'QUERY_GET_OPERATION' " |
EXPORTING | ||
TABLE | = lv_table | |
TABLES | ||
EXCLUDE_FIELDS | = lt_exclude_fields | |
EXCEPTIONS | ||
CANCELLED_BY_USER = 1 | ||
NO_VALID_FIELDS = 2 | ||
TABLE_NOT_FOUND = 3 | ||
. " QUERY_GET_OPERATION |
ABAP code using 7.40 inline data declarations to call FM QUERY_GET_OPERATION
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."SELECT single TABLE FROM OCUS INTO @DATA(ld_table). | ||||
Search for further information about these or an SAP related objects