SDDL_PARSER_MSG - Nachrichtenklasse f�r DDL Parser
The following messages are stored in message class SDDL_PARSER_MSG: Nachrichtenklasse f�r DDL Parser.
It is part of development package SDDIC_VIEWPARSER in software component BC-DWB-PAR. This development package consists of objects that can be grouped under "DDIC Viewparser".
It is part of development package SDDIC_VIEWPARSER in software component BC-DWB-PAR. This development package consists of objects that can be grouped under "DDIC Viewparser".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Syntax Errors |
| 001 | Syntax error (& was expected) |
| 002 | Obsolete: internal error in syntax check in C function & |
| 003 | The name & is too long; a maximum of & characters is allowed |
| 004 | The data source "&" does not exist or is not active |
| 005 | The name & is not unique |
| 006 | The name & is not unique; an alias needs to be assigned |
| 007 | Specification of selection list missing |
| 008 | Length of names list is not the same number as the selected fields |
| 009 | The annotation name & is used multiple times |
| 010 | The column & is unknown |
| 011 | Automatic client handling is not possible; see long text |
| 012 | Unexpected character & |
| 013 | The DDIC source code does not contain a valid definition |
| 014 | Only one definition allowed per DDIC source code |
| 015 | Unexpected word "&1" |
| 016 | Unexpected word & (the keyword & was expected) |
| 017 | The table name & is unknown or obscured by an alias |
| 018 | Number of fields in selection lists in unions must be the same |
| 019 | $$EXTENSION is not allowed within unions |
| 020 | Selection list must not consist solely of $$EXTENSION |
| 021 | Only field names are allowed in GROUP BY |
| 022 | obsolete: $$EXTENSION and GROUP BY are not valid together |
| 023 | Obsolete: this expression and GROUPB BY are not valid together |
| 024 | Column &1 is not contained in the GROUP BY list |
| 025 | Aggregate functions are not allowed in the WHERE condition |
| 026 | The function & is unknown |
| 027 | The HAVING condition can only contain columns from the GROUP BY list |
| 028 | Comparison value of LIKE condition must be a character-type literal |
| 029 | GROUP BY must not contain any LOB columns |
| 030 | UNION must not contain any LOB columns in the selection list |
| 031 | Conditions must not contain any LOB columns |
| 032 | $$EXTENSION and aggregate functions are not valid together |
| 033 | The GROUP BY clause is missing |
| 034 | Aggregate functions can only be compared with literal values |
| 035 | The column & requires a numeric comparison value |
| 036 | The column & requires a text literal as a comparison value |
| 037 | The & function requires a numeric comparison value |
| 038 | The & function can only be calculated for numeric columns |
| 039 | Automatic client handling is not possible; see long text |
| 040 | Select * and joins are not valid together |
| 041 | The length of the names list does not match the number of columns |
| 042 | Select * and GROUP BY are not valid together |
| 043 | An alias name must be assigned for literal values |
| 044 | The column & is not contained in the entity selection list |
| 045 | This element is not allowed in ON conditions in associations (class &) |
| 046 | This argument is not allowed in aggregate functions |
| 047 | An internal exception was raised ( & ) |
| 048 | Obsolete: DDIC inconsistent (Table &) |
| 049 | This element is not yet supported (&) |
| 050 | The component & does not exist or is not active |
| 051 | The association & cannot be translated to SQL |
| 052 | This path must end only with a field or a structure |
| 053 | Path expressions are not allowed here |
| 054 | Field "&1" must be included together with "&2" in the selection list |
| 055 | No filters or parameter bindings allowed in path element "&" |
| 056 | Path expressions in the From clause must contain associations only |
| 057 | "To many" associations (cardinality [n..*]) are not allowed here |
| 058 | An alias name must be assigned for the expression (& ...) |
| 059 | This expression is not contained in the GROUP BY list |
| 060 | The function & expects & parameters |
| 061 | The association & cannot be used locally in the view (see long text) |
| 062 | The serialized join condition of the association & is too long |
| 063 | It is not possible to expand path element & |
| 064 | The data type "&" is unknown or is not supported |
| 065 | Obsolete: This function is not supported in non-Unicode systems |
| 066 | Function or expression ("&1") not supported in this position |
| 067 | The cardinality of the association & must not be 0 |
| 068 | Cardinality lower limit must not be greater than the upper limit |
| 069 | Combination of UNION and associations is not yet supported |
| 070 | The namespace & is unknown |
| 071 | Namespace & expected |
| 072 | Name list cannot be used with Select * or $$EXTENSION |
| 073 | Filters cannot be used together with aggregate functions |
| 074 | The association & can modify the cardinality of the results set |
| 075 | Filters cannot be used together with GROUP BY |
| 076 | A parameter with the name & does not exist |
| 077 | Double quotation marks are not necessary for & |
| 078 | The name & does not conform with DDIC conventions |
| 079 | The parameter & is bound multiple times |
| 080 | Parameter & is not defined for entity & |
| 081 | The entity & requires parameter & |
| 082 | Number is outside valid value range |
| 083 | Parameters cannot be bound to associations |
| 084 | CASE expression without ELSE branch can lead to NULL values |
| 085 | The parameter & is not contained in the selection list of the entity |
| 086 | The parameter & is not used |
| 087 | Use of the association & can produce cyclical dependencies |
| 088 | The data type & does not allow a length to be specified |
| 089 | Namespace &1 is interpreted as namespace ABAP and must be corrected |
| 090 | Use of Union and Union All in one view is too unspecific |
| 091 | Union: client-specific and cross-client selections will be linked |
| 092 | Use of various paths with quantity values in aggregate functions |
| 093 | The annotation for suppressing messages has an incorrect structure |
| 094 | "VIEW", "TABLE FUNCTION", or "ABSTRACT" was expected instead of '&1' |
| 097 | Extension of a view extend is not possible |
| 098 | Extension of a table function is not possible |
| 099 | "Select *" cannot be used to add to the projection list |
| 100 | Extension of a view with UNION or UNION ALL is not possible |
| 101 | "VIEW", "TABLE FUNCTION", or "ABSTRACT" was expected instead of '&1' |
| 102 | The keyword "FUNCTION" was expected here |
| 103 | Either "WITH PARAMETERS" or "RETURNS" was expected here |
| 104 | The keyword "PARAMETERS" was expected here |
| 105 | A list of input parameters is expected after "WITH PARAMETERS" |
| 106 | ": <type name>" was expected instead of "&1" |
| 107 | "RETURNS" must be followed by a parameter list in '{}' |
| 108 | Return column has incorrect form or contains a reserved word |
| 109 | "IMPLEMENTED BY METHOD" was expected here |
| 110 | The method name must be specified in the form "<class>=><method>" |
| 111 | ABAP DDL source code can only be closed with ";" |
| 112 | The annotation "AbapCatalog" is not allowed in table functions |
| 113 | The annotation "Environment.SystemField #CLIENT" is not allowed here |
| 114 | The association & is not used |
| 115 | ( ) expected after the name of a table function |
| 116 | An empty parameter list is only allowed for table function |
| 117 | "TABLE FUNCTION" must be followed by the name of the table function |
| 118 | In view extends, no INNER JOIN must be used |
| 119 | The path expression "&" is not allowed in ON conditions |
| 120 | The path expression "&" is not allowed in filter conditions |
| 121 | The name & is obscured by an alias |
| 122 | The view & cannot be extended |
| 123 | Set operators must match in CDS view "&1" and extend "&2" |
| 124 | The selection list in view & cannot be extended |
| 125 | The GROUP BY list in view & cannot be extended |
| 126 | Union: Association "&1" is different between the selections (&2) |
| 127 | Association &2 is not required for selection of the element &1 |
| 128 | The view & contains a UNION and cannot be extended |
| 129 | PRESERVE TYPE can only be used with CAST on a data element |
| 130 | Inconsistent annotation for client handling |
| 131 | Automatic client handling not possible |
| 132 | Client handling generates a CROSS Join with Table T000 |
| 133 | Error in processing of pseudo comments (&) |
| 134 | "&" is an invalid parameter name or a reserved keyword |
| 135 | & |
| 136 | The INCLUDE & is not allowed in table entities |
| 137 | The element & cannot be used in the ON condition |
| 138 | Syntax error in "&" (one of the following elements was expected: &) |
| 139 | Syntax error in "&". The following element was expected: "&" |
| 140 | The column & is unknown |
| 141 | The component & does not exist or is not active |
| 142 | Invalid value "&1" for annotation "ClientDependent" |
| 143 | Old and new client annotations must not be combined |
| 144 | Invalid value "&1" for annotation "ClientHandling.Type" |
| 145 | "ClientHandling.Algorithm" is not allowed in table functions |
| 146 | Annotation "&1" is not allowed in table entities |
| 147 | Invalid value "&1" for annotation "&2" |
| 148 | The annotation "&1" does not exist |
| 149 | A type cannot be specified in function "&1" |
| 150 | Type must be specified after addition AS in function "&1" |
| 151 | The annotation NULL is not allowed within arrays |
| 152 | The annotation value NULL is only allowed within the selection list. |
| 153 | Optimization of Case expression and Join used is not possible. |
| 154 | Invalid value for annotation "&1" |
| 155 | Different case-join expressions |
| 156 | Annotation "@ClientHandling.type: #CLIENT_DEPENDENT" is required. |
| 157 | No annotation "@Environment.systemField: #CLIENT" for client parameter |
| 158 | Permitted values for "&1" are "#SESSION_VARIABLE" and "#NONE" |
| 160 | Permitted value "#NONE" for annotation "@ClientHandling.algorithm" |
| 161 | Syntax error: Space required between "&1" and "&2" |
| 162 | Client is missing in selection list (add "$$session.client as mandt") |
| 163 | Parameter "&" is not defined for view "&" |
| 164 | Parameter "&" is not defined for table "&" |
| 165 | Association on-condition for "&" not available in metadata; see long text |
| 166 | Association "&1" cannot be used in this place |
| 167 | Only the elements of &1 and &2 are allowed at this position |
| 168 | Use alias "&1", not entity name "&2" |
| 169 | Internal error (association with two path entries unexpected) |
| 170 | "$$projection" is not supported in abstract entities |
| 171 | Client field must be specified manually to avoid duplicates |
| 172 | Entity "&1" cannot be used as the data source |
| 173 | Association "&1" of entity "&2" cannot be used |
| 174 | Released association "&1" is not used (see long text) |
| 175 | Client field must be defined in the first position in the selection list |
| 176 | "ClientDependent" cannot be used in entities |
| 177 | "ClientHandling.type" cannot be used in entities |
| 178 | "ClientHandling.algorithm" cannot be used in entities |
| 179 | "AbapCatalog.internal.isMandt" cannot be used |
| 180 | Quoted identifiers are not allowed in abstract or custom entities |
| 181 | Association name "&1" cannot be the same as the target entity name |
| 182 | Post-annotations are not supported and must be replaced by preannotations |
| 183 | Use alias name "&1" instead of "&2" |
| 184 | Lower limit of cardinality must not be "*". |
| 185 | Join type information is lost for the exposed association |
| 186 | Parameters must not be used in the associations ON condition. |
| 187 | Use one of the alias names instead of "&2" |
| 188 | Table names not specified |
| 189 | "&1" is not a transparent table |
| 190 | The left side must contain a table column |
| 191 | Marker "&1" not defined |
| 192 | Only table names can be specified in the on clause |
| 193 | Table name "&1" is defined more than once in on clause |
| 194 | Table name "&1" is not defined in on clause |
| 195 | Table name "&1" is not used |
| 196 | Data source is not valid |
| 197 | Expression is not valid |
| 198 | select * is not allowed |
| 199 | "$$node.&1" is not allowed |
| 200 | "CHILD TO PARENT ASSOCIATION" clause is missing |
| 201 | "&1" is not a "child to parent" association. Target must be "&2". |
| 202 | On condition not set for association "&1" |
| 203 | Cannot parse on condition for association "&1" |
| 204 | Association "&1" On condition is not compatible for "child to parent" |
| 205 | "Is Initial" cannot be used in an association filter |
| 206 | Cardinality cannot be specified for association "&1" |
| 207 | Default filter cannot be specified for association "&1" |
| 208 | Parameter type "&1" is not specified |
| 209 | "ClientDependent" cannot be used in hierarchies |
| 210 | "ClientHandling.type" cannot be used in hierarchies |
| 211 | "ClientHandling.algorithm" cannot be used in hierarchies |
| 212 | Client field cannot be used in hierarchies |
| 213 | "MULTIPLE PARENTS" is not allowed in "TEMPORAL" hierarchy |
| 214 | Association "&1" cannot be specified in 'TEMPORAL' hierarchy |
| 215 | Entity "&1" contains column "&2" (not allowed within hierarchies) |
| 216 | Only literals or parameters are allowed for 'DEPTH' values |
| 217 | Only numeric values are allowed |
| 218 | "&1" already exists in 'SIBLINGS ORDER BY' clause |
| 219 | Expression cannot be used in 'SIBLINGS ORDER BY' clause |
| 220 | Object "&1" with type "&2" is not released as an API |
| 221 | Object "&1" with type "&2" does not exist in the system |
| 222 | Cardinality of association "&1" (&2) does not match "MULTIPLE PARENTS" |
| 223 | The parent entity "&1" requires a unique key |
| 224 | The child entity "&1" of a composition cannot be ROOT |
| 225 | A composition already exists for the child entity &1 |
| 226 | "OR" expression in "CHILD TO PARENT" association is not allowed |
| 227 | Key field &1 is missing in the ON condition of the composition definition |
| 228 | An entity cannot use itself as a child entity |
| 229 | "$$projection" is not supported in hierarchies |
| 230 | Only parameters and literals are allowed on the right side |
| 231 | Column &1 not defined in hierarchy directory association ON condition |
| 232 | Data source &1 is used in FROM clause or JOIN clause of the view |
| 233 | The composition "&1" must be included in the selection list |
| 234 | The composition "&1" cannot be published with an alias |
| 235 | The composition "&1" cannnot be published with attributes |
| 236 | Composition definitions are not allowed in extend views |
| 237 | The requested kernel version "&1" is not valid |
| 238 | Compositions are not allowed in CDS views with Union and Union All |
| 239 | The type of the child entity "&1" is not supported in compositions |
| 240 | Only "AND" joins allowed as ON condition of composition definition |
| 241 | Only "=" comparisons allowed in ON conditions of compositions |
| 242 | (unused) |
| 243 | "Is Initial" clause cannot be used for RAW fields |
| 244 | "*" is not allowed in root entities and parent entities |
| 245 | CDS view &1 uses non-supported client handling annotation &2 |
| 246 | "&1" is not a key field in the ON condition of a composition definition |
| 247 | Key field "&1" already used in ON condition of the composition definition |
| 248 | The specified path expression can be replaced by "&1.&2" |
| 249 | Invalid comparison in the ON condition of the composition definition |
| 250 | Literals are not valid in the ON condition of a composition definition |
| 251 | Field &1 already used in the ON condition of the composition definition |
| 252 | "&1" is not allowed as an alias |
| 253 | "depth" can only be used together with "orphans ignore" |
| 254 | "&2" must be specified instead of "&1"."&2" in the hierarchy selection |
| 255 | Element &1 must have type DATS, TIMESTAMP, or TIMESTAMPL |
| 256 | --- Not used --- |
| 257 | Two target fields cannot be compared in the composition definition |
| 258 | Child entity "&1" does not contain a key field |
| 259 | "*" not allowed in child entity "&1" |
| 260 | Internal error: Could not read DDL source for entity "&1" |
| 261 | Session variables are not allowed in composition definitions |
| 262 | Parameters are not allowed in composition definitions |
| 263 | Table name "&1" must be removed from this place |
| 264 | "Siblings Order By" expression is mandatory |
| 265 | Field "&1" is missing in "filter by" clause |
| 266 | Field "&1" can be specified only once in "filter by" clause |
| 267 | Association "&1" for custom entity "&2" cannot be used |
| 268 | The string "&1" is not supported |
| 269 | "'" must be followed by "'" |
| 270 | "&1" is not a valid string literal |
| 271 | "ORPHANS" cannot be combined with "GENERATE SPANTREE" |
| 272 | No more than one data source with hierarchy type allowed in FROM clauses |
| 273 | Parameter not allowed as key field |
| 274 | Parameters cannot be used in the default filter of the association |
| 275 | Keyword "root" is not allowed |
| 276 | Compare different columns in "child to parent" association on condition |
| 277 | Compare different data sources in "child to parent" association on cond. |
| 278 | Alias "&1" cannot be used for the non-client field |
| 279 | "&1" must be defined directly after the "&2" clause |
| 280 | "$$projection" is not allowed |
| 281 | "$$projection" not permitted in group by clause |
| 282 | "$$projection" not permitted in having clause |
| 283 | "CYCLES BREAKUP" only permitted with "MULTIPLE PARENTS" |
| 284 | "MULTIPLE PARENTS" cannot be combined with "GENERATE SPANTREE" |
| 285 | Only one "child to parent" association allowed |
| 286 | Type of super-entity "&1" not supported |
| 287 | "*" not allowed in super-entity "&1" |
| 288 | Super-entity "&1" does not contain a key field |
| 289 | WITH HIERARCHY cannot be combined with UNION/UNION ALL |
| 290 | WITH HIERARCHY cannot be combined with GROUP BY |
| 291 | WITH HIERARCHY requires a hierarchy-type data source in FROM clause |
| 292 | Alias "&1" must be used in WITH HIERARCHY clause |
| 293 | Child-to-parent association &1 is not allowed in extend views |
| 294 | The passed entity &1 does not have a composition definition for &2 |
| 295 | Only "=" comparison in ON condition allowed in to-parent association |
| 296 | Only "AND" join valid as ON condition in "to parent" association |
| 297 | Parameters not allowed in child-to-parent association |
| 298 | Key &1 already used in ON condition in to-parent association |
| 299 | Field &1 already used in ON condition in to-parent association |
| 300 | Cannot compare two source fields in to-parent association |
| 301 | WITH HIERARCHY cannot be combined with INNER JOIN |
| 302 | ON condition in to-parent association must contain a key field |
| 303 | Literals not allowed in ON condition of a to-parent association |
| 304 | Session variables are not allowed in child-to-parent associations |
| 305 | LEFT OUTER JOIN is not supported with WITH HIERARCHY clause |
| 306 | LEFT OUTER TO MANY JOIN is not supported with WITH HIERARCHY |
| 307 | RIGHT OUTER JOIN is not supported with WITH HIERARCHY clause |
| 308 | CROSS JOIN is not supported with WITH HIERARCHY clause |
| 309 | Algorithm &1 cannot be combined with the WITH HIERARCHY clause |
| 310 | The annotation @ClientDependent is not allowed |
| 311 | Hierarchy must be on the left |
| 312 | JOIN type cannot be specified |
| 313 | Only key fields from parent are allowed in to-parent associations |
| 314 | Key field &1 is missing in ON condition of to-parent association |
| 315 | The associations with cardinality TO MANY cannot be used |
| 316 | Cannot compare two target fields in to-parent associations |
| 317 | Association &1 must be included in the selection list |
| 318 | To-parent association &1 cannot be published with alias |
| 319 | To-parent association &1 cannot be published with attributes |
| 320 | To-parent association can be exposed once only |
| 321 | Path contains a hierarchy and cannot be used |
| 322 | Child entity &1 does not have a to-parent association with &2 |
| 323 | Only "AND" joins allowed in condition |
| 324 | Cardinality cannot be specified for to-parent associations |
| 325 | To-parent association entities must be different |
| 326 | CASE JOIN not supported with WITH HIERARCHY clause |
| 327 | The WHERE clause can cause inconsistencies in hierarchies |
| 328 | Same data type expected for period from "&1" and period to "&2" column |
| 329 | Only "&1" and "&2" are allowed as a column prefix in on condition |
| 330 | The annotation @ClientHandling.algorithm is missing |
| 331 | Only "&1" is allowed as a source column prefix in on condition |
| 332 | Only "&1" is allowed as a target column prefix in on condition |
| 333 | $$node is not allowed here |
| 334 | "$$node.&1" is invalid |
| 335 | The data type for parameter "&1" must have type DATS |
| 336 | The data type for parameter "&1" must have type TIMS |
| 337 | An alias name must be granted for "$$node.&1" |
| 338 | The parameter type "&1" must have type "abap.dats", "abap.tims" |
| 339 | On conditions are not allowed in compositions |
| 340 | "CYCLES" cannot be combined with "GENERATE SPANTREE" |
| 341 | Locally defined compositions cannot be used |
| 342 | "period from" and "period to" columns must be different |
| 343 | Root entity cannot define a to-parent association |
| 344 | Composition and to-parent association cannot reference same target |
| 345 | WITH HIERARCHY clause is not supported |
| 346 | Domain in ON condition of "to parent" association is not valid |
| 347 | Association "&1" cannot be exposed in "select *" case |
| 348 | "LOAD INCREMENTAL" expects "ORPHANS IGNORE" |
| 349 | DD08B-ON_SOURCE entry invalid; "&1"."&2" - index "&3" incorrect ("&4") |
| 350 | A hierarchy cannot be extended |
| 351 | Parameter value "INCREMENTAL" can produce a runtime crash in "&1" |
| 352 | Could not parse DDL source for entity "&1" (&2 &3 &4) |
| 353 | "ORPHANS" cannot be combined with temporal hierarchies |
| 354 | Temporal hierarchies cannot be combined with span tree hierarchies |
| 355 | Associations cannot be combined with SELECT * |
| 356 | Cannot track path (see long text) |
| 357 | Only "=" and "AND" allowed in directory association ON conditions |
| 358 | Domain values not allowed |
| 359 | Parameter expression not allowed |
| 360 | Session variable not allowed |
| 361 | "$$projection" is not supported in view cache definitions |
| 362 | Table name "&1" does not match data source "&2" |
| 363 | Literals not allowed in ON condition of directory association |
| 364 | Parameter "&1" is already used in the ON condition |
| 365 | Session variables not allowed in ON condition of directory association |
| 366 | Parameters not allowed in ON condition of directory association |
| 367 | Domain values not allowed in ON condition of directory association |
| 368 | Use "&1" as source column prefix for "&2" in ON of directory association |
| 369 | Use "&1" as target column prefix for "&2" in ON of directory association |
| 370 | No comparison of two source columns in directory association ON condition |
| 371 | No comparison of two target columns in directory association ON condition |
| 372 | No multiple use of source column &1 in directory association ON condition |
| 373 | No multiple use of target column &1 in directory association ON condition |
| 374 | Client field does not need to be specified in client-specific CDS view |
| 375 | Expressions cannot be used as parameters of aggregate functions |
| 376 | CAST expression cannot be used as a parameter of aggregate functions |
| 377 | Function expression "&1" cannot be used as aggregate function parameters |
| 378 | Client field in association ON condition (filter or default filter) |
| 379 | Algorithm for implicit client handling invalid |
| 380 | WITH DEFAULT FILTER not allowed in ON condition of directory association |
| 381 | Annotations are not supported |
| 382 | Alias is not supported |
| 383 | "&1" cannot be used in the definition "&2" |
| 384 | Projection views are not supported |
| 385 | Name lists are not supported in view entities |
| 386 | Session variables are not supported |
| 387 | Fixed domain values are not supported |
| 388 | Parameters are not supported |
| 389 | Target entity &1 cannot be the same as the original |
| 390 | Entity &1 must select from &2 |
| 391 | Extensions are not supported |
| 392 | Marker &1 cannot be used in this position |
| 393 | Quoted identifiers are not allowed in dynamic cache |
| 394 | Column &2 in target entity &1 must be a key field |
| 395 | Literals are not allowed in the dynamic cache selection list |
| 396 | Association "&1" does not have the property "To Parent" |
| 397 | Aggregate functions are not allowed in the SEGREGATE-BY clause |
| 398 | Column "&2" in target entity "&1" cannot be a key field |
| 399 | Target entity "&1" must be a projection view |
| 400 | ROOT keyword not valid since &1 is not a root property |
| 401 | ROOT keyword missing since &1 has the root property |
| 402 | Only CDS view entities or CDS DDIC-based views can be basis entities |
| 403 | Basis entity must have a ROOT property or a TO PARENT association |
| 404 | Association "&1" does not have the property "Composition" |
| 405 | To parent association in "&1" must point to target entity "&2" |
| 406 | Column &1 must be defined as a key field |
| 407 | Column "&1" cannot be defined as a key field |
| 408 | Only "=" and "AND" are allowed in SEGREGATE-BY clauses |
| 409 | Key field &1 missing in select list |
| 410 | VIRTUAL element "&1" cannot be used as a key field |
| 411 | Key field order must match basis view |
| 412 | Target entity "&1" cannot be used more than once |
| 413 | "REDIRECTED TO PARENT" keyword missing for "&1" |
| 414 | "REDIRECTED TO COMPOSITION CHILD" keyword missing for "&1" |
| 415 | Multiple to-parent associations cannot be specified |
| 416 | Projection view "&1" cannot be used as a data source |
| 417 | To-parent association "&1" cannot point to itself |
| 418 | Annotation "&1" is not allowed in view entities |
| 419 | Composition "&1" cannot point to itself |
| 420 | Extend on projection view not supported |
| 421 | Path expression not allowed in projection view |
| 422 | Keyword "key" not allowed |
| 423 | Functions are not allowed in the SEGREGATE-BY clause |
| 424 | CAST expressions are not allowed in the SEGREGATE-BY clause |
| 425 | Client field cannot be modeled |
| 426 | Virtual element name "&1" overlaps with the name of the basis entity |
| 427 | Client field not allowed in view entities |
| 428 | Annotations for client handling are not allowed |
| 429 | Redirect of associations with client not allowed in ON condition |
| 430 | The association "&" is unknown |
| 431 | Projection view &1 cannot be used as an association target |
| 432 | Internal error: AIEPP=TRUE without SEMANTIC=TRUE is not supported |
| 433 | "Is Initial" clause is not allowed for fields of type "&1" |
| 434 | CAST in CAST is not supported |
| 435 | Redirected target entity must be a CDS view entity |
| 436 | Association with client field in ON condition cannot be propagated |
| 437 | Alias "&1" is not allowed |
| 438 | --- free for use --- |
| 439 | Field with name &1 is not allowed; an alias must be granted |
| 440 | &1 is not allowed; choose another name for the virtual element |
| 441 | Virtual element not allowed in extends for non-projection view |
| 442 | "Redirected To" not allowed in extends for non-projection view |
| 443 | Keyword DISTINCT required for COUNT(DISTINCT &1) |
| 444 | Literal expressions not allowed in projection views |
| 445 | Arithmetic expressions not allowed in projection views |
| 446 | Case expressions not allowed in projection views |
| 447 | Domain values not allowed in view entities |
| 448 | Parameter expressions not allowed in projection views |
| 449 | Session variables not allowed in projection views |
| 450 | Functions not allowed in projection views |
| 451 | Double quotation marks are not allowed for "&" |
| 452 | Could not parse DDL source for entity "&1" |
| 453 | Statement is incomplete |
| 454 | "LOCALIZED" select list entry cannot finish with an association |
| 455 | "LOCALIZED" supported only in projection views and path expressions |
| 456 | Entity "&1" can contain only key fields with type "LANG" |
| 457 | Key field with type "LANG" does not exist in entity "&1" |
| 458 | Text association "&1" must be a "to many" association |
| 459 | Target of text association must be a CDS view or projection view |
| 460 | Key field "&1" missing in On condition of association "&2" |
| 461 | Field with type LANG cannot be specified in On condition of "&1" |
| 462 | Field "&1" in On condition of "&2" can only be used in "=" comparison |
| 463 | Multiple use of field "&1" not allowed in On condition of "&2" |
| 464 | JOIN type cannot be specified in projection views |
| 465 | Error in view cache API release check |
| 466 | Keyword ENTITY expected |
| 467 | "LOCALIZED" supported in projection views only |
| 468 | CDS view becomes client-specific view due to association tracking |
| 469 | Only "=" and "AND" allowed in the "&1" ON condition |
| 470 | Target fields "&1 and "&2" cannot be compared in "&3" ON condition |
| 471 | Syntax error: Keyword &1 not allowed |
| 472 | A path cannot end in an association in projection views |
| 473 | No alias can be specified for associations in projection views |
| 474 | No associations can be defined in projection views |
| 475 | UNION cannot be used in extends on projection views |
| 476 | "GROUP BY" cannot be used in projection views |
| 477 | "Redirected to" is not yet supported |
| 478 | Locally defined associations cannot propagate in projection views |
| 479 | The name "&" is unknown or obscured by an alias |
| 480 | Syntax "EXTEND VIEW ENTITY" permitted for view entities only |
| 481 | Element "&1" must have type "&2" |
| 482 | Stack code missing for association "&1" in entity "&2" (DDCDS_CONDITION) |
| 483 | Extension not supported for abstract entities or custom entities |
| 484 | Data source with parameters cannot be used in projection view |
| 485 | "&1" cannot be used in view entities |
| 486 | Selection list must be specified after FROM clause in view entities |
| 500 | Error "&1" in usage calculation for DDLS source "&2" |
| 501 | Syntax "&1" is supported in projection views only |
| 502 | Syntax "&1" can be used with "EXTEND VIEW ENTITY" only |
| 503 | Filters are not supported in exposed associations in projection views |
| 504 | All fields of type LANG are bound in On condition of "&1" |
| 505 | Local "&1" associations are not supported in projection views |
| 506 | Virtual fields are not allowed in on conditions of associations |
| 507 | "&1" is not allowed in local associations in projection views |
| 508 | Filters cannot raise the maximum cardinality in projection views |
| 509 | Prefix "&1" must be specified for an expression |
| 510 | Use expression "&1" instead of "&2" |
| 511 | "&1" is not supported in exposed associations with filter |
| 512 | Expression must be a full qualified expression |
| 513 | Expression "&1" cannot be used |
| 514 | "&1" requires a parameter binding; use the associated CDS entity |
| 515 | Association "&1" cannot be used in the on condition of "&2" |
| 516 | "$$projection" is allowed only for simple fields in the select list |
| 517 | The annotation "&1" is not allowed in table functions |
| 518 | Function "&1" cannot be used in arithmetic expressions |
| 519 | Redefinitions of a locally defined association are not supported |
| 520 | Lower limit of cardinality cannot be greater than 1 |
| 521 | Upper limit of cardinality must be 1 or "*" |
| 522 | Cardinality is not in the permitted range |
| 523 | Syntax "&1" is not supported in redefined associations |
| 524 | "&1" is not supported in redefined associations with filter |
| 525 | CACHE is not supported |
| 526 | $$projection expression cannot be reused |
| 527 | Cycle detected when resolving $$projection expression |
| 528 | Syntax error, "PROVIDER CONTRACT" is not supported |
| 529 | Column "&1" is unknown but can be reached using association "&2" |
| 530 | Cardinality for to-parent association cannot be changed |
| 531 | Association with max. cardinality not equal to 1 not permitted here |
| 532 | Unexpected keyword "&1" |
| 533 | Provider contract not modifiable if view contains "&1" associations |
| 534 | Parser call no longer supported. Specify the basis source too. |
| 535 | Expression "&1" is not supported |
| 536 | "Is Initial" clause for "&1" with type "&2" cannot be used |
| 537 | Cardinality not specified for "&1". 0..1 used as default. |
| 538 | "Typed Literals" not supported |
| 539 | "Typed Literals" not supported in annotations |
| 540 | Cannot determine initial value for type "&1" |
| 541 | Cannot determine initial value for expression "&1" |
| 542 | Syntax "&1" supported only from parser version &2 |
| 543 | "between" expression not supported in "having" clause |
| 544 | Syntax "EXTEND ABSTRACT ENTITY" does not match basic type |
| 545 | Syntax "EXTEND CUSTOM ENTITY" does not match basic type |
| 546 | Access to element in extend source "&1" not supported |
| 547 | Annotation "&1" not supported in abstract/custom entities |
| 548 | Parser call "extend first" not supported with semantic check |
| 549 | Entity "&1" can be enhanced using "&2" syntax only |
| 550 | Case join cannot be combined with a union |
| 551 | Case join annotation is only allowed in "searched case" expressions |
| 552 | Case join: &1 not supported in "when" clause; only "=" operations allowed |
| 553 | Case join: Only literals allowed on right of when clause |
| 554 | Case join: Only fields allowed on left of when clause |
| 555 | Path expression of then clause must be built as follows: _assoc.field |
| 556 | Path expressions of all "then" clauses must have same data source "&2" |
| 557 | Annotation "&1" is not allowed in hierarchies |
| 558 | Cannot expose association "&1" with projection "&2" as target |
| 559 | Error when reading from database |
| 560 | Required activation status is not available on the database |
| 561 | DDLS name exists in the database |
| 562 | "&1" is not a basis view |
| 563 | DDLS name does not exist in the database |
| 564 | Invalid parameter ddic_state: &1 |
| 565 | "Abstract Entity Extends" not supported |
| 566 | The C1 check is not supported for the DDLS type of &1 |
| 567 | This method is only supported for language version 2 |
| 574 | Error in C1 contract check |