Recharge a Set of Chargeable Items

Service Operation (WS)

Definition

To recharge a set of chargeable items

Technical Data

Software Product and Version	SAP Convergent Charging 2025
Technical Details	chargeableItemRechargeMass
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

This service operation is used to recharge a set of chargeable items in the context of a recharging operation.

It is the version 2 of the Web Service (WS) operation. It replaces the former versions.

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.

Related Service Operations

You can also use the following operations to recharge chargeable items:

• Recharge a single chargeable item

Features

This WS operation is a mass operation and contains a set of recharging operations which are executed sequentially.

In a rerating scenario involving charging contracts that use shared allowances within a sharing group, single operations are organized by consumption dates and times, second by second, and sent in parallel to the rater instances of the SAP CC system for each consumption date and time within the same second. The sharedAllowanceOptimization option is required to force this preprocessing and ensure correct computations.

The behavior of this operation can be configured by specifying a context (see context) and enabling the sharedAllowanceOptimization option.

• sharedAllowanceOptimization: This XML attribute is required in a rerating scenario involving charging contracts that use shared allowances within a sharing group to ensure correct computations. When set to true in the mass operation request, it forces the dispatcher instance to organize the single operations by consumption dates/times (up to the second). Single operations are sent sequentially by ascending consumption dates/times to the rater instances, but operations within the same second are sent in parallel.

  Note

  In your scenario, this optimization is efficient only if all the mass operations used to recharge all the consumption items, are also ordered by ascending consumption dates/times for achieving maximum consistency in counter values implemented by the shared allowances.

In the context, the possible configurations are:

• rechargingContext
  • rechargingLockId: specifies the recharging lock identifier of the recharging operation
• senderInfo
  • jobId: specifies an identifier for the sender of the operation
• chargingOutputContext
  • chargeableItemExported: specifies if chargeable items must be exported in the output of the charging operation
  • itemImmediatelyLoaded: must not be enabled for this service operation (available only for single and bundle operations)
• chargingResultContext
  • chargingProcessInfoReturned: specifies if information about the charging process must be returned in the result of each included operation
  • chargingContractInfoReturned: specifies if information about the target charging contract must be returned in the result of each included operation
  • chargeableItemInfoReturned: specifies if information about the chargeable item must be returned in the result of each included operation
  • accountOperationReturned: specifies if the generated account operations must be returned in the result of each included operation
  • accountInfoReturned: specifies if information about the impacted accounts must be returned in the result of each included operation
  • chargedItemReturned: specifies if the generated charged items must be returned in the result of each included operation
  • notificationReturned: specifies if the generated notifications must be returned in the result of each included operation
• chargingResultOnErrorContext
  • notificationReturned: when the recharging has been aborted by a No Access component, specifies if the error notification (i.e., the "No access" notification) must be returned in the result.
    Regardless of this setting, user alerts are never returned for a charging operation that has been aborted.

The context can be specified either in this operation or in the included recharging operations. The context specified in this operation is used for all the included single operations, except for the operations specifying a different local context.

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

If the execution of an included operation fails, the corresponding result will contain information about the error. The failure of an included operation fails does not stop the execution of the subsequent operations. Refer to the information about error handling related to the single operation.

Message Types

Consult the structures of the message types related to this service operation of SAP CC:

• chargeableItemRechargeMassRequest
• chargeableItemRechargeMassResponse

Prerequisites

The prerequisites of each of the included operations must be fulfilled.

This mass operation must fulfill the prerequisites for the rerating process. Refer to the SAP CC Application Help for more information about the prerequisites for the rerating process, its detailed process, and technical functions/mechanisms.

Integration

When several mass operations are called in a sequence to be able to recharge all the chargeable items/consumptions items that have been previously charged for a given period, the calls must be ordered by ascending consumption dates/times (oldest to newest). Otherwise, this can lead to inconsistencies in counter values.

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).