Lock a Charging Contract Collection

Service Operation (WS)

Definition

To lock a charging contract collection

Technical Data

Software Product and Version SAP Convergent Charging 5.0
Technical Details chargingContractCollectionLock
Namespace http://recharging.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 lock a charging contract collection in the context of a recharging operation to prevent the charging contracts from being used by another business process until they are unlocked.

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 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 system landscape:

The recharging step may be followed by:

Related Service Operations

You can also use the following operations for locking or unlocking charging contract collections:

Features

Repeated invocations of this operation with the same charging contract collection and recharging lock identifier have no effect.

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 a charging error classified into a category and an error stack detailing the issue and its cause.

Categories

Use the following error categories to customize the behavior of your application or system:

Prerequisite Missing The master data required for the execution of the operation request is missing, or the request is incorrect and does not target the correct master data.

Applicable for this service operation: Next follows a non-exhaustive list of errors linked to the Prerequisite Missing category:

  • The subscriber account specified does not exist
  • The subscriber account specified does not have associated charging contracts
  • At least one of the charging contracts specified does not exist
  • At least one of the charging contracts specified does not belong to the subscriber account specified

Invalid The parameters of the request are not valid. The request must be corrected before sending it again.

Applicable for this service operation: Next follows a non-exhaustive list of errors linked to the Invalid category:

  • No subscriber account identifier was specified in the request
  • The recharging lock ID is missing or invalid

Invalid Configuration The configuration of the SAP CC system is not valid. It must be corrected before sending the request again.

Applicable for this service operation: Next follows a non-exhaustive list of errors linked to the Invalid Configuration category:

  • The recharging feature is deactivated

Illegal State The master data used by the operation is not in a valid state. This is usually a normal behavior of the process and should be acknowledged as a failure.

Applicable for this service operation: Next follows a non-exhaustive list of errors linked to the Illegal State category:

  • At least one charging contract in the collection is already locked by another recharging operation

Temporary Illegal System State The connected SAP CC system is currently not in an appropriate state to execute the operation request. The request can usually be sent again later without any modification. If the error persists, the system administrators must be informed about it.

Applicable for this service operation

Illegal System State The operation request failed because of a technical error or an unexpected issue. The system administrators must be informed about this error.

Applicable for this service operation

Note

This list of errors is not exhaustive.

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

  • The relevant subscriber account exists
  • The relevant charging contracts exist
  • The relevant charging contracts belong to the subscriber account
  • The relevant charging contracts are not locked by another recharging operation

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