Bapi's are nothing but RFC enabled function module.......

and the main differenc e b/w RFC & BAPI is that BAPI is maintained in BOR(business object repository)... BAPI is nothing but a method of SAP Business Objects that has the data and busin ess process in the R/3 system. Technically BAPI is a remote enabled Fm but BAPI is basically a method of a busi ness object which is called as a method in an outside system. RFC is an enables function module that can be used to implement the BAPI as a me thod, when enabling the link to the external application using the ALE-Application Ena bling Link. RFC is the protocol used to call functions in an R/3 system by a caller external to R/3 or to call programs external to R/3 from an R/3 system. BAPI methods are RFC enabled function modules. The difference between RFc and BA PI 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 sys tem in BAPI there is no direct system call. while RFC are direct system call.Some BAPIs provide basic functions and can be u sed for most SAP business object types. These BAPIs should be implemented the same for all bu siness object types. Standardized BAPIs are easier to use and prevent users having to deal with a num ber of different BAPIs. BAPI is having all Key fields, methods, interfaces etc.

We can develope RFC & BAPI also. One more difference between RFC & BAPI is: Through RFC, there is direct System Call; whereas there is no direct system calls in case of BAPI. Bapi can't handle exceptions , the calling program has to handle it whereas RFC fm can handle it. every BAPI is a RFc whereas every RFC is not a BAPI. Rfc enabled are basically for sap systems whereas BAPI are for non sap systems like i want to acess data via java or vb.