What is an exit ?

Hello Experts,
I have a basic question.
What is an Exit in SAP ? Does the word refer to its literal meaning here too?
If so, where do we exit from and what do we enter in ?
Please educate me and I promise points

Hi Raj,
SAP provides you a place to include your custom code to enhance/modify the standard functionality, it is called exit.
Regards,
Praveen

Similar Messages

What is AT Exit-Command in MPP

Hi all
What is AT Exit-Command in MPP...

Hi rohini,
The statement associated with at exit command is :
MODULE <module_name> AT EXIT-COMMAND.
Addition AT EXIT-COMMAND at the event PAI causes module <module_name> to be called exactly as if:
a)The function used to trigger event PAI has function type "E"
b )Into the input field of the standard toolbar, the user entered a character string starting with "E" and confirmed it using ENTER.
The dialog module is called before the automatic input checks defined in the system or in the ABAP Dictionary and independent of its position in the event block. The only screen field transported to the ABAP program is the OK field. If the function that triggered the PAI event does not fulfill any of the above prerequisites, the MODULE statement is not executed.
If several MODULE statements have the AT EXIT COMMAND addition, only the first one is executed. If no MODULE statement has the addition AT EXIT COMMAND, a normal PAI processing is executed: The predefined input checks are executed and then the PAI event block is processed sequentially. Provided the screen processing is not terminated in the dialog module mod, after the return from the dialog module, the complete PAI processing is executed. You must not use the addition AT EXIT COMMAND in connection with the statement FIELD.
The function type of a function is determined in the Screen Painter or Menu Painter. Usually those functions of the user interface are defined with function type "E" that are assigned to the icons Back, Exit and Cancel in the standard toolbar of the GUI status. Therefore, the called dialog module should terminate the screen processing and allow security checks, if required.
If you are talking about the on exit-command in report programming,
then the statement associated with it is
at selection-screen on exit-command.
Effect
This event is triggered if the user has called one of the functions Back, Exit or Cancel. In the event block, possible clean-up actions can be executed.

What is the Exit / Badi triggered after PGI is done in VL02N???/

What is the Exit / Badi triggered after PGI is done in VL02N??/ Once PGI is done then i have to update some tables. so whats is the userexit or a bapi that is triggered ones the PGI is done.?????????????

BADI LE_SHP_GOODSMOVEMENT is called when the post goods issue is performed.
It handles a number of goods movements, so is_likp-lfart eq 'LF' will limit it down to goods movements for deliveries.

What is conversion exit in SAP BI

Hi to all,
Please can any body can tell me what is conversion exit in SAP BI.
Regards
Pavneet Rana
If you do a search in http://help.sap.com/erp2005_ehp_04/helpdata/EN/2a/fa0115493111d182b70000e829fbfe/frameset.htm
you will find lots of documentation:
Colin
Edited by: Colin Moloney on Jun 9, 2010 10:18 AM

If you do a search in http://help.sap.com/erp2005_ehp_04/helpdata/EN/2a/fa0115493111d182b70000e829fbfe/frameset.htm
you will find lots of documentation:
Colin

In what case the exit MBCF0002 is useful.

In what case the exit MBCF0002 is useful. please explain with an exmple.

The user exit MBCF0002 includes a function module that is called up when you enter a goods movement for each item.
It enables you to fill in the item text in the material document item, depending on the following data:
MKPF     (Material document header)
MSEG     (Material document item)
VM07M    (Additional data for material document item)
DM07M    (Additional data for material document item)
The item text is also stored in the accounting document.
Examples:
Goods receipt for a purchase order assigned to an account: since the purchase order number does not contain a material number, the material description entered in the purchase order is used as an item text (field MSEG-SGTXT).
Example of source text:
IF I_MSEG-MATNR IS INITIAL.
    E_SGTXT = I_DM07M-MAKTX.
ENDIF.
If the material description is to be used as the item text for all goods movements, the source text has the following line only:
E_SGTXT = I_DM07M-MAKTX.
*I think this will clear you abt this exit. This is the standard sap help.For help goto SMOD, enter the enhancement and select the Documentation and go through it..
Reward if helpful..
Regards,
Srib

