Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
Showing results for 
Search instead for 
Did you mean: 


Former Member
0 Kudos

what is enhancements? can give me one example plzzzzzzzzzzzz.with steps.


Former Member
0 Kudos

Why do you need enhancements ?

The standard applications do not offer some of the functionality you need. The R/3 enchancement concept allows you to add your own functionality to SAP's standard business applications.

What are the different types of enhancements ?

Enhancements using customer exits

Customers' potential requirements which are not included in the standard software are incorporated in the standard as empty modification 'shells'. Customers can then fill these with their own coding. Enhancements can relate to programs, menus and screens. Upward compatibility is assured. In other words, SAP guarantees that the jump from the standard software to the exit and the interface which call the exit will remain valid in future releases.

Enhancements to ABAP/4 Dictionary elements

These are ABAP/4 Dictionary enhancements (creation of table appends), text enhancements (customer-specific key words and documentation for data elements) and field exits (creation of additional coding for data elements).

What is customer development ?

Creating customer-specific objects within the customer name range.

What is SSCR ?

SSCR (SAP Software Change Registration) is a procedure, for registering all manual changes to SAP source coding and SAP Dictionary objects.

What is the difference between modifications and enhancements ?

Modifications mean making changes to the SAP standard functionality.

Enhancements mean adding some functionality to SAP standard functionality.

What are the disadvantages of modification ?

Modifying standard code can lead to errors

Modifications mean more work during software upgrades

What are the advantages of enhancements ?

Do not affect standard SAP source code

Do not affect software upgrades

when do you opt for modification ?

Customer exits are not available for all programs and screens within the R/3 standard applications. You can only use exits if they already exist within the SAP R/3 System . Otherwise you have to opt for modifications .

What are the various types of customer exits ?

Menu exits

Screen exits

Function module exits

Keyword exits

What is a menu exit ?

Adding items to the pulldown menus in standard R/3 applications .

13.What is a screen exit ?

Adding fields to the screens within R/3 applications. SAP creates screen exits by placing special subscreen areas within a standard R/3 screen and calling a customer subscreen from within the standard dynpro's flow logic.

What is a function module exit ?

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

What is a keyword exit ?

Add documentation to the data elements of key words defined in the ABAP/4 Dictionary. The system displays this documentation whenever a user presses F1 to get online help for a screen field.

How do SAP organizes its exits ?

SAP organizes its exits in packages that are called SAP enhancements. Each SAP enhancement can contain many individual exits.


Former Member
0 Kudos


Former Member
0 Kudos


Enhancements are nothing but if you want to add extra functionality to standard applications i.e for each and every application there is a standard program (system<status<program(screen) double click on that program name you will get standard code). If we want to add extra functionality to the standard application then we have to change source code. But it will ask for access key. so inorder to change functionality we are going for enhancements.

Already SAP provides pre defined function modules to write our own functionality.

• Go to SMOD

• Give F4 Help

• Click on SAP Applications

• Double click on the Component

• Click on Change button

• Click on Components on the Application Toolbar

Then you will get list of components which was provided by SAP . Read the documentation for each and choose the components which meets your requirements.

Now in CMOD you have to group them ina single project.

• Go to CMOD

• Create one Project and give description for that

• Save it

• Click on Enhancement on the Application Toolbar

• Here we can add number of Components i.e what ever we want to add in a single project

• Click on Components on the Application Toolbar

Then you will get functiona modules to add your own source code.


Suppose if we want to add menu item to ABAP Editor then

• Go to SE38 &#61664;System &#61664; Status

• Repository data &#61664; Transaction &#61664; Double click on it

• Copy package name (SEDT)

• Go to SMOD

• Press F4 then a popup will open

• Click on information system

• Enter package name and press Enter

• Then we will get Exit (SEV00002)

• Put cursor on that exit and press Enter

• Go to change mode and save it.

• Go to CMOD or alternatively we can use the path tools &#61664; ABAP/4 Workbench &#61664; Utilities &#61664; Enhancements &#61664;Project Management

• Specify Project name in the enhancement text box

• Click on Create icon on the application toolbar.

• Enter description for the project and save it

• Click on Enhancement Assignment button on the application toolbar

• Give Exit (SEV00002) and save it

• Go to Components on the application toolbar

• Double Click on MENUS001

• Write function text which we want to add to menu item and save it with an request number

• Double Click on Exit and write code there to display menu item in the screen

• Activate the include program and finally activate the project.

Former Member
0 Kudos


Please refer to the following links:

Reward points if useful,



Former Member
0 Kudos


Please refer to the following links:

Reward points if useful,



Former Member
0 Kudos

As opposed to the term "modification", an addition to an R/3 standard program made via a user exit provided for making such additions. An enhancement does not change R/3 Repository objects. With the ABAP Workbench you can develop any R/3 Repository objects you might need. Enhancements are not affected by upgrading to a new release.

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.

here are several different types of customer exits. Each of these exits acts as hooks where you can attach or "hang" your own add-ons.

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

Creating an Add-On Project

To take advantage of the exits available in standard R/3 applications, you need to create an add-on project. This project lets you organize the enhancement packages and exits you want to use. The add-on project also allows you to hang add-on functionality onto the exit hooks contained with SAP enhancements.

Managing an Add-On Project

An add-on project contains a series of exits, as well as the add-ons that you develop to attach to these exits (like menu entries or function modules). To create an add-on project from within the ABAP Workbench menu, choose Utilities ® Enhancements ® Project management.

Before you begin defining a project, you need to decide which application, application component, or specific standard transaction you would like to add your own functionality to. Give your project a name that indicates the type of functions it contains and that shows which transactions are affected. It may be useful to agree upon a company-wide naming convention for enhancement projects.

There are two factors you need to keep in mind when you create an add-on project. First, you can include an SAP enhancement package and the customer exits it contains in one project only. The same SAP enhancement may not appear in two separate customer projects.

Second, in order to make your add-ons, such as menu items or screen fields, appear in standard R/3 applications, you must activate your add-on project. When you activate a project, all of the add-ons created within this project are activated as well. For this reason, you should ensure that the exits you include in your project contain functions that can be activated simultaneously. It is not possible to activate exits individually.

After you have specified the name of your new project, proceed as follows:

Choose Create.

Describe the nature of the project by providing a short descriptive text.

Choose Save.

The system then prompts you to assign a change request. This assignment allows you to transport the project and its components into a productive system once you have completed it.

Specify which SAP enhancement packages you want to include in your project by choosing SAP enhancements.

Enter the names of these SAP enhancements in the spaces provided.

You should choose enhancement packages that logically belong together. For example, if you are planning to use several enhancements that deal with Materials Management modules, you can include all of these enhancements in the same project. If you are working on enhancements that deal with different applications, or if the enhancements are not logically related, you should include these enhancements in separate projects.

Once you have identified the SAP enhancements you want to include in your project, you can begin adding your own functions to the exits offered in the enhancements. To display the individual components of the SAP enhancements, return to the main screen of the Project Management transaction and choose Enhancement components The system displays all of the exits included in the enhancements assigned to your project.

After you have attached add-on functionality to the exits in your project, you need to activate the project. Activating a project turns on all your add-ons. You also need to activate your project after you have transported it from a development system into a productive system.

When you activate your project, the system turns on all add-ons that the project contains. You cannot activate individual add-ons separately. To activate an add-on project, proceed as follows:

Call the Project management transaction.

Choose Activate project.

The system displays a message confirming that the project was activated.

You can now call up any standard SAP transaction that contains an exit you used in your add-on project. The newly added add-on function(s) should appear.

If you need to make changes to any of your add-ons, you must first deactivate the project that contains that add-on. Deactivating a project turns off all of that project’s add-ons. To deactivate an add-on project, proceed as follows:

Call the Project management transaction.

Choose Deactivate.

The system confirms that the project was deactivated.

Once the project is turned off, you can make changes to the project’s add-ons or build new functions and attach them to other exits in the project.

check for the exit in smod and cretae new project using cmod and assign the exit to you progject and writ ethe code in the include.and activate the project.