Difference Between BAPI and RFC Function Module in SAP

Difference Between BAPI and RFC Function Module in SAP

From this tutorial ,we will learn what is the difference BAPI and RFC in SAP?BAPI and RFC definitions.

IBAPIs are standardized programming interfaces (methods) enabling external applications to access business processes and data in the R/3 System.

BAPIs provide stable and standardized methods to achieve seamless integration between the R/3 System and external applications, legacy systems and add-ons.

BAPIs are defined in the BOR(Business object repository) as methods of SAP business object types that carry out specific business functions.

BAPIs are carried out as RFC-enabled characteristic modules and are created within the Function Builder of the ABAP Workbench.

The most critical difference btwn BAPI and FM is that BAPI can be wrapped in Business objects whereas RFC cant.

The following standardized BAPIs are provided:

Reading times of SAP commercial enterprise objects

GetList ( ) With the BAPI GetList you could select a range of object key values, as an example, organization codes and material numbers.

The BAPI GetList() is a class method.

GetDetail() With the BAPI GetDetail() the details of an example of a enterprise item kind are retrieved and back to the calling software. The instance is identified via its key. The BAPI GetDetail() is an instance approach. BAPIs which could create, trade or delete times of a commercial enterprise object type

The following BAPIs of the equal object type must be programmed so that they can be called several times within one transaction. For example, if, after income order 1 has been created, a 2nd sales order 2 is created inside the same transaction, the second one BAPI name ought to not affect the consistency of the sales order 2. After completing the transaction with a COMMIT WORK, each the orders are saved consistently in the database.

Delete( ) and Undelete( ) The BAPI Delete() deletes an example of an SAP business item type from the database or sets a deletion flag.

The BAPI Undelete() eliminates a deletion flag. These BAPIs are example methods.

Cancel ( ) Unlike the BAPI Delete(), the BAPI Cancel() cancels an example of a enterprise object type. The instance to be cancelled stays in the database and an extra instance is created and that is the only that is sincerely canceled. The Cancel() BAPI is an instance technique.

Create( ) and CreateFromData! ( )

The BAPIs Create() and CreateFromData() create an example of an SAP commercial enterprise object kind, for example, a purchase order. These BAPIs are class techniques.

Change( )

The BAPI Change() adjustments an present instance of an SAP enterprise object kind, for example, a purchase order. The BAPI Change () is an instance approach.

Add<subobject> ( ) and Remove<subobject> ( ) The BAPI Add<subobject> adds a subobject to an existing item inst! Ance and the BAPI and Remove<subobject> removes a subobject from an object instance. These BAPIs are example strategies.

BAPI are RFC enabled characteristic modules. The difference among RFc and BAPI are commercial enterprise objects. You create business items and people are then registered in your BOR (Business Object Repository) which may be accessed outdoor the SAP gadget through the usage of a few other applications (Non-SAP) which include VB or JAVA. In this example u best specify the commercial enterprise item and its approach from external gadget in BAPI there is no direct machine name. While RFC are direct gadget name Some BAPIs provide simple capabilities and may be used for most SAP commercial enterprise object types. These BAPIs need to be applied the equal for all business object sorts. Standardized BAPIs are easier to apply and prevent customers having to deal with a number of exceptional BAPIs. Whenever viable, a standardized BAPI must be used in choice to an character BAPI.
RFC

A remote function call is a call to a function module running in a system different from the caller's. The remote function can also be called from within the same system (as a remote call).

RFC consists of two interfaces : A calling interface for ABAP Programs and a calling interface for Non-SAP programs.

The RFC Interface takes care of :-

- Converting all parameter data to the representation needed in the remote system

Calling the communication routines needed to talk to the remote system.

Handling communications errors, and notifying the caller, if desired ( using EXCEPTIONS paramater of the CALL FUNCTION).
End