SAP ABAP Message Class ESH_BOS_INDEX_CTRL (ESH_BOS_INDEX_CTRL)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-EIM-ESH (Application Component) NetWeaver Enterprise Search
⤷ S_ESH_ENG_BOS_INDEX (Package) BOS Index
⤷ BC-EIM-ESH (Application Component) NetWeaver Enterprise Search
⤷ S_ESH_ENG_BOS_INDEX (Package) BOS Index
Attributes
Message class | ESH_BOS_INDEX_CTRL | |
Short Description | ||
Changed On | 20130531 | |
Last Changed At | 091206 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 001 | Application log created by the index controller for logical system &1 | The short text describes the object sufficiently | |
2 | 002 | Existence check for &1: Index found | The short text describes the object sufficiently | |
3 | 003 | Existence check for &1: Error number &2, description: &3 | The short text describes the object sufficiently | |
4 | 004 | Deletion of index &1: Index deleted | The short text describes the object sufficiently | |
5 | 005 | Deletion of index &1: Error number &2, description: &3 | The short text describes the object sufficiently | |
6 | 006 | Creation of index &1: Index created | The short text describes the object sufficiently | |
7 | 007 | Creation of index &1: Error number &2, description: &3 | The short text describes the object sufficiently | |
8 | 008 | Existence check of &1: Index not found | The short text describes the object sufficiently | |
9 | 009 | Entries not consistent: Node &1 and object type &2 | The short text describes the object sufficiently | |
10 | 010 | Starting extraction/indexing for object type &1 and node &2 | The short text describes the object sufficiently | |
11 | 011 | Starting process chain &1 | The short text describes the object sufficiently | |
12 | 012 | Could not start process chain &1 -> stop indexing | The short text describes the object sufficiently | |
13 | 013 | Process chain &1 completed successfully | The short text describes the object sufficiently | |
14 | 014 | Process chain &1 ended with error | The short text describes the object sufficiently | |
15 | 015 | Process chain &1 was terminated | The short text describes the object sufficiently | |
16 | 016 | Data extraction ended with error -> indexing aborted | The short text describes the object sufficiently | |
17 | 017 | No process chain found for &1 &2 | The short text describes the object sufficiently | |
18 | 018 | Starting preparation for object type &1 and node &2 | The short text describes the object sufficiently | |
19 | 019 | Could not create definition for index ID &1 | The short text describes the object sufficiently | |
20 | 020 | Iterator for index ID &1 is missing | The short text describes the object sufficiently | |
21 | 021 | Iterator for index ID &1 contains no data | The short text describes the object sufficiently | |
22 | 022 | &1 | The short text describes the object sufficiently | |
23 | 023 | Indexing of &1 has returned subrc &2, error code &3, and error text &4 | The short text describes the object sufficiently | |
24 | 024 | Optimization of &1 has returned subrc &2, error code &3, and err. text &4 | The short text describes the object sufficiently | |
25 | 025 | Optimization of &1 was successful | The short text describes the object sufficiently | |
26 | 026 | TREX destination has not been maintained | The short text describes the object sufficiently | |
27 | 027 | Search connector ID &1 (&2) is not valid | The short text describes the object sufficiently | |
28 | 028 | Generating process chain for data source &1 | The short text describes the object sufficiently | |
29 | 029 | Number of nodes to prepare: &1 | The short text describes the object sufficiently | |
30 | 030 | Logical system &1 is different to the one used by instance &2 | The short text describes the object sufficiently | |
31 | 031 | Business object &1 is different to the one used by instance &2 | The short text describes the object sufficiently | |
32 | 032 | Index ID is initial | The short text describes the object sufficiently | |
33 | 033 | Error while indexing &1; index ID &2 returns no results | Space: object requires documentation | |
34 | 034 | &1: Preparation is still running for some nodes | The short text describes the object sufficiently | |
35 | 035 | Schedule job &1 | The short text describes the object sufficiently | |
36 | 036 | Job &1 scheduled successfully | The short text describes the object sufficiently | |
37 | 037 | Exception at 'JOB_OPEN': &1 | The short text describes the object sufficiently | |
38 | 038 | Exception at 'JOB_INSERT': &1 | The short text describes the object sufficiently | |
39 | 039 | Exception at 'JOB_CLOSE': &1 | The short text describes the object sufficiently | |
40 | 040 | Extracting/indexing is still running for some nodes | The short text describes the object sufficiently | |
41 | 041 | No model instance received for model &1 | The short text describes the object sufficiently | |
42 | 042 | Number of nodes to index: &1 | The short text describes the object sufficiently | |
43 | 043 | An error occurred during indexing in TREX | The short text describes the object sufficiently | |
44 | 044 | Process chain &1 ended with status &2 | The short text describes the object sufficiently | |
45 | 045 | TREX comp. definition could not be determined for node &1 and index &2 | The short text describes the object sufficiently | |
46 | 046 | Error occurred during index creation in TREX | The short text describes the object sufficiently | |
47 | 047 | Error while creating the physical index &1 | The short text describes the object sufficiently | |
48 | 048 | Set node status to: &1 | The short text describes the object sufficiently | |
49 | 049 | Create join indices | The short text describes the object sufficiently | |
50 | 050 | No root node found for object type &1 | The short text describes the object sufficiently | |
51 | 051 | Error while decomposing index ID &1 | The short text describes the object sufficiently | |
52 | 052 | Invalid parameter while decomposing index ID &1 | The short text describes the object sufficiently | |
53 | 053 | Error while reading the index buffer | The short text describes the object sufficiently | |
54 | 054 | Error while creating the data structure for index ID &1 | The short text describes the object sufficiently | |
55 | 055 | No data to be indexed for authorization index ID &1 | The short text describes the object sufficiently | |
56 | 056 | Error while composing the index name for object type &1, node &2, type &3 | The short text describes the object sufficiently | |
57 | 057 | Error while filling the definition of object type &1, node &2, scope &3 | The short text describes the object sufficiently | |
58 | 058 | Logical system &1 or object type &2 is empty | The short text describes the object sufficiently | |
59 | 059 | Error while checking the existence of join index &1 on TREX &2 | The short text describes the object sufficiently | |
60 | 060 | Error while reading the model for the object type &1 | The short text describes the object sufficiently | |
61 | 061 | No instance of the object model was created | The short text describes the object sufficiently | |
62 | 062 | No instance of the data provider was created | The short text describes the object sufficiently | |
63 | 063 | No table entry found for data provider &1 and model &2 | The short text describes the object sufficiently | |
64 | 064 | Extraction technology: &1 | The short text describes the object sufficiently | |
65 | 065 | Data source type: &1 | The short text describes the object sufficiently | |
66 | 066 | Data source name: &1 | The short text describes the object sufficiently | |
67 | 067 | Cross client: &1 | The short text describes the object sufficiently | |
68 | 068 | Indexing ended with error | The short text describes the object sufficiently | |
69 | 069 | No data iterator was created for the node | The short text describes the object sufficiently | |
70 | 070 | Invalid parameter: ID &1, value &2 | The short text describes the object sufficiently | |
71 | 071 | User data is not indexed, yet. Index user data first | Space: object requires documentation | |
72 | 072 | Indexing of authorization indices ended with error | The short text describes the object sufficiently | |
73 | 073 | Indexing of logical indices ended with error | The short text describes the object sufficiently | |
74 | 074 | At least one physical index could not be indexed | The short text describes the object sufficiently | |
75 | 075 | Indexing of authorization indices and logical indices not possible | The short text describes the object sufficiently | |
76 | 076 | Found status: &1 | The short text describes the object sufficiently | |
77 | 077 | Wait and try again | The short text describes the object sufficiently | |
78 | 078 | No nodes found -> exit program | The short text describes the object sufficiently | |
79 | 079 | Indexing of complete objects from type &1 has returned &2 &3 | The short text describes the object sufficiently | |
80 | 080 | Reading of &1 has returned subrc &2, error code &3, and error text &4 | The short text describes the object sufficiently | |
81 | 081 | No connectivity instance received for connection GUID &1 | The short text describes the object sufficiently | |
82 | 082 | No requests found -> exit program | The short text describes the object sufficiently | |
83 | 083 | No fields found -> exit program | The short text describes the object sufficiently | |
84 | 084 | No fields found for node &1 | The short text describes the object sufficiently | |
85 | 085 | Error while creating the data structure for node &1 | The short text describes the object sufficiently | |
86 | 086 | No instance of the indexing controller was created | The short text describes the object sufficiently | |
87 | 087 | No instance of the object iterator was created | The short text describes the object sufficiently | |
88 | 088 | No instance of the object iterator by time was created | The short text describes the object sufficiently | |
89 | 089 | Provider error during creation of the object iterator | The short text describes the object sufficiently | |
90 | 090 | Unknown ID error during creation of the object iterator | The short text describes the object sufficiently | |
91 | 091 | Delta indexing not supported -> switch to full indexing | The short text describes the object sufficiently | |
92 | 092 | Provider error during execution of the NEXT method | The short text describes the object sufficiently | |
93 | 093 | Error while populating index &1 | The short text describes the object sufficiently | |
94 | 094 | Execute initial indexing | The short text describes the object sufficiently | |
95 | 095 | Execute periodic indexing | The short text describes the object sufficiently | |
96 | 096 | Error while optimizing index &1 | The short text describes the object sufficiently | |
97 | 097 | Provider error during creation of the object iterator time | The short text describes the object sufficiently | |
98 | 098 | The implementing class does not support the iterator by time interface | The short text describes the object sufficiently | |
99 | 099 | Multi-index call of index &1 has returned &2: &3 | The short text describes the object sufficiently | |
100 | 100 | Not supported error during creation of the object iterator | The short text describes the object sufficiently | |
101 | 101 | Implementation did not provide any data -> exit indexing | The short text describes the object sufficiently | |
102 | 102 | &1 objects extracted in &2 seconds | The short text describes the object sufficiently | |
103 | 103 | Indexing &1; error when searching dependent entries from &2 | The short text describes the object sufficiently | |
104 | 104 | Data of NW authorization objects could not be indexed | The short text describes the object sufficiently | |
105 | 105 | No instance of class CL_ESH_OM_AUTHNW was created | The short text describes the object sufficiently | |
106 | 106 | No authorization objects found -> exit indexing | The short text describes the object sufficiently | |
107 | 107 | No hash code generated for node &1, check &2, and authorization object &3 | The short text describes the object sufficiently | |
108 | 108 | Error when reading the authorization check &1 | The short text describes the object sufficiently | |
109 | 109 | Error when reading the index &1 | The short text describes the object sufficiently | |
110 | 110 | No language attribute filled for the information to be indexed in &1 | The short text describes the object sufficiently | |
111 | 111 | No instance of the indexing controller was created for object type &1 | The short text describes the object sufficiently | |
112 | 112 | Error reading the model for object type &1 and node &2 | The short text describes the object sufficiently | |
113 | 113 | Response attribute &1 refers to something inactive &2 &3 &4 | The short text describes the object sufficiently | |
114 | 114 | Request attribute &1 refers to something inactive &2 &3 &4 | The short text describes the object sufficiently | |
115 | 115 | Relation &1 between node &2 and node &3 has no attribute mapping | The short text describes the object sufficiently | |
116 | 116 | Error while checking the response attributes of object type &1 node &2 | The short text describes the object sufficiently | |
117 | 117 | Error while checking the request attributes of object &1 node &2 req. &3 | The short text describes the object sufficiently | |
118 | 118 | Authorization check &1 refers to something inactive &2 &3 &4 | The short text describes the object sufficiently | |
119 | 119 | Authorization check &1 refers to an inactive start object type &2 &3 | The short text describes the object sufficiently | |
120 | 120 | Authorization check &1 could not be read | The short text describes the object sufficiently | |
121 | 121 | Could not calculate path object type &1 node &2 to object type &3 node &4 | The short text describes the object sufficiently | |
122 | 122 | Could not find the node for object type &1 and check &2 | The short text describes the object sufficiently | |
123 | 123 | Indexing for object &1, logsys &2 already running. Process canceled | The short text describes the object sufficiently | |
124 | 124 | Technical error while requesting lock for indexing object &1 logsys &2 | The short text describes the object sufficiently | |
125 | 125 | Check if the generic extraction can be used for &1 | The short text describes the object sufficiently | |
126 | 126 | The generic extraction implementation cannot be used for &1 | The short text describes the object sufficiently | |
127 | 127 | Indexing of type &1 has no information for the root node | The short text describes the object sufficiently | |
128 | 128 | Use the generic extraction implementation for &1 | The short text describes the object sufficiently | |
129 | 129 | No implementation has been selected for object type &1 | The short text describes the object sufficiently | |
130 | 130 | TREX classification: Could not calculate path to node &1 | Space: object requires documentation | |
131 | 131 | TREX classification: Could not calculate path to node &1 | Space: object requires documentation | |
132 | 132 | Error while creating the property join index &1 on TREX &2 | The short text describes the object sufficiently | |
133 | 133 | Error while creating the extraction tables for object type &1 | The short text describes the object sufficiently | |
134 | 134 | No class instance was created to get the data by ID | The short text describes the object sufficiently | |
135 | 135 | Error in method CREATE_JOIN_CRT: ASSERT &1 | The short text describes the object sufficiently | |
136 | 136 | Error in method GET_INVOLVED_ATTRIBUTES: ASSERT &1 | The short text describes the object sufficiently | |
137 | 137 | Create attribute &1 in index &2: Error number &3, description: &4 | The short text describes the object sufficiently | |
138 | 138 | Delete attribute &1 in index &2: Error number &3, description: &4 | The short text describes the object sufficiently | |
139 | 139 | Change attribute &1 in index &2: Error number &3, description: &4 | The short text describes the object sufficiently | |
140 | 140 | Invalid search connector ID: &1 | The short text describes the object sufficiently | |
141 | 150 | Indexing of index &1 failed with dynamic call/illegal type exception | The short text describes the object sufficiently | |
142 | 151 | TREX call ended with return code &1, error message: &2&3&4 | The short text describes the object sufficiently |
History
Last changed on/by | 20130531 | SAP | |
SAP Release Created in | 100 |