Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

BAdI

Former Member
0 Kudos

Hi,

How to create BAdI ..?

Can u plz give me step wise procedure..

5 REPLIES 5

Former Member
0 Kudos

Have a look at below links.

http://help.sap.com/saphelp_nw04/helpdata/en/e6/d54d3c596f0b26e10000000a11402f/content.htm

http://help.sap.com/saphelp_nw2004s/helpdata/en/c2/eab541c5b63031e10000000a155106/frameset.htm

Business add-ins are enhancements to the standard version of the system.

Business Add-In is a new SAP enhancement technique based on ABAP Objects.

They can be inserted into the SAP system based on specific user requirements.

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

In order to enhance a program, a Business Add-In must first be defined

Subsequently two classes are automatically generated:

• An interface with ‘IF_EX_’ inserted between the first and second characters of the BADI name.

• An adapter class with ‘CL_EX_’ inserted between the first and second characters of the BADI name.

The Application developer creates an interface for this Add-In.

There are multiple ways of searching for BADI.

• Finding BADI Using CL_EXITHANDLER=>GET_INSTANCE

• Finding BADI Using SQL Trace (TCODE-ST05).

• Finding BADI Using Repository Information System (TCODE- SE84).

1. Go to the Transaction, for which we want to find the BADI, take the example of Transaction VD02. Click on System->Status. Double click on the program name. Once inside the program search for ‘CL_EXITHANDLER=>GET_INSTANCE’.

Make sure the radio button “In main program” is checked. A list of all the programs with call to the BADI’s will be listed.

The export parameter ‘EXIT_NAME’ for the method GET_INSTANCE of class CL_EXITHANDLER will have the user exit assigned to it. The changing parameter ‘INSTANCE’ will have the interface assigned to it. Double click on the method to enter the source code.Definition of Instance would give you the Interface name.

2. Start transaction ST05 (Performance Analysis).

Set flag field "Buffer trace"

Remark: We need to trace also the buffer calls, because BADI database tables are buffered. (Especially view V_EXT_IMP and V_EXT_ACT)

Push the button "Activate Trace". Start transaction VA02 in a new GUI session. Go back to the Performance trace session.

Push the button "Deactivate Trace".

Push the button "Display Trace".

The popup screen "Set Restrictions for Displaying Trace" appears.

Now, filter the trace on Objects:

• V_EXT_IMP

• V_EXT_ACT

Push button "Multiple selections" button behind field Objects

Fill: V_EXT_IMP and V_EXT_ACT

All the interface class names of view V_EXT_IMP start with IF_EX_. This is the standard SAP prefix for BADI class interfaces. The BADI name is after the IF_EX_.

So the BADI name of IF_EX_CUSTOMER_ADD_DATA is CUSTOMER_ADD_DATA

3. Go to “Maintain Transaction” (TCODE- SE93).

Enter the Transaction VD02 for which you want to find BADI.

Click on the Display push buttons.

Get the Package Name. (Package VS in this case)

Go to TCode: SE84->Enhancements->Business Add-inns->Definition

Enter the Package Name and Execute.

Here you get a list of all the Enhancement BADI’s for the given package MB.

For more info have a look at below links:

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

/people/thomas.weiss/blog/2006/04/03/how-to-define-a-new-badi-within-the-enhancement-framework--part-3-of-the-series

/people/thomas.weiss/blog/2006/04/18/how-to-implement-a-badi-and-how-to-use-a-filter--part-4-of-the-series-on-the-new-enhancement-framework

Former Member
0 Kudos

What are BAdIs?

• is an anticipated point of extension – these points act like sockets and exist in the original source code

• based on ABAP Objects. BAdI defines an interface that can be implemented by BAdI-implementations that are transport objects of their own

• Important! There are 2 roles: Enhancement Option-provider & Implementer.

• In the above context, Enhancement Implementation can be done only if option (hook) is provided by the Option-provider. In simple words there are no implicit BAdIs.

Note: In the following slides, Definitions are created so as to understand the method of BAdI definition & for example purpose. As stated above this is the role of Enhancement Option-Provider.

Classic BAdIs already exist since SAP Release 4.6

BAdIs have been Re-implemented in ECC7.0 under the new Enhancement Framework & Switch Framework

