Hi,
BAPIs are standardized programming interfaces (methods) enabling external applications to access business processes and data in the R/3 System.
BAPIs provide stable and standardized methods to achieve seamless integration between the R/3 System and external applications, legacy systems and add-ons.
BAPIs are defined in the BOR(Business object repository) as methods of SAP business object types that carry out specific business functions.
BAPIs are implemented as RFC-enabled function modules and are created in the Function Builder of the ABAP Workbench
Standardized BAPIs
BAPIs for Reading Data
GetList() , GetDetail() , GetStatus() , ExistenceCheck()
BAPIs for Creating or Changing Data
Create() or CreateFromData(),Change(),Delete() and Undelete() ,
Cancel() ,Add<subobject> and Remove<sub-object>
BAPIs for Mass Processing
ChangeMultiple(), CreateMultiple(), DeleteMultiple().
BAPIs for Replicating Business Object Instances Replicate() and SaveReplica()
ALE
PURPOSE
ALE supports the distribution of the business functions and process across loosely coupled R/3 systems. Connections from R/2 and non SAP systems is also supported.
IMPLEMENTATION CONSIDERATIONS
Distributing business applications and at the same time ensuring data consistency is practical because:
The increasing globalization of markets has led to the physical division of organizational units.
Business processes are not restricted to one organization only and an increasing number of customers and vendors are involved.
The performance of an R/3 System can be improved by distributing the business applications.
FEATURES-
ALE supports:
Distribution of applications between different releases of R/3 Systems
Continued data exchange after a release upgrade without requiring special maintenance
Customer-specific extensions.
Communication interfaces that allow connections to non-SAP systems.
Coupling of R/3 and R/2 Systems.
ALE has functions for controlling messages flows (Audit) and for eliminating malfunctions.
Thanks
reward if useful
