2007 Aug 07 6:43 PM
Hi Experts,
Can anyone tell me the DRAWBACKS/disadvantages of LSMW?
Thanks
Dany
2007 Aug 07 8:42 PM
Hi Dan,
The main disadvantages with LSMW are
1) It will not handle the large amount of data even though it handles it is not advisable to process large amount of data with LSMW due to performance reason.
2) It will not support the call transaction method.
3) It will not handle the dynamically calling screens
Thanks,
Vinay
Hi Experts,
Can anyone tell me the DRAWBACKS/disadvantages of LSMW?
Thanks
Dany
2007 Aug 07 8:36 PM
It is very much a developers tool - I am currently struggling to find ways to make it bullet proof for an average user.
Another drawback is that depending on what method (DI/BI/BAPI) you can have multiple ways of execution and finding errors.
Correcting errors is very much a manual process (unless you load to a non-production environment and get all of your errors out of the import file).
This is all an opinion - take with a grain of salt.
2007 Aug 07 8:42 PM
Hi Dan,
The main disadvantages with LSMW are
1) It will not handle the large amount of data even though it handles it is not advisable to process large amount of data with LSMW due to performance reason.
2) It will not support the call transaction method.
3) It will not handle the dynamically calling screens
Thanks,
Vinay
2007 Aug 08 5:33 AM
Hi Dan,
LSMW is an encapsulated data transfer tool. It can provide the same functionality as BDC .
<b>Advantages:</b>
1 no need to write large code .almost 60% logic is provided by the tool only.
2 LSMW mapping is done by SAP
3 we can transfer data using session ,direct Input BAPI and IDOC
4.used for single time data transfer
5.It is mostly used for standard transaction codes and predefined objects.
<b>Disadvantage :</b>
only used for single data transfer.
only used for large amount of data.
<b>BDC:</b>
<b>Advantages:</b>
1 used for small as well as large amount of data.
2 we can transfer data for customized applications as well as predefined applications
3 we can transfer data through Recording with Session,Call transaction and Direct Input method.
4 We can check errors in sm35 in case of session method
<b>Disadvantages:</b>
doesn't support enhancements.
we have to provide explicit mapping.
BDC is the way to transfer data by writing a batch input program which can use either session or call transaction method.
LSMW used to transfer data without/less code.
What type of data we transfer using LSMW?
LSMW is best suited for transferring master data.
Actually BDC and LSMW are not comparable at all.
for example LSMW itself can use BDC as a way of mass data transfer.
BDC is a mass data transfer technique via screen logic of existing SAP Data entry transactions. It behaves as if you are manually making thousand of entires into sap system as a background job. And that is probably the reason why BAPI's are preffered over BDC's.
On the other hand LSMW is a tool to facilitate DATA migration from other legacy systems ... It contains step by step procedure for data migration.
Like Managing Data Migration Projects , Creating Source Structures , Mapping Source structures wid Target structures , etc etc
LSMW internally might well be using the following techniqes for data transfer..
1. IDOX
2. Direct Input / BDC
4. BAPI's
LSMW is an encapsulated data transfer tool. It can provide the same functionality as BDC infact much more but when coming to techinical perspective most the parameters are encapulated. To listout some of the differences :
LSMW is basicaly designed for a fuctional consultant who do not do much coding but need to explore the fuctionality while BDC is designed for a technical consultant.
LSMW offers different techinque for migrating data: Direct input ,BAPI,Idoc,Batch input recording. While bdc basically uses recording.
LSMW mapping is done by SAP while in BDC we have to do it explicitly .
LSMW is basically for standard SAP application while bdc basically for customized application.
Coding can be done flexibly in BDC when compared to LSMW
"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."
<b>Reward Points if Useful</b>
Regards
Gokul
| User | Count |
|---|---|
| 4 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |