SAP ABAP Message Class ESH_EX (Extraction)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-EIM-ESH (Application Component) NetWeaver Enterprise Search
⤷ S_ESH_ENG_EXTRACTION (Package) Extraction
⤷ BC-EIM-ESH (Application Component) NetWeaver Enterprise Search
⤷ S_ESH_ENG_EXTRACTION (Package) Extraction
Attributes
Message class | ESH_EX | |
Short Description | Extraction | |
Changed On | 20130531 | |
Last Changed At | 115943 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | Error opening real-time indexing job | The short text describes the object sufficiently | |
2 | 001 | Error submitting real-time indexing job | The short text describes the object sufficiently | |
3 | 002 | Error closing real-time indexing job | The short text describes the object sufficiently | |
4 | 003 | Error deleting real-time indexing job | The short text describes the object sufficiently | |
5 | 004 | Error aborting real-time indexing job | The short text describes the object sufficiently | |
6 | 005 | RFC communication failure: | The short text describes the object sufficiently | |
7 | 006 | RFC system failure: | The short text describes the object sufficiently | |
8 | 007 | Insufficient authorization for real-time indexing | The short text describes the object sufficiently | |
9 | 008 | Technical error during real-time indexing | The short text describes the object sufficiently | |
10 | 009 | Data extractor daemon could not be scheduled | The short text describes the object sufficiently | |
11 | 010 | Attempt to start daemon while running; second instance terminated | The short text describes the object sufficiently | |
12 | 011 | Technical error with enqueue server; daemon process could not be locked | The short text describes the object sufficiently | |
13 | 012 | RFC system failure calling hub destination: &1&2&3&4 | The short text describes the object sufficiently | |
14 | 013 | RFC communication failure calling hub destination: &1&2&3&4 | The short text describes the object sufficiently | |
15 | 014 | Logical system/connection GUID for &1 client &2 not defined on hub | The short text describes the object sufficiently | |
16 | 015 | Destination &1 does not connect to Enterprise Search Hub | The short text describes the object sufficiently | |
17 | 016 | RFC ping: RFC communication failure during back connection from hub | The short text describes the object sufficiently | |
18 | 017 | RFC ping: RFC system failure during back connection from hub | The short text describes the object sufficiently | |
19 | 018 | Technical error on test connection | The short text describes the object sufficiently | |
20 | 019 | Real-time indexing is not supported at destination &1 | The short text describes the object sufficiently | |
21 | 020 | Enter a date in the parameter "Deletion-To Date" | The short text describes the object sufficiently | |
22 | 021 | Real-time indexing daemon is starting; refresh your screen | The short text describes the object sufficiently | |
23 | 022 | Real-time indexing daemon is auto-restarting; refresh your screen | The short text describes the object sufficiently | |
24 | 023 | Real-time indexing daemon is running | The short text describes the object sufficiently | |
25 | 024 | Real-time indexing daemon is not running | The short text describes the object sufficiently | |
26 | 025 | Real-time indexing daemon process has terminated unexpectedly | Space: object requires documentation | |
27 | 026 | Daemon is stopping; process will be set to hold after current execution | The short text describes the object sufficiently | |
28 | 027 | Real-time indexing daemon is on hold | The short text describes the object sufficiently | |
29 | 028 | Real-time indexing daemon is stopping; idle time has been exceeded | The short text describes the object sufficiently | |
30 | 029 | Idle time has been exceeded; daemon will be auto-restarted on request | The short text describes the object sufficiently | |
31 | 030 | Real-time indexing daemon is stopping with technical errors: &1 &2 &3 &4 | The short text describes the object sufficiently | |
32 | 031 | Real-time indexing daemon has failed with technical errors: &1 &2 &3 &4 | The short text describes the object sufficiently | |
33 | 032 | Current status: &1&2&3&4 | The short text describes the object sufficiently | |
34 | 033 | Real-time indexing daemon manually started in debug mode | The short text describes the object sufficiently | |
35 | 034 | Real-time indexing daemon manually started in single execution mode | The short text describes the object sufficiently | |
36 | 035 | Hub is currently locked for updates, e.g. because backup is running | The short text describes the object sufficiently | |
37 | 036 | No objects registered for real-time indexing | The short text describes the object sufficiently | |
38 | 037 | Daemon scheduled for restart after temporary error: &1 &2 &3 &4 | The short text describes the object sufficiently | |
39 | 038 | &1: Daemon auto-restarted | The short text describes the object sufficiently | |
40 | 039 | &1: Daemon auto-restarted from status 'Temporarily Stopped' | The short text describes the object sufficiently | |
41 | 040 | &1: Daemon restarted from status 'On Hold' | The short text describes the object sufficiently | |
42 | 041 | &1: Daemon restarted from status 'Failed' | The short text describes the object sufficiently | |
43 | 042 | &1: Daemon restarted after temporary error | The short text describes the object sufficiently | |
44 | 043 | &1: Daemon manually started in debug mode | The short text describes the object sufficiently | |
45 | 044 | &1: Daemon manually started in single execution mode | The short text describes the object sufficiently | |
46 | 045 | &1: Daemon started | The short text describes the object sufficiently | |
47 | 046 | Daemon has been set to 'On Hold' by user &1 | The short text describes the object sufficiently | |
48 | 047 | Stopping with exception: &1 | The short text describes the object sufficiently | |
49 | 048 | Processing successfully completed; status has been reset | The short text describes the object sufficiently | |
50 | 049 | Last real-time indexing processsed at &1 | The short text describes the object sufficiently | |
51 | 050 | Migratn to new change-pointer handling unsuccessful (real-time indexing) | Space: object requires documentation | |
52 | 051 | Real-time indexing (migration to new change-pointer handling) | Space: object requires documentation | |
53 | 052 | Could not schedule next daemon execution | The short text describes the object sufficiently | |
54 | 053 | Daemon has been rescheduled for immediate execution | The short text describes the object sufficiently | |
55 | 054 | Daemon has been rescheduled for restart in 5 minutes | The short text describes the object sufficiently | |
56 | 055 | Change pointer migration: Successfully migrated: &1, already present: &2 | The short text describes the object sufficiently | |
57 | 056 | Change pointer migration: Could not migrate change pointer data | The short text describes the object sufficiently | |
58 | 057 | Could not schedule change pointer reorganization | The short text describes the object sufficiently | |
59 | 058 | User &1 does not exist | The short text describes the object sufficiently | |
60 | 059 | User &1 does already exist | The short text describes the object sufficiently | |
61 | 060 | Could not generate extraction user: &1 &2 &3 &4 | The short text describes the object sufficiently | |
62 | 061 | SAP default extraction roles cannot be modified on customer system | The short text describes the object sufficiently | |
63 | 062 | Custom extraction roles cannot be maintained on SAP system | The short text describes the object sufficiently | |
64 | 063 | Referenced default role with reference key &1 does not exist | The short text describes the object sufficiently | |
65 | 064 | Selected extraction role &1 does not exist | The short text describes the object sufficiently | |
66 | 065 | Enter a custom extraction role - Possibilities: &1 &2 &3 | The short text describes the object sufficiently | |
67 | 066 | Selected software component &1 does not exist | The short text describes the object sufficiently | |
68 | 067 | Selected object &1 does not exist in software component &2 | The short text describes the object sufficiently | |
69 | 068 | &1 "&2" differs in model &3 and in connector metadata - update &4 | The short text describes the object sufficiently | |
70 | 069 | Cannot determine metadata for object type &1 | The short text describes the object sufficiently | |
71 | 070 | Application has raised exception while extracting data for object type &1 | The short text describes the object sufficiently | |
72 | 071 | Technical error during extract of data for object type &1 | The short text describes the object sufficiently | |
73 | 072 | Instances of object type &1 have been set to status 'Failed' | The short text describes the object sufficiently | |
74 | 073 | Open SQL error when trying to update change pointers for &1. Skip object | The short text describes the object sufficiently | |
75 | 074 | Source system, source client not provided on RFC communication | The short text describes the object sufficiently | |
76 | 075 | Schedule indexing request can only be delegated to enterprise search hub | The short text describes the object sufficiently | |
77 | 076 | Schedule indexing request delegated from back end with unknown connection | The short text describes the object sufficiently | |
78 | 077 | Object &1 (SWC &2) has been registered for real-time indexing | The short text describes the object sufficiently | |
79 | 078 | Object &1 (SWC &2) has been deregistered from real-time indexing | The short text describes the object sufficiently | |
80 | 079 | Object &1 (SWC &2): Real-time indexing registration has been updated | The short text describes the object sufficiently | |
81 | 080 | Real-time indexing job could not automatically be restarted | The short text describes the object sufficiently | |
82 | 081 | Could not register/deregister &1 (SWV &2) for real-time indexing: &3 &4 | The short text describes the object sufficiently | |
83 | 082 | Could not register object &1 (SWV &2) for real-time indexing: &3 &4 | The short text describes the object sufficiently | |
84 | 083 | Could not call registration handler &3 on registration of &1 (SWC &2) | The short text describes the object sufficiently | |
85 | 084 | Could not call deregistration handler &3 on deregistration of &1 (SWC &2) | The short text describes the object sufficiently | |
86 | 085 | Open SQL error when trying to update next transaction pointer for &1 | The short text describes the object sufficiently | |
87 | 086 | Manual real-time indexing session (&1, &2) has been terminated before &3 | The short text describes the object sufficiently | |
88 | 087 | Customized extraction packagesize cannot be read from backend system | The short text describes the object sufficiently | |
89 | 088 | Customized extraction packagesize cannot be read: Unknown logical system | The short text describes the object sufficiently | |
90 | 089 | SQL error on update of unprocessed changepointers after initial load | The short text describes the object sufficiently | |
91 | 090 | &1 unprocessed changepointers updated to status &2 after initial load | The short text describes the object sufficiently | |
92 | 091 | Not all changepointers could be cleaned up prior to initial load | The short text describes the object sufficiently | |
93 | 092 | Changepointer cleanup prior to initial load successfully completed (&1) | The short text describes the object sufficiently | |
94 | 100 | Indexing is currently suspended -> exit indexing | The short text describes the object sufficiently | |
95 | 101 | Indexing has been suspended globally | The short text describes the object sufficiently |
History
Last changed on/by | 20130531 | SAP | |
SAP Release Created in | 720 |