Upgrade from CRM 4.0 sp6 to CRM 2007

We are in the process of upgrading our sandpit from CRM 4.0 sp 6 to CRM 2007 as part of an overall CRM upgrade project. The technical upgrade phase went fine we now have the sandpit running some of the standard delieved business roles etc. My question is with respect to my original customizing:
- what customizing/configuration needs to be redone
- what needs to be adjusted.
- what is no longer relevant
Is there any documentation out there that deals with addressing this topic. Can anyone share their experiences.
We have a number of different Web based interaction centers some dealing with order taking in place in our original installation.
Thanks in advance
Eddie

Eddie,
The rule of thumb is the following:
- All UI based modifications/configurations/enhancements done in the lower release, must be redone in the new release. Classic example is you removed fields from a screen or added new fields. You also lose all your UI work done in CRM 40.
- All non-UI based config/development that is in the business layer of the system should be fine, and may need some minor adjustments, but you should be able to keep this. You probably though will have to redo some of your IC config as there were functional changes between releases. I don't think however you will find that the configuration adjustments to take a lot of time
- The old PCUI/IC webclient and SAP GUI applications(for data entry) are no longer relevant.
Take care,
Stephen

Similar Messages

It's possbile to upgraded from win2003 x64 sp2 which installed SCOM 2007 R2 into windows 2008 R2 directly?

current OS: windows 2003 R2 x64 SP2
current SCOM version: SCOM 2007 R2
current database version: SQL Server 2005
it's possbile to upgraded from win2003 which installed SCOM 2007 R2 into windows 2008 R2 directly without reconfiguartion SCOM?

Hi,
And as far as I know, in-place operating system upgrade could work, but there is no document about this. Please take backup before doing upgrade.
If you want to in place upgrade the OS, we can simply move SCOM databases to new servers and rebuild management servers one at a time. the downtime for SCOM would be very minimum if the management group has the capacity for agents to report to failover
management servers while the primary MS is getting rebuilt. You do not have to perform in place upgrade on the OS to keep SCOM.
Based on your need, I would like to suggest you add a Windows 2008 R2 as additional management server for your management group. And if possible, please also upgrade your SQL 2005 to SQL 2008.
Here is a thread for your reference:
http://social.technet.microsoft.com/Forums/systemcenter/en-US/4713e303-76a7-4954-9494-55565757d65e/scom-server-os-and-sql-upgrade-from-2003-to-2008-r2
Regards, Yan Li
Dear Yan, Since rebuild/config SCOM Server is very complicated so it's better that I can just upgraded OS into windows 2008 R2 without do anything else.

Appc error when upgrade from weblogic sp5 to sp6

Hi,
I got an appc compilation error for an Entity Bean. It is exactly the same code. the generated xxxx__WebLogic_CMP_RDBMS.java compiles in weblogic8.1sp5. After upgrading to sp6, I got the following error for "cannot resolve symbol
symbol : method setStringForClob (int,java.lang.String)
location: interface oracle.jdbc.OraclePreparedStatement".
I checked the generated java code. addition code is generated on sp6 which reference to oracle.jdbc.OraclePreparedStatement.setStringForClob().
The databased used is oracle 9i. driver is oracle shipped ojdbc14.jar for 9i. If I change to 10g driver, it compiles of course. But we don't have plan to upgrade the driver.
Would someone help me find what is wrong.
Thanks alot
JC

any ideas about this problem?? i am getting the same error. is it a bug in the weblogic sp 6??
Thanks,
Raj

Just upgraded from Tiger to Snow Leopard on a 2007 Macbook. MASSIVE speed boost. Why?

I'm just wondering, is there any way to tell exactly why a mac was slow before a system upgrade but fine again afterwards?
My old Tiger OS had got to the stage where Safari would bounce about 10 times before opening, remain unresponsive for minutes after that, when clicking the spotlight icon in the corner would produce a spinning beachball for ages, when the entire machine had turned into an incredibly slow piece of junk.
I upgraded to Snow Leopard last night and it's as fast pretty much as it was when I first bought it. Have 2GB of RAM, 30GB free disk space, etc.
What caused the massive speed boost? Should I now assume that there was some sort of mismatch in my old OS installation or something, some out of date extensions or files which were causing it to slow down?
I know a new OS brings a speed boost, but this is so dramatic I can only assume some sort of gigantic error was fixed when I upgraded. Any way to know exactly what?

