Oracle® Business Intelligence Applications Installation and Configuration Guide Version 7.9.4 E10742-01 |
|
Previous |
Next |
This appendix describes additional configuration steps for Oracle's Pharma Disconnected Analytics, and contains the following sections:
Pharma Disconnected Analytics is a preconfigured Disconnected Analytics application for Pharma Sales. Pharma components for Disconnected Analytics are installed during an Oracle Business Intelligence installation in the \OracleBIData\Disconnected\Pharma directory.
The following is a list of components that have been tailored for Pharma Disconnected Analytics and their locations:
PharmaDisconnect.rpd. The Pharma Disconnected Analytics repository is tailored for Pharma Disconnected Analytics and downloaded to the laptop during synchronization. It is located in the \OracleBIData\Disconnected\Pharma\Application directory.
PharmaDisconnect.webcat. Presentation Services tailored for Pharma Disconnected Analytics. It is located in the \OracleBIData\Disconnected\Pharma\Application directory.
Pharma.XML. Application configuration file tailored for Pharma Disconnected Analytics. It is located in the \OracleBIData\Disconnected\Pharma directory.
SQL Files. Series of predefined DDL files to create the Pharma Disconnected Analytics mobile database tables and indexes. The files are located in the \OracleBIData\Disconnected\Pharma\Application directory.
Messages XML Files. Language specific message XML files for localized Presentation Catalog captions in the Pharma Disconnected Analytics application. The files are located in the \OracleBIData\Disconnected\Pharma\messages directory.
Disconnected Sourcing Reports. Predefined Presentation Catalog reports used to extract data during the synchronization process to populate the tables in the Pharma Disconnected Application's mobile database. The reports are located in the Presentation Services catalog under the shared\disconnected folder.
The Pharma Disconnected Analytics components have been built to work against the standard server side Oracle Pharma Sales Analytics Application and Data Warehouse. The Pharma Disconnected Analytics components need to be customized to correctly reflect any changes and customizations made to the standard server side application before any initial synchronization.
To improve the performance of preprocessed synchronization by reducing query execution time on the Oracle BI Server, you can fine-tune the index strategy and sort the data during the ETL mapping process.
Note: For more detailed information on Disconnected Analytics Application configuration and deployment, see the Oracle Business Intelligence Disconnected Analytics Administration and Configuration Guide. |
Table F-1 contains a list of the sourcing reports (queries) for Oracle's Pharma Disconnected Analytics. These reports issue logical SQL to the Oracle BI Server to extract the data used to populate the local Disconnected client schema.
Table F-1 Sourcing Reports for Pharma Disconnected Analytics
Subject Area | Sourcing Report Name | Target Table |
---|---|---|
Pharma Promotional Effectiveness |
Day Dimension |
W_DAY_D |
Pharma Promotional Effectiveness |
Product Ranking Dimension |
W_CON_RANK_D |
Pharma Promotional Effectiveness |
Brick Dimension |
W_AREA_D |
Pharma Promotional Effectiveness |
Geography Dimension |
W_GEO_D |
Pharma Promotional Effectiveness |
Payor Plan Dimension |
W_INS_PLAN_D |
Pharma Promotional Effectiveness |
Product Hierarchy |
W_PRODUCT_DH |
Pharma Promotional Effectiveness |
Position Hierarchy |
W_POSITION_DH |
Pharma Promotional Effectiveness |
Call Priority List of Value Dimension |
W_LOV_D |
Pharma Promotional Effectiveness |
Product Indication List of Value Dimension |
W_LOV_D |
Pharma Sales Effectiveness |
Period Type List of Value Dimension |
W_LOV_D |
Pharma Promotional Effectiveness |
Person Dimension |
W_PERSON_D |
Pharma Objective Achievement |
Plan Promotion Dimension |
W_PLAN_PROMO_D |
Pharma Customer Demographics |
Contact Primary Address Dimension |
W_POSTN_CON_D |
Pharma Promotional Effectiveness |
Contact Call Activity Fact |
W_CON_CALL_F |
Pharma Promotional Effectiveness |
Contact Call Activity Aggregate |
W_CON_CALL_N_A |
Pharma Objective Achievement |
Contact Objective Fact |
W_CON_OBJ_F |
Pharma Sales Effectiveness |
Indirect Sales Market Level Fact |
W_MARKET_IDS_F |
Pharma Sales Effectiveness |
Indirect Sales Market Level Aggregate |
W_MARKET_IDS_N_A |
Pharma Sales Effectiveness |
Prescription Market Level Fact |
W_MARKET_RX_F |
Pharma Sales Effectiveness |
Prescription Market Level Aggregate |
W_MARKET_RX_N_A |
Pharma Sales Effectiveness |
Direct Sales Fact |
W_SYND_DS_F |
Pharma Sales Effectiveness |
Direct Sales Aggregate |
W_SYND_DS_N_A |
Pharma Sales Effectiveness |
Indirect Sales Fact |
W_SYND_IDS_F |
Pharma Sales Effectiveness |
Indirect Sales Aggregate |
W_SYND_IDS_N_A |
Pharma Sales Effectiveness |
Prescription Sales Fact |
W_SYND_RX_F |
Pharma Sales Effectiveness |
Prescription Sales Aggregate |
W_SYND_RX_N_A |
Note: The ATC hierarchy's ATC IV level should be linked to the lowest level of the Standard Product hierarchy and the lowest product level available for the Syndicated Data type loaded into the fact table. As a general rule, load data at the lowest level possible in the product hierarchy. For more information about best practices when using reports in Oracle's Pharma Analytics, see Appendix B in Siebel Life Sciences Guide, Version 8.0. |