difference between user exit and enhancements

[Former Member]

hi

Iam bit confused with the blogs i read.

Going to tcode se84 and there by giving package name we get the exits......i think they are customer exits

User exits are different we can search them through program only

Is this rite?

cutomer exits come under enhancements for tat we dont need access key where as for usaerexits we need access key

wat i meant is correct???

[Former Member]

Hi,

Enhancement consists of various components.

Function modules exits (user exits)

Function codes (menu options)

Screen areas (Subscreens)

Includes.

For example, an SAP enhancement may comprise a subscreen and the function exits for data transfer. Customers simply select the components they wish to edit, combine them together in enhancement projects, edit the components and activate the projects.

Check these threads for more details about user exits.

http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm

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

http://www.planetsap.com/userexit_main_page.htm

contains custom program which gives details about SAP enhancement projects specified by SAP for standard transactions.

Regards

[Former Member]

hi,

User exit - A user exit is a three character code that instructs the system to access a program during system processing.

SXX: S is for standard exits that are delivered by SAP. XX represents the 2-digit exit number.

UXX: U is for user exits that are defined by the user. XX represents the 2-digit exit number

Customer exit - The R/3 enhancement concept allows 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.

The program for transaction VA01 Create salesorder is SAPMV45A

If you search for CALL CUSTOMER-FUNCTION i program

SAPMV45A you will find ( Among other user exits):

CALL CUSTOMER-FUNCTION '003'

exporting

xvbak = vbak

xvbuk = vbuk

xkomk = tkomk

importing

lvf_subrc = lvf_subrc

tables

xvbfa = xvbfa

xvbap = xvbap

xvbup = xvbup.

The exit calls function module EXIT_SAPMV45A_003

Development

Creating a Project to include the enhancement

1. Go to transaction CMOD and create a project.

2. Enter a description for the project. Then, click on the pushbutton ‘Enhancement Assignments’ in the Application Toolbar.

3. Enter the name of the enhancement and Save.

4. Go to ‘Components’.

Creating Custom Include for ANLU

The screen shown below will appear, showing all the enhancement components under the assignment AIST0002. Double-click on the name of the Include Structure to create it.

Create the include structure with three new fields, as required. Then, save and activate it.

Develop the subscreen and the program

Go to transaction SE80. For the function group XAIS, create a new subscreen 9000.

Create it as subscreen.

Then, go to the Layout of the screen and create three new fields from Database table ANLU.

Drag the fields in the screen body and place them.

Then, save and activate the screen and come back to screen flow editor.

Create the PAI module to add validation for field “Location 2”, as required .

Activate the whole function group and come out.

Write code in the Function Exits to synchronize the programs

Now, code has to be written in the function modules EXIT_SAPLAIST_002 and EXIT_SAPLAIST_003 so that data flows to and fro between the main SAP program and custom subscreen program. For that, go back to transaction CMOD and change the function exits.

Write code in the function module EXIT_SAPLAIST_002 called once at the beginning of the transaction:

Write code in EXIT_SAPLAIST_003 to pass the data from the subscreen to SAP main program.

Then, activate everything – the whole project and come out.

Complete the configuration to link the subscreen

The development portion is complete. Now, linking of the subscreen has to be done with the subscreen area of the main program. In most of the cases, this linking can be done in the enhancement itself. But, here, requirement is a bit different. It is done by configuration using SPRO.

Assets are created under Asset class. And for each asset class, there is a layout assigned to it. For a layout, there are multiple tab pages assigned to it. And, for each tab page, there are multiple screen groups/field groups assigned.

Here, the requirement is to create these three custom fields in the tab page ‘General’ of asset master screen ( AS01/AS02/AS03/AS91).

Determine the Layout

To achieve this, first of all, we need to find out which layout is assigned to asset class 1000.For that, go to transaction AOLK( information has to be obtained from functional consultant).Select the Asset Class ‘1000’ and click on folder ‘General Assignment of Layout’.

Here, for Asset class 1000, for all the user groups, tab layout SAP is assigned. Since layout ‘SAP’ cannot be changed, it has to be copied and manipulated to include our screen group. Later, the new layout has to be assigned over here.

Create new tab layout

Go to transaction AOLA. Copy the tab layout ‘SAP’ to create another layout, say, YSUB.

System will copy all the settings and will inform you about that.

Select your newly created layout and double-click on the folder ‘Tab page titles’.

You want to put your custom fields in the tab page “General”. So, select this tab page entry and double-click on the folder "Position of Groups".

Here, all the field groups currently residing in the tab-page “General” are shown. Add an entry for your newly created fields.

Select the group box from the list. An entry will come with “U” padded with the custom subscreen prepared by you.

Then, save and come out.

Assign the new Layout to Asset Class

Now, go to tcode AOLK and assign tab layout YSUB for asset class 1000.

Save and come out.

Test the Exit

Everything is over. Now, go to transaction code AS01/02/03 or AS91 to deal with an asset of asset class 1000. You will see your new fields added to the screen. Add values to them…save. Then, enter into the tcodes again to see whether the values entered by you are being displayed or not.

regards

Kiran

[Former Member]

the procedure wat u explained here is for enhancement...

when will i use smod and cmod.......If im not doing enhancement from the scratch then is there any need to create a project with 'cmod'

[Former Member]

Hi Kiran

the procedure wat u explained here is for enhancement...

when will i use smod and cmod.......If im not doing enhancement from the scratch then is there any need to create a project with 'cmod'

[former_member186099]

Hi Krishna,

USER EXIT:

As you have mentioned it requires access key and also you can find this using programs only. It is a modification.

CUSTOMER EXIT:

As you have mentioned it does not requires any access key and you have to create a project to use this. It is an enhancement.

Reward points if it is useful.

Regards,

Prasanna

[Former Member]

Hi,

Customer Exits and User Exits are same. So dont get confused. We dont require any access key for using exits.

Reward If Useful

[former_member200338]

Hi,

The thing u find usinf SE84 ( or SMOD/ CMOD) is function exit / Menu exit.

This is a funciton module which needs to be associated with a project and activate it.

Once the project is activated, the program controls goes to the function module. you can write ur code there ( with in the given include).

Enhancements are SAP given includes where you can modify the code directly by creating enhacment points. it can be implicit/expclit enhancment. you dont require access to do that.

you require access key only when u need to modify a standard program.

Regards,

Niyaz

[P507709]

Hi,

User-exits and Customer-exits

1) User-exits(modifications) Customer-exits(enhancements)

USER EXITS are FORMS and are called by SAP standard programs using PERFORM.

CUSTOMER EXITS are FUNCTIONS so they are called using CALL FUNCTION (or more exactly CALL CUSTOMER FUNCTION).

Inside the form (user exit) you can read and change almost any global data from host program. Inside a function (customer exit) you can only acces your import/export/changing/tables parameters.

2) User exits are more flexible because you have more information to use in your code but on the other hand , it is very easy to manipulate erroneously global data and lead the standard program to a dump or even to make database inconsistent .

Customer exits are more restrictive but you are sure any change you can make to any parameters will never lead to inconsistency

3) User-exit doesn’t have any classification. In customer-exit we have function-module exit , screen exit , menu exit

Basically designed For SD module Are available for MM,SD,FI,HR…..Basically designed for all modules.

User-exits can be written only using access-key No need of access key

With user-exits the code , the developer has written will not be there for next version unless modification assistance tool is used

Customer-exits are not wiped during upgradation.

Reward if its usefull

Regards,

Durgaprasad