Change the State of a Charging Contract

Service Operation (WS)

Definition

To change the state of a charging contract during a customer data migration

Technical Data

Software Product and Version	SAP Convergent Charging 5.0
Technical Details	chargingContractStateChange
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 used in a migration context of customer master data (subscriber data) of the service provider. You use this operation to finalize the migration by changing the state of a charging contract just created and stored in SAP Convergent Charging. You can restore counters that reflect credits from a former system.

Customer Data Migration

A former system manages master data related to the end customers of a service provider. You want to migrate this data to SAP Convergent Charging.

• You must extract this information
• You must implement the conversion of this data into master data (and data models) provided and managed by SAP CC before any activity:
  • Business partners ( subscriber accounts , subscriber mapping tables , subscriber range tables )
  • Business agreements ( prepaid accounts and external accounts )
  • Contracts ( charging contracts , subscriber mapping tables , subscriber range tables )
• You must determine the states of the prepaid accounts and the states of the migrated charging contracts .

Then, you must implement the provisioning of this converted data to SAP CC by choosing one of the following solutions:

• Solution 1: You must implement bulk provisioning of this converted data to SAP CC according to the following sequence:
  • Create the necessary subscriber accounts in bundle mode or in mass mode
  • Create the necessary external accounts in bundle mode or in mass mode
  • Create the necessary prepaid accounts in bundle mode or in mass mode
  • Change the state of the prepaid accounts in bundle mode or in mass mode
  • Change the schedule of the blocked/locked/closed statuses of each relevant prepaid account
  
  
  • Create the necessary subscriber mapping tables
  • Create the necessary subscriber range tables
  
  
  • Create the necessary charging contracts in bundle mode or in mass mode
  • Change the state of the charging contracts in bundle mode or in mass mode
  • Create the necessary data tables relating to a charging contract or to a group of charging contracts ( subscriber mapping tables or subscriber range tables )
  Two different processing modes are provided for these bulk operations: The bundle mode (all-or-none) or the mass mode (most) . Determine the mode recommended for your business requirements.

• Solution 2: You must implement the one step provisioning of this converted data to SAP CC according to the following sequence:
  • Import customer data
  • Change the operational status of the imported single or parent charging contract(s) to set it to active

• Switch off the business traffic to SAP Convergent Charging

Make sure that no business traffic acquired from mediation systems can trigger the charging services related to the customer data been migrated. This can corrupt the state of this master data. Make sure that no activation process of periodic and one-off fees can be manually or automatically triggered by a user or a connected system.

Related Service Operations

You can use the following operations to change the state of charging contracts in bulk:

• Change the state of charging contracts in bundle mode
• Change the state of charging contracts in mass mode

You can use the following operations to perform queries on the overall state of charging contracts:

• Read the state of a charging contract

Features

This service operation changes the state of a charging contract been migrated. In the single operation request, you specify the state of the charging contract you want to modify.

Refer to the specifications of the charging contract state data model.

Consult the technical details for more information about this service 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 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: A counter or a charge is referenced several times in the operation request A counter or a charge does not exist
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 charging contract does not exist in customer master data stored in SAP CC
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.

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 :

• chargingContractStateChangeRequest
• chargingContractStateChangeResponse

Prerequisites

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

Integration

There is no specific integration information.

Constraints and Integrity Conditions

Consider the constraints and integrity conditions specified for the process component (Web service).

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

Limitations

Some names are reserved for internal counters in the state of the charging contract. You cannot use these names for defining counters in the chargingContractStateChange operation. Here is the list of the reserved names:

• LAST_ACTIVATION_DATE
• RR_NEXT_ID
• _LAST_SNAPSHOT_DATE
• _LAST_EXPORT_DATE
• RERATING_LOCK_CODE
• RERATING_LAST_CODE
• RERATING_LAST_STATUS
• RERATING_SUGGESTED_DATE