The 2wenty Terms in 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
An ordered series of related dimensions used for multidimensional analysis.
15.Join
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.
Note:- All the rest terms will be continued in the successive articles
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
An ordered series of related dimensions used for multidimensional analysis.
15.Join
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.
Note:- All the rest terms will be continued in the successive articles
No comments:
Post a Comment