on 10-04-2008 8:39 AM
Hi all,
What is user exist?
How it will be configured?
Where all it will be used,like in SD for certain transctions I heard there will be user exists,
Kindly let me know about User exists.
hi,
User exits are standard gate ways provided by SAP to exit the standard code and we can write our own code with the help of ABAP workbench. its not new functionality which we are trying to build in sap but its slight enhancement within the same code.
Regards,
Jaiprakash.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Seema,
kindly check the link below:
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
Thanks & Regards
T.Arulvanan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Seema+ Please make a search in this forum you will get tons of inputs. +thanks G. Lakshmipathi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Any forum will give you tons and tons more of inputs (adding upon Lakshmipathi's post).
Check the wiki:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/erplo/sdUserexits
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/erplo/userexitforRestrictingUserModifyingConditiontypeinSales+Order
Regards,
GSL.
Dear Seema,
User exit
A point in an SAP program where a customer's own program can be called.
In contrast to customer exits, user exits allow developers to access and modify program components and data objects in the standard SAP System. On upgrade, each user exit must be checked to ensure that it conforms to the standard system.
There are the following types of user exit:
User exits that use INCLUDEs -
These are customer enhancements that are called directly in the program.
User exits that use tables -
Purpose
If the standard PC operations are insufficient, you have the option of using User Exits as processing steps.
For example, if you want to process other non-standard infotypes.
The number of processed infotypes is fixed in a processing context.
These are used and managed using Customizing.
I can give you one simple example:-
When we delete the farwarding agent as per the standard process system will allow the deleted FA with warrning message but client requirement is systen should not allow if the sales order have deleted Farwarding agent(FA) at this situation User Exit will be used to convert the warrning message to error message.
I hope this will help you,
Regards,
Murali.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
107 | |
12 | |
11 | |
6 | |
5 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.