MSG_CL_ER - Message Class for Enterprise Registry
The following messages are stored in message class MSG_CL_ER: Message Class for Enterprise Registry.
It is part of development package SOAP_CONFIG_SR in software component BC-ESI-WS-ABA-CFG. This development package consists of objects that can be grouped under "Web Services Configuration Services Registry Consumer".
It is part of development package SOAP_CONFIG_SR in software component BC-ESI-WS-ABA-CFG. This development package consists of objects that can be grouped under "Web Services Configuration Services Registry Consumer".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Proxy instantiation error |
| 001 | Services Registry parameters not found in customizing |
| 002 | Error during endpoint publication |
| 003 | Exception raised during physical system publication. Code : '&1' |
| 004 | Physical system was published successfully |
| 005 | All publication stamps deleted for Services Registry "&1" |
| 006 | Error during proxy instance creation |
| 007 | Error during cache update for classification system meta data/values |
| 008 | Error importing file &1 |
| 009 | Client copied. Physical system re-published |
| 010 | Service &1 contains invalid tModel key &2 |
| 011 | Physical system validated successfully |
| 012 | Classification system cache updated from Services Registry |
| 013 | Service definition "&1" published successfully in Services Registry |
| 014 | Endpoint(s) for service &1 published successfully in Services Registry |
| 015 | Physical system republished along with deployment units |
| 016 | Error occurred during service definition(s) &1 publication |
| 017 | Error saving values for classification system &1 |
| 018 | Physical system was published with existing Deployment Units in system |
| 019 | Error retreiving physical system from Services Registry |
| 020 | Publcation rule saved for classification system &1 |
| 021 | No changes made in rule for classification system &1 |
| 022 | No service(s) to be published with the given criteria |
| 023 | Restricted publication is active |
| 024 | No classification system maintained. Restrictions not possible |
| 025 | No sufficient authorisations: &1. Ask user administrator |
| 026 | Services Registry name : &1. Logical port : &2 |
| 027 | Services Registry version is &1 |
| 028 | Error retrieving Services Registry (SR) version information |
| 029 | Service definition &1 not processed |
| 030 | Wrong selection criteria |
| 031 | There can be only one primary Services Registry. Check field 'Primary' |
| 032 | Service endpoints for service definition &1 not found/processed |
| 033 | Error occurred while publishing service definition &1 |
| 034 | Error retrieving design time WSDL URL |
| 035 | Error reading configuration(s) for service definition &1: &2 |
| 036 | Error fetching service info: SD &1, Service &2, Binding &3 |
| 037 | Endpoint published. WSD:&1, Service:&2, Endpoint:&3 |
| 038 | Error publishing Endpoint for SD : &1, Service : &2, EP : &3 |
| 039 | New classification values saved in Services Registry |
| 040 | No new classification values found in backend for Services Registry |
| 041 | No Publication possible from Integration Server(IS) |
| 042 | Invalid PortType Name.Publication not possible for Service Definition &1 |
| 043 | Invalid WSDL url. Publication not possible for Service Definition &1 |
| 044 | The process of hiding for the backend system started as background job |
| 045 | The process of synchronization of services started as background job |
| 046 | Error retrieving design time WSDL URL for Service Definition &1 |
| 047 | Framework exception: &1&2&3&4 |
| 048 | Physical System gets published in the Services Registry '&1' |
| 049 | Endpoint(s) for Service Definition &1 removed in Services Registry &2 |
| 050 | Error: &1&2&3&4 |
| 051 | &1&2&3&4 |
| 052 | Error occurred during consumer(s) &1 publication |
| 053 | Service Definition &1 published in Services Registry &2 |
| 054 | IBC &1 published in Services Registry &2. |
| 055 | Bindings with Key &1 published in Services Registry &2 |
| 056 | Original System &1 published in Services Registry &2 |
| 057 | Service Definition &1 removed from Services Registry &2 |
| 058 | IBC &1 removed from Services Registry &2 |
| 059 | All bindings of Service Definition &1 removed from Services Registry &2 |
| 060 | Deletion of object &1 (Type: &2) suceeded |
| 061 | All Bindings of Service Definition &1 published to Services Registry &2 |
| 062 | No Central/Primary Services Registry connection maintained in this system |
| 063 | Error reading Message Type information in cache for consumer proxy '&1' |
| 064 | Error reading Binding Information for PublicationID & from Registry & |
| 065 | System with application key &1 removed from Services Registry &2 |
| 066 | Consumer logical port &1 removed from Services Registry &2 |
| 067 | Cannot find matching objects since list of classification is empty |
| 068 | Getting classifications for registry '&1' failed |
| 069 | Getting classification value for registry '&1' failed |
| 070 | Services Registry connections with Proxy Class '&1' or '&2' allowed |
| 071 | No Services Registry connection '&1' found in this system |
| 072 | Invalid bindings of Service Definition &1 removed from Registry &2 |
| 092 | No Services Registry connection maintained in this system |
| 093 | No primary Services Registry maintained in this system |
| 100 | Not a valid classification system (tModel Key). |
| 101 | Not a valid classification value (classification Code). |
| 102 | No values found. |
| 103 | Enter tModel Key first. |
| 104 | Error during file import process. |
| 105 | Not a valid service ESR Name &1. |
| 106 | Blank ESR Name found in the file. |
| 107 | Import process for file ----- &1 -----. |
| 108 | Classification saved successfully... |
| 109 | Error saving classifications. |
| 110 | No service to go further. Use change operation if needed. |
| 111 | Service &1 classified, &2 and val &3. |
| 112 | Error classifying service &1 with class &2 and val &3. |
| 113 | No Service to go further. Use create operation if needed. |
| 114 | NW BASIS:&1. Operation '&2' not implemented for Service '&3' '&4' |
| 115 | Please enter valid service name(s). |
| 116 | Error retrieving classification systems and their values from Registry. |
| 117 | Error during deletion of classifications |
| 118 | This transaction is obsolete; please edit services in transaction SE80 |
| 119 | This program is obsolete. More information can be found in Note 1319742 |
| 120 | Classification system &1 is for read only purpose. |
| 121 | Classification system &1 used more than once. |
| 122 | Manual usage of classification system "&1" is forbidden in this release. |
| 123 | Checks failed with classification system &1 |
| 125 | Object &1 already locked |
| 126 | User &1 does not have sufficient authorisations. |
| 127 | Internal error changing object &1. |
| 128 | Operation not allowed on deleted object &1. |
| 130 | Invalid object state: Not persistent and no modification |
| 132 | Empty value for &1 not permitted |
| 133 | Object not locked: &1 |
| 134 | Insufficient parameters: One of &1 &2 &3 &4 not provided |
| 135 | Entry with key-value combination already exists: &1 - &2 |
| 136 | Object not available: &1 |
| 137 | Fatal error in application logic: &1 |
| 138 | Unknown described entitiy: &1 |
| 139 | Dynamic SQL error |
| 140 | Object already exists: &1 |
| 141 | System publication failed: Logical Key = &1, UDDI Key = &2 |
| 142 | System &1 does not exist |
| 143 | Invalid object state: Not persistent and updated |
| 144 | Unknown ISO language: &1 |
| 145 | Unknown SAP language: &1 |
| 146 | IBC &1 does not exist |
| 147 | WSD publication failed: Logical Key = &1, UDDI Key = &2 |
| 148 | SEP publiciation failed: Service Log. Key = &1, Binding Log. Key = &2 |
| 149 | WSD &1 does not exist |
| 150 | SEP &1 does not exist |
| 151 | Classification &1 does not exist |
| 152 | WSD &1 can not be deleted because of &2 child SEPs. |
| 153 | System &1 can not be deleted because of &2 child WSDs. |
| 154 | Logical key(s) missing! |
| 155 | Classification system publication failed: Uddi key = &1 |
| 156 | Publication to predefined classification system not allowed! |
| 157 | Classification system &1 does not exist |
| 158 | Value &1 does not exist in classification system &2 |
| 159 | Classification system &1 is read only |
| 160 | Insufficient key: &1 required |
| 161 | Insufficient key: &1 &2 required |
| 162 | Insufficient key: &1 &2 &3 required |
| 163 | Insufficient key: &1 &2 &3 &4 required |
| 164 | Invalid update: &1 may not be changed |
| 165 | Invalid update: &1 &2 may not be changed |
| 166 | Invalid update: &1 &2 &3 may not be changed |
| 167 | Unknown physical system type: &1 |
| 168 | Technical name may not be changed |
| 169 | TModel Key may not be changed |
| 170 | Insufficient parameters: TModel Key is missing |
| 171 | Insufficient parameters: Qualified Name is missing |
| 172 | Insufficient parameters: TModel Key and Qualified Name are missing |
| 173 | Insufficient parameters: Classification value may not be empty |
| 174 | Invalid update: Attempt to change readonly data |
| 175 | UDDI Key may not be initial |
| 176 | Name may not be initial |
| 177 | Namespace may not be initial |
| 178 | Value &1 of Classification System &2(&3) is in use and can not be deleted |
| 179 | Classification System &1(&2) is in use and can not be deleted |
| 180 | Unknown Web Service Definition Configuration State &1 |
| 181 | Parameters generated for Services Registry '&1' using proxy class '&2' |
| 182 | Parameters deleted for Services Registry '&1' using proxy class '&2' |
| 183 | Parameters for Services Registry '&1' does not exist |
| 184 | Services Identifier data created with Business Application ID '&1' |
| 185 | Services Identifier data updated with Business Application ID '&1' |
| 186 | Reverse Proxy '&1' deleted. ( &2 | &3 | &4 ) |
| 187 | Reverse Proxy '&1' created. ( &2 | &3 | &4 ) |
| 188 | Reverse Proxy '&1' updated. ( &2 | &3 | &4 ) |
| 189 | Service Definition '&1' is not allowed to be published. |
| 190 | IBC &1 does not exist. |
| 191 | Application &1 can not be deleted because of &2 dependent objects. |
| 192 | IBC publication failed: Logical Key = &1 |
| 193 | Application publication failed: Logical Key = &1, UDDI-key = &2 |
| 194 | Logical Key '&1' already registered with Application Key '&2' |
| 195 | Application not registered with Change Key &1 |
| 196 | System not found in Services Registry belonging to Change Key &1 |
| 197 | Application change key cannot be empty |
| 198 | Application not registered with Application Key &1 |
| 199 | Application key cannot be empty |
| 200 | Error scheduling background publication job &3/&2 for Registry &1. |
| 201 | Error updating background publication job &3/&2 for Registry &1. |
| 202 | Error deleting background publication job &3/&2 for Registry &1. |
| 203 | There are active assignments for publication rule &1 |
| 204 | There are active assignments for services registry &1 |
| 205 | IBC '&1' is not allowed to be published |
| 206 | Binding '&1' of service definition '&2' is not allowed to be published |
| 207 | IBC publication failed: Logical Key = &1 |
| 208 | Import of Classification &1 failed. |
| 209 | Import of Classification &1 failed: &2 |
| 210 | Import of IBC &1 failed. |
| 211 | Import of IBC &1 failed: &2 |
| 212 | Import of Binding &1 failed. |
| 213 | Import of Binding &1 failed: &2 |
| 214 | Import of Service Definition &1 failed |
| 215 | Import of Service Definition &1 failed: &2 |
| 216 | Import of System &1 failed |
| 217 | Import of System &1 failed: &2 |
| 218 | Assignment for classification value &1 failed: &2 |
| 219 | Invalid PortType Name. Publication not possible for Consumer &1 |
| 220 | Service Definition '&1' is not allowed to be published |
| 221 | Consumer &1 does not exist |
| 222 | Relation &1 does not exist |
| 223 | Insufficient parameters: Object guid for relation is empty. |
| 224 | Insufficient parameters: Object type for relation is empty. |
| 225 | Subscription of &1 to &2 failed: &3 |
| 226 | Subscription of &1 to &2 failed due to missing consumer. |
| 227 | Subscription of &1 failed due to missing consumer proxy. |
| 228 | Subscription of &1 to &2 failed: &3 |
| 229 | Notification of &1 for &2 failed due to missing notification info. |
| 230 | Publication of &1 failed due to missing service definition. |
| 231 | Publication of &1 failed due to missing publication info. |
| 232 | Subscription of &1 to &2 failed due to missing subsciption info. |
| 233 | Deletion of binding '&3' from registry '&2' failed &1 |
| 234 | Subscription of &4 (&3) to registry &2 failed: &1 |
| 235 | Notification failed in system &1: &2 |
| 236 | Lookup of Consumer Proxy failed for guid &1 |
| 237 | Lookup of Service Definition failed for guid &1 |
| 238 | Lookup of Binding failed for guid &1 |
| 239 | Lookup of IBC failed for guid &1 |
| 240 | Lookup of Classification failed for guid &1 |
| 241 | Lookup of System failed for guid &1 |
| 242 | Lookup of Notification failed for guid &1 |
| 243 | Pull of subscription for proxy '&1', lp '&2' and registry '&3' succeeded |
| 244 | Pull of notification for Subscription '&1' and registry '&2' succeeded. |
| 245 | Hidden publication &1 found with different object id &2 and type &3 |
| 246 | Classification &1(&2) is used by SR Views and can not be deleted |
| 247 | Classification &1(&2) is used by Publication Rules and can not be deleted |
| 248 | Value &1 of classif. &2(&3) is used by SR Views and can not be deleted |
| 249 | Value &1 of classif. &2(&3) is used by Pub. Rules and can not be deleted |
| 250 | Binding '&1' not found in local Services Registry |
| 251 | Publication with empty Application change key is not possible |
| 252 | Deletion with empty Application change key is not possible |
| 253 | Subscription with empty Application change key is not possible |
| 254 | Notification with empty Application change key is not possible |
| 255 | System with application key '&1' not found in local Services Registry |
| 256 | IBC with ID '&1' not found in local Services Registry |
| 257 | This entry cannot be processed by the Queue |
| 258 | Invalid Services Registry API version '&1' for this entry |
| 259 | Service Type not found |
| 260 | Error while Parsing XML &1 |
| 261 | Could not create Http Client with URL &1 |
| 262 | Could not authenticate on system with username &1 |
| 263 | Error while sending request to HTTP client |
| 264 | Error while receiving response from HTTP client with URL &1 |
| 265 | HTTP Error with status &1 and URL &2 |
| 266 | Title name is initial |
| 267 | Internal name is initial |
| 268 | Internal name is already in use |
| 269 | Version is initial |
| 270 | Metadata URL is initial |
| 271 | Namespace s initial |
| 272 | Service URL is initial |
| 273 | Service URL is not valid |
| 274 | ODataServices enabled in system |
| 275 | ODataServices disabled in system |
| 276 | All NWSDs (ODataServices) deleted |
| 277 | The selected setting value already fits with the system settings |
| 278 | ODataService deletion canceled |
| 279 | Error occurred while deleting ODataServices |
| 280 | You cannot delete the Services when you enable them |
| 281 | System is not selected |
| 282 | User name for authentication is empty |
| 283 | Password for authentication is empty |
| 284 | System is invalid |
| 285 | Select at least one service |
| 286 | Error while Parsing XML |
| 300 | Invalid T-Model Key '&1' |
| 999 |