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 5.0:
The user interfaces of SAP Convergent Charging send their operation requests to the SAP CC system.
Some business or technical issues may occur. The SAP CC system can audit these operations by recording the isolated or cascaded failures.
This user assistance is intended for troubleshooting purposes and for understanding why an operation was not executed or has failed in the SAP CC Core Server system (aka SAP Convergent Charging system).
View the information topic that relates to your situation and continue your investigations.
During the implementation project, you use this documentation when integrating the business services provided by the Web Services (WS) technical interface 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 that is used by the SAP CC user interfaces (Core Tool or Cockpit).
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.
During the project implementation phase or the productive 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
Audited user operations that you can view and inspect with the app Display User Operations in SAP CC 5.0 Cockpit
XML messages exchanged between the SAP CC system and an SAP CC user interface
SAP Convergent Charging manages different types of errors replied in the operation responses. An error may include:
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:
Caution
Error codes can be deprecated or revoked 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 Convergent Charging.
Texts in error messages may change to improve your user experience. First consider the numerical code for an error.
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.
You can see also the technical details of the 'Charge a Single Chargeable Item (Offline Charging or Soft Real-Time)' operation.
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.
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 expected process.
For a better experience, the system completes a message with runtime information such as identifiers, names, references, indexes, or dates/times. For example, it can be the code of an object managed in the SAP CC system or in its back-end database.
Note
The meaning of an error message depends on the software layers and on the internal architecture of the SAP CC systems. The error message relates to the internal vision of the SAP CC system.
You may have to translate the message terms to the SAP CC terminology. Consider the concept views and the data model views for the technical interface that has transported the error message. Refer to the appropriate specifications:
Use this information to troubleshoot your issue with a cause analysis and a solution.
Select the module signaled in the error replied in the operation response by the SAP CC system:
| Signaled Module | Definition | |
|---|---|---|
| AGGREGATIONPOLICY |
Errors related to the processing of basic operations working on aggregation policies. |
|
| ALLOWANCE |
Errors related to the processing of basic operations working on allowances (allowance plan, allowance logic, allowance interface). |
|
| CC-SEC-AUTH |
Errors related to authentication, mainly describing logon 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 related to the processing of basic operations on charging contracts (pricing and charging view for 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:
Notes
|
|
| DICTIONARY |
Errors related to the counter dictionary. |
|
| HCI | Generic errors related to some XML communication validation | |
| 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 that occur when using or implementing some basic operations (create, search, modify, import, and delete) on the following master data:
|
|
| 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:
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:
|
|
| 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:
|
|
| SPENDINGSTATUS | Errors related to the processing of basic operations to manage some spending status descriptions | |
| 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:
|
|
| 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. |
|
As SAP Convergent Charging evolves over time, rare error codes may become obsolete because of some enhancements in the SAP CC system or data.
When a feature or a function of SAP CC becomes deprecated, some error codes can be deprecated or revoked.
When a feature is revoked, some error codes can become revoked.
Feature deprecation is announced whereas error code deprecation or revocation cannot be announced in advance.
| Error Code | Definition | |
|---|---|---|
| Deprecated |
Deprecated error codes are error codes that the newest versions of your SAP CC system still generate but they may become revoked. Some newest error codes may replace the obsolete codes. |
|
| Revoked |
Revoked error codes are error codes that the newest versions of your SAP CC system will not generate anymore. The code are not signaled whereas some old log messages or traces for the SAP CC system or for other systems may contain these codes with an error message. |
|
Example
For example, with this software evolution, the code MAPPINGTABLE-232 replaces the MAPPINGTABLE-6 error code.
This SAP 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 on SAP Help Portal.
Refer to the SAP CC Web Services Documentation and the SAP CC Java/XML API References. Consult the documentation set of SAP CC for more information.
For more information, see the related product documentation of SAP Convergent Charging on SAP Help Portal:
For more information and user assistance about the functions and the processes in SAP Convergent Charging, consult the following document:
For more information and user assistance about the configuration of master data and the configuration of an SAP CC system, consult the following documents:
