Upgrade ECC 5.0 to ECC 6.0

Hi,
Currently we have an R3 system running on ECC 5.0, meaning SAP_BASIS has release 640 we also have an CRM system running on (ECC 6.0?) SAP_BASIS 700. Now we want to use SAP Netweaver 2004s on both systems. As I read in previous formus this can not be done via hotpacks and we need to do a full upgrade. Does anyone has experience with this upgrade (in terms of time and changing functionallity)?
Thanks in advance,
Annemarie Vaessen

Hi,
Which version of CRM do you have now? 2004s SAP_BASIS is on 700 and ECC6.0 also on SAP_BASIS 700.
For Upgrade you have two options
1)Down time minimized
2)Resource minimized
The strategy depends on your company strtegy/scenario
Also keep in mind that ECC6.0 is ( mandatory) Unicode release so this might have an impact on you database depending upon which DB you have
http://sap.ittoolbox.com/groups/strategy-planning/sap-projectmanagement/r3-47-vs-mysapsap-enterprise-883745#
http://www.absoft.co.uk/absoft/web/site/AbsoftSAPServices/Upgrade.asp
Cheers,
Shyam

Similar Messages

Error in Upgrading ECC 6.0 to EHP4

Hi sap gurus,
Am upgrading ECC 6.0 to EHP4. now am in configuration phase. in the EHP_INCLUSION phase am getting a error:
" Severe error(s) occured in phase PREP_EXTENSION/SUBMOD_EXTENSION_NEW/EHP_INCLUSION!
Last error code set: Stack inclusion failed: patch level 53 for component EA-HR is too low, destination level is already at 55"
Then i downloaded the required patches of patch level service pack 56-61 and continued, but getting the same error..after that i checked the current status of the server. its having EA-HR component till service pack 55. but when i checked the stack XML file, its showing only EA-HR component SP02 to SP53. i think this error is due to the mismatch in stack XML file. i dono what should i do for this. should i need to alter the stack XML file manually? Please help me guys. my upgradation is hanging. please help me guys.
Thanks and regards,
Santhosh Kumar.

it is fine to assume that the stack file is mismatched with the system as the file suggested the ehpi to patch until level 53 but the original system already up to 55. if you are set on editing the xml file and this is not for production, you could try to remove the HR part entirely, just use find and try to remove all of that content that related to HR, be careful with the tag. just delete <software-component> until </software-component> for the HR part, remember to backup original file. it will avoid the error. Since the xml suggested 53 and the system already at 55 and assuming all other components correctly defined in the stack, i think it is fine to continue, and if i'm not mistaken after calculation with stack file, ehpi will offer to add support package level manually, you can add HR level until 61 or just leave it at 55 and add manually with spam later.
if this is for production system, i think you should go with AC suggestion, just find whats wrong with solman and reinstall using the right xml file.
Edited by: Henry Hsu on Oct 26, 2010 4:40 AM
Edited by: Henry Hsu on Oct 26, 2010 4:54 AM

Error AFAB after upgrade ECC 6

Dear All,
My company just upgrade ECC 6, but when I test it with AFAB,
test run
System gives message:
T E S T R U N was terminated Refer to the error log
No documents were created in this run
Error Log:
Number range 30 has not been created for document type AF.
Message no. AA738
Diagnosis
No valid number range interval has been created for document type AF.
Procedure
Specify an interval for number range 30 in the year 999 for company code .
Please help me.
Thanks
Ocep

Hi,
Kindly check in transaction FBN1 for Company code and number range 30 whether external number flag tick is marked or not. If it is marked , remove the same.
In ECC 6 above mentioned tick for external number flag is not required.
and later maintain number ranges for current period.
Hope this help you.
Regards,

How to upgrade ECC 6.0 SR2 to EHP4..

Dear all,
Currently we are on ECC 6.0 SR2 ABAP stack only
We are planing to upgrade to EHP4 .
Is Java stack mandatory for EHP4 ? If yes what in documents i need to go through....
If JAVA stack is not required, How hosuld i update to EHP4.
Regards
rahul

