Upgrade to EhP4/NW 7.01 in ECC

We are on ECC 6 and BI 700.The Basis team is planning for an upgrade to EhP4/NW 7.01 in ECC . Does that mean the bi 7 is upgraded with EHP1? Can some one please clear this. What does NW 7.01 in ECC mean?
Thanks,

Hi,
ABA Support Package 20 for 7.00
Basis Support Package 20 for 7.00
BW Support Package 22 for 7.00
It appears that the BI system is separate as the component levels here do appear to be
from BI system rather than having ECC components also.
Your SP stack level looks to be SPS20 which is quite old and should be updated before
updating system to EHP1.
Please refer to the following documentation:
1142832 - Installation Enhancement Package 1 for Netweaver 700
1146578 - Central Note: Upgrade to Systems on SAP NetWeaver 7.0 EHP1
1276895 - Add. info. about Upgrading to SAP Solution Manager 7.0 EHP1
1248905 - SP Equivalence for update/upgrade to EHP 1 for SAP NW 7.0
Also you can refer to the Ehancement Package Upgrade Guide at
service.sap.com/instguides
-> Installation & Upgrade Guides
-> SAP NetWeaver
-> SAP NetWeaver 7.0 (2004s)
-> Upgrade
Regards,
Aidan

Similar Messages

Excel layout changed after EHP5 upgrade from EHP4.

Hi All,
We have just finished the EHP5 upgrade from EHP4 for ECC 6.0 for our production system. BUT we noticed that The standard layout, (also known as Dynamic List Display) has been chagned in EHP5 compare to EHP4.
This is affected us as we have lot of macros enable for the excel files.
Request you all to help. Is there any sapnote, anyway we can resolved this issue.
Thanks

Hi Markus,
Thanks for reply.
I not sure how i can attached file over here? Is there anyway to attached files in the forum?. I have the before and after image of excel file.
But the position of the data which is downloaed in the excel sheet has been changed after upgrade. For example ,Before upgrade the column named "Description" in the production plan report was in the second column i.e. B where as after upgrade the "Description" column in the production plan report is in the first column i.e. A.
I mean the postion of the data changed in after upgrade. Therefore macro which are enable are not working anymore.
New Format Example
Production plan
Description                        Material                               Sales doc.
IRB 2600 M2004                 3HAC020536-018              104861
IRB 2600 M2004                 3HAC020536-018              2BT0615486
OLD Format
Production plan
                                      Description                    Material                               Sales doc.
                                      IRB 2600 M2004            3HAC020536-018               104861
                                      IRB 2600 M2004            3HAC020536-018               2BT0615486
Hope this above will help to make it clear.
After checking this message ... the output example given above seems to be not showing the way i itend to... But in above example in the old format the Description column was at column B instead of column A after upgrade.
Thanks
Edited by: deepak.shinde on Oct 11, 2011 8:34 AM
Edited by: deepak.shinde on Oct 11, 2011 8:36 AM

Upgrade from R/3 4.7 to ECC 5.0

Hello Everyone
This is my very first post on SDN. I am going to do an upgrade from R/3 4.7 to ECC 5.0. Can anyone please tell me how do I start and procede, this will be my very first upgrade and I definitely need help!!!. I will be really thankful if anyone can give me any suggestions as to how to procede with the planning and then the actual upgrade. What documentation from the service.sap.com should I follow???........PLS help!!!

Dear Mir,
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

Upgrade Sap R/3 4.6b to ECC 6.0 -unicode enabling

Hi,
I am going to work Upgrade Sap R/3 4.6b to ECC 6.0
My role only Unicode enabling syntax check.
Can any one explain what are the work involved in
Custom Reports, Custom Transaction and Screens, BDC, Enhancements and Exits(BTE), Script ,Custom DDIC
Particularly need information Sapscript forms
Regards,
Ram

Hi Ram,
For Unicode, transaction UCCHECK is your best friend. It will even tell you how to fix the error.
All programs Most of the time you will just go and set the Unicode Checks Active program attribute, save, activate.
- If there are Unicode errors, fix them.
http://iorboaz.blogspot.com/2008/03/sap-abap-solution-instructions-for.html
SAPScript - Not sure if it even needs Unicode-enabling. We are still in the middle of an upgrade. Will add more later.
Custom DDIC In our case, the BASIS team handled the Unicode conversion of the DDIC objects.I think they ran a consistency check first, then run SPUMG or something.
Search the web for a Combined Upgrade and Unicode Conversion Guide.
Hope this helps.

