Design approaches for handling single ALC values related to multiple vendors/vendor sites?

Hi,

We're curious what sort of solution agencies are looking at/employing for handling the scenarios of a single ALC value being applicable to multiple existing eBS vendor/vendor site records.

Background:

The base solution from Oracle for deriving the vendor/vendor site for a GT&C and Order assumes that each Agency Location Code (ALC) relates to a distinct eBS vendor site record. There are a few situations I'm familiar with (& likely plenty more that I'm not aware of), where a single ALC may map to numerous different entities that could exist as different vendors/vendor sites. 

For example, within Dept of Energy (DOE), the single ALC 89000001 is used by a large number of different DOE laboratories and various entities. The different entities may exist as different vendors/vendor sites within an eBS setup, yet they are all related to ALC 89000001. We have this data condition in our Federal Financials environment, so the base "one ALC = one Vendor Site" solution doesn't hold up for us in these types of cases.