Skip to Content
author's profile photo Former Member
Former Member

code modification...urgent

hi experts,

i am new to enhancement and modifications.

can anybody tell me the term modification and code modification one and the

same?or different?if so,

2.what is code modification? do u do code modification?

4.adv. and disadv. of code modifications?

i appreciate if u provide links also.

thanks in advance.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Feb 01, 2008 at 04:35 AM


    Explicit Enhancement Options

    There are two types of explicit enhancement options: Source code enhancements with source code plug-ins and BAdIs:

    • Explicit enhancement options of the source code enhancement type allow you to insert source code plug-ins. These are lines of code that are executed if the source code enhancement option is inserted in the code with the Enhancement Point command. Source code enhancement options with the Enhancement Section command behave the same, except that the source code plug-in replaces the section in the original code. Therefore, you are not only able to enhance the original code, but can also flag specific code sections (as enhancement sections) so that other developers can replace these sections with other code without making modifications.

    • Business Add-Ins (BAdIs) are “hangers” for object plug-ins. A BAdI definition comprises an interface with methods. BAdIs are enhanced by classes that implement the BAdI interface. If you instantiate a BAdI and then call its methods, you can, among other things, specify which method implementations are to be carried out on the basis of filter values. In other words, a BAdI method call is a dynamic method call with a specified interface, for which it is not determined until runtime which method implementations are to take place.

    In the case of source code enhancements, the definition and call coincide. You define BAdIs once in the BAdI Builder and can then call them at different points in the various compilation units.

    Implicit Enhancement Options

    Implicit enhancement options are fixed points in compilation units – that is, points that remain intact even if the code is changed. This is important for the following reason: If the location of an enhancement is moved, you have to check manually after an upgrade whether the enhancement is still at the correct point and replace it if necessary. The following are implicit enhancement options at which enhancements can always be inserted:

    • You can always insert source code plug-ins before the first and the after the last line of includes, methods, reports, and function modules.

    • You can always add further optional parameters to function modules.

    • For global classes, there are different permanent, implicit options for enhancements: You can insert additional attributes or methods, and you can add optional parameters to existing methods

    Customer-Specific Modification and Enhancement Possibilities


    The following documentation provides an overview of the customer-specific modification and enhancement possibilities in the IS-H System. Note that to implement enhancements, you require ABAP programming knowledge.


    The IS-H system provides the following technical possibilities for customer-specific modifications and enhancements

    Business Add-Ins (BAdIs)

    If default code (standard procedure defined by SAP) exists for the BAdI, please note it will be overwritten when you implement the BAdI. You can, if required, re-use the default code in your implementation.

    As of SAP NetWeaver 2004, the enhancement concept of the ABAP Workbench (Enhancement Framework) is available for BAdIs. Note that SAP Patient Management contains BAdIs that use the Enhancement Framework as well as the classic BAdIs.

    Customer Exits (transaction SMOD)

    If SAP delivers sample code for the customer exit, you can access it when implementing the exit by choosing Goto ® Sample Code. You can re-use the sample code using Copy&Paste

    User Exits from the IS-H Implementation Guide: Basic Settings ® Configuration/Systems/Events ® Display SAP User Exits.

    To implement the IS-H user exits, copy the function module delivered by SAP into a customer-specific function group. The name of the function module delivered by SAP is specified in the table you call in the IS-H Implementation Guide by choosing the path specified to the left here.

    Once you’ve copied the source code, you can modify this copy to meet your needs. Note that you must not modify the interface of your own function module.

    Now enter the name you’ve chosen for the function module in the customer table. You access this table by choosing Basic Settings ® Configuration/Systems/Events ® Configure Customer User Exits.

    If it is helpful rewards points.



    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Feb 01, 2008 at 05:45 AM

    Enhancements to the Standard

    Enhancements represent potential customer requirements that have not been developed in the standard. Instead, the standard provides for further development of such exits at the customer site, using logic specific to the customer. Upward compatibility is assured since SAP guarantees that the call of an enhancement from the standard software and the calling interface will remain valid in future releases.

    You can make enhancements to the standard using customer exits.

    From Release 4.6A, you can implement enhancements for the system standard using a new technique called Business Add-Ins

    Modifying the Standard

    Before you modify your system or develop your own solution, make sure that your requirements cannot be fulfilled by either Customizing or Personalization, or by the exits or business add-ins provided in the system.

    Before making modifications to the standard, refer to the section on the Modification Assistant

    For information on modifying SAP tables, consult the portion of the ABAP Dictionary documentation called Making Changes to Tables . You can also create append structures for tables and structures with the Modification Assistant (see Modifying Tables and Structures ).

    SSCR (SAP Software Change Registration) is a procedure for registering all modifications to SAP source code and SAP Dictionary objects. For more information on this subject, see the section on the SAP Software Change Registration Procedure (SSCR) .

    You should also consult the sections General development organization


    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.