Import Data in CSV Format into a Subscriber Range Table

Service Operation (WS)

Definition

To import data in CSV format into a subscriber range table.

Technical Data

Software Product and Version	SAP Convergent Charging 2025
Technical Details	rangeTableDataCSVImport
Namespace	http://subscriberrangetable.v3.ws.highdeal.com/
Proxy Instance in SAP CC System	Updater
Service Operation Version	3
User Operation Auditing	Yes
Audit Domain	CATALOG
Application Area	IS-CC
Direction	inbound
Mode	synchronous
Idempotency	false

Business Context and Use

This service operation is used in the provisioning context, by a Customer Relationship Management (CRM) application or another external provisioning system. This operation is used to import CSV-formatted data into a subscriber range table, and can optionally create this table automatically. By default, the system merges the range sets specified in the operation request with the ones already defined in the subscriber range table.

Note

This service operation is available in SAP CC 2025, but only as of FPS 1.

Business Partner Management

Your CRM application or another provisioning system manages master data related to the business partners and replicates data in SAP CC by maintaining some subscriber data for end customers of the service provider. Data includes: Subscriber accounts, subscriber mapping tables, subscriber range tables.

Order Capture and Contract Management

A CRM application or another provisioning system manages master data related to the order capture and contract management and replicates data in SAP CC by maintaining subscriber data for end customers. Data includes: Charging contracts (provider contracts), subscriber mapping tables, subscriber range tables.

Related Operations

You can use the following operation to export the data of a subscriber range table:

Export data from a subscriber range table to CSV format

You can use the following operation to find subscriber range tables based on specified criteria:

Find subscriber range tables

Features

This service operation imports CSV-formatted data into a subscriber range table.

To import data, you must provide the identifier of the existing subscriber range table, and the CSV string containing that data.

The CSV format can be customized by specifying the field separator and the number format (decimal separator and thousand separator).

Two import modes are available (see the csvImportMode element):

Merge (default):

The merge mode lets you update an existing subscriber range table:
- Either by updating the range sets already defined in the table with those specified in the operation request
- Or by adding the range sets specified in the operation request to the table if they are not already defined in the table.
The merge mode operates only at the range set level. You can import any number of range sets, each with its own period, while preserving other range sets not specified in your operation request.

A range set is defined by its input values. It consists of at least one range with a unique combination of input values.
In merge mode, each range set specified in the operation request:
- Is inserted into the subscriber range table for the specified chronology of contiguous periods. If any part of that period overlaps with an existing definition for the same range set, then only the overlapping portion is updated with new data. The overlapping portion may be split into multiple periods to match existing periods in the subscriber range table's chronology. The rest of the previous definition remains unchanged.
- Is considered separately. If more than one range set applies to the same period, then they coexist within that period but do not affect each other.
Important

When using the merge mode, the system manages dates as follows:
- For every range set specified in the operation request, the system records the exact periods (the final one in chronological order does not have an end date and therefore continues indefinitely). If a previous chronology exists for the same range set, its entire end is overwritten by the new input: only those portions strictly earlier than the newly imported periods are retained, meaning the first overwritten period may be divided if there is no exact date match. To overwrite a specific time slot while keeping subsequent data intact, it is necessary to re-specify these later periods explicitly (for the same range set).
- If the periods of your range set revisions don't match exactly, then all their dates are preserved in the resulting chronology. This results in forming shorter time slots, causing the periods to be split to align with these changes. As a result, some revisions may be distributed over several consecutive slots, although they continue to contain identical information and cover precisely the requested period. This enables the system to create revisions sharing matching start and end dates.
  
  Updating a subscriber range table multiple times with different period definitions can lead to an accumulation of dates, resulting in brief periods with the same data. To reorganize or combine fragmented periods, you can use the rangeTableRangeSetMaintain or rangeTableRangeSetCancel operation.
At the end of the process, the whole chronology is broken down so that a distinct period begins for every start date that was ever imported into the table (which may repeat the same data on consecutive periods).
ClearAndReplace:

With this import mode, the system clears all existing data from the subscriber range table and replaces it with the data specified in the operation request.

Caution

After an import has been completed using the clear and replace mode, the previous data of the subscriber range table is permanently deleted.

Option: Creation of the Subscriber Range Table

An optional tableCreationAttributes element enables the creation of the subscriber range table if it does not exist yet (so that you do not have to make sure the table exists before the import).

When present, this element must contain the attributes of the subscriber range table to create: identifiers of its range table class and of its parent subscriber account and, optionally, a description and/or additional information.

If the subscriber range table already exists, then SAP CC completely ignores all these attributes (your SOAP envelope only needs to pass the XML validation).

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 of SAP Convergent Charging.

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.	Not applicable for this service operation
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:
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.	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.	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 of SAP CC:

Prerequisites

There is no prerequisite.

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