Ecc 4.7 to Ecc6.0 Upgrade

Hi
We are Upgrade Ecc 4.7 R/3 Enterprice to Ecc 6.0
Can any one tell what are procedure to do a Upgrade
Regards
haynes

Refer
http://www.thespot4sap.com/upgrade_guide_v2.pdf
http://sap.ittoolbox.com/documents/popular-q-and-a/%20sap-upgrade-4453
https://websmp101.sap-ag.de/instguides
www.sap.com/services/servuptech/bestpractices/index.epx
Solution Browser would give the differences (Features):
http://solutionbrowser.erp.sap.fmpmedia.com/ Give source and target versions.
Release Info:
ECC 6.0:
http://help.sap.com/saphelp_erp2005/helpdata/en/43/68805bb88f297ee10000000a422035/frameset.htm
ECC 5.0:
http://help.sap.com/saphelp_erp2004/helpdata/en/c6/feda40ebccb533e10000000a155106/frameset.htm
You can find the difference in release notes of each SAP version.
Here are the links.
http://help.sap.com/saphelp_47x200/helpdata/en/fc/e3003deddfae4de10000000a114084/frameset.htm
http://help.sap.com/saphelp_scm50/helpdata/en/28/b34c40cc538437e10000000a155106/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/43/68805bb88f297ee10000000a422035/frameset.htm
hope this will help you ,
cheers
dEE

Similar Messages

Upgrading SAP ECC 5.0 to ECC6 phase GETSYNC_PREUP_FINI_D

I'm in process of the Upgrading SAP ECC 5.0 to ECC6 And, now it is in upgrade phase GETSYNC_PREUP_FINI_D. But, phase in GETSYNC_PREUP_FINI_D the Upgrade already runs to 24 hours.
============================================
The following START modes are available:
- Repeat phase GETSYNC_PREUP_FINI_D to continue
   the upgrade at the point it stopped.
- Initialize phase GETSYNC_PREUP_FINI_D to restart
   this phase from the beginning.
- Initialize and run another upgrade phase
   (caution, refer to your installation guide).
- Exit this program.
> repeat
>> 2008/10/22 11:49:04 UPGRADE/SWITCH: START OF PHASE GETSYNC_PREUP_FINI_D
The parallel running J2EE upgrade needs some more time...
Please be patient...
===============================================
Database: MSSQL2005
What could be the problem. I can skip it and go to the next stage???
Please help me out solution.?
Regards
Marcelo P. Silva

It seems that you have a combined upgrade - ABAP + Java in your system - is that right? If yes, did you start the Java upgrade in parallel?
Markus

ECC6.0 Upgrade and BW Extractors

