SAP OXT_GENOBJDEF_GET Function Module for
OXT_GENOBJDEF_GET is a standard oxt genobjdef get 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 oxt genobjdef get FM, simply by entering the name OXT_GENOBJDEF_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: OXT_TASK_API
Program Name: SAPLOXT_TASK_API
Main Program: SAPLOXT_TASK_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function OXT_GENOBJDEF_GET 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 'OXT_GENOBJDEF_GET'".
EXPORTING
I_TASKID = "ID of OXT Task
IMPORTING
E_GOX_HEADER = "Table for Generic Object Extension (Header)
EXCEPTIONS
TASK_NOT_FOUND = 1
IMPORTING Parameters details for OXT_GENOBJDEF_GET
I_TASKID - ID of OXT Task
Data type: OXT_TASKIDOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for OXT_GENOBJDEF_GET
E_GOX_HEADER - Table for Generic Object Extension (Header)
Data type: COMT_GOX_DEF_HEADEROptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
TASK_NOT_FOUND - Task Not Found
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for OXT_GENOBJDEF_GET 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_i_taskid | TYPE OXT_TASKID, " | |||
| lv_e_gox_header | TYPE COMT_GOX_DEF_HEADER, " | |||
| lv_task_not_found | TYPE COMT_GOX_DEF_HEADER. " |
|   CALL FUNCTION 'OXT_GENOBJDEF_GET' " |
| EXPORTING | ||
| I_TASKID | = lv_i_taskid | |
| IMPORTING | ||
| E_GOX_HEADER | = lv_e_gox_header | |
| EXCEPTIONS | ||
| TASK_NOT_FOUND = 1 | ||
| . " OXT_GENOBJDEF_GET | ||
ABAP code using 7.40 inline data declarations to call FM OXT_GENOBJDEF_GET
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