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
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

BADI - An Example

Former Member

‎01-10-2008 5:45 AM

0 Kudos

Hi Experts

i am new to badi, can anyone pls explain me one example of badi with step by step procedure.

Thanks in advance.

Regards

Rajaram

5 REPLIES 5

Former Member

‎01-10-2008 5:46 AM

0 Kudos

There are two steps in User Exit creation.

1} Identify the User Exit suitable for the requirement and that is available in the system:

Code SE18 is used to Identify the BADI available.

Look for the string 'CL_EXITHANDLER' in the standard program. This is a class which has a method 'GET_INSTANCE' which is used to trigger BADI's from the Standard Program. The interface parameter for this static method 'EXIT_NAME' is used to pass the BADI to the method.

Open Standard Program and do a global search 'CL_EXITHANDLER'.

SE18 > give the BADI name found through above search.

CUSTOMER_ADD_DATA > which has a method SAVE_DATA.

2} Implement the User Exit identified through above process.

T.Code SE19 is used to Implement BADI.

SE19 > give the implementation name > Give the Definition name as CUSTOMER_ADD_DATA and the Short Text.

Check this blogs 2 find a BADI:

How To Define a New BAdI Within the Enhancement Framework (Some Basics About the BAdI,BAdI Commands in ABAP,

When to Use a BAdI?)

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

How to implement a BAdI And How to Use a Filter

/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

Introducing Business Add-Ins

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f3202186-0601-0010-6591-b832b1a0...

How to implement BAdi in Enhancement Framework

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d0456c54-0901-0010-f0b3-cd765fb9...

Business Add-Ins

http://help.sap.com/saphelp_47x200/helpdata/en/ee/a1d548892b11d295d60000e82de14a/frameset.htm

BAdI: Customer-Defined Functions in the Formula Builder

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

Difference Between BADI and User Exits

http://www.sap-img.com/abap/difference-between-badi-and-user-exits.htm

To Use BADI - Business Add In you need to Understand ABAP OO Interface Concept

http://www.sap-img.com/abap/business-add-in-you-need-to-understand-abap-oo-interface-concept.htm

You can check the links for Step by Step Badi Implemntation

(very helpful self learning docs).

BADI Step by Step Implementation.

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

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

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

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

www.sapgenie.com/publications/saptips/022006%20-%20Zaidi%20BADI.pdf

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

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

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

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

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

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

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/srm/badi-general+information&

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

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

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

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

www.sapgenie.com/publications/saptips/022006%20-%20Zaidi%20BADI.pdf

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

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

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

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

http://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://www.allsaplinks.com/badi.html

/people/thomas.weiss/blog/2006/04/03/how-to-define-a-new-badi-within-the-enhancement-framework--part-3-of-the-serieshttps:///people/alwin.vandeput2/blog/2006/04/13/how-to-search-for-badis-trace-it

/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 /people/thomas.weiss/blog/2006/05/03/source-code-enhancements--part-5-of-the-series-on-the-new-enhancement-framework

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

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

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

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

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

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40921dd7-d5cf-2910-1894-bb62316a...

http://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

/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

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

Difference Between BADI and User Exits

http://www.sap-img.com/abap/difference-between-badi-and-user-exits.htm

Reward points if useful.

Former Member

‎01-10-2008 5:52 AM

0 Kudos

Hi Ram,

Business Add-Ins

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 (SMOD/CMOD [Page 40]), 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-system infrastructure (SAP and customers), but instead allow for multiple levels of software development (by SAP, partners, and customers, and 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. In Release 4.6A, program and menu enhancements can be made with Business Add-Ins. 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

DEFINING THE BADI

1) execute Tcode SE18.

2) Specify a definition Name : ZBADI_SPFLI

3) Press create

4) Choose the attribute tab. Specify short desc for badi.. and specify the type :

multiple use.

5) Choose the interface tab

6) Specify interface name: ZIF_EX_BADI_SPFLI and save.

7) Dbl clk on interface name to start class builder . specify a method name (name,

level, desc).

Method level desc

Linese;ection instance methos some desc

😎 place the cursor on the method name desc its parameters to define the interface.

Parameter type refe field desc

I_carrid import spfli-carrid some

I_connid import spefi-connid some

9) save , check and activate…adapter class proposed by system is

ZCL_IM_IM_LINESEL is genereated.

IMPLEMENTATION OF BADI DEFINITION

1) EXECUTE tcode se18.choose menuitem create from the implementation menubar.

2) Specify aname for implementation ZIM_LINESEL

3) Specify short desc.

4) Choose interface tab. System proposes a name fo the implementation class.

ZCL_IM_IMLINESEL which is already generarted.

5) Specify short desc for method

6) Dbl clk on method to insert code..(check the code in “AAA”).

7) Save , check and activate the code.

Some useful URL

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

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

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

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

www.sapgenie.com/publications/saptips/022006%20-%20Zaidi%20BADI.pdf

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

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

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

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

Now write a sample program to use this badi method..

Look for “BBB” sample program.

“AAA”

data : wa_flights type sflight,

it_flights type table of sflight.

format color col_heading.

write:/ 'Flight info of:', i_carrid, i_connid.

format color col_normal.

select * from sflight

into corresponding fields of table it_flights

where carrid = i_carrid

and connid = i_connid.

loop at it_flights into wa_flights.

write:/ wa_flights-fldate,

wa_flights-planetype,

wa_flights-price currency wa_flights-currency,

wa_flights-seatsmax,

wa_flights-seatsocc.

endloop.

“BBB”

&----

*& Report ZBADI_TEST *

*& *

&----

REPORT ZBADI_TEST .

tables: spfli.

data: wa_spfli type spfli,

it_spfli type table of spfli with key carrid connid.

*Initialise the object of the interface.