Hi Experts,
We are doing a Source system upgrade from 4.6c to ECC6.0 just a Technical upgrade. Can you please let me know if we need to delete all the delta queues and re-initialize delta.
Following are the 4.6c Pre- Export Activities in relation BW.
1. Lock the users
2. Clear the entire delta queues in RSA7 (till we achieve - 0 records in BW) and make sure no outbound queues are empty in SMQ1
3. Delete Set -up table data.
4. Reshedule V3 Jobs
5. ReSchedule - BW process chains
After upgrading to ECC6.0
1. SM59 connections with new system.
2. Restore Source System connections in RSA1
3. Replicate DS and Activate Transfer Structure. (In relation to BW: we have done the technical upgrade from 3.x to BI7.0 (but the datasoucre and data flow are still 3.x).
After all Post processing of ECC6.0 Upgrade activities, the source system is only available to users for posting the transaction.
Please let me know if we need to delete all the delta queues and re - initialize delta.
1.We are not installing any new business content extractors from ECC6.0 - Just using same 4.6c extractors and structures.
2.And consider that no users post any transaction after clearing the delta queues in RSA7.
Appreciate your feedback,

Hello Subbu,
There is no need to reinitialize the extractors, the steps you mentioned in your original post are enough, the reason
for these steps is to make sure that there is no data left in sm13, lbwq, ras7, setup tables etc, you need to run the related infopackages twice on the BW side to clear the BW repeat part of the queue in RSA7, if you have a doubt that this was
not done you can goto rsa7, select the queue and on the next screen you can check if there is any data available in the
delta repeat part of the queue.
The reason for the step is that that the upgrade could potentially change an extract structure for a datasource and then if you
have data in the old format it may not be possible to upload it in the old format.
I repeat though there is NO need to delete the current entries in RSA7 and reinitialize.
Best Regards,
Des

ALV Layouts are missing in ECC6 after upgrade

Dear Friends,
we have an issue of missing ALV Layouts in ECC6 after upgrade of ECC6 from 4.7 version
For example, we have a custom table ZRCILOT, data displayed using tocde se16, but when we check layout are missing in ECC6 but the same exist in 4.7 version.
please check the attached screen-shots.
kindly suggest, is there any possibility to retrive it.
Thanks,
Munvar Basha.

Hello
Variants should be preserved by the upgrade...
You could export/import layout using the report from the here under note
Regards
551178 - FAQ ALV Layout
During the upgrade of or when importing Support Packages?
Answer: Layouts created by the customer are retained and you can continue to use them.
643330 - ALV layout: Importing and exporting layouts

Impacts on ECC6 Functional Upgrade

We have just technical upgraded our SAP ERP 4.6 to ECC6 recently, we're soon going to perform the functional upgrade of the ECC6.
I would like to check if the ECC6 functional upgrade will have any impact to our existing BW 3.5 system?
Please advice, thanks.

i dont think, the new plugins will impact your BI system. if you go for the technical upgrade, this may break your source system connection and that time you have to do source system restrore connection.
Other than that, no major impacts would be happened in the BI system.

Upgrade from ECC 5.0 to ECC6.0

Hi All,
Can you please explain and list down the differences you observed from SAP ( SAles and Distribution ) point of view , while moving from ECC 5.0 TO ECC 6.0.
Thanks
Umesh S.

Hi,
If you want to compare difference between ECC 5.0 and ECC 6.0 functionally then you can use below link to compare both releases:
http://solutionbrowser.erp.sap.fmpmedia.com/
Thanks
Sunny

ECC6.0 upgrade issue with IDoc release

Hi experts,
we are in the process of upgrading our ECC environment from 5.0 to 6.0. We have quite a few interfaces which use ORDERS/Invoice Idocs in customised form. In ECC5.0 environment, we had developed a Z segment in the ORDERS Idoc and the segment release was set as 640. Everything worked fine in ECC5.0.
In upgraded environment, SAP has released new version of some segments. one of those is E1EDP01. This segment has 2 new versions in ECC6.0 environment - 007 and 008. This change in the version changes the data in the IDoc and hence interface goes in error at the EDI provider.
We have tried to use 640 as the IDoc segment release in the partner profile of the IDocs. This still gives us an issue because the 007 version of the segment E1EDP01 has release 620 and hence the Idoc picks up 007 version instead of 006 version as desired. When we change the partner profile with Segment release in the IDoc type as 46C, it gives us an issue in the Z segment saying that the IDoc segment is not released in 46C and the Idoc goes in error.
has any one faces such situation in the past? if yes, please throw some light.
Thanks in advance.

Hello,
Iam new to SAP. Thars why i cant understand well to do upgrade,
Then i found out some notes from internet about Upgrade : SAP Note Number 857904 (upgrade from Release 6. To 7.0).
In that notes,
Actually i would like to know about some key words (for example : ASSIGNING, REPLACE, TRANSFER. ) which how to work in the Release 7.0
Always i have some objets in 4.6C.
Ex 01: READ DATASET p_dataset INTO wa_record
Ex 02 : TRANSFER i_crhu TO p_crhd
LOOP AT i_crhd.
*disable controls in crhd
    PERFORM f_disable_crhd.
    TRANSFER i_crhd TO p_crhd.
    IF sy-subrc NE 0.
      MESSAGE a045.        "Error when transfering data to error file
    ENDIF.
ENDLOOP.
CLEAR i_crhd.
CLOSE DATASET p_crhd.
IF sy-subrc NE 0.
    MESSAGE a039.                      "Error at close dataset
ENDIF.
OPEN DATASET v_crhd FOR OUTPUT IN TEXT MODE.
And then i have some FM (ex : WS_UPLOAD , WS_DOWNLOAD)
So I have changed the code for WS_UPLOAD by GUI_UPLOAD
                              and WS_DOWNLOAD by GUI_DOWNLOAD
now my problem is to know about some key word which how to work in ECC6 (for example ASSIGNING, REPLACE, TRANSFER. )
thanks in advance
Rathy

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

ECC6.0 upgrade and BW steps for mapping the new ECC6.0 source system

Hello gurus
We are upgrading from R3 4.6C to ECC6.0. We use BW 7.0 SP 18. We will create the new ECC6.0 source system in BW, replicate metadata and everything. The question is how do we copy or reassign the existing objects pointing to our current 4.6c dev system (transfer rules, transformations, infopackages, process chains) to point to the new ECC6.0 dev system ? As a note, we also need to keep the current 4.6c source system objects until go-live o ECC6.0.
What is the common practice in such a case ? I am sure we are not unique...
A prompt response would be appreciated.
Thank you all.

So the plan is to copy dev R3 and upgrade that - then Q r3 copied and upgrade that - then upgrade directly prod R3?
If so - then if it were me - I would firstly prove all this in a sandbox environment where BW dev points at an upgraded sandbox R3 ecc
ie same logical system
Then once that is proved I would organise downtime of BW development for a few months whilst the d-q-p ecc happens
Then when they copy dev r43 to ecc r3 i would then just point BW dev at the new ecc box and go from there (ie clear the deltas - change the logical system name to the new ecc box - replicate meta data - transtru all the datasources - run the process chains nothign to worry about)
However if you cant afford the down time - you may have to have an alternative transport route - ie copy dev BW to a another dev bw box and have an alternative path to production for issues
Then once everything is upgraded redo the changes through d-q-p to get the transports back in line (thats what we did)

SAP ECC 6.0 service pack level upgrade from 15 to 18 impact on SAP SRM 5.0

Hi All,
What all needs to be tested in SAP SRM when we upgrade SAP ECC6.0 service pack level from 15 to a8.
I am already facing issue in BBPGET VD and HR Interface with SAP SRM.Workflow issue while testing in EBQ.
Kindly let me know is anythings needs to be tested.
Regards
Vivek.

Hello,
There are no known issues related to ECC 6.0 support package upgrade when this system is integrated with SRM 5.0.
Since SRM 5.0 is fully supported with ECC 6.0.
Regards,
Ricardo

ECC 5.0 and ECC6.0

Hi SAP Gurus
Can any one please explain the mail differences b/w ECC 5.0 andECC 6.0 in terms of Security implementation/upgrade.
Thanks in advance
KV
P.S : This is kind of urgent. Any information will be appreciated. Thanks

ECC5.0 is ERP2004,centeral component NW04
While ECC6.0 is ERP2005 centeral component NW04s ,it comes with EP,WAS & Etc.
Message was edited by:
saumin oza

SAP 4.7 to ECC6 EHP5 Upgrade inc.OGSD - "/ICO/MOC_NEW_GUI" nametab error

Hello all,
I'm currently running a SAP upgrade from 4.72 to ECC6 EhP5 SPS6.
This upgrade include OGSD upgrade from4.72 SP12 to OGSD 6.10 SP5.
Duing phase upgrade phase RUN_RSPTBFIL_DEST, I have the following error message : Could not read nametab "/ICO/MOC_NEW_GUI".
According to OSS note 1377262, I download fix A61000INOGSD.SAR and extract file A-61000INOGSD.SAP in <upgdir>/cofiles (and also in <transdir>/cofiles).
Phase RUN_RSPTBFIL_DEST is still in error when I repeat it.
I note that content of A-61000INOGSD.SAP file is a little bit different regarding my error message:
Inside file:
I 2EETW109 table "/ICO/MOC_NEW_GUI" does not exist in nametab.
My error message:
2EETG011 "[DESTINFO] Could not read nametab""/ICO/MOC_NEW_GUI"
Many thanks for your help & feedback,
Chris

Hello Chris,
we experienced the same issue as you.
After discussion with the SAP Support team, it appears that this migration path is not the good one.
The right procedure is now to upgrade to ECC6 EhP5 with OGSD 6.10 SP0 and then to apply manually the SPs you want on OGSD add-on.
I think they are currently updating the corresponding OSS Notes.
I hope it will help.
Vincent

Runtime Errors SYNTAX_ERROR in SAPLS_CODE_INSPECTOR after the ECC6.0 upgrad

we recently upgraded our development test sandbox from 46C to ECC6.0 using downtime minimized strategy for practice purposes.After a sucessful completion of the upgrade we applied all the support packages successfully upto the latest available. Upon testing we found that everything else works fine except code inspector. Everytime we go to transaction sci we get syntax error
Runtime Errors         SYNTAX_ERROR
Date and Time          08/20/2008 08:26:29
Short text
     Syntax error in program "SAPLS_CODE_INSPECTOR ".
What happened?
     Error in the ABAP Application Program
     The current ABAP program "????????????????????????????????????????" had to be
      terminated because it has
     come across a statement that unfortunately cannot be executed.
     The following syntax error occurred in program "SAPLS_CODE_INSPECTOR " in
      include "LS_CODE_INSPECTORTOP " in
     line 11:
     ""SCI_DYNP" must be a flat structure. You cannot use internal tables, s"
     "trings, references, or structures as components. ."
     The include has been created and last changed by:
     Created by: "SAP "
     Last changed by: "CRENSHAWDP "
     Error in the ABAP Application Program
     The current ABAP program "????????????????????????????????????????" had to be
      terminated because it has
     come across a statement that unfortunately cannot be executed.
What can you do?
     Please eliminate the error by performing a syntax check
     (or an extended program check) on the program "SAPLS_CODE_INSPECTOR ".
     You can also perform the syntax check from the ABAP Editor.
If the problem persists, proceed as follows:
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
r analysis
The following syntax error was found in the program SAPLS_CODE_INSPECTO
""SCI_DYNP" must be a flat structure. You cannot use internal tables, s
"trings, references, or structures as components. ."
to correct the error
Probably the only way to eliminate the error is to correct the program.
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
   To save the description, choose "System->List->Save->Local File
2. Corresponding system log
    Display the system log by calling transaction SM21.
    Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
    In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
tem environment
SAP-Release 700
Application server... "kiel"
Network address...... "138.254.140.161"
Operating system..... "AIX"
Release.............. "5.3"
Hardware type........ "000B7B2ED600"
Character length.... 8 Bits
Pointer length....... 64 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "kiel"
Database type..... "ORACLE"
Database name..... "UPD"
Database user ID.. "SAPR3"
Terminal................. "D800204486"
Char.set.... "en_US.ISO8859-1"
SAP kernel....... 700
created (date)... "Jun 22 2008 20:58:25"
create on........ "AIX 2 5 005DD9CD4C00"
Database version. "OCI_102 (10.2.0.2.0) "
Patch level. 166
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"
Memory consumption
Roll.... 16128
EM...... 8379840
Heap.... 0
Page.... 40960
MM Used. 705904
MM Free. 3481488
r and Transaction
Client.............. 070
User................ "CRENSHAWDP"
Language key........ "E"
Transaction......... "SCI "
Transactions ID..... "48AB59A7D7E00112E10080008AFE8CA1"
Program............. "????????????????????????????????????????"
Screen.............. " "
Screen line......... 0
Information on where terminated
Contents of system fields
Name     Val.
SY-SUBRC 0
SY-INDEX 0
SY-TABIX 0
SY-DBCNT 0
SY-FDPOS 0
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY
SY-UCOMM
SY-TITLE
SY-MSGTY
SY-MSGID
SY-MSGNO 000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO 0
SY-DATUM 20080820
SY-UZEIT 082629
SY-XPROG
SY-XFORM
Internal notes
    The termination was triggered in function "ab_genprog"
    of the SAP kernel, in line 1551 of the module
     "//bas/700_REL/src/krn/runt/abgen.c#10".
    The internal operation just processed is " ".
    Internal mode was started at 20080820082629.
    Program name.........: "SAPLS_CODE_INSPECTOR ".
    Error message........: ""SCI_DYNP" must be a flat structure. You cannot use
     internal tables, s".
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
=> 64 bit R/3 Kernel
=> 64 bit AIX Kernel
=> Heap limit      = 2684354560
=> Stack limit     = unlimited
=> Core limit      = unlimited
=> File size limit = unlimited
=> Heap address = 0x11716f260
=> Stack address = 0xfffffffffff2a20
=> Stack low     = 0xfffffffffff2a20
=> Stack high    = 0xffffffffffff710
=> Stack Trace:
#AixStack() at 0x1000a2474
#CTrcStack2() at 0x1000a256c
#rabax_CStackSave__Fv() at 0x1000d0e04
#ab_rabax() at 0x1000cd7e4
#ab_genprog() at 0x100b3d5f8
#newload__FPCcP13TmpSubpoolDirUiPUi() at 0x1002194ac
#ab_LoadProgOrTrfo__FPCcUiPUi() at 0x10021905c
#ab_load() at 0x100218e2c
#ab_LoadMainProg() at 0x100820d6c
#dystartx() at 0x100ade944
#dy_cdiag() at 0x100833174
#ab_ctransaction__Fv() at 0x100ae1ef0
#ab_retdynp__Fi() at 0x100821c98
#ab_dstep() at 0x100821924
#dynpmcal() at 0x100e932e0
#dynppai0() at 0x100e905ec
#dynprctl() at 0x100e99d48
#dynpen00() at 0x100e8cc18
#Thdynpen00() at 0x1000f9ed4
#TskhLoop() at 0x1000fec7c
#ThStart() at 0x100115890
#DpMain() at 0x1017f4b14
#nlsui_main() at 0x1018e2b6c
We contacted SAP OSS about this problem and they suggested that we check our LS_CODE_INSPECTORTOP include in program SAPLS_CODE_INSPECTOR and revert it to the original version. We did that and still are getting this error. Any suggestions how to fix this issue. All advices are welcome.
Thanks.
Kamran

Nope... this is SAP standard code so I will reply to the OSS and wait for them to come back to you.
Regards
Juan

SAP R/3 4.6B to ECC6 EHP4 Upgrade

Hello,
We are on SAP R/3 4.6B and are in the process/plan of Upgrading to ECC 6...
Is it possible to directly go to EHP4 in a single downtime..?
I am trying to finf the Source/DVD's from the market place but unable to locate one...
Is it possible or should we go to EHP3 only?
If someone has link/path for the software download , kindly help...
Thanks,
RaHuL...

[http://service.sap.com/swdc|http://service.sap.com/swdc]
- download
- Installations and upgrades
- installations and upgrades - Entry by Application Group
- SAP Application Components
- SAP ERP
- SAP ERP Enhance Package
- EHP4 for SAP ERP 6.0 / NW 7.01
Here you should read the info page carefully.
Download the Master Guide and read it to find out about how to perform the upgrade.
- Installation and Upgrade
- <Database Platform>
There is your media. Please note that it is both Installation and upgrade media
and also both ERP and SRM media
In order to get the kernel etc you have to select (instead of "Installation and Upgrade --> Database Platform")
- SAP EHP1 FOR SAP NETWEAVER 7.0
- Installation and Upgrade
- <Operating System>
- <Database Platform>
There is your media together with installation and upgrade for the Netweaver platform (used when upgrading BI etc).
Please note that you also need the Maintenance Optimizer configured in Solution Manager in order to download
(actually you approve them for download) support packages etc from the Service Marketplace.

Unicode/ECC6.0 Upgrade Question

We are going to upgrade to ECC 6.0 soon and are working on making the system unicode compliant. Is it manditory to fix all the ws_download and ws_upload functions to gui_upload and gui_download?
Thanks,
David

>
David Dockham II wrote:
> We are going to upgrade to ECC 6.0 soon and are working on making the system unicode compliant. Is it manditory to fix all the ws_download and ws_upload functions to gui_upload and gui_download?
>
>
>
> Thanks,
>
> David
Dear David,
Yes, because iff its unicode upgrade project, very first step you have to check is attributes of the program, activate the "unicode check active" checkbox. Next you have to goto "UCCHECK" transaction, there it will throws all errors like unicode errors and Obsolete FMs(ws_download,ws_upload,upload,download,popup_to_confirm_step,,etc). After this if you have any doubts on Obsolete function modules, goto Extended program check for that object, in that, it will shows all Obsolete FMs(it will displayed in 3rd row "call function interface warnings".
Let me know if you have any queries.
Regards
Arani Bhaskar

Ecc 4.7 to Ecc6.0 Upgrade

Similar Messages

Maybe you are looking for