Is this a one-time data fix, or will this process need to be run regularly?
I assume, too, that data values such as 130B, 130C, etc... may also be required?
I have to say, it is rarely a good idea to create ID values this way (though I understand that sometimes the business model requires it), but it is also rare that a good application design requires stored data to be ordered in a specific manner, either logically or physically. Records should be independent from one-another.
I suspect that this is a case of either:
1) Poor application design.
2) A data-import issue.
3) A homework problem for a class.
If it's not practically useful, then it's practically useless.
It is a problem of moving data from a legacy system (a whole lot of rubbish) into a new ERP. Business logics and data models are way different. Under this circumstances, a non-key field in the old system is now a key in the new model, from here the need of updating the values with a trailer character (or what have you).
Blindman, the values you mentioned are allowed, altough the repetition is often limited to two rows only.
Pat, there are no possible sorting orders because the other fields may vary 'randomly'.