topic Re: About BADI in Application Development and Automation Discussions

About BADI

Former Member — Wed, 03 Oct 2007 07:04:50 GMT

Hi Friends,

I'm new to BADI. Plz explain the steps of doing it.

Anshu

Re: About BADI

Former Member — Wed, 03 Oct 2007 07:06:58 GMT

Hi Anshu,

Refer below material from SAP

http://help.sap.com/saphelp_nw04/helpdata/en/04/f3683c05ea4464e10000000a114084/content.htm

Regards,

Atish

Re: About BADI

former_member189629 — Wed, 03 Oct 2007 07:07:39 GMT

Anshu,

Business Add-Ins are a new SAP enhancement technique based on ABAP Objects. They can be inserted into the SAP System to accommodate user requirements too specific to be included in the standard delivery. Since specific industries often require special functions, SAP allows you to predefine these points in your software.

As with customer exits two different views are available:

In the definition view, an application programmer predefines exit points in a source that allow specific industry sectors, partners, and customers to attach additional software to standard SAP source code without having to modify the original object.

In the implementation view, the users of Business Add-Ins can customize the logic they need or use a standard logic if one is available.

In contrast to customer exits, Business Add-Ins no longer assume a two-level infrastructure (SAP and customer solutions), but instead allow for a multi-level system landscape (SAP, partner, and customer solutions, as well as country versions, industry solutions, and the like). Definitions and implementations of Business Add-Ins can be created at each level within such a system infrastructure.

SAP guarantees the upward compatibility of all Business Add-In interfaces. Release upgrades do not affect enhancement calls from within the standard software nor do they affect the validity of call interfaces. You do not have to register Business Add-Ins in SSCR.

The Business Add-In enhancement technique differentiates between enhancements that can only be implemented once and enhancements that can be used actively by any number of customers at the same time. In addition, Business Add-Ins can be defined according to filter values. This allows you to control add-in implementation and make it dependent on specific criteria (on a specific Country value, for example).

All ABAP sources, screens, GUIs, and table interfaces created using this enhancement technique are defined in a manner that allows customers to include their own enhancements in the standard. A single Business Add-In contains all of the interfaces necessary to implement a specific task.

The actual program code is enhanced using ABAP Objects. In order to better understand the programming techniques behind the Business Add-In enhancement concept, SAP recommends reading the section on ABAP Objects.

Use these links for reference...

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

http://help.sap.com/saphelp_nw04/helpdata/en/04/f3683c05ea4464e10000000a114084/content.htm

Steps to Activate BAdI Implementations

http://help.sap.com/saphelp_nw04/helpdata/en/5f/071eed117c11d5b37d0050dadef62b/content.htm

reward if helpful,

Karthik

Message was edited by:

Karthik

Re: About BADI

Former Member — Wed, 03 Oct 2007 11:28:52 GMT

Hi,

R u asking for the steps to create ur own badi or to use a standard one??

Anyways,

Let me start with ,

1)what is badi??

a)An enhancement technique based on ABAP

Objects.

b)Used to bundle program, menu and screen enhancements

into a single add-in.

c)Each Business Add-In has :

– at least one Business Add-In definition

– a Business Add-In interface

– a Business Add-In class that implements the interface.

2) Steps For Creation Of A New Badi

• To define a BAdI use Sap Menu -> Tools -> ABAP Workbench -> Utilities -> BusinessAd-Ins -> Definition or directly go to transaction SE18.

•An Interface is also automatically created.

• When a BAdI is created, BADI class gets automatically created with the suffix ‘CL_EX_’ after the first character of the BAdI name.

• Save the BADI to a Package.

• When you double click the interface you will be taken into the class builder where you can define the methods, parameters and exceptions for that interface.

• Specify the methods in the Class Builder for the interface

• Instance methods can access all of the attributes of a class, and can trigger all of the events of the class

• Static methods can only access static attributes and trigger static events

• Click on the Parameters button to specify any Import/Export parameters for the method.

• Check the Optional field if it is not a mandatory parameter

• The type, default value and description of the parameter can be specified.

• You can specify any exceptions in the Exceptions section.