46C- ECC6 upgrade with EHP4 SAP_BASIS package not found

We are executing an upgrade from 46C to ECC6 SR3 and binding in EHP4.
We have successfully downloaded EHP4 using Solution Manager MOPZ and
provided the generated "XML" file during the PREPARE.
During the phase EHP_INCLUSION, PREPARE is stopping with a message "No
matching SAINT package for 'SAP_BASIS' found".
The KB70102.SAR and KB70103.SAR packages from EHP4 have definitely been unpacked
and are available in /usr/sap/trans/EPS/in and we have prompted PREPARE to search EPS/in but it just returns to the previous error after searching.
It appears from the logs that the upgrade is expecting a "SAINT"
install package for SAP_BASIS and does not consider the KB70102/3
patches as acceptable?
Any clues as to why PREPARE is not accepting the SAP_BASIS packages and looking for a SAINT install?
Below is an excerpt from the EHP_INCLUSION.LOG
2 ETQ732 Package descriptions uploaded successfully
4 ETQ399 Looking for SAINT package for 'SAP_BASIS' ...
4 ETQ399 ... Read uploaded packages calling function module:
4 ETQ399      current: name = 'SAP_BASIS', release = '700'
4 ETQ399      patch type = 'U', ncvers-component = 'SAP_BASIS'
4 ETQ399 R3upReadNewPackages:
4 ETQ399   patchType='U', langVect='DEFS'
4 ETQ359 RFC Login to: System="CB1", Nr="00", GwHost="dbusrcb1", GwService="sapgw00"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "spda_read_new_packages" by RFC
4 ETQ399   ismovesVersion='0'
4 ETQ399 R3upReadNewPackages: exit: rc=0
4 ETQ399 ... No matching package found.
Regards,
Mike Tarr

Ok, I was able to download the K-701DHINSAPBASIS package from Service Marketplace and this resolved the SAP_BASIS problem. Thank you Markus for this solution.
I also downloaded the SAP_ABA, SAP_BW, and the PI_BASIS components and unpacked those as well in /usr/sap/trans/EPS/in.    My upgrade is now stuck asking for a SAINT package for SAP_ABA! I'm sure the SAP_ABA install, K-701DHINSAPABA, is unpacked and available in /usr/sap/trans/EPS/in.
The SAP_ABA files are definitely readable and there are entries in table PAT03_SDA for them.
I have a ticket open with SAP support but they have not had a solution yet for the SAP_ABA
Solution Manager failed to identify any of these packages as required in MOPZ.
I'm starting to wonder if anybody has ever done a 4.6C to ECC6 upgrade with EHP4 bound before?
Any ideas on the SAP_ABA would be appreciated. Here's a section of the EHP_INCLUSION.LOG file from PREPARE.
4 ETQ399 R3upReadNewPackages: exit: rc=0
4 ETQ399      Found: name = 'SAP_BASIS', release = '701', package = 'SAPK-701DHINSAPBASIS'
4 ETQ399 ... Matching package found: 'SAP_BASIS','701','SAPK-701DHINSAPBASIS'
4 ETQ399 (trc) R3upPatchDisassembleQueue: 1 package queue entries
4 ETQ399 (trc) R3upPatchDisassembleQueue: force=NO
4 ETQ399 (trc) R3upPatchDisassembleQueue: 0 packages will be disassembled
4 ETQ399 ... ... INST/UPG SAINT decision ok
4 ETQ399 ... EhP component SAP_ABA, 701
4 ETQ399 Looking for SAINT package for 'SAP_ABA' ...
4 ETQ399 ... Read uploaded packages calling function module:
4 ETQ399      current: name = 'SAP_ABA', release = '700'
4 ETQ399      patch type = 'U', ncvers-component = 'SAP_ABA'
4 ETQ399 R3upReadNewPackages:
4 ETQ399   patchType='U', langVect='DEFS'
4 ETQ359 RFC Login to: System="CB1", Nr="00", GwHost="dbusrcb1", GwService="sapgw00"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "spda_read_new_packages" by RFC
4 ETQ399   ismovesVersion='0'
4 ETQ399 R3upReadNewPackages: exit: rc=0
4 ETQ399 ... No matching package found.
4 ETQ010 Date & Time: 20090511150018

ECC/ERP Upgrading to EHP4 - basic steps?