OSX directory structures get a little wierd over time (thus the "Repair Disk" item under DU which many people need for very minor fixes).
Also some of your system files may have been living on hard disk sectors that were questionable, and the upgrade process forced enough of a re-evaluation of disk sectors to find good ones.
Either way, I would just say "Thank you, Santa", and move on.
<Following OSXFreak> ... Or maybe I know nothing about Tiger ... which is very likely.

Upgrade from CRM 4.0 Mobile Components to SAP CRM 7.0

Hi CRM guru's
I am a SAP BASIS consultant. New to CRM. I have a few queries for which i require help.
1) Is it possible to upgrade CRM 4.0 Mobile Components to SAP CRM 7.0 platform?
2) What is the approach used to upgrading a CRM 4.0 Mobile Components to SAP CRM 7.0 platform?
3) Are there any constraints in upgrading CRM 4.0 Mobile Components to SAP CRM 7.0 platform?
4) What would be the impact of such upgrade on current applications and processes?
5) Is it a straight forward technical upgrade or would involve technical tweaking to align it to CRM 7.0 mobile platform?
6) What would be the Pros and Cons of going for such upgrade?
Also,
1 )What is the use of the code migration tool in CRM mobile upgrade, whether it can covert the VB6 to .Net
2) What effort involved in the migration
3) Complexity in support pack upgrade from sp6 to sp7 in CRM 4.0 mobile( Please let me know whether the technology changed from VB to .Net in this support pack upgrade). CRM mobile Repository Server can be upgraded from 4.0 to 7.0 directly.

Hi Sriram,
Mobile component changed to .Net in 5.0 so the first upgrade of support packages should not be a problem. Your only concern will be the rollout of the support package upgrade to the users in the field.
I don't know much about the upgrade from 4.0 to 7.0 and the complications around the custom code migration from vb to .net. I imagine this is something you may need to talk to SAP about.
Depending on the amount of work involved it may be easy to upgrade the CRM system and do a re-implementation of the mobile component.
Good luck.
Cheers
Andrew

Problem with Billing Engine after upgrade from CRM 5.0 to CRM 7.0

Hello together,
The system of our customer has been upgraded from CRM 5.0 to CRM 7.0. After that some problems occurred regarded the billing.
In the Billing Due List a dump occurs when clicking on an item and then on conditions
Dump message: No function module can be found named "/1BEA/CRMB_DL_PAR_O_DERIVE" however.
(Other classes are new generated after the upgrade)
During the Analysis we looked to the billing engine navigator:
In the Billing Engine Navigator (Transaction: BEFN_F1) the Generation Log shows the following:
We have re-generated the Object PAR in CRMB->DL->Feature->PAR. But this shows the above displayed error message. How can we add value to the Placeholder?
Another question is which impacts does it have if we regenerate the complete billing engine for CRMB with transaction BEA_CONFIG_F1 (Configure Application)?
BR, Anne

Hi Nawanit,
we checked the key figure settings and categories. Everything is maintained correctly.
Since we work with MRP areas we also checked the "Global Parameters and Default Values for MRP Areas" in APO Customizing: The "Default values for Stock Transfer Documents" is set to "1" = Stock Transport Requisitions for MRP Areas.
BUT: When I try ot change this indicator I get the following message no. /SAPAPO/MRPA000:
"Process. w. stock transp. requisitions is not supported in standard sys. The process with stock transport requisitions will be supported as of SAP R/3 Enterprise Core Release 4.70 with SAP R/3 Enterprise Extension Set 2.0. ".
As far as we work with ECC 6.0, EHP4 this message makes no sense.
Does anyone have another idea?
Thanks
Jan

How to create new field while upgrading from CRM 4.0 to 7.0

Hi ,
How do we create new field on UI and store data into existing field in database?
Is there any option in AET to skip the creation of new field in the database table ?
Custom field is already created in GUI and database table while using CRM 4.0
Now, after upgrading to 7.0 EHP3 , I need to bring this field on the UI .
Using AET may create new field again in the database table.Please suggest.
New filed needed to be created in Marketing Campaign Element Header data.
Thanks
Jayasri

