Charge a Set of Chargeable Items in Bundle Mode (offline charging using the ALL mode)

Service Operation (WS)

Definition

To charge a set of chargeable items in bundle mode (offline charging using the ALL mode)

Technical Data

Software Product and Version	SAP Convergent Charging 5.0
Technical Details	chargeableItemChargeBundle
Namespace	http://charging.ws.highdeal.com/
Proxy Instance in SAP CC System	Dispatcher
Service Operation Version	0
Application Area	IS-CC
Direction	inbound
Mode	synchronous
Idempotency	false

Business Context and Use

This service operation is used to charge a set of chargeable items in bundle mode (offline charging using the ALL mode).

Charging

The Charging process rates (dynamic pricing) and charges received chargeable items representing customer service usages by calculating their monetary amounts, and by identifying the accounts to charge for the service consumption and other fees. Depending on the type of the charging operation request, the monetary amount is either debited from the account or simply reserved for authorization.

The charging operations generate multiple data files (aka item files) for billing or invoicing purposes that the bulk loading process of SAP Convergent Charging can transfer to third-party systems such as billing or invoicing systems. For example, in an integrated SAP Solution scenario with SAP ERP in SAP Business Suite or S/4HANA, SAP CC posts billable items and consumption items to SAP Convergent Invoicing (SAP CI). Refer to the integration guides.

Consult the SAP Application Help for more information and user assistance.

Related Service Operations

You can also use the following operations for charging chargeable items:

Features

This service operation contains a set of charging operations which are executed sequentially by the connected SAP CC system until all operations have been executed successfully or an operation fails. The charging operations must target the same charging contract.

If all the included charging operations are successful, the modifications performed by these operations are applied, and the result of the bundle operation contains a result for each charging operation.

If one of the included operations fails or targets a different charging contract, the modifications performed by the already executed operations are cancelled, and the result of the bundle operations contains a single error result for the failed operation.

The context of the bundle operation defines the behavior of all the included operations. The context of each included operation cannot be redefined.

Result Configuration

You can specify if the result of each included operation includes:

Information about the charging process
Information about the identified target charging contract
Information about the charged chargeable item
Information about the generated accounting operation(s)
Information about the charged account(s)
Information about the generated charged item(s)
Information about the generated business notification(s)
Information about the errors

The list of possible options is the following:

Sender Information (see senderInfo)
- jobId: specifies an identifier for the sender of the operation
Charging Operation Output (see chargingOutputContext)
- chargeableItemExported: specifies if the rater instances of the SAP CC system must store the chargeable items into data files
Operation Result (see 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
Operation Result on Errors (see chargingResultOnErrorContext)
- notificationReturned: specifies if the notifications generated when an error occurs must be returned in the result of each included operation (for example, the notifications generated by the no access component)

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

If the execution of an included operation fails, the bundle result will contain a single result which contains information about the error.

The failure of an included operation prevents 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 :

Prerequisites

The prerequisites of each included operation must be fulfilled.

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