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

Renaming custom objects, what object types cannot be renamed?

Former Member
0 Likes
1,412

I have a task to basically copy a custom development from environment A to environment B. These two SAP environments (A and B) are not linked and I cannot use transports to bring the objects over so I'm hoping to use the SAPLINK tool to export the objects from A and then import to B and activate.

Our SAP project naming standards/conventions for custom objects is different for environment B. For nealy all the objects I'm bringing over, I'll have to also rename them to match the standard.

The object types I have to move are:

table

domain

data element

enhancement

function group

function module

message

class

class definition

method

parameter

program

transaction

Business Add-Ins Implementation

Customer Enhancement

report source code

report text

I've been told that a large percentage of the ABAP object types can be renamed but I don't know which ones cannot, so my question is what ABAP object types cannot be renamed once they're created? I hope, as I said, to use the SAPLINK tool to export the objects from environment A and then import to environment B. I'd only have to manually re-create the object types that cannot be renamed, if I knew what those types are.

Thanks for any and all help!

Carolyn Caster (c2)

1 ACCEPTED SOLUTION
Read only

matt
Active Contributor
0 Likes
1,173

When I wanted to bring in abap2xlsx to a validated system in a multinational company, this issue raised its head. The solution was to get an exception signed off by the Head of Development on the grounds that:

1) Bulk renaming/copying was considerable effort for no purpose other than the bureaucratic "it satisfies our naming conventions".

2) Future releases would be easier to handle if the objects were not renamed

The way to find out what is renamable is easy. Go to the appropriate object editor (or SE80) and look for a rename option! Five minute's effort at the most.

4 REPLIES 4
Read only

RaymondGiuseppi
Active Contributor
0 Likes
1,173

With help of basis you can copy transport request between two systems not sharing common transport directory.

You have to download/upload some files from DIR_TRANS. Use search tool to identify documents/wiki as How to download / upload transport request from / to a server or How to download / upload transport request from / to a server

Also most objects that can not be renamed can be copied, but you have to update their reference in other objects.

Regards,

Raymond

Read only

0 Likes
1,173

Thank you, I'll investigate these links.

Read only

matt
Active Contributor
0 Likes
1,174

When I wanted to bring in abap2xlsx to a validated system in a multinational company, this issue raised its head. The solution was to get an exception signed off by the Head of Development on the grounds that:

1) Bulk renaming/copying was considerable effort for no purpose other than the bureaucratic "it satisfies our naming conventions".

2) Future releases would be easier to handle if the objects were not renamed

The way to find out what is renamable is easy. Go to the appropriate object editor (or SE80) and look for a rename option! Five minute's effort at the most.

Read only

Former Member
0 Likes
1,173

Thank you, I've brought this up with the 'powers that be' and perhaps logic will prevail.