User Exit, Field Exit

Hi Folks.
I have a question about user exit, or field exit. The question is that if is possible to fill a field with a value, depending on a value entered by the user within the same transaction.
Thanks for your help.
Regards,
Gilberto Li

The field Exit have only INPUT and OUTPUT, but u can validate using another values.
U can:
1- Use the values in that Screen ( Using function GET_DYNP_VALUE)
example:
DATA: l_vkorg TYPE STRING.
CALL FUNCTION 'GET_DYNP_VALUE'
EXPORTING
 I_FIELD = 'RMMG1-VKORG'
 I_REPID = 'SAPLMGD1'
 I_DYNNR = '1004'
CHANGING
 O_VALUE = l_vkorg.
2- Use Parametes ID:
example:
DATAL l_matnr TYPE MARA-Matnr.
GET PARAMETER ID 'MAT' FIELD l_matnr
3- Get Data from tables using SELECT with any of the values that u can get in options 1 or 2.
Example:
DATA:
 l_matnr TYPE MARA-matnr,
 l_mtart TYPE MARA-mtart.
IF INPUT is INITIAL.
GET PARAMETER ID 'MAT' FIELD l_matnr.
SELECT SINGLE MTART
 INTO l_mtart
 FROM MARA
 WHERE MATNR = l_matnr.
Now I have the value l_mtart to validate.
IF l_mtart = 'Z001'
ENDIF.
Greetings

Similar Messages

User Exit/Field Exit for Field Selection in MM01 & MM02

Dear All,
Please Tell if I want to make Field Purchasing group Mandatory in MM01 & MM02 in Purchasing view only.I dont want the data to be updated in MRP1 view. Please tell me is there any exit for the same.
Regards,
Sandeep

You can customize
via
SPRO>Logistics - General>Material Master>Field Selection>
first from
Assign Fields to Field Selection Groups
you must assign MARC-EKGRP (Purchasing Group)
to a selection Group which will be mandatory.
Then from Maintain Field Selection for Data Screens
you must choose the Material Types which you want to make
Purchasing Group mandatory.
You must check Reqd Entry for the material types you want
Best Regards
Hope will help

Need a document for field exit....urgent

Can any one please send a document for field exit or have a simple document on how to work on a field exit with screen shots. pls send it ...its urgent
Thanks and regards
Nandha kumar R

Hi,
A field exit is a type of user exit.
A user exit is a hook where you can inject your own add-on functionality or behavior to SAPs standard business applications without having to modify the original applications.
Field exits allow you to create your own programming logic for any data element in the Dictionary. You can use this logic to carry out checks, conversions, or business-related processing for any screen field.
Field Exits
Field exits allow you to create your own programming logic for any data element in the Dictionary. You can use this logic to carry out checks, conversions, or business-related processing for any screen field. Example: The data element BBBNR identifies a companys international location number. You might want to set up your R/3 System so that all international location numbers are larger than 100.
The field exit concept lets you create a special function module that contains this logic.
You assign the special function module to the data element BBBNR. You then assign the module to any programs and screens in which users can add new international location numbers. When you activate your field exit, the system automatically triggers your special routine whenever a user enters a company location number.
In 4.6c, you can use "RSMODPRF" program to create field exits.
An example of a user exits :-
MODULE user_exit_0001 INPUT
    CASE okcode.
        WHEN 'BACK OR EXIT'.
            CASE sy-dynnr.
                    WHEN '100'.
                         SET SCREEN 0.
                         LEAVE SCREEN.
                    WHEN '200'.
Note that you can write any code that satisfy your needs.                                                     ****
But in this case, this was wrote as a sample code for reference sake.                                    ****
And you can test it.                                                                                ****
                         SET SCREEN 100.
                         LEAVE SCREEN.
             ENDCASE.
      ENDCASE.
Field exits (SMOD/CMOD) Questions and Answers
1. Field exit was created with CMOD, but is not processed when calling the screen.
- Since the field exit is not processed until PAI, an action must be triggered on the screen (Return, Save, ...).
- Set profile parameter abap/fieldexit to YES and restart the system.
- After activating the function module FIELD_EXIT... and the field exit, leave the transaction on whose screen the field exit is to be executed. The screen is not generated until the transaction is started.
- Do not work on different application servers since there may be some delay before the field exit is activated.
- The profile parameter must be set on all or none of the application servers.
- If the field exit is to only be active on specific screens, check whether you chose the correct program and the correct screen
      number (take care with subscreens).
