ECC upgrade

we are performing the ECC upgrade with unicode conversion from 620 system which has db size 7.24TB
1. do any one performed this on similar huge database?if yes give details
2. since db size is high do we need to go for CUUC or upgrade with unicode in two projects
3. how to calculate the downtime apart from the OSS note provided by SAP which is purely theoritical
4. what are the major challenges during export,import

Hi,
I'm going to do Productive Upgrade from 4.6C to ECC 6.0 next week with a 7.4 TB Oracle Database and I have already done 5 tests using a copy from Production database let me give answers your questions:
1. do any one performed this on similar huge database?if yes give details
Yes, R/3 4.6C to ECC 6.0 on HP/UX 11 and Oracle 10.2.0.2.
You will find upgrade info that says the database size is not that critical and this is true as long as you do some fixes before the actual upgrades (of course after real live test upgrades with a PRD copy). The last Upgrade test we did we achieved 7 hours and 31 minutes of downtime not including post upgrade that will be the longest part of the whole process. In our downtime we had to include a lot of support packages and this system has some specific industry solutions that makes thinks harder. The first test run used 117 hours. SAP assesment service is really recomended in this kind landscapes and they helped us to do some cleanup of unused tables or unused data that let us move in the second test to 20 hours and with some other investigation and trials by our own we achieve the final 7:31 time and espect to get a lower time during Production Upgrade because the PRD server and DB server are more powerfull . Downtime depends a lot in Hardware and here the servers are running on servers with 8 1.6 Itanium CPU's and 32Gb of RAM, EVA system for DISKS.
2. since db size is high do we need to go for CUUC or upgrade with unicode in two projects
I will strongly recomend to do it in two projects unless you have a long time that you could use to achieve all this in one step or in case your post upgrade is really short.
3. how to calculate the downtime apart from the OSS note provided by SAP which is purely theoritical
The only way to calculate downtime is to actually doing a test upgrade on a PRD copy. This is also what SAP people will tell you.
4. what are the major challenges during export,import
I can´t answer this as we did not went to Unicode.
Good Luck during your upgrades,

Similar Messages

PKUNRE field not getting populated in 2LIS_13_VDITM after ECC upgrade

Hi,
We are seeing blank values for PKUNRE / 0BILLTOPARTY during extraction from 2LIS_13_VDITM.
We are experiencing this issue after ECC upgrade which went live recently.
We have applied note 580694 to correct missing fields in the billing extractor.
This field is sourced from VBPA/VBRP.
Our functional teams confirmed that VBPA/VBRP are updated properly and there seems to be no timing issue.
However, the record is landing in PSA with blank BILLTOPARTY.
Where could the problem be?
Is there any thing we missed?
Can any one throw some light if you have experienced this kind of an issue after upgrade.
Thanks a ton in advance,
Sandy.

Hi Sandy:
In my system I didn't find the Field PKUNRE on the VBPA / VBRP Tables, so my guess is that you're dealing with a Custom Enhancement, if this is the case the SAP Note 576886 - "Change to user-defined fields not extracted" might help you in solving this issue.
Regards,
Francisco Milán.
***Follow up note:
I double checked and found the Field PKUNRE on the Extract Structure for 2LIS_13_VDITM (using Transaction Code LBWE) so now I know that you're working with a Standard field and not with a custom ehnancement, the SAP Notes below address a similar issue to yours but they are related to Applications 11 and 12, not for App 13. I apologize for the confusion.
Note 621684 - "Fields PKUNRE and PKUNRG are not filled from delivery"
Note 379237 - "BW Content LE-SHP: missing partners in 2LIS_12_VCITM"
Edited by: Francisco Milan on Jan 28, 2011 12:54 PM

SO_OBJECT_SEND does not work after ECC upgrade

Hi Gurus,
I find a problem after ECC upgrade with SO_OBJECT_SEND.
This was used in a zprog and was wroking fine in 4.6 C.
When this prog is executed it sends mails to the users thru SOST/SCOT.
But in ECC , upon execution I did not see the mails in SOST.
The prog passes the User id ( type B) to the receivers table.The mail
is sent to Business workplace but not to SOST/SCOT.
Pls help gurus.

Hi,
Use type U instead of type B.
Type of RECEIVER entry.
The following values are permitted:
'B' : SAP user name
' ' : SAPoffice name
'C' : Shared distribution list
'F' : Fax number
'U' : Internet address
'R ' : Remote SAP name
'X' : X.400 address
Regards
Indu

ECC Upgrade from ECC 5.0 to ECC 6.0 EHP4 - impact on XI 3.0

Hi,
We are palnning for upgrade our ECC System from ECC 5.0 to ECC 6.0 EHP4. We do not have any plan of upgrade on XI, which is on XI 3.0.
After ECC upgrade please provide the impact on XI 3.0 ?
Will XI 3.0 able to work with ECC 6.0 without any change or any change is required in the XI configuration level, please specify?
Thanks.

>>Will XI 3.0 able to work with ECC 6.0 without any change or any change is required in the XI configuration level, please specify?
As far as I know, no change is required in XI configuration.
Regards,
Praveen Gujjeti.

SAP HR ECC upgrade

Hi,
Could someone tell me what will be the role of SAP HR abap developer in SAP ECC upgrade.
Specially Payroll programming.
and after the upgrade is done what kind of development support is required.
Many thanks
Swetha

Hi Swetha,
ABAPer needs to check all of the user exits and BADIs implemented before in order to check whether any changes need to be done.
Additionally, if there had been any repairs in the system, these need to be reimplemented after upgrade.
For further reference please check the following links:
Re: what are abaper tasks during upgrade to ECC 6.0?
http://www.sapdev.co.uk/upgrade/ug_tasks.htm
Regards,
Dilek

ECC Upgrade impact on BDC's

Hi All,
My question is regarding transaction level changes resulting dfrom ECC upgrade.
We are upgrading ECC 4.7 to ECC6.0. There are certain BDC's already working in 4.7 and I need know the transction level changes so as to see impact on BDC pragrams.
I have already tried using SPAU and SPDD for modifications.
Is this kind of information maintained on help or service-marketplace portals? I checked but could not get the information.
Thanks and Regds,
Gaurav

Hi Gautham,
The table u suggested gives details on trasnaction names.
Also the link you have given is about the various issues related to BDC in upgradation process.
My question is different as to find out the changed at transaction level like ...field changes.... mandatory.....sequesce of fields....
is this kind of incormation maintained in any help or service marketplace folders....
I have already tried SPAU and SPDD but don't want to do that for number of transactions.
Regds,
Gaurav

SAP ECC upgrade from EHP6 to EHP7

Is GTS upgrade from NW 7.2 to GTS 7.3 to be mandated as ECC is getting upgraded from ECC 6.0 EHP6 to EHP 7 . Why?

Hi John,
Your statement looks a bit misaligned.. There is no GTS 7.3 version, the SAP Netweaver 7.3* application server on which SLL_LEG GTS component sits.
The underlying Netweaver AS versions between ECC and GTS systems can be different BUT what needs to be the same is the GTS plugin component in ECC and GTS components in GTS system itself, as best practice they should also be on the same support pack level.
If the ECC upgrade from ehp6 to ehp7 requires you to upgrade SLL_PI gts plugin component in ECC, then in this case you should upgrade SLL_LEG component in GTS system to the same version.
I personaly dont think its required, but check Service markeplace for, PAM Product-availability-matrix and other ehp 7 requirements..
Hope this helps,
Branio

SAP ECC Upgrade : Userexit or Related Enhancement been Overwriten

Hi All,
Is that anyone get explanation from SAP why during ECC upgrade most of the enhancement been overwritten and need to re-do.
Thank in advance on your knowledge sharing.
Trevor Wong.

Ok. There might be need to do "adjustmens" in case of upgrade conflict, or just simple confirmations of code enhancements in transactions SPAU + SPAU_ENH.
I think you should find all missing code enhancements there, waiting for adjustment.

Need details about ECC upgrade

Hi Gurus,
Greetings..
Need help on ECC upgrade
We are currently on 4.0B system and upgrading to ECC 6.0
Need details on the following
1.) Can we directly upgrade from 4.0 to 6.0
2.) What will be the system details ( like database os etc)
Thanks in Advance
Gopi

