‎2008 Jan 14 6:38 PM
hi friends,
i am being put on an upgradation team in 2 or 3 days,
i never did an upgradation project,
the upgradation is from 4.6 to ECC 6.0
did any one of you have ever done an upgradation project, if so,
please tell me what kind of waork am i expected to know or do.
thanks a lott.
‎2008 Jan 14 6:42 PM
As an ABAPer;
Fix unicode problem with custom code. Run tcode UCCHECK which will show you all errors you need to correct,
Correct problems as functional people test. Short dumps etc. There will be lots of OSS notes notes to apply
Run tcode SAMT which flags problems in code besides unicode errors,
Much of the effort is in the unicode fixes. We are 6 months into our upgrade from 4.6b to ECC 6.0
Edited by: J.J on Jan 14, 2008 1:42 PM
‎2008 Jan 14 6:42 PM
As an ABAPer;
Fix unicode problem with custom code. Run tcode UCCHECK which will show you all errors you need to correct,
Correct problems as functional people test. Short dumps etc. There will be lots of OSS notes notes to apply
Run tcode SAMT which flags problems in code besides unicode errors,
Much of the effort is in the unicode fixes. We are 6 months into our upgrade from 4.6b to ECC 6.0
Edited by: J.J on Jan 14, 2008 1:42 PM
‎2008 Jan 14 6:50 PM
Sanjana,
Get to know more about SPAU and SPDD.
SPDD is used to identify dictionary objects
and
SPAU (repository objects), will identify any objects where the hot package is overwriting changes you have made through OSS notes.
You must check all objects identified in SPAU and decide whether you need to reapply the OSS note or reset the code to the original SAP Code.
When you upgrade the dev environment you may generate a transport in SPDD (at the begin of ACT_* phase) and at the end of upgrade for SPAU.
You may then include this transport in the next system upgrade (QAS) system, The Upgrade program will ask you this at prepare.
The procedure is well explained in The SAP on-line help (http://help.sap.com)
http://help.sap.com/saphelp_nw70/helpdata/en/83/7a18ecde6e11d195460000e82de14a/content.htm
http://help.sap.com/saphelp_45b/helpdata/en/60/d6ba7bceda11d1953a0000e82de14a/content.htm
http://www.thespot4sap.com/upgrade_guide_v2.pdf
Vinodh Balakrishnan
‎2008 Jan 14 7:51 PM
thanks JJ and Vinodh,
your replies are very informative,
i have one more basic question,
is it that, as i go there, i will be given a 4.6 system and also a ECC system,
then how do i shift this 4.6 programs to ECC,
and also , is it that i do these tests you mentioned in the 4.6 system or ecc system afetr transporting.
thanks a lot.
‎2008 Jan 14 8:40 PM
You will run all checks on programs in you new ECC 6.0 box after BASIS has completed the upgrade.
First will be SPDD
then SPAU
You create transports based on these from SPDD and SPAU.
Once that is complete, run UCCHECK to get the list of unicode corrections. Again , you will make corrections in ECC 6.0 box.
Then run SAMT and make corrections based on this output.
‎2008 Jan 14 8:10 PM
Sanjana,
Every thing will be done in ECC 6.0
Here are the steps.
1. Developer need to run the Transaction SPDD which provides the details of SAP Standard Dictionary objects that have been modified by the client. Users need to take a decision to keep the changes or revert back to the SAP Standard Structure. More often decision is to keep the change. This is mandatory activity in upgrade and avoids data loses in new system.
2. After completing SPDD transaction, we need to run SPAU Transaction to get the list of Standard SAP programs that have been modified. This activity can be done in phases even after the upgrade. Generally this will be done in same go so that your testing results are consistent and have more confident in upgrade.
3. Run SPUMG Transaction for Unicode Conversion in non-Unicode system. SPUM4 in 4.6c.
4. Then we need to move Z/Y Objects. Need to do Extended programming check, SQL trace, Unit testing, Integration testing, Final testing, Regression Testing, Acceptance Testing etc.,
Hope this Helps
Vinodh Balakrishnan
‎2008 Jan 14 9:00 PM