LSMW - Batch Input Recording Method

(1)

NTT DATA

Legacy System Migration Workbench

Batch Input Recording

Mohammed Mubeen Ahmed 1/28/2014

(2)

Legacy System Migration Workbench

1

LSMW by Mohammed Mubeen Ahmed SAP CRM

LSMW: Legacy System Migration Workbench

As we all know LSMW is very helpful and easy when it comes to upload heavy data into SAP system in less time. It’s a tool used to upload master data in SAP

Let’s create a LSMW to upload condition type PR00, to upload new price for large set of materials.

Process:

Go to transaction LSMW and to will take you to below screen –

SAP has provided user to segregate there LSMW’s in a proper manner by divided it into 3 parts “Projects, sub projects and objects”.

Click on the highlighted button to create a new LSMW a pop up will appear as shown below asking for project name and description -

(3)

Legacy System Migration Workbench

2

LSMW by Mohammed Mubeen Ahmed SAP CRM Fill in the appropriate project name and description of your LSMW and press ok. Again a pop up appears asking for more details as shown below-

Sub project: It is 2nd node in the hierarchy; in simple terms you can say it’s a sub category

Fill in the appropriate Sub project name and description of your LSMW and press ok. Pop up demands for more details as shown below-

Object: Object can be list of entities falls under the sub category. Fill in appropriate object name and description and press ok.

(4)

Legacy System Migration Workbench

3

Example:

After you fill in all details press the highlighted execute button or press F8, this will take you to below screen.

Object

Sub Project

Project

Eatables

Fruits

Fruit salad

Fruit juice

Vegetables

Vegetable

soup

(5)

Legacy System Migration Workbench

4

LSMW by Mohammed Mubeen Ahmed SAP CRM This is the overview screen of LSMW.

Step1: Maintain object attribute

Here in this step we decide which process we used to input out legacy data into SAP system, SAP has provided some of the process as shown below-

 Standard Batch/Direct Input

 Batch input recording

 Business object method (BAPI)

(6)

Legacy System Migration Workbench

5

LSMW by Mohammed Mubeen Ahmed SAP CRM We will be using the Batch input recording method which I feel is bit simple when compare to other process.

Click on the highlighted radio button of batch input record and then click on overview button which is highlighted as well in the right side of above screen; it will take you to below screen-

(7)

Legacy System Migration Workbench

6

LSMW by Mohammed Mubeen Ahmed SAP CRM Now click on create button highlighted in above screen to create a new recording, system will ask you name the recording and describe it as shown below-

As soon as you name the recording and describe it system will ask for which transaction you want to do recording.

Recording: As the name goes recording means recording step by step process how you key data in that particular transaction, system uses this recorded example as skeleton to feed those thousands of entries which you hold in sheet.

(8)

Legacy System Migration Workbench

7

LSMW by Mohammed Mubeen Ahmed SAP CRM System takes you to VK11 (condition record maintenance screen) fill in data and complete one record as shown below-

(9)

Legacy System Migration Workbench

8

LSMW by Mohammed Mubeen Ahmed SAP CRM Click on save after you completes the transaction then system will take you to below screen

(10)

Legacy System Migration Workbench

9

LSMW by Mohammed Mubeen Ahmed SAP CRM Click on the highlighted entry of the recording a pop up will appear as shown

(11)

Legacy System Migration Workbench

10

LSMW by Mohammed Mubeen Ahmed SAP CRM Name the field as KSCHL in name column and then describe it as condition type in next name field, and keep PR00 as default value if all of the records you want to feed in is on PR00 only otherwise make it blank.

In this example I have all records for PR00 only so I will keep it as default only, as shown below-

In the same way click on second field and repeat the process again as shown below

As I don’t want sales organization to be default I removed it from default value which was recorded by system.

Repeat the same process for rest fields in the list and it always better to keep name of field as same highlighted in above screen (standard) this will help in future step 5 when we try to map these fields. This is how screen looks after you complete the process

(12)

Legacy System Migration Workbench

11

LSMW by Mohammed Mubeen Ahmed SAP CRM 1. Name of the fields

2. Default values

3. Options like default all, default, reset, delete field, add field repeat recording for quick access.

This complete the first step and as soon as you save changes system takes you to below screen for next step, cursor goes to next step automatically as shown below

(13)

Legacy System Migration Workbench

12

Step 2: Maintain source structure

Source structure is all about structure of you data file, it’s like a group name, system ask you to key the name and description of structure, give some sensible name as shown below-

(14)

Legacy System Migration Workbench

13

Step 3: Maintain source field

Source fields: It’s a set of field’s names which we have in our source data file and details about them

Click on execute or press F8 system will take you to below screen.

Click on highlighted button of table content and system will take you to below screen where you can feed in all source fields.

(15)

Legacy System Migration Workbench

14

LSMW by Mohammed Mubeen Ahmed SAP CRM Fill all the fields in this table with their technical name, data type, field length and description as shown above.

And it should be in the same order as you have positioned in the source data file with correct process as per transaction.

(16)

Legacy System Migration Workbench

15

LSMW by Mohammed Mubeen Ahmed SAP CRM It’s always betted to keep source data file in text format with tab delimited as shown above.

The above screen shows that the recently created source structure contains the recently create source fields, both highlighted source structure and fields.

Step 4: maintain structure relation

This is the step where you relate your source structure which contains all source fields to the recording which we created in first step, it’s just an assignment.