Hi Gopi,
according to SAP Product Availability Matrix you can upgrade directly from 4.0B system. Please check the link below:
https://service.sap.com/sap/support/pam?hash=pvnr%3D01200615320900001296%26pt%3Dg%257Cr
Please activate the check marks on the left side (pressing below link) to get an overview about supported OS/DB combination:
https://service.sap.com/sap/support/pam?hash=pvnr%3D01200615320900001296%26pt%3Dt%257CPLTFRM%26ainstnr%3D012006153249000…
Cheers,
Andreas

ECC upgrade impact on data archival

Friends,
We are working on the data archival SAP version 4.7, parallely ECC upgrades activities are going on. We are working on the archive tools like transactions SARA, SARI etc as part of archiving. Not sure on what changes to the features will be available in the ECC6.0 version and its impact on already archived files. Can somebody give some inputs/direction?
thanks
Nalinikanth.

Hi,
Retrieval of Archived data
1. SAP system support to retrieve data archived from 4.7 system by ECC system. There is no negative impact in retrieving archived data of deferent version in ECC system.
Advice to take back ups of Field catalog, Archive infostructure in case it is Custom or any additional field added to standard structure.
2. Some changes in Archive index is there in ECC system -
In ECC system, if you want to retrieve archived data from FB03 then activate and fill the Archive infostructure, Archive build index will not work.
This method remains same for Material document and other documents
In ECC system SAP recommends to use Archive system instead of building archive index table such as ARIX_BKPF...
Archive Program
1. All the BC sets to upgrade archiving process are been implemented in ECC system, so you can see some changes in the Write program, Delete program.. or for some archiving object you may also see addition of preprocessing program..
For example: MM_EKKO in initial released 4.7 version didn't had preprocessing job, Write job variant had option of company code to archive purchase order. Later BC set was released with upgraded programs with Preprocessing program and in Write variant with selection of Purchase organization instead of Company code.
If you have already implemented latest release of BC sets then in ECC 6.0 will not have any changes otherwise some minor changes you can see.
Please specify which archiving object with program you are concern with.
Store Function
1. In ECC system, SAP has filled up a long standing gap of storing archived data of different company code in separate content repository. This is very much useful when you want to store the archived data of different organization units in different storage repository. This also easy to get rid of data that has completed total retention period from the storage system.
Remain other functionality remains the same. Please let me know if you have any concern about archiving object that you are using.
-Thanks,
Ajay

ECC upgrade impact on BI

Hi Gurus,
We are currently on BI7 but the R/3 version is 4.7. The R/3 is going to be upgraded to ECC6 shortly. I know this is going to have an impact on BI7 since some of the tables & fields are going to be standard, which might have been customized earlier. Can u give suggestions on the impact on BI and what care needs to be taken from a BI perspective during the ECC upgrade. Also, any doc or pointers which talks about such impact on BI. Points will be awarded accordingly. Thanks for the help in advance.
Ud

Hi,
the following are the activities that I can think of Pre- and Post ECC Upgrade on the BI box.
Pre-Upgrade
- ensure that the Delta queue is cleared in RSA7
- check the PI in ECC6.0
- stop all loads from BW
Post-upgrade
- run Init w/o Data Transfer for deltas
- check extraction for full & delta loads
- replicate all data sources in ECC
- activate all rules thru programs
Other than this, is there any other activity a BW consultant has to do. Also, would it make any difference to our upgrade approach if the BW system is BW3.5 or BI7? our system is on BI7 currently.
Additionally, what SAP Notes will have to be applied pre and Post ECC upgrade.
Would the ECC upgrade have any impact on BI Unicode conversion?
Also, I am still worried about the change to Data Sources post-upgrade to ECC as we have a lot of customization. how do i find out which fields in the Data Sources have been standardized in ECC?
Reponses highly appreciated and points duly awarded.
Uday

ECC Upgrade and XI 3

Hello all,
We're going to start an ECC 6 upgrade project from R/3 4.6C with XI 30 in the system landscape and would like to know if we have first to upgrade the XI system to 70/71.
Since SAP note 1043047 states that PI systems must be at the same version or newer than connected system our concerns are that we could get into troubles without upgrading XI (which is based on 640 while ECC 6 is based on Netweaver 2004s).
Do you have any suggestion ??
Many thanks and best regards,
Michele

