Advantages of LSMW over BDC

What are the advantages of LSMW over BDC ? In which context we would be using LSMW ?
( as per my idea ,LSMW doesnt require any coding and would be used by functional consultants.Apart from this any other advantages of using LSMW ? )

Hi,
Apart from the advantages that you mentined in your question,
we can directly process LSMW with the help of IDOC BAPI through LSMW.
And if we create 1 project in LSMW we can create multiple sub projects and in 1 sub project we create multiple objects.
So by this facility we can use the Object and sub project with in the whole project.
And in LSMW we have a very good facility like conversions fixed rules and constant maintaining facility.
So LSMW is far better than using BDC programs.
We have lot of facilities like Auto field mapping and many others .
When we come to use it we know it better.

Similar Messages

LSMW Vs BDC

what is the differnece between LSMW and BDC
what is the additional advantage of BDC over LSMW

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
1. Do not require ABAPer for this. Any SAP functional person can do this.
2. Do not have to do Recording , using SHDB.
3. No Coding requirer, just follow simple 13-14 steps.
If it is helpful please give me reward point.
Thanks
Murali Poli

Lsmw and bdc r mandatory to sd

hello gurrus,
is lsmw and bdc r mandatory for sd.
bye

Hi Basha,
We cannot say that LSMW and BDC are mandatory for SD.
LSMW is actually a tool to upload data into SAP. BDC is also a program which can be used for the same purpose.But LSMW is not available with the earlier versions of SAP. Ex: versions 3.1H and 3.1I.BDC was used most of the times.LSMW has got more advantages than BDC in terms of less coding,easy to use etc.
Hope this helps.
Please reward if useful.
Thanks,
Srinivasa

Difference in lsmw and bdc

What is the advantage of using lsmw instead of bdc whether there is any disadvantage in using 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/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.
Call transaction.
1) asynchronous processing
2) can transfer small amount of data
3) processing is faster.
4) errors need to be handled explicitly
5) data is updated automatically
Session method.
1) synchronous processing.
2) can tranfer large amount of data.
3) processing is slower.
4) error log is created
5) data is not updated until session is processed.
Session method is to populate the data by filling BDC structure
and keep as session to process from SM37 to post in appropriate Transaction.
Call transaction method is to post the data directly into the Transaction from an Executable program.
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
some more links
BDC
http://www.sap-img.com/bdc.htm
LSMW
http://www.sap-img.com/sap-data-migration.htm
http://www.sapgenie.com/saptech/lsmw.htm
http://sapabap.iespana.es/sapabap/manuales/pdf/lsmw.pdf
http://www.sap.info/public/INT/int/glossary/int/glossaryletter/Word-17643ed1d6d658821_glossary/L#Word-17643ed1d6d658821_glossary
Thanks
Manju

Differnce b'w lsmw and bdc

pls tell the differnce b'w lsmw and bdc . when we use bdc and when we use lsmw .for uploading master data (ex: cusomer data ) in tosap which method s u prrefer out of thhse 4
method scall transaction
session input
lsmw bapi whic one is the better one
when use session method and when we use call tran sac
which method is better for bacjground processing call tran s or session method . pls tell
the reason
answres as soon as possible

Hi,
LSMW IS JUST A TOOL TO GET THE DATA FROM A LEGACY SYSTEM.
IN BDC WE HAVE 2 WRITE THE CODE AND CALL THE REQUIRED METHOD
THATS IT. IN FUNCTIONALITY PERSPECTIVE THERE IS NO
DIFFERENCE.
BDC is Batch Data Communication. It is basically a program
either generated by SAP after a recording or programmed by a
abaper.Its like running the transaction manually but all the
data is populated on the screens automatically.It is a
little complex when the screens contain table controls.
LSMW is legacy system migration workbench is a more user-
friendly tool thru which one can do the same as a BDC. One
just has to follow some 14 steps, click buttons and the data
is set to be uploaded ….LSMW offer you 4 ways to import data
into SAP, they are BDC, Direct Input, BAPI(BO), IDOC.
To spell out the differences in detail:
look at the below threads to know more
Diff between LSmw and Bdc
Diff. between LSMW & BDC
Regards
Sudheer

What is the advantages of polymorphism over method overriding?

what is the advantages of polymorphism over method overriding,that means if we are able to to create object at different instances at diff time for that sub class reff variable than what is the need of careating object of super class data type(i.e why always it is necessary to have upcasting for polymorphism?but if we can achive the same output without upcasting).....please tell me..lets have complete discuss..

Seriously though....
WebLogic (for which I have deployed many apps on) as
well as Websphere are both high end Java application
servers, meaning J2EE servers (in short). They allow
one to deploy Enterprise Archive(EAR), a Web
Archive(WAR), or an EJB Archive (in a JR file).
These two servers allow one to deploy EJBs, use
e JNDI, JMS, connectors, and other J2EE technologies
- Tomcat does not. well, EJBs - no
JNDI, yes - http://tomcat.apache.org/tomcat-4.1-doc/jndi-resources-howto.html
JMS - yes (with an implementation, such as ActiveMQ: http://activemq.codehaus.org/Tomcat)
Not sure what you mean by "connectors".
Tomcat provides quite a bit of functionality (but yes, no EJBs)

Data Migration using LSMW or BDC ?

Hi,
Can anyone provide me with the following information about uploading MM Master Data using LSMW or BDC :-
1. What and all tables are used for uploading Material Master, Vendor Master, Info Record, Open PO, Open PR, RFQ, Open Contracts/Agreements ?
2. What problems are faced during Data Upload ?
3. What error appears/encouontered during upload ?
4. What is the diffrence b/w LSMW and BDC ? Both can be used for Data upload so, what differences are b/w them ?
5. Any other thing to remember/know during Data Upload ?
Thanks,
Lucky

Hi Lucky,
Dont get angry by seeing my response.
See each and every question posted by u is available , in this forum,
u need to do just a search on individual post.
see what ever ur posted, u r definetly got the solutions through others,
remember most of these answers are fetching by this threads itself (60-70%)
a few solutions are there that are given by own,
so better to search first, in the forum , if not satisfied with the solutions then .........
Just its an friendly talk
and Reward points for helpful answers
Thanks
Naveen khan

Advantage of DMS over "Services for object" functionality

Hi Experts,
I have got very basic doubt about advantages of DMS Over existing standard functionality of SAP.
We can attach documents or files to SAP Objects using "services for object" push button ( Next to title bar).
So please answer for my below queries
1. What is the disadvantage of using Services for Object??
2. If I use services for object, then file is stored in SAP Data base or in my local drive??
Thanks and Regards,
Kiran T

Hello ,
DMS Vs GOS
DMS- Document Management System
The Document Management System (DMS) in SAP R/3 offers the following distinct advantages over the current procedures and systems.
u2022     It avoids data redundancy, maintains consistency of data and minimizes the workload involved in entering and updating data.
u2022     In order to use large databases to the full, it is required to exchange data quickly and securely. Data can be accessed directly using electronic search tools, or find documents using known parameters.
u2022     Document distribution functionality (SAP-Workflow functionality is required)
The SAP R/3 Document Management System meets all these demanding requirements. In addition to managing documents, it also coordinates document processing. It is possible to automate the entire life cycle of a document: from document creation to document storage, its access and its update. Each document can be accessed immediately from any computer on the netwerk.
GOS-
All these DMS advantages are not available with GOS.
The Detailed PPT of comparison is sent to your id.
Regards
fapreeth

Advantages of BPC over BI-IP

Dear All,
I am new to BPC NW and would like your expert views on some of my observations on the much debated advantages of BPC over BI IP.
One of the benefits of BI IP was the integrated reporting capabilities with a common master data and combining the transaction data (actual and budget). However, as I understand BPC is intentionally not integrated with backend BW.
BW master data is different and separate from BPC master data, thus it is not possible to integrate BPC cubes with BW cubes. To view an actual vs plan comparison, data would need to be copied / loaded back and forth between the BW cubes and BPC cubes. However, it does not seem practical in scenarios where planning requires significant amount of actual data. Moreover, this would mean multiple reporting interfaces for the users.
BPC will be driven by Business users.
What is it that we are empowering the business users with? The ability to define his own dimensions / applications/ dimension members / Input schedules?
Usually planning requirement is not just a simple input enabled screen. There are many more functionalities that would be required which would need writing of logic, code etc. Loading of master / transaction data requires creation of transformation, conversion files and data packages. Obviously, these tasks would not be done by the business users.
To be honest, I am slightly concerned over giving the business user a free reign on creating objects in the system. Without proper training, things could get out of hand with duplicate objects popping up everywhere in the system. Another area of concern is possibility of modeling same data differently in BPC and BW. It might cause complexities while integrating the data between the two
BPC seem to be targeted to facilitate financial planning. However, we require planning for areas outside finance (headcount, volume allocation / distribution etc). I would have assumed that a reporting application of Type u2018Genericu2019 would have the flexibility to include only the required dimensions as opposed to having to include the standard dimensions of type A, E, T and C.
When compared to BI IP, I am not sure if BPC NW in its current form would be the best tool to deliver integrated planning in multiple areas.
Having said that, these are still early days for BPC NW. Hopefully we will see a tighter integration of BPC NW with BW and more flexible planning in non-financial areas in the future releases.

Thank you for your statement regarding the issues of using BPC in the context of BW. I very much appreciate your excellent comments.
Also thank you for providing the link to the statement about the advantages of using BPC because of the Excel user interface. It certainly does appear that SAP marketing is trying to get customers to move to Business Objects and BPC. Of course, it would be a strong advantage to be able to leverage the existing skills of Excel users.
We already own Integrated Planning and it appears to satisfy the immediate business requirements. We would have to pay for the software licences for BPC, which we don't currently own. Of course, we don't want to pay for these BPC licenses when we already own the IP licenses that will satisfy the requirements.
In addition, it indeed looks as though SAP is positioning BPC to use the Business Objects universe. Although we know that, eventually, we will probably have to convert to selected components of Business Objects for business intelligence, we don't want to have to once again make another substantial investment in SAP business intelligence when we so recently made such a large investment in the SAP Business Information Warehouse. We will have not yet earned our return on investment on the Business Informastion Warehouse.
Given the timing, we don't think it is fair that SAP expects companies to once again have to pay for the business intelligence software and to implement Business Objects, convert from the Business Information Warehouse to Business Objects, redevelop, retrain, and redeploy all the reports using the Business Objects tools. The customers will incur additional costs because of the reimplementation, conversion, redevelopment, retaining, and redeployment of the reports. Without this kind of consideration, in these economic times, it will be difficult for the installed base of companies to justify the conversion to Business Objects, and, consequently, for SAP to realize a reasonable return on its, not insignificant, investment in Business Objects.
SAP should provide an existing customer of the components of the Business Information Warehouse a migration path to the corresponding Business Objects components of comparable capabilities at no additional license fee as long as the customer is current on its maintenance. Of course, adjustments in the license fees and annual maintenance fees should be made if there are differences in functional and/or quality capabilities between the corresponding components of the Business Information Warehouse and Business Objects.
In our situation, we already and recently made a significant investment in the Business Information Warehouse and the Business Explorer (BEx) tools, implementation, and reports development. We don't want to have to pay to replace them with Business Objects. We thought we already paid big-time for the business intelligence tools and reports. We even paid for the BI Accelerator and have been very happy with its dramatic improvement on performance. We fear that a commitment to BPC may soon commit us to Business Objects, the latter of which, so far, carries a very large price.

Differences between LSMW and BDC

Hi All
Please can you give me the few points about the differences between LSMW and BDC?
Awaiting for your Responce
Praveen

Hai Check with the following document
GOOD
THERE IS THREE TYPE OF METHOD IN BDC
BDC SESSION
CALL TRANSACTION
CALL DIALOG
What is BDC or batch input
The Batch Input is a SAP technic that allows automating the input in transactions. It lies on a BDC (Batch Data Commands) scenario.
BDC functions:
· BDC_OPEN_GROUP : Opens a session group
· BDC_CLOSE_GROUP : Closes a session
· BDC_INSERT : Insert a BDC scenario in the session
· The ABAP statement "CALL TRANSACTION" is also called to run directly a transaction from its BDC table.
It runs the program RSBDCSUB in order to launch automatically the session. The session management is done through the transaction code SM35.
The object itself is maintanable through the transaction SE24.
BDC methods:
Method
Description
Parameters
OPEN_SESSION
Opens a session
SUBRC (Return Code 0 OK)
SESSIONNAME (Session to be created)
CLOSE_SESSION
Closes a session
None
RESET_BDCDATA
Resets the BDC Internal Table...
None. Normally, for internal purpose
BDC_DYNPRO
Handles a new screen
PROGNAME (Name of the program)
DYNPRONR (Screen Number)
BDC_FIELD
Puts a value on the screen
FIELDNAME (Name of the field)
FIELDVALUE (Value to be passed)
CONSTRUCTOR
Constructor - Initializes NO_DATA
NODATA (No data character). The constructor is called automatically when the object is created.
RUN_SESSION
Launches a session with RSBDCBTC
None
CALL_TRANSACTION
Calls a transaction with the current BDC Data
MODE (Display Mode)
UPDATE (Update Mode)
TCODE (Transaction to be called)
BDC_INSERT
Inserts the BDC scenario in the session
TCODE (Transaction to be called)
BDC techniques used in programs:
1) Building a BDC table and calling a transaction,
2) Building a session and a set of BDC scenarios and keeping the session available in SM35,
3) Building a session and lauching the transaction right after closing the session.
BDC using Call Transaction
BDC using Call transaction involves calling an SAP transaction in back ground from within the ABAP
program. The process involves building an Internal BDC table containing the screen information needed to
execute the required transaction and then passing this to the Call transaction command (See code example).
The full procedure for creating a BDC program is as follows:
What is the difference between batch input and call transaction in BDC?
Session method.
1) synchronous processing.
2) can tranfer large amount of data.
3) processing is slower.
4) error log is created
5) data is not updated until session is processed.
Call transaction.
1) asynchronous processing
2) can transfer small amount of data
3) processing is faster.
4) errors need to be handled explicitly
5) data is updated automatically
BATINPUT/DIRECT INPUT
A: Batch-inputs can not be used to fill the "delivery due list" screen because it is not a dynpro. This is a standard SAP report. A SAP report (check with "System -> Status") may be called using SUBMIT sentence with the appropriate options . It is preferred to call a report than create a Batch-input program.
GO THROUGH THIS LINK
http://www.guidancetech.com/people/holland/sap/abap/zzsni001.htm
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.
LSMW vs DX Workbench
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).
Experiences made in successful implementation projects have shown that using the LSM Workbench significantly contributes to accelerating data migration.
SAP provides this tool along with documentation to customers and partners free of charge.
Users of the LSM Workbench receive the usual support via SAP Net - R/3 Frontend (component BC-SRV-DX-LSM).
Releases:
Version 1.7.2 of the LSM Workbench ("LSMW 1.7.2") available
Attention : LSMW 1.7.2 requires an SAP R/3 system with SAP R/3 4.0 or SAP R/3 4.5.
Version 1.8.0 of the LSM Workbench (1.21mb) ("LSMW 1.8.0") available
Attention : LSMW 1.8.0 requires an SAP R/3 system with SAP R/3 4.6.
Version 3.0 of the LSM Workbench (1.89mb) ("LSMW 3.0") available for Web Application Server 6.10
Attention : LSMW 3.0 requires a SAP WAS 6.10. Functionality of version 1.7.2 and 3.0 are identical !
Version 4.0 of the LSM Workbench ("LSMW 4.0") integrated in Web Application Server 6.20
Attention : LSMW 4.0 is an integrated part of SAP WAS 6.20.
Thanks & regards
Sreenivasulu P
Message was edited by: Sreenivasulu Ponnadi

