SAP ISM_SE_GET_INTERRUPTION_DATA2 Function Module for
ISM_SE_GET_INTERRUPTION_DATA2 is a standard ism se get interruption data2 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 ism se get interruption data2 FM, simply by entering the name ISM_SE_GET_INTERRUPTION_DATA2 into the relevant SAP transaction such as SE37 or SE38.
Function Group: JKSEORDER03
Program Name: SAPLJKSEORDER03
Main Program: SAPLJKSEORDER03
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISM_SE_GET_INTERRUPTION_DATA2 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 'ISM_SE_GET_INTERRUPTION_DATA2'".
EXPORTING
IN_VBELN = "
IN_POSNR = "
IN_DATE = "
IMPORTING
OUT_INTERRUPTION = "
IMPORTING Parameters details for ISM_SE_GET_INTERRUPTION_DATA2
IN_VBELN -
Data type: VBAK-VBELNOptional: No
Call by Reference: Yes
IN_POSNR -
Data type: VBAP-POSNROptional: No
Call by Reference: Yes
IN_DATE -
Data type: SY-DATUMOptional: No
Call by Reference: Yes
EXPORTING Parameters details for ISM_SE_GET_INTERRUPTION_DATA2
OUT_INTERRUPTION -
Data type: JKSEINTERRUPTOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISM_SE_GET_INTERRUPTION_DATA2 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_in_vbeln | TYPE VBAK-VBELN, " | |||
| lv_out_interruption | TYPE JKSEINTERRUPT, " | |||
| lv_in_posnr | TYPE VBAP-POSNR, " | |||
| lv_in_date | TYPE SY-DATUM. " |
|   CALL FUNCTION 'ISM_SE_GET_INTERRUPTION_DATA2' " |
| EXPORTING | ||
| IN_VBELN | = lv_in_vbeln | |
| IN_POSNR | = lv_in_posnr | |
| IN_DATE | = lv_in_date | |
| IMPORTING | ||
| OUT_INTERRUPTION | = lv_out_interruption | |
| . " ISM_SE_GET_INTERRUPTION_DATA2 | ||
ABAP code using 7.40 inline data declarations to call FM ISM_SE_GET_INTERRUPTION_DATA2
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 VBELN FROM VBAK INTO @DATA(ld_in_vbeln). | ||||
| "SELECT single POSNR FROM VBAP INTO @DATA(ld_in_posnr). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_in_date). | ||||
Search for further information about these or an SAP related objects