Thanks Andrew.
I looked at the prj_projects_alloc_act_etc_read, filtering on 6 projects and one resource in my XOG filter. It retrieved 5 of the 6 projects I requested, but it still brought back allocation data for all of the resources in each project, instead of just the resource I filtered on.
So I guess if we were going to put this into practice, we would need to
1) Probably retrive the list of projects the resource is allocated to via DB call
2) Invoke a XOG read using the result set on 1)
3) Traverse the file created in 2 and delete all resource data except the resource we are filtering on
4) Update the allocation Data for the resource remaining
5) XOG write the data back.
Not a pretty solution, but if there is a compelling business case to terminate going-forward allocations, and we want to automate, we'll find a way to make it work.
Thanks again for the input.