BAPI

[Former Member]

Can anyone explain me why BAPIs are used.How it can be created?

Urgently Required..

[Former Member]

Hi

BAPIs (Business Application Programming Interfaces) are the standard SAP interfaces. They play an important role in the technical integration and in the exchange of business data between SAP components, and between SAP and non-SAP components. BAPIs enable you to integrate these components and are therefore an important part of developing integration scenarios where multiple components are connected to each other, either on a local network or on the Internet.

BAPIs allow integration at the business level, not the technical level. This provides for greater stability of the linkage and independence from the underlying communication technology.

BAPI is a Remote enabled function module.

Just follow this simple procedure or steps to create a BAPI.

1. Defining BAPI Data structures in SE11

2. Program a RFC enabled BAPI function module for each method

3. Create a Business object for the BAPI in the BOR

4. Documentation the BAPI

5. Generate ALE interface for asynchronous BAPIs

6. Generate and release

IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an

asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.

While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.

There are basically two types of IDOCs.

Basic IDOCs

Extended IDOCs

Idoc Components

Basic Idoc

Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.

Extension Idoc

Extending the functionality by adding more segments to existing Basic IDOCs.

<b>Reward points for useful Answers</b>

Regards

Anji

[Former Member]

Hi,

If you are talking about RFC then you can create them in SE37..

If you are talking about business object then check this link

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

Thanks

Naren

[Former Member]

https://forums.sdn.sap.com/click.jspa?searchID=3173058&messageID=2531053

[Former Member]

Hi Ditty,

Welcome to SDN :).

BAPI's are used to load data into SAP system. They are not created mostly. They are the standard SAP FM.

Please let us know as for which purpose you are looking the BAPI so that we can tell you the exact BAPI to be used.

Reward points if useful.

Regards,

Atish

[Former Member]

Hi,

Business Application Program Interfaces allow developers to integrate third-party software into SAP's R/3 product. BAPI is one of a set of tools at your disposal for interfacing with an SAP R/3 system. It’s important to understand its role among them, and to have an idea of what each does in relation to the other.

This stand-alone program is, in essence, the toolbox you carry with you as a hands-on SAP consultant. Its contents give you access to SAP R/3’s objects. All the information you need for setting up remote function calls from outside SAP is found here. Most importantly, SAP Assistant holds your set of keys to SAP’s business objects, allowing you access to what’s there, and enabling you to create what you need.

BAPI is ultimately a mechanism for getting data out of SAP R/3. If a BAPI is a ship pushing a barge (data), the engine of that ship is a Remote Function Call (RFC). An RFC is a function module in a system that is called from some other system. This, of course, covers a great deal of ground. The two systems can both be SAP, or they can be different platforms, or an RFC may be used on the spot in real time by any party making an inquiry of an SAP system from the outside (including you, sitting at your laptop).

An RFC is the means by which the business object represented by a BAPI is implemented. A BAPI is a business object; an RFC is functional code.

A great deal goes on in the Business Object Repository (BOR), and you must know it well. It’s not overstating the case to say that the BOR is the core of SAP. If an SAP R/3 system can be described as the animation of otherwise lifeless data, the BOR describes the living cells of this new body. Cells come in many different types, and that’s what the BOR holds: all the different types of data comprising an SAP system of databases.

The BOR’s contents essentially define the implementing company’s business model. The information it holds includes the definitions of all business objects internal to the company, as well as the defining information of all interfaces to other companies.

Check out the links

Step by step guide

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/snippets/bapi+step-by-step&;

http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html

http://help.sap.com/saphelp_nw04/helpdata/en/e0/9eb2370f9cbe68e10000009b38f8cf/frameset.htm

http://help.sap.com/saphelp_46c/helpdata/en/7e/5e115e4a1611d1894c0000e829fbbd/frameset.htm

Hope this helps.

Regards,

Richa