topic Re: user exit in Application Development and Automation Discussions

user exit

Former Member — Mon, 15 Oct 2007 11:36:08 GMT

Please give me brief detail of

what is user exit ?

how to find user exit?

a simple example of user exit.

regards

sami

Re: user exit

Former Member — Mon, 15 Oct 2007 11:39:43 GMT

USER EXITS

1. Introduction:

User exits (Function module exits) are exits developed by SAP.

The exit is implementerd as a call to a functionmodule.

The code for the function module is writeen by the developer.

You are not writing the code directly in the function module,

but in the include that is implemented in the function module.

The naming standard of function modules for functionmodule exits is:

EXIT_<program name><3 digit suffix>

The call to a functionmodule exit is implemented as:

CALL CUSTOMER.-FUNCTION ❤️ digit suffix>

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

For information on Exits, check these links

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

http://www.sapgenie.com/abap/code/abap26.htm

http://www.sap-img.com/abap/what-is-user-exits.htm

http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction

http://www.easymarketplace.de/userexit.php

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

http://www.sappoint.com/abap/userexit.pdfUser-Exit

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

To find user exist:

Copy...activate and runthis program

&----

*& Report Z_USER_EXIT *

*& *

&----

*& *

&----

*REPORT Z_USER_EXIT .

REPORT z_find_userexit NO STANDARD PAGE HEADING.

&----

*& Enter the transaction code that you want to search through in order

*& to find which Standard SAP User Exits exists.

&----

*& Tables

&----

TABLES : tstc, "SAP Transaction Codes

tadir, "Directory of Repository Objects

modsapt, "SAP Enhancements - Short Texts

modact, "Modifications

trdir, "System table TRDIR

tfdir, "Function Module

enlfdir, "Additional Attributes for Function Modules

tstct. "Transaction Code Texts

&----

*& Variables

&----

DATA : jtab LIKE tadir OCCURS 0 WITH HEADER LINE.

DATA : field1(30).

DATA : v_devclass LIKE tadir-devclass.

&----

*& Selection Screen Parameters

&----

SELECTION-SCREEN BEGIN OF BLOCK a01 WITH FRAME TITLE text-001.

SELECTION-SCREEN SKIP.

PARAMETERS : p_tcode LIKE tstc-tcode OBLIGATORY.

SELECTION-SCREEN SKIP.

SELECTION-SCREEN END OF BLOCK a01.

&----

*& Start of main program

&----

START-OF-SELECTION.

Validate Transaction Code

SELECT SINGLE * FROM tstc

WHERE tcode EQ p_tcode.

Find Repository Objects for transaction code

IF sy-subrc EQ 0.

SELECT SINGLE * FROM tadir

WHERE pgmid = 'R3TR'

AND object = 'PROG'

AND obj_name = tstc-pgmna.

MOVE : tadir-devclass TO v_devclass.

IF sy-subrc NE 0.

SELECT SINGLE * FROM trdir

WHERE name = tstc-pgmna.

IF trdir-subc EQ 'F'.

SELECT SINGLE * FROM tfdir

WHERE pname = tstc-pgmna.

SELECT SINGLE * FROM enlfdir

WHERE funcname = tfdir-funcname.

SELECT SINGLE * FROM tadir

WHERE pgmid = 'R3TR'

AND object = 'FUGR'

AND obj_name = enlfdir-area.

MOVE : tadir-devclass TO v_devclass.

ENDIF.

Find SAP Modifactions

SELECT * FROM tadir

INTO TABLE jtab

WHERE pgmid = 'R3TR'

AND object = 'SMOD'

AND devclass = v_devclass.

SELECT SINGLE * FROM tstct

WHERE sprsl EQ sy-langu

AND tcode EQ p_tcode.

FORMAT COLOR COL_POSITIVE INTENSIFIED OFF.

WRITE:/(19) 'Transaction Code - ',

20(20) p_tcode,

45(50) tstct-ttext.

SKIP.

IF NOT jtab[] IS INITIAL.

WRITE:/(95) sy-uline.

FORMAT COLOR COL_HEADING INTENSIFIED ON.

WRITE:/1 sy-vline,

2 'Exit Name',

21 sy-vline ,

22 'Description',

95 sy-vline.

WRITE:/(95) sy-uline.

LOOP AT jtab.

SELECT SINGLE * FROM modsapt

WHERE sprsl = sy-langu AND

name = jtab-obj_name.

FORMAT COLOR COL_NORMAL INTENSIFIED OFF.

WRITE:/1 sy-vline,

2 jtab-obj_name HOTSPOT ON,

21 sy-vline ,

22 modsapt-modtext,

95 sy-vline.

ENDLOOP.

WRITE:/(95) sy-uline.

DESCRIBE TABLE jtab.

SKIP.

FORMAT COLOR COL_TOTAL INTENSIFIED ON.

WRITE:/ 'No of Exits:' , sy-tfill.

