What is the difference between End to End to Implementation & Roll Out?

End to End implementation

In this all modules of sap which a business wants to run are implemented. All companies who need
to implement sap must undergo end-to-end implementation and also after purchasing the package of
sap they become partners of sap. These projects run for large amount of time usually and a large
team of consultants is required usually.
Roll-out
In this one or two modules which a business wants to implement after the project is go-live and
business is running smoothly in sync with sap so roll-out takes place
Both in rollout and end to end implementation projects developments are done usually. Generally in
case of rollout if a business has say sap implemented at their DUBAI location now the company has
separate plant running in different locations and it wants to implement sap on the prototype of
earlier model so roll out takes place.

Steps in both cases:
Implementation Project:
A company or an enterprise which is going to start using SAP for their Business processes, for this
we start with ASAP methodology steps like
1. Project preparation
2. Business Blue print
3. Realization
4. Final Preparation
5. Go-Live & Support.
For Example:
Let's assume FORD is having their head office in DUBAI and their assembly (manufacturing plant) at
DUBAI and KSA. Initially they are willing to implement SAP in DUBAI location alone. So initial part
done.
Dubai will be an end to end implementation and later almost 90 % of the processes will be used for
KSA also and it will be extended and that part of the project which may be done after say 6 months
or 1 year will be called as Rollout project.


Implementation Learnings:
Say, for a car manufacturing company SAP is to be implemented, so they finish the implementation
by following the above 5 phases.
Once after implementation project is over, they want to extend or going to use SAP for another
company or plant which belong to same controlling area. So at that point we say it as a Rollout
project, which means the new company will be using all the existing functionalities and also some
new business processes also.
Roll-out project:
1. New company codes & plants will be created for this project. Say for Ex: company Code 1500 &
plant 1501 is created.
2. All the settings will be copied from an existing Plant to the newly created Plant. Say For Ex: 1401
plant is already existing and now from 1401 all the settings will be copied to the new plant 1501.
3. So all the relevant module settings say for Ex: PP, MM, SD configuration settings will be copied to
this new plant also.
4. Say for Ex: In PP if there's an order Type TT01 which was for plant 1401, the same can be found
also for plant 1501 after copying.
5. The irrelevant settings say for Ex, if an order type say SS01 which was for Re-work which was
used in Plant 1401 and if it not applicable for plant 1501, then the same has to be edited.
6. New Storage Locations for the plant 1501, MRP controllers are to be created and transported.
7. So like this, individual Module members will be testing the Business processes and then
Integration testing followed by Cut-Over activities..Go-Live.
I hope this will give some idea.