What is this table used for? alm_user_stockroom

[clktester]

We've set the Location field for our users to be the building they are located in. 

This poses a problem when we are bringing on HAM because it appears Location of user needs to tie to location of warehouse for the sourcing task to work to find available items when requesting. 

I see this table - alm_user_stockroom - and see it's populated in a training PDI with users and local stockrooms, but it doesn't seem to do anything. 

Can someone tell me where this table is used / what purpose? The documentation just lists the table and states: 

Default Stockroom [alm_user_stockroom] - Stores the relationship between a user and their default stockroom.

Thanks for any light you can shed on this one! 

[Uncle Rob]

I haven't done any ALM stuff in a long time but I'd suspect that when delivering assets to a user there's a choice of where to deliver it from, and the default stock room would be the default option?

If I was going to look deeper I'd start looking for shout outs to that table in different code objects:  business rules, script includes, UI actions, etc.

[Thomas Wright1]

On the note about locations used for sourcing from local stock, in Vancouver a new HAM feature exists called "Service Locations" where you can have a list of locations added to a stockroom which get treated as "local" when sourcing a model.

I haven't figured out what alm_user_stockroom is used for though, there are a couple business rules related to this, but they just used for keeping the data on the table clean without hinting what it's used for OOTB. BRs are "Verify Not Field Agent" and "Validate Unique Users"

I'm trying to figure out the best way of marking an asset as being taken out of stock as part of being built before being put back into stock, field services has a way of assigning assets to personal stockrooms - but for HAM for some reason that's been restricted without field services installed.