Create or Change Charging Contracts in Bundle Mode
Definition
To create or change charging contracts in bundle mode (all-or-none)
Technical Data
| Software Product and Version | SAP Convergent Charging 4.1 |
| Technical Details | chargingContractMaintainBundle |
| Namespace | http://provisioning.v2.ws.highdeal.com |
| Proxy Instance in SAP CC System | Updater |
| Service Operation Version | 2 |
| 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 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 all charging contracts.
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: Charging contracts (provider contracts) , subscriber mapping tables , subscriber range 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 , 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 accounts in bundle mode or in mass mode
- Create the necessary external accounts in bundle mode or in mass mode
- Create the necessary prepaid accounts in bundle mode or in mass mode
- Change the state of the prepaid accounts in bundle mode or in mass mode
- Change the schedule of the blocked/locked/closed statuses of each relevant prepaid account
- 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 )
- Solution 2: You must implement the one step provisioning of this converted data to SAP CC according to the following sequence:
- Switch off the business traffic to SAP Convergent Charging
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
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
Two cases occur:
ChargingContractMaintain operations are performed sequentially.
In bundle mode, the remote SAP CC system starts processing the single operations, stops at the first 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 charging contract, no modification is done.
chargingContractMaintain
contained in the chargingContractMaintainBundle operation.
Note
The operation fails if one of the charging contracts to be modified has an operational status set to locked or closed.
Note that idempotency does not apply to each of the chargingContractMaintain single operation contained in the chargingContractMaintainBundle operation
but only to the chargingContractMaintainBundle operation itself.
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
Message Types
Consult the structures of the message types related to this service operation:
Prerequisites
There is no prerequisite.
Integration
There is no specific integration information.
Constraints and Integrity Conditions
Notes on SAP CC Implementation
You must have installed and configured the SAP CC Core Server system.