9 Documentation Updates

This chapter provides an overview of the documentation updates introduced in Oracle Communications Billing and Revenue Management (BRM) 7.5 Patch Set 1 through BRM 7.5 Maintenance Patch Set 1.

Documentation Updates in Maintenance Patch Set 1

This section describes the documentation updates in BRM 7.5 Maintenance Patch Set 1.

Taxware Information Removed

BRM no longer supports an integration with Taxware. Therefore, the Taxware information in all BRM 7.5 documents was removed.

BRM CDR Format Renamed

The phrase ”BRM CDR format” in BRM documentation has been replaced by the phrase ”Oracle CDR format”.

Documentation Updates in Patch Set 12

This section describes the documentation updates in BRM 7.5 Patch Set 12.

Updates to BRM 7.5 Developer's Reference

Information about the PCM_OP_ACT_LOG_USER_ACTIVITY opcode is now added in BRM Developer's Reference.

Documentation Updates in Patch Set 5

This section describes the documentation updates in BRM 7.5 Patch Set 5.

Updates to Account Synchronization Multidatabase and Multischema Information

Oracle no longer supports BRM multidatabase systems. Instead, it recommends using BRM multischema systems based on an Oracle Real Application Clusters (Oracle RAC) system.

Therefore, the multidatabase information in the account synchronization chapters in BRM Installation Guide was replaced with multischema information.

Documentation Updates in Patch Set 4

This section describes the documentation updates in BRM 7.5 Patch Set 4.

Updates to Multidatabase and Multischema Information

Oracle no longer supports BRM multidatabase systems. Instead, it recommends using BRM multischema systems based on an Oracle RAC system.

Therefore, the multidatabase information in all BRM 7.5 documents except BRM Upgrade Guide and the account synchronization chapters in BRM Installation Guide was replaced with multischema information. In particular, the following have been updated to support multischema systems:

Documentation Updates in Patch Set 3

This section describes the documentation updates in BRM 7.5 Patch Set 3.

Updates to BRM 7.5 Changing Service Status Documentation

In the BRM 7.5 documentation, the discussions about changing service status in BRM Managing Customers and the Customer Center Help do not include the following information:

Before changing the status of a service that uses the default life cycle in a plan with options, note the following:

  • For standalone services:

    • Closing a required service closes all the services in the plan.

    • Inactivating a required service inactivates only that service.

    • Closing or inactivating an optional service closes or inactivates only that service.

  • For services in subscription groups:

    • Closing a required subscription or member service closes all the services in the plan.

    • Inactivating a required subscription service inactivates all its member services.

    • Inactivating a required member service inactivates only that member service.

    • Closing or inactivating an optional member service closes or inactivates only that member service.

Note:

The effects of changing the status of a service in a standard plan have not changed. See BRM Managing Customers and the Customer Center Help for more information.

Updates to BRM 7.5 Custom Field ID Information

BRM Developer's Guide and the Storable Class Editor Help include incorrect information about custom field IDs.

Table 9-1 lists the field ID ranges for Oracle-only use and for customer use:

Table 9-1 BRM Field ID Restrictions

Field ID Range Reserved For

0 through 9999

Oracle use only

10,000 through 999,999

Customer use

1,000,000 through 9,999,999

Oracle use only

Over 10,000,000

Customer use


Updates to Information about Installing 32-Bit Client Libraries

Starting with Oracle Database 11g Release 2 (11.2), Oracle does not include any 32-bit client binaries in its 64-bit client software. If you use utilities (such as pin_rel) that require lib32 in their library paths, you must explicitly install the Oracle 32-bit client software and configure the Oracle libraries for Rated Event (RE) Loader accordingly.

See the discussion about configuring Oracle libraries for RE Loader in BRM Configuring Pipeline Rating and Discounting for information about configuring the Oracle 32-bit client for RE Loader.