difference between BDC and ALE

[Former Member]

hi

[Former Member]

hi,

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.

where as bdc can upload data into sap R/3 database.

using either call transaction which is online or session method ..data is uploaded

regards

sree

[Former Member]

Hi,

You can go throgh the documenetion then you get an idea

Why Should we use IDOC to transfer data from Legacy (Peoplesoft) System to SAP r/3. Why cant we use BDC.. can u explain wen should we use BDC and Wen we go for Idoc ,,, if possible explain the purpose of all transfer techniques

You can use the idoc method to transfer the data when you are having an interface between the sap system and the legacy system......

All the times BDC is not preferable like take the case you developed on upload program with bdc after some days your company thought to go for upgrade the sap vesion from lower version to upper version... in that upgraded version the application may change like sequence of fields or screens at that time you previous bdc program will not work here so u have to develop a new program and and you have to take the things into consideration again...

where as if you use bapi or idoc method it will support the upgradations...

in the case of bdc you have to take the data into flat files.... and then upload it to sap system after all the validations done some times the data which is in the flat file is confidential so there is no security if u take such data in flat file any user can chang the data even though if u maintain the data in application server super user can change the data

where is idoc is fully secured... you can easily establich the interface between the systems and once it is done you can transfer the data with full security because idoc r generated by a program... so there is no manual interaction..

Regards

[Former Member]

hi

good

ALE /EDI :

Both technologies are used to set up communication between SAP to SAP or SAP to Non-SAP systems.

Both technologies use IDOCS for data transfer between two systems.Difference lies in way of communication.

EDI uses EDI subsystem (translator) to transform IDOC formatted messages in EDI standard messages.

These EDI subsystems(translator) are third-party software & SAP does not have control over the process.

In case of ALE data IDOCS are communicated directly through the memory.There is no data transalation as in EDI.

BDC /LSMW :

BDC is Batch Data Communication. It is basically a program

either generated by SAP after a recording or programmed by a

abaper.Its like running the transaction manually but all the

data is populated on the screens automatically.It is a

little complex when the screens contain table controls.

LSMW is legacy system migration workbench is a more user-

friendly tool thru which one can do the same as a BDC. One

just has to follow some 14 steps

In bdc we have to write source code.

in lsmw there is no need of write source code .

in bdc no concept of bapi's and idoc .

in lsmw here we have also avaialble bapi and idoc.

in bdc we have to create session for error analysis .

in lsmw we can analysis errors very easily .

just refer to the link below once. no need to search any other link

http://www.sapmaterial.com/?gclid=CN322K28t4sCFQ-WbgodSGbK2g (SAP link- ultimate material )

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

http://www.allsaplinks.com/

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

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

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf

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://expertanswercenter.techtarget.com/eac/knowledgebaseCategory/0,295197,sid63_tax296858_idx0_off...

http://sap.ittoolbox.com/documents/popular-q-and-a/extending-a-basic-idoc-type-2358

http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b7eee43d711d1893e0000e8323c4f/frameset.htm

reward point if helpful.

Thanks

mrutyun^