Launch a CDR Batch Rating and Charging Session

Service Operation (WS)

Definition

To create and launch a CDR batch rating and charging session in the connected SAP CC BART Server system in order to charge a set of CDRs already stored in the BART Database system according to the consumption date of the customer service to monetize

Technical Data

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

Business Context and Use

This service operation enables you to create and start a CDR batch rating and charging session in the SAP CC BART Server system.

You send the operation request to the SAP CC Core Server system that transmits the request to the SAP CC BART Server system dedicated to trigger the batch charging services in the Core Server system.

This service operation is a business operation reserved to the business administration in your system landscape. You implement this operation to drive the offline charging operations from your interfaced application (or system).

The identifier of the created job is returned and can be used to retrieve the status of this job (see the Read the status of a job operation).

Related Service Operations

Read the status of a job to monitor the processing of the request and to handle possible errors

Features

The following recommended modes are available to batch charge CDRs assigned to provider contracts or subscriptions:

Day Subscribtion First Fail: You specify this mode to process all the CDRs converted into chargeable items, whatever the subscription or the provider contract they are associated to. The CDRs are grouped according to the consumption date. This mode requires fewer resources than the other modes. If an error occurs in a subscription (or a provider contract), the batch charging operation stops processing the subscription (or the provider contract) and continues with the other subscriptions and contracts.
Day Most: All the CDRs are batch rated and charged even if an error occurs. BART Server then sends all the chargeable items.

Note

Other modes are available for compatibility purposes: subscription first fail, subscription most, subscription try.

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 failed.
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: Next follows a non-exhaustive list of errors related to the Invalid category: Prepaid account identifier is not specified
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 temporarilly 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 Illegal State category. The state of a data is temporarilly 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.

Note

This list of errors is not exhaustive: consider the technical details of the operation response.

You must implement the Read the status of a job operation in your client application or system to be able to handle possible errors during the processing. The behavior depends on the mode specified in the operation request: Day Subscribtion First Fail or Day Most.

Troubleshooting

Refer to the SAP CC Error Code Reference ( SAP Site ) 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 :

Prerequisites

There is no prerequisite.

Integration

There is no specific integration information.

Constraints and Integrity Conditions

For further information about the constraints related to the charging process, refer to the SAP CC Application Help available in SAP Help Portal.

Notes on SAP CC Implementation

To implement this service operation, you must have installed the SAP CC Core Server system and an SAP CC BART Server system in back end.

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

Additional Information

Consult the SAP CC Application Help for more information about the charging process in batch mode.