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
⤷
⤷
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 | The number & is outside the valid number interval | Space: object requires documentation | ||
| 2 | Number range for notification type & not maintained | Space: object requires documentation | ||
| 3 | External number assignment, enter notification number | Space: object requires documentation | ||
| 4 | Number range does not allow external number assignment | Space: object requires documentation | ||
| 5 | External notification number contains invalid characters | Space: object requires documentation | ||
| 6 | Notification &1 blocked by USER &2 | Space: object requires documentation | ||
| 7 | Error during locking of notification | Space: object requires documentation | ||
| 8 | Notification &1 blocked. It is being processed externally | The short text describes the object sufficiently | ||
| 9 | Notification blocked by USER &1 | The short text describes the object sufficiently | ||
| 10 | Enter the unique ID of the notification | Space: object requires documentation | ||
| 11 | A notification with number &1 already exists | Space: object requires documentation | ||
| 12 | No notification exists with GUID &1 | Space: object requires documentation | ||
| 13 | Notification number &1 does not exist | The short text describes the object sufficiently | ||
| 14 | You do not have authorization to create a notification | Space: object requires documentation | ||
| 15 | You do not have authorization to &1 a notification | The short text describes the object sufficiently | ||
| 16 | Specify a notification type | Space: object requires documentation | ||
| 17 | No notification type found | Space: object requires documentation | ||
| 18 | Notificaton type &1 is not defined | Space: object requires documentation | ||
| 19 | Notification & saved | Space: object requires documentation | ||
| 20 | Error while saving notification &1: &2 | The short text describes the object sufficiently | ||
| 21 | No interface defined for notification type &. Display is not possible | The short text describes the object sufficiently | ||
| 22 | No interface defined for notification type &, processing not possible | The short text describes the object sufficiently | ||
| 23 | Priority &1 is not valid | Space: object requires documentation | ||
| 24 | Topic &1 is not valid | Space: object requires documentation | ||
| 25 | Language &1 is not valid | Space: object requires documentation | ||
| 26 | Execution date reset according to priority | Space: object requires documentation | ||
| 27 | Import parameter &1 is missing or incomplete | The short text describes the object sufficiently | ||
| 28 | Duplicate key when inserting into table &1 | The short text describes the object sufficiently | ||
| 29 | Error updating table &1 Sy - Subrc = &2 | The short text describes the object sufficiently | ||
| 30 | Error deleting from table &1 system subscr = &2 | The short text describes the object sufficiently | ||
| 31 | Change document NOTIF: & | The short text describes the object sufficiently | ||
| 32 | Partner not created, partner number or address number missing | Space: object requires documentation | ||
| 33 | Missing partner type for partner number &1 | Space: object requires documentation | ||
| 34 | Partner type &1 is not recognised | Space: object requires documentation | ||
| 35 | Missing partner type for partner number &1 | Space: object requires documentation | ||
| 36 | Partner function &1 is not defined for notification type &2 | Space: object requires documentation | ||
| 37 | You cannot make changes to partner function &1 | Space: object requires documentation | ||
| 38 | A partner with partner function &1 already exists | Space: object requires documentation | ||
| 39 | Enter partner type and partner number | Space: object requires documentation | ||
| 40 | Specification for assignment of the note incomplete | Space: object requires documentation | ||
| 41 | Note type &1 unknown | Space: object requires documentation | ||
| 42 | Error when displaying note &1 of category &2 | The short text describes the object sufficiently | ||
| 43 | Note installation not possible for category & | The short text describes the object sufficiently | ||
| 44 | RFC error in notes assistant: & | The short text describes the object sufficiently | ||
| 45 | Error calling the notes assistant | The short text describes the object sufficiently | ||
| 46 | Notes assistant: Enter the RFC destination of the target system | The short text describes the object sufficiently | ||
| 47 | & & & & | The short text describes the object sufficiently | ||
| 48 | Notification &1 cannot be read, unknown error | The short text describes the object sufficiently | ||
| 49 | Text will not be created: Text segment type missing | Space: object requires documentation | ||
| 50 | Text segment type &1 unknown | Space: object requires documentation | ||
| 51 | No text segment types maintained for notification type &1 | Space: object requires documentation | ||
| 52 | You cannot make changes to text with text segment type &1 | The short text describes the object sufficiently | ||
| 53 | No notifications found | Space: object requires documentation | ||
| 54 | Message &1 sent successfully | Space: object requires documentation | ||
| 55 | Could not read message &1 | Space: object requires documentation | ||
| 56 | No authorization to read message &1 | Space: object requires documentation | ||
| 57 | Attachment with file type &1 (&2) cannot be sent | The short text describes the object sufficiently | ||
| 58 | The system could not find your SAP customer message system user | Space: object requires documentation | ||
| 59 | No text information available for SAP | Space: object requires documentation | ||
| 60 | Error while trying to connect to SAP &1 | Space: object requires documentation | ||
| 61 | Notification cannot be sent via RFC connection &1 and S-User &2 | Space: object requires documentation | ||
| 62 | You have not made all required entries in the notification | Space: object requires documentation | ||
| 63 | Error while saving the notification | Space: object requires documentation | ||
| 64 | You do not have authorization &1 at SAP | Space: object requires documentation | ||
| 65 | Installation number not known in the SAP customer notification system | Space: object requires documentation | ||
| 66 | You are not recognized as a user in the SAP customer notification system | Space: object requires documentation | ||
| 67 | Invalid entries in field: &1 &2 &3 | Space: object requires documentation | ||
| 68 | Notification already confirmed in SAP customer notification system | Space: object requires documentation | ||
| 69 | Notification blocked in SAPNet | The short text describes the object sufficiently | ||
| 70 | Notification blocked in external system | The short text describes the object sufficiently | ||
| 71 | Notification could not be blocked | The short text describes the object sufficiently | ||
| 72 | Error while reading the notification | The short text describes the object sufficiently | ||
| 73 | Error while saving the notification | The short text describes the object sufficiently | ||
| 74 | Notification is locked by SAP; no authorization to make changes | Space: object requires documentation | ||
| 75 | Notification locked by SAP; try again in 5 minutes | Space: object requires documentation | ||
| 76 | No authorization for this notification | The short text describes the object sufficiently | ||
| 77 | Entry &1 in table &2 not found | The short text describes the object sufficiently | ||
| 78 | SAP notification number missing. Not possible to access SAP notification | The short text describes the object sufficiently | ||
| 79 | Notification has not been changed by SAP | The short text describes the object sufficiently | ||
| 80 | Notification has been changed by SAP | The short text describes the object sufficiently | ||
| 81 | The notification cannot be confirmed | Space: object requires documentation | ||
| 82 | The notification could not be confirmed | The short text describes the object sufficiently | ||
| 83 | Error when confirming notification | The short text describes the object sufficiently | ||
| 84 | Partner not found | The short text describes the object sufficiently | ||
| 85 | Notification created in the SAP customer notification system with no. &1 | Space: object requires documentation | ||
| 86 | An error occurred when creating the notes | Space: object requires documentation | ||
| 87 | You are not recognized as a customer at SAP &1 | Space: object requires documentation | ||
| 88 | Mail was not sent: Text or creator missing | Space: object requires documentation | ||
| 89 | No notification has been refreshed or newly created | Space: object requires documentation | ||
| 90 | Notification &1 created | Space: object requires documentation | ||
| 91 | Notification &1 created in the SAP customer notification system | Space: object requires documentation | ||
| 92 | Notification &1 confirmed in the SAP customer notification system | Space: object requires documentation | ||
| 93 | Notification has been compared with SAP customer notification system | Space: object requires documentation | ||
| 94 | Notification was sent to the SAP customer notification system | Space: object requires documentation | ||
| 95 | Mail has been sent | Space: object requires documentation | ||
| 96 | RFC error: &1 &2 | Space: object requires documentation | ||
| 97 | Action cannot be executed. Message &1 has not yet been sent to SAP. | Space: object requires documentation | ||
| 98 | None of the installations were assigned to a destination in the BAdI | Space: object requires documentation | ||
| 99 | The selected installations could not be considered | Space: object requires documentation | ||
| 100 | Invalid entries in field: &1 &2 &3 | Space: object requires documentation | ||
| 101 | BAdI incomplete: it may not be possible to compare all notifications | Space: object requires documentation | ||
| 102 | BAdI incomplete: notification cannot be updated | Space: object requires documentation | ||
| 103 | No active implementation exists for BAdI DNO_RFC_DATA | The short text describes the object sufficiently | ||
| 104 | No maintenance active for installation no. in SAP customer notif. system | The short text describes the object sufficiently | ||
| 105 | Job for notification comparison is running - cancellation, s.a. SM37 | The short text describes the object sufficiently | ||
| 106 | Notification &1 cannot be created due to disallowed language &2 | The short text describes the object sufficiently | ||
| 107 | Notification cannot be created under notification &1 | Space: object requires documentation | ||
| 108 | The parent notification does not exist | The short text describes the object sufficiently | ||
| 109 | Specify either the notification to the left or to the right | The short text describes the object sufficiently | ||
| 110 | No hierarchy entry exists for notification &1 | The short text describes the object sufficiently | ||
| 111 | &1 is not to the right of &2 | The short text describes the object sufficiently | ||
| 112 | &1 cannot be moved further to the left | The short text describes the object sufficiently | ||
| 113 | &1 cannot be moved further to the right | The short text describes the object sufficiently | ||
| 114 | You can only process notifications for exactly one higher-lever node | The short text describes the object sufficiently | ||
| 115 | The hierarchy for notification &1 has been saved | The short text describes the object sufficiently | ||
| 116 | Note is already included in the table | Space: object requires documentation | ||
| 117 | Select a row | Space: object requires documentation | ||
| 118 | Always enter a note number | Space: object requires documentation | ||
| 119 | Enter the correct client | The short text describes the object sufficiently | ||
| 120 | System error when sending to the BC: & & & | The short text describes the object sufficiently | ||
| 121 | Communication error when sending to BC: & & & | The short text describes the object sufficiently | ||
| 122 | Internal error when sending to the BC: & & & | The short text describes the object sufficiently | ||
| 123 | Message &1 &2 does not exist | Space: object requires documentation | ||
| 124 | Message type &1 is not permitted | Space: object requires documentation | ||
| 125 | Select at least one status indicator | The short text describes the object sufficiently | ||
| 126 | Error during log-on. User does not belong to partner &1 | The short text describes the object sufficiently | ||
| 127 | Error during log-on to SAP. Partner &1 is not permitted | The short text describes the object sufficiently | ||
| 128 | Internal error during log-on to SAP | The short text describes the object sufficiently | ||
| 129 | Error when switching to partner mode (ISV) | The short text describes the object sufficiently | ||
| 130 | 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 |