ELSE.

FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.

WRITE:/(95) 'No User Exit exists'.

ENDIF.

ELSE.

FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.

WRITE:/(95) 'Transaction Code Does Not Exist'.

ENDIF.

Take the user to SMOD for the Exit that was selected.

AT LINE-SELECTION.

GET CURSOR FIELD field1.

CHECK field1(4) EQ 'JTAB'.

SET PARAMETER ID 'MON' FIELD sy-lisel+1(10).

CALL TRANSACTION 'SMOD' AND SKIP FIRST SCREEN.

Please give me reward points..

Re: user exit

Former Member — Mon, 15 Oct 2007 11:59:46 GMT

EXIT s are nothing but the R/3 Enhancements which allows you to add your own functionality to SAP’s standard business applications without having to modify the original applications.

Use

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

Purpose

To introduce the techniques of enhancement in standard SAP system. 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.

Function Module Exits

Use the project management function (transaction CMOD) to edit function modules for function module exits.

Use the pushbutton for editing components to branch directly to the function module editor (display mode).

DO NOT change the function module itself. It is especially important that you do not alter the interface in any way. The function module does , however, contain an INCLUDE statement for an include program that you have to create.

Double-click on the object you want to select. This automatically takes you to the editor of the include program, where you can enter your code.

Reward if usefull

Re: user exit

Former Member — Mon, 15 Oct 2007 12:03:03 GMT

execute this program u will get all the user exits available for this tcode

reward if usefull

************************************************************************

Finding the user-exits of a SAP transaction code

Enter the transaction code in which you are looking for the user-exit
and it will list you the list of user-exits in the transaction code.
Also a drill down is possible which will help you to branch to SMOD.

************************************************************************

*----

TABLES DECLARATION

*----

TABLES : TSTC, "SAP Transaction Codes.

TADIR, "Directory of Repository Objects.

MODSAPT, "SAP Enhancements - Short Texts.

MODACT, "Modifications.

TRDIR, "System table TRDIR.

TFDIR, "Function Module.

ENLFDIR, "Additional Attributes for Function Modules

TSTCT. "Transaction Code Texts

*----

INTERNAL TABLE DECLARATIONS

*----

DATA : ITAB LIKE TADIR OCCURS 0 WITH HEADER LINE.

*----

DATA DECLARATIONS

*----

DATA : V_FIELD1(30).

DATA : V_DEVCLASS LIKE TADIR-DEVCLASS.

*----

INPUT SCREEN DECLARATIONS

*----

PARAMETERS : P_TCODE LIKE TSTC-TCODE OBLIGATORY.

*----

START OF SELECTION EVENT

*----

START-OF-SELECTION.

*--Read SAP Transaction Code from the given input.

SELECT SINGLE *

FROM TSTC

WHERE TCODE EQ P_TCODE.

IF SY-SUBRC EQ 0.

*--Get the Directory of Repository Objects for the

*---selected program name.

SELECT SINGLE *

FROM TADIR

WHERE PGMID = 'R3TR' AND

OBJECT = 'PROG' AND

OBJ_NAME = TSTC-PGMNA.

MOVE : TADIR-DEVCLASS TO V_DEVCLASS.

IF SY-SUBRC NE 0.

*--Read System table TRDIR for the selected program name.

SELECT SINGLE *

FROM TRDIR

WHERE NAME = TSTC-PGMNA.

*--Get the function module name for the selected program name.

IF TRDIR-SUBC EQ 'F'.

SELECT SINGLE *

FROM TFDIR

WHERE PNAME = TSTC-PGMNA.

*--Get the function group for the selected program name.

SELECT SINGLE *

FROM ENLFDIR

WHERE FUNCNAME = TFDIR-FUNCNAME.

*--Read the development class for the corresponding function group.

SELECT SINGLE *

FROM TADIR

WHERE PGMID = 'R3TR' AND

OBJECT = 'FUGR' AND

OBJ_NAME EQ ENLFDIR-AREA.

MOVE : TADIR-DEVCLASS TO V_DEVCLASS.

ENDIF.

*--Read all the entries into the internal table itab.

SELECT *

FROM TADIR

INTO TABLE ITAB

WHERE PGMID = 'R3TR' AND

OBJECT = 'SMOD' AND

DEVCLASS = V_DEVCLASS.

*--Read Transaction code information from the table tstct.

SELECT SINGLE *

FROM TSTCT

WHERE SPRSL EQ SY-LANGU AND

TCODE EQ P_TCODE.

*-- Column Headings

FORMAT COLOR COL_POSITIVE INTENSIFIED OFF.

WRITE:/(19) 'Transaction Code - ',

20(20) P_TCODE,

45(50) TSTCT-TTEXT.

SKIP.

IF NOT ITAB[] IS INITIAL.

WRITE:/(95) SY-ULINE.

FORMAT COLOR COL_HEADING INTENSIFIED ON.

WRITE:/1 SY-VLINE,

2 'Exit Name',

21 SY-VLINE ,

22 'Description',

95 SY-VLINE.

WRITE:/(95) SY-ULINE.

LOOP AT ITAB.

*--Read SAP Enhancements short texts information.

SELECT SINGLE *

FROM MODSAPT

WHERE SPRSL = SY-LANGU AND

NAME = ITAB-OBJ_NAME.

FORMAT COLOR COL_NORMAL INTENSIFIED OFF.

WRITE:/1 SY-VLINE,

2 ITAB-OBJ_NAME HOTSPOT ON,

21 SY-VLINE ,

22 MODSAPT-MODTEXT,

95 SY-VLINE.

ENDLOOP.

WRITE:/(95) SY-ULINE.

DESCRIBE TABLE ITAB.

SKIP.

FORMAT COLOR COL_TOTAL INTENSIFIED ON.

WRITE:/ 'No of Exits:' , SY-TFILL.

ELSE.

FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.

WRITE:/(95) 'No User Exit exists'.

ENDIF.

ELSE.

FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.

WRITE:/(95) 'Transaction Code Does Not Exist'.

ENDIF.

*----

AT LINE-SELECTION EVENT

*----

AT LINE-SELECTION.

GET CURSOR FIELD V_FIELD1.

CHECK V_FIELD1(4) EQ 'ITAB'.

SET PARAMETER ID 'MON' FIELD SY-LISEL+1(10).

*-- call transation SMOD : Sap Enhancement.

CALL TRANSACTION 'SMOD' AND SKIP FIRST SCREEN.

*---End of Program

Re: user exit

Former Member — Mon, 15 Oct 2007 12:06:10 GMT

Exits are basically the hooks whcih SAP has provided to add your own code. There are two types of Exits:

1. Customer exits: Implemented as Function Modules within z includes. Anybody can change it and no access key is required.

2. User Exit: Implemented as subroutines within includes (any include except y or z includes). You need access for the specific include and then you can any subroutine (user exit) within that Include.

BADIs are the enhanced version of user exits where the same logic is implemented via classes and object (OOP)

Enchancement point is the latest once introduces with ECC6.0 . Not very sure about that but you can change it without any access key.

Please go through the following link which will help you understand the exits in a much better way:

http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec07a25db911d295ae0000e82de14a/content.htm

http://www.sap-img.com/abap/what-is-the-difference-between-smod-and-cmod.htm

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

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

http://www.sap-img.com/ab038.htm

User Exits.

http://www.erpgenie.com/sap/abap/code/abap26.htm

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

http://www.sapgenie.com/abap/code/abap26.htm

http://www.sap-img.com/abap/what-is-user-exits.htm

http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction

http://www.easymarketplace.de/userexit.php

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

http://www.sappoint.com/abap/userexit.pdfUser-Exit

customer exits

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f1a7e790-0201-0010-0a8d-f08a4662562d

Menu Exit.

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

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

http://www.sapdevelopment.co.uk/enhance/mod_sapmenu.htm

http://www.sapdevelopment.co.uk/enhance/enhancehome.htm

USER EXIT

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

http://www.sapgenie.com/abap/code/abap26.htm

http://www.sap-img.com/abap/what-is-user-exits.htm

http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction

http://www.easymarketplace.de/userexit.php

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

http://www.sappoint.com/abap/userexit.pdfUser-Exit

http://www.sap-img.com/ab038.htm

http://help.sap.com/saphelp_46c/helpdata/en/64/72369adc56d11195100060b03c6b76/frameset.htm

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

http://www.sap-img.com/abap/what-is-user-exits.htm

http://expertanswercenter.techtarget.com/eac/knowledgebaseAnswer/0,295199,sid63_gci982756,00.html

Rewards if useful.........

Minal

Re: user exit

Former Member — Mon, 15 Oct 2007 12:09:36 GMT

Changes to SAP:

Customizing: Customizing constitutes changing the system parameters with its own special user interface. These changes are organized and preplanned. It is an obligatory part of SAP implementation

Enhancement: It constitutes changing the SAP repository objects by the customer without modification.

Modification: Modifying the SAP repository objects in the form custom changes. This should be avoided because when SAP changes occur in new version these customer versions and new SAP versions have to be reconcile manually. This means increased maintenance workload because of need to adjust all these modifications. This should be avoided.

Custom Development: If the customer requirements are not met by SAP then we should go for customer developments. This means that we need to create customer specific objects within the customer ranges.

Find out Enhancement

There are a number of ways by which we can search for user exits related

to a program / transaction.

Transaction SMOD:

Go to Se 93

Enter the transaction name

Note down the package name

Go to SMODUtilitiesFind (Same screen will appear as given in last slide)

Enter the package name and it will list down all related enhancements.

Transaction SE84:Go to transaction SE84

Select Enhancement  customer exits  Enhancements

Now we can search the exits as explained using SMOD