Technical upgrade to ERP2005 6.0 and CRM2007 with CUA on 640?

We are in the planning stages of a technical upgrade to ERP2005 6.0 and CRM2007. Our CUA system is not being considered for this upgrade; it's currently at kernel release 640, patch level 80, ABAP load 1521, CUA load 15.
I've searched all over for recommendations, and all I've found is this from the SAP Help pages: "Use the most up-to-date system in your system landscape as your central system (if possible with a release status of 4.6C or higher). In this way, the newest functions in CUA are available to you." In Frank's NetWeaver Identity Management 7.0 Technical Overview Presentation, he states "IdM will replace the CUA in the long run, however, SAP will continue to support CUA in its current functionality according to SAP maintenance rules."
Will we have a problem if our CUA system is at a lower release than the rest of our systems?
thanks,
Mary-Anne

possibly not. still i would test the scenario on a sandbox system which is already on ERP 6.0 and another one with CRM2007 on it. you could for that purpose simply add them to your ALE-scenario (BD64). after such a test you can be sure whether everything is still o.k.
that recommendation from SAP makes sense though: distributing from a system which is running on the latest software is preferable, since you would have a source which is likely to be more 'reliable' than the target.
why don't you upgrade your CUA central? what are the reasons for this?

Similar Messages

Technical upgrade from 4.6c to 6.0ecc with unicode conversion

Hi Experts,
Can you explain me technical upgrade from 4.6c to 6.0ecc with Unicode conversion.
if u got any notes pls send it to [email protected]
vijay

Check these links. Search SDN with Term "Upgradation" you will get lot of links
http://help.sap.com/saphelp_nw04/helpdata/en/16/4b3c88170e11d6999d00508b6b8b11/frameset.htm
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f0f9f37c-be11-2a10-3baf-d5d7de5fb78d
http://www.sdn.sap.com/irj/sdn/wiki?path=/display/unicode/system%2blandscape%2bconversion
http://www.sdn.sap.com/irj/sdn/wiki?path=/display/unicode/project%2bplanning%2b-%2bmdmp%2bsystem
http://www.sdn.sap.com/irj/sdn/wiki?path=/display/unicode/communication%2binterfaces
Message was edited by: Jason Lax (Removed link to deleted content)

Recent upgrade to 3.1.2 and issue with voicemail password request

just went thru the 3.1.2 upgrade, froze my original phone-just like the 3.1 upgrade- had to go to store and get a new refurshied phone (dont even go there!) which only worked for three days, then had to return to store again......excuse me, i do sound angry don't i?
anyway, now i continue to get a message----"password incorrect enter voicemail password" now i have never had a voicemail password so i can not figure out why it wants one- have never seen this message until the upgrade... cant make it go away either- any suggestions out there? thanks

EVERYTIME I update my phone, I lose all my music, podcasts, and apps. I dont know why. Pics, contacts, texts, etc are all saved, but anything else is deleted and NOT restored when the phone is restored from backup. I feel your pain...

Upgrade to GRC AC 10 and Integration with BI

Hello,
I am running a study to integrate GRC Acces Control 5.3 and business warehouse 7.02 and should install it to production soon.
We also have an upgrade to GRC 10 in the pipe.
I understood with OSS note 1667517 that no business content is delivered with this latest GRC AC version (version 10.0)
When the GRC upgrade will be done, do you know if I will be able to load and use reports created/activated with GRC AC 5.3 ?
Thank you
Seb

Hi Jyoti,
When UNinstalling 5.2 have you uninstalled virsa~ccxsysdb.sda file.?????
As per the Upgrade guide we should not uninstall virsa~ccxsysdb.sda.
you need to redeploy the Database file named "virsa~ccxsysdb.sda" of CC 5.2 with the overwrite option in the SDM
Regards
Gangadhar
Edited by: gangadhar hm on Sep 18, 2009 12:21 PM
Edited by: gangadhar hm on Sep 18, 2009 2:17 PM

Sending email problems from iphone since upgrade to 4.3.5 and now with 5

I'm having problems sending email more often than not. Does anyone know why tis is happening and if there is a fix for this? I am using yahoo.

There is no way to officially do what you're trying to do, and the terms of use here prohibit us from giving you instructions. Sorry.

Older CUA version connectivity and functionality with ECC 6.0

