GAPS in Implementation

[Former Member]

Hi , Can any one send some Gaps found in the implementation . taking any one project as example .

Thanks

reddy

[Former Member]

Hi,

This is not the right forum for such questions.

Thread locked.

Thank you.

[Former Member]

Hi Nagaraj

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

Reward if useful to u

[Former Member]

<b>Hi

make small search in sdn there are lot of posts on this</b>

[Lakshmipathi]

Hi Nagaraj

Gap analysis is undertaken as a means of bridging the gap between existing system or legacy system with Client and new is SAP.

This is nothing but wherever SAP has not addressed the clients' specific requirements, with the help of ABABer, we need to develop Transaction based TCodes or Reports based TCodes which should be prefixed with "Z".

For example, if a client is asking the break up of plant wise - material group wise sales report, you need to develop a "Zee" report.

Hope this example will suffice your requirement.

Thanks

G. Lakshmipathi

[former_member227476]

dear reddy

Some gaps

1. Linking Sales Order of Customer & Purchase order issued to Customer.

2. Creating Actual Billing Document (not proforma) before Delivery Document for Delivery related scenario.

3. To reflect stock position on Sales Order screen, while creating Sales orders.

& so on....

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

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

6. In sales order we need customer Phone number, we can use user exit.

reweards if it helps

siva