Siebel Business Analytics Server Administration Guide > Completing Setup and Managing Repository Files > Setting Up the Repository to Work with Delivers >

Setting Up the SA System Subject Area

The Siebel Business Analytics Web Server is preconfigured to look for the SA System subject area on startup and will use it if it exists. You can import any external schema that holds group membership, users' primary email addresses, and users' SMTP devices (cell phones, handhelds, and so on), and then map it to the SA System subject area.

You can add columns to the SA System table (for example, adding a provider name) by extending the Siebel S_User table. For instructions, see the chapter about configuring tables and columns in Configuring Siebel Business Applications. You also need to import and map the extended table.

This section contains the following topics:

• Guidelines for Implementing the SA System Subject Area
• Setting Up the SA System Subject Area for a Stand-Alone Implementation
• Setting Up the SA System Subject Area for an Analytics Application

Guidelines for Implementing the SA System Subject Area

The name for the subject area must always be SA System. User table and column names for this subject area must exactly match the column names shown in Table 26 for mapping to be successful.

The following is a list of some general guidelines to use when implementing the SA System subject area.

• If the SA System subject area is used, every user and group must be present in the data. Siebel Business Analytics does not support group membership through a mix of internal analytics repository users and external users in the SA System subject area.
• When the SA System subject area is used, it is not recommended for the user to set up a delivery profile because there is no way for administrators to control this profile. For example, the administrator looses the ability to perform a mass update of email addresses. If a user does set up a delivery profile, the delivery profile will take precedence over what is shown in the SA System subject area.
• This feature affects what users are allowed to do in the system (authorization), not who users are (authentication). For related information about database authentication, see About Delivers and Database Authentication.
• The SA System subject area only needs to have read-access to the Administrator account and as a result, security settings are not compromised. If group membership is seen as privileged data, you can allow only the administrator to have access to this subject area.

Setting Up the SA System Subject Area for a Stand-Alone Implementation

Siebel Business Analytics standalone customers need to create and populate the SA System subject area in the analytics repository (RPD).

Customers who install the Analytics Server in a standalone environment (without Siebel Business Analytics applications) must perform the following tasks in the order shown using the data described in Table 26:

• Create tables and columns in your data source (for example your external database). For instructions, see the chapter about configuring tables and columns in Configuring Siebel Business Applications.
• Create and build the subject area in the analytics repository.
  • Import schema that stores the appropriate information. For instructions, see Creating and Administering the Physical Layer in a Repository.
  • Map the tables and columns from the Physical Layer to the Business Model and Mapping layer. For instructions, see Creating and Administering the Business Model and Mapping Layer in a Repository.
  • Map the tables and columns from the Business Model and Mapping layer to the Presentation layer. For instructions, see Creating and Maintaining the Presentation Layer in a Repository.

    The Presentation layer metadata needs to contain the SA System folder, User table, and columns as pictured in Figure 15.

Setting Up the SA System Subject Area for an Analytics Application

For Siebel Business Analytics application customers, the SA System subject area is preconfigured in the analytics repository. Figure 15 shows the table and columns in the presentation layer of the repository.

Figure 15. SA System Subject Area in the Presentation Layer

Columns in the SA System User Table

For Siebel Business Analytics application customers, the SA System subject area in the Presentation layer of the analytics repository is preconfigured for your use. Table 26 describes the columns in the User table of the SA System subject area folder. Any external schema that has the information in this table can be mapped to the SA System subject area.

Preconfigured Mapping for the SA System Subject Area

For Siebel Business Analytics application customers, Table 27 describes the preconfigured mappings for the SA system subject area. Fields that are not available in Oracle's Siebel transactional database will default to values shown in the table.

• Overriding Defaults. You can add user-specific values for these fields, by creating an extension table to the S_USER table. to store the user-specific defaults for these fields. Additionally, you can change any of the default values. The metadata for the following logical table can be modified to include any physical extension table.

  SA User.(User)

  For instructions, see the chapter about configuring tables and columns in Configuring Siebel Business Applications.

• Setting Provider Info. Typically, the cell phone and the fax numbers in Siebel Data Warehouse do not contain a provider name. Therefore, the Pager will typically be a numeric value such as 555-483-3843. To append a provider to this address, use the following guidelines:
  • If the entire company has the same provider, then you can append the provider in the column mappings.
  • If users can have different providers, you need to create an extension table. For instructions, see the chapter about configuring tables and columns in Configuring Siebel Business Applications.