cancel
Showing results for 
Search instead for 
Did you mean: 

Data migration

Former Member
0 Kudos

Hi Gurus,

Could anyone explain me how to start up with the data migration?

I KNOW HOW TO MIGRATE DATA USING LSMW, but pls tell me how to start up with users and what data i need to get from them?

2. how to clean the data?

thank you

with regards

anil

Accepted Solutions (1)

Accepted Solutions (1)

Lakshmipathi
Active Contributor
0 Kudos

Hi Anil

First you have to give templates of datas whatever you have to upload in bulk. Say for example, during Go-Live, you need to upload master datas like Customer Master, Material Master, Pricing Conditions etc.,

The templates should be in an excel file which should be filled in by either the Core Team members or the end users which will vary from company to company. Once they forward the completed data, the same has to be converted into a text file and upload through LSMW

Thanks

G. Lakshmipathi

Answers (3)

Answers (3)

Former Member
0 Kudos

Thanx alot everybody it was really good stuff and more relevent i appreciate that.

in the data sent by Shesagiri, i got the following questions

1.How to archive the data and who does that?

2. what is a redundant data record?

3. do we transfer the data at the time of CUT OVER STRATEGY?

thanks alot

with regards

chaitanya

Former Member
0 Kudos

No ABAP effort are required for the SAP data migration. However, effort are required to map the data into the structure according to the pre-determined format as specified by the pre-written ABAP upload program of the LSMW.

The Legacy System Migration Workbench (LSMW) is a tool recommended by SAP that you can use to transfer data once only or periodically from legacy systems into an R/3 System.

More and more medium-sized firms are implementing SAP solutions, and many of them have their legacy data in desktop programs. In this case, the data is exported in a format that can be read by PC spreadsheet systems. As a result, the data transfer is mere child's play: Simply enter the field names in the first line of the table, and the LSM Workbench's import routine automatically generates the input file for your conversion program.

The LSM Workbench lets you check the data for migration against the current settings of your customizing. The check is performed after the data migration, but before the update in your database.

So although it was designed for uploading of legacy data it is not restricted to this use.

We use it for mass changes, i.e. uploading new/replacement data and it is great, but there are limits on its functionality, depending on the complexity of the transaction you are trying to replicate.

The SAP transaction code is 'LSMW' for SAP version 4.6x.

For those with the older SAP version (4.7 and below), the data migration programs might not have been pre-loaded.

You can download the LSMW at no cost from SAPNet under Services, SAP Methodology and Tools, category Tools.

If you are an existing SAP customer with an OSS ID, you can access the SAP Service Marketplace to download the LSWM for your Basis teams to install to your SAP system: http://service.sap.com/lsmw

The LSM Workbench carries out the following tasks:

  • Reads the transfer data from one or more files (for example, spreadsheets, sequential files etc.)

  • Converts the data from the source format into the target format

Note that with background processing, the input file must not be located in the presentation server. Access to presentation server files is only possible when you are working online<a href="http://www.sap-img.com/sd001.htm">Upload Condition Pricing</a>

<a href="http://www.sap-img.com/general/lsmw-steps-for-data-migration.htm">LSMW STEPS</a>

<b>Data Cleansing</b>

Data cleansing allows you to compare, include and merge redundant business partner master records (potential duplicates) in data cleansing cases. Following the data cleansing process you can remove data records from the system using archiving.

Integration

Before you can carry out data cleansing, you must determine the redundant data in your system and include it in data cleansing cases.

You have the following options for duplicate recognition and creation of data cleansing cases.

  • The Business Address Services (BAS) provide interfaces for integrating the relevant external software (search machines).

  • User-defined programs

  • Services of data providers, who check their data for possible duplicates.

In the options described above, the data cleansing cases are created via the system and put into the data cleansing worklist for further processing.

  • In individual cases you can find potential business partner duplicates in the hitlist of the business partner search and create a separate data cleansing case.

After connecting the non-SAP software (search engines), the system starts duplicate recognition (Delta Scan) with every change to or new entry of a business partner for this specific individual record. You should do a full scan through the complete dataset at the beginning of the consolidation process using the non-SAP software, this registers all potential duplicates in data cleansing cases and makes them available or further processing.

Within the application basis, the referencing objects, which are taken into account by the data cleansing, are limited to the sub-objects of the business partner. You have the possibility to make modification-free enhancements to the referencing objects.

Prerequisites

You must have determined the redundant data records in your system.

To use the interface of the Business Address Services, make the following Customizing settings: SAP Implementation Guide -> Basis -> Basis Services -> Address Management -> Activate Duplicate Check Index Pool

Make the following system settings in the IMG of the SAP Business Partner: Basic Settings -> Data Cleansing -> Maintain Number Range / Define Priorities / Activate Data Cleansing.

Activities

Register data cleansing cases via BAPIs or create them in the dialog for business partner maintenance from the worklist or the business partner search.

Process the created data cleansing cases in a separate process step afterwards.

Former Member
0 Kudos

hi,

Mostly the migration will be of master data & transaction data. Master data like customer master, master master, pricing master. So u need to get the details of existing master data in execel file so that u can convert into TAB limited file/tabulator file etc........... & uploaded.

Example:

U need to get customer name, address, mail id, etc.....

U can also follow this link regarding LSMW, it gives u LSMW procedure with screen shot.

<a href="http://www.slideshare.net/arun_bala1/sap-sd-lsmw-legacy-system-migration-workbench">LSMW</a>

regards,

Arun prasad