SAP ISH_EDI_MESSAGE_HANDLER Function Module for









ISH_EDI_MESSAGE_HANDLER is a standard ish edi message handler 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 edi message handler FM, simply by entering the name ISH_EDI_MESSAGE_HANDLER into the relevant SAP transaction such as SE37 or SE38.

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



Function ISH_EDI_MESSAGE_HANDLER 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_EDI_MESSAGE_HANDLER'"
EXPORTING
MSGTY = "
* I_FUNCTION = ' ' "
* I_RSTATUS = ' ' "
* I_ECODE = ' ' "
* I_TCODE = ' ' "
* I_MANDFLD = ' ' "
* I_ERRSGM = ' ' "
* I_ERRSGMPOS = ' ' "
* I_ERRFLDPOS = ' ' "
ARBGB = "
MSGNR = "
* MSGV1 = ' ' "
* MSGV2 = ' ' "
* MSGV3 = ' ' "
* MSGV4 = ' ' "
* I_UCONTROL_ENABLED = ' ' "
* I_INSTITUTION = ' ' "

IMPORTING
E_MSGTY = "
.



IMPORTING Parameters details for ISH_EDI_MESSAGE_HANDLER

MSGTY -

Data type: RNC301ERR-MSGTY
Optional: No
Call by Reference: No ( called with pass by value option)

I_FUNCTION -

Data type: TN21M-FUNKT
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_RSTATUS -

Data type: RNC301ERR-RSTATUS
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_ECODE -

Data type: RNC301ERR-ECODE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_TCODE -

Data type: SY-TCODE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_MANDFLD -

Data type: RNCOM-XFELD
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_ERRSGM -

Data type: RNC301ERR-ERRSGM
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_ERRSGMPOS -

Data type: RNC301ERR-ERRSGMPOS
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_ERRFLDPOS -

Data type: RNC301ERR-ERRFLDPOS
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

ARBGB -

Data type: RNC301ERR-ARBGB
Optional: No
Call by Reference: No ( called with pass by value option)

MSGNR -

Data type: RNC301ERR-MSGNR
Optional: No
Call by Reference: No ( called with pass by value option)

MSGV1 -

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

MSGV2 -

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

MSGV3 -

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

MSGV4 -

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

I_UCONTROL_ENABLED -

Data type: RNCOM-XFELD
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_INSTITUTION -

Data type: TN01-EINRI
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ISH_EDI_MESSAGE_HANDLER

E_MSGTY -

Data type: RNC301ERR-MSGTY
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for ISH_EDI_MESSAGE_HANDLER 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_msgty  TYPE RNC301ERR-MSGTY, "   
lv_e_msgty  TYPE RNC301ERR-MSGTY, "   
lv_i_function  TYPE TN21M-FUNKT, "   SPACE
lv_i_rstatus  TYPE RNC301ERR-RSTATUS, "   SPACE
lv_i_ecode  TYPE RNC301ERR-ECODE, "   SPACE
lv_i_tcode  TYPE SY-TCODE, "   SPACE
lv_i_mandfld  TYPE RNCOM-XFELD, "   SPACE
lv_i_errsgm  TYPE RNC301ERR-ERRSGM, "   SPACE
lv_i_errsgmpos  TYPE RNC301ERR-ERRSGMPOS, "   SPACE
lv_i_errfldpos  TYPE RNC301ERR-ERRFLDPOS, "   SPACE
lv_arbgb  TYPE RNC301ERR-ARBGB, "   
lv_msgnr  TYPE RNC301ERR-MSGNR, "   
lv_msgv1  TYPE RNC301ERR, "   SPACE
lv_msgv2  TYPE RNC301ERR, "   SPACE
lv_msgv3  TYPE RNC301ERR, "   SPACE
lv_msgv4  TYPE RNC301ERR, "   SPACE
lv_i_ucontrol_enabled  TYPE RNCOM-XFELD, "   SPACE
lv_i_institution  TYPE TN01-EINRI. "   SPACE

  CALL FUNCTION 'ISH_EDI_MESSAGE_HANDLER'  "
    EXPORTING
         MSGTY = lv_msgty
         I_FUNCTION = lv_i_function
         I_RSTATUS = lv_i_rstatus
         I_ECODE = lv_i_ecode
         I_TCODE = lv_i_tcode
         I_MANDFLD = lv_i_mandfld
         I_ERRSGM = lv_i_errsgm
         I_ERRSGMPOS = lv_i_errsgmpos
         I_ERRFLDPOS = lv_i_errfldpos
         ARBGB = lv_arbgb
         MSGNR = lv_msgnr
         MSGV1 = lv_msgv1
         MSGV2 = lv_msgv2
         MSGV3 = lv_msgv3
         MSGV4 = lv_msgv4
         I_UCONTROL_ENABLED = lv_i_ucontrol_enabled
         I_INSTITUTION = lv_i_institution
    IMPORTING
         E_MSGTY = lv_e_msgty
. " ISH_EDI_MESSAGE_HANDLER




ABAP code using 7.40 inline data declarations to call FM ISH_EDI_MESSAGE_HANDLER

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 MSGTY FROM RNC301ERR INTO @DATA(ld_msgty).
 
"SELECT single MSGTY FROM RNC301ERR INTO @DATA(ld_e_msgty).
 
"SELECT single FUNKT FROM TN21M INTO @DATA(ld_i_function).
DATA(ld_i_function) = ' '.
 
"SELECT single RSTATUS FROM RNC301ERR INTO @DATA(ld_i_rstatus).
DATA(ld_i_rstatus) = ' '.
 
"SELECT single ECODE FROM RNC301ERR INTO @DATA(ld_i_ecode).
DATA(ld_i_ecode) = ' '.
 
"SELECT single TCODE FROM SY INTO @DATA(ld_i_tcode).
DATA(ld_i_tcode) = ' '.
 
"SELECT single XFELD FROM RNCOM INTO @DATA(ld_i_mandfld).
DATA(ld_i_mandfld) = ' '.
 
"SELECT single ERRSGM FROM RNC301ERR INTO @DATA(ld_i_errsgm).
DATA(ld_i_errsgm) = ' '.
 
"SELECT single ERRSGMPOS FROM RNC301ERR INTO @DATA(ld_i_errsgmpos).
DATA(ld_i_errsgmpos) = ' '.
 
"SELECT single ERRFLDPOS FROM RNC301ERR INTO @DATA(ld_i_errfldpos).
DATA(ld_i_errfldpos) = ' '.
 
"SELECT single ARBGB FROM RNC301ERR INTO @DATA(ld_arbgb).
 
"SELECT single MSGNR FROM RNC301ERR INTO @DATA(ld_msgnr).
 
DATA(ld_msgv1) = ' '.
 
DATA(ld_msgv2) = ' '.
 
DATA(ld_msgv3) = ' '.
 
DATA(ld_msgv4) = ' '.
 
"SELECT single XFELD FROM RNCOM INTO @DATA(ld_i_ucontrol_enabled).
DATA(ld_i_ucontrol_enabled) = ' '.
 
"SELECT single EINRI FROM TN01 INTO @DATA(ld_i_institution).
DATA(ld_i_institution) = ' '.
 


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!