/IWNGW/CM_HUB - Notification Gateway Hub messages
The following messages are stored in message class /IWNGW/CM_HUB: Notification Gateway Hub messages.
It is part of development package /IWNGW/HUB_COS_MESSAGES in software component OPU-GW-NOT. This development package consists of objects that can be grouped under "Notification Channel - Hub - Messages - Fully translated".
It is part of development package /IWNGW/HUB_COS_MESSAGES in software component OPU-GW-NOT. This development package consists of objects that can be grouped under "Notification Channel - Hub - Messages - Fully translated".
Message Nr ▲ | Message Text |
|---|---|
| 000 | The notification cannot be accessed. Notification ID: '&1' |
| 001 | The notification provider action cannot be accessed. Action ID: '&1' |
| 002 | The entity type '&1' is not supported |
| 003 | The function '&1' is not supported |
| 004 | The function import '&1' is not supported |
| 005 | The action '&1' is not supported |
| 006 | The action import '&1' is not supported |
| 007 | Read reference via navigation '&1' not supported |
| 008 | The HTTP destination '&1' configured as SMP destination does not exist |
| 009 | No authorization to use HTTP destination '&1' |
| 010 | HTTP/HTTPS communication is not available |
| 011 | Inernal error occurred |
| 012 | Unexpected exception when creating UUID |
| 013 | Failed to update the metadata cache on the Hub |
| 014 | Internal server error. Failed to get notifications |
| 015 | An http error '&1' occured while getting metadata from external provider |
| 016 | RFC Error: Communication failure |
| 017 | RFC Error: System error |
| 018 | RFC Error: User misses authorization object |
| 019 | BG RFC Queue: Duplicate queue id generated |
| 020 | The provider is not activated |
| 021 | Error while resolving notification related information from the provider |
| 022 | RFC destination not found for the system alias '&1' |
| 023 | There was an exception when firing the notification provider action |
| 024 | Error while fetching notification metadata from provider |
| 025 | Error while fetching notification data from provider |
| 026 | Exception when firing the action '&2' on notification '&1' |
| 027 | The notification with id '&1' was not found |
| 028 | Secure Store SSF application id '&1' not configured |
| 029 | Error while deleting notification(s) from the secure store |
| 030 | Error while updating notification '&1' from the secure store |
| 031 | Error while creating notification '&1' from the secure store |
| 032 | Secure Store SSF envelop failed |
| 033 | Secure Store SSF develop failed |
| 034 | Secure Store Access Failure |
| 035 | Could not create HTTP client |
| 036 | CSRF token not found |
| 037 | Unable to fetch metadata from provider |
| 038 | Conversion of data type String to xstring failed |
| 039 | EDM error has occurred |
| 040 | &1 &2 &3 &4 |
| 041 | The requested entity of type '&1' does not exist |
| 042 | The entity of type '&1' already exists |
| 043 | Parsing of .xml batch into ABAP failed due to invalid entry |
| 044 | No authorization to access HTTP destination: Contact system administrator |
| 045 | HTTP destination does not exist |
| 046 | Could not read the HTTP destination |
| 047 | Error while creating the HTTP client from the destination |
| 048 | Unknown error while creating an HTTP client |
| 049 | Action &1 completed successfully for &2 out of &3 Notifications |
| 050 | Action &1 completed on notification id &2 |
| 051 | The action '&1' is not valid for ParentId '&2' |
| 052 | Exception while executing the action '&2' on ParentId '&1' |
| 053 | Notification(s) with ParentId '&1' does not exist |
| 054 | Update of Entity Type '&1' failed |
| 055 | The action '&1' is not valid for NotificationId '&2' |
| 056 | Default priority is not in correct format |
| 057 | All the recipients are invalid |
| 058 | No Notifications found for given input |
| 059 | Notifications not found for some inputs |
| 060 | Notification could not be created |
| 061 | All Notifications were not deleted succesfully.So, process is cancelled. |
| 062 | Select atleast one option to clear the cache on hub |
| 063 | Notification is not sent to these recipients, as they are not valid |
| 064 | Either provider id or source id or origin id not passed |
| 065 | Creation of batch failed beacuse of wrong change set |
| 066 | Bad request for execution of function import |
| 067 | Exception occured while deleting the notification '&1' |
| 068 | Exception occured while deleting notifications with parent id '&1' |
| 069 | No notification for user '&1' with notification id '&2' |
| 070 | Processing in hub started |
| 071 | Notification created in hub system |
| 072 | User does not have a notification with id '&1' |
| 073 | Push notifications to client started |
| 074 | Callback not performed as metadata and data are available on hub |
| 075 | RFC callback performed to resolve metadata or data (system alias '&1') |
| 076 | Http error '&1' occured while delivering notifications to smp/hcpms |
| 077 | OData callback performed to resolve metadata or data (system alias '&1') |
| 078 | Ping sent using websocket to recipients for whom do not deliver is false |
| 079 | Push channels not active or not registered |
| 080 | Error in abap push channel while sending notification using websocket |
| 081 | Error in abap message channel while sending notification using websocket |
| 082 | An error in abap channels message type Push Channel Protocol occured |
| 083 | Notification(s) delivered through channel SMP |
| 084 | Action &1 not completed |
| 085 | Notification(s) of type &1 with vers. &2 text &3 from provider &4 ignored |
| 086 | User does not have authorization to invoke the RFC |
| 087 | Call to create notification(s) completed for valid recipients |
| 088 | No http client found for destination '&1' |
| 089 | Csrf token or rest client not found while getting metadata in callback |
| 090 | Notification(s) marked read |
| 091 | Notification with id &1 dismissed for this user |
| 092 | All notifications with parent id &1 are dismissed for this user |
| 093 | Badge number is reset |
| 094 | System Alias not maintained with name &1 |
| 095 | |
| 096 | Badge number received |
| 097 | Missing implementation of methods in provider |
| 098 | No authorization to read '&1'. |
| 099 | No authorization to maintain/delete '&1'. |
| 100 | Notifications (if any) fetched |
| 101 | Actions fetched successfully |
| 102 | Navigation parameter fetched successfully |
| 103 | User setting for notification type, (if any) fetched |
| 104 | Push channel fetched successfully |
| 105 | User setting for notification type id &1 updated |
| 106 | There are few invalid recipients in the request |
| 107 | Notification(s) marked read and seen |
| 108 | Updating badge count |
| 109 | Failed to mark the notifications as read |
| 110 | Processing in hub started for &1 |
| 111 | No notification present in the hub for the user &1 |
| 112 | There was an exception raised from provider |
| 114 | Deleting notifications as per provider settings |
| 115 | Notification recipient entry deleted for user who triggered action |
| 116 | Notification instance deleted for notification(s) |
| 117 | All notification recipient(s) deleted for given source id |
| 118 | Notifications are not deleted as per provider settings |
| 119 | All notification instances deleted for given input |
| 120 | No user setting for notification type available |
| 121 | Call back not performed as system alias is invalid |
| 122 | Processing in hub ended |
| 123 | Ping not sent through channel websocket as it is not active |
| 124 | Error in odata notification provider RFC |
| 125 | RFC Error: |
| 126 | Invalid recipients exist for below source id(s) |
| 127 | Action &1 completed for parent id &2 |
| 128 | Notification(s) not created as all recipients are invalid in hub |
| 129 | Action &1 completed |
| 130 | Information |
| 131 | You can maintain System Aliases for Notification Channel in this new view |
| 132 | ABAP push channel for notification is inactive |
| 133 | HTML Codepage not found |
| 134 | Email not delivered to below recepients of notification '&1' |
| 135 | Email will not be delivered to all recepients of notification '&1' |
| 136 | Empty Space not allowed in the field SAP System Alias |
| 137 | Special Characters not allowed in the field SAP System Alias |
| 138 | Email notification not sent for ID '&1' in lang '&2' from provider '&3' |
| 139 | Push Channel '&1' not registered. |
| 140 | Notification(s) of type &1 with version &2 from provider &3 is ignored |
| 141 | Outbound channel '&1' created successfully. |
| 142 | Entry for outbound channel '&1' found. |
| 143 | Outbound channel '&1' deleted successfully. |
| 144 | System alias '&1' created successfully. |
| 145 | System alias '&1' was found. |
| 146 | System alias '&1' deleted successfully. |
| 147 | Outbound channel '&1' already exists. |
| 148 | Destination and OAuth Profile for SAP Cloud Service not maintained |
| 149 | HTTP Client could not be created for Destination &1 |
| 150 | Notification not sent to User &1 on SAP Cloud Notification Service |
| 151 | Notification &1 not sent to SAP Cloud Notification Service |
| 152 | bgRFC Configurations are not properly maintained for queue &1 |
| 153 | Notifications will be sent without bgRFC Queue |
| 154 | Exception creating OAuth Client with maintained configuration |
| 155 | Exception during OAuth Token fetch. Please check configuration |