SAP Upgrade project

Hi Experts,
I need some inputs to do SAP upgrade from 4.& to ECC 6.0.
Generally the steps involved in the Upgrade project?
What is the role of ABAPer in Upgrade project?
What us the role og Functional consultant in project?
How the configuration kind of stuff take care?
Can anyone send me the best document to understand the process..?
Regards,
Sekhar.J

Hi,
Upgrade Overview
The objective on SAP Technical version upgrade would be to bring in enhanced SAP functionality while retaining the custom development in the original system. The enhanced functionality is not necessarily implemented during the upgrade. The upgraded system is tested for all the functional scenarios existing in the original system and the custom objects are tested for its functioning as in the original system.
Upgrade project consists of 5 phases:
1.     Project Preparation
2.     Blueprinting
3.     Realization
4.     Production Preparation
5.     Go Live & Support
ABAPer Role
a) Syntax Correction
b) Upgrade Correction (Replacement of obsolete statement)
c) BDC Program correction
d) BDC to BAPI conversion
e) Unicode testing using UCCHECK transaction
Functional consultant role
Unit Testing
Test Scripts preparations for Changes
Regards
Praneeth

Similar Messages

Going live check for SAP upgrade projects

Hello,
I am interested in "going live check" service and procedures for my upgrade projects. May I find any documentation? Do I have to pay for it?..
Thanking you in advance and a happy new years!
Kind regards
Nilüfer Çalışkan

Hi Nilufer,
The following Input as follows :
Source : http://www.thespot4sap.com/upgrade_guide_v2.pdf
This service is included as part of your annual maintenance fee.
The underlying concept of the SAP GoingLive Functional Upgrade Check is
to ensure smooth operation of your mySAP.com solution by taking action
proactively, before severe technical problems occur.
The GoingLive Functional Upgrade Check is made up of three sessions
(Planning, Analysis and Verification)two sessions (Planning and Analysis)
before the upgrade and the other (Verification) after the upgrade.
Planning Session: This session should be performed as much in advance as
possible when the upgrade is first being considered.
Analyses compatibility for the target release with regards to connected
systems in the Solution Landscape, OS version, DB version, installed Add-
Ons, Plug-ins, Country Versions, and so on.
Analysis Session: It is generally performed two months before the
production upgrade (consider lead time for hardware procurement).
The focus is on resource planning and system configuration.
There is a high-level hardware plausibility check (this is not a hardware
sizing exercise).
Potential resource bottlenecks are identified.
Necessary changes will be recommended to prepare the system for the
productive use of the new release.
38 SAP Upgrade Guide | Simplifying Your Upgrade
Verification Session: Generally performed four to six weeks after the
production upgrade, and the recommendation from the analysis session
implemented.
Comparison of performance with results prior to upgrade
Recommendations on configuration and optimization
More information and ordering . For more information, see the GoingLive
Functional Upgrade Check web page at:
<b>http://service.sap.com/goinglive-fu</b>
To order a GoingLive Functional Upgrade Check, contact SAP Customer Care
Center at least eight weeks prior to the planned upgrade of your production
system.
For customers of value-added resellers (VARs) such as CBS customers in the
US, special conditions apply. Contact your VAR.
Remote Upgrade Service
Remote Upgrade Service is a technical upgrade that is performed by SAP
remote consultants. Pricing is based on the complexity of the customers
environment.
SAP performs the technical upgrade of your system, allowing you to focus on
the functional and training side of the upgrade. You are still responsible for
resolving object conflicts.
See SAP Notes 106447 and 84044.
The Remote Upgrade Service is an attractive option for CBS sized customers
with small or non-existent mySAP Technology group.
For more information see the Remote Upgrade Service web page at:
http://service.sap.com/remoteupgrade
Resources
The following list shows some of the resources you can use as you prepare for
your upgrade of SAP. These resources include:
Your installation partner
Customers and others you have networked with at customer functions and
conferences such as:
ASUG
Hope this Info helps you.
<i>Advanced New Year wishes.</i>
Br,
Sri
Award points for helpful answers

SAP MM Functional Consultant's role in a Upgrade Project from 4.6C to 6.0

Hi Guys,
I will be thrown into a SAP Upgrade Project. I would appreciate if someone could shed some light on what a SAP MM Functional Consultants role would be in this kind of Project.
I would appreciate a comprehensive guide where it includes role within each stage of the ASAP methodology for Upgrades.
Thanks guys.

