Charging Contract State

Business Object (WS)

Definition

A charging contract state is a technical view of a charging contract that contains all the elements of the contract that can change over the time. You use this data model during a migration of end customer related master data (subscriber data) from a former system to a SAP CC system.

Technical Data

Software Product and Version	SAP Convergent Charging 5.0
Technical Details	Data Types
Version	0
Application Area	IS-CC

Business Context and Use

The charging contract state business object is a technical view of a 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 stored 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 , subscriber range tables )
  • Business agreements ( prepaid accounts and external accounts )
  • Contracts ( charging contracts , subscriber mapping tables , subscriber range tables )
• You must determine the states of the prepaid accounts and the states of the migrated charging contracts .

Then, you must implement the provisioning of this converted data to SAP CC by choosing one of the following solutions:

• Solution 1: You must implement bulk provisioning of this converted data to SAP CC according to the following sequence:
  • Create the necessary subscriber accounts in bundle mode or in mass mode
  • Create the necessary external accounts in bundle mode or in mass mode
  • Create the necessary prepaid accounts in bundle mode or in mass mode
  • Change the state of the prepaid accounts in bundle mode or in mass mode
  • Change the schedule of the blocked/locked/closed statuses of each relevant prepaid account
  
  
  • Create the necessary subscriber mapping tables
  • Create the necessary subscriber range tables
  
  
  • Create the necessary charging contracts in bundle mode or in mass mode
  • Change the state of the charging contracts in bundle mode or in mass mode
  • Create the necessary data tables relating to a charging contract or to a group of charging contracts ( subscriber mapping tables or subscriber range tables )
  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.

• Solution 2: You must implement the one step provisioning of this converted data to SAP CC according to the following sequence:
  • Import customer data
  • Change the operational status of the imported single or parent charging contract(s) to set it to active

• Switch off the business traffic to SAP Convergent Charging

Make sure that no business traffic acquired from mediation systems can trigger the charging services related to the customer data been migrated. This can corrupt the state of this master data. Make sure that no activation process of periodic and one-off fees can be manually or automatically triggered by a user or a connected system.

Related Operations

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

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

Consider also the service operation:

• 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

It contains information such as:

• 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 stored in internal counters that are required by the pricing logic set in the charge plans or refill plan activated in the contract

State of a Charging Contract

The state of a charging contract is defined by:

• The unique identifier 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

State of a Contract Item

The state of a charging contract item is defined by:

• 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.

State of a Charge/Refill Activation Element

The state of the charge activation (or refill activation) is defined by:

• 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

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 rates using 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.

Notes on SAP CC Implementation

You must have installed and configured the SAP CC Core Server system.

Configuration

Consult the SAP CC Configuration and Implementation Guide to know the necessary configuration or Customizing of the SAP CC system.

Before implementing SAP Convergent Charging in your SAP system landscape, you must configure the systems and the data (master data, business data).