gap analysis

[Former Member]

Can anyone expalin what is gap analysis ? Which phase of implementation it comes?Pls give some examples

Heeru

[Former Member · Accepted solution]

hi

gap analysis is nothing but. which is SAP not supporting to implement so, we find those gaps and fill with ABAPers help.

this phase will come project final preparation time.

thanks and regards

kranthi

[former_member227476]

dear nath

GAP Analysis

A through gap analysis will identify the gaps between how the business operates ad its needs against what the package can't do. For each gap there will be one of three outcomes which must be recorded and auctioned, GAP must be closed and customized software can be developed close the gap, GAP must be closed but software cannot be written therefore a workaround is required; GAP does not need to be closed.

In simple terms: Gap means small cracks. In SAP world. In information technology, 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 blue print stage.

Cutover Plans:

Detailed plans need to be developed for cutting over from the old system(s) to the new. Parallel runs of what will happen over the conversion period using test data, convert and watch for a period after wards to ensure nothing unexpected happens.

Train Users

Well trained users will support and defend the system on site. Unsupportive users will continually undermine the system and eventually it will be replaced. Therefore the more effort you put into helping the users master the system early the better

rewards pls

siva

[Former Member]

hi,

Gap Analysis:

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 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'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.

<b>Cut-Over Activities </b>:

Cutover Plan - The details of how to move to the production environment and go live. Ensuring that all master data to be loaded to production server is ready & in correct format. User training is conducted & user is in a comfort or atleast manageable position to work on production server. Preparation of user manual. All go-live preparatory activities.

<b>Open Client activity </b>:

The activity or configuration to be done in production server, by opening a client should be ensured that it is done before go-live.

CHAN

[Former Member]

Hi,

Gap analysis can be done in the blue print stage if implementation or rollout.

Gapanalysis is basically the business which cannot be fit in SAP.here we need to prepare gap requirement document and then we need to check alternative solutions which we can map into SAP.

These are basically local and legal requirements.

To follow asap methodology we neeed to first start confi. on the std. scenarios and the we need to analyse and check solutions for gap analysis.

Regards,

Chandra

[Former Member]

getting new business requirements

this comes in final preparation

[Former Member]

Simply Gap Is Nothing But,

Client Requirement Doesn’t Meet With The SAP Application,

The Distance Between Actual And Existing/Supporting,

E.g.: On Purchase Of Material-X, The Other Material Will Get 50% Discount, Which Sap Doesn’t Support,

Commission Paid To The Agent Also , Not Supported In SAP,

To Fill This Gap, We Use The Enhancements,

These Enhancements Divided Into Exits,

Like

User exits,

Field Exits

Screen Exits &

Menu Exits.

These Enhancements Used To Update The Standard Program In Its Respective Business Transactions, Used As A Gateway To Meet The Client Requirements.

Refer below

In n 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 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 auctioned,

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'.

Make a small search n sdn , u can have lot of stuff