SAP ABAP Message Class SRT_LOGGING (SRT_LOGGING)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-ESI-WS-ABA-RT (Application Component) WebServices ABAP Runtime
⤷ SOAP_UTIL (Package) SOAP Runtime Utilities
⤷ BC-ESI-WS-ABA-RT (Application Component) WebServices ABAP Runtime
⤷ SOAP_UTIL (Package) SOAP Runtime Utilities
Attributes
Message class | SRT_LOGGING | |
Short Description | ||
Changed On | 20140121 | |
Last Changed At | 103802 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | Started Session SystemId "&" on Host "&" for User "&" Program "&" | The short text describes the object sufficiently | |
2 | 001 | Deletion started from Consumer to Provider records | The short text describes the object sufficiently | |
3 | 002 | Deletion only of Provider records | The short text describes the object sufficiently | |
4 | 003 | &1 Consumer record(s) has/ve been deleted from header table | The short text describes the object sufficiently | |
5 | 004 | &1 Provider record(s) has/ve been deleted from header table | The short text describes the object sufficiently | |
6 | 005 | Parameters: Created before "&" User "&" SeqProcState "&" | The short text describes the object sufficiently | |
7 | 006 | Parameters: Sequence ID "&" | The short text describes the object sufficiently | |
8 | 007 | bgRFC no authority for deletion at client "&" destination "&" | The short text describes the object sufficiently | |
9 | 008 | bgRFC empty queue list at client "&" destination "&" | The short text describes the object sufficiently | |
10 | 009 | bgRFC invalid destination at client "&" destination "&" | The short text describes the object sufficiently | |
11 | 010 | System failure in remote call to client "&" destination "&" | The short text describes the object sufficiently | |
12 | 011 | Communication failure in remote call to client "&" destination "&" | The short text describes the object sufficiently | |
13 | 012 | bgRFC missing destination at client "&" | The short text describes the object sufficiently | |
14 | 013 | Not all bgRFC queues could be deleted. See Application log for details | The short text describes the object sufficiently | |
15 | 014 | Delete of queue names for table 'SRT_SEQ_QUE' failed | The short text describes the object sufficiently | |
16 | 015 | Unknown error calling 'SRT_SEQ_DELETE_BGRFC_QUEUES' | The short text describes the object sufficiently | |
17 | 018 | Message ID &1 is started with debugging | The short text describes the object sufficiently | |
18 | 019 | Sequence ID &1 is (re)started with debugging | The short text describes the object sufficiently | |
19 | 020 | Logical sequence with ID &1 is closed (soft terminated) | The short text describes the object sufficiently | |
20 | 021 | Logical sequence with ID &1 is manually restarted | The short text describes the object sufficiently | |
21 | 022 | Logical sequence with ID &1 is deleted (hard terminated) | The short text describes the object sufficiently | |
22 | 023 | Persist ID &1 is cancelled because of Logical sequence hard termination | The short text describes the object sufficiently | |
23 | 024 | Message ID &1 at pipeline ID &2 is manually restarted | The short text describes the object sufficiently | |
24 | 025 | Message ID &1 at pipeline ID &2 is manually cancelled | The short text describes the object sufficiently | |
25 | 026 | Message ID &1 at pipeline ID &2 is manually set to "Finish" | The short text describes the object sufficiently | |
26 | 027 | Payload of message ID &1 at pipeline ID &2 is changed | The short text describes the object sufficiently | |
27 | 028 | Message ID &1 at pipeline ID &2 is cancelled via clean-up tool | The short text describes the object sufficiently | |
28 | 029 | Persist ID &1 | The short text describes the object sufficiently | |
29 | 030 | Logical sequence ID &1 | The short text describes the object sufficiently | |
30 | 031 | SEQ = &1 | The short text describes the object sufficiently | |
31 | 032 | MSG = &1 and SEQ = &2 | The short text describes the object sufficiently | |
32 | 033 | &1 &2 &3 &4 | The short text describes the object sufficiently | |
33 | 034 | MSG = &1 MSG_PID = &2 | The short text describes the object sufficiently | |
34 | 035 | MSG = &1 | The short text describes the object sufficiently | |
35 | 036 | Sequence status manually changed from & to & by forwarded error handling | The short text describes the object sufficiently | |
36 | 037 | Message &1 at pipeline &2 is manually reconciled via clean-up tool. | The short text describes the object sufficiently | |
37 | 038 | Logical sequence with ID &1 with WSRM gaps is deleted (terminated) | The short text describes the object sufficiently | |
38 | 039 | Persist ID &1 is cancelled because of sequence termination with WSRM gaps | The short text describes the object sufficiently | |
39 | 040 | Event with Event ID &1 is manually restarted | The short text describes the object sufficiently | |
40 | 041 | WS-RM event handler is started | The short text describes the object sufficiently | |
41 | 042 | WS-RM event handler is stopped | The short text describes the object sufficiently | |
42 | 043 | Change of number for maximum permitted allowed processes from <&> to <&> | The short text describes the object sufficiently | |
43 | 044 | Task watcher is started | The short text describes the object sufficiently | |
44 | 045 | Task watcher is stopped | The short text describes the object sufficiently | |
45 | 046 | Change of time period for task watcher from <&> seconds to <&> seconds | The short text describes the object sufficiently | |
46 | 047 | Technical Setup started | The short text describes the object sufficiently | |
47 | 048 | Technical Reset started | The short text describes the object sufficiently | |
48 | 049 | User &1 created for web service service destination in client: &2 | The short text describes the object sufficiently | |
49 | 050 | User &1 deleted for web service service destination in client: &2 | The short text describes the object sufficiently | |
50 | 051 | RFC Destination &1 created as service destination in client: &2 | The short text describes the object sufficiently | |
51 | 052 | RFC Destination & deleted as service destination in client: & | The short text describes the object sufficiently | |
52 | 053 | RFC Destination &1 registered as service destination in client: &2 | The short text describes the object sufficiently | |
53 | 054 | RFC Destination &1 deregistered as service destination in client: &2 | The short text describes the object sufficiently | |
54 | 055 | Inbound destination &1 registered at bgrfc for prefixes | The short text describes the object sufficiently | |
55 | 056 | Inbound destination &1 registered at global properties | The short text describes the object sufficiently | |
56 | 057 | Inbound destination &1 deregistered from bgrfc for prefixes | The short text describes the object sufficiently | |
57 | 058 | Inbound destination &1 deregistered from global properties | The short text describes the object sufficiently | |
58 | 059 | Change time period for IDP switch area &1 from &2 to &3 min | The short text describes the object sufficiently | |
59 | 060 | Compensate ID &1 was restarted for client &2 by user &3 | The short text describes the object sufficiently | |
60 | 061 | Compensate ID &1 was cancelled/deleted for client &2 by user &3 | The short text describes the object sufficiently | |
61 | 062 | Compensate ID &1 Status was manually changed for client &2 by user &3 | The short text describes the object sufficiently | |
62 | 063 | Compensate ID &1 is related to sequence ID &2 | The short text describes the object sufficiently | |
63 | 064 | Compensate ID &1 has no relation to any sequence | The short text describes the object sufficiently | |
64 | 065 | Compensate ID &1 is related to Persist ID &2 | The short text describes the object sufficiently | |
65 | 066 | SEQ = &1 and TECH_SEQ = &2 | The short text describes the object sufficiently | |
66 | 067 | IDOC sequence was created again, predecessor date: &1 | The short text describes the object sufficiently | |
67 | 068 | IDoc reconciliation request initiated by application on consumer side | The short text describes the object sufficiently | |
68 | 069 | IDoc reconciliation request sent on consumer side | The short text describes the object sufficiently | |
69 | 070 | IDoc reconciliation request received on provider side | The short text describes the object sufficiently | |
70 | 071 | Message ID: &1 | The short text describes the object sufficiently | |
71 | 072 | Message ID: &1, Message number: &2 | The short text describes the object sufficiently | |
72 | 073 | IDoc message discarded due to reconciliation message with higher number | The short text describes the object sufficiently | |
73 | 074 | Error terminating WSRM sequence &1 | The short text describes the object sufficiently | |
74 | 075 | Queue unlock error: &1 | The short text describes the object sufficiently | |
75 | 076 | Missing End of Performance Trace: &1 &2 | The short text describes the object sufficiently | |
76 | 077 | Mass message cancelling finished | The short text describes the object sufficiently | |
77 | 078 | &1 message(s) have been cancelled. | The short text describes the object sufficiently | |
78 | 079 | Mass message cancelling started | The short text describes the object sufficiently | |
79 | 080 | Cancelling starts for & message(s). | The short text describes the object sufficiently | |
80 | 081 | &3 trace level for &1 &2 was set to &4 | The short text describes the object sufficiently | |
81 | 082 | Trace configuration for &1 &2 was created | The short text describes the object sufficiently | |
82 | 083 | Trace configuration for &1 &2 was removed | The short text describes the object sufficiently | |
83 | 084 | Configuration for &1 was changed to "&2" | Space: object requires documentation | |
84 | 085 | Logical Port &1 of of event is manually cancelled | The short text describes the object sufficiently | |
85 | 086 | Parent Event ID &1 | The short text describes the object sufficiently | |
86 | 087 | Event with Event ID &1 is manually cancelled | The short text describes the object sufficiently | |
87 | 088 | Operation: &1, &2, &3 | The short text describes the object sufficiently | |
88 | 100 | Message not restarted due to too many failed attempts to restart | Space: object requires documentation |
History
Last changed on/by | 20140121 | SAP | |
SAP Release Created in | 711 |