What is User Exits ? what are Enhancements

What is User Exits ? what are Enhancements ?

You can find information in the SAP help, e.g. under http://help.sap.com/saphelp_nw04/helpdata/en/c8/1978b543b111d1896f0000e8322d00/frameset.htm.
User exits can be realized through BADI's or customer exits.
In SAP Standard Transactions, if you need to do some customization via programming then SAP has identified the milestones in the behavior of the transactions where these customized effects may be needed.
This customization to standard transactions is done by some special function modules wherein one can write the customized code with the given SAP import/export parameters. These function modules relate to user exits. Transaction for user exit & its usage in any project are CMOD/SMOD.
Create a project in CMOD and implement that project in SMOD
PS If the answer solves your query, plz do reward points to everyone responding.

What are user exits & enhancements & how to use those .

What are user exits & enhancements & how to use those .

Hi,
BADI , Customer Exit / User Exit , Enhancement all are same.
Customer Exit & User Exit terms were earlier used in case of R/3. Now in ECC 6.0 they are known as
BADI means Business Add-Ins.
BADIs :
Use:
SAP provides multiple implementations of Business Add-Ins (BAdIs), which enhance the functions of the Configuration Control component.
In addition, there are multiple empty BAdIs available for implementing a customer-specific logic for special functions.
Pls. find listed below some important PP Enhancements / BADIs :
Exit name Short text
PPAPO002 Publication of APO Data in Transfer from APO to R/3
PPAPO003 Production Order R/3->APO: Check if Operation is APO-Re
PPAPO004 Planned Order Conversion from APO: New BOM Explosion?
PPAPO005 Enh. of Relationships in Proc. Order during Transfer to
PPAPO006 Influencing Initial Supply of Manufacturing Orders
PPAPO007 Overriding Checkbox Fields for Production Order APO ->
PPAPO008 Override Order Type for Planned Order Conversion
PPAPO009 Customer Exit for Addition of Components and Items
PPAPO010 Filtering Components out of Quantity Propagation
PPAPO011 Performance-Related Adjustment of Remaining Duration
PPCO0001 Application development: PP orders
PPCO0002 Check exit for setting delete mark / deletion indicator
PPCO0003 Check exit for order changes from sales order
PPCO0004 Sort and processing exit: Mass processing orders
PPCO0005 Storage location/backflushing when order is created
PPCO0006 Enhancement to specify defaults for fields in order hea
PPCO0007 Exit when saving production order
PPCO0008 Enhancement in the adding and changing of components
PPCO0009 Enhancement in goods movements for prod. process order
PPCO0010 Enhancement in make-to-order production - Unit of measu
PPCO0012 Production Order: Display/Change Order Header Data
PPCO0013 Change priorities of selection crit. for batch determin
PPCO0014 Select process orders for external relationships
PPCO0015 Additional check for document links from BOMs
PPCO0016 Additional check for document links from master data
PPCO0017 Additional check for online processing of document link
PPCO0018 Check for changes to production order header
PPCO0019 Checks for changes to order operations
PPCO0020 Process order: Display/change order header data
PPCO0021 Release Control for Automatic Batch Determination
PPCO0022 Determination of Production Memo
PPCO0023 Checks Changes to Order Components
PPCP0001 P.Cost Planning: Additional Cost Elements for Person
PPEACT01 Customer Fields at Mode D
PPECMP01 Customer Fields for CMP Node
PPECMP02 Customer Fields: CMP Variants
PPEGEN01 General Engineering Node: Customer Fields
PPEMPA01 MPA Customer Enhancement
PPEMPO01 Customer Enhancement for Material Planning Object
PPEMPO02 Customer Enhancement for Model
PPERES01 Customer Fields at RES Node
Alternately you can find User Exits / BADIs in TCode : SMOD ( SAP Enhancements)
Hope this helps.
Regards,
Tejas

What is Field Exit--Step By Step procedure..

