Maintaining the Repository and Warehouse

This chapter contains the following topics:

Maintaining the Oracle Healthcare Provider Supply Chain Analytics Repository
Maintaining the Oracle Healthcare Provider Supply Chain Analytics Warehouse

Maintaining the Oracle Healthcare Provider Supply Chain Analytics Repository

You can modify the OHPSCA-delivered repository file (RPD) for any one of the following reasons:

You have added a column or table to the data warehouse, and now need to propagate that addition into the layers of the repository.
To add a calculated column as a function of some set of physical layer columns.
To modify a repository variable value, or add a new repository variable, for use in some Web Catalog calculation.
To modify a group, an account, or a privilege maintained through the repository.

Caution:

Exercise caution when you modify the RPD. Please conform with the following recommendations.

The following rules apply when you modify the RPD:

Privileges to make changes should be granted only to a limited set of users who need to make such changes and also know how to make them correctly.
At upgrade time, use the OBIEE utility equalizerpds.exe to merge your modified RPD with the Oracle-supplied RPD.

Maintaining the Oracle Healthcare Provider Supply Chain Analytics Warehouse

For better performance of the dashboards and reports, you should partition the following tables:

Table 4-1 Tables for Partitioning

Table	Partition Type	Columns Involved
W_AP_INV_DIST_F	PARTITION BY RANGE	INVOICED_ON_DT_WID
W_EHA_CONSIGN_INVENTRY_F	PARTITION BY RANGE	CONSIGN_INV_BALANCE_DT_WID
W_EHA_INV_CYCLE_COUNT_F	PARTITION BY RANGE	INVENTORY_CYCLE_COUNT_DT_WID
W_EHA_LINEN_XACT_F	PARTITION BY RANGE	LINEN_TRANSACTION_DT_WID
W_EHA_PURCH_CYCLE_LINE_A	PARTITION BY RANGE	ORDERED_ON_DT_WID
W_EHA_PURCH_ORDER_A	PARTITION BY RANGE	ORDERED_ON_DT_WID
W_EHA_SUPPLY_EXPENSE_F	PARTITION BY RANGE	CALENDAR_DT_WID
W_INVENTORY_DAILY_BAL_F	PARTITION BY RANGE	INV_BALANCE_DT_WID
W_PURCH_COST_F	PARTITION BY RANGE	ORDERED_ON_DT_WID
W_PURCH_CYCLE_LINE_F	PARTITION BY RANGE	ORDERED_ON_DT_WID
W_PURCH_ORDER_F	PARTITION BY RANGE	ORDERED_ON_DT_WID
W_PURCH_RCPT_F	PARTITION BY RANGE	ORDERED_ON_DT_WID
W_PURCH_RQSTN_LINE_F	PARTITION BY RANGE	SUBMITTED_ON_DT_WID
W_PURCH_RQSTN_STATUS_F	PARTITION BY RANGE	SUBMITTED_ON_DT_WID
W_RQSTN_LINE_COST_F	PARTITION BY RANGE	SUBMITTED_ON_DT_WID

You should make partitions such that one partition holds data for one calendar month for a fact. For example, if the warehouse table has data for one year, there should be 12 partitions created based on the values of the partitioned column.

Also, the create script for bitmap indexes on partitioned tables should be changed. For example:

CREATE BITMAP INDEX IDX1 ON TAB1 (COL) local;