LSMW and BDC

Hi,
To post the data for RG23C with multiple Line Items in the J1IEX T-code is it advisable to use LSMW or BDC Program. B'cas through LSMW recording method the Multiple Line Items seems to be impossible to upload, and in BDC some of the screen fields are not being caputured.
Suggsestions and Help will be much appreciated.
Regards.
Ramesh.

Hello,
I guess such complex scenarios shall be handled theu BDC, as it gives a better control and flexibility.
If there are some fields in the table that are not getting captured during recording, verify that you are doing the required scrolling within the screen.
If still there is something not getting captured thru BDC, search for some OSS note.
Also try if there is a BAPI or Function to do the required posting, then you can avoid the BDC as well..simple and sweet
Regards,
Vishal

LSMW And BDC's

Can you send me the Documents and Links regarding LSMW and BDC's my id is [email protected]

hi,
check below sites
LSMW
http://www.sap-img.com/bdc.htm.
LSMW:
steps for LSMW: detail documnets: http://www.scmexpertonline.com/downloads/SCM_LSMW_StepsOnWeb.doc
http://sapabap.iespana.es/sapabap/manuales/pdf/lsmw.pdf
http://www.sap-img.com/sap-data-migration.htm
https://websmp207.sap-ag.de/lsmw
http://esnips.com/doc/8e732760-5548-44cc-a0bb-5982c9424f17/lsmw_sp.ppt
http://esnips.com/doc/f55fef40-fb82-4e89-9000-88316699c323/Data-Transfer-Using-LSMW.zip
http://esnips.com/doc/1cd73c19-4263-42a4-9d6f-ac5487b0ebcb/LSMW-with-Idocs.ppt
http://esnips.com/doc/ef04c89f-f3a2-473c-beee-6db5bb3dbb0e/LSMW-with-BAPI.ppt
http://esnips.com/doc/7582d072-6663-4388-803b-4b2b94d7f85e/LSMW.pdf
http://www.sap-img.com/sap-data-migration.htm
http://www.sapgenie.com/saptech/lsmw.htm
http://sapabap.iespana.es/sapabap/manuales/pdf/lsmw.pdf
http://www.sap.info/public/INT/int/glossary/int/glossaryletter/Word-17643ed1d6d658821_glossary/L#Word-17643ed1d6d658821_glossary
BDC
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d62292b3-0301-0010-df98-aaac31cd4a41
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d4c5e890-0201-0010-bd9a-c3fd8683fc97
http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm
excel sheet uploading:
http://www.sap-img.com/abap/upload-direct-excel.htm
http://www.sap-img.com/abap/excel_upload_alternative-kcd-excel-ole-to-int-convert.htm
http://www.sapdevelopment.co.uk/file/file_upexcel.htm
http://www.sapdevelopment.co.uk/file/file_upexcel.htm
http://www.sapdevelopment.co.uk/ms/mshome.htm
if useful don't forgot to give points.

