Backup BOR object, not just the code, how

[Former Member]

Hello all,

I know that I can use the version management from transaction SE38 to save a version of the business object code. But I haven't found a way to systemically make a version of the events, or parameters of the business object.

Short of going through each method and finding out what it's parameters and exceptions are, and documenting them, what are people doing?

We have some changes that have been made to a business object a couple of years ago. Now some different changes need to be made to the business object, but we don't have time to test all the previous changes so we want to take them out and be able to put them back in after these new changes have been made and moved into production.

Yeah I know that changes should not be left lying around for two years before being moved to production. Higher priorities kept bumping the testing of these two year old changes.

Thanks

Bruce

[Former Member]

Hi,

To my understanding from the transport perspective of a Business Object(Not the program behind), it is always considered as a Repository object for transporting. In other wordsany changes to the business object attributes, events, or parameters will be saved to the transport as a R3TR, with the object ID SOBJ. For transporting it means that, the entire business object is transported to the new system. There is no LIMU(sub object\ changes only) transport for BO.

May be in your case you may need to either revert back all the previous changes and add your current changes to the BO and transport .. OR as you said... test the old changes along with the new one...

Cheers,

Thomas.