I have little experience with ‘complex’ queries, intersections, unions, etc. I feel that BO can do what I am looking to do, just not sure of the how.
Simply, I am trying to have two tables on one report.
The query for the first table includes loan number, social security, and status(one of 3 specific statuses).
The query for the second table includes loan number, social security, and status(2 different statuses then the first query).
I would like the report to display data for when the same social security number returns in each query. So, when there is a match, I want to see the row from the first query and a row from the second query with common match of SSN between the two.
I think the answer to your question depends on how the different statuses are obtained - from your description it seems that they exist as objects in the universe? Is there a reason you need 2 tables? It would seem at first glance that all you need to do is to have a single query that returns a data set where status = 1 AND (status = 2 OR status = 3) which is built into the query conditions.
The only reason I can think of for using multiple queries is if the statuses are derived from different universes; then you have to fiddle around with linked queries, merged dimensions and detail objects.
Really, I am trying to flag circumstances when a given Social Security Number is associated to loan that meets the first set of parameters along with the second set of parameters. Seeing as that same SSN would be associated to two different loan numbers when the circumstance occurs that I am trying to flag, I can’t think of a way to do this with a single query…so just assumed some sort of combined query/matching could be done.
(BOB member since 2009-01-09)