Transport objects from 4.6C to ECC 6.0?

[Former Member]

Hello,

I have developed some custom z-tables and an application in ABAP / Screen Painter on a 4.6C server. Is it possible to transport these to an ECC 6.0 system? Otherwise I will have to recreate everything on the ECC 6.0 server. Help is appreciated, thanks.

Regards

[andrea_olivieri · Accepted solution]

Hello,

you can transport custom objects between different releases without any problems.

Consider that after the import in ECC you should perform adjustement of those objects, i.e. ...your screen painter uses a standard object that no longer exists in ECC...

Thanks .

Kind regrads.

Andrea

[markus_doehr2 · Accepted solution]

> you can transport custom objects between different releases without any problems.

I wouldn't sign that.

There are syntactical differences in ABAP as well as your objects may refer to standard DDIC objects that may not exist any more...

Technically it may work but that doesn't mean that the application works as expected.

Markus

[andrea_olivieri · Accepted solution]

Hello Markus,

thanks for the reply.

You're right, but in my opinion this type of transport is part of the normal activity of double-maintenance of an upgrade project where in some cases you have to handle the alignment of thousands of custom developments that becomes productive montly.

In my experience I have handled with success the transport of custom objects from a productive landscape (rel. 4.0b) to an upgraded development system (rel. 4.7) where the jump is much larger and where the adjustment of post-import required only a few minutes.

The question is: it takes more time to completely redo the program directly in ECC or make the transportation from the old release and fix errors in ECC after import?

It 'possible that in the case of Khan, the custom screen-painter doesn't work properly or gives syntax error due to some obsolete ABAP instructions, but this is part of the game....

Ciao.

Andrea

[Former Member]

Hello,

SAP note 1090842 deals with the subject of transporting between different SAP releases. This note contains pointers to further releas-specific notes.

A general rule:

- SAP objects: must never be transported (I think this is obvious)

- Customizing: must never be transported (not supported)

- Own (Y,Z) workbench objects: physically these can normally be transported without problems, in the sense that they will not corrupt the system. Whether they will work will of course depend, e.g. dictionary structures might have changed, ABAP syntax checks might be more rigorous, etc.

Regards,

Mark

[_IvanFemia_]

I Khan,

I'm agree with Andrea, you could transport the objects to the new release and then make the adjustments (in many cases are very simple adjustments).

Regards,

Ivan

[Former Member]

Hi Khan,

Have you saved all your custom tables,applications with valid package and Transport request. If so there is no doubt in it to transport from lower version to higher. Make sure that ur developments/modifications should done with valid package and Transport request.

Regards

Arani Bhaskar