Copying $TMP local objects to another system

[Former Member]

Hello all,

I did a dump of table TADIR in our production system on DEVCLASS $TMP and got a list of many local objects.

We want to bring these back into our dev environment so they can be corrected and have our landscapes be consistent. I know local objects are not transportable, so is there a way to do this besides either a DB copy (homogenous system copy) or creating the objects manually in DEV?

Any help would be greatly appreciated.

Thanks.

[vijaymanikandan]

Hi

Yo u can do this in many ways.

1. Go into every object and reassign the object to a z package and include them into a Transport request in production and import the same in your development system.

2. Decide the Package that you are going to use. Now go to transaction SE03 and under Object Directory there is an option Change object Direct Entries and you can enter the package there.

3. Another way is go to SE16 and enter TADIR and enter all your objects. Next you can change the package there directly in change mode. Then you can go to SE03 and include all these objects manually into a transport request in SE03.

Note: In case there is any Table maintenance generator you need to take of that as well.

BR,

Vijay V

[Former Member]

Thanks Vijay,

I have suggested to our ABAP team to place these in a transport so they can be moved and tracked. Thanks for your input.

[ThomasZloch]

Are you sure this is stuff you want to move to development? I don't have system access right now to double-check, but I remember a lot of these $TMP objects are generated dynamically, e.g. based on ad-hoc queries, report painter, SE16, validations/substitutions, etc.

If your production system was always closed for changes to repository objects (like it should be), then there should be nothing to be transported back to development.

Thomas

[Former Member]

Hi Thomas,

Excellent point! Unfortunately, our PRD system was allowed to be wide open for changes in the past, so even though most of these $TMP objects are probably junk, some need to be evaluated and possible fixed in DEV to avoid any inconsistencies. (We are doing this as a precautionary measure before an upgrade project).

Thanks.