topic Re: Diffrence between RFC and BAPI? in Application Development and Automation Discussions

Diffrence between RFC and BAPI?

Former Member — Mon, 12 Nov 2007 02:45:14 GMT

Hi,

Diffrence between RFC and BAPI?

Early reply is highely appriciable.

Regards,

Chow

Re: Diffrence between RFC and BAPI?

Former Member — Mon, 12 Nov 2007 03:06:44 GMT

Hi,

Check below link

http://www.sap-img.com/fu026.htm

Regards,

Atish

Re: Diffrence between RFC and BAPI?

Former Member — Mon, 12 Nov 2007 04:35:01 GMT

Check the links -

Remote Function Call:

RFC is an SAP interface protocol. Based on CPI-C, it considerably simplifies the programming of communication processes between systems.

RFCs enable you to call and execute predefined functions in a remote system - or even in the same system.

RFCs manage the communication process, parameter transfer and error handling.

http://help.sap.com/saphelp_47x200/helpdata/en/22/042860488911d189490000e829fbbd/frameset.htm.

BAPI

BAPI stands for Business API(Application Program Interface).

A BAPI is remotely enabled function module

ie it can be invoked from remote programs like standalone JAVA programs, web interface etc..

You can make your function module remotely enabled in attributes of Function module but

A BAPI are standard SAP function modules provided by SAP for remote access.

Also they are part of Businees Objest Repository(BOR).

BAPI are RFC enabled function modules. the difference between RFc and BAPI are business objects.

You create business objects and those are then registered in your BOR (Business Object Repository)

which can be accessed outside the SAP system by using some other applications (Non-SAP) such as VB or JAVA.

In this case u only specify the business object and its method from external system

in BAPI there is no direct system call. while RFC are direct system call.

Some BAPIs provide basic functions and can be used for most SAP business object types.

These BAPIs should be implemented the same for all business object types.

Standardized BAPIs are easier to use and prevent users having to deal with a number of different BAPIs.

Whenever possible, a standardized BAPI must be used in preference to an individual BAPI.

Technically, not much difference at all. They are both remote enabled functions that can be accessed from outside of SAP (to be more technically correct, from outside of the ABAP stack).

From a usage/functional perspective however, BAPIs are a little bit more special from RFCs.

BAPIs:

- are designed as the methods of business objects in the business object repository (accessable using transaction BAPI or SWO1)

- have non-technical parameter names (the technical field names in SAP are mapped)

- have a fixed interface and functionality across all SAP releases (this is probably the key point as it means you can develop integrations with them which do not need to be changed when you upgrade)

Generally, if you are trying to find a function for a particular requirement you should look for a BAPI first, then for a RFC function which has a released status (check the function attributes in SE37), and then just a normal RFC last.

The benefit of an RFC function with released status means that it also has a fixed interface which will not change with new SAP releases.

An RFC, or Remote Function Call, describes an external interface to a system function module available in SAP. For example, getting the system parameters is a system function available via RFC.

An BAPI, or Business Application Programming Interface, is an RFC-enabled function module that provides external access to an SAP business application such as creating a sales order.

In effect, all BAPIs are RFCs but there are a superset of RFCs that are not considered BAPIs. Really, two sides of the same coin.

CHECK THIS URL :

http://www.ask.com/web?q=WhatisthedifferencebetweenRFCandBAPIin+ABAP&qsrc=119&o=333&l=dir