Enhancing Business Content: Why BAdIs Are the Better Choice

  • by Anurag Barua, Independent SAP Advisor
  • February 1, 2006
When working with standard extractors delivered as part of SAP BW business content, you may have had to execute several requests to enhance standard functionality in these extractors. You have probably used SAP user exit RSAP0001, but a Business Add-In (BAdI) may work better. See why and how to use BAdIs.
Key Concept

As part of its business content, SAP delivers several standard extractors in SAP source systems. These extractors, when implemented as part of the process of installing DataSources from business content, enable you to extract data from your desired application. Often, users need to enhance these standard extractors to meet the specific needs of their business or the application area. The process is well documented. To quickly recap: In the source system, you activate your DataSource, analyze it, and find that you need to enhance it. You edit the DataSource via transaction RSA6 where you add (using an append structure) the fields you feel are missing from SAP’s standard extract structure. You populate these fields using SAP user exit RSAP0001.

Since R/3 Release 4.6C, SAP has recommended using Business Add-Ins (BAdIs) rather than user exits as a more efficient way to enhance SAP standard content. Despite this fact, most experienced SAP professionals still employ user exits in even the latest releases (R/3 Enterprise and mySAP ERP). In addition, SAP sometimes suggests user exits even when corresponding BAdIs exist, especially to enhance standard SAP extractors.

For example, consider the conventional way of populating newly added fields in the extract structure by adding the required code in SAP user exit RSAP0001. A BAdI has been available to do the same thing since the release of Basis 6.20 and PI_BASIS_2004_1 plug-in. The technical name of this BAdI is RSU5_SAPI_BADI. Unfortunately, despite several advantages that it provides over user exit RSAP0001, the latter is still very popular even among implementations that are on or above Basis 6.20 and plug-in PI_BASIS_2004_1.

Based on my experience, SAP professionals are unfamiliar with and therefore under-use the BAdI RSU5_SAPI_BADI. In this article, I’ll briefly talk about the concept of a BAdI and its advantages and drawbacks. Then I’ll provide a detailed overview of how to use BAdI RSU5_SAPI_BADI and walk you through the steps of implementing this BAdI to enhance existing extractor functionality.

Anurag Barua

Anurag Barua is an independent SAP advisor. He has 23 years of experience in conceiving, designing, managing, and implementing complex software solutions, including more than 17 years of experience with SAP applications. He has been associated with several SAP implementations in various capacities. His core SAP competencies include FI and Controlling FI/CO, logistics, SAP BW, SAP BusinessObjects, Enterprise Performance Management, SAP Solution Manager, Governance, Risk, and Compliance (GRC), and project management. He is a frequent speaker at SAPinsider conferences and contributes to several publications. He holds a BS in computer science and an MBA in finance. He is a PMI-certified PMP, a Certified Scrum Master (CSM), and is ITIL V3F certified.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.