- Using SE51 -> Field list, check that the screen field does have a reference to a data element. In the name of the field exit use the name of the data element and not the field name.
- After transport, field exits are marked as active but will not be processed.
   Tip: First try deactivating the field exit once more and then afterwards, activate it again.
2. How is performance affected by setting abap/fieldexit?
- If a screen is generated and the profile parameter is set, a check is run on 2 tables (TDDIR, TDDIRS) to see whether a field exit must be generated for the respective field. In practice, the screen load is not generated until the screen is selected after an
update. The user should not notice any difference because screen generation is very fast.
3. Can you read the contents of other screen fields in the field exit?
- In principle, every field exit can store its value in the global variables of the function group (TOP) and hence make them
available to other field exits. Note here that field exits are always called and not only if an entry is made in the field or if the field is empty. In addition, it is not possible to make any assumptions about the order in which the field exits will be called in the future.
4. How does the field exit behave on step loop fields ?
- After the user has entered data, the field exit is called in PAI as often as there are visible fields in the step loop. The system
variable SY-STEPL is incremented each time. If a new value is assigned to the field, it is displayed in the module between LOOP and ENDLOOP. This module is also called once for each visible step loop line.
5. Can field exits be debugged ?
- No. Field exits must be tested separately in the ABAP/4 Development Workbench. For errors which only occur in the screen environment, it is helpful to write interesting variable to the file system using TRANSFER... . These can then be analysed there.
6. What can you do if the field contents are no longer transported to to ABAP/4.
- Check whether a value is assigned to the field OUTPUT.
7. When is the field exit called if a conversion exit is attached to the
   data element ?
- The field exit is called after the conversion exit. This means that the INPUT field receives the data in the same format as the
ABAP/4 program also receives it.
8. Although a global field exit is inactive, a function module is called which does not exist (for example FIELD_EXIT_PROGRAMM_@)
- This is an error in the kernel which no longer occurs as of 3.0C. As a temporary measure, it is useful to assign a program and a screen which do not exist to the field exit and then activate the field exit.
9. Field exit is not visible in CMOD, although created.
- If you want to create a field exit for a data element, a function module is proposed with the name FIELD_EXIT_. This
function module must exist for the field exit to work. If you do not create this function module, but do create one with a suffix,
the data element is not displayed in CMOD.
10. Field exit is not executed although it is active.
- Fields which do not have the 'Input field' attribute usually do not trigger a field exit. The field exit is designed to allow an
extended input check. It is therefore only called for input fields - even if they are not ready for input at runtime of the         application by LOOP AT SCREEN.
This rule does not apply, however, if the field is located within a steploop. Here the field will be always activated, even if it is
invisible.
- Field exits can only be executed for fields that are directly related tothe dictionary. If the relation is indirect, i.e. via an       ABAP declaration ( LIKE ), no field exit can be executed.
11. Field exits on check buttons do not work
- Field exits are only intended for input fields. As check buttons count as graphical elements, you cannot install field exits on
them.
12. Field exits do not work on selection screens
SAP Field Exits
From 4.6c onwards, Field exits will no more be supported by SAP. They removed the function of field exit but they had given lot of flexibility through userexit.
However, if you still required it, here is how to activate it :-
First called up transaction CMOD.
Then called up transaction PRFB.
or
Activation of the field exits and assignment of the dynpros can also be carried out using program RSMODPRF. For this purpose, the program must be started without parameters (input fields remain blank). If required, new field exits can be created using program RSMODPRF (see the program documentation).
REFER THIS LINK ALSO.
defining screen fields using FIELD-SYMBOL
Thanks,
Shankar

Documentation about Screen, Menu and Field Exits

Hi all!!
I need some documentation about Screen, Menu and Field Exits.
I´m very interested specially on steps by steps.
My mail is [email protected]
Helpful posts will be rewarded.
Thanks in advance and regards,
Manuel.

