RSO_SEGR - Messages for TLOGO = SEGR (Semantic Group of ADSOs)
The following messages are stored in message class RSO_SEGR: Messages for TLOGO = SEGR (Semantic Group of ADSOs).
It is part of development package RSO_RES_SEGR in software component BW-WHM-MTD. This development package consists of objects that can be grouped under "Semantic Group (of ADSOs)".
It is part of development package RSO_RES_SEGR in software component BW-WHM-MTD. This development package consists of objects that can be grouped under "Semantic Group (of ADSOs)".
Message Nr ▲ | Message Text |
---|---|
000 | &1 &2 &3 &4 |
001 | Semantic Group '&1' does not exist |
002 | Semantic Group '&1' already exists |
003 | Version '&2' of Semantic Group '&1' does not exist or cannot be loaded |
004 | Version '&2' of Semantic Group '&1' does not exist in database |
005 | Enter a name for the Semantic Group |
006 | Wrong version '&1' found. Version '&2' was expected. |
007 | Semantic Groups are only supported on SAP Hana: &1 |
008 | Illegal object version: &1 |
009 | M and A version of Semantic Group '&1' are different |
010 | Save Semantic Group '&1' |
011 | Semantic Group '&1' saved |
012 | M and A Version of Semantic Group '&1' identical |
020 | Check Semantic Group '&1' |
021 | Semantic Group '&1' checked |
022 | Error while checking Semantic Group '&1' |
023 | The name of the semantic group is not valid |
030 | Generation of semantic group '&1' started |
031 | Semantic group '&1' has been generated |
032 | Error while generating semantic group '&1' |
033 | Cannot generate: Semantic Group '&1' has not been checked |
034 | Semantic Group '&1' needs to be generated; 'M' version exists |
035 | Semantic Group '&1' has already been generated |
036 | Sem. Group '&1': DB-partitioning could not be adapted for member '&2' |
037 | Semantic group '&1': DB partition criteria on '&2' cannot be transferred |
038 | System is not changeable. Semantic group '&1' cannot be created. |
040 | Deleting semantic group '&1' |
041 | Semantic group '&1' deleted |
042 | Error while deleting semantic group '&1' |
043 | Cannot delete: Semantic group '&1' is still being used |
050 | Semantic Group '&1' is not locked |
051 | Semantic Group '&1' could not be locked |
052 | Semantic Group '&1' is locked by another user |
053 | Semantic Group '&1': lock handle failure |
060 | Reset Semantic Group '&1' to the active version |
061 | Semantic Group '&1' reset to active version |
062 | Error while resetting Semantic Group '&1' to active version |
070 | You are not authorized to display Semantic Group '&1' |
071 | You are not authorized to change Semantic Group '&1' |
090 | Error while changing the database tables (table &1) |
110 | Error while building the DTA structure of provider &1 |
111 | Error while building the DTA_PRO structure of field &2 of provider &1 |
112 | Metadata of InfoObject &2 of provider &1 not found |
114 | Error '&2' during metadata operation in function '&1' |
115 | Metadata inconsistency in method '&1'. Location: '&2' |
120 | Invalid URI format. Unable to retrieve name of Semantic Group. |
121 | Error in deserialization for Semantic Group '&1' |
122 | Error in serialization for Semantic Group '&1' |
150 | Member '&1' has been created and added to semantic group |
151 | Member '&1' has been added to semantic group |
152 | Member '&1' has been updated |
153 | Member '&1' has been removed from semantic group |
154 | CompositeProvider '&1' has been created for semantic group |
155 | CompositeProvider '&1' has been updated |
156 | CompositeProvider '&1' has been removed from semantic group |
157 | Member '&1' could not be added/updated because remodelling is required |
158 | Error during the creation/update of member &1 |
159 | Error during operation on CompositeProvider &1 |
200 | Sem. Group '&1' is consistent |
201 | Sem. Group '&1' is not consistent |
202 | Name of semantic group is not specified in header |
203 | Name of template DataStore object is not specified |
204 | Metadata for template &1 not found |
205 | '&1' has invalid TLOGO type '&2' (expected '&3') |
206 | No InfoArea specified |
207 | No CompositeProvider specified |
208 | Inconsistent name in header: '&1' |
209 | Inconsistent name in range table: '&1' |
210 | Inconsistent objvers in header: '&2' (expected '&1') |
211 | Inconsistent objvers in range table: '&2' (expected '&1') |
212 | No ranges specified |
213 | Error &1 when reading metadata for template '&2' |
214 | Name of semantic group not specified in range table |
215 | Name of DataStore object not specified in range table |
216 | Name of data slice object not specified in range table |
217 | Specified object '&1' is not part of the template '&2' |
218 | Invalid 'option' '&1' in range |
219 | Lower bound ('&1') is larger than upper bound ('&2') |
220 | Restrictions on different objects are not allowed |
221 | Overlap on the restrictions of '&1' and '&2' |
222 | Upper bound ('&1') is specified for EQUAL condition |
223 | DataStore object '&1' belongs to group but no field specified |
224 | There are DataStore objects with different fields in the same group |
225 | DataStore object '&1' will be removed from group |
226 | Existing DataStore object '&1' will be added |
227 | DataStore object '&1' will be created and added to group |
228 | DataStore object '&1' already belongs to another group '&2' |
229 | No ranges defined for member '&1' |
230 | Data slice object '&1' is not part of DataStore object '&2' |
231 | Criteria [&2] will be added to member '&1' |
232 | Criteria [&2] will be removed from member '&1' |
233 | aDSO '&1' belongs already to group |
234 | Lower bound ('&1') equals upper bound. Please use option 'EQUAL'. |
235 | No members specified |
236 | Name of semantic group not specified in member table |
237 | Inconsistent name in member table: '&1' |
238 | Inconsistent objvers in member table: '&2' (expected '&1') |
239 | Name of DataStore object is not specified in member table |
240 | Illegal value '&1' for field '&2' |
241 | DataStore object '&1' already exists |
242 | Member '&1' does not exist anymore and will be removed during generation |
243 | Structure of DataStore object '&1' will be overwritten |
244 | New CompositeProvider '&1' will be created |
245 | CompositeProvider '&1' will no longer be assigned to group |
246 | CompositeProvider '&1' already exists |
247 | No object specified for data slice |
248 | Fields &1.&2 and &3.&4 have different types but have the same name |
249 | Field &1.&2 and InfoObject &3.&4 have the same name |
250 | CompositeProvider '&1' does not exist |
251 | CompositeProvider specified even though 'unset' flag is set |
252 | Only CompositeProviders without joins can be used in a semantic group |
253 | CompositeProvider '&1' will be updated because of added/removed members |
254 | Remodelling of DataStore object '&1' is pending. Please execute first. |
255 | CompositeProvider '&1' (M version) will be overwritten |
256 | Name of element is not specified |
257 | Reference object can only be changed if CHANGE flag is set |
258 | Could not convert '&2' of field '&1' from external to internal format |
259 | Could not convert '&2' of field '&1' from internal to external format |
260 | CompositeProvider '&1' will be updated due to added/removed elements |
261 | aDSO '&1' will not be part of the group metadata anymore |
262 | Specified object '&1' is not part of the aDSO '&2' |
263 | |
264 | Name '&1' is used for two different members |
265 | Name '&1' is used for CompositeProvide and member |
266 | Name of semantic group ('&1') contains illegal character: '/' |
267 | Type of reference element '&1' has changed in template &2 |
269 | CompositeProvider specified although no members exist after generation |
270 |