SAP DOCUMENTATION

Create or Change Charging Contracts in Mass Mode

service operation

Definition

To create or change charging contracts in mass mode

Technical Data

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

Business Context and Use

This service operation is used in contexts of customer data provisioning or customer data migration.

It allows you to create or change in mass mode a large volume of charging contracts stored in SAP Convergent Charging. The mass mode means that you maintain several charging contracts at the same time. The modifications apply for each successful single operation, even if the operation fails for one or several charging contracts. However, the charging contracts for which the operation fails are not created or modified.

Main Use Cases:

You want to implement the creation, replication, synchronization, or maintenance of charging contracts in mass mode from a Customer Relationship Management (CRM) application
During a customer data migration, you want to import charging contracts in bulk from another system (previous versions of SAP CC or other former systems) to a new SAP CC system

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

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 use the following operations to maintain charging contracts:

You can use the following operations to perform queries on existing charging contracts:

Find charging contracts

Features

This bulk operation allows you to maintain a large volume of charging contracts in mass mode. The operation request embeds a sequence of single operations (Create or Change a Charging Contract).

In mass mode, the remote SAP CC system processes all the single operations sequentially. The modifications apply to the charging contracts for which the chargingContractMaintain operation is successful, even if it failed for other charging contracts.

Operation Result

The final result of the operation is a list containing the results of the operations chargingContractMaintain. It may contain successful and and failed results.

Note

Idempotency does not apply to each of the chargingContractMaintain operation contained in the sequence but only to the chargingContractMaintainMass operation itself.

Error Handling

Consider the error handling information specified for the mass operations. Refer to the information about error handling in the ChargingContractMaintain 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:

Prerequisites

There is no prerequisite.

Integration

There is no specific integration information.

Constraints and Integrity Conditions

In a migration context of master data related to end customers (subscriber data) of the service provider, consider the constraints and integrity conditions specified for this context.