Interface comparison with SAP integration: Differences between IDOC BAPI RFCs

Se37 write called function, which can be remotely called rfc,remote-enabled FUNCTION,ABAP syntax and input and output parameters will have some limitations. BAPI is an RFC for specific business operations done by SAP. IDoc is a way to exchange document data based on SAP's own XML-like format. The RFC must be called online in a way that is generally synchronous, idoc-based documentation that can be implemented asynchronously.

IDoc is a way to exchange document data based on SAP's own XML-like format. The RFC must be called online in a way that is generally synchronous, idoc-based documentation that can be implemented asynchronously.

IDoc is the use of message delivery between systems, not involving the underlying function calls, IDOC processing is done with EDI.
As you can understand, IDOC is a data structure used by SAP for different client communication with external systems or internally, and different idoc types define different formats, such as IDoc, BOM, PO,SO, etc. related to material master data, , ALE is mainly used for internal data exchange, such as different client, EDI for the exchange of data with external systems, they are essentially base on IDOC ... IDoc is a way to exchange document data based on SAP's own XML-like format. IDoc is document-based and can be implemented asynchronously.

RFC is process-oriented, simple and straightforward to call;
BAPI is object-oriented, with attributes, methods, events, complexity and richness that reflect SAP's business applications, and
The construction of the BAPI method is RFC-based, and you can also assume that the BAPI encapsulates the RFC
I think the RfC is the most flexible to use.
IDOC is the SAP standard file Exchange format, and SAP already has a number of function module to handle and pass IDOC, especially
is to exchange data with other systems, with some systems such as BizTalk Server,idoc will appear very convenient, open
The workload of the hair is also minimal.
RFC, if it is used with the BDC of SAP, or if you are a master of ABAP, the RFC is very flexible.
As for BAPI, I think the BAPI concept of sap is very good, but the interface is very imperfect, many data can not be through the SAP itself
BAPI finished, you have to do the development.
For BAPI and RFCs, I don't think it's conclusive.
Sometimes the BAPI is easy to use and sometimes the RFCs are useful.
BAPI is easy to use, its efficiency is relatively high, this is mainly reflected in some BAPI is the way direct input is written,
High efficiency.
But if you write with the RFC also has his advantage, when you write not only a LUW, and each LUW is relatively simple,
In this case it is faster to develop with RFC.
The IDoc file for SAP replaces the role of EDI files.
Ale is a mode of communication.
BAPI, a function that SAP provides a whole bunch of processing for major business processes
RFC, a function that is used with external programs to invoke

It should be said that the RFC is the basis of other content, it is a function module, can be called remotely. and BAPI itself is a
RFC, but it has been used as a interface of Bo, and has a further role to play, in addition to what is mentioned in the BAPI documentation.
The basis for the development of Ale/idoc.
Ale is the application layer data exchange between R/3 systems, as for what to use, depending on the configuration, such as can be used idoc, synchronous/
asynchronous BAPI, even with EDI. Non-SAP systems cannot be implemented with ale.
As for the way of data transmission, can be idoc (the bottom is the RFC to the actual), also can be EDI, so said Idoc/edi real
Is the carrier of the data.

Interface comparison with SAP integration: Differences between IDOC BAPI RFCs