Create a BAPI?

[Former Member]

Why it is required to Create a BAPI?

[Former Member]

Programming a BAPI consists of some tasks like:

• Defining BAPI Data structures ( using SE11 )

• Creating BAPI Function Modules (For each method)

• Defining BAPI Methods in the BOR

• Generate and release

1. Defining BAPI Data structures: This is the basic step followed while creating BAPIs. All the relevant structures that are required for BAPI have to be created using T-Code SE11. The structures can be created for Import/Tables parameters.

2. Creating BAPI Function Modules: We must create new function group for each BAPI. If the BAPIs are related then the same can be grouped under the same FUNCTION GROUP to enable the sharing of global data amongst the related BAPIs.

3. Defining BAPI Methods in the BOR: When creating a new object type in BOR (Business Object Repository), there can be two possibilities. Either it is created as a subtype of an existing business object or it is created as a new business object from scratch. Create a business object using the T-Code SWO1. The business object gets created with the standard interface that contains an Interface IFSAP, an Attribute ObjectType, and two methods namely ExistenceCheck and Display. All these cannot be changed. You can add a method to the business object. For this, we will choose from the menu path, Utillities -> API methods -> Add method. To use the business object Object type status has to be set to Implemented.

4. Generate and Release: Go to SE37 and release the API enabled Function module. In the Object created in the BOR, set the status of Object Type Component to Released.

You can then display the BAPI in the BAPI Explorer. Invoke the same using the T-code BAPI.

Also have a look at below links.

http://www.sappoint.com/abap/bapiintro.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE8/BCFESDE8.pdf

http://help.sap.com/saphelp_nw04/helpdata/en/a5/3ec9f74ac011d1894e0000e829fbbd/frameset.htm

http://www.allsaplinks.com/bapi.html

http://www.allsaplinks.com/bapi_example.html

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

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

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

I hope it helps.

Best Regards,

Vibha

*Please mark all the helpful answers

[Former Member]

Hi Vibha.

Thanks for your reply. I know how to create BAPI.

My Qs is 2.

Why it is required to create a BAPI?

[Former Member]

BAPI is a Interface providing access to processes and data in business application systems such as R/3.

BAPIs are described and stored in Business Object Repository (BOR). To use BAPI, application program only needs to know method’s interface definition.

Sometimes the required customised functionality is not provided by sap, then in that case you need to create BAPIs.

Some Advantages of using BAPIs instead of FM are -

Business Standard – SAP business objects and their BAPIs provide a business content standard, rather than a technical interoperability standard.

Standards Conformance – SAP business objects and their BAPIs can be accessed by using object-oriented interfacing technologies.

Stability and Downward Compatibility – BAPIs interface definition and implementation remain stable in long term.

Object Orientation - BAPIs provide access to R/3 data and processes following an object-oriented programming model.

Openness – BAPIs can be accessed from all developmental platforms that support SAP Remote Function Call protocol.

I hope it helps.

Best Regards,

Vibha

Please mark all the helpful answers

[Former Member]

HI,

BAPIs can be called within the R/3 System from external application systems and other programs. BAPIs are the communication standard for business applications. BAPI interface technology forms the basis for the following developments:

Connecting:

New R/3 components, for example, Advanced Planner and Optimizer (APO) and Business Information Warehouse (BW).

Non-SAP software

Legacy systems

Isolating components within the R/3 System in the context of Business Framework

Distributed R/3 scenarios with asynchronous connections using Application Link Enabling (ALE)

Connecting R/3 Systems to the Internet using Internet Application Components (IACs)

PC programs as frontends to the R/3 System, for example, Visual Basic (Microsoft) or Visual Age for Java (IBM).

Workflow applications that extend beyond system boundaries

Customers' and partners' own developments

Reward points if helpful.

Thanks and regards,

Narayana.