Prepaid Account State Management

Process Component (Web Service)

Definition

Management of the states of prepaid accounts in subscriber accounts been migrated to SAP Convergent Charging.

Technical Data

Software Product and Version	SAP Convergent Charging 5.0
Technical Details	prepaidaccountstate
Namespace	http://schema.prepaidaccountstate.ws.highdeal.com/
Proxy Instance in SAP CC System	Updater
Web Service Version	0
WSDL	https://<UPDATER_INSTANCE_HOST>:<UPDATER_WS_PORT_NUMBER>/prepaidaccountstate?wsdl
Endpoint	https://<UPDATER_INSTANCE_HOST>:<UPDATER_WS_PORT_NUMBER>/prepaidaccountstate
Application Area	IS-CC

Business Context and Use

This process component is used in a migration context of end customer related mater data (subscriber data). You want to migrate customer data from a former system to SAP Convergent Charging. This process component enables you to finalize the migration of subscriber accounts by restoring prepaid balances to their appropriate initial values. This state of a prepaid account is composed of:

• The balance (amount and currency) of the prepaid account

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.

Included Service Operations

The following operations are related to the management of the state of prepaid accounts in bulk:

• Change the state of prepaid accounts in bundle mode (all-or-none)
• Change the state of prepaid accounts in mass mode (most)

You can use the following single operation to change the state of a prepaid account in a subscriber account:

• Change the state of a prepaid account

See here the technical details about these service operations.

Related Process Components

• Customer Master Data (Business Partner Management): Subscriber Mapping Table Management and Subscriber Range Table 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.

Integration

There is no specific integration information.

Constraints and Integrity Conditions

In a customer data migration context, you must ensure that no process can corrupt the master data been migrated. Until the end of the complete migration, make sure that:

• No business traffic acquired from mediation systems can trigger the charging services related to the customer data been migrated
• No activation process of periodic and one-off fees can be manually or automatically triggered by a user or a connected system

Do not use this process component and its included 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).