LSMW

[Former Member]

What is the role of SD Consultant in LSMW AND SCCOT

[Former Member · Accepted solution]

Dear Habib,

SCATT is used to upload mass data.

For Ex your client has said to change Credit Representative group nearly 1000.

By using SCATT you can upload all the Credit Representative group within a few minutes.

In LSMW we are having total 14 steps:

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

The main screen of LSMW provides wizard-like step-by-step tasks, as shown in Figure below. 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.

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.

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,

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.

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 below.

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

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

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 below.) Since, there is only one Source and Target Structure, the relationship is defaulted automatically.

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

Similarly, assign 'Source Field' rules to the remaining fields.

Once all the fields are mapped, you should have an overview screen as

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 [Community:Tab] delimited with the first row as field names. It is present on my PC (local drive) as C:\XD02.txt.

with Regards

Amjad

[Former Member · Accepted solution]

hi

plz go through it for LSMW.

The whole LSMW process is described for transferring customer legacy data as follows:

Enter T-code LSMW

Enter project name (LSMW-DEMO)

Click on create entry button (shift+F1)

Enter the description

Press enter button

Enter sub project name & description

Press enter button

Enter object & object name

Press enter button

Click on continue (F8) button

 System displays 21 steps

(Focus on the 1st step)

Step (1): - Maintain object attributes

Click on object attributes

Click on execute button (ctrl +F8)

Click on display change (ctrl+F1)

Click on batch INPUT recording (radio button)

Click on go to and select recordings overview

 Click on u201Ccreate recordingu201Dbutton. (Ctrl+F1)

Enter name (RECCUST) of recording & description (RECORDING FOR CUSTOMER)

Enter owner (SAPUSER)

Press enter button

Enter the transaction code (VDOL)& press enter button

Create CMR using the general process

System displays the newly created customer number

Click on default ALL

 System displays field names for which date is maintained

Note these fields names in a text tile

Click on save button

Click on back button

 Click on back button

Enter the recording name in recoding field ex RECCUST

Press enter button

Click on save button

Click on back button

Observation: -

1) The cursor position is automatically changed to second step. After every step completion the cursor position is changed to succeeding step.

2) Steps are reduced to 14

Step (2) :- Maintain source structures

Click on execute button

Click on display change button

Click on create a structure button

Enter source structure name 2 description,& 2 press enter button

Click on save button

Click on back button

Step(3) :- Maintain source fields

Click on execute button

Click on display change button

(note)try to maintain the source field names same as target fields names

Click on the source structure

 Click on copy fields button

Select upload (text separated with tabs) & press enter button

Click on save button

Click on back button

Step (4) :- Maintain structure relations

Click on execute button

Click on display change button

Observations :-source structure & target structure relations is already maintained

Click on save button

Click on back button

Step (5) :- Maintain field mapping 2 convention rules

Click on execute button

Click on display change button

Select the first field (under fields)

Click on u201Cextrasu201D & select u201Cauto field mappingu201D

Click on ok button(continue button)

Click on accept proposal

Continue clicking on accept proposal till all the fields are mapped

System displays auto field mapping complete

Press enter button

Click on save button

Click on back button

Step(6) :- Maintain fixed values transudation user defined routines

This step is optional

We may use this when creation changes are to be made like dollar to euro etc.

Step(7) :- Specify files

Select specify files

 Click on enecute button

Click on display change button

Click on legacy data

Click on u201CAdd entryu201D button

Specify the file name (customer records file path)

Specify the name (CMR RECORDS)

Click on tabulator

Press enter button

Click on save button

Click on back button

Step(8) :-Assign files

Click on execute button

Click on display change button

Click on save button

Click on back button

Step(9):-import data

Click on execute button

Click on execute button again

Observations:-transactions read & transactions written are same & and equal to the no. of records maintained in text file.

Click on back button

Again click on back button

Step(10) :-Display imported data.

Click on execute button

Press enter button.(imported data is displayed)

Click on back button

Step(11) :-Convert data

Click on execute button

Again click on execute button

Observations :- transactions red & transactions written are same and are equal to records in the text file

Click on back button

Again click on back button

Step(12) :-Display converted data

Click on execute button

Press enter button

Click on back button

Step(13) :-Create batch input session

Click on create button

Again click on execute button

System displays a message saying that a u201Cbatch input folderu201D is created with specified number of transactions

Press enter button

 Click on back button

Step(14) :- Run batch input session

Click on execute button

Select the required u201Csession nameu201D and click on u201Cprocess buttonu201D

Select u201Cforeground processu201D or u201Cbackground processu201Detc

Click on u201Cprocess buttonu201D

Regards

Navin patidar

Edited by: Navin Patidar on Sep 26, 2008 12:41 PM

[Former Member]

Hi,

LSMW:

The LSM Workbench covers the following steps:

(1) Read the legacy data from one or several files (e.g. spreadsheet tables, sequential files).

(2) Convert the data from source format to target format.

(3) Import the data using standard interfaces (Batch Input, Direct Input, BAPI, IDoc).

There are following data, might get uploaded via LSMW, as far as SD is concerned:

1. Customer Master uploads:

2. Material Master uploads

3. Price uploads

4. Open Orders (say 4.6c to ECC 6.0)

SCAT:

SCAT is similar to LSMW/BDC to upload/updated data in SAP from legacy system.

The differences between SCAT and LSMW :-

LSMW and SCAT has different functionalities and different advantages, but common thing is they are used for data upload.

SCAT is mainly used as a testing tool for follow-on transactions i.e. Purchase Requisition, Purchase order, Goods Receipt etc.

Whereas LSMW is used for Master data (Materials, Customer, Vendor, BOM, Info record etc) and some of the transactions data (Purchase order, purchase requisition)

There are many standard objects are available in LSMW so most of the consultants use LSMW, but again depends on the requirement.

Best Regards,

Amit.

[Former Member]

SCAT is used to mass-upload data into the system. E.g. mass upload of prices / credit master data etc. And an SD consultant normally does it since he/she understands what is being uploaded and how to verify that it has been uploaded correctly.

[Former Member]

Hai Anil

Is SCAT is used for mass-upload data or it is used for testing purpose

if it is not using for testing purpose, can U help me to know how to do this?

[Former Member]

Hi

Inur project u have to fetch the data from the legacy system of Customer for that purpose being a sd consultant, u hav to use this tools .

u should prefect on this process.

as far as concerned to SCAT

this is basically use fro testing pirpose means u hav to sent the data from ur one client to another by using this tools.

thanks

mk

[Former Member]

as sd consulatant we have to upload customer master material master pricing master for that we are using this tool

[Former Member]

Thanks Mahesh for Ur Guideline

Can U tell me about the steps that we want to do in LSMW

OR

What all are the things v want to do in LSMW and SCAT