DDLS - F�r Ddl Source Behandlung
The following messages are stored in message class DDLS: F�r Ddl Source Behandlung.
It is part of development package SDDL in software component BC-DWB-DIC. This development package consists of objects that can be grouped under "DDL-Specific Dictionary Functions".
It is part of development package SDDL in software component BC-DWB-DIC. This development package consists of objects that can be grouped under "DDL-Specific Dictionary Functions".
Message Nr ▲ | Message Text |
|---|---|
| 000 | ===================== Base Messages for DDLs ============================ |
| 001 | Invalid input value: &1 = &2 |
| 002 | & |
| 003 | (&) |
| 004 | Internal error (&) occurred |
| 005 | This DDLS type is still in development |
| 006 | Object type & is not allowed in this system |
| 008 | DDLS type switch is still being developed |
| 020 | ===================== Read/Write/Activate/Delete ======================== |
| 021 | DDL source & could not be read |
| 022 | View & could not be saved |
| 023 | View entity & could not be saved |
| 024 | Internal error while activating view & |
| 025 | DDL source & was activated |
| 026 | DDL source & was activated with warning messages |
| 027 | DDL source & could not be activated |
| 028 | Name of view entity not in DDL source &: DEFINE VIEW <View entityname> |
| 029 | Name of SQL view missing; annotation & must be specified |
| 030 | Activate DDL source & |
| 031 | Activate DDL source & (active version) |
| 032 | Error while writing usages (duplicate entries for &) |
| 033 | Sources for DDL view & in & version could not be read |
| 034 | SQL view name was changed from & to & |
| 035 | Extended DDL source & must be adapted |
| 036 | Entity name was changed from & to & |
| 037 | Old SQL view & will be deleted |
| 038 | Old DDL View & will be deleted |
| 039 | DDL source & could not be deleted |
| 040 | TADIR entry for & & (package &) not written |
| 041 | Activating dependent DDL source & (active version) |
| 042 | Old view & will not be deleted because it is not generated |
| 043 | No DDL views to be generated found |
| 044 | & DDL views from altogether & DDL sources processed |
| 045 | & DDL views created |
| 046 | & DDL views with warnings have been generated |
| 047 | & DDL views could not be generated |
| 048 | Activation of DDL sources - see log & |
| 049 | Could not enter dependent DDL & - SQL object and entity (&) |
| 050 | Syntax error in &: DDL source could not be saved |
| 051 | &: Either DDL source or get_state must be specified |
| 052 | Name of SQL View Append missing; annotation & must be specified |
| 053 | Error while reading table & |
| 054 | Error while writing table & |
| 055 | Problem while reading TADIR entry for & & (RC = &) |
| 056 | Problem while determining AccessControl.target information for & |
| 057 | & is a DDL source extend (parent DDL source &) |
| 058 | &: Dependencies on table functions could not be written |
| 059 | &: Use of AMDP function could not be written |
| 060 | Base objects are AMDP table functions: metadata cannot be determined |
| 061 | Internal error while reading active extend data (& &) |
| 062 | Internal error while writing active extend data (& &) |
| 063 | Internal error while determining select * usage (&) |
| 064 | Could not enter dependent DDL & - SQL view/entity (&/&) |
| 065 | Could not enter dependent DDL & - DB table/entity (&/&) |
| 066 | Could not enter dependent DDL & - entity (&) |
| 067 | DDL source & is embedded in a cycle |
| 068 | The specified DDL source & is either not active or inconsistent. |
| 069 | Name of entity & and DDL source & must be identical |
| 070 | Abstract entities with parameters are not supported |
| 071 | Cannot read nametab of object & with status & |
| 072 | DDL source & will be activated with associations (strong) |
| 073 | DDL source & will be activated without associations (weak) |
| 074 | Views with active buffering require at least one key field |
| 075 | Could not read DDLDEPENDENCY for DDLS &1 in status &2 |
| 076 | View &1: Literals on left side only allowed with literals on right |
| 077 | Literals are not permitted on the left side of comparison expressions |
| 078 | Annotation value &1 is not valid for annotation &2 |
| 079 | The annotation "AbapCatalog" is not allowed in table functions |
| 100 | ====================== Object Generation from DDL ======================= |
| 101 | Object of type & is undefined in calling method & |
| 102 | Annotation for & does not exist |
| 103 | Standard functions are not supported in the & clause |
| 104 | Random expressions are not supported in a condition |
| 105 | In the On condition, only the operator Equals is supported |
| 106 | The Join operators Inner, Left/Right, Outer, and Full Join are supported |
| 107 | A Join or a table must follow after the From clause |
| 108 | In a condition, =, <, <=, >, >=, <>, and is null are supported |
| 109 | Only literals are supported on the right-hand side of a Where condition |
| 110 | No additional selection condition follows after AND/OR |
| 111 | Base object missing in the selection list for element & |
| 112 | The current expression is not supported in the selection list |
| 113 | Alias name & for column & table & is too long (>30 characters) |
| 114 | Unknown syntax in the selection list |
| 115 | Base tables for creating generic view & could not be read |
| 116 | Base table & for creating generic view & doesn't exist or is not active |
| 117 | Generic view cannot be set up due to duplicate fields |
| 118 | Generic view cannot be set up; error while reading the A version |
| 119 | In the ON condition, only the equals operator (=) is allowed |
| 120 | & & is defined in multiple DDL sources (&) |
| 121 | Append & for base table &: no fields found |
| 122 | Internal error: no base views/tables for view entity & found |
| 123 | Alias & for & has the same name as another base object |
| 124 | Name of parent view is missing for append view & |
| 125 | View append information for view & could not be read |
| 126 | Selection list is empty |
| 127 | Field &: A constant (&) in a condition is too long (>38) |
| 128 | SQL view name & and DDL view name & cannot be identical |
| 129 | Alias & already being used for base object & |
| 130 | Base object, view entity &, is inconsistent; there is no SQL view for it |
| 131 | Name of a base table or a base view is missing |
| 132 | View &: Base view & does not have any active field information |
| 133 | View &: '$extension' for base view & not prepared |
| 134 | At least one enhancement of base objects found, but no field information |
| 135 | Basis table & is in selection more than once; '$extension.*' not possible |
| 136 | Internal error: '$extension' statem.is inconsistent; table name missing |
| 137 | Short description for view & is limited to length 60; will be shortened |
| 138 | Selection condition for &-&: quot. marks missing for comparison value & |
| 139 | $extension: no base tables/views for view entity & found |
| 140 | Base object name missing in "group by" statement for identifier & |
| 141 | Only identifiers are currently allowed in the "group by" clause |
| 142 | Identifiers, literals, and CASE are allowed in aggregate functions |
| 143 | Base object name missing in standard function for identified & |
| 144 | Aggregate function & requires an alias for the column |
| 145 | Expressions with identifiers are not allowed in the & clause |
| 146 | User-defined functions are not supported in the & clause |
| 147 | Aggregate function &: Type information could not be determined |
| 148 | Table name is missing in an expression |
| 149 | Error with standard function & (&) |
| 150 | In the "order by" clause, currently only identifiers are allowed |
| 151 | As a minimum, the base objects (&) return double fields |
| 152 | Select * and joins cannot be combined |
| 153 | With select *, no additional columns can be specified explicitly |
| 154 | select * could not be expanded; base table & does not exist |
| 155 | Length of names list does not match the number of selected columns |
| 156 | An alias must be specified for literals (here &) in the selection list |
| 157 | Type of literal & is unknown or not supported |
| 158 | String/char literal & incorrect, e.g. error in length or quotation marks |
| 159 | Alias missing for column & |
| 160 | Value of literal (-)& is greater than an 8-byte integer |
| 161 | Association &: target & does not exist |
| 162 | Base object & with alias & is not unique |
| 163 | Base object & is not unique |
| 164 | Names in selection list are not unique: &-& appears more than once |
| 165 | The specified function & is not known as a standard function |
| 166 | Currently, only unmanaged associations are supported |
| 167 | Association expressions are not allowed in the & condition |
| 168 | Error in standard function & for database & |
| 169 | Association &: Column information of source & does not exist |
| 170 | Association &: Column information for target & does not exist |
| 171 | After CASE, currently only a table column is allowed |
| 172 | No table or view is specified for column & after CASE |
| 173 | CASE without WHEN or THEN keyword |
| 174 | CASE (WHEN): value & does not have expected type &, length <= & |
| 175 | CASE for column &/(&): column &-&, type properties do not suit |
| 176 | Literals, columns, case, arith. expressions, functions allowed after & |
| 177 | CASE for column &: the resulting column is type (&,&,&) |
| 178 | CASE (THEN): value & does not have expected type &, length & |
| 179 | After WHEN in CASE, literals, column, case, functions, paths allowed |
| 180 | No table or view is specified for column &1 after &2 |
| 181 | Unknown expression at current position |
| 182 | CASE: Default & does not have correct type &, length <= & |
| 183 | Columns, arithm. expressions, and predefined functions allowed after CASE |
| 184 | Annotation &: default value is missing |
| 185 | Type of literal & is unknown or not supported |
| 186 | Specified function & is not known as a predefined function |
| 187 | Function & expects & parameters; current number is & |
| 188 | Internal error: unknown syntax for function & |
| 189 | Function &: parameter at position & has incorrect type & |
| 190 | Error statement generation function & (&) |
| 191 | Error statement generation function & on database & |
| 192 | Literal & of type CHAR must have at most 1333 characters |
| 193 | Error in function & in selection list |
| 194 | Function &: Resulting length cannot be determined or is initial value |
| 195 | Function & not supported; select list allows the following functions: |
| 196 | Function & is not supported |
| 197 | Type of case expression in selection list could not be determined |
| 198 | Function & requires an alias for the column |
| 199 | Column & in arithmetic expression: table, view, or entity missing |
| 200 | Operators *, +, - are supported in arithmetic expressions |
| 201 | Column & in arithm. expression: view or table & does not contain column |
| 202 | Data type of function & could not be determined |
| 203 | Data type of arithmetic expressions & could not be determined |
| 204 | CASE for column &/(&): non-supported data type & |
| 205 | CASE for column &/(&): data type conflict |
| 206 | CASE (&): Nested CASE & does not supply consistent data type info |
| 207 | CASE (&): Aggregate function & does not supply a valid data type |
| 208 | CASE for column &/(&): Function & does not supply a valid data type |
| 209 | Name list in Select cannot be combined with $extension and select * |
| 210 | Results type & is not supported |
| 211 | A length must be specified for results type & |
| 212 | CASE (&): CAST function does not supply a valid data type |
| 213 | Function &: forbidden value & for parameter & |
| 214 | Literal & of type NUMC can have maximum 255 characters |
| 215 | Length of resulting field for literal or expression enlarged from & to & |
| 216 | Short text for entity & is restricted to length 60 and will be shortened |
| 217 | Parent object & for extend & could not be read |
| 218 | Currently supported: & & |
| 219 | View field &-& already exists in parent object (DDL source &) |
| 220 | >>>> The following errors are caused by Extend DDL Source &: |
| 221 | Extend DDL Source &: Determination of parent DDL name not possible |
| 222 | Field & will be copied from a switchable append & |
| 223 | CASE (&): Conversion function does not return a valid data type |
| 224 | Currently allowed number & for unions is exceeded |
| 225 | Column &: Result type of aggregate function & cannot be determined |
| 226 | Information of parent DDL source & could not be determined |
| 227 | Association &: Information on origin of fields is missing |
| 228 | Type of parameter & is unknown or not supported |
| 229 | Used view & with parameters: Only scalars or columns can be bound |
| 230 | View &: type information for view columns could not be determined |
| 231 | Domain & does not exist or is not active. Value taken directly. |
| 232 | & is not a fixed value of domain &. Value taken directly. |
| 233 | Length & > 10 char., so not a fixed value domain &. Value taken directly. |
| 234 | Not a valid domain and/or fixed value definition |
| 235 | Data type of domain fixed value & cannot be determined |
| 236 | select * could not be expanded: base entity & does not exist |
| 237 | CASE (WHEN): maximum data type cannot be determined (&,&) (&,&) |
| 238 | CASE (THEN): Maximum data type cannot be determined (&,&) (&,&) |
| 239 | CASE (DEFAULT): Maximum data type cannot be determined (&,&) (&,&) |
| 240 | CASE (&): & does not return a valid type |
| 241 | View extend & for &: column information missing, will not be added |
| 242 | View extend info (SQL view &) for & is incomplete; adding data not poss. |
| 243 | Statement for extend & (DDL source &) for view & cannot be generated |
| 244 | Function &: value for &. Parameter must be greater than & (is &) |
| 245 | Function &: value of &. Parameter must be a positive integer value |
| 246 | Type of session variable & is unknown or not supported |
| 247 | Alias name for session variable & is missing |
| 248 | Alias name for parameter & is missing |
| 249 | Specification of table or view for column & after CAST is missing |
| 250 | Specification of table or view for column & in function & is missing |
| 251 | Specified function & is not a valid named function |
| 252 | Parameter & is not known |
| 253 | In function &, only columns, literals and parameters allowed |
| 254 | The current expression is not allowed in function & |
| 255 | Association & ignored: target & currently only has limited availability |
| 256 | Extend & will not be added since incorrect regarding alias definition |
| 257 | CASE (&): Function & does not return a valid data type |
| 258 | CAST is not supported for current expression, for ex., aggregate function |
| 259 | Current expression is not allowed as operand of an arithmetic operation |
| 260 | Nested SEARCHED CASE does not return any consistent data type info |
| 261 | For data type &, length &, no results type was determined |
| 262 | (expected: &) |
| 263 | Array-type annotations cannot be nested |
| 264 | No takeover taking place |
| 265 | Parameter &: Specified type abap.& is not a built-in dictionary type |
| 266 | Function CAST for column &: target type & not specified correctly |
| 267 | Type abap.& is not a built-in dictionary type |
| 268 | Data element & does not exist or is not active |
| 269 | Data element & does not exist; name must not be longer than 30 characters |
| 270 | Name of table function missing |
| 271 | Neither a view definition nor a view extend definition exists |
| 272 | Short text table function & has length 60 and is truncated |
| 273 | Return parameters of table function & missing |
| 274 | CDS view of a view extend cannot be changed, in this case (&1->&2) |
| 275 | & is marked as client-specific; type field & at pos. 1 is & (not CLNT) |
| 276 | Annotation name & ... can be max. & characters long; will be truncated |
| 277 | Annotation value & ... can be max. & characters long; will be truncated |
| 278 | Column & from "group by" is not a field in base objects of parent view |
| 279 | Annotation value & is longer than 255 char.; translation not possible |
| 280 | Alias name can be at most & characters in length (alias & for &) |
| 281 | Controlled changes were not applied |
| 282 | Controlled changes (&) were applied |
| 283 | Expressions with parameters are not allowed in the & clause |
| 284 | Expressions with domain fixed values are not allowed in the & clause |
| 285 | Expressions with session variables are not allowed in the & clause |
| 286 | DDL source type is unknown (<> View, Extend, Table Function, Entity) |
| 287 | AVG is for current expression, e.g. aggregate function not supported |
| 288 | Only columns or NULL possible for case join return element |
| 289 | Return elements in case join are missing |
| 290 | The CAST function is not supported in the & clause |
| 291 | DDL Source Name & and Entity Name & are not the same. |
| 292 | No technical settings defined for entity &. |
| 293 | Internal error while reading technical settings for entity &. |
| 294 | Name of abstract identity is missing. |
| 295 | ON definition missing for association &, source &, target &, with type & |
| 296 | Association &: No local field exists for element index & |
| 297 | Reference fields in abstract entities must be defined locally |
| 298 | IS NULL is not supported for associations |
| 299 | DDL source &: parse_cds returned initial AST and no errors |
| 300 | ================================= Checks =============================== |
| 301 | Specify a name for the DDL source |
| 302 | Specify a name for the & object |
| 303 | Incorrect object type &; name check is not possible |
| 304 | Type conflict for object & type & |
| 305 | Name & is not correct in the ABAP environment |
| 306 | Object & of type & already exists |
| 307 | No valid view name could be found |
| 308 | Object & of type & was already created in DDL source & |
| 309 | Entity & was checked successfully |
| 310 | Entity & was checked with warning messages |
| 311 | Entity & is inconsistent |
| 312 | Check entity & |
| 313 | Object & of type & was already created in DDL source & (newest version) |
| 314 | No valid entity name could be found |
| 315 | & & was deleted; & & no longer exists in DDL source |
| 316 | Defined view & already exists in active version |
| 317 | &: - not allowed |
| 318 | The name & contains a blank; enter it again without blanks |
| 319 | The name & contains a non-alphanumeric character |
| 320 | String column & is not possible with SELECT DISTINCT |
| 321 | & is not a valid annotation |
| 322 | SQL view & cannot be renamed as &; DDL source & is already shipped |
| 323 | CDS view & cannot be renamed as &; DDL source & already shipped |
| 324 | Type information for &-& does not exist (please check base object &) |
| 325 | No support for function & on database & |
| 326 | select * cannot be combined with 'group by' |
| 327 | select * cannot be combined with 'having' |
| 328 | select * and $extension can cause duplicate fields |
| 329 | Type & is not allowed as target type for CAST function |
| 330 | Basis object & is external view. CDS view thus only available on HANA DB. |
| 331 | Case for column &: type information of default value is not correct |
| 332 | Case for column &: type information of value after & is not correct |
| 333 | Data type & is currently not supported in an arithmetic expression |
| 334 | At least one operand is of type FLTP. This requires explicit FLTP. |
| 335 | Data types of operands of arithmetic expression are missing |
| 336 | Maximum accuracy 37 at DEC exceeded by an arithmetic expression |
| 337 | Max. number of decimal places 37 at DEC in arithmetic expression exceeded |
| 338 | Path & contains errors |
| 339 | & was selected as reference field; type must be UNIT/CUKY, not & |
| 340 | &-&: Non-supported data type & in a condition |
| 341 | Data type conflict in a selection condition or ON condition for &-& |
| 342 | CAST: Source type & is not supported |
| 343 | & is not supported as target type at CAST |
| 344 | CAST & of type & to type & is not possible |
| 345 | CAST & of type & to & is not possible; lengths must match |
| 346 | CAST & from & to type &: target type length too small, loss of data poss. |
| 347 | & & on type &: Length information of target type is missing |
| 348 | CAST & type & with this length to type & is not possible |
| 349 | CAST & to identical type & |
| 350 | Column & is not contained in the GROUP BY list |
| 351 | Column &.& is not contained in the GROUP BY list |
| 352 | Target type & has fixed length &. Correct it or do not specify at all. |
| 353 | Function &: At position &, only & allowed |
| 354 | At least one column, in addition to client column &, must be maintained |
| 355 | CAST & from & to type & is not possible; target length is too small |
| 356 | View with parameters &: view name is missing |
| 357 | View with parameters &: select statement is missing |
| 358 | View with parameters &1: information on result type is missing |
| 359 | Parameter information for the DB statement cannot be set up |
| 360 | & is not a valid parameter, is not contained in the definition |
| 361 | Parameter binding for view & contains errors; view & has no parameters |
| 362 | Input parameter & is not defined in the bound view & |
| 363 | & for &: Non-supported data type & for parameter passing to view & |
| 364 | & for &: Type/length/dec. incompatible for parameter passing to view & |
| 365 | Parameters can only be bound to CDS views; & is table or SQL view |
| 366 | Parent view & contains union/intersect/except; extends are not allowed |
| 367 | Parent view &1 has aggregate function/s or group by; no extension allowed |
| 368 | Entity &: Data element & parameter/field & does not exist or not active |
| 369 | Entity &: Type info for parameters cannot be determined |
| 370 | View with parameters &: parameter & is not defined |
| 371 | CAST & of type & to & is not possible. Decimal places of target too small |
| 372 | DIVISION: Decimal places must be less than or equal to & |
| 373 | Function &: For parameter & only & can be passed |
| 374 | Function &: parameter & has incorrect type & (expected: &) |
| 375 | Function &: parameter & missing, but is mandatory |
| 376 | Function &: Parameter & of type & has incorrect length (expected &) |
| 377 | CAST is not supported for type & (possible - &) |
| 378 | Searched case &. condition : type info of value after & is not correct |
| 379 | SEARCHED CASE: Type information of default value is not correct |
| 380 | The current expression is not supported in SEARCHED CASE after THEN |
| 381 | Escape characters in LIKE must only be literals |
| 382 | Escape character after LIKE must only have length 1 |
| 383 | ASCII characters are allowed as escape characters (not SPACE, ', _, or %) |
| 384 | %, _, or escape symbol must follow the escape character in like |
| 385 | Division only allowed for float numbers (left operand has type &) |
| 386 | Division only allowed for float numbers (right operand has type &) |
| 387 | Division x/y is only allowed for float numbers |
| 388 | LPAD: Length of result must not be shorter than the Ipad string |
| 389 | Parameter &: data type & is not allowed for parameters |
| 390 | Function &: parameter at position & has incorrect data type & |
| 391 | ( allowed types: & ) |
| 392 | Select lists with unions must have the same name or else insert aliases |
| 393 | Extend & has further extend & as parent. This is not supported. |
| 394 | The basis view of the extend & does not exist |
| 395 | Problematic alias or column name & in union & is not the same as name & |
| 396 | Select with aggregate functions requires a group by clause |
| 397 | Parent view & contains selection list interface: Extend view not possible |
| 398 | View contains selection list interface: Extend views then not possible |
| 399 | Function &(&): only columns with length <= & allowed |
| 400 | Function &(&) can only be used for columns of even length |
| 401 | Input parameter & has a different position in bound view & |
| 402 | Function &: parameter & has incorrect data type & |
| 403 | & & on type &: length of target type is too large |
| 404 | & & on type &: The number of decimal places is too large for target type |
| 405 | Function &: parameter has incorrect data type & |
| 406 | Literal of &. parameter of function & must have length & |
| 407 | Column of &. parameter of function & must have length & |
| 408 | If CAST with type is on & (&, type &), type and length must be the same |
| 409 | Checking length information for result with CAST/function: |
| 410 | Checking decimal places for result with CAST/function: |
| 411 | Name of proxy object not specified |
| 412 | Name of proxy object & is not an active entity name |
| 413 | No active replacement object found |
| 414 | Function &(&): only literals of length <= & allowed |
| 415 | Function &(&) only usable for literals with even length |
| 416 | Function &(&): Only characters 0123456789ABCDEFabcdef allowed |
| 417 | Function &: DECIMAL_SHIFT = true implicit ROUND = true |
| 418 | Extend & has table function & as parent. This is not supported. |
| 419 | DDL source contains non-7bit ASCII character '&' |
| 420 | Parameter information of parent (DDL source &/view &) does not exist |
| 421 | Parameter &: @Environment.systemField: #CLIENT must be set |
| 422 | Table function is cross-client function; & should not be set |
| 423 | Parameter &: & requires data type CLNT |
| 424 | Besides &, table function & is implemented by AMDP method & |
| 425 | DDL source & of type & cannot be converted to & (-> long text) |
| 426 | Return parameter & of type NUMC can have a maximum length of 69 |
| 427 | Return parameter &: type Decfloat Scale is not supported |
| 428 | Input parameter &: type Decfloat Scale is not supported |
| 429 | Input parameters &: Long char. types (&, STRING, &) are not supported |
| 430 | Input parameter &: binary type LRAW is not supported |
| 431 | Input parameter &: binary type RAWSTRING is not supported |
| 432 | Value &: type/length/decimals incompatible with type info. domain & |
| 433 | Field & still used in CDS view &, association & |
| 434 | Deleted/changed association & still used in CDS view & |
| 435 | Association & with new target &: field & still used in CDS view & |
| 436 | CDS view &: parameter & was deleted |
| 437 | CDS view &: parameter & was added |
| 438 | CDS view &: parameter &, type was changed |
| 439 | The following dependent CDS views with parameter should be checked: |
| 440 | No table function can be selected as proxy object |
| 441 | Function INSTR: search string must not be the empty string |
| 442 | Function &: literal at position & is from the set of forbidden values & |
| 443 | Function &: literal for & is not from the set of allowed values |
| 444 | View with parameters & cannot be used as a replacement object |
| 445 | Number of Basis objects & is greater than the allowed number & |
| 446 | Function &: at position &, only &, possibly positive integers allowed |
| 447 | Error during handling of dependents |
| 448 | Problem during delta calculation; all dependents will be activated |
| 449 | Return parameter &: & is a generated proxy type and cannot be used |
| 450 | Input parameter &: & is a generated proxy type and cannot be used |
| 451 | Dependent objects contain errors |
| 452 | Obj. with select * cannot be determined, all dependents will be activated |
| 453 | Check of dependent objects |
| 454 | Dependent objects checked successfully |
| 455 | Dependent objects checked, errors found |
| 456 | At least one column, apart from the client column, must be specified |
| 457 | CDS view &: parameter definition changed |
| 458 | Name association & is too long; a maximum of 30 characters is allowed |
| 459 | With LIKE in compares, only literals allowed on the right |
| 460 | View contains union: extension through extends is not possible |
| 461 | View with parameters and selection list interface cannot be combined |
| 462 | Function &: value of &. parameter not from set of allowed values & |
| 463 | Parent view & must not be extended; extends are not allowed |
| 464 | View must not be extended: extends are not allowed |
| 465 | Checks SQL View & |
| 466 | Enhancement group_by can only be allowed if group_by already exists |
| 467 | Checks DDL Source & |
| 468 | DDL source & was checked successfully |
| 469 | DDL source & was checked and has warning messages |
| 470 | DDL source & contains errors |
| 471 | CAST & using data element only with identical type/length (target type &) |
| 472 | No aggregate function can be added to extend &1 |
| 473 | Invalid value '&' for annotation 'ClientHandling.Type' |
| 474 | Old and new annotation for client dependency are contradictory |
| 475 | Direct activation is currently not allowed |
| 476 | Extension category #NONE is not combinable |
| 477 | Extension category #GROUP_BY or #UNION requires #PROJECTION_LIST |
| 478 | &: A limiting target type &(&,&) is not possible |
| 479 | &: DEC, QUAN, CURR, D16N, and D34N are allowed as a target type for INT* |
| 480 | &: DEC, CURR, QUAN (not &) allowed as target type |
| 481 | &: DEC/CURR/QUAN/D16N/D34N are allowed as a target type for DEC/CURR/QUAN |
| 482 | &: Only FLTP itself allowed as target type for FLTP |
| 483 | The DDL source & can only be used to define a &. |
| 484 | The DDL source & can only be used to define a &. |
| 485 | Definition of DDL Source & is not possible. Unknown DDL type &. |
| 486 | Field &: Data type & is not allowed for fields |
| 487 | Client annotations are not allowed in abstract entities |
| 488 | Row & column & contains a non-7-bit ASCII character '&' |
| 489 | The name of the custom entity is missing |
| 490 | SQL view &1 for DDL source &4 in use; cannot be renamed as &2 |
| 491 | Field & of type & must be in the final position |
| 492 | Field & does not have a preceding length field of type & |
| 493 | Only one long field allowed |
| 494 | The value of the annotation & is invalid |
| 495 | The annotation "&1" is deprecated. Use annotation "&2" instead. |
| 496 | Currency and quantity reference not permitted in the same element |
| 497 | &: Currency reference only valid for type CURR, DECFLOAT34, DEC, FLTP |
| 498 | &: Quantity reference only valid for type QUAN, DECFLOAT, DEC, FLTP, INT |
| 499 | &: D16N/D34N are allowed as target types for D16N (only D34N for D34N) |
| 500 | ================== Statement Generation (also DB-specific) ============== |
| 501 | Problems while generating the Like statement for 'like &' |
| 502 | No support for 'literals' on database & (selection list) |
| 503 | Statement for literal & for DB & not generated |
| 504 | No support for 'literals' on database & (case statement) |
| 505 | Statement for literal & in CASE for database & not generated |
| 506 | CAST statement for arithmetic expression & to DB & could not be generated |
| 507 | No support for 'literals' on database & (arithmetic expressions) |
| 508 | Statement generation DB & is not possible (method &) |
| 509 | Error statement generation CAST for arithmetic expression & for DB & (&) |
| 510 | DB-dependent operations (here &) are not possible (&) |
| 511 | CAST statement for expression & on DB & could not be generated |
| 512 | Error statement CAST generation for expression & for DB & (&) |
| 513 | DB-specific support (&) not possible (&) |
| 514 | Parameter &: statement at usage location for DB & not generated |
| 515 | Parameterized view & is currently not supported on DB & |
| 516 | At least one base view is an external view and not supported on DB & |
| 517 | View & will not be created on DB & |
| 518 | Error statement generation of CAST for arithmetic operand & for DB & (&) |
| 519 | CAST for arithmetic operand & on DB & could not be generated |
| 520 | In the object hierarchy, there is at least one pooling/cluster table |
| 521 | Problem for database & while creating join operator |
| 522 | Input parameters & could not be mapped onto database types |
| 523 | Output parameters & could not be mapped onto database types |
| 524 | Statement table function & could not be created |
| 525 | & is a table function |
| 526 | The table function & is not created on DB & |
| 527 | In the object hierarchy, at least one table function exists |
| 528 | Session variable &: statement for DB & was not generated |
| 529 | Compare DD - DB is not possible |
| 530 | Create statement is unchanged - > no deletion/recreation possible |
| 531 | Problems while generating Like statement for database &. |
| 532 | At least one Basis object is not supported on database system & |
| 533 | SQL view &1 cannot be renamed as &2 (DDL source &3 is active) |
| 534 | DDL view &1 cannot be renamed as &2 (DDL source &3 is active) |
| 700 | =========================== Generate Statements ========================= |
| 701 | Generating statements for selected views |
| 702 | Processing DDL source & >>> |
| 703 | DDL source & does not exist |
| 704 | Info. on DB view / table function cannot be determined from DDL source & |
| 705 | Statements for database view & will be determined |
| 706 | Statements for & cannot be generated; DDL sources & missing |
| 707 | Generating statements for the following databases: & |
| 708 | Statements for view & could not be generated |
| 709 | Statements for view & could not be written (&) |
| 710 | Uuid for unique statement label could not be generated |
| 711 | Editing DDL sources for database & |
| 712 | Statements for DDL source &; DB object & generated |
| 713 | View with parameter &: statement could not be generated (DB access error) |
| 714 | View with parameters &: statement for DB & could not be generated |
| 715 | Determine base objects: view & does not have any base objects |
| 716 | No DDL views found |
| 717 | View statements will be deleted for DBs & |
| 718 | No statements to be deleted exist for the specified DDL sources |
| 719 | & entry for & (DB &) could not be deleted or does not exist |
| 720 | Not all statements deleted or no entries exist |
| 721 | All statements were deleted |
| 722 | All view statements will be deleted |
| 723 | No DB systems were specified |
| 724 | DB-specific mapping (&) for parameter binding view & has errors |
| 725 | DDL source & exists only in N version; statement generation impossible |
| 726 | Start of program: & Time stamp & & |
| 727 | End of program & & & |
| 728 | Program ended with return code & |
| 729 | No DB feature for view/table function/hierarchy & (DDL source &) |
| 730 | Statements for & will not be generated for & |
| 731 | Table function & could not be deleted from or recreated on the database |
| 732 | Table function & could not be created on the database |
| 733 | DB feature AMDP table function (DDL source &) not supported |
| 734 | Statements for AMDP table function & will be determined |
| 735 | &: only views and AMDP table functions are supported (not &) |
| 736 | & is a DDL source extend and statements cannot be created |
| 737 | At least one basis view is an external view |
| 738 | The name of the basis object is missing for the extend & |
| 739 | Message number & from SD_EXPRESSION is unknown |
| 740 | Typed literals are not allowed in DDLS type V (views) |
| 741 | Literal handled without decimal places; cast may be necessary |
| 800 | ========== Various DDL Tools =========================================== |
| 801 | No DDL sources found for selection |
| 802 | Parameter combination is not allowed (&) (&) |
| 803 | Namespace of DDL '&1' does not match namespace of ENTITYNAME '&2' |
| 804 | Namespace of DDL '&1' does not match namespace of VIEWNAME '&2' |
| 805 | Associated entity '&1' for '&2' |
| 806 | Annotation '&1' not allowed in DDIC-based CDS views |
| 807 | Select * not supported in DDIC-based CDS views with union |
| 808 | Method get_select() is deprecated; use generate_create_statement() |