Step by step instruction for Using LSMW Recoding method for Material Master

[former_member1005887]

Guys,

Can some one explain step by step procedure for uploading the materials master data to R/3 by using LSMW Recoding method. By the time you reply I will go through the rule of uploading the data..

Thanks guys,

Dhanu.

[Former Member · Accepted solution]

http://help.sap.com/saphelp_erp2004/helpdata/en/7f/b6f45805b111d2b41c006094b944c8/content.htm

http://www.scmexpertonline.com/downloads/SCM_LSMW_StepsOnWeb.doc

http://www.mydatabus.com/visitor.php?pt=downloadFile&tc=6289701541332&cl=53&cn=000003&uid=6659

http://www.erpgenie.com/sap/saptech/lsmw.htm

regards,

Chintan

[former_member1005887 · Accepted solution]

Hi Guys,

Thanks for your valuable reply. Like the document in below link for Customer moster I am looking for Material master. Please guide me.

http://www.scmexpertonline.com/downloads/SCM_LSMW_StepsOnWeb.doc

Thanks

Dhanu

[JL23 · Accepted solution]

The steps would be equal for any recording.

However, the material master is that complex, that a recording is not the best option for loading, as a recording is a static program version.

As a material master may have different views to maintain base on the material type, you would have to do at least one recording per material type.

And again, as there are fields that are dynamically presented, e.g. based on the lot size procedure in MRP views, you would again need a seperate recording if that would be the case for your materials.

Better use the standard given mthods, like direct input or IDOC for load materials and use recordings only in case SAP has not given any standard load method (as it is e.g. for price changes with MR21).

[BijayKumarBarik]

Hi,

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

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

The Steps for LSME are:

Example: Customer Master upload:

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

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.

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 u2018Table Maintenanceu2019 icon to enter Fieldname, Type and Length for each field

Step 4: Maintain Structure Relations

Execute a step to u2018Maintain Structure Relationsu2019. 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 u2018Sales viewu2019 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 u2018Xu2019.

If your source file already has the field value, you choose rule u2018Source Fieldu2019.

Keep cursor on field u2018KUNNRu2019 and click on u2018Assign Source fieldu2019 icon to choose source field CUSTOMER from structure XD02S

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.

Step 8: Assign files

Execute step u2018Assign Filesu2019 and the system automatically defaults the filename to the source structure.

Step 9: Read data

In this step, LSMW reads the data from the source file (from your PCu2019s local drive). You have the option to read only selected rows and convert data values to Internal format.

Step 10: Display read data

This step is optional. If required, you can review the field contents for the rows of data read.

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

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.

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

Follow the link for material master

http://www.sap123.com/showthread.php?t=98

Regards,

Biju K

[former_member192897]

Hi Dhana,

http://www.sap123.com/showthread.php?t=98

reg,

Ashok