Explore topic-wise InterviewSolutions in .

Yes. It is POSSIBLE to BUILD PERIODIC interfaces USING the frame program /SAPDMC/SAP_LSMW_INTERFACE

Yes. It is possible to build periodic interfaces using the frame program /SAPDMC/SAP_LSMW_INTERFACE

YES, but:

EXPORT has to be programmed

Source STRUCTURES have to be defined

Fields of the source structures can be loaded from the dictionary

Mapping has to be done manually è a lot of fields!! Automatic fieldmapping might be used Import of large data amounts can take a lot of time (most of the time data amount is higher than for Migration from legacy systems) History data can not be BUILD up most of the time

Yes, but:

Export has to be programmed

Source structures have to be defined

Fields of the source structures can be loaded from the dictionary

Mapping has to be done manually è a lot of fields!! Automatic fieldmapping might be used Import of large data amounts can take a lot of time (most of the time data amount is higher than for Migration from legacy systems) History data can not be build up most of the time

There is no specific training COURSE for LSMW LSMW is PART of the 5-day standard training BC420 Workshops at customer site are done at CUSTOMERS charge Examples in the media CENTER can be used for self-study

There is no specific training course for LSMW LSMW is part of the 5-day standard training BC420 Workshops at customer site are done at customers charge Examples in the media center can be used for self-study

No. The LSM Workbench is available FREE of charge to SAP’s customers and PARTNERS

No. The LSM Workbench is available free of charge to SAP’s customers and partners

No. The LSM WORKBENCH can be DOWNLOADED for FREE from SAPNET: HTTP://service.sap.com/LSMW

No. The LSM Workbench can be downloaded for free from SAPNET: http://service.sap.com/LSMW

Yes. The LSM WORKBENCH can READ the data directly from your PC. Only when USING the periodic interface, the data has to be on a server accessible by R/3

Yes. The LSM workbench can read the data directly from your PC. Only when using the periodic interface, the data has to be on a server accessible by R/3

No. BUSINESS objects such as MATERIAL master, CUSTOMER master or FI DOCUMENT are migrated

No. Business objects such as material master, customer master or FI document are migrated

No. The LSM workbench provides the MAIN conversion techniques at the PUSH of a button. For complex CONVERSIONS, individual ABAP CODING can be added.

No. The LSM workbench provides the main conversion techniques at the push of a button. For complex conversions, individual ABAP coding can be added.

Yes. The LSM WORKBENCH WORKS on the PRINCIPLE of central (reusable) rules. This approach guarantees that, for EXAMPLE, the material number is converted in the same way wherever the reusable rule is USED for conversion.

Yes. The LSM Workbench works on the principle of central (reusable) rules. This approach guarantees that, for example, the material number is converted in the same way wherever the reusable rule is used for conversion.

YES. The data is loaded via the standard INTERFACES of the applications. This will include all CHECKS that are run for ONLINE transactions. Invalid data will be rejected.

Yes. The data is loaded via the standard interfaces of the applications. This will include all checks that are run for online transactions. Invalid data will be rejected.

By means of standard TRANSFER programs: a wide range of MASTER data (e.g. G/L accounts, customer master, vendor master, material master, bills of material) and transaction data (e.g. financial documents, sales orders)

By means of RECORDING of transactions: further data objects (if the transaction can be run in batch INPUT mode)

By means of standard transfer programs: a wide range of master data (e.g. G/L accounts, customer master, vendor master, material master, bills of material) and transaction data (e.g. financial documents, sales orders)

By means of recording of transactions: further data objects (if the transaction can be run in batch input mode)

Importing legacy data from PC SPREADSHEET tables or sequential files

Converting data from its ORIGINAL (legacy system) format to the target (R/3) format

Importing the data using the standard interfaces of R/3 (IDOC inbound processing, batch INPUT, DIRECT input)

Importing legacy data from PC spreadsheet tables or sequential files

Converting data from its original (legacy system) format to the target (R/3) format

Importing the data using the standard interfaces of R/3 (IDoc inbound processing, batch input, direct input)

