SAP GRCINT_AM_DS_OBJ_QUERY Function Module for AM - Business Object Query
GRCINT_AM_DS_OBJ_QUERY is a standard grcint am ds obj query SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for AM - Business Object Query 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 grcint am ds obj query FM, simply by entering the name GRCINT_AM_DS_OBJ_QUERY into the relevant SAP transaction such as SE37 or SE38.
Function Group: GRCINT_AM_BR_OBJECT
Program Name: SAPLGRCINT_AM_BR_OBJECT
Main Program: SAPLGRCINT_AM_BR_OBJECT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function GRCINT_AM_DS_OBJ_QUERY 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 'GRCINT_AM_DS_OBJ_QUERY'"AM - Business Object Query.
EXPORTING
IV_TABNAME = "Table Name
TABLES
ET_OBJECT_LIST = "AM - Object List
IMPORTING Parameters details for GRCINT_AM_DS_OBJ_QUERY
IV_TABNAME - Table Name
Data type: TABNAMEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for GRCINT_AM_DS_OBJ_QUERY
ET_OBJECT_LIST - AM - Object List
Data type: GRCINT_S_OBJECT_LISTOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for GRCINT_AM_DS_OBJ_QUERY 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_iv_tabname | TYPE TABNAME, " | |||
| lt_et_object_list | TYPE STANDARD TABLE OF GRCINT_S_OBJECT_LIST. " |
|   CALL FUNCTION 'GRCINT_AM_DS_OBJ_QUERY' "AM - Business Object Query |
| EXPORTING | ||
| IV_TABNAME | = lv_iv_tabname | |
| TABLES | ||
| ET_OBJECT_LIST | = lt_et_object_list | |
| . " GRCINT_AM_DS_OBJ_QUERY | ||
ABAP code using 7.40 inline data declarations to call FM GRCINT_AM_DS_OBJ_QUERY
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