SAP ABAP Message Class DDLS (For DDL source handling)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-DWB-DIC (Application Component) ABAP Dictionary
⤷ SDDL (Package) DDL-Specific Dictionary Functions
⤷ BC-DWB-DIC (Application Component) ABAP Dictionary
⤷ SDDL (Package) DDL-Specific Dictionary Functions
Attributes
Message class | DDLS | |
Short Description | For DDL source handling | |
Changed On | 20141121 | |
Last Changed At | 124009 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | ===================== Base Messages for DDLs ============================ | The short text describes the object sufficiently | |
2 | 001 | Invalid input value: &1 = &2 | The short text describes the object sufficiently | |
3 | 002 | & | The short text describes the object sufficiently | |
4 | 020 | ===================== Read/Write/Activate/Delete ======================== | The short text describes the object sufficiently | |
5 | 021 | DDL source & could not be read | The short text describes the object sufficiently | |
6 | 022 | View & could not be saved | The short text describes the object sufficiently | |
7 | 023 | View entity & could not be saved | The short text describes the object sufficiently | |
8 | 024 | Internal error while activating view & | The short text describes the object sufficiently | |
9 | 025 | DDL source & was activated successfully | The short text describes the object sufficiently | |
10 | 026 | DDL source & was activated with warning messages | The short text describes the object sufficiently | |
11 | 027 | DDL source & could not be activated | The short text describes the object sufficiently | |
12 | 028 | Name of view entity missing in DDL srce &: DEFINE VIEW <View entityname> | The short text describes the object sufficiently | |
13 | 029 | Name of SQL view missing; annotation & must be specified | Space: object requires documentation | |
14 | 030 | Activate DDL source & | The short text describes the object sufficiently | |
15 | 031 | Activate DDL source & (active version) | The short text describes the object sufficiently | |
16 | 032 | Error while writing usages (duplicate entries for &) | The short text describes the object sufficiently | |
17 | 033 | Sources for DDL view & in & version could not be read | The short text describes the object sufficiently | |
18 | 034 | SQL view name was changed from & to & | The short text describes the object sufficiently | |
19 | 035 | Extended DDL source & must be adapted | The short text describes the object sufficiently | |
20 | 036 | Entity name was changed from & to & | The short text describes the object sufficiently | |
21 | 037 | Old SQL view & will be deleted | The short text describes the object sufficiently | |
22 | 038 | Old DDL View & will be deleted | The short text describes the object sufficiently | |
23 | 039 | DDL source & could not be deleted | The short text describes the object sufficiently | |
24 | 040 | Package & is not usable for & | Space: object requires documentation | |
25 | 041 | Activating dependent DDL source & (active version) | The short text describes the object sufficiently | |
26 | 042 | Old view & will not be deleted because it is not generated | The short text describes the object sufficiently | |
27 | 043 | No DDL views to be generated found | The short text describes the object sufficiently | |
28 | 044 | & DDL views from altogether & DDL sources processed | The short text describes the object sufficiently | |
29 | 045 | & DDL views generated successfully | The short text describes the object sufficiently | |
30 | 046 | & DDL views with warnings have been generated | The short text describes the object sufficiently | |
31 | 047 | & DDL views could not be generated | The short text describes the object sufficiently | |
32 | 048 | Activation of DDL sources - see log & | The short text describes the object sufficiently | |
33 | 049 | Dep. DDL & - View/Entity (&/&) could not be entered | The short text describes the object sufficiently | |
34 | 050 | Syntax error in DDL source &: Dependencies were not written | The short text describes the object sufficiently | |
35 | 051 | &: Either DDL source or get_state must be specified | The short text describes the object sufficiently | |
36 | 100 | ====================== Object Generation from DDL ======================= | The short text describes the object sufficiently | |
37 | 101 | Object of type & is undefined in calling method & | The short text describes the object sufficiently | |
38 | 102 | Annotation for & does not exist | The short text describes the object sufficiently | |
39 | 103 | Standard functions are not supported in the & clause | The short text describes the object sufficiently | |
40 | 104 | Random expressions are not supported in the ON condition | The short text describes the object sufficiently | |
41 | 105 | In the On condition, only the operator Equals is supported | The short text describes the object sufficiently | |
42 | 106 | The Join operators Inner, Left/Right, Outer, and Full Join are supported | The short text describes the object sufficiently | |
43 | 107 | A Join or a table must follow after the From clause | The short text describes the object sufficiently | |
44 | 108 | In a condition, =, <, <=, >, >=, <>, and is null are supported | The short text describes the object sufficiently | |
45 | 109 | Only literals are supported on the right-hand side of a Where condition | The short text describes the object sufficiently | |
46 | 110 | No additional selection condition follows after AND/OR | The short text describes the object sufficiently | |
47 | 111 | Base object missing in the selection list for element & | The short text describes the object sufficiently | |
48 | 112 | Table columns and standard functions are supported in the selection list | The short text describes the object sufficiently | |
49 | 113 | Alias name & for column & table & is too long (>30 characters) | The short text describes the object sufficiently | |
50 | 114 | Unknown syntax in the selection list | The short text describes the object sufficiently | |
51 | 115 | Base tables for creating generic view & could not be read | The short text describes the object sufficiently | |
52 | 116 | Base table & for creating generic view & doesn't exist or is not active | The short text describes the object sufficiently | |
53 | 117 | Generic view cannot be set up due to duplicate fields | The short text describes the object sufficiently | |
54 | 118 | Generic view cannot be set up; error while reading the A version | The short text describes the object sufficiently | |
55 | 119 | In the ON condition, only the equals operator (=) is allowed | The short text describes the object sufficiently | |
56 | 120 | & & is defined in several DDL sources (&) | The short text describes the object sufficiently | |
57 | 121 | Append & for base table &: no fields found | The short text describes the object sufficiently | |
58 | 122 | Internal error: no base objects (views, tables) for view & found | The short text describes the object sufficiently | |
59 | 123 | Alias & for table & has the same name as a base table | The short text describes the object sufficiently | |
60 | 124 | Name of parent view is missing for append view & | The short text describes the object sufficiently | |
61 | 125 | View append information for view & could not be read | The short text describes the object sufficiently | |
62 | 126 | Selection list is empty | The short text describes the object sufficiently | |
63 | 127 | Field &: A constant (&) in a condition is too long (>38) | The short text describes the object sufficiently | |
64 | 128 | SQL view name & and DDL view name & cannot be identical | Space: object requires documentation | |
65 | 129 | Alias & already being used for table & | The short text describes the object sufficiently | |
66 | 130 | Base object, view entity &, is inconsistent; there is no SQL view for it | Space: object requires documentation | |
67 | 131 | Name of a base table or a base view is missing | The short text describes the object sufficiently | |
68 | 132 | View &: Base view & does not have any active field information | The short text describes the object sufficiently | |
69 | 133 | View &: '$extension' for base view & not prepared | Space: object requires documentation | |
70 | 134 | At least one enhancement of base objects found, but no field information | Space: object requires documentation | |
71 | 135 | Base tab.& appears several times in selection; '$extension.*' not poss. | The short text describes the object sufficiently | |
72 | 136 | Internal error: '$extension' statem.is inconsistent; table name missing | The short text describes the object sufficiently | |
73 | 137 | Short description for view & is limited to length 60; will be shortened | The short text describes the object sufficiently | |
74 | 138 | Selection condition for &-&: quot. marks missing for comparison value & | The short text describes the object sufficiently | |
75 | 139 | Append & for base view &: no errors found | The short text describes the object sufficiently | |
76 | 140 | Base object name missing in "group by" statement for identifier & | The short text describes the object sufficiently | |
77 | 141 | Only identifiers are currently allowed in the "group by" clause | The short text describes the object sufficiently | |
78 | 142 | Identifiers, literals, and CASE are allowed in aggregate functions | The short text describes the object sufficiently | |
79 | 143 | Base object name missing in standard function for identified & | The short text describes the object sufficiently | |
80 | 144 | Aggregate function & requires an alias for the column | The short text describes the object sufficiently | |
81 | 145 | Expressions with identifiers are not allowed in the & clause | The short text describes the object sufficiently | |
82 | 146 | User-defined functions are not supported in the & clause | The short text describes the object sufficiently | |
83 | 147 | Aggregate function &: Type information could not be determined | The short text describes the object sufficiently | |
84 | 148 | Table name is missing in an expresson | The short text describes the object sufficiently | |
85 | 149 | Error with standard function & (&) | The short text describes the object sufficiently | |
86 | 150 | In the "order by" clause, currently only identifiers are allowed | The short text describes the object sufficiently | |
87 | 151 | As a minimum, the base objects (&) return double fields | Space: object requires documentation | |
88 | 152 | Select * and joins cannot be combined | The short text describes the object sufficiently | |
89 | 153 | With select *, no additional columns can be specified explicitly | The short text describes the object sufficiently | |
90 | 154 | select * could not be expanded; base table & does not exist | The short text describes the object sufficiently | |
91 | 155 | Length of names list does not match the number of selected columns | The short text describes the object sufficiently | |
92 | 156 | An alias must be specified for literals (here &) in the selection list | The short text describes the object sufficiently | |
93 | 157 | Type of literal & is unknown or not supported | The short text describes the object sufficiently | |
94 | 158 | String or Char literal & is not correct; example - error with quot. marks | The short text describes the object sufficiently | |
95 | 159 | Alias missing for column & | The short text describes the object sufficiently | |
96 | 160 | Value of literal & is greater than a 4-byte integer | The short text describes the object sufficiently | |
97 | 161 | Association &: target & does not exist | The short text describes the object sufficiently | |
98 | 162 | Table & with alias & is not unique | The short text describes the object sufficiently | |
99 | 163 | Table & is not unique | The short text describes the object sufficiently | |
100 | 164 | Names in selection list are not unique: &-& appears several times | The short text describes the object sufficiently | |
101 | 165 | The specified function & is not known as a standard function | The short text describes the object sufficiently | |
102 | 166 | Currently, only unmanaged associations are supported | The short text describes the object sufficiently | |
103 | 167 | Association expressions are not allowed in the & condition | The short text describes the object sufficiently | |
104 | 168 | Error in standard function & for database & | The short text describes the object sufficiently | |
105 | 169 | Type of column & is not correct for standard function & | The short text describes the object sufficiently | |
106 | 170 | Association &: Column information for target & does not exist | The short text describes the object sufficiently | |
107 | 171 | After CASE, currently only a table column is allowed | The short text describes the object sufficiently | |
108 | 172 | No table or view is specified for column & after CASE | The short text describes the object sufficiently | |
109 | 173 | CASE without WHEN or THEN keyword | The short text describes the object sufficiently | |
110 | 174 | CASE (WHEN): value & does not have expected type &, length <= & | The short text describes the object sufficiently | |
111 | 175 | CASE for column &/(&): column &-&, type properties do not suit | The short text describes the object sufficiently | |
112 | 176 | After &, only literals, columns, and simple case expressions supported | The short text describes the object sufficiently | |
113 | 177 | CASE for column &: the resulting column is type (&,&,&) | The short text describes the object sufficiently | |
114 | 178 | CASE (THEN): value & does not have expected type &, length & | The short text describes the object sufficiently | |
115 | 179 | After WHEN in CASE, table column, literal, or simple case allowed | The short text describes the object sufficiently | |
116 | 180 | No table or view is specified for column &1 after &2 | The short text describes the object sufficiently | |
117 | 181 | Searched Case expressions are currently not supported | The short text describes the object sufficiently | |
118 | 182 | CASE: Default & does not have correct type &, length <= & | The short text describes the object sufficiently | |
119 | 183 | After CASE, identifiers, arithm.expressions, and predef.functions allowed | The short text describes the object sufficiently | |
120 | 184 | Annotation &: default value is missing | The short text describes the object sufficiently | |
121 | 185 | Type of literal & is unknown or not supported | The short text describes the object sufficiently | |
122 | 186 | Specified function & is not known as a predefined function | The short text describes the object sufficiently | |
123 | 187 | Function & expects & parameters; current number is & | The short text describes the object sufficiently | |
124 | 188 | Internal error: unknown syntax for function & | The short text describes the object sufficiently | |
125 | 189 | Function &: parameter at position & has incorrect type & (expected: &) | The short text describes the object sufficiently | |
126 | 190 | Error statement generation function & (&) | The short text describes the object sufficiently | |
127 | 191 | Error statement generation function & on database & | The short text describes the object sufficiently | |
128 | 192 | Literal & of type CHAR must have at most 1333 characters | The short text describes the object sufficiently | |
129 | 193 | Error in function & in selection list | The short text describes the object sufficiently | |
130 | 194 | Function &: Resulting length cannot be determined or is initial value | The short text describes the object sufficiently | |
131 | 195 | Function & is not supported. The select.list allows the following funct.: | The short text describes the object sufficiently | |
132 | 196 | Function & is not supported | The short text describes the object sufficiently | |
133 | 197 | Type of case expression in selection list could not be determined | The short text describes the object sufficiently | |
134 | 198 | Function & requires an alias for the column | The short text describes the object sufficiently | |
135 | 199 | Column & in arithm. expression: table, view, or entity missing | The short text describes the object sufficiently | |
136 | 200 | Operators *, +, - are supported in arithmetic expressions | The short text describes the object sufficiently | |
137 | 201 | Column & in arithm. expression: view or table & does not contain column | The short text describes the object sufficiently | |
138 | 202 | Data type of function & could not be determined | The short text describes the object sufficiently | |
139 | 203 | Data type of arithmetic expressions & could not be determined | The short text describes the object sufficiently | |
140 | 204 | CASE for column &/(&): non-supported data type & | The short text describes the object sufficiently | |
141 | 205 | CASE for column &/(&): data type conflict | The short text describes the object sufficiently | |
142 | 206 | CASE (&): Nested CASE & does not supply consistent data type info | The short text describes the object sufficiently | |
143 | 207 | CASE (&): Aggregate function & does not supply a valid data type | The short text describes the object sufficiently | |
144 | 208 | CASE for column &/(&): Function & does not supply a valid data type | The short text describes the object sufficiently | |
145 | 209 | Name list in Select cannot be combined with $extension and select * | The short text describes the object sufficiently | |
146 | 210 | Results type & is not supported | The short text describes the object sufficiently | |
147 | 211 | A length must be specified for results type & | The short text describes the object sufficiently | |
148 | 212 | CASE (&): CAST function does not supply a valid data type | The short text describes the object sufficiently | |
149 | 213 | Function &: forbidden value & for &.th/st/rd parameter | The short text describes the object sufficiently | |
150 | 214 | Literal & of type NUMC can have maximum 255 characters | The short text describes the object sufficiently | |
151 | 215 | Length of resulting field for literal or expression enlarged from & to & | The short text describes the object sufficiently | |
152 | 300 | ================================= Checks =============================== | The short text describes the object sufficiently | |
153 | 301 | Specify a name for the DDL source | The short text describes the object sufficiently | |
154 | 302 | Specify a name for the & object | The short text describes the object sufficiently | |
155 | 303 | Incorrect object type &; name check is not possible | The short text describes the object sufficiently | |
156 | 304 | Type conflict for object & type & | The short text describes the object sufficiently | |
157 | 305 | Name & is not correct in the ABAP environment | The short text describes the object sufficiently | |
158 | 306 | Object & of type & already exists | The short text describes the object sufficiently | |
159 | 307 | No valid view name could be found | The short text describes the object sufficiently | |
160 | 308 | Object & & already generated in DDL source & | The short text describes the object sufficiently | |
161 | 309 | Entity & was checked successfully | The short text describes the object sufficiently | |
162 | 310 | Entity & was checked with warning messages | The short text describes the object sufficiently | |
163 | 311 | Entity & is inconsistent | The short text describes the object sufficiently | |
164 | 312 | Check entity & | The short text describes the object sufficiently | |
165 | 313 | Object & & was already generated in DDL source & (most recent version) | The short text describes the object sufficiently | |
166 | 314 | No valid entity name could be found | The short text describes the object sufficiently | |
167 | 315 | & & was deleted; & & no longer exists in DDL source | The short text describes the object sufficiently | |
168 | 316 | Defined view & already exists in active version | The short text describes the object sufficiently | |
169 | 317 | &: - not allowed | The short text describes the object sufficiently | |
170 | 318 | The name & contains a blank. Enter without blanks | The short text describes the object sufficiently | |
171 | 319 | The name & contains a non-alphanumeric character | The short text describes the object sufficiently | |
172 | 320 | String column & is not possible with SELECT DISTINCT | The short text describes the object sufficiently | |
173 | 321 | & is not a valid annotation | The short text describes the object sufficiently | |
174 | 322 | SQL view & cannot be renamed to &; DDL source & is already shipped | Space: object requires documentation | |
175 | 323 | CDS view & cannot be renamed to &; DDL source & has been shipped | Space: object requires documentation | |
176 | 324 | Type information for &-& does not exist (check table &) | The short text describes the object sufficiently | |
177 | 325 | No support for function & on database & | The short text describes the object sufficiently | |
178 | 326 | select * cannot be combined with 'group by' | The short text describes the object sufficiently | |
179 | 327 | select * cannot be combined with 'having' | The short text describes the object sufficiently | |
180 | 328 | select * and $extension can cause duplicate fields | The short text describes the object sufficiently | |
181 | 329 | Allowed destination types of CAST function are &. & is not allowed. | The short text describes the object sufficiently | |
182 | 330 | Basis object & is external view. CDS view thus only available on HANA DB. | The short text describes the object sufficiently | |
183 | 331 | Case for column &: type information of default value is not correct | The short text describes the object sufficiently | |
184 | 332 | Case for column &: type information of value after & is not correct | The short text describes the object sufficiently | |
185 | 333 | Data type & is currently not supported in an arithmetic expression | The short text describes the object sufficiently | |
186 | 334 | At least one operand is of type FLTP. This requires explicit CAST. | The short text describes the object sufficiently | |
187 | 335 | Data types of operands of arithmetic expression are missing | The short text describes the object sufficiently | |
188 | 336 | Maximum accuracy 31 at DEC exceeded by an arithmetic expression | The short text describes the object sufficiently | |
189 | 337 | Max. number of decimal places 7 at DEC in arithmetic expression exceeded | The short text describes the object sufficiently | |
190 | 338 | Path & contains errors | The short text describes the object sufficiently | |
191 | 339 | & was selected as reference field; type must be UNIT/CUKY, not & | The short text describes the object sufficiently | |
192 | 340 | Non-supported data type & in a condition | The short text describes the object sufficiently | |
193 | 341 | Data type conflict in a selection condition for &-& | The short text describes the object sufficiently | |
194 | 342 | CAST: Source type & is not supported | The short text describes the object sufficiently | |
195 | 343 | & is not supported as target type at CAST | The short text describes the object sufficiently | |
196 | 344 | CAST & of type & to type & is not possible | The short text describes the object sufficiently | |
197 | 345 | CAST & of type & to & is not possible; lengths must match | The short text describes the object sufficiently | |
198 | 346 | CAST & from & to type & is not possible. Source type length too small. | The short text describes the object sufficiently | |
199 | 347 | CAST & to type &: length information for target type is missing | The short text describes the object sufficiently | |
200 | 348 | CAST & type & with this length to type & is not possible | Space: object requires documentation | |
201 | 349 | CAST & to identical type & | The short text describes the object sufficiently | |
202 | 350 | Column & is not contained in the GROUP BY list | The short text describes the object sufficiently | |
203 | 351 | Column &.& is not contained in the GROUP BY list | The short text describes the object sufficiently | |
204 | 352 | Target type & has fixed length &. Correct it or do not specify at all. | The short text describes the object sufficiently | |
205 | 353 | Function &: At position &, only & allowed | The short text describes the object sufficiently | |
206 | 500 | ================== Statement Generation (also DB-specific) ============== | The short text describes the object sufficiently | |
207 | 501 | Problems while generating the Like statement for 'like &' | The short text describes the object sufficiently | |
208 | 502 | No support for 'literals' on database & (selection list) | The short text describes the object sufficiently | |
209 | 503 | Statement for literal & for DB & not generated | The short text describes the object sufficiently | |
210 | 504 | No support for 'literals' on database & (case statement) | The short text describes the object sufficiently | |
211 | 505 | Statement for literal & in CASE for database & not generated | The short text describes the object sufficiently | |
212 | 506 | CAST for arithmetic expression & to DB & could not be generated | The short text describes the object sufficiently | |
213 | 507 | No support for 'literals' on database & (arithmetic expressions) | The short text describes the object sufficiently | |
214 | 508 | Statement generation DB & is not possible (method &) | The short text describes the object sufficiently | |
215 | 509 | Error statement generation CAST for arithmetic expression & for DB & (&) | The short text describes the object sufficiently | |
216 | 510 | DB-dependent operations (here &) are not possible (&) | The short text describes the object sufficiently | |
217 | 511 | CAST for expression & on DB & could not be generated | The short text describes the object sufficiently | |
218 | 512 | Error statement CAST generation for expression & for DB & (&) | The short text describes the object sufficiently |
History
Last changed on/by | 20141121 | SAP | |
SAP Release Created in | 740 |