Create or Change Charging Contracts in Bundle Mode

Business Context and Use

This service operation is used in a provisioning context (replication in bulk) or in a migration context.

The operation enables you to create or change charging contracts in bundle mode in SAP Convergent Charging. The bundle mode means that you maintain several charging contracts at the same time but the modifications apply only if the operation is successful for each charging contract.

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

• Create or change a charging contract
• Create or change charging contracts in mass mode

• Find charging contracts

Features

This bundle operation enables you to create or change charging contracts in bulk.

The operation request embeds a sequence of single operations (Maintain Charging Contract). The single ChargingContractMaintain operations are performed sequentially. In bundle mode, the remote SAP CC system starts processing the single operations, stops at the fisrt failure and rolls back the single operations already processed. The modifications apply only if all the operations contained in the chargingContractMaintainBundle operation are successful. If the operation fails for one or several charging contracts, 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 chargingContractMaintain contained in the chargingContractMaintainBundle 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 chargingContractMaintain single operation contained in the chargingContractMaintainBundle operation but only to the chargingContractMaintainBundle bundle operation itself.

Error Handling

Refer to the information about message handling in the charging contract business object and in the ChargingContractMaintain 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:

• chargingContractMaintainBundleRequest
• chargingContractMaintainBundleResponse

Prerequisites

There is no prerequisite.

Integration

There is no specific integration information.

Constraints and Integrity Conditions

There is no specific constraint.