SAP ABAP Message Class COM_SE_SEARCH (SES: End user messages -> Translate to maximum languages)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-TRX-SES (Application Component) TREX Search Engine Service
⤷ SES_ENDUSER_TEXT (Package) SES: End user UI elements -> Translate to maximum languages
⤷ BC-TRX-SES (Application Component) TREX Search Engine Service
⤷ SES_ENDUSER_TEXT (Package) SES: End user UI elements -> Translate to maximum languages
Attributes
Message class | COM_SE_SEARCH | |
Short Description | SES: End user messages -> Translate to maximum languages | |
Changed On | 20140121 | |
Last Changed At | 103714 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | &1 &2 &3 &4 | The short text describes the object sufficiently | |
2 | 001 | Entry &2 &3 &4 missing in table &1 | Space: object requires documentation | |
3 | 002 | Index ID &1 is not defined in table COM_SE_BUSOBJTY | The short text describes the object sufficiently | |
4 | 003 | RFC destination in table COM_SE_SEARCH is not defined | The short text describes the object sufficiently | |
5 | 004 | More than 100 objects were found | The short text describes the object sufficiently | |
6 | 005 | Error during dynamic call of method | Space: object requires documentation | |
7 | 006 | The search request was not clear enough | The short text describes the object sufficiently | |
8 | 007 | No objects found for this selection | The short text describes the object sufficiently | |
9 | 008 | No search engine support for partner relationships | The short text describes the object sufficiently | |
10 | 009 | No objects found during EXACT searches. A FUZZY search was performed | The short text describes the object sufficiently | |
11 | 010 | No objects found during EXACT searches. A LINGUISTIC search was performed | The short text describes the object sufficiently | |
12 | 011 | Class &2 does not recognize object type &1 | The short text describes the object sufficiently | |
13 | 012 | No active index was found for this selection | The short text describes the object sufficiently | |
14 | 013 | The business object &2 &3 is currently being indexed by user &1 | Space: object requires documentation | |
15 | 014 | Error during INSERT: Table &1, Key = &2 &3 &4 | The short text describes the object sufficiently | |
16 | 015 | Error During UPDATE: Table &1, Key = &2 &3 &4 | The short text describes the object sufficiently | |
17 | 016 | Error during MODIFY: Table &1, Key = &2 &3 &4 | The short text describes the object sufficiently | |
18 | 017 | Error during DELETE: Table &1, Key = &2 &3 &4 | The short text describes the object sufficiently | |
19 | 018 | Error during SELECT: Table &1, Key = &2 &3 &4 | The short text describes the object sufficiently | |
20 | 019 | Search Engine Error &1: &2 | The short text describes the object sufficiently | |
21 | 020 | Object ID conversion error: Type &1, ID = &2 | The short text describes the object sufficiently | |
22 | 021 | No search engine is connected | The short text describes the object sufficiently | |
23 | 022 | Select a line by clicking on it | The short text describes the object sufficiently | |
24 | 023 | No spool list exists for the selected line | Space: object requires documentation | |
25 | 024 | Flush queue triggered for business object &1 &2 | The short text describes the object sufficiently | |
26 | 025 | Indexing for business object &1 &2 started in the background | The short text describes the object sufficiently | |
27 | 026 | Business object &1: Object of related class &2 cannot be created | The short text describes the object sufficiently | |
28 | 027 | Indexes created: &1, Indexes activated: &2 | The short text describes the object sufficiently | |
29 | 028 | The index for business object &1 &2 has been deactivated | The short text describes the object sufficiently | |
30 | 029 | The index for business object &1 &2 is not active | The short text describes the object sufficiently | |
31 | 030 | The index for business object &1 &2 has been deleted | The short text describes the object sufficiently | |
32 | 031 | Importing parameter &1 may not be initial | The short text describes the object sufficiently | |
33 | 032 | Importing parameter &1 has invalid value &2 | The short text describes the object sufficiently | |
34 | 033 | Currently all object changes have been transferred to the search engine | The short text describes the object sufficiently | |
35 | 034 | Currently you not need to trigger a flush to process any of the queues | Space: object requires documentation | |
36 | 035 | Processing triggered for &1 queues | The short text describes the object sufficiently | |
37 | 036 | Use each language only once in the supplementation language sequence | The short text describes the object sufficiently | |
38 | 037 | Exception triggered without error message assignment | Space: object requires documentation | |
39 | 038 | Object class &1: Instance of type IF_COM_SE_BUSOBJ cannot be created | The short text describes the object sufficiently | |
40 | 039 | Check the Customizing for business objects | Space: object requires documentation | |
41 | 040 | &1 objects were indexed | The short text describes the object sufficiently | |
42 | 041 | An error occured for the business object &1 &2 | Space: object requires documentation | |
43 | 042 | Syntax error in Query: location = &1 | The short text describes the object sufficiently | |
44 | 043 | The requested business object type has not yet been customized | The short text describes the object sufficiently | |
45 | 044 | The required index has not been created yet in the search engine | Space: object requires documentation | |
46 | 045 | Syntax error in list of requested attributes: location = &1 | The short text describes the object sufficiently | |
47 | 046 | The relation index for business object &1 &2 has been deactivated | The short text describes the object sufficiently | |
48 | 047 | The relation index for business object &1 &2 has been deleted | The short text describes the object sufficiently | |
49 | 048 | Relation indexing for business object &1 &2 started in the background | The short text describes the object sufficiently | |
50 | 049 | Business object &1 class &2: create relation interface failed | The short text describes the object sufficiently | |
51 | 050 | Business object &1 does not support relations | Space: object requires documentation | |
52 | 051 | The selected business object does not support relations | The short text describes the object sufficiently | |
53 | 052 | Build TREX attribute name failed for index id &1, attr name &2 | The short text describes the object sufficiently | |
54 | 053 | The requested SELECT-OPTION &1 is not supported | The short text describes the object sufficiently | |
55 | 054 | Internal error: Unexpected rowtype &1 in search engine query | The short text describes the object sufficiently | |
56 | 055 | The use of wildcards (*, +) disables fuzzy mode | The short text describes the object sufficiently | |
57 | 056 | There might be more entries. Please restrict your selection further | The short text describes the object sufficiently | |
58 | 057 | The entries were only found due to a fuzzy search | The short text describes the object sufficiently | |
59 | 058 | Syntax error in list of sort attributes: location = &1 | The short text describes the object sufficiently | |
60 | 059 | Error concatenating object type key: busobj = &1, object_type = &2 | The short text describes the object sufficiently | |
61 | 060 | Mapping of result attribute failed: attr_name = &1 | The short text describes the object sufficiently | |
62 | 061 | Search by relation and freestyle search cannot be combined. | The short text describes the object sufficiently | |
63 | 062 | Delete index "&1" -> TREX message: "&2"; TREX return code: "&3" | The short text describes the object sufficiently | |
64 | 063 | Deactivate index in COM_SE_BUSOBJT -> return code: "&1" for index: "&2" | The short text describes the object sufficiently | |
65 | 064 | Delete index line in COM_SE_STATUS -> return code: "&1" for index: "&2" | The short text describes the object sufficiently | |
66 | 065 | Create object index "&1" -> TREX message: "&2"; TREX return code: "&3" | The short text describes the object sufficiently | |
67 | 066 | Create relation index "&1" -> TREX message: "&2"; TREX return code: "&3" | The short text describes the object sufficiently | |
68 | 067 | Create compound index "&1" -> TREX message: "&2"; TREX return code: "&3" | The short text describes the object sufficiently | |
69 | 068 | Update index in COM_SE_BUSOBJTY -> return code: "&1" for index: &2 | The short text describes the object sufficiently | |
70 | 069 | Insert index line in COM_SE_STATUS -> return code: "&1" for index: "&2" | The short text describes the object sufficiently | |
71 | 070 | Set new RFC Destination: "&1". The old one was "&2" | The short text describes the object sufficiently | |
72 | 071 | Error indexing object id = &1, attribute name = &2, value = &3 | The short text describes the object sufficiently | |
73 | 072 | The Business Object &1 &2 is enabled for Embedded Search | Space: object requires documentation | |
74 | 073 | Search Engine Service does not run on SAP HANA | The short text describes the object sufficiently | |
75 | 074 | Destination "&1" does not exist or does not have connection type "T" | The short text describes the object sufficiently | |
76 | 075 | SES does not support this function for Business Object &1 (see longtext) | Space: object requires documentation | |
77 | 076 | SES does not support this function for Business Objects (see longtext) | Space: object requires documentation | |
78 | 090 | Query part not available for each query entry | The short text describes the object sufficiently | |
79 | 091 | Query part not available for requested attribute "&1" | The short text describes the object sufficiently | |
80 | 100 | &1 &2&3&4 | The short text describes the object sufficiently | |
81 | 101 | Inconsistency in value assistant | The short text describes the object sufficiently |
History
Last changed on/by | 20140121 | SAP | |
SAP Release Created in | 300 |