on 04-23-2007 11:23 AM
Hi,
i have to update few customer master records using LSMW but i never worked on it.i have to migrate the CMRs from Legacy to sap. please provide me the steps to follow.this cld b very helpful.
thanks in advance.
cheers,
anil.
HI Anil,
give your mail ID
regards
Srini
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Anil,
Check these links to know about LSMW
http://www.sap-img.com/sap-data-migration.htm
http://www.sapgenie.com/saptech/lsmw.htm
http://sapabap.iespana.es/sapabap/manuales/pdf/lsmw.pdf
Step-by-Step Guide for using LSMW to Update Customer Master Records
Note! The screen prints in this article are from IDES Release 4.6. They may differ slightly in other versions.
Call Legacy System Migration Workbench by entering transaction code LSMW. Every conversion task is grouped together as Project / Subproject / Object structure. Create a Project called LSMW_DEMO and a Subproject as CUSTOMERS and Object as CUST_REC as shown in Figure 1.
Figure 1 Conversion Task with Project, Subproject and Object
The main screen of LSMW provides wizard-like step-by-step tasks, as shown in Figure 2. To complete your data conversion, you need to execute these steps in sequence. Once a step is executed, the cursor is automatically positioned to the next step.
Note that these steps may look different depending upon your Personal menu settings. You could make step numbers visible by Numbers on icon or hidden by Numbers off icon. You can execute a step by double-clicking on the row. Toggle icon Doubleclick=Display or Doubleclick=Edit, makes the step in display mode or change mode.
Figure 2 LSMW Wizard initial screen
Step 1: Maintain Object attributes
In this example, you will be updating the customer master records with the help of recording a transaction (XD02). Choose radio button Batch Input Recording and click on the recording overview icon to record the R/3 transaction. Enter the Recording name as XD02_REC, the description as Customer Master Updates Recording, and the transaction code as XD02.
Figure 3 Object type Transaction Recording
The system calls the transaction code XD02 and prompts you to complete the Change
Customer transaction, as shown in Figure 4. Enter the key customer information (I entered customer number 1000, sales organization 1000, distribution channel 01, and division 00) and choose Sales view within Sales area data. Make changes to these three fields (I entered, sales office 1010, sales group 110, and customer group 01) and save the transaction.
Figure 4 Transaction recording for Transaction Code XD02
Once the transaction is completed, R/3 records the flow of screens and fields and saves the information, as shown in Figure 5.
Default Values
Field Names
Figure 5 Transaction recording overview
Note that the fields are populated with default values. The values you entered when you recorded the transaction are set by default.
Note that if you have more fields in the recording than needed, you can remove them by clicking Remove Screen field icon.
Observe that the transaction-recording process stores field names in a technical format. By pressing the F1 key on individual screen fields and then pressing the F9 key, the system displays technical names. You then can replace the technical names with descriptive names. Double-click on the field RF02D-KUNNR and enter the name as KUNNR and the description as Customer Account Number and remove the default value. (See Figure 6.)
Figure 6 Field attributes
Similarly, double-click on all other fields with default values and make appropriate changes. Once you have made changes, the recording overview screen looks like what you see in Figure 7.
Figure 7 Transaction Recording Overview with screen field attributes
Save your changes. When you go back to the initial screen, you will see that the initial screen steps have changed. Since you want to import data via the BDC method, the Direct Input and IDoc-related steps are hidden, as they are not relevant.
Step 2. Maintain Source Structures
Give a name and a description to the source structure (Figure 8).
Figure 8 Source Structure
Step 3. Maintain Source Fields
In this step, you need to list what fields are present in the source structure. The easiest way is to click on Table Maintenance icon to enter Fieldname, Type and Length for each field as shown in Figure 9.
Figure 9 Source fields of source Structure
Note that your input file will have four fields as key fields and you need to update three fields in the system.
Step 4: Maintain Structure Relations
Execute a step to Maintain Structure Relations. (See Figure 10.) Since, there is only one Source and Target Structure, the relationship is defaulted automatically.
Figure 10 Structure Relation
Step 5: Maintain field mapping and conversion rules
Field RF02D-D0310 represents that you chose Sales view for the customer Master screen accordingly its value should be set to X. Keep your cursor on field RF02D-D0310 and click on Constant rule icon to choose the constant value of X.
If your source file already has the field value, you choose rule Source Field.
Keep cursor on field KUNNR and click on Assign Source field icon to choose source field CUSTOMER from structure XD02S as shown in Figure 11.
Figure 11 Assign source fields
Similarly, assign Source Field rules to the remaining fields.
Once all the fields are mapped, you should have an overview screen as shown in Figure 12.
Figure 12 Field mapping and Conversion rules overview
Step 6: Maintain fixed values, translations, user-defined routines
You can also maintain re-usable translations and user-defined routines, which can be used across conversion tasks. In this case, that step is not required.
Step 7: Specify files
In this step, we define how the layout of the input file is. The input file is a [Tab] delimited with the first row as field names. It is present on my PC (local drive) as C:\XD02.txt. (See Figure 13.)
figure 13 File attributes
Create an Excel file (Figure 14) with your data and save it as a Tab-delimited text file on your local drive (C:\) and name it XD02.txt.
Figure 14 Source data in Excel file (saved as Tab delimited file)
Step 8: Assign files
Execute step Assign Files (Figure 15) and the system automatically defaults the filename to the source structure.
Figure 15 Assign file to Source Structure
Step 9: Read data
In this step, LSMW reads the data (Figure 16) from the source file (from your PCs local drive). You have the option to read only selected rows and convert data values to Internal format.
Figure 16 Read Data
Step 10: Display read data
This step (Figure 17) is optional. If required, you can review the field contents for the rows of data read.
Figure 17 Display Read Data
Step 11: Convert data
This is the step that actually converts the source data (in source format) to a target format. Based on the conversion rules defined, source fields are mapped to target fields.
Step 12: Display Converted data
Again this is an optional step to view how the source data is converted to internal SAP format (Figure 18).
Figure 18 Display Converted Data
Step 13: Create batch input session
Once the source data is converted in an internal format, you can create a batch session to process updates (Figure 19).
Figure 19 Create Batch Input Session
Step 14: Run Batch Input Session
You can execute the BDC session by Run Batch input session. Executing a batch input session is a standard SM35 transaction for managing BDC sessions. Once you have successfully executed the batch input session, the customer master records are updated in the system. You can confirm this by viewing the customer master records (XD03).
Note! Browsing thru these 14 steps, you may get a feeling that this is a very lengthy and time-consuming activity. However, for the purposes of demonstration, I have made it detailed. Although it looks lengthy, actually it takes hardly few hours from start-to-finish! After playing around with few simple LSMW scripts, you will find it so easy to change and create more complex ones.
Thanks,
Vinay
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Re the Customer data migration using LSMW very nice user guide.
But we faced a problem we need to add Street3 and street5 fields to the customer master record, i.e. to the ADRC table how could we migrate this data Do you know that foreign key ADRNR in KNA1 table is a primary key in ADRC table.
That number will be created by the system during KNA1 data save.
I appreciate you in advance,
Best,
Eddie
adi@opex-il.com
hi,
LSMW Steps for Data Migration
How to develop a lsmw for data migration for va01 or xk01 transaction?
You can create lsmw for data migration as follows (using session method):
Example for xk01 (create vendor)
initially there will be 20 steps but after processing 1 step it will reduced to 14 for session method.
1. TCode: LSMW.
2. Enter Project name, sub project name and 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 ur choice.
Save + back.
Enter recording name in lsmw screen.
Save + back
Now there will be 14 steps.
2. MAINTAIN SOURCE STRUCTURES.
Here you have to 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 come.
Select -> from data file
apply source fields
enter No. of fields
length of fields
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 tabulator
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
With regards
Rajesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi anilo you have linked CRM and R/3 systems and find that your CRM team must spend time manually updating customer records in R/3? For example, sales, marketing, and customer service analysts may have to mass update customer master records to reflect an organizational restructuring. Instead of making such changes manually, SAP offers Legacy System Migration Workbench (LSMW), a standard automated tool that makes mass data changes. The name incorrectly suggests that you use this tool for legacy data conversion only. In fact, you can use LSMW for day-to-day activities.
LSMWs wizard-like setup is easy to follow, similar to step-by-step instructions. For typical conversion and migration tasks, you can use standard R/3 programs with built-in conversion routines. Also, you can create your own transaction recordings for custom transactions or if you want to update only specific fields in standard SAP transactions. I will describe how to update customer master records quickly using LSMW. Note that though the example illustrates how to use LSMW for updating customer master records, you can use it for any data updates.
Say you want to change a customers sales office. Normally you would use transaction XD02 to manually update a customers sales view. You would provide the customer key (customer number, sales org, distribution channel, division) and update relevant fields on the sales view screen. Its fine to manually change customer records if you just have a few of them, but what if you want to update a few hundred records? In this case you can use LSMW, a better tool for data updates. LSMW offers flexible data formatting options from simple mapping rules to more complex requirements. You dont need to know ABAP to perform the conversion tasks a wizard-like feature makes it easy for anyone to use LSMW without technical prerequisites.
reward if helps
Regards
AK
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
96 | |
10 | |
9 | |
6 | |
3 | |
3 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.