Types of Exits 
There are several different types of user 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 items 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 screens 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 pull down 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. SAP application developers create function module exits by writing calls to customer functions into the source code of standard R/3 programs.
These calls have the following syntax:
CALL CUSTOMER-FUNCTION 001.
Field Exits
Field exits allow you to create your own programming logic for any data element in the Dictionary. You can use this logic to carry out checks, conversions, or business-related processing for any screen field. Example: The data element BBBNR identifies a companys international location number. You might want to set up your R/3 System so that all international location numbers are larger than 100.
The field exit concept lets you create a special function module that contains this logic.
You assign the special function module to the data element BBBNR. You then assign the module to any programs and screens in which users can add new international location numbers. When you activate your field exit, the system automatically triggers your special routine whenever a user enters a company location number.
In 4.6c, you can use "RSMODPRF" program to create field exits.
An example of a user exits :-
MODULE user_exit_0001 INPUT
 CASE okcode.
 WHEN 'BACK OR EXIT'.
 CASE sy-dynnr.
 WHEN '100'.
 SET SCREEN 0.
 LEAVE SCREEN.
 WHEN '200'.
**** Note that you can write any code that satisfy your needs. ****
**** But in this case, this was wrote as a sample code for reference sake. ****
**** And you can test it. ****
 SET SCREEN 100.
 LEAVE SCREEN.
 ENDCASE.
 ENDCASE.
reward points if it is usefull..
Girish

Field Exits for XD01.

HI Experts,
I want to implement the Field Exit for Changing the Field discription for Standard sap field for XD01 and MK01.
could any one tell me what are the ( Exits )Field Exits for above T Codes.
Thanks in Advance.
sudeer.

hi,
cherck this link.
http://www.****************/Tutorials/ABAP/XD01/XD01.htm
these r exits available in xd01.
Transaction Code - XD01                     Create Customer (Centrally)
Enhancement/ Business Add-in            Description
Enhancement
SAPMF02D                                User exits: Customer master data
Business Add-in
CUSTOMER_ADDRSCR_CHG                    Change Address Screen in the Master Data Maintenance
CUSTOMER_ADD_DATA                       Additional Data at Customers
CUSTOMER_ADD_DATA_BI                    Additional Data at Customers (Batch Input and ALE)
CUSTOMER_ADD_DATA_CS                    Additional Data at Customers (Subscreen Container 4000)

Regarding field exit

hi guru
my requirement is that i want to change a predefined field lenth 9 character. to 12 character. how can i do it.
please help me.

hI
ABAP DICTIONARY
Field Exits:
 Field exits take you from a screen field with a data element reference to a function module. Field exits can be either global or local.
Field exit function modules adhere to the following naming convention:
prefix: FIELD_EXIT_
name: <data element name>_
suffix (optional): 0 to 9, A to Z
Global field exits are not limited to a particular screen. If a global field exit's data element is used on multiple screens, you will branch to a function module from all of these screens once the exit has been activated. Here you can, for example, edit the contents, force a new entry to be made by outputting an error message, or prohibit certain users from proceeding further.
Local field exits are valid for one screen only. If you assign a screen from a specific program to the data element, then you will only branch to a function module from this screen once the exit has been activated. To be able to allow different functionality on different screens referring to the same data element, you can assign exit numbers to data elements. Each exit number refers to a different function module.
prefix: FIELD_EXIT_
name: <data element name>_
suffix (optional): 0 to 9, A to Z
 Field Exits It is triggered at field level.
 It is attached at data element
 Specific to one screen only or to all the screen where field appears.
 Field exit is not allowed in SAP version 4.7 and above .
Example with screen shots for consultants working in
SAP V 4.6 below version.

Help in field exits

Hello
i'm working in ECC 6 and my req is to create a field exit for a data element so as to validate the field before saving ..
i have executed the program 'RSMODRPF' and created the function module and also in CMOD in 'Field exits for data elements' when i'm trying to assign the screen name and no, it is not getting saved. i understand i need to set the system parameter 'ABAP/FIELDEXIT' to 'YES'..
my question is how to set the above system parameter? also am i in the right direction in creating a field exit to validate the field?
Thanks in advance

Hi Shekar
Please do not post multiple threads for same topic. We all could see the threads irrespective of where you have posted in ABAP Development section.

