Solved: enhancement

Former Member · ‎2008 Jul 24

Hello gurus

Please tel me the step by step procedure for each anhancement consept

regards

rohan

Former Member · ‎2008 Jul 24

Hi Rohan,

Go through the folling links.

http://help.sap.com/saphelp_nw2004s/helpdata/en/94/9cdc40132a8531e10000000a1550b0/frameset.htm

Reagrds.

Eshwar.

Former Member · ‎2008 Jul 24

hi

CMOD and SMOD for enhancement

The new enhancement concept of the ABAP Workbench (Enhancement Framework) enables the integration of different concepts for modifying and enhancing development objects. The enhancement concept is supported by the Enhancement Builder tool and ABAP language elements.

refer the link

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9cd334f3-0a01-0010-d884-f5612003...

https://www.sdn.sap.com/irj/sdn/nw-development?rid=/webcontent/uuid/2342e1f3-0b01-0010-a186-fdd40488...

this might help u

Amit

Former Member · ‎2008 Jul 24

Hi rohan,

[http://help.sap.com/saphelp_nw70/helpdata/en/42/d356adddec036fe10000000a114cbd/content.htm]

Regards,

Sravanthi

Former Member · ‎2008 Jul 24

hi go through the following document u will get an idea

Enhancement :

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.
It can be done using 
  Customer Exits
  Business ADD-Ins

Why user exits

they do not affect SAP source code but allow to change the functionality of SAP to suit your needs. SAP has provided us with standard exits that we should modify by adding your own functionality to them.
 they are named according to the naming convention they do not affect future upgrades

SAP Programs call Repository objects that you as a customer have created/changed.

Enhancement can be done at the following levels

In ABAP programs( function module exits)

On GUI interfaces (menu exits)

On screens by inserting a subscreen in an area specified by SAP (screen exits)

WHAT IS AN BADI?

BADI - Business Add-Ins
Business Add-Ins are a new SAP enhancement technique based on ABAP Objects.
Each Business Add-In has :
u2013 at least one Business Add-In definition
u2013 a Business Add-In interface
u2013 a Business Add-In class that implements the interface
   BADI is an exit point in a source that allows specific industry sectors, partners, and customers to attach additional software to standard SAP source code with out modifying the original object.
When you define a Business Add-In, enhancement management generates a class that implements your interface. 
The adapter class methods generated by add-in management decide if multiple active implementations should be called. If necessary, these implementations are subsequently executed

.

Advantages of BADIu2019s

This enhancement technique has the advantage of being based on a multi-level system landscape (SAP, country versions, IS solutions, partner, customer and so on).
We can create definitions and implementations of business add-ins at any level of the system landscape

Difference between customer exits and BAdiu2019s

Customer exits assume a two-tiered system infrastructure (SAP - Customers). Where as in case of BAdiu2019s you can create and implement enhancements in as many software layers as you like.

BAdiu2019s can be used to bundle program, menu and screen enhancements into a single add-in. BAdiu2019s can be created and employed in each of the various software levels.

Former Member · ‎2008 Jul 24

Hi Rohan,

Go through the folling links.

http://help.sap.com/saphelp_nw2004s/helpdata/en/94/9cdc40132a8531e10000000a1550b0/frameset.htm

Reagrds.

Eshwar.

Former Member · ‎2008 Jul 24

Hi Rohan,

1. Customer exits: Implemented as Function Modules within z includes. Anybody can change it and no access key is required.

2. User Exit: Implemented as subroutines within includes (any include except y or z includes). You need access for the specific include and then you can any subroutine (user exit) within that Include.

BADIs are the enhanced version of user exits where the same logic is implemented via classes and object (OOP)

Enchancement point is the latest once introduces with ECC6.0 . Not very sure about that but you can change it without any access key.

Please go through the following link which will help you understand the exits in a much better way:

http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec07a25db911d295ae0000e82de14a/content.htm

http://www.sap-img.com/abap/what-is-the-difference-between-smod-and-cmod.htm

http://sap.niraj.tripod.com/id21.html

http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm

http://www.sap-img.com/ab038.htm

User Exits.

-

http://www.erpgenie.com/sap/abap/code/abap26.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

customer exits

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f1a7e790-0201-0010-0a8d-f08a4662...

Menu Exit.

http://www.sappoint.com/abap/spmp.pdf

http://www.sappoint.com/abap/userexit.pdf

http://www.sapdevelopment.co.uk/enhance/mod_sapmenu.htm

http://www.sapdevelopment.co.uk/enhance/enhancehome.htm

1. Previously there were only user-exits.

2. Then came the concept of customer-exits.

3. user exits were nothing but subroutines

FORM/PERFORM

called from standard programs.

4. The FORM defintion was placed inside

an empty include file.

5. So It was called EVERYTIME.

and we need to MODIFY/REPAIR the

standard include .

6. Then it came with concept of customer-exit

7. It consists of calling a FUNCTION MODULE,

which is called only if

the user-exit is ACTIVATED (other wise not called)

In this case, the code in put inside

a pre-defined Z include.

8. Functionality of both is same, howerver

we can note the following important differences

a) Customer exit is called only if activated.

