Step-by-Step Guide For Using LSMW To Update Customer Master Records
Step-by-Step Guide For Using LSMW To Update Customer Master Records
Step-by-Step Guide For Using LSMW To Update Customer Master Records
Master Records
Business Case:
Note! The screenprints in this article are from IDES Release 4.6. They may differ slightly
in other versions.
Demo Example 1
LSMW to Update Customer Master Records with Transaction Recording
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.
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.
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.
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
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.)
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.
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.
Note that your input file will have four fields as key fields and you need to update three
fields in the system.
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.
Once all the fields are mapped, you should have an overview screen as shown in Figure
12.
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.
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.
Demo Example 2
LSMW to Update Customer Master Records with Standard Object
As an alternative to using ‘Transaction Recording’, you could also use a standard SAP
object to update Customer Master Records. Business Object ‘0050’ is already pre-defined
in the system with standard Batch Input Interface Program ‘RFBIDE00’.
Note! For the Demo example 2, I will list only those steps that are different from the first
demo example.
Even though you don’t want to update any fields in these structures, you need to create a
relationship with source structures. In all, you need to create relationship for four target
structures.
Create relationship between source structures XD02S with these target structures with
icon ‘Create Relationship’ .
Keep Cursor on these four target structures and click on icon ‘Create Relation’ and
structure relations are maintained as shown in Figure 22.
-- Keep your cursor on ‘TCODE’ field and click on ‘Insert Rule’ icon
Choose radio button ‘Constant’ (Figure 23) to enter value ‘XD02’ transaction code.
-- Keep your cursor on field ‘KUNNR’ and click on ‘Assign source field’ icon
Choose source field ‘Customer’ from source structure ‘XD02S’. (See Figure 24.)
-- Similarly, choose source fields for Sales Organization, Distribution Channel, and
Division. (See Figure 25.)
-- Scroll down to structure BKNVV fields and assign source fields to three fields Sales
Office, Sales Group, and Customer Group (Figure 26).
Note that if you had only one record in source file, the converted file has four records.
Earlier, creating this input file, so that the standard interface program can read it, was a
big nightmare, the primary reason being that it could have multiple record layouts. Even
for a simple conversion with one input record, you would have to create this complex file
with many record layouts. The advantage of LSMW is that it prepares these multi-layout
files automatically.
Summary
Once BDC session is processed successfully, SAP updates the customer master records
with relevant changes. Review these specific customers (transaction code XD03) and
confirm that the changes are correctly reflected in the master records.