SAP Upgrade from ECC 5.0 to ECC 6

Hello All,
We are planning for an upgrade from ECC 5 to ECC 6. As some obsolete statements like "Use of header line" is no more supported in ECC 6, do we need to manually change in all custom programs and FMs? Or is there available a tool to do so? or will SAP as part of the upgrade do the necessary. Because this is a huge effort
Thanks in advance for your response
Anirban

Hi,
It has to be manually done for each and every program.
Probably your company can check if there are any third party vendor tools that does the conversion, but anyways someone has to manually check the programs and test all of them.
Regards,
Subramanian

Similar Messages

BI 7.0: Source System upgrade from R/3 Enterprise to ECC 6.0

Background:
I am relatively new to BW team and will be going through my 1st source system upgrade.
We currently have BI 7.0 SPS 17 connected to source system R/3 Enterprise EP1.
We are upgrading to the source system to ECC 6.0.
In Development and QA Environments:
we will have access to both old (R/3 Enterpirse) and the new (ECC 6.0) source systems.
We have a opportunity to compare the BW Objects, data flow and data loading from
both source systems.
In Production, however, we will just upgrade over 3 days downtime.
One Question that comes to mind in this regard...
What sort of things, we should be checking for before and after upgrade in Dev/QA and in Prod environments and what tools are available that can help the analysis and validation process ?
Some of the suggestions that were given to me include following points.
Before Upgrade:
1 Check data, taking pre images of it for testing with post upgrade.
2. Perform proper analysis of Source system related BW objects.
- A complete listing of actively used Datasources,.. etc.
3. Make delta queues empty,
Make sure that all existing deltas are loaded into BW.The last request delta must not deliver any data and must be green in the monitor.
4. Stop Process chains from BI (remove from schedule) and collection runs from R/3 side
After Upgrade:
1 After the OLTP upgrade, refer to note 458305 and other notes that are relevant to the actual upgrade
(depending on the R/3 system release / R/3 plug-in to BI plug-in compatibility).
2. Check logical system connections. Transactions SMQS, RSMO and SM59, If no access, then we can use Program RSRFCPIN_NEW for RFC Test.
3. Check and/or Activate control parameters for data transfer. SBIW ---> General Settings --->
Maintain Control Parameters for Data Transfer
http://help.sap.com/saphelp_nw70/helpdata/EN/51/85d6cf842825469a51b9a666442339/frameset.htm
4. Check for Changes to extract structures in LBWE Customizing Cockpit
- OSS Notes 328181, 396647, 380078 and 762951
5. Check if all the required transfer structures are active. See OSS Note 324520 for mass activation.
7. Check if all Source system related BW Objects are active - Transfer rules, Communication rules, update rules,DTPs,..etc.
Below is a link for some useful programs in this regard.
https://www.sdn.sap.com/irj/scn/wiki?path=/pages/viewpage.action&pageid=35458
6. Test all important datasources using RSA3 and check for OLTP Datasources changes .
As soon as BW notices that the time stamp at the DataSource in the OLTP is newer than the one in the transfer structure, it requests replication of the DataSource and activation of the transfer structure. Transfer the relevant DataSources only if required, and transfer only the ones that have changed (RSA5 -> Delta).
7. Create Data flow objects (trnasfer rules, infopackages, trnasformations, DTPs) for the Replicate
new/changed datasources,if needed.
8. Check all CMOD enhancements.
If we are using a customer exit with the extractor in the OLTP, see Note 393492.
7. Check for unicode (all custom programs or Function Modules for DataSources)
5. Check all the queues in RSA7, start delta runs and test data consistency.
For delta problems:In the BW system, start the 'RSSM_OLTP_INIT_DELTA_UPDATE' program for the DataSource and the source (OLTP) system for which the init selections are then transferred from BW into the ROOSPRMSC and ROOSPRMSF tables in the source system so that the delta can continue.
9. Take back up of data posted during upgrade for contingency planing.
10. Run the entire set of process chains once if possible and let it pick up no data or the usual master data.
Since we have lot of experts in this forum, who have probably gone through such scenario many times, i wanted to request you to Please Please advise if i have stated anything incorrectly or if i am missing additional steps, OSS Notes, important details...

