Diff b/w BDC and LSMW

hi
i want know what is the difference between BDC and LSMW and which is best also tell me BDC and LSMW using for which type data (like master or transactional data)
thanka in advance
deepak

Hi deepak,
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.
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
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

Similar Messages

'Create' Push button is not working in BDC and LSMW while uploading G/L master data

Hello Experts:
I am facing the following problem:
While uploading G/L master data with the BDC program, 'create' push button is not working even after executing following lines.
PERFORM BDC_DYNPRO      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                               '=ACC_CRE'.
Create G/L account screen is not coming in BDC. Please suggest me what to do.
Thanks !!

Re: 'Create' Push button is not working in BDC and LSMW while uploading G/L master data
Re: 'Create' Push button is not working in BDC and LSMW while uploading G/L master data
Hi Glen Anthony
Thank you for the reply Glen Anthony please take a look at the following code.
REPORT ZFI_BDC_FS00
        NO STANDARD PAGE HEADING LINE-SIZE 255.
*INCLUDE BDCRECX1.
TYPES : BEGIN OF STR,
   BUKRS TYPE GLACCOUNT_SCREEN_KEY-BUKRS,        "Company Code
   SAKNR TYPE GLACCOUNT_SCREEN_KEY-SAKNR,        "G/L Account Number
   KTOKS TYPE GLACCOUNT_SCREEN_COA-KTOKS,        "G/L Account Group
   XPLACCT TYPE GLACCOUNT_SCREEN_COA-XPLACCT,    "P&L statement account
   XBILK TYPE GLACCOUNT_SCREEN_COA-XBILK,        "Indicator: Account is a balance sheet account?
   TXT20_ML TYPE GLACCOUNT_SCREEN_COA-TXT20_ML, "G/L account short text
   TXT50_ML TYPE GLACCOUNT_SCREEN_COA-TXT50_ML, "G/L account short text
   WAERS TYPE GLACCOUNT_SCREEN_CCODE-WAERS,      "Account currency
   XSALH TYPE GLACCOUNT_SCREEN_CCODE-XSALH,      "Indicator: Only Manage Balances in Local Currency
   MWSKZ TYPE GLACCOUNT_SCREEN_CCODE-MWSKZ,      "Tax Category in Account Master Record
   XMWNO TYPE GLACCOUNT_SCREEN_CCODE-XMWNO,      "Indicator: Tax code is not a required field
   MITKZ TYPE GLACCOUNT_SCREEN_CCODE-MITKZ,      "Account is reconciliation account
   XOPVW TYPE GLACCOUNT_SCREEN_CCODE-XOPVW,      "Indicator: Open item management?
   XKRES TYPE GLACCOUNT_SCREEN_CCODE-XKRES,      "Indicator: Can Line Items Be Displayed by Account?
   ZUAWA TYPE GLACCOUNT_SCREEN_CCODE-ZUAWA,      "Key for sorting according to assignment numbers
   FSTAG TYPE GLACCOUNT_SCREEN_CCODE-FSTAG,      "Field status group
   XINTB TYPE GLACCOUNT_SCREEN_CCODE-XINTB,      "Indicator: Is account only posted to automatically?
   END OF STR.
DATA : ITAB TYPE TABLE OF STR WITH HEADER LINE,
        IT_BDCDATA TYPE TABLE OF BDCDATA WITH HEADER LINE,
        TXT(4096) TYPE C OCCURS 0,
        MSG TYPE STRING,
        COUNT(5) TYPE N.
SELECTION-SCREEN : BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001.
   PARAMETERS : MY_FILE TYPE RLGRAP-FILENAME.
SELECTION-SCREEN : END OF BLOCK B1.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR MY_FILE.
CALL FUNCTION 'F4_FILENAME'
EXPORTING
    PROGRAM_NAME        = SYST-CPROG
    DYNPRO_NUMBER       = SYST-DYNNR
*   FIELD_NAME          = ' '
IMPORTING
    FILE_NAME           = MY_FILE
CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'
   EXPORTING
