topic Re: Difference between User Exit and Routine in Application Development and Automation Discussions

Difference between User Exit and Routine

Former Member — Sat, 20 Oct 2007 11:29:32 GMT

Hi Experts ,

I would like to know the difference between user exit and routine.

For what purpose we use user exit and routine.

What are different types of routines and their use ?

And how to find them.

Any useful material or links related with user exit and routine ?

thanks ,

Re: Difference between User Exit and Routine

Former Member — Sat, 20 Oct 2007 11:41:23 GMT

if you want some modification in standard programs then it might be useless when you upgrade the version of SAP. So for preventing it SAP has provided userexit where you can write your own code to achive your needs for standard transactions and it will not be useless when you upgrade the version as well... eg 4.7 to ECC 6

you can use transaction CMOD or SMOD for user exit...

For getting available userexits for any transaction run below program which will give you a list of userexits.....

just enter T code and get list of user exit...

Then choose the appropriate one for your use according to ur requirement..

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.

Thanks & Regards

ilesh 24x7

Re: Difference between User Exit and Routine

Former Member — Sat, 20 Oct 2007 11:46:48 GMT

Both are used to enhance the standard functionality of SAP application document related functionality

Routines are created using VOFM transaction

VOFM is the transaction where you can maintain routines for Output types, Pricing and Requirements, which are

assigned through cusomization.

To create a routine you need access key & routine no. starts with "9".for ex. 901,902 etc.

one important thing to note that even if you have some syntax errors inside your routine, it will get activated

without errors. So, you need to do Main Program check before activation.

Refer to SAP Note no : 327220,381348,156230.

goto VOFM tcode for wrting the Routines

from menu Requirements-> pricing

You can create the pricing related routines here

Use the Number from 900 only

take the acess key and try to copy the existing routine and change the code to your requirement and keep a break

point and see

Activate it before execution

USER EXITS

User exits (Function module exits) are exits developed by SAP. The exit is implementerd as a call to a function module. The code for the function module is written 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>

To find a Exit.

Goto Transaction -- Find The Package

SMOD ~~>f4~~>Use the Package here to Find the Exits In the Package.

Else if you Want to search by Application Area wise ,

There is one more tab to find the Exits in the Respective Application Area.

Implementing the Exit-- CMOD ~~Create Projects~~Assgn your Component .

Now Run ur Transaction to Check if it Triggers.

Thats it..