SAP SALERT_PROCESSOR_API Function Module for

Search SAP Function Modules

SALERT_PROCESSOR_API is a standard salert processor 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 salert processor api FM, simply by entering the name SALERT_PROCESSOR_API into the relevant SAP transaction such as SE37 or SE38.

Function Group: SALERT_PROCESSING_API
Program Name: SAPLSALERT_PROCESSING_API
Main Program: SAPLSALERT_PROCESSING_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SALERT_PROCESSOR_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 'SALERT_PROCESSOR_API'"
  EXPORTING
   IP_GUID =  "
   IP_USER_NAME =  "
   IP_PROCESSING =  "
*  IP_WAIT_ON_COMMIT = ' ' "

EXCEPTIONS
   ALERT_LOCKED = 1    ALERT_RECIPIENT_UNKNOWN = 2    ALERT_UNKNOWN = 3    ALERT_NO_AUTHORIZATION = 4    ALERT_ONLY_ONE_RECIPIENT = 5    ALERT_ESCALATION_RECIPIENT = 6 

.

IMPORTING Parameters details for SALERT_PROCESSOR_API

IP_GUID -

Data type: OS_GUID
Optional: No
Call by Reference: No ( called with pass by value option)

IP_USER_NAME -

Data type: SALRTDRCPT
Optional: No
Call by Reference: No ( called with pass by value option)

IP_PROCESSING -

Data type: SALERTDPROCESS
Optional: No
Call by Reference: No ( called with pass by value option)

IP_WAIT_ON_COMMIT -

Data type: SALERTDCOMMIT
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

ALERT_LOCKED -

Data type:
Optional: No
Call by Reference: Yes

ALERT_RECIPIENT_UNKNOWN -

Data type:
Optional: No
Call by Reference: Yes

ALERT_UNKNOWN -

Data type:
Optional: No
Call by Reference: Yes

ALERT_NO_AUTHORIZATION -

Data type:
Optional: No
Call by Reference: Yes

ALERT_ONLY_ONE_RECIPIENT -

Data type:
Optional: No
Call by Reference: Yes

ALERT_ESCALATION_RECIPIENT -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SALERT_PROCESSOR_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.

ABAP code using 7.40 inline data declarations to call FM SALERT_PROCESSOR_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.

Search for further information about these or an SAP related objects