4 Storable Class Changes

This chapter provides an overview of the storable class changes introduced in Oracle Communications Billing and Revenue Management (BRM) 7.5 Patch Set 1 through BRM 7.5 Patch Set 4.

New Storable Classes

Table 4-1 lists the storable classes introduced in the BRM 7.5 patch sets. The new storable classes are grouped by the respective patch sets.

Table 4-1 New Storable Classes

New Storable Class	Description
/profile/collections_params	(Patch Set 4) Stores the customer's collections profile information. The /profile/collections_params object is created when the customer's account is created using the PCM_OP_CUST_COMMIT_CUSTOMER opcode. See the discussion about creating customer's collections profiles at the time of customer account creation in BRM Managing Customers for more information.
/offer_profile	(Patch Set 3) Stores the static information associated with services in policy labels. An /offer_profile object is an optional element in a price list and is associated with a /product object or a /discount object. /offer_profile objects are created and managed using the loadpricelist utility and the price list opcodes (PCM_OP_SET_PRICE_LIST and PCM_OP_GET_PRICE_LIST). For more information, see the discussion about managing offer profiles in BRM Managing Customers.
/collections_action/collect_payment	(Patch Set 2) Stores information about the amount to be paid and a link to the /payinfo object for a Collect Payment action. For more information, see the discussion about collecting payments in BRM Collections Manager.
/collections_action/promise_to_pay	(Patch Set 2) Stores information about the promise-to-pay milestones. For more information, see the discussion about promise-to-pay in BRM Collections Manager.
/config/collections/scenario_params	(Patch Set 2) Stores additional parameters for scenario assignment or replacement. For more information, see the discussion about collections scenario replacement in BRM Collections Manager.
/event/activity/collections	(Patch Set 2) Stores information about the collections for promise-to-pay and scenario replacement activities. For more information, see the discussion about promise-to-pay agreements and collections scenario replacement in BRM Collections Manager.
/event/activity/collections/promise_to_pay	(Patch Set 2) Stores the parameter information while entering into the promise-to-pay agreement. For more information, see the discussion about promise-to-pay events in BRM Collections Manager.
/event/activity/collections/replace_scenario	(Patch Set 2) Stores the parameter information while replacing a bill unit's existing scenario with a new scenario. For more information, see the discussion about collections scenario replacement in BRM Collections Manager.
/event/group/collections_targets	(Patch Set 2) Stores the information about the collections group.
/group/collections_targets	(Patch Set 2) Stores the information about several bill units under a single group entering or exiting collections and processes the collections actions.
/config/lifecycle_states	(Patch Set 1) Stores configuration information about the states, rules, and transitions in a custom service life cycle. A separate instance of this class is created for each custom service life cycle in your system. For more information, see the discussion about managing service life cycles in BRM Managing Customers.
/config/service_state_map	(Patch Set 1) Stores mapping between custom service life cycle states (PIN_FLD_LIFECYCLE_STATE field in /service objects) and default service life cycle statuses (PIN_FLD_STATUS field in /service objects). All state-to-status mapping in your system is stored in a single instance of this class. The instance can contain mapping for multiple service life cycles. For more information, see the discussion about managing service life cycles in BRM Managing Customers.
/config/subscriber_preferences_map	(Patch Set 1) Stores the possible configurations for subscriber preferences. For more information, see the discussion about in-session notifications in BRM Telco Integration.
/profile/subscriber_preferences	(Patch Set 1) Stores the preferences associated with a subscriber's profile. For more information, see the discussion about in-session notifications in BRM Telco Integration.

Changed Storable Classes

Table 4-2 lists the storable classes changed in the BRM 7.5 patch sets. The changed storable classes are grouped by the respective patch sets.

Table 4-2 Changed Storable Classes

