SAP ISU_M_DISCON_EVENT_CREATE Function Module for IS-U Migration: Create Event
ISU_M_DISCON_EVENT_CREATE is a standard isu m discon event create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-U Migration: Create Event 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 m discon event create FM, simply by entering the name ISU_M_DISCON_EVENT_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: ISU_M_DISCONNECTION
Program Name: SAPLISU_M_DISCONNECTION
Main Program: SAPLISU_M_DISCONNECTION
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_M_DISCON_EVENT_CREATE 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_M_DISCON_EVENT_CREATE'"IS-U Migration: Create Event.
EXPORTING
* X_LANGUAGE = "SAP System, Current Language
X_AUTO = "IS-U Migration: Automation Data DISCON* (Discon.Documents)
IMPORTING
Y_EDISCDOC = "Disconnection document
Y_EVENT_ID = "Event
Y_DB_UPDATE = "Indicator
EXCEPTIONS
INPUT_ERROR = 1 SYSTEM_ERROR = 2
IMPORTING Parameters details for ISU_M_DISCON_EVENT_CREATE
X_LANGUAGE - SAP System, Current Language
Data type: SY-LANGUOptional: Yes
Call by Reference: Yes
X_AUTO - IS-U Migration: Automation Data DISCON* (Discon.Documents)
Data type: EMG_DISCONNECTION_AUTOOptional: No
Call by Reference: Yes
EXPORTING Parameters details for ISU_M_DISCON_EVENT_CREATE
Y_EDISCDOC - Disconnection document
Data type: EDISCDOCOptional: No
Call by Reference: Yes
Y_EVENT_ID - Event
Data type: SWR_STRUCT-EVENT_IDOptional: No
Call by Reference: Yes
Y_DB_UPDATE - Indicator
Data type: EMGGEN-KENNZXOptional: No
Call by Reference: Yes
EXCEPTIONS details
INPUT_ERROR -
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_M_DISCON_EVENT_CREATE 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_language | TYPE SY-LANGU, " | |||
| lv_y_ediscdoc | TYPE EDISCDOC, " | |||
| lv_input_error | TYPE EDISCDOC, " | |||
| lv_x_auto | TYPE EMG_DISCONNECTION_AUTO, " | |||
| lv_y_event_id | TYPE SWR_STRUCT-EVENT_ID, " | |||
| lv_system_error | TYPE SWR_STRUCT, " | |||
| lv_y_db_update | TYPE EMGGEN-KENNZX. " |
|   CALL FUNCTION 'ISU_M_DISCON_EVENT_CREATE' "IS-U Migration: Create Event |
| EXPORTING | ||
| X_LANGUAGE | = lv_x_language | |
| X_AUTO | = lv_x_auto | |
| IMPORTING | ||
| Y_EDISCDOC | = lv_y_ediscdoc | |
| Y_EVENT_ID | = lv_y_event_id | |
| Y_DB_UPDATE | = lv_y_db_update | |
| EXCEPTIONS | ||
| INPUT_ERROR = 1 | ||
| SYSTEM_ERROR = 2 | ||
| . " ISU_M_DISCON_EVENT_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM ISU_M_DISCON_EVENT_CREATE
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 LANGU FROM SY INTO @DATA(ld_x_language). | ||||
| "SELECT single EVENT_ID FROM SWR_STRUCT INTO @DATA(ld_y_event_id). | ||||
| "SELECT single KENNZX FROM EMGGEN INTO @DATA(ld_y_db_update). | ||||
Search for further information about these or an SAP related objects