I recommend biting the bullet and duplicating the objects. It will be additional universe development, but the benefits are worthwhile. Here's why:
- The universe will be user-friendly. You'll have classes for "Case Info", "Parent Member", "Child Member", and "Generic Member". Your users can pick objects from the first three classes to easily create your scenario 1 report. And the scenario 2 report can be built from the "Generic Member" class.
- Creating the scenario 1 report without aliasing the DEMOGRAPHICS table and duplicating the objects would require that the logic be built into the report rather than the universe. So you would need to have report variables like
=Max([SSN]) Where ([Role]="Parent"])
. It gets the job done, but your users would need to know this syntax and create the variables in each report.
There are tools available on the BOB forum (http://www.forumtopics.com/busobj) that can reduce the work required for batch universe changes such as this.