ESH_INTEGRATION - ESH Integration
The following messages are stored in message class ESH_INTEGRATION: ESH Integration.
It is part of development package S_ESH_ENG_INTEGRATION in software component BC-EIM-ESH. This development package consists of objects that can be grouped under "Backend Integration Services".
It is part of development package S_ESH_ENG_INTEGRATION in software component BC-EIM-ESH. This development package consists of objects that can be grouped under "Backend Integration Services".
Message Nr ▲ | Message Text |
|---|---|
| 001 | No blueprint specified; cannot create data object |
| 002 | Error in blueprint table: Can create only one data field |
| 003 | Field &1: Unknown data type &2 |
| 004 | No components; cannot create data object |
| 005 | &1: Error during data cluster import from remote system |
| 006 | Function can only be used in a ES hub |
| 007 | Relocation of Enterprise Search to Enterprise Search hub |
| 008 | ...Completed |
| 009 | 01/&1: Connect back-end system to ES hub |
| 010 | 02/&1: Create reverse connection in back-end system |
| 011 | 04/&1: Determine relocation scope |
| 012 | 05/&1: Read template data from back-end system |
| 013 | 03/&1: Lock template modeler in back-end system |
| 014 | 06/&1: Map software component keys |
| 015 | 07/&1: Write template data in ES hub |
| 016 | 08/&1: Assign back-end system to software components |
| 017 | 09/&1: Read connector data from back-end system |
| 018 | 10/&1: Suspend extraction in back-end system |
| 019 | 12/&1: Adapt connector data |
| 020 | 13/&1: Create connectors in ES hub |
| 021 | 11/&1: Export TREX index content from back-end system |
| 022 | 14/&1: Import TREX index content to ES hub |
| 023 | 15/&1: Replicate connector runtime buffer to back-end systems |
| 024 | 16/&1: Register software components for delegation to ES hub |
| 025 | 17/&1: Delete connectors in back-end system |
| 026 | Resume with step &1 |
| 027 | Invalid connection data |
| 028 | Specify connection |
| 029 | Back-end system: &1 |
| 030 | Select start step: |
| 031 | Own logical system not registered in ES configuration |
| 032 | Back-end system successfully disconnected from the ES hub |
| 033 | Process successfully completed |
| 034 | Process terminated |
| 035 | Model updates available for system &1 |
| 036 | File share for index content relocation is missing |
| 037 | No connectors in back end; skip corresponding steps 9 to 14 and 17 |
| 038 | All model data is up-to-date; skip steps &1 to &2 |
| 039 | Active connectors exist and no import path is specified |
| 040 | This process may take some minutes, please be patient |
| 041 | RFC failure at destination &1: &2 |
| 042 | No changes detected, all models are up-to-date |
| 043 | End of log |
| 044 | Connector cannot be created |
| 045 | Start relocation process for back-end system &1, client &2 first |
| 046 | No authorization to detach back-end system |
| 047 | Please be patient... |
| 048 | Error occurred |
| 049 | Cannot resolve dependencies of software component &1 |
| 050 | Get software component &1 |
| 051 | Processing software component &1 |
| 052 | Back-end system: &1 -> ES hub: &2 |
| 053 | System &1, client &2 is not connected to ES hub |
| 054 | System &1, client &2 is an ES hub; choose a back-end system |
| 055 | Runtime data was updated in back-end system &1 |
| 056 | System &1 is currently not available |
| 057 | Back-end system connection exists; skip steps 1 to 3 |
| 058 | Replicate connector runtime buffer to back-end systems |
| 059 | Delete connection (RFC destination: &1) |
| 060 | Back-end system and ES hub share TREX instance; skip step 11 |
| 061 | Relocation process was unexpectedly terminated |
| 062 | &1&2&3&4 |
| 063 | System could not be reached via RFC destination &1 |
| 064 | Client copy was unexpectedly terminated |
| 065 | System is already linked to another ES hub: &1 |
| 066 | System &2, client &3 could not be reached via RFC destination &1 |
| 067 | System &1, client &2 processed &3 relevant search connectors |
| 068 | Another relocation process is already running |
| 069 | Back-end software component &1 is mapped and up-to-date; skip |
| 070 | Back-end software component &1 maps to &2 in ES hub; skip |
| 071 | Back-end system &1 client &2 cannot be assigned to the selected SWC |
| 072 | All model data is up-to-date |
| 073 | Error writing model data to remote system |
| 074 | Class &1 is not available via RFC destination &2 |
| 075 | Class &1 is not registered for data interchange |
| 076 | Class not provided for data interchange |
| 077 | Unknown error during data interchange with RFC destination &1 |
| 078 | Function can only be used in a ES appliance |
| 079 | Hub test: The Relocation process will be simulated |
| 080 | Hub test: The back-end system specified does not exist |
| 081 | SAP HANA back-end system: Search content cannot be relocated |
| 200 | System is RemoteSearch proxy |
| 201 | System is RemoteSearch back-end |
| 202 | Connecting back-end |
| 203 | Connection to back-end created |
| 204 | Reverse connection from back-end to proxy created |
| 205 | No back-end found for connection &1 |
| 206 | Server registered on back-end |
| 207 | Error on registering system as proxy |
| 208 | System is still connected to proxy &1 |
| 209 | Error on creating connection to back-end |
| 210 | Error on creating reverse connection from back-end |
| 211 | No RemoteSearch proxy registered for connection &1 |
| 212 | System has still back-ends connected |
| 213 | Error on unregistering system as proxy |
| 214 | Connect process terminated |
| 215 | Disconnecting back-end |
| 216 | Connection to back-end deleted |
| 217 | Reverse connection from backend to proxy deleted |
| 218 | System successfully registered as RemoteSearch back-end |
| 219 | Proxy unregistered on back-end |
| 220 | Backend unregistered on proxy |
| 221 | Error on discarding connection on proxy |
| 222 | Error on deleting connection to back-end |
| 223 | Error on deleting reverse connection from back-end |
| 224 | System successfully unregistered as RemoteSearch back-end |
| 225 | Error on registering system as back-end |
| 226 | Error on unregistering system as back-end |
| 227 | Disconnect process terminated |
| 228 | Relevant data imported from back-end |
| 229 | Error on importing relevant data from back-end |
| 230 | System successfully registered as RemoteSearch proxy |
| 231 | System successfully unregistered as RemoteSearch proxy |
| 232 | System is not a RemoteSearch proxy |
| 233 | System is not a RemoteSearch back-end |
| 234 | Relevant data of back-end removed |
| 235 | Error on removing relevant data from back-end |
| 236 | Connect process successfully completed |
| 237 | Disconnect process successfully completed |
| 238 | No RemoteSearch back-end for connection &1 |
| 239 | Prefix of data base connection (:DB: or :RFC:) wrong or missing |
| 240 | Data Base connection &1 unkown |
| 241 | Connection Error: &1 |
| 242 | Data Base is not a HANA |
| 243 | RFC connection error: &1 |
| 244 | Data Base connection &1 is valid |
| 245 | Connection to back-end exists already |
| 246 | Reverse connection from back-end to proxy created |
| 247 | Data base connection has to be indicated |
| 248 | &1 is not a valid RFC-connection for back-end systems |
| 249 | Save your changes first |
| 250 | Runtime data from back-end &1 was updated on local system |
| 251 | Delete all connectors before disconnecting a back-end system |
| 252 | HANA-version too old to support meta data import from views |
| 253 | HANA-version too old to support meta data import from InA-models |
| 254 | HANA-version too old; use at least SP08 |
| 255 | Import/ Discard views first |
| 256 | Personalized Search is NOT controled by RemoteSearch proxy |
| 257 | Personalized Search settings have been pushed to system &1(&2) |
| 258 | Error pushing Personalized Search settings to system &1(&2) |
| 259 | The personalization settings cannot be replicated to backend &1(&2) |
| 260 | Backend &1(&2) does not support personalization (release too low) |