SAP SRT_EVENT_IN_UPDATE_TASK Function Module for Eventing in Update Task
SRT_EVENT_IN_UPDATE_TASK is a standard srt event in update task SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Eventing in Update Task 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 srt event in update task FM, simply by entering the name SRT_EVENT_IN_UPDATE_TASK into the relevant SAP transaction such as SE37 or SE38.
Function Group: SRT_EVENTING
Program Name: SAPLSRT_EVENTING
Main Program: SAPLSRT_EVENTING
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1

Function SRT_EVENT_IN_UPDATE_TASK 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 'SRT_EVENT_IN_UPDATE_TASK'"Eventing in Update Task.
EXPORTING
I_PERSIST_ID = "GUID for Integration Engine Objects
* I_TRACE_LEVEL = "
* I_APPLICATION_ID = "UUID in character form
IMPORTING Parameters details for SRT_EVENT_IN_UPDATE_TASK
I_PERSIST_ID - GUID for Integration Engine Objects
Data type: SXMSGUIDOptional: No
Call by Reference: No ( called with pass by value option)
I_TRACE_LEVEL -
Data type: IOptional: Yes
Call by Reference: No ( called with pass by value option)
I_APPLICATION_ID - UUID in character form
Data type: SYSUUID_COptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SRT_EVENT_IN_UPDATE_TASK 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_persist_id | TYPE SXMSGUID, " | |||
| lv_i_trace_level | TYPE I, " | |||
| lv_i_application_id | TYPE SYSUUID_C. " |
|   CALL FUNCTION 'SRT_EVENT_IN_UPDATE_TASK' "Eventing in Update Task |
| EXPORTING | ||
| I_PERSIST_ID | = lv_i_persist_id | |
| I_TRACE_LEVEL | = lv_i_trace_level | |
| I_APPLICATION_ID | = lv_i_application_id | |
| . " SRT_EVENT_IN_UPDATE_TASK | ||
ABAP code using 7.40 inline data declarations to call FM SRT_EVENT_IN_UPDATE_TASK
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