> I will be thrown into a SAP Upgrade Project. I would appreciate if someone could shed some light on what a SAP MM Functional Consultants role would be in this kind of Project.
- defining the core processes
- test and customize them
- release the customizing transports for production
> I would appreciate a comprehensive guide where it includes role within each stage of the ASAP methodology for Upgrades.
Since each project is different and each system has a different customizing/configuration it's not possible to generate a step-by-step guide what you have to do. The requirements are usually defined by the business.
Your project leader should be able to give you a project plan (e. g. by using Solution Manager Upgrade Project) where you can get an idea based on the system you're going to upgrade.
Markus

Cutover Activities for Upgrade Project

Experts
What are the cutover support activities for the administration of the ECC 6.0 (SAP) upgrade project. Also please do let me know how to prepare cutover strategy , and how do we develp cutover plans.
Regards,
Mahesh

Hi,
Check this thread.
CutOver activities in BI7.0 while doing production upgrade BI7.0 FromBW3.x
Regards.

Put Together A Data Archiving Strategy And Execute It Before Embarking On Sap Upgrade

A significant amount is invested by organizations in a SAP upgrade project. However few really know that data archiving before embarking on SAP upgrade yields significant benefits not only from a cost standpoint but also due to reduction in complexity during an upgrade. This article not only describes why this is a best practice but also details what benefits accrue to organizations as a result of data archiving before SAP upgrade. Avaali is a specialist in the area of Enterprise Information Management. Our consultants come with significant global experience implementing projects for the worlds largest corporations.
Archiving before Upgrade
It is recommended to undertake archiving before upgrading your SAP system in order to reduce the volume of transaction data that is migrated to the new system. This results in shorter upgrade projects and therefore less upgrade effort and costs. More importantly production downtime and the risks associated with the upgrade will be significantly reduced. Storage cost is another important consideration: database size typically increases by 5% to 10% with each new SAP software release – and by as much as 30% if a Unicode conversion is required. Archiving reduces the overall database size, so typically no additional storage costs are incurred when upgrading.
It is also important to ensure that data in the SAP system is cleaned before your embark on an upgrade. Most organizations tend to accumulate messy and unwanted data such as old material codes, technical data and subsequent posting data. Cleaning your data beforehand smoothens the upgrade process, ensure you only have what you need in the new version and helps reduce project duration. Consider archiving or even purging if needed to achieve this. Make full use of the upgrade and enjoy a new, more powerful and leaner system with enhanced functionality that can take your business to the next level.
Archiving also yields Long-term Cost Savings
By implementing SAP Data Archiving before your upgrade project you will also put in place a long term Archiving Strategy and Policy that will help you generate on-going cost savings for your organization. In addition to moving data from the production SAP database to less costly storage devices, archived data is also compressed by a factor of five relative to the space it would take up in the production database. Compression dramatically reduces space consumption on the archive storage media and based on average customer experience, can reduce hardware requirements by as much as 80% or 90%. In addition, backup time, administration time and associated costs are cut in half. Storing data on less costly long-term storage media reduces total cost of ownership while providing users with full, transparent access to archived information.

Maybe this article can help; it uses XML for structural change flexiblity: http://www.oracle.com/technetwork/oramag/2006/06-jul/o46xml-097640.html

SAP Upgrade and Integration

Hello All
i'm a new employee and i have been chosen to be the integration team leader in the SAP Upgrade project resources.
this project is about
*Upgrading the SAP from ECC 5 to ERP 6
Unicode which is unable the SAP to work with the other characters.
*upgrading the Oracle
I need your help????
i want to know what should i put in my mind and what kind of question should be asked in this sitiuation. because i'm a new employee and being the integration team leader is like a challenge for me.
Please give me your help

Hi,
First you should read Upgrade Master guide. Check guides on http://service.sap.com/erp-ehp.
Thanks
Sunny

SAP Upgrade - Features

Hi,
We are working in a sap upgrade project ECC 5.0 to ECC6.0. We have found a issue in the features ( PE03) after the upgrade of the dev system. The modifications done to the features has now been overwritten by sap.
eg: The dates maintained in the Feature GBCHG - decision tree nodes are not the same before and after upgrade.
1. Are changes to features captured in SPAU/SPDD or what is the way to find out which/what features need to be adjusted again ?
2. Are there any other sap hr objects configurations which needs to be taken care similar to features?
Thanks
Jagruthi

