Long lists in an organizational level

Question: My company is beginning to restrict authorization based on the Plant organization level. We have a very large number of plants and their codes are alphabetical and not in a form that can be used in a range. In some cases I am faced with the need to key in groups of 50-100 plant codes over a large number of authorization groups and further to have to update these lists periodically. Does anyone know a better way?

Answer:
1. The obvious, Do not control on plant.
2. Rename the plants
3. Accept that it is a cost of doing business and maintian the security.

Answer:
(1) not legal
(2) not economical
(3) While it is certainly a cost of doing business, my question concerns whether someone out there has discovered a more efficient means.

Answer:

(1) not legal
Out of interest where are you located? Often Company Code provides control over legal entities.

(2) not economical
See my answer to point 3


(3) While it is certainly a cost of doing business, my question concerns whether someone out there has discovered a more efficient means.

I had a similar problem at a client site where they wanted many individual cost centres to be assigned. In the end all permutations of cost centres required were assigned to groups in a custom table. When you created a role you left the c/c org field empty and ran a custom program (parameters are role and group). The program would look in the table, assign the correct vales and regen the role. If you added c/c's to the master table you could update and regenerate the roles affected.

It was a dirty solution and has caused a maintenance burden. The business decided to save costs by not adressing the fundamental problem. They are now at break even point after 2 years. In 2 years time they would have spent more maintaining the solution than fixing the initial problem This appears to be similar to your case.