If Java is required or not depends on your scenario. If you only use the ABAP part now and you don't plan any other scenarios then Java is not required.
The guide can be found at
http://service.sap.com/instguides
--> SAP Business Suite Applications
--> SAP ERP
--> SAP ERP 6.0
--> SAP enhancement packages for SAP ERP 6.0
--> SAP enhancement package 4 for SAP ERP 6.0
Read here
Must Know document
How to install SAP Enhancement Package 4 guide
There is a separate forum here for EHP installations:
/community [original link is broken]
Markus

Re: Upgrading ECC 6.0 to EHP4 on Linux 32 bit.

Hi gurus,
    Am new to SAP. Basis. i've started a project on "Test upgrade of PRD server ECC 6.0 to EHP4" I finished installtion of SAP ECC 6.0 and took backup from PRD server and restored it in my test server. now i've to through my upgradation phase.
           Now i configured in solution manager and started maintenance optimizer. Now my problem is wen i configured in maintenance optimizer for the first time, i choose in 2. select files phase i chose the following options.
    2. select files --> calculate files automatically-Recommended.
                           --> Enhancement package
2.1 choose stack---> i tick 'media' only.
2.3 stack dependent files----> its selected some files showing totally 623 files ready to be download in download basket.
but due to collapse in download manager i missed some files..so i started the maintenance optimiser again in a new transaction. but i can find its selected some files by default including 'media; option with other options also. in the next phases also it defaultly selected all the files required for upgradation. but this time i can see only 298 files ready for downloading.. i dono which one is correct one. shall i go the first transaction or he new transaction.. please help me guys..
Thanks and regards,
Santhosh Kumar.

Hi,
Better make new transaction and choose again otherwise if you will miss some file then you will get error in upgrade.
Thanks
Sunny

Question about upgrading ECC 6.0 to EHP 4 and NW 7.0 to EHP 1

Hi All,
I have read articles about installing Enhancement Packs. How ever I am a little confused.
We are currently on ECC 6.0 and NW2004s. For Portal also we are on Nw2004s (EP 7.0 SP 16)
We want to install EHP4 for our ECC system. Do we have to install EHP1 for our NW side? Does this mean we need to upgrade our portal also to EHP 1?
Also, do we need to update our ESS and MSS business packages also?
I have an OSS note open about a VC issue. They have recommended us to upgrade to SP 18. if we install EHP 1 on Portal, do we still need to upgrade to SP 18 or all previous SPs are included in EHP1?
I really appreciate your help on this. If you can refer me to some docs which give more detail on EHP 1 for NW, I will greatly appreciate it.
Thanks in Advance
Preet

Hai,
Check the below link.....
SAP Enhancement Package 1 for SAP NetWeaver 7.0
/docs/DOC-7741#section4 [original link is broken]
Regards,
Yoganand.V
Edited by: Yoganand Vedagiri on Feb 7, 2009 1:06 PM

ERROR in ADD-ON conflict phase while upgrading ECC 6.0 system

Hi all,
I am having ECC 6.0 system and am upgrading its SAP-APPL component to 603 patch level 03. I was having SAP-APPL 603 but at patch level 0, i checked for all dependencies and defined the queue in SPAM and it showed all green (OK) for SAP-APPL and so i started but i faced error in add-on coflict phase. It said CRT needed for ADD-ON FICAX release 603. I searched alot but i cant find it on market place. This conflict occured for SAP-APPL 603 patch level 01 it said either include CRT as mentioned above or remove SAP-APPL 60301. Please help me out.

The conflict check detected conflicts between the Add-On FI-CAX release 603 and the OCS Package SAPKH60301.
The conflict check detected conflicts between the Add-On FI-CAX release 603 and the OCS Package SAPKH60302.
The conflict check detected conflicts between the Add-On FI-CAX release 603 and the OCS Package SAPKH60303.
Check the support packs of components FI-CAX on Service Market place, I think FI-CAX is dependant on SAPKH603301 and others so you can check the import condidtions of FI-CAX on service marketplace and update FI-CAX first then only you would be able to update patch of SAPKH60301
Regards
Subhash

Upgrading ECC 6.0 to EHP4

