Charge a Set of Chargeable Items in Mass Mode (offline charging using the MOST mode)

service operation

Definition

To charge a set of chargeable items in mass mode (offline charging using the MOST mode)

Technical Data

Software Product and Version	SAP Convergent Charging 4.1
Technical Details	chargeableItemChargeMass
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 mass mode (offline charging using the MOST mode).

Charging

The acquisition process of SAP Convergent Charging acquires chargeable items from a mediation system and records them into a data storage such as the BART database, SAP Convergent Invoicing (SAP CI) in the SAP ERP system, or a third-party system.

The charging process rates (dynamic pricing) and charges received chargeable items representing customer service usages by calculating their monetary amounts, and identifies 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 process generates data 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. In an integrated SAP Solution with SAP ERP/FI-CA in SAP Business Suite, SAP CC can post billable items and consumption items to SAP CI.

Related Service Operations

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

Features

This mass service operation contains a set of charging operations which are all executed sequentially by the connected SAP CC system, regardless of whether they succeed or fail.

If one of the included operations fails, the modifications performed by the operation are cancelled, but the modifications performed by previous successful operations are kept.

The result of the mass operation contains a result for each included operation.

The context can be specified either in the mass operation or in the included charging operations. The context specified in the mass operation is used for all the included operations, except for the operations specifying a different context.

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)

Authorization

Refer to the SAP CC Security Guide , to know the role that is expected in the SAP CC user profile of the service user specified in your request messages.

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 does not prevent 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 system landscape, you must configure the systems and the data (master data, business data).

Additional Information

Consult the SAP CC Application Help for more information about the charging process in batch mode.
Consult the SAP CC Java API Reference (Core) for more information about the offline charging services and the batch charge operation in the com.highdeal.cnd.message Java package.