@ Jagruthi:
Hmmm, have you checked the overall structure of the Feature in QA using PE03. A lot of implementations change the way a structure is used to assist their configuration.
When you are in PE03 click on Attributes to look at the author of the changes for the Feature. This is seen on the Administrative Data box (bottom of the page). Notice if Last Changed is a User Name of a company user instead of SAP.
Also when you're in this view, review the actual structure to determine if the same Structure and fields match what you have in DEV.
I really doubt SAP has changed the Feature from ECC 5 to ECC 6. It is much more likely someone has reconfigured the Feautre a long time back.
Cheers, Al

SAP Upgrade Templates

Hi
Can any one send me the templates that are used for an SAP Upgrade project.The kind of templates i need for Change request,Project issue,Upgrade Checks and other......
If you have any other templates regarding Upgrade project, kindly mail to my e-mail id:[email protected]
Thanks in Advance
T.Ram

Hi,
Please follow the below mentioned link. You will get clear understanding about the upgrade here..
https://wiki.sdn.sap.com/wiki/display/HOME/ERP2005+Upgrade
Incase of any specific requirement, please get back.
Regards,
Imran

Pre Upgrade Project details Required

Hi Experts,
Could anyone please explain in detail with sufficient links/materials as to what kind of a role does an Abapper Play in Pre Upgrade Project.
What kind of Problems one can face and solutions to it if possible.
Thanks in Advance.
Regards
Ullas

Hi Ullas,
please check this link
abaper role in Upgradation project
SAP Upgrade project
Regarding the Steps involved in Upgrade Project
First it will be to find objects whcih are impacted by upgrade. Now most of the solution providers have tools to do this work automatically with less human involvement. These tools give you a list of custom developments that will be impacted by upgrade which need correction in higher version. Each object in the list will be distributed to a person in team for fix. It is the responsibity of the Abaper to find out the error and fix the error in a given program and make it error free. This is checked by testing the object after the correction is completed. For exapmle a screen number has changed in higher version for a particular transaction. This implies a correction to all custom programs where this screen is used in BDC. Another example may be an obsolete function module which is not available in higher version and it is the responsibility of Abaper to find out suitable replacement for this.
But prior to this activity there is one more activity. If there are any changes to standard SAP developments like user exits or changes to standard code or changes to data dictionary, then they will not be reflected automatically after upgrade. There are transaction SPAU for workbench objects and SPDD for data dictionary objects. Abaper has to analyse the changed done to standard programs and dictionary objects and has to decide whther these are required in higher version. If they are required then correct them through these transaction codes.
There is a document given by SAP on roles played by different people in an upgrade project. I suggest you to read that.
Best regards,
raam

Upgrade project : from SAP R/3 4.6C to ECC 6.0 by using SAP Data Services

Hi All,
My client is upgrading from SAP R/3 4.6C to ECC 6.0
We are planning to use SAP Data Services(Data Integrator) in the upgrade plan from SAP R/3 4.6C to ECC 6.0 for Data Migration.
we have no idea whether we can use this SAP Data Services(Data Integrator) in SAP upgrade data migration.
The bottom line is we have to make use this Data Services (Data Integrator) product in our upgrade plan for Data Migration.
Please tell us if anybody already used it such kind of scenario in a data migration project with Data Services(Data Integrator).
If we can use Data Service(Data Integrator) what are the pros and cons in using this Data Services(Data Integrator).
Thank You,
Ashok

My opinion is you would want to utilize SAP tools to port the data - our SAP BASIS administrator is out this week but we can provide exact tool names when he returns. ELM (External List Management), IDOC are some of the tools.
You could use DS/DI to export, cleanse, deduplicate the records prior to importing with SAP tools if that is your end goal.
We also offer a data quality tool that extends DS/DI to cleanse/deduplicate name/address records as they are entered into the system. It also comes with batch tools to cleanse/dedup the entire systems name/address information. See Data Quality Management for SAP for further details.

Question about Managing SAP ERP 6.0 Upgrade Projects

