Activate Charging Contracts in Bulk

Service Operation (WS)

Definition

To activate a set of charging contracts in bulk according to a reference date

Technical Data

Software Product and Version	SAP Convergent Charging 2020
Technical Details	chargingContractBulkActivate
Namespace	http://rating.ws.highdeal.com/
Proxy Instance in SAP CC System	Updater
Service Operation Version	0
User Operation Auditing	Yes
Audit Domain	CUSTOMER
Application Area	IS-CC
Direction	inbound
Mode	synchronous
Idempotency	false

Business Context and Use

This service operation enables to trigger the recurring and one-shot charges related to a set of charging contracts (see charging contracts). You implement this operation in an external billing system to prepare the invoicing and billing processes. This operation ensures that all periodic fees anterior to a reference date are computed by the SAP CC system before launching the creation of invoices.

Related Service Operations

• Activate subscriptions in bulk
• Read the status of a job

Features

This service operation processes all the charging contracts according to a filter: Only the recurring and one-shot charges of the charging contracts which match this filter are triggered. This limits the scope of the activation and optimize the processing time.

If no reference date is specified, the operation cannot be executed.

Performance Management

A maximum throughput can also be provided. It represents the maximum number of charging contracts which can be activated per second and per rater instance of the SAP CC system.

Job Management

This operation creates a job in the SAP CC system which immediately triggers the bulk activation of a set of charging contracts. The identifier of this job is returned and can be used to retrieve the status of the job and handle errors: Refer to the Read the status of a job operation.

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 fail.
Does Not Exist	The data to be modified or deleted does not exist in the connected SAP CC system.	Applicable for this service operation:
Invalid	The request or the data is invalid.	Applicable for this service operation:
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 temporary 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 the Illegal State category. The state of a data is temporary 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.

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 :

• chargingContractBulkActivateRequest
• chargingContractBulkActivateResponse

Prerequisites

The pricing modeling of the pricing policy is based on periodic fees or refills. The items of the charging contracts relate to charges and to the refill logic (configured in the pricing catalog of the service provider) that define recurring or one-shot events.

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