The Oracle BRM database consists of many tables. In this article, the most important ones are presented and described. Underneath, a picture of the Oracle BRM 7.3. data model has been added.
In the database, account/customer related data such as names, addresses, profiles, current account balances, group charge sharing, and account hierarchy are stored. Deals can be purchased by the customer and associated with every account. Each customer can purchase more services. To know more, please examine the text underneath.
Stores information about the customer, including contact names, address, status, and customer segment information.
Stores data about an ongoing session.
Stores the balance information such as dollars, free minutes, bytes, and frequent flyer miles for various resources in an account . A balance group includes one or more sub-balances for each resource. The sub-balance contains the current amount, resource type, validity dates for the resource, rollover data, and sub-balance contributors.
Stores billing information, such as the amount due, amount adjusted, currency, and bill number. A /bill object is created at the beginning of a billing cycle.
Stores all billing, payment method, accounting cycle, and hierarchy information necessary to bill an account. A /billinfo object is created for every account. If the billinfo is subordinate, the /billinfo object points to the parent account and the parent account’s /billinfo object.
Base table for configuration objects. Subclasses hold specific configuration information for various features, for example, /config/beid defines currency and non-currency resources.
Stores information about a deal.When you use Pricing Center and connect to the database, all /deal objects in the database are shown in Pricing Center.
Stores information about devices. There is a separate /device object for every device managed by BRM. Generic data applicable to all devices is stored in the parent /device object. Subclasses such as /device/num store information specific to a particular device type.
Abstract class to record system-initiated and user-initiated events. Event objects are related to a specific service or to an account. An event includes generic information such as start and end times as well the balance impacts that are incurred by the account due to this event. The /event object points to the account balance group that is impacted.
Stores event data.
Stores a customer invoice and information about the invoice, such as the bill it is associated with. Each /bill object can have a corresponding /invoice object.
Created to bundle events, this table summarizes billable item activity by type. Rows in this table are added for each row in the BILL_T table.
Stores generic payment method information for an account.
Stores the information for a single product.
Abstract class to support custom account information. To use a /profile object, always create a subclass. You can link an account to any number of /profile objects.
Contains an entry for each discount owned by an account at the time of conversion.
Contains an entry for each product owned by an account at the time of conversion.
Tracks resources reserved for multi-service prepaid systems. Stores information about the account, balance group, and the service for which the resource reservation is created, the resource amount, and the expiration time for when the reserved resource expires.
Stores generic service type information for accounts. There is one row in this table for each applicable service for each entry in ACCOUNT_T. In addition to a row in this table, a row must be created in the service type table, such as IP service or email.