1. Collections Manager
  2. Setting Up Collections Profiles

8 Setting Up Collections Profiles

In Oracle Communications Billing and Revenue Management (BRM), you create collections profiles to organize bill units for collections purposes.

Topics in this document:

Setting Up Collections Profiles

Collections profiles define categories into which you organize bill units for collections purposes. For example, you could organize bill units by credit score. Bill units with a score below a certain number are assigned to one collections profile, and bill units with higher scores are assigned to a different profile.

A bill unit's collections profile helps determine to which collections scenario a bill unit is assigned. (Scenarios define entry and exit criteria for collections as well as what happens to a bill unit while it is in collections.)

For example, bill units in the low-credit-score profile might be assigned to scenarios with more aggressive collections actions and lower entry criteria. Customers in the high-credit-score profile could be assigned to scenarios with more lenient policies.

By default, all bill units belong to a single collections profile. If you do not need a more complex system, you do not have to define any additional profiles. You can map all your scenarios to the default profile.

To set up additional profiles, you complete two sets of tasks:

  1. Define names and descriptions for the profiles by using Collections Configuration.

    When you define a new profile, Collections Configuration creates a /config/collections/profile object, which stores definitions of collections profiles.

  2. Customize the PCM_OP_COLLECTIONS_POL_SELECT_PROFILE policy opcode. You need to write code that defines the characteristics of the collections profiles and maps bill units to them.

    Note:

    This step requires programming.

Increasing the Size of the CM Cache for Profiles Data

When setting up additional profiles, you might need to increase the space allocated to the profiles data in the CM cache.

To increase the CM cache size for profiles data:

  1. Open the CM configuration file (BRM_home/sys/cm/pin.conf) in a text editor.

  2. Increase cache_size in the following entry: 
    - cm_cache fm_collections_config_profiles_cache number_of_entries, cache_size, hash_size

    Note:

    The default is 20480 bytes.

  3. Save and close the file.

  4. Stop and restart the CM.