Changed Storable Class	Description
/balance_group	(Patch Set 3) Now includes the PIN_FLD_CONSUMED_RESERVED_AMOUNT field in the PIN_FLD_BALANCES array to store the consumed reserved amount for the resource.
/config/reserve	(Patch Set 3) Now includes the PIN_FLD_RESOURCE_ID field, which stores the resource counter corresponding to the PIN_FLD_REQ_MODE passed in the input flist.
/event/billing/product/action	(Patch Set 3) Now includes the PIN_FLD_PRICE_LIST_NAME field, which stores information about the pricelist name associated with the purchased products.
/purchased_product	(Patch Set 3) Now includes the PIN_FLD_PRICE_LIST_NAME field, which stores information about the pricelist name associated with the purchased products.
/reservation	(Patch Set 3) Now includes the PIN_FLD_CONSUMED_RESERVED_AMOUNT field in the PIN_FLD_BALANCES array to store the input (from the network) about the used quantities and the consumed reserved amount for the resource.
/reservation_list	(Patch Set 3) Now includes the PIN_FLD_CONSUMED_RESERVED_AMOUNT field in the PIN_FLD_BALANCES array to store the consumed reserved amount for the resource.
/collections_scenario	(Patch Set 2) Now includes the PIN_FLD_PROMISE_TO_PAY array that stores the date and time the promise-to-pay agreement is effective for a bill unit, the total promised amount, and the link to the /event/activity/collections/promise_to_pay object. For more information, see the discussion about promise-to-pay in BRM Collections Manager.
/config/collections/action	(Patch Set 2) Now includes the PIN_FLD_TARGET_ACTION field to determine which bill units the action should target.
/config/collections/scenario	(Patch Set 2) Now includes the following parameters: PIN_FLD_SEVERITY: Stores the scenario severity information. This parameter is added in the PIN_FLD_SCENARIO_INFO substruct. PIN_FLD_PROFILE_DATA_ARRAY: Stores the additional configurable parameters that are used to evaluate assignment or replacement of a scenario. The array elements form the evaluation formula associated with the collections scenario. For more information, see the discussion about collections scenario replacement in BRM Collections Manager.
/event/audit	(Patch Set 2) Now includes the PIN_FLD_EVENT_AUDIT array to store the pending receivables of the child and the effective_t field for auditing when a parent goes into collections because a group member has gone into collections.
/active_session	(Patch Set 1) Now includes the list of all thresholds breached during the current session. For more information, see the discussion about in-session notifications in BRM Telco Integration.
/config/aaa	(Patch Set 1) Now includes the maximum scaled delay time MaxScaledDelayTime configured for each resource ID. Used in calculating scaled delay time for tariff change indications in in-session notifications. For more information, see the discussion about in-session notifications in BRM Telco Integration.
/config/business_params	(Patch Set 1) Now includes the following parameters: SubscriberLifeCycle This parameter enables BRM to support custom service life cycles. By default, it is set to disabled. For more information, see the discussion about managing service life cycles in BRM Managing Customers. Piggyback This parameter enables BRM to support in-session notifications. By default, it is set to disabled. For more information, see the discussion about providing in-session notifications in BRM Telco Integration.
/config/opcodemap/tcf	(Patch Set 1) Now includes the VALIDATE_LIFECYCLE processing stage. During this stage, the PCM_OP_TCF_AAA_VALIDATE_LIFECYCLE helper opcode is called to validate a service request against the business rules configured for the current state of a service that uses a custom service life cycle. For more information, see the discussion about managing service life cycles in BRM Managing Customers.
/config/template	(Patch Set 1) Now supports the following key-value pair: Key: lifecycle_obj Value: Name of the custom service life cycle This key-value pair enables users to associate a /config/lifecycle_states object with a particular /service object. For more information, see the discussion about managing service life cycles in BRM Managing Customers.
/event/customer/status	(Patch Set 1) Now includes the following fields: PIN_FLD_LIFECYCLE_STATE: Stores the numeric ID of a custom service life cycle state. PIN_FLD_SERVICE_STATE_EXPIRATION_T: Stores the expiration day and time (time stamp) of the custom service life cycle state. For more information, see the discussion about managing service life cycles in BRM Managing Customers.
/service	(Patch Set 1) Now includes the following fields: PIN_FLD_LIFECYCLE_STATE: Stores the numeric ID of the service's current custom life cycle state. PIN_FLD_SERVICE_STATE_EXPIRATION_T: Stores the day and time (time stamp) the current state of the service expires and the transition to the next state in the service life cycle occurs. This field can contain a value only when the PIN_FLD_LIFECYCLE_STATE field contains a value. For more information, see the discussion about managing service life cycles in BRM Managing Customers.

New Notification Events

Table 4-3 lists the notification events introduced in the BRM 7.5 patch sets. The new notification events are grouped by the respective patch sets.

Table 4-3 New Notification Events

New Notification Event	Description
/event/notification/offer_profile/create	(Patch Set 3) Generated when a new offer profile is created.
/event/notification/offer_profile/delete	(Patch Set 3) Generated when an offer profile is deleted.
/event/notification/offer_profile/ThresholdBreach	(Patch Set 3) Generated when the sum of current balance and the consumed reservation is equal to or greater than the nearest threshold configured in the offer profile for a service and resource ID.
/event/notification/offer_profile/update	(Patch Set 3) Generated when an existing offer profile is modified.