Transporting ABAP to different version system

[sap_cohort]

Hi, I have some ABAP Code (Function Module Changes) in my 7.0  BW System and I would like to transport/import it into my 7.3 BW System.  I would need to manually import the file into my 7.3 system because i do not have an available transport path. 

Would the different system versions prevent the transport of simple abap from importing?

[sap_cohort]

Hi, I have some ABAP Code (Function Module Changes) in my 7.0  BW System and I would like to transport/import it into my 7.3 BW System.  I would need to manually import the file into my 7.3 system because i do not have an available transport path. 

Would the different system versions prevent the transport of simple abap from importing?

[edgar_nagasaki]

Hi Keneth,

Only scenario I see where you could have issues is when you have Unicode x Non-unicode systems involved but I think this is not the case.

Regards,

Edgar

[Former Member]

Hi Kenneth,

Recently we have upgraded our system from EHP 4 to EHP6. Other then this our earlier development system was non-unicode where as the new one is an unicode system.

Let me share you what are all the major problems we faced with these

1. Function modules that are called inside our simple custom FM are changed. For example FTP_CONNECT is a FM that we use to connect to FTP and save some files and all. Earlier in that standard FM we just need to pass the host name, user id and its password. Even now we pass the same thing, however SAP has enhanced this FM and it looks for a table(m sorry i missed out the name) That table does not exist in older system, So we have to manually identify the situation and need to inser values into the table(done by our Basis Genious).

2, Major impact was Unicode system itself. For example dd03m is a table that stores the value for meta data of a table-field. Let me tell you how it works. Assume there is an 8 character long string. Now typically in Non-Unicode system it takes 1 byte for each character. So total 8 bytes. Now in unicode-code system it use to take 2 bytes for each charcater, Hence 16 bytes. dd03m was copied from the old system, hence it was 1 byte so some of our Custom search helps got wrongly aligned. So we went into each table and reactivated them which finally updated dd03m with correct 2 byte character value..

Just for an analysis purpose you can check transactions SPAU and SPDD. but that is to be done before UAT for the new system. However transactions are worth a try.

HAPPY ABAPing

[Former Member]

Hi,

I dont think there would be any issue as both are latest version with a difference of few additional components.

But this will not affect the code writeen in lower version going to higher version.

Feel free to go ahead and do the import.

Regards,

Amit

[sap_cohort]

Thank you for the detailed reply!  Sounds like a non-issue unless going from a non-unicode system to a unicode system.  Thanks again!