SAP ISU_DATEX_DEFINITION_SET_OBJ Function Module for Set Instance for Dialog Processing
ISU_DATEX_DEFINITION_SET_OBJ is a standard isu datex definition set obj SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Set Instance for Dialog Processing 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 isu datex definition set obj FM, simply by entering the name ISU_DATEX_DEFINITION_SET_OBJ into the relevant SAP transaction such as SE37 or SE38.
Function Group: EDATEX_DEFINITION
Program Name: SAPLEDATEX_DEFINITION
Main Program: SAPLEDATEX_DEFINITION
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_DATEX_DEFINITION_SET_OBJ 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 'ISU_DATEX_DEFINITION_SET_OBJ'"Set Instance for Dialog Processing.
EXPORTING
X_DEXDEF = "Data Exchange Definition
* X_NO_SCREEN = "Indicator
IMPORTING Parameters details for ISU_DATEX_DEFINITION_SET_OBJ
X_DEXDEF - Data Exchange Definition
Data type: CL_ISU_DATEX_DEFINITIONOptional: No
Call by Reference: Yes
X_NO_SCREEN - Indicator
Data type: KENNZXOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for ISU_DATEX_DEFINITION_SET_OBJ 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_x_dexdef | TYPE CL_ISU_DATEX_DEFINITION, " | |||
| lv_x_no_screen | TYPE KENNZX. " |
|   CALL FUNCTION 'ISU_DATEX_DEFINITION_SET_OBJ' "Set Instance for Dialog Processing |
| EXPORTING | ||
| X_DEXDEF | = lv_x_dexdef | |
| X_NO_SCREEN | = lv_x_no_screen | |
| . " ISU_DATEX_DEFINITION_SET_OBJ | ||
ABAP code using 7.40 inline data declarations to call FM ISU_DATEX_DEFINITION_SET_OBJ
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