JAVA Upgrade from CRM 5.0 to CRM 2007

Hi,
I need help. I'm trying to upgrade our CRM 5.0 to CMR2007 and encountered a problem during the JAVA Prepare Phase.
Here is the error I received.
The execution of ended in error.
Could not load class com.sap.sdt.j2ee.phases.PhaseTypeDetermineSystemId.
com.sap.sdt.util.misc.LoaderException: Class com.sap.sdt.j2ee.phases.PhaseTypeDetermineSystemId not found using classpath.
com.sap.sdt.ucp.pce.ctrl.PhaseLoaderException
Could not load class com.sap.sdt.j2ee.phases.PhaseTypeDetermineSystemId.
DETERMINE_SIDS
INIT
PREPARE
NetWeaver Upgrade
SAPJup
Java Upgrade
Thanks,

Hi Ramon,
In subdirectory trc you should find a file SAPJup.TRC containing some more details on the exception that happened. Add the stack if you find it there.
PhaseTypeDetermineSystemId is the first phase class to be loaded from package lib/sdt_j2ee.jar. So, you should check if this jar is around.
Regards,
Thomas

Similar Messages

Upgrade from CRM2007 (6.0) to CRM 7.0

Hi community,
we are working on an upgrade from 6.0 to 7.0.
After checking modifications with TA SPAU, I'm checking our adaption in the WebUI.
Extending a WD Component with the workbench means, that a Z class is generated which inherits from the SAP standard class, then you can redefine the methods you need to adapt! Mostly we copied standard method and added our coding!
This means after upgrade I have to check all these redefined methods, because the overtaken SAP standard coding could probaby have changed due upgrade.
When I check table BSPWD_CMP_C_REPL I see that we habe about 90 classes which inherit from a SAP standard class.
So I think I have to check each reimplemtated method if the adapted coding is now different to standard method implementation?
Am I right with my suggestions?
I didn't start yet, because I'm still in hope that there's a transaction / programm supporting this job?
regards
Markus

Hi Markus,
Things that are available in 7.0 may have been made available in 6.0 through custom enhancements. You should therefore validate each and every implementation to see if the requested functionality is still necessary. This makes sure you're not poluting the system with unnecessary enhancements. This is not a process you'd want to automate in my opinion. It requires a person (or 2) with
1) good knowledge of the framework
2) the enhancements brought in 7.0
3) the functionality as requested by the business
Hope this helps you!
Cheers, Roel

Upgrading from SCM 4.1 to SCM 2007/5.1 (HP-UX/MaxDB)

Here's my challenge - I need to upgrade an SCM 4.1 system (HP-UX IA64 11.23/MaxDB 7.5) to SCM2007/5.1. From what I can see in the Product Availability Matrix, SCM2007/5.1 requires MaxDB 7.7. What I need to know is how and when should the MaxDB database and liveCache be upgraded from 7.5 to 7.7 (or 7.5 > 7.6 > 7.7). I've tried to run PREPARE on the first system we wanted to test the upgrade on, but it fails with the following hard error: "ERROR: MaxDB Version is not supported by this upgrade. ERROR: Error in database software path determination (ERR -10)". This leads me to believe I need to upgrade the database before upgrade upgrading the application, yet I can't seem to find this requirement documented in any of the SCM upgrade guides.
Any assistance will be appreciated.
John

Hi Kaushik
just a little input about funtional DP (not sure of system architectural improvements) :
I dont think performance would drastically improve per se
the areas that might be of some impact/ use in terms of performance are -
- parallel processing profiles
- macro improvements
- changes in Admin Workbench (BW 7 functionality might make things easier)
- changes in Planning area (no negatives for eg can help remove macros that used to do that function making it easier)
The important improvements are in more functionality
Its recommended to do some better process and layout deisgns to get performance improvements
pl note, there would be an initial long run time the first time you perform any transaction because of indexes being created

Upgrading from SBS 2008 and Exchange Server 2007 and Adding Modest Failover Protection

