The design method consists of two major phases.
During the first phase, you create the underlying database structure of your universe. This structure includes the tables and columns of a database and the joins by which they are linked. You may need to resolve loops which occur in the joins using aliases or contexts. You can conclude this phase by testing the integrity of the overall structure.
During the second phase, you can proceed to enhance the components of your universe. You can also prepare certain objects for multidimensional analysis. As with the first phase, you should test the integrity of your universe structure. You may also wish to perform tests on the universes you create from the BusinessObjects User module. Finally, you can distribute your universes to users by exporting them to the repository or via your file system.
For a universe based on a simple relational schema, Designer provides Quick Design, a wizard for creating a basic yet complete universe. You can use the resulting universe immediately, or you can modify the objects and create complex new ones. In this way, you can gradually refine the quality and structure of your universe
At-least one object in the class must be present in the other class so that they can have a join n afcourse the datatypes.
Measure objects are the objects which have facts i.e all $ amounts
a dimension object cannot be calculated with another dim object
in order to have a seperate identity for $ amounts we define as measure objects
just create an object for ex:revenue then right clicck on the object or double click on the object n then change the property of that object to measure its that simple
If your database consist all dates something like 01/02/2000 or 01-Feb-2000, you will need to break the date field into year, qtr,month & if required date.
to do this, create a class named TIME, under that create new object, in it's select box use oracle's date functions to get required information.
For E.g. : to_char(sales_date, 'YYYY') for getting only year from the date.
similarly, for quarter you can use to_char(sales_date, 'Q')
& for month to_char(sales_date, 'MM') for month number, instead of 'MM' if you use 'MON' it will return you abrevations like Jan for January & so on. for full name of month use 'MONTH'
Business Objects deals with databases, for every universe you need to specify a database connection. flat files dont have the database format so you'll need to convert them into some database. to do that, you will need to write a procedure which will read data from flat files & relate it according to surrogate keys, then using that procedure populate the database & then use that database for the source of the universe.
using flat files ONLY , you can not create universe. because there is nothing as database connection available for flat file.
We have securities in business objects
3.supervisor level securities, ie User name/ password
To create context :
goto Tools --> Detect Loops, BO will detect loops if there are any & will suggest the context candidate (something like Sales, Costs that is related to that specific subject area)
Select the suggested candidate & click on create Context. It will map all those joins that are required for say Sales subject area & put it in Sales Context. same with Costs.
So it will avoid the confilcts in path by using Contexts.
This Auto Detection works in most of the times....but not always.
Creating a filter in designer is different from creatind a filter in business object
if u create a filter in designer it can acessible to all the reports ur r using i'e,it can used for further applications where as creatin a filter vin business object is dynamic(run time) it will applicable to only tht particular report
We can set the predefined condition in the universe level. In the task bar of the designer there is an icon for filtering. Just click on the icon. It asks for the condition name. After giving the name for the condition type the sql for that condition. finally submit the sql.
Guidelines are provided in the Universe guide:
Here is the Summary:
1) Modify the array fetch size in SBO file
2) Assign table weights and change the default order of the tables in a query by changing parameter in PRM file
3) Use shorcut joins to avoid unnecessary tables that may come in Query
4) Use aggregated tables