user exits

[Former Member]

Hi,

Wat are the different types of exits ans how to distinguish them?

wat is customer exit?

Thanks&Regards

rams

[Former Member]

Hi,

Refer this link for exits:

http://help.sap.com/saphelp_erp2005/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm

http://www.sappoint.com/abap/userexit.pdf

If you can mention your mailid I shall send you more documents

Regards,

Gayathri

Message was edited by: Gayathri Hariharan

[Former Member]

hi rams,

the different types of user exits are..

1. Menu Exits

Menu exits add items to the pulldown menus in standard SAP applications

2.Screen Exits

Screen exits add fields to screens in R/3 applications. SAP creates screen exits by placing special subscreen areas on a standard R/3 screen and calling a customer subscreen from the standard screen’s flow logic.

3.Function Module Exits

Function module exits add functions to R/3 applications. Function module exits play a role in both menu and screen exits.

4.Field Exits

Field exits allow you to create your own programming logic for any data element in the Dictionary.

5.For <a href="http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/content.htm">Customer Exits</a>

regards

satesh

[aris_hidalgo]

Hello experts,

Can you also send me documents regarding exits. I would greatly appreciate it. Thanks a lot guys!

[Former Member]

Hi ,

Tell me your e-mail id so that I can send you the docs related to exits.

Regards,

Sylendra.

[Former Member]

Chk these out

http://sap.ittoolbox.com/groups/technical-functional/SAP-R3-DEV/503784

Customizing exits allow you to add your own functionality to SAP’s standard business applications without having to modify the original applications. SAP creates customer exits for specific programs, screens, and menus within standard R/3 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.

If you want to enhance the functionality of your R/3 System, you should take advantage of the exits available in standard R/3 applications. There are two main reasons why you should use exits rather than modifying SAP software yourself. Add-ons attached to exits have the advantage that:

• They do not affect standard SAP source code

When you add new functionality to your SAP System using SAP’s exits, you do not alter the source code of standard SAP programs in any way. The code and screens you create are encapsulated as separate objects. These customer objects are linked to standard applications, but exist separately from SAP’s standard software package.

• They do not affect software updates

When you add new functionality to your R/3 System using SAP’s exits, your objects (called customer objects) must adhere to strict naming conventions. When it comes time to upgrade a to a new software release, customer objects’ names ensure that they will not be affected by any changes or new additions to the standard software package.

Customer exits are not available for all programs and screens found in R/3 standard applications. You can only use customer exits if they already exist in the R/3 System. You find find more information about locating applications with pre-defined exits in Locating Applications that have Exits.

As part of the enhancement concept, it is possible for the customer to

add his own elements to application logic, screens and menus.

The current possibilities for enhancement are:

Text enhancements:

Allow the customer to add supplementary documentation for data fields

non-specific to a transaction, and to change key word texts.

Field exits:

Every screen element with data element reference can branch to PBO or

prior to PAI to a function module if desired. The field contents are

available here for doing special checks and making changes (e.g. user-

specific checks, authority checks, writing entered data and producing

statistics...).

Function exits:

From the main program you branch into a software level, in which you you

can store ABAP/4 coding. The applications programmer at SAP determines

where in the main program the function exit is placed, and which data is

imported/exported via the interface. The accompanying documentation

describes the functionality of the function exit.

Menu enhancements:

Pre-conceived menu items can be activated and named. On the function code

set at menu item selection, there can be a reaction in a relevant

function exit.

Screen enhancements:

The customer can determine the layout of areas in screens provided by the

applications developer. Here, additional information can be displayed or

data entered.

[Former Member]

hai rams,

different types of exits and how to distinguish them?

these are the types of exits.

• Menu Exits

• Screen Exits

• Function module Exits

• field exits.

Menu exits---> allow you to attach your own processes to action menu items. For this, the SAP applications programmer reserves certain menu entries in the GUI interface.The Menu exit entries have function codes that begin with + (Plus sign).

Screen exits----> add fields to screens in R/3 applications. SAP creates screen exits by placing special subscreen areas on a standard R/3 screen and calling a customer subscreen from the standard screen’s flow logic.

Function module exits---> allow you, as customer, to implement additional logic in an application function.

Function module exits add functions to R/3 applications. Function module exits play a role in both menu and screen exits.

Function module exits also control the data flow between standard programs and screen exit fields. SAP application developers create function module exits by writing calls to customer functions into the source code of standard R/3 programs.

field exits----->Field exits allow you to create your own programming logic for any data element in the Dictionary. You can use this logic to carry out checks, conversions, or business-related processing for any screen field.

what is customer exits?

customer exits:

You can hang your own add-on functionality onto these hooks.

As with customer exits two different views are available:

In the definition view----

---

> an application programmer predefines exit points in a source that allow specific industry sectors, partners, and customers to attach additional software to standard SAP source code without having to modify the original object.

In the implementation view -

---

>the users of Business Add-Ins can customize the logic they need or use a standard logic if one is available.

hope this is helpful to u.

regards,

praba.

[Former Member]

Hi Rams,

Definition:

Exits are R/3 enhancement concept which allows you to add your own functionality to SAP standard business applications without having to modify the original applications.

SAP creates user exits for specific programs, screens, and menus within standard R/3 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.

Different types of Exits:

Menu Exits:

Menu exits add items to the pulldown menus in standard SAP applications. You can use these menu items to call up your own screens or to trigger entire add-on applications.

SAP creates menu exits by defining special menu items in the Menu Painter. These special entries have function codes that begin with "+" (a plus sign). You specify the menu item’s text when activating the item in an add-on project.

Screen Exits:

Screen exits add fields to screens in R/3 applications. SAP creates screen exits by placing special subscreen areas on a standard R/3 screen and calling a customer subscreen from the standard screen’s flow logic.

Function Module Exits:

Function module exits add functions to R/3 applications. Function module exits play a role in both menu and screen exits.

When you add a new menu item to a standard pull down menu, you use a function module exit to define the actions that should take place once your menu is activated.

Function module exits also control the data flow between standard programs and screen exit fields. SAP application developers create function module exits by writing calls to customer functions into the source code of standard R/3 programs.

These calls have the following syntax:

CALL CUSTOMER-FUNCTION ‘001’.

Field Exits:

Field exits allow you to create your own programming logic for any data element in the Dictionary. You can use this logic to carry out checks, conversions, or business-related processing for any screen field. Example: The data element BBBNR identifies a company’s international location number. You might want to set up your R/3 System so that all international location numbers are larger than 100.

The field exit concept lets you create a special function module that contains this logic.

You assign the special function module to the data element BBBNR. You then assign the module to any programs and screens in which users can add new international location numbers. When you activate your field exit, the system automatically triggers your special routine whenever a user enters a company location number.

In 4.6c, you can use "RSMODPRF" program to create field exits

Regards

Sylendra.

[Former Member]

Hi,

Check this SAP help Document..

http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm

Regards

Vijay

[Former Member]

Hi,

Gimme ur EmailID.

Regs,

Venkat Ramanan