Classic BAdIs

• To understand what a powerful pattern a BAdI is, we will now define & then implement a BAdI

BADI Class is created automatically.

The various options are described below in detail:

1. Enhanceable: Enhanceability of filter types can only be specified for filter-dependent BADI definitions under very special conditions. For example, the domain belonging to the filter type must be linked with a value table that is of the type E or G. A BADI implementation can then be created in one step by creating a new filter value that is automatically entered into the value table at save and also copied into the transport order of the BADI implementation. In addition, it is also possible to create a new filter value and, at the same time, a BADI implementation with the same name. Naturally, you can also specify existing filter values.

You should select this feature if there is a prerequisite that a new filter value is created together with a new BADI implementation - that is, that BADI implementations are not created solely with existing filter values, although this, too, is possible.

2. Multiple-Use

3. Filter-Dependent

Instance Methods can access all of the attributes of a class and can trigger all events of a class. Static Methods can only access static attributes and static events.

Adding event handling & exception(s) is not a necessary step…

Exceptions:

Events:

Events can be defined in classes or in interfaces. Corresponding methods can trigger these events with the RAISE EVENT statement. Each class (or interface) that is going to handle the corresponding event must implement a relevant handler method, and register it using the SET HANDLER statement. When an event occurs, the system calls all of the handler methods registered for that event.

Like method definitions, events have a parameter interface. The only difference is that events may only have EXPORTING parameters.

Save and activate the BAdI definition!

BADI Implementation

BAdI Implementation (SE19)

Save and activate the BAdI implementation!

Implementation for SAP provided BAdI…

Roles: (BADI Definition & Implementation)

• Developer: Enhancement (BAdI) Option-Implementer

• SAP: Option-Provider

BAdI as a ‘controlled’ Enhancement Option:

• Option-provider defines the interface and limits the implementer to the class that the implements the BAdI

• Assured that BAdI implementer can only change the parameters handed over to the BAdI by the option provider

Steps:

1. Search for the BAdI corresponding to the transaction

2. Create a custom Implementation for the BAdI by adding code in the appropriate method

3. Test that the method with custom code is invoked on executing the transaction.

Create Material using MM01. Copy from existing Material.

Select the required views.

Enter mandatory data and click on Save.

Check the Exit Name ‘BADI_MATERIAL_CHECK’. This is the BAdI we are going to implement.

Implementing the BAdI ‘BADI_MATERIAL_CHECK’

Go to SE18 & check the BAdI definition (Methods)

We will be using the ‘CHECK_DATA’ method. Double Click to see the Method Parameters.

Implementing BADI

Go to SE19. Specify a name for the BAdI Implementation.

Enter the Definition Name.

Double-click the method ‘CHECK_DATA’ to enter the source code

Double-click the method ‘CHECK_DATA’ to enter the source code

We are only showing an message in this case; if division in ‘Basic Data’ tab of Material Creation is not entered.

The structure CMARA is defined as ‘Exporting Parameter’. Data can be modified using this.

Activate the Implementation

Testing the BAdI

Testing the BAdI implementation (BADI_MATERIAL_CHECK)

MM01 / MM02 and create / change material and save. On clicking Save, our BADI will trigger.

Message is displayed (Division not entered)

BAdIs…in the new Enhancement Framework (ECC 6.0)

• How the new BAdIs differ from the Classic BAdI?

• Good news is that…basic thing about the BAdI remains the same!

• Differ in the manner in which new BAdI is embedded in the container-structure of the Enhancement Framework

• Better performance & Lower Memory consumption

• Evaluates as much information as possible during compile time

• 40-600 times faster than Classic BAdIs

• Internal handle-class integrated in the SAP Kernel

• Provides ‘switchable’ implementation(s) through use of Switch Framework

• Special optimizations with ‘GET BADI’ & ‘CALL BADI’ (new ABAP commands)

• Implementation Inheritance

Usage of old (classic) BAdIs versus New BAdIs…

• Two new ABAP commands for the new BAdI:

• GET BADI : all active implementations are selected and the method of BAdI is called (amounts to a loop with different method calls in it)

Enhancement Spot as a container for BAdI…

