Problem in BAdI

Former Member — Thu, 15 May 2008 06:27:25 GMT

Hiii gurus,

If i m having the name of BAdI how do i can get to know that at which point of a program that BAdI will call.

Thanks In Advance.

Re: Problem in BAdI

Former Member — Thu, 15 May 2008 06:32:19 GMT

Hi,

Implement the badi in se19.

put the Break-point in the required methods.

Run the Transaction for which you are required.

Then you can know at which point the Badi is getting Triggered.

Go to SE18 And display the Badi you will find DOcumentation Button on the top Rightside.If the documentation is Available for that badi ,you can read that to know the functionality.

Regards,

Raj.

Re: Problem in BAdI

Former Member — Thu, 15 May 2008 06:33:12 GMT

hi manish,

U can find badi at which point it s clicking by this method.

1. se37.

2. put SXV_GET_CLIF_BY_NAME

3. Put breakpoint on

CALL FUNCTION 'SXV_ADD_PREFIX'

NOW IN OTHER SESSION CALL YOUR T-CODE AND AS U MOVE ON U WILL GET BREAKPOINT THEN CLICK ON NAME.

FROM THIER U CAN GET NAME OF BADI.

PRIYA .

IF HELPFUL REWARD POINTS.

Re: Problem in BAdI

Former Member — Thu, 15 May 2008 06:33:16 GMT

Please go though below details which shows how to find badi. Might be helpful for your requirement:

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.

Re: Problem in BAdI

Former Member — Thu, 15 May 2008 06:33:27 GMT

Hi Manish,

Keep a break point in the BAdI and run the transaction .

u could know where thw BAdI is used.

Best regards,

raam

topic Problem in BAdI in Application Development and Automation Discussions

Problem in BAdI

Re: Problem in BAdI

Re: Problem in BAdI

Re: Problem in BAdI

Re: Problem in BAdI