SAP RSAU_WRITE_EXT_TEMPLATE Function Module for Eventtrigger for Extension Template
RSAU_WRITE_EXT_TEMPLATE is a standard rsau write ext template SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Eventtrigger for Extension Template 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 rsau write ext template FM, simply by entering the name RSAU_WRITE_EXT_TEMPLATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SECU_MSG_WRAPPER_01
Program Name: SAPLSECU_MSG_WRAPPER_01
Main Program: SAPLSECU_MSG_WRAPPER_01
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RSAU_WRITE_EXT_TEMPLATE 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 'RSAU_WRITE_EXT_TEMPLATE'"Eventtrigger for Extension Template.
EXPORTING
ID_EVENT = "System Message Number
* ID_TEMPL_ID = "Template ID
* ID_TEMPL_VERS = "Template Version
* ID_FILE_NAME = "File Name
IMPORTING Parameters details for RSAU_WRITE_EXT_TEMPLATE
ID_EVENT - System Message Number
Data type: RSAUEVENTOptional: No
Call by Reference: Yes
ID_TEMPL_ID - Template ID
Data type: EIT_TEMPLATE_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
ID_TEMPL_VERS - Template Version
Data type: EIT_TEMPLATE_VERSIONOptional: Yes
Call by Reference: No ( called with pass by value option)
ID_FILE_NAME - File Name
Data type: STRINGOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RSAU_WRITE_EXT_TEMPLATE 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_id_event | TYPE RSAUEVENT, " | |||
| lv_id_templ_id | TYPE EIT_TEMPLATE_ID, " | |||
| lv_id_templ_vers | TYPE EIT_TEMPLATE_VERSION, " | |||
| lv_id_file_name | TYPE STRING. " |
|   CALL FUNCTION 'RSAU_WRITE_EXT_TEMPLATE' "Eventtrigger for Extension Template |
| EXPORTING | ||
| ID_EVENT | = lv_id_event | |
| ID_TEMPL_ID | = lv_id_templ_id | |
| ID_TEMPL_VERS | = lv_id_templ_vers | |
| ID_FILE_NAME | = lv_id_file_name | |
| . " RSAU_WRITE_EXT_TEMPLATE | ||
ABAP code using 7.40 inline data declarations to call FM RSAU_WRITE_EXT_TEMPLATE
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