Hi Jayasri,
As a custom fields are already there in crm 4.0. You don't need to use AET again to add field.
These enhancements still exist after the upgrade. Dependent on the enhancement object and type some manual steps are necessary.
For example regarding a single field enhancement for the BP the whole framework is enhanced after the upgrade. There is only one manual step to bring the field on the relevant view(s) via the UI Configuration Tool. For whole BP tables some more manual steps are necessary, these steps are described in the note 1069791 - CRM WebClient UI for EEW enhancements (reference to more notes regarding the EEW after the upgrade).
For set types, we need to generate UI With the help of the UI configuration tool the settypes could become visible in the Web UI.
I didn't understood your scenario, can add little more information why you want to add field by AET if available in DB?
Refer
FAQ - SAP CRM Upgrade from release 4.0 to 7.0
Regards,
Arjun

Upgrading from CRM 3.1 to 5.0

Hi experts!
Can anyone of you tell me about risks and scope (what must be done) regarding upgrading from CRM 3.1 to 5.0? Do you have any links to good documentation?
Thanks, Camilla

Hello Camilla,
For the moment, to upgrade to CRM5.0, it will be a rampup project : https://websmp106.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000654884&.
Regarding the upgrade, have a look in the 'Upgrade Master Guide mySAP CRM 2005 (SAP CRM 5.0)'
https://websmp106.sap-ag.de/~sapidb/011000358700005413872005E.
Best Regards,
Frédéric

Upgrade from CRM 5.0 to CRM 7.0 MY Worklist Worklist

Hello,
we're upgrading from CRM 5.0 Interaction Center to CRM 7.0. The client is using MYWORKLIST in CRM 5.0. In CRM 7.0 I found
following three options for Worklist in Navigational Bar:
CH-WORKLST
CT-WORKLST
ICM-WRKLST
Please let me know which one is closer to MY_WORKLIST.
Thanks,
Saeed
Edited by: Saeed Ahmad on Aug 19, 2010 7:52 PM

Hi,
We have resloved issue using my activities from PRO* roles.
Regards,
Saeed
Edited by: Saeed Ahmad on Oct 12, 2010 4:45 PM

Upgradation from SAP CRM 5.0 GUI/PCUI to SAP CRM Ehp3

Hi Experts,
We have a requirement to upgrade SAP CRM 5.0 to SAP CRM Ehp3.
We can do the technical adjustment by using tcode SPDD and SPAU.
But how we can migrate from SAP GUI and PCUI screens to SAP WebUi screens ?
Please tell me all the upgradation steps and challenges to upgrade from GUI/PCUI screens to Webui.
Thanks & Regards,
Akhilesh Bhagat.

It's a tedious manual process to re-implement all your customizations over to the Webclient. I will say if you were good and kept business logic in BADI's then all you need to worry about is screen customizations. If not and you were like many folks, you are going to have to recode everything.
I did this about five years ago from CRM 4.0 to CRM 5.2(the first CRM release with webclient) and if you look at the content under my profile with way older blogs, you can find some of my commentary on doing this.
For EHP3, you need to learn/love/embrace the AET. You are also going to need to learn the SAP Web Client stuff ASAP. The great part for you is SAP offer classes or there is a book or two on it. You don't have to learn it from lean documentation like I did.
I disagree with the system reimplementation comment. There is no need to throw out your CRM instance. That's why we have upgrades. Keep your system, but reimplement the code in the SAP Web Client Logic. The great part is since you are coming from 5.0 -> EHP3 it's going to be like having a new CRM system again, as all the parts that need to be enhanced don't exist in your 5.0 box and that section of the upgrade system will look like a brand new system(at least that's how my 5.2 box looked like coming form 4.0).
Take care,
Stephen

Upgradation from CRM 4.0 to CRM 7.0 with respect to sales order.

Hi All,
Can you please tell me what are all the 'EEWB enchacement changes' to be carried out during upgrade from CRM 4.0 to CRM 7.0 with respect to sales order..
Thanks & Regards
Prasanna

hi
check out the upgradation Note available in the Master Lists for upgradation.

Upgrade from CRM 5.0 to 5.1 or 5.2 or 2007