The profile parameter abap/fieldexit should be set to 'YES'. Use transaction RZ11 to check the parameter value.
Please read these threads which discusses the same problem and might be helpful,
problem field exit
Field exits don't work
Debugging Field Exits
Other Links
http://www.sap-img.com/abap/field-exits-smod-cmod-questions-and-answers.htm
Regards
Kathirvel

Creating a user-defined field in VL06

Dear all ,
Please guide me how to add few user defined fields in the output list of standard VL06 transaction code - (Delivery Monitor Report - WS_DELIVERY_MONITOR) - I have to add in the option of 'List Outbound deliveries' -
Pls revert.
Thanks in Advance.
P.G.R

Hai
Follow the bellow steps for creating User Defined Field Exit
Step by step procedure for creating Field Exits
There are eight steps to creating a field exit:
Step 1: Determine Data Element
Step 2: Go To Field Exit Transaction
Step 3: Create Field Exit
Step 4: Create Function Module
Step 5: Code Function Module
Step 6: Activate Function Module
Step 7: Assign Program/Screen
Step 8: Activate Field Exit
Step 1: Determine Data Element
- Before you can begin adding the functionality for a field exit, you must know the corresponding data element.
- An easy way to determine the data element associated to a particular screen field is to:
Go the appropriate screen.
Position the cursor in the appropriate field.
Press F1 for field-level help.
Click on the Technical info pushbutton (or press F9) on the help dialog box.
On this Technical Information dialog box, the data element will be specified if the field is 'painted' from the ABAP/4 Dictionary.
Step 2: Go To Field Exit Transaction
- The transaction to create field exits is CMOD.
- You can use the menu path Tools -> ABAP/4 Workbench -> Utilities -> Enhancements -> Project management.
- From the initial screen of transaction CMOD, choose the Text enhancements -> Field exits menu path.
- After choosing this menu path, you will be taken to the field exits screen. From here, you can create a field exit.
NOTE : Even though you use transaction CMOD to maintain field exits, you do not need to create a project to activate field exits.
Step 3: Create Field Exit
- From the field exit screen of transaction CMOD, choose the Field exit -> Create menu path.
- After choosing this menu path, a dialog box will prompt you for the appropriate data element .
- Enter the data element name and click the Continue pushbutton.
- Now, you will be able to create the function module associated to the data elements field exit.
Step 4: Create Function Module
- You will automatically be taken to the Function Library (SE37) after entering a data element name and clicking the Continue pushbutton.
- In the Function module field, a function module name will be defaulted by the system based on the data element specified. This name will have the following convention:
FIELD_EXIT_<data element>
- You can add an identifier (an underscore followed by a single character ).
- The first function module for a data elements field exit must be created without an identifier.
- To create the function module, click on the Create pushbutton, choose menu path Function module -> Create, or press F5.
- After choosing to create the function module, you will get the warning: "Function module name is reserved for SAP". This message is just a warning so a developer does not accidentally create a function module in the field exit name range. By pressing Enter, you will be able to go ahead and create the function module.
- Before coding the function module, you will have to specify the function modules attributes -- function group, application, and short text.
Step 5: Code Function Module
- From the function modules attributes screen, click on the Source code pushbutton or choose the Goto -> Function module menu path to the code of the function module.
- Here you will add your desired functionality for the field exit.
- Remember that field exits function module will have two parameters -- one importing parameter called "INPUT" and one exporting parameter called "OUTPUT". These parameters will be set up automatically by the system.
- You must remember to assign a value to the OUTPUT field. Even if the value does not change, it must be moved from the INPUT field to the OUTPUT field.
Step 6: Activate Function Module
- After coding the function module, you must remember to activate it.
- Use the Function module -> Activate menu path to activate the function module.
- At this point, you can return to the field exit transaction.
- You should be able to 'green arrow' back to this transaction.
- When you return to the field exit transaction, you will see an entry for the newly created field exit.
- At this point, the field exit is global. That is, it applies to all screens that use a particular data element. On any screen that uses the data element, the corresponding field exit function module will be triggered, once it is active.
- Also, the field exit will not be triggered yet because it is inactive.
Step 7: Assign Program/Screen
- This step is only needed if you want to make a field exit local.
- To make a field exit local, select the field exit and click on the Assign prog./screen pushbutton.
- In the dialog box , indicate the appropriate program name and screen number.
This information indicates that the field exit is local to the specified screen in the specified program.
- In the dialog box, you determine which function module gets executed for the field exit by specifying the identifier in the Fld. Exit field.
- If this field is left blank, the function module triggered will be 'FIELD_EXIT_<data element>'.
- If a single-character identifier is entered into the field, the function module triggered will be 'FIELD_EXIT_<data element>_<identifier>'.
Step 8: Activate Field Exit
- The field exit must be active for it to be triggered by the system.
- Activate the field exit by choosing the Field exit -> Activate menu path.
- After assigning the field exit to a change request, its status will change to Active and it will be triggered automatically on the appropriate screen(s).
NOTE : In order to activate the field exit the profile parameter abap/fieldexit = YES must be set on all application servers
Regards
Sreeni

