'LO130318001LO130318002' is not like 'LO130318001-LO130318002', although 'LO130318001%LO130318002' is like 'LO130318001-LO130318002'.
What the ultimate solution should be here is difficult to say for sure, without perhaps a better understanding of the "rules" that would explain what the expected format/structure of the values to compared will be (e.g.: are they of a known fixed length, will the hyphen always be in the same place, etc.?).
"Please give us a simple answer, so that we don't have to think, because if we think, we might find answers that don't fit the way we want the world to be."
~ Terry Pratchett in Nation
That still doesn't really explain to me what the naming rules are for the value in the DB versus the value you want to compare to it. The most efficient search for the current DB schema and value would be to simply insert the hyphen into the string to be compared to the DB value. But this would assume that there is something standard/fixed about the value so that you could determine exactly where to stick the hyphen.
For example, if it's always before the "LO", then you could use a fairly simple regex: