Well, once you finally get to the phase of creating a namespace and making yourself a program, inevitably, things change. In my case, I joined forces with a partner, created a new company and started moving forward. So, in order to keep things keep everything consistent, I had to generate some new namespaces. The problem is that you can’t simply rename things for a new namespace, you have to copy each component to the new namespace, then delete the existing stuff. Of course, the fun comes in the sequencing.
In order to start everything, I recommend using transaction SE80. Since a namespace is generally associated with a package, the easiest way to pull everything for a particular package. This will give you everything associated with the namespace. Initially, you I suggest just copying everything. For this piece, it doesn’t matter the sequence.
Once everything is copied, now is where the fun part begins. Go back to the original namespace pull up all of the objects. Typically I go through and start with the highest level objects. This will include any programs, web dynpro objects or BSP objects. For each object, do a where used to make sure it isn’t included anything else, if the where used list is empty, then I’ll delete the item. Next I move to functions and function group. Then I’ll move onto the data dictionary objects. Starting again with the highest level tables and table types. Then move down the chain to structures and finally data types.
It’s not a simple task, and can be rather tedious… but at the end of the day, you can move from one namespace to another with very little risk, and just a little bit of time.
Thanks for reading,
As always, thanks for reading and don't forget to check out our SAP Service Management Products at my other company JaveLLin Solutions,Mike