Transfer the State of a Charging Contract

Service Operation (WS)

Definition

To transfer the state and allowances of a charging contract

Technical Data

Software Product and Version SAP Convergent Charging 2022
Technical Details chargingContractStateTransfer
Namespace http://contractstate.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 true

Business Context and Use

This service operation is called in the provisioning context, by a Customer Relationship Management (CRM) application or another external provisioning system. This operation transfers the state and allowances of a source charging contract to a target charging contract in an SAP Convergent Charging system.

Related Service Operations

You can use the following operations to manage charging contracts:

You can use the following operations to perform queries on existing charging contracts.

Features

This service operation transfers the state and allowances of a source charging contract to a target charging contract in a SAP Convergent Charging system. You specify the source charging contract, the target charging contract and the list of mappings between the source charging contract items and the target charging contract items as input of the operation.

The transfer operation considers the following rules:

  • To transfer the charging contract state of a particular contract item, ensure that the source and target contract items use the same plan.
  • To transfer a particular contract counter, ensure that the source and target contract use the same counter sharing and namespace.
  • To transfer a particular allowance, ensure that the parent contract item is also transferred.

During the operation, counters are copied from the source contract to the target contract when possible. The other existing counters of the target contract are not modified. Active allowances are moved from the source contract to the target contract.

Note that:

  • the operation does not provide the list of allowances, counters or contract items which are not transferred
  • the expired allowances and shared allowances will not be transferred
  • the transfer operation, like other provisioning operations, is not considered by the rerating process

Consult the technical details for more information about this service operation.

To avoid inconsistencies, ensure that:

  • the source contract is activated until the transfer date
  • the target and source contracts are locked

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:

Next follows a non-exhaustive list of errors related to the Does Not Exist category:

  • The source or target charging contract does not exist in customer master data stored in SAP CC
  • A source or target charging contract item does not exist in its corresponding charging contract

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:

  • The source and target charging contracts are the same
  • No account could be assigned to an allowance in the target charging contract

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.

Next follows a non-exhaustive list of errors related to the Prerequisite Missing category:

  • The source or target charging contract is not root or defines pooled counters
  • The source or target charging contract operational status is not set to "locked"
  • A source or target charging contract item is mapped more than once
  • A source and target charging contract item cannot be mapped because their Charge Plan differ

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.

Note

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

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 :

Prerequisites

Consider the prerequisites specified for the process component (Web service).

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