‎2007 Sep 06 8:26 AM
Hi SDN,
What are the standard ways to write & implement user exit.
What code one should avoid in user exit?
Can we write Data base commit, Error messages table update etc. in user exit?
Regards,
Rahul
‎2007 Sep 06 8:31 AM
Hi
yes you can write messages inside user exits..but lagre commitns and updates are avoidable.
exits are for generally samll validations.
just check this
you will get every thing
http://www.csee.umbc.edu/help/oracle8/server.815/a42525/ch11.htm#toc126
reward if helpful
vivekanand
‎2007 Sep 06 8:31 AM
Hi
yes you can write messages inside user exits..but lagre commitns and updates are avoidable.
exits are for generally samll validations.
just check this
you will get every thing
http://www.csee.umbc.edu/help/oracle8/server.815/a42525/ch11.htm#toc126
reward if helpful
vivekanand
‎2007 Sep 06 8:36 AM
Hi Rahul,
There is no standard way to write User Exits, coz if there was a standard way SAP would have done that themselves and it would not have been called User Exits.
User Exits are meant to provide you with additional functionality, which SAP doesn't provide. So User Exits are most commonly used for:
- Enhancement to the existing functionality.
- Populating Custom tables
- Adding Field Values to Screen Exits
- Sometimes for extra checks and validation that you need.
Bottom Line : It allows you the flexibility to customize the standard functionality to meet your specific business needs.
You should avoid following codes in the user exits :
-Changes to the Internal Tables ,structures and variables being used by the
standard program. If need be you can create a copy of the variables you need
and do your processing.
- Database commits should be avoided(You can write it but its not advised)
- Error Messages can be done, but be careful as to where you place it.
- As long as it is Custom tables you can update them through User Exits, but
not standard tables(you are not supposed to do that anywhere except SM30
or BDC).
Reward if helpful.
Best Regards,
Imran