SAP ABAP Message Class DNO (Messages for General Notifications)
Basic Data
Hierarchy
☛
SAP_ABA (Software Component) Cross-Application Component
⤷ CA-NO (Application Component) Messages
⤷ DNO (Package) Messages
⤷ CA-NO (Application Component) Messages
⤷ DNO (Package) Messages
Attributes
Message class | DNO | |
Short Description | Messages for General Notifications | |
Changed On | 20110908 | |
Last Changed At | 160704 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 001 | The number & is outside the valid number interval | Space: object requires documentation | |
2 | 002 | Number range for notification type & not maintained | Space: object requires documentation | |
3 | 003 | External number assignment, enter notification number | Space: object requires documentation | |
4 | 004 | Number range does not allow external number assignment | Space: object requires documentation | |
5 | 005 | External notification number contains invalid characters | Space: object requires documentation | |
6 | 010 | Notification &1 blocked by USER &2 | Space: object requires documentation | |
7 | 011 | Error during locking of notification | Space: object requires documentation | |
8 | 012 | Notification &1 blocked. It is being processed externally | The short text describes the object sufficiently | |
9 | 013 | Notification blocked by USER &1 | The short text describes the object sufficiently | |
10 | 020 | Enter the unique ID of the notification | Space: object requires documentation | |
11 | 021 | A notification with number &1 already exists | Space: object requires documentation | |
12 | 022 | No notification exists with GUID &1 | Space: object requires documentation | |
13 | 023 | Notification number &1 does not exist | The short text describes the object sufficiently | |
14 | 030 | You do not have authorization to create a notification | Space: object requires documentation | |
15 | 031 | You do not have authorization to &1 a notification | The short text describes the object sufficiently | |
16 | 040 | Specify a notification type | Space: object requires documentation | |
17 | 041 | No notification type found | Space: object requires documentation | |
18 | 042 | Notificaton type &1 is not defined | Space: object requires documentation | |
19 | 043 | Notification & saved | Space: object requires documentation | |
20 | 044 | Error while saving notification &1: &2 | The short text describes the object sufficiently | |
21 | 045 | No interface defined for notification type &. Display is not possible | The short text describes the object sufficiently | |
22 | 046 | No interface defined for notification type &, processing not possible | The short text describes the object sufficiently | |
23 | 050 | Priority &1 is not valid | Space: object requires documentation | |
24 | 051 | Topic &1 is not valid | Space: object requires documentation | |
25 | 052 | Language &1 is not valid | Space: object requires documentation | |
26 | 053 | Execution date reset according to priority | Space: object requires documentation | |
27 | 060 | Import parameter &1 is missing or incomplete | The short text describes the object sufficiently | |
28 | 061 | Duplicate key when inserting into table &1 | The short text describes the object sufficiently | |
29 | 062 | Error updating table &1 Sy - Subrc = &2 | The short text describes the object sufficiently | |
30 | 063 | Error deleting from table &1 system subscr = &2 | The short text describes the object sufficiently | |
31 | 064 | Change document NOTIF: & | The short text describes the object sufficiently | |
32 | 070 | Partner not created, partner number or address number missing | Space: object requires documentation | |
33 | 071 | Missing partner type for partner number &1 | Space: object requires documentation | |
34 | 072 | Partner type &1 is not recognised | Space: object requires documentation | |
35 | 073 | Missing partner type for partner number &1 | Space: object requires documentation | |
36 | 074 | Partner function &1 is not defined for notification type &2 | Space: object requires documentation | |
37 | 075 | You cannot make changes to partner function &1 | Space: object requires documentation | |
38 | 076 | A partner with partner function &1 already exists | Space: object requires documentation | |
39 | 077 | Enter partner type and partner number | Space: object requires documentation | |
40 | 080 | Specification for assignment of the note incomplete | Space: object requires documentation | |
41 | 081 | Note type &1 unknown | Space: object requires documentation | |
42 | 082 | Error when displaying note &1 of category &2 | The short text describes the object sufficiently | |
43 | 083 | Note installation not possible for category & | The short text describes the object sufficiently | |
44 | 084 | RFC error in notes assistant: & | The short text describes the object sufficiently | |
45 | 085 | Error calling the notes assistant | The short text describes the object sufficiently | |
46 | 086 | Notes assistant: Enter the RFC destination of the target system | The short text describes the object sufficiently | |
47 | 088 | & & & & | The short text describes the object sufficiently | |
48 | 089 | Notification &1 cannot be read, unknown error | The short text describes the object sufficiently | |
49 | 090 | Text will not be created: Text segment type missing | Space: object requires documentation | |
50 | 091 | Text segment type &1 unknown | Space: object requires documentation | |
51 | 092 | No text segment types maintained for notification type &1 | Space: object requires documentation | |
52 | 093 | You cannot make changes to text with text segment type &1 | The short text describes the object sufficiently | |
53 | 100 | No notifications found | Space: object requires documentation | |
54 | 110 | Message &1 sent successfully | Space: object requires documentation | |
55 | 111 | Could not read message &1 | Space: object requires documentation | |
56 | 112 | No authorization to read message &1 | Space: object requires documentation | |
57 | 123 | Attachment with file type &1 (&2) cannot be sent | The short text describes the object sufficiently | |
58 | 150 | The system could not find your SAP customer message system user | Space: object requires documentation | |
59 | 151 | No text information available for SAP | Space: object requires documentation | |
60 | 152 | Error while trying to connect to SAP &1 | Space: object requires documentation | |
61 | 153 | Notification cannot be sent via RFC connection &1 and S-User &2 | Space: object requires documentation | |
62 | 154 | You have not made all required entries in the notification | Space: object requires documentation | |
63 | 155 | Error while saving the notification | Space: object requires documentation | |
64 | 156 | You do not have authorization &1 at SAP | Space: object requires documentation | |
65 | 157 | Installation number not known in the SAP customer notification system | Space: object requires documentation | |
66 | 158 | You are not recognized as a user in the SAP customer notification system | Space: object requires documentation | |
67 | 159 | Invalid entries in field: &1 &2 &3 | Space: object requires documentation | |
68 | 160 | Notification already confirmed in SAP customer notification system | Space: object requires documentation | |
69 | 161 | Notification blocked in SAPNet | The short text describes the object sufficiently | |
70 | 162 | Notification blocked in external system | The short text describes the object sufficiently | |
71 | 163 | Notification could not be blocked | The short text describes the object sufficiently | |
72 | 164 | Error while reading the notification | The short text describes the object sufficiently | |
73 | 165 | Error while saving the notification | The short text describes the object sufficiently | |
74 | 166 | Notification is locked by SAP; no authorization to make changes | Space: object requires documentation | |
75 | 167 | Notification locked by SAP; try again in 5 minutes | Space: object requires documentation | |
76 | 168 | No authorization for this notification | The short text describes the object sufficiently | |
77 | 169 | Entry &1 in table &2 not found | The short text describes the object sufficiently | |
78 | 170 | SAP notification number missing. Not possible to access SAP notification | The short text describes the object sufficiently | |
79 | 171 | Notification has not been changed by SAP | The short text describes the object sufficiently | |
80 | 172 | Notification has been changed by SAP | The short text describes the object sufficiently | |
81 | 173 | The notification cannot be confirmed | Space: object requires documentation | |
82 | 174 | The notification could not be confirmed | The short text describes the object sufficiently | |
83 | 175 | Error when confirming notification | The short text describes the object sufficiently | |
84 | 176 | Partner not found | The short text describes the object sufficiently | |
85 | 177 | Notification created in the SAP customer notification system with no. &1 | Space: object requires documentation | |
86 | 178 | An error occurred when creating the notes | Space: object requires documentation | |
87 | 179 | You are not recognized as a customer at SAP &1 | Space: object requires documentation | |
88 | 180 | Mail was not sent: Text or creator missing | Space: object requires documentation | |
89 | 181 | No notification has been refreshed or newly created | Space: object requires documentation | |
90 | 182 | Notification &1 created | Space: object requires documentation | |
91 | 183 | Notification &1 created in the SAP customer notification system | Space: object requires documentation | |
92 | 184 | Notification &1 confirmed in the SAP customer notification system | Space: object requires documentation | |
93 | 185 | Notification has been compared with SAP customer notification system | Space: object requires documentation | |
94 | 186 | Notification was sent to the SAP customer notification system | Space: object requires documentation | |
95 | 187 | Mail has been sent | Space: object requires documentation | |
96 | 188 | RFC error: &1 &2 | Space: object requires documentation | |
97 | 189 | Action cannot be executed. Message &1 has not yet been sent to SAP. | Space: object requires documentation | |
98 | 190 | None of the installations were assigned to a destination in the BAdI | Space: object requires documentation | |
99 | 191 | The selected installations could not be considered | Space: object requires documentation | |
100 | 192 | Invalid entries in field: &1 &2 &3 | Space: object requires documentation | |
101 | 193 | BAdI incomplete: it may not be possible to compare all notifications | Space: object requires documentation | |
102 | 194 | BAdI incomplete: notification cannot be updated | Space: object requires documentation | |
103 | 195 | No active implementation exists for BAdI DNO_RFC_DATA | The short text describes the object sufficiently | |
104 | 196 | No maintenance active for installation no. in SAP customer notif. system | The short text describes the object sufficiently | |
105 | 198 | Job for notification comparison is running - cancellation, s.a. SM37 | The short text describes the object sufficiently | |
106 | 199 | Notification &1 cannot be created due to disallowed language &2 | The short text describes the object sufficiently | |
107 | 200 | Notification cannot be created under notification &1 | Space: object requires documentation | |
108 | 201 | The parent notification does not exist | The short text describes the object sufficiently | |
109 | 202 | Specify either the notification to the left or to the right | The short text describes the object sufficiently | |
110 | 203 | No hierarchy entry exists for notification &1 | The short text describes the object sufficiently | |
111 | 204 | &1 is not to the right of &2 | The short text describes the object sufficiently | |
112 | 205 | &1 cannot be moved further to the left | The short text describes the object sufficiently | |
113 | 206 | &1 cannot be moved further to the right | The short text describes the object sufficiently | |
114 | 207 | You can only process notifications for exactly one higher-lever node | The short text describes the object sufficiently | |
115 | 208 | The hierarchy for notification &1 has been saved | The short text describes the object sufficiently | |
116 | 210 | Note is already included in the table | Space: object requires documentation | |
117 | 211 | Select a row | Space: object requires documentation | |
118 | 212 | Always enter a note number | Space: object requires documentation | |
119 | 213 | Enter the correct client | The short text describes the object sufficiently | |
120 | 220 | System error when sending to the BC: & & & | The short text describes the object sufficiently | |
121 | 221 | Communication error when sending to BC: & & & | The short text describes the object sufficiently | |
122 | 222 | Internal error when sending to the BC: & & & | The short text describes the object sufficiently | |
123 | 223 | Message &1 &2 does not exist | Space: object requires documentation | |
124 | 224 | Message type &1 is not permitted | Space: object requires documentation | |
125 | 225 | Select at least one status indicator | The short text describes the object sufficiently | |
126 | 230 | Error during log-on. User does not belong to partner &1 | The short text describes the object sufficiently | |
127 | 231 | Error during log-on to SAP. Partner &1 is not permitted | The short text describes the object sufficiently | |
128 | 232 | Internal error during log-on to SAP | The short text describes the object sufficiently | |
129 | 233 | Error when switching to partner mode (ISV) | The short text describes the object sufficiently | |
130 | 234 | A new 7.1 job is running or planned, hence termination, see also SM37 | Space: object requires documentation |
History
Last changed on/by | 20110908 | SAP | |
SAP Release Created in | 50A |