Technical Data
| Software Component Version |
SAP Convergent Charging 3.0 SP08
|
| Technical Details |
|
| 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 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
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:
-
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:
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 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:
- All the single operations are successful. The result of the operation is a list of successful results for all the operations
subscriberAccountMaintain
contained in the subscriberAccountMaintainBundle 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 subscriberAccountMaintain single operation contained in the subscriberAccountMaintainBundle operation
but only to the subscriberAccountMaintainBundle bundle operation itself.
Main Use Cases:
- You want to maintain subscriber accounts in bundle mode with a Customer Relationship Management (CRM) application
- During a migration, you want to import subscriber accounts in bulk from another system (previous versions of SAP Convergent Charging or other systems)
to SAP Convergent Charging
Error Handling
Consider the error handling information specified for the bundle operations.
Refer to the information about error handling in the subscriber account business object and in the SubscriberAccountMaintain 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.
|