SAP ABAP Message Class /IWFND/CM_LOGGING (SAP NetWeaver Gateway Framework Step Descriptions)
Basic Data
Hierarchy
☛
SAP_GWFND (Software Component) SAP Gateway Foundation
⤷
OPU-FND-CS (Application Component) IWF Common Services
⤷
/IWFND/COS_SHARED_OBJECTS (Package) GW Framework - Shared Objects among Package /IWFND/COS
SAP_GWFND (Software Component) SAP Gateway Foundation⤷
OPU-FND-CS (Application Component) IWF Common Services⤷
/IWFND/COS_SHARED_OBJECTS (Package) GW Framework - Shared Objects among Package /IWFND/COS 
Attributes
| Message class |  |
/IWFND/CM_LOGGING |
| Short Description |  |
SAP NetWeaver Gateway Framework Step Descriptions |
| Changed On |  |
20141120 |
| Last Changed At |  |
212331 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  000 |
Request &1 has been successfully processed on the Gateway server | Space: object requires documentation | |
| 2 | 001 |
Example for logging a simple message | The short text describes the object sufficiently | |
| 3 | 002 |
Example for logging a step-completion message | The short text describes the object sufficiently | |
| 4 | 003 |
Example for logging a step-initiation message | The short text describes the object sufficiently | |
| 5 | 004 |
Example for logging an exception | The short text describes the object sufficiently | |
| 6 | 005 |
Message &1 &2 of agent &3 could not be logged in CCMS | Space: object requires documentation | |
| 7 | 006 |
Exception of type &1 has occurred. See details for more information | The short text describes the object sufficiently | |
| 8 | 007 |
&2 '&1' messages of this request will be logged | Space: object requires documentation | |
| 9 | 008 |
SAP NW Gateway Agent '&1' initialized. | The short text describes the object sufficiently | |
| 10 | 010 |
GET_SYSTEM_ALIASES called: Obj Type = '&1', User = '&2', Context = '&3' | The short text describes the object sufficiently | |
| 11 | 011 |
GET_SYSTEM_ALIASES succeeded. '&1' System Alias found | The short text describes the object sufficiently | |
| 12 | 012 |
GET_SYSTEM_ALIASES failed | Space: object requires documentation | |
| 13 | 013 |
GET_SYSTEM_ALIASES_FOR_GROUP called: GSDO Group = '&1', User = '&2' | The short text describes the object sufficiently | |
| 14 | 015 |
CREATE_CONSUMER_BY_KEY failed | Space: object requires documentation | |
| 15 | 016 |
GET_GSDO_FROM_GNIL_MODEL failed | Space: object requires documentation | |
| 16 | 020 |
GET_GSI_IMPLEMENT called: Obj Type='&1'|User ='&2'|Cont='&3'|Cons='&4' | The short text describes the object sufficiently | |
| 17 | 021 |
GET_GSI_IMPLEMENT succeeded | The short text describes the object sufficiently | |
| 18 | 022 |
GET_GSI_IMPLEMENT failed | Space: object requires documentation | |
| 19 | 023 |
GET_GSI_IMPLEMENT_FOR_DESTIN called: G='&1'|C='&2'|SA='&3'|SV='&4' | The short text describes the object sufficiently | |
| 20 | 024 |
GET_GSI_IMPLEMENT_FOR_DESTIN succeeded | The short text describes the object sufficiently | |
| 21 | 025 |
GET_GSI_IMPLEMENT_FOR_DESTIN failed | Space: object requires documentation | |
| 22 | 026 |
GET_GSI_IMPLEMENT_FOR_DESTINS called | The short text describes the object sufficiently | |
| 23 | 027 |
GET_GSI_IMPLEMENT_FOR_DESTINS succeeded | The short text describes the object sufficiently | |
| 24 | 028 |
GET_GSI_IMPLEMENT_FOR_DESTINS failed | Space: object requires documentation | |
| 25 | 030 |
All messages of this request will be logged | The short text describes the object sufficiently | |
| 26 | 031 |
Step Completion Information messages of this request will be logged | The short text describes the object sufficiently | |
| 27 | 032 |
Only Error, Security and Warning messages of this request will be logged | The short text describes the object sufficiently | |
| 28 | 033 |
Only Error and Security messages of this request will be logged | The short text describes the object sufficiently | |
| 29 | 034 |
Only Error messages of this request will be logged | The short text describes the object sufficiently | |
| 30 | 035 |
The short text describes the object sufficiently | ||
| 31 | 036 |
The short text describes the object sufficiently | ||
| 32 | 037 |
The short text describes the object sufficiently | ||
| 33 | 038 |
The short text describes the object sufficiently | ||
| 34 | 040 |
****************User and Roles******************* | The short text describes the object sufficiently | |
| 35 | 041 |
Retrieve external role for internal role '&1' and consumer '&2' | The short text describes the object sufficiently | |
| 36 | 042 |
No external role found for internal role '&1' and consumer '&2' | Space: object requires documentation | |
| 37 | 043 |
External role '&1' found for internal role '&2' and consumer '&3' | The short text describes the object sufficiently | |
| 38 | 044 |
Retrieve internal role for external role '&1' and consumer '&2' | The short text describes the object sufficiently | |
| 39 | 045 |
No internal role found for external role '&1' and consumer '&2' | Space: object requires documentation | |
| 40 | 046 |
Internal role '&1' found for external role '&2' and consumer '&3' | The short text describes the object sufficiently | |
| 41 | 047 |
Roles found for consumer '&1' | The short text describes the object sufficiently | |
| 42 | 048 |
No roles found for consumer '&1' | Space: object requires documentation | |
| 43 | 049 |
Found users in role '&1' | The short text describes the object sufficiently | |
| 44 | 050 |
User '&1' is in role '&2' | The short text describes the object sufficiently | |
| 45 | 051 |
Retrieve users of GSDO type '&1' consumer '&2' for role '&3' | The short text describes the object sufficiently | |
| 46 | 052 |
GSDO groups found for GSDO type '&1' | The short text describes the object sufficiently | |
| 47 | 053 |
No GSDO groups found for GSDO type '&1' | Space: object requires documentation | |
| 48 | 054 |
Roles found for GSDO type '&1' | The short text describes the object sufficiently | |
| 49 | 055 |
No roles found for GSDO type '&1' | Space: object requires documentation | |
| 50 | 056 |
Specified role '&1' not allowed for GSDO type '&2' | Space: object requires documentation | |
| 51 | 057 |
Users of GSDO type '&1' consumer '&2' for role '&3' found | The short text describes the object sufficiently | |
| 52 | 058 |
No users of GSDOt type '&1' consumer '&2' for role '&3' found | The short text describes the object sufficiently | |
| 53 | 059 |
Retrieve GSDO types for user '&1' and consumer '&2' | The short text describes the object sufficiently | |
| 54 | 060 |
GSDO groups for user '&1' and consumer '&2' found | The short text describes the object sufficiently | |
| 55 | 061 |
No GSDO groups for user '&1' and consumer '&2' found | Space: object requires documentation | |
| 56 | 062 |
Roles for user '&1' and consumer '&2' found | The short text describes the object sufficiently | |
| 57 | 063 |
No roles for user '&1' and consumer '&2' found | Space: object requires documentation | |
| 58 | 064 |
GSDO types for user '&1' and consumer '&2' found | The short text describes the object sufficiently | |
| 59 | 065 |
No GSDO types for user '&1' and consumer '&2' found | The short text describes the object sufficiently | |
| 60 | 066 |
No active GSDO group '&1' found | Space: object requires documentation | |
| 61 | 067 |
No GSDO groups found | Space: object requires documentation | |
| 62 | 068 |
No active GSDO groups found | Space: object requires documentation | |
| 63 | 069 |
No GSDO types in GSDO group '&1' found | Space: object requires documentation | |
| 64 | 100 |
********* Event Manager ********* | The short text describes the object sufficiently | |
| 65 | 101 |
Deferred processing of events has been initiated | The short text describes the object sufficiently | |
| 66 | 102 |
Deferred processing of events has been completed | The short text describes the object sufficiently | |
| 67 | 103 |
The process of adding an event to the Event Manager has started | The short text describes the object sufficiently | |
| 68 | 104 |
The process of adding an event to the Event Manager has been completed | The short text describes the object sufficiently | |
| 69 | 105 |
The Notification has event type &1 and is for object type &2 | The short text describes the object sufficiently | |
| 70 | 106 |
The Notification has been added to the queue | The short text describes the object sufficiently | |
| 71 | 107 |
The event has to be processed immediately | The short text describes the object sufficiently | |
| 72 | 108 |
Missing Event Handler configuration | Space: object requires documentation | |
| 73 | 109 |
The Notification has event type &1 | The short text describes the object sufficiently | |
| 74 | 110 |
Processing of the event has started | The short text describes the object sufficiently | |
| 75 | 111 |
Processing of the event has been completed | The short text describes the object sufficiently | |
| 76 | 112 |
The process of calling the Event Handler &1 has started | The short text describes the object sufficiently | |
| 77 | 113 |
The process of calling the Event Handler &1 has been completed | The short text describes the object sufficiently | |
| 78 | 114 |
The process of retrieving an object instance in the Event Handler started | The short text describes the object sufficiently | |
| 79 | 115 |
The process of retrieving an object instance in Event Handler finished | The short text describes the object sufficiently | |
| 80 | 116 |
No active consumers configured for event handlers | Space: object requires documentation | |
| 81 | 120 |
********* BOP Generators ********* | The short text describes the object sufficiently | |
| 82 | 121 |
Generation of RFC BOP has been initiated for &1 using &2, target &3 | The short text describes the object sufficiently | |
| 83 | 122 |
Generation of RFC BOP has been completed | The short text describes the object sufficiently | |
| 84 | 123 |
Generation of a custom BOP has been initiated for BOP ID &1 and system &2 | The short text describes the object sufficiently | |
| 85 | 124 |
A custom BOP has been generated | The short text describes the object sufficiently | |
| 86 | 130 |
********* Backend Connectivity Runtime ********* | The short text describes the object sufficiently | |
| 87 | 131 |
The process of creating an RFC BOP with ID &1 for system &2 has started | The short text describes the object sufficiently | |
| 88 | 132 |
The process of creating an RFC BOP has been completed | The short text describes the object sufficiently | |
| 89 | 133 |
Using RFC destination &1 | The short text describes the object sufficiently | |
| 90 | 134 |
Using custom RFC proxy class &1 | The short text describes the object sufficiently | |
| 91 | 135 |
Starting to initialize the BOP | The short text describes the object sufficiently | |
| 92 | 136 |
Acquiring Enhancement Class implementations for object type &1 | The short text describes the object sufficiently | |
| 93 | 137 |
BAdI implementation &1 found | The short text describes the object sufficiently | |
| 94 | 138 |
Pre/post processing an SAP system call using BAdI implementation &1 | The short text describes the object sufficiently | |
| 95 | 139 |
The Web service BOP creation process with ID &1 for system &2 has started | The short text describes the object sufficiently | |
| 96 | 141 |
Web service BOP creation process has been completed | The short text describes the object sufficiently | |
| 97 | 142 |
Creating a BOP for logical port &1 | The short text describes the object sufficiently | |
| 98 | 143 |
Creating a BOP for provider system &1 and service group &2 | The short text describes the object sufficiently | |
| 99 | 144 |
Executing a BOP with ID &1, RFC &2, destination &3 | The short text describes the object sufficiently | |
| 100 | 145 |
Finished processing the BOP | The short text describes the object sufficiently | |
| 101 | 146 |
Exiting a BOP as requested by BAdI without calling the SAP system | The short text describes the object sufficiently | |
| 102 | 147 |
Executing a BOP with ID &1, service group &2, provider system &3 | The short text describes the object sufficiently | |
| 103 | 150 |
*** Generic Serive Provider 150 - 199 *** | The short text describes the object sufficiently | |
| 104 | 151 |
Generic Service Provider called. Operation='&1' GenIL Component='&2'- | The short text describes the object sufficiently | |
| 105 | 152 |
Generic Service Provider succeeded | The short text describes the object sufficiently | |
| 106 | 153 |
Generic Service Provider failed | Space: object requires documentation | |
| 107 | 154 |
No request ID provided. Idempotent functionallity not used. | The short text describes the object sufficiently | |
| 108 | 160 |
Call GSI method SAVE_LOCAL_OBJECTS_PRE_REMOTE | The short text describes the object sufficiently | |
| 109 | 161 |
Call GSI method SAVE_REMOTE_OBJECTS | The short text describes the object sufficiently | |
| 110 | 162 |
Call GSI method AFTER_SAVE_REMOTE_OBJECTS | The short text describes the object sufficiently | |
| 111 | 163 |
Call instance manager for routing (Object ID available, System Alias not) | Space: object requires documentation | |
| 112 | 200 |
******* GSI Runtime Steps 200 - 299 ******* | The short text describes the object sufficiently | |
| 113 | 210 |
QUERY_BY_ELEMENTS called: Object Type='&1'| Class Name ='&2' | The short text describes the object sufficiently | |
| 114 | 211 |
QUERY_BY_ELEMENTS succeeded | The short text describes the object sufficiently | |
| 115 | 212 |
QUERY_BY_ELEMENTS failed. Result Code='&1'| Process Code='&2' |Class='&3' | Space: object requires documentation | |
| 116 | 213 |
QUERY_BY_ELEMENTS calls pre-mapping: Class Name ='&1' | The short text describes the object sufficiently | |
| 117 | 214 |
QUERY_BY_ELEMENTS calls post-mapping: Class Name ='&1' | The short text describes the object sufficiently | |
| 118 | 220 |
GET_OBJECTS called: Object Type='&1'| Class Name ='&2' | The short text describes the object sufficiently | |
| 119 | 221 |
GET_OBJECTS succeeded | The short text describes the object sufficiently | |
| 120 | 222 |
GET_OBJECTS failed. Result Code='&1'| Process Code='&2' | Class Name='&3' | Space: object requires documentation | |
| 121 | 223 |
GET_OBJECTS calls pre-mapping: Class Name ='&1' | The short text describes the object sufficiently | |
| 122 | 224 |
GET_OBJECTS calls post-mapping: Class Name ='&1' | The short text describes the object sufficiently | |
| 123 | 225 |
GET_OBJECTS: GSDO retrieved from the read cache. | The short text describes the object sufficiently | |
| 124 | 230 |
SAVE_REMOTE called: Object Type='&1'| Class Name ='&2' | The short text describes the object sufficiently | |
| 125 | 231 |
SAVE_REMOTE succeeded | The short text describes the object sufficiently | |
| 126 | 232 |
SAVE_REMOTE failed. Result Code='&1'| Process Code='&2' | Class Name='&3' | Space: object requires documentation | |
| 127 | 240 |
SAVE_REMOTE calls pre-mapping for create: Class Name ='&1' | The short text describes the object sufficiently | |
| 128 | 241 |
SAVE_REMOTE calls post-mapping for create: Class Name ='&1' | The short text describes the object sufficiently | |
| 129 | 242 |
SAVE_REMOTE calls pre-mapping for update: Class Name ='&1' | The short text describes the object sufficiently | |
| 130 | 243 |
SAVE_REMOTE calls post-mapping for update: Class Name ='&1' | The short text describes the object sufficiently | |
| 131 | 244 |
SAVE_REMOTE calls pre-mapping for delete: Class Name ='&1' | The short text describes the object sufficiently | |
| 132 | 245 |
SAVE_REMOTE calls post-mapping for delete: Class Name ='&1' | The short text describes the object sufficiently | |
| 133 | 246 |
Preliminary id '&2' successfully replaced by backend id. Class Name ='&1' | Space: object requires documentation | |
| 134 | 250 |
*** Logging abstract BSO implementation - check before save | The short text describes the object sufficiently | |
| 135 | 251 |
CHECK_BEFORE_SAVE called: GSDO Type='&1'| Class Name ='&2' | The short text describes the object sufficiently | |
| 136 | 252 |
CHECK_BEFORE_SAVE succeeded | The short text describes the object sufficiently | |
| 137 | 253 |
CHECK_BEFORE_SAVE failed. Result C.='&1'| Process C.='&2' | Class ='&3' | Space: object requires documentation | |
| 138 | 254 |
CHECK_BEFORE_SAVE calls pre-mapping for create: Class Name ='&1' | The short text describes the object sufficiently | |
| 139 | 255 |
CHECK_BEFORE_SAVE calls post-mapping for create: Class Name ='&1' | The short text describes the object sufficiently | |
| 140 | 261 |
Create called. Object is buffered at the write cache. | Space: object requires documentation | |
| 141 | 262 |
Update called. Object is buffered at the write cache. | Space: object requires documentation | |
| 142 | 263 |
Delete called. Object is buffered at the write cache. | Space: object requires documentation | |
| 143 | 264 |
CREATE called: Object Type='&1'| Class Name ='&2' | The short text describes the object sufficiently | |
| 144 | 265 |
CREATE succeeded | The short text describes the object sufficiently | |
| 145 | 266 |
CREATE failed | The short text describes the object sufficiently | |
| 146 | 267 |
MODIFY called: Object Type='&1'| Class Name ='&2' | The short text describes the object sufficiently | |
| 147 | 268 |
MODIFY succeeded | The short text describes the object sufficiently | |
| 148 | 269 |
MODIFY failed | The short text describes the object sufficiently | |
| 149 | 270 |
DELETE called: Object Type='&1'| Class Name ='&2' | The short text describes the object sufficiently | |
| 150 | 271 |
DELETE succeeded | The short text describes the object sufficiently | |
| 151 | 272 |
DELETE failed | The short text describes the object sufficiently | |
| 152 | 300 |
******* Consumer Connectivity Steps 300 - 399 ******* | The short text describes the object sufficiently | |
| 153 | 301 |
Retrieve the IDP utility instance | The short text describes the object sufficiently | |
| 154 | 302 |
The retrieval of the IDP utility instance was successful | The short text describes the object sufficiently | |
| 155 | 303 |
Check if the request message has already been processed | The short text describes the object sufficiently | |
| 156 | 304 |
The request message has already been processed | The short text describes the object sufficiently | |
| 157 | 305 |
No duplicate request message found | The short text describes the object sufficiently | |
| 158 | 306 |
Store the response message in the IDP framework | The short text describes the object sufficiently | |
| 159 | 307 |
Successful storage of the response message in IDP framework | The short text describes the object sufficiently | |
| 160 | 313 |
Processing consumer request '&1' on the Gateway server has started | The short text describes the object sufficiently | |
| 161 | 314 |
Processing consumer request '&1' on the Gateway server has been completed | The short text describes the object sufficiently | |
| 162 | 315 |
Processing consumer request '&1' on the GW server was finished with error | The short text describes the object sufficiently | |
| 163 | 320 |
An error has occurred when calling a BAdI for function '&1' | The short text describes the object sufficiently | |
| 164 | 321 |
A BAdI implementation has caused an exception with message '&1' | The short text describes the object sufficiently | |
| 165 | 322 |
Unregister the request for ability to resume | The short text describes the object sufficiently | |
| 166 | 323 |
Unregistering of request for ability to resume has been completed | The short text describes the object sufficiently | |
| 167 | 324 |
Register the request status for ability to resume | The short text describes the object sufficiently | |
| 168 | 325 |
Registering of request status for ability to resume has been completed | The short text describes the object sufficiently | |
| 169 | 330 |
No runtime configuration for service definition '&1' found | Space: object requires documentation | |
| 170 | 331 |
No Service Definition found for GSDO '&1' and context '&2' | Space: object requires documentation | |
| 171 | 397 |
Some problem might have occurred but no message was provided | Space: object requires documentation | |
| 172 | 398 |
Permanent Exception: &1 | The short text describes the object sufficiently | |
| 173 | 399 |
Temporary Exception: &1 | The short text describes the object sufficiently | |
| 174 | 400 |
******* IFL Consumer Steps 400 - 450 ******* | The short text describes the object sufficiently | |
| 175 | 401 |
Consumer create: init | The short text describes the object sufficiently | |
| 176 | 402 |
Consumer create-method was executed successfully | The short text describes the object sufficiently | |
| 177 | 403 |
Consumer read: init | The short text describes the object sufficiently | |
| 178 | 404 |
Consumer read-method was executed successfully | The short text describes the object sufficiently | |
| 179 | 405 |
Consumer update: init | The short text describes the object sufficiently | |
| 180 | 406 |
Consumer update-method was executed successfully | The short text describes the object sufficiently | |
| 181 | 407 |
Consumer delete: init | The short text describes the object sufficiently | |
| 182 | 408 |
Consumer delete-method was executed successfully | The short text describes the object sufficiently | |
| 183 | 409 |
Consumer simple query: init | The short text describes the object sufficiently | |
| 184 | 410 |
Consumer simple query-method was executed successfully | The short text describes the object sufficiently | |
| 185 | 411 |
Consumer complex query: init | The short text describes the object sufficiently | |
| 186 | 412 |
Consumer complex query-method was executed successfully | The short text describes the object sufficiently | |
| 187 | 413 |
Consumer get_gsdo: init | The short text describes the object sufficiently | |
| 188 | 414 |
Consumer get_gsdo-method was executed successfully | The short text describes the object sufficiently | |
| 189 | 415 |
Consumer constructor: Comp &1, Root &2, gsdo &3, ConsID &4 | The short text describes the object sufficiently | |
| 190 | 416 |
Consumer constructor was executed successfully | The short text describes the object sufficiently | |
| 191 | 417 |
Consumer service type: &1 | The short text describes the object sufficiently | |
| 192 | 418 |
Consumer gets mapper of type: &1 for service ID: &2 | The short text describes the object sufficiently | |
| 193 | 419 |
Consumer recognized a business error: type &1 | The short text describes the object sufficiently | |
| 194 | 420 |
Consumer create-method failed and cleanup was executed | The short text describes the object sufficiently | |
| 195 | 421 |
Consumer read-method failed and cleanup was executed | The short text describes the object sufficiently | |
| 196 | 422 |
Consumer update-method failed and cleanup was executed | The short text describes the object sufficiently | |
| 197 | 423 |
Consumer delete-method failed and cleanup was executed | The short text describes the object sufficiently | |
| 198 | 424 |
Consumer complex query-method failed and cleanup was executed | The short text describes the object sufficiently | |
| 199 | 425 |
Consumer simple query-method failed and cleanup was executed | The short text describes the object sufficiently | |
| 200 | 426 |
Consumer get_gsdo-method failed and cleanup was executed | The short text describes the object sufficiently | |
| 201 | 427 |
Consumer factory: init for gsdo/service_id: &1 | The short text describes the object sufficiently | |
| 202 | 428 |
Consumer factory: end for Object: &1 | The short text describes the object sufficiently | |
| 203 | 429 |
Consumer DCS create Object: init | The short text describes the object sufficiently | |
| 204 | 430 |
Consumer DCS create Object successfully finished | The short text describes the object sufficiently | |
| 205 | 431 |
Consumer DCS create Object failed and cleanup executed | The short text describes the object sufficiently | |
| 206 | 432 |
Consumer DCS update Object: init | The short text describes the object sufficiently | |
| 207 | 433 |
Consumer DCS update Object successfully finished. | The short text describes the object sufficiently | |
| 208 | 434 |
Consumer DCS update Object failed and cleanup executed | The short text describes the object sufficiently | |
| 209 | 435 |
Consumer DCS delete Object: init | The short text describes the object sufficiently | |
| 210 | 436 |
Consumer DCS delete Object successfully finished | The short text describes the object sufficiently | |
| 211 | 437 |
Consumer DCS deletd Object failed and cleanup executed | The short text describes the object sufficiently | |
| 212 | 438 |
Consumer DCS finalizer: init | The short text describes the object sufficiently | |
| 213 | 439 |
Consumer DCS finalizer successfully finished | The short text describes the object sufficiently | |
| 214 | 440 |
Consumer DCS finalizer failed and cleanup executed | The short text describes the object sufficiently | |
| 215 | 441 |
Consumer DCS read data: init | The short text describes the object sufficiently | |
| 216 | 442 |
Consumer DCS read data successfully finished | The short text describes the object sufficiently | |
| 217 | 443 |
Consumer DCS read data failed and cleanup executed | The short text describes the object sufficiently | |
| 218 | 444 |
Consumer read-method was executed, but no ID was provided | The short text describes the object sufficiently | |
| 219 | 445 |
The short text describes the object sufficiently | ||
| 220 | 446 |
The short text describes the object sufficiently | ||
| 221 | 450 |
******** Consumer Design Time ******** | The short text describes the object sufficiently | |
| 222 | 451 |
Consumer design time: write objects to transport: started | The short text describes the object sufficiently | |
| 223 | 452 |
Consumer design time: write objects to transport: completed | The short text describes the object sufficiently | |
| 224 | 453 |
Consumer design time: create service: started | The short text describes the object sufficiently | |
| 225 | 454 |
Consumer design time: create service: completed | The short text describes the object sufficiently | |
| 226 | 455 |
Consumer design time: delete model: started | The short text describes the object sufficiently | |
| 227 | 456 |
Consumer design time: delete model: completed | The short text describes the object sufficiently | |
| 228 | 457 |
Consumer design time: generate service: started | The short text describes the object sufficiently | |
| 229 | 458 |
Consumer design time: generate service: completed | The short text describes the object sufficiently | |
| 230 | 459 |
Consumer design time: generate Web service: started | The short text describes the object sufficiently | |
| 231 | 460 |
Consumer design time: generate Web service: completed | The short text describes the object sufficiently | |
| 232 | 461 |
Consumer design time: load attributes: started | The short text describes the object sufficiently | |
| 233 | 462 |
Consumer design time: load attributes: completed | The short text describes the object sufficiently | |
| 234 | 463 |
Consumer design time: load service: started | The short text describes the object sufficiently | |
| 235 | 464 |
Consumer design time: load service: completed | The short text describes the object sufficiently | |
| 236 | 465 |
Consumer design time: save attributes: started | The short text describes the object sufficiently | |
| 237 | 466 |
Consumer design time: save attributes: completed | The short text describes the object sufficiently | |
| 238 | 467 |
The short text describes the object sufficiently | ||
| 239 | 468 |
Conversion report: started | The short text describes the object sufficiently | |
| 240 | 469 |
Conversion report: completed | The short text describes the object sufficiently | |
| 241 | 470 |
The short text describes the object sufficiently | ||
| 242 | 471 |
The short text describes the object sufficiently | ||
| 243 | 472 |
The short text describes the object sufficiently | ||
| 244 | 499 |
******CAL runtime | The short text describes the object sufficiently | |
| 245 | 500 |
Load flat mapping model for mapping service ID: '&1' | The short text describes the object sufficiently | |
| 246 | 501 |
Load flat mapping model finished successfully | The short text describes the object sufficiently | |
| 247 | 520 |
******Event Handler | The short text describes the object sufficiently | |
| 248 | 521 |
Content Publisher's Object Notification Event Handler processing started | The short text describes the object sufficiently | |
| 249 | 522 |
Content Publisher's Object Notification Event Handler succeeded | The short text describes the object sufficiently | |
| 250 | 523 |
Content Publisher's Object Notification Event Handler failed | Space: object requires documentation | |
| 251 | 524 |
Content Publisher's Message Notification Event Handler processing started | The short text describes the object sufficiently | |
| 252 | 525 |
Content Publisher's Message Notification Event Handler succeeded | The short text describes the object sufficiently | |
| 253 | 527 |
*****Log of person related data | The short text describes the object sufficiently | |
| 254 | 528 |
Client has received data for GSDO. This is a security log information. | The short text describes the object sufficiently | |
| 255 | 529 |
Business Object disclosed to a client in the response. See details. | The short text describes the object sufficiently | |
| 256 | 530 |
&1 of the Business Object were disclosed to a client in the response. | The short text describes the object sufficiently | |
| 257 | 531 |
Entity disclosed to a client in the response. See details. | The short text describes the object sufficiently | |
| 258 | 532 |
*****STC GSDO Generator | The short text describes the object sufficiently | |
| 259 | 533 |
Generation of the STC for GSDO '&1' class '&2' model '&1' started. | The short text describes the object sufficiently | |
| 260 | 534 |
Generation of the STC for GSDO '&1' class '&2' completed successfully. | The short text describes the object sufficiently | |
| 261 | 600 |
******* Subscriptions & Notifications ******* | The short text describes the object sufficiently | |
| 262 | 601 |
Started processing of event &1 for object &2 received from &3/&4 | The short text describes the object sufficiently | |
| 263 | 602 |
Completed processing of event &1 for object &2 received from &3/&4 | The short text describes the object sufficiently | |
| 264 | 603 |
The short text describes the object sufficiently |
History
| Last changed on/by | |
20141120 | SAP |
| SAP Release Created in | 100 |
