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

Function ISHCM_ORDER_DISPATCH 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 'ISHCM_ORDER_DISPATCH'".
EXPORTING
* COLLECT_AND_WAIT = ' ' "
* DESTSYSTEM = ' ' "Fixed target system, if specified (optional)
* DO_INDEPENDENT_OF_TN00E = ' ' "Create order also with interactive msg dispatch
* DO_INDEPENDENT_OF_TN02S = ' ' "Create order also with blocked systems
EINRI = "Institution of event reporter (mandatory)
* TESTKZ = ' ' "Indicator for test dispatch orders (optional)
IMPORTING
HCM_DIRECT_SEND = "Indicator whether direct dispatch is active
TABLES
I_ORDERS = "Order Data (Events + Movements)
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_SAPLNCOM_001 IS-HCM: Enhance/modify dispatch control for customers
IMPORTING Parameters details for ISHCM_ORDER_DISPATCH
COLLECT_AND_WAIT -
Data type: RNCOM-XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
DESTSYSTEM - Fixed target system, if specified (optional)
Data type: NC00-DESTSYSTEMDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
DO_INDEPENDENT_OF_TN00E - Create order also with interactive msg dispatch
Data type: RNCOM-XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
DO_INDEPENDENT_OF_TN02S - Create order also with blocked systems
Data type: RNCOM-XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EINRI - Institution of event reporter (mandatory)
Data type: NC01-EINRIOptional: No
Call by Reference: No ( called with pass by value option)
TESTKZ - Indicator for test dispatch orders (optional)
Data type: NC01-TESTORDSGNDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISHCM_ORDER_DISPATCH
HCM_DIRECT_SEND - Indicator whether direct dispatch is active
Data type: TN02S-KZDELIVEROptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ISHCM_ORDER_DISPATCH
I_ORDERS - Order Data (Events + Movements)
Data type: RNCORDEROptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISHCM_ORDER_DISPATCH 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: | ||||
| lt_i_orders | TYPE STANDARD TABLE OF RNCORDER, " | |||
| lv_hcm_direct_send | TYPE TN02S-KZDELIVER, " | |||
| lv_collect_and_wait | TYPE RNCOM-XFELD, " SPACE | |||
| lv_destsystem | TYPE NC00-DESTSYSTEM, " SPACE | |||
| lv_do_independent_of_tn00e | TYPE RNCOM-XFELD, " SPACE | |||
| lv_do_independent_of_tn02s | TYPE RNCOM-XFELD, " SPACE | |||
| lv_einri | TYPE NC01-EINRI, " | |||
| lv_testkz | TYPE NC01-TESTORDSGN. " SPACE |
|   CALL FUNCTION 'ISHCM_ORDER_DISPATCH' " |
| EXPORTING | ||
| COLLECT_AND_WAIT | = lv_collect_and_wait | |
| DESTSYSTEM | = lv_destsystem | |
| DO_INDEPENDENT_OF_TN00E | = lv_do_independent_of_tn00e | |
| DO_INDEPENDENT_OF_TN02S | = lv_do_independent_of_tn02s | |
| EINRI | = lv_einri | |
| TESTKZ | = lv_testkz | |
| IMPORTING | ||
| HCM_DIRECT_SEND | = lv_hcm_direct_send | |
| TABLES | ||
| I_ORDERS | = lt_i_orders | |
| . " ISHCM_ORDER_DISPATCH | ||
ABAP code using 7.40 inline data declarations to call FM ISHCM_ORDER_DISPATCH
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 KZDELIVER FROM TN02S INTO @DATA(ld_hcm_direct_send). | ||||
| "SELECT single XFELD FROM RNCOM INTO @DATA(ld_collect_and_wait). | ||||
| DATA(ld_collect_and_wait) | = ' '. | |||
| "SELECT single DESTSYSTEM FROM NC00 INTO @DATA(ld_destsystem). | ||||
| DATA(ld_destsystem) | = ' '. | |||
| "SELECT single XFELD FROM RNCOM INTO @DATA(ld_do_independent_of_tn00e). | ||||
| DATA(ld_do_independent_of_tn00e) | = ' '. | |||
| "SELECT single XFELD FROM RNCOM INTO @DATA(ld_do_independent_of_tn02s). | ||||
| DATA(ld_do_independent_of_tn02s) | = ' '. | |||
| "SELECT single EINRI FROM NC01 INTO @DATA(ld_einri). | ||||
| "SELECT single TESTORDSGN FROM NC01 INTO @DATA(ld_testkz). | ||||
| DATA(ld_testkz) | = ' '. | |||
Search for further information about these or an SAP related objects