Hi,
What is Field Exit.
And How to validate a field on any screen using field exit.
what is the Procedure.
Please give me Step by Step Procedure.
Points will be given for straight answers..
Regards,
Kiran

Please find below the step by step procedure for field exit :-
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
Kiran

What is user exit to update individual length in batch master?

Hi,
We need some help on user exit. We are using MILL production, SAP_MILLCA_LENGTH_SUB.
May I know what is the user exit will be called when we perform good issue to production order (movement type 261)?
We need to customize some logic to update the individual length in batch master.
Any sugession?
Thanks in advance.

Hi,
You can do this things by maintaining material classification with characteristic by length or breadth.So at the time of GR you have to maintain the characteristic field and by the help of batch search strategy you can get the relevant batch.
You search extensively in google you can find proper documentations for the same.
Regards
AKS

What is user exit in MM?

is there any difference between user exit and enhancement? does a end user raise a ticket for user exit? please help
Edited by: sherlyn chopra on Oct 1, 2008 4:36 PM

What is and how user exits can be used?
What is the transaction code to see all available user exits?
Method of using this?
User exit jus nothing but just a code ....which is not provided the standard sap system..but function could be added later into the code ..this is done by abap people...
User exit is a place where we can write our own logic inside SAP programs. Instead of modification of SAP code, we can place our custom logic in User Exit.
There are three types of User exits:
1. Function Exits
2. Menu Exits
3. User Exits
Finding User Exits:
1. Take VA03 as example. Go to System status; select the program (double click); Find by the key word u2018Call Customer-functionu2019; Double click on the u2018Call Functionu2019 to go to the code; Double click on the customer function no.
It will take to the function exit in which SAP provides a Include program, where we can write down our own logic.
2. Run transaction SE84 and click on u2018Enhancementu2019 on left screen. Then click on u2018Customer Exitsu2019. Then double click on u2018Enhancementsu2019.
3. In transaction CMOD, type the name of your project and press the CREATE pushbutton; Once you SAVE your project, you can add as many enhancements as you want by pressing the SAP enhancements pushbutton; Add the enhancements
you want to add to the Project.
4. There are some exit provided by SAP in the program as subroutines. For example, go to transaction VA02; Double click on the program. It will take to the program; Some includes are provided by SAP as user exit. Double click on the include name, then it will take inside the include. Double click on MV45AFZZ (Program)include; Here we have different forms which acts as user exits. In these forms we can include our custom logic
5. Open the program through SE80 transaction; Click on the u2018Screenu2019 and all the available screens will be displayed. Then search if any Exit screen is available. Normally short text of the screen gives an idea whether Exit screen or not.
6. Finding BADIs : Double click on the u2018Programu2019; Search by string u2018cl_exithandler=>get_instanceu2019
;Search result is displayed. Double click on any one in the list.
http://www.sap-basis-abap.com/abap/difference-between-user-exits-screen-exits-field-exits.htm
http://www.sap-basis-abap.com/pm/user-exits-in-sap-pm.htm
http://www.sap-basis-abap.com/sapab013.htm
for eg:
BAPI_INCOMINGINVOICE_CANCEL Invoice Verification: reverse invoice
BAPI_INCOMINGINVOICE_CREATE Invoice Verification: Post Invoice
BAPI_INCOMINGINVOICE_GETDETAIL Invoice Verification: display invoice
BAPI_INCOMINGINVOICE_GETLIST Invoice Verification: List Invoices
BAPI_INCOMINGINVOICE_PARK Invoice Verification: Park Invoice
BAPI_INCOMINGINVOICE_RELEASE Invoice Verification: release invoice
BAPI_INCOMINGINVOICE_SAVE Invoice Verification: Flag Invoice for Background Processing
Thanks & Regards,
Kiran

Is APICS useful? What are my exit options after SAP ?

