Now you can learn ABAP by watching and listening video classes by experienced consultant.
Read, Surf and Download useful ABAP tips, tutorials, code and download many eBooks and documents free
Get all latest opening for SAP ABAP and related jobs, vaccancies across India and apply for the same.
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 you 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. It is not possible to connect SAP to Non-SAP systems to retrieve data using RFC alone. RFC can access the SAP from outside only through BAPI and same is for vice versa access. RFC is the protocol used by SAP for remote communication, that is, for communications between remote (independent) systems.
RFC is used for communications between two independent SAP systems, or for communications between an SAP system and a non-SAP system, such as an external application. It can also be used for communications between modules on the same system.
Using the RFC interfaces you can extend the functionality of R/3 applications from an external program.
BAPI has it's corresponding RFC function module where as vice versa is not possible.
We can call BAPI as Remote Enabled Function Module and Call as the method of Business Object in the BOR, where as RFC can be called as Remote Enabled Function Module only. BAPI has no User dialog and Exceptions.
Whenever possible, a standardized BAPI must be used in preference to an individual BAPI. It is not possible to connect SAP to Non-SAP systems to retrieve data using RFC alone. RFC can access the SAP from outside only through BAPI and same is for vice versa access. RFC is the protocol used by SAP for remote communication, that is, for communications between remote (independent) systems.
RFC is used for communications between two independent SAP systems, or for communications between an SAP system and a non-SAP system, such as an external application. It can also be used for communications between modules on the same system.
Using the RFC interfaces you can extend the functionality of R/3 applications from an external program.
BAPI has it's corresponding RFC function module where as vice versa is not possible.
We can call BAPI as Remote Enabled Function Module and Call as the method of Business Object in the BOR, where as RFC can be called as Remote Enabled Function Module only. BAPI has no User dialog and Exceptions.
