DNO - Nachrichten zu Basismeldungen
The following messages are stored in message class DNO: Nachrichten zu Basismeldungen.
It is part of development package DNO in software component CA-NO. This development package consists of objects that can be grouped under "Notifications".
It is part of development package DNO in software component CA-NO. This development package consists of objects that can be grouped under "Notifications".
Message Nr ▲ | Message Text |
|---|---|
| 001 | The number & is outside the valid number interval |
| 002 | Number range for notification type & not maintained |
| 003 | External number assignment, enter notification number |
| 004 | Number range does not allow external number assignment |
| 005 | External notification number contains invalid characters |
| 010 | Notification &1 blocked by USER &2 |
| 011 | Error during locking of notification |
| 012 | Notification &1 blocked. It is being processed externally |
| 013 | Notification blocked by USER &1 |
| 020 | Enter the unique ID of the notification |
| 021 | A notification with number &1 already exists |
| 022 | No notification exists with GUID &1 |
| 023 | Notification number &1 does not exist |
| 030 | You do not have authorization to create a notification |
| 031 | You do not have authorization to &1 a notification |
| 040 | Specify a notification type |
| 041 | No notification type found |
| 042 | Notificaton type &1 is not defined |
| 043 | Notification & saved |
| 044 | Error while saving notification &1: &2 |
| 045 | No interface defined for notification type &. Display is not possible |
| 046 | No interface defined for notification type &, processing not possible |
| 050 | Priority &1 is not valid |
| 051 | Topic &1 is not valid |
| 052 | Language &1 is not valid |
| 053 | Execution date reset according to priority |
| 060 | Import parameter &1 is missing or incomplete |
| 061 | Duplicate key when inserting into table &1 |
| 062 | Error updating table &1 Sy - Subrc = &2 |
| 063 | Error deleting from table &1 system subscr = &2 |
| 064 | Change document NOTIF: & |
| 070 | Partner not created, partner number or address number missing |
| 071 | Missing partner type for partner number &1 |
| 072 | Partner type &1 is unknown |
| 073 | Missing partner type for partner number &1 |
| 074 | Partner function &1 is not defined for notification type &2 |
| 075 | You cannot make changes to partner function &1 |
| 076 | A partner with partner function &1 already exists |
| 077 | Enter partner type and partner number |
| 080 | Specification for assignment of the note incomplete |
| 081 | Note type &1 unknown |
| 082 | Error when displaying note &1 of category &2 |
| 083 | Note installation not possible for category & |
| 084 | RFC error in notes assistant: & |
| 085 | Error calling the notes assistant |
| 086 | Notes assistant: Enter the RFC destination of the target system |
| 088 | & & & & |
| 089 | Notification &1 cannot be read, unknown error |
| 090 | Text will not be created: Text segment type missing |
| 091 | Text segment type &1 unknown |
| 092 | No text segment types maintained for notification type &1 |
| 093 | You cannot make changes to text with text segment type &1 |
| 100 | No notifications found |
| 110 | Message &1 sent |
| 111 | Could not read message &1 |
| 112 | No authorization to read message &1 |
| 123 | Attachment with file type &1 (&2) cannot be sent |
| 150 | The system could not find your SAP customer message system user |
| 151 | No text information for SAP exists |
| 152 | Error while trying to connect to SAP &1 |
| 153 | Notification cannot be sent using RFC connection &1 and S user &2 |
| 154 | You have not made all required entries in the notification |
| 155 | Error while saving the notification |
| 156 | You do not have authorization &1 at SAP |
| 157 | Installation number not known in the SAP customer notification system |
| 158 | You are not recognized as a user in the SAP customer notification system |
| 159 | Invalid entries in field: &1 &2 &3 |
| 160 | Notification already confirmed in SAP customer notification system |
| 161 | Notification blocked in SAPNet |
| 162 | Notification blocked in external system |
| 163 | Notification could not be blocked |
| 164 | Error while reading the notification |
| 165 | Error while saving the notification |
| 166 | Notification is locked by SAP; no authorization to make changes |
| 167 | Notification locked by SAP; try again in 5 minutes |
| 168 | No authorization for this notification |
| 169 | Entry &1 in table &2 not found |
| 170 | SAP notification number missing. Not possible to access SAP notification |
| 171 | Notification has not been changed by SAP |
| 172 | Notification has been changed by SAP |
| 173 | The notification cannot be confirmed |
| 174 | The notification could not be confirmed |
| 175 | Error when confirming notification |
| 176 | Partner not found |
| 177 | Notification created in the SAP customer notification system with no. &1 |
| 178 | An error occurred when creating the notes |
| 179 | You are not recognized as a customer at SAP &1 |
| 180 | Mail was not sent: Text or creator missing |
| 181 | No notification has been refreshed or newly created |
| 182 | Notification &1 created |
| 183 | Notification &1 created in the SAP customer notification system |
| 184 | Notification &1 confirmed in the SAP customer notification system |
| 185 | Notification has been compared with SAP customer notification system |
| 186 | Notification was sent to the SAP customer notification system |
| 187 | Mail has been sent |
| 188 | RFC error: &1 &2 |
| 189 | Action cannot be executed. Message &1 has not yet been sent to SAP. |
| 190 | None of the installations were assigned to a destination in the BAdI |
| 191 | The selected installations were ignored |
| 192 | Invalid entries in field: &1 &2 &3 |
| 193 | BAdI incomplete: it may not be possible to compare all notifications |
| 194 | BAdI incomplete: notification cannot be updated |
| 195 | No active implementation exists for BAdI DNO_RFC_DATA |
| 196 | No maintenance active for installation no. in SAP customer notif. system |
| 198 | Job for notification comparison is running so canceled; see also SM37 |
| 199 | Notification &1 cannot be created due to disallowed language &2 |
| 200 | Notification cannot be created under notification &1 |
| 201 | The parent notification does not exist |
| 202 | Specify either the notification to the left or to the right |
| 203 | No hierarchy entry exists for notification &1 |
| 204 | &1 is not to the right of &2 |
| 205 | &1 cannot be moved further to the left |
| 206 | &1 cannot be moved further to the right |
| 207 | You can only process notifications for exactly one higher-lever node |
| 208 | The hierarchy for notification &1 has been saved |
| 210 | Note is already included in the table |
| 211 | Select a row |
| 212 | Always enter a note number |
| 213 | Enter the correct client |
| 220 | System error when sending to the BC: & & & |
| 221 | Communication error when sending to BC: & & & |
| 222 | Internal error when sending to the BC: & & & |
| 223 | Message &1 &2 does not exist |
| 224 | Message type &1 is not permitted |
| 225 | Select at least one status indicator |
| 230 | Error during log-on. User does not belong to partner &1 |
| 231 | Error during log-on to SAP. Partner &1 is not permitted |
| 232 | Internal error during log-on to SAP |
| 233 | Error when switching to partner mode (ISV) |
| 234 | A new 7.1 job is running or planned, hence termination, see also SM37 |