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 Enhancement

Former Member
0 Kudos

Hi folks,

I need some help in BADI development. Having gone through various resources on Search Forums, regarding BADI, need some assistance.

I need to make an enhancement regarding the Fast Entry actions (HR_FAST_ACTION_CHECK). Firslty, I decided to enhance the existing BADI. Hence I created a custom BADI (ZHR_FEFA_CHECK_ZA) followed by the filter type, the interface and the method.

Then using se19, i went on to implement the BADI. Here is the problem. It selects the custom filter type that I created for the BADI but the 'filter value' draws blank. The interface has the implmenting class, method that I created.

Since the filter value is blank, it is resulting in error and I am stuck here. Am I missing something?

I checked in the standard BADI, the filter value runs something like /1PAPAXX/FEFA0000101_0001.

How can this be generated in the custom BADI.

Any thoughts or leads is widely appreciated.

Thanks in advance,

VG

3 REPLIES 3

Former Member
0 Kudos

Hai.

check the example codes.

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.

-


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.

regards.

sowjanya.b

0 Kudos

Thanks for the response.

I got your point of expalnation. I do get the gist of how BADI works. To simplify things, here is what my task is...

I am using an standard BADI -HR_FAST_ACTION_CHECK.

Here is what I am trying to achieve, when I use the tcode PA42 (fast Entry transaction), it lists a series of action types. whenever I choose a particluar action type say (Hire) it takes to the interface table that has all the applicant records, upon performing the hire action it takes to the actions (0000) infotype screen. On the action screen, in the actions (massn) field, I want the same 'Hire action' type that I had chosen on PA42 screen to default on this screen instead of end user choosing from the list of all action types.

Under SPRO, they have mentioned about this BADI to check for Fast entry actions. However I ran the same transaction PA42 using the debugger, to find whether it calls this BADI under the normal circumstances and it did not.

Now, how can I link this bADI to get the desired result? At this point I am little confused.

Any thoughts or leads as how can I move ahead with it would be really helpful.

VG

0 Kudos

I got the BADI working.

VG