Errors which occur when the execution of a price plan or a charging plan fails during
a rating or charging operation.
To continue your troubleshooting investigations, select the error code signaled in the operation response replied by the SAP CC system:
| Error Code | Message | Action |
|---|---|---|
| CHARGINGPLAN-1 | Rate operation failed for usage rate "{0}". | Fix the usage rate component, or one of its children |
| CHARGINGPLAN-2 | Rate operation failed for recurring rate "{0}". | Fix the recurring rate component, or one of its children |
| CHARGINGPLAN-3 | Rate operation failed for oneshot rate "{0}". | Fix the oneshot rate component, or one of its children |
| CHARGINGPLAN-4 | Charge operation failed for usage charge "{0}". | Fix the usage charge component, or one of its children |
| CHARGINGPLAN-5 | Charge operation failed for recurring charge "{0}". | Fix the recurring charge component, or one of its children |
| CHARGINGPLAN-6 | Charge operation failed for oneshot charge "{0}". | Fix the oneshot charge component, or one of its children |
| CHARGINGPLAN-7 | Rating failure in price plan "{0}". | Fix the price plan or one of its children |
| CHARGINGPLAN-8 | Rating failure in charge activation "{0}" in charging contract or subscription "{1}". | Fix the price plan or one of its children |
| CHARGINGPLAN-9 | Invalid delimitation ''{0}'' used for the conversion from type String to type Multi-Valued String in component ''{1}'' | Define a delimitation character of exactly one character long |
| CHARGINGPLAN-10 | Invalid delimitation ''{0}'' used for the conversion from type String to type Multi-Valued Number in component ''{1}'' | The string that you define as delimitation to convert String into Multi-Valued Number must respect the following constraints: - the delimitation string must be exactly one character long - the delimitation string must be different from the decimal separator - the delimitation string must be different from the thousand separator |
| CHARGINGPLAN-11 | Invalid decimal separator ''{0}'' used for the conversion from type String to type Multi-Valued Number in component ''{1}'' | Define a decimal separator of exactly one character long |
| CHARGINGPLAN-12 | Invalid thousand separator ''{0}'' used for the conversion from type String to type Multi-Valued Number in component ''{1}'' | Define a thousand separator of exactly one character long |
| CHARGINGPLAN-13 | Invalid conversion from type String to type Multi-Valued Number in component ''{0}'', the substring ''{1}'' from the string ''{2}'' cannot be converted to a number | The part of the input string to convert must be a number |
| CHARGINGPLAN-14 | Invalid conversion from type String to type Multi-Valued Number in component ''{0}'', the substring ''{1}'' from the string ''{2}'' cannot be converted to a number | The part of the input string to convert must be a number |
| CHARGINGPLAN-15 | Invalid delimitation ''{0}'' used for the conversion from type Multi-Valued String to type String in component ''{1}'' | Define a delimitation character of exactly one character long |
| CHARGINGPLAN-16 | Invalid decimal separator ''{0}'' used for the conversion from type Multi-Valued String to type Multi-Valued Number in component ''{1}'' | Define a decimal separator of exactly on character long |
| CHARGINGPLAN-17 | Invalid thousand separator ''{0}'' used for the conversion from type Multi-Valued String to type Multi-Valued Number in component ''{1}'' | Define a thousand separator of exactly one character long |
| CHARGINGPLAN-18 | Invalid conversion from type Multi-Valued String to type Multi-Valued Number in component ''{0}'', the field ''{1}'' cannot be converted to a number | Every field of the Multi-Valued String must be convertible to a number |
| CHARGINGPLAN-19 | Invalid delimitation ''{0}'' used for the conversion from type Multi-Valued Number to type String in component ''{1}'' | Define a delimitation character of exactly one character long |
| CHARGINGPLAN-20 | Invalid decimal separator ''{0}'' used for the conversion from type Multi-Valued Number to type String in component ''{1}'' | Define a decimal separator of exactly on character long |
| CHARGINGPLAN-21 | Invalid thousand separator ''{0}'' used for the conversion from type Multi-Valued Number to type String in component ''{1}'' | Define a thousand separator of exactly one character long |
| CHARGINGPLAN-22 | Invalid decimal separator ''{0}'' used for the conversion from type Multi-Valued Number to type Multi-Valued String in component ''{1}'' | Define a decimal separator of exactly one character long |
| CHARGINGPLAN-23 | Invalid thousand separator ''{0}'' used for the conversion from type Multi-Valued Number to type Multi-Valued String in component ''{1}'' | Define a thousand separator of exactly one character long |
| CHARGINGPLAN-24 | Invalid conversion in component ''{0}''. The start offset ''{1}'' must be greater than 0. The start offset ''{1}'' must be lower than or equal to the stop offset value ''{2}'' plus one, and the length ''{3}'' of the input string plus one. | Change the start offset or the stop offset according to those constraints |
| CHARGINGPLAN-25 | Invalid decimal separator ''{0}'' used for the conversion from type String to type Number in component ''{1}'' | Define a decimal separator of exactly one character long |
| CHARGINGPLAN-26 | Invalid thousand separator ''{0}'' used for the conversion from type String to type Number in component ''{1}'' | Define a thousand separator of exactly one character long |
| CHARGINGPLAN-27 | Invalid conversion from type String to type Number in component ''{0}'', the string ''{1}'' cannot be converted to a number | |
| CHARGINGPLAN-28 | Invalid conversion from type String to type Date in component ''{0}'', the string ''{1}'' cannot be converted to a date | |
| CHARGINGPLAN-29 | Invalid decimal separator ''{0}'' used for the conversion from type Number in component ''{1}'' | Define a decimal separator of exactly one character long |
| CHARGINGPLAN-30 | Invalid thousand separator ''{0}'' used for the conversion from type Number in component ''{1}'' | Define a thousand separator of exactly one character long |
| CHARGINGPLAN-31 | Invalid conversion from type Date to type String in component ''{0}'', the date ''{1}'' cannot be converted to a string | |
| CHARGINGPLAN-32 | Invalid conversion from type Multi-Valued String in component ''{0}''. The start offset ''{1}'' and the stop offset ''{2}'' must be greater than 0. The start offset ''{1}'' must be lower than or equals to the stop offset value ''{2}'' plus one, and the length ''{3}'' of the input sub-string plus one. | Change the start offset or the stop offset according to those constraints |
| CHARGINGPLAN-33 | Rating operation failed for Account Event Refill rate component "{0}". | Fix the Account Event Refill rate component, or one of its children |
| CHARGINGPLAN-34 | The date "{0}" specified for an activation or a charging operation is too far in the future considering the value of the parameter PERIOD_LIMIT_ACTIVATION ("{1}") and the current system date | In the business operation requests, change the activation date or the consumption date to a date before the period limit. Verify if the value of the parameter PERIOD_LIMIT_ACTIVATION is correct depending on the business requirements. |
| CHARGINGPLAN-35 | The technical configuration of the shared allowances feature is not complete | Set a positive value for the following parameters: DISTRIBUTED_COUNTER_RESERVATION_POOL_SIZE, DISTRIBUTED_COUNTER_CLEANUP_POOL_SIZE and DISTRIBUTED_COUNTER_CHECK_POOL_SIZE |
The SAP CC system fills in the error message dynamically with relevant information. {0} marks such an information entry.
