The Note
SAP CC 5.0 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.
SPENDINGSTATUS module groups multiple error codes that relate to errors occurring when processing operations
that manages spending status descriptions stored in SAP Convergent Charging 5.0:
These private operations are available in the HCI technical interface that is used by the SAP CC Core Tool user interface.
To continue your troubleshooting investigations, select the error code signaled in the operation response replied by the SAP CC system:
| Error Code | Message | Action |
|---|---|---|
| SPENDINGSTATUS-1 | The label "{0}" is not valid because it does not verify the regular expression "{1}". | Set up another value of label verifying the regexp syntax. |
| SPENDINGSTATUS-2 | The code ID of the spending status description "{0}" is not valid because it does not verify the regular expression "{1}". | Set up another ID of the spending status description verifying the regexp syntax. |
| SPENDINGSTATUS-3 | The text description of the spending status description "{0}" is not valid because it does not verify the regular expression "{1}". | Set up another text description of the spending status description verifying the regexp syntax. |
| SPENDINGSTATUS-4 | The label "{0}" at the index "{1}" is not valid. | Check the previous error messages in the error stack. |
| SPENDINGSTATUS-5 | The label "{0}" is duplicated at the index "{1}" and "{2}". | Remove a label in the spending status description specified in the operation request. |
| SPENDINGSTATUS-6 | The spending status description needs at least a label. | Add at least a label in the spending status description. |
| SPENDINGSTATUS-100 | The spending status description is missing in the create operation. | Specify a spending status description in the create operation request. |
| SPENDINGSTATUS-101 | The spending status description "{0}" already exists. | Specify another spending status description in the create operation request. |
| SPENDINGSTATUS-200 | The spending status description is missing in the modify operation. | Specify a spending status description in the modify operation request. |
| SPENDINGSTATUS-201 | The spending status description "{0}" does not exist. | Specify another spending status description to the modify operation request. |
| SPENDINGSTATUS-202 | Cannot modify the spending status description "{1}"; Its label "{0}" is still used. | Add the missing label back in the spending status description to modify or check why the label is still used. |
| SPENDINGSTATUS-203 | Cannot modify the spending status description "{1}"; Its description "{0}" cannot be changed. | Create a new spending status description. |
| SPENDINGSTATUS-300 | The mandatory filter is missing in the search operation. | Specify a filter in the search operation request. |
| SPENDINGSTATUS-301 | Cannot search for spending status descriptions. The search operation or the specified filter is invalid. Reason: {0} | Check the reason information recorded in your error message; The reason is based on the Java Technology. It details the exception raised in the connected SAP CC system. Typical reasons are: Invalid search filter, Back-end database failure. Refer to the SAP CC Java/XML API Reference (Core) technical documentation for more information about the com.highdeal.filter.hci.InvalidSearchException. |
| SPENDINGSTATUS-400 | The ID of the spending status description is missing in the delete operation. | Specify the ID of the relevant spending status description in the operation request. |
| SPENDINGSTATUS-401 | The spending status description "{0}" does not exist. | Specify another ID of spending status description in the delete operation request. |
| SPENDINGSTATUS-402 | Error while deleting the spending status description "{0}". The spending status description is still used in one monitoring plan. | First delete all monitoring plans referencing the spending status description. |
The SAP CC system fills in the error message dynamically with relevant information. {0} marks such an information entry.