difference between ale and bapi

[Former Member]

hi,

experts.

could any one provide me the solution regarding ale and bapi

thanku very much

all

[Former Member]

the functionality of both idoc and bapi are same.

the main difference in BAPI is it is used for Third party application like JAVA, VB etc.

and IDOC is used transfer data from the SAP to sap or non-sap system.

For details refer the contents below

ALE

ALE is SAP proprietary technology that enables data communications between two or more SAP R/3 systems and/or R/3 and external systems. When a new enterprise resource planning (ERP) solution such as R/3 is implemented, companies have to interface the ERP system with legacy systems or other ERP systems.

ALE provides intelligent mechanisms where by clients can achieve integration as well as distribution of applications and data.

ALE technology facilitates rapid application prototyping and application interface development, thus reducing implementation time.

The ALE components are inherently integrated with SAP applications and are robust, leading to a highly reliable system.

ALE comes with application distribution/integration scenarios as well as a set of tools, programs, data definitions, and methodologies that you can easily configure to get an interface up and running.

BAPI

BAPIs provide a stable, standardized method for third-party applications and components to integrate into the Business Framework. These interfaces are being specified as part of SAP's initiative with customers, partners and leading standards organizations. Also, SAP has implemented the emerging Object Application Group (OAG) specifications with BAPIs.

*************************************************************

At a high level, BAPI's are ABAP function modules that are enabled for calls from external systems (can also be used internally).

A BAPI usually has defined import and export parameters. You call a BAPI via a program, input some values, and the BAPI executes and returns some values to the calling program.

ALE is a means of migrating DATA between SAP systems. You configure logical destinations, establish some migrating criteria and the system takes care of getting your data from point A to point B

Here are some links

http://searchsap.techtarget.com/general/0,295582,sid21_gci1110008,00.html

http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html

http://help.sap.com/saphelp_nw04/helpdata/en/43/b46c4b53c111d395fa00a0c94260a5/content.htm

************************************************************

At a high level, BAPI's are ABAP function modules that are enabled for calls from external systems (can also be used internally).

A BAPI usually has defined import and export parameters. You call a BAPI via a program, input some values, and the BAPI executes and returns some values to the calling program.

ALE is a means of migrating DATA between SAP systems. You configure logical destinations, establish some migrating criteria and the system takes care of getting your data from point A to point B

That's pretty general but I hope it helps.

[Former Member]

THANK YOU

Ramesh Babu Chirumamilla

thank you for spending time for my question

[Former Member]

Hi Kiran,

Check these links which has differences between ALE and BAPI.

http://www.sap-img.com/abap/ale-bapi.htm

http://expertanswercenter.techtarget.com/eac/knowledgebaseAnswer/0,295199,sid63_gci983331,00.html

http://searchsap.techtarget.com/loginMembersOnly/1,289498,sid21_gci879631,00.html

Thanks,

Vinay

[Former Member]

Dear Kiron,

Please go through the following links:

<b>ALE</b>

http://www.thespot4sap.com/Articles/SAP_ALE_Introduction.asp

http://www.erpgenie.com/ale/index.htm

http://www.sapbrain.com/TUTORIALS/TECHNICAL/ALE_tutorial.html

<b>BAPI</b>

http://www.sapbrain.com/TUTORIALS/TECHNICAL/BAPI_tutorial.html

Regards,

Abir

************************************

• Don't forget to award Points *

[Former Member]

Hi,

This are the difference between BAPI and BDC and RFC AND ALE

<b>BAPI ,

Then Standard BDC

Then Specifc BDC!

BAPI are made in order to work correctly even after a SAP realease change. Moreover, a bapi includes the same rules as the Txn.

If you have possibility to use bapi then its better to go for bapi rather than bdc the main difference between these two is

If any upgradations are made in the system then bdc programs willnot work properly where as bapi's will support the upgradations

if you don't have standard bapi better to go with bdc

if you find it useful mark the points

If there is one then defenitly BAPI.

Also many times you might not have all the data which is required by the BAPI to successfully run.

A BDC is conv when u have less fields or when there's no BAPI existing.

A BDC cannot be called form some other language as an object but BAPI is an object and has methods which can be called.

BAPI is better one than BDC....When u have internal table, using BAPI directly loads data to sap but where as for BDC u have to write hughe code etc....

Check below links which will give u better idea...

/message/2272598#2272598 [original link is broken]

1. Which is better to use BAPI or BDC?

BAPI is always better.

2. a) Very easy to use (Just like FM)

b) In future, if screen sequence changes, then we have to change BDC,

whereas sap guarantees the corresponding compatibilty/change

in BAPI.

c) Recording/screen sequence/programname/screen fieldname,

--- all these things are not required to be explored & recorded.

BAPI vs BDC

SAP usually upgrade their Version, so each and every time they will change the screens .so you have to change your BDC programs accordingly ,tis is not the case with BAPI .

CHK THIS LINKS:

http://www.sapgenie.com/abap/bapi/example.htm

http://sappoint.com/abap/

BAPI stands for Business API(Application Program Interface).

A BAPI is remotely enabled function module

ie it can be invoked from remote programs like standalone JAVA programs, web interface etc..

