Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

bdc

Former Member
0 Kudos
131

what is the major diff between bdc and lsmw

1 ACCEPTED SOLUTION

Former Member
0 Kudos
105

BDC:

Here you will write the code screen by screen and you will decide what fields you need to fill and major disadvantage in BDC is when you are going for upgrade and if there was some change in screen, you need to change your BDC code as well

LSMW:

In LSMW we will have different methods to post the data

1) Idoc: You can create Idocs using LSMW

2) Direct Input: This is the SAP provided standard programs which will be taken care of your postings.

3) BAPI: using bapi also you can post the SAP Data

Pavan

7 REPLIES 7

Former Member
0 Kudos
106

BDC:

Here you will write the code screen by screen and you will decide what fields you need to fill and major disadvantage in BDC is when you are going for upgrade and if there was some change in screen, you need to change your BDC code as well

LSMW:

In LSMW we will have different methods to post the data

1) Idoc: You can create Idocs using LSMW

2) Direct Input: This is the SAP provided standard programs which will be taken care of your postings.

3) BAPI: using bapi also you can post the SAP Data

Pavan

Former Member
0 Kudos
105

Hi

janani

BAPI

BAPI stands for Business API(Application Program Interface).

A BAPI is remotely enabled function module

ie it can be invoked from remote programs like standalone JAVA programs, web interface etc..

You can make your function module remotely enabled in attributes of Function module but

A BAPI are standard SAP function modules provided by SAP for remote access.

Also they are part of Businees Objest Repository(BOR).

BAPI are RFC enabled function modules. the difference between RFc and BAPI are business objects.

You create business objects and those are then registered in your BOR (Business Object Repository)

which can be accessed outside the SAP system by using some other applications (Non-SAP) such as VB or JAVA.

In this case u only specify the business object and its method from external system

in BAPI there is no direct system call. while RFC are direct system call.

Some BAPIs provide basic functions and can be used for most SAP business object types.

These BAPIs should be implemented the same for all business object types.

Standardized BAPIs are easier to use and prevent users having to deal with a number of different BAPIs.

Whenever possible, a standardized BAPI must be used in preference to an individual BAPI.

List of all BAPIs

http://www.planetsap.com/LIST_ALL_BAPIs.htm

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

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

http://www.sap-img.com/sap-data-migration.htm

http://www.scmexpertonline.com/downloads/SCM_LSMW_StepsOnWeb.doc

http://allsaplinks.com/lsmw.html

http://myweb.dal.ca/hchinni/sap/lsmw_home.htm

For BDC:

http://myweb.dal.ca/hchinni/sap/bdc_home.htm

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&;

http://www.sap-img.com/abap/learning-bdc-programming.htm

http://www.sapdevelopment.co.uk/bdc/bdchome.htm

http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm

http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm

http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html

and also go through these links

plzz reward if usefull

for any further quiries

my mail id is mutyalasunilkumar@gmail.com

Former Member
0 Kudos
105

The Legacy System Migration Workbench (LSMW) is an R/3-based tool that supports You when transferring data from non-SAP systems ("Legacy Systems") to SAP systems 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 SAP system via techniques like batch input, direct input, BAPIs, IDocs Etc.

Where as,

BDC is Batch Data Communication where data is transferred from legacy system to SAP system. Different methods of BDC are

1. Call Transaction Method.

2. Session Method

3. Direct Input method.

Le'me know if you need more information. I can send in some documents to you.

Vinodh Balakrishnan

Former Member
0 Kudos
105

yes if u could forward me some materials ........

0 Kudos
105

send in your personal mail id.... i'll forward the docs

0 Kudos
105

plss send me ur mail id...i ll send a test mail...

Former Member
0 Kudos
105

one thing.

LSMW fails when you use append structures for enhancements.

then only way is BDC.

Regards