‎2008 Apr 09 5:24 PM
Hi ALL,
Can u pls help me out with the following queries?
1. how can we handle exceptions in BAPI?
2.wats the major/important differences between BAPI and RFC?( im really confused)
Pls help me out!!!
<REMOVED BY MODERATOR>
Jack
Edited by: Alvaro Tejada Galindo on Apr 9, 2008 5:51 PM
‎2008 Apr 09 5:34 PM
Hi,
BAPI is also a RFC only but it should be add in API method
BAPIs will use in Workflow main purpose using BAPIs we can pull and push the data from R/3 to 3rd party systems.
RFCs are useful in between different servers same environment.
Thanks
Ganesh
‎2008 Apr 09 5:36 PM
BAPI is a subset of RFC.
BAPI is a remote enabled function module.
With out RFC BAPI can not itself be invoked from a different system. It requires RFC to make remote calls.
You can hadle the exceptions of BAPI similar to that of a normal FM.
Go to SE37 and give BAPI_*. It would display available BAPI FM. Click display and check any BAPI. You would see it having import , export etc parameters.
When a BAPI is used data doesn't get stored in database. You have to also use BAPI_COMMIT module following the BAPI which you used only then data gets stored.
You can find error or warning messages in BAPI RETURN structure.
Hope it helps.
Thanks
‎2008 Apr 09 10:57 PM
Hi Jack,
BAPI stands for Business Application Programming Interface. It is a library of functions that are released to the public as an interface into an existing SAP system from an external system.
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.
Functions can only be called via RFC, if they are tagged as RFC functions in the SAP development workbench. They are then called RFC function modules. BAPIs are complete sets of (BAPI) function modules that model a business application.
When you are familiar with web developments: RFC can be compared to HTTP and BAPIs are CGI applications.
In other words: A BAPI function is a function module that can be called remotely using the RFC technology.
Thanks,
Greetson