• Enhancement Framework has containers for BAdI implementations as well

Former Member
0 Kudos

Hi Tharani, this will solve ur problem.

REPORT Z_BADI_TEST.

  • test call Badi from standard abap. (Only from rel 6.40 and above)

  • do the following

  • 1) define the Badi (SE18). For Abap call test uncheck multiple use

  • and filter boxes

  • 2) Implement the badi (SE19). Add any methods here in the implemntation

  • 3) activate

*

  • 4) define the standard class exithandler to the abap. This class is the "Badi caller

"

  • 5) define an exit variable referring to your Badi Implementation interface

  • this interface will normally be something like ZIF_EX***************

  • You will see this in SE18/SE19.

*

  • 6) Instantiate your instance of the badi (method call get_instance)

  • 7) Now call any method(s) in the Badi.

*

class cl_exithandler definition load. "Declaration

data exit type ref to zif_ex__jimbotest. "Interface reference

data yes type c.

data: v_knvv type knvv. "Used in Fmod call in Badi methods

start-of-selection.

yes = ' '.

selection-screen begin of block b1.

parameters: r1 radiobutton group rad1,

r2 radiobutton group rad1,

r3 radiobutton group rad1.

selection-screen end of block b1.

parameters: p_kunnr type knvv-kunnr.

select single * into v_knvv

from knvv

where kunnr eq p_kunnr.

export v_knvv to memory id 'CUST6A'. "Save customer data for the function module

call method cl_exithandler=>get_instance "Factory method call

exporting "Method

exit_name = 'Z_JIMBOTEST' "Name of your BADI

  • null_instance_accepted = yes

changing instance = exit.

if not exit is initial.

break-point 1.

if r1 = 'X'.

call method exit->dispord . "Add-In call

  • changing testparm1 = word.

endif.

if r2 = 'X'.

call method exit->dispfakt.

endif.

if r3 = 'X'.

call method exit->dispmat.

endif.

In the badi methods

1)

method ZIF_EX__JIMBOTEST~DISPORD.

CALL FUNCTION 'Z_DISPLAY_CUST'.

endmethod.

2)

method ZIF_EX__JIMBOTEST~DISPFAKT.

CALL FUNCTION 'Z_DISPLAY_FAKT'.

endmethod

3)

method ZIF_EX__JIMBOTEST~DISPMAT.

CALL FUNCTION 'Z_DISPLAY_CUST'.

endmethod.

Copy via SE 41 the status SALV_STANDARD from standard SAP program SALV_DEMO_METADATA into the main program where you've created the 3 function modules below (SAP______TOP)

Global Data for the three function modules I'm calling

FUNCTION-POOL Z_BADI_KNVV. "MESSAGE-ID ..

include <color>.

include <icon>.

include <symbol>.

tables: zknvv.

data: v_zzkvgr6 TYPE KNVV-ZZKVGR6.

data: choice1 type c.

data: choice2 type c.

data: choice3 type c.

data: choice4 Type c.

data: ok-code(5) type c.

data: answer type string.

data: value1 type SPOP-VARVALUE1.

data: answer1 type string.

tables: vbak, vbap, vakpa, vbrk, vrkpa.

data: lr_functions type ref to cl_salv_functions_list.

constants: gc_true type sap_bool value 'X',

gc_false type sap_bool value space.

  • add for colour displays

data: ls_color type lvc_s_colo.

DATA : LV_SALV_COLUMNS_TABLE TYPE REF TO CL_SALV_COLUMNS_TABLE.

data: lr_columns type ref to cl_salv_columns_table,

lr_column type ref to cl_salv_column_table.

Data:

gr_table TYPE REF TO cl_salv_table.

data: z_datum type sy-datum.

data: v_knvv type knvv.

data : begin of s_vbak,

vkorg type vakpa-vkorg,

vkgrp type vakpa-vkgrp,

vtweg type vakpa-vtweg,

spart type vakpa-spart,

auart type vakpa-auart,

vbeln type vakpa-vbeln,

bstnk type vakpa-bstnk,

audat type vakpa-audat,

netwr type vbak-netwr,

end of s_vbak.

data : begin of s_vbrk,

vbeln type vrkpa-vbeln,

vkorg type vrkpa-vkorg,

fkart type vrkpa-fkart,

fkdat type vrkpa-fkdat,

netwr type vbrk-netwr,

end of s_vbrk.

data: begin of s_vbap,

matnr type vbap-matnr,

arktx type vbap-arktx,

netwr type vbap-netwr,

kwmeng type vbap-kwmeng,

end of s_vbap.

data: t_vbap like table of s_vbap.

data: t_vbak

like table of s_vbak.

data: t_vbrk

like table of s_vbrk.

data: s_name type tabname.

data: gr_selections type ref to cl_salv_selections.

data: gr_events type ref to cl_salv_events_table.

Source code of the function modules.

Function modules

FUNCTION Z_DISPLAY_CUST.

*"----


""Lokale interface:

*"----


s_name = 'S_VBAK'.

  • orders in last 6 months

z_datum = sy-datum - 180.

import v_knvv from memory id 'CUST6A'.

  • get data

select avkorg aaudat avkgrp avtweg aspart aauart abstnk avbeln b~netwr

into corresponding fields of table t_vbak

up to 100 rows

from ( vakpa as a

inner join vbak as b

on avbeln eq bvbeln )

where a~kunde eq v_knvv-kunnr

and a~parvw eq 'AG'

  • and a~vkorg eq 'EN01'

and a~trvog eq '0'

and a~audat gt z_datum.

sort t_vbak by audat descending.

*data: gt_hyperlink type standard table of g_type_s_hyperlink.

  • Instead of if_salv_c_bool_sap=>false, you can pass the

  • value if_salv_c_bool_sap=>true to this method to

  • see your ALV as a list.

  • display data in Grid / List

TRY.

CALL METHOD cl_salv_table=>factory

EXPORTING

list_display = if_salv_c_bool_sap=>false

IMPORTING

r_salv_table = gr_table

CHANGING

t_table = t_vbak.

CATCH cx_salv_msg.

ENDTRY.

try.

LV_SALV_COLUMNS_TABLE = gr_table->get_columns( ).

lr_column ?= LV_SALV_COLUMNS_TABLE->get_column( 'NETWR' ).

ls_color-col = col_negative.

ls_color-int = 0.

ls_color-inv = 0.

lr_column->set_color( ls_color ).

catch cx_salv_not_found.

endtry.

try.

lr_column ?= LV_SALV_COLUMNS_TABLE->get_column( 'VBELN' ).

ls_color-col = col_negative.

ls_color-int = 1.

ls_color-inv = 1.

lr_column->set_color( ls_color ).

catch cx_salv_not_found.

endtry.

try.

*LV_SALV_COLUMNS_TABLE = gr_table->get_columns( ).

lr_column ?= LV_SALV_COLUMNS_TABLE->get_column( 'NETWR' ).

lr_column->set_short_text( 'Short' ).

lr_column->set_medium_text( 'Medium' ).

lr_column->set_long_text( 'Net Value' ).

*lr_column ?= LV_SALV_COLUMNS_TABLE->get_column( 'URL' ).

*

catch cx_salv_not_found.

endtry.

gr_table->set_screen_status( pfstatus = 'SALV_STANDARD'

report = sy-repid

set_functions = gr_table->c_functions_all ).

  • this statement actually does the display.

gr_table->display( ).

ENDFUNCTION.

FUNCTION Z_DISPLAY_FAKT.

*"----


""Lokale interface:

*"----


s_name = 'S_VBRK'.

  • invoices in last 6 months

z_datum = sy-datum - 180.

import v_knvv from memory id 'CUST6A'.

  • get data

select avbeln afkart avkorg afkdat

b~netwr

into corresponding fields of table t_vbrk

up to 100 rows

from ( vrkpa as a

inner join vbrk as b

on avbeln eq bvbeln )

where a~kunde eq v_knvv-kunnr

and a~parvw eq 'RG'

  • and a~vkorg eq 'EN01'

and a~vbtyp eq 'M'

and a~fkdat gt z_datum.

sort t_vbrk by fkdat descending.

*data: gt_hyperlink type standard table of g_type_s_hyperlink.

  • Instead of if_salv_c_bool_sap=>false, you can pass the

  • value if_salv_c_bool_sap=>true to this method to

  • see your ALV as a list.

  • display data in Grid / List

TRY.

CALL METHOD cl_salv_table=>factory

EXPORTING

list_display = if_salv_c_bool_sap=>false

IMPORTING

r_salv_table = gr_table

CHANGING

t_table = t_vbrk.

CATCH cx_salv_msg.

ENDTRY.

try.

LV_SALV_COLUMNS_TABLE = gr_table->get_columns( ).

lr_column ?= LV_SALV_COLUMNS_TABLE->get_column( 'NETWR' ).

ls_color-col = col_negative.

ls_color-int = 0.

ls_color-inv = 0.

lr_column->set_color( ls_color ).

catch cx_salv_not_found.

endtry.

try.

lr_column ?= LV_SALV_COLUMNS_TABLE->get_column( 'VBELN' ).

ls_color-col = col_negative.

ls_color-int = 1.

ls_color-inv = 1.

lr_column->set_color( ls_color ).

catch cx_salv_not_found.

endtry.

try.

*LV_SALV_COLUMNS_TABLE = gr_table->get_columns( ).

lr_column ?= LV_SALV_COLUMNS_TABLE->get_column( 'NETWR' ).

lr_column->set_short_text( 'Short' ).

lr_column->set_medium_text( 'Medium' ).

lr_column->set_long_text( 'Net Value' ).

*lr_column ?= LV_SALV_COLUMNS_TABLE->get_column( 'URL' ).

*

catch cx_salv_not_found.

endtry.

gr_table->set_screen_status( pfstatus = 'SALV_STANDARD'

report = sy-repid

set_functions = gr_table->c_functions_all ).

  • this statement actually does the display.

gr_table->display( ).

ENDFUNCTION.

FUNCTION Z_DISPLAY_MATERIAL.

*"----


""Lokale interface:

*"----


s_name = 'S_VBAP'.

  • invoicesrs in last 6 months

z_datum = sy-datum - 180.

import v_knvv from memory id 'CUST6A'.

  • get data

select avbeln bmatnr barktx bnetwr b~kwmeng

into corresponding fields of table t_vbap

up to 100 rows

from ( vakpa as a

inner join vbap as b

on avbeln eq bvbeln )

where a~kunde eq v_knvv-kunnr

and a~parvw eq 'AG'

  • and a~vkorg eq 'EN01'

and a~trvog eq '0'

and a~audat gt z_datum.

TRY.

CALL METHOD cl_salv_table=>factory

EXPORTING

list_display = if_salv_c_bool_sap=>false

IMPORTING

r_salv_table = gr_table

CHANGING

t_table = t_vbap.

CATCH cx_salv_msg.

ENDTRY.

try.

LV_SALV_COLUMNS_TABLE = gr_table->get_columns( ).

lr_column ?= LV_SALV_COLUMNS_TABLE->get_column( 'NETWR' ).

ls_color-col = col_negative.

ls_color-int = 0.

ls_color-inv = 0.

lr_column->set_color( ls_color ).

catch cx_salv_not_found.

endtry.

try.

lr_column ?= LV_SALV_COLUMNS_TABLE->get_column( 'ARKTX' ).

ls_color-col = col_negative.

ls_color-int = 1.

ls_color-inv = 1.

lr_column->set_color( ls_color ).

catch cx_salv_not_found.

endtry.

try.

*LV_SALV_COLUMNS_TABLE = gr_table->get_columns( ).

lr_column ?= LV_SALV_COLUMNS_TABLE->get_column( 'NETWR' ).

lr_column->set_short_text( 'Short' ).

lr_column->set_medium_text( 'Medium' ).

lr_column->set_long_text( 'Net Value' ).

*lr_column ?= LV_SALV_COLUMNS_TABLE->get_column( 'URL' ).

*

catch cx_salv_not_found.

endtry.

gr_table->set_screen_status( pfstatus = 'SALV_STANDARD'

report = sy-repid

set_functions = gr_table->c_functions_all ).

  • this statement actually does the display.

gr_table->display( ).

ENDFUNCTION.

kindly reward if helpful.

cheers,

Hema.

Former Member
0 Kudos

Hi,

Step by step procedure for BADI

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

Regards,

Satish