DDUT1 - DD: Verschiedene Dictionary Hilfsprogramme
The following messages are stored in message class DDUT1: DD: Verschiedene Dictionary Hilfsprogramme.
It is part of development package SDUT in software component BC-DWB-DIC-AC. This development package consists of objects that can be grouped under "ABAP/4 Dictionary: Analysis Repair Utilities".
It is part of development package SDUT in software component BC-DWB-DIC-AC. This development package consists of objects that can be grouped under "ABAP/4 Dictionary: Analysis Repair Utilities".
Message Nr ▲ | Message Text |
---|---|
000 | Start of program: & Time stamp & & |
003 | End of program & & & |
004 | Program ended with return code & |
100 | ================= Handling of Transports and Temporary Objects ========== |
101 | Analyze transport requests and adapt temporary objects |
102 | No objects to be processed found for the specified requests |
103 | Object & & could not be reset to status 'new' |
104 | Object type & ( & &) cannot be handled |
105 | Handling several transport requests cannot be supported at this time |
106 | Transport requests are not valid |
107 | No local objects found |
108 | No entries for processing in DDXTT |
109 | Analyze objects from inactive nametab and adapt local objects |
110 | & &: Entry deleted from put control tables |
120 | ================= Handle DDL and DCL Dependencies ====================== |
121 | No relevant objects (DDLS or DCL) found |
122 | The following DCL/DDL combinations were found: |
123 | Transport request &: (Dcl/Ddl): &/& |
124 | The following DDL sources were deleted: |
125 | DDL Source: & |
130 | ========================= RUTADAPTANNO ================================== |
131 | DDL source & could not be read in the active version |
132 | DDL source &: metadata for field annotations could not be generated |
133 | Processing DDL source & |
134 | DDL source & was processed successfully |
135 | DDL source & processing finished with warning messages |
136 | DDL source & could not be processed |
137 | DDL source &: annotations could not be written |
138 | Translatable field annotations: quotation marks removed |
139 | Translatable parameter associations: quotation marks removed |
140 | >>> Start Processing Alias Names Annotations for Associations |
141 | >>> Start of removal of quotation marks in translatable annotations |
142 | >>> End of editing alias name annotations for associations |
143 | >>> End of removal of quotation marks in translatable annotations |
144 | Translatable & annotations: no quotation marks or already removed |
145 | No relevant entities in customer system |
146 | DDL source &, entity &: lang. missing in TADIR for lang.-dep. annotations |
147 | >>> Start of resetting number of base objects |
148 | >>> End of resetting number of base objects |
149 | Resetting number of base objects was already performed |
150 | Editing of alias names of annotations for associations already performed |
151 | DDL source &: type could not be determined |
152 | >>> Start of editing source type in DDL source metadata |
153 | >>> End of editing source type in DDL source metadata |
154 | Source type already defined for all DDL sources -> no action required |
155 | DDL source &: view information could not be generated |
160 | ========================= RUTCRESTMTVIEW ================================ |
161 | Valid DB systems could not be found |
162 | DDL source & could not be read |
163 | Create Statement View & for DB & could not be generated |
164 | Ddl source & is neither available as an active nor as an inactive version |
165 | Formatted output of Create Statement View & for DB system &: |
166 | Create Statement View & for DB & could not be formatted |
167 | View &: Cannot compare Create Stmt <-> DB text for DB & |
168 | View &: Statements DD <-> DB do not match |
169 | View &: Statements DD <-> DB do not match |
170 | View &: Comparison Statements DD <-> DB |
171 | Statement for &; database & was not formatted |
172 | & is not a CDS view |
173 | DDL source name will be copied |
174 | Please specify the DDL source name or view name |
175 | DB statement view & for DB & cannot be output as formatted |
176 | Formatted output DB statement: |
177 | Formatted Output DD Create Statement: |
178 | DD Create Stmt. View & for DB & cannot be output in formatted version |
190 | ========================= RUTASSOCSOURCE ================================ |
191 | >>> Start processing; setting of association source |
192 | >>> End of processing; setting of association source |
193 | Source is already set for all associations -> no action |
194 | Ddl source &: Metadata for association cannot be created |
200 | ========================= RUTSETDCLFLAGS ================================ |
201 | >>> Start processing; setting of DCL nametab flags |
202 | >>> End processing; setting of DCL nametab flags |
203 | Structured object & could not be read in active version |
204 | Structured object & could not be written in active version |
205 | Structured object & was processed successfully |
206 | Structured object & was processed with warnings |
207 | Structured object & could not be processed. |
210 | ========================= RUT_TFUNC_REACTIVATE ========================== |
211 | >>> Start processing; activation of all table functions |
212 | >>> End processing; activation of all table functions |
213 | Table functions were processed successfully |
214 | Table functions were processed with warnings |
215 | Not all table functions could be processed successfully. |
216 | No table function for processing could be found |
217 | Error & when activating |
219 | ========================= ========================== |
220 | >>> Start editing field reference updates |
221 | >>> End of editing field reference updates |
222 | Number of entities with missing references: & |
223 | Editing of entity & not ended |
224 | Entity & edited |
300 | ====================== 300-400 Different Tools/Programs ================= |
301 | No DDL sources found for selection |
302 | DDL source & was reset to new |
303 | DDL source & is new; no reset necessary |
304 | DDL source &: error during write, reset not possible |
305 | Table maximum width (DB &): & |
306 | Table maximum key width (DB &): & |
307 | Table maximum index width (DB &): & |
308 | View maximum width (DB &): & |
309 | Table maximum number of columns (DB &): & |
310 | Table maximum number of key columns (DB &): & |
311 | Table with maximum number of index columns (DB &): & |
312 | View maximum number of columns (DB &): & |
313 | DBs without features: |
314 | DBs with features: |
315 | Row/Column Store &: |
316 | Session variables and Intstring changes already executed. |
317 | New DDL source code &1 created in the software component SAP_BASIS |
318 | SQL error &1 when accessing table DDNTT |
319 | ABAP Dictionary mass check: Nametab buffer reset |
330 | ========================= RUTDDLSSETROOTANDPARAMETER ==================== |
331 | No active nametab (&) found for source & (no update) |
333 | Source & has syntax errors (isroot updated automatically when activated) |
334 | Setting the parameter type |
335 | Number of modified entries: & |
336 | Activating the entities that use ENVIRONMENT.SYSTEMFIELD without # |
337 | Activating entity & with parameter & |
338 | No entities found to be activated |
339 | Error code & in activation |
341 | Entities were processed with warnings |
342 | Not all entities were processed without errors |
343 | Invalidating annotation cache with time stamp & |
344 | No entries found to be processed |
345 | Setting the isroot flag in the DDIC metadata and the nametab |
346 | Processing DDL source & |
347 | isroot flag for DDL source & was set in the metadata |
348 | Starting individual processing of the DDL sources |
349 | isroot flag for DDL source & was not set in the metadata |
350 | isroot flag for DDL source & was set for & entries |
351 | isroot flag removed for entity & |
360 | =======================QUICKFIX ACTION_HANDLER=========================== |
361 | Domain &1: Length cannot be changed from &2 to &3 |
362 | Domain &1: Extension only allowed for type CHAR and NUMC |
363 | Domain &1: The change was already made |
380 | =======================Index Cleanup===================================== |
381 | Primary key 0 for table &1 does not exist on the database |
382 | Primary key for table &1 index name &2 was renamed |
383 | Secondary index &1 for table &2 does not exist on the database |
384 | Secondary index &1 for table &2 was renamed |
385 | No suitable index exists on the database |
386 | CREATE INDEX failed for table &1, index &2 |
387 | DROP INDEX failed for table &1, index &2 |
388 | Error in &1 |
389 | Error when creating &1 statement (table &2, index &3) |
390 | BlueGreen system not supported |
391 | Error in input: &1 is not a database table |
392 | FULLTEXT INDEX attributes are inconsistent between DD and HDB |
393 | Full text index &1 for table &2 was renamed |
394 | SIMULATION: Index &1 for table &2 would be renamed |
395 | SIMULATION: Full text index &1 for table &2 would be renamed |
396 | Error when reading &1: &2 |
397 | Error when changing HDB configuration &1: &2 |
398 | Error when reading index metadata for &1 &2 |
400 | No objects to repair found |
401 | Objects to repair &1: &2 repaired, &3 not repaired |
402 | Nametab buffer and type load buffer reset |
403 | &1 repaired by forced activation |
404 | &1 repaired by deleting DDNTT-FILEDS_DATA |
405 | &1: Inactive RTOBJ exists (no automatic repair possible) |
406 | &1: Inactive DD source exists; no automatic repairs possible |
407 | &1: Forced activation failed |
408 | &1: Could not delete DDNTT-FIELDS_DATA |
409 | &1: TABTYPE &2 TABFORM &3 unexpected, automatic repair not possible |
410 | &1: Repaired by generating RTOBJ from active source |
411 | FIELDS_DATA of &1 objects set to NULL |