Technical Data
| Software Component Version |
SAP Convergent Charging 3.0 SP08
|
| Technical Details |
|
| Namespace |
http://prepaidaccountstate.ws.highdeal.com/ |
| Application Area |
IS-CC |
| Direction |
inbound |
| Mode |
synchronous |
|
Idempotency
|
true |
Business Context and Use
This service operation is used in a migration context of master data related to end customers (subscriber data) of the service provider.
The operation enables you to change the state of prepaid accounts in mass mode
in SAP Convergent Charging.
The mass mode means that you maintain the state of several prepaid accounts at the same time.
The modifications apply for each successful operation,
even if the operation fails for one or several prepaid accounts. However, the state of prepaid accounts for which the operation fails is not modified.
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 implement the following operation to change the initial state of prepaid accounts in bulk with the bundle processing mode:
You can use the following operation to change the initial state of a prepaid account in a subscriber account:
You can use the following operations to perform queries on existing prepaid accounts:
Features
This mass operation enables you to change the initial state of prepaid accounts in bulk.
The operation works as a container for several single operations of type
PrepaidAccountStateChange. The
PrepaidAccountStateChange single operations are performed sequentially.
The modifications apply to the prepaid accounts for which the single operation is successful,
even if it failed for other prepaid accounts.
The result of the operation is a list containing the results of the operations prepaidAccountStateChange. It may contain successful and
and failed results.
Note that idempotency does not apply to each of the prepaidAccountStateChange single operation contained in the prepaidAccountStateChangeMass operation
but only to the prepaidAccountStateChangeMass mass operation itself.
Main Use Case:
- During a migration, after you have created the prepaid accounts to be migrated in SAP Convergent Charging, you want to update their state in bulk.
Error Handling
Consider the error handling information specified for the mass operations.
Refer to the information about error handling in the PrepaidAccountStateChange 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
Refer to the information valid for the single operation.
Integration
There is no specific integration information.
Constraints and Integrity Conditions
Consider the constraints and integrity conditions specified for the process component (Web service).
|