Hi experts,
Some questions in this link(google: Managing SAP ERP 6.0 Upgrade Projects and download PDF)
http://www.google.com.tw/url?sa=t&rct=j&q=Managing_SAP_ERP_60_Upgrades_SAP_PRESS_sample&source=web&cd=4&ved=0CDgQFjAD&url=http%3A%2F%2Fmedia.techtarget.com%2FsearchSAP%2Fdownloads%2FManaging_SAP_ERP_60_Upgrades_SAP_PRESS_sample.pdf&ei=vTsVT7PKI4T6mAXL0czcAw&usg=AFQjCNFq83vYG3k14xC5tcoYy96PfllYFw
1. Is figure 5.3 in page 165 correct?
I think it should be
Temporary system: DEV 6.0
Productive system: DEV' 4.6C -> QAS 4.6C -> PRD 4.6C
2. Is this transport route possible?
"During this phase, you continue dual maintenance of the development
systems. You also transfer changes that you make in DEV' to DEV, and
transport changes to both quality assurance systems."
DEV' 4.6C -> DEV 6.0 -> QAS 6.0 -> QAS' 4.6C
If we modified some standard programs and transport between two different SAP versions, I think the programs can't work, right?

> 1. Is figure 5.3 in page 165 correct?
> I think it should be
> Temporary system: DEV 6.0
> Productive system: DEV' 4.6C -> QAS 4.6C -> PRD 4.6C
>
> 2. Is this transport route possible?
> "During this phase, you continue dual maintenance of the development
> systems. You also transfer changes that you make in DEV' to DEV, and
> transport changes to both quality assurance systems."
> DEV' 4.6C -> DEV 6.0 -> QAS 6.0 -> QAS' 4.6C
> If we modified some standard programs and transport between two different SAP versions, I think the programs can't work, right?
Here, you need to do manual replication between both development system. No transport is possible because of different versions. I am not sure about the document that you posted but same is explained very well in upgrade guide. Please check there.
Thanks
Sunny

Upgradation project in sap xi

hi expects ,
     i want to know about what would the problem or process in upgradation project.please help me.
                                                                                thank u

Hi,
As an XI Developer one has the following responsibilities
SLD developement is depends upon the Organization.
1) Developing Interface Objects
2) Developing maping objects
3) Developing Config objects like Creation of Communication channels , Sender and Receiver agreemnets, Interface data and    Receiver data.
In Addition to this he has to check whether the files are correctly picking and the files are correctly placing in the Target.
Any Mapping related error means he has to look into those
what are the responsibilities of an XI Developer?
A) Steps are as follows.
1) Receives functional specs.
2) Understand the business requirements.
3) Check whether are the required information is provided in Functional specs or not information like, source sturucutre,target strucutre,Transformation rule, test files, validation rules, error handling, data size etc.
4) Raise issue log if there are issues and resolve it with functional team.
5) Start building or designing the tech specs with all the required details like IR and ID part.
6) Develop the object as per the design.
7) Follow the naming convention as per the doc.
8) Test the developed object with test cases and prepare UTC.
9) Then review will happen with other team members.
Regards
Mohammed

How To Use SPDD and SPAU Transaction in An Upgrade Project

Hi Friends,
I will be working in an upgrade project very soon. this is my first experience for Upgrade project. Though I know these two transaction are used for Upgrade.
Can anyone give me a step by step document for using these two transactions and other relevant information.
Also, I have one query where do we use these transactions : On the old system e.g. R/3 4.7 or ECC 6.0
Thanks,
Pradeep
<REMOVED BY MODERATOR - REQUEST OR OFFER POINTS ARE FORBIDDEN>
Edited by: Alvaro Tejada Galindo on Dec 23, 2008 10:39 AM

Hi Pradeep,
For SPDD see this link
http://help.sap.com/erp2005_ehp_03/helpdata/EN/2e/6d66587d9011d396b60000e82de14a/frameset.htm
For SPAU
http://help.sap.com/erp2005_ehp_03/helpdata/EN/c8/61ec66e33611d1954b0000e82de14a/frameset.htm
Why you need this Adjustments
http://help.sap.com/erp2005_ehp_03/helpdata/EN/60/d6ba7bceda11d1953a0000e82de14a/frameset.htm
You use the transactions in the new system.
Regards

4.6 C to ECC 6.0 Upgrade Project Timeline Sheet in MPP format

Dear all,
We are now proposing our customer for the 4.6c to ECC 6.0 Upgrade.
Our customer is currently in 4.6c/oracle 9i/HPUX 11 i. He wants to move to ECC 6.0.
If you have the project timeline for the above Technical Upgrade, can you pl send it to me.
If you don't have in MPP format atleast send me the Work Breakdown structure with timelines.
I shall modity the same to our customer and submit
Thanks & Regards
Senthil
[email protected]

