Hi Purna,
Technically, not much 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.
Hope that helps.
Cheers,
Brad
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.