LSMW or BDC

Hi Experts,
I do migration for FS00(G/L Account). I dont know which one is correct (LSMW or BDC)
Thanks advance,
Amudha.

Hi,
Thanks for your previous answer. Can you tell me which one is best for migrating below master data (Ex: LSMW or BDC)
1.Commitment Item
2.Price Master
3.Fund Center
4.cost element
Thanks and advance
Amudha

Advantages of HANA over BWA

Hi,
I am currently working on my thesis on the topic SAP BW on SAP HANA.
One of the topics that i want to emphasize is on the technical and the functional advantages of HANA over BWA.
P.S: I have collected some points after going through most of your discussions but i would welcome your opinions on the same.
Thank you.
Regards,
Joe

Interesting Question.
As far a an opinion is concerned;
I posed this question to a Google search.
" what are functional advantages SAP BW vs SAP HANA   "
The Resultant listing.
[   https://www.google.com/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=what%20are%20functional%20advantages%20SAP%20BW%20vs%20SAP%20HANA       ]
The first url answer is; Why SAP-HANA should start replacing BW!, SCN 2012.
The third; Does HANA Replace BW, (hint NO).
As you are writing an academic paper this could be the answer. My opinion there are none, no advantages.
From a current global ROI business perspective list the pros and cons for each, SAP BW and SAP HANA. My own opinion ten pros for SAP HANA;
1) Newer technology
2) Easier to deploy in the cloud
3) More head room, going forward bigger OLTP capacity.
4) Simple presentation of end result to you customer.
5) Show the customer an iPad with the solution running.
6) Show a youTube video with the SAP HANA cloud solution running
in side an e-mail.
7)   SAP HANA cloud solution is more affordable to smaller companys, $10 million to $100 million annual sales.
8)   A cloud deployment of SAP HANA localized by region based on language and culture.
9) I prefer SAP HANA cloud and mobile application deployment.
10) Current market conditions are move to mobile applications.
There are plenty of consultants that will point out the flaws in the above. And we can reduce the question to a matter of semantics.
But I hope this helps you and you can use it.

