Charging Contract State

Business Context and Use

The charging contract state business object is a technical view of a provider contract (see charging contract). This data model facilitates the migration of subscriber data to SAP CC. It enables to migrate information such as:

• The status of some parts of the contract (if they are active, expired, ...)
• Values stored in persistent counters created in a charging contract stored in SAP CC such as the number of free minutes for voice calls for example
• Values stores in persistent internal counters used by SAP CC only

Customer Data Migration

A former system manages master data related to the end customers of a service provider. You want to migrate this data to SAP Convergent Charging.

• You must extract this information
• You must implement the conversion of this data into master data (and data models) provided and managed by SAP CC before any activity:
  • Business partners (subscriber accounts, subscriber mapping tables )
  • Business agreements (prepaid accounts and external postpaid accounts)
  • Contracts (charging contracts, subscriber mapping tables )
• You must determine the initial states of the prepaid accounts and the initial states of the migrated charging contracts.
• You must implement the bulk provisioning of this converted data to SAP CC according to the following sequence:
  • Create or change subscriber accounts in bundle mode
  • Create or change external accounts in bundle mode
  • Create or change prepaid accounts in bundle mode
  • Change the initial state of prepaid accounts in bundle mode
  • Create the necessary the subscriber mapping tables
  • Create the necessary charging contracts in bundle mode (or in mass mode)
  • Change the initial state of charging contracts in bundle mode
  Two different processing modes are provided for these bulk operations: The bundle mode (all-or-none) or the mass mode (most). Determine the mode recommended for your business requirements.
• Switch the business traffic to SAP Convergent Charging

Related Operations

You can use the following operations to restore the appropriate initial state of charging contracts been migrated. Two bulk operations are available with dedicated processing modes according to your migration requirements.

• Change the initial state of a charging contract
• Change the initial state of multiple charging contracts in bundle mode
• Change the initial state of multiple charging contracts in mass mode

• Read the current state of a charging contract

Features

A charging contract state contains all the elements of the charging contract that can change over time.

Structure

• The status of some parts of the charging contract (if they are active, expired, ...)
• Values stored in counters defining credits such as the number of free minutes for voice calls
• Values stores in internal counters that are required by the pricing logic set in the charge plans or refill plan activated in the contract

Initial State of a Charging Contract

• The unique identifier of the charging contract
• The last snapshot date of the charging contract
• The last snapshot days of the charging contract
• The list of the counters shared with several contract items; Several namespaces can be set to restrict the sharing.
• The states of the contract items activating charge/refill plans

Initial State of a Contract Item

• The identifier of the contract item; This item activates a charge plan or a refill plan configured in the pricing catalog owned by the service provider that markets the contracted customer service.
• The list of the counters created at contract item level
• The states of the charge activation elements of the contract items; These objects are managed by the SAP CC system in background.

Initial State of a Charge/Refill Activation Element

• The identifier of the charge activation
• The status of the charge activation with the related last activation date
• The list of the counters defined at charge activation level

Prerequisites

There is no prerequisite.

Integration

There is no specific integration information.

Constraints and Integrity Conditions

• Do not use this data model and its related operations to implement a regular reset of counters visible from a CRM application. Model this function in the pricing logic and configure the pricing catalog of the service provider with charges including recurring ratesusing the SAP CC Core Tool.
• Do not use this data model and its related operations to implement online refilling services. Use the relevant process component Refilling provided by the SAP CC Web Services.