SCM 5.1 Implementation Project, Upgrade Project

Hello,
Is any one working on SCM 5.1 Implementation or upgrade Projects..
If you are doing SCM 4.0 to SCM 5.1 upgrade what are the Delta changes you have observed for DP, SNP , PPDS, GATP modules?

i suppose its called SCM2007
you can find the help file for this in help.sap.com
you can also find the release restrictions and release notes for SCM 2007
not sure of active customers
the release date is 31/08/07 as per the PAM
i think it wouldve been beta tested for the last 6 months at least
one might fond some customer specific SCM 2007 notes and that might give an idea of the customers who are using it - nestle/ HP??.... am guessing

Similar Messages

Difference between implementation, support & upgradation projects

Hello Friends,
I am new to SAP. Can anyone tell me what are implementation, support & upgradation projects..what are the differences between those projects? what is role of ABAP developer in these projects?
Regards,

Hi,
SAP Implementation: SAP Implementation is the whole of processes that defines a complete method to
implement SAP software in an organization. It is based on best practices and case studies from various
literature sources and presents a collection of processes and products that make up a complete
implementation method to allow any organization to plan and execute the implementation of SAP (ERP)
software.The SAP implementation process is made up out of four main phases, i.e. the project preparation
where a vision of the future-state of the SAP solution is being created, a sizing and blueprinting phase
where the solution stack is created and training is being performed, a functional development phase and
finally a final preparation phase, when the last tests are being performed before the actual go live.
ABAP Developer Role is to prepare the Technical Specification (based on a Functional Specification given
by a Functional Consultant), build the code, Review the code and finally to prepare the Unit Test Cases.
Sometimes ABAPer may be asked to do a technical research for an optimal solution.
SAP Support: After a go live, the application needs a maintenance/support to resolve the issues/tickets raised by the users when using the application.Ticket is like a request for changes/bug fixing or a request for a new
ABAP Developer Role includes bug fixing/change the existing code due to new requirements/build a new code etc.
SAP Upgrade: SAP Upgrade is nothing but upgrading the software with a superior version which has got more advantages when compared to the earlier version.
ABAP Developer Role is to go through transactions SPAU/SPDD to compare the old and new version of the change and finally need to activate the relevant one.Some times might need to work on SAP notes too.
Hope this helps.
Thanks,
Srinivas

Upgradation projects

From MM point of view what were the areas this upgradation will be helpful......can anyone tell what really upgradation is and how it helps the client...what were the steps followed in the upgradation project...???
Moderator message:
Locked. Reason: topic has been discussed a few times....
Please read answered threads or ask a more sepcific question.
Edited by: Csaba Szommer on Aug 29, 2011 9:50 AM

Hi,
Go through this info.
Difference between implementation, support & upgradation projects and the role of ABAPer in each of them
SAP Implementation:
SAP Implementation is the whole of processes that defines a complete method to
implement SAP software in an organization. It is based on best practices and case studies from various literature sources and presents a collection of processes and products that make up a complete implementation method to allow any organization to plan and execute the implementation of SAP (ERP) software. The SAP implementation process is made up out of four main phases, i.e. the project preparation where a vision of the future-state of the SAP solution is being created, a sizing and blueprinting phase where the solution stack is created and training is being performed, a functional development phase and finally a final preparation phase, when the last tests are being performed before the actual go live.
ABAP Developer Role is to prepare the Technical Specification (based on a Functional Specification given by a Functional Consultant), build the code, Review the code and finally to prepare the Unit Test Cases. Sometimes ABAPer may be asked to do a technical research for an optimal solution.
SAP Support:
After a go live, the application needs a maintenance/support to resolve the issues/tickets raised by the users when using the application. Ticket is like a request for changes/bug fixing or a request for a new ABAP Developer Role includes bug fixing/change the existing code due to new requirements/build a new code etc.
SAP Upgrade:
SAP Upgrade is nothing but upgrading the software with a superior version which has got more advantages when compared to the earlier version.
ABAP Developer Role is to go through transactions SPAU/SPDD to compare the old and new version of the change and finally need to activate the relevant one. Some times might need to work on SAP notes too.
Rewords some points.
Rgds,
P.Naganjana Reddy

NWDI in upgrade project - Recommendations

Dear All,
We are upgrading ECC and Portal. Earlier client doesn't have NWDI.
Now we are using NWDI, so the customer wants the below recommendations.
1. Provide a recommendation for use of NWDI within the Upgrade project.
2. Provide a recommendation for possible ongoing / expanded usage of NWDI at the project.
Please provide your suggestions.
Thanks.

