hi

[Former Member]

plz send me any gaps in ur proj........with scnearios.........With solution,

100% rewarded if its need ful.........

Thanks in advance,

Durga

[former_member227476]

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.

rewards if it helps

siva

[Former Member]

Hi

GAP analysis simplistically speaking, is the difference between the current position of the system/business and its future state.

It is also referred as the "As Is" and to "To Be" state.

In other words you have to document the current state of the SAP system and how its used by the business and then map this to the new business requirements.

Any business requirements that are found in the new set of requirements can be included in the GAP analysis. Also there may be functional GAPS whereby the business may have requirements which cannot be met by standard functionality and this is also part of the GAP Analysis.

I suggest you try the SAP Help Portal or obtain the ASAP DVD's which has some standard documentation .

Solution Manager in ECC6 also provides Blueprint template which you can use for your GAP Analysis .

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 user exit

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 incoming raw material and and going for production...

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'

Message was edited by:

SHESAGIRI.G