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

Function ISH_EDI_DECODE 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_DECODE'".
EXPORTING
I_PROCEDURE = "EDI Procedure
I_MSGID = "Message Number
* I_CMSTAND = "Communication Standard
* I_CMSTVER = "Version
* I_NTNR = ' ' "Message Type
* I_NTOWNERCDE = ' ' "
* I_PROGNAME = ' ' "
* I_SPECHARS = ' ' "Separator
* I_NC301S = "
TABLES
* I_BUFFER_MAIL = "
* I_BUFFER_SEGMENTS = "
E_FIELDS = "
EXCEPTIONS
PARAMETER_ERROR = 1 DECODING_ERROR = 2 NOT_SUPPORTED = 3
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_SAPLNC11_001 IS-H: User Exit for EDI in reception_dispatcher Module
IMPORTING Parameters details for ISH_EDI_DECODE
I_PROCEDURE - EDI Procedure
Data type: TNC301G0-EDIPROCOptional: No
Call by Reference: No ( called with pass by value option)
I_MSGID - Message Number
Data type: NC301S-LF301Optional: No
Call by Reference: No ( called with pass by value option)
I_CMSTAND - Communication Standard
Data type: TNCT1-STANDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_CMSTVER - Version
Data type: TNCT1-STVEROptional: Yes
Call by Reference: No ( called with pass by value option)
I_NTNR - Message Type
Data type: TNCT1-NTNRDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_NTOWNERCDE -
Data type: TNCT1-NTOWNERCDEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_PROGNAME -
Data type: SY-REPIDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_SPECHARS - Separator
Data type: NC301D-SPECHARSDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_NC301S -
Data type: NC301SOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ISH_EDI_DECODE
I_BUFFER_MAIL -
Data type: RNCBUFOptional: Yes
Call by Reference: No ( called with pass by value option)
I_BUFFER_SEGMENTS -
Data type: NC301WOptional: Yes
Call by Reference: No ( called with pass by value option)
E_FIELDS -
Data type: RNCSPLITOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
PARAMETER_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DECODING_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_SUPPORTED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISH_EDI_DECODE 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_i_procedure | TYPE TNC301G0-EDIPROC, " | |||
| lt_i_buffer_mail | TYPE STANDARD TABLE OF RNCBUF, " | |||
| lv_parameter_error | TYPE RNCBUF, " | |||
| lv_i_msgid | TYPE NC301S-LF301, " | |||
| lv_decoding_error | TYPE NC301S, " | |||
| lt_i_buffer_segments | TYPE STANDARD TABLE OF NC301W, " | |||
| lt_e_fields | TYPE STANDARD TABLE OF RNCSPLIT, " | |||
| lv_i_cmstand | TYPE TNCT1-STAND, " | |||
| lv_not_supported | TYPE TNCT1, " | |||
| lv_i_cmstver | TYPE TNCT1-STVER, " | |||
| lv_i_ntnr | TYPE TNCT1-NTNR, " SPACE | |||
| lv_i_ntownercde | TYPE TNCT1-NTOWNERCDE, " SPACE | |||
| lv_i_progname | TYPE SY-REPID, " SPACE | |||
| lv_i_spechars | TYPE NC301D-SPECHARS, " SPACE | |||
| lv_i_nc301s | TYPE NC301S. " |
|   CALL FUNCTION 'ISH_EDI_DECODE' " |
| EXPORTING | ||
| I_PROCEDURE | = lv_i_procedure | |
| I_MSGID | = lv_i_msgid | |
| I_CMSTAND | = lv_i_cmstand | |
| I_CMSTVER | = lv_i_cmstver | |
| I_NTNR | = lv_i_ntnr | |
| I_NTOWNERCDE | = lv_i_ntownercde | |
| I_PROGNAME | = lv_i_progname | |
| I_SPECHARS | = lv_i_spechars | |
| I_NC301S | = lv_i_nc301s | |
| TABLES | ||
| I_BUFFER_MAIL | = lt_i_buffer_mail | |
| I_BUFFER_SEGMENTS | = lt_i_buffer_segments | |
| E_FIELDS | = lt_e_fields | |
| EXCEPTIONS | ||
| PARAMETER_ERROR = 1 | ||
| DECODING_ERROR = 2 | ||
| NOT_SUPPORTED = 3 | ||
| . " ISH_EDI_DECODE | ||
ABAP code using 7.40 inline data declarations to call FM ISH_EDI_DECODE
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 EDIPROC FROM TNC301G0 INTO @DATA(ld_i_procedure). | ||||
| "SELECT single LF301 FROM NC301S INTO @DATA(ld_i_msgid). | ||||
| "SELECT single STAND FROM TNCT1 INTO @DATA(ld_i_cmstand). | ||||
| "SELECT single STVER FROM TNCT1 INTO @DATA(ld_i_cmstver). | ||||
| "SELECT single NTNR FROM TNCT1 INTO @DATA(ld_i_ntnr). | ||||
| DATA(ld_i_ntnr) | = ' '. | |||
| "SELECT single NTOWNERCDE FROM TNCT1 INTO @DATA(ld_i_ntownercde). | ||||
| DATA(ld_i_ntownercde) | = ' '. | |||
| "SELECT single REPID FROM SY INTO @DATA(ld_i_progname). | ||||
| DATA(ld_i_progname) | = ' '. | |||
| "SELECT single SPECHARS FROM NC301D INTO @DATA(ld_i_spechars). | ||||
| DATA(ld_i_spechars) | = ' '. | |||
Search for further information about these or an SAP related objects