Business Objects
Business Objects
1.Alias
A logical pointer to an alternate table name. The purpose of an alias is to resolve loops in the paths of joins.
2.Cardinality
Expresses the minimum and the maximum number of instances of an entity B that can be associated with an instance of an entity
A. The minimum and the maximum number of instances can be equal to 0,1, or N.
3.Cartesian product
A situation in which a query includes two or more tables that are not linked by a join. If executed, this type of query retrieves all
possible combinations between each table and may lead to inaccurate results.
4.Class
A logical grouping of objects and conditions within a universe. In general, the name of a class reflects a business concept that
conveys the category or type of objects.
5.Condition
A component that controls the type and the amount of data returned by a specific object in a query. A condition created in the
Designer module is referred to as a predefined condition.
6.Connection
Set of parameters that provides access to an RDBMS. These parameters include system information such as the data account,
user identification, and path to the database. Designer provides three types of connections: secured, shared, and personal.
7.Context
A method by which Designer can decide which path to choose when more than one path is possible from one table to another in
the universe.
8.Detail object
An object qualified as a detail provides descriptive data about a dimension object. A detail object cannot be used in drill down
analysis.
9.Dimension object
An object being tracked in multidimensional analysis; the subject of the analysis. Dimensions are organized into hierarchies.
10.Document domain
The area of the repository that stores documents, templates, scripts, and lists of values.
11.Drill
The action of navigating through levels of data. When you drill up, you obtain more summarized or general information. By drilling
down, you can reach more refined or detailed information.
12.Equi-join
A join based on the equality between the values in the column of one table and the values in the column of another. Because the
same column is present in both tables, the join synchronizes the two tables.
13.Enterprise mode
A work mode whereby a designer creates universes in an environment with a repository. The mode in which a universe is saved
determines whether other designers are able to access it. By default, a universe is saved in the mode in which the designer is
already working.
14.Hierarchy
A relational operation that causes two tables with a common column to be combined into a single table. Designer supports equi-
joins, theta joins, outer joins, and shortcut joins.
16.List of values
A list of values contains the data values associated with an object. These data values can originate from a corporate database, or a
flat file such as a text file or Excel file. In Designer you create a list of values by running a query from the Query Panel. You can
then view, edit, purge, refresh and even export this file. A list of values is stored as an .lov file in a subfolder of the UserDocs folder.
17.Loop
A situation that occurs when more than one path exists from one table to another in the universe.
18.Measure object
An object that is derived from an aggregate function. It conveys numeric information by which a dimension object can be
measured.
19.Object
A component that maps to data or a derivation of data in the database. For the purposes of multidimensional analysis, an object
can be qualified as a dimension, detail, or measure. Objects are grouped into classes.
20.Offline mode
The work mode in which the designer works with universes stored locally.
21.Online mode
The work mode appropriate for a networked environment in which the general supervisor has set up a repository.
22.Outer join
A join that links two tables, one of which has rows that do not match those in the common column of the other table.
23.Personal connection
A personal connection is used to access resources such as universes or documents. It can be used only by the user who created
it. Information about a personal connection is stored in both the PDAC.LSI and PDAC.SSI files; its definition is static and cannot be
modified.
24.Qualification
A property of an object that determines how it can be used in multidimensional analysis. An object can be qualified as one of three
types: a dimension, detail or measure.
25.Query
In Designer a query is a technique for creating or modifying a list of values associated with an object. From the Query Panel, a
designer builds a query from the classes, objects, and conditions of a universe.
In the BusinessObjects User module, a query is a type of data provider. An end user builds a query from a universe, and then runs
the query to generate a BusinessObjects report.
26.Quick Design
A wizard in the Designer module that provides guided instructions for creating a basic universe. It lets a designer name a universe,
set up a connection to a database, select strategies, create classes and objects, as well as generate joins with cardinalities.
27.Repository
A centralized set of relational data structures stored in a database. It enables BusinessObjects users to share resources in a
controlled and secured environment. The repository is made up of three domains: the security domain, the universe domain, and
the document domain.
28.Secured connection
2
A secured connection is used to access universes or documents that may be restricted or confidential.
It can be shared by several authorized users. Stored in the repository, the definition of a secured connection is updated
dynamically.
29.Shared connection
A shared connection is used to access common resources such as universes or documents. It can be used by several users.
Information about a shared connection is stored in a SDAC.LSI or SDAC.SSI file; its definition is updated dynamically.
30.Shortcut join
A join that links two tables by bypassing one or more other tables in the universe.
31.Strategy
Scripts that automatically extract structural information about tables, columns, joins, or cardinalities from a database. Designer
provides default strategies but a designer can also create strategies. These are referred to as external strategies.
32.Structure pane
The graphical component within the main Designer window that shows the schema of the universe. It reflects the underlying
database structure of the universe.
33.Subclass
A component within a class that groups objects. A subclass can itself contain other subclasses or objects.
34.Table Browser
The graphical component within the main Designer window that lets you create the classes and objects of the universe from the
tables and columns of a database.
35.Theta join
A join that links tables based on a relationship other than equality between two columns.
36.Universe
A mapping of the data structure found in databases: tables, columns, joins, etc. A universe, which is made up of classes, objects,
and conditions, can represent any specific application, system, or group of users.
37.Universe domain
The area of the repository that holds exported universes. The universe domain makes it possible to store, distribute, and
administrate universes. There may be multiple universe domains in a repository.
38.Universe pane
The graphical component within the main Designer window that displays a hierarchical view of the classes, objects, and conditions
in a universe.
Two radio buttons on the lower edge of the pane filter the display of the components. One button, the Classes/Objects filter,
provides a view of the classes and objects. The other button, Classes/Conditions, provides a view of the classes and conditions.
39.User object
An object created by the end user from the BusinessObjects User module. A user object can be inserted into a universe by the
designer.
40.Workgroup mode
A work mode whereby a designer creates universes in an environment without a repository. The mode in which a universe is saved
determines whether other designers are able to access it. By default, a universe is saved in the mode in which the designer is
already working.
41.What is Designer?
Designer is a BusinessObjects IS module used by universe designers to create and maintain universes. Universes are the
semantic layer that isolates end users from the technical issues of the database structure.
3
Universe designers can distribute universes to end users by moving them as files through the file system, or by exporting them to
the repository.
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.
The first step in creating a universe is to specify its parameters. These parameters include the definition of a universe, which is
comprised of:
You enter universe parameters from the Universe Parameters dialog box. This dialog box also lets you set up database options,
external strategies, graphic options, and print settings.
You create the initial classes and objects of your universe by selecting them from the tables and columns listed in the Table
Browser, and inserting them into the Structure pane.Depending on the database connection parameters, the browser presents you
with a list of database tables and columns.
Note
Before selecting tables, you should indicate the strategies you wish to use in creating your universe.
With the Check Integrity command, you can test the structure of your active universe. This means testing to determine whether its
components are accurate and up-to-date.
It detects any inconsistencies in the objects, joins, conditions, and cardinalities of your universe.
It detects whether there are any loops in the joins.
It determines whether changes were made to the database to which the universe is connected.
46.What is a universe?
A universe is a business-oriented mapping of the data structure found in databases: tables, columns, joins, etc. It can represent
any specific application, system, or group of users. For example, a universe can relate to a department in a company such as
marketing or accounting.In the BusinessObjects User module, universes enable end users to build queries from which they can
generate and perform analysis.Universes isolate end users from the complexities of the database structure as well as the
intricacies of SQL syntax.
Aggregate awareness is a feature that makes use of predefined aggregate tables to enhance the performance of SQL
transactions. It is used to improve the speed by which aggregates are calculated in the database.
To set up aggregate awareness in a universe, you define or more objects using the @Aggregate_Aware function. The syntax for
this function is as follows:
4
The arguments of this function are all the names of alternative aggregate tables. When you formulate the syntax, you should be
aware of the order of the arguments. The precedence is from left to right; this means that BusinessObjects determines the
aggregate to use beginning from the leftmost argument.
As a general rule, you should enter the most aggregate table as the first argument, the next most aggregate table as the second
argument, and so on.You must then use the Aggregate Navigation editor to set up a list of incompatible objects and/or
incompatible conditions for each aggregate table in your universe. These are the components that cannot be used with an
aggregate table.You can either set up these lists manually, or cause the list of objects to be detected by Designer.
Multidimensional analysis is a technique for manipulating data in order to view it from different perspectives and on different levels
of detail. In BusinessObjects, multidimensional analysis involves drill mode and slice-and-dice mode, and is enabled by the
Analyzer and Explorer components of the User module.
To set up a universe for multidimensional analysis, you must define hierarchies and dimensions that determine how users view and
analyze the data.
A dimension is simply the object to be tracked. A dimension can be an object such as Country, Region, and City. A hierarchy is an
ordered series of related dimensions. An example of a hierarchy is Geography, which may group dimensions such as Country,
Region, and City.
A class is a logical grouping of objects within a universe. In general, the name of a class reflects a business concept that conveys
the category or type of objects. For example, in a universe pertaining to human resources, one class might be Employees.
A class can be further divided into subclasses. In the human resources universe, a subclass of the Employees class could be
Personal Information.As designer, you are free to define hierarchies of classes and subclasses in a model that best reflects the
business concepts of your organization.
An object is the most refined component in a universe. It maps to data or a derivation of data in the database. Using objects, end
users can build queries to generate reports.The name of an object suggests a concept drawn from the terminology of a business or
discipline. For a human resources manager, objects might be Employee Name, Address, Salary, or Bonus, while for a financial
analyst, objects might be Profit Margin, Return on Investment, etc.For the purposes of multidimensional analysis, objects are
qualified as one of three types: dimension, detail, or measure
.
51.What is a list of values?
A list of values contains the data values associated with an object. These data values can originate from a corporate database, or a
flat file such as a text file or Excel file. In Designer you create a list of values by running a query from the Query Panel. You can
then view, edit, purge, refresh, and even export this file. A list of values is stored as an .lov file in a subfolder of the UserDocs
folder.
The SQL editor lets you enter or modify an SQL statement for either the Select statement or Where clause. To invoke this editor,
click the button to the right of either the Select or Where text box. You can type the SQL statement directly in the text box located
in the upper part of the editor window. Or you can formulate your syntax by using any combination of the following elements:
tables, columns, classes, objects, operators, or functions. To select an element (and cause it to appear in the text box) double-click
it in the appropriate pane.The functions listed in the Functions pane include the native SQL functions of your RDBMS as well as
BusinessObjects @ functions. For further information on @ functions, click .
By clicking on a function, you can view its syntax and purpose; this information is displayed in the Description box.
Notes
If you intend to export the universe, you must select Secured as the connection type.
If you click the File/New starts Quick Design wizard check box in the General tab (Tools menu, Options command) the New
command automatically launches the Quick Design
The Universe pane displays the components of the universe from the point of view of BusinessObjects; that is the classes, objects,
and conditions.
The Structure pane reflects the underlying database structure of the universe including the tables, columns, and joins.
The Table Browser is the component that lets you create the classes and objects of the universe from the tables and columns of a
database.
Designer contains a variety of features for organizing and viewing the tables and columns in the Structure pane. Among these
features are:
List Mode, which adds three panes to the Structure pane. These panes are for viewing the names of tables, joins, and contexts.
When you click a component in a pane, its corresponding graphical representation in the schema is highlighted.
Graphic options, which let you customize the shape or appearance of the tables, columns, joins, and cardinalities in the
Structure pane.
Arrange tables, a feature that reorganizes the tables in the Structure pane so as to produce an orderly display.
Gridlines, a command that displays a grid, which you can use to align tables in the Structure pane.
Table (Column) Values, commands that display the data values associated with a particular table or column.
5 Click OK.
A strategy is a script that automatically extracts structural information from a database. Designer provides a number of default
strategies you can use. These are strategies for extracting joins, detecting cardinalities, and creating default classes and objects.
Options for indicating default strategies are located in the Database tab of the Options dialog box.
You can also create your own strategies. Such strategies are referred to as external strategies. With an external strategy, you can
specify the exact way that objects and joins are to be extracted from the database structure. The strategy you use, for example,
can be a script generated from a CASE Access tool. An external strategy is specific to one RDBMS.
3 In the Default Creation box, select the default strategies you want.
Option Description
Extract joins with tables. Retrieves tables with the joins that link them according to a join strategy.
Detect cardinalities in joins. Detects the cardinalities inherent in the joins.
6
Create default classes and objects from tables. Causes classes and objects to be generated in the Universe pane when you
insert tables in the Structure pane.
If you select one or more options, Designer uses the corresponding strategies specified in the Strategies tab of the Universe
Parameters dialog box:
Option Description
Objects The strategy creates classes, and names them based on the tables in the database; it also creates objects, and
names them based on the columns in the database. It replaces all underscore characters (_) with spaces.
Joins From the list box, select a join strategy. A description is displayed below the name of the current strategy.
Tables Reads the table structure from the database system tables.
With an external strategy, you can specify the exact way that objects and joins are to be extracted from the database structure.All
external strategies are contained within the same text file. The name of this text file is indicated in the .prm file specific to your
RDBMS. In the .prm file, the strategy file is declared as follows:
STG=[StrategyFileName]
where StrategyFileName is the name of the strategy file.
An external strategy, whether for objects or for joins, is made up of the following sections:
a name and description (These are visible in the Strategies tab of the Universe Parameters dialog box.)
a type parameter: object or join
an SQL parameter or file parameter
an optional parameter that points to a connection other than the universe connection.
An external strategy can be based on SQL or a file.
After you have set up external strategies, you can specify them from the Quick Design wizard. Or you can specify them from the
Strategies tab of the Universe Parameters dialog box.
Select the List Mode command from the View menu.panes (Tables, Joins, and Contexts) are added above the display of the
schema. When you click a component in one of these panes, Designer highlights its graphical representation in the schema, and
vice-versa.
1 In the Structure pane, click the table whose values you wish to view.
2 Select the Table Values command from the View menu.displays a window, which lists all the values for each
column in the table. With the check box Distinct Values, you can filter the display so that only unique values are shown.
7
1 In the Structure pane, place the pointer on the column whose values you wish to
view.may wish to enlarge the view of the columns by applying the Zoom In command
one or more times.
This makes it easier to select a column.
2 Click the right mouse button.pop-up menu appears.
3 From the pop-up menu, select the View Column Values command.displays a window, which lists all the values for the
column. With the check box, Distinct Values, you can filter the display so that only unique values are shown.
Designer supports the following types of joins: equi-joins, outer joins, theta joins, and shortcut joins.
In addition to join strategies, Designer provides several other methods for creating or editing joins:
the Detect Joins command
tracing the joins manually
the Edit Join dialog box
the formula bar
1 Select the Detect Joins command from the Tools menu.Candidate Joins dialog box appears. It displays the joins that were
detected according to the join strategy set for the universe. By default, all the joins are selected.
2 Insert the joins by doing any of the following:
Select one join by clicking it, and then click the Insert button.
Select several contiguous joins. Hold down the Shift key, then click the first and last join. All the joins between the selected
joins will be highlighed. Click the Insert button.
Select several joins that are not contiguous. Click each join while holding down the Ctrl key. Click the Insert button.
Select all highlighted joins, and then click the Insert.
3 Click the Close button to dismiss the dialog box.joins appear in the Structure pane.
1 Position the mouse pointer over the column to be the source of the join.pointer is transformed into a hand symbol.
2 Click the column with the left mouse button.column is highlighted.
3 While keeping the left mouse button pressed, drag the join which begins to appear away from the source column toward the
destination column.pointer is transformed into a pencil.
4 Position the pencil over the column to be the destination of the join.
5 When the second column is highlighted, release the mouse button.join between the two tables is created.
1 Click the join that you want to edit.formula for the join appears in the formula bar.
2 Click the entry area of the formula bar, and edit the formula.
3 Press the Enter key to exit from the formula bar.
Note
By default, the formula bar is activated. To deactivate it, select the Formula Bar command from the View menu.
74.Delete a join
Cardinality expresses the minimum and maximum number of instances of an entity B that can be associated with an instance of an
entity A. The minimum and the maximum number of instances can be equal to 0, 1, or N.Because a join represents a bidirectional
relationship, it must always have two cardinalities.
If you selected the Detect cardinalities in joins options in the Database tab of the Options dialog box, Designer detects and
retrieves the cardinalities of the joins. If you do not use this option, you can still retrieve the cardinalities for one or all joins in the
universe.
There are two main methods for detecting or editing cardinalities:
the Detect Cardinalities command
the Edit Join dialog box
76.Detect cardinalities
You can detect the cardinalities for one join or for all the joins in the universe. For a single join, click it, and in the Edit Join dialog
box, click the Detect button. To detect the cardinalities for all joins:
Note
The Graphics tab of the Options dialog box contains a number of options for the display of cardinalities in the Structure pane.
A loop is a situation that occurs when more than one path exists from one table to another. Loops result in ambiguity in the design
of a universe. Designer enables you to identify loops in one of two ways:
You can run the Check Integrity function, which indicates the existence of any loops.
You can select the Detect Loops command from the Tools menu. If there are loops, the Loop Detection viewer appears; it indicates
the joins causing a loop.You can then use aliases or contexts to resolve the loops in your universe.
An alias is a logical pointer to an alternate table name. The purpose of an alias is to resolve loops in the paths of joins. In some
cases, more than one alias may be necessary for a given table.
As you create aliases, Designer may prompt you to create other aliases. This occurs when the new aliases result in the need for
additional aliases; in other words, creating such aliases entails the propagation of other aliases.
In such a situation, two options are available to you:
You can cause only the first table proposed to be aliased
You can alias all the tables listed (i.e. propagate the aliases)
Designer displays an alias in the Structure pane as a table. It links an aliased table to existing tables, re-arranging joins, as
necessary.
1 Select the Detect Aliases command from the Tools menu.Candidate Alias dialog box appears.
2 In the left pane of the dialog box, click the first table that you wish to alias.right pane displays the alias name(s) Designer
suggests for the table you selected. To give an alias a different name, click the Rename button, and enter the new name.
3 Click the Create button.message box prompts you to confirm the creation of the alias(es). In some cases, a dialog box may
prompt you to propagate additional aliases.
Notes
Before using Detect Aliases, check to see that all the tables in the universe are already linked by joins.
Before using Detect Aliases, be sure that Designer has already detected all the cardinalities of joins; if this is not the case,
select the Detect Cardinalities command from the Tools menu.
9
80.Create an alias manually
1 In the Structure pane, click the table for which you want to create an alias.
2 Select the Alias command from the Insert menu.dialog box appears prompting you to enter a name for the aliased table.
3 Enter a new name for the aliased table, or keep the one proposed.
4 Click OK.aliased table appears in the Structure pane.
Note
If you create an alias manually, you must also create the joins necessary to link it to the other tables.
A context is a rule by which Designer can decide which of two paths to choose when more than one path is possible from one table
to another. Contexts can be used to resolve loops in the universe.
You can create contexts manually, or cause them to be detected by Designer. When contexts are useful, Designer suggests a list
of contexts that you can create.
1 Select the Detect Contexts command from the Tools menu.Candidate Contexts dialog box is displayed.
2 In the left pane of the dialog box, click the name of the first context you wish to create. Click the Add button.context is
displayed in the right pane. You can remove any context from the right pane by selecting it, and then clicking the Remove button.
4 Repeat steps 2 and 3, if applicable, to add the other contexts.
5 If you wish to rename a context, select it from the right pane, and then click the Rename button.Rename Context dialog box
appears from which you can enter a new name.
6 Click the OK button.Structure pane is displayed in List Mode. This lets you view the contexts you created.
With the Check Integrity command, you can test the structure of your active universe. This means testing to determine whether its
components are accurate and up-to-date.
Check Integrity serves the following purposes:
It detects any inconsistencies in the objects, joins, conditions, and cardinalities of your universe.
It detects whether there are any loops in the joins.
It determines whether changes were made to the database to which the universe is connected.
1 Select the Check Integrity command from the Tools menu.Integrity Check dialog box appears.
2 In the dialog box, click the component(s) to be checked by clicking the corresponding check boxes.Check All causes all the
options to be checked.
3 Click the parse level.parsing checks only the syntax of a component Thorough parsing checks both the syntax and
semantics of a component. Of the two options, the latter may take longer to run.
4 Click OK.
Note
Options for running Check Integrity automatically are available in the Options dialog box (Tools menu).
1 Click the class after which you want the new class to appear in the Universe pane.
2 Select the Class command from the Insert menu.Edit Properties dialog box appears.
3 Enter the name of the class in the Class Name text box.
4 Enter information about the class in the Description text box.
10
5 Click the OK button.
Notes
A class appears within the Universe pane with a symbol.
If you insert a class in an opened class, it becomes a subclass of this class. Otherwise, it appears
87.Create an object manually
1 In the Universe pane, position the pointer within the class in which you want the object
to appear.
2 Select the Object command from the Insert menu.Edit Properties dialog box appears; by default, the Definition tab is
displayed.
3 In the Name box, type the name of the object.
4 If necessary, change the type of the object in the list box.object can be a character, number, long text, or date.
5 Enter information about the object in the Description text box.
Note
You can use the SQL editor to enter the SQL definition of the object; i.e. the Select statement and the Where clause. To invoke this
editor, click the to the right of either the Select or Where text box.
The SQL editor lets you enter or modify an SQL statement for either the Select statement or Where clause. To invoke this editor,
click the button to the right of either the Select or Where text box.
You can type the SQL statement directly in the text box located in the upper part of the editor window. Or you can formulate your
syntax by using any combination of the following elements: tables, columns, classes, objects, operators, or functions. To select an
element (and cause it to appear in the text box) double-click it in the appropriate pane.
The functions listed in the Functions pane include the native SQL functions of your RDBMS as well as BusinessObjects @
functions. For further information on @ functions, click .
By clicking on a function, you can view its syntax and purpose; this information is displayed in the Description box.
Designer provides four types of functions: Number, Character, Date and @Functions. Refer to your database guide for further
details on the first three types of functions. Functions beginning with the @ character are BusinessObject functions that render the
definition of objects dynamic and database-independent.
@Function Purpose
@Aggregate_Aware is used to enhance the performance of SQL transactions; i.e. it determines which tables to use in SQL
generation: either aggregate tables or detailed tables.
@Prompt is used to create an interactive object. In the Query Panel, this type of object causes a message to appear that
prompts the end user to enter a specific value.
@Script is used to recover the results of an executed macro created with the Visual Basic Editor in the BusinessObjects
User module.
@Select lets you re-use the Select statement of an existing object
@Variable is used to reference the value assigned to a name or variable.
@Where lets you re-use the Where clause of an existing object.
@Aggregate_Aware
Syntax @Aggregate_Aware(aggregate_table_1, ... aggregate_table_n)arguments are the names of alternative aggregate tables.
The precedence of the arguments is from left to right.
Description is used to enhance the performance of SQL transactions; i.e. it determines which tables to use in SQL generation:
either aggregate tables or detailed tables.
Example @Aggregate_Aware(sum(Region_SLine.sales_revenue), sum(Service.price * Invoice_Line.days *
Invoice_Line.nb_guests))
@Prompt
Syntax @Prompt ('message', ['type'], [lov], [MONO|MULTI], [FREE|CONSTRAINED]) message is the text of a message within
single quotes. type can be one of the following: 'A' for alphanumeric, 'N' for number, or 'D' for date. lov can be either a list of
values enclosed in brackets (each value must be within single quotes and separated by commas) or the name of a class and object
separated by a backslash and within single quotes. MONO means that the prompt accepts only one value. MULTI means that the
11
prompt can accept several values. FREE refers to free input as opposed to CONSTRAINED, which means that the end user
must choose a value suggested by the prompt.
Description Is used to create an interactive object. In the Query Panel, this type of object causes a message to appear. This
message prompts the end user to enter a specific value.
Note The last four arguments are optional; however, if you omit an argument you must still enter the commas as separators.
Example In Where Clause:.city IN @Prompt ('Choose City', 'A', {'Chicago', 'Boston', 'New York'}, MULTI, FREE)the Query
Panel, the object prompts the end user to choose a city.
@Script
Syntax @Script('var_name', 'vartype', 'script_name') 'var_name' is a variable name declared in the VBA macro. This name enables
the results of the executed macro to be recovered in the SQL definition of an object. This name must be identical in both the macro
and in the SQL definition of the object. 'vartype' is the variable type declared in the VBA macro: 'A' for alphanumeric, 'D' for
date, 'N' for numeric. 'script_name' is the name of the VBA macro to be executed. VBA macro files are located in the Scripts folder.
Description Recovers the results of an executed macro created with the Visual Basic Editor in the BusinessObjects User
module.
Note The second argument is optional; however, if you omit it you must still enter the commas as separators.
Example In Where clause:.cust_id = @Script('Number_of_customers', 'A', 'customers')the results of a macro called
customers, which calculates the number of customers.
@Select
Syntax @Select(Classname\Objectname)
Description Lets you re-use the Select statement of an existing object.
@Variable
Syntax @Variable('myname')'myname' can be one of the following: The text of an interactive object previously created with
the @Prompt function; i.e. the first argument entered in the @Prompt function. A BusinessObjects system variable such as
BOUSER or BOPASS. These variables represent respectively the user name and password forming the user identification. System
variables also exist for the connection to the RDBMS.
@Where
Syntax @Where(Classname\Objectname)
Description Lets you re-use the Where clause of an existing object.
The qualification of an object reveals how it can be used in multidimensional analysis. An object can be qualified as a dimension, a
detail, or a measure.In the Universe pane, the symbol beside each object indicates its qualification:
a for a dimension
a for a measure
a for a detail
1 Double-click the object in the Universe pane.Edit Properties dialog box is displayed.
2 In the Definition tab, change the object's type, if necessary.
3 Click the Properties tab.
4 In the Qualification box, click the Dimension radio button.the object is of type date, click the Automatic Time Hierarchy
button, enter the necessary options, and then click the OK button.
5 Click the OK button.
Notes
By default, all objects you create manually already have a dimension qualification.
A dimension object appears within the Universe pane
12
1 First create a dimension object of type date.
2 Click the Properties tab of the Edit Properties dialog box.
3 Click the Automatic Time Hierarchy button.Automatic Time Hierarchy dialog box appears.
4 In the dialog box, select and name the dimensions you wish to use, and click OK.
5 Click the OK button.
Note
In the Universe pane, each time dimension appears as an subobject of the date object.
1 Double-click the object in the Universe pane.Edit Properties dialog box is displayed.
2 In the Definition tab, change the object's type to number.
3 Click the Properties tab.
4 In the Qualification box, click the Measure radio button.
5 Indicate how the measure is to be projected when aggregated: Average, Count, Max, Min, Sum, or Unknown.the
appropriate value from the list box.
6 Click the OK button.
Note
A measure object appears within the Universe pane with a symbol.
1 Double-click the object within the Universe pane.Edit Properties dialog box is displayed.
2 In the Definition tab, change the object's type, if necessary.
3 Click the Properties tab.
4 In the Qualification box, click the Detail radio button.
5 Click the Associated Dimension list box, and select the object to which you are assigning the detail object.
6 Click the OK button.
Notes
A detail object is displayed in the Universe pane with a symbol.
A detail object appears in the Universe pane as a subobject of the dimension object it describes.
95.Create a condition
Notes
You can use the SQL editor to formulate the Where clause.
A condition appears in the Universe pane with a symbol.
1 Select the User Objects command from the Insert menu.Insert User Objects dialog box is displayed.
2 Click a user object file.user object file has a .udo extension
3 Click the Open button.
Notes
By default, user object files are stored in the Universe folder.
By default, user objects appear in a class called Created from User Objects.
Multidimensional analysis is a technique for manipulating data in order to view it from different perspectives and on different levels
of detail. In BusinessObjects, multidimensional analysis involves drill mode and slice-and-dice mode, and is enabled by the
Analyzer and Explorer components of the User module.
To set up a universe for multidimensional analysis, you must define hierarchies and dimensions that determine how users view and
analyze the data.
A dimension is simply the object to be tracked. A dimension can be an object such as Country, Region, and City. A hierarchy is an
ordered series of related dimensions. An example of a hierarchy is Geography, which may group dimensions such as Country,
Region, and City.
13
98.Create a custom hierarchy for multidimensional analysis
Notes
When you add a hierarchy, you automatically include all its dimension objects.
You can also drag and drop a hierarchy from the Default Hierarchies box to the Custom Hierarchies box.
You can rearrange the order in which hierarchies are displayed by using the Move Up or Move down button.
Note
You can rearrange the order in which dimension objects are displayed in a hierarchy by using the Move Up or Move down button.
A list of values contains the data values associated with an object. These data values can originate from a corporate database, or a
flat file such as a text file or Excel file. In Designer you create a list of values by running a query from the Query Panel. You can
then view, edit, purge, refresh, and even export this file. A list of values is stored as an .lov file in a subfolder of the UserDocs
folder.
1 In the Universe pane, double-click the object for which you want to create a list of values.Edit Properties dialog box
appears.
2 Click the Properties tab.
3 Enter a name for the .lov file in the List Name text box.can enter up to 8 alphanumeric characters.
4 Click the Display button to obtain the List of Values dialog box.List of Values dialog box displays all the possible data values
associated with the object.
5 Click the OK button to create the .lov file.stores .lov files in a subfolder of the UserDocs folder. The name of the subfolder is
that of the universe in which the object is located.
1 Select the Lists of Values command from the Tools menu.List of Values dialog box is displayed.
2 In the dialog box, click the object whose list of values you wish to edit.
3 Click the Personal Data radio button in the Properties group box.message box informs you that you are about to change the
.lov type from corporate to personal.
4 Click the OK button to confirm the action.displays the Access Personal Data dialog box. The options displayed vary
depending on the file type you select.
5 Click the Browse button, and from the browser, specify the file to be used as the .lov.can also type the file name in the
Name text box.
6 Specify the file format by selecting an option from the Format list box.options are Text Files (*.asc;*.prn;*.txt;*.csv),
Microsoft Excel, Lotus 1-2-3, or dBASE.
7 Specify the remaining options, as necessary.a text file, one line is equivalent ot one row. For a text file, indicate the type of
column delimiter: a tabulation, space, or character. If you select character as the type, enter the character in the text box.
8 Click the Run button to confirm the above actions, and to close the dialog box.
14
104.What is aggregate awareness?
Aggregate awareness is a feature that makes use of predefined aggregate tables to enhance the performance of SQL
transactions. It is used to improve the speed by which aggregates are calculated in the database.
To set up aggregate awareness in a universe, you define or more objects using the @Aggregate_Aware function. The syntax for
this function is as follows:
The arguments of this function are all the names of alternative aggregate tables. When you formulate the syntax, you should be
aware of the order of the arguments. The precedence is from left to right; this means that BusinessObjects determines the
aggregate to use beginning from the leftmost argument.
As a general rule, you should enter the most aggregate table as the first argument, the next most aggregate table as the second
argument, and so on.
You must then use the Aggregate Navigation editor to set up a list of incompatible objects and/or incompatible conditions for each
aggregate table in your universe. These are the components that cannot be used with an aggregate table.
You can either set up these lists manually, or cause the list of objects to be detected by Designer.
Designer lets you save universes in either enterprise or workgroup mode.Enterprise mode means that you are working in an
environment with a repository. Workgroup mode means that you are working without a repository. The mode in which you save
your universe determines whether other designers are able to access them.By default, a universe is saved in the mode in which
you are already working. For example, if you launched a session in enterprise mode, any universe you save is automatically in that
mode. However, if you want to make a universe accessible to another designer working without a repository, then click the Save as
Workgroup check box in the Save as universe dialog box.
1 Select the Export command from the File menu.Export Universe dialog box appears.
2 In the Repository list box, click the universe domain to which you want to export the universe.
3 In the Groups box, click the group(s) to which you want to export the universe.
4 If you wish to export other universes at the same time, click the Add button, and then use the browser to specify the
universes.default, all open universes are displayed.
5 Double-click each universe you wish to keep locked in the repository.padlock appears beside a locked universe.
6 In the Universes box, click the universe(s) you wish to export.
7 Click OK.
15
Notes
You can export a universe only if its connection type is secured.
By default, the Universes box displays a list of all open universes. To remove a universe from this list, select it, and then
click the Remove button.
6 Click OK.
Linked universes are universes that share common components such as parameters, classes, objects, or joins. Among linked
universes, one universe is said to be the kernel or master while the others are the derived universes.A kernel or master universe
represents a re-useable library of components.
Derived universes may contain some or all of the components of the kernel or master universe, in addition to any components that
have been added to it.
Some of the benefits inherent in the use of linked universes are as follows:
A dynamic link may considerably reduce development and maintenance time. When you modify a component in the kernel
universe, Designer propagates the change to the same component in all the derived universes. Instead of re-creating common
components each time you create a new universe, you can centralize such components in a kernel universe, and then include
them in all new universes.
Linked universes promote workgroup design. Common components can be shared among several designers.
Linked universes facilitate specialization. Development can be split between database administrators who set up a basic kernel
universe, and the more specialized designers who create more functional universes based on their specific field.
You can link the active universe to a kernel universe, only if the following requirements are met:
The kernel universe and active universe were created from the same data account and the same RDBMS.
The kernel universe was exported and re-imported at least once.
Exported derived universes are located in the same universe domain as the kernel universe.
All classes and objects are unique in both the kernel universe and the derived universes. (Otherwise, collisions may occur.)You are
authorized to link the given universe.
Note
A derived universe does not recover the lists of values containing personal data from the kernel universe. However, if you need
certain lists of values, you can use the following workaround: in the derived universe, create new objects defined in the same way
as those in the kernel, then hide them. You can then assign them to these objects lists of values, which you can then modify and
export.
Notes
To link an active universe to a kernel universe, you must have exported the kernel universe at least once. Otherwise, Designer
does not allow the link.
Designer displays the components from the kernel universe as dimmed in both the Universe and Structure panes of the
active universe. You cannot modify or delete them; however, you can create a join linking a table originating from the kernel
universe to one in the active universe.
16
GENERAL
BUSINESSOBJECTS is an integrated query, reporting and analysis solution for business professionals that allow them to access
the data in their corporate databases directly from their desktop and present and analyze this information in a
BUSINESSOBJECTS document.
It is an OLAP tool that high-level management can use as a part of a Decision Support Systems (DSS).
BUSINESSOBJECTS makes it easy to access the data, because you work with it in business terms that are familiar to you, not
technical database terms like SQL.
How many modes are there in BO & Designer? (KPIT Infotech, Pune)
There are 2 types: Enterprise Mode, Workgroup Mode.
Q. How do you save a Business Objects document which can be accessed by all users in workgroup mode?
If we want to make a universe accessible to another designer working without a repository, then click the Save as Workgroup
check box in the Save as universe dialog box.
4. What is a macro?
A macro is a series of commands and functions that are stored in a Visual Basic for Applications module and can be run
whenever you need to perform the task. If you perform a task repeatedly, you can automate the task with a macro. You
create macros using the Visual Basic Editor.
5. What is an add-in?
Add-ins are programs that add optional commands and features to BUSINESSOBJECTS. Add-ins are usually created by
those responsible in your company for adding customized features to BUSINESSOBJECTS. All you probably need to do
is install and uninstall add-ins that are sent to you.
DESIGNER
In the BusinessObjects User module, universes enable end users to build queries from which they can generate and
perform analysis. Universes isolate end users from the complexities of the database structure as well as the intricacies of
SQL syntax.
17
Q. Can a Universe connect to multiple databases? (AG Technologies)
7. What are the types of connections we use when connecting to the database? (KPIT Infotech, Pune)
There are three types of connections namely: - Secured, Shared and Personal.
A secured connection is used to centralize and control access to sensitive or critical data. It is the safest type of
connection for protecting access to data.
A shared connection is used to access common resources such as universes or documents. Several users can thus use
it.
A personal connection is specific to one user and can be used only from the computer on which it was created.
A universe is a set of classes and objects intended for a specific application or group of users.
When creating universes, universe designers define and qualify objects. The qualification of an object reveals how it can
be used in analysis in reports. An object can be qualified as a dimension, a detail, or a measure.
A dimension object is the object being tracked; in other words, it can be considered the focus of the analysis. A dimension
can be an object such as Service, Price, or Customer.
Dimension objects retrieve the data that will provide the basis for analysis in a report. Dimension objects typically retrieve
character-type data (customer names, resort names, etc.), or dates (years, quarters, reservation dates, etc.)
A detail object provides descriptive data about a dimension object (or attribute of a dimension). It is always associated
with a specific dimension object. However, a detail object cannot be used in drill down analysis. E.g. Address & phone
number can be attributes about the customer dimension.
Quarter
Region
City
Month
Creating hierarchies
You can create your own custom hierarchies from any dimensions available in
the report. The dimensions you include in a hierarchy can be local variables,
derived variables, or dimensions returned by data providers.
Note: You can also use a date-type user object as the basis for a time hierarchy.
For information on user objects see “Creating User Objects” on page 78.
To create a custom hierarchy
1. Click the Hierarchies command on the Analysis menu.
The Hierarchy Editor opens.
2. In the Hierarchy Editor, click New.
3. Type the name of the new hierarchy, then click outside the name box.
4. In the Available Dimensions box, click the first dimension for the new
hierarchy, then click Add.
The dimension you clicked appears in the new hierarchy's folder in the
Available Hierarchies box.
5. Add the other dimensions you want to include and then click OK.
19
11. Can a Universe have more than 1 fact Table?
Yes. Typically a universe can have more than 1 fact table and numerous aggregated tables.
With certain database structures, you may need to use contexts rather than aliases to resolve loops. A situation where
this commonly occurs is a transactional database with multiple fact tables (“multiple stars”) that share lookup tables.
Of course, the reliability of the technique depends on the accuracy of the aggregate tables. In fact, they must be refreshed
at the same time as all fact tables. A universe that is “aggregate aware” has one or more aggregate objects with
alternative definitions based on these tables. These definitions correspond to levels of aggregation. For example, a Profit
object can be aggregated by month, by
quarter, or by year. Queries built from such a universe return information aggregated to the
appropriate level at optimal speed.
Aggregate awareness is a feature that makes use of predefined aggregate tables to enhance the performance of SQL
transactions. It is used to improve the speed by which aggregates are calculated in the database.
To set up aggregate awareness in a universe, you define one or more objects using the @Aggregate_Aware function.
The syntax for this function is as follows:
@Aggregate_Aware(aggregate_table_1, ... aggregate_table_n)
The arguments of this function are all the names of alternative aggregate tables. When you formulate the syntax, you
should be aware of the order of the arguments. The precedence is from left to right; this means that BusinessObjects
determines the aggregate to use beginning from the leftmost argument. As a general rule, you should enter the most
aggregate table as the first argument, the next most aggregate table as the second argument, and so on. You must then
use the Aggregate Navigation editor to set up a list of incompatible objects and/or incompatible conditions for each
aggregate table in your universe. These are the components that cannot be used with an aggregate table. You can either
set up these lists manually, or cause the list of objects to be detected by Designer.
When an object is at the same or higher level of aggregation as the table, it is compatible with the table.
When an object is at a lower level of aggregation than the table (or if it is not at all related to the table), it is incompatible
with the table.
16. I have Customer dimension table and a fact table with cust_to_ship_key and cust_to_bill_key. How do I get the
corresponding customer names?
Create an Alias table for Customer dimension table. Join the cust_to_ship_key with a customer key of Actual customer
table and join the cust_to_bill_key with customer key of the Alias.
Built-in Strategies: Designer provides a number of default strategies which we can use. These are strategies for
extracting joins, detecting cardinalities, and creating default classes and objects. Options for indicating default strategies
are located in the Database tab of the Options dialog box.
External Strategies: We can also create our own strategies. Such strategies are referred to as external strategies. With
an external strategy, we can specify the exact way that objects and joins are to be extracted from the database structure.
The strategy we use, for example, can be a script generated from a CASE Access tool. An external strategy is specific to
one RDBMS.
21
You can select the Detect Loops command from the Tools menu. If there are loops, the Loop Detection viewer appears; it
indicates the joins causing a loop.
You can then use aliases or contexts to resolve the loops in your universe.
There is no strict rule to follow for resolving loops. However, whenever possible you should use an alias instead of a context. When
you use a context, you expose the BUSINESSOBJECTS end user to the database structure. They are forced to decide which
context they want to use to run their query. The role of the universe is to shield end users from the database structure, so they do
not have to make such decisions.
29. How many types of join are available? (KPIT Infotech, Pune)
Designer supports the following types of joins: equi-joins, outer joins, theta joins, and shortcut joins.
A Theta join links tables based on a relationship other than equality between two columns.
@Function Purpose
@Aggregate_Aware is used to enhance the performance of SQL transactions; i.e. it determines which
tables to use in SQL generation: either aggregate tables or detailed tables.
22
@Prompt is used to create an interactive object. In the Query Panel, this type of object
causes a message to appear that prompts the end user to enter a specific value.
@Script is used to recover the results of an executed macro created with the Visual Basic
Editor in the BusinessObjects User module.
@Select lets you re-use the Select statement of an existing object
@Variable is used to reference the value assigned to a name or variable.
@Where lets you re-use the Where clause of an existing object.
Because a join represents a bi-directional relationship, it must always have two cardinalities.
If you selected the Detect cardinalities in joins options in the Database tab of the Options dialog box, Designer detects
and retrieves the cardinalities of the joins. If you do not use this option, you can still retrieve the cardinalities for one or all
joins in the universe.
34. What are linked universes? (Designer’s Guide, 246) (Mascot, MBT, KPIT Infotech Pune)
Linked universes are universes that share common components such as parameters, classes, objects, or joins. Among
linked universes, one universe is said to be the kernel or master universe while the others are the derived universes.
A kernel or master universe represents a re-usable library of components. Derived universes may contain some or all the
components of the kernel or master universe, in addition to any components that have been added to it.
Approaches to linking universes
You can use one of three approaches when linking universes:
• The kernel approach
• The master approach
• The component approach
Q. How many types of Linked universes are there, and what are they? (ITC)
Answered above
SUPERVISOR
· A security domain, which contain the definition of the other domains as well as the definition of users
· Universe domains, which are meta-models of related databases, containing a description of the data to be
accessed
· Document domains, which contain the structures for storing shared documents and for executing tasks according to
a time stamped definition.
Define users and user groups, as well as assign profiles to them. User profiles include user identification (user name and
password), the products and modules they can work with, the universes they can access, and the documents that they
can share.
Control user access to Business Objects products, and manage the exchange and distribution of the universe and
documents of all the users.
24
USER MODULE
41. Can one create a report having two Data Provider each pointing to different Universes?
Yes.
Each BO channel is associated with a BROADCAST AGENT, itself associated with a user group in the BO repository.
Each channel uses a Channel Definition Format (CDF) file as an index to the Website.
The first time a document is published in the channel, the CDF file is created based on the template. It is then updated
every time a new document is published in the channel.
BO users can schedule a document to be published in one or more channels by a BROADCAST AGENT.
They can only publish in channels associated with the BROADCAST AGENT of groups to which they belong.
When BROADCAST AGENT publishes a BO document in a channel, it converts the document to HTML format and
simultaneously updates the channel’s CDF file so channel subscribers via IE4 can view the document.
SCHEDULING/PUBLISHING RELATED
25
BROADCAST AGENT lets users not only automate simple actions such as refreshing and printing documents, but control
processing with conditions which trigger distribution when pre-defined events occur.
Users can choose to publish documents to the repository, on a web server or on the server file system. Users with access
to the repository can view documents that BROADCAST AGENT has processed in BUSINESSOBJECTS or
WEBINTELLIGENCE. BROADCAST AGENT supports HTML publishing on the web, on channels and on your intranet or
extranet.
Like Business Objects, with WebIntelligence, you can access the data in your corporate databases or data warehouses
from within your office, home, or around the world, using your corporate intranet, extranet, or the World Wide Web.
The repository is set up and administered by the BUSINESSOBJECTS supervisor. All of the rights you have as a user are granted
by your BUSINESSOBJECTS supervisor using BUSINESSOBJECTS SUPERVISOR. The supervisor defines:
• The parts of the BUSINESSOBJECTS interface you can access. Your supervisor can restrict the availability of
BUSINESSOBJECTS functionality, such as access to certain menu commands.
• Your database connections
• The universes you can access for creating and editing queries
Q. What are the different tools in Business Objects 5.1? (AG technologies)
· Save as PDF
· Add hyperlinks to reports
· Zero Administration BusinessObjects
Q. Explain the Reporting features in Business Objects reporting tool? (AG Technologies)
BUSINESSOBJECTS let you access data from a wide range of sources. You can access data from
• Relational databases (RDBMS), such as ORACLE, Microsoft SQL Server, Informix and IBM DB2.
• Multidimensional (OLAP) databases, such as Microsoft OLAP Services, Hyperion Essbase, and
ORACLE Express.
• Text files and spreadsheets
• Packaged applications such as SAP
• Virtually any data source using Microsoft Visual Basic for Applications (VBA) procedures.
26
To access a data source with BUSINESSOBJECTS, you build a data provider. The types of data providers supported in
BUSINESSOBJECTS depends on whether you install BUSINESSOBJECTS from the installation CD or install
BUSINESSOBJECTS via an Internet browser.
What is scope of analysis? (BO User’s guide,65) (Mascot, KPIT Infotech, Pune)
Analysis means looking at data from different viewpoints and on different levels of detail. In reports, you can use scope of analysis
to ensure that the data included in your report can be displayed at the appropriate level of detail for your analysis. Setting a scope
of analysis allows you to work in drill mode, which enables you to display data in progressively greater detail. “Scope of analysis”
27
means a subset of data, returned by a query, that you will use for analysis in your report. The data for your scope of analysis does
not appear in
the report until you decide that you want to use it in analysis. The scope of analysis you can define depends on hierarchies in the
universe. A hierarchy, which the designer sets up when creating the universe, consists of dimension objects ranked from “less
detailed” to “more detailed”. The objects that belong to hierarchies are the ones you can use to define scope of analysis.
Applying conditions
A condition is a way of limiting the data that a query returns.
When universe designers build universes, they can create predefined
Predefined conditions for you to use. For example, the Island Resort Marketing
conditions universe contains predefined conditions such as Year 98, which lets you
obtain reservations for 1998 only. You can apply one or more predefined
conditions when you build a query. However, you can neither delete
predefined conditions from a universe, nor can you edit their definition.
Simple Conditions Enable you to limit data returned by a result object. For example, you
can find out about certain customers by applying a simple condition on
the Customer object, then selecting the customer names that appear in
a dialog box.
Complex Enable you to limit the query results by any object in the Universe.
Conditions
Note: Scheduling reports containing user objects is not a supported feature. User objects are removed when
the report is refreshed.
28
How can an end-user share user objects with other users?
If an end-user wants to share user objects with other users, they should ask the universe designer to include these user objects in
the related universe in order to make them available to all BUSINESSOBJECTS end-users. The universe designer includes the file
UNIVERSE_NAME.UDO in the universes where the user objects are to be used.
A group of conditions consists of two or more conditions applied on the same query. In the Conditions box in the Query Panel,
conditions are linked by an operator (AND or OR).
Note: You can only work in drill mode if you have installed the EXPLORER option with BUSINESSOBJECTS.
Client/Server connection
29
If you are using a BUSINESSOBJECTS client/server connection offline and not connected to a repository, you can still work with
documents and universes stored locally on your computer and even create and refresh documents if you have a connection to the
database, and the database connection and security information is stored on your computer.
Web connection
If you are using a web connection offline, you will not be able to retrieve documents from, and send documents to, Personal
Document folders on the web server, and will not be able to create queries or refresh documents because all the database and
connection information is stored on the web server.
In offline mode, you can continue to work on documents stored locally; you can work on the formatting of your reports or analyze
data in existing reports, for example, and work with the data contained in the document to build new reports. If
BUSINESSOBJECTS cannot establish the connection you requested with the web server, it may give you the option of starting
BUSINESSOBJECTS in offline mode if your user rights allow you to work offline.
No remote connection
You may also choose to start BUSINESSOBJECTS in offline mode because you know you have no remote connection at all - for
example, on a plane - and want to continue to work on documents you have stored locally. Note: The right to use
BUSINESSOBJECTS offline is given to you by your BUSINESSOBJECTS supervisor or system administrator. Depending on how
BUSINESSOBJECTS has been set up in your company, you may not even have the option of logging on to BUSINESSOBJECTS
in offline mode.
Tables: BUSINESSOBJECTS tables display data in either rows or in columns and have a header and a footer. Header and footer
rows and columns are special rows and columns. The header displays information about the row or column e.g. a label or the
name of the variable whose values are displayed. The footer displays
calculations on the values displayed in the columns or rows.
Crosstab tables: A crosstab is a particular kind of table where data is displayed in columns and in rows. Corresponding data
appears at the intersection of the columns and rows; this part of the crosstab is called the body. The body typically displays
numerical data. A crosstab can display both row totals and column totals as well as a grand total. You need at least three variables
to display data in a crosstab including one measure. The measure is placed in the body of the crosstab.
30
Free-Standing Cells: BUSINESSOBJECTS reports have two types of cell: cells that make up tables and freestanding cells. A
free-standing cell is a single cell that is not attached to any other report component and can be moved and formatted individually.
Free-standing cells have many uses in BUSINESSOBJECTS reports. They are containers for text, calculations or graphics and are
used among other things for report titles, for adding comments and for displaying page numbers.
You set up a master/detail report by setting a variable as a master cell. This section describes the different ways to do this. You
can:
• use a variable in a table or crosstab to create a master cell
• add a variable from the Report Manager to create a master cell
Ignoring filters
You can force BUSINESSOBJECTS to ignore any filters you have inserted on a report so that when you make a calculation, the
calculation is made on all the data, not just the filtered values. To do this, you use the
NoFilter function. The syntax is: =NoFilter(formula)
Highlighting Data: using Alerter Note: You cannot use alerters on charts.
What is a break?
A break does what its name implies. It breaks up the data in a table or crosstab by grouping the data according to a selected value.
This allows you to display all the data for each value of a dimension variable together, and more importantly, it allows you to
display subtotals.
Calculations
31
BUSINESSOBJECTS has standard calculation functions that enable you to make quick calculations on the data in reports. These
calculations are available directly from a menu. The most commonly used calculations are also available on the Report toolbar.
Hierarchies
Objects are also organized in this way for drilling. When you analyze data in drill mode, you use hierarchies. The Universe classes
are the default hierarchies you use for drilling but the Universe designer can also set up custom hierarchies. You can also create
and edit hierarchies in your reports. Drill hierarchies only contain dimension objects. In drill mode, you drill down on dimensions, for
example from Year to Quarter to Month. At each level, measures, such as Revenue or Profit Margin, are recalculated.
Slice-and-dice mode enables you to switch the position of data in a report. You can, for ex, move data from columns to rows. The
result would be a crosstab, where numeric data such as revenue appears at the intersection of rows and columns. You can also
use slice-and-dice mode to:
• Work with master/detail reports • Display and remove data
• Rename, reset and delete blocks • Turn tables and crosstabs into charts, and vice versa
• Apply, edit and delete breaks, filters, sorts, rankings and calculations.
Slice-and-dice mode is enabled by the Slice and Dice Panel, a pop-up window that provides a graphical representation of the
report you are working on. You carry out tasks by dragging and dropping icons that represent the data you can use.
Formatting Sections
Formatting Tables
Tables and crosstabs are made up of headers and footers, columns and rows, and cells. All these elements together make up the
block. The cell is the most basic element of a table or crosstab. Rows and columns are made up of groups of cells. When you
format tables and crosstabs, you can work on the formatting cell by cell or on the block formatting.
32
Using hyperlinks in BusinessObjects reports
You can easily add hyperlinks such as email addresses and web site addresses to your reports. BUSINESSOBJECTS
automatically recognizes certain keywords or symbols included in the address, adds any extra syntax behind the scenes and
formats the address as a hyperlink. Hyperlinks you add to a BUSINESSOBJECTS report are retained when you save the report in
PDF or in HTML format.
When you have a report in sections with a lot of information in each section, a convenient way of presenting the report is to use
outline view. Outline view folds up the sections in the report to display only the high level information that you’ve included at the top
of each section. People viewing your reports can then open up the sections they are interested in to get more details. A bar with
arrows is displayed at the left side of the report window. The number of buttons displayed at the bottom of the outline bar depends
on the number of sections you have in the report.
What is a template?
A standard report does not contain information on page setup or include custom elements such as graphics. A
BUSINESSOBJECTS template allows you to do this. A template is a special kind of BUSINESSOBJECTS document that
contains pre-defined styles and structure that you use as a foundation to create reports. BUSINESSOBJECTS comes with
several templates for you to use and you can also create your own.
Structure: The structure of a report defines how the data is presented. Your data can be presented in a crosstab, a column chart,
or it can have a master/detail structure
Styles: The styles contained in a template define the report page background and the style of the headers and footers.
What are categories? (while publishing the reports (supervisor & BCA))
Planning
Break down the information system into functional
areas
33
Analysis
Analyze the information needs of users
Design
Design a conceptual schema
Design the specification of a universe
Implementation
Create a universe with DESIGNER
Test the universe with BUSINESSOBJECTS/WEBINTELLIGENCE
Distribute the universe
Repeat the above steps for other universes
Maintenance
Update and maintain the universe
Notify end users of changes
34
A Business Objects repository is a set of data structures stored on a database. A repository makes it possible to share the
resources necessary for client/server architecture. To ensure security and manage user resources, a repository comprises
three types of domains:
• a security domain, which contain the definition of the other domains as well as the definition of users
• universe domains, which are meta-models of related databases, containing a description of the data to be accessed
• document domains, which contain the structures for storing shared documents and for executing tasks according to a
timestamped definition.
These three types of domains make it possible for all users to share resources.
Business Objects
1. Can we create aliases for every table before hand ? If yes what are the disadvantages?
2. What problems are NOT known while performing Integrity Check?
3. Where do we use GLOBAL FILTERS, explain with example?
4. What sort of Drill Down charts did you prepare, name few.
5. Outer Join Pl/Sql statement
6. How did you give a developed Universe to your client.
7. Using Formula Object in another Formula Object
8. What happens if Cardinalities are not Resolved.
2. Explain the steps to create Universe? (Need to explain all the necessary steps including filters, joins, objects etc.)
3. How if you will create conditions and where we will create these filters?
4. Can we create conditions at report level? What are disadvantages creating conditions at report level. Explain?
5. Practical question: I have one department and avg(sal) of each department,
Now I want a report some thing like department name along with Avg(sal) by specifying the department number as
Parameter. Explain how best we can do this report.
35