SAP SALRT_CONFIRM_BY_GUID_API Function Module for
SALRT_CONFIRM_BY_GUID_API is a standard salrt confirm by guid api 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 salrt confirm by guid api FM, simply by entering the name SALRT_CONFIRM_BY_GUID_API into the relevant SAP transaction such as SE37 or SE38.
Function Group: SALRT_CREATE_LOCAL
Program Name: SAPLSALRT_CREATE_LOCAL
Main Program: SAPLSALRT_CREATE_LOCAL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SALRT_CONFIRM_BY_GUID_API 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 'SALRT_CONFIRM_BY_GUID_API'".
EXPORTING
* IP_APPL_GUID = "GUID in 'CHAR' Format in Uppercase
* IT_APPL_GUID = "Alerts: Table of GUIDs
* IP_WAIT_ON_COMMIT = 'X' "Wait for COMMIT WORK
EXCEPTIONS
DESTINATION_UNDEFINED = 1
IMPORTING Parameters details for SALRT_CONFIRM_BY_GUID_API
IP_APPL_GUID - GUID in 'CHAR' Format in Uppercase
Data type: GUID_32Optional: Yes
Call by Reference: Yes
IT_APPL_GUID - Alerts: Table of GUIDs
Data type: SALRTTGUIDOptional: Yes
Call by Reference: Yes
IP_WAIT_ON_COMMIT - Wait for COMMIT WORK
Data type: CHAR1Default: 'X'
Optional: No
Call by Reference: Yes
EXCEPTIONS details
DESTINATION_UNDEFINED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SALRT_CONFIRM_BY_GUID_API 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_ip_appl_guid | TYPE GUID_32, " | |||
| lv_destination_undefined | TYPE GUID_32, " | |||
| lv_it_appl_guid | TYPE SALRTTGUID, " | |||
| lv_ip_wait_on_commit | TYPE CHAR1. " 'X' |
|   CALL FUNCTION 'SALRT_CONFIRM_BY_GUID_API' " |
| EXPORTING | ||
| IP_APPL_GUID | = lv_ip_appl_guid | |
| IT_APPL_GUID | = lv_it_appl_guid | |
| IP_WAIT_ON_COMMIT | = lv_ip_wait_on_commit | |
| EXCEPTIONS | ||
| DESTINATION_UNDEFINED = 1 | ||
| . " SALRT_CONFIRM_BY_GUID_API | ||
ABAP code using 7.40 inline data declarations to call FM SALRT_CONFIRM_BY_GUID_API
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.| DATA(ld_ip_wait_on_commit) | = 'X'. | |||
Search for further information about these or an SAP related objects