BADI

[Former Member]

Hi Friends,

I want to know about BADIs. How they helps in a report generation? How the virtual keyfigures finds data using BADIs and all.

Hope you people will give me a detailed scenario...

Thanks and Regards'

Obily B W

[former_member189638 · Accepted solution]

For creating Virtual Key Fig in BADI you need to go to transaction <b>SE19</b>

In this transaction you can create a new or display the existing <b>BADI</b>.

There you can see two tabs

The <b>Attribute Tab</b> we need to give the name of the Multiprovider on which the query with the virtual key fig is getting executed.

The <b>Inerface Tab</b> has three following sections. Need to write the ABAP code for al the three.

<b>Define</b> : Defind all the characteristics and virtual key fig that will be used for virtual Key Fig calculation

<b>Initialize</b> : Initialize them

<b>Compute</b> : Here you will have to write the logic for calculating the virtual key fig.

[former_member228339]

Hi,

Customers with particular requirements for copying control can enhance the conditions according to their wishes. You have the option of writing your own data transfer routines using BADi (business add-in) methods.

A Business Add-In (BAdI) is an enhancement of the well-known user exit that you can use in BW 2.x and higher, as well as in SAP R/3 4.6. Despite having been available for a few years, BAdIs are not well known or used a lot. This is likely to change, given SAP's approach toward using BAdIs from SAP BW 3.0 on. For example, SAP recommends the use of BAdIs with the transformation library in BW 3.x.

If you are part of a functional team, you might never work directly with a BAdI. Nonetheless, it is important to know about this system feature so you understand how it might be used in the appropriate situation. BAdIs give technical teams more flexibility in using the same ABAP code (BAdI) for different levels of the company. For example, you could use the same code for each country during a global rollout. With a user exit, new code would be required for each country.

To review, user exits are points in the SAP program code where you can add a custom program to derive and exchange (upload, download, change, and so on) data with the standard SAP program, thus extending the functionality of standard SAP. In BW, user exits are used mainly in routines that are part of transfer and update rules.

BAdIs do not make user exits obsolete. Your existing user exits will still work after an upgrade as long as none of the objects (e.g., fields and tables) the program uses have changed. You also do not have to open an SAP Software Change Registration (SSCR). The same holds true of BAdIs after an upgrade.

Virtual keyfigures are those derived from a calculation dynamically at the runtime