SAP ISU_DISCDOC_OBJECT_EXIST Function Module for Private: Disconnection Doc.: Read Object Data via Handle
ISU_DISCDOC_OBJECT_EXIST is a standard isu discdoc object exist SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Private: Disconnection Doc.: Read Object Data via Handle 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 discdoc object exist FM, simply by entering the name ISU_DISCDOC_OBJECT_EXIST into the relevant SAP transaction such as SE37 or SE38.
Function Group: ES34ALLG
Program Name: SAPLES34ALLG
Main Program: SAPLES34ALLG
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_DISCDOC_OBJECT_EXIST 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_DISCDOC_OBJECT_EXIST'"Private: Disconnection Doc.: Read Object Data via Handle.
EXPORTING
X_DISCNO = "Disconnection document number
IMPORTING
X_OBJ_EXIST = "Indicator
Y_HANDLE = "Object Identification
IMPORTING Parameters details for ISU_DISCDOC_OBJECT_EXIST
X_DISCNO - Disconnection document number
Data type: DISCNOOptional: No
Call by Reference: Yes
EXPORTING Parameters details for ISU_DISCDOC_OBJECT_EXIST
X_OBJ_EXIST - Indicator
Data type: KENNZXOptional: No
Call by Reference: Yes
Y_HANDLE - Object Identification
Data type: EBAGEN-HANDLEOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISU_DISCDOC_OBJECT_EXIST 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_discno | TYPE DISCNO, " | |||
| lv_x_obj_exist | TYPE KENNZX, " | |||
| lv_y_handle | TYPE EBAGEN-HANDLE. " |
|   CALL FUNCTION 'ISU_DISCDOC_OBJECT_EXIST' "Private: Disconnection Doc.: Read Object Data via Handle |
| EXPORTING | ||
| X_DISCNO | = lv_x_discno | |
| IMPORTING | ||
| X_OBJ_EXIST | = lv_x_obj_exist | |
| Y_HANDLE | = lv_y_handle | |
| . " ISU_DISCDOC_OBJECT_EXIST | ||
ABAP code using 7.40 inline data declarations to call FM ISU_DISCDOC_OBJECT_EXIST
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 HANDLE FROM EBAGEN INTO @DATA(ld_y_handle). | ||||
Search for further information about these or an SAP related objects