The LSM Workbench is an R/3-based TOOL that supports single or PERIODIC DATA TRANSFER from your non-SAP system to R/3.

The LSM Workbench is an R/3-based tool that supports single or periodic data transfer from your non-SAP system to R/3.

No. of steps VARIES for different import METHODS. Initially there will be 20 steps but after processing step 1 it will reduced to 14 for SESSION method.

No. of steps varies for different import methods. Initially there will be 20 steps but after processing step 1 it will reduced to 14 for session method.

WIDE range of Master DATA (e.g. G/L accounts, CUSTOMER master, vendor master, material master, bills of material) and Transaction Data (e.g. financial DOCUMENTS, sales orders) can be migrated using LSMW.

Yes, the imported data will be consistent because the data is LOADED via standard interfaces of the applications which will include all checks that are run for online transactions. 

Wide range of Master Data (e.g. G/L accounts, customer master, vendor master, material master, bills of material) and Transaction Data (e.g. financial documents, sales orders) can be migrated using LSMW.

Yes, the imported data will be consistent because the data is loaded via standard interfaces of the applications which will include all checks that are run for online transactions. 

YES, transaction CODES can be created from SHD0 for LSMW Objects.

Yes, transaction codes can be created from SHD0 for LSMW Objects.

YES, data can be transferred from one R/3 System to another. Export functionality has to be PROGRAMMED to ACHIEVE the same.

Yes, data can be transferred from one R/3 System to another. Export functionality has to be programmed to achieve the same.

Yes, Validations can be carried out in LSMW. Similarly custom CODE can also be added in LSMW. Validations can be handled in 5th step (MAINTAIN field mapping and CONVERSION rules) of LSMW.

For EXAMPLE, if you are updating VENDOR Master, You will need to carry out a validation to check whether vendor is valid or not.

Yes, Validations can be carried out in LSMW. Similarly custom code can also be added in LSMW. Validations can be handled in 5th step (Maintain field mapping and conversion rules) of LSMW.

For example, if you are updating Vendor Master, You will need to carry out a validation to check whether vendor is valid or not.

Generally Multiple RECORDINGS are DONE for transactions which has multiple access sequences like VK11, TK11, ETC. BATCH Input Method is capable of handling multiple recording and Batch Input recording is one of the IMPORT methods available in LSMW. So yes, LSMW can be used for handling multiple recordings.

Generally Multiple Recordings are done for transactions which has multiple access sequences like VK11, TK11, etc. Batch Input Method is capable of handling multiple recording and Batch Input recording is one of the import methods available in LSMW. So yes, LSMW can be used for handling multiple recordings.

The 3 main FUNCTIONS of the LSMW are:

• Reading the legacy data from one or several files (e.g. spreadsheet tables, sequential files).
• Converting data from its original (legacy system) format to the target (SAP) format
• Importing the data using standard interfaces (Batch INPUT, DIRECT Input, BAPI, IDoc) into the database of the R/3 application.

Transaction Code to start the LSM WORKBENCH is LSMW.

The 3 main functions of the LSMW are:

Transaction Code to start the LSM Workbench is LSMW.

Data MIGRATION stands for data TRANSFER between two LIKE or alike systems. During SAP R/3 implementation the data NEEDS to be moved from legacy system to the SAP system. Sometimes periodic data transfer between R/3 and other system (interfacing) is also required. Both of the above form a part of data migration.

Significance of data migration are:

• Data migration comes in the end of R/3 implementation.
• To start with Data Migration first configuration should be fully completed
• Data migration is about 20% to 40% of the total implementation expenses.

The TOOLS for data migration are:-

• BDC (Batch Data Communication)
• LSMW (Legacy System Migration Workbench)

Data Migration stands for data transfer between two like or alike systems. During SAP R/3 implementation the data needs to be moved from legacy system to the SAP system. Sometimes periodic data transfer between R/3 and other system (interfacing) is also required. Both of the above form a part of data migration.

Significance of data migration are:

The tools for data migration are:-

There are four standard import METHODS available in LSMW.

IDOC's:

• ADVANTAGES: Fast to load, easy processing, low programming for standard IDOC’s.
• Disadvantages: Good knowledge of IDOC processing required, time consuming if changes have to be made to a created IDOC.

