About enhancement

hello,
Can any body explain the type of exits available in sap.
Thanks.

Hi papa,
Go through this info.
What is User Exits and Customer Exits?
Difference between user exits & customer exits:
User exit - A user exit is a three character code that instructs the
system to access a program during system processing.
SXX: S is for standard exits that are delivered by SAP. XX
represents the 2-digit exit number.
UXX: U is for user exits that are defined by the user. XX
represents the 2-digit exit number
Customer exit - The R/3 enhancement concept allows you to add your
own functionality to SAP's 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. *-- Mani
The following document is about exits in SAP :-
The R/3 enhancement concept allows you to add your own functionality
to SAP's standard business applications without having to modify the
original applications.
SAP creates user 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.
Types of Exits
There are several different types of user 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 item's 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 screen's
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 pull down 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 `001'.
Field Exits
Field exits allow you to create your own programming logic for any
data element in the Dictionary. You can use this logic to carry out
checks, conversions, or business-related processing for any screen
field. Example: The data element BBBNR identifies a company's
international location number. You might want to set up your R/3
System so that all international location numbers are larger than
100.
The field exit concept lets you create a special function module
that contains this logic.
You assign the special function module to the data element BBBNR.
You then assign the module to any programs and screens in which
users can add new international location numbers. When you activate
your field exit, the system automatically triggers your special
routine whenever a user enters a company location number.
In 4.6c, you can use "RSMODPRF" program to create field exits.
An example of a user exits :-
MODULE user_exit_0001 INPUT
CASE okcode.
WHEN 'BACK OR EXIT'.
CASE sy-dynnr.
WHEN '100'.
SET SCREEN 0.
LEAVE SCREEN.
WHEN '200'.
Note that you can write any code that satisfy your
needs. ****
But in this case, this was wrote as a sample code for reference
sake. ****
And you can test
it.
SET SCREEN 100.
LEAVE SCREEN.
ENDCASE.
ENDCASE.
Rewards some points if it is helpful.
Rgds,
P.Naganjana Reddy

Similar Messages

  • Please tell me about Enhancement Techniques used in SAP Other then BADI/Usr

    Hi Experts .
    Please guide me about Enhancement Techniques used in SAP apart from BADI/User-Exit .
    1.) what is set and how to create it ?
    2.) What is formula is SAP and How to set it for Enhancement Pupose .
    3.) What is BTE (Buisness Transection Events) ? How to create it for Enhancement Pupose ?
    Please Elabarate the reply with step by step procedure .
    Thanx .
    Regards : Rajneesh

    Hi Raj,
                  Check these links
       help.sap.com/saphelp_nw04/helpdata/en/eb/3e7ceb940e11d295df0000e82de14a/content.htm
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/207835fb-0a01-0010-34b4-fef1240ba9b7
    Regards,
    Sana.
    reward for useful answers..

  • Please tell me about Enhancement Technique like BTE , SET and Formula

    Hi Experts .
    Please guide me about Enhancement Techniques used in SAP apart from BADI/User-Exit .
    1.) what is set and how to create it ?
    2.) What is formula is SAP and How to set it for Enhancement Pupose .
    3.) What is BTE (Buisness Transection Events) ? How to create it for Enhancement Pupose ?
    Please Elabarate the reply with step by step procedure .
    Thanx .
    Regards : Rajneesh

    Hi rajneesh mittal  ,
    Business Transaction Events
    Business Transaction Events (Open FI) The Open FI enhancement technique was developed in the Financial Accounting component. Open FI is based upon the following principles: Application developers must define their interface in a function module, an assignment table is read in the accompanying (generated) code, and the customer modules assigned are called dynamically. This technique differentiates between enhancements that are only allowed to have one implementation and enhancements that can call multiple implementations in any sequence desired. Both industry-specific and country-specific enhancements may be defined.
    SAP business transaction events are one type of customer enhancements provided by SAP! We can access the business transaction events using FIBF.Next we have to find the process interface for duplicate invoice check!
    check this blog for details on SAP business transaction events
    Business Transaction Events
    Business Transaction Events
    http://fuller.mit.edu/user_exits/business_transaction_event.htm
    FI Enhancement Technique – How-To-Guide on the Usage of Business Transaction Events (BTE)
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/207835fb-0a01-0010-34b4-fef1240ba9b7
    Creation of Events via Business Transaction Events
    http://help.sap.com/saphelp_nw04/helpdata/en/3b/7f3e8be57c11d1951f0000e82dec10/content.htm
    In SAP R/3 you must activate the business transaction events (BTEs) for Availability Check Using SAP R/3. To set this indicator in SAP R/3:........
    http://help.sap.com/saphelp_crm40/helpdata/en/b6/de3efc6bbcdc4b948d466857a10323/content.htm
    cheers!
    gyanaraj
    ****Pls reward points if u find this helpful

  • About enhancements

    hi friends,
    plz explain me about enhancements what you did in implementation project with examples?
    thanks
    Sudhakar

    In our project, for example we want to check if the customer account group is 'Z001', user should enter field KNVV-KTGRD with Z1 and if account group is 'Z002', KNVV-KTGRD should have Z2.
    What we done before is:
    1. in SMOD t-code, use enhancement SAPMF02D,
    2. then in function :EXIT_SAPMF02D_001, create new include, for example: ZXF04U01
    3. put the validation program code, in that include (ask your ABAPer to add the program)
    4. activate the enhancement
    5. if needed, you can put your enhancement in CMOD
    Best regards,
    Gunadi

  • Abap query about enhancement set

    How do we use an enhancement set?Where we can maintain a particular enhancement set to a client?
    *How do we know about an activated enhancement set?
    Moderator message: please search for available information/documentation before asking, this is not a training forum.
    locked by: Thomas Zloch on Oct 5, 2010 5:32 PM

    Hi,
    In PBO code this way :
    MODULE f4_scr OUTPUT.
      REFRESH g_list1.
      g_name1 = c_status.
      g_value_1-key = c_to_be_sub.
      g_value_1-text = c_to_be_sub.
      APPEND g_value_1 TO g_list1.
      g_value_1-key = c_sub.
      g_value_1-text = c_sub.
      APPEND g_value_1 TO g_list1.
      g_value_1-key = c_chg_needed.
      g_value_1-text = c_chg_needed.
      APPEND g_value_1 TO g_list1.
      g_value_1-key = c_app.
      g_value_1-text = c_app.
      APPEND g_value_1 TO g_list1.
      IF NOT g_list1 IS INITIAL.
        CALL FUNCTION 'VRM_SET_VALUES'
          EXPORTING
            id     = g_name1
            values = g_list1.
      ENDIF.
    ENDMODULE.                 " F4_SCR  OUTPUT
    And in PAI :
    MODULE user_command_9000 INPUT.
    * function module to get the list box values.
      g_name1 = c_status.
      CALL FUNCTION 'VRM_GET_VALUES'
        EXPORTING
          id           = g_name1
        IMPORTING
          values       = g_list1
        EXCEPTIONS
          id_not_found = 1
          OTHERS       = 2.
      IF sy-subrc <> 0.
        MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
      ENDIF.
      READ TABLE g_list1 INTO g_wa_list WITH KEY key = g_status.
      IF sy-subrc EQ 0.
        g_status = g_wa_list-text.
      ENDIF.
    ENDMODULE.                 " USER_COMMAND_9000  INPUT
    Hope this helps.
    thanx,
    dhanashri.
    Edited by: Dhanashri Pawar on Aug 21, 2008 11:36 AM

  • About Enhancement Options:CrossOriginResourceSharingRequestorsForByDGroupware

    Hi , experts
        Who know the enhancement options clearly in cloud application studio.
    I meet some trouble  about enhancemnet option:CrossOriginResourceSharingRequestorsForByDGroupware,
    I want to get some help from you . Could somebody tell me what this use for and how to use it?
    what scenarios can  call this enhancement and  which work center can trigger it?
        Please provide me some useful information and clues. Thank you !

    Hi,
    For Details Check this link-
    http://www.sap.com/solutions/business-suite/erp/enhancement_packages.epx
    http://download.sap.com/download.epd?context=AF47734897DE1CB5E0BE0AFA9A5608AAF867BD6437451DABD4596BF148080AF36D76338812A0D980012B441399C4E2C3E87CEF925C8EA197

  • About Enhancement Packages

    Dear gurus,
    I am trying to learn about EHP ( Enhancement packages ), I did understand few things like, EHP are available in SAP market place. But after down loading EHPs. How exactly is the coding is done in the EHP is not at at all clear to me can any one please explain this.........
    Thanks & Regards,
    Rama.

    Hi,
    For Details Check this link-
    http://www.sap.com/solutions/business-suite/erp/enhancement_packages.epx
    http://download.sap.com/download.epd?context=AF47734897DE1CB5E0BE0AFA9A5608AAF867BD6437451DABD4596BF148080AF36D76338812A0D980012B441399C4E2C3E87CEF925C8EA197

  • Question about "Enhanced for loop"

    public class NewLoopTest{
         public NewLoopTest(){
              int result=0;                      
              int[] a=new int[20];           
              for(int i=0;i<a.length;i++){
                   a=i++;
              for(int i:a){  
    System.out.println("i="+i+";"+"a["+i+"]="+a[i]+";result="+result+"+"+i+"="+(result+i));
                   result+=i;           
              System.out.println("-------------");
              result=0;
              for(int i=0;i<a.length;i++){
                   System.out.println("i="+i+";"+"a["+i+"]="+a[i]+";result="+result+"+"+i+"="+(result+i));
                   result+=i;
    This code counts sum of the elements of a array.
    At first I use the enhanced for loop and at second I use the traditional for.
    Enhanced for loop in sdk1.5 returns only even elements of array, am I right?

    Enhanced for loop in sdk1.5 returns only even
    elements of array, am I right?No. It covers them all.
    The i in the enhanced for loop is not the index. It's the element at the current index. You don't have access to the index in the new loop because you don't need it.
    for (int item : arr) {
        System.out.println(item);
    // is equivalent to
    for (int ix = 0; ix < arr.length; ix++) {
        int item = aa[ix];
        System.out.println(item);
    }The i in your new loop is the same as a [ i ] in the old loop.

  • How to get information about enhancements

    HI,
    I am new to ABAP.
    Is there  any easy way to see the enhancements/exits.
    Moderator message : Read forum rules before posting. This is an FAQ and discussed many times in forums, search for avaialble information. Thread locked.
    Edited by: Vinod Kumar on May 27, 2011 10:44 AM

    hi, you can use the sys_context function, like this:
    select sys_context('userenv','current_user'),
         sys_context('userenv','os_user'),
         sys_context('userenv','host'),
         sys_context('userenv','ip_address'),
         sys_context('userenv','instance'),
         sys_context('userenv','sessionid'),
         sys_context('userenv','terminal')
    from dual;
    Is this what you 're looking for?

  • Need information about Enhancement packages

    Hi all,
    We are planning to implement Enhancement Packages in our Solution Manager server. The primary purpose will be to generate reports for the BI and APO systems configured in the Solman 7.0 system-System status and health check reports.
    Can anyone help me with some information and how beneficial EHP will be for reporting and any other better ways to utilize that?
    Thanks,
    Anupama

    Hi Anupama,
    Hope this is regarding EHP1 for solman?.
    1) For Health Checks, you already have EWA- this forms the primary Report for your analysis of the system and by default you can get EWA for ABAP-(little configurations needed). But for getting EWA-Java you need to configure Diagnostics. Diagnostics will also help in root cause analysis,in case of any issue - EHP1 has the guided procedure for the same. Also Live cache- workload analysis is also possible.
    2) System Status - Once the sytem monitoring and Alerting mechanism is configured, you can get the status of the system, Errors,
    job failures etc. Its an enhancement of CCMS.
    feel free to revert for queries.
    Thanks,
    Jagan

  • Any info about 'Enhancing the Quality of ABAP Development'

    Hi,
    There is a new SAPPRESS book 'Enhancing the Quality of ABAP Development', which looks interesting.
    There is some info here:
    http://www.sap-press.com/product.cfm?account=&product=H975
    Does anybody have it?
    Is it worth to buy?
    Thanks,
    Peter

    If anybody is interested in, there is a sample available here:
    http://www.sap-press.de/download/dateien/637/sappress_enhancing_quality_abap.pdf
    Peter

  • Brief about enhancements and user exits

    hai,
    can any  one tell me what are enhancements and user exits in sap sd,
    their  signifcance & configuration
    regards
    sriram

    hi,
    an example of user exit
    In case of Inbound DELINS IDOC (830 type) once there was a requirement of taking the “Target *** Qty required” and the “Target *** Date” for a specific customer who was not sending “*** Qty Received” by him.
    So for that specific customer we used the search term and added the same in the “Data 4” field of the IDOC under segment E1EDK09.
    There was one user exit available in IDOC_INPUT_DELINS_START Function module of SAP. We triggered this logic by the search term of customer and reached the user exit where we had made some code changes. (User Exits are used to make code changes when we are running standard programs or reports or function modules). With this we were able to reach the desired point of calculating “*** Issued” and then find out the difference from “Target *** Qty” and get “*** Qty Received” for the scheduling agreement. We did not copy the standard function module into Z . Instead the same was done using a user exit.
    <b>User exits in SD</b>
    Menu Path:
    SPRO- IMG- SD- System Modification- User Exists. User Exists are available in SD for the following processes:
    • User exits for price determination
    • User exits for partner determination
    • User exits for credit check & risk management
    • User exits in sales:
    o User exits in sales doc processing
    o User exits for contract processing
    o User exits for product allocation processing
    o User exits for availability checking
    o User exits for component supply processing
    o User exits for product selection
    o User exits for billing plan
    • User exits for shipping
    • User exits for transportation
    • User exits for billing
    • User exits for general billing interface
    • User exits for sales support
    • User exits for lists.
    The topic of user exits is a subject that concerns ABAP development & extensive experience in ABAP is required to understand and use the user exits.
    A customer user exit is essentially a function module using a unique naming convention, in which set import and export parameters are defined to limit the data that can be manipulated. This is to protect certain data from being changed. This function module is attached to an enhancement that may contain other function modules. A user exit should only be used if the possibilities for customizing or application-specific user exits are inadequate.
    NEW FIELDS IN PRICING:
    To use a field in pricing, one creates a cond table. This cond table is created using the allowed fields from the field catalog. Should the fields one requires not be included in the list of allowed fields, one can add the fields from the list of available fields. However, one may find that a new field may not be in the list of available fields. For this reason, one must create new fields for pricing. The document & item data in SD is stored in data tables such as VBAK & VBAP (for the order transaction). Many of the fields from these tables are available in the field catalog.
    The field catalog is a structure (KOMG) that consists of 2 tables (KOMK & KOMP). These tables contain the header & item data for pricing respectively. They are called KOM”x” because they are communications structures used to communicate the transaction data with the pricing procedure. Table KOMG contains the field KOMK & KOMP.
    If you require a field that is not in KOMG, it means that it is not in KOMK or KOMP. This means that the field you require cannot be used in pricing because there is no communication of this field from the transaction to the pricing procedure via the communication structures.
    To use a field not defined in the field catalog, you need to add this field to KOMK or KOMP structures, and then write the ABAP code to transfer the data in the field from the transaction tables to the communication structure. Follow these steps:
    Create the field in the KOMK (header data) & KOMP (item data) tables using the standard includes provided for this requirement.
    Write the code in the user exit to read the transaction data & transfer it to the KOM”x” structures.
    Menu Path:
    SPRO- IMG- SD- System Modification- Create New Fields (using the cond tech)- New fields for Pricing.
    Adding the field to KOMK & KOMP:
    This process requires some knowledge of the ABAP dictionary & how to use the ABAP dictionary to create & change fields & tables. If the field is from the header table (for e.g. the order table: VBAK), you will need to add it to the include table KOMKAZ in the table KOMK. If the field is from the item table (for e.g. the order item table: VBAP), you will need to add it to the include table KOMPAZ in table KOMP.
    Let’s say you need to use the ‘base material’ to define a price & the base material is no in the pricing field catalog. The base material is a field on the MMR basic data screen & is defined as MARA-WRKST. Since this relates to the material, it is at the item level, so you would add the field to KOMKAZ include table.
    • When you add a field to these tables, it must start with ‘ZZ’. Therefore, the field you add would be ZZWRKST. In ABAP, when you add the field, use the same domain as in the field in the original table MARA-WRKST.
    • After adding the field, generate the structure KOMP. This field is not available in the field catalog & can be used in condition tables.
    Menu Path:
    SPRO- IMG- SD- System Modification- User Exists. User Exists are available in SD for the following processes:
    • User exits for price determination
    • User exits for partner determination
    • User exits for credit check & risk management
    • User exits in sales:
    o User exits in sales doc processing
    o User exits for contract processing
    o User exits for product allocation processing
    o User exits for availability checking
    o User exits for component supply processing
    o User exits for product selection
    o User exits for billing plan
    • User exits for shipping
    • User exits for transportation
    • User exits for billing
    • User exits for general billing interface
    • User exits for sales support
    • User exits for lists.
    The topic of user exits is a subject that concerns ABAP development & extensive experience in ABAP is required to understand and use the user exits.
    A customer user exit is essentially a function module using a unique naming convention, in which set import and export parameters are defined to limit the data that can be manipulated. This is to protect certain data from being changed. This function module is attached to an enhancement that may contain other function modules. A user exit should only be used if the possibilities for customizing or application-specific user exits are inadequate.
    NEW FIELDS IN PRICING:
    To use a field in pricing, one creates a cond table. This cond table is created using the allowed fields from the field catalog. Should the fields one requires not be included in the list of allowed fields, one can add the fields from the list of available fields. However, one may find that a new field may not be in the list of available fields. For this reason, one must create new fields for pricing. The document & item data in SD is stored in data tables such as VBAK & VBAP (for the order transaction). Many of the fields from these tables are available in the field catalog.
    The field catalog is a structure (KOMG) that consists of 2 tables (KOMK & KOMP). These tables contain the header & item data for pricing respectively. They are called KOM”x” because they are communications structures used to communicate the transaction data with the pricing procedure. Table KOMG contains the field KOMK & KOMP.
    If you require a field that is not in KOMG, it means that it is not in KOMK or KOMP. This means that the field you require cannot be used in pricing because there is no communication of this field from the transaction to the pricing procedure via the communication structures.
    To use a field not defined in the field catalog, you need to add this field to KOMK or KOMP structures, and then write the ABAP code to transfer the data in the field from the transaction tables to the communication structure. Follow these steps:
    Create the field in the KOMK (header data) & KOMP (item data) tables using the standard includes provided for this requirement.
    Write the code in the user exit to read the transaction data & transfer it to the KOM”x” structures.
    Menu Path:
    SPRO- IMG- SD- System Modification- Create New Fields (using the cond tech)- New fields for Pricing.
    Adding the field to KOMK & KOMP:
    This process requires some knowledge of the ABAP dictionary & how to use the ABAP dictionary to create & change fields & tables. If the field is from the header table (for e.g. the order table: VBAK), you will need to add it to the include table KOMKAZ in the table KOMK. If the field is from the item table (for e.g. the order item table: VBAP), you will need to add it to the include table KOMPAZ in table KOMP.
    Let’s say you need to use the ‘base material’ to define a price & the base material is no in the pricing field catalog. The base material is a field on the MMR basic data screen & is defined as MARA-WRKST. Since this relates to the material, it is at the item level, so you would add the field to KOMKAZ include table.
    • When you add a field to these tables, it must start with ‘ZZ’. Therefore, the field you add would be ZZWRKST. In ABAP, when you add the field, use the same domain as in the field in the original table MARA-WRKST.
    • After adding the field, generate the structure KOMP. This field is not available in the field catalog & can be used in condition tables.
    Pl reward if helpful.
    Thanks
    Sadhu Kishore

  • Question about enhancement

    Hi All,
    Anybody konw how can i create the implementation using se19?
    or somebody have notes talking about that?
    Regards,
    Luke
    Moderator message: please (re)search yourself before asking.
    locked by: Thomas Zloch on Aug 5, 2010 11:34 AM

    Hello,
    I don't think SAP gives you any message like that.
    I believe that this is more related to FI period.
    When you cancel SD billing document, by default you cancel it with the date the billing document is created.
    However, FI period is closed between the time you created billing document and do cancellation of the billing document, your VF11 works yet no accounting document created.
    The error message you get is 'Posting period xxx year is not open'.
    hope it helps.

  • About enhancement point for va41

    hai ,
    plz help me to find out userexit point .
    i want make make  little validation code for the additional  data tab A in tcode va41 in sap

    Hi,
    Following are the Exits available for va41 tcode
    Exit name           Short text
    SDTRM001      Reschedule schedule lines without a new ATP check
    V45A0001       Determine alternative materials for product selection
    V45A0002       Predefine sold-to party in sales document
    V45A0003       Collector for customer function modulpool MV45A
    V45A0004       Copy packing proposal
    V45E0001       Update the purchase order from the sales order
    V45E0002       Data transfer in procurement elements (PRreq., assembly)
    V45L0001       SD component supplier processing (customer enhancements)
    V45P0001       SD customer function for cross-company code sales
    V45S0001       Update sales document from configuration
    V45S0003       MRP-relevance for incomplete configuration
    V45S0004       Effectivity type in sales order
    V45W0001      SD Service Management: Forward Contract Data to Item
    V46H0001       SD Customer functions for resource-related billing
    V60F0001       SD Billing plan (customer enhancement) diff. to billing plan
    Regards,
    Aravinth

  • About ENHANCEMENT and ENDENHANCEMENT

    Hi all SAP GURUS,
        In SAP 6.0 I found  some tline like
    <b>enhancemnet-point ......
    enhancement
    endenhancement</b>
    how can we work with this enhancements. I think it is new concept in sap6.0 for enhancemnts. At the time of implementing this enhancement it is showing so many static and dynamic enhancement implementations, what are these static and dynamic enhancements.

    Hi siri,
    <u><b>Enhancement Implementations</b></u> :
    Definition
    The enhancement implementations manage the enhancements of the enhancement options, both explicitly and implicitly.
    In the same way that we differentiate between enhancement options and their management in the case of enhancement spots, we also differentiate between the actual enhancement and its management in the case of enhancement implementations.
    Use
    An enhancement is managed by assigning one or more simple enhancement implementations to an enhancement spot of a concrete enhancement spot element definition. Conversely, every simple enhancement implementation belongs to exactly one enhancement spot. A simple enhancement implementation can have one or more enhancement implementation elements, which are assigned to the enhancement spot element definitions of the enhancement spot. A simple enhancement implementation must be assigned to at least one composite enhancement implementation:
    Simple and composite enhancement implementations are Repository objects that form a tree-like structure, where the leaves and branches represent simple and composite enhancement implementations respectively.
    Therefore, to implement the actual enhancement, one or more enhancement implementation elements are assigned to an enhancement spot element definition of an explicit or implicit enhancement option.
    You can assign source code plug-ins, defined between ENHANCEMENT and ENDENHANCEMENT in an ABAP program, to an enhancement option defined using ENHANCEMENT-POINT. These source code plug-ins are inserted into the code unchanged if the switch is in the relevant position.
    Enhancement implementations are processed with the Enhancement Builder tool, which is integrated in the ABAP Workbench. The Enhancement Builder’s hierarchical display of the enhancement implementations in a system shows the enhancements made in a system.
    An enhancement implementation describes the enhancement of a Repository object at one or more enhancement options. An enhancement implementation element always belongs to exactly one enhancement option. However, several enhancement implementation elements can be assigned to an enhancement option. The enhancement implementation element contains the actual enhancement – for example, a source code plug-in contains the source code to be added. However, an enhancement implementation element contains no information concerning at which positions of a Repository object the enhancement options were created. Composite enhancement implementations are used for the semantic grouping of simple enhancement implementations. A composite enhancement implementation contains either one or more simple enhancement implementations and/or one or more composite enhancement implementations of the relevant type. You can use composite enhancement implementations to combine simple enhancement implementations into meaningful units.
    The position of a Switch Framework switch assigned to the package of an enhancement implementation specifies whether or not an enhancement is taken into account in a system.
    <u><b>Creating Source Code Plug-Ins</b></u> :
    Procedure
           1.      Call the Enhancement Builder from the ABAP Editor using forward navigation.
           2.      Create an enhancement implementation for an implicit or explicit enhancement option. For more information, see Creating an Enhancement Implementation.
    An empty source code plug-in is automatically created. It has a unique ID and is displayed in the ABAP Editor below the enhancement option as follows:
    ENHANCEMENT id.
    <b>ENDENHANCEMENT</b>.
           3.      Implement the enhancement between the ENHANCEMENT and ENDENHANCEMENT lines.
    A source code plug-in is assigned to exactly one enhancement option. An enhancement option can be enhanced through several source code plug-ins of an enhancement implementation and through several enhancement implementations.
    Although source code plug-ins are displayed in the same source code as the respective enhancement options, they are actually stored in other Include programs managed by the Enhancement Builder.
    http://help.sap.com/search/highlightContent.jsp;
    http://help.sap.com/search/highlightContent.jsp.
    reward points , if useful
    regards,
    Bhaskar

Maybe you are looking for