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

Function ISH_AT_READ_EDI_KOM 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_AT_READ_EDI_KOM'".
EXPORTING
I_EINRI = "
* I_LFDNR = "
* I_LF301 = "
* I_READ_DB = ' ' "
* I_READ_STORN = ' ' "
* I_READ_AVAILABLE = ' ' "
I_FALNR = "
* I_KOSTR = "
* I_EDIPROC = "
* I_NTNR = "
* I_SUBTYP = "
* I_SUBTYP_KOM = ' ' "
* I_SUBTYP_CTL = ' ' "
* I_PERIOD = "
IMPORTING
ES_NWAT_EDI_KOM = "
ET_NWAT_EDI_KOM = "
EXCEPTIONS
ERROR_INPUT = 1 NOT_FOUND = 2
IMPORTING Parameters details for ISH_AT_READ_EDI_KOM
I_EINRI -
Data type: EINRIOptional: No
Call by Reference: Yes
I_LFDNR -
Data type: NWAT_EDI_LFDKOMOptional: Yes
Call by Reference: Yes
I_LF301 -
Data type: ISH_LF301Optional: Yes
Call by Reference: Yes
I_READ_DB -
Data type: ISH_ON_OFFDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_READ_STORN -
Data type: ISH_ON_OFFDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_READ_AVAILABLE -
Data type: ISH_ON_OFFDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_FALNR -
Data type: FALNROptional: No
Call by Reference: Yes
I_KOSTR -
Data type: KH_KOSTROptional: Yes
Call by Reference: Yes
I_EDIPROC -
Data type: N_EDIPROCOptional: Yes
Call by Reference: Yes
I_NTNR -
Data type: NTNROptional: Yes
Call by Reference: Yes
I_SUBTYP -
Data type: NWAT_EDI_SUBTYPOptional: Yes
Call by Reference: Yes
I_SUBTYP_KOM -
Data type: ISH_ON_OFFDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_SUBTYP_CTL -
Data type: ISH_ON_OFFDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_PERIOD -
Data type: NWAT_EDI_PERIODOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for ISH_AT_READ_EDI_KOM
ES_NWAT_EDI_KOM -
Data type: NWAT_EDI_KOMOptional: No
Call by Reference: Yes
ET_NWAT_EDI_KOM -
Data type: ISH_AT_YT_NWAT_EDI_KOMOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR_INPUT -
Data type:Optional: No
Call by Reference: Yes
NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISH_AT_READ_EDI_KOM 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_einri | TYPE EINRI, " | |||
| lv_error_input | TYPE EINRI, " | |||
| lv_es_nwat_edi_kom | TYPE NWAT_EDI_KOM, " | |||
| lv_i_lfdnr | TYPE NWAT_EDI_LFDKOM, " | |||
| lv_i_lf301 | TYPE ISH_LF301, " | |||
| lv_i_read_db | TYPE ISH_ON_OFF, " SPACE | |||
| lv_i_read_storn | TYPE ISH_ON_OFF, " SPACE | |||
| lv_i_read_available | TYPE ISH_ON_OFF, " SPACE | |||
| lv_i_falnr | TYPE FALNR, " | |||
| lv_not_found | TYPE FALNR, " | |||
| lv_et_nwat_edi_kom | TYPE ISH_AT_YT_NWAT_EDI_KOM, " | |||
| lv_i_kostr | TYPE KH_KOSTR, " | |||
| lv_i_ediproc | TYPE N_EDIPROC, " | |||
| lv_i_ntnr | TYPE NTNR, " | |||
| lv_i_subtyp | TYPE NWAT_EDI_SUBTYP, " | |||
| lv_i_subtyp_kom | TYPE ISH_ON_OFF, " SPACE | |||
| lv_i_subtyp_ctl | TYPE ISH_ON_OFF, " SPACE | |||
| lv_i_period | TYPE NWAT_EDI_PERIOD. " |
|   CALL FUNCTION 'ISH_AT_READ_EDI_KOM' " |
| EXPORTING | ||
| I_EINRI | = lv_i_einri | |
| I_LFDNR | = lv_i_lfdnr | |
| I_LF301 | = lv_i_lf301 | |
| I_READ_DB | = lv_i_read_db | |
| I_READ_STORN | = lv_i_read_storn | |
| I_READ_AVAILABLE | = lv_i_read_available | |
| I_FALNR | = lv_i_falnr | |
| I_KOSTR | = lv_i_kostr | |
| I_EDIPROC | = lv_i_ediproc | |
| I_NTNR | = lv_i_ntnr | |
| I_SUBTYP | = lv_i_subtyp | |
| I_SUBTYP_KOM | = lv_i_subtyp_kom | |
| I_SUBTYP_CTL | = lv_i_subtyp_ctl | |
| I_PERIOD | = lv_i_period | |
| IMPORTING | ||
| ES_NWAT_EDI_KOM | = lv_es_nwat_edi_kom | |
| ET_NWAT_EDI_KOM | = lv_et_nwat_edi_kom | |
| EXCEPTIONS | ||
| ERROR_INPUT = 1 | ||
| NOT_FOUND = 2 | ||
| . " ISH_AT_READ_EDI_KOM | ||
ABAP code using 7.40 inline data declarations to call FM ISH_AT_READ_EDI_KOM
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.| DATA(ld_i_read_db) | = ' '. | |||
| DATA(ld_i_read_storn) | = ' '. | |||
| DATA(ld_i_read_available) | = ' '. | |||
| DATA(ld_i_subtyp_kom) | = ' '. | |||
| DATA(ld_i_subtyp_ctl) | = ' '. | |||
Search for further information about these or an SAP related objects