SAP EAMS_SIMULATE_CREATE_NTF Function Module for Simulates Notification Header Create Operation
EAMS_SIMULATE_CREATE_NTF is a standard eams simulate create ntf SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Simulates Notification Header Create Operation processing and below is the pattern details for this FM, 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 eams simulate create ntf FM, simply by entering the name EAMS_SIMULATE_CREATE_NTF into the relevant SAP transaction such as SE37 or SE38.
Function Group: EAMS_BO_NOTIF
Program Name: SAPLEAMS_BO_NOTIF
Main Program: SAPLEAMS_BO_NOTIF
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function EAMS_SIMULATE_CREATE_NTF 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 'EAMS_SIMULATE_CREATE_NTF'"Simulates Notification Header Create Operation.
EXPORTING
IV_NOTIF_TYPE = "Notification Type
IS_NOTIF_HEADER = "Notification Header
IV_OMIT_PARTNER_CHECK = "Do not check mandatory partner assignment?
* IV_TEST_PMM3 = "Check Order Assignment (PMM3)
TABLES
T_LONGTEXT = "Notification long text
T_RETURN = "Return Parameter
IMPORTING Parameters details for EAMS_SIMULATE_CREATE_NTF
IV_NOTIF_TYPE - Notification Type
Data type: BAPI2080-NOTIF_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
IS_NOTIF_HEADER - Notification Header
Data type: BAPI2080_NOTHDRIOptional: No
Call by Reference: No ( called with pass by value option)
IV_OMIT_PARTNER_CHECK - Do not check mandatory partner assignment?
Data type: BAPIFLAG-BAPIFLAGOptional: No
Call by Reference: No ( called with pass by value option)
IV_TEST_PMM3 - Check Order Assignment (PMM3)
Data type: BAPIFLAG-BAPIFLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for EAMS_SIMULATE_CREATE_NTF
T_LONGTEXT - Notification long text
Data type: BAPI2080_NOTFULLTXTIOptional: No
Call by Reference: Yes
T_RETURN - Return Parameter
Data type: BAPIRET2Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for EAMS_SIMULATE_CREATE_NTF 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_t_longtext | TYPE STANDARD TABLE OF BAPI2080_NOTFULLTXTI, " | |||
| lv_iv_notif_type | TYPE BAPI2080-NOTIF_TYPE, " | |||
| lt_t_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_is_notif_header | TYPE BAPI2080_NOTHDRI, " | |||
| lv_iv_omit_partner_check | TYPE BAPIFLAG-BAPIFLAG, " | |||
| lv_iv_test_pmm3 | TYPE BAPIFLAG-BAPIFLAG. " |
|   CALL FUNCTION 'EAMS_SIMULATE_CREATE_NTF' "Simulates Notification Header Create Operation |
| EXPORTING | ||
| IV_NOTIF_TYPE | = lv_iv_notif_type | |
| IS_NOTIF_HEADER | = lv_is_notif_header | |
| IV_OMIT_PARTNER_CHECK | = lv_iv_omit_partner_check | |
| IV_TEST_PMM3 | = lv_iv_test_pmm3 | |
| TABLES | ||
| T_LONGTEXT | = lt_t_longtext | |
| T_RETURN | = lt_t_return | |
| . " EAMS_SIMULATE_CREATE_NTF | ||
ABAP code using 7.40 inline data declarations to call FM EAMS_SIMULATE_CREATE_NTF
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 NOTIF_TYPE FROM BAPI2080 INTO @DATA(ld_iv_notif_type). | ||||
| "SELECT single BAPIFLAG FROM BAPIFLAG INTO @DATA(ld_iv_omit_partner_check). | ||||
| "SELECT single BAPIFLAG FROM BAPIFLAG INTO @DATA(ld_iv_test_pmm3). | ||||
Search for further information about these or an SAP related objects