13 Configuring Oracle Sales Analytics

This chapter describes how to configure Oracle Sales Analytics used with a Siebel CRM source system to meet your business needs.

It contains the following topics:

• Section 13.1, "Overview"

• Section 13.2, "Configuration Required Before A Full Load"

13.1 Overview

Oracle Sales Analytics is a comprehensive analytical solution that provides timely, fact-based insight into the entire sales process. It provides new levels of information richness, usability, and reach to sales professionals throughout the enterprise and in the field. All users, from sales executives to front-line sales representatives, get up-to-the-moment, complete, and in-context sales insight; insight that is personalized, relevant, and actionable. The benefits are faster and more informed decisions that help the sales organization compete more effectively, lower sales costs, and achieve better results.

13.2 Configuration Required Before A Full Load

This section contains configuration steps that you need to perform on Oracle Sales Analytics before you do a full data load, and contains the following topics:

• Section 13.2.1, "How to Deploy Stored Procedures"

• Section 13.2.2, "Configuration Steps for Controlling Your Data Set"

13.2.1 How to Deploy Stored Procedures

Stored procedures are a group of SQL statements that perform particular tasks on the database. For example, stored procedures can help to improve the performance of the database. You deploy stored procedures by copying the stored procedure files from your Oracle BI Analytics installation and deploying them to the target data warehouse.

Note: Some sessions may fail if these procedures are not compiled in the database before running the workflows.

To deploy stored procedures:

1. Navigate to the OracleBI\dwrep\Informatica\Stored_Procedure_Scripts folder.

2. Open one of the folders based your database platform, and copy the source code from the file FIND_AUDIT_VALUES.sql into the target data warehouse schema.

3. Compile the stored procedures in the target data warehouse database.

Note: If you have problems deploying the stored procedures, see your database reference guide, or contact your database administrator.

13.2.2 Configuration Steps for Controlling Your Data Set

This sections contains additional configuration steps for Oracle Sales Analytics, and contains the following topics:

• Section 13.2.2.1, "How to configure the snapshot frequency in Pipeline fact"

13.2.2.1 How to configure the snapshot frequency in Pipeline fact

Even though the snapshot of Pipeline is captured every time ETL is run, you can choose to persist daily snapshots, or weekly snapshots or monthly snapshots or even yearly snapshots. There is one parameter you need to modify to configure for this. This parameter is called "GRAIN".

The GRAIN parameter has a preconfigured value of 'DAY'. The possible values for the GRAIN parameter are:

• DAY

• WEEK

• MONTH

• QUARTER

• YEAR

To configure the snapshot frequency in Pipeline fact:

1. Open the parameterfileDW.txt file using a text editor in the OracleBI\DAC\Informatica\parameters\input folder.

2. Locate [SIL_PipelineFact] and $$GRAIN

3. Replace the default parameter value with your new value.

   Note: You need to use single quotes for the value.

4. Save and close the file.