Create or Change a Prepaid Account
Definition
To create or change a prepaid account in a subscriber account
Technical Data
| Software Product and Version | SAP Convergent Charging 5.0 |
| Technical Details | prepaidAccountMaintain |
| Namespace | http://provisioning.ws.highdeal.com/ |
| Proxy Instance in SAP CC System | Updater |
| Service Operation Version | 1 |
| User Operation Auditing | Yes |
| Audit Domain | CUSTOMER |
| Application Area | IS-CC |
| Direction | inbound |
| Mode | synchronous |
| Idempotency | true |
Business Context and Use
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 accounts.
Related Service Operations
You can use the following operations to perform actions on prepaid accounts:
You can use the following operations to perform queries on existing prepaid accounts:
Features
This operation maintains a prepaid account in a subscriber account.
The prepaid account is identified by a pair composed of its ID and the ID of the related subscriber account.
Two cases occur:
If the prepaid account does not exist then it is created.
If the prepaid account already exists then it is modified.
In the both cases, you are not allowed to use the following items of the prepaid account:
- The
balance - The
currentState
In the second case, you are not allowed to modify the following items of the prepaid account:
- The
currencyCode - The
stateSchedule
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
The SAP CC system may return an error classified into a category and an error stack detailing the issue and its cause.
Categories and Treatments to Implement
Consider the following error categories to design and implement the appropriate behavior of your connected application or system:
| Error Category | Description | Error Handling |
| Already Exists | The data has to be created but another data already exists in the connected SAP CC system with the same type and the same identifier. |
Applicable for this service operation: You implement the logging of this error to enable a system administrator or a consultant to investigate and resolve the issue. Data replication or data synchronization mechanisms may failed. Next follows a non-exhaustive list of errors related to the Already Exists category:
|
| Does Not Exist | The data to be modified or deleted does not exist in the connected SAP CC system. |
Applicable for this service operation: Next follows a non-exhaustive list of errors related to the Does Not Exist category:
|
| Invalid | The request or the data is invalid. |
Applicable for this service operation: Next follows a non-exhaustive list of errors related to the Invalid category:
|
| Incompatible Configuration | The configuration of the connected SAP CC system is not compatible with the data specified in the operation request and the scope of the request. Creating or correcting the prerequisite configuration data (master data, business data) has to be done in the SAP CC system with the Core Tool user interface or within your connected application or system. |
Applicable for this service operation: |
| Prerequisite Missing | Another data mandatory for the operation is not available or is not compatible with the data specified in the operation request. Create a prerequisite for the data. |
Applicable for this service operation: The prerequisite data is managed outside the SAP CC system. |
| Illegal State | The operation request is valid but was rejected because of the current state of the data in the connected SAP CC system which prevents the execution of the request. The current state of the complete system can be also the origin of the error. |
Applicable for this service operation: The request will not succeed without a required manual correction or change in the SAP CC system. You implement error logging and manual retry mechanisms. |
| Temporary Illegal State | The valid request was rejected because of the temporarilly illegal state of the data in the connected SAP CC system. The data state may automatically change without any further notification. This is a subcategory of Illegal State category. The state of a data is temporarilly illegal but the operation request can be sent again after a waiting period. The current state of the complete system can be also the origin of the error. |
Applicable for this service operation: You can implement an automated resend function. |
Note
This list of errors is not exhaustive: consider the technical details of the operation response.
Troubleshooting
Refer to the SAP CC Error Code Reference ( SAP Site ) for more information about a returned error code and the corrective actions necessary for troubleshooting your implementation project.
Message Types
Consult the structures of the message types related to this service operation :
Prerequisites
Integration
There is no specific integration information.
Constraints and Integrity Conditions
There is no specific constraint.
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).