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