Create or Change Subscriber Accounts in Bundle Mode
Definition
To create or change subscriber accounts in bundle mode (all-or-none)
Technical Data
| Software Product and Version | SAP Convergent Charging 5.0 |
| Technical Details | subscriberAccountMaintainBundle |
| Namespace | http://provisioning.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 provisioning context or in a migration context of master data related to end customers (subscriber data) of the service provider.
The operation enables you to create or change subscriber accounts in bundle mode
in SAP Convergent Charging.
The bundle mode means that you maintain several subscriber accounts at the same time but the modifications apply only
if the processing is successful for each subscriber account.
Business Partner Management
Your CRM application or another provisioning system manages master data related to the business partners and replicates data in SAP CC by maintaining some subscriber data for end customers of the service provider. Data includes: Subscriber accounts, 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
You can use the following operations to maintain subscriber accounts:
You can use the following operations to perform queries on existing subscriber accounts:
Features
This bundle operation enables you to maintain multiple subscriber accounts in bulk.
It works as a container for several single operations of type
SubscriberAccountMaintain. The
single operations are performed sequentially by the SAP CC system.
The modifications apply only if all the single operations contained in the bundle operation are successful.
If the operation fails for one subscriber account, no modification is done.
Two situations occur:
subscriberAccountMaintain
contained in the subscriberAccountMaintainBundle operation.
Note that idempotency does not apply to each of the subscriberAccountMaintain single operation contained in the subscriberAccountMaintainBundle operation
but only to the subscriberAccountMaintainBundle 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).