Hi,
I have completed my MBA and will be joining SAP as business process consultant in supply chain. As I will be doing SAP certifications in the company, I was thinking of doing APICS certifications (CPIM/CSCP), first I wanted to understand whether it would be a good idea to do the APICS certification i.e. would it actually have any value addition, second which one should I consider (CPIM or CSCP) and would be more helpful for me.
Also, is it that after joining SAP, I will be restricted to SAP related jobs, (i.e. ERP roles) or will I be able to switch to supply chain roles in Retail/FMCG sector and eventually move to strategy roles (management consulting). Though I know I would be learning implementation of SAP in multiple sector, I actually wanted to know my exit options.
I would be really glad if someone would help me better understand.
Thanks
Rohit

Not sure why you posted this in the iPhone forum but sorry you're having such a difficult time. With that being said, unfortunately, VZW isn't obligated to assist you in difficult financial times although it would be great if they did. As far as you wanting to get into a non-smart phone to lessen your bill...you will have to look into alternative ways to obtain one if you want to avoid paying full retail. Do you have any friends with Verizon? Check and see if any of them have an old phone that they don't use. Lower your plan to less minutes and actively monitor your usage. Save non-essential personal calls until after 9:00 pm on weekdays if you're calling non-verizon customers. Even without a house phone it is not difficult to get by on a 450 min plan without going over your minutes. My mother did it for 5 years and never once went over her minutes nor did she have a landline phone to use. Text when possible to avoid using minutes. If you stay with the Droid then try to find texting apps or widgets that can help eliminate the need for a text plan. You can also check into services like Skype that can allow you to make free calls to other users...some of your friends may gladly subscribe to those services so that you can communicate and use less plan minutes. You should also talk to VZW to see what lower plan options you have.

What ActionScript quits/exits/closes a SWF?

To offer a user the chance to quit the Flash application and
return to the web site, I have a button. What ActionScript do I
attach to the button in order to quit the swf and close the window
it is in?

I have a container swf that creates movie clips and loads
swfs into them. The first swf is a tease or advertisement for the
survey. When this movie clip is clicked it brings in the survey
which is called success tool.
This works fine but I do have a problem with it, which is
that the sounds in my survey (user feedback sounds that play when
survey answers are selected) turn off when the survey is loaded.
It sounds as though it's fine to just put a link on my exit
button to simply navigate back to the web site, who cares if the
swf is still running?
But what is the "closure" event I can use to trigger sending
my data out of the swf to my email? That is, if the user closes the
swf without finishing the survey, and therefore without getting to
my exit button where I can attach ActionScript to send my data out,
is there an event to which I can attach AS so that the data is sent
whenever the close takes place? Or is there another way to handle
this data which I need for market research and to build a database
of survey responses?

What is USER EXIT ..?

Hi all
can anybody explain me briefly about the user exit in SAP-MM module .
1.Why the user exit we r using ..?
2.Pls explain me with some standard user exit .
3.ANd explain me , how to develop the new user exit for USER EXIT in MM
Thanks
sap-mm

Hi
1.Why the user exit we r using ..?
The R/3 enhancement concept allows you to add your own functionality to SAPu2019s 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.
There are several different types of customer 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 itemu2019s 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 screenu2019s 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 pulldown 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 u2018001u2019.
2.Pls explain me with some standard user exit .
ME590001 - Grouping of requsitions for PO split in ME59
This user exit can be used for Grouping multiple PR's with similar items into one PO.
This has the Function exit - EXIT_SAPLME59_001
Grouping of Requisitions for Automatic Generation of Purchase Orders
3.ANd explain me , how to develop the new user exit for USER EXIT in MMWe cannot develop new user exits , we can only use the existing user exits in the stnadrad Programs whcih are vailable.
The User exits are implmented using Transaction CMOD
you need to know ABAP coding for Implementing the same.
Use Transaction SMOD to list down all the user exits avialble.
Thanks & Regards
Kishore

What is customer exits?

Can someone explain customer exits?
Can it be used more than once?

A pre-planned enhancement to the standard SAP System.
SAP anticipates potential customer requests not already implemented in the standard system by predefining them as empty modification modules. Customers fill these modules with their own logic according to their own requirements.
SAP creates customer exits using the Transaction SMOD. From these customer exits, customers then use the Transaction CMOD to choose the enhancements they want to process, assign them to enhancement projects, edit the components, and activate the relevant projects.
Using customer exits guarantees upwards compatibility. This is because calls to exits from the standard software and the validity of the call interface are retained, even in future release upgrades.

What are User exits?

Hi SAP gurus can u explain me on user exits?

Hi Chandrakanth,
Userexits are system modifications. The requirements of the client which can be met with Standard SAP are done with help of routines or userexits.
Userexits are nothing but a provision given by sap to write your own code/logic in the standard program.
Say for example while processing a sales order you want to check certain criteria weather they are met or not then you can use userxit_save_document_prepare.Here depending on the code you write system checks the if the criteria is fulfilling if not you can set an error or warning message in the code. This userexit is being executed just before saving of document.
one more commonly used exit is adding field in field catalog
In spro check this path Sales and Distribution-System modifications-Userexits.
Read the document provided,you will find all the exits in different processing for SD with program name and their purpose.
User exits are the enhancements provided by SAP
you can use them in transactions. Each transaction will have user exits.
If you want to use your own requirements by making your coding while the transaction is run you can use user exits.
For example if you want to run the MRP in MD02 specific to MRP controller you can user exit.
Please also refer the document below.
USEREXIT
Userxits allow us to add our own functionality to SAP standard program
without modifying it. These are implemented in the form of subroutines and hence are also known as FORM EXITs. The userexits are generally collected in includes and attached to the standard program by the SAP.
All Userexits start with the word USEREXIT_...
FORM USEREXIT_..
z..
ENDFORM.
The problem lies in finding the correct userexit and how to find it if one exists for the purpose. Once the correct userexit is found the necessary customer code is inserted in the customer include starting with the z. in the form routine.
e.g. USEREXIT_SAVE_DOCUMENT_PREPARE
Certain application like SD still provide this form of enhancement using userexit but this practice is no longer being followed for newer extensions instead they are using EXITs which come bundled in enhancement packages . Nevertheless existing USEREXITS will be supported by SAP an all the newer versions of SAP.
HOW TO FIND USEREXITS
Userexits can be found in number of ways:
1) To find userexits in SD module , goto object navigator(SE80) and select
development class from the list and enter VMOD in it. All of the userexits in SD are contained in the development class VMOD. Press enter and you will find all the includes which contain userexits in SD for different functions like PRICING, ORDER PROCESSING etc. Select the userexit according to the requirement and read the comment inserted in it and start coding.
Some examples of userexits in SD (SALES & DISTRIBUTION) are:
1)ADDING OF NEW FIELDS IN PRICING
In Pricing in SD the fields on the basis of which pricing is done are derived from the FIELD CATALOG which is a structure KOMG .This structure is used to transfer transaction data to the pricing procedure in SD and is also known as communication structure. This structure KOMG consists of two tables KOMK for Header related fields and KOMP for item related fields. The fields which are not in either of the two tables KOMK and KOMP cannot be used in pricing .Sometimes a need arises when the pricing is to be based on some other criteria which is not present in the form of fields in either of the two tables. This problem can be solved by using USEREXITS which are provided for pricing in SD. Pricing takes place both when the SALES ORDER ( Transaction VA01) is created as well as when INVOICING ( Transaction VF01) is done. Hence SAP provides 2 userexits ,one for sales order processing which is
USEREXIT_PRICING_PREPARE_TKOMP or
USEREXIT_PRICING_PREPARE_TKOMK
Depending upon which table (KOMK or KOMP) the new fields were inserted we use either of the above two userexits.These userexits are found in include MV45AFZZ of the standard SAP sales order creation program SAPMV45A.
In the case of userexit which will be called when invoicing is done ,these
are provided in the include RY60AFZZ which is in the standard SAP program SAPMV45A. The name of the userexits are same. i.e.
USEREXIT_PRICING_PREPARE_TKOMP or
USEREXIT_PRICING_PREPARE_TKOMK
These userexits are used for passing the data from the communication structure to the pricing procedure, for this we have to fill the newly created field in the communication structure KOMG for this we fill the code in the above userexit using the MOVE statement after the data that has to be passed is taken from the database table by using the SELECT statement. The actual structure which is visible in these userexits and which is to be filled for that particular field is TKOMP or TKOMK.
Before the coding for these userexits is done ,it is necessary to create a new field in either of the two tables KOMK or KOMP .For this purpose includes are provided in each of them .
To create the field in header data (KOMK) the include provided is KOMKAZ
and to create the field in item data (KOMP) the include provided is KOMPAZ.
One possible example for the need of creating new fields can be e.g. Freight to be based upon transportation zone, for this no field is available in field catalog and hence it can be created in KOMK and then above userexits can be used to fill the transportation data to it.
2) The other method of finding userexit is to find the word USEREXIT in the
associated program of the transaction for which we want to determine userexit using SE38.
3) The other method of finding userexits is to find the include in case of SD/MM applications where the userexits are located, this can be found in the SAP reference IMG generally in the subfolder under SYSTEM MODIFICATION.
Some other examples of userexits in SD are:
USEREXIT_NUMBER_RANGE
This userexit is used to assign a different internal document number to the
sales order(VA01) when it is created depending on some criteria like a different SALES ORGANIZAION(VKORG) .
USEREXIT_SAVE_DOCUMENT_PREPARE
This userexit is used to insert the ABAP code which will be called when
the document (sales order VA01) is just about to be saved. This userexit is used generally for custom checks on different fields , to display some information before the order will be saved or for making changes to certain fields before the sales order will be saved.
Exits & Enhancements
There are mainly six types of EXITs in sap which have been collected in the form of enhancement packages and attached to standard code in SAP.
These are different from USEREXIT in the way that they are implemented
in the form of FUNCTIONs while in USEREXITS we use form routines for their implementation. These are also sometimes known as function exits.
These start from the word EXIT_ followed by the program name and then followed by a three digit number.
e.g. EXIT_SAPMV45A_002
This exit is found in SD in enhancement V45A0002.
TYPES OF EXITS
1) MENU EXITS
2) FUNCTION EXITS
3) TABLE EXITS
4) SCREEN EXITS
5) KEYWORD EXITS
6) FIELD EXITS
We use SAP transactions CMOD and SMOD to manage exits. Before implementing an exit, it is required to create the project by using CMOD
selecting the enhancement e.g. V45A0002 and selecting the component
(one which fulfills our need) i.e. the exit which will be implemented in SMOD and after coding has been done the project has to be activated.
An exit can be coded only once.
FUNCTION EXITS
These are used to add functionality through ABAP code. These start from the word EXIT_programname_NNN ending in a 3 digit number. No access code is required to implement any type of exit including function exits.
The function exits are called from the standard SAP program in the form
of ABAP statement
CALL CUSTOMER-FUNCTION 'NNN'
This is in contrast to USEREXITs where PERFORM statement is used to call
the required userexit.
To implement the FUNCTION EXITs first of all the project is created and a suitable enhancement package is selected and from its components the function exit to be implemented is selected and on double clicking it the exit code will appear in ABAP EDITOR(se38) where a Z include will be found and the customer code should be entered in this include.
e.g.
ADDING A DEFAULT SOLD-TO-PARTY in Sales Order Creation
To show a default sold-to-party in this field when the user creates a sales order (VA01) we can use a function exit .This function exit is located in enhancement no V45A0002 . Before we can choose the exit we have to create a project in CMOD after that enter V45A0002 in the enhancement field and click on the components. In the components you will see the exit EXIT_SAPMV45A_002. This exit is used for our purpose.
Double clicking on this exit will takes us to function builder (SE37) . This
function exit has one exporting parameters and two importing parameters, we are interested in exporting parameter which is E_KUNNR of type KNA1-KUNNR i.e. if we move the desired customer name to this structure(E_KUNNR) it will be shown in the field as the default value when we create the sales order. This function also contains a customer include ZXVVA04. This include will be used to write our custom code.
Double clicking on this include and it will prompt us that this include does not exists do you want to create this object, select yes and the include will be created .In this include we can write our own code that will fill the field E_KUNNR.
e.g. E_KUNNR = 301.
Activate the include and Activate the project. Now when ever the SALES ORDER will be created, sold-to-party field will come up with a predefined customer.
FIELD EXITS
The field exits are managed, created, activated through program RSMODPRF. The field exit is associated with a data element existing in ABAP dictionary and hence to the screen field using that data element.
The format of field exit is:
FIELD_EXIT_dataelement_A-Z or 0-9
If a particular screen and program name is not specified than the field exit will effect all the screens containing that data element.
The function module associated with field exit shows two parameters
INPUT and OUTPUT. Input parameter contains the data passed to the field exit when the field exit was invoked by the R/3, we can write our own code to change the output parameter depending upon our requirements.
Before the field exit can have any effect the system profile parameter
ABAP/FIELDEXIT in all the application servers should be set to YES
ABAP/FIELDEXIT = YES.
User exits in the SD orders. These are program names (SE38):
MV45ATZZ
For entering metadata for sales document processing. User-specific
metadata must start with "ZZ".
MV45AOZZ
For entering additional installation-specific modules for sales
document processing which are called up by the screen and run under
PBO (Process Before Output) prior to output of the screen. The
modules must start with "ZZ".
MV45AIZZ
For entering additional installation-specific modules for sales
document processing. These are called up by the screen and run under
PAI (Process after Input) after data input (for example, data
validation). The User exits in the SD orders. These are program names (SE38):
MV45ATZZ
For entering metadata for sales document processing. User-specific
metadata must start with "ZZ".
MV45AOZZ
For entering additional installation-specific modules for sales
document processing which are called up by the screen and run under
PBO (Process before Output) prior to output of the screen. The
modules must start with "ZZ".
MV45AIZZ
For entering additional installation-specific modules for sales
document processing. These are called up by the screen and run under
PAI (Process after Input) after data input (for example, data
validation). The modules must start with "ZZ".
MV45AFZZ and MV45EFZ1
for entering installation-specific FORM routines and for using user
exits, which may be required and can be used if necessary. These
program components are called up by the modules in MV45AOZZ or
MV45AIZZ. e modules must start with "ZZ".
MV45AFZZ and MV45EFZ1
for entering installation-specific FORM routines and for using user
exits, which may be required and can be used if necessary. These
program components are called up by the modules in MV45AOZZ or
MV45AIZZ.
SMOD is the transaction to view user exits assigned to an object.
CMOD is the transaction to change the user exits according to your requirement.
You can find user exits by looking into the phrase USER_EXIT.
Check this program to find out user exits for a transaction
TABLES: tftit,
e071,
e070.
TYPES: BEGIN OF x_tstc,
tcode TYPE tcode,
pgmna TYPE program_id,
END OF x_tstc.
TYPES: BEGIN OF x_tadir,
obj_name TYPE sobj_name,
devclass TYPE devclass,
END OF x_tadir.
TYPES: BEGIN OF x_slog,
obj_name TYPE sobj_name,
END OF x_slog.
TYPES: BEGIN OF x_final,
name TYPE smodname,
member TYPE modmember,
include(15), "Include name
END OF x_final.
DATA: it_tstc TYPE STANDARD TABLE OF x_tstc WITH HEADER LINE.
DATA: it_tadir TYPE STANDARD TABLE OF x_tadir WITH HEADER LINE.
DATA: it_jtab TYPE STANDARD TABLE OF x_slog WITH HEADER LINE.
DATA: it_final TYPE STANDARD TABLE OF x_final WITH HEADER LINE.
SELECTION-SCREEN: BEGIN OF BLOCK blk01 WITH FRAME TITLE text-t01.
PARAMETERS: p_tcode LIKE tstc-tcode OBLIGATORY.
SELECTION-SCREEN END OF BLOCK blk01.
START-OF-SELECTION.
PERFORM get_tcodes. "Get Tcodes
PERFORM get_objects. "Get Objects
END-OF-SELECTION.
PERFORM display_results. "Display Results
FORM get_tcodes.
SELECT tcode
pgmna
INTO TABLE it_tstc
FROM tstc
WHERE tcode = p_tcode.
IF sy-subrc = 0.
SORT it_tstc BY tcode.
ENDIF.
ENDFORM. " get_tcodes
FORM get_objects.
DATA: l_fname LIKE rs38l-name,
l_group LIKE rs38l-area,
l_include LIKE rs38l-include,
l_namespace LIKE rs38l-namespace,
l_str_area LIKE rs38l-str_area.
DATA: v_include LIKE rodiobj-iobjnm.
DATA: e_t_include TYPE STANDARD TABLE OF abapsource WITH HEADER LINE.
DATA: l_line TYPE string,
l_tabix LIKE sy-tabix.
IF NOT it_tstc[] IS INITIAL.
SELECT obj_name
devclass
INTO TABLE it_tadir
FROM tadir FOR ALL ENTRIES IN it_tstc
WHERE pgmid = 'R3TR' AND
object = 'PROG' AND
obj_name = it_tstc-pgmna.
IF sy-subrc = 0.
SORT it_tadir BY obj_name devclass.
SELECT obj_name
INTO TABLE it_jtab
FROM tadir FOR ALL ENTRIES IN it_tadir
WHERE pgmid = 'R3TR' AND
object = 'SMOD' AND
devclass = it_tadir-devclass.
IF sy-subrc = 0.
SORT it_jtab BY obj_name.
ENDIF.
ENDIF.
ENDIF.
*- Get UserExit names
LOOP AT it_jtab.
SELECT name
member
INTO (it_final-name, it_final-member)
FROM modsap
WHERE name = it_jtab-obj_name AND
typ = 'E'.
APPEND it_final.
CLEAR it_final.
ENDSELECT.
ENDLOOP.
*- Process it_final contents.
LOOP AT it_final.
l_tabix = sy-tabix.
CLEAR: l_fname,
l_group,
l_include,
l_namespace,
l_str_area.
l_fname = it_final-member.
CALL FUNCTION 'FUNCTION_EXISTS'
EXPORTING
funcname = l_fname
IMPORTING
group = l_group
include = l_include
namespace = l_namespace
str_area = l_str_area
EXCEPTIONS
function_not_exist = 1
OTHERS = 2.
IF sy-subrc = 0.
IF NOT l_include IS INITIAL.
*- Get Source code of include.
CLEAR: v_include, e_t_include, e_t_include[].
v_include = l_include.
CALL FUNCTION 'MU_INCLUDE_GET'
EXPORTING
i_include = v_include
TABLES
e_t_include = e_t_include.
IF sy-subrc = 0.
LOOP AT e_t_include.
IF e_t_include-line CS 'INCLUDE'.
CLEAR l_line.
l_line = e_t_include-line.
CONDENSE l_line NO-GAPS.
TRANSLATE l_line USING '. '.
l_line = l_line+7(9).
it_final-include = l_line.
MODIFY it_final INDEX l_tabix TRANSPORTING include.
ENDIF.
ENDLOOP.
ENDIF.
ENDIF.
ENDIF.
ENDLOOP.
ENDFORM. " get_objects
FORM display_results.
FORMAT COLOR COL_HEADING.
WRITE:/1(150) sy-uline.
WRITE:/ sy-vline,
2(23) 'Extension Name',
24 sy-vline,
25(39) 'Exit Name',
64 sy-vline,
65(74) 'Description',
140 sy-vline,
141(9) 'Include',
150 sy-vline.
WRITE:/1(150) sy-uline.
FORMAT RESET.
SORT it_final BY name member.
LOOP AT it_final.
CLEAR tftit.
SELECT SINGLE stext
INTO tftit-stext
FROM tftit
WHERE spras = 'EN' AND
funcname = it_final-member.
WRITE:/ sy-vline,
it_final-name COLOR COL_KEY, 24 sy-vline,
25 it_final-member, 64 sy-vline,
65 tftit-stext, 140 sy-vline,
141 it_final-include, 150 sy-vline.
WRITE:/1(150) sy-uline.
ENDLOOP.
ENDFORM. " display_results
Hope this Clarifies your Doubts and Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula

What is an exit ?

Similar Messages

Maybe you are looking for