Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>SAP has provided various customer plug-ins in order to enable customers to modify and adapt standard code:</p> <ul> <li><p>User exits (Transactions SMOD, CMOD and SE81). <a href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/208811b0-00b2-2910-c5ac-dd2c7c50c8e8" rel="nofollow noreferrer">This article</a> covers user exists in greater detail. </p></li> <li><p>BADI's (Business Add-inns, Transaction SE18). This is an Object Oriented(ish) way of extending standard functionality. <a href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3001894b-b1fb-2910-77ba-e80b6f2053b7" rel="nofollow noreferrer">This article</a> covers BADI's in greater detail</p></li> <li><p>Explicit Enhancement Points (Netweaver 7.0 and later only, Transaction SE80) are placeholders in the SAP standard code where programmers can add their own code. <a href="http://help.sap.com/saphelp_nw04s/helpdata/en/91/f1e540f8648431e10000000a1550b0/frameset.htm" rel="nofollow noreferrer">Read more here</a> about enhancement spots.</p></li> </ul> <p>All these options require SAP to have anticipated the need to enhance the code and provide the hooks for enhancements. If they are there it is a great way to maintain SAP standard code without voiding the support agreement with SAP.</p> <p>The following 2 ways <em>do not</em> require SAP to do anything:</p> <ul> <li><p>Implicit Enhancement Spots (Netweaver 7.0 and later only, Transaction SE80). Works the same as Explicit Enhancement Spots, but exists at the start and end of <em>ALL</em> functions, forms, methods, structures etc. The menu path Edit->Enhancement Operations->Show Implicit Enhancement Points will make these visible. The beauty of Implicit Enhancement Spots is that <em>it is still supported by SAP</em>.</p></li> <li><p>Program Repairs: In SE80 hit the change icon and SAP will ask for a repair key - this can be requested from SAP at <a href="http://service.sap.com" rel="nofollow noreferrer">http://service.sap.com</a> (usually by the Basis guys). Once you've provided the key you can edit the code normally (or with modification assistant if it is turned on). <em>Repaired objects are not supported by SAP</em> </p></li> </ul> <p>Edit: As of 2008/2009 under the SAP Enterprise licensing agreement Repaired Objects may still be supported by SAP</p> <p>Copying a SAP standard program to a Z-package and modifying it there should be a last resort, as you will have to manually compare and maintain any such programs for every patch and upgrade which makes the general maintainabiliby of your system a lot harder.</p> <p>SAP provide tools to patch or upgrade all the abovementioned changes to standard code and most times you have to do little more than just confirm the change after a patch or upgrade.</p> <p><em>Note:</em> You may need an OSS logon to access the documents. If you can't SAP help is usually quite good.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload