2007 Feb 12 3:37 PM
How to use the Translation option in Rules under Direct Input Method for LSMW
2007 Feb 12 3:54 PM
1. First you should define a translation table: it is in LSMW - "Maintain Fixed Values, Translations, User-Defined Routines". Create a new table there, after that define in it source and output lengths and types - Save - and go to "1:1 Translation Value". For example if you want to translate document types and the value from the source system is "01" and in SAP it is "AB", then you should put these values in Old Value and New Value. Dont forget to check the OK checkbox on the same row! And Save at the end. Now we have a translation for document type "01" to "AB".
2. Go to LSMW - "Maintain Field Mapping and Conversion Rules". Choose the field where you want to make the translation, assign a source field to it (in our example - the field for document type). After that choose Rule -> Translation -> Own Selection and with the input help F4 choose the table created in step 1.
3. The result - we have a translation rule
Hope it is what you asked!
2007 Feb 12 3:54 PM
1. First you should define a translation table: it is in LSMW - "Maintain Fixed Values, Translations, User-Defined Routines". Create a new table there, after that define in it source and output lengths and types - Save - and go to "1:1 Translation Value". For example if you want to translate document types and the value from the source system is "01" and in SAP it is "AB", then you should put these values in Old Value and New Value. Dont forget to check the OK checkbox on the same row! And Save at the end. Now we have a translation for document type "01" to "AB".
2. Go to LSMW - "Maintain Field Mapping and Conversion Rules". Choose the field where you want to make the translation, assign a source field to it (in our example - the field for document type). After that choose Rule -> Translation -> Own Selection and with the input help F4 choose the table created in step 1.
3. The result - we have a translation rule
Hope it is what you asked!
2007 Feb 12 4:04 PM
could u elaborate as to how I could create a table in the Maintain Fixed values,...option.
2007 Feb 12 4:14 PM
1. You are in LSMW -> "Maintain Fixed Values, Translations, User-Defined Routines"
2. Position your mouse cursor to "Translations", go to Create Entry (Ctrl+F1)
3. On the first row give a unique name to the translation table, on the second - some description. Enter. Now you should see the table under "Translations"
3. Double click the table, it opens in display mode. Choose "Display<->Change", enter the length, type of souce field; and length, type of target field. Save
4.Go to tab "1:1 translation" enter old and new values, and check the OK (if not it will not be active). Save
5. Our simple translation table is ready.
2007 Feb 13 5:58 AM
I did just like u told me .... I keep getting the following error.
1:1 translation 'MEINS': No translation value exists for value 'ea'.
1:1 translation 'MEINS': No translation value exists for value 'kg'.
2007 Feb 13 6:56 AM
I think translations are case-sensitive, so please check if this is the case.
Also in the translation "MEINS" be sure that you have checked the "OK".
2007 Feb 13 7:09 AM
2007 Feb 13 7:20 AM
2007 Feb 13 7:26 AM
1) I had not assigned a source field before assigning a translation rule.
2) The case sensitivity issue. That was when I realized the true use of the checkbox Lower case letters.
2007 Feb 13 7:34 AM
What is checkbox Lower case letters?
The checkbox "OK" shows if the record on the row is valid or no
2007 Feb 13 6:38 AM
this is the steps of LSMW
LSMW  Transaction Code
Enter Project Name => Module Name (Material Management)
Enter Subproject => Transaction Group (Master Data)
Enter Object Name => Transaction (Vendor Master)
Press Create / Change
Enter Projects Descriptions
Continue (F8)
Maintain Object Attributes
Execute (Ctrl+F8)
Press Display <> Changes button
Select Batch Input Recording (Radio Button)
Press Recordings Overview button (SHDB for Transaction Recording)
Press Create Recording
Enter Recording Name & Description
Enter Currently Using Transaction Code
Enter Needed Fields (Ex. Account Group for Vender Master)
Enter Values for All Uploading Field
Save
Press Default All Button
Maintain Source Structures
Press Display <> Changes button
Enter Source Structure Name & Description
Save
Maintain Source Fields
Press Display <> Changes button
Save
Enter Field Names & Length
Maintain Structure Relations
Press Display <> Changes button
Save
Maintain Field Mapping and Conversion Rules
Select or Auto set Fields to Real Fields
Save
Maintain Fixed Values, Translations, User-Defined Routines
Optional
Specify Files
Select Uploading File
Save
Assign Files
Press Display <> Changes button
Save
Read Data
Enter No of Transactions to View Data Summary
Display Read Data
Enter No of Transactions to View Data List
Convert Data
Optional
Display Converted Data
Optional
Create Batch Input Session
Run Batch Input Session
Rewads if helpful