Gap means small cracks.

In SAP world or in Information Technology world, gap analysis is the study

of the differences between two different information systems or applications( ex; existing system or
legacy system with Client and new is SAP), often for the purpose of determining how to get from one
state to a new state. A gap is sometimes spoken of as "the space between where we are and where
we want to be."
Gap Analysis is undertaken as a means of bridging that space. Actual Gap Analysis is time
consuming and it plays vital role in Business Blueprint [AS IS Process] stage.
A through Gap Analysis will identify the gaps between how the business operates and its needs
against what the package can can't do. For each gap there will be one of three outcomes which must
be recorded and actioned,
1. GAP must be closed and customized software can be developed
2. GAP must be closed but software cannot be written therefore a workaround is required
3. GAP does not need to be closed.
A point worth mentioning here is that at time people confuse between user-exits and Gap Analysis.
User exits are standard gate ways provided by SAP to exit the standard code and we can write our
own code with the help of ABAP workbench, its not new functionality which we are trying to build in
sap but its slight enhancement within the same code.
Gap analysis is start point of Realization and once business Blueprint is finished we have to find the
realization of sap system for client requirement and there will be certain gaps when compared to
system fit. Those gaps can be closed either by re-engineering of business process to fit with SAP or
we have to use USER exits in case of small deviations or complete enhancements with the help of
ABAP to fit with the SAP system.
The Gaps can differ from company to company. Most commonly, however, missing functionality is
industry-specific.
Examples:
1. MGM Studios and Lycos sometime back worked with SAP to develop its new intellectual property
management and media advertising management functionality, respectively.
2. A leading Oral care product company wanted the promotion of free-goods where they wanted 'Buy
one get 2 different products free'

In customer master data the client requirement needs legacy

customer number which can be solved with User exit.
In sales order we need customer Phone number, we can use
user exit
If client want new field in customer master like nearest
fire station.

GAP analysis is done in Blue Print stage. It aims to

understand what can be done with the standard SAP and how
the client actually wants a particular scenario to be
processed.
It’s an understanding of the GAP between the actual &
required scenarios.
Tthe difference between agreed work and completed work is
GAP Analysis.

E.g.: To Fill This Gap, We Use The Enhancements,These

Enhancements Divided Into Exits, Like User exits, Field
Exits Screen Exits & Menu Exits.These Enhancements are used
to update the standard program in its Respective Business
Transactions, Used as a Gateway to Meet the Client
Requirements.

Implementation of Project

It actually depends on various factors, such as :

1. how many modules they want to implement.
2. Team Size.
3. Organizational Structure (Volume of data)
4. Legacy System
5. Business Complexity etc.
There is no hard and fast rule that every project should be completed in a particular duration of time.
Depending on the above factors, it may vary any where from 6 months to 18 months or so.
(Approximately, it may be less than 6 months or more than 18 months in some exceptional cases).
Usually it is divided into phases:
1. Project Preparation : Project team, infrastructure, Software, Steering committe etc will be
identified in this phase.
2. Business Blue Print : Re-engineering of Business process and BBP sign off.
3. Realization : Analysing Gap and Realization of possible customization and development effort
4. Final Preparation and Go Live : Development and Configuration
5. Post Go Live support : Support after go live
You would allot specific time periods for each of these phases and will set milestones accordingly.
or it could even be like :
Project Start
Analysis
Design
Design Freeze / Client Sign-off
Construction
Testing
Implementation
Project End
Project Management Framework
Post Close Review
Training
Change Management
Refer following links for more info:
http://en.wikipedia.org/wiki/SAP_Implementation
http://www.sapfans.com/sapfans/asap/be_01_e.htm
There are different flavors of project implementations.
1. Template implementation - without much customization - based on a predefined rollout template
2. CUstom rollout
3. Ramp up rollout
4. Enhancements to an existing implementation
5. project recovery
The project life cycle consists of [1] Project Charter,[2]Scope,[3] planning,[4]Execution,[5]Control and
[6] closure.
Charter tells you the purpose of the project,for example,to eliminate an expensive Transmission
process by implementing EDI.
Scope tells what all you will be doing in the project.In SAP,this is Blue printing.
planning:Here you plan the capital Expenditure - capital budgeting,Expenses,Revenue,Resources
and other elements that go in to the project.
projectExecution : Actual execution of the planned activities
Control:Here you steer the project towards the intended goals-variance analysis,cost
Reduction,Value engineering,budget,standards,fast tracking,crashing,Resource allocation etc etc
,....all find a role here.Here Time,Cost and the other resources are controlled so as to complete the
project in time and within the cost baselines.
Testing also comes here-unit test,integration test,UAT........
Closure:The project sign off takes place here.
In the support Environment the "project" will cover a]incident management,b] problem
management,c]change management,d]configuration management e] Release management and f]
help desk.

Team size

The SAP team depends on the relavent company in which you are working with.
In Generic terms for a Implementing Partner eg:- IBM ,PWC TCS etc.
The team consists of a project Manager and a Bussiness developer .
In the team there can be 1-2 Consultants for each module (SD ,MM,PP,PM etc)
With 1 or 2 ABAP er and BASIS person..
While in the Client Payrolls there can be 1-1 Consultant for each module
depending on requirements .
So generally there are 3 teams.
1. The Core Bussiness Members of the Client
2. The Company Payroll Consulant for Implemention pre and post & support
3. The Implementing Partners(Project team)