Customer Data Import

Service Operation (WS)

Definition

To import customer data

Technical Data

Software Product and Version	SAP Convergent Charging 5.0
Technical Details	customerDataImport
Namespace	http://customerdata.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 enables to import customer data in an SAP CC system. It is used in the following contexts:

• Move or copy customer data from one SAP CC system to another. It is used in conjunction with the export operation to import customer data previously exported from another SAP CC system.
• Provision customer data with a Customer Relationship Management (CRM) application or another external provisioning system.

Related Service Operations

• Customer data export: This operation enables you to export customer data. The customer data resulting from this operation can be used without being modified to be imported with the import operation.
• Operational status change: This operation enables to update the status of the contracts that have been imported with the import operation. By default, the operational status of the contracts that have been imported is set to 'locked', meaning that the contracts cannot be used. You have to set the operational status of the contracts to 'active' so that they can be used in the SAP CC destination system.

Features

This operation takes a customerData object containing data to be imported into an SAP CC system as an argument. You can import one or several objects. The customerData object contains the following customer data:

• Subscriber accounts
• External accounts
• Prepaid accounts
• Subscriber mapping tables
• Subscriber range tables
• Charging contracts (including their states and their allowances)

Import management when data already exist

If one of the objects contained in the customer data already exists in the SAP CC destination system, the import operation does not overwrite it. The import operation is rejected and no object is imported by default.

There are the two following exceptions to this behavior:

• The charging contracts with an operational status set to 'closed'.
  It is possible to import a charging contract whose operational status is set to 'closed' in the destination system. You can also import its linked contracts in the same import request. The existing closed contract and its linked contracts are deleted. New charging contracts are created by using the contracts given in the import operation.

  Note

  You are not allowed to import a linked charging contract which already exists in the destination system without its parent contract, even if the parent contract has an operational status set to 'closed'.

• The subscriber mapping tables and the subscriber range tables when the parameter onAlreadyExistingTable is set to 'overwrite'.
  You can use the parameter onAlreadyExistingTable to overwrite a subscriber table that already exists and belongs to the same subscriber account in the destination system. Set this parameter to 'overwrite' if you want to replace existing tables in the destination system. Otherwise, the parameter is set to 'rejectImport' and the import is rejected.

  Note

  However, you cannot import a subscriber table belonging to a subscriber account different from that of the import request. In this case, perform the following modifications:

  • Generate a new ID for the subscriber table.
  • Update the import request with the new ID. Do not forget to update the contract parameters referring to the subscriber table.

Operational status of the imported charging contracts

By default, the operational status of all the imported charging contracts is set to "locked" in the SAP CC destination system. However, it is possible to override this value by providing a specific operational status for all the charging contracts to be imported. Do not provide the value 'closed' for this specific status because the operation will be rejected.

Balance of the imported prepaid accounts

The balance of the prepaid accounts imported with this operation is set to zero. The value of the balance is not copied into the destination system. To update a balance in the destination system after importing a prepaid account, perform a refill operation or a balance transfer with SAP ERP.

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. Next follows a non-exhaustive list of errors related to the Already Exists category: The subscriber account to be imported already exists in the SAP CC destination system The external account to be imported already exists in the SAP CC destination system The prepaid account to be imported already exists in the SAP CC destination system The subscriber mapping table to be imported already exists in the SAP CC destination system The subscriber range table to be imported already exists in the SAP CC destination system The charging contract to be imported already exists in the SAP CC destination system
Does Not Exist	The data to be modified or deleted does not exist in the connected SAP CC system.	Not 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: The chargingContractOperationalStatusChangedTo cannot be set to "closed". Only "active" or "locked" are allowed in the import request The external account is duplicated in the import request The prepaid account is duplicated in the import request The subscriber mapping table is duplicated in the import request The subscriber mapping table belongs to another subscriber account in the SAP CC destination system The subscriber range table is duplicated in the import request The subscriber range table belongs to another subscriber account in the SAP CC destination system The charging contract is duplicated in the import request The allowance is duplicated in the import request
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.	Not 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.	Not applicable for this service operation
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.	Not applicable for this service operation
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.	Not applicable for this service operation

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 :

• customerDataImportRequest
• customerDataImportResponse

Prerequisites

• You have identified the customer data to be imported.
• You have built a valid customerData object containing the customer data to be imported.

  Note

  The result of the export operation is a valid customerData object. If you have used the export operation, you can directly reuse this file.

• You have checked the constraints and integrity conditions described below.

Integration

If you implement the contract transfer feature:

• Use customer data previously exported with the export operation.
• In an integrated scenario with SAP ERP and SAP CRM, import customer data containing only charging contracts and subscriber tables. Subscriber accounts are created in the destination system by SAP ERP without using SAP CC Web Services.

Constraints and Integrity Conditions

Constraints on the customer data

• You are allowed to import a customerData that is empty.
• You are allowed to import one and only one customerData object by import operation.
• If you import several objects with the same import operation, all the objects must belong to the same subscriber account.
• If the customerData object to be imported contains a subscriber account id, all the other objects in the customerData must belong to this subscriber account.

Constraints on the SAP CC destination system

Check that the customer data to be imported is consistent with the data in the SAP CC destination system.

• If the subscriber account is not specified in the request, the subscriber account referenced by the objects to be imported must already exist in the SAP CC destination system.
• If you import a linked contract without its parent contract, the parent contract must exist and have an operational status set to 'active' in the SAP CC destination system.

  Note

  A linked contract refers to the same subscriber account as its parent contract. If other objects are imported at the same time, they must refer to the same subscriber account as the linked and parent contracts.

• If you import a charging contract without a subscriber account and without subscriber tables, you must check that the subscriber tables used in this contract exist in the destination system.

Check that the SAP CC destination system has the same configuration as the SAP CC source system. The following configurations must be similar in the two systems:

• The list of currencies because they can be used in charging contract parameters
• The mapping table classes and the range table classes to import subscriber tables
• The tax configuration
• The plans: charge plans, refill plans, allowance plans and monitoring plans

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