• For class based exceptions, check the checkbox ‘Exception Classes’.

BAdI Implementation

Choose ABAP Workbench -> Utilities -> Business Add-Ins (transaction SE19) from

the SAP menu

– Enter a name for the implementation and choose Create.

– Enter the name of the BAdI you want to create an implementation for in the dialog box that appears.

• During implementation creation, a class for implementing the enhancement's interface is

also created

• Navigate to the Class Builder by double-clicking the method.

• Insert the source code between the method and endmethod statements and activated.

• Exception handling for the method can be handled in this section.

How to call the new badi in our program??

• When a BAdI is created, the enhancement manager automatically generates a class that implement the interface

• In order to be able to call static methods, you must declare the corresponding class in ABAP Objects using the ‘class … definition load’ statement

• In the example having created a BAdI for division, you can program the call for the BAdI in the following manner:

– Create an Interface Reference Variable in the program ‘L_BADI_INSTANCE’

– Perform the statement ‘call method cl_exithandler …’ using the BAdI and the

interface reference variable.

– Call method DIVIDE_NUMBERS using the interface reference variable

L_BADI_INSTANCE.

report demo.

class cl_exithandler definition load.

data: L_BADI_INSTANCE type ref to <interface name>,

RES TYPE I,

STATUS TYPE C.

SELECTION-SCREEN: BEGIN OF BLOCK B1,

PARAMETER: p1 type i, p2 type i.

SELECTION-SCREEN: END OF BLOCK B1.

START-OF-SELECTION.

CALL METHOD CL_EXITHANDLER=>GET_INSTANCE

EXPORTING

EXIT_NAME = <NEWBADI DEFINITION NAME>

NULL_INSTANCE_ACCEPTED = 'X'

CHANGING

INSTANCE = L_BADI_INSTANCE

EXCEPTIONS

OTHERS = 1.

CALL METHOD L_BADI_INSTANCE->DIVIDE_NUMBERS

EXPORTING

NUM1 = P1

NUM2 = P2

IMPOTING

RESULT = RES

STATUS = STATUS.

IF STATUS EQ SPACE.

WRITE RES.

ENDIF.

Types of Badi's

• Single use : only one active implementation possible.

• Multiple use : With this option you can have multiple implementations for the same BAdI

• Filter-Dependent : Business Add-Ins may be implemented depending on a specific filter value (example, country-specific versions: Distinct implementations of the BAdI can be created for each country). A filter type must be entered when defining your enhancement (a country or industry sector, for example). All methods created in the enhancement's interface have filter value 'FLT_VAL' as their import parameter. The method then selects the active implementation based on the data provided in the filter value.

To search for existing Badis

Scenario: Need to find the name of the BADI available in a transaction

1. Go to Transaction SE24

2. Enter the Object Type CL_EXITHANDLER and click on Display.

3. Double Click on method "GET_INSTANCE".

4. Put a Break-point on

Call method cl_exithandler=>get_class_name_by_interface

5. Run any Transaction for which you need enhancements.

6. The execution will stop at the break point. Check the values of variable 'exit_name', it will give you the BADI name called at that time.

This way you will find all the BADIs called on click of any button in any transaction.

Hope this helps.

Regards,

simy Abraham.

Re: About BADI

Former Member — Wed, 03 Oct 2007 17:08:53 GMT

go through this link

/message/1388480#1388480 [original link is broken]

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

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

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

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

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

Here is the best solution,

Follow the below steps to find out what all BADI's are called when you press any button in any transaction.

1) Goto se24 (Display class cl_exithandler)

2) Double click on the method GET_INSTANCE.

3) Put a break point at Line no.25 (CASE sy-subrc).

Now

4) Execute SAP standard transaction

5) Press the required button for which you need to write an exit logic, the execution will stop at the break point.

6) Check the values of variable 'exit_name', it will give you the BADI name called at that time.

7) This way you will find all the BADIs called on click of any button in any transaction

Please give me reward point..

Thanks

Murali Poli

Re: About BADI

Former Member — Thu, 04 Oct 2007 04:06:55 GMT

helpful BADI detail