AIST0002-User Exit - Validation of user defined field

I have implemented the enhancement aist0002. I added a user defined field in a user defined subcreen and added it to the leasing tabstrip. I would like to validate this field against a another field in sap's leasing subscreen. In the pai of the user defined subsrceen the field of the other subscreen does not get filled. Is there a way to access the field of the other subscreen on the leasing tabstrip from the pai module of the user defined subscreen?
Thank you
Tom

Thank you for your response but I am not sure where the import occurs?
This is the pai of the user subscreen 9000 for AS01.
form edit_input .
data: itab type lfza.
if anlu-zzempfk is not initial.
 select * from lfza into itab
 where empfk = anlu-zzempfk and
 lifnr = anla-leafi.
 endselect.
 if sy-subrc <> 0.
 set cursor field 'ANLU-ZZEMPFK'.
 message e007(zvalid).
 endif.
endif.
endform.
Function exit EXIT_SAPLAIST_002 include zxaisu03
looks like this:
anlu = i_anlu.
anla = i_anla.
Data gets moved to anlu or anla if it was already built. They are empty when it is a create transaction(as01).
Function exit exit_saplaist_003. include zxaisu04
looks like this:
e_anlu = anlu.
After the subscreen is processed it exports the data to global variable.
The problem is the pai module for the user subscreen 9000, the field anla-leafi is not filled. This field is located in sap's subsceen 1403. It has data in the screen field. My assumption is that it would be accessible as global data that could be used by my user defined subscreen once I began the validation in the pai of subscreen 9000.
Could you provide more insight on how I would access the field from the other subscreen?

Field exit is not working for a user

Hi,
We have implemented a field exit in ME12 to change the purchase info record short description. It is working fine for most of the users except for some users. I just wanted to know is there any way we can restrict the field exits based on Authorization
Did any one faced this kind of issues
Bhanu

Hi,
Reason could be that users are logged on different servers : check that profile parameter abap/fieldexit is set equally in all application servers.
If it's okay, then you'll find the reason only by tracing 2 users, one which is okay, the other not, doing exactly the same thing. To do that, use SE30 with a variant with "no aggregation", as Olga explains in her blog ([SDN blog: ABAP Runtime Analysis (SE30) - How to analyze ABAP program flow|http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/4847/17050 [original link is broken] [original link is broken] [original link is broken] ]). Then you compare the 2 traces to see from which point execution differs. You can use SAT transaction, available from 7.0, to compare 2 traces far more quickly.
BR
Sandra

Field Exit - How do I show list for user to select?

Hi,
I am writing a field exit for Group Asset on TCode AS01. The field exit will check a custom table to give the user an option to select values from a dropdown list.
Any suggestions on how to do this? I understand how to force a value in the field by putting it in OUTPUT, but not sure how to allow the user to select from a list?
Thanks!!!

Thanks for the replies!
I'm not sure how to attach a search help to it because it is a field on a standard SAP screen that already has a search help.
This is probably not going to be very clean, but let me give more details as to what I'm trying to accomplish.
There is a field "Group Asset" that is on t-codes AS01, AS01, AS11. There is already a search help provided by SAP. The functional person wants me to create a field-exit to check a custom table based on Company Code, Cost Center, and Asset Class importing PIDs. If there is only one group asset that fits the criteria, then I will just place it in the field. If there are multiple group assets, then the user has to select which one and place it in the field.
I appreciate any suggestions. Thanks!!!
Mark

Field Exit or User Exit for Maintenance Order field.

Dear All,
we need an field exit or an user exit for order(AUFNR)field in PM module.
The Client wants that the value of this field should be validated and for certaion condition an error message should be given while saving an invoice for this order.
Kindly provide the user exit ..
Its urgent.
Thansk in advance ..
regards
Ajay.

Implement Field Exit within program
For this example I am using dta element 'EBELN' from table EKKO.
Step 1: Execute program 'RSMODPRF', entering the data element of the field
Step 2:Create function module when prompted, and add you code to the source section using the parameter 'INPUT' as the field value you are checking
Step 3:      Save and activate Function and execute transaction 'CMOD'.
Step 4:      Choose option: Goto-> Text Enhancements->Data elements->New DE cust docu.
Step 3:      Save and activate Function and execute transaction 'CMOD'.
Step 4:      Choose option: Goto-> Text Enhancements->Data elements->New DE cust docu.
Step 5:      Enter data element
Step 6:      Save and activate
Step 7: Execute program 'RSMODPRF' again but this time leave data element field blank. Step 8: Select the checkbox for the data element you have just created and choose option: Field exit->Activate This will now be active for all instances of this data element, but you can assign specific program and screen combinations by pressing the 'Assign prog./screen' button. You can also change the code you entered in the field exit function module by pressing the 'Edit FM' button.
regards
vinod

Warning message in field exit

Hi All,
I'd the requirement of giving a warning message for transaction VA01 if user enters some specific order type.
So I'd created a field exit for AUART for this screen. But i am able to give error message only and found out that warning & info messages can't be given in a field exit.
Please help me out. Is there any way I can give a warning message in field exit or suggest some other sol. for it.
Thanks,
Manu

Hi,
Thanks f or your answers, but the issue is that i need to give this message as User enters the details on VA01 screen & presses enters.SO i can't use user exit like move_field_to_Vbak & others.
Also, using a FM to give pop up message will ultimately make use of statement CALL SCREEN which is not allowed in field exit, i also tried FMs which displays messages normally means not in pop up screen, but again through it also i can only give error messages.
Please suggets if there is any other option.
Thanks,
Manu Parihar

Use of field exit for validation of KNTTP in ME51N

Hi All,
I've a client who is still running on SAP 4.6C. There is a requirement to validate the Account Assignment Field KNTTP based on the document type, and if the validation fails, to raise an error message. As there is no standard user exit that I've been able to find for this field, and we don't want to modify standard screens, I've created a field exit against the KNTTP field and generated the FM FIELD_EXIT_KNTTP, and activated it, but it doesn't work.
As this is the first Field Exit I've coded could someone please assist me with understanding the following: in the parameters list is the value of INPUT the value of, in this instance, the KNTTP field and also is it possible to read other screen data within this FM, for example, if the KNTTP value eq 9, can I read the BSART field of the current transaction, and if so, how do I reference it (BSART, EKKO-BSART, MEREQ_TOPLINE-BSART, parameter id BSA, etc)?
Any suggestions on how to debug the process would be greatly appreciated as well.
Any help would be greatly appreciated.
Regards,
Steve

Due to lack of assistance, we were unable to pursue this requirement - the users were not happy, but what can you do, huh!

Field Exit for ME21N & ME22N transactions

HI Friends,
I need to make the SAP Standard screen field "Overdeliv. Tol." & "Unlimited" to inactive under the Item level data --> Delivery tab in ME21N & ME22N transaction.
Can i do ths? If so give me the steps and Screen exit for the same...

For User Exit's
goto to tcode->status->program name->double click on that,
then goto to-> attribute take the package name and
Goto SMOD tcode ->Utilities->give the package name and F8
then a list of exits will display for that tcode as well as that package.
double click on the exit u can see the Fm exit,screen exit,feild exit,include exit. there
u can check the table MODSAP
For BADI's,
1)goto to tcode SE24 give the CL_EXITHANDLER and display and then double click on the GET_INSTANCE
keep Break point at this location 'call method cl_exithandler=>get_class_name_by_interface'
then the tcode it will trigger there and we can debugg there we can find badi'for that tcode and then remove the break point.
2)Goto to tcode->status->program name->double click on that program will display's
then press crtl+F then cl_exithandler
Thank u,
santhosh

User Exit, Field Exit

Similar Messages

Maybe you are looking for