Hi guys,
I am a little kid in SAP. Before 30 days i don know what SAP is? am a newly joined trainee in basis in a concern.
now am given a oppurtunity to work on a project of "Test upgrade of Production server ECC 6.0 to EHP4".
i've to start my project. i've been preparing about the EHP4. but am not clear about the concept.will u guys give me the link for this upgrade guide??
i've seen that EHP4 has released as a new tool of installation unlike as other upgrade versions. And it allows to choose the netweaver component 7.0 for portal upgrade. Am not sure of this.please any guys, will u please elaborate about this concept??
And another thing is, my boss wants business suite 7.0 in that. i've no idea of business suite. when i asked my senior, he told that if u upgrade to EHP4, business suite components will be added to tht enhancement package. will u please exlain weather business suite is available in EHP4?
Thanks and Regards,
Santhosh.
Edited by: santhoshkumarvellore on Sep 4, 2010 4:40 PM

Hi,
Please get the upgrade document from servicemarket place.
https://websmp204.sap-ag.de/instguides or https://service.sap.com/instguides
You can do it from EHPI installer tool. this document also you can get it from above website.
From solution manager you can get the key and Stack file. download required support stack as per the stack file.
follow the steps in upgrade/Ehpi installer document.
Thanks and Regards,
Jibin,
Edited by: jibin singh on Sep 7, 2010 2:54 PM

Impact in portal for Upgrade ECC 5.0 SP04 to ECC 6.0

We are upgrading the ECC system from SAP_APPL 500 SP04(ECC 5.0) to SAP_APPL 600 EHP4 SP10(ECC 6.0) . I need to know what will be the impact on Portal 6.4 VErsion which is having ESS/MSS and BI integrated .

Hi GjEPCons ,
The Ess/mss application are standard some application webdynpro java and web dynpro abap so nothing happen upgrade one version to another version in backend and bi reports also but we can check the system object if case any thing happen ,
Ecc 5.0 and Ecc 6.0 nothing more change some features have add in Ecc 6.0 so we dont bother tome to upgrading .
Upgrade from ECC 5.0 to ECC 6.0
Hope this information help s to you
Thanks&Regards,
G.srinu

UPGRADE ECC 6.0 with AFS 6.3 from R/3 4.7

We are now preparing the upgrade of our R/3 server to ECC 6.0 with
AFS . As per the plan and SAP guide for upgrade we started the prepare
phase with upgrade master for ERP 6.0 . But in the initial stage i saw
the page of prepare it showing all the induatry specific components
like ECC DIMP ,IS_OIL etc . But we want to use AFS 6.3 . So if i
continue the installation all the industry specific addon installed .
So why because of the conflict iam should not apply AFS into our
server .
So kindly tell me how can i remove ECC DIMP like industry components
from the prepare phase .

good

Upgrading ECC 5.0 to ERP 6.0 EHP5

Hi -
We are planning to upgrade our ECC5.0(our present ECC 5.0 is on support pack stack 19) to ERP 6.0 EHP5.We are going to give a try in our Sandbox system first.So I have the following questions
1)Can we upgrade our ECC 5.0 directly to ERP 6.0 EHP5 or initially we need to upgrade to ERP 6.0 Stack 18 as available in SMP and then install EHP5?
2)Heard that Kernel will also be upgraded along with ERP 6.0 upgrade and no need to update Kernel separately.Is that correct?
or
3)Do we need to upgrade Kernel NW 7.0 SR3 first then upgrade to ERP 6.0 and finally install EHP 5.
Please let me know.
Thanks & regards,
Nagendra.
Edited by: Nagendra Devineni on Jul 19, 2011 6:01 AM

We are planning to upgrade our ECC5.0(our present ECC 5.0 is on support pack stack 19) to ERP 6.0 EHP5.We are going to give a try in our Sandbox system first.So I have the following questions
1)Can we upgrade our ECC 5.0 directly to ERP 6.0 EHP5 or initially we need to upgrade to ERP 6.0 Stack 18 as available in SMP and then install EHP5?
A) Yes, The current mass shipment release already contains EHP5.
Link for Master Guide
https://websmp203.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000731312&
2)Heard that Kernel will also be upgraded along with ERP 6.0 upgrade and no need to update Kernel separately.Is that correct?
or
A) Kernel will be upgrade automatically during the System Upgrade. You may wish to update to n or n-1 level available at the marketplace after the upgrade.
3)Do we need to upgrade Kernel NW 7.0 SR3 first then upgrade to ERP 6.0 and finally install EHP 5.
A) Since direct upgrade is possible, please read the master guide. You should be able to figure out the minimum levels required.
Br,
Venky

