SAP ISH_NPMI_DISPATCH_MESSAGE Function Module for
ISH_NPMI_DISPATCH_MESSAGE is a standard ish npmi dispatch message 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 ish npmi dispatch message FM, simply by entering the name ISH_NPMI_DISPATCH_MESSAGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: NC20
Program Name: SAPLNC20
Main Program: SAPLNC20
Appliation area: N
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISH_NPMI_DISPATCH_MESSAGE 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 'ISH_NPMI_DISPATCH_MESSAGE'".
EXPORTING
INSTITUTION = "
EDIPROC = "
USER = "
FUNCTION_NAME = "
RFC_DESTINATION = "
* INC301B = "
CHANGING
INC301S = "
TABLES
* E_RNC301ERR = "
I_RNCMAIL = "
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_SAPLNC20_001 IS-H SG: User exit for NPMI, prior to data dispatch
IMPORTING Parameters details for ISH_NPMI_DISPATCH_MESSAGE
INSTITUTION -
Data type: NC301S-EINRIOptional: No
Call by Reference: No ( called with pass by value option)
EDIPROC -
Data type: NC301S-EDIPROCOptional: No
Call by Reference: No ( called with pass by value option)
USER -
Data type: SY-UNAMEOptional: No
Call by Reference: No ( called with pass by value option)
FUNCTION_NAME -
Data type: TNC301X-RFNAMEOUTOptional: No
Call by Reference: No ( called with pass by value option)
RFC_DESTINATION -
Data type: TNC301X-RFCDESTOptional: No
Call by Reference: No ( called with pass by value option)
INC301B -
Data type: NC301BOptional: Yes
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for ISH_NPMI_DISPATCH_MESSAGE
INC301S -
Data type: NC301SOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ISH_NPMI_DISPATCH_MESSAGE
E_RNC301ERR -
Data type: RNC301ERROptional: Yes
Call by Reference: No ( called with pass by value option)
I_RNCMAIL -
Data type: RNCMAILOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISH_NPMI_DISPATCH_MESSAGE 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_inc301s | TYPE NC301S, " | |||
| lt_e_rnc301err | TYPE STANDARD TABLE OF RNC301ERR, " | |||
| lv_institution | TYPE NC301S-EINRI, " | |||
| lv_ediproc | TYPE NC301S-EDIPROC, " | |||
| lt_i_rncmail | TYPE STANDARD TABLE OF RNCMAIL, " | |||
| lv_user | TYPE SY-UNAME, " | |||
| lv_function_name | TYPE TNC301X-RFNAMEOUT, " | |||
| lv_rfc_destination | TYPE TNC301X-RFCDEST, " | |||
| lv_inc301b | TYPE NC301B. " |
|   CALL FUNCTION 'ISH_NPMI_DISPATCH_MESSAGE' " |
| EXPORTING | ||
| INSTITUTION | = lv_institution | |
| EDIPROC | = lv_ediproc | |
| USER | = lv_user | |
| FUNCTION_NAME | = lv_function_name | |
| RFC_DESTINATION | = lv_rfc_destination | |
| INC301B | = lv_inc301b | |
| CHANGING | ||
| INC301S | = lv_inc301s | |
| TABLES | ||
| E_RNC301ERR | = lt_e_rnc301err | |
| I_RNCMAIL | = lt_i_rncmail | |
| . " ISH_NPMI_DISPATCH_MESSAGE | ||
ABAP code using 7.40 inline data declarations to call FM ISH_NPMI_DISPATCH_MESSAGE
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 EINRI FROM NC301S INTO @DATA(ld_institution). | ||||
| "SELECT single EDIPROC FROM NC301S INTO @DATA(ld_ediproc). | ||||
| "SELECT single UNAME FROM SY INTO @DATA(ld_user). | ||||
| "SELECT single RFNAMEOUT FROM TNC301X INTO @DATA(ld_function_name). | ||||
| "SELECT single RFCDEST FROM TNC301X INTO @DATA(ld_rfc_destination). | ||||
Search for further information about these or an SAP related objects