SAP FDT_OBJECT_QUERY Function Module for FDT: Object query in a remote system
FDT_OBJECT_QUERY is a standard fdt object 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 FDT: Object query in a remote system 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 fdt object query FM, simply by entering the name FDT_OBJECT_QUERY into the relevant SAP transaction such as SE37 or SE38.
Function Group: FDT_REMOTE_QUERY
Program Name: SAPLFDT_REMOTE_QUERY
Main Program: SAPLFDT_REMOTE_QUERY
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function FDT_OBJECT_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 'FDT_OBJECT_QUERY'"FDT: Object query in a remote system.
EXPORTING
* IT_AP_SELECTION = "Audit Trail (ILM): Field Names (Sel. Tab.)
* IT_ID_SELECTION = "Audit Trail (ILM): Field Names (Sel. Tab.)
* IV_CUSTOMIZING_OBJECTS = ABAP_TRUE "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
* IV_SYSTEM_OBJECTS = ABAP_TRUE "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
* IV_FAST_MODE = ABAP_FALSE "Fast mode - without determination of object description
IMPORTING
ET_OBJECT_DATA = "FDT: Table for the remote object query
IMPORTING Parameters details for FDT_OBJECT_QUERY
IT_AP_SELECTION - Audit Trail (ILM): Field Names (Sel. Tab.)
Data type: FDT_T_SELECTIONOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_ID_SELECTION - Audit Trail (ILM): Field Names (Sel. Tab.)
Data type: FDT_T_SELECTIONOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_CUSTOMIZING_OBJECTS - Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
Data type: BOOLE_DDefault: ABAP_TRUE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_SYSTEM_OBJECTS - Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
Data type: BOOLE_DDefault: ABAP_TRUE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_FAST_MODE - Fast mode - without determination of object description
Data type: BOOLE_DDefault: ABAP_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FDT_OBJECT_QUERY
ET_OBJECT_DATA - FDT: Table for the remote object query
Data type: FDT_T_OBJECT_DATAOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FDT_OBJECT_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_et_object_data | TYPE FDT_T_OBJECT_DATA, " | |||
| lv_it_ap_selection | TYPE FDT_T_SELECTION, " | |||
| lv_it_id_selection | TYPE FDT_T_SELECTION, " | |||
| lv_iv_customizing_objects | TYPE BOOLE_D, " ABAP_TRUE | |||
| lv_iv_system_objects | TYPE BOOLE_D, " ABAP_TRUE | |||
| lv_iv_fast_mode | TYPE BOOLE_D. " ABAP_FALSE |
|   CALL FUNCTION 'FDT_OBJECT_QUERY' "FDT: Object query in a remote system |
| EXPORTING | ||
| IT_AP_SELECTION | = lv_it_ap_selection | |
| IT_ID_SELECTION | = lv_it_id_selection | |
| IV_CUSTOMIZING_OBJECTS | = lv_iv_customizing_objects | |
| IV_SYSTEM_OBJECTS | = lv_iv_system_objects | |
| IV_FAST_MODE | = lv_iv_fast_mode | |
| IMPORTING | ||
| ET_OBJECT_DATA | = lv_et_object_data | |
| . " FDT_OBJECT_QUERY | ||
ABAP code using 7.40 inline data declarations to call FM FDT_OBJECT_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.| DATA(ld_iv_customizing_objects) | = ABAP_TRUE. | |||
| DATA(ld_iv_system_objects) | = ABAP_TRUE. | |||
| DATA(ld_iv_fast_mode) | = ABAP_FALSE. | |||
Search for further information about these or an SAP related objects