Hi,
What I would like to understand is if I have to upgrade first to PI before starting the ECC upgrade project.
Note 1043047 states that "For PI, it is a prerequisite that no other system in the system landscape
has a higher release than the PI system."
This means to me that since ECC 6 is Netweaver 2004s based we have first to reach at least Netweaver 2004s level on the XI side..or am I wrong ?
Thanks and regards,
Michele

BW Extractors During ECC Upgrade

All, We are moving from 46B to ECC. One of the open questions we have is what needs to be done during the upgrade prepare phase with the extractors from our BW system.
We are using the downtime minimized approach, so the prepare phase will start several days prior to the start of upgrade downtime. Here is the question: We have 50+ delta extractors running that pull data from the ECC system to BW. SAP has told us that during the prepare phase (this is during system uptime) we will need to turn off the extractors and clear the delta queues prior to the prepare phase running. But they are also telling us that we COULD turn them back on after prepare is complete but before the downtime starts but that they do not recommend it.
Any experience with BW extractors and an ECC upgrade? Since we are starting the ECC prepare phase several days prior to the start of downtime for the upgrade, we are trying to determine whether we will be without BW feeds for that entire time or only during the downtime.
Thanks!

> Thanks for the reply. So you see no reason to have
> the extrators off the entire time between when
> RSVBCHK is run during prepare and when it is run
> during the downtime?
No - I don't see it. We used that procedure when we went from 4.6 to 4.7 and it worked - we didn't have any data loss.
> We will have approximately 48 hours between the
> prepare and the start of downtime and obviously the
> business would prefer to have the extracts available
> during this time.
RSVBCHK doesn't just check for the BI deltas but for cancelled update tasks too and some more things.
You must though make sure that nobody creates any more deltas (thus no more production) after you passed RSVBCHK during UPGRADE OR make sure, someone is around at a later point before you shutdown the system and load the data out of the R/3 system. You must make sure that all deltas are loaded before you enter MODPROF_TRANS, if you still have delta there, it will be lost.
Markus

Customer exit is not functioning after ECC upgrade/support package

It seems our customer exit is not functioning after ECC upgrade/support package. I tried to activate the project again, no use. please help. Thanks! (see below for the enhancement info)
COZF0002 Change purchase req. for externally procured component
EXIT_SAPLCOZF_002
INCLUDE ZXCOZU02
*& Include           ZXCOZU02
CONSTANTS: lcc_eban(25)   TYPE c VALUE '(SAPLCOBC)EBAN'.
FIELD-SYMBOLS: <fs_eban>   TYPE eban.
DATA: l_fkstl TYPE prps-fkstl.
Move values from the LUW to the Internal Table
ASSIGN (lcc_eban) TO <fs_eban>.
If the field symbol is "NOT' empty then proceed
IF ( <fs_eban> IS ASSIGNED ).
if WBS work order, get cost center from PRPS
IF ( caufvd_imp-auart = 'ZM05' ).
    SELECT SINGLE fkstl INTO l_fkstl FROM prps
      WHERE pspnr = caufvd_imp-pspel.
    IF ( sy-subrc = 0 ).
      WRITE l_fkstl TO <fs_eban>-zzfistl.
    ENDIF.
if not WBS WO, move cost center minus leading zeros to funds center
ELSE.
    WRITE caufvd_imp-kostl TO <fs_eban>-zzfistl.
ENDIF.
ENDIF.

Did you mean set a break point in the follow code?(Include ZXCOZU02), I tried set a break point in this code, but It didn't stop .
*& Include ZXCOZU02
CONSTANTS: lcc_eban(25) TYPE c VALUE '(SAPLCOBC)EBAN'.
FIELD-SYMBOLS: <fs_eban> TYPE eban.
DATA: l_fkstl TYPE prps-fkstl.
Move values from the LUW to the Internal Table
ASSIGN (lcc_eban) TO <fs_eban>.
If the field symbol is "NOT' empty then proceed
IF ( <fs_eban> IS ASSIGNED ).
if WBS work order, get cost center from PRPS
IF ( caufvd_imp-auart = 'ZM05' ).
SELECT SINGLE fkstl INTO l_fkstl FROM prps
WHERE pspnr = caufvd_imp-pspel.
IF ( sy-subrc = 0 ).
WRITE l_fkstl TO <fs_eban>-zzfistl.
ENDIF.
if not WBS WO, move cost center minus leading zeros to funds center
ELSE.
WRITE caufvd_imp-kostl TO <fs_eban>-zzfistl.
ENDIF.
ENDIF.

