BAPI & BADI

Former Member — Sat, 23 Feb 2008 09:59:39 GMT

Hi,

Just wanted to know what exactly is BAPI in SAP?

Also if someone can help me understand what exactly is BADI?

Detail meaning will be apreciated.

Re: BAPI & BADI

Former Member — Sat, 23 Feb 2008 10:00:46 GMT

Business Application Programming Interface (BAPI)

Standard R/3 interface that enables you to integrate third-party software into the R/3 System. Business Application Programming Interfaces (also known as Business APIs or BAPIs) are defined in the Business Object Repository (BOR) as methods applied to SAP business objects, in order to perform specific business tasks. BAPIs are implemented and stored in the R/3 System as RFC-enabled function modules in the ABAP Workbench.

BADI stands for Business Add-In.

These are like user exits but are implemented using ABAP Objects. BADI's can be implemented in every stage of the systems landscape. That means there are more than SAP and Customer specific views, but also country or language specific views.

Expecting more details from experts

Re: BAPI & BADI

Former Member — Sat, 23 Feb 2008 12:48:48 GMT

to get a practical example of a bapihere is a link

www.erpgenie.com/abap/bapi/example.htm

what are bapis?

Business Application Programming Interfaces (BAPIs) enable access to SAP functions across formal, stable and dialog-free interfaces. These interfaces can be used by external applications developed by customers and complementary software partners as well as by other SAP applications.

BAPIs are defined as API methods of SAP Business Object Types. These object types are used within the Business Framework to enable object-based communication between components. Business objects and their BAPIs enable object orientation to be used in central information processing in companies. For example, existing functions and data can be reused, trouble-free technical interoperability can be achieved, and non-SAP components can be implemented.

Applications can use BAPIs to directly access the application layer of the R/3 System and, as clients, applications can use the business logic of the R/3 System. BAPIs provide the client with an object-oriented view of the application objects, without needing to know the implementation details.

BAPIs are always developed by defining scenarios. These scenarios are used to map and implement system-wide business processes.

Target Group for Documentation

This documentation describes the guidelines SAP uses for developing and implementing BAPIs to ensure that the development of BAPIs is as standard as possible. These standards make BAPIs easy to use.

This programming guide is targeted at SAP developers, partners and customers who want to implement BAPIs.

This documentation has been written for Release 4.6C. Unless stated otherwise, these guidelines also apply to Releases back to and including 4.0.

http://help.sap.com/saphelp_46c/helpdata/en/43/b46c4853c111d395fa00a0c94260a5/frameset.htm

Designing the BAPI

After the scenario and the business object types and BAPIs used in it have been identified in the analysis, the BAPI signature is defined conceptionally within the design phase. The content should be described and the parameter names and the parameter structure must be defined.

Because BAPIs are business interfaces and not technical interfaces, when you develop a BAPI, you must fulfil the central requirement that:

A user must be able to implement a BAPI call correctly in an external application, using only their knowledge of the application and the BAPI documentation. Users are not expected to have any knowledge of R/3, so that they can view the R/3 System as a "black box".

In this phase you also have to decide from the BAPI's functions whether the BAPI is an instance method or a class method and whether it can be implemented as a Standardized BAPI.

Instance methods refer to a specific instance of a business object type, for example, the BAPI SalesOrder.GetDetail retrieves the details of precisely one sales order. These methods are defined as instance-dependent in the BOR.

Class methods do not refer to a specific instance of a business object type, for example, the BAPI SalesOrder.GetList supplies a list of all the existing sales orders that match specific criteria. Standardized create methods also belong to class methods. A create method creates a new instance, for example, the BAPI SalesOrder.Create creates a new sales order in the R/3 System. These methods are defined as instance-independent in the BOR.

The specific instances of a business object type are identified by their key fields , which is why they play a special role in this context. In the design phase, the keys of instance-dependent BAPIs should be identified as special parameters. For more details see Defining the Interface.

When designing the BAPI signature you should keep in mind:

The design of the method (BAPI) and the parameters must comply with certain conventions See also Conventions.

There are a range of standard methods and parameters that provide basic functions. If the BAPIs and their parameters fall into this category, they must be structured according to specified rules. For an overview see Standardized BAPIs and Standardized Parameters.

So that the signature is clearly structured and easy to use, you should follow the Design Recommendations.

http://help.sap.com/saphelp_46c/helpdata/en/43/b46c4853c111d395fa00a0c94260a5/frameset.htm

implementing a bapi

Once you have completed the conceptual design of the BAPI, information specific to SAP must now be considered in the implementation phase. For example, the SAP data structures are determined and the program logic is implemented for the BAPI parameters.

The following documentation provides an overview of the implementation process and the relevant components and tools for the BAPIs are introduced. Each work step is then described in detail.

http://help.sap.com/saphelp_46c/helpdata/en/43/b46c4853c111d395fa00a0c94260a5/frameset.htm

follow the limk for detailed information

http://help.sap.com/saphelp_46c/helpdata/en/43/b46c4853c111d395fa00a0c94260a5/frameset.htm

BADI

SAP Business Add-Ins (BAdIs) are one of the most important technologies used to adapt SAP software to specific requirements. BAdIs were introduced with Release 4.6 and replace function module exits. This technology is not limited to SAP applications. BAdI calls can be integrated in customer applications. These can then be enhanced by other customer applications. In the various SAP applications, BAdI calls are implemented at places where enhancements are appropriate.

getting started

Introducing Business Add-Ins (PDF 219 KB)

SDN Contributor Aveek Ghose introduces the original BAdi concepts.

Implementing a BAdI in an Enhancement Project (CMOD) (PDF 233 KB)

This article by SDN Contributor Glen Spalding demonstrates older BAdI techniques.

How to Define a New BAdI Within the Enhancement Framework

This blog is part three of the series on the new Enhancement Framework and shows you how to define a new BAdI in the new Enhancement Framework. You learn how to create a BAdI with the respective tools in the ABAP Workbench, how to use the relevant commands in ABAP, and how to provide a default class for a BAdI.

the link is

https://www.sdn.sap.com/irj/sdn/nw-development?rid=/webcontent/uuid/2342e1f3-0b01-0010-a186-fdd404884050 [original link is broken]

do reward if helpful

topic Re: BAPI & BADI in Application Development and Automation Discussions

BAPI & BADI

Re: BAPI & BADI

Re: BAPI & BADI