LSMW is mostly used to migrate data from non-sap legacy system to SAP.

The tool supports conversion of data of the legacy system in a convenient way. T he data can then be imported into the R/3 system via 1. Batch input. 2. Direct input. 3. BAPIs or IDocs. Following are the principles for LSMW 1. Most of the functions should reside in R/3. No collection of individual progr ams on different platforms. 2. The quality and consistence of the data imported into R/3 should be more impo rtant than speed and performance of data migration. 3. Existing knowledge and coding should be used. 4. The developed "mapping" and rules should be reusable and thus be used repeate dly in projects. The main functions of the LSMW are: 1. Import data (legacy data in spreadsheet tables and/or sequential files) 2. Convert data (from source format to target format) 3. Import data (into the database of the R/3 application) The following items should be considered: 1. Make sure that R/3 customizing is finished. 2. Determine the data contained in your legacy system and which of the data will be required in the future (with respect to business operation). 3. Decide whether it makes sense to use this tool with respect to the data volum e to be transferred. Preconditions 1. Identify the transaction(s) in R/3 via which you want to import the data into your SAP system. 2. Map the fields in advance in written form: Assign the source fields to the ta rget fields. 3. Determine the form in which non-SAP data will be transferred into the SAP sys tem (e.g. via "Move" or according to a rule). 4. In which way will the data be extracted from the non-SAP system? Note: The LS MW does not extract data. 5. In which form is the legacy data available? Determine accordingly which of th e LSMW functions will be applied. CATT1. What CATT does is record you performing the actual transaction once.

2. You then identify the fields that you wish to change in that view. 3. Then export this data to a spreadsheet to populate with the data required. 4. This is uploaded and executed saving you keying in the data manually. 5. To perform CATT, it has to be enabled in your production environment (your sy stems administrator should be able to do this - SCC4). 6. You will also need access to your development system to create the CATT scrip t. The use of CATT is for bulk uploading of data. Although CATT is primarily a test ing tool, it can be used for the mass upload of data. The way CATT works is like a real user actually inputting on the SAP screen. You prepare a set of data tha t are required to be input into the system and execute what you called a Test Ca se and CATT will do the boring task of keying for you.