‎2007 Oct 12 7:06 AM
‎2007 Oct 12 7:08 AM
Hi
See the different project types and their sequences
Go-Live means the Client really starts using the SAP for his daily business transactions
There are different types of Projects in SAP:
1. Implementation
Customer wants to install SAP/Include different modules of SAP viz. MM/SD/FI/CO/PP etc for the first time.Previously he might be using some legacy system in his orgn. This is implementation project. Here one needs to integrate several modules, migrate data from Legacy system to SAP system. Need to prepare interfaces/RFC's to interact with 3rd party systems.
Most of the company's follow ASAP methodology for the Implementation projects
there are 5 stages in the ASAP methodology
they are
1. Project Initial Preparation
2.Business Blueprint
3.Realization
4/ Final Preparation
5.Golive And Support
ABAP work mostly starts in the Blue print ending stage or in the realization stage
2. Support
Customer has already installed SAP & wants to give the work of maintaining those systems. This is support project
There is no phases in it. Just receive the tickets, solve and send back to client.
3. Upgrade
Customer has SAP Version 4.6b and wants to update his version i.e. wants to go to Version 4.7. This is upgrade project
4. Rollouts
Customer has upgraded his version & wants to rollout country specific changes.
This is rollout project
Say a COmpany is having branches in 3 to 4 countries.
In One country they have already implemented SAP
IF they wants to implement the same SAP in other countries of their branches they will simply follow the same SAP implementation policy (Rollout) how they have done for the first country just by changing the country specific settings and configurations.
Check the links,
https://forums.sdn.sap.com/click.jspa?searchID=3895726&messageID=3698776
https://forums.sdn.sap.com/click.jspa?searchID=3895726&messageID=2270483
Regards
Anji
‎2021 Aug 07 12:29 PM
‎2007 Oct 12 7:08 AM
Hi Vijay,
It is nothing but moving on the new system. Lets say you do some upgrade then once the system (production envoirnemt) is fully on the upgraded version then it is called go live
Regards,
Atish
‎2007 Oct 12 7:10 AM
After configuring everthings in Dev, in go live phase you transfer data from Development server to Production server.
Development --> Quality server
In Qulaity you need to Unit, Integration testing, Once it is OK in Qulaity server,
Then you need
Development --> Production
with regards,
Sagar
‎2007 Oct 12 7:11 AM
Hi,
check the below link..
http://www.sapfans.com/sapfans/asap/be_07_e.htm
Reward if helpful.
Regards,
nagaraj
‎2007 Oct 12 7:14 AM
hi
good
Keeping work process documentation current during 'Business Blue Print' and design/build is fundamental. Maintaining it during implementation and 'Go Live' is where most teams fall short. Caught up in the rush to meet deadlines last minute process and systems updates never seem to get formally documented or back-cast into the origninal 'Blue Print'. By not bringing your process and system document forward through 'Go Live' you are condemning your post production support teams to excessive 'Mean Time To Detect' and 'Mean Time To Resolve' troubles. The short term goal of 'Go Live' is achieved but the true price may be far greater than is immediately obvious. Accurate and current process documentation may take time up front but in the world of 'Total IT Return' it's can spell the difference between making and falling short of this KPI
reward point if helpful.
thanks
mrutyun^