Uploading HR Master Data through LSMW or BDC

I want to upload the HR Master Data to the system through LSMW or BDC, I am aware that for some infotypes like 000,1 &2 BDC is more suited, whereas for other infotypes LSMW is more convenient. I would like to understand how to start the activity. Should I start with infotype 0000 first and then 0001 and so on or can I take any infotype randomly and upload? What I mean is, is there any dependency that an infotype data can be loaded only after certain other related infotype data is loaded first? e.g. can load infotype 0006 first and then infotype 0001?
Also please guide me on for which infotype LSMW is preferred and for which infotype BDC is preferred? Can BDC be used within LSMW?
-Shambhvi

Hi,
Do it like this way:- come into recording screen and give tcode PA40 now select in PA40 screen hiring action>execute> fill the details>save when 0001 screen wil open click on back button.> now in second step> give any name and discr.>save>back> third step> click on table button and give >
PERNR     c     8
EINDA     ddmm     10
SELEC_01     c     1
BEGDA     ddmm     10
ENDDA     ddmm     10
MASSN     c     2
MASSG     c     2
PLANS     c     8
WERKS     c     4
PERSG     c     1
PERSK     c     2
4) save it
5) select PA40 click on etras> auto feild mapping press enter when date format will come select 2nd option. save
7)specify flat file with tabular option
8) assign it
9, 10,11,12,13 & 14 just execute
Thanks and regards,
ARU

Advantages of LSMW over BDC

Similar Messages

Maybe you are looking for