*   I_FIELD_SEPERATOR          =
*   I_LINE_HEADER              =
     I_TAB_RAW_DATA             = TXT
     I_FILENAME                 = MY_FILE
   TABLES
     I_TAB_CONVERTED_DATA       = ITAB[]
EXCEPTIONS
    CONVERSION_FAILED          = 1
    OTHERS                     = 2
IF SY-SUBRC <> 0.
* IMPLEMENT SUITABLE ERROR HANDLING HERE
ENDIF.
START-OF-SELECTION.
COUNT = 0.
LOOP AT ITAB.
*PERFORM OPEN_GROUP.
REFRESH IT_BDCDATA.
PERFORM BDC_DYNPRO      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                               'GLACCOUNT_SCREEN_KEY-BUKRS'.
PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                               '=ACC_CRE'.
*PERFORM BDC_FIELD       USING 'BDC_CURSOR'
*                              'GLACCOUNT_SCREEN_KEY-BUKRS'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_KEY-SAKNR'
                               ITAB-SAKNR. "'5'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_KEY-BUKRS'
                               ITAB-BUKRS. "'TATA'.
PERFORM BDC_DYNPRO      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                               '=2102_GROUP'.
PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                               'GLACCOUNT_SCREEN_COA-KTOKS'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-KTOKS'
                               ITAB-KTOKS. "'GL'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-XPLACCT'
                               ITAB-XPLACCT. "'X'.
PERFORM BDC_DYNPRO      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                               '=2102_BS_PL'.
PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                               'GLACCOUNT_SCREEN_COA-XBILK'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-KTOKS'
                               ITAB-KTOKS. "'GL'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-XPLACCT'
                               ITAB-XPLACCT. "''.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-XBILK'
                               ITAB-XBILK. "'X'.
PERFORM BDC_DYNPRO      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                               '=TAB02'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-KTOKS'
                               ITAB-KTOKS. "'GL'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-XBILK'
                               ITAB-XBILK. "'X'.
PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                               'GLACCOUNT_SCREEN_COA-TXT50_ML'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-TXT20_ML'
                               ITAB-TXT20_ML. "'G/L ACCOUNT'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-TXT50_ML'
                               ITAB-TXT50_ML. "'G/L ACCOUNT'.
PERFORM BDC_DYNPRO      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                               '=TAB03'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-WAERS'
                               ITAB-WAERS. "'INR'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-XSALH'
                               ITAB-XSALH. "'X'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-MWSKZ'
                               ITAB-MWSKZ. "'*'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-XMWNO'
                               ITAB-XMWNO. "'X'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-MITKZ'
                               ITAB-MITKZ. "''.
PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                               'GLACCOUNT_SCREEN_CCODE-ZUAWA'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-XOPVW'
                               ITAB-XOPVW. "'X'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-XKRES'
                               ITAB-XKRES. "'X'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-ZUAWA'
                               ITAB-ZUAWA. "'1'.
PERFORM BDC_DYNPRO      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                               '=SAVE'.
PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                               'GLACCOUNT_SCREEN_CCODE-XINTB'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-FSTAG'
                               ITAB-FSTAG. "'G019'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-XINTB'
                               ITAB-XINTB. "'X'.
*PERFORM BDC_TRANSACTION USING 'FS00'.
CALL TRANSACTION 'FS00' USING IT_BDCDATA MODE 'E' UPDATE 'S'.
COUNT = COUNT + 1.
*PERFORM CLOSE_GROUP.
ENDLOOP.
CONCATENATE COUNT ' RECORDS UPDATED SUCCESSFULLY' INTO MSG.
MESSAGE MSG TYPE 'I'.
FORM BDC_DYNPRO USING PROGRAM DYNPRO.
   CLEAR IT_BDCDATA.
   IT_BDCDATA-PROGRAM = PROGRAM.
   IT_BDCDATA-DYNPRO   = DYNPRO.
   IT_BDCDATA-DYNBEGIN = 'X'.
   APPEND IT_BDCDATA.
