SAP SALERT_CREATE_DELIVERY_RULE Function Module for
SALERT_CREATE_DELIVERY_RULE is a standard salert create delivery rule 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 salert create delivery rule FM, simply by entering the name SALERT_CREATE_DELIVERY_RULE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SALERT_VIEW_SERVICES
Program Name: SAPLSALERT_VIEW_SERVICES
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SALERT_CREATE_DELIVERY_RULE 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 'SALERT_CREATE_DELIVERY_RULE'".
EXPORTING
IT_RULE = "Table For Rules
* IP_OLD_RULE_ID_MAIL = "
* IP_OLD_RULE_ID_FAX = "
* IP_OLD_RULE_ID_SMS = "
* IP_OLD_RULE_ID_WAP = "
* IP_OLD_RULE_ID_XML = "
* IP_FACTORY_CAL = "Factory Calendar
* IP_HOLIDAY_CAL = "Public Holiday Calendar
* IP_TIMEZONE = 'UTC' "Time zone for this weekday
IMPORTING
EP_RULE_ID_MAIL = "
EP_RULE_ID_FAX = "
EP_RULE_ID_SMS = "
EP_RULE_ID_WAP = "
EP_RULE_ID_XML = "
IMPORTING Parameters details for SALERT_CREATE_DELIVERY_RULE
IT_RULE - Table For Rules
Data type: SALRTTDELVOptional: No
Call by Reference: Yes
IP_OLD_RULE_ID_MAIL -
Data type: SCRULES-RULE_IDOptional: Yes
Call by Reference: Yes
IP_OLD_RULE_ID_FAX -
Data type: SCRULES-RULE_IDOptional: Yes
Call by Reference: Yes
IP_OLD_RULE_ID_SMS -
Data type: SCRULES-RULE_IDOptional: Yes
Call by Reference: Yes
IP_OLD_RULE_ID_WAP -
Data type: SCRULES-RULE_IDOptional: Yes
Call by Reference: Yes
IP_OLD_RULE_ID_XML -
Data type: SCRULES-RULE_IDOptional: Yes
Call by Reference: Yes
IP_FACTORY_CAL - Factory Calendar
Data type: WFCIDOptional: Yes
Call by Reference: Yes
IP_HOLIDAY_CAL - Public Holiday Calendar
Data type: HIDENTOptional: Yes
Call by Reference: Yes
IP_TIMEZONE - Time zone for this weekday
Data type: SC_RULEWTZDefault: 'UTC'
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for SALERT_CREATE_DELIVERY_RULE
EP_RULE_ID_MAIL -
Data type: SCRULES-RULE_IDOptional: No
Call by Reference: Yes
EP_RULE_ID_FAX -
Data type: SCRULES-RULE_IDOptional: No
Call by Reference: Yes
EP_RULE_ID_SMS -
Data type: SCRULES-RULE_IDOptional: No
Call by Reference: Yes
EP_RULE_ID_WAP -
Data type: SCRULES-RULE_IDOptional: No
Call by Reference: Yes
EP_RULE_ID_XML -
Data type: SCRULES-RULE_IDOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for SALERT_CREATE_DELIVERY_RULE 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_it_rule | TYPE SALRTTDELV, " | |||
| lv_ep_rule_id_mail | TYPE SCRULES-RULE_ID, " | |||
| lv_ep_rule_id_fax | TYPE SCRULES-RULE_ID, " | |||
| lv_ip_old_rule_id_mail | TYPE SCRULES-RULE_ID, " | |||
| lv_ep_rule_id_sms | TYPE SCRULES-RULE_ID, " | |||
| lv_ip_old_rule_id_fax | TYPE SCRULES-RULE_ID, " | |||
| lv_ep_rule_id_wap | TYPE SCRULES-RULE_ID, " | |||
| lv_ip_old_rule_id_sms | TYPE SCRULES-RULE_ID, " | |||
| lv_ep_rule_id_xml | TYPE SCRULES-RULE_ID, " | |||
| lv_ip_old_rule_id_wap | TYPE SCRULES-RULE_ID, " | |||
| lv_ip_old_rule_id_xml | TYPE SCRULES-RULE_ID, " | |||
| lv_ip_factory_cal | TYPE WFCID, " | |||
| lv_ip_holiday_cal | TYPE HIDENT, " | |||
| lv_ip_timezone | TYPE SC_RULEWTZ. " 'UTC' |
|   CALL FUNCTION 'SALERT_CREATE_DELIVERY_RULE' " |
| EXPORTING | ||
| IT_RULE | = lv_it_rule | |
| IP_OLD_RULE_ID_MAIL | = lv_ip_old_rule_id_mail | |
| IP_OLD_RULE_ID_FAX | = lv_ip_old_rule_id_fax | |
| IP_OLD_RULE_ID_SMS | = lv_ip_old_rule_id_sms | |
| IP_OLD_RULE_ID_WAP | = lv_ip_old_rule_id_wap | |
| IP_OLD_RULE_ID_XML | = lv_ip_old_rule_id_xml | |
| IP_FACTORY_CAL | = lv_ip_factory_cal | |
| IP_HOLIDAY_CAL | = lv_ip_holiday_cal | |
| IP_TIMEZONE | = lv_ip_timezone | |
| IMPORTING | ||
| EP_RULE_ID_MAIL | = lv_ep_rule_id_mail | |
| EP_RULE_ID_FAX | = lv_ep_rule_id_fax | |
| EP_RULE_ID_SMS | = lv_ep_rule_id_sms | |
| EP_RULE_ID_WAP | = lv_ep_rule_id_wap | |
| EP_RULE_ID_XML | = lv_ep_rule_id_xml | |
| . " SALERT_CREATE_DELIVERY_RULE | ||
ABAP code using 7.40 inline data declarations to call FM SALERT_CREATE_DELIVERY_RULE
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 RULE_ID FROM SCRULES INTO @DATA(ld_ep_rule_id_mail). | ||||
| "SELECT single RULE_ID FROM SCRULES INTO @DATA(ld_ep_rule_id_fax). | ||||
| "SELECT single RULE_ID FROM SCRULES INTO @DATA(ld_ip_old_rule_id_mail). | ||||
| "SELECT single RULE_ID FROM SCRULES INTO @DATA(ld_ep_rule_id_sms). | ||||
| "SELECT single RULE_ID FROM SCRULES INTO @DATA(ld_ip_old_rule_id_fax). | ||||
| "SELECT single RULE_ID FROM SCRULES INTO @DATA(ld_ep_rule_id_wap). | ||||
| "SELECT single RULE_ID FROM SCRULES INTO @DATA(ld_ip_old_rule_id_sms). | ||||
| "SELECT single RULE_ID FROM SCRULES INTO @DATA(ld_ep_rule_id_xml). | ||||
| "SELECT single RULE_ID FROM SCRULES INTO @DATA(ld_ip_old_rule_id_wap). | ||||
| "SELECT single RULE_ID FROM SCRULES INTO @DATA(ld_ip_old_rule_id_xml). | ||||
| DATA(ld_ip_timezone) | = 'UTC'. | |||
Search for further information about these or an SAP related objects