Charging Contract Management

Business Context and Use

This process component is used in context of Order Capture and Contract Management. It provides the necessary operations to manage the provisioning of charging contracts (provider contracts) master data stored in SAP Convergent Charging.

Terminology

A charging contract is the charging view of a provider contract. It includes the pricing and charging data that is stored in SAP Convergent Charging. Consult the charging contract business object for more information.

To complete the master data provisioning related to end customers in SAP CC, implement the operations of the Subscriber Mapping Table Management and the Subscriber Range Table Management process components.

Important note

In a context of migration of end customer related master data (subscriber data), you must first implement the necessary operations of this process component to be able to convert the data of the former system to data stored in SAP CC. Once this data migrated, you must finalize the migration by using the Charging Contract State Management process component to set this data back to its appropriate initial state.

Order Capture and Contract Management

A CRM application or another provisioning system manages master data related to the order capture and contract management and replicates data in SAP CC by maintaining subscriber data for end customers. Data includes: Provider contracts (charging contracts), subscriber mapping tables

• Create and maintain a charging contract for an end customer of the service provider

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 Service Operations

The following operations are related to charging contract management:

• Create or change charging contracts in bundle mode
• Create or change charging contracts in mass mode
• Create or change a charging contract
• Cancel a charging contract
• Find a charging contract

Related Process Compoments

• Customer Master Data (Business Partner Management):
  • Subscriber Account Management
  • Subscriber Mapping Table Management
  • Subscriber Range Table Management
• Customer Master Data (Business Agreement Management): Subscriber Account Management
• Data Migration (Order Capture and Contract Management): Charging Contract State Management

Prerequisites

• You have determined the customer data that must be replicated to or synchronized with subscriber data stored in SAP Convergent Charging
• You have implemented the necessary operations of the Subscriber Account Management process component in contexts of Business Partner Management and Business Agreement Management

Integration

There is no specific integration information.

Constraints and Integrity Conditions

There is no specific constraint.