System automatically relates the recent created source structure with the recording which we have created in first step,

(17)

Legacy System Migration Workbench

16

LSMW by Mohammed Mubeen Ahmed SAP CRM Just click on change button and then save the transaction.

Step 5: Maintain field mapping and conversion rule Field mapping:

This is the critical and most important step in LSMW; it is used to map the fields of recording (Step1) with the source structure fields (step 4&5).

(18)

Legacy System Migration Workbench

17

LSMW by Mohammed Mubeen Ahmed SAP CRM System shows all the fields which we have recorded in first step as shown above.

(19)

Legacy System Migration Workbench

18

LSMW by Mohammed Mubeen Ahmed SAP CRM Then click on auto field mapping which hides under extras tab in menu bar to automatically map the recording field with source structure fields. The below pop up appears-

Just make sure highlighted radio button is opted then system will map the same field name from recording with same field name in source structure field name.

(20)

Legacy System Migration Workbench

19

LSMW by Mohammed Mubeen Ahmed SAP CRM You can see that under target field, name of field is KSCHL from recording name REC8 (step 1) and under source filed, name is the field is also KSCHL of source structure PR00_SOURCE_STRUCTURE (step 4)

(21)

Legacy System Migration Workbench

20

LSMW by Mohammed Mubeen Ahmed SAP CRM Click on the accept proposal and continue doing same for rest all fields.

When it comes to dates and values system smartly ask for the format of date as shown below

(22)

Legacy System Migration Workbench

21

LSMW by Mohammed Mubeen Ahmed SAP CRM This is how screen looks after mapping gets completed.

Step 6: fixed values, translation and user define routine.

This is used to give fix value to some filed after mapping and to validate the date by using user define routine. We will skip this step as this is optional and of no use for our LSMW.

(23)

Legacy System Migration Workbench

22

Step 7: specify file

Specify file: It is the step where we show and specify where we store our source data file in our directory.

Place the cursor “on the PC” first line and click on create button a pop will appear asking for directory path

(24)

Legacy System Migration Workbench

23

LSMW by Mohammed Mubeen Ahmed SAP CRM 1. File path and file name.

2. Type of delimiter source data file contains (its tabulator in our case). 3. Whether file contain headings (field name) at the starting of file.

(25)

Legacy System Migration Workbench

24

Step 8: Assign file

(26)

Legacy System Migration Workbench

25

Step 9: Read data

This will read all the records from the source data file, system shows that what will be the date and value format as shown below-

(27)

Legacy System Migration Workbench

26

Step 10: Display read data

(28)

Legacy System Migration Workbench

27

LSMW by Mohammed Mubeen Ahmed SAP CRM Double click on one record and system shows the record and its value traced while reading the source data file.

(29)

Legacy System Migration Workbench

28

LSMW by Mohammed Mubeen Ahmed SAP CRM 1. File path where system stores the traced data from source date file, file path ends with read. 2. Source structure which has been assigned to source data file.

3. Field name of source fields of source structure.

4. Value extracted again field names from the source data file.

Step 11: Convert data

System converts the list of records traced from source data file into its own transactional format of VK11 in this step.

(30)

Legacy System Migration Workbench

29

LSMW by Mohammed Mubeen Ahmed SAP CRM Click on the execution button or press F8 to proceed further

(31)

Legacy System Migration Workbench

30

LSMW by Mohammed Mubeen Ahmed SAP CRM System shows number of records which have been converted.

(32)

Legacy System Migration Workbench

31

LSMW by Mohammed Mubeen Ahmed SAP CRM This is an optional step which shows the converted records from the source data file.

(33)

Legacy System Migration Workbench

32

LSMW by Mohammed Mubeen Ahmed SAP CRM 1. Path where system stores the converted data and file path ends with CONV.

2. Recording name which has been used as skeleton to convert the data from source data file. 3. Field names based on recording.

(34)

Legacy System Migration Workbench

33

Step 13: Create batch input session

In this step we will create batch session which can be run in next step to run the heavy source data file.

(35)

Legacy System Migration Workbench

34

LSMW by Mohammed Mubeen Ahmed SAP CRM An information pop up appears saying these many records has been created in this batch folder.

Step 13: Run batch input session

(36)

Legacy System Migration Workbench

35

LSMW by Mohammed Mubeen Ahmed SAP CRM Select the latest session based on session name and user id and click on highlighted process button

A pop up appears as shown below-

Process/foreground: It runs the file in foreground, this is recommended when you run sample file to see how system creates entry through batch input recording.

Background: System runs the file in background, this is recommended when you run huge file to avoid manual work of pressing entry every single time.

(37)

Legacy System Migration Workbench

36

Extended log: By enabling this system give detail analysis or log about both successful and unsuccessful transactions.

This is how analysis screen looks like-

Go to VK13 (display mode of condition record) transaction and check random entries to confirm created entries are accurate and correct.

(38)

Legacy System Migration Workbench

37

LSMW by Mohammed Mubeen Ahmed SAP CRM Thank you for taking out time and going through this document, you can use it as reference and create LSMW as per your business need. If you have any doubts and need my assistance you can reach me out, I have pasted my details below.

You can provide your Valuable feedback, suggestions & corrections, thank you. My details:

Name Mohammed Mubeen Ahmed

Designation Consultant

Practice CRM

Employee ID 18313

E-mail [email protected]