Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from Unny_boy on Nov 27 at 1:33 PM No, it's standard SAP. Do NOT use ABAP!
Go to customizing OMNN
There the conversion of storage unit numbers will be shown.
In you case I think the length of su numbers = 20
If you say your client ONLY has 8 digits and you are 100% sure (check LQUA) then you change 20 to 8. The lead-in zero's in de SU will be gone. Try this first in a test environment.
I think it's unwise to have only 8 digits, very strange, you will run out of SU's. Normally it's 11 digits.
Thinking about that it may be a problem in a few years doing what I say.
Better: change it to 8 (first checking LQUA if there are no SU's longer then 8. Then CHANGE your SU-label and make it so that it prints always 20 digits (follow up zero's + SU number). Your will have to change in a year the setup to 11 I would think.
| | | ---------------Original Message---------------
From: tags123
Sent: Thursday, February 07, 2013 3:03 PM
Subject: How to Pad Leading Zeroes for Storage Unit I LM51 TF Transaction?
For my client, storage unit bar code is 8 characters long (for example: 20001214). While using LM51 when scanned it says SU not found. I believe system stores as 00000000000020001214, where as barcode is read as 20001214. So there is a mismatch and it fails. Is there any workaround/configuration in RF transaction to pad leading zeroes to scanned SU (barcode)?
Any help please? |
| Reply to this email to post your response. __.____._ |   _.____.__ |
