BADI Implementation

[Former Member]

Hi all,

I am new to BADI. I have got an object in which i have to create a custom implementation.

They have given me name of SAP BADI and also the method name.

But they have not mentioned how this BADI will be triggered.

Can anyone guide me how to proceed?

Thanks in advance.

Sunanda.

[Former Member]

Hi

Goto SE19- create the implementation for the same

then enter the implementation and go inside the BADI then double click on the implementation and

write the code inside it

Regards

Shiva

[Former Member]

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.

Regards.

[Former Member]

Hi Sunanda,

The person who gave you the BAdi and method has obviously did his/her homework and hence knows where the BAdi is called from.

All you need to do is creaet an implementation for the BAdi from SE19 and code within the method mentioned the required logic for manipulation.

Activate the implementation and then put a break point in the method code.

Then run the main SAP program and the control will stop @ break point in your implementation. In debugging, then check the call stack.

Cheers.

[Former Member]

But i dont know the main program from where i have to execute.

I am using BAdI.. DOCUMENT_MAIN01 method BEFORE_SAVE.

I have done coding in this method but dont know how to check whether it is working fine.

Thanks

Sunanda.

[Former Member]

u can put break point in ur implementation then u can find when it is triggering

[Former Member]

Hi ,

As the name of BADI suggest ,it is called on some "check " event before Save.

I think you must be aware on the application you are working.So put breakpoints in

our code and if it passes the filter condition then your implementation will be called,once you run the application.Contact the people who assigned the task for starting point of application.

Once in debug mode ,you can see the call stack and understand from where your implementation is called.As suggested by some other people ,explore Se19 , 18.

If there are multiple implemenations then control sequence of your code being called might not be implicitly possible.

Regards,

Abhishek

[Former Member]

Hi

try running T code CV01N or CV02N

Regards

Shiva

[Former Member]

Hai.

check this.

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 a_{vkorg a}audat a_{vkgrp a}vtweg a_{spart a}auart a_{bstnk a}vbeln b~netwr

into corresponding fields of table t_vbak

up to 100 rows

from ( vakpa as a

inner join vbak as b

on a_{vbeln eq b}vbeln )

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 a_{vbeln a}fkart a_{vkorg a}fkdat

b~netwr

into corresponding fields of table t_vbrk

up to 100 rows

from ( vrkpa as a

inner join vbrk as b

on a_{vbeln eq b}vbeln )

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 a_{vbeln b}matnr b_{arktx b}netwr b~kwmeng

into corresponding fields of table t_vbap

up to 100 rows

from ( vakpa as a

inner join vbap as b

on a_{vbeln eq b}vbeln )

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.

check this also.

u can find BADI's in different ways...

1>First go to any transaction->iN THE menu bar SYSTEM->STATUS->Get the program name ->double click->u will go to the program attached to the tcode.Now search term will be CALL CL_EXITHANDLER.Now u will get list of BADI'S available..

2>Goto SE24->Give class name as CL_EXITHANDLER->Display->double click on get_instance mathod->Now u will go inside the method->Now put break point on the cl_exithandler.Now go to any transaction code and pass dat..U will see that it will be stopped on the break point which u set on the cl_exithandler...In the exit name u can find list of badi's attached to the tcode..

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.

The simplese way for finding BADI is

1. chooes Tcode Program & package for that Tcode.

2. Go to Tcode se18

3. Press F4

4. search by package or by program.

regards.

sowjanya.b