How to transport a program to customer systems

[roland_spindler]

Hello,

We have developed a program within our own namespace. We want to transport this program to different customer systems.

What we can do is export the transport request and import it at the customer systems. Then there will be different change request from each customer, so we have to change the original system of each object, before we can change anything. (This can be done manually with a lot of work, or with a dirty Z-program.)

Is there a better way to transport a program to a different system in a way that it can still be changed there?

kind regards

Roland

[Former Member]

Don't change manually objects in destination systems.

Include all objects affected by this program in your transport request (manually) and transport it together to destination systems.

I think that should do the trick.

kind regards,

Mario

[roland_spindler]

Yes, like I said, we already do that.

But the problem is that the original system stays the same, so we cannot change the objects on the customer system.

[Former Member]

Did you check that all related objects have been included in that transport request?

Since you will manualy include that objects it shouldn't be important if they aren't changed.

[roland_spindler]

The problem is not that objects are missing, but that they cannot be changed.

Anyway, Thomas already answered my question.

[ThomasZloch]

You can mass-change the original system using standard SE03 transaction, "change object directory entries", by marking the relevant entries (or even an entire tree) and entering "MASS" in the action box.

Thomas

[roland_spindler]

Wow, a hidden feature.

Strange that there is no button or menu button for a very useful functionality...

[raymond_giuseppi]

Relocation and update of original system, like SE03 'Change Object Directory Entries of Objects in a Request' option will do the job, but why don't you provide some BAdI in your program ?

Regards,

Raymond

[roland_spindler]

That would work for minor changes, but some customers want to change major features of the program. That would be cumbersome using BAdIs.