cancel
Showing results for 
Search instead for 
Did you mean: 

gaps

Former Member
0 Kudos

hi all sd gurus,

can some body tell me how do we fill the gaps,as a sd functional consultant...

is it just filed by using userexits or wht els?

wating for ur quick responces

regards

vivek

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Userexit is one of the possible way to plug the gap. Apart from user exit, it can also be plugged through Abap program, fields exits, bdc, & in few cases by workaround through standard configuration. As SAP is an ocean of knowledge, it is not necessary that we are aware of all functionality. Hence at times we can also bridge the gap by further exploring the system.

To bridge the gaps we must ensure that it is within the scope of the project.

Regards,

Rajesh Banka

Reward suitable points.

Former Member
0 Kudos

hi Rajesh thanks for the reply,but just wud like to know sd consultant tole in brdiging gaps,is it minimul...or do we do in conjunction with ababpers..

regards

vivek

Former Member
0 Kudos

Normally the possibility of bridging the gap by SD consultant alone is certainly possible, but to a very minimal possibility, as the time limitation does not permits exploring to a great extend, when we are in project. however, mojor gaps can only be bridged with conjuction with Abaper.

Some of the example, which can be illustrated which can be bridged by SD consultant are as under, but even an consultant learns with experience.

1. PO number in SO should not repeat:

soultion: Tick the Check Box in Sales Document Type & maintain the appropriate drop down from deop down list.

2. Incase if the client wants to reduce the cycle time, in that case even normal sales order can be configured as rush order & in Delivery Item Category, Picking field can be greyed out & the necessary changes can be done for Delivery quantity, if lesser quantity is to be delivered.

3. In Indian Manufacturing Scenarion, Excise invoice is an requirement, which can be automated in Standard CIN setting.

Ofcourse, The major role of bridging the gaps will be possible with Abap developments.

Regards,

Rajesh Banka

reward suitable points.

Former Member
0 Kudos

Hi Vivek,

If the Thread is Related to GAP Analysis at the time of Implementation Time, Please find the Complete stuff on this with Examples:

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

A through gap analysis will identify the gaps between how the business operates ad its needs against what the package can and can't do. For each gap there will be one of three outcomes which must be recorded and actioned.GAPs must be closed and therefore customized software can be developed to close the gap. In some cases GAP must be closed but software cannot be written therefore a workaround is required in other words a business process change is recommended to the client.

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.

Regarding Userexits:

User exits are the enhancements provided by SAP

you can use them in transactions. Each transaction will have user exits.

If you want to use your own requirements by making your coding while the transaction is run you can use user exits.

For example if you want to run the MRP in MD02 specific to MRP controller you can user exit.

Please also refer the document below.

USEREXIT

Userxits allow us to add our own functionality to SAP standard program

without modifying it. These are implemented in the form of subroutines and hence are also known as FORM EXITs. The userexits are generally collected in includes and attached to the standard program by the SAP.

All Userexits start with the word USEREXIT_...

FORM USEREXIT_..

z..

ENDFORM.

Hope this Clarifies your Doubts and Please Reward If Really Helpful,

Thanks and Regards,

Sateesh.Kandula

Former Member
0 Kudos

thanks satish

regards

vivek