Read the Status of a Recharging Process Preparation Operation
Definition
To read the status of a recharging process preparation operation
Technical Data
| Software Product and Version | SAP Convergent Charging 2025 |
| Technical Details | rechargingProcessPrepareStatusRead |
| Namespace | http://recharging.v2.ws.highdeal.com/ |
| Proxy Instance in SAP CC System | Dispatcher |
| Service Operation Version | 2 |
| Application Area | IS-CC |
| Direction | inbound |
| Mode | synchronous |
| Idempotency | false |
Business Context and Use
It is the version 2 of the Web Service (WS) operation. It replaces the former versions.
Important
This is the latest version of this service operation. It replaces the previous versions: version 1 and version 0.
With the version 1, decimal numbers are no longer restricted to the (28,6) precision.
For decimal numbers stored in the database, the precision is limited to the precision supported by the database.
With this version 2, the scope of the recharging is extended to support the charging contracts that belong to a sharing group and that use shared allowances.
Rerating Scenario
A correction step precedes the recharging step of the rerating scenario. This step performs corrections when errors leading to the computation of wrong prices are identified. For example, such errors are related to the pricing logic, the properties of chargeable items, and so on.
The recharging step of the rerating scenario consists in sending again chargeable items which were previously charged so that SAP Convergent Charging (SAP CC) computes the correct prices after the correction step.
You can implement the following customizing sequence of operations for the recharging step if you want to provide rerating services in your SAP CC system landscape:
- Find the charging contracts that must be recharged together
- Lock the related charging contracts
- Find information on the feasibility of the recharging for a charging contract at a given date/time
- Prepare the execution of the recharging process
- Find the restoration points for the related charging contracts
- Restore the related charging contracts at a date corresponding to one of their restoration points
- Recharge the related chargeable items
- Unlock the related charging contracts
The recharging step may be followed by:
- An activation step, in order to trigger again recurring charges which have been undone during the recharging step. See the Activate charging contracts in bulk operation.
- A re-invoicing step in the connected billing system such as SAP Convergent Invoicing
Rerating Scenario for Contracts Using Shared Allowances Within a Sharing Group
As of the version 2 of the Recharging web service, the WS operations are enhanced to support the recharging step for charging contracts that use shared allowances within a sharing group. This version provides you with this new scenario of rerating to implement in your SAP CC system landscape.
To be able to rerate all the charging contracts that belong to the same sharing group and that use shared allowances created by the contributor contract, you implement the following operations:
- Find the charging contracts belonging to a given sharing group and that must be recharged together as dependent charging contracts
- Lock the related charging contracts belonging to the sharing group
- Find information on the feasibility of the recharging for charging contracts belonging to the sharing group at a given date/time
- Prepare the execution of the recharging process by purging the remaining item files
- Find the restoration points for all the related charging contracts belonging to the sharing group
- Check the reversibility of the billable items (BITs) related to all the charging contracts to rerate (belonging to the sharing group)
- Restore the related charging contracts at a common date/time corresponding to one of their restoration points
- Reverse the BITs related to all the charging contracts to rerate (belonging to the sharing group)
- Retrieve all consumption items issued from the charging contracts belonging to the sharing group
- Recharge all the collected consumption items ordered by ascending dates/times (oldest to newest) to ensure consistency in counter values
- Unlock all the related charging contracts belonging to the sharing group
The operations for checking the reversibility of BITs and for reversing BITs are not part of SAP CC Web Services.
Important
Refer to the SAP CC Application Help for more information about the rerating feature, its detailed process, and technical functions/mechanisms. Consult the counter snapshot management (storage, creation, and triggering within a sharing group) feature.
Review the prerequisites, conditions of use, limitations, and recommendations for implementing this rerating scenario for contracts that use shared allowances within a sharing group.
Rerating is not possible for charging contracts using shared allowances outside of any sharing group.
When consumption items to recharge are not ordered by ascending consumption dates/times (oldest to newest), the processing may lead to inconsistencies in counter values.
Related Service Operations
Features
init, running, success, or inError)
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 of SAP Convergent Charging.
Error Handling
The SAP CC system may return a charging error classified into a category and an error stack detailing the issue and its cause.
Categories
Use the following error categories to customize the behavior of your application or system:
| Prerequisite Missing | The master data required for the execution of the operation request is missing, or the request is incorrect and does not target the correct master data. |
Applicable for this service operation: Next follows a non-exhaustive list of errors linked to the Prerequisite Missing category:
|
| Invalid | The parameters of the request are not valid. The request must be corrected before sending it again. |
Applicable for this service operation: Next follows a non-exhaustive list of errors linked to the Invalid category:
|
| Invalid Configuration | The configuration of the SAP CC system is not valid. It must be corrected before sending the request again. |
Applicable for this service operation |
| Illegal State | The master data used by the operation is not in a valid state. This is usually a normal behavior of the process and should be acknowledged as a failure. |
Applicable for this service operation |
| Temporary Illegal System State | The connected SAP CC system is currently not in an appropriate state to execute the operation request. The request can usually be sent again later without any modification. If the error persists, the system administrators must be informed about it. |
Applicable for this service operation |
| Illegal System State | The operation request failed because of a technical error or an unexpected issue. The system administrators must be informed about this error. |
Applicable for this service operation |
Note
This list of errors is not exhaustive.
Troubleshooting
Refer to the SAP CC Error Code Reference 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 of SAP CC:
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).