lsmw

Former Member — Tue, 22 Jan 2008 14:00:08 GMT

can anybody explain about the difference between bdc and lsmw in detail?

thanyou.

Re: lsmw

Former Member — Tue, 22 Jan 2008 14:06:25 GMT

Hi,

"The Data Transfer Workbench (or DX Workbench, transaction SXDA) is an integrated SAP tool that supports data transfer and analysis. It

does not have the built-in features for mapping for source structures to target structures, but it will allow you to integrate Legacy System Migration Workbench (LSMW) objects as processing tasks within a run definition. The DX workbench has many features for creating

test data and performing data migrations - for example, logging of data migration runs.

However, if you need to map or convert data, you should use the LSMW. Or, you can integrate

your LSMW objects as task within a more user-friendly data migration run, in which the LSMW

project steps "Read data", "Convert data," and "Start IDoc processing" are automated

and use the features of both tools. If you donot need logging and automated data migration

runs, you can perform your data migration without the DX Workbench."

The following was taken at this site :

http://www.info-sun.com/docs/wp_sapinter.pdf

“Batch Data Communication (BDC) is the oldest batch interfacing technique that SAP provided since the early versions of R/3. BDC is not a

typical integration tool, in the sense that, it can be only be used for uploading data into R/3 and so it is not bi-directional.

BDC works on the principle of simulating user input for transactional screen, via an ABAP program. Typically the input comes in the form

of a flat file. The ABAP program reads this file and formats the input data screen by screen into an internal table (BDCDATA). The

transaction is then started using this internal table as the input and executed in the background.

In ‘Call Transaction’, the transactions are triggered at the time of processing itself and so the ABAP program must do the error handling.

It can also be used for real-time interfaces and custom error handling & logging features. Whereas in Batch Input Sessions, the ABAP

program creates a session with all the transactional data, and this session can be viewed, scheduled and processed (using

Transaction SM35) at a later time. The latter technique has a built-in error processing mechanism too.

Batch Input (BI) programs still use the classical BDC approach but doesn’t require an ABAP program to be written to format the

BDCDATA. The user has to format the data using predefined structures and store it in a flat file. The BI program then reads this and

invokes the transaction mentioned in the header record of the file.

Direct Input (DI) programs work exactly similar to BI programs. But the only difference is, instead of processing screens they validate

fields and directly load the data into tables using standard function modules. For this reason, DI programs are much faster (RMDATIND - Material Master DI program works at least 5 times faster) than the BDC counterpart and so ideally suited for loading large volume data. DI programs are

not available for all application areas.

RegardS

Re: lsmw

Former Member — Tue, 22 Jan 2008 14:17:49 GMT

thank you

Re: lsmw

Former Member — Sat, 15 Mar 2008 07:11:47 GMT

In LSMW, BDC is the one method. Abepers will do the programming

Re: lsmw

Former Member — Mon, 17 Mar 2008 05:21:38 GMT

Hi,

LSMW offers different technique for migrating data: Direct input, BAPI, Idoc, Batch input recording. While BDC basically uses batch input sessions and CALL TRANSACTION method.

Limit on number of records which can be uploaded in one session of BDC (999 records). No such limit in LSMW.

LSMW is more to do with configuration while BDC involves programming.

LSMW can import data from legacy systems (e.g. in the form of Excel sheets or CSV files). I guess LSMW converts your data into batch input files automatically. If you use BDC; you need to write your batch input file yourself, line per line.

With LSMW, you get a "wizard" (so to say) that writes the batch input for you. It's the difference between writing a program yourself and letting a wizard write it for you.

But a wizard can only handle some specific situations (Excel file, sequential data in CSV files, for instance) but not ALL situations of data import. For those situations that LSMW cannot handle, you will need BDC.

Reward if usefull

Thank You,.

Gopi.S

topic Re: lsmw in Application Development and Automation Discussions

lsmw

Re: lsmw

Re: lsmw

Re: lsmw

Re: lsmw