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

Function ISU_DISCDOC_REMOTE_SAVE 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_REMOTE_SAVE'".
EXPORTING
X_DISCNO = "
IMPORTING
Y_SUCCESS = "Indicator
YT_MSG = "Return Table
EXCEPTIONS
ACTION_FAILED = 1
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLEDCN_001 User Exit for Determining Processsing Variants for Disconnection Document
EXIT_SAPLEDCN_002 Uer exit for user-defined authorization check in disconnection document
EXIT_SAPLEDCN_003 USer Exit for Determining Contract for Disconnection Charges
IMPORTING Parameters details for ISU_DISCDOC_REMOTE_SAVE
X_DISCNO -
Data type: DISCNOOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISU_DISCDOC_REMOTE_SAVE
Y_SUCCESS - Indicator
Data type: KENNZXOptional: No
Call by Reference: No ( called with pass by value option)
YT_MSG - Return Table
Data type: BAPIRET2_TOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ACTION_FAILED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISU_DISCDOC_REMOTE_SAVE 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_y_success | TYPE KENNZX, " | |||
| lv_action_failed | TYPE KENNZX, " | |||
| lv_yt_msg | TYPE BAPIRET2_T. " |
|   CALL FUNCTION 'ISU_DISCDOC_REMOTE_SAVE' " |
| EXPORTING | ||
| X_DISCNO | = lv_x_discno | |
| IMPORTING | ||
| Y_SUCCESS | = lv_y_success | |
| YT_MSG | = lv_yt_msg | |
| EXCEPTIONS | ||
| ACTION_FAILED = 1 | ||
| . " ISU_DISCDOC_REMOTE_SAVE | ||
ABAP code using 7.40 inline data declarations to call FM ISU_DISCDOC_REMOTE_SAVE
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