Gap is the gap between the requirements and the std. datasource,std. infocube etc.
This will give you the idea as to how much of customization is involved and hence will help in estimation of efforts.
You will do this by mapping the requirements to the std. datasources. This will give you the idea about the how much percentage of the user requirements is already available and covered by the std. datasources.
According to your requirement go ahead and check the BI content datasource. if you find all the required datasources and if you think you need to do any enhancement to your extract structure then that would be a GAP at extract structure level. Same way once you identity standard BI content cube , transfer rules and update rules... you will check the mappings for your source fields. if any thing is missing in a cube or TR or UR then it would be a gap. Once you identify all your gaps then you can think how to model or what all custimizations you can do at each level.
Gap Analysis is:In the design/blueprinting phase of the BW project,the business content in BW is analyzed and tried to match to the client's requirements.
If the std Business Content cannot satisfy the client's requirement for that particular scenario,it is identified as a 'GAP' and is assigned a 'GAP ID'.
All development/config work required for that particular scenario,is tracked based on that GAP ID.
Also check this:
The gap analisys is the analisys on what are the difeerences between actul system and what the customer want to develop.
GAP Analysis in simpler terms refers to study of existing state of system and desired state of system, there by identifying the gap between states. In the context of SAP, GAP analysis is very important before implementation of SAP system. The implementation team should study what is that an SAP system can provide for each business process and what is the actual business process. One should evaluate each such gap and should find out the ways to fill the gap. The gap might be filled in different ways: System enhancements, custom ABAP code development, interfaces with some other external systems. etc.
In the Enterprise Systems field, GAP Analysis is a process done while bleprinting the solution and aimed to discover the gaps between the user requirements and the "off-the-shelf" (or packaged) solution. For example you want to implement an ERP system , you do a GAP Analysis to assess gaps between the processes supported by that System and the process as executed by the organization that will be implementing the solution.
In the SAP BI area, we do a GAP Analysis to map between our logical and physical BI solution design and the Business Content that SAP offers. Business Content is a set of preconfigured BI objects aimed to save us valuable time when developing BI solutions by providing the "best practices" for that functional domain.
The reason we do a GAP analysis in BI is to find out whether we can save ourselves a lot of time by implementing a Business Content solution instead of developing from scratch.
In simple terms: 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 BlueprintAS 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 customised 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 requirment 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.
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'.
for more info check these links