Change the State of Charging Contracts in Mass Mode

service operation

Definition

To change the state of charging contracts in mass mode during a customer data migration

Technical Data

Software Product and Version	SAP Convergent Charging 4.1
Technical Details	chargingContractStateChangeMass
Namespace	http://contractstate.ws.highdeal.com
Proxy Instance in SAP CC System	Updater
Service Operation Version	0
User Operation Auditing	Yes
Audit Domain	See the audit domain of the single operation
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 state of charging contracts in mass mode in SAP Convergent Charging. The mass mode means that you change the state of several charging contracts at the same time. The modifications apply for each successful single operation, even if the processing fails for one or several charging contracts. However, the state of the charging contracts for which the single operation fails are not modified.

See the description of the related business object charging contract state for more information.

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

Example

In an integrated scenario with SAP ERP of the SAP Business Suite, SAP ERP implements the necessary service operations of SAP CC to provide the migration services of master data related to end customers.

Related Service Operations

You can implement the following operations to change the state of charging contracts:

You can use the following operations to perform queries on the overall state of charging contracts:

Read the state of a charging contract

Features

This mass operation enables you to change the state of charging contracts in bulk.

The operation works as a container for several single operations of type ChargingContractStateChange. The single operations are performed sequentially. The modifications apply to the charging contracts for which the chargingContractStateChange single operation is successful, even if it failed for other charging contracts.

Note

Note that idempotency does not apply to each of the chargingContractStateChange single operation contained in the chargingContractStateChangeMass operation but only to the mass operation itself.

Response and Errors

The result of the mass operation is a list containing the results of the execution of the single operations chargingContractStateChange. It may contain successful and failed single results.

Authorization

Refer to the SAP CC Security Guide , to know the role that is expected in the SAP CC user profile of the service user specified in your request messages.

Error Handling

Consider the error handling information specified for the mass operations. Refer to the information about error handling in the charging contract state object and in the single operation.

Message Types

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

Prerequisites

Consider the prerequisites specified for the process component (Web service).

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 charging contracts been migrated before you have changed their intial state.

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 system landscape, you must configure the systems and the data (master data, business data).

Limitations

Consider the limitation information specified for the single operation.