customer master

[Former Member]

Hi Gurus,

I want to extend my customer master data in one COMPANY CODE/SALES AREA to another COMP CODE/SALES AREA using LSMW.

tell me the differences in LSMW in this case if we use BATCH INPUT method.

pls dont gmme the LSMW steps.

thank you

with regards

anil

[Former Member · Accepted solution]

Hi Anil,

Diff between LSMW and BDC

LSMW doesn't have screen no's and screen navigation direct table update with the structure of LSWM . where as BDC has screen navigation with DYNPR Which doesn't have structure only screen fields ....

LSMW is generally for normal SAP applications, while BDC is mainly for any customized application.

LSMW provides various methods for the migration of data, namely, those of direct input, Batch input recording and IDOC. BDC however, simply makes use of recording. There are two ways of implementing BDC, the call transaction method and the session method.

In LSMW, mapping is taken care of with the help of SAP, whereas in BDC one has to provide explicit mapping directions.

Coding is not very flexible in LSMW, whereas in BDC, coding is very flexible and applications can be easily customized. This is mainly because LSMW is devised specially for functional consultants who do not perform coding, while BDC is mainly made use of by technical consultants, who do perform coding.

There are no types in LSMW.. but there are different methods are available in lsmw..

they are

1.direct input method

2.standard batch input method

3.using BAPI

4.using Idoc.

Go to the transasction LSMW and choose the idoc method..

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.

Batch Data Communication or BDC is a batch interfacing technique that SAP developed. It is mainly used for uploading data into the SAP R/3 system. BDC works by simulating the user input from transactional screen via an ABAP program.

The data input data file will come in the form of a flat file which the user save as file type txt file or prn file from the Microsoft Excel program. An Abaper will create a program to read the text file and upload into the SAP system.

Normally, the tcode SHDB will be used to record the transaction code the user used. After, the simulation, the Abaper can generate a sample program and modify from there. It makes the programming easier and faster.

Award points if it adds information.

Thanks

Mohan

[Former Member]

hi,

Please follow this link

This gives u both the method

1.Batch input recording

2.Using SAP object

This ppt gives u with snap shots

<a href="http://www.slideshare.net/arun_bala1/sap-sd-lsmw-legacy-system-migration-workbench">LSMW</a>

Difference b/w LSMW & BDC

<a href="http://www.geekinterview.com/question_details/33450">LSMW VS BDC</a>

LSMW and BDC are vastly different.

BDC (Batch Data Communication) is a technology used for data transfer. it is meant for transferring data thru SAP transactions itself. when u use BDC for data transfer, the sequence of steps is the same as when u use standard sap transaction screens for data upload. the only difference is that u can use different options for foreground/background processing.

LSMW on the other hand is a tool that helps migrate data from a legacy system (non-sap system ) to SAP system. it offers u various options to use either batch input, direct input, BAPIs or idocs. it involves a series of some 17-18 steps to migrate data.

BDC:

Batch Data Communication (BDC) is the process of transferring data from one SAP System to another SAP system or from a non-SAP system to SAP System.

Features :

BDC is an automatic procedure.

This method is used to transfer large amount of data that is available in electronic medium.

BDC can be used primarily when installing the SAP system and when transferring data from a legacy system (external system).

BDC uses normal transaction codes to transfer data.

Types of BDC :

CLASSICAL BATCH INPUT (Session Method)

CALL TRANSACTION

BATCH INPUT METHOD:

This method is also called as ‘CLASSICAL METHOD’.

Features:

Asynchronous processing.

Synchronous Processing in database update.

Transfer data for more than one transaction.

Batch input processing log will be generated.

During processing, no transaction is started until the previous transaction has been written to the database.

CALL TRANSACTION METHOD :

This is another method to transfer data from the legacy system.

Features:

Synchronous processing. The system performs a database commit immediately before and after the CALL TRANSACTION USING statement.

Updating the database can be either synchronous or asynchronous. The program specifies the update type.

Transfer data for a single transaction.

Transfers data for a sequence of dialog screens.

No batch input processing log is generated.

LSMW:

The LSM Workbench is an R/3-based tool that supports You when transferring data from non-SAP systems ("Legacy Systems") to R/3 once or periodically.

The tool supports conversion of data of the legacy system in a convenient way. The data can then be imported into the R/3 system via batch input, direct input, BAPIs or IDocs.

Furthermore, the LSM Workbench provides a recording function that allows to generate a "data migration object" in an entry or change transaction.

The main advantages of the LSM Workbench:

• Part of R/3 and thus independent of individual platforms

• A variety of technical possibilities of data conversion:

• Data consistency due to standard import techniques:

Batch input

Direct input

BAPIs (Business Application Programming Interfaces)

IDocs (Intermediate Documents)

The import technique to be used in an individual case depends on the business object.

• Generation of the conversion program on the basis of defined rules

• Clear interactive process guide

• Interface for data in spreadsheet format

• Creation of data migration objects on the basis of recorded transactions

• Charge-free for SAP customers and SAP partners

regards,

Arunprasad

Message was edited by:

arun prasad