SFSG_RP_MESSAGES - Nachrichtenklasse f�r FastSearch Repository
The following messages are stored in message class SFSG_RP_MESSAGES: Nachrichtenklasse f�r FastSearch Repository.
It is part of development package SFSG_RP in software component BC-SRV-FSI. This development package consists of objects that can be grouped under "Fast Search Repository".
It is part of development package SFSG_RP in software component BC-SRV-FSI. This development package consists of objects that can be grouped under "Fast Search Repository".
Message Nr ▲ | Message Text |
---|---|
000 | Authorization provider is not specified |
001 | Search definition & could not be found |
002 | View definition & could not be found |
003 | Extension definition & could not be found |
004 | Original definition & could not be found |
005 | Authorization structure is not specified |
006 | Authorization provider & could not be found |
007 | Definition with the name & already exists |
008 | Definition & could not be locked |
009 | & does not implement IF_GFS_AUTH_CONSTRAINT. |
010 | & cannot be instanced |
011 | Fallback provider & could not be found |
012 | Fallback provider & does not implement IF_GFS_QUERY_EXECUTION |
013 | Search definition & could not be found or is not active |
014 | Transport exception on saving the definition with name & |
015 | Runtime object & could not be found |
016 | Runtime object & could not be deleted |
017 | Lock exception on deletion of 'N' version of & |
018 | Query does not exist |
019 | Definition & could not be found |
020 | Search Definitions are not currently supported |
021 | No BO node view set |
022 | Input mapping incomplete: No view field assigned to &1 |
100 | Result definition: Line &: Element & does not exist in output structure |
101 | Selection condition: Line &: Function expressions are not supported |
102 | Result definition: Line &: Attribute & does not exist |
103 | Result definition: Line &: An operator must be specified |
104 | Input mapping: Line &: Type conflict between the attributes |
105 | Selection condition: Line &: Syntactically incorrect constant output |
106 | Selection condition: Closing parenthesis missing |
107 | Selection condition: Opening parenthesis missing |
108 | Selection condition: Line &1: AND or OR missing at end of line |
109 | Selection condition: Line &: IN calls for an element of entry structure |
110 | Result definition: Line &: No alias assigned to output |
111 | Result definition: Line &: No output assigned to alias |
112 | Result definition: Line &: Type conflict between the attributes |
113 | Input Mapping: Line &: Attribute & does not exist |
114 | A query can only contain one view as a data object |
115 | The data object that contains the query must be a view |
116 | No FSI retrieve method is defined for the business object node & |
117 | Selection condition: Line &: A comparison value must be set |
118 | Selection condition: Line &: Two comparison values must be set |
119 | Exactly one anchor table or data source must be defined |
120 | Only data sources of the same type can be used |
121 | Join conditions between &1 and &2 have different directions |
122 | Input mapping: Line &1: Attribute &2 does not exist in input structure |
123 | Input mapping: Line &1: Invalid format for input parameter |
124 | Input mapping: Line &1: &2 is not an element of the input structure |
125 | Input mapping: Line &1: No value was assigned to &2 |
126 | View &1 causes recursive usage |
127 | An invalid Join cycle has occurred |
128 | &1 |
129 | Incorrect join graph: Anchor is not set |
130 | Batch activation has been started: View &1 |
131 | Batch activation has ended: View &1 |
132 | You do not have authorization |
133 | Incorrect join graph: Different join types |
134 | Incorrect join graph: Join cycle is only permitted for inner join |
135 | Different join types occur within the view |
136 | Join between &1-&2 and &3-&4 causes outer-join cycle |