Thanks Rav for your detailed post and very helpful contribution by posting all the information you had regarding the upgrade.
We have similar scenario -
We are upgrading our source system from 4.7 to ECC 6.0. We have our BI system with BI 7.0 at support pack 19 (SAPKW70019).
Our strategy in ECC deployment ->
In development we copied our old DEV 4.7 system DXX to new ECC system DXY (new system ID).
In production we are going to use same system PRXX upgraded from 4.7 to ECC.
Now we are in testing phase of ECC with all interfaces like BI in Dev.
My questions are below ->
How can we change/transfer mapping of all our datasources in Dev BW system BID to new ECC dev system DXY (Eg. Logical system LOGDXY0040) from Old dev system DXX (Eg. Logical system LOGDXX0040). We donot want to create new datasources or change all transfer rules/Infosources for old BW3.x solutions on our BI.
Also in new ECC sourcesystem copy we see all datasources in Red in RSA7 transaction. Do we need to initialize again all the datasources from our BW BID system.
Is there any easy way for above scenario ?
Please let me know if you have any further helpful information during your ECC 6.0 upgrade connecting to BI 7.0 system.
I have found some other links which have some pieces of information regarding the topic -
Upgrade R/3 4.6C to ECC 6.0 already in BI 7.0
http://sap.ittoolbox.com/groups/technical-functional/sap-bw/sap-r3-migration-and-sap-bw-version-1744205
BI 7.0: Source System upgrade from R/3 Enterprise to ECC 6.0
Re: ECC 6.0 Upgrade
Re: Impact of ECC 6.0 upgrade on BI/BW Environment.
ECC 5.0 to ECC 6.0 upgrade
Thanks
Prasanth

Issues during technical upgrade from version 4.6C to ECC 6.0

Dear All,
We have done a technical upgrade from version 4.6C to ECC 6.0 and encountered following issues -
In the t-code ABZE (acquisition with in house production) there is a check-box for reversal posting on screen with version 4.6C. However, this field is missing in ECC 6.0. Why so?
In the report s_alr_87012327, there is a field "only with creation block" in version 4.6C. However, this field is missing in ECC 6.0. Why so?
Request to kindly suggest the alternative to carry out the same in ECC 6.0.
Thanks in advance.
Regards,
Dhawal

Hi Akshya,
Please find answers below.
1) 4.6c is NON-UNICODE system, Can I upgrade it into ECC 6.0 UNICODE system?
Yes you can.
If you are on a single code page system then you can give a gap between your uprade and unicode conversion. There is no problem with the singlecode upgrade and conversion.
But if your system is MDMP then you will have to do the CUUC method that is both upgrade and unicode conversion together. Though you can give a gap and sign an disclaimer with SAP it is still not recomended way.
2) 4.6c does not have any ITS system installed. If we upgrade it to ECC6.0 ABAP only, then Can I activate WAS internal ITS?
Yes you can activate it.
3) 4.6c does not have any JAVA stack. When I upgrade it to ECC 6.0, can I upgrade it to dual stack (ABAP+JAVA)? If yes, then how?
After the upgrade and unicode conversion you can install the java stack.
Regards,
Ravi.

Upgrade from 4.6 B to ECC 6.0

Hi Gurus,
Well and I would like to inform to our gurus that currently we are in the Phase of upgrading form 4.6 B to ECC 6.0
I this regarding, can any one of our Guru's guide me regarding the following doubts.
1. How to do Upgrade from 4.6 B to ECC 6.0?
2. If you have any documents in this regard?
3. Do you have any documentation for ECC 6.0?
I request you to kindly forward the information to mail id: [email protected]
Thanks with regards,
Bala

Hi,
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.
Please assign points if it useful.
Regards
Ravinah Boni

Role of Time Mgmt functional consultant during SAP Upgrade from 4.7 to ECC6

Hi,
Could anyone explain the role of a time management functional consultant during SAP upgrade from R/3 4.7 to ECC6.0. Please provide me if you got any documentation.
Thanks,
Sunny

"After you upgrade to SAP ERP 6.0, you can enhance the functionality of your application without performing a further
upgrade thanks to a new deployment technology u2013 the SAP enhancement package for SAP ERP. The enhancement
packages simplify the way you manage and deploy new software functions for SAP ERP." - that is the real benefit of ECC 6.0
There aren't any major changes to PTM functionalities from 4.7 to 6.0. I hope your system is already using IT 2006 instead of IT 0005. Under functional role, you are required to configure/test any functional upgrade and manage data.
Regards
Yash

MB_DOCUMENT_BADI - SAP R/3 release upgrade from 4.7.1 to ECC 6

Once finished upgrading from SAP R/3 4.7.1 to SAP ECC 6, from SPAU I see that there was no problem on the implementations of this BAdI. But when I tried the transaction, where this BAdi was implemented in, I realized that my implementations were not working. In addition, from SE19, I see that these implementations are active, so why they aren't working?
I think that there are some problem in BAdI implementations when upgrading SAP release, but I don't know how to solve my problem and turn on my implementations.
Thanks,
Luca

