Link to Content's target Space: Applies to: SAP ABAP, my SAP ECC 6.0, for more information, visit the ABAP homepage. Summary The enhancement concept allows you to add your own functionality to SAP's standard business applications without having to modify the original applications. To modify the standard SAP behavior as per customer requirements, we can use enhancement framework. This document explains about User exits and Customer Exits. Author(s): Tutun Nandy Company: Infosys Technology Ltd Created on: 20 May 2010 Author(s) Bio Tutun Nandy is working with Infosys Technology Ltd since 2008. His expertise includes SAP ABAP. Table of Contents 1) Overview of this document.... 2) User Exit with example.... Funcion de la vista parcial del encefalo humano. LSMW, ALE, BDC, IDOCs, BAPI's, Uploading Data Object to SAP. Operating SystemsBS 2000. Combined with automatic upload programs for the modification of Product hierarchies, material master, internal orders and pricing conditions. 3) Customer Exit..... 4) Types of Customer Exits.... 5) Function Module exits.... 6) Screen Exist..... 7) Menu Exits..... ![]() 8) Methods to find out customer Exits... 9) CMOD and SMOD transactions... Overview of this document The enhancement concept allows you to add your own functionality to SAP's standard business applications without having to modify the original applications. To modify the standard SAP behavior as per customer requirements, we can use enhancement framework. There are different ways to implement custom functionality in the SAP standard code. Ex: User exits, customer exits, BADI etc. This document explains about User exits and Customer Exits. User exits These are implemented in the form of subroutines and hence are also known as FORM EXITs. The user exits are generally collected in includes and attached to the standard program by the SAP. User exits are a type of system enhancement that was originally developed for the R/3 SD (Sales and distribution) module. User-exits are empty subroutines that SAP Developers have provided for you. You can fill them with your own source code. Technically this is a modification. All User exits start with the word USEREXIT_. FORM USEREXIT_XXXX. INCLUDE ZZUSEREXIT. User exits can be found in the following ways: Go to Object Navigator (SE80), select Package and put VMOD (Application development R/3 SD customer modification) and press enter. You will find all the includes for user exits in SD. You will get User exits for Sales order, Delivery, Billing, Pricing etc. Most of the time documentation is maintained for each subroutine which helps developer for better understanding of the subroutine. Select the subroutine according to the requirement and start coding within the subroutine. Examples: - In User exits MV45AFZZ(Sales Order Exit), we have subroutine USEREXIT_PRICING_PREPARE_TKOMK USEREXIT_PRICING_PREPARE_TKOMP This user exit can be used to move additional fields into the communication table which is used for pricing. TKOMK for header fields and TKOMG for item fields. The fields which are not in either of the two tables KOMK and KOMP cannot be used in pricing. Zvendpgm (Vendor Program), zpricegrp (Price Group), kvgr5(Airport Code) fields value moving from VBAP to KOMP table. - In User exits MV50AFZ1(Delivery Exit), you have subroutine USEREXIT_SAVE_DOCUMENT_PREPARE This user exit can be used for changes or checks, before a document is saved. Customer exits SAP creates customer exits for specific programs, screens, and menus within standard 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. Customer exits are nothing but a include in customer name space will be provided in the function module which starts with CALL CUSTOMER. You can fill them with your own source code. Technically this is an enhancement. User exits generally refer to SD module while customer exits refer to all modules like MM, SD, PP, FICO etc. Advantage: - They do not affect standard SAP source code - They do not affect software updates Disadvantage: - Customer exits are not available for all programs and screens found in the SAP System. You can only use customer exits if they already exist in the SAP System. Types of Customer Exits 1. Function Module exits 2. Screen exits 3. Menu exits 1. Function Module exits Function module exits are exits developed by SAP. The exit is implemented as a call to a function module. The code for the function module is written by the developer. You are not writing the code directly in the function module, but in the include that is implemented in the function module.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |