Create or Change Charging Contracts in Mass Mode
Definition
To create or change charging contracts in mass mode
Technical Data
| Software Product and Version | SAP Convergent Charging 2020 |
| Technical Details | chargingContractMaintainMass |
| 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 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.
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 SAP Solution 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 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 Note The modification fails for the charging contracts with an operational status set to locked or closed.
The final result of the operation is a list containing the results of the operations Note
Idempotency does not apply to each of the chargingContractMaintain operation is successful,
even if it failed for other charging contracts.
Operation Result
chargingContractMaintain. It may contain successful and
failed results.
chargingContractMaintain operation contained in the sequence
but only to the chargingContractMaintainMass operation itself.
Authorizations
To know the role that is expected in the user profile of the SAP CC user specified in your request messages, refer to the SAP CC Security Guide .
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.
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 SAP system landscape, you must configure the systems and the data (master data, business data).