Hi All,
Can we upgrade from SAP CRM 5.0 to SAP CRM 5.1 or SAP CRM 5.2 or 2007 ?
If yes, is there any upgrade path or documentation ?
Regards
Sandeep G

Hi Shalini
Thaks a lot for your swift reply.
Shalini, can you provide any documents to justify your statement, as i need this to pass on to a client. Further is PCUI available in 5.1 or 5.2?
Regards
Sandeep G

Upgrade from CRM 4.0 7.0 Missing existing Custom fields

Hi experts:
We have recently upgraded from 4.0 to 7.0 and many of the custom fields we created in 4.0 are not available in the UI. When I look in the BSP workbench under the page view that is defaulting in the webUI, I can see the fields in the context node structure but I cannot get them to appear on the webUI as available to add to the page.
Any help would be most appreciated!
Thanks!
Chris

Hi Chris,
Follow the path in SPRO
CRM-> UI Framework ->UI Fr Def ->Design Layer-> Deactivate hiding of Fields
Create New entry and set the flag for No hiding of fields by design layer. Save your changes. Your fields should be available.
Thanks,
Vikash.

Reasons to upgrade from CRM 4.0 to CRM 7.0 ?

Hi Experts,
We have CRM 4.0 working on our client system. Why should they upgrade from CRM 4.0 to CRM 7.0 ?
A few reasons that I can think of are :
1) SAP will not support CRM 4.0 -
But they can get maintenance support from SAP although at a higher cost
2) CRM WebClient - fast and easy to configure and maintain -
but this is not so convincing a reason that they should upgrade and then almost implement whole of CRM again. They already have Portal.
3) Some new functionality added by SAP in the newer versions-----That is good but their business is working good with the existing functionality of CRM 4.0
Please provide some compelling reasons so that we can ask our client to go for upgrade.
Thanks in advance.
Regards,
Vikas

Hi Vikas,
Although your customer happy with the functions in CRM 4.0, and they are willing to pay extra money for extended maintenance fee. SAP will end the support of CRM 4.0 sooner for later.
Other reasons I could mention:
1. if there is Java stack then the support of jave stack and the jdk version 1.3.1 is ended.
2. CRM architecture was changed since CRM 6.0 and and 7.0 provided New tools and assistants simplify, standardize, and reduce development effort significantly, i.e. less code development, more flexible customizing. From this prospective, 7.0 is the investment safe release for long-term
3. Enhancement of existing functions, details can be found in CRM 7.0 Release notes
4. If you use compoenent like TREX, definately you will be benefit from newer version, stable, faster etc.
There should be a lot, and you can order upgrade value proposition service from SAP for formal evaluation.
Cheers,
Denny

Collision Detection during Upgrade from CRM 4.0 to CRM 2007

We are in the process of doing an upgrade from CRM 4.0 to CRM 2007. As part of this upgrade we are following the steps detailed in the mobile upgrade guide. we are currently working on the collision
resolution issues in the mobile area. The latest issue on the UI layer is caused by changes on tiles like docactdocu2 or capsearch2 that were reverted to standard SAP.
When solving the collisions we have been working on sub objects to these tiles. When changes to theses sub objects were finished not only the collision for the sub object was solved but no collision on the parent object was shown. But the result was that the parent objects have returned to SAP standard on vital objects like custom anchors and/or custom controllers are missing on these tiles resulting in build errors. You can easily see what happened in the version tree of these objects as no merge between the changed branch and the SAP branch took place.
Returning to the tiles version from the changed branch is not possible though this function is offered in the version tree.
Why is the collision resolution functionality not working as we would expect. Why can we not chsange the tile version to the changed branch.
Has anyone else experienced these issues
Regards
Eddie

Hi Shankar
We resolved collisions on script level like "docactdocu2onLoad" by merging or accepting the change list (SAP) version. With the collision on script level being resolved the tile the script belongs to (in this case "docactdocu2") also vanished from the collision list. The result was that the tile was reverted to the SAP version.
With the change list being released we cannot go back to the custom version of the tile except by using the version tree. But the option "Copy to Open Version" offered by a right click on the version node wanted does not work.
Any ideas
Regards
Eddie

Upgrade from CRM 4.0 sp6 to CRM 2007

Similar Messages

Maybe you are looking for