Application Development and Automation 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: 
Read only

Package check error after object deletion

former_member246634
Active Participant
0 Likes
3,655

Hi experts,

I'll try to describe my problem as good as I can:

I've activated service interface in SPROXY so in my package were created data elements and class. Unfortunately I had to delete those objects. While deleting Service Consumer from SE80 I chose "Delete root" option instead of "Show used". All generated structures, tables and table types were deleted and are no more visible in SE80. Later I ran package check and I got some errors like in picture below:

And here's the screen from SE10:

As you can see table types were not marked as deleted. And my question is: should I be worried while moving transport request with those object to QAS?

Rebuilding object lists didn't show those "deleted" objects, they are not visible in SE11 (object ... does not exist. Check name).

I'd be grateful for any answers

Bartłomiej

1 ACCEPTED SOLUTION
Read only

RaymondGiuseppi
Active Contributor
0 Likes
2,389

When you will release the transport request, the system will check If the object does not exist, in this case the system will output a warning that the object is transported as a deletion, the delete icon will appear in SE10 and the TADIR entry be removed. As those do not exists in  target system, no problem should raise.

Regards,

Raymond

Hello, Bartlomiej!

Deleted objects remains in the TADIR table until transport request is released.

Try this:

4 REPLIES 4
Read only

RaymondGiuseppi
Active Contributor
0 Likes
2,390

When you will release the transport request, the system will check If the object does not exist, in this case the system will output a warning that the object is transported as a deletion, the delete icon will appear in SE10 and the TADIR entry be removed. As those do not exists in  target system, no problem should raise.

Regards,

Raymond

Read only

0 Likes
2,389

Before releasing the transport request you should aggregate it to have a distinct list of objects. This avoids still having the error if in the transport request the creation and deletion of the object is included.

To do this, open the transport request in edit mode and execute the menu point Request/Task -> Object List -> Aggregate

Read only

former_member246634
Active Participant
0 Likes
2,389

Thanks guys, I did what you suggested and everything was fine. In transport request log there were messages about those non-existing objects:

"Object not found; object also deleted in target system".

Also, there are no errors during package check.

Thank you very much,

Bartłomiej

Read only

0 Likes
2,389

Hello, Bartlomiej!

Deleted objects remains in the TADIR table until transport request is released.

Try this: