Suppose you have a table containing persons. Now you want to subclass them into
Sales persons, Development Persons, Administrativ Persons, etc.
I first create a subclass “Sales” under the class person. Then I added a WHERE-statement for the PK-attribute (object) in the sales subclass. When I try this in BusinessObjects it works great, but only if I add the PK-attribute to the table. The subclass contains lots of attributes, and I don’t want to add the WHERE-statement to eacb one of them. How can I set up a global where-statement (filter or something) for a whole subclass?
If you only need the subclasses for reporting, you can derive variables (groups) from your data and use these variables to group (break) your information. If you need more information, let me know.
Suppose you have a table containing persons. Now you want to subclass
them
into Sales persons, Development Persons, Administrativ Persons, etc.
I first create a subclass “Sales” under the class person. Then I added a WHERE-statement for the PK-attribute (object) in the sales subclass. When
I
try this in BusinessObjects it works great, but only if I add the PK-attribute to the table. The subclass contains lots of attributes, and
I
don’t want to add the WHERE-statement to eacb one of them. How can I set
up
a global where-statement (filter or something) for a whole subclass?
Oh, some thoughts for you … each point is a different design direction … reporting requirements should be taken into consideration before deciding on direction.
(1) create the where clause once and use the BusinessObjects @where function (would still need to touch each object) (2) create alias against the table for each type of person. point the objects to the associated alias. create a self join on the alias (ie: create a join on the Sales person alias that says something like where sales_alias.attribute=PK. each time an oject using the sales person alias, these where clause will be invoked).
(3) create a predefined condition in the unierse for user to pull over when they want only the sales people.
I am assuming the pk-attribute object indicates the type of person. If this is true you could probably use a decode statement in the select statement for your object. If pk-attribute could be x, y or z then the statement might look something like:
This statement says if the persons field is x return ‘admin’ if y return sales and so on. If you have a lot of possible values that you wouldn’t want to type out in a decode, you could try deriving a variable within the user module.
Suppose you have a table containing persons. Now you want to subclass them
into
Sales persons, Development Persons, Administrativ Persons, etc.
I first create a subclass “Sales” under the class person. Then I added a
WHERE-statement for the PK-attribute (object) in the sales subclass. When I
try this in BusinessObjects it works great, but only if I add the PK-attribute to the table. The subclass contains lots of attributes, and I
don’t want to add the WHERE-statement to eacb one of them. How can I set up
a global where-statement (filter or something) for a whole subclass?