You can make your function module remotely enabled in attributes of Function module but

A BAPI are standard SAP function modules provided by SAP for remote access.

Also they are part of Businees Objest Repository(BOR).

BAPI are RFC enabled function modules. the difference between RFc and BAPI are business objects.

You create business objects and those are then registered in your BOR (Business Object Repository)

which can be accessed outside the SAP system by using some other applications (Non-SAP) such as VB or JAVA.

In this case u only specify the business object and its method from external system

in BAPI there is no direct system call. while RFC are direct system call.

Some BAPIs provide basic functions and can be used for most SAP business object types.

These BAPIs should be implemented the same for all business object types.

Standardized BAPIs are easier to use and prevent users having to deal with a number of different BAPIs.

Whenever possible, a standardized BAPI must be used in preference to an individual BAPI.

The following standardized BAPIs are provided:

Reading instances of SAP business objects

GetList ( ) With the BAPI GetList you can select a range of object key values,

for example, company codes and material numbers.

The BAPI GetList() is a class method.

GetDetail() With the BAPI GetDetail() the details of an instance of a business object type are retrieved

and returned to the calling program.

The instance is identified via its key.

The BAPI GetDetail() is an instance method.

BAPIs that can create, change or delete instances of a business object type

The following BAPIs of the same object type have to be programmed

so that they can be called several times within one transaction.

For example, if, after sales order 1 has been created, a second sales order 2 is created in the same transaction,

the second BAPI call must not affect the consistency of the sales order 2.

After completing the transaction with a COMMIT WORK, both the orders are saved consistently in the database.

Create( ) and CreateFromData! ( )

The BAPIs Create() and CreateFromData() create an instance of an SAP business object type,

for example, a purchase order. These BAPIs are class methods.

Change( )

The BAPI Change() changes an existing instance of an SAP business object type,

for example, a purchase order. The BAPI Change () is an instance method.

Delete( ) and Undelete( ) The BAPI Delete() deletes an instance of an SAP business object type from the database

or sets a deletion flag.

The BAPI Undelete() removes a deletion flag. These BAPIs are instance methods.

Cancel ( ) Unlike the BAPI Delete(), the BAPI Cancel() cancels an instance of a business object type.

The instance to be cancelled remains in the database and an additional instance is created

and this is the one that is actually canceled. The Cancel() BAPI is an instance method.

Add<subobject> ( ) and Remove<subobject> ( ) The BAPI Add<subobject> adds a subobject to an existing object inst!

ance and the BAPI and Remove<subobject> removes a subobject from an object instance.

These BAPIs are instance methods.

Check these Links out

http://searchsap.techtarget.com/ateQuestionNResponse/0,289625,sid21_cid558752_tax293481,00.html

http://www.sap-img.com/abap/interview-question-on-bapi-rfc-abap-objects-tables.htm

http://www.sap-img.com/fu033.htm

http://www.sap-img.com/abap/ale-bapi.htm

Please check out this thread..

Also refer to the following links..

www.sappoint.com/abap/bapiintro.pdf

www.sap-img.com/bapi.htm

www.sap-img.com/abap/bapi-conventions.htm

www.planetsap.com/Bapi_main_page.htm

www.sapgenie.com/abap/bapi/index.htm

Checkout !!

http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html

http://techrepublic.com.com/5100-6329-1051160.html#

http://www.sap-img.com/bapi.htm

http://www.sap-img.com/abap/bapi-conventions.htm

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

Java Connector(JCO) can call not only BAPI's but also the function modules which are remotely enabled..

BAPI's as i said earlier are remotely enabled function modules..

Hence, JCO can call also BAPI's(n not only BAPI's as u mentioned).

Check the following BDC over BAPI

The steps to be followed are :

1. Find out the relevant BAPI (BAPI_SALESORDER_CHANGE for VA02).

[for VA01 use BAPI_SALESORDER_CREATEFROMDAT2]

2. Create a Z program and call the BAPi (same as a Funtion module call).

2. Now, if you see this BAPi, it has

-> Importing structures.

eg: SALESDOCUMENT: this will take the Sales order header data as input.

-> Tables parameters:

eg: ORDER_ITEM_IN: this will take the line item data as input.

Note :

Only specify fields that should be changed

Select these fields by entering an X in the checkboxes

Enter a U in the UPDATEFLAG field

Always specify key fields when changing the data, including in the checkboxes

The configuration is an exception here. If this needs to be changed, you need to complete it again fully.

Maintain quantities and dates in the schedule line data

Possible UPDATEFLAGS:

U = change

D = delete

I = add

Example

1. Delete the whole order

2. Delete order items

3. Change the order

4. Change the configuration

Notes

1. Minimum entry:

You must enter the order number in the SALESDOCUMENT structure.

You must always enter key fields for changes.

You must always specify the update indicator in the ORDER_HEADER_INX.

2. Commit control:

The BAPI does not run a database Commit, which means that the application must trigger the Commit

so that the changes are read to the database. To do this, use the BAPI_TRANSACTION_COMMIT BAPI.

For further details... refer to the Function Module documentation for the BAPi.

</b>.

Thanks

Avi

[Former Member]

its more enough