Our current Solution manager box, which is used for CUA, is on Netweaver 04 (sap basis 640 patch 16). We are in the process of upgrading to ECC 6.0.
Generally speaking I would recommend having a CUA box at the same level or higher than the child systems. However I'm would like to know if anyone has experience with a similar version scenario as described above. If so what issues did you run into and or other items should I be aware.
Also, ECC has several new system parameters and other password related changes. Can any of the newer password functionality be used if CUA is still on the older version?
--B

have a look at this thread
Technical upgrade to ERP2005 6.0 and CRM2007 with CUA on 640?
it should answer both your questions.

Grantor Managment solutions and BCS problem after technical upgrade.

Hello every one,
The current release SAP installation was upgraded to ECC 6.0; this was a technical upgrade and did not replace functionality such as "Former Budgeting" with the new BCS functionality. SAP developed the Grantor Management solution utilizing BCS. BCS utilizes a different table structure from the Former Budgeting functionality. The current tables do not contain the BCS reference points to each other which limits the implementation of Grantor Management in the same instance. There are no plans to upgrade to BCS functionality at this point in time.
what are my options? How can we work around this issue?
Regards
K

Hi,
Thanks for the resposnse.
But when i go through the OSS notes it is provided that there will be performance problem in executing the report.
How to get it solved?
Thanks,
Regards
M.A

Y-transactions missing after upgrade 46C -- ERP2005

Dear all,
After an upgrade from SAP 46C to mySAP ERP2005 (ECC 6.0 on Web AS 700), which ran suspiciously smooth by the way, a number of customizing transactions (81, to be precise) seems to be missing (all starting with customer namespace letter "Y"), while others (the most, fortunately) are present and working like before. I checked, and the transactions are indeed not in table TSTC, as expected.
Ofcourse the functional consultants are blaming the technical upgrade, and like to hear from me where these transctions might have gone. However, as stated before, the technical upgrade was performed without too much problems, and there's nothing to indicate when and where this could have occurred.
Can you please help me out on this? Does anyone have the same experience regarding an SAP upgrade? What could be the cause, and what the solution?
With kind regards,
Henk.

Hi
Actualy no Z or y program should affect this.
Just see the transaction SPDD and SPAU whether these programes are stuck in these transaction .
Regards
Dhananjay

Technical Upgrade

Hi All,
I am new to upgradtion.I am upgrading from 4.6C to ECC6.0.
I am working in ABAP.I want the technical upgrade Procedure.LIke Basis people has done the every thing.They given me the system.What i need to do exactly.What is the procedure i have to follow.
If anybody has the documentation.By seeing that documentation i need to do Technical Upgrade.Please can anybody help me.Please this is very urgent.I will reward you more points.

Following are the activities carried out after Basis activities in a Technical Upgrade -
SPAU & SPDD
During an upgrade or the import of a Support Package, existing objects of the SAP standard are overwritten with the objects redelivered. To help the customer retain the objects modified in a previous release, SAP provides all modified objects which are redelivered (in an upgrade or Support Package) in the upgrade adjustment of transactions SPAU and SPDD. These transactions allow customers to enter their modifications into the corresponding new objects being delivered at upgrade. The Modification Assistant supports this process of adopting customer modifications.
In the past, all objects modified by a customer and delivered again by SAP, an IBU or an SAP partner had to be manually re-modified during an upgrade. Now, modifications are either automatically adopted or the system provides you with an assistant for adjusting your modifications to the newly upgraded configuration.
http://help.sap.com/saphelp_nw2004s/helpdata/en/60/d6ba7bceda11d1953a0000e82de14a/content.htm
Catch up of Transports
There were some transports moved from DEV to PRD (4.6 c) after the development system was upgraded to ECC 6.0.
To keep both the development systems DEV 4.6c and D60 ECC 6.0 in Sync remediation of the respective objects was done. All the changes w.r.t the latest transport was incorporated in the new upgraded system D60 after comparison with DEV using the Remote Comparison functionality or the SE39 transaction.
DDCHECK
Table enhancement categories
OSS note Note 493387 - Potential effects of table- and structure - extensions
ABAP Fixing of the affected or Obsolete Function modules
Some tables are obsolete in ECC 6.0, moving the data from Obsolete tables to new tables
Some transactions are either changed or outdated or obsolete, or there are some screen changes; BDCs recorded for all such transactions should be re-recorded.
Please refer to the below WIKI page for details on upgrade -
https://wiki.sdn.sap.com/wiki/display/HOME/ERP2005+Upgrade
Hope this helps you.

