Change the Initial State of Prepaid Accounts in Bundle Mode

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 prepaid accounts in bundle mode in SAP Convergent Charging. The bundle mode means that you change the state of several prepaid accounts at the same time but the modifications apply only if the processing is successful for each 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 )
  • 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

You can implement the following operation to change the initial state of prepaid accounts in bulk with the mass processing mode:

• Change the initial state of prepaid accounts in mass mode

• Change the initial state of a prepaid account

• Read a prepaid account

Features

This bundle operation enables you to change the state of prepaid accounts in bulk during a customer data migration.

It works as a container for several single operations of type PrepaidAccountStateChange. The single operations are performed sequentially. The modifications apply only if all the single operations contained in the bundle operation are all successful. If a single operation fails for one prepaid account, no modification is done.

Two cases occur:

• All the operations are successful. The result of the operation is a list of successful results for all the operations prepaidAccountStateChange contained in the prepaidAccountStateChangeBundle operation.
• One operation fails. The process stops immediately and the result of the operation is a list of successful results and one failed result.

Note that idempotency does not apply to each of the prepaidAccountStateChange operation contained in the prepaidAccountStateChangeBundle operation but only to the prepaidAccountStateChangeBundle operation itself.

Error Handling

Consider the error handling information specified for the bundle operations. Refer to the information about error handling related to the single operation.

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:

• prepaidAccountStateChangeBundleRequest
• prepaidAccountStateChangeBundleResponse

Prerequisites

Refer to the information valid for the single operation.

Integration

There is no specific integration information.

Constraints and Integrity Conditions

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