hi

Former Member — Wed, 06 Dec 2006 06:41:57 GMT

hi all,

1) when will go for lsmw and when will go for session and call transaction

Thanks

rams

Re: hi

Former Member — Wed, 06 Dec 2006 06:45:10 GMT

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."

“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.

Re: hi

sreekanthgo — Wed, 06 Dec 2006 06:54:09 GMT

Hi Rams,

Generally we will first use the call transaction method, if it gets failed we will populate session.

Check the below code.

*-- Call VA02 transaction
        CALL TRANSACTION 'VA02'
                         USING  IT_BDCDATA
                         MODE   'N'
                         UPDATE 'S'.
        IF SY-SUBRC <> 0.
           " Populate session
        ENDIF.

Error records will be updated using session metho later.

Thanks,

Sreekanth

<i>* Please do not forget to mark the helpful answers</i>

Re: hi

Former Member — Wed, 06 Dec 2006 07:00:58 GMT

Lsmw is mainly desined for the purpose of functional people.

And mainly it is cost effective.

If the data is to be immediately uploaded then we go for call transaction.(for small data).

Otherwise we go for session method(for lage data).

topic Re: hi in Application Development and Automation Discussions

hi

Re: hi

Re: hi

Re: hi