Objects that no longer exist and therefore can no longer be processed are displayed in the object list of a development class. Updating the object list does not help (up to Release 6.10 - using the Update button, as of Release 6.20 using the context menu option for additional functions.
On the contrary: Although the object first disappears from the object list after being deleted, it is displayed again after the update.
When an actual object is deleted, the corresponding entry in the object list is immediately deleted as well. However, the corresponding
entry in the TADIR database table is only deleted if it is a local
object ($TMP). Otherwise, the TADIR entry remains until the transport is released. Only then is it deleted.
When the object list of a development class is explicitly updated,
only the TADIR information counts. For this reason, if the deleted
object is still contained in the TADIR, it will be displayed again
after the update.
- Wait until transport release is granted (if the object is in a correction). Then update the object list again.
- The TADIR entry can be deleted using the correction system:
As User DDIC!
- a) Choose transaction SE01 -> Maintain transport properties
- b) Enter the appropriate TADIR object (R3TR ..) -> Find
- c) Select object from hit list and -> Maintain
- d) Delete on maintenance pop-up (F14)
The object must be original in the system. If needed, change the system name to your own SID.
- e) Update object list again.
Other terms
() EUNOTE EUWORKBENCH
No comments:
Post a Comment