ESH_ADAPT_MSG - Adapter Messages
The following messages are stored in message class ESH_ADAPT_MSG: Adapter Messages.
It is part of development package S_ESH_CONTENT_FED_ADAPTERS in software component BC-EIM-ESH. This development package consists of objects that can be grouped under "Adapters for Federated Search".
It is part of development package S_ESH_CONTENT_FED_ADAPTERS in software component BC-EIM-ESH. This development package consists of objects that can be grouped under "Adapters for Federated Search".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &1 |
| 001 | Adapter &1: Error constructing the response |
| 002 | Adapter &1: No KM connectors delivered for searching |
| 003 | Error in connectivity manager of &1 |
| 004 | Error during creation of the logical port for adapter &1 |
| 005 | Error while getting indexes from KM: &1 |
| 006 | No connectivity details available for adapter &1 |
| 007 | Missing input parameters for defining a KM connectivity |
| 008 | Error in index manager of &1. Index service not available |
| 009 | Could not delete logical port &1 |
| 010 | Error during metadata retrieval in adapter &1 |
| 011 | Error during search in adapter &1 |
| 012 | Error during response conversion in adapter &1 |
| 013 | Missing input parameters for defining a WS connectivity |
| 014 | Error during connectivity creation in adapter &1 |
| 015 | Error during connectivity deletion in adapter &1 |
| 016 | Error while accessing KM server/KM index management service |
| 017 | Could not create handler for log.port &1. Check if KM system is available |
| 018 | No properties available for log.port &1. Check if KM system is available |
| 019 | No HTTP client could be created for destination &1 (by ping-destination) |
| 020 | Ping for destination &1 unsuccessful with message &2 (by send) |
| 021 | Ping for destination &1 unsuccessful with message &2 (by receive) |
| 022 | Communication unsuccessful in adapter &1 |
| 023 | Could not create handler for log.port &1. Check if WS is available |
| 024 | No properties available for log.port &1. Check if WS is available |
| 025 | Web service (proxy &1) not available |
| 026 | Duplicate logical port name &1 |
| 027 | Characters &1 are not allowed in logical port name |
| 028 | Blanks are not allowed in logical port name |
| 029 | Characters &1 and blanks are not allowed in logical port name |
| 030 | Error calling the external HTTP service &1 |
| 031 | --> User account/authorization (S_RFCACL) is missing in back-end system |
| 032 | Error building template type reference |
| 033 | Error while structuring the display in the SAP List Viewer |
| 034 | Logical port &1 cannot be deleted |
| 035 | Logical port &1 cannot be deleted |
| 036 | Action was completed successfully |
| 037 | You are not authorized to delete logical ports for data provider services |
| 038 | Records with connection GUID &1 could not be deleted |
| 039 | Logical port &1 is already synchronous |
| 040 | Logical port &1 cannot be synchronized |
| 041 | &1 &2 &3 &4 |
| 042 | Record with connection GUID &1 locked by user &2 |
| 043 | Business object &1 is not supported in system &2 |
| 044 | Error parsing the OpenSearch results |
| 045 | Characters &1 are not allowed in RFC destination name |
| 046 | Blanks are not allowed in RFC destination name |
| 047 | Characters &1 and blanks are not allowed in RFC destination name |
| 048 | RFC destination name must not be initial |
| 049 | Internal error creating RFC destination &1 |
| 050 | The authentication method for the RFC destination &1 requires logon data |
| 051 | Character &1 is not allowed at position 1 in RFC destination name |
| 052 | Internal error reading RFC destination &1 |
| 053 | Internal error generating ID for RFC destination &1 |
| 054 | Internal error deleting RFC destination &1 |
| 055 | RFC destination &1 is locked by another user. Deletion not possible |
| 056 | Logical port &1 does not exist |
| 057 | Logical port name must not be initial |
| 058 | Search adapter instatiation: ABAP class name is initial |
| 059 | Search adapter instatiation: Template type is initial |