Message Number list used by SAP ABAP Class CL_SOAP_LOGGER_EXT (Utilized methods for logging special message and sequence op)
SAP ABAP Class
CL_SOAP_LOGGER_EXT (Utilized methods for logging special message and sequence op) is using
| # | Object Type | Object Name | Object Description | Note |
|---|---|---|---|---|
| 1 | SRT_LOGGING - 007 | bgRFC no authority for deletion at client "&" destination "&" | ||
| 2 | SRT_LOGGING - 008 | bgRFC empty queue list at client "&" destination "&" | ||
| 3 | SRT_LOGGING - 009 | bgRFC invalid destination at client "&" destination "&" | ||
| 4 | SRT_LOGGING - 010 | System failure in remote call to client "&" destination "&" | ||
| 5 | SRT_LOGGING - 011 | Communication failure in remote call to client "&" destination "&" | ||
| 6 | SRT_LOGGING - 012 | bgRFC missing destination at client "&" | ||
| 7 | SRT_LOGGING - 014 | Delete of queue names for table 'SRT_SEQ_QUE' failed | ||
| 8 | SRT_LOGGING - 015 | Unknown error calling 'SRT_SEQ_DELETE_BGRFC_QUEUES' | ||
| 9 | SRT_LOGGING - 018 | Message ID &1 is started with debugging | ||
| 10 | SRT_LOGGING - 019 | Sequence ID &1 is (re)started with debugging | ||
| 11 | SRT_LOGGING - 021 | Logical sequence with ID &1 is manually restarted | ||
| 12 | SRT_LOGGING - 022 | Logical sequence with ID &1 is deleted (hard terminated) | ||
| 13 | SRT_LOGGING - 023 | Persist ID &1 is cancelled because of Logical sequence hard termination | ||
| 14 | SRT_LOGGING - 024 | Message ID &1 at pipeline ID &2 is manually restarted | ||
| 15 | SRT_LOGGING - 025 | Message ID &1 at pipeline ID &2 is manually cancelled | ||
| 16 | SRT_LOGGING - 026 | Message ID &1 at pipeline ID &2 is manually set to "Finish" | ||
| 17 | SRT_LOGGING - 027 | Payload of message ID &1 at pipeline ID &2 is changed | ||
| 18 | SRT_LOGGING - 028 | Message ID &1 at pipeline ID &2 is cancelled via clean-up tool | ||
| 19 | SRT_LOGGING - 029 | Persist ID &1 | ||
| 20 | SRT_LOGGING - 029 | Persist ID &1 | ||
| 21 | SRT_LOGGING - 029 | Persist ID &1 | ||
| 22 | SRT_LOGGING - 029 | Persist ID &1 | ||
| 23 | SRT_LOGGING - 029 | Persist ID &1 | ||
| 24 | SRT_LOGGING - 029 | Persist ID &1 | ||
| 25 | SRT_LOGGING - 030 | Logical sequence ID &1 | ||
| 26 | SRT_LOGGING - 030 | Logical sequence ID &1 | ||
| 27 | SRT_LOGGING - 030 | Logical sequence ID &1 | ||
| 28 | SRT_LOGGING - 030 | Logical sequence ID &1 | ||
| 29 | SRT_LOGGING - 030 | Logical sequence ID &1 | ||
| 30 | SRT_LOGGING - 030 | Logical sequence ID &1 | ||
| 31 | SRT_LOGGING - 031 | SEQ = &1 | ||
| 32 | SRT_LOGGING - 031 | SEQ = &1 | ||
| 33 | SRT_LOGGING - 031 | SEQ = &1 | ||
| 34 | SRT_LOGGING - 031 | SEQ = &1 | ||
| 35 | SRT_LOGGING - 031 | SEQ = &1 | ||
| 36 | SRT_LOGGING - 032 | MSG = &1 and SEQ = &2 | ||
| 37 | SRT_LOGGING - 032 | MSG = &1 and SEQ = &2 | ||
| 38 | SRT_LOGGING - 032 | MSG = &1 and SEQ = &2 | ||
| 39 | SRT_LOGGING - 032 | MSG = &1 and SEQ = &2 | ||
| 40 | SRT_LOGGING - 032 | MSG = &1 and SEQ = &2 | ||
| 41 | SRT_LOGGING - 032 | MSG = &1 and SEQ = &2 | ||
| 42 | SRT_LOGGING - 032 | MSG = &1 and SEQ = &2 | ||
| 43 | SRT_LOGGING - 032 | MSG = &1 and SEQ = &2 | ||
| 44 | SRT_LOGGING - 032 | MSG = &1 and SEQ = &2 | ||
| 45 | SRT_LOGGING - 032 | MSG = &1 and SEQ = &2 | ||
| 46 | SRT_LOGGING - 033 | &1 &2 &3 &4 | ||
| 47 | SRT_LOGGING - 033 | &1 &2 &3 &4 | ||
| 48 | SRT_LOGGING - 035 | MSG = &1 | ||
| 49 | SRT_LOGGING - 036 | Sequence status manually changed from & to & by forwarded error handling | ||
| 50 | SRT_LOGGING - 037 | Message &1 at pipeline &2 is manually reconciled via clean-up tool. | ||
| 51 | SRT_LOGGING - 038 | Logical sequence with ID &1 with WSRM gaps is deleted (terminated) | ||
| 52 | SRT_LOGGING - 039 | Persist ID &1 is cancelled because of sequence termination with WSRM gaps | ||
| 53 | SRT_LOGGING - 040 | Event with Event ID &1 is manually restarted | ||
| 54 | SRT_LOGGING - 041 | WS-RM event handler is started | ||
| 55 | SRT_LOGGING - 042 | WS-RM event handler is stopped | ||
| 56 | SRT_LOGGING - 043 | Change of number for maximum permitted allowed processes from <&> to <&> | ||
| 57 | SRT_LOGGING - 044 | Task watcher is started | ||
| 58 | SRT_LOGGING - 045 | Task watcher is stopped | ||
| 59 | SRT_LOGGING - 046 | Change of time period for task watcher from <&> seconds to <&> seconds | ||
| 60 | SRT_LOGGING - 047 | Technical Setup started | ||
| 61 | SRT_LOGGING - 048 | Technical Reset started | ||
| 62 | SRT_LOGGING - 049 | User &1 created for web service service destination in client: &2 | ||
| 63 | SRT_LOGGING - 050 | User &1 deleted for web service service destination in client: &2 | ||
| 64 | SRT_LOGGING - 051 | RFC Destination &1 created as service destination in client: &2 | ||
| 65 | SRT_LOGGING - 052 | RFC Destination & deleted as service destination in client: & | ||
| 66 | SRT_LOGGING - 053 | RFC Destination &1 registered as service destination in client: &2 | ||
| 67 | SRT_LOGGING - 054 | RFC Destination &1 deregistered as service destination in client: &2 | ||
| 68 | SRT_LOGGING - 056 | Inbound destination &1 registered at global properties | ||
| 69 | SRT_LOGGING - 059 | Change time period for IDP switch area &1 from &2 to &3 min | ||
| 70 | SRT_LOGGING - 060 | Compensate ID &1 was restarted for client &2 by user &3 | ||
| 71 | SRT_LOGGING - 061 | Compensate ID &1 was cancelled/deleted for client &2 by user &3 | ||
| 72 | SRT_LOGGING - 062 | Compensate ID &1 Status was manually changed for client &2 by user &3 | ||
| 73 | SRT_LOGGING - 063 | Compensate ID &1 is related to sequence ID &2 | ||
| 74 | SRT_LOGGING - 063 | Compensate ID &1 is related to sequence ID &2 | ||
| 75 | SRT_LOGGING - 063 | Compensate ID &1 is related to sequence ID &2 | ||
| 76 | SRT_LOGGING - 064 | Compensate ID &1 has no relation to any sequence | ||
| 77 | SRT_LOGGING - 064 | Compensate ID &1 has no relation to any sequence | ||
| 78 | SRT_LOGGING - 064 | Compensate ID &1 has no relation to any sequence | ||
| 79 | SRT_LOGGING - 065 | Compensate ID &1 is related to Persist ID &2 | ||
| 80 | SRT_LOGGING - 065 | Compensate ID &1 is related to Persist ID &2 | ||
| 81 | SRT_LOGGING - 065 | Compensate ID &1 is related to Persist ID &2 | ||
| 82 | SRT_LOGGING - 066 | SEQ = &1 and TECH_SEQ = &2 | ||
| 83 | SRT_LOGGING - 066 | SEQ = &1 and TECH_SEQ = &2 | ||
| 84 | SRT_LOGGING - 067 | IDOC sequence was created again, predecessor date: &1 | ||
| 85 | SRT_LOGGING - 068 | IDoc reconciliation request initiated by application on consumer side | ||
| 86 | SRT_LOGGING - 069 | IDoc reconciliation request sent on consumer side | ||
| 87 | SRT_LOGGING - 070 | IDoc reconciliation request received on provider side | ||
| 88 | SRT_LOGGING - 071 | Message ID: &1 | ||
| 89 | SRT_LOGGING - 072 | Message ID: &1, Message number: &2 | ||
| 90 | SRT_LOGGING - 072 | Message ID: &1, Message number: &2 | ||
| 91 | SRT_LOGGING - 073 | IDoc message discarded due to reconciliation message with higher number | ||
| 92 | SRT_LOGGING - 074 | Error terminating WSRM sequence &1 | ||
| 93 | SRT_LOGGING - 075 | Queue unlock error: &1 | ||
| 94 | SRT_LOGGING - 076 | Missing End of Performance Trace: &1 &2 | ||
| 95 | SRT_LOGGING - 077 | Mass message cancelling finished | ||
| 96 | SRT_LOGGING - 078 | &1 message(s) have been cancelled. | ||
| 97 | SRT_LOGGING - 079 | Mass message cancelling started | ||
| 98 | SRT_LOGGING - 080 | Cancelling starts for & message(s). | ||
| 99 | SRT_LOGGING - 081 | &3 trace level for &1 &2 was set to &4 | ||
| 100 | SRT_LOGGING - 082 | Trace configuration for &1 &2 was created | ||
| 101 | SRT_LOGGING - 083 | Trace configuration for &1 &2 was removed | ||
| 102 | SRT_LOGGING - 084 | Configuration for &1 was changed to "&2" | ||
| 103 | SRT_LOGGING - 085 | Logical Port &1 of of event is manually cancelled | ||
| 104 | SRT_LOGGING - 086 | Parent Event ID &1 | ||
| 105 | SRT_LOGGING - 087 | Event with Event ID &1 is manually cancelled | ||
| 106 | SRT_LOGGING - 088 | Operation: &1, &2, &3 |