SAP ISU_CHANGEDOCUMENT_DISPLAY Function Module for
ISU_CHANGEDOCUMENT_DISPLAY is a standard isu changedocument display 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 isu changedocument display FM, simply by entering the name ISU_CHANGEDOCUMENT_DISPLAY into the relevant SAP transaction such as SE37 or SE38.
Function Group: ECD0
Program Name: SAPLECD0
Main Program: SAPLECD0
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_CHANGEDOCUMENT_DISPLAY 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_CHANGEDOCUMENT_DISPLAY'".
EXPORTING
X_OBJECTCLAS = "
X_OBJECTID = "
* X_USERNAME = "
* X_UDATE = "
* X_UTIME = "
* X_TABNAME = "
* X_FNAME = "
* X_TCODE = "
* X_NO_TABLE_LINE = ' ' "
EXCEPTIONS
AUTHORIZATION_FAILED = 1 OBJCLASS_INVALID = 2 POSITION_NOT_FOUND = 3 SYSTEM_ERROR = 4
IMPORTING Parameters details for ISU_CHANGEDOCUMENT_DISPLAY
X_OBJECTCLAS -
Data type: CDHDR-OBJECTCLASOptional: No
Call by Reference: No ( called with pass by value option)
X_OBJECTID -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
X_USERNAME -
Data type: CDRED-USERNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
X_UDATE -
Data type: CDRED-UDATEOptional: Yes
Call by Reference: No ( called with pass by value option)
X_UTIME -
Data type: CDRED-UTIMEOptional: Yes
Call by Reference: No ( called with pass by value option)
X_TABNAME -
Data type: CDRED-TABNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
X_FNAME -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
X_TCODE -
Data type: CDRED-TCODEOptional: Yes
Call by Reference: No ( called with pass by value option)
X_NO_TABLE_LINE -
Data type: REGEN-KENNZXDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
AUTHORIZATION_FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OBJCLASS_INVALID -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
POSITION_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SYSTEM_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISU_CHANGEDOCUMENT_DISPLAY 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_objectclas | TYPE CDHDR-OBJECTCLAS, " | |||
| lv_authorization_failed | TYPE CDHDR, " | |||
| lv_x_objectid | TYPE CDHDR, " | |||
| lv_objclass_invalid | TYPE CDHDR, " | |||
| lv_x_username | TYPE CDRED-USERNAME, " | |||
| lv_position_not_found | TYPE CDRED, " | |||
| lv_x_udate | TYPE CDRED-UDATE, " | |||
| lv_system_error | TYPE CDRED, " | |||
| lv_x_utime | TYPE CDRED-UTIME, " | |||
| lv_x_tabname | TYPE CDRED-TABNAME, " | |||
| lv_x_fname | TYPE CDRED, " | |||
| lv_x_tcode | TYPE CDRED-TCODE, " | |||
| lv_x_no_table_line | TYPE REGEN-KENNZX. " SPACE |
|   CALL FUNCTION 'ISU_CHANGEDOCUMENT_DISPLAY' " |
| EXPORTING | ||
| X_OBJECTCLAS | = lv_x_objectclas | |
| X_OBJECTID | = lv_x_objectid | |
| X_USERNAME | = lv_x_username | |
| X_UDATE | = lv_x_udate | |
| X_UTIME | = lv_x_utime | |
| X_TABNAME | = lv_x_tabname | |
| X_FNAME | = lv_x_fname | |
| X_TCODE | = lv_x_tcode | |
| X_NO_TABLE_LINE | = lv_x_no_table_line | |
| EXCEPTIONS | ||
| AUTHORIZATION_FAILED = 1 | ||
| OBJCLASS_INVALID = 2 | ||
| POSITION_NOT_FOUND = 3 | ||
| SYSTEM_ERROR = 4 | ||
| . " ISU_CHANGEDOCUMENT_DISPLAY | ||
ABAP code using 7.40 inline data declarations to call FM ISU_CHANGEDOCUMENT_DISPLAY
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 OBJECTCLAS FROM CDHDR INTO @DATA(ld_x_objectclas). | ||||
| "SELECT single USERNAME FROM CDRED INTO @DATA(ld_x_username). | ||||
| "SELECT single UDATE FROM CDRED INTO @DATA(ld_x_udate). | ||||
| "SELECT single UTIME FROM CDRED INTO @DATA(ld_x_utime). | ||||
| "SELECT single TABNAME FROM CDRED INTO @DATA(ld_x_tabname). | ||||
| "SELECT single TCODE FROM CDRED INTO @DATA(ld_x_tcode). | ||||
| "SELECT single KENNZX FROM REGEN INTO @DATA(ld_x_no_table_line). | ||||
| DATA(ld_x_no_table_line) | = ' '. | |||
Search for further information about these or an SAP related objects