Regarding Migrating data from Legacy to SAP

[Former Member]

Hi All,

We are in Migration Project. We have to upload data from legacy to SAP, either using BDC or Cross-Applications in the following SD scenario's.

1. Customer Master

2. Inquiries

3. Quotations

4. Proposals

5. Sales Order

6. Goods Issue

I would like to know, which concept is better for each of the above scenario. Each option have advantages and disadvantages. So, I need suggestion regarding this.

Regards,

Sathya.

[Former Member]

Hi,

Could you please explain which other scenarios you would like to compare with BDC approach?

Regards,

Lijo Joseph

[Former Member]

Hi,

Only the mentioned scenario's we have to work. Please send advantages and disadvantages regarding each scenario.

[Former Member]

Hi,

The best way to migrate data in large volumes is by using LSMW (tcode: LSMW). This mainly used mode of migrating data. You could transfer the data and also make changes to the data itself on the fly before uploading the data.

Once the bulk data is in, then we could use BDCs or Direct Input programmes to upload the remaining data.

Thanks..

Preetham S

[Former Member]

Hi,

Actually we have approximately 10 lakh records. Is, it better to use LSMW. What do u fell about BAPI. When can we use it. And when can we use BDC.

[alpesh_saparia3]

1. For customer master there is standard utility RFBIDE00.

2. For Inquiry/Quotations/Sales Order - BAPI's are available

Inquiry - BAPI_INQUIRY_CREATEFROMDATA2

Quotation - BAPI_QUOTATION_CREATEFROMDATA2

Sales Order- BAPI_SALESORDER_CREATEFROMDAT2

3. Proposals use BDC.

4. Goods Issue - BAPI_GOODSMVT_CREATE

BAPIs are good as it is standard, BDC's is second priority as it is customer generated, even you can go for LSMW.

-Alpesh

[Former Member]

hi,

The goal of using SHDB is to create BDC programs and sessions. But BDC doesn’t support Enjoy transactions.

Enjoy transactions use Enjoy SAP Controls like ALV Grid, ALV Tree. If you run BDC in background these Controls would not be able to communicate front-end since they need some files in front-end (client - PC), so BDC fails.

Therefore what can be done? There are two possibilities:

1- ) There might be a alternative, usually older version, transaction. You can use it. For example ME22N is a Enjoy transaction, but ME22 is the older one, does the same thing. So ME22 can be used.

- ) If it is available, a BAPI can be used. Whatever you want to do, you can search BAPIs and use it instead of BDC technique.

hope it helps.

plz reward points rgds.

[Former Member]

hi

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/backgrou nd 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

also check this link:

plz reward points if it helps

rgds.