Upgrading ECC 5.0 to ECC 6.0

Dear Friends,
We are planning to upgrade our SAP version from ECC 5.0 to ECC 6.0.
I need some information from you all;
1. What are the advantages.
2. If we upgrade 32 - bit to 64 - bit what is the difference and why 64 - bit SAP is preferring, what would be the main advantages.
Please clear me in this, i need your support to enhance my knowledge before start the proposed.
Regards,
Praveen Merugu

Dear Praveen Kumar Merugu,
Since SAP Basis Release 4.0, the 64-bit SAP kernel has been available. The mySAP.com solutions which are based on Web Application Server 6.10 or higher are - with few exceptions - available as 64-bit versions only for operating systems based on 64-bit-capable hardware.
1. 64-bit mySAP.com, what's behind it?
In order to provide a R/3 system as 64-bit version the source code of the R/3 kernel was re-translated. However, the source code itself was not modified. The functions of the 64-bit and the 32-bit versions therefore do not differ.
Basically, 64-bit software differs from the 32-bit version only in the different manner of addressing the memory. 64-bit software uses a 64-bit address pointer which, in theory, can address 18 billion Gb of memory directly. Actually, a 64-bit application can address a lot less with the different operating systems and the hardware available, but still the addressing of several terabyte (that is several 1000 Gbyte) of memory is possible. This is considerably more than required by the components of the myAP.com software.
For a 32-bit address pointer, the address space is limited to about 4 Gbyte; in reality, even less is available to the application. There are examples where this 4 Gbyte limit prevents an efficient operation of a mySAP.com system.
2. Advantages of the 64-bit technology for mySAP.com
The administration of the SAP system is considerably facilitated.
The SAP software can scale the available hardware (RAM, CPU) to a much higher degree.
3. System requirements for 64-bit mySAP.com
a) 64-bit-capable hardware
A basic requirement for using 64-bit operating systems and 64-bit applications is a 64-bit-capable hardware. In particular the version of the used processors (CPU) determines the 64-bit capability of existing hardware. For information on the compatibility of the hardware with 64- bit operating systems you should contact the responsible person at your hardware partner.
b) 64-bit operating system
For using a 64-bit SAP software, an upgrade to a 64-bit operating system may be required. For releases, please refer to the release notes that are available for each database for each SAP kernel release.
c) 64-bit database
When using a 64-bit mySAP.com software, a combination with a 64-bit database version (RDBMS) is recommended by SAP. Databases of SAP, IBM, INFORMIX, and ORACLE have already been supported as 64-bit versions since SAP release 4.0.
4. Exceptions
a) Operating systems on servers with Intel Pentium processors.
The Intel Pentium processor is a 32-bit processor. For this reason, the SAP Software for Microsoft Server operating systems and Linux will still be available in the 32-bit version for the next years to come. In the long run, SAP will change over to the 64-bit version of the SAP software also on these platforms which requires 64-bit Itanium processors. When changing over to the 64-bit version, SAP will also take into account the investment security of their customers.
b) DB2 UDB for Unix and Windows (DB6):
Since the DB2 UDB database allows a mixed operation of 32-bit and 64-bit database client applications as of version 8 only, SAP will make available 32-bit SAP Software of Release 6.x for DB2 UDB systems until the end of 2003.
5. Availability of 64-bit mySAP.com solutions
The latest information on R/3 Release planning can be found on the SAP Website under http://sapnet.sap.com/platforms. Detailed information on the platform combinations released by SAP can be found in SAP release notes under the XX_SER-SWREL component.
All existing 32-bit 4.x releases are supported with 32-bit versions of the SAP kernel until futher notice.
6. Availability of the different 64-bit mySAP.com solutions
a) R/3
R/3 is available as of release R/3 4.0.
b) Business Information Warehouse (BW)
Business Information Warehouse is available with 64-bit SAP kernel as of version 2.0A.
c) Enterprise Buyer Professional (EBP), former BBP
EBP is available with 64-bit SAP kernel as of version 2.0A.
d) Customer Relationship Management (CRM)
Customer Relationship Management is available with 64-bit SAP kernel as of version 1.2.
e) Advanced Planner and Optimizer (APO)
APO is available with 64-bit SAP kernel as of version 3.0A.
7. Possible combinations of 32-bit and 64-bit
a) Possible combinations within a SAP system
For the SAP releases as of 4.0B, a mixed use of 32-bit and 64-bit instances within one SAP system is supported on application server level. 32-bit and 64-bit SAP instances must reside on separate servers, however. The mixed use of 32-bit and 64-bit SAP instances on the same server is not supported.
For the SAP releases as of 4.0, the combination of 32-bit SAP application servers with a 64-bit database server, and of a 32-bit database with 64-bit application servers is possible in principle. Releases for such combinations are granted in justified cases. In case of a mixed installation of a 32-bit SAP application server and a 64-bit database server or vice versa on a shared host, you need to make sure in particular that the SAP application server uses the correct database libraries. A subsequent manual configuration may be required. The database upgrade guide describes how to proceed (see also Ora Note 406140 or 539922, for example).
b) Possible combinations within a mySAP.com system landscape
Transports with 'tp' or 'R3trans' between 32-bit and 64-bit SAP systems are possible.
There are many differences between a 32-bit and a 64-bit SAP system, e.g. the parameter settings of the HP-UX operating system kernel and SAP kernel that do not take into account a combined configuration of test and production systems.
All features and functions that depend on the parameter settings cannot be sufficiently tested for a 64-bit production environment in a 32-bit test or development system. This includes in particular the effect of the parameter settings on the memory management and the performance of a SAP system.
For this reason, SAP recommends to have at least one other 64-bit system available for each 64-bit production system within the transport track where the availability of SAP kernel, operating system and database can be tested.
c) Interoperability with 32-bit add-on products
For software products of third-party suppliers used with SAP software it is not important whether a 32-bit or a 64-bit SAP R/3 kernel is used. The use of a 32-bit or 64-bit SAP R/3 kernel is completely transparent for add-on products of third party suppliers as long as these products use SAP certified interfaces.
32-bit and 64-bit applications that directly access shared memory segments cannot be combined. For add-on products of SAP with direct access to the shared memory you have to ensure the bit size corresponds to that of the SAP kernel. This is e.g. valid for the product 'saposcol'. With a 64-bit SAP kernel it is only possible to use a 64- bit saposcol.
8. Preparations for the installation of a 64-bit SAP kernel
In addition to the basic requirements, 64-bit hardware, 64-bit operating system and 64-bit database the following aspects are to be taken into account for preparing the installation of a 64-bit SAP kernel:
a) Shared memory
Since there is virtually no limit of the shared memories in the case of a 64-bit SAP you can set large sizes for all buffers. (Refer to the recommendation of SAP Note 103747 under III).
b) Swap space
Addressing a very large memory requires the configuration of a correspondingly large swap space. To use a 64-bit SAP kernel you must at least configure 20 GB swap space.
c) Operating system kernel parameters
Except for some cases the parameter settings of the operating system kernel for a 32-bit and a 64-bit R/3 are identical. he most important operating system kernel parameters and their values recommended by SAP can be found in Note 146289. For HP-UX please also refer to Note 172747.
INSTALLATION TIPS
The installation of the 64-bit SAP kernel for Release 4.0B and 4.5B is carried out manually. First the system requirements described above must be fulfilled . The installation of the 64-bit SAP kernel is then simply performed by replacing all existing 32-bit executables of the SAP kernel with the corresponding 64-bit executables.
Example:
Initial state:              SAP release       4.5B
             SAP kernel        4.5B 32-bit
             RDBMS             ORACLE 8.0.5 64-bit
             OS:               HP-UX 11.00   64-bit
