SAP DOCUMENTATION

Change the Initial State of a Prepaid Account

service operation

Definition

To change the initial state of a prepaid account in a subscriber account during a customer data migration

Technical Data

Software Component Version	SAP Convergent Charging 3.0 SP08
Technical Details	prepaidAccountStateChangeRequest prepaidAccountStateChangeResponse
Namespace	http://prepaidaccountstate.ws.highdeal.com/
Application Area	IS-CC
Direction	inbound
Mode	synchronous
Idempotency	true

Business Context and Use

This service operation is used in a migration context of master data related to end customers (subscriber data) of the service provider. The operation enables you to change the initial state of a prepaid account in a subscriber account and stored in SAP Convergent Charging.

Note

Consider the bulk operations in bundle processing mode and in mass processing mode.

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

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 initial state of this master data. Make sure that no activation process of periodic or one-off fees can be manually or automatically triggered by a user or a connected system.

Related Service Operations

You can implement the following operations to change the initial state of prepaid accounts in bulk:

You can use the following operations to perform queries on existing prepaid accounts:

Read a prepaid account

Features

This service operation enables you to change the initial state of a prepaid account during a customer data migration.

Error Handling

The following is a non-exhaustive list of errors:

The prepaid account does not exist
A required field is missing such as the identifier of the prepaid account or the identifier of the related subscriber account

Refer to the information about error handling in the prepaid account business object.

The SAP CC system may return an error stack that details the issue.

Message Types

Consult the structures of the message types related to this operation:

Prerequisites

The prepaid account must exist in the subscriber account specified.

Integration

There is no specific integration information.

Constraints and Integrity Conditions

Consider the constraints and integrity conditions specified for the process component (Web service).

Caution

Make sure that no process can corrupt the prepaid accounts an subscriber accounts been migrated before you have changed their intial state.