cancel
Showing results for 
Search instead for 
Did you mean: 

Transport System

Former Member
0 Kudos

Hi,

I need help we are planning to upgrade our R3 to ECC 6.0 and our first step is to create a 4.6C Development system to support the 4.6C Production system. We did a copy of our Production system and configure our transport system and now we cannot change Z programs we received this message "Carry out repairs in non-original system only if they are urgent".

Thanks,

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi,

We create a new development system to support our Production 4.6C every time we created a new programs or changed the old programs the transport request showing Local change request and when we released the request it doesn't create a data file or cofile.

We have created a new transport route and virtual system but using the same transport layer.

Thanks,

Former Member
0 Kudos

Hi Ramon,

local requests ALWAYS do not create datafiles ... they are designed for the "last system" in your landscape or for customers with a single system landscape only.

Therefore, you should typically do not use a virtual system but include it to PRD. But, the virtual system is a nice workaround as well, because this creates then the datafiles and you can use "add to buffer" and import it in PRD - unfortunately you need to be careful with this technique, because you could forget transports ...

as it is an emerngy stuff only, it should be ok.

Regards

Volker Gueldenpfennig, consolut.gmbh

http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

Former Member
0 Kudos

Hi Ramon,

if you need the system copy only for a schedduled period, you should not change the original-system. Because when the original system of the objects is changed, you will have similiar problems after upgrade scenario is completed.

You should think about Transport Layer, it is usual Z<SID>. Just add the transport layer of the objects to be "repaired" to your transport routes. So you will have one consolidation route with three layers: SAP, Z<SID_NEW> and Z<SID_ORG>.

With this changes you will have only one original!!!

By changing original system you will have teo originals in your system landscape, what is not recommended!

Regards

Guido

Former Member
0 Kudos

Hi Ramon,

Those messages are kind of "normal" because they are telling the truth.

We run Tcode SE06 - Database copy - yes - yes - yes after each database copy, then reconfigure TMS from client 000. After that developers can change Z programs (maybe just ignore the messages).

Good luck,

Victor

Former Member
0 Kudos

Could it be that these z-programs have been created on another SID than the new development system? If so you can run a small program to change the origival system - to avoid this message. Let me know if you need the program. Then I can send it.

Regards

Flemming