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

Function ISU_DISCDOC_CREATE_REMOVE 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_CREATE_REMOVE'".
CHANGING
XY_OBJ = "
ERR = "
TABLES
XT_EDISCORDSTATE = "
EXCEPTIONS
ACTION_FAILED = 1
CHANGING Parameters details for ISU_DISCDOC_CREATE_REMOVE
XY_OBJ -
Data type: ISU05_DISCDOC_INTERNALOptional: No
Call by Reference: Yes
ERR -
Data type: ISU05_ERROROptional: No
Call by Reference: Yes
TABLES Parameters details for ISU_DISCDOC_CREATE_REMOVE
XT_EDISCORDSTATE -
Data type: V_EDISCORDSTATEOptional: No
Call by Reference: Yes
EXCEPTIONS details
ACTION_FAILED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISU_DISCDOC_CREATE_REMOVE 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_xy_obj | TYPE ISU05_DISCDOC_INTERNAL, " | |||
| lv_action_failed | TYPE ISU05_DISCDOC_INTERNAL, " | |||
| lt_xt_ediscordstate | TYPE STANDARD TABLE OF V_EDISCORDSTATE, " | |||
| lv_err | TYPE ISU05_ERROR. " |
|   CALL FUNCTION 'ISU_DISCDOC_CREATE_REMOVE' " |
| CHANGING | ||
| XY_OBJ | = lv_xy_obj | |
| ERR | = lv_err | |
| TABLES | ||
| XT_EDISCORDSTATE | = lt_xt_ediscordstate | |
| EXCEPTIONS | ||
| ACTION_FAILED = 1 | ||
| . " ISU_DISCDOC_CREATE_REMOVE | ||
ABAP code using 7.40 inline data declarations to call FM ISU_DISCDOC_CREATE_REMOVE
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