Difference between ALE vs BAPI.

[ramesh_kajuru]

Dear Experts,

Please brief the differences between ALE & BAPI.

In a business requirement when should i suggest to go for ALE / BAPI ?

Many Thanks

Ramesh.

[Former Member]

This message was moderated.

[Former Member]

This message was moderated.

[Former Member]

This message was moderated.

[uwe_schieferstein]

Hello Ramesh

ALE asynchronously links different systems by sending/receiving IDocs. The IDocs may be processed in the receiving system via BAPIs or other means (e.g. BDC / CALL TRANSACTION).

BAPIs enable you to access SAP business objects on remote systems via RFC. The BAPI call is synchronous, i.e. you expect an immediate response from the remote system.

The BAPI call will fail if the remote system is not available. In contrast, the IDoc processing (ALE) will wait until the remote system is available again and then the message is delivered.

Regards

Uwe

[Former Member]

hi,

ALE uses the asynchronous calls based on idoc structures,

However in the distribution model of ALE can also be used BAPIs. They will then automatically converted into IDOC structures. After creating the IDOCs they will be passed over to the receiver using the tRFC protocol.

BAPIs are a subset of the RFC-enabled function modules, especially designed as Application Programming Interface (API) to the SAP business object, or in other words: are function modules officially released by SAP to be called from external programs.

BAPIs are called synchronously and (usually) return information

[Former Member]

you can refer to this links

ALE/ IDOC

http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm

http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc

http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419

http://www.netweaverguru.com/EDI/HTML/IDocBook.htm

http://www.sapgenie.com/sapedi/index.htm

http://www.sappoint.com/abap/ale.pdf

http://www.sappoint.com/abap/ale2.pdf

http://www.sapgenie.com/sapedi/idoc_abap.htm

http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm

http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm

http://www.allsaplinks.com/idoc_sample.html

http://www.sappoint.com/abap.html

http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm

http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc

http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419

http://www.netweaverguru.com/EDI/HTML/IDocBook.htm

http://www.sapgenie.com/sapedi/index.htm

http://www.allsaplinks.com/idoc_sample.html

http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs

go trough these links.

http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm

http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc

http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419

http://www.netweaverguru.com/EDI/HTML/IDocBook.htm

http://www.sapgenie.com/sapedi/index.htm

http://www.sappoint.com/abap/ale.pdf

http://www.sappoint.com/abap/ale2.pdf

http://www.sapgenie.com/sapedi/idoc_abap.htm

http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm

http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm

http://www.allsaplinks.com/idoc_sample.html

http://www.sappoint.com/abap.html

http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm

http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc

http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419

http://www.netweaverguru.com/EDI/HTML/IDocBook.htm

http://www.sapgenie.com/sapedi/index.htm

http://www.allsaplinks.com/idoc_sample.html

http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm

regards.

[Former Member]

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