SAP ABAP Message Class MSG_CL_ER (Message Class for Enterprise Registry)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-ESI-WS-ABA-CFG (Application Component) WebServices ABAP Configuration
⤷
SUDDICLIENT_NEW (Package) New development regarding UDDI Publication
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-ESI-WS-ABA-CFG (Application Component) WebServices ABAP Configuration⤷
SUDDICLIENT_NEW (Package) New development regarding UDDI Publication 
Attributes
| Message class |  |
MSG_CL_ER |
| Short Description |  |
Message Class for Enterprise Registry |
| Changed On |  |
20140121 |
| Last Changed At |  |
103738 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  000 |
Proxy instantiation error | The short text describes the object sufficiently | |
| 2 | 001 |
Services Registry parameters not found in customizing | The short text describes the object sufficiently | |
| 3 | 002 |
Error during endpoint publication | The short text describes the object sufficiently | |
| 4 | 003 |
Exception raised during physical system publication. Code : '&1' | The short text describes the object sufficiently | |
| 5 | 004 |
Physical system was published successfully | The short text describes the object sufficiently | |
| 6 | 005 |
All publication stamps deleted for Services Registry "&1" | The short text describes the object sufficiently | |
| 7 | 006 |
Error during proxy instance creation | The short text describes the object sufficiently | |
| 8 | 007 |
Error during cache update for classification system meta data/values | The short text describes the object sufficiently | |
| 9 | 008 |
Error importing file &1 | The short text describes the object sufficiently | |
| 10 | 009 |
Client copied. Physical system re-published | The short text describes the object sufficiently | |
| 11 | 010 |
Service &1 contains invalid tModel key &2 | The short text describes the object sufficiently | |
| 12 | 011 |
Physical system validated successfully | The short text describes the object sufficiently | |
| 13 | 012 |
Classification system cache updated from Services Registry | The short text describes the object sufficiently | |
| 14 | 013 |
Service definition "&1" published successfully in Services Registry | The short text describes the object sufficiently | |
| 15 | 014 |
Endpoint(s) for service &1 published successfully in Services Registry | The short text describes the object sufficiently | |
| 16 | 015 |
Physical system republished along with deployment units | The short text describes the object sufficiently | |
| 17 | 016 |
Error occurred during service definition(s) &1 publication | The short text describes the object sufficiently | |
| 18 | 017 |
Error saving values for classification system &1 | The short text describes the object sufficiently | |
| 19 | 018 |
Physical system was published with existing Deployment Units in system | The short text describes the object sufficiently | |
| 20 | 019 |
Error retreiving physical system from Services Registry | The short text describes the object sufficiently | |
| 21 | 020 |
Publcation rule saved for classification system &1 | The short text describes the object sufficiently | |
| 22 | 021 |
No changes made in rule for classification system &1 | The short text describes the object sufficiently | |
| 23 | 022 |
No service(s) to be published with the given criteria | The short text describes the object sufficiently | |
| 24 | 023 |
Restricted publication is active | The short text describes the object sufficiently | |
| 25 | 024 |
No classification system maintained. Restrictions not possible | The short text describes the object sufficiently | |
| 26 | 025 |
No sufficient authorisations. Ask user administrator | The short text describes the object sufficiently | |
| 27 | 026 |
Services Registry name : &1. Logical port : &2 | The short text describes the object sufficiently | |
| 28 | 027 |
Services Registry version is &1 | The short text describes the object sufficiently | |
| 29 | 028 |
Error retrieving Services Registry (SR) version information | The short text describes the object sufficiently | |
| 30 | 029 |
Service definition &1 not processed | The short text describes the object sufficiently | |
| 31 | 030 |
Wrong selection criteria | The short text describes the object sufficiently | |
| 32 | 031 |
There can be only one primary Services Registry. Check field 'Primary' | The short text describes the object sufficiently | |
| 33 | 032 |
Service endpoints for service definition &1 not found/processed | The short text describes the object sufficiently | |
| 34 | 033 |
Error occurred while publishing service definition &1 | The short text describes the object sufficiently | |
| 35 | 034 |
Error retrieving design time WSDL URL | The short text describes the object sufficiently | |
| 36 | 035 |
Error reading configuration(s) for service definition &1 | The short text describes the object sufficiently | |
| 37 | 036 |
Error fetching service info: SD &1, Service &2, Binding &3 | The short text describes the object sufficiently | |
| 38 | 037 |
Endpoint published. WSD:&1, Service:&2, Endpoint:&3 | The short text describes the object sufficiently | |
| 39 | 038 |
Error publishing Endpoint for SD : &1, Service : &2, EP : &3 | The short text describes the object sufficiently | |
| 40 | 039 |
New classification values saved in Services Registry | The short text describes the object sufficiently | |
| 41 | 040 |
No new classification values found in backend for Services Registry | The short text describes the object sufficiently | |
| 42 | 041 |
No Publication possible from Integration Server(IS) | The short text describes the object sufficiently | |
| 43 | 042 |
Invalid PortType Name.Publication not possible for Service Definition &1 | The short text describes the object sufficiently | |
| 44 | 043 |
Invalid WSDL url. Publication not possible for Service Definition &1 | The short text describes the object sufficiently | |
| 45 | 044 |
The process of hiding for the backend system started as background job | The short text describes the object sufficiently | |
| 46 | 045 |
The process of synchronization of services started as background job | The short text describes the object sufficiently | |
| 47 | 046 |
Error retrieving design time WSDL URL for Service Definition &1 | The short text describes the object sufficiently | |
| 48 | 047 |
Framework exception: &1&2&3&4 | The short text describes the object sufficiently | |
| 49 | 048 |
Physical System gets published in the Services Registry '&1' | The short text describes the object sufficiently | |
| 50 | 049 |
Endpoint(s) for Service Definition &1 removed in Services Registry &2 | The short text describes the object sufficiently | |
| 51 | 050 |
Error: &1&2&3&4 | The short text describes the object sufficiently | |
| 52 | 051 |
&1&2&3&4 | The short text describes the object sufficiently | |
| 53 | 052 |
Error occurred during consumer(s) &1 publication | The short text describes the object sufficiently | |
| 54 | 053 |
Service Definition &1 published in Services Registry &2 | The short text describes the object sufficiently | |
| 55 | 054 |
IBC &1 published in Services Registry &2. | The short text describes the object sufficiently | |
| 56 | 055 |
Bindings with Key &1 published in Services Registry &2 | The short text describes the object sufficiently | |
| 57 | 056 |
Original System &1 published in Services Registry &2 | The short text describes the object sufficiently | |
| 58 | 057 |
Service Definition &1 removed from Services Registry &2 | The short text describes the object sufficiently | |
| 59 | 058 |
IBC &1 removed from Services Registry &2 | The short text describes the object sufficiently | |
| 60 | 059 |
All bindings of Service Definition &1 removed from Services Registry &2 | The short text describes the object sufficiently | |
| 61 | 060 |
Deletion of object &1 (Type: &2) suceeded | The short text describes the object sufficiently | |
| 62 | 061 |
All Bindings of Service Definition &1 published to Services Registry &2 | The short text describes the object sufficiently | |
| 63 | 062 |
No Central/Primary Services Registry connection maintained in this system | The short text describes the object sufficiently | |
| 64 | 063 |
Error reading Message Type information in cache for consumer proxy '&1' | The short text describes the object sufficiently | |
| 65 | 064 |
Error reading Binding Information for PublicationID & from Registry & | The short text describes the object sufficiently | |
| 66 | 065 |
System with application key &1 removed from Services Registry &2 | The short text describes the object sufficiently | |
| 67 | 066 |
Consumer logical port &1 removed from Services Registry &2 | The short text describes the object sufficiently | |
| 68 | 067 |
Cannot find matching objects since list of classification is empty | The short text describes the object sufficiently | |
| 69 | 068 |
Getting classifications for registry '&1' failed | The short text describes the object sufficiently | |
| 70 | 069 |
Getting classification value for registry '&1' failed | The short text describes the object sufficiently | |
| 71 | 070 |
Services Registry connections with Proxy Class '&1' or '&2' allowed | The short text describes the object sufficiently | |
| 72 | 071 |
No Services Registry connection '&1' found in this system | The short text describes the object sufficiently | |
| 73 | 072 |
Invalid bindings of Service Definition &1 removed from Registry &2 | The short text describes the object sufficiently | |
| 74 | 092 |
No Services Registry connection maintained in this system | The short text describes the object sufficiently | |
| 75 | 093 |
No primary Services Registry maintained in this system | The short text describes the object sufficiently | |
| 76 | 100 |
Not a valid classification system (tModel Key). | The short text describes the object sufficiently | |
| 77 | 101 |
Not a valid classification value (classification Code). | The short text describes the object sufficiently | |
| 78 | 102 |
No values found. | The short text describes the object sufficiently | |
| 79 | 103 |
Enter tModel Key first. | The short text describes the object sufficiently | |
| 80 | 104 |
Error during file import process. | The short text describes the object sufficiently | |
| 81 | 105 |
Not a valid service ESR Name &1. | The short text describes the object sufficiently | |
| 82 | 106 |
Blank ESR Name found in the file. | The short text describes the object sufficiently | |
| 83 | 107 |
Import process for file ----- &1 -----. | The short text describes the object sufficiently | |
| 84 | 108 |
Classification saved successfully... | The short text describes the object sufficiently | |
| 85 | 109 |
Error saving classifications. | The short text describes the object sufficiently | |
| 86 | 110 |
No service to go further. Use change operation if needed. | The short text describes the object sufficiently | |
| 87 | 111 |
Service &1 classified, &2 and val &3. | The short text describes the object sufficiently | |
| 88 | 112 |
Error classifying service &1 with class &2 and val &3. | The short text describes the object sufficiently | |
| 89 | 113 |
No Service to go further. Use create operation if needed. | The short text describes the object sufficiently | |
| 90 | 114 |
NW BASIS:&1. Operation '&2' not implemented for Service '&3' '&4' | The short text describes the object sufficiently | |
| 91 | 115 |
Please enter valid service name(s). | The short text describes the object sufficiently | |
| 92 | 116 |
Error retrieving classification systems and their values from Registry. | The short text describes the object sufficiently | |
| 93 | 117 |
Error during deletion of classifications | The short text describes the object sufficiently | |
| 94 | 118 |
This transaction is obsolete; please edit services in transaction SE80 | The short text describes the object sufficiently | |
| 95 | 119 |
This program is obsolete. More information can be found in Note 1319742 | The short text describes the object sufficiently | |
| 96 | 120 |
Classification system &1 is for read only purpose. | The short text describes the object sufficiently | |
| 97 | 121 |
Classification system &1 used more than once. | The short text describes the object sufficiently | |
| 98 | 122 |
Manual usage of classification system "&1" is forbidden in this release. | The short text describes the object sufficiently | |
| 99 | 123 |
Checks failed with classification system &1 | The short text describes the object sufficiently | |
| 100 | 125 |
Object &1 already locked | The short text describes the object sufficiently | |
| 101 | 126 |
User &1 does not have sufficient authorisations. | The short text describes the object sufficiently | |
| 102 | 127 |
Internal error changing object &1. | The short text describes the object sufficiently | |
| 103 | 128 |
Operation not allowed on deleted object &1. | The short text describes the object sufficiently | |
| 104 | 130 |
Invalid object state: Not persistent and no modification | The short text describes the object sufficiently | |
| 105 | 132 |
Empty value for &1 not permitted | The short text describes the object sufficiently | |
| 106 | 133 |
Object not locked: &1 | The short text describes the object sufficiently | |
| 107 | 134 |
Insufficient parameters: One of &1 &2 &3 &4 not provided | The short text describes the object sufficiently | |
| 108 | 135 |
Entry with key-value combination already exists: &1 - &2 | The short text describes the object sufficiently | |
| 109 | 136 |
Object not available: &1 | The short text describes the object sufficiently | |
| 110 | 137 |
Fatal error in application logic: &1 | The short text describes the object sufficiently | |
| 111 | 138 |
Unknown described entitiy: &1 | The short text describes the object sufficiently | |
| 112 | 139 |
Dynamic SQL error | The short text describes the object sufficiently | |
| 113 | 140 |
Object already exists: &1 | The short text describes the object sufficiently | |
| 114 | 141 |
System publication failed: Logical Key = &1, UDDI Key = &2 | The short text describes the object sufficiently | |
| 115 | 142 |
System &1 does not exist | The short text describes the object sufficiently | |
| 116 | 143 |
Invalid object state: Not persistent and updated | The short text describes the object sufficiently | |
| 117 | 144 |
Unknown ISO language: &1 | The short text describes the object sufficiently | |
| 118 | 145 |
Unknown SAP language: &1 | The short text describes the object sufficiently | |
| 119 | 146 |
IBC &1 does not exist | The short text describes the object sufficiently | |
| 120 | 147 |
WSD publication failed: Logical Key = &1, UDDI Key = &2 | The short text describes the object sufficiently | |
| 121 | 148 |
SEP publiciation failed: Service Log. Key = &1, Binding Log. Key = &2 | The short text describes the object sufficiently | |
| 122 | 149 |
WSD &1 does not exist | The short text describes the object sufficiently | |
| 123 | 150 |
SEP &1 does not exist | The short text describes the object sufficiently | |
| 124 | 151 |
Classification &1 does not exist | The short text describes the object sufficiently | |
| 125 | 152 |
WSD &1 can not be deleted because of &2 child SEPs. | The short text describes the object sufficiently | |
| 126 | 153 |
System &1 can not be deleted because of &2 child WSDs. | The short text describes the object sufficiently | |
| 127 | 154 |
Logical key(s) missing! | The short text describes the object sufficiently | |
| 128 | 155 |
Classification system publication failed: Uddi key = &1 | The short text describes the object sufficiently | |
| 129 | 156 |
Publication to predefined classification system not allowed! | The short text describes the object sufficiently | |
| 130 | 157 |
Classification system &1 does not exist | The short text describes the object sufficiently | |
| 131 | 158 |
Value &1 does not exist in classification system &2 | The short text describes the object sufficiently | |
| 132 | 159 |
Classification system &1 is read only | The short text describes the object sufficiently | |
| 133 | 160 |
Insufficient key: &1 required | The short text describes the object sufficiently | |
| 134 | 161 |
Insufficient key: &1 &2 required | The short text describes the object sufficiently | |
| 135 | 162 |
Insufficient key: &1 &2 &3 required | The short text describes the object sufficiently | |
| 136 | 163 |
Insufficient key: &1 &2 &3 &4 required | The short text describes the object sufficiently | |
| 137 | 164 |
Invalid update: &1 may not be changed | The short text describes the object sufficiently | |
| 138 | 165 |
Invalid update: &1 &2 may not be changed | The short text describes the object sufficiently | |
| 139 | 166 |
Invalid update: &1 &2 &3 may not be changed | The short text describes the object sufficiently | |
| 140 | 167 |
Unknown physical system type: &1 | The short text describes the object sufficiently | |
| 141 | 168 |
Technical name may not be changed | The short text describes the object sufficiently | |
| 142 | 169 |
TModel Key may not be changed | The short text describes the object sufficiently | |
| 143 | 170 |
Insufficient parameters: TModel Key is missing | The short text describes the object sufficiently | |
| 144 | 171 |
Insufficient parameters: Qualified Name is missing | The short text describes the object sufficiently | |
| 145 | 172 |
Insufficient parameters: TModel Key and Qualified Name are missing | The short text describes the object sufficiently | |
| 146 | 173 |
Insufficient parameters: Classification value may not be empty | The short text describes the object sufficiently | |
| 147 | 174 |
Invalid update: Attempt to change readonly data | The short text describes the object sufficiently | |
| 148 | 175 |
UDDI Key may not be initial | The short text describes the object sufficiently | |
| 149 | 176 |
Name may not be initial | The short text describes the object sufficiently | |
| 150 | 177 |
Namespace may not be initial | The short text describes the object sufficiently | |
| 151 | 178 |
Value &1 of Classification System &2(&3) is in use and can not be deleted | The short text describes the object sufficiently | |
| 152 | 179 |
Classification System &1(&2) is in use and can not be deleted | The short text describes the object sufficiently | |
| 153 | 180 |
Unknown Web Service Definition Configuration State &1 | The short text describes the object sufficiently | |
| 154 | 181 |
Parameters generated for Services Registry '&1' using proxy class '&2' | The short text describes the object sufficiently | |
| 155 | 182 |
Parameters deleted for Services Registry '&1' using proxy class '&2' | The short text describes the object sufficiently | |
| 156 | 183 |
Parameters for Services Registry '&1' does not exist | The short text describes the object sufficiently | |
| 157 | 184 |
Services Identifier data created with Business Application ID '&1' | The short text describes the object sufficiently | |
| 158 | 185 |
Services Identifier data updated with Business Application ID '&1' | The short text describes the object sufficiently | |
| 159 | 186 |
Reverse Proxy '&1' deleted. ( &2 | &3 | &4 ) | The short text describes the object sufficiently | |
| 160 | 187 |
Reverse Proxy '&1' created. ( &2 | &3 | &4 ) | The short text describes the object sufficiently | |
| 161 | 188 |
Reverse Proxy '&1' updated. ( &2 | &3 | &4 ) | The short text describes the object sufficiently | |
| 162 | 189 |
Service Definition '&1' is not allowed to be published. | The short text describes the object sufficiently | |
| 163 | 190 |
IBC &1 does not exist. | The short text describes the object sufficiently | |
| 164 | 191 |
Application &1 can not be deleted because of &2 dependent objects. | The short text describes the object sufficiently | |
| 165 | 192 |
IBC publication failed: Logical Key = &1 | The short text describes the object sufficiently | |
| 166 | 193 |
Application publication failed: Logical Key = &1, UDDI-key = &2 | The short text describes the object sufficiently | |
| 167 | 194 |
Logical Key '&1' already registered with Application Key '&2' | The short text describes the object sufficiently | |
| 168 | 195 |
Application not registered with Change Key &1 | The short text describes the object sufficiently | |
| 169 | 196 |
System not found in Services Registry belonging to Change Key &1 | The short text describes the object sufficiently | |
| 170 | 197 |
Application change key cannot be empty | The short text describes the object sufficiently | |
| 171 | 198 |
Application not registered with Application Key &1 | The short text describes the object sufficiently | |
| 172 | 199 |
Application key cannot be empty | The short text describes the object sufficiently | |
| 173 | 200 |
Error scheduling background publication job &3/&2 for Registry &1. | The short text describes the object sufficiently | |
| 174 | 201 |
Error updating background publication job &3/&2 for Registry &1. | The short text describes the object sufficiently | |
| 175 | 202 |
Error deleting background publication job &3/&2 for Registry &1. | The short text describes the object sufficiently | |
| 176 | 203 |
There are active assignments for publication rule &1 | The short text describes the object sufficiently | |
| 177 | 204 |
There are active assignments for services registry &1 | The short text describes the object sufficiently | |
| 178 | 205 |
IBC '&1' is not allowed to be published | The short text describes the object sufficiently | |
| 179 | 206 |
Binding '&1' of service definition '&2' is not allowed to be published | The short text describes the object sufficiently | |
| 180 | 207 |
IBC publication failed: Logical Key = &1 | The short text describes the object sufficiently | |
| 181 | 208 |
Import of Classification &1 failed. | The short text describes the object sufficiently | |
| 182 | 209 |
Import of Classification &1 failed: &2 | The short text describes the object sufficiently | |
| 183 | 210 |
Import of IBC &1 failed. | The short text describes the object sufficiently | |
| 184 | 211 |
Import of IBC &1 failed: &2 | The short text describes the object sufficiently | |
| 185 | 212 |
Import of Binding &1 failed. | The short text describes the object sufficiently | |
| 186 | 213 |
Import of Binding &1 failed: &2 | The short text describes the object sufficiently | |
| 187 | 214 |
Import of Service Definition &1 failed | The short text describes the object sufficiently | |
| 188 | 215 |
Import of Service Definition &1 failed: &2 | The short text describes the object sufficiently | |
| 189 | 216 |
Import of System &1 failed | The short text describes the object sufficiently | |
| 190 | 217 |
Import of System &1 failed: &2 | The short text describes the object sufficiently | |
| 191 | 218 |
Assignment for classification value &1 failed: &2 | The short text describes the object sufficiently | |
| 192 | 219 |
Invalid PortType Name. Publication not possible for Consumer &1 | The short text describes the object sufficiently | |
| 193 | 220 |
Service Definition '&1' is not allowed to be published | The short text describes the object sufficiently | |
| 194 | 221 |
Consumer &1 does not exist | The short text describes the object sufficiently | |
| 195 | 222 |
Relation &1 does not exist | The short text describes the object sufficiently | |
| 196 | 223 |
Insufficient parameters: Object guid for relation is empty. | The short text describes the object sufficiently | |
| 197 | 224 |
Insufficient parameters: Object type for relation is empty. | The short text describes the object sufficiently | |
| 198 | 225 |
Subscription of &1 to &2 failed: &3 | The short text describes the object sufficiently | |
| 199 | 226 |
Subscription of &1 to &2 failed due to missing consumer. | The short text describes the object sufficiently | |
| 200 | 227 |
Subscription of &1 failed due to missing consumer proxy. | The short text describes the object sufficiently | |
| 201 | 228 |
Subscription of &1 to &2 failed: &3 | The short text describes the object sufficiently | |
| 202 | 229 |
Notification of &1 for &2 failed due to missing notification info. | The short text describes the object sufficiently | |
| 203 | 230 |
Publication of &1 failed due to missing service definition. | The short text describes the object sufficiently | |
| 204 | 231 |
Publication of &1 failed due to missing publication info. | The short text describes the object sufficiently | |
| 205 | 232 |
Subscription of &1 to &2 failed due to missing subsciption info. | The short text describes the object sufficiently | |
| 206 | 233 |
Deletion of binding '&3' from registry '&2' failed &1 | The short text describes the object sufficiently | |
| 207 | 234 |
Subscription of &4 (&3) to registry &2 failed: &1 | The short text describes the object sufficiently | |
| 208 | 235 |
Notification failed in system &1: &2 | The short text describes the object sufficiently | |
| 209 | 236 |
Lookup of Consumer Proxy failed for guid &1 | The short text describes the object sufficiently | |
| 210 | 237 |
Lookup of Service Definition failed for guid &1 | The short text describes the object sufficiently | |
| 211 | 238 |
Lookup of Binding failed for guid &1 | The short text describes the object sufficiently | |
| 212 | 239 |
Lookup of IBC failed for guid &1 | The short text describes the object sufficiently | |
| 213 | 240 |
Lookup of Classification failed for guid &1 | The short text describes the object sufficiently | |
| 214 | 241 |
Lookup of System failed for guid &1 | The short text describes the object sufficiently | |
| 215 | 242 |
Lookup of Notification failed for guid &1 | The short text describes the object sufficiently | |
| 216 | 243 |
Pull of subscription for proxy '&1', lp '&2' and registry '&3' succeeded | The short text describes the object sufficiently | |
| 217 | 244 |
Pull of notification for Subscription '&1' and registry '&2' succeeded. | The short text describes the object sufficiently | |
| 218 | 245 |
Hidden publication &1 found with different object id &2 and type &3 | The short text describes the object sufficiently | |
| 219 | 246 |
Classification &1(&2) is used by SR Views and can not be deleted | The short text describes the object sufficiently | |
| 220 | 247 |
Classification &1(&2) is used by Publication Rules and can not be deleted | The short text describes the object sufficiently | |
| 221 | 248 |
Value &1 of classif. &2(&3) is used by SR Views and can not be deleted | The short text describes the object sufficiently | |
| 222 | 249 |
Value &1 of classif. &2(&3) is used by Pub. Rules and can not be deleted | The short text describes the object sufficiently | |
| 223 | 250 |
Binding '&1' not found in local Services Registry | The short text describes the object sufficiently | |
| 224 | 251 |
Publication with empty Application change key is not possible | The short text describes the object sufficiently | |
| 225 | 252 |
Deletion with empty Application change key is not possible | The short text describes the object sufficiently | |
| 226 | 253 |
Subscription with empty Application change key is not possible | The short text describes the object sufficiently | |
| 227 | 254 |
Notification with empty Application change key is not possible | The short text describes the object sufficiently | |
| 228 | 255 |
System with application key '&1' not found in local Services Registry | The short text describes the object sufficiently | |
| 229 | 256 |
IBC with ID '&1' not found in local Services Registry | The short text describes the object sufficiently | |
| 230 | 257 |
This entry cannot be processed by the Queue | The short text describes the object sufficiently | |
| 231 | 258 |
Invalid Services Registry API version '&1' for this entry | The short text describes the object sufficiently | |
| 232 | 300 |
Invalid T-Model Key '&1' | The short text describes the object sufficiently | |
| 233 | 999 |
Test Message &1 &2 &3 &4 | The short text describes the object sufficiently |
History
| Last changed on/by | |
20140121 | SAP |
| SAP Release Created in | 700 |
