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.
It enables you to create or change external accounts in mass mode
in SAP Convergent Charging. The mass mode means that you maintain several external accounts at the same time. The modifications apply for each successful operation,
even if the operation fails for one or several external accounts. However, the external accounts for which the operation fails are not created or modified.
Business Agreement Management
Your CRM application or another provisioning system manages master data related to the business agreements between partners and replicates data in SAP CC by maintaining some subscriber data for end customers of the service provider.
Data includes:
Prepaid accounts and external (postpaid) accounts
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 external accounts:
You can use the following operations to perform queries on existing external accounts:
Features
The operation externalAccountMaintainMass enables you to maintain external accounts in mass mode.
It works as a container for several operations of type
ExternalAccountMaintain. The
ExternalAccountMaintain operations are performed sequentially.
The modifications apply to the external accounts for which the ExternalAccountMaintain operation is successful,
even if it failed for other external accounts.
The result of the operation is a list containing the results of the operations externalAccountMaintain. It may contain successful and
and failed results.
Note that idempotency does not apply to each of the externalAccountMaintain single operation contained in the externalAccountMaintainMass operation
but only to the externalAccountMaintainMass mass operation itself.
Main Use Cases:
- You want to maintain external accounts in mass mode with a Customer Relationship Management
- During a migration, you want to import external accounts in bulk from another system (previous versions of SAP Convergent Charging or other systems)
to Convergent Charging
Error Handling
Consider the error handling information specified for the mass operations.
Refer to the information about error handling in the subscriber account business object and in the ExternalAccountMaintain 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
The subscriber accounts containing an external account must exist.
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.
|