SAP Reports / Programs | Basis Components | Basis Services / Communication Interfaces | Alert Framework(BC-SRV-GBT-ALM) SAP BC

RSALERTTEST SAP ABAP Report - Alerts: Trigger Alerts







RSALERTTEST is a standard Executable ABAP Report available within your SAP system (depending on your version and release level). Below is the basic information available for this SAP report including which OBJECTS it interacts with such as TABLES, FUNCTION MODULES, INCLUDES ETC. Also check out the submitted Comments related to this SAP report or see any standard documentation available.

If you would like to execute this report or see the full code listing simply enter RSALERTTEST into the relevant SAP transactions such as SE38 or SE80


ABAP code to call this SAP report using the submit statement

This report can be called from another progam/report simply by using the ABAP SUBMIT statement, see below for example ABAP code snipts of how to do this.






SUBMIT RSALERTTEST. "Basic submit
SUBMIT RSALERTTEST AND RETURN. "Return to original report after report execution complete
SUBMIT RSALERTTEST VIA SELECTION-SCREEN. "Display selection screen of submitted report to user
    See more syntax options for the ABAP SUBMIT statement


Text pool values


Selection Text: P_CAT = Alert Category
Selection Text: P_CONF = Additional Configuration
Title: Alerts: Trigger Alerts
Text Symbol: 001 = ID of Alert Created:
Text Symbol: 002 = Alert ID is unknown. Maybe the alert was not created.
Text Symbol: 003 = --- Unknown Category ---
Text Symbol: 004 = --- Unknown User ---


INCLUDES used within this REPORT RSALERTTEST

No INCLUDES are used within this REPORT code!


TABLES used within REPORT and the associated SELECT statement:





No SAP DATABASE tables are accessed within this REPORT code!


Function Modules used within report and the associated call statement:

SALERT_CREATE CALL FUNCTION 'SALERT_CREATE' EXPORTING ip_cat = ip_cat IMPORTING ep_alert_id = l_alert_id EXCEPTIONS alert_category_unknown = 1 alert_no_recipients = 2 OTHERS = 3.

LVC_FIELDCATALOG_MERGE CALL FUNCTION 'LVC_FIELDCATALOG_MERGE' EXPORTING i_structure_name = 'SALRTSUSR' CHANGING ct_fieldcat = gt_ufcat EXCEPTIONS inconsistent_interface = 1 program_error = 2 OTHERS = 3.

LVC_FIELDCATALOG_MERGE CALL FUNCTION 'LVC_FIELDCATALOG_MERGE' EXPORTING i_structure_name = 'SALRTSCOMM' CHANGING ct_fieldcat = gt_efcat EXCEPTIONS inconsistent_interface = 1 program_error = 2 OTHERS = 3.

LVC_FIELDCATALOG_MERGE CALL FUNCTION 'LVC_FIELDCATALOG_MERGE' EXPORTING i_structure_name = 'SALRTSACTC' CHANGING ct_fieldcat = gt_afcat EXCEPTIONS inconsistent_interface = 1 program_error = 2 OTHERS = 3.

SALERT_CREATE CALL FUNCTION 'SALERT_CREATE' EXPORTING ip_cat = p_cat IMPORTING ep_alert_id = l_alert_id TABLES it_container = lt_container EXCEPTIONS alert_category_unknown = 1 alert_no_recipients = 2 alert_error_unknown = 3.

CONVERT_ITF_TO_STREAM_TEXT CALL FUNCTION 'CONVERT_ITF_TO_STREAM_TEXT' TABLES itf_text = gt_text text_stream = gt_streamtext.

BAPI_USER_GET_DETAIL CALL FUNCTION 'BAPI_USER_GET_DETAIL' EXPORTING username = gs_user-username IMPORTING address = gs_address TABLES return = gt_return.



Contribute (Add Comments)

Although this basic information may have limited use it does provide an easy to find location to store any knowledge about this program/report.







The contribute/comments section below therefore offer's an opportunity for anyone to add additional information. This can be anything from useful hints, tips and screen shots to relevant SAP notes or anything else you feel is relevant to this report.

This will then be available for everyone to easily find by simply searching on the report name RSALERTTEST or its description.