SAP ISR_SHOW_STATUS Function Module for
ISR_SHOW_STATUS is a standard isr show 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 isr show status FM, simply by entering the name ISR_SHOW_STATUS into the relevant SAP transaction such as SE37 or SE38.
Function Group: MPO_46CFF_ISR_SERVICE
Program Name: SAPLMPO_46CFF_ISR_SERVICE
Main Program: SAPLMPO_46CFF_ISR_SERVICE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISR_SHOW_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 'ISR_SHOW_STATUS'".
EXPORTING
NOTIF_NO_IN = "
MODE_IN = "
CHANGING
CT_ADDITIONAL_DATA = "
IMPORTING Parameters details for ISR_SHOW_STATUS
NOTIF_NO_IN -
Data type: QMNUMOptional: No
Call by Reference: Yes
MODE_IN -
Data type: QISRDMODEOptional: No
Call by Reference: Yes
CHANGING Parameters details for ISR_SHOW_STATUS
CT_ADDITIONAL_DATA -
Data type: QISRTSPECIAL_PARAMOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISR_SHOW_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_notif_no_in | TYPE QMNUM, " | |||
| lv_ct_additional_data | TYPE QISRTSPECIAL_PARAM, " | |||
| lv_mode_in | TYPE QISRDMODE. " |
|   CALL FUNCTION 'ISR_SHOW_STATUS' " |
| EXPORTING | ||
| NOTIF_NO_IN | = lv_notif_no_in | |
| MODE_IN | = lv_mode_in | |
| CHANGING | ||
| CT_ADDITIONAL_DATA | = lv_ct_additional_data | |
| . " ISR_SHOW_STATUS | ||
ABAP code using 7.40 inline data declarations to call FM ISR_SHOW_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.Search for further information about these or an SAP related objects