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: 

Transport Basics

nikhil_bose
Active Contributor
0 Kudos

Hi All,

I have few questions on Transport Request in ABAP.

1) How to do we handle requests numbers when deleting an object from data dictionary and creating those with the same names?

2) could both delete and create entry be put into single request?

3) what does happen in the target system when a request contains deleted objects is released?

Nikhil

1 ACCEPTED SOLUTION

Former Member
0 Kudos

HI,

To Delete a Request, you have to delete the sub-objects first from it, then Object, then Child Request and then Parent Request.

Secondly, Need not to delete the request, but you can use the same for new object creation.

In Case of customization, many times object is first crested, then deleted and then re-created.

So all of these changes can be stored under same objects.

It does not make any wrong impact on system as per the sequence of object creation.

But as per the zero risk factor, it is suggested to create a fresh request for the final object.

If Same Request including deleted object goes to target system, it could create problem during transport, like object not found and during use of the object in target system, wrong results could occur.

Regds,

Anil

2 REPLIES 2

Former Member
0 Kudos

Hi,

1) If you refresh your development environment every x period eg. by your production environment you can delete your transport request. Otherwise you can better transport your requests.

2) yes, this is possible.

3) see 2, but never release a request with deletions which are not in the receiving system. These transports will fail.

Succes

Former Member
0 Kudos

HI,

To Delete a Request, you have to delete the sub-objects first from it, then Object, then Child Request and then Parent Request.

Secondly, Need not to delete the request, but you can use the same for new object creation.

In Case of customization, many times object is first crested, then deleted and then re-created.

So all of these changes can be stored under same objects.

It does not make any wrong impact on system as per the sequence of object creation.

But as per the zero risk factor, it is suggested to create a fresh request for the final object.

If Same Request including deleted object goes to target system, it could create problem during transport, like object not found and during use of the object in target system, wrong results could occur.

Regds,

Anil