Sap 6.0 features

hi,
  what are the new features in sap 6.0 than sap 5.0

ECC 5.0 is based on WAS 6.40 and ECC 6.0 is based on WAS 7.00.
From functional point of view there are some minor differences, as the core functionalities are not changed a lot. However there is Industrial Solutions integrated to ECC 6.0 by default.
http://solutionbrowser.erp.sap.fmpmedia.com/

Similar Messages

  • SAP BI New Features???

    Hi,
    Is there any way to find out details of an imported support pack...we are working on SAP BI 7.0 support pack 17.
    We jumped from SP13 to SP17 and there are few new features which i am not able to get any info docs anywhere...(SAP Marketplace, Help.sap.com)
    Regards,
    Aadil

    hi
    i sent u some features of bi 7.0
    Metadata Search (Developer Functionality) :
    1.     It is possible to search BI metadata (such as InfoCubes, InfoObjects, queries, Web templates) using the TREX search engine. This search is integrated into the Metadata Repository, the Data Warehousing Workbench and to some degree into the object editors. With the simple search, a search for one or all object types is performed in technical names and in text.
    2.     During the text search, lower and uppercase are ignored and the object will also be found when the case in the text is different from that in the search term. With the advanced search, you can also search in attributes. These attributes are specific to every object type. Beyond that, it can be restricted for all object types according to the person who last changed it and according to the time of the change.
    3.      For example, you can search in all queries that were changed in the last month and that include both the term "overview" in the text and the characteristic customer in the definition. Further functions include searching in the delivered (A) version, fuzzy search and the option of linking search terms with u201CANDu201D and u201CORu201D.
    4.     "Because the advanced search described above offers more extensive options for search in metadata, the function ""Generation of Documents for Metadata"" in the administration of document management (transaction RSODADMIN) was deleted. You have to schedule (delta) indexing of metadata as a regular job (transaction RSODADMIN).
         Effects on Customizing
         Installation of TREX search engine
         Creation of an RFC destination for the TREX search engine
         Entering the RFC destination into table RSODADMIN_INT
         Determining relevant object types
         Initial indexing of metadata"
    Remote Activation of DataSources (Developer Functionality) :
    1.      When activating Business Content in BI, you can activate DataSources remotely from the BI system. This activation is subject to an authorization check. You need role SAP_RO_BCTRA. Authorization object S_RO_BCTRA is checked. The authorization is valid for all DataSources of a source system. When the objects are collected, the system checks the authorizations remotely, and issues a warning if you lack authorization to activate the DataSources.
    2.       In BI, if you trigger the transfer of the Business Content in the active version, the results of the authorization check are based on the cache. If you lack the necessary authorization for activation, the system issues a warning for the DataSources. BW issues an error for the corresponding source-system-dependent objects (transformations, transfer rules, transfer structure, InfoPackage, process chain, process variant). In this case, you can use Customizing for the extractors to manually transfer the required DataSources in the source system from the Business Content, replicate them in the BI system, and then transfer the corresponding source-system-dependent objects from the Business Content. If you have the necessary authorizations for activation, the DataSources in the source system are transferred to the active version and replicated in the BI system. The source-system-dependent objects are activated in the BI system.
    3.     Source systems and/or BI systems have to have BI Service API SAP NetWeaver 2004s at least; otherwise remote activation is not supported. In this case, you have to activate the DataSources in the source system manually and then replicate them to the BI system.
    Copy Process Chains (Developer Functionality):
    You find this function in the Process Chain menu and use it to copy the process chain you have selected, along with its references to process variants, and save it under a new name and description.
    InfoObjects in Hierarchies (Data Modeling):
    1.      Up to Release SAP NetWeaver 2004s, it was not possible to use InfoObjects with a length longer than 32 characters in hierarchies. These types of InfoObjects could not be used as a hierarchy basic characteristic and it was not possible to copy characteristic values for such InfoObjects as foreign characteristic nodes into existing hierarchies. From SAP NetWeaver 2004s, characteristics of any length can be used for hierarchies.
    2.      To load hierarchies, the PSA transfer method has to be selected (which is always recommended for loading data anyway). With the IDOC transfer method, it continues to be the case that only hierarchies can be loaded that contain characteristic values with a length of less than or equal to 32 characters.
    Parallelized Deletion of Requests in DataStore Objects (Data Management) :
    Now you can delete active requests in a DataStore object in parallel. Up to now, the requests were deleted serially within an LUW. This can now be processed by package and in parallel.
    Object-Specific Setting of the Runtime Parameters of DataStore Objects (Data Management):
    Now you can set the runtime parameters of DataStore objects by object and then transport them into connected systems. The following parameters can be maintained:
    u2022        Package size for activation
    u2022        Package size for SID determination
    u2022        Maximum wait time before a process is designated lost
    u2022        Type of processing: Serial, Parallel(batch), Parallel (dialog)
    u2022        Number of processes to be used
    u2022        Server/server group to be used
    Enhanced Monitor for Request Processing in DataStore Objects (Data Management):
    1.      For the request operations executed on DataStore objects (activation, rollback and so on), there is now a separate, detailed monitor. In previous releases, request-changing operations are displayed in the extraction monitor. When the same operations are executed multiple times, it will be very difficult to assign the messages to the respective operations.
    2.      In order to guarantee a more simple error analysis and optimization potential during configuration of runtime parameters, as of release SAP NetWeaver 2004s, all messages relevant for DataStore objects are displayed in their own monitor.
    Write-Optimized DataStore Object (Data Management):
    1.      Up to now it was necessary to activate the data loaded into a DataStore object to make it visible to reporting or to be able to update it to further InfoProviders. As of SAP NetWeaver 2004s, a new type of DataStore object is introduced: the write-optimized DataStore object.
    2.      The objective of the new object type is to save data as efficiently as possible in order to be able to further process it as quickly as possible without addition effort for generating SIDs, aggregation and data-record based delta. Data that is loaded into write-optimized DataStore objects is available immediately for further processing. The activation step that has been necessary up to now is no longer required.
    3.      The loaded data is not aggregated. If two data records with the same logical key are extracted from the source, both records are saved in the DataStore object. During loading, for reasons of efficiency, no SID values can be determined for the loaded characteristics. The data is still available for reporting. However, in comparison to standard DataStore objects, you can expect to lose performance because the necessary SID values have to be determined during query runtime.
    Deleting from the Change Log  (Data Management):
    The Deletion of Requests from the Change Log process type supports the deletion of change log files. You select DataStore objects to determine the selection of requests. The system supports multiple selections. You select objects in a dialog box for this purpose. The process type supports the deletion of requests from any number of change logs.
    Using InfoCubes in InfoSets (Data Modeling):
    1.      You can now include InfoCubes in an InfoSet and use them in a join. InfoCubes are handled logically in InfoSets like DataStore objects. This is also true for time dependencies. In an InfoCube, data that is valid for different dates can be read.
    2.      For performance reasons you cannot define an InfoCube as the right operand of a left outer join. SAP does not generally support more than two InfoCubes in an InfoSet.

  • SAP HANA Spatial Features (Store Error)

    I've been stumbling with an the folowing error : "Error: SAP DBTech JDBC: [2048]: column store error: search table error: " over and over again. Every time I add a spatial column to a table it becomes unsuable (can't query, edit, add, update) so I have to delete the whole table and repopulate it, which is really annoying. Sometimes it doesn't happen right away, sometimes it works just fine at first but after a few minutes or hours the table just stops "working". It has happened several times with different tables.
    If anyone can tell me why is that happening or how to solve it I would be very grateful.
    I'm using Hana Version 1.00.74.00.390550.
    Thanks in advance.

    Hi Dario,
    Does the calculation view work without xsodata service? From the URL, your XS project name should be Project_DM, but from the xsodata source, the project name is EricssonItalgas. I'm confused with this. Did you use rewrite_rules or?
    Best regards,
    Wenjun

  • SAP MRS product features and modules integrated

    Hi
    Looking for SAP MRS product details with modules integrated
    Regards,
    Parameshwar

    Yes i possibly feel there are some more services which are not activated in the system.
    Try using Transaction NWBC in SAPGUI & then follow the various Applications to to reach to appointment booking.
    Once NWBC opens follow the service advisors cockpit. /DBM/SERVICE_ADVISOR.
    Step by step it will first ask you to search vehicle / customer & then once vehicle is searched you can continue to proceed to appointment application to book an appointment
    Ensure the master data is set up for the vehicle & customer to be able to search in the service advisors cockpit
    Ensure you have all the roles of the assigned to your user id these application appear in the your users menus.
    Regards,
    Sachin Balmiki

  • Can SAP provide this feature in PI7 or PI7.1?

    Hi Expert,
    We have an option to trace the userid of manualy canceled message in the ABAP stack of XI in SXI_MONITOR. Is there any option we can trace the userid of the  manualy canceled message in the RWB or in the Adapter Engine?
    thanks to all of you
    Sugata B Majumder

    If you really want to achieve your requirments here, you probably need to investigate the following blog:
    Interesting ABAP tables in XI u2013 Part I
    /people/gourav.khare2/blog/2007/12/12/interesting-abap-tables-in-xi-150-part-i
    The information you needed might be stored in some PI tables, then you can write ABAP reports to get them.
    Regards.
    Liang

  • Credit Card Number Encryption Feature in SAP

    Hi,
    I am interfacing between legacy system and SAP(probably through BAPI). The Credit card master table is VCNUM.
    The requirement is to have the Credit card number in the encrypted form. Does SAP has any feature that supports encryption feature?
    Please do reply with valuable suggestions.
    Thanks & Regards,
    Rajesh

    Hi,
    You can refer to below <b>threads</b>:
    Encryption / Decryption of Credit Card Number
    Re: Password encryption in SAP
    Re: Information regarding encryption.
    Hope you find your solution here.
    Reward points for useful answers
    Rgds,

  • Print a report from SAP Mobile

    Hi,
        I want to print a report (not a screen shot) from iPad (SAP Mobile/SAP BI), but there is no option there for printing.  I don't think this feature is available in the current SAP Mobile (6.1.11).  Can anyone have a way to work around it?  Can SAP add this feature as an enhancement in the future releases?
        Thanks.
                    James

    Hi,
    The feature is not available in Mobile BI App. You can search an existing idea and vote up or post a fresh at IDEA Place SAP BusinessObjects Mobile: Ideas.
    Would be helpful if you provide the following details
    - What is the business use case
    - How many users would be using this feature
    - What content types you are expecting to print
    - How should the printed report look like - mobile view, web view, pdf view
    - Primary used device - IOS/Android
    Regards,
    Ashutosh

  • What is difference between SAP R3 And SAP IS Mills Product

    HI Friends
    What is difference between SAP R3 And SAP IS Mills Product
    What are the futures are availables in IS MIlls
    Regards

    Hi,
    SAP R/3 is the central enterprise version. It is not specifically designed for any inducstry sectors and it can cater many of the industry types.
    Is is developed for specific industries an for SMB's (small and medium business). It will have components specifically for the industry.
    The SAP Mill Products component adds sector-specific functionality to an ERP system to satisfy the complex requirements of mill industries (e.g. metal, wood, paper, textiles, construction materials, and cable sectors).
    These industry segments differ from others primarily in that the materials used have a large number of characteristics and variants. The materials in the segments listed above are also predominantly area-based (e.g. paper, textiles, plastic film) or length-based (e.g. cables, piping). Account must be taken of these material characteristics throughout the entire supply chain.
    To cater for the particularities of these industry segments, SAP Mill Products features processes and functions that cover the entire supply-chain cycle – from product design and configuration, through planning, order processing, capacity planning and production, to final delivery. Additional functions are available in costing and inventory management. SAP Mill Products are also integrated into Quality Management, Financial Accounting, and Controlling.
    Prase

  • SAP R/3 and DSXI tool

    Hi All,
    Before posting this thread i have googled on how SAP DSXI tool can be used to ensure proper address data maintanance in SAP and couldnt succeed in finding any good info.
      Our requirement is we use external tax system(Sabrix) for calculating taxes for R/3 transactions. As we know in U.S and Canada the one important parameter for calculating taxes is the Jurisdiction code of the customer. This will be determined by the third party system when ever any address data is maintained in SAP system either it is customer master, plant/shipping point etc...
    The thing is to return a unique jurisdiction the third party system expects that SAP sends the complete address like country,state,district, postal code , Postal code +4 geocode value.  When creating the customer master data manually or during mass upload our user will have only  5 digit Postal code/zip code, they dont have the information of +4 geocode value of the zip code (which becomes 9 digits in total). Since the geocode value is not maitained in SAP, the tax system wont be able to determine the jurisdiction and it errors out the transaction.
      We thought of making it mandatory to enter the geo code value when the cusotmer master data is maintained, but this will not solve our purpose as most of the time at the time of customer master creation the users wont be having the +4 geocode value.
    I heard about SAP tool "DSXI" which can be used to get the geo code value.  Does any one have an idea on what is this tool and how it can be used / integrated with SAP and what features the DSXI tool is capable to do. Any inputs/documentation in this regard is highly appriciated.
    Thanks & Regards,
    Srinivas

    Hi Lakshmipathi,
             Thanq so much for your inputs. Can we find any documentation in sap help or service.sap on how to integrate SAP and DSXI. Basically our requirement is when ever a customer master is created with out GEOCODE value (ZIP+4 value), that customer record need to be picked by DSXI and update it with the geo code value. For this we want to know any standard interfaces/programs exist to link up SAP R/3 and DSXI.
    Thanks,
    Srini

  • SAP Lumira 1.18 - Error while publishing story to Lumira Server

    Hi,
    I installed Lumira Server and did the configuration in SAP Fiori as mentioned in the blog below.
    Simplified SAP Lumira Server Feature Configuration
    I created following users with mentioned roles.
    LSADMIN - sap.bi.admin::BI_CONFIGURATOR and sap.bi.admin::BI_ADMIN
    LUMIRADEV - sap.bi.common::BI_DATA_ANALYST
    LUMIRADEMO - sap.bi.common::BI_DATA_CONSUMER
    I logged into SAP Fiori with LSADMIN and successfully added Lumira Configuration Tile to New Group "SAP Lumira Server" and Configured all the roles for Technical user (LUMIRATECH) that has sap.bi.common::BI_TECH_USER role assigned. It was successful. Please see the screenshot below.
    After this when I tried to publish a story (created using excel data) from SAP Lumira Desktop application to SAP Lumira Server with LUMIRADEV user, I am getting below error.
    Do I need to give any additional privileges to LUMIRADEV/LUMIRADEMO ids to be able to create/view stories?
    Please suggest.
    Thanks,
    Abhijit

    Hi Henry,
    We have SAP HANA SPS 08 Database Revision 82.
    I suspect this is an issue with some HANA Authorizations. So as a random trial, I assigned MODELLING role to LUMIRADEV user and also granted SELECT rights on LUMIRADEV schema to _SYS_REPO with grant option. Post that I noticed, I could publish Stories created on HANA in Online mode to Lumira Server with out any issue but still having same issue for other data sources e.g. HANA Offline, Excel etc.
    Please let me know if there are any additional rights required for LUMIRADEV user.
    Thanks,
    Abhijit

  • SAP Lumira Server 1.18 - Error While creating visualization

    Hi,
    I installed Lumira Server 1.18 and configured as mentioned in the blogs below.
    Simplified SAP Lumira Server Feature Configuration
    I created following users with the roles mentioned -
    LSADMIN - sap.bi.admin::BI_CONFIGURATOR and sap.bi.admin::BI_ADMIN
    LUMIRADEV - sap.bi.common::BI_DATA_ANALYST
    LUMIRADEMO - sap.bi.common::BI_DATA_CONSUMER
    I did the configuration in SAP Fiori mentioned in the blog with LSADMIN id. I also had Technical user id LUMIRATECH with sap.bi.common::BI_TECH_USER role which was used for configurations in Fiori. It was successful. Please see the screenshot below.
    After that I logged on to SAP Lumira Server Launchpad (http://<SERVER>:80<INSTANCE>/sap/bi/launchpad) with LUMIRADEV user. I acquired the dataset from excel. But when I tried to create visualization post successful acquisition, I am getting below error on dropping any dimension/measure on to chart.
    Please help. Do I need to give any additional rights to LUMIRADEV?
    Thanks,
    Abhijit

    Hi Henry,
    We have SAP HANA SPS 08 Database Revision 82.
    Are there any additional authorizations required for LUMIRADEV user (user which is used for Lumira Server). Please note I am able to publish stories and data sets created on top of HANA Online connection from Lumira Desktop and I am able to access, edit Stories as well as create visualization from published data set on Lumira Server. I suspect this is an issue with authorization.
    Appreciate your help.
    Thanks,
    Abhijit

  • Daily morning report mentioning the availability of the SAP systems ?

    Hello,
    We have been asked by the business team to send them every morning at 8h00, a report that would mention which SAP systems are available.
    For the moment,we are doing that manually.
    Of course CCMSPING has already been implemented on our Solution manager, but as you can imagine we generate emails only when the satelites systems are not availables.
    But this is not what has been asked to us, the business team want to know which systems are available every morning.
    I did some researchs about sap solution manager feature that could fulfill this requests but I couldn't find it.
    The SLR (Service Level Reporting) can not be used : because SLR reports are generated weekly.
    Any idea would be highly appreciated.
    Best Regards.
    Thanks

    You can difine in trx SM36,  a new JOB, in button SPOOL LIST RECIPIENT add every the email, or distribution list that you need.  In the button STAR CONDITION must indicate PERIOD VALUES at 8:00 that every day.
    Regards

  • New G/L features

    Hi All
    I'm in a greenfield implementation for FICO module. We are going to implement SAP in ECC 6.0. My doubt is that whether i can activate the new features in Ecc 6.0 (since i read that we need to activate the new G/L features only at the time of the start of new fiscal year & we are going to go live in the mid of fiscal year) or just go for SAP 4.7 features alone? Plz advise on the approach.
    Regards
    Rajaram

    If your implementation is a new implementation then the New GL accounting should be activated from the start.  It doesn't really matter, if you Go-Live in mid of the fiscal year or at the end.
    If the project is an upgrade from a previous version of SAP then it's better to activate New GL at the start of new fiscal year.
    Regards,

  • SAP-BW general

    Hi,
    I am working as an abaper and have got an opportunity to move to SAP-BW. I dont have much idea about BW. please throw some light on BW and guide me whether to move from abap to BW.
    thanks and regards
    victor

    Hi,
                   BIW is mostly on reporting side
    The reporting, analysis, and interpretation of business data is of central importance to a company in guaranteeing its competitive edge, optimizing processes, and enabling it to react quickly and in line with the market. As a core component of SAP NetWeaver, the SAP Business Information Warehouse (SAP BW) provides data warehousing functionality, a business intelligence platform, and a suite of business intelligence tools that enable businesses to attain these goals. Relevant business information from productive SAP applications and all external data sources can be integrated, transformed, and consolidated in SAP BW with the toolset provided. SAP BW provides flexible reporting and analysis tools to support you in evaluating and interpreting data, as well as facilitating its distribution. Businesses are able to make well-founded decisions and determine target-orientated activities on the basis of this analysis.
    SAP Business Information Warehouse
    Purpose
    The reporting, analysis, and interpretation of business data is of central importance to a company in guaranteeing its competitive edge, optimizing processes, and enabling it to react quickly and in line with the market.  As a core component of SAP NetWeaver, the SAP Business Information Warehouse (SAP BW) provides data warehousing functionality, a business intelligence platform, and a suite of business intelligence tools that enable businesses to attain these goals. Relevant business information from productive SAP applications and all external data sources can be integrated, transformed, and consolidated in SAP BW with the toolset provided. SAP BW provides flexible reporting and analysis tools to support you in evaluating and interpreting data, as well as facilitating its distribution. Businesses are able to make well-founded decisions and determine target-orientated activities on the basis of this analysis.
    The following graphic shows how the SAP BW concept is structured. Data Warehousing, BI Platform and BI Suite represent the core areas of SAP BW.
    Integration
    The following graphic shows where SAP BW is positioned within SAP NetWeaver. Furthermore, those subareas that incorporate SAP BW are listed. These are described in detail below.
    Integration with Other SAP NetWeaver Components
    BEx Information Broadcasting allows you to publish precalculated documents or Online links containing Business Intelligence content to SAP Enterprise Portal (SAP EP). The portal role Business Explorer illustrates the various options that are available to you when working with content from SAP BW in the Enterprise Portal.  For more information, see Information Broadcasting.
    You are able to integrate content from SAP BW in SAP EP using the BEx Broadcaster, the BEx Web Application Designer, the BEx Query Designer, KM Content, the SAP Role Upload or the Portal Content Studio. For more information, see Integration into the SAP Enterprise Portal. For an overview of the ways in which BI content can be integrated into the Enterprise Portal, see Overview: Ways of Integrating and Displaying BW content in the Portal.
    The documents and metadata created in SAP BW (metadata documentation in particular) can be integrated using the repository manager in Knowledge Management in SAP Enterprise Portal. The BW Metadata Repository Manager is used within BEx Information Broadcasting. For more information, see BW Document Repository Manager and BW Metadata Repository Manager.
    You can send data from SAP and non-SAP sources to SAP BW using SAP Exchange Infrastructure (SAP XI). In SAP BW the data is placed in the delta queue where it is available for further integration and consolidation. Data transfer using SAP XI is SOAP-based. For more information, see Data Transfer Using SAP XI.
    Integration with SAP BI Content Add-On
    With SAP BI Content, SAP delivers pre-configured role and task-based information models and reporting scenarios for SAP BW that are based on consistent metadata.  SAP BI Business Content offers selected roles in a company the information they need to carry out their tasks. The information models delivered cover all business areas and integrate content from almost all SAP and selected external applications.
    SAP BI Content is delivered as an add-on to SAP BW.
    Features
    SAP BW Subareas
    Area
    Description
    Data Warehousing
    Data warehousing in SAP BW represents the integration, transformation, consolidation, cleanup, and storage of data. It also incorporates the extraction of data for analysis and interpretation. The data warehousing process includes data modeling, data extraction, and administration of the data warehouse management processes.
    The central tool for data warehousing tasks in SAP BW is the Administrator Workbench.
    BI Platform
    The Business Intelligence platform serves as the technological infrastructure and offers various analytical technologies and functions. These include the OLAP processor, the Metadata Repository, Business Planning and Simulation, special analysis processes such as Data Mining, and the Reporting Agent.
    BI Suite: Business Explorer
    The SAP BW Business Intelligence Suite, the Business Explorer (BEx), provides flexible reporting and analysis tools for strategic analyses, operational reporting, and decision-making support within a business. These tools include query, reporting, and analysis functions. As an employee with access authorization you can evaluate past or current data on various levels of detail, and from different perspectives, not only on the Web but also in MS Excel.
    You can use BEx Information Broadcasting to distribute Business Intelligence content from SAP BW by e-mail either as precalculated documents with past data, or as links with live data. You can also publish it to the Enterprise Portal.
    The Business Explorer allows a broad spectrum of users access to information in the SAP BW using the Enterprise Portal, the Intranet (Web application design) or mobile technologies.
    Development  technologies
    ·        BI Java SDK
    With the BI Java SDK you can create analytical applications with which you access both multidimensional (Online Analytical Processing or OLAP) and tabular (relational) data. You can also edit and display this data. BI Java Connectors, a group of four JCA-enabled (J2EE Connector Architecture) resource adapters, implement the BI Java SDK APIs and allow you to connect applications that you have created with the SDK to various data sources.
    ·        Open Analysis Interfaces
    The Open Analysis Interfaces make various interfaces available for connecting front-end tools from third-party providers. 
    ·        Web Design API
    The Web design API and table interface allows you to realize highly individual scenarios and demanding applications with customer-defined interface elements.
    The following graphic shows how subareas and their functions are integrated into the SAP BW architecture:
    Regards

  • Regarding Migrating data from Legacy to SAP

    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.

    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:
    Diff. between LSMW & BDC
    Re: bdc and lsmw
    plz reward points if it helps
    rgds.

Maybe you are looking for