Transport package to customer system; wrong source system?; avoid using modification assistant

[cfb]

Hello,

we'd like to transport a development (for Solman respectively)  from our system the the customer system. Now we've put the entire package into one transport via SE80-> rightclick on the package and selecting "write transport entry".

We then released this TR and copied the file from the DATA and the COFILES folder into the customer systems respective folders within TRANS. We imported the TR via "add other requests" (STMS) but we still need to do some adjustments to the code now.. but since the customer system still sees our development system as source system.. we can only use the "modification assistant" and this is not a feasible solution.

So my questions  are..

a) if my approach is correct so far.. what do i have to do in the customer (foreign) system to give me full access to the development environment (and not just the "modification assistant")?

B) if it's not... how to properly transport a TR to another system outside the transport route.(a customer system for example)

best regards

Chris

[ThomasZloch]

The basic question is: what should be the correct original system for these transported objects?

1) still your original development system

-> apply changes using the modification assistant (which you do not want), or switch off the assistant (from the ABAP editor menu)

2) the customer's development system

-> the original system of the objects must be changed to the customer's system, use SE03 "change object directory entry" for this, select by old system ID or package, mark the entire tree, type "MASS" in the action box and enter the new system ID

Thomas