SAP SEND_LCAALERT_SDB Function Module for
SEND_LCAALERT_SDB is a standard send lcaalert sdb 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 send lcaalert sdb FM, simply by entering the name SEND_LCAALERT_SDB into the relevant SAP transaction such as SE37 or SE38.
Function Group: SADB
Program Name: SAPLSADB
Main Program: SAPLSADB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SEND_LCAALERT_SDB 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 'SEND_LCAALERT_SDB'".
EXPORTING
IV_CON_NAME = "Logical Name for a Database Connection
TABLES
IT_LCAALERTS = "liveCache Application Alerts
EXCEPTIONS
NO_CONNECTION = 1 CREATE_TABLE_FAILED = 2
IMPORTING Parameters details for SEND_LCAALERT_SDB
IV_CON_NAME - Logical Name for a Database Connection
Data type: DBCON-CON_NAMEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SEND_LCAALERT_SDB
IT_LCAALERTS - liveCache Application Alerts
Data type: LCAALERTSOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_CONNECTION -
Data type:Optional: No
Call by Reference: Yes
CREATE_TABLE_FAILED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SEND_LCAALERT_SDB 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_iv_con_name | TYPE DBCON-CON_NAME, " | |||
| lt_it_lcaalerts | TYPE STANDARD TABLE OF LCAALERTS, " | |||
| lv_no_connection | TYPE LCAALERTS, " | |||
| lv_create_table_failed | TYPE LCAALERTS. " |
|   CALL FUNCTION 'SEND_LCAALERT_SDB' " |
| EXPORTING | ||
| IV_CON_NAME | = lv_iv_con_name | |
| TABLES | ||
| IT_LCAALERTS | = lt_it_lcaalerts | |
| EXCEPTIONS | ||
| NO_CONNECTION = 1 | ||
| CREATE_TABLE_FAILED = 2 | ||
| . " SEND_LCAALERT_SDB | ||
ABAP code using 7.40 inline data declarations to call FM SEND_LCAALERT_SDB
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 CON_NAME FROM DBCON INTO @DATA(ld_iv_con_name). | ||||
Search for further information about these or an SAP related objects