SAP EHSWA_210_DISPATCH Function Module for









EHSWA_210_DISPATCH is a standard ehswa 210 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 ehswa 210 dispatch FM, simply by entering the name EHSWA_210_DISPATCH into the relevant SAP transaction such as SE37 or SE38.

Function Group: EHSWA_210
Program Name: SAPLEHSWA_210
Main Program: SAPLEHSWA_210
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function EHSWA_210_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 'EHSWA_210_DISPATCH'"
EXPORTING
* I_NO_UPDATE_TREE = "

TABLES
I_MN_API = "
.



IMPORTING Parameters details for EHSWA_210_DISPATCH

I_NO_UPDATE_TREE -

Data type:
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for EHSWA_210_DISPATCH

I_MN_API -

Data type: EHSWAS_MNAPI
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for EHSWA_210_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_mn_api  TYPE STANDARD TABLE OF EHSWAS_MNAPI, "   
lv_i_no_update_tree  TYPE EHSWAS_MNAPI. "   

  CALL FUNCTION 'EHSWA_210_DISPATCH'  "
    EXPORTING
         I_NO_UPDATE_TREE = lv_i_no_update_tree
    TABLES
         I_MN_API = lt_i_mn_api
. " EHSWA_210_DISPATCH




ABAP code using 7.40 inline data declarations to call FM EHSWA_210_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.

 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!