(hence, it does not waste resources)

b) in customer exit, REPAIR does not happen

to the standard include.

Exits are basically the hooks whcih SAP has provided to add your own code.

reward points if helpful

cheers,

sowjanya

Former Member · ‎2008 Jul 24

Hi Rohan,

These are the links for BADI's,

http://help.sap.com/saphelp_nw04/helpdata/en/eb/3e7cf7940e11d295df0000e82de14a/frameset.htm

and

http://help.sap.com/saphelp_nw04/helpdata/en/eb/3e7cf7940e11d295df0000e82de14a/frameset.htm

Badihttp://help.sap.com/saphelp_erp2005/helpdata/en/73/7e7941601b1d09e10000000a155106/frameset.htm

http://support.sas.com/rnd/papers/sugi30/SAP.ppt

http://www.sts.tu-harburg.de/teaching/sap_r3/ABAP4/abapindx.htm

http://members.aol.com/_ht_a/skarkada/sap/

http://www.ct-software.com/reportpool_frame.htm

http://www.saphelp.com/SAP_Technical.htm

http://www.kabai.com/abaps/q.htm

http://www.guidancetech.com/people/holland/sap/abap/

http://www.planetsap.com/download_abap_programs.htm

http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/content.htm

http://esnips.com/doc/e06e4171-29df-462f-b857-54fac19a9d8e/ppt-on-badis.ppt

http://esnips.com/doc/43a58f51-5d92-4213-913a-de05e9faac0d/Business-Addin.doc

http://esnips.com/doc/10016c34-55a7-4b13-8f5f-bf720422d265/BADIs.pdf

http://esnips.com/doc/1e10392e-64d8-4181-b2a5-5f04d8f87839/badi.doc

http://esnips.com/doc/365d4c4d-9fcb-4189-85fd-866b7bf25257/customer-exits--badi.zip

http://esnips.com/doc/3b7bbc09-c095-45a0-9e89-91f2f86ee8e9/BADI-Introduction.ppt

http://help.sap.com//saphelp_470/helpdata/EN/eb/3e7cee940e11d295df0000e82de14a/frameset.htm

Reward points if helpful.

cheers,

sowjanya

Former Member · ‎2008 Jul 24

Hi Rohan,

ABAP Enhacements(CMOD) - Modify SAP standard code using the SAP enhancement transaction CMOD

User exits(Customer Functions)

Enhancing SAP code using user exits and customer functions

Business Data Toolset(BDT)

Using the BDT to enhance SAP transactions such as GMGRANT

Enhancement framework

Using the new Enhancement Framework to enhance standard SAP objects (enhancement points)

Implementing enhancements using Business Add-Ins (BADI's)

Using BADI's to enhance SAP functionality

Find a BADI called from within an SAP transaction

getting SAP to break-point when transaction has access to a BADI

Changing Data Element field text

Changing the text of a data element without modifying the object

Changing Data Element document(F1 help) text

Using CMOD to change the F1 documentation text

Retrieve values not immediately available within exits (user, field)

How to capture additional values not passed as a parameter to the customer function

Add fields to standard Infotype

Shows how to add fields to a standard Infotype

Enhancement Framework

The new enhancement concept of the ABAP Workbench (Enhancement Framework) enables the integration of different concepts for modifying and enhancing development objects. The enhancement concept is supported by the Enhancement Builder tool and ABAP language elements. In the long-term, the new Enhancement Framework is to replace or incorporate the existing enhancement and modification concepts.

Getting Started

Enhancement Framework - The New Way to Enhance Your ABAP Systems (PDF 460 KB)

SAP NetWeaver Product Manager Oliver Mayer presented this content during the ABAP Online Meetup Series.

Switch Framework Demo

This audio visual demonstration by Oliver Mayer features the Switch Framework.

Introduction to the Enhancement Framework

SAP NetWeaver Product Manager Venky Varadadesigan introduces the concepts of the Enhancement Framework.

What the New Enhancement Framework Is For - Its Basic Structure and Elements For Beginners

This blog from SAP NetWeaver Product Manager Thomas Weiss describes what SAP does to bridge the gap between standard software and proprietary solutions.