Hi Sunny,
i continued with the option - without ADD ON.
So, this mount point and ADD ON dvd issues are over.
In the next screen, i have to specify the xml file and place the packages under EPS/in. I have done that accordingly and now i get a new error - No matching SAINT package for 'SAP_APPL' found.
Any ideas where i have done wrong?
Thanks,
Mohan.

SAP Upgrade from 4.7 to ECC 6.0 connected to BW 7.0 Best Practices

We are upgrading SAP R/3 4.7 to ECC 6.0. We have been running live in a BW 7.0 environment. We have done some enhancements for 2LIS_11_VAITM - Sales Document Item Data and 2LIS_13_VDITM - Billing Document Item Data datasources. We currently have a test instance that has been upgraded to ECC6.0.
What are the best business practices for testing BW to insure data transfer and enhancements are working correctly?
Eg. Should we connect the ECC6 instance to BWD and test there OR upgrade R/3 TST that is connected BWD and test there OR Upgrade QAS and test in BWQ.
Thanks in advance . . .
Edited by: RWC on May 4, 2011 6:26 PM

Hi RWC,
the plug-in will change slightly, you may notice differences in the screens of RSA2 and others after the upgrade.
Regarding best practices: In a recent upgrade our project team decided to create a parallel landscape with a new, additional Dev and QA on the R/3 side.
We connected these new systems to a BW Sandbox and the BW QA.
We identified all datasources, transfer rules and infopackages in use in production and recorded them with related objects onto transports in BW Dev. Before the import into BW Sandbox and BW QA we adjusted the system name conversion table to convert from old R/3 Dev to new R/3 Dev in order set up all the required connections for testing with the upgraded R/3 systems.
After the go LIVE of the upgrade we renamed the old R/3 Dev system in BW Dev and ran BDLS to convert everything (speak to your Basis team). That way we made sure not to lose any Development and we got rid of the old R/3 Dev system.
Take a look at this post for issues we encountered during this project and test everything you load in production.
Re: Impact on BI 7.0 due to ECC 5.0 to ECC 6.0 Upgrade
Best,
Ralf

SAP Upgradation from 4.5B to ECC 6.0

Hi all,
We need to upgrade from 4.5B to ECC 6.0. Gathered all the information abt. the 4.5 B system...Its on AIX using ORACLE.
I want to know few more info. with your help. i have access to the system through GUI, but didnt have OS level access..
1.) How to know whether the system is CLUSTER configured, any transaction?
2.) I didnt find any Upgradation Guide particular to AIX, can u pls. guide me the path for that in SMP?
3.) How to check whether its using any third party tools(Like Fire Fighter...etc) and any usage types configured(Like PI, BI...)
please guide me in knowing the above through GUI?
Thanks,
Subbu

Hi,
Roadmap is the recomended way to manage the Upgrade project, but this will not make anything automatic. If you don´t have the knowledge and time to configure the project in Solman then just follow the Upgrade Guide. In this Roadmap is included Technical and Funtional processes and it is an excellent starting point for the project but as already said, if don´t have the knowledge or any other person from the team either, then don´t worry much about it althoug it is imperative that a good Project is designed before starting the process either using MS Project or any other software, after the first tests you will have to adjust times for next upgrades.
Buy the way in the upgrade guide there are some sections specially dedicated to AIX but most parts of the process are the same for any OS/DB combo. Basically check prerequisites, do prepare, fix what ever is necesary and then run upgrade process.
Read the Upgrade Guide 2 or 3 times to get a clear Idea on what should be done before, during and after the upgrade process, read all related notes and have them printed in case of any problem.
AND you should have access to OS level, if you don´t then when doing Prepare or Upgrade then you won´t be able to look at the logs and that is Vital during the process. Also need to have access to SAP directories to check and change files like copying upgrade DVD's, upgrading R3trans, TP, etc so explain that to them or make one of them to be next to you.
Good Luck

Regarding Upgradation From 4.6 C To ECC 6.0-Urgent

Hi all
can anybody let me know what is procedure to upgrade the SAP From 4.6 C To ECC 6.0 from MM and CIN point of view
--is Up gradation is just like an implementation or Enhancement process
any help would be appreciable
thanks in Advance
Edited by: JAM SAP on Feb 27, 2008 8:47 AM

Upgrading project mostly involves testing with the existing system with the new system.SAP already released the release notes for this Upgrading ECC 6.0.
(1). YOu have to do unit test/Integration test/Regression test in your new system based on the business process documents prepared for your present system.
(2). You mostly encounter Interface issues(If exist)/Authorization issues/Enhanced naming issues/Usage issues.
(3). In 46C you have to do external configuration for CIN.However In ERP 2005, It is already in built.Hence Knowledge of CIN will be more than sufficient to manage the CIN issues.
(4). More over you must be very confident in the business process.Unless you will receive many UAT issues.
(5). I strongly advice you based on my experience, Whenever you do unit test and Integration test, use your user id to.When you do regression testing, get the user id from user copy all the roles from the user id and create new id.Using this new id you do the Regression testing.This will avoid many problems.
(6). Another Imprtant big issue is patch work infomation.After release of 46C, SAP released many patches for 46C.However these patches are all not updated in to your present 46C system.These patches are already in in built in ECC 6.0, hence you will get diff.result when you do testing.If such a case, advice the user about the patch work, and proceed. In most of my cases , SAP enjoyed with 46C without patch scenario, but in ECC6.0 they started to complain, b'cas the new patches.
(7).Give me your mail id ,I will send you the release notes.
(8).Note down my forum discussion to know about the some of the issues.
Hopefully it will be helpful, Let me know, If you need more Information.Thanks
Reward If useful!

Tehnical upgrade from 4.6C MDMP to ECC 6.0 using CU &UC approach

Hi SAP Experts,
We are embarking on a project for Technical upgrade from SAP R/3 4.6C MDMP system to ECC 6.0 using the CU & UC approach for our Asian operations (comprising of India, Japan, Taiwan & Singapore).
Please share with me the Best Practices you followed in your projects, checklists, DOs, DONTs, typical problems you encountered and the possible safeguards, any other useful information, etc.
Since very little information is available from Organizations who have used this upgrade successfully, I am raising this in SDN to share your experiences during the Technical upgrade.
All useful information will be surely awarded with suitable points.
Looking for your invaluable inputs which will be a BIG help for our project.
Best regards,
R.Rajaraman

Pls go thru the below mentioned notes and its related notes
Note 928729 - Combined Upgrade & Unicode Conversion (CU&UC) FAQ
Note 73606 - Supported Languages and Code Pages
Note 79991 - Multi-Language and Unicode support of SAP applications
Note 959698 - Twin Upgrade & Unicode Conversion FAQ

Upgrade from 4.6 c to Ecc 6.0

Hi all,
We have R/3 on 4.6c with windows 2000 on 32 bit with Sqlserver 2000, we are planning to upgrade to Ecc6.0 and windows to windows 2003 with 64bit and sqlserver 2000 to sqlserver 2005
Can you plz guide me the the process of doing things like
which one i have to do like 32bit to 64 bit or windows to 2003 then bit upgrade then DB .
I have done upgrade on 4.7 to Ecc 6.0 does 4.6c upgrade to Ecc 6.0 is the same process...
Plz suggest...
Thanks,
Subhash.G

Hi all,
We have 4.6c and windows 2000 32 bit and sql server 2000 32 bit on 64 bit hardware.
On the same if we want to upgrade windows 2003 to 64 bit then sql server 2005 64 bit and 4.6c to ECC 6.0 what is the approach.
I have one approch please guide if i am wrong.
For OS Upgrade:
There is no approach to upgrade 32 bit windows 2000 to 64 bit windows 2003, we have Install the 2003 from scrath.
For Sqlserver:
We can use attach/detach methods, we have to install sqlserver 2005 64 bit with correct collation Bin2 and attach the DB .
For SAP upgrade:
Install the 4.6c or restore the file system , since we have the DB , replace the kernel with 4.6D 64 bit then do the upgrade.
Please correct the approach if it's wrong.
Thanks,
Subhash.G

Urgent SAP upgrade from 4.0B to 4.7 Oracle 9.2.0.6

Dear support,
I have upgraded my oracle database to 8.1.7.4 with 4.0B extended kernel along with upgradation from NT 4.0 to Win 2000 is finished , and we are planning to upgrade SAP to 4.7 version.Please let me know whether i need to upgrade my database to oracle 9.2.0.6 before upgrade prepare phase ,
If yes then , do 4.0B ext kernel on Win 2000 will support oracle 9.2.0.6
I am not able to find any info on service.sap.com\PAM , because info about 4.0B
version not available.
Best Regards,
AjitR.

-> regarding 40B_EXT see sapnote 1.009.695
-> see sapnote 85.838 (section Operating System: WINDOWS FOR X86):
SAP KERNEL 4.0B_COM 32-BIT:
ORACLE 8.1.7 WINDOWS SERVER 2000/IA32 32BIT 4,5
ORACLE 9.2 WINDOWS SERVER 2000/IA32 32BIT 6,7,8
ORACLE 9.2 WINDOWS SERVER 2003/IA32 32BIT 9
SAP KERNEL 4.0B_EXT 32-BIT:
ORACLE 9.2 WINDOWS SERVER 2000/IA32 32BIT 6,7,8
ORACLE 9.2 WINDOWS SERVER 2003/IA32 32BIT 9
GreetZ, AH

SAP Upgrade from SAP R/3 4.6 C to ECC6.0, Delete DMC componenet

Dear All,
We are upgrading SAP from R/3 4.6C to ECC6.0 . Our client has installed DMC in 4.6C as a "Main transport" request . DMC becomes an Add-on tool in ECC6.0 . SAP pepare phase recognize DMC is already installed in 4.6C and required upgrade CD 51031689. Upgrade CD 51031689 is not available in marketplace and required an restricted access . Actually we are not using DMC component and would not planning to upgrade to DMC 6.0 . SAP Upgrade Prepere phase has facility to mark as "Delete" for unwanted add-on componenets. We are able to select "delete" radio button for other Add-on compoenents but unfortunately "IS_SELECT" phase doesn't provide me an option to select "delete" radio button .Any help/suggestions are highly appreciated.
Thanks
Mahendra

Hi
Try this link, which will give functionality enchancements between different versions of SAP.
http://solutionbrowser.erp.sap.fmpmedia.com/
Regards
Ramakrishna

WCF-SAP Adapter throwing errors after SAP Upgrade from ECC 5 to ECC6 Release 640 to 700

Hello Everyone,
We were able to communicate(Send and Receive Idoc's) to SAP via WCF-SAP Adapter in BizTalk 2010.
SAP Servers were upgraded to ECC5 to ECC 6 and we started facing below issue communicating on send and receive both.
I am aware that there is a hotfix available but that is more on the Receive Side from SAP. Nevertheless I installed the hotfix but issue still persists. Any suggestions will be highly appreciated.
Microsoft.ServiceModel.Channels.Common.XmlReaderParsingException: The segment name is not valid for the IDOCTYP, Release, or CIMTYP. Segment name: E2EDP01006GRP   IDOCTYP: ORDERS05
Release: 700    CIMTYP: . Ensure that your message xml validates against the operation schema.
Server stack trace:
   at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.EndRequest(IAsyncResult result)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at System.ServiceModel.Channels.IRequestChannel.EndRequest(IAsyncResult result)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.
Thanks,
Vikingss

I am aware that there is a hotfix available but that is more on the Receive Side from SAP. Nevertheless I installed the hotfix but issue still persists. Any suggestions will be highly appreciated.
For this issue, you can contact Microsoft support directly(http://support.microsoft.com).

HTML Page not appearing after SAP Upgrade from 4.6c to ECC 6.0

Dear All,
I am novice in ITS and IAC configuration stuff....
Issue: We have a HTML page which shows a tree structure of Functional location and Equipments. A Z transaction is built to cater the requirement. User logs on to the HTML page navigates thru the Tree structure of Functional locations and equipments and the logs the workrequest or Break down details. In 4.6C every thing is working fine. But after Upgrade in Testing Server (We are not go live yet) we are facing a problem where the HTML page with tree structure is skipped off and directly the Z transaction is appearing on the web page.
Did any one faced such issue? Any thoughts is highly appreciable?
Thanks,
Sanjay.

Thanks Frank and Dhurairaj....and sorry for the delay in responding..
I have checked my service in SICF and it is active. I also tried to create a new Service and now I am now getting "500 Connection timed out" error.
Our Z transaction is ZW03 and Service name is ZW03_2.
We are on Netweaver 7 (2004s)
Steps I followed:
1. Created a Service ZW03_2 in SICF (New Sub element) and then Activated.
default host -> SAP -> bc -> gui -> sap -> its
2. Created a folder ZW03_2 under SAP->Public->ITS (Transaction SE80, MIME Repository) and imported all MIME objects into that folder.
3. Created a Internet Service ZW03_2 in SE80. Once I created a Service already there is blank folder Topic 99. Then I created two folders Mime Objects and HTML Templates. Imported all Mime objects into folder "Mime Objects" and Created templates in "HTML Templates" folder. Then I published ..
After doing all the above setting then I tried to test the service and I am getting 500 Connection time out.
Please let me know if I missed any step or if I have done any setting incorrectly.
Thanks,
Sanjay.

SAP Upgrade from ECC 5.0 to ECC 6

Similar Messages

Maybe you are looking for