Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Object type TOBJ - which transaktion can be used to delete it?

Former Member
0 Kudos

Hello ABAP experts,

I have to delete an hole old development. I've used SE80 to delete all objects shown there for the package.

The package itself can only be deleted if all relating entries in table TADIR are deleted after release of the transport order. That has been done. But with new transport order the deletion of the package is not possible, because one entry in TADIR still exists:

PGMID = R3TR

OBJECT = TOBJ

OBJ_NAME = ZZ_PROV_STS

 

This object will not be listed in transaction SE80.

Which transaction may I use to delete this last Object?

Regards

George

1 ACCEPTED SOLUTION

JJosh
Active Participant

Hi,

Check whether this entry exists in the Transport Request.. If so delete the entry from TR and delete the TR too. Hence the object gets unlocked.

Else, open the object with the required tcode and try deleting the object and any related sub-objects. Also try the rebuild the object list in SE80 (Right Click on Package) and see whether any dependent objects exists or not.

17 REPLIES 17

raymond_giuseppi
Active Contributor
0 Kudos

Use transaction SOBJ (or SE54) to manage those "Definition of a Maintenance and Transport Object"

If a problem has destroyed the object but not the entry in object directory use SE03 to delete this ghost.

Regards,

Raymond

0 Kudos

Deletion of entry with SE03 does not work, message "object allready exists".

I try to find the object with SOBJ and SE54 but not successful.

Any further idea?

Thanks a lot!

George

JJosh
Active Participant

Hi,

Check whether this entry exists in the Transport Request.. If so delete the entry from TR and delete the TR too. Hence the object gets unlocked.

Else, open the object with the required tcode and try deleting the object and any related sub-objects. Also try the rebuild the object list in SE80 (Right Click on Package) and see whether any dependent objects exists or not.

Former Member
0 Kudos

Hi,

rebuild object list give no new informations, object will not be listed there.

If I check the object within SE03 it was mentioned as unlocked.

0 Kudos

Don't look for ZZ_PROV_STS but for ZZ_PROV_ST (type S). It should be a maintenance dialog generated on table ZZ_PROV_ST with a text table.

If error arise, you may consider building against the dialog maintenance via SE54 and deleting it immediately.

Regards,

Raymond

JJosh
Active Participant
0 Kudos

Hi,

  Try using the function module MI_PACKAGE_DELETE .. or inSE37 .. try searching for function modules to delete the package. just try executing this.

Thanks.

Former Member
0 Kudos

Can't find also object ZZ_PROV_ST, does not exist.

What do you mean with your second sentence "consider building against the dialog maintenance via SE54" ?

Former Member
0 Kudos

It seems not so good to delete the package with any function module or an ABAP report, because deletion must be stored in the transport order to delete it also in Q and P systems.

0 Kudos

When the dialog maintenance was created via SE54, a database table existed with a text table. The dialog maintenance created or used an existing function group and created the "Definition of a Maintenance and Transport Object". (R3TR TOBJ - check existing entries in SOBJ, click on Obj. directory entry)

You deleted workbench objects via SE80 ?

Now SOBJ is not able to display the orphan object, it don't find the database table. Maybe you should recreate a dummy table with this name (removing the trailing S) delete then the object and then the dummy table.

A dirty way, would be deletion of records in TDDAT and TVDIR.... don't...but you can check this tabkle to check existence of records for this object.

Regards,

Raymond

Former Member
0 Kudos

rebuild of a dummy table with name ZZ_PROV_ST (without last S as original object from TADIR), than created a new maintenance dialog, than deleted the maintenance dialog and the dummy table. Release the transport request to Q, TADIR now is empty (only teh enty of development package itself exist). Now it is possible to delete the package.

Many thanks to all!

Kind regards

George

Former Member
0 Kudos

you can use txn code se14 which will delete total table entries or you write a simple program using delete statement   'delete tadir from ztable-fieldname'

good luck

'

0 Kudos

With SE14 I can't find the object.

Not so good to delete the entry only in TADIR with simple report, because in transaction SE03 I get the information, that object already exist.

0 Kudos

go to se10 find the request number and delete the object

0 Kudos

Hopefully you did not found the object, else you would have delete the definition of the database tab le behind...

0 Kudos

The object is not listed in my or in any other request.

The problem is, that I can not find the real object in system, relating to the TADIR entry

R3TR TOBJ ZZ_PROV_STS

but if I want to delete the entry in TADIR with Tcode SE03 I get the message that the object already exist.

0 Kudos

I've deleted all tables of the package, also all views and all other objects.

With SE84 I get also no ddic objects if I search for ZZ_PROV* or ZZ_PR*, searched in all possible selections.

0 Kudos

if function group is assigned check it in  table TLIBG and delete from there also