Hi,
1. If you are implementing ESS/MSS you can upgrade the components using NWDI.
In general for deploying components you either use JSPM or SDM to deploy. And NWDI uses the same method to deploy the components.
It's upto you to use NWDI or to deploy them directly.
Recommendation would be if implementing ESS/MSS you can use NWDI. If you are not modifying the standard SAP Delivered component then you can deploy the components directly.
2. It depends on what all things are you planning to implement.
Hope this helps.
Cheers-
Pramod

Role of ABAP Consultant in an Upgrade Project

Hi Friends,
I'm an ABAP consultant, I've worked on Implementation Projects till now. Last one was on ECC 6.0.
I have been assigned to an upgrade project (from 4.6 to ECC 6.0).
So can anybody let me know what is the role and what are the responsibilites of an ABAP consultant in an Upgrade Project?

Hi,
Role of technical consultant:
1) Code fixes and bugs for upgrade objects
2) SPAU / SPDD corrections
3) removal of obselete statements by checking through the code inspector or EPC
4) replacing the BDC on enjoy transactions with BAPI
5) replacing the call transaction on obselet transactions with the corresponding new transactions.
Few of them are listed above..
Reward if useful
Regards
Shiva

Upgrade projects and Compare and ajust func.???

Hi All.
I am trying setting up a demo of the benefits using SolMan for upgrade projects with Compare and Adjust functionality.
I am following a guide with the following steps:
1. Create an Implementation project with some processes from BPR (Using SAP R/3 Enterprise 4.7 as logical component).
2. Model (change) the processes to simulate that a not fully SAP std. process is used at this compagny.
3. Copy the implementation project to an Upgrade Project (with option "Adjust target project to original of the source project".
4. Adding logical component SAP R/3 ECC 6.0 to the system landscape.
5. Executing transaction SA_PROJECT_UPGRADE for the Upgrade project.
Now, when I go to the project, I see no marking of changes anywhere...
Could this be because I am using the wrong processes in my Implementation project from BPR?
Does anyone have a good example of processes that can be good to demo this?
Thanks in advance!
/Per

Hi All.
I am trying setting up a demo of the benefits using SolMan for upgrade projects with Compare and Adjust functionality.
I am following a guide with the following steps:
1. Create an Implementation project with some processes from BPR (Using SAP R/3 Enterprise 4.7 as logical component).
2. Model (change) the processes to simulate that a not fully SAP std. process is used at this compagny.
3. Copy the implementation project to an Upgrade Project (with option "Adjust target project to original of the source project".
4. Adding logical component SAP R/3 ECC 6.0 to the system landscape.
5. Executing transaction SA_PROJECT_UPGRADE for the Upgrade project.
Now, when I go to the project, I see no marking of changes anywhere...
Could this be because I am using the wrong processes in my Implementation project from BPR?
Does anyone have a good example of processes that can be good to demo this?
Thanks in advance!
/Per

Abaper role in Upgradation project

Pls let me know the Role and Responsibilities of ABAPER in Upgradation project.

Murugesh,
are we people here for only replying your qns?
we all have own work at our desk also.it is not nesseccery for us to ans your qns.please dont say like this as you are saying.it is community you have to understand how can servive in community.please dont xpect here from anyone to spoon feeding to you.please support SDN.
Go through this info.
SAP Implementation:
SAP Implementation is the whole of processes that defines a complete method to
implement SAP software in an organization. It is based on best practices and case studies from various literature sources and presents a collection of processes and products that make up a complete implementation method to allow any organization to plan and execute the implementation of SAP (ERP) software. The SAP implementation process is made up out of four main phases, i.e. the project preparation where a vision of the future-state of the SAP solution is being created, a sizing and blueprinting phase where the solution stack is created and training is being performed, a functional development phase and finally a final preparation phase, when the last tests are being performed before the actual go live.
ABAP Developer Role is to prepare the Technical Specification (based on a Functional Specification given by a Functional Consultant), build the code, Review the code and finally to prepare the Unit Test Cases. Sometimes ABAPer may be asked to do a technical research for an optimal solution.
SAP Support:
After a go live, the application needs a maintenance/support to resolve the issues/tickets raised by the users when using the application. Ticket is like a request for changes/bug fixing or a request for a new ABAP Developer Role includes bug fixing/change the existing code due to new requirements/build a new code etc.
SAP Upgrade:
SAP Upgrade is nothing but upgrading the software with a superior version which has got more advantages when compared to the earlier version.
ABAP Developer Role is to go through transactions SPAU/SPDD to compare the old and new version of the change and finally need to activate the relevant one. Some times might need to work on SAP notes too.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b8d163a7-0301-0010-d9b0-98f692ea3c60
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2e8e5288-0b01-0010-2ea8-bcd4df5084a7
Go through this link.I think you don't need any other doc.
http://help.sap.com/saphelp_nw2004s/helpdata/en/index.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/472443f2-0c01-0010-20ab-fbd380d45881
https://websmp102.sap-ag.de/upgrade-bw
please close this thread after giving mark.
Rgds,
Amit

Go/No go criteria for an Upgrade Project.

Can someone please provide information on Go/No go criteria for any Upgrade Projects. What are the key factors which should be considered for any Upgrade project?
Regards,
Gajendra Bhatt

Here are some of the key factors that force TO GO to Upgrade Project:
1. Current version that the customer is having. If it is
   3.X version, then the customer might have implemented
   very long back and his support contract would be
   getting expired. It would be difficult for the customer
   to maintain the system without SAP support. If customer
   go for Upgrade then SAP would extend the support in the
   new contract. This would be a major factor for the
   decision of TO GO to Upgrade.
2. Customer business expansion plans/business prospects
   with different kind of systems like R/3, R/2, web based
   etc., systems which will force to go Upgrade. Because
   new versions of SAP is having different flavors of
   interacting with other systems. So this would save
   more man hours in the future, if they can upgrade
   their central R/3 system.
3. The amount of customization they did in the current
   version, which would be automatically coming in the
   new versions. This would be like credit card process
   in sales etc. This switch over will make them more
   maintenance free system that reduces the future costs.
These are some of the factors that will force the customer
to go for an Upgrade.
Not to go scenarios would be
1. If the customer is already in the nearer version and
   most of the new features are already available, then
   it would not be required.
2. If the project the duration is going to be very long
   as per their processes, which would increases the cost
3. If more customization process has been implemented
   which would not be available in the newer versions
Hope these would be helpful for your analysis.
Regards,
Sivapratap Reddy

MM Upgrade Project

Hi
What are the roles & responsibilities of MM Consultant in a upgrade project ?
What are the major functionality difference between SAP 4.7 c & Ecc 6.0 version ?
Explain me in detail ?
Thanks & Regards ,
Mani.

HI,
Upgrade is of two types :
1. technical : in technical upgrade role of funcitonal consultant is to test all the existing functionalities in ECC development (unit testinf)and QA server(UAT )
Also MM consultatn has to sit with Abaper for some SPAU adn SPDD adjustments.
2. Fucntional Upgrade: respective consultatn has to identify teh new functions and take it up further with Business for approval and sign off and then implement the new funscitons.
http://solutionbrowser.erp.sap.fmpmedia.com is the site where in you can get the new functionalities available in target source.
Award points if helpful as points collection awards through SAP goes to welfare of some of the poorest regions of the world
regards

Upgrade Project.

Hi everyone ,
I wanted to have some advice : we have an upgrade project (for SAP HR)coming up in office , it would be from 4.6 to 6 version i guess.
Presently i am on a support project.
What is the difference between the upgrade project , support project and implementation project.
Is it adviceable to work on upgrade other than support.
Thanks,
Rohit

Am implementation is introducing SAP where some other system has been working till now. Implementation requires deep knowledge of the business processes because you have to understand the existing processes of the customer and try to map them to SAP. It is tough because you have to deliver from end to end, right from understanding client requirement, interpreting it, being involved in change management, educating the client, data loading and so on. Thats the reason E2E implementation carries so much weightage in a CV.
Support starts where implementation ends. You basically have to take care of the problems in an existing system and make some minor changes/improvements in the system. Its not a high pressure job but you never can foresee what you will be facing. Problems can come from anywhere.
Upgrade is technical upgradation. I think it has been covered very well in the thread.
Value-wise, Imlementation is considered to be the best while it is true that the best rerources are invariably found in support. Upgrades are rare, comparitively market for the support projects is the best as implementation is done once, upgrade once in a while but support is for lifetime!
Regards
Lincoln

Benefits of working in BI upgrade project

Hi,
I will be embarking on BI upgrade project soon. and would like to know what are the benefits in terms of career working in such a project as a consultant.
e.g
what can I learn that will be useful in the future.
what knowledge will be gained etc.
and if possible give advice on what to look at for and materials.
thanks

[Hello ,|http://chandranonline.blogspot.com]
BI Upgrade Project will be a challenging one. Upgrade is a process and will never end with this version. Today its BI7.0 then later it can be some new version.
You will have to identify the new functionality and map to the existing one. Some time the entire technical feature may change example, implementing Business Objects.
See these checklist docs for more
[Upgrading BW 3.X to SAP NetWeaver 2004s BI|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2e8e5288-0b01-0010-2ea8-bcd4df5084a7]
[SAP NetWeaver 7.0 Business Intelligence Upgrade Specifics|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/10564d5c-cf00-2a10-7b87-c94e38267742]
[How to Checklist: Rapid SAP NetWeaver 7.0 BI Technical Upgrade with BI Accelerator Implementation (NW7.0)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e0c9c8be-346f-2a10-2081-cd99177c1fb9]
[How to SAP BW 3.5 Upgrade Preparation and Post Upgrade CheckList (NW2004)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/472443f2-0c01-0010-20ab-fbd380d45881]
[Thanks|http://chandranonline.blogspot.com]
[Chandran|http://chandranonline.blogspot.com]

ABAP developer part in an upgrade project

Dear experts,
can anyone explain me the role of an abaper in an upgrade project...
thanks in advance.

Upgrade Project:
The Upgrade Project is to upgrade the SAP implementation version to the latest version of the SAP R/3 released by the SAP.
Generally the Upgrade Projects are initiated because SAP has suggested to the clients that few of the components delivered by it are no longer supported in the old version. Hence for the Support and Performance reasons it will suggest the clients to upgrade its SAP R/3 version to the latest release.
In upgrade projects we will have to revive all the BDC programs and implement the BAPI's that are given. Because the BDC is a Screen Dependent Object and the SAP might have made changes in Screen Fields, or may have removed the screen totally. So to achieve the functionality with BDC we have to deliver new BDC program or implement BAPI'S instead of BDC.
Check below thread
upgradation to ecc 6
Role
abaper
what kind of documentation an abaper has to do give it with an exaple
Upgrade
http://www.thespot4sap.com/upgrade_guide_v2.pdf#search=%22upGRADE%20STEPS%20-%20SAP%22
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5ac31178-0701-0010-469a-b4d7fa2721ca
http://service.sap.com/instguides%20service.sap.com/upgrade
http://service.sap.com/releasenotes
Check transactions SPAU and SPDD. For more information please have a look at the link.
http://help.sap.com/saphelp_nw2004s/helpdata/en/60/d6ba7bceda11d1953a0000e82de14a/content.htm
Reward Points if useful.

Regarding Upgrade project

Hi I want to know about upgrade project from 4.7 to ECC 6.0.
The points to be known is........
1. What are the steps to be followed during upgradation?
2. Any phases are there in an upgradation?
3. In an ABAP program run what are the statements giving the problem (Few examples)?
Help would be appreciated.
Thanks in advance
Ramesh

Hi Ramesh,
When we go for upgradation, first we read upgrade guide thoroughly and implement accordingly then we will do very fast and with out problem. Please ready carefully and implement.
Regards,
Anil

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

Regarding information on Upgrade Project

Hi Experts,
I would like to know more details about Upgrade Project. What are the technical and functional tasks will be there in the process of Upgrade.
Please help me this because i'll be starting my work in Upgrade Project in another 2 days.
Thanks in advance
Tanveer

Hi,
first of all upgrade is nothing but
Upgrade is nothing but installing a new version of software which have more functionality earlier version.
in Upgrade mainly three types
1.Technical Upgrade
2.Functional Upgrade
3.Strategic upgrade
Technical upgrade : is a fast upgrade without additional functionality but with minor user interface changes, to ensure business continuity. This upgrade type includes a cleanup of the system without implementing additional functionality, as well as technology upgrade with the opportunity to eliminate not used modifications and custom developments.
Functional upgrade : Is built on the technical upgrade, the functional upgrade provides in addition the opportunity to implement new functionalities in area like FI,HR,Logistics ..,this upgrade type also represents an opportunity to maximize the use of SAP standard functionalities by replacing custom modifications and consolidate instance or systems.
Strategic upgrade: Is driven by enterprise SOA to provide more flexibility to business process innovation. This type of upgrade approach represents a significant technology improvements step by leveraging SAP Net weaver functionality to standardize, adapt, and enable new business processes and optimized scenarios.
The major stages of a technical upgrade can be:
System preparation and stack level patch upgrade u2013 Basis Team
SPDD Phase u2013 ABAP and Functionals
Up gradation of the system u2013 Basis Team
SPAU Phase u2013 ABAP and Functionals
DBACOCKPIT for indexing u2013 ABAP TEAM
Unicode check
Issues during upgrade
For Further clarification in this regard, Do let me know.
Hope I have answered your query.
Regards,
Abdur Rafique

SCM 5.1 Implementation Project, Upgrade Project

Similar Messages

Maybe you are looking for