Scribd
Upload
105 views7 pages

Differences Between LSMW, BDC & LTMC in SAP

Uploaded by

RP Tech
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
105 views7 pages

Differences Between LSMW, BDC & LTMC in SAP

Uploaded by

RP Tech
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

1

DIFFERENCES
BETWEEN LSMW,
BDC & LTMC
IN SAP

Phone/Whatsapp: +1 (515) 309-7846 (USA)


Email: [email protected]
Website: www.zarantech.com
1 1

Differences between LSMW and BDC

BDC vs. LSMW


BDC and LSMW are the two data migration techniques (from legacy to
SAP). BDC technique is usually done by ABAPers.
Batch Data Communication (BDC):
BDC(Batch Data Communication) is basically a program which is either
generated by SAP after a recording or programmed by a abaper. It’s like
running the transaction manually but all the data is populated in the
screens automatically. BDC basically uses recording.There are two ways
of implementing BDC, the Call transaction metod and the Session
method. BDC is designed for a technical consultant.
Legacy System Migration Workbench(LSMW):
It is used for migrating the data b/w the Non-SAP and SAP application to
do for that we can take the Non-SAP application data and Converts the
data into the Legacy data.(Legacy data means Cleansing data and Purging
the data. After the Legacy data creation convert the data in to the "Flat
file".
That flat file is in the form of text file or excel format. If the file is in the
form of text format we can create the ".txt" file ("ABC.txt") and in the
form of excel ".xls" file is created. flat file for dos and .xls file for IBM. The
converted file (.txt/.xls) is either upload or download. The Upload
functionality if used for .txt file to SAP and where as Downloading is the
concept while SAP to .txt/.xls file. LSMW is basicaly designed for a
fuctional consultant who do not do much coding but need to explore the
fuctionality
Difference between BDC and LSMW
LSMW offers four ways to import data into SAP, and they are: BDC,
Direct Input, BAPI(BO) and IDOC.
LSMW is generally for normal SAP applications. BDC basically for
customized application.
LSMW is a Non-SAP to SAP communication TOOL, while BDC is a SAP to
SAP communication UTILITY.
LSMW is a more user-friendly tool, through which one can do the same
work as the BDC. One just has to follow the 14 steps.
In BDC, we can schedule the job, so the uploading can be done at the
same time or later periodically while in LSMW it has to be done at once
only.
In LSMW, mapping is taken care of with the help of SAP, whereas
in BDC one has to provide explicit mapping directions.
So through LSMW, one cannot upload huge amount of data. Hence we
use LSMW for updating or inserting below 5000 records and we
use BDC to upload records more than 5000.
Coding is not very flexible in LSMW, whereas in BDC coding is very
flexible and applications can be easily customized. this is mainly
because LSMW is devised specially for functional consultants who do not

Phone/Whatsapp: +1 (515) 309-7846 (USA) Email: [email protected]


www.zarantech.com
1 1

perform coding, while BDC is mainly used by technical consultants, who


perform coding
BDC and LSMW both are use for loading data into SAP system. The
difference is LSMW is loading tool by SAP where you can use various
methods to upload, massage data or cleansed your data while loading
into SAP from legacy system. The method can be BDC, BAPI, Idocs or
SAP ABAP codes. Usually in BDC the user has to write an ABAP program
or use other utility to load legacy data.
In case of BDC session can be processes multiple times according to the
requirement coming to LSMW it is used only one time, but it can have
periodical update. but the functionality can't be changed here.
LSMW is recommended for large amount of data.

Transitioning from LSMW to LTMC

After 20 years of success in the realm of R/3 and ECC, LSMW finally has a
viable competitor called LTMC or Legacy Transfer Migration Cockpit. LTMC
is native to S/4 and enjoys a small advantage over LSMW in most cases,
but only when implementing S/4; it isn't available for R/3 or ECC.

Understanding what LTMC is actually doing...

The inner workings of LTMC are going to be explained here in reverse


order of the training from SAP because, for ABAP programmers and
experienced Data Migration resources, it helps to understand at the
beginning what is happening under the hood. The thing to know at the
outset is that LTMC is a wrapper for BAPIs.

LTMC does a lot of the heavy lifting, but the hardest work is carried out
behind the curtain using BAPI's with specific requirements. These include:

Must have a simulation mode.


Must not commit (uses BAPI_TRANSACTION_COMMIT?)
Consistency and plausibility checks must be performed in the BAPI.
Must return report in a BAPIRET2 structure.
When calling the BAPI, the system cleverly teases the data to be loaded
out of an XML load file and into internal tables based on structures that
the BAPI expects to be importing. The system then calls the BAPI to
validate the data in the system or to commit the upload.
The BAPIRET2 internal table returned by the BAPI is then passed back to
the user as a report and stored in LTMC.

Source file templates made easy . . .

Phone/Whatsapp: +1 (515) 309-7846 (USA) Email: [email protected]


www.zarantech.com
1 1

One of the best features of the LTMC is its ability


to automatically generate a template file based on the expected structure
of the BAPI which makes starting the process incredibly convenient.
Because the XML files are likely to be populated in Excel by users, some
training will be required teach users how to maintain data integrity while
handling Excel files as copy-pasting can cause formatting issues that corrupt the
file.

This chart explains where the relationships between LSMW and LTMC exist
so that an LSMW user can be confident and proficient in under five hours
with just a little hand holding, self-study and experimentation.

Where LSMW still shines . . .

While the glossy brochure claims that LTMC can be used to migrate
data without programming, it ends up pushing the transformation to
wherever the source data is being prepared and validation back into the
SAP system. The example used when "Creating Your Own Migration
Object Using the Migration Object Modeler" calls a custom BAPI in the SAP
system which seems like it would require exponentially more work than
using LSMW; it would look something like this:

Phone/Whatsapp: +1 (515) 309-7846 (USA) Email: [email protected]


www.zarantech.com
1 1

LTMC LSMW

Get a developer key. Create a new LSMW object


Create structures in SE11 for in development system.
importing and exporting Create a recording.
parameters. Maintain the source structure.
Create a remote enabled Maintain the source fields.
function module with Map the source fields to
importing and exporting recording fields.
parameters (must be of type Import the original source file.
structure) in SE37. Create a batch.
Create a business object in Load the data using SM35.
SWO1. Export the LSMW object.
Insert RFC function module Import the LSMW object to
into business object. the quality system and test
Test the BAPI. there.
Produce copious amounts of Import the LSMW object to
documentation to demonstrate the production system and
that the BAPI does what it is load the data.
intended to do. Produce high-level report for
Create a transport to get BAPI user.
into a quality system.
Get a Solman account (if
BASIS team doesn't handle
this)
Test the function in third-party
system.
Get sign off from bureaucrats.
Transport the BAPI to
the quality system.
Activate and test the BAPI in
the quality system.
Produce more documentation.
Create another transport to
move BAPI

Phone/Whatsapp: +1 (515) 309-7846 (USA) Email: [email protected]


www.zarantech.com
1 1

to production system.
Get more sign off.
Transport BAPI to production.
Create custom migration
object in Migration Object
Modeler.
Create source structures.
Download template from
LTMC.
Carefully copy data from
source file to template.
Upload the new source file.
Activate the new source file.
Transfer the records.

These scenarios are oversimplified, but the process of writing reports and
functions is grossly oversimplified in the LTMC example above. LSMW, on
the other hand doesn't require transports to move custom code through
the development landscape for testing and then for use in the production
system.

LTMC comes with templates (based on best practices) containing the


fields that are most frequently used in order to avoid confusing users with
hundreds of esoteric fields that almost nobody uses. By using the
Migration Object Modeler, structures and fields can be added or removed from
the downloadable template in order to accommodate business requirements

Phone/Whatsapp: +1 (515) 309-7846 (USA) Email: [email protected]


www.zarantech.com
THANK YOU

Corporate Training Course Catalog


https://bit.ly/SAP-course-catalog

SAP Learner Community


https://www.linkedin.com/showcase/sap-learner-community/

Get any SAP Video Training


https://zarantech.teachable.com/courses/category/sap

Phone/Whatsapp: +1 (515) 309-7846


Email: [email protected]
www.zarantech.com

You might also like