Target:              SAP release       4.5B
             SAP kernel        4.5B 64-bit
             RDBMS             ORACLE 8.0.5 64-bit
             OS:               HP-UX 11.0   64-bit
Procedure:
The procedure is described in detail in the following SAP notes:
SAP note: 146248    Installation of SAP R/3 4.0B 64-bit kernel
SAP note: 155355    Installation of SAP R/3 4.5B 64-bit kernel
Installation of the 64-bit SAP kernel as of SAP Basis release 4.6B
As of SAP release 4.6B the installation tool R3SETUP is delivered and supported as 64-bit version on CD.
System copy with 64-bit SAP 4.5B (ORACLE)
While unloading an Oracle database with the R3SETUP (32-bit version) it cannot connect to the database if a 64-bit SAP kernel is used.
If you use the 64-bit SAP kernel for Oracle you automatically use a 64- bit Oracle client library as only a 64-bit library can be loaded for a 64-bit SAP kernel. However, since the R3SETUP is only available as 32- bit version up to Release 4.5B and since the 32-bit R3SETUP is not compatible with the 64-bit Oracle client library the error mentioned above occurs in the case of a system copy (in particular during the unload).
While loading the 32-bit SAP kernel is unpacked first so no problems should occur here.
In order to be able to perform a system copy (unload) with the 32-bit R3SETUP follow the instructions of Note 177724.
UPGRADE TIPS
Upgrade from a 32-bit to a 64-bit SAP system
The operating system upgrade and the SAP upgrade should be performed separately (if possible). The same applies to the change of the 32-bit SAP kernel to the 64-bit kernel to ensure that the phases can be tested and completed separately.
As of 4.6C the change to a 64-bit SAP kernel will be supported during an upgrade.
That means that the individual phases like operating system upgrade, database migration and kernel exchange should be included in the planning.
Database
For a database, you need to check whether the binaries have to be replaced during the operating system upgrade. The binaries for HP-UX 10.20 do not run on HP-UX 11, for example!! The corresponding Oracle software for HP-UX 11 must be installed. When upgrading to a 64-bit Oracle 8 version you have to migrate to a 32-bit Oracle 8 version fist. Only then, you can import the 64-bit RDBMS.
The SAP upgrade should always be carried out before the 32-bit SAP kernel is replaced by the 64-bit SAP kernel, since the latter includes an adjustment of the UNIX kernel and the instance parameters.
Sample scenario 1:
     Initial state:                          R/3 release 3.1I
                         SAP kernel 3.1I (32-bit)
                         RDBMS:      ORACLE 7.3.4 (32-bit)
                         OS:         HP-UX 10.20 (32-bit)
    Target:                         R/3 release 4.6B
                        SAP kernel   3.1I (32-bit)
                        RDBMS:       ORACLE 8.0.5 64-bit
                        OS:          HP-UX 11.0 64-bit
