customer exist

[Former Member]

what is the diff b/w customer exist and user exits?

what are the major complexities to develop the user exits?

please post any imp faq in enhancements?

[Former Member]

Hi ,

User exits are also referred as Customer Exit , as they are provided by SAP to perform customization .

The major complexity in development will be to identify the appropriate exit for any customisation and determine if the desired logic can be implemented there .

Eg if in a VA01 Transaction Code , u want to assign to the Purchase Order Data Field to a particular value based on a logic , then the same can be performed in Program MV45AFZZ , but the appropriate FORM also needs to be indentified .

[Former Member]

customer exits r developed with function modules.

user exits are developed with abap routines.

customer exits do not need access key, but user exits do.

advanced level:

user exit(routines) < customer exits (FMS) < BADIs (abap objects)

normally we call customer exits as user exits:)

i think only in SD, we can use user exits(still available)

[Former Member]

Hi

Customer exits and user exits are same in functionality, but differ in implementation. Customer exits are implemented as function modules, by call statement.

User exits are implemented as subroutines, as form endform.

Secondly Customer exits are further of following sub types..

1) menu exits

2) function exits

3) screen exits

Hope this helps to solve ur problem....

<b>do reward if useful....</b>

regards

dinesh

[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

[Former Member]

hi

just refer to the link below. i hope <b>it will be of gr8 help to u</b>

http://www.sapmaterial.com/?gclid=CN322K28t4sCFQ-WbgodSGbK2g

regards

ravish

<b>plz dont forget to reward points if helpful</b>

[Former Member]

1. Customer Exit and User exits satisfies the basic requirement of adding the customized code to the SAP standard as per the requirement. The main difference is that Customer exits are implemented function modules within z Includes which any body can change, however, userexits are implemented in the form of subroutines in include (other than y and z). So in order to create a userexit or change an existing user exit you need the access for that specific Include as the access key will be unique for an include. Once you get the access key for that include, you can change all the user exits(implemented as subroutines within the include) within that include.

2. The main problem is that when you have a requirement, you need to analyse whether SAP already provides an existing user exit in standard SAP code or your requriement is too complex or customer specific that you need to create a new userexit.

3. Please go through the following link which will help you understand the basic of user exits an customer exits. I hope it will clear all your doubts about exits:

http://sap.niraj.tripod.com/id21.html

Please reward the helpful entries.

Regards,

Raman