SAP ISU_DISCDOC_BOL_STATUS Function Module for
ISU_DISCDOC_BOL_STATUS is a standard isu discdoc bol status 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 bol status FM, simply by entering the name ISU_DISCDOC_BOL_STATUS 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): Normal Function Module
Update:

Function ISU_DISCDOC_BOL_STATUS 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_BOL_STATUS'".
EXPORTING
X_ANLAGE = "Installation
* X_KEYDATE = SY-DATUM "Attribute Value
* X_KEYTIME = SY-UZEIT "Current Time of Application Server
IMPORTING
Y_EANLDISCST = "Header Information of Disconnection Status
Y_EDISCOBJ_TAB = "Standard Table for V_EDISCOBJ Category
Y_EDISCDOC_TAB = "
Y_EDISCACT_TAB = "
YT_MSG = "Return Table
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_BOL_STATUS
X_ANLAGE - Installation
Data type: ANLAGEOptional: No
Call by Reference: Yes
X_KEYDATE - Attribute Value
Data type: V_EDISCOBJ-ABDefault: SY-DATUM
Optional: Yes
Call by Reference: Yes
X_KEYTIME - Current Time of Application Server
Data type: V_EDISCOBJ-AB_TIMEDefault: SY-UZEIT
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for ISU_DISCDOC_BOL_STATUS
Y_EANLDISCST - Header Information of Disconnection Status
Data type: DISC_HEADTXTOptional: No
Call by Reference: No ( called with pass by value option)
Y_EDISCOBJ_TAB - Standard Table for V_EDISCOBJ Category
Data type: V_EDISCOBJ_TABOptional: No
Call by Reference: No ( called with pass by value option)
Y_EDISCDOC_TAB -
Data type: ISU_EDISCDOC_TABOptional: No
Call by Reference: No ( called with pass by value option)
Y_EDISCACT_TAB -
Data type: ISU_EDISCACT_TABOptional: 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)
Copy and paste ABAP code example for ISU_DISCDOC_BOL_STATUS 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_anlage | TYPE ANLAGE, " | |||
| lv_y_eanldiscst | TYPE DISC_HEADTXT, " | |||
| lv_x_keydate | TYPE V_EDISCOBJ-AB, " SY-DATUM | |||
| lv_y_ediscobj_tab | TYPE V_EDISCOBJ_TAB, " | |||
| lv_x_keytime | TYPE V_EDISCOBJ-AB_TIME, " SY-UZEIT | |||
| lv_y_ediscdoc_tab | TYPE ISU_EDISCDOC_TAB, " | |||
| lv_y_ediscact_tab | TYPE ISU_EDISCACT_TAB, " | |||
| lv_yt_msg | TYPE BAPIRET2_T. " |
|   CALL FUNCTION 'ISU_DISCDOC_BOL_STATUS' " |
| EXPORTING | ||
| X_ANLAGE | = lv_x_anlage | |
| X_KEYDATE | = lv_x_keydate | |
| X_KEYTIME | = lv_x_keytime | |
| IMPORTING | ||
| Y_EANLDISCST | = lv_y_eanldiscst | |
| Y_EDISCOBJ_TAB | = lv_y_ediscobj_tab | |
| Y_EDISCDOC_TAB | = lv_y_ediscdoc_tab | |
| Y_EDISCACT_TAB | = lv_y_ediscact_tab | |
| YT_MSG | = lv_yt_msg | |
| . " ISU_DISCDOC_BOL_STATUS | ||
ABAP code using 7.40 inline data declarations to call FM ISU_DISCDOC_BOL_STATUS
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 AB FROM V_EDISCOBJ INTO @DATA(ld_x_keydate). | ||||
| DATA(ld_x_keydate) | = SY-DATUM. | |||
| "SELECT single AB_TIME FROM V_EDISCOBJ INTO @DATA(ld_x_keytime). | ||||
| DATA(ld_x_keytime) | = SY-UZEIT. | |||
Search for further information about these or an SAP related objects