Preparation Phase* 6 days
Kick Off Meeting 1 day
Upgrade Project Procedures Preparation 1 day
Prepare Upgrade Project Plan 1 day
Technical Requirements Assessment 3 days
Assess Training needs of Key-users & End-users 1 day
Prepare Detailed Basis Activity List for DEV, QA & PRD 1 day
Business Blueprint Phase 6 days
Develop System Landscape Upgrade Plan 1 day
Functional Requirement Checklist 1 day
ABAP Development check list 1 day
Develop detailed Training Procedures & Documentation for Key Users & End Users 1 day
Identify Testing Scope & Scenarios 1 day
Identify Authorizations Conversion to Roles for SAP ECC 6.0 2 days
Develop Documents as per Basis Activity List 1 day
Develop Authorization Matrix for Activity Groups to Roles Conversion 2 days
Prepare Upgrade Deliverables Checklist 1 day
Realization Phase 28 days
Installation of Solution Manager 3.2 System 1 day
Creation of New Development System for Upgrade Project (Homogenous System Copy - PRD) 2 days
Upgrade to AIX & Oracle 10g, SAP ECC 6.0 on New Development Server 3 days
Upgrade Frontend Software 4 days
Perform SPAU & SPDD Corrections 5 days
Perform ABAP Development & Corrections 10 days Perform Authorizations Conversions and corrections after upgrade 8 days
Perform Upgrade Testing for each Application Module 7 days
Perform Unit & Integration Testing 6 days
Perform Training to Key Users & End Users (Generic & Specific) 3 days
Upgrade to AIX, Oracle 10g, SAP ECC 6.0 on Quality System 1 day
Homogenous System Copy of PRD to New Quality & Upgrade to AIX, Oracle 10g & SAP ECC 6.0 2 days Perform Testing in Quality System 3 days
Testing by end users on Quality System 1 day
Production Realization & Go-Live Phase 6 days
Upgrade to Production System Operating System to AIX (after close of business hours - 23:00) 1 day
Oracle Upgrade to 10g (after close of business hours - 23:00) 1 day
SAP Release Upgrade to ECC 6.0(Downtime Minimized - Downtime occurs in non-business hours) 2 days
User Acceptance Testing 1 day
Production System Go-Live 1 day
Post Go-Live Support 14 days
Post Go-Live Support 14 days Note: This is high level plan subject to change during Business Blue Print Phase 0 days
This is taken from a post in Ittoolbox, May be this is generic. Hope you can tailor this to meet your requirements.

What do you mean by changing a Function Group in upgradation projects

Hi ABAPers,
I am new to upgradation project will any one help me in understanding the concepts like.
1) what do you mean by changing a Function Group in upgradation projects
2) what is the relation b/w the Maintenance view and function group
3) what happens when we regenerate the table maintenance in se11
4) how can i restore the changes that have done to FG after regenerating
5) Suggest me is there any Tcode or procedure to see the code in Remote system (like how we compare the versions of remote system)
Could you please help me ..
Any relevant docs you can send it to [email protected]
Thanks in advance..

Hello Smriti,
          Exploding a BOM means to display all the components and sub-components for a BOM in a particular transaction (eg) VA01,CO01,ME22N etc..
You can use the SAP FM's depend on the Functionality:
CS_BOM_EXPLOSION               General BOM explosion
CS_BOM_EXPLOSION_EQUI          BOM explosion - initial screen: equipment
CS_BOM_EXPLOSION_MAT           BOM explosion (old version); as of 3.0, use CS_BOM_EXPL_MAT_V2
CS_BOM_EXPL_EQU_V2             BOM explosion for equipment
CS_BOM_EXPL_KND_V1             BOM explosion for material
CS_BOM_EXPL_MAT_V2             BOM explosion for material
CS_BOM_EXPL_PSP_V1
CS_BOM_EXPL_TPL_V1             BOM explosion for functional location
CSS7                           Explode BOM (Document)
CS_BOM_EXPL_DOC_V1             BOM explosion: document sub-assemblies
CS_BOM_EXPL_GNRL2_V1           General BOM explosion: document sub-assemblies
CSSO
CS_SO_MODE_BOM_EXPLOSION
As per Garet in response to your question better talk to the Functional team to get the better underatanding for your requirement.
Check the below link for more details on BOM:
http://sap-img.com/sap-sd/what-is-bom-referring-to-sap-sd.htm
Thanks,
Greetson

SAP Upgrade project

Similar Messages

Maybe you are looking for