Siebel Analytics Server Administration Guide > Setting Up and Working with a Repository > Components of a Repository in the Administration Tool >

Business Model and Mapping Layer

The Business Model and Mapping layer organizes information by business model. Each business model contains logical tables. Logical tables are composed of logical columns. Logical tables have relationships to each other expressed by logical joins. The relationship between logical columns can be hierarchical, as defined in business model hierarchies. Logical tables map to the source data in the Physical layer. The mapping can include complex transformations and formulas.

The Business Model and Mapping layer defines the meaning and content of each physical source in business model terms. The Siebel Analytics Server uses these definitions to pick the appropriate sources for each data request.

You can change the names and set the permissions of physical objects independent from corresponding business model object names and properties, and vice versa. Any changes in the underlying physical databases need not change the view of the tables in the business model that end user applications ultimately see and query—the business model to physical table mappings can change dramatically while remaining transparent to end user applications.

The logical schema defined in each business model needs to contain at least two logical tables. Relationships need to be defined between all the logical tables. For information about creating business model schemas, see Data Modeling.


 Siebel Analytics Server Administration Guide 
 Published: 23 June 2003