Warning codes generated in UCCHECK   - Technical Upgrade - 4.0b to ECC 6.0

Hi SDN'ers ,
I am currently working on Technical Upgrade project from 4.0 b system to ECC 6.0 system . I am facing a
problem relating to the analysis of the warnings displayed whehn we run the UCCHECK for the client inventory by
checking the "Display lines that cannot be analyzed statically" option under the Selection-screen block
"Statements that cannot be analyzed statically" .Based on the warning codes generated during UCCHECK, they can
be classified into 12 different categories given below in the list ( Viz. ABB,MESSAGEG!C,MESSAGEG!D......MESSAGEG!P).The same are given below in the end
I want to know
- Which are the warning codes which need resolution so that the program does not encounter any runtime
errors or during Integration testing ?
- Do all the offset related errors (For example ;variable A = B+offset(length)
or variable A+offset(length) = B ) need resolution so that the program gives no runtime error.
- Also, do all statements where length is calculated using STRLEN also need changes ? I have seen offset length related warnings come under MESSAGEG!M warning code.
The objective of this is to make sure that the upgraded system ECC 6.0 in Australia ,when rolled out to
non-English speaking geographies in APAc such as Malaysia,Japan or China would only need translations and no ABAP Coding effort even when using languages such as Japanese which have double byte characters.
S.No.     Error Code     Message
1     ABB     Syntax Check Aborted
     ABB Total
2     MESSAGEG!C      check at runtime. at runtime.
           statement because of untyped or generic operands. It can only carry out this
          The system could not perform a static convertibility check on the current
     MESSAGEG!C Total
3     MESSAGEG!D      out this check at runtime. It can only carry out this check at runtime.
           to a table line because of untyped or generic operands. It can only carry out
          The system could not perform a static check on convertibility from a work area
     MESSAGEG!D Total
4     MESSAGEG!E      check at runtime. at runtime.
           defined by a "DATA" statement. .
           statement because of untyped or generic operands. It can only carry out this
          Field "ELEMENTN" is unknown. It is neither in one of the specified tables nor
          The system could not perform a static comparability check on the current
     MESSAGEG!E Total
5     MESSAGEG!F      operand "<FELD1>" for the current statement. .
     MESSAGEG!F Total
6     MESSAGEG!G      current statement on incompletely typed operand "<DATA>". .
     MESSAGEG!G Total
7     MESSAGEG!H      for the incompletely typed operand "<S>". . - - - - - - - - -
          The system cannot perform a static check on a character-type field data type
     MESSAGEG!H Total
8     MESSAGEG!I      incompletely-typed operand "<A>" in the current statement. .
          The system cannot perform a static check on a character-type data type for the
     MESSAGEG!I Total
9     MESSAGEG!J      "<%_1_SYSINI>" in the current statement to check whether the operand can be
          The system cannot perform a static check on incompletely-typed operand "VALUE"
     MESSAGEG!J Total
Early response wil be highly appreciated.

Hi Karthik
>
> 1) SPDD adjustments are done in which phase? PREPARE or UPGRADE?
>
SPDD is done in Upgrade ->Phase ACT_700
> 2) Are here special cases where the adjustments need to be done before running the UPGRADE phase?
>
At ACT_700 phase stop the upgrade and take a backup of the DB and the PUT<DIR> before starting the SPDD activity.
Make sure there are no pending tp request. Either release them or delete them.
All phase need to be completed successfully in PREPARE, before starting UPGRADE
Cheers
Shaji
Edited by: Shaji Jacob on May 5, 2008 9:23 PM

Technical Upgrade of the system from R/3 4.6 to ECC 6.0

Hi all i have a query regaring system upgrade:
Currently i have 2 systems R/3 4.6: Development(D1), Quality(Q1).
Now this systems needs to be upgraded to ECC 6.0.
First the D1 is going to be copied to a new development(D2).
Then D2 will be upgraded to ECC 6.0.
Here a unicode check and other required modification (code compatibility) to
all the customizing and workbench objects is to be done.
Now a copy of Q1 is to be done in new Quality(Q2).
My requirement is to determine all the transported requests from D1 to Q1 and
then transport the same from D2 to Q2 so that the unidcode complaint objects are transported and they overwrite in the new quality system.
Is this process feasible? If yes, How?
If anyone has worked on technical upgrade project, please suggest?
If any other information is required pls mention.

