Glossary

ABAP/4: SAP's 4GL for R/3.
ALE: SAP's Application Link Enabling technology that provides distributed processing for R/3 systems and third-party systems through the broadcast and guaranteed delivery of IDOCs to their appropriate destination(s).
ALE Inbound: The BEA eLink Adapter for R/3 component that processes and submits inbound IDOCs to R/3 for ALE processing.
ALE Outbound: The BEA eLink Adapter for R/3 component that receives and processes outbound IDOCs from R/3.
BAPI: SAP's Business Application Programming Interface, which provides remotely-callable RFCs (methods) that are associated with R/3 Business Objects.
BDC: SAP's Batch Data Control, which processes screen-oriented data in transactions.
BDC Transaction Executor: The BEA eLink Adapter for R/3 component that allows non-R/3 application to submit BDC data to R/3.
BO: SAP Business Object framework that provides an object-oriented model of the enterprise. For example, a Sales Order is represented in R/3 as a Business Object.
BOR: SAP's Business Object Repository that contains the definitions of R/3 Business Objects and their associated BAPIs.
FML: BEA's Field Manipulation Language, a type of message buffer in ATMI. In BEA eLink Adapter for R/3 documentation, FML always refers to FML32.
IDOC: SAP's Intermediate Document (a flat file record of data) that is distributed via ALE.
R/3: SAP's client-server product that provides access to the SAP system via a three-tier architecture consisting of database, application, and presentation components.
RFC: SAP's Remote Function Call interface that allows non-R/3 systems to invoke remotely callable ABAP/4 functions.
RFC Inbound: The BEA eLink Adapter for R/3 component that allows non-R/3 applications to execute RFC-enabled APAB/4 functions.
RFC Outbound: The BEA eLink Adapter for R/3 component that allows R/3 to access data and functionality in non-R/3 applications.
SAPGUI: SAP's graphical user interface utility.
TID: Transaction ID for tracking IDOC transactions.