data: exit_ref type ref to ZCL_IM_IM_LINESEL,

exit_ref1 type ref to ZIF_EX_BADISPFLI1.

selection-screen begin of block b1.

select-options: s_carr for spfli-carrid.

selection-screen end of block b1.

start-of-selection.

select * from spfli into corresponding fields of table it_spfli

where carrid in s_carr.

end-of-selection.

loop at it_spfli into wa_spfli.

write:/ wa_spfli-carrid,

wa_spfli-connid,

wa_spfli-cityfrom,

wa_spfli-deptime,

wa_spfli-arrtime.

hide: wa_spfli-carrid, wa_spfli-connid.

endloop.

at line-selection.

check not wa_spfli-carrid is initial.

create object exit_ref.

exit_ref1 = exit_ref.

call method exit_ref1->lineselection

EXPORTING

i_carrid = wa_spfli-carrid

i_connid = wa_spfli-connid.

clear wa_spfli.

kindly reward if found helpful.

cheers,

Hema.

Former Member

‎01-10-2008 5:53 AM

0 Kudos

Hi Ram, check this BADI creation with an example.

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.

cheers,

Hema.

Former Member

‎01-10-2008 5:54 AM

0 Kudos

hi Raja,

You can use the transaction SE18 to define a new BAdI definition which may be implemented by other developers later. It is not so challenging. Here is the roadmap:

A. BAdI Definition

1. SE18

2. Enter the name for the BAdI to be created in customer namespace and press "Create".

3. Enter a definition for your BAdI and on the interface tab enter a name for the BAdI interface. SAP proposes a name and it is pretty good. Meanwhile a BAdI class is also created which is not in our concern.

e.g for "ZTEST", SAP proposes "ZIF_EX_TEST" for the interface and "ZCL_EX_TEST" for the class.

4. Save your BAdI.

5. Double-click on the interface name. It will pass to a Class Builder session to make you implement your interface. If you are not familiar to the Class Builder; it's a bit like Function Builder and it will be easy to discover its procedure.

6. Save and activate your interface.

B. Calling your BAdI from an application program

1. Declare a reference variable with reference to the Business Add-In interface.

e.g. DATA exit_ref TYPE REF TO zif_ex_test.

2. Call the static method GET_INSTANCE of the service class CL_EXITHANDLER. This returns an instance of the required object.

e.g.

CALL METHOD CL_EXITHANDLER=>GET_INSTANCE

CHANGING instance = exit_ref .

3. After those two steps, you can now call all of the methods of the BAdI where it is required in your program. Make sure you specify the method interfaces correctly.

C. BAdI Implementations

1. SE19

2. Enter the name for the BAdI implementation to be created in customer namespace and press "Create".

3. It will request the BAdI definition name to which this implementation will be tied.

4. Enter a definition for your implementation and on the interface tab enter a name for the implementing class. Again SAP proposes a name and it is pretty good.

e.g for "ZIMPTEST", SAP proposes "ZCL_IM_IMPTEST".

5. Save your implementation.

6. To implement a method, just double-click on the method name and you will be taken to the Class Builder to write the code for it. Here you redefine the BAdI interface methods.

7. You must activate your implementation to make it executable. You can only activate or deactivate an implementation in its original system without modification. The activation or deactivation must be transported into subsequent systems

Reward if helpful.

Thankyou,

Regards.

Former Member

‎01-10-2008 5:56 AM

0 Kudos

Hi Raja,

BADIs are Business Add-Ins

Similar to user exits, helps hook custom enhancements to SAP functionality

Definition / Implementation

Transactions SE18 (Definition) / SE19 (Implementation)

BADI Vs User Exits –

BADIs are object oriented

BADI’s can be implemented multiple times

for step by step example:

http://www.sapmaterial.com/badi.html

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

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

http://www.sapmaterial.com/?gclid=CN322K28t4sCFQ-WbgodSGbK2g

(SAP link- ultimate material )

Business Add-Ins

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 (SMOD/CMOD Page 40), 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-system infrastructure (SAP and customers), but instead allow for multiple levels of software development (by SAP, partners, and customers, and 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. In Release 4.6A, program and menu enhancements can be made with Business Add-Ins. 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

DEFINING THE BADI

1) execute Tcode SE18.

2) Specify a definition Name : ZBADI_SPFLI

3) Press create

4) Choose the attribute tab. Specify short desc for badi.. and specify the type :

multiple use.

5) Choose the interface tab

6) Specify interface name: ZIF_EX_BADI_SPFLI and save.

7) Dbl clk on interface name to start class builder . specify a method name (name,

level, desc).

Method level desc

Linese;ection instance methos some desc

😎 place the cursor on the method name desc its parameters to define the interface.

Parameter type refe field desc

I_carrid import spfli-carrid some

I_connid import spefi-connid some

9) save , check and activate…adapter class proposed by system is

ZCL_IM_IM_LINESEL is genereated.

IMPLEMENTATION OF BADI DEFINITION

1) EXECUTE tcode se18.choose menuitem create from the implementation menubar.

2) Specify aname for implementation ZIM_LINESEL

3) Specify short desc.

4) Choose interface tab. System proposes a name fo the implementation class.

ZCL_IM_IMLINESEL which is already generarted.

5) Specify short desc for method

6) Dbl clk on method to insert code..(check the code in “AAA”).

7) Save , check and activate the code.

Each BAdI has a definition and more than one implementation. The definition means the methods(in class concept) that are used for performing various functions. The BAdI definition can be viewed in SE18 transaction(for standard ones) and user-defined BAdIs can be created in the same transaction as well.

When you create a BAdI definition, an class interface will be automatically created and you can define your methods in the interface. The implementation of the methods can be done in SE19 transaction .

reward if useful

thanks and regards

suma sailaja