| TK284 |
Global information was updated for user & |
| TK285 |
Create documentation for task & |
| TK287 |
Special character "&" in generic key |
| TK288 |
Only the specified table keys are transported |
| TK289 |
Empty key lines were deleted before saving |
| TK290 |
Adjustment of the key entries may be necessary, however has not happened |
| TK291 |
Adjustment of the key entries necessary, however has not been done |
| TK292 |
Client & does not correspond to the logon client |
| TK293 |
Language & does not correspond to the logon language |
| TK294 |
& is not a valid client |
| TK295 |
& is not a valid language |
| TK296 |
Only a final asterisk can be used as a generic entry |
| TK297 |
Cannot access global object directory (GTADIR) |
| TK298 |
Comparison with the & system is currently locked |
| TK299 |
Object directory entry could not be deleted |
| TK300 |
Object must belong to package &1 |
| TK301 |
&1 cannot be included in request/task |
| TK304 |
Object &3 is not original in this system |
| TK305 |
Relocations cannot contain subobjects |
| TK306 |
Transport objects from package &2 to target &1 only |
| TK307 |
No conversion for object type &1 &2 possible |
| TK308 |
Do not enter test objects in transportable Workbench requests |
| TK309 |
Request lock for &1 is in invalid task/request &2 |
| TK310 |
&1 is locked in request/task &2 |
| TK311 |
Unknown syntax "&1" "&2" "&3" |
| TK312 |
Incorrect internal lock argument: &1 &2 &3 |
| TK313 |
Object &1 &2 &3 requires a directory entry |
| TK314 |
Table &1 has no fields |
| TK315 |
Table &1 does not exist or is not activated |
| TK316 |
Object &1 is not a database table |
| TK317 |
Table keys of table &1 contradict the data type |
| TK318 |
No key fields are defined for table &1 |
| TK319 |
Fill table key for table &1 only up to position &2 only |
| TK320 |
Key entry for table &1 may only be generic |
| TK321 |
&1: Object &2 &3 &4 could not be converted |
| TK322 |
Lock for & applies to a request that does not exist or is empty |
| TK323 |
&1 is a table, it cannot be accessed as a view |
| TK324 |
&1 is a view, it cannot be accessed as a table |
| TK326 |
Choose a correction |
| TK327 |
Choose a repair |
| TK328 |
Object prepared for display only |
| TK329 |
Object directory entries are only displayed and may not be changed |
| TK330 |
Selected changes to object directory entry only in original system |
| TK331 |
User "&1" does not exist in this system |
| TK332 |
Only edit objects from package &2 in local requests |
| TK333 |
& Perforce release has been started asynchronously |
| TK334 |
& Perforce test release has been started |
| TK335 |
& Perforce test release has been stopped |
| TK336 |
Have all data elements and messages been documented (long text docu.)? |
| TK337 |
Are all screen fields defined in the Data Dictionary? |
| TK338 |
Are all language-specific texts in ABAP sources translatable ? |
| TK339 |
Was the performance of the function measured with SQL trace + ABAP trace? |
| TK340 |
Was the amount of table entries reduced to a minimum? |
| TK341 |
Was each table assigned to the correct delivery class ? |
| TK342 |
No namespace assignment per object naming convention for object type &2 |
| TK343 |
Cannot assign namespace using package for object &1 &2 &3 |
| TK344 |
Namespace is reserved for partner development (partner project &2) |
| TK345 |
Cannot delete &1: Referenced packages exist |
| TK346 |
There is currently no check function for object type & & |
| TK347 |
Namespace is reserved (generated objects or internal use only) |
| TK348 |
Enter the full object name |
| TK350 |
Export & performed successfully (see log) |
| TK351 |
Export & performed with warnings (see log) |
| TK352 |
& export ended with errors (request is modifiable again, see log) |
| TK353 |
System name length for object type &1 not defined in this function |
| TK354 |
Specified object type &1 is not known in this function |
| TK355 |
Objects locked for other requests |
| TK356 |
Not all objects can be edited as desired |
| TK357 |
Object "&1" "&2" "&3" cannot be transported |
| TK358 |
Choose a different name for namespace &1 |
| TK359 |
No valid license exists for namespace &1 |
| TK360 |
No suitable namespace available |
| TK361 |
Object type &1 &2 is unknown or does not have an object directory entry |
| TK362 |
Namespace &1 is unknown, check syntax |
| TK363 |
Dictionary objects with long names are not relocated to Basis systems |
| TK364 |
Request contains corrupt (non-ASCII) table key |
| TK365 |
Exception: SAP object although customer name range |
| TK366 |
Object already exists globally in system & |
| TK367 |
Objects in SAP namespace cannot be included in local packages |
| TK368 |
Cannot display where-used list |
| TK369 |
Call only for objects of SAP partners (J in the first position) |
| TK370 |
Namespace conflict between object &1 and target package &3 |
| TK371 |
&1 &2 has tested the change request; &3 |
| TK372 |
&1 2& has eliminated the error in the request |
| TK373 |
Extended syntax check (SLIN) is missing for certain ABAP sources |
| TK374 |
Menu Painter standards check is missing for certain CUA interfaces |
| TK375 |
Not all ABAP/4 Dictionary elements are free of errors and activated |
| TK376 |
Not all data elements and messages have long text documentation |
| TK377 |
Not all screen fields are defined in the ABAP/4 Dictionary |
| TK378 |
Not all language-specific texts in ABAP sources are translatable |
| TK379 |
Performance measurements (SQL/ABAP trace) missing for certain functions |
| TK380 |
More tables entries than necessary are transported |
| TK381 |
Tables may be in the wrong delivery class |
| TK382 |
No test procedure has been defined for your functions |
| TK383 |
Adjustment (request function was not carried out in the group) |
| TK384 |
Requests with archived key are not copied |
| TK385 |
Not all text modules have the status "final version" |
| TK386 |
Log overview updated |
| TK389 |
Documentation of object & has status '&' |
| TK390 |
No documentation found |