User Assistance for Developers

Java	WS	ERR	Notif.
Param.	Admin+	Setup Tool
Core Tool		Other UIs
Logs	Metrics

Error Code Reference

Target Audience

Development consultant
Technology consultant
Support specialist (level 3)

Getting Started

This SAP product documentation is a nonexhaustive list of the errors that can be returned to a client application sending request messages to the SAP CC Core Server system.

Your application (or system) sends service operation requests by using the different technical interfaces of SAP Convergent Charging 4.1:

Web Services (WS)
HTTP Communication Interface (HCI)
Message TCP

This user assistance is intended for troubleshooting purposes and for understanding why an operation was not executed or has failed in the SAP CC system.

View the information topic that relates to your situation and continue your investigations.

Working With Error Causes and Codes

Implementation

During the implementation project, you use this documentation when integrating the business services provided by the Web Services technical of SAP Convergent Charging. Refer to the error handling information provided with its SOAP API specifications for each service operation that you can implement in your SAP system landscape. You can view some errors translated from the HCI technical interface.

Note that you can partially use this documentation when developing your applications with the Java APIs of SAP CC for troubleshooting certain operations requested via the Message TCP technical interface.

Technical Operations

During the implementation phase or the operation phase, the errors detailed in this documentation may be visible in logs or traces of the applications and systems that connect to the SAP CC systems.

Errors

SAP Convergent Charging manages different types of errors replied in the operation responses. An error may include:

A failure category such as already exists, does not exist, invalid, prerequisite missing, incompatible configuration, illegal state, or temporary illegal state; the definitions of these categories depend on the technical interfaces and their specification. See the corresponding documentation.
A comprehensive message
An error cause
A stack of 'caused-by' information items

SAP CC handles several error patterns that are specialized to the requested service operations. The failure categories are defined in the corresponding SAP CC API specifications.

Each error cause includes:

A unique identifier composed with:
- a technical module name
- and a numerical cause code
An intelligent message completed dynamically
Suggested actions and steps for troubleshooting the issue

Caution

Errors can be deprecated at any time
Before you start the troubleshooting, make sure that you have the latest version of this document. It is available in the Software Development Kit (SDK) of SAP CC.

Examples

See the technical details that specify the responses of the 'Find Subscriber Accounts' operation provided in the Web Services technical interface and its SOAP API specification.

Error Codes

Errors are listed and grouped by technical modules. The code of an error is unique; It is composed of the name of the module followed by a number identifying the error inside the module.

Error Messages

SAP CC provides you with a comprehensive message that explains why the processing has failed in the SAP CC system or why the SAP CC system did not trigger the execution of the process

Optionally, some information such as the identifier, the name, or the code of an object managed in the SAP CC system or in its back-end database.

Note

The meaning of this error message depends on the software layers and on the internal architecture of the SAP CC systems. The error message is the internal vision of the SAP CC system.

You may have to translate the terminology to the concepts and data models of the technical interface that has transported the error. Refer to the appropriate specifications:

Next Actions and Steps (Troubleshooting)

Use this information to troubleshoot your issue with a cause analysis and a solution.

Quick Access by Modules

Select the module signaled in the error replied in the operation response by the SAP CC system:

Signaled Module	Definition
AGGREGATIONPOLICY	Errors which occur when implementing basic operations on aggregation policies.
ALLOWANCE	Errors which occur when implementing basic operations on allowances.
AUTHORIZATION	Errors which occur when implementing basic operations (such as create, modify, delete, or search) on authorizations.
CC-SEC-AUTH	Errors related to authentication, mainly describing login and password issues.
CHANGEID	Errors occurring when issues are encountered when using change identifiers.
CHANGELIST	Errors which occur when implementing basic operations on change lists.
CHARGECOMPONENT	Errors which occur when implementing basic operations on charge components (including price plans and charging plans). A charge component is a reusable charge that is added to different charge plans to design the pricing logic for several customer services.
CHARGEPLAN	Errors which occur when implementing basic operations on charge plans and charge plan items. A charge plan item represents a reusable charge customized in a charge plan.
CHARGINGPLAN	Errors which occur when the execution of a price plan or a charging plan fails during a rating or charging operation.
CICLASS	Errors which occur when implementing basic operations on chargeable item classes.
CONTRACT	Errors which occur when implementing basic operations on charging contracts (charging data of provider contracts) and contract items.
CONTRACTSTATE	Errors which occur when implementing operations dedicated to the management of the initial state of charging contracts during the migration of master data related to end customers. A charging contract is the charging data that is part of the overall provider contract. It is a partial view of this master data and is stored in SAP CC. Note Refer to the SOAP API Specifications of the SAP CC Web Services for more information about the necessary Customizing activities to implement the customer data migration.
CUSTOMERDATA	Errors which occur when exporting or importing customer data with the Web Services. Note: These errors relate to the contract transfer feature in case this feature is implemented on your landscape. This feature is available if SAP CC is integrated with SAP CRM and SAP ERP, it enables you to transport contracts from one SAP CC system to another SAP CC system.
CUSTOMERMANAGEMENTAREA	Errors which occur when an SAP CC user manages some customer management areas with the SAP CC Core Tool user interface: Maintain (Create, Modify, Delete) Get (Search) These operations are only available in the SAP CC Core Tool user interface when the system landscape includes SAP CRM or SAP ERP systems. These errors must not be visible by an SAP CC user. Notes SAP CC Core Tool may display some error codes in the below list. Use this technical documentation for troubleshooting purpose. In a production system landscape, contact your SAP Support Team. These private operations are available in the HCI technical interface that is used by the SAP CC Core Tool user interface. The operations cannot be implemented in a connected system.
DICTIONARY	Errors related to the counter dictionary.
HCI	Generic errors related to XML communication. Example: Errors on data types.
MACROCOMPONENT	Errors which occur when managing (creating, changing, or importing) some reusable charges or refill logic objects that include a price plan (or a charging plan or the refill logic) configured with a logic component named Macro Operator to use an existing pricing macro in the pricing catalog. Note All these errors are embedded in a CHARGECOMPONENT error or in a REFILLPLAN error. Check the error stack in the operation response answered by the SAP CC system.
MAPPINGTABLE	Errors which occur when using basic operations on: Mapping table classes Mapping tables Subscriber mapping tables
MAPPINGTABLECOMPONENT	Errors which occur when managing (creating, changing, or importing) some reusable charges or refill logic objects that include a price plan (or a charging plan or the refill logic) configured with a logic component named Mapping Table Introducer. Note All these errors are embedded in a CHARGECOMPONENT error or in a REFILLPLAN error. Check the error stack in the operation response answered by the SAP CC system.
MONITORINGPLAN	Errors which occur when: Implementing the find operations for monitoring plans via the Web Services technical interface Using basic operations (create, search, modify, and delete) that manage monitoring plans stored in SAP CC; These private operations are available in the HCI technical interface that is used by the SAP CC Core Tool user interface. Note SAP CC Core Tool may display some error codes in the below list. Use this technical documentation for troubleshooting purpose. In a production system landscape, contact your SAP Support Team.
OPERATIONALSTATUS	Errors which occur when modifying the operational status of a charging contract with the Web Service operation chargingContractOperationalStatusChange.
PREPAIDACCOUNTSTATE	Errors which occur when implementing operations dedicated to the management of the initial state of prepaid accounts in subscriber accounts during the migration of master data related to end customers. Note Refer to the specifications of the SAP CC Web Services for more information about the necessary Customizing activities to implement a customer data migration.
RANGETABLE	Errors which occur when using basic operations on: Range table classes Range tables Subscriber range tables
RANGETABLECOMPONENT	Errors which occur when managing (creating, changing, or importing) some reusable charges or refill logic objects that include a price plan (or a charging plan or the refill logic) configured with a logic component named Range Table Introducer. This logic component enables to design the pricing logic that uses data tables: Range tables of the pricing catalog of the service provider or subscriber range tables assigned to a subscriber account. Note All these errors are embedded in a CHARGECOMPONENT error or in a REFILLPLAN error. Check the error stack in the operation response answered by the SAP CC system.
REFILLPLAN	Errors which occur when using basic operations on: Refill item classes Refill logic Refill plans Refill record classes
ROLE	Errors which occur when handling roles that can be assigned to SAP CC users.
SPENDINGSTATUS	Errors which occur when using operations that manages spending status descriptions stored in SAP CC: Create Modify Search Delete These private operations are available in the HCI technical interface that is used by the SAP CC Core Tool user interface. Note SAP CC Core Tool may display some error codes in the below list. Use this technical documentation for troubleshooting purpose. In a production system landscape, contact your SAP Support Team.
SQL	Errors related to the initialization and usage of the back-end database.
SUBSCRIBERDATA	Errors related to the import or the export of subscriber data. Subscriber data (or customer related data) consists in: A subscriber account Subscriptions Accesses Counter snapshots Note that the import and the export of subscriber data are mainly used during a migration.
SUBSCRIBERACCOUNT	Errors which occur when implementing operations dedicated to the management of subscriber accounts.
TRANSPORTREQUEST	Errors which occur when implementing basic operations on transport requests.

This Documentation

This product documentation provides you with user assistance about the SAP Convergent Charging software product when developing or implementing the integration between your client application (or system) and the SAP CC systems in your SAP system landscape.

Recommendation

For offline consultation, you can download this document in SAP Help Portal.

Refer to the Web Services Documentation and the SAP CC Java/XML API References. Consult the documentation set of SAP CC for more information.