Procedure:
1st alternative:
9. Upgrading the operating system to HP-UX 11.0
10. Installation of the 7.3.4 RDBMS binaries for HP-UX 11.0
11. Migration to 8.0.5 32-bit RDBMS for HP-UX 11.0 (see the instructions guide). This step is required as the database migration from 7 to 8 must always be performed via Oracle 8 32-bit.
12. Subsequent exchange of the RDBMS 8.0.5 32-bit to 8.0.5 64-bit. This step can be performed after the upgrade as well (prior to the SAP kernel exchange).
13. Upgrade of the R/3 system to 4.6B with a 32-bit SAP kernel. The PREPARE unpacks the 32-bit tools automatically so that no manual intervention is necessary.
14. Exchange of the SAP R/3 kernel on 64-bit prior to the upgrade and adjustment of the R/3 kernel and instance parameters
2nd alternative:
15. Migration to 8.0.5 32-bit on HP-UX 10.20
16. Operating system upgrade to HP-UX 11.0
17. Exchange of RDBMS binaries on 8.0.5 64-bit for HP-UX 11.0
18. Upgrade of the R/3 system to 4.6B with 32-bit SAP kernel
19. Exchange of the SAP R/3 kernel on 64-bit
Or (if required)
3rd alternative:
20. Oracle migration to 8.0.5 32-bit (on HP-UX 10.20)
21. Upgrade of the R/3 system to 4.6B with 32-bit SAP kernel
22. Operating system upgrade to HP-UX 11 64-bit
23. Exchange of the Oracle binaries on 8.0.5 64-bit
24. Exchange of the SAP kernel on 4.6B 64-bit
Sample scenario 2:
Initial state:                R/3 release    3.1I
               SAP kernel     3.1I (32-bit)
               RDBMS          Oracle 7.3.4 (32-bit)
               OS             HP-UX 10.20 (32-bit)
Target:               R/3 release     4.5B
              SAP kernel      4.5B 64-bit
              RDBMS           Oracle 8.0.5 64-bit
              OS              HP-UX 11.0 64-bit
Procedure:
The procedure is similar to the one described in the 1. scenario. However, in this case it is not possible to already import the 64-bit SAP kernel in the upgrade phase KX_SWITCH as the 64-bit kernel for Release 4.5B will not be delivered on the upgrade CD. The import of the 64-bit SAP kernel must be manually performed after the SAP upgrade. Release 4.5B will not be delivered on the upgrade CD. The import of the 64-bit SAP kernel must be manually performed after the SAP upgrade.
Do let me know in case of any queries.
Hope this helps you.
Do award points if you found them useful.
Regards,
Rakesh

Need your help to upgrade ECC 6.0 SPS 6 to Current

Hi gurus,
I know there are lots of document but not able to reach any decision. I am kind of confusion with what to do. I am thinking I will get my answer with the experts in this forum.
Current environment: SAP ERP ECC 6.0 SPS 6 Kernel 700 release and level 179 windows NT x64 and MS SQL 8.00 179 level
Requirement: update the environment to current.
With research either can go from SPS 6 to SPS 17
OR
update to SPS13 and then upgrade to EHP4 (not quite sure about this)
But if you go EHP4 might require hardware or memeory or other changes.
Question:
Detail Steps to
What are the steps required and time to complete the upgrade going from SPS 6 to SPS 17?
What are the steps required and time to complete the upgrade going from SPS 6 to EHP4?
Everybody might say this depend on the data and other customization etc.
But still there will be standard steps and time which will help me to complete the process.
Please let me know the steps and process to complete this.
what are the steps we need to adapt in order to Minimize System downtime.
Thanks in Advance.
Krish

Krish,
SAP Course ADM326 include the content for ECC enhancement package upgrade, probably it's worth to you to start from the training course if you hate to read guides in SAP service marketplace.
Cheers,
Denny

Upgrade ECC 6 Message AC435 inconsistent rounding entries were corrected

When I go in the transaction OAYO in ECC 6 I get the message AC435:
CoCd XXXX, area 01: inconsistent rounding entries were corrected
Message no AC435.
You entered a capiatlization version in the area cost accounting depreciation. A capiatlization version is not allowed in this depreciation area however, since there is always 100% capitalization in this area
System response
Remove the capitalization version, or change the type of the
depreciation area.
If you set the area type to "cost-accounting valuation" after you
already entered the capitalization version, then you first have to
change back the type of the area. The "capitalization version" field is
then displayed again by the system, and you can remove the version you
entered.
The system give this message for all items. When I do the same in 4.6 there is no message.
Then ECC 6 want to save these new settings. Can I save this! and what is then changed?

Thanks,
I had a look to the note's and I let it as it is. When there is a test system before his refres a will tray this change and see what the result is. Functional I don't have any problems.
But in the in future this will come back.

Improvements - Upgrade ECC 6.0

Dear all,
Does anyone know the improvements between 4.7 to ECC 6.0 version?
Iu2019m studying the differences between them, and I have to explain new functionalities and better ways involving the 2 versions.
Does anyone have guides that may help me to understand the differences?
I want to discover opportunities to improve my client business.
Please help me.
Regards,

Hi,
In order to check functional difference, you can check on http://service.sap.com/erp-ehp.
You can also use solution browser tool to compare the both releases using below link:
http://solutionbrowser.erp.sap.fmpmedia.com/
Thanks
Sunny

Upgrade ECC 5.0 to ECC 6.0

Similar Messages

Maybe you are looking for