I haven't seen anyone describe this scenario, so maybe it can't be done, but it seems it should work. Can someone either confirm this is viable or set me straight and tell me it's not wise (and if not, why not).
I currently have SBS 2008 (2008 Server + Exchange Server 2007 + some other components). I use redirected folders so all my user data is stored primarily on the server, and then sync'd with their local harddrives for roaming use and as an additional
backup precaution. I want to upgrade to a modern version of Exchange (don't care too much about the underlying server OS, but seems like a good time to upgrade everything). I also want to improve the reliability for rapid recovery in the event of a system
failure. I have always felt nervous with SBS because it only runs on a single server.
My plan is:
Install Windows Server 2012 Standard on a new server machine
Join that new server to the existing SBS domain and sync the users, etc.
Install Exchange Server 2013 on the new 2012 Server
Migrate the existing Exchange data and account info to the new server
Demote the SBS Server and promote the new server to primary DC
Reformat the old SBS server and install Windows Server 2012 on it too, and join it to the domain as a second DC
Set up DFS Replication and keep all my user data folders between the two servers (so if one server fails, the other can take over, just not automatically like with a cluster)
Install Exchange Server 2013 on the reformatted 2012 Server box (so second instance on the domain) and set it up to sync with the first Exchange Server 2013 via DAG (so if either computer crashes, the other can take over for both Exchange Server and file
services)
Wouldn't that give me a complete slow-response failover system without the need for setting up a cluster (I know a cluster would provide instant failover protection, but I don't need that kind of speed - a manual switchover in the rare event of a server
failure is acceptable for us)? I could do this using cheap hardware for each server, because unless both servers fail at the same time, clients can point to the other server. And because it's not a formal cluster, I don't need to buy anything for a shared
SAN. This seems like such an obvious more cost-effective solution for a small network, I don't understand why this isn't a common approach, which makes me wonder if there is some reason it won't work.
Any suggestions or feedback? Are Redirected Folders still recommended for users on a Server 2012-based domain?
Thanks,
Colin
Colin

Ed, thanks again for your help. OK, so here's my updated plan (I realize I should probably check on some of these pieces on the Server group, instead of this Exchange group).
Constraints/objectives:
None of the machines are truly server grade hardware, but only 5 people on the network, so performance is generally not an issue, unless a given server is just pegged on CPU or HD due to its own internal maintenance tasks and can't respond to user requests.
Haven't seen any problems, since upgrading server from 4GB RAM to 8GB a few years ago.
Not going to buy any new hardware at this time, but do have several unused consumer-grade computers I can deploy as wimpy or moderate servers.
Main issue is to limit repair time in the event of a system failure (instant failover is not required, but want to be able to restore network functions within less than 24 hours in the event of a hardware failure) and minimize time spent on IT
maintenance.
Because of light IT maintenance (not anyone's primary job and we're too small to justify a dedicated IT person or to pay for outside help), almost every touch takes me research and time to re-learn what I haven't done in weeks, months, or years -- so also
want to keep all IT tasks as simple as possible.
We philosophically want to invest now for the next 5 years and avoid ongoing cloud fees (so zero interest in Windows Server Essentials with Exchange Online)
A little nervous about using VM's, just because I never have before, but I do respect that's probably the right way to do many of these things...
Currently I have SBS 2008 (Windows Server 2008 R2, Exchange Server 2007, WSUS 3, all with latest SP's, also includes SharePoint and other stuff, but I don't really care about most of it) on a single 8GB consumer grade system, which functions as a file
server and Exchange server. We use Redirected Folders and Offline files for all users, which works great for us and provides additional file redundancy (if server goes down, all of each user's files are also on their own machine and they can even continue
to work just fine w/o the server, losing only ability to send and receive e-mail). It has been sufficient, but I want to upgrade our version of Exchange and I am nervous that if that current one server fails, it would take me a long time to restore everything
from backup, easily many days, especially if I need to buy any replacement hardware. It is RAID1, so a single drive failure is easy to handle, but that's the only hardware redundancy for the current server.
New Plan:
Install Windows Server 2012 R2 Standard on a new modest machine (16GBR RAM, Core i7, 1TB RAID1 (may upgrade to 3 or 4 TB), 256 GB SSD boot drive, this had been my old personal computer)
Join that new server to the existing SBS domain (2008 R2/Exchange 2007), make it a DC, sync the users, etc.
Install Windows Server 2012 R2 Standard on a wimpy computer (4GB RAM Core i3 processor), leave it as a member server
Install Exchange Server 2013 on the wimpy new 2012 R2 Server (and nothing else, this will be dedicated to Exchange to make the most of such a wimpy machine)
Migrate the existing Exchange data from the old SBS Exchange 2007 server and account info to the new server
(or should I just create new accounts and copy the data from the user end through Outlook -- is that safer and cleaner than attempting any kind of server-level Exchange data migration?)
Demote the old SBS Server and promote the new 16GB server to primary DC. Now it's OK to take the old SBS server off the network.
Reformat the old SBS server and install Windows Server 2012 R2 on it too, and join it to the domain as a second DC (and possibly DCPROMO it to be the main server)
Install Exchange Server 2013 in a VM on the reformatted 2012 R2 Server box (so second instance on the domain for Exchange redundancy) and set it up to sync with the first Exchange Server 2013 via DAG OR set up another physical wimpy member server and install
it there. In any case, do NOT install Exchange directly on either DC.
Set up DFS Replication or a Failover Cluster (still need to research this, but I had planned on DFS, thinking Cluster required shared drive, but Ed corrected me on this) between the two DC's for redirected files and keep all my user data folders between
the two servers. We don't need automatic failover, like with a cluster, a manual switch would be acceptable, but if no additional cost or risk to clustering the two DC's, then the auto-failover protection that provides would be better than DFS.
I think this incorporates all of your points, Ed. Does this sound right now? What's your advice on #5 (how to best migrate user data)?
Thanks so much for all your help,
Colin

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

Java Enging upgrade from CRM 5.0 to CRM 2007

Hello all,
we would like to upgrade our CRM 5.0 System to 2007 (MS SQL Server 2005, Windows 2003 X64) and now we have a problem when we want to upgrade the JAVA Engine. I've got an error in Phase READ_AND_CHECK_ADMIN_PASSWORD in Java Prepare programm. A possible reason, says the system, is that the J2EE engine is not started. I must say that we have an ABAP and Java System and there are some ABAP workprocesses in the SAP management console but I cannot see any J2EE processes under "J2EE Process Table". Is that normal? I have no idea. I worked with the system perfectly, therefore I thought that this was not a problem, but now, after this upgrade error I'm not certain any longer. In which cases do we need Java processes anyway? Can/shall I uninstall the java component if we don't need it? If yes, how?
Thanks for your help.
Diana

The upgrade process is asking for a mounting point on iSeries. Removing the Windows drive letter Y: solved the issue. The correct mounting point was /BASISDVD/.......

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

Impact of upgrade from SAP CRM Interaction Center 4.0 to 5.0 on Genesys CTI

Hi Friends,
I would like to know that what is the impact of upgrade from SAP CRM Interaction Center 4.0 to 5.0 on Genesys CTI software.
1) Will there be anything we need to change?
            for e.g.
                 a) Settings
                 b) Software
                 c) Hardware
2) What do we need to keep in mind when upgrading from SAP CRM Interaction Center 4.0 to 5.0?

Hello!
The biggest change you must face is related to Java. If you had CRM4.0 Java configuration, you must change your settings to the non-java configuration CRM5.0 has. Most of those changes are performed by the upgrade program, but you must activate services in transaction SCIF.
Your other concerns:
- Software: Most of the Genesys releases are compatible with both java and non java configurations. Anyway, I am sure Genesys has compatibility instructions.
- Hardware: No changes to my knowledge
<b>Hope it helps. Please, reward points if so</b>
Regards
Joaquin

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

Upgrade from CIC0 to CRM IC Web - is NetWeaver XI required?

Hi,
I have a customer who is looking to move their processes from the customer interaction centre (CIC0) in the SAP GUI to the CRM 2007 IC WebClient. They have upgraded to ECC 6.0, but do not have NetWeaver in place today, so they have asked whether this is required for the implementation of CRM. Do I correctly assume that the CRM middleware concept has not changed (ie it still uses BDocs) with CRM 2007? Also, can you please confirm whether XI required for them to move to the CRM 2007 IC WebClient?
Thanks
Janine

Hi Janine,
Yes. There is no change in the CRM Middleware concepts in CRM 2007. There is no need for an XI for using the CRM Webclient.
Regards,
Shwetha

Upgrade IC Web Client from CRM 4.0 to CRM 5.0

Hello All Gurus,
We are planning to upgrade from CRM 4.0 SP9 to CRM 5.0.
Where can I get what are the modifications and what are the things to keep in mind.
We did a lot of custom developments which are now part of standard. In such a case what is the best option do we go on with the custom developments or do we move more to the standard.
Thanks and regards,
Murli Rao

Hi Vikas - so is it working now?
steps would be
1. go to C:\WINDOWS\system32\drivers\etc
2. open the 'hosts' file in notepad and type in ur IP address and the URL. There will be other entries also in this file, and u can refer to that for format.....
eg:
10.121.986.87 xxxxxxx.yyyy.com
-Aarthi.

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 2007

Hi,
We are planning to update from CRM 5.0 to CRM 2007. We are using CRM for Leads, Opportunities and Account & Contact Management with PCUI as front end. We do have some customized iViews for Sales People and Customers. Can any one, please provide me the step-by-step process to do technical and functional upgrade or point me towards the documentation on the same
You will rewarded with the points. Thanks in advance. Please, Its URGENT...
Cheers,
Amit

Amit,
Based on your reply your work looks like the following:
1. Basis teams performs tech upgrade of your dev system
2. Security team grants temporary expanded access in dev system to access new UI and new UI tools
3. Dev/Config team takes standard delivered new UI screens and adjusts screen layouts
4. Dev/Config team adjusts any BADI's built in the previous release
The data model of CRM has not changed. If you stuck with the EEWB and used all the standard methods of enhancing the data model, you don't need to worry about data migration. However if you did not play by the SAP standards you could have more work.
As far as tracking your project you can use solution manager or build simple project tracking in MS project.
If you did no coding period, and only configuration. You should be able to complete all the configuration work in less than two weeks to get the screens as needed. However that is based on having at least one to two weeks of learning the new UI tool.
I would guess a config-only CRM implementation would only need two-three to finish all reconcilation work not including testing and training.
Take care,
Stephen

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

JAVA Upgrade from CRM 5.0 to CRM 2007

Similar Messages

Maybe you are looking for