SXMSALERTRULE SAP (Alert Rule) Structure details
Description: Alert Rule
Related tables to SXMSALERTRULE
Access table SXMSALERTRULE
Structure field list including key, data, relationships and ABAP select examples
SXMSALERTRULE is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "Alert Rule" Information within sap ABAP programs.
This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.
i.e. DATA: wa_SXMSALERTRULE TYPE SXMSALERTRULE.
The SXMSALERTRULE table consists of various fields, each holding specific information or linking keys about Alert Rule data available in SAP. These include ERRORCODE (Character field, length 70), FROMPARTY (XI: From-Party), FROMSERVICE (XI: From-Service), FROMACTIONNS (XI: From-Action (Outbound Interface) Namespace).. See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .
Delivery Class:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Can be enhanced (character-type)
SAP SXMSALERTRULE structure fields - Full list of fields found in SAP data dictionary
| Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
| ERRORCAT | XI: Error Category | SXMSERRCAT | CHAR | 20 | TEXT20 | ||||
| ERRORCODE | Character field, length 70 | CHAR70 | CHAR | 70 | CHAR70 | ||||
| FROMPARTY | XI: From-Party | SXI_FROM_PARTY | CHAR | 60 | SXI_PARTY | ||||
| FROMSERVICE | XI: From-Service | SXI_FROM_SERVICE | CHAR | 60 | SXI_SERVICE | ||||
| FROMACTIONNS | XI: From-Action (Outbound Interface) Namespace | SXI_FROM_ACTION_NS | CHAR | 255 | SXI_NAMESPACE | ||||
| FROMACTION | XI: From-Action (Outbound Interface) Name | SXI_FROM_ACTION | CHAR | 120 | SXI_NAME | ||||
| TOPARTY | XI: To-Party | SXI_TO_PARTY | CHAR | 60 | SXI_PARTY | ||||
| TOSERVICE | XI: To-Service | SXI_TO_SERVICE | CHAR | 60 | SXI_SERVICE | ||||
| TOACTIONNS | XI: To-Action (Inbound Interface) Namespace | SXI_TO_ACTION_NS | CHAR | 255 | SXI_NAMESPACE | ||||
| TOACTION | XI: To-Action (Inbound Interface) Name | SXI_TO_ACTION | CHAR | 120 | SXI_NAME | ||||
| ADAPTERNAME | XI Services: Adapter Name | SSRV_ADAPTER_NAME | CHAR | 120 | SSRV_ADAPTER_NAME | ||||
| CATEGORY | Alert Category | SALRTDCAT | CHAR | 30 | Assigned to domain | SALRTDCAT | |||
| RULENAME | Description | SXMSDESCR | CHAR | 60 | TEXT60 |
| Key field | Non-key field |
How do I retrieve data from SAP structure SXMSALERTRULE using ABAP code?
As SXMSALERTRULE is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on SXMSALERTRULE as there is no data to select.How to access SAP table SXMSALERTRULE
Within an ECC or HANA version of SAP you can also view further information about SXMSALERTRULE and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects