cancel
Showing results for 
Search instead for 
Did you mean: 

4.6B Migration+Upgrade -> ECC6 Discussion

Former Member
0 Kudos

We will be upgrading from 4.6b on a Windows/SQLServer platform to ECC6.0 on a Unix/DB2 platform. The first step in this process is a migration to the new OS and RDBMS.

I would like to discuss the potential pitfalls of the migration to Unix and DB2 here. Perhaps you've been through this process and can give me some input on what to watch out for? I already know of a number of things that will break due to EXEC SQL use.

Thanks for any input.

Accepted Solutions (1)

Accepted Solutions (1)

markus_doehr2
Active Contributor
0 Kudos

OS migrations are more or less painless beside the fact, that most "Unix" operating systems are using a different endianess (aside from Solaris on X86_64). For RFC and other SAP proprietary communication this is done in the kernel but if you use own software to read BINARY data (not talking about textfiles) you need to take care of that in your software.

--

Markus

Answers (3)

Answers (3)

Former Member
0 Kudos

Thanks for the input. To the question about 4.6b being able to upgrade directly to ECC6, I'm told the answer is yes. We had planned on doing a homogeneous upgrade (same OS/same RDBMS) at first and it was going to be one step only. Corporate IT wants to host the box and is dictating UNIX and DB2 hence the two-step migration+upgrade.

Here are a couple of things that I'm concerned about.

1. We have applications (VB6/ASP) that read SAP tables directly. Syntax differences and the need for a new ODBC link might cause issues.

2. Batch jobs write to Windows server locations using a UNC address like
server\folder\file.txt and I need to know if Unix can write to a Windows server using the same method.

3. VB6 apps use rfc calls into SAP. I hope that this one is stable moving from an NT backend to a UNIX backend. Since this is all through the GUI's rfc libs on the PC, I would think it would be ok.

4. Several SAP batch program read/write external DBs using ABAP's CONNECT syntax. How does ODBC access work from a UNIX box to Window's based SQLServers?

Most of my concerns are based on a lack of experience with UNIX in general. I've been using Windows based servers since 1988 and only worked with Linux a little these past few years.

Thanks for the input. I appreciate you all taking time to help me build a comfort level for this upgrade.

Former Member
0 Kudos

Dear Crew,

It is not the direct answer of your question but while upgrading you might need them.

Please visit the following links:

http://service.sap.com/erp

http://solutionbrowser.erp.sap.fmpmedia.com/ (Functional prespective)

http://service.sap.com/instguides --> mySAP Business Suite Applications --> mySAP ERP --> mySAP ERP 2005 --> Upgrade

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf

For Functionality Differences pls refer to the below site -

http://solutionbrowser.erp.sap.fmpmedia.com/

After opening the site, please select the Source Release Version which is 4.6 b Then Select the Target Release Version which is "mySAP ERP 2005" or ECC 6.0

Select the Solution Area like Financials, Human Capital Management, Sales....

Select module like MM, PP, SD, QM.....

Click on Search

Then it displays the Release Version and the Delta Functionality. which can be downloaded to a word document if required.

and also check the release notes of ECC 6.0 in service.sap.com.

Hope this helps you.

Do award points if you found them useful.

Regards,

Rakesh

RamBilasYadav
Participant
0 Kudos

Hi,

I am a sales person for SAP and am new to it.

I would like to know if a direct upgrade from 4.6B to ECC 6 is possible? If not what would be the path of upgradation.

Thanx in advance.

Regards,

Rara