SXDA and LSMW

[Former Member]

Hi,

What is the different between LSMW (Legacy System Migration Workbench) and SXDA (Data Transfer Workbench)??

Any reference reference guide about it??

Regards,

Kit

[Former Member]

Hi,

What is the different between LSMW (Legacy System Migration Workbench) and SXDA (Data Transfer Workbench)??

Any reference reference guide about it??

Regards,

Kit

[ak_upadhyay]

Hi,

SXDA is just an interface for working with a "pool" ofstandard data transfer programs that can be run independently with SE38.

standard programs are available for some business objects only, such as:

- Materials: program RMDATIND

- Customers: program RFBIDE00

- Inforecords: program RM06IBI0

- Sales Orders: ...

Each program uses either BINP (Batch Input) or DINP (Direct Input)technology.

+ Batch Input allows "session management" through tcode SM35

+ Direct Input allows "session management" through tcode BMV0

Each program entry is based on a flat file mapping the input data underone given format.

So, you have to create yourself from your input data one flat file withthe specific format of the program you use.

All input structures are stored in the DDIC, but you have to know theirnames.

For example, program RMDATIND for materials uses structures:

BGR00 - session header (like all DX programs)

BMM00 - transaction header (for each single material data input)

BMMH1

BMMH2

BMMH3

BMMH4

...

You may have a look into the ddic (SE11) to better understand thosestructures.

Structures can be used more than once for each transaction.

Transactions can be used more than once for each sessions.

And of course, all structures are not mandatory: you may want tocreate/update only general data and not orgnizational data for example.

But anyway, you will need some "reference guide" to know the flat filestructure for the program you want to use. This "reference guide" isgiven for free by SAP at this location:http://wwwtech.saplabs.com/guidebooks/data transfer.asp

You will find here all general questions on data transfer, and above allyou'll find all structures used for all programs.

I hope this helps.

Once you've dowloaded and printed this guide, I may help you on sometopic and provide you with example of flat files.

LSMW

No ABAP effort are required for the SAP data migration. However, effort are required to map the data into the structure according to the pre-determined format as specified by the pre-written ABAP upload program of the LSMW.

The Legacy System Migration Workbench (LSMW) is a tool recommended by SAP that you can use to transfer data once only or periodically from legacy systems into an R/3 System.

More and more medium-sized firms are implementing SAP solutions, and many of them have their legacy data in desktop programs. In this case, the data is exported in a format that can be read by PC spreadsheet systems. As a result, the data transfer is mere child's play: Simply enter the field names in the first line of the table, and the LSM Workbench's import routine automatically generates the input file for your conversion program.

The LSM Workbench lets you check the data for migration against the current settings of your customizing. The check is performed after the data migration, but before the update in your database.

So although it was designed for uploading of legacy data it is not restricted to this use.

We use it for mass changes, i.e. uploading new/replacement data and it is great, but there are limits on its functionality, depending on the complexity of the transaction you are trying to replicate.

The SAP transaction code is 'LSMW' for SAP version 4.6x.

For those with the older SAP version (4.7 and below), the data migration programs might not have been pre-loaded.

You can download the LSMW at no cost from SAPNet under Services, SAP Methodology and Tools, category Tools.

If you are an existing SAP customer with an OSS ID, you can access the SAP Service Marketplace to download the LSWM for your Basis teams to install to your SAP system: http://service.sap.com/lsmw

The LSM Workbench carries out the following tasks:

Reads the transfer data from one or more files (for example, spreadsheets, sequential files etc.)

Converts the data from the source format into the target format

Note that with background processing, the input file must not be located in the presentation server. Access to presentation server files is only possible when you are working online.

Or Try These Links.....

http://help.sap.com/saphelp_nw04s/helpdata/en/87/f3ae74e68111d1b3ff006094b944c8/content.htm

http://www.erpgenie.com/saptech/lsmw.htm

http://www.sapbrainsonline.com/TOOLS/LSMW/SAP_LSMW_steps_introduction.html

For SXDA......

http://goldenink.com/abap/data_transfer.html

http://www.sappro.com/downloads/DX_Workbench.pdf

Reward Points if useful....

Regards

AK

[Former Member]

Hi,

here are some differences between BDC and LSMW.

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

LSMW is an encapsulated data transfer tool. It can provide the same functionality as BDC infact much more but when coming to techinical perspective most the parameters are encapulated. To listout some of the differences :

LSMW is basicaly designed for a fuctional consultant who do not do much coding but need to explore the fuctionality while BDC is designed for a technical consultant.

LSMW offers different techinque for migrating data: Direct input ,BAPI,Idoc,Batch input recording. While bdc basically uses recording.

LSMW mapping is done by SAP while in BDC we have to do it explicitly .

LSMW is basically for standard SAP application while bdc basically for customized application.

Coding can be done flexibly in BDC when compared to LSMW

Regards,

swami.

[Former Member]

HI,

I THINK THIS WILL HELPFUL FOR U

LSMW internally might well be using the following techniqes for data transfer..

1. IDOC

2. Direct Input

3. BDC recording

4. BAPI's

LSMW is an encapsulated data transfer tool. It can provide the same functionality as BDC infact much more but when coming to techinical perspective most the parameters are encapulated. To listout some of the differences :

LSMW is basicaly designed for a fuctional consultant who do not do much coding but need to explore the fuctionality while BDC is designed for a technical consultant.

LSMW offers different techinque for migrating data: Direct input ,BAPI,Idoc,Batch input recording. While bdc basically uses recording.

LSMW mapping is done by SAP while in BDC we have to do it explicitly .

LSMW is basically for standard SAP application while bdc basically for customized application.

Coding can be done flexibly in BDC when compared to LSMW

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

REGARDS,

PANKAJ

[Former Member]

follow these links

For more help on SXDA and data transfer techniques refer SAP help..

http://help.sap.com/saphelp_46c/helpdata/en/2e/9e4638a28b2763e10000009b38f8cf/frameset.htm

http://help.sap.com/saphelp_erp2005/helpdata/en/87/f3ae74e68111d1b3ff006094b944c8/frameset.htm

http://help.sap.com/saphelp_46c/helpdata/en/2e/9e4638a28b2763e10000009b38f8cf/frameset.htm

Do Reward if Helpful