SALERT - Nachrichten f�r das Alert-Framework
The following messages are stored in message class SALERT: Nachrichten f�r das Alert-Framework.
It is part of development package SALERT_LOCAL in software component BC-SRV-GBT-ALM. This development package consists of objects that can be grouped under "Application Interface for Alert Framework".
It is part of development package SALERT_LOCAL in software component BC-SRV-GBT-ALM. This development package consists of objects that can be grouped under "Application Interface for Alert Framework".
Message Nr ▲ | Message Text |
---|---|
000 | *** Message class (000-999) reserved for Alert Framework *** |
001 | You have subscribed to alert category &1 |
002 | You are a recipient of alert category &1 |
003 | You are the escalation recipient for alert category &1 |
004 | Alert forwarded to you by &1 |
005 | The triggering application determined you as a recipient |
006 | You are entered as substitute for &1 |
007 | Alert has no recipients |
008 | Editing locked by user & |
009 | Lock operation failed |
010 | Alert forwarded to &1 successfully |
011 | Alert could not be forwarded to recipient &1 |
012 | Alert category & does not exist |
013 | No alert category specified |
014 | No further information about error |
015 | You have been determined as a recipient using the role & |
016 | Alert could not be deleted |
017 | Alert created. ID: & |
018 | Alert forwarding in XML format |
019 | Alert is generated on the Central Alert Server |
020 | Alert category: & |
021 | Recipient from container: & |
022 | Recipient & not accepted |
023 | Recipient from alert category: & |
024 | Recipient from role assignment: & |
025 | Substitute recipient: & |
026 | Alert has no recipients and will not be created |
027 | Delivery by e-mail to & & |
028 | Delivery by e-mail in XML format to & |
029 | Delivery by SMS (text message) to & & |
030 | Delivery & completed |
031 | External ID of alert: & |
032 | External ID for alert could not be obtained |
033 | Address of recipient & (&) could not be read |
034 | Escalate alert (ID &, category &) |
035 | Deliver alert (ID &, category &) |
036 | Current alert state does not allow escalation |
037 | Alert category & has no escalation |
038 | Escalation recipient: & |
039 | Escalation recipient & could not be added |
040 | Delete alert (ID &, category &) |
041 | Expiry time: & & |
042 | Confirm alert (ID &, category &) |
043 | Confirm alert for user & |
044 | No user specified for confirmation |
045 | Forward alert (ID &) to & |
046 | No user specified for forwarding |
047 | User & already exists as recipient of the alert |
048 | No escalation; alert has already reached expiration date |
049 | A BCS exception (&) was raised |
050 | Send request for & has no recipients |
051 | Communication method & is not supported (&) |
052 | E-mail address & could not be added |
053 | SMS number & (for text message) could not be added |
054 | Sender & could not be assigned |
055 | Business Add-In is not assigned (user &) |
056 | User & has no factory calendar |
057 | Appointment rule & does not exist (user &) |
058 | Appointment rule & has errors (user &) |
059 | Delivery decision using rules for & |
060 | Delivery by fax to & & |
061 | Fax number & could not be added |
062 | Delivery by XML to & & |
063 | External recipient & |
064 | Error in XML formatting, alert not forwarded |
065 | Alert being forwarded to HTTP destination & |
066 | No response from HTTP destination & |
067 | Response from HTTP destination &: & |
068 | Format of response from HTTP destination & is invalid |
069 | HTTP destination cannot be accessed |
070 | No HTTP destination is defined in customizing |
071 | No e-mail address is entered in customizing for XML forwarding |
072 | Delivery by WAP Push to & & |
073 | Alert was generated in logical system & |
074 | No authorization for executing action & |
075 | No IP address for the WAP Gateway has been specified in the configuration |
076 | Recipient &1 does not exist in Address Management |
077 | Restrict your selection further |
078 | Alert (ID &, category &) is being processed |
079 | Alert is being processed by user &1 |
080 | Alert processing (ID &, category &) was terminated |
081 | Alert processing was terminated by user &1 |
082 | Alert processing (ID &, category &) was rejected |
083 | Alert processing was rejected by user &1 |
084 | You are defined as recipient by rule &1 |
085 | Recipient from rule evaluation: &1 |
086 | Alert is locked by another user |
087 | User & is not a recipient of this alert |
088 | Alert with ID & does not exist |
089 | You do not have the authorization required to perform this action |
090 | Unknown error occurred |
091 | Alert processing cannot be rejected |
100 | ** Messages from the Customizing interface ** |
101 | Creation of alert category & |
102 | Alert category & already exists |
103 | Alert category & could not be deleted |
104 | Short text for alert category could not be saved |
105 | Long text for alert category could not be saved |
106 | Container for alert category could not be loaded |
107 | Alert category requires a unique name |
108 | Data was saved |
109 | Could not save data |
110 | Select an entry |
111 | Enter a description for the subsequent activity |
112 | Enter an e-mail address |
113 | Enter an HTTP destination |
114 | Enter the RFC destination for the alert server |
115 | Alert classification & already exists |
116 | Deleting not possible! There are alert categories for the classification |
117 | Deleting not possible! There are subclassifications |
118 | The specified rule &1 does not exist |
119 | Data flow must be checked |
120 | Create data flow between alert container and rule container |
121 | Error while accessing container element &1 |
122 | Internal error while changing recipient rule |
123 | Internal error while creating recipient rule |
124 | Internal error while calling data flow editor |
125 | Internal error in configuration |
126 | The name of the alert category must not contain special characters |
127 | The name of the alert classification must contain only ASCII characters |
128 | Alert classification & does not exist |
150 | ** Messages from Alert Display ** |
151 | Alert has no container |
152 | Error while calling the Alert Inbox |
153 | Error while calling Personalization of the Alert Inbox |
154 | Error while calling Subscription for the Alert Inbox |
200 | ** Messages for the API (SALERT_LOCAL) ** |
201 | RFC destination for alert server cannot be determined |
202 | A alert of category &1 is to be sent |
203 | Communication error: & & |
204 | System error: & & |
205 | Confirm alerts with application GUID: & |
206 | Read alerts with application GUID: & |
300 | ** Messages for Inbound Processing ** |
301 | Alert is locked by user & and cannot be confirmed |