hi.
it sounds quite complicate for me...
you do not need to upgrade D2 to ECC 6.0 to be able to do the unicode checks. when you go to transaction se38 and select the report Z* you will find something like "unicode checks active" in the properties. if you enable them and check the reports you will find the problems regarding unicode...
i think there is another problem too. what are you doing with the unicode-enabled transports on system D2? you transport them to Q2 and what else? Are you transporting them to D1 too? If yes it is possible that you will overwrite the originals on D1 (it depends on your settings on system D2).
hope my answer helps...
regards,
martin

Technical Upgrade from R/3 4.6 to ECC 6.0

Hi all i have a query regaring system upgrade:
Currently i have 2 systems R/3 4.6: Development(D1), Quality(Q1).
Now this systems needs to be upgraded to ECC 6.0.
First the D1 is going to be copied to a new development(D2).
Then D2 will be upgraded to ECC 6.0.
Here a unicode check and other required modification (code compatibility) to
all the customizing and workbench objects is to be done.
Now a copy of Q1 is to be done in new Quality(Q2).
My requirement is to determine all the transported requests from D1 to Q1 and
then transport the same from D2 to Q2 so that the unidcode complaint objects are transported and they overwrite in the new quality system.
Is this process feasible? If yes, How?
Please suggest.

Hi Himansu,
I am making the assumption that you will as the final step upgrade your production to ECC 6.0 and then transport the Unicode corrected ABAP's from your Q2 environment into Prod, and then D2 and Q2 will become your new production support path while D1 and Q1 is removed. Is this assumption correct?
If so, then the next assumption for your plan is your reason for doing this is to keep the production support path D1->Q1->P1 intact while you are performing the upgrade and Unicode program testing in D2 and Q2.
I am also assuming that you are not doing a unicode upgrade/conversion at the same time, you are just making the code Unicode compliant to prepare for a future Unicode upgrade.
If so your plan will work just fine. To say it a little differently, here are the steps
1. Copy D1 to D2
2. Upgrade D2 to ECC 6.0
3. Run UCCHECK to test your code for compliance and to identify objects that need remediation
4. Fix the code that need fixing, and put it in transports with Q2 as your target system
5. Copy Q1 to Q2
6. Upgrade Q2 to ECC 6.0
7. Transport the converted code from step #4 to Q2
8. Perform thorough acceptance testing of the converted code
Now you can plan for your production cutover. While the above steps occurred, you either had a freeze on any changes to the production landscape, or you manually captured changes that was done in D1 in D2. The upgrade project is complex in itself and will need significant user testing assuming that it is only a technical upgrade with no additional or modified functionality.
If your D2 and Q2 was kept in sync, you can now upgrade your P1 system to ECC 6.0 (no need to copy), and configure your transport routes so that D2 and Q2 are now the new production support systems, then you transport the items in step #4 above from Q2 to the upgraded P1.
Regards
John
[SAP Unicode|http://www.sapunicodeupgrade.com|SAP Unicode]

Technical upgrade from 4.6C MDMP system 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 the CU & UC upgrade approach 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,
Rajaram

Hello Rajaram!:
It's a very big project, that you have to do in a lot of steps........
If you want sent me a email with the problems and you want.
Regards,
Alfredo.

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.

Issues during technical upgrade from 4.6c to ecc 6.0

Hi
We are doing a technical upgrade from 4.6C to ECC 6.0. Some transactions in QM module when tested in ECC 6.0 test client give a abap termination message (or dump) and certain transactions like qs42,46, qa18, qs34 etc do not get executed (error = no entry foound for......) and similarly in PP-PI module transactions like C203 have similar problems, even though master data does exist. What should I look for? Can somebody pl. give details on configuration checks and the OSS notes from a functional point of view for a technical upgrade?
For certain transactions I get the error message - "Central system of distribution SM-P06CLNT430_TRUSTED is unreachable RFC destination SM_P06CLNT430_Trusted does not exist" - what does this mean?
thanks
BE

Hi,
1. Have you done successfull installation from 4.6C to ECC 6.0 at the time of PrePare ans SAPUP?
2. Check SP' for QM and PP-PI modules from http://service.sap.com/sp-stacks.
3. Configure RFC connections correctly, SM_<SID>CLNT<No>_Trusted automatically created, not manually.
http://service.sap.com/notes --> search for RFC trusted connections for Ecc 6.0
http://service.sap.com/upgrade.
Regards,
Srini Nookala

Technical upgrade to ERP2005 6.0 and CRM2007 with CUA on 640?

Similar Messages

Maybe you are looking for