BAPI’s:

• Advantages: Fast to load, easy processing, logical interface for functional/end user based on the business processes involved.
• Disadvantages: Not always complete with all input FIELDS of a transaction.

STANDARD/DIRECT INPUT:

• Advantages: Well tested method, Fast to load, easy processing.
• Disadvantages: No enjoy transactions, not always complete with all input fields of a transaction.

BATCH INPUT:

• Advantages: Easy modifiable, all fields are available, easy re-processing.
• Disadvantages: Comparatively slow, to use new screens or tabs a new recording has to be created, not easily usable for enjoy transactions, DEPENDENT on user settings, difference in foreground and background processing may occur.

There are four standard import methods available in LSMW.

IDOC's:

BAPI’s:

STANDARD/DIRECT INPUT:

BATCH INPUT:

LSMW is not suitable for FREQUENT data transfer as there are a number of STEPS that are to be repeated EVERY time.

LSMW is not suitable for frequent data transfer as there are a number of steps that are to be repeated every time.

• It's a code free tool (however if REQUIRED coding can be done) - THEREFORE it helps functional people to upload data from legacy to SAP system.
• Since it's an uploading tool provided by SAP, it has a structured way of working. You will have to finish EVERY step before starting the NEXT step.
• Since it is integrated in R/3 it is independent of individual platform. The entire project can be downloaded and UPLOADED in any environment unlike BDC which has to be developed in development server and then transported to Production Server.
• It can be preferred when there is a need to upload large volume of data.
• It is preferred only if there is a requirement for one time transfer of data.

• In CASE if you trust the data in the flat file and know there is not much coding to be done, then we can use LSMW. On the other hand if there is a lot of validations to be done GO for BDC.
• Also LSMW can be preferred for uploading MASTER Data records and standard SAP applications. SINCE LSMW is a tool and generally it makes use of standard program/objects, the execution would be faster, and less effort is needed to upload master data.

• LSMW is basically designed for functional consultants who do not do much coding but need to explore the functionality while BDC is designed for a technical consultant.
• LSMW offers different technique for migrating data: Direct input, BAPI, I-Doc, 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.

LSMW is a tool provided by SAP in order to UPLOAD huge amount of data from legacy file to R/3 system. The Legacy System Migration Workbench (LSMW) is a tool to transfer data from legacy systems (Non SAP System) into an R/3 System (SAP System).

LSMW supports a step-by-step procedure; if one step is executed and saved then next step automatically FOLLOWS.

Apart from creation of PROJECT/ subproject/ object and recording, there are 14 BASIC steps included in LSMW.

Through LSMW one can create Master data, create transactional data, modify existing master data etc. This tool is very useful when some mass changes are to be carried out and no standard SAP transactions are available for that.

There are few standard objects available in LSMW e.g. material master, vendor master, customer master, purchasing info record, purchase requisitions, purchase orders etc. Using these standard objects one can do mass data upload and mass transactions.

Apart from this LSMW provides another functionality of recording the transaction and then carrying that out MANY times with large data. Examples are mass deletion of purchase requisitions, mass deletion of planned orders etc.

LSMW is a tool provided by SAP in order to upload huge amount of data from legacy file to R/3 system. The Legacy System Migration Workbench (LSMW) is a tool to transfer data from legacy systems (Non SAP System) into an R/3 System (SAP System).

LSMW supports a step-by-step procedure; if one step is executed and saved then next step automatically follows.

Apart from creation of project/ subproject/ object and recording, there are 14 basic steps included in LSMW.

Through LSMW one can create Master data, create transactional data, modify existing master data etc. This tool is very useful when some mass changes are to be carried out and no standard SAP transactions are available for that.

There are few standard objects available in LSMW e.g. material master, vendor master, customer master, purchasing info record, purchase requisitions, purchase orders etc. Using these standard objects one can do mass data upload and mass transactions.

Apart from this LSMW provides another functionality of recording the transaction and then carrying that out many times with large data. Examples are mass deletion of purchase requisitions, mass deletion of planned orders etc.