‎2006 Nov 14 9:15 AM
Hi all
Can anybody explain me abt customizing,personalization and modifications.
Thanks and regards
vijaya
‎2006 Nov 14 9:21 AM
The R/3 enhancement concept allows you to add your own functionality to SAPs 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. Thus Enhancements allow you to add additional functions to the SAP standard.
If you want to enhance the functionality of your SAP System, you should take advantage of the exits available in standard R/3 applications. There are two main reasons why you should use exits rather than modifying SAP software yourself. Add-ons attached to exits have the advantage that:
-> They do not affect standard SAP source code
-> They do not affect software updates
http://www.erpgenie.com/sap/abap/code/abap26.htm
which gives the list of exits for a tcode
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec079f5db911d295ae0000e82de14a/frameset.htm
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sapgenie.com/abap/code/abap26.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
http://www.easymarketplace.de/userexit.php
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sappoint.com/abap/userexit.pdfUser-Exit
http://www.planetsap.com/userexit_main_page.htm
Business add-ins are enhancements to the standard version of the system. They can be inserted into the SAP System to accommodate user requirements too specific to be included in the standard delivery. Since specific industries often require special functions, SAP allows you to predefine these points in your software.
SAP guarantees the upward compatibility of all Business Add-In interfaces. Release upgrades do not affect enhancement calls from within the standard software nor do they affect the validity of call interfaces. You do not have to register Business Add-Ins in SSCR.
The Business Add-In enhancement technique differentiates between enhancements that can only be implemented once and enhancements that can be used actively by any number of customers at the same time. In addition, Business Add-Ins can be defined according to filter values. This allows you to differentiate between Add-In implementations using the filter Country or other criteria.
The enhancement technique is set up in such a way that it is possible to define interfaces for ABAP soure code, screens, GUI interfaces, and tables. These allow customers to include their own enhancements in the standard. A single Business Add-In contains all of the interfaces necessary to implement a specific task.
The actual program code is enhanced using ABAP Objects.
Have a look at http://help.sap.com/saphelp_nw04/helpdata/en/04/f3683c05ea4464e10000000a114084/
I hope it helps.
Best Regards,
Vibha
*Please mark all the helpful answers
‎2006 Nov 14 9:20 AM
Read this link:
http://help.sap.com/saphelp_47x200/helpdata/en/31/09a02f0b848245b139d1c208a5b735/frameset.htm
Regards,
ravi
‎2006 Nov 14 9:21 AM
The R/3 enhancement concept allows you to add your own functionality to SAPs 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. Thus Enhancements allow you to add additional functions to the SAP standard.
If you want to enhance the functionality of your SAP System, you should take advantage of the exits available in standard R/3 applications. There are two main reasons why you should use exits rather than modifying SAP software yourself. Add-ons attached to exits have the advantage that:
-> They do not affect standard SAP source code
-> They do not affect software updates
http://www.erpgenie.com/sap/abap/code/abap26.htm
which gives the list of exits for a tcode
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec079f5db911d295ae0000e82de14a/frameset.htm
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sapgenie.com/abap/code/abap26.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
http://www.easymarketplace.de/userexit.php
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sappoint.com/abap/userexit.pdfUser-Exit
http://www.planetsap.com/userexit_main_page.htm
Business add-ins are enhancements to the standard version of the system. They can be inserted into the SAP System to accommodate user requirements too specific to be included in the standard delivery. Since specific industries often require special functions, SAP allows you to predefine these points in your software.
SAP guarantees the upward compatibility of all Business Add-In interfaces. Release upgrades do not affect enhancement calls from within the standard software nor do they affect the validity of call interfaces. You do not have to register Business Add-Ins in SSCR.
The Business Add-In enhancement technique differentiates between enhancements that can only be implemented once and enhancements that can be used actively by any number of customers at the same time. In addition, Business Add-Ins can be defined according to filter values. This allows you to differentiate between Add-In implementations using the filter Country or other criteria.
The enhancement technique is set up in such a way that it is possible to define interfaces for ABAP soure code, screens, GUI interfaces, and tables. These allow customers to include their own enhancements in the standard. A single Business Add-In contains all of the interfaces necessary to implement a specific task.
The actual program code is enhanced using ABAP Objects.
Have a look at http://help.sap.com/saphelp_nw04/helpdata/en/04/f3683c05ea4464e10000000a114084/
I hope it helps.
Best Regards,
Vibha
*Please mark all the helpful answers
‎2006 Nov 16 6:48 AM
Hi vijaya durga ,
These are the different provisions given by SAP to solve the basic purpose ...
user friendly & acheiving the business requirement / need
<b>Customizing:</b>
As the word is the work ... you will customize the standard according to your business need ... eg ... SAP will deliver some standard functionality with some points which you can switch on/off or even add your own functionality to the standard ....
The main transaction from where the customizings are done is <b>"SPRO"</b> popularly refered to as IMG (Implementation guide) .... here you have documents too which will assist you in performing the customizing
<b>Personalisation :</b>
This means you personalise the GUI of any transaction according to the user specification ... here you can switch on /off screen fields, tabs and even the entire screen itself .... you can even set some defaults (like date field always to populate with todays date etc) all these things are personalisation ...
the major transaction used is ...<b> SHD0</b>
<b>Modification :</b>
If the SAP standard doesnt provide you any add-on points but you want to change the business logic explicity by disturbing the code of the standard then you are modifying the code .... this is called modification ....
<b>Note :</b> Its not a good process to do lots of modifications.... prior doing any modification it is better to confirm that there is NO provision given in the standard to add your buisness logic on to it ...
Hope this helps you !
Cheers
Kripa Rangachari!
Message was edited by:
Kripa Rangachari