Integration Guide for Oracle Billing Insight > Integrating Oracle Billing Insight With Oracle BRM >

Oracle BRM Data Assumptions

The following data and data relationships in Oracle BRM are required for integrating Oracle BRM with Oracle Billing Insight. Due to the flexible nature of Oracle BRM, it is not possible to list all the possible requirements for integration.

• Billing accounts for the same company must have the same company value. Additionally:
  • The top level account of hierarchy must have the account contact information
  • The company contact is required information for extracting the company object.
  • The integration uses the canon_company column of the Oracle BRM account_nameinfo_t table for the company identity, so all accounts for the one company must have the same value in this field.
• One service can be associated with one number device only. For example, if a user purchases telephone service, only one number-device can be associated to this service at a time. This allows Oracle Billing Insight to retrieve the subtotal of a device at the item level.
• The integration uses items to differentiate charge types. One item must contain only one type of usage charge. Different types of charges must be broken down into different items, if they are currently aggregated in Oracle BRM. For example, telephone, SMS, and data usage charges must be separate items.
• An account can have multiple services, and each service or combination of services can have one billinfo (bill unit) value. Oracle Billing Insight supports one billinfo for one account, and no billinfo at the service level. The billinfo value can be prepay or postpay. The billinfo value can associate with a business profile, and Oracle Billing Insight assumes billinfo is prepay if the associated business profile has a key/value pair of prepaid/yes.
• Add a description for the device when associating it to a service. Oracle Billing Insight uses the the DESCR column of the DEVICE_T Oracle BRM table as the contact name for the device.
• Make sure the billing contact information, address, city, state, canon_countr, and zip code values are not null in the account_nameinfo_t table. This is required information in Oracle Billing Insight.