Implementation Guide for Oracle Self-Service E-Billing > Customizing Oracle Self-Service E-Billing > Customizing the User Interface Files >

Using the OLAP Schema

OLAP is the Oracle Self-Service E-Billing data warehouse. It is a non-transaction schema used to save billing information and has no APIs for access. These tables are accessed directly through report XML files. For information on how to use report XML files to retrieve data from the OLAP schema, check the report XML files used to generate various billing reports. These files are defined in the EDX_HOME/config/rpt directory (or the EDX_HOME\config\rpt directory on Windows). In these directories, EDX_HOME is the directory where you installed Oracle Self-Service E-Billing.

The OLAP schema includes three kinds of tables:

• OLTP-OLAP Synchronization-Related Tables. Because OLAP is a non-transactional schema, it has no (or very limited) UI transactional operations. However, it requires transaction data to report on, for example, hierarchy information. This information is synchronized from OLTP to OLAP at real time. The tables related to this operation are:
  • EDX_RPT_ACCOUNT_WSPACE
  • EDX_RPT_ACCOUNT_XREF (Not used)
  • EDX_RPT_CC_CHARGE_WSPACE
  • EDX_RPT_HIERARCHY_NODE_PERIOD
  • EDX_RPT_HIERARCHY_TREE_DIM
  • EDX_RPT_HIERARCHY_TYPE_DIM
  • EDX_RPT_HIERARCHY_XREF_DIM
  • EDX_RPT_USER_HIERARCHY_WSPACE (Not used)
  • EDX_RPT_USER_SERVICE_WSPACE (Not used)

    Do not customize these tables. Operations on these tables are read-only.

• Dimensional Tables. Except the ones described in this topic, the remaining dimensional tables are used to save dimensional data such as accounts, services, dates, periods, and so on. Also most all the dimensional tables have some flexible fields which are for customization. Use the flexible fields to hold your custom information instead of adding your own columns. You can also create new dimensional tables.
• Fact Tables. Fact tables are used to hold the fact information such as call details or summaries. You can add new columns to the fact tables if necessary or add your own fact tables.

Never make any changes that could break the backward compatibility of the DB schema, such as changing the column type or renaming a column or a table.

The Oracle Self-Service E-Billing screen JSPs pick the label from the property file using a unique key.