SAP ABAP Message Class SALERT (Messages for the Alert Framework)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-SRV-GBT-ALM (Application Component) Alert Framework
⤷ SALERT_LOCAL (Package) Application Interface for Alert Framework
⤷ BC-SRV-GBT-ALM (Application Component) Alert Framework
⤷ SALERT_LOCAL (Package) Application Interface for Alert Framework
Attributes
Message class | SALERT | |
Short Description | Messages for the Alert Framework | |
Changed On | 20110908 | |
Last Changed At | 153135 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | *** Message class (000-999) reserved for Alert Framework *** | Space: object requires documentation | |
2 | 001 | You have subscribed to alert category &1 | Space: object requires documentation | |
3 | 002 | You are a recipient of alert category &1 | Space: object requires documentation | |
4 | 003 | You are the escalation recipient for alert category &1 | Space: object requires documentation | |
5 | 004 | Alert forwarded to you by &1 | Space: object requires documentation | |
6 | 005 | The triggering application determined you as a recipient | Space: object requires documentation | |
7 | 006 | You are entered as substitute for &1 | Space: object requires documentation | |
8 | 007 | Alert has no recipients | Space: object requires documentation | |
9 | 008 | Maintenance locked by user & | Space: object requires documentation | |
10 | 009 | Lock operation failed | Space: object requires documentation | |
11 | 010 | Alert forwarded to &1 successfully | Space: object requires documentation | |
12 | 011 | Alert could not be forwarded to recipient &1 | Space: object requires documentation | |
13 | 012 | Alert category & does not exist | Space: object requires documentation | |
14 | 013 | No alert category specified | Space: object requires documentation | |
15 | 014 | No further information about error | Space: object requires documentation | |
16 | 015 | You have been determined as a recipient via the role & | Space: object requires documentation | |
17 | 016 | Alert could not be deleted | Space: object requires documentation | |
18 | 017 | Alert created. ID: & | Space: object requires documentation | |
19 | 018 | Alert forwarding in XML format | Space: object requires documentation | |
20 | 019 | Alert is generated on the Central Alert Server | Space: object requires documentation | |
21 | 020 | Alert category: & | Space: object requires documentation | |
22 | 021 | Recipient from container: & | Space: object requires documentation | |
23 | 022 | Recipient & not accepted | Space: object requires documentation | |
24 | 023 | Recipient from alert category: & | Space: object requires documentation | |
25 | 024 | Recipient from role assignment: & | Space: object requires documentation | |
26 | 025 | Substitute recipient: & | Space: object requires documentation | |
27 | 026 | Alert has no recipients and will not be created | Space: object requires documentation | |
28 | 027 | Delivery by e-mail to & & | Space: object requires documentation | |
29 | 028 | Delivery by e-mail in XML format to & | Space: object requires documentation | |
30 | 029 | Delivery by SMS (text message) to & & | Space: object requires documentation | |
31 | 030 | Delivery & completed | Space: object requires documentation | |
32 | 031 | External ID of alert: & | Space: object requires documentation | |
33 | 032 | External ID for alert could not be obtained | Space: object requires documentation | |
34 | 033 | Address of recipient & (&) could not be read | Space: object requires documentation | |
35 | 034 | Escalate alert (ID &, category &) | Space: object requires documentation | |
36 | 035 | Deliver alert (ID &, category &) | Space: object requires documentation | |
37 | 036 | Current alert status does not allow escalation | Space: object requires documentation | |
38 | 037 | Alert category & has no escalation | Space: object requires documentation | |
39 | 038 | Escalation recipient: & | Space: object requires documentation | |
40 | 039 | Escalation recipient & could not be added | Space: object requires documentation | |
41 | 040 | Delete alert (ID &, category &) | Space: object requires documentation | |
42 | 041 | Expiry time: & & | Space: object requires documentation | |
43 | 042 | Confirm alert (ID &, category &) | Space: object requires documentation | |
44 | 043 | Confirm alert for user & | Space: object requires documentation | |
45 | 044 | No user specified for confirmation | Space: object requires documentation | |
46 | 045 | Forward alert (ID &) to & | Space: object requires documentation | |
47 | 046 | No user specified for forwarding | Space: object requires documentation | |
48 | 047 | User & already exists as recipient of the alert | Space: object requires documentation | |
49 | 048 | No escalation. Alert has already reached expiry date. | Space: object requires documentation | |
50 | 049 | BCS exception (&) occurred | Space: object requires documentation | |
51 | 050 | Send request for & has no recipients | Space: object requires documentation | |
52 | 051 | Communication method & is not supported (&) | Space: object requires documentation | |
53 | 052 | E-mail address & could not be added | Space: object requires documentation | |
54 | 053 | SMS number & (for text message) could not be added | Space: object requires documentation | |
55 | 054 | Sender & could not be assigned | Space: object requires documentation | |
56 | 055 | Business Add-In is not assigned (user &) | Space: object requires documentation | |
57 | 056 | User & has no factory calendar | Space: object requires documentation | |
58 | 057 | Appointment rule & does not exist (user &) | Space: object requires documentation | |
59 | 058 | Appointment rule & has errors (user &) | Space: object requires documentation | |
60 | 059 | Delivery decision using rules for & | Space: object requires documentation | |
61 | 060 | Delivery by fax to & & | Space: object requires documentation | |
62 | 061 | Fax number & could not be added | Space: object requires documentation | |
63 | 062 | Delivery by XML to & & | Space: object requires documentation | |
64 | 063 | External recipient & | Space: object requires documentation | |
65 | 064 | Error in XML formatting, alert not forwarded | Space: object requires documentation | |
66 | 065 | Alert being forwarded to HTTP destination & | Space: object requires documentation | |
67 | 066 | No response from HTTP destination & | Space: object requires documentation | |
68 | 067 | Response from HTTP destination &: & | Space: object requires documentation | |
69 | 068 | Format of response from HTTP destination & is invalid | Space: object requires documentation | |
70 | 069 | HTTP destination cannot be accessed | Space: object requires documentation | |
71 | 070 | No HTTP destination is defined in Customizing | Space: object requires documentation | |
72 | 071 | No e-mail address is entered in Customizing for XML forwarding | Space: object requires documentation | |
73 | 072 | Delivery by WAP Push to & & | The short text describes the object sufficiently | |
74 | 073 | Alert was generated in logical system & | The short text describes the object sufficiently | |
75 | 074 | No authorization for executing action & | Space: object requires documentation | |
76 | 075 | No IP address for the WAP Gateway has been specified in the configuration | The short text describes the object sufficiently | |
77 | 076 | Recipient &1 does not exist in Address Management | The short text describes the object sufficiently | |
78 | 077 | Restrict your selection further | The short text describes the object sufficiently | |
79 | 078 | Alert (ID &, category &) is being processed | The short text describes the object sufficiently | |
80 | 079 | Alert is being processed by user &1 | The short text describes the object sufficiently | |
81 | 080 | Alert processing (ID &, category &) was terminated | The short text describes the object sufficiently | |
82 | 081 | Alert processing was terminated by user &1 | The short text describes the object sufficiently | |
83 | 082 | Alert processing (ID &, category &) was rejected | The short text describes the object sufficiently | |
84 | 083 | Alert processing was rejected by user &1 | The short text describes the object sufficiently | |
85 | 084 | You are defined as recipient by rule &1 | The short text describes the object sufficiently | |
86 | 085 | Recipient from rule evaluation: &1 | The short text describes the object sufficiently | |
87 | 086 | Alert is locked by another user | The short text describes the object sufficiently | |
88 | 087 | User & is not a recipient of this alert | The short text describes the object sufficiently | |
89 | 088 | Alert with ID & does not exist | The short text describes the object sufficiently | |
90 | 089 | You do not have the authorization required to perform this action | The short text describes the object sufficiently | |
91 | 090 | Unknown error occurred | The short text describes the object sufficiently | |
92 | 091 | Alert processing cannot be rejected | The short text describes the object sufficiently | |
93 | 100 | ** Messages from the Customizing interface ** | Space: object requires documentation | |
94 | 101 | Creation of alert category & | Space: object requires documentation | |
95 | 102 | Alert category & already exists | Space: object requires documentation | |
96 | 103 | Alert category & could not be deleted | Space: object requires documentation | |
97 | 104 | Short text for alert category could not be saved | Space: object requires documentation | |
98 | 105 | Long text for alert category could not be saved | Space: object requires documentation | |
99 | 106 | Container for alert category could not be loaded | Space: object requires documentation | |
100 | 107 | Alert category requires a unique name | Space: object requires documentation | |
101 | 108 | Data was saved | Space: object requires documentation | |
102 | 109 | Could not save data | Space: object requires documentation | |
103 | 110 | Select an entry | Space: object requires documentation | |
104 | 111 | Enter a description for the subsequent activity | Space: object requires documentation | |
105 | 112 | Enter an e-mail address | Space: object requires documentation | |
106 | 113 | Enter an HTTP destination | Space: object requires documentation | |
107 | 114 | Enter the RFC destination for the alert server | Space: object requires documentation | |
108 | 115 | Alert classification & already exists | The short text describes the object sufficiently | |
109 | 116 | Deleting not possible! There are alert categories for the classification | The short text describes the object sufficiently | |
110 | 117 | Deleting not possible! There are subclassifications | Space: object requires documentation | |
111 | 118 | The specified rule &1 does not exist | The short text describes the object sufficiently | |
112 | 119 | Data flow must be checked | The short text describes the object sufficiently | |
113 | 120 | Create data flow between alert container and rule container | The short text describes the object sufficiently | |
114 | 121 | Error while accessing container element &1 | The short text describes the object sufficiently | |
115 | 122 | Internal error while changing recipient rule | The short text describes the object sufficiently | |
116 | 123 | Internal error while creating recipient rule | The short text describes the object sufficiently | |
117 | 124 | Internal error while calling data flow editor | The short text describes the object sufficiently | |
118 | 125 | Internal error in configuration | The short text describes the object sufficiently | |
119 | 126 | The name of the alert category must not contain special characters | The short text describes the object sufficiently | |
120 | 127 | The name of the alert classification must contain only ASCII characters | The short text describes the object sufficiently | |
121 | 128 | Alert classification & does not exist | The short text describes the object sufficiently | |
122 | 150 | ** Messages from Alert Display ** | Space: object requires documentation | |
123 | 151 | Alert has no container | Space: object requires documentation | |
124 | 152 | Error while calling the Alert Inbox | The short text describes the object sufficiently | |
125 | 153 | Error while calling Personalization of the Alert Inbox | The short text describes the object sufficiently | |
126 | 154 | Error while calling Subscription for the Alert Inbox | The short text describes the object sufficiently | |
127 | 200 | ** Messages for the API (SALERT_LOCAL) ** | Space: object requires documentation | |
128 | 201 | RFC destination for alert server cannot be determined | Space: object requires documentation | |
129 | 202 | A alert of category &1 is to be sent | Space: object requires documentation | |
130 | 203 | Communication Error: & & | Space: object requires documentation | |
131 | 204 | System Error: & & | Space: object requires documentation | |
132 | 205 | Confirm alerts with application GUID: & | The short text describes the object sufficiently | |
133 | 206 | Read alerts with application GUID: & | The short text describes the object sufficiently | |
134 | 300 | ** Messages for Inbound Processing ** | Space: object requires documentation | |
135 | 301 | Alert is locked by user & and cannot be confirmed | Space: object requires documentation |
History
Last changed on/by | 20110908 | SAP | |
SAP Release Created in | 300 |