Just installed fresh ERP/ECC 6 from disks labeled EHP4 ready. Needing to upgrade immediately to EHP4. To do this, my understanding is that I need to initiate a maintenance transaction from solution manager to start the process and then proceed (basically following these directions http://sap.wsteinert.com/blog/2009/10/implementing-the-ehp-4-part-2/ ).
Can anyone describe (in detail) the maintenance transaction process and what I have to configure on the solution manager side to get this up & going?
Also, does the EHP4 process require that I download the components? It looks like I already have some media that may have EHP4 components on it. Can I just do a local upgrade using the media?

> Can anyone describe (in detail) the maintenance transaction process and what I have to configure on the solution manager side to get this up & going?
You have to Create a maintenance transaction in the SAP Solution Manager and select the
appropriate technical usages in order to calculate the corresponding software
packages.
Refer https://websmp204.sap-ag.de/~sapidb/011000358700000293582009E.PDF
> Also, does the EHP4 process require that I download the components? It looks like I already have some media that may have EHP4 components on it. Can I just do a local upgrade using the media?
refer https://websmp104.sap-ag.de/~sapidb/011000358700000931872009E .
regards,
Nibu Antony

ECC 6.0 upgrade to EHP4 via EHPI - Problem

I'm upgrading an ECC 6 system to EHP 4.
In the extraction process I get the a strange error message:
Error: unknown hostname "<hostname>"
       The message server of your SAP system is not running,
       or the hostnames known by the message server are wrong.
I've checked. The message server is running and the hostname is known in my host file and in the server's hostfile.
Any idea's to what this is causing?

Hi,
Please help on this. I am getting the same error.
ERROR: unknown hostname "<hostname>"
       The message server of your SAP system is not running,
       or the hostnames known by the message server are wrong.
We have HA installation on Solaris.
Regards
Dhiraj

ECC6.0 - upgrade from EHP4 to EHP6 - cross release transports.

Hi Experts
We are planning to upgrade our system from ECC6.0 -EHP4 to EHP6.
Source - ECC6.0-EHP4
Target - ECC6.0-EHP6(Enhancement pack6)
Current ECC version -
SAP_BASIS 701 0014 SAPKB70114 SAP Basis Component
SAP_APPL 604 0013 SAPKH60413 Logistics and Accounting
We would like to know during the project if we can do a transport
between upgraded development ECC6.0 -EHP6 to non upgrade production ECC6.0-EHP4.
We have data from note 1090842 and 1273566.
But last 10 lines of note 1090842 are contradictory wherein on one side it says you can do transports between Releases 7.0*, 7.3* and 7.4* and
on other it says it can be problem if support pack levels are different on same release.(if problem can happen on same release with different pack
level then there are greater chances of issues between different releases).Note 1273566 is clear and suggest no issues exist yet for
technical and logical transports between suggested version 700/701 to >=702
Also below is the extract from SUM guide - (SUM-1.0-SP07)
RECOMMENDATION
We strongly recommend that you perform transports only between systems of the same release or enhancement package level, and where the same business functions are activated. If you do not follow this recommendation, you do so at your own risk regarding potential problems.
Please suggest if we need to create Dual maintainance parallel landscape during the tenure of project where two development system co-exist.One
with current and one with upgraded version and changes need to be done on both in parallel.Support fixes and LTO’s go from non upgraded dev to non upgraded prod.
Thanks

Hello
I won't perform cross version transport even if it can be possible.
As of 7.02 cross version transport are prevented by default with option SP_TRANS_SYNC (see here under note).
The best way is, if possible, to have a manual dual maintenance. All corrections created in the Ehp4 dev should be manually recreated in the Ehp6 dev.
What is usually done is to upgrade at first a copy of production for test/discovery purpose, the aim is to identify most of the regressions/evolutions. This will reduce the time you will have to spend in the migrated dev to adjust your system. You then migrate dev and enter in a freeze period where you reduce activity on legacy Ehp4 system to the minimum (bug correction for prod).
One good thing with the manual reprocessing of changes on the Ehp6 system is that this kind of constraint will help consultants to reduce their activity.
Regards
1742547 - Information about component version check in TMS

Eror upgrading from EHP4 to EHP5 , Database : MAxDB 7.8.0.14

Hello
I have updated Max db from 7.6 to 7.8 recenlty required to Upgrade ECC6.0 EHP5
Current ECC 6.0 EHP4 , NW 7.00 EHP1
Below is the i am getting while upgrading EHP5 through SAPEHpi
TOOLOUT.LOG-->
SAPehpi> Starting subprocess tp.exe with id 5580 at 20110503154658
EXECUTING tp.exe pf=J:\EHP5_INST\EHPI\abap\bin\DEFAULT.TPP getdbinfo WT9
Environment: JAVA_HOME=C:\j2sdk1.4.2_11
Environment: PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\j2sdk1.4.2_11\bin;E:\usr\sap\WT9\SYS\exe\uc\NTAMD64;E:\sdb\programs\bin;E:\sdb\programs\pgm;E:\usr\sap\WT9\SYS\exe\uc\NTAMD64
Environment: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
Environment: auth_shadow_upgrade=0
Environment: dbms_type=SDB
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
HALT 20110503154658
ERROR: *Cannot determine database version, database type is not defined in profile. [tpconnect.c,1158]*ERROR: EXIT(16) -> process ID is: 3176
Process with ID 3176 terminated with status 204
Please help
Regads
Jain Pankaj

> EXECUTING tp.exe pf=J:\EHP5_INST\EHPI\abap\bin\DEFAULT.TPP getdbinfo WT9
> Environment: JAVA_HOME=C:\j2sdk1.4.2_11
You Java version is 32bit and is ancient where you platform seems to be 64bit. I highly suggest using a recent JDK.
> Environment: dbms_type=SDB
I guess this is the problem, dbms_type must be "ADA".
Markus

Upgrade from R/3 4.6C to ECC 6.00 : languages

Hi,
We're trying to upgrade from SAP R/3 4.6C to ECC 6.00 under NT environment, having Oracle as database. During the preparation phase, we got the following error, and in our current SAP system R/3 we have 2 additional languages NL and FR (EN and DE are already in), can you please explain why this phase is blocking in this step, and if I continue I've to do a full language import, thanks in advance.
The following language(s) could not be updated yet:
- French       for component EA-APPL
- French       for component EA-DFPS
- French       for component EA-FINSERV
- French       for component EA-GLTRADE
- French       for component EA-HR
- French       for component EA-IPPE
- French       for component EA-PS
- French       for component EA-RETAIL
- French       for component ECC-DIMP
- French       for component ERECRUIT
- French       for component FI-CA
- French       for component FI-CAX
- French       for component FINBASIS
- French       for component INSURANCE
- French       for component IS-CWM
- French       for component IS-H
- French       for component IS-M
- French       for component IS-OIL
- French       for component IS-PS-CA
- French       for component IS-UT
- French       for component LSOFE
- French       for component PI_BASIS
- French       for component SAP_ABA
- French       for component SAP_AP
- French       for component SAP_APPL
- French       for component SAP_BASIS
- French       for component SAP_BW
- French       for component SAP_HR
- French       for component SEM-BW
- French       for component ST-PI
- Dutch        for component EA-APPL
- Dutch        for component EA-DFPS
- Dutch        for component EA-FINSERV
- Dutch        for component EA-GLTRADE
- Dutch        for component EA-HR
- Dutch        for component EA-IPPE
- Dutch        for component EA-PS
- Dutch        for component EA-RETAIL
- Dutch        for component ECC-DIMP
- Dutch        for component ERECRUIT
- Dutch        for component FI-CA
- Dutch        for component FI-CAX
- Dutch        for component FINBASIS
- Dutch        for component INSURANCE
- Dutch        for component IS-CWM
- Dutch        for component IS-H
- Dutch        for component IS-M
- Dutch        for component IS-OIL
- Dutch        for component IS-PS-CA
- Dutch        for component IS-UT
- Dutch        for component LSOFE
- Dutch        for component PI_BASIS
- Dutch        for component SAP_ABA
- Dutch        for component SAP_AP
- Dutch        for component SAP_APPL
- Dutch        for component SAP_BASIS
- Dutch        for component SAP_BW
- Dutch        for component SAP_HR
- Dutch        for component SEM-BW
- Dutch        for component ST-PI
Please mount another Language Disk for these language(s).
If you do not have further Language Disk(s), you may
continue, but the languages mentioned above will be lost
after the upgrade. A full language import has to be
performed after the upgrade to reinstall the language(s).
? continue
? cancel

Hi Markus,
I've introduce the following information:
> MOUNT POINT 07 = S:\export\Data\CDLAN2
> MOUNT POINT 01 = S:\export\Data\KN_WINDOWS_X86_64_AUPG
> MOUNT POINT 06 = S:\export\Data\CDLAN1
> MOUNT POINT 05 = S:\export\Data\CD3
> MOUNT POINT 03 = S:\export\Data\CD1
> MOUNT POINT 08 = S:\export\Data\UMN_WINDOWS_X86_64
> MOUNT POINT 02 = S:\export\Data\KN_WINDOWS_X86_64
> MOUNT POINT 04 = S:\export\Data\CD2
And in mount point 06/07 we have the languages.
The content of the trace file is:
here's the complete trace:
2007/07/05 16:35:01 *****************************
2007/07/05 16:35:01 Checking directories ...
2007/07/05 16:35:01 Searching for Data Carrier labeled AOXUPGR
Adding path: S:\export\Data\KN_WINDOWS_X86_64_AUPG
2007/07/05 16:35:01 Working on S:\export\Data\KN_WINDOWS_X86_64_AUPG ... no matching label
Adding path: S:\export\Data\KN_WINDOWS_X86_64
2007/07/05 16:35:01 Working on S:\export\Data\KN_WINDOWS_X86_64 ... no matching label
Adding path: S:\export\Data\CD1
2007/07/05 16:35:01 Resolving directory structure below S:\export\Data\CD1
Adding path: S:\export\Data\CD1\UPG1
Adding path: S:\export\Data\CD1\UPG2
Adding path: S:\export\Data\CD1\UPG3
Adding path: S:\export\Data\CD1\UPG4
Adding path: S:\export\Data\CD1\UPG5
Adding path: S:\export\Data\CD1\UPG6
2007/07/05 16:35:01 Directory structure below S:\export\Data\CD1 resolved
2007/07/05 16:35:01 Working on S:\export\Data\CD1 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD1\UPG1 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD1\UPG2 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD1\UPG3 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD1\UPG4 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD1\UPG5 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD1\UPG6 ... no matching label
Adding path: S:\export\Data\CD2
2007/07/05 16:35:01 Resolving directory structure below S:\export\Data\CD2
Adding path: S:\export\Data\CD2\UPG7
Adding path: S:\export\Data\CD2\UPG8
Adding path: S:\export\Data\CD2\UPG9
Adding path: S:\export\Data\CD2\UPG10
Adding path: S:\export\Data\CD2\UPG11
Adding path: S:\export\Data\CD2\UPG12
2007/07/05 16:35:01 Directory structure below S:\export\Data\CD2 resolved
2007/07/05 16:35:01 Working on S:\export\Data\CD2 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD2\UPG7 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD2\UPG8 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD2\UPG9 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD2\UPG10 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD2\UPG11 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD2\UPG12 ... no matching label
Adding path: S:\export\Data\CD3
2007/07/05 16:35:01 Resolving directory structure below S:\export\Data\CD3
Adding path: S:\export\Data\CD3\UPG13
Adding path: S:\export\Data\CD3\UPG14
Adding path: S:\export\Data\CD3\UPG15
Adding path: S:\export\Data\CD3\UPG16
2007/07/05 16:35:01 Directory structure below S:\export\Data\CD3 resolved
2007/07/05 16:35:01 Working on S:\export\Data\CD3 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD3\UPG13 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD3\UPG14 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD3\UPG15 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD3\UPG16 ... no matching label
Adding path: S:\export\Data\CDLAN1
2007/07/05 16:35:01 Resolving directory structure below S:\export\Data\CDLAN1
Adding path: S:\export\Data\CDLAN1\LANG1
Adding path: S:\export\Data\CDLAN1\LANG2
Adding path: S:\export\Data\CDLAN1\LANG3
Adding path: S:\export\Data\CDLAN1\LANG4
2007/07/05 16:35:01 Directory structure below S:\export\Data\CDLAN1 resolved
2007/07/05 16:35:01 Working on S:\export\Data\CDLAN1 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CDLAN1\LANG1 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CDLAN1\LANG2 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CDLAN1\LANG3 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CDLAN1\LANG4 ... no matching label
Adding path: S:\export\Data\CDLAN2
2007/07/05 16:35:01 Resolving directory structure below S:\export\Data\CDLAN2
Adding path: S:\export\Data\CDLAN2\LANG5
Adding path: S:\export\Data\CDLAN2\LANG6
2007/07/05 16:35:01 Directory structure below S:\export\Data\CDLAN2 resolved
2007/07/05 16:35:01 Working on S:\export\Data\CDLAN2 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CDLAN2\LANG5 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CDLAN2\LANG6 ... no matching label
Adding path: S:\export\Data\UMN_WINDOWS_X86_64
2007/07/05 16:35:01 Working on S:\export\Data\UMN_WINDOWS_X86_64 ... no matching label
Regards,
A.Kamel

EHP4 installation on top of ecc 6.0

Hi,
I have planned to install ecc 6.0 sr3 windows 2008 server oracle and put ehp4 on top of it.Pls guide me how to do that.
I have read the doc where they have told to provide space for the seperate shadow instance of 100 gb.I have planned to keep to keep 400 gb of hard disk for the ecc 6.0 installation.So do i need to provide extra space(new partition) for the shadow instance?and also i have read that finally this shadow instance will be converted to real instance.So my original space would go after converting in to ehp4?
also tell me what post installation to be done after ecc 6.0 installation.Say i do all the post installation for ecc 6.0 including client creation and clinet copy with update of stack to 14.After this do i need to do ehp4?
pls guide me in this as i need to it urjently.
Rajesh

> I have planned to install ecc 6.0 sr3 windows 2008 server oracle and put ehp4 on top of it.Pls guide me how to do that.
You have two possibilities:
- read the installation guides (http://service.sap.com/instguides) and try yourself
- get a basis consultant on your side to help you
> I have read the doc where they have told to provide space for the seperate shadow instance of 100 gb.I have planned to keep to keep 400 gb of hard disk for the ecc 6.0 installation.So do i need to provide extra space(new partition) for the shadow instance?and also i have read that finally this shadow instance will be converted to real instance.So my original space would go after converting in to ehp4?
A shadow instance will be built with parts of the tables of the source instance, the new coding from the EHP4 packages is imported and is then merged with your original instance. And yes, those 100 GB are free after that again.
> also tell me what post installation to be done after ecc 6.0 installation.Say i do all the post installation for ecc 6.0 including client creation and clinet copy with update of stack to 14.After this do i need to do ehp4?
Yes.
> pls guide me in this as i need to it urjently.
To start the installation you need an installed and configured Solution Manager system. You need that to generate the installation keys and to generate a valid XML file for the EHP4 installation.
And: This is here is a public forum, it's not meant to "teach" you. If you want some real guidance I suggest you attend some SAP classes if you have never done an installation before, especially if Oracle is involved.
Markus

Major considerations for the Upgrade from R/3 4.6c to ECC on HR Part.

Hi Experts,
We are doing an upgrade from SAP R/3 4.6c to ECC 6.0
What would be the impact on Personnel Administration and Organizational Management submodules of HR? and the major worries abt ESS and MSS. Currently my client is using ESS and MSS in portal that can retrieve the data from the Backend 4.6c system. while doing upgrade is there any prerequisites i need to met or is there any post upgrade activities for HR or is there Any dependencies?
Because there is a complete architecutre difference for ESS and MSS in both versions, so how can i manage the things without data inconsistencies?
Responses would be heighly appreciated.
Regards,
Srini

Hi Experts,
We are doing an upgrade from SAP R/3 4.6c to ECC 6.0
What would be the impact on Personnel Administration and Organizational Management submodules of HR? and the major worries abt ESS and MSS. Currently my client is using ESS and MSS in portal that can retrieve the data from the Backend 4.6c system. while doing upgrade is there any prerequisites i need to met or is there any post upgrade activities for HR or is there Any dependencies?
Because there is a complete architecutre difference for ESS and MSS in both versions, so how can i manage the things without data inconsistencies?
Responses would be heighly appreciated.
Regards,
Srini

Pre and post-upgrade tasks in BW for Upgrading R/3 4.6c to mySAP ECC 5.0

We are currently in the process of migrating our R/3 4.6c System to mySAP ECC 5.0.
We would appreciate if anyone could provide the major and minor
Changes / impacts / measures, to be taken in BW side.
<u><b>Questions:</b></u>
1. What are the major impacts on the extractors, mainly delta?
2. Do we need to activate all the datasource immaterial of its status?
3. Steps to be taken for Unicode conversion
4. Routines and structure change if any?
5. Is there any change in DDIC objects?
6. Any old methods that can be replaced by new methods? (for better performance e.g, LIS was replaced by LO)
7. Changes in the database.
8. Anyother issues
Any relevant document will be helpful.
Thanks & Regards
Chandran Ganesan

It depends on what you are taking about: functional or Technical.
Tehcnially, after the upgrade you should make sure all the PI are working fine. The other things (i.e. extract)should be able keep the same. Unless you want to take advantage of the new WAS640 functionaity.
If you plan to migrate your BW system into ECC 5.0, you might have long way to go.
Also, depends on your BW release. If it's BW 3.1 or below, you might need to upgrade by end of this year anyway.

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.

Upgrade to EhP4/NW 7.01 in ECC

Similar Messages

Maybe you are looking for