Error in ecc upgrade phase

Hi,
while upgrading ECC 4.7 to ECC 6.0, I am not able to start shadow instance. Following error is giving .
Aditionally I can able to open the shadow instance from GUI lavel. But unable to login through DDIC password. The ddic password has been locked. Can anyone advice me how to unlock the ddic password in the upgrade phase.
Starting shadow system ...
waiting 20 seconds for system to come up ...
testing if system is available ...
waiting 20 seconds for system to come up ...
testing if system is available ...
waiting 20 seconds for system to come up ...
testing if system is available ...
waiting 20 seconds for system to come up ...
testing if system is available ...
waiting 20 seconds for system to come up ...
testing if system is available ...
waiting 20 seconds for system to come up ...
testing if system is available ...
      SAPup error message
SAPup> ERROR: Starting system failed, rc=0
              To analyse the errors during start of shadow instance,
              view files 'STARTSFI.LOG' and 'DEVTRACE.LOG'
              in directory '/dsttemp/put/log'
              Repeat phase until shadow instance is started
              and you can log on instance number '21'.
            - "continue"
            - "cancel"
Enter one of these options [continue] :=
===============================================
===============================================
ERROR in PHASE STARTSAP_IMP
================================
=================================
SAPup> CHECKS AFTER UPGRADE PHASE STARTSAP_IMP WERE NEGATIVE !!!
       It is recommended that you repeat phase STARTSAP_IMP
       You can exit and restart the phase after the errors
       have been corrected. Alternatively, if you know that
       the error is not of concern, you may ignore it
       and continue with phase REPACHK2
              You are urged to repeat phase STARTSAP_IMP !
            - "repeat"
            - "init"
            - "exit"
            - "ignore"
Enter one of these options [repeat] := init
14:50:31 UPGRADE/EUIM: END OF PHASE   STARTSAP_IMP
14:50:31 UPGRADE/EUIM: START OF PHASE STARTSAP_IMP
Starting system ...
waiting 20 seconds for system to come up ...
testing if system is available ...
waiting 20 seconds for system to come up ...
testing if system is available ...
waiting 20 seconds for system to come up ...
testing if system is available ...
waiting 20 seconds for system to come up ...
testing if system is available ...
waiting 20 seconds for system to come up ...
testing if system is available ...
waiting 20 seconds for system to come up ...
testing if system is available ...
      SAPup error message
SAPup> SYSTEM START failed, code -2
                    -2: the test rfc did not work.
                    Try to log on to the system with user DDIC.
            - "continue"
            - "cancel"
Enter one of these options or "help" [continue] :=
Enter one of these options or "help" [continue] :=
      SAPup message
SAPup> CHECKS AFTER UPGRADE PHASE STARTSAP_IMP WERE NEGATIVE !!!
       It is recommended that you repeat phase STARTSAP_IMP
       You can exit and restart the phase after the errors
       have been corrected. Alternatively, if you know that
       the error is not of concern, you may ignore it
       and continue with phase REPACHK2
              You are urged to repeat phase STARTSAP_IMP !
            - "repeat"
            - "init"
            - "exit"
            - "ignore"
Enter one of these options [repeat] :=
Appreciate for an immediate response ...
Thanks in advance

while upgrading ECC 4.7 to ECC 6.0, I am not able to start shadow instance. Following error is giving .
Aditionally I can able to open the shadow instance from GUI lavel. But unable to login through DDIC password. The ddic password has been locked. Can anyone advice me how to unlock the ddic password in the upgrade phase.
This doesn´t make sense. If you can´t start the shadow instance then you can´t logon to the system
Try the following:
cd <put-directory>/bin
./SAPup stopshd
set the parameter
login/no_automatic_user_sapstar = 0
in the instance profile of the shadown instance
then start the shadow instance
cd <put-directory>/bin
./SAPup startshd
Unlock the shadow instance using
./SAPup unlockshd
Try to logon with user SAP* and unlock DDIC.
Markus

ECC upgrade

Similar Messages

Maybe you are looking for