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

Function ISH_AT_EDHON_S1101_FILL 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_EDHON_S1101_FILL'".
CHANGING
INC301 = "
TABLES
SEGM_MAIL = "
* CT_ERRORS = "
EXCEPTIONS
NO_MAIL = 1
CHANGING Parameters details for ISH_AT_EDHON_S1101_FILL
INC301 -
Data type: NC301Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ISH_AT_EDHON_S1101_FILL
SEGM_MAIL -
Data type: RNCMAILOptional: No
Call by Reference: Yes
CT_ERRORS -
Data type: NC301EOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
NO_MAIL -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISH_AT_EDHON_S1101_FILL 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_inc301 | TYPE NC301, " | |||
| lv_no_mail | TYPE NC301, " | |||
| lt_segm_mail | TYPE STANDARD TABLE OF RNCMAIL, " | |||
| lt_ct_errors | TYPE STANDARD TABLE OF NC301E. " |
|   CALL FUNCTION 'ISH_AT_EDHON_S1101_FILL' " |
| CHANGING | ||
| INC301 | = lv_inc301 | |
| TABLES | ||
| SEGM_MAIL | = lt_segm_mail | |
| CT_ERRORS | = lt_ct_errors | |
| EXCEPTIONS | ||
| NO_MAIL = 1 | ||
| . " ISH_AT_EDHON_S1101_FILL | ||
ABAP code using 7.40 inline data declarations to call FM ISH_AT_EDHON_S1101_FILL
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