cancel
Showing results for 
Search instead for 
Did you mean: 

Data migration

Former Member
0 Kudos

Hi Gurus

1.When do we migrate customer master data? is it in Production server?

is it by the time of cut over strategy? what is a functional consultant role in cut over strategy and what happens in cut over strategy?

2. Suppose i have master data already which went to go live already now i want to extend a customer master data to some other sales area, i have got too many records of this type tell me how can i do that?

thank you

with regards

anil

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

hi anil,

if you are upgrading to a new version hten the masters must have moved direclty at the time of tech upgrade. however if as part of a functional upgrade excercise u wish to change teh masters then they wud have to be created afresh on the production server. use of BDC and LSMW is recommended for this. but the old records wud and shud continue to remain on teh PRD as the users wud need to refer to them. make sure the old codes are blocked so that no new transactions can happen in them. its preferable that all teh three views are moved separately. at a subsequent date they can be archived.

data migration is a very critcal activity and is a part of the cut-over phase. the time and issues shud be properly envionsed by all concerned before hand else the problems wud be difficult to track. if you want to extend the sales view then you can incorporate the new data in your BDCs. a lot of work needs to be done to clean the data and may take a lot of time and strategic decisions to be made, like deciding not to migrate some data.

saurabh

Answers (2)

Answers (2)

Former Member
0 Kudos

HI ANIL

SAP Data Migration with LSMW

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.

This is one of the very powerful tools available in SAP to upload large amount of data to the system. This tools is comparable to ecatt or scatt. But the advantage LSMW has over them is the amount of data processed in single session. Moreover LSMW is easer to learn and execute.

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. eg for that can be mass deletion of purchase requisitions, mass deletion of planned orders etc.

For creating simple projects user can go to tcode LSMW and get started. All the steps are listed very nicely and system will not allow user to skip the steps enlisted. User will need to create Project, Subproject and Object.

Input to LSMW can be simple excel sheet or text tab delimited file(text file like note pad).

Example of a LSMW project in step wise manner is presented below:

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.

LSMW data migration for sales order VA01 / XD01 customer

LSMW using session method for data migration as follows

E.g. for XD01 (create customer)

initially there will be 20 steps but after processing 1 step it will reduced to 14 for session method.

1. T-Code: LSMW.

2. ENTER PROJECT NAME

Sub project name

Object name.

Execute.

3. MAINTAIN OBJECT ATTRIBUTES.

Execute

Select Batch Input recording

go to->recording overview

create

Recording name.

Enter transaction code.

Start recording

do recording as per your Requirement.

Save à Back.

Enter recording name in LSMW screen.

Save à Back

Now there will be 14 steps.

2. MAINTAIN SOURCE STRUCTURES.

Enter the name of internal table.

Display change

Create

Save à Back

3. MAINTAIN SOURCE FIELDS.

Display change

Select structure

Source_fieldsàCopy fields. (a dialogue window will pop out )

Select à From data file

Apply source fields

a. Enter No. of field's

b. Length of fields

c. Attach file

Save à Back.

4. MAINTAIN STRUCTURE RELATIONS

Display change

Save à Back.

5. MAINTAN FIELD MAPPING & CONVERSION RULE

Display change

Click on source field, select exact field from structure and Enter

***repeat these steps for all fields.

Save à Back.

6. MAINTAIN FIXED VALUES, TRANSACTION, USER DEFINED

Execute

Save à Back.

7. SPECIFY FILES.

Display change

Click on legacy data

Attach flat file

Give description

Select tabulators

Enter

Save à Back.

8. ASSIGN FILE

Execute

Display change

Save à Back.

9. IMPORT DATA.

Execute

Display change

Save à Back.

10. DISPLAY IMPORTED DATA

Enter ok ***it will show records only.

Back

11. CONVERT DATA

Execute

Display change

Save à Back.

12. DISPLAY CONVERTED DATA

Execute

Display change

Save à Back.

13. CREATE BATCH INPUT SESSION

Tick keep batch input folder

F8

Back

14. RUN BATCH INPUT SESSION.

SM35 will come

Object name will be shown here

Select object & process

REWARD IF USEFUL TO U

Former Member
0 Kudos

Masters will be extended at the time of Cut over strategy.....cut over strategy is.....by what extent you are going to operationalise your newly builtup production server...so it all depends upon company's policy...whether to go say..70 % first & say rest 30 % later on...etc etc....for migrating Customer Master..LSMW and SCAT can be used...now SAP has introuduced a new tool for Historical data of Customer or even transactional data migration from Legacy System through ADM..i.e. Accelerated Data Migration.

on your 2nd query..say if you have the customer existing in 1 sales area and you want to extend that to another sales area/s....again you can do that throgh LSMW/SCAT...the limitation with LSMW being that at a single shot you can go for a max of 5000 records.

Reward Points if it helps,

Regards,

N

null