Import 4.6c transport into ECC 6.0

[Former Member]

Hello,

I have transport files created in 4.6c version of SAP containing ABAP objects. What is the procedure to import it into a ECC 6.0 development system?

Thanks in advance.

Pankaj

[Former Member · Accepted solution]

HI Pankaj,

It may be possible or may not be possible.

Depending upon your request , if same dictionary objects are available in both the releases(4.6c and ECC 6.0) you can do it as usual transport.

Add to STMS queue manually in DEV and then import, but if there is difference in structure then its not possible to import.

Regards,

[Former Member · Accepted solution]

Hi,

Thanks for the input.

The objects do not exist in the new system. The transport is to create fresh objects. Is it possible ?

How do I add them to the STMS queue manually? Do you mean adding it at the OS level?

Best Regards, Pankaj

[Former Member · Accepted solution]

Hi,

Is this all about Z* development or it is something related to SAP standards.

There are number of thing to consider before importing to DEV.

Any how i suggest you to import into some sandbox client first and then analysis.

Manually Adding:

1) Get co and data file for trasnport request(Basis person must know about this)

2)Copy both of these to corresponding data and cofiles directory of target system

3) Go to STMS queue of target system

4) Extra>other request>add

5) Provide the request number and then finally import

6) Check for warnings

Regards,

[Former Member · Accepted solution]

Hello,

All z* objects but they were created in 4.6c that need to be brought into ECC 6.0. I do have access to a sandbox system.

Any other thing I need to be careful off?

Thanks, Pankaj

[Former Member · Accepted solution]

Hi ,

If its Z* and its dependant dictionary objects(i am not a abaper so cant tell exactly) are available.

Its best to import to sandbox first and then analyze.I cant see any risk to import this request into sand box that is why it is there...

Hope it will go through..

All the best..

Regards,

[Former Member · Accepted solution]

Hello Pankaj,

You need to throughly check that any of the objects are making references to any of the standard SAP objects.

Not only this you need to also consider unicode/non-unicode compatability in ase 4.6C is non-unicode whilst ECC is unicode.

Regards.

Ruchit.

[Former Member · Accepted solution]

Hi Ruchit,

Thanks. The objects in the transport are z* objects. However they may be calling standard function modules. Does that affect the scenario?

Thanks, Pankaj

[Former Member · Accepted solution]

Hello Pankaj,

On of my colleagues faced a similar scenario. He did transports from a lower version non-unicode system to as higher release unicode box and the transported bombed because of unicode/non-unicode incomptability of standard objects.

When transport gets vimported objects get generated and most likey SAP would reject a non-unicode object in unicode environment calling a unicode standard object or for that matter the import of a non-unicode object itself in an unicode environment.

Other than that other issues might also occur.

Regards.

Ruchit.