ENDFORM.
*        INSERT FIELD                                                  *
FORM BDC_FIELD USING FNAM FVAL.
* IF FVAL <> NODATA.
     CLEAR IT_BDCDATA.
     IT_BDCDATA-FNAM = FNAM.
     IT_BDCDATA-FVAL = FVAL.
     APPEND IT_BDCDATA.
* ENDIF.
ENDFORM.

Differences between BDC and LSMW

Hello SAP Gurus,
Kindly let me know the various differences between BDC and LSMW.
Also, please tell me the STEPS of the CUT-OVER PLANNING (Shifting of Data from the Legacy System to the SAP System). Here, the "Data" means which data? Please explain in details.
Looking for your early feedback.
Regards,
Kaushik.

Hi,
BDC- It is Batch data communication. Its used for data conversion from legacy system to SAP system. Only technical people can do it. Tcode is SHDB.
LSMW- It is legacy system migration workbench. Its also used for data conversion from legacy system to SAP system. But it is role of functional consultant.
There are 14 steps in LSMW. As soon as you complete the one step, automatically it will go to next step.
In general you can use LSMW. But if you want to transfer more than 40,000 data, then it is not possible in LSMW. That time you can take help of BDC.
Cutover strategy depends upon how the organizations design their data load strategies. Normally, you decide the sequence of Data loads for Configuration settings, Master data, Transaction data which follows whom and then you make a copy of the system as a Production system a day before and after checking the successful data loads, you go-live 100% or partial again depending upon organizational setup and policies.
Cutover planning is highly site specific. There's no thumb rule. The stock data as on the date of going live should be correctly entered. But stock being a highly dynamic quantity, the strategy for loading should be crystal clear. Then you have to load all the back dated transaction on the stock. Some stock comes into your plant/storage location as return and some stock is actually delivered to your customer through sales orders of various kinds.
Please refer this link,
[PP Cut over activity|http://www.sap-img.com/production/pp-questions-answers.htm]
Regards,
R.Brahmankar

What is BDC and LSMW? Difference

Dear experts!
Explore the concept of BDC and LSMW and their difference.
Merits/Demerits.
Transactions used for executing and viewing the same.
Rishi.

Rishi,
Hope these links help you:
http://sap-img.com/bdc.htm
http://sap-img.com/sap-data-migration.htm
http://sap-img.com/sap-data-migration.htm
https://websmp206.sap-ag.de/lsmw
<b>LSMW</b>
Data Migration from Non-SAP Systems to SAP systems* Made Easy
The LSM Workbench is an SAP R/3 based tool that supports the one-time or periodic transfer of data from non-SAP systems ("legacy systems") to SAP systems.
The LSM Workbench helps you to organize your data migration project and guides you through the process by using a clear sequence of steps.
The most common conversion rules are predefined. Reusable conversion rules assure consistent data conversion for different data objects.
The LSM Workbench covers the following steps:
Read the legacy data from one or several files (e.g. spreadsheet tables, sequential files).
Convert the data from source format to target format.
Import the data using standard interfaces (Batch Input, Direct Input, BAPI, IDoc).
Detailed Information
Objectives
High Flexibility to Ensure the Optimal Solution
The Data Transfer Workbench gives you control of the SAP data transfer interfaces: from proven batch input, through very fast direct input, to Business APIs (BAPIs), which are also suitable for permanent interfaces. This solution is sufficient if certified partner products are available for the transfer of open interfaces, or if you explicitly want to do interface programming in ABAP or the language of the legacy system. SAP provides its customers with the Legacy System Migration (LSM) Workbench, which dramatically reduces the considerable expenditure involved in individual programming. This tool makes it possible to transfer data without any programming. You define the rules for the changeover. The LSM Workbench then uses this definition to generate an ABAP program and thus gives you considerable support during the migration.
Description
Data Migration Controlled by your SAP System
In contrast to many conventional approaches, the solution described here is a component of your SAP system. As a result it is no longer necessary to program in a number of different systems. All you need are basic unloading programs in the legacy system, or, alternatively, existing data interfaces can be used. Everything else takes place in the SAP system. With SAP R/3 Release 4.6C the LSM Workbench is also integrated into the Data Transfer Workbench, and can be called up there.
Maximum Quality
Data migration with the Data Transfer Workbench and the LSM Workbench guarantees maximum quality and consistency of your data in the SAP system. When data is imported, the system performs the same checks as it does during online entry. The update in your database is performed through the Standard Batch Input Program, the Standard Direct Input Program, IDOC interfaces, and R/3 System BAPIs.
Proven Concepts
SAP has already gathered over seven years of migration experience with its own products. The LSM Workbench has been developed on the basis of experience gained with the R/2-R/3 Migration Workbench. In the meantime, the LSM Workbench has also been successfully used over 500 times in the migration of legacy systems to R/3.Concepts and techniques that have proven their worth form the backbone of the LSM Workbench:
Transfer of business data objects (such as material master data) instead of individual tables
Definition of flexible conversion rules that are adapted as part of migration customizing
Automatic generation of a conversion program
Synergy Effects through Uniform Procedures
SAP's experience shows that certain algorithms and techniques appear over and over again during data conversion projects. These techniques have been standardized in the LSM Workbench and can be called at the touch of a button. With this concept of central rules you can ensure, for example, that your vendor numbers are converted in the same way in both your vendor master data and in your purchase orders. This uniform procedure guarantees the consistency of your data and captures synergy effects in cases where you need to migrate data from disparate legacy systems.
Importing Data from PCs
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.
Data Verification before Update in the Database
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.
Substantial Reduction of Effort
SAP's experiences show that using the Data Transfer Workbench in conjunction with the LSM Workbench can reduce the effort required for data migration by 30% and more.
Project Library - A Knowledge Database
The LSM Workbench is a learning tool: The experience gained in other implementation projects is continually fed into the LSM Workbench, where it directly benefits your project.

Want to upload data without BDC and LSMW in FB01

Hi Expert,
I want to upload data in FB01 without using BDC and LSMW. I want to use all posting key for posting the data. Could any body provide me the code using BAPI. My flat file has all the posting key for the operation.
Regards
Sanjay

Hi Sanjay,
Here is one example showing BAPI_ACC_DOCUMENT_POST for posting vendor invoices. In the similar manner you can populate other tables like accountrecievables also. So by using the same BAPI you will be able to post a document with all possible conditions:
DATA: lt_glacct TYPE TABLE OF bapiacgl09,
      lt_vendact TYPE TABLE OF bapiacap09,
      lt_curramt TYPE TABLE OF bapiaccr09,
      lt_return TYPE TABLE OF bapiret2.
DATA: lv_objtyp TYPE bapiache09-obj_type,
      lv_objkey TYPE bapiache09-obj_key,
      lv_objsys TYPE bapiache09-obj_sys,
      wa_docheader TYPE bapiache09,
      wa_glacct LIKE LINE OF lt_glacct,
      wa_curramt LIKE LINE OF lt_curramt,
      wa_vendact LIKE LINE OF lt_vendact,
      wa_return LIKE LINE OF lt_return.
* Populate header data of document
wa_docheader-obj_type = 'REACI'.
wa_docheader-obj_key = '$'.
wa_docheader-obj_sys = 'T90CLNT090'.
wa_docheader-bus_act = 'RMRP'.
wa_docheader-comp_code = '1000'.
wa_docheader-username = sy-uname.
wa_docheader-header_txt = 'Upload using BAPI'.
wa_docheader-doc_date = '20090331'.
wa_docheader-pstng_date = '20090331'.
wa_docheader-fisc_year = '2009'.
wa_docheader-doc_type = 'RE'.
wa_vendact-itemno_acc = '0000000001'.
wa_vendact-vendor_no = '0000005200'.
wa_vendact-pmnttrms = '0001'.
wa_vendact-bline_date = '20090421'.
wa_vendact-item_text = 'Account payable'.
APPEND wa_vendact TO lt_vendact.
wa_glacct-itemno_acc = '0000000002'.
wa_glacct-gl_account = '0000089000'.
wa_glacct-item_text = 'GL account'.
APPEND wa_glacct TO lt_glacct.
wa_curramt-itemno_acc = '0000000001'.
wa_curramt-curr_type = '00'.
wa_curramt-currency = 'EUR'.
wa_curramt-amt_doccur = '-1000.00'.
APPEND wa_curramt TO lt_curramt.
CLEAR wa_curramt.
wa_curramt-itemno_acc = '0000000002'.
wa_curramt-curr_type = '00'.
wa_curramt-currency = 'EUR'.
wa_curramt-amt_doccur = '1000.00'.
APPEND wa_curramt TO lt_curramt.
CLEAR: wa_curramt,wa_glacct,wa_vendact.
CALL FUNCTION 'BAPI_ACC_DOCUMENT_POST'
EXPORTING
    documentheader = wa_docheader
IMPORTING
    obj_type       = lv_objtyp
    obj_key        = lv_objkey
    obj_sys        = lv_objsys
TABLES
    accountgl      = lt_glacct
    accountpayable = lt_vendact
    currencyamount = lt_curramt
    return         = lt_return.
IF sy-subrc EQ 0.
WRITE:/ lv_objtyp.
WRITE:/ lv_objkey.
WRITE:/ lv_objsys.
LOOP AT lt_return INTO wa_return.
    WRITE:/ wa_return-message.
    CLEAR wa_return.
ENDLOOP.
COMMIT WORK AND WAIT.
ENDIF.
Hope this solves your problem.
Regards,
Brajvir

Errors in BDC and LSMW

Hi Guys,
While transforming the data from the legacy to sap system using BDC or LSMW.
Generally what r the errors we face while performing the process.
POINTS WILL B ASSIGNED
Thanks and regards
KK

HI,
Error in LSMW getting return code 6 , after asign a file , in the read data step i am getting the error .
I got an error while converting data in LSMW as
'For type "C" , a maximum length specification of 65535 is allowed'.
bdc:
BDC errors are similar to what you get in online transaction. Suppose you enter an invalid material number in online ME21N ( create Po ) system will throw an error and you have to correct it by chnaging a valid material number . Same error you can get in BDC as well. It is very difficult to generalize types of error as errors will depend on the transacation you are doing.
However some of the common BDC errors are ( Data for Screen Not Found, Field Not available in Screen ). These again are transaction specific and you have to analyze it by calling the transacion in display ALL mode.
The errors you get depends upon the transaction you are
running.
PLS:AWARD POINTS IF USEFUL.
SRI

Bdc and lsmw

Hi All,
I am presuming that both bdc's and lsmw are being used for data migration. if this is right then when would someone prefer bdc over lsmw or vice versa. if my assumption is wrong then tell me for what specifications we use lsmw and for what specs we use a bdc.

Hi,
"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."
The following was taken at this site :
http://www.info-sun.com/docs/wp_sapinter.pdf
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.
Remote Function Call (RFC) in SAP R/3 is based on UNIXs Remote Procedure Call (RPC). RFC enables the real-time link between different R/3 instances and can connect SAP to Non-SAP systems. With Remote Function Call, both inbound (RFCServer) and outbound (RFCClient) interfaces are possible.
SAP also provides a toolkit called RFC API for non-SAP systems to interact with SAPs Function modules remotely.
RFC is a very powerful tool for interfacing with SAP system in real time. Most other interfacing techniques like ALE, EDI, BAPI etc are
inherently based on the RFC technology.
Electronic Data Interchange (EDI) is the industry standard format for exchanging Business data. SAP uses a neutral format called Intermediate Document
(IDoc) for communicating EDI & ALE messages.
The IDoc interface contains data structures and processing logic for each of the business transaction. These are grouped as Message
Types. The external EDI Server is responsible for receiving the EDI messages sent by the trading partners. These EDI messages are then
mapped onto the IDoc structure fields and stored in the IDoc interface layer by SAP.
EDI/IDoc supports both inbound and outbound interfaces. The IDocs received through the EDI Server can be configured to automatically get
processed, or can be stored in the IDoc interface layer for a future manual or scheduled processing. The IDoc interface layer also has a powerful error
handling, reporting, monitoring and reprocessingmechanism built into it (Transaction WEDI). IDoc is also tightly integrated with the WorkFlow system
of SAP for initiating other business tasks upon receiving/sending EDI messages.
The IDoc interface can be employed for non-SAP applications to load or extract data from SAP system. But typically, EDI / IDoc is engaged when
SAP system is to be integrated with any of its business partners (Customers, Suppliers and other partners) for carrying out standard business
transactions (like Create Sales orders, Sending Purchase orders to Suppliers, etc).
Application Link Enabling (ALE) is a middleware tool, which is part of SAPs Business framework Architecture (BFA). ALE can effectively be used
for loosely coupled Asynchronous communication between SAP systems and with non-SAP systems. ALE is based on the distributed processing
architecture and hence integrates applications with the local database rather than centralized one. ALE messages are based on the Intermediate
Document (IDoc) format, similar to the EDI counterpart. Though ALE can be used to interface with non-SAP systems, usually it is used to
distribute Master & Transactional data between SAP R/3 instances.
The ALE distribution can be based on,
Business APIs
IDoc Message Types"
Business API (BAPI) is the most important component of SAP Business Framework. BAPI enables SAP and third party applications to interact and integrate
with each other at the Business Object / Process level.

Faq on bdc and lsmw

hi all,
i want some faq on lsmw and bdc.
thanks in advance.

Hai,
1. What is BDC ?
2. What is call transaction method ? what is the
syntax/procedure?
3. What is session method and what is the
syntax/procedure?
4. Difference between call transaction & session method?
5. which of these methods can be best used in background
process?
6. What is direct input method?
7. How LSMW is advantageous than normal BDC?
8. what are the steps in lsmw?
9. IN LSMW can you use BAPI, ?
10. Can you call a bdc from a report program?
11. what is the difference between synchronus &
asynchronus methods?
12. call transaction uses synchronus or synchronus method?
13. session method uses synchronus or synchronus method?
14. What is bapi?
15. how bapi is different from call transaction/session?
16. what r the advantages of bapi?
17. for uploading master data(ex:customer data) into sap,
which methods you prefer? call
transaction/session/lsmw/bapi? why?
18. tell any 2 standard bapi function modules used for
uploading sales order data?
Regards,
Padmam.

Whwn to use BDC and When to use LSMW

Hi all,
Kindly tell me when to use BDC and when to use LSMW.
Please give me some scenarios, so that I can get a clear idea.
Note : Do not give the difference between BDC and LSMW.
Thanks to all in advance.
Regards,
Rajesh P

Hi Rajesh,
LSMW is for standard SAP applications and BDC is for customized applications.
Its worth to check the below link. Its already answered by our Community
Diff between LSmw and Bdc
Regards,
Suresh

Difference among BDC eCATT and LSMW

Hi guys,
   May I have your attention please?
   I encounter difficulities regarding the relation among the above Data Transfer Tools.
   So far,I have learned a little about these tools, and done some data batch input from
local drive.I find the three tools can deal with the same thing. So my question is what
distinction exists among them since they are similar so much?
Thank you

Refer these links might be useful -
Differences between BDC , LSMW, BAPI,CATT
LSMW Vs BDC
Difference between BDC and LSMW
Regards,
Amit
Reward all helpful replies.

Diff b/w mk01 and mk02 using lsmw

what is diff b/w mk01 and mk02 to transfer data using lsmw
which steps are different, what are those

what is diff b/w mk01 and mk02 to transfer data using lsmw
which steps are different, what are those

Unable to Update infotype 586 and 585 through BDC or LSMW

Dear Sir/ Madam,
I am in process of updating actual investment by employee in info type 0586 and 585.
I have already inputed the projected investments in 586 & 585 and as per tax tax is computed.
Also I have written a LSMW to update in the actual Tick.
But the problem is now I want to update actual investemnet using BDC, But my ABAper is unbale to do so as the records has been sorted on the projected investmnet ( ascending order),.
As this is to be updated for nearly 2500 records which vary ..
IKinldy suggest any standard program availble or in BDC can I use the investvent codes in Table T7INI3
Regards
Deepak Gadekar

Hi,
Recording of psv2 and psv1 are complex.
I have done it using BDC since i need to do certain validations.
Go with BDC rather than LSMW.
Kindly mention the fields u need to update.Based on it u can decide on BDC or LSMW?
Edited by: Thyagu on Jun 15, 2009 11:51 AM

In LSMW, what is diff between LSMW-BAPI and LSMW-IDOC

hello all
In LSMW, what is diff between LSMW-BAPI and LSMW-IDOC

Hi Swamy,
The differences between IDoc and BAPI are as follows:
IDOC
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system.
Idocs are processed asynchronously and no information whatsoever is returned to the client.
The target system need not be always online. The IDOC would be created and would send the IDOC once the target system is available (tRFC concept). Hence supports guaranteed delivery.
With asynchronous links the sub-process on the client can be finished even if the communication line or the server is not available. In this case the message is stored in the database and the communication can be done later.
The disadvantage of asynchronous links is that the sub-process on the server cannot return information to the calling sub-process on the client. A special way for sending information back to the client is required. In addition, a special error handling mechanism is required to handle errors on the receiving side.
IDOCs may be more changeable from release to release.
IDOCs are poorly documented.
BAPI
BAPIs are a subset of the RFC-enabled function modules, especially designed as Application Programming Interface (API) to the SAP business object, or in other words: are function modules officially released by SAP to be called from external programs.
BAPIs are called synchronously and (usually) return information.
For BAPIs the client code needs to do the appropriate error handling.
Problems with synchronous links occur if the communication line or the server is temporarily not available. If this happens, the sub-process on the client cannot be finished (otherwise there would be data inconsistencies).
Synchronous links have the advantage that the sub-process on the server can return values to the sub-process on the client that has started the link.
BAPIs are not totally immune to upgrades.
BAPIs are reasonably well documented.
Reward points if useful.
Best Regards,
Sekhar

Diff bet eCATT and LSMW

Hello Guru's,
Will anyone clarify me the diff between eCATT and LSMW ?. shall we have eCATT for uploading Legacy data to R/3?.
<REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Jun 12, 2008 12:08 PM

eCATT is an SAP Testing Tool used to automate & test business scenarios in R/3. Each test generates a detailed log that documents the test process and results. If the testing is smooth without any errors, this means that the business scenarios mapped in R/3 are correct. If the test results in error then the problem can be analyzed using the error log that is generated.
eCATT enables automatic testing in SAP GUI for Windows and SAP GUI for Java.
Features of eCATT:
Following functions can be performed using eCATT:
Test transactions, reports and scenarios.
Call BAPIs and function modules.
Test remote systems.
Check authorizations (user profiles).
Test updates (database, applications, GUI).
Set up customizing tables.
Test the effect of changes to customizing settings.
Perform load testing.
Check system messages.
Integrated with Test Workbench, so allows proper management of scripts using SCAT transaction.
Supports CATT migration to eCATT.
All eCATT Objects are Repository Objects. Therefore one can take advantage of Standard SAP Transport Tools.
eCATT Objects can easily download & upload in XML with XSD format.
There can be several versions of Test Scripts, which allows different implementations with different releases.
The separation of Test Scripts, Test Data & System Data allows for a considerable degree of reuse.
All eCATT Objects are Repository Objects. Therefore one can take advantage of Standard SAP Transport Tools.
eCATT Objects can easily download & upload in XML with XSD format.
eCATT- An Introduction
/people/sumeet.kaul/blog/2005/07/26/ecatt-an-introduction
2) http://allaboutsap.blogspot.com/search/label/LSMW
also u can findout many threads in the forum itself no need to wait for new posts(if u get, that also from forum itself)
Thanks

Adv of BDC over LSMW

What are the advantages of BDC over LSMW?

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
i hope it is clear
plz do let me know, if any update.
Thanks,
Sankar M

Diff b/w BDC and LSMW

Similar Messages

Maybe you are looking for