Gap anlysis

[Former Member]

hello Gurus

In real time What is the Gap nalyisis in project would you please help me

[Former Member]

HI REFER BELOW

GAP Analysis

A through gap analysis will identify the gaps between how the business operates ad 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, GAP must be closed and customised 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.

Cut Over 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. Fit gap means, before implementing the SAP all the business data is in the form of documents, we cannot keep this data as is in the SAP. There should be a gap. So by filling this gap, we make configuration with the help of these documents. This is called as fit gap analysis.

GAP Analysis

A through gap analysis will identify the gaps between how the business operates ad 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, GAP must be closed and customised 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

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

2 gaps are,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 userexit

These 2 are gaps which we cant find in Standard SAP

1. if client want new field in customer master like nearest fire station ..

2. order will be uploaded directly with out va01. through BDC... bcoz lot of orders if they get daily, they can opt these...

Movement type 1 uses when a material have two movement types.. like example 101 and 261.. one is incomeing raw material and and going for production...

<b>

REFER FOLLOWING THREADS ON GAP on SDN</b> post

[Former Member]

Hi Mallik,

AS-IS is the study of current process of the client. It is advisable to do this study at micro level & gather as much information as possible. This will be helpful to design the TO-BE methodolgy.

TO-BE is an proposal of what functionality will be availble from SAP & what is not posiible or out of scope. Out of scope would refer to possible in SAP, but not a part of the project. Incase such functionality is to be handled, it is the seniors who will take a call to provide it within the project scope or add it to project scope at extra charge. We define at overview level that what the process will be in SAP & what requires to be managed outside SAP.

Gap Analysis is a document which records the open gap between the AS-IS & TO-BE. There may be certain issues which the client is ready to keep outside SAP, but certain issues which client insist that he requires in SAP. The issues which client insist as required in SAP are recorded in Gap Analysis.

Thanks,

Vinay