The basis for all communication between SAP and external components (as well as for most communication between SAP components) is the Remote Function Call (RFC) protocol. Most client programs want to use regular, Synchronous RFC (sRFC), but SAP also supports Transactional RFC (tRFC) and Queued RFC (qRFC). tRFC is used mainly to transfer ALE Intermediate Documents (IDocs).
ABAP Function Modules can only be called from an external client if they are marked as RFC-enabled. R/3 contains several thousands of such RFC-enabled Function Modules (RFMs). Amongst them are the BAPIs. BAPIs are RFMs that follow additional rules and are defined as object type methods in SAP's Business Object Repository (BOR).
Most BAPIs are released RFMs, only very new ones may be unreleased at first for testing before the releasing. On the other hand, there are quite a few extremely useful RFMs that are not officially released for customer use. (From sap.com)
[@more@]来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/8433094/viewspace-965613/,如需转载,请注明出处,否则将追究法律责任。
转载于:http://blog.itpub.net/8433094/viewspace-965613/
本文介绍了SAP系统中用于内外部组件间通信的基础协议——远程函数调用(RFC)。详细探讨了同步RFC(sRFC)、事务性RFC(tRFC)及队列RFC(qRFC)的不同用途,并解释了如何通过标记使ABAP函数模块对外可用。

被折叠的 条评论
为什么被折叠?



