SAP ABAP Message Class SOAP_UDS (Messages for user defined search)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-ESI-WS-ABA-RT (Application Component) WebServices ABAP Runtime
⤷
SOAP_USER_DEFINED_SEARCH (Package) User defined search
⤷
⤷
Attributes
| Message class | SOAP_UDS | |
| Short Description | Messages for user defined search | |
| Changed On | 20140121 | |
| Last Changed At | 103758 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | &1 &2 &3 &4 | The short text describes the object sufficiently | ||
| 2 | Your are not authorized to perform this operation | The short text describes the object sufficiently | ||
| 3 | Required context menu &1 is not found | The short text describes the object sufficiently | ||
| 4 | Current configuration is already locked by user &1 | The short text describes the object sufficiently | ||
| 5 | Warning on deletion of UDS configuration | Space: object requires documentation | ||
| 6 | The search name will no longer be available in the value (F4) help | The short text describes the object sufficiently | ||
| 7 | Alternatively, you can deactivate the configuration | The short text describes the object sufficiently | ||
| 8 | to retain the search names in the value (F4) help. | The short text describes the object sufficiently | ||
| 9 | Do you want to delete the search name "&1"? | The short text describes the object sufficiently | ||
| 10 | Current configuration is not consistent | The short text describes the object sufficiently | ||
| 11 | &1 message(s) found | The short text describes the object sufficiently | ||
| 12 | Search for messages with a proper searching method and time range | The short text describes the object sufficiently | ||
| 13 | Start simulation after selecting a message | The short text describes the object sufficiently | ||
| 14 | No message found. | The short text describes the object sufficiently | ||
| 15 | Messages must be from interface "&1:&2" and operation "&3" | The short text describes the object sufficiently | ||
| 16 | You may increase the time range to include older messages. | The short text describes the object sufficiently | ||
| 17 | &1 interface and operation combination(s) displayed | The short text describes the object sufficiently | ||
| 18 | Configuration with interface "&1" and operation "&2" could not be found | The short text describes the object sufficiently | ||
| 19 | No row is deleted from database with interface "&1" and operation "&2" | The short text describes the object sufficiently | ||
| 20 | Configuration is inconsistent, probablly deleted | The short text describes the object sufficiently | ||
| 21 | Search name "&1" cannot be added because the same name exists already | The short text describes the object sufficiently | ||
| 22 | Current configuration cannot be changed. Switch to editing mode first | The short text describes the object sufficiently | ||
| 23 | Configuration with interface "&1" and operation "&2" exists already | The short text describes the object sufficiently | ||
| 24 | Transporting current configuration(s) has been canceled | The short text describes the object sufficiently | ||
| 25 | Current client settings allow no change of configurations | The short text describes the object sufficiently | ||
| 26 | Current client settings allow no transport of configurations | The short text describes the object sufficiently | ||
| 27 | Current configuration has been modified, save or cancel first | The short text describes the object sufficiently | ||
| 28 | Transporting current configuration(s) has been done with request "&1" | The short text describes the object sufficiently | ||
| 29 | Deleting a configuration also deletes the search names it contains. | The short text describes the object sufficiently | ||
| 30 | These names will no longer be available in the value (F4) help | The short text describes the object sufficiently | ||
| 31 | when retrieving messages in User Definied Search (SRT_MONI). | The short text describes the object sufficiently | ||
| 32 | Transporting current configuration(s) failed - "&1". | The short text describes the object sufficiently | ||
| 33 | *** Indexing messages *** | The short text describes the object sufficiently | ||
| 34 | No authorization for UDS index maintenance (object = S_SRT_UDSM) | The short text describes the object sufficiently | ||
| 35 | No authorization for complete UDS re-indexing (object = S_SRT_UDSM) | The short text describes the object sufficiently | ||
| 36 | A UDS indexing job is already running. The present execution is stopped. | The short text describes the object sufficiently | ||
| 37 | The enqueue service reports a system failure. | The short text describes the object sufficiently | ||
| 38 | Failure for message "&1" in location "&2". Interface/Operation not found. | The short text describes the object sufficiently | ||
| 39 | Failure for message "&1" in location "&2". No payload found. | The short text describes the object sufficiently | ||
| 40 | Messages processed: &1. Messages indexed: &2. Last UTC timestamp: &3 | The short text describes the object sufficiently | ||
| 41 | UDS indexing failed. | The short text describes the object sufficiently | ||
| 42 | UDS indexing started. | The short text describes the object sufficiently | ||
| 43 | UDS indexing finished. | The short text describes the object sufficiently | ||
| 44 | &1&2&3&4 | The short text describes the object sufficiently | ||
| 45 | Execution aborted by user. | The short text describes the object sufficiently | ||
| 46 | Unexpected Exception caught | The short text describes the object sufficiently | ||
| 47 | UDS Indexing job failed. The Index is not complete. | The short text describes the object sufficiently | ||
| 48 | Failure for message "&1" in location "&2". UDS extraction failed. | The short text describes the object sufficiently |
History
| Last changed on/by | 20140121 | SAP | |
| SAP Release Created in | 740 |