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.
To continue your troubleshooting investigations, select the error code signaled in the operation response replied by the SAP CC system:
| Error Code | Message | Action |
|---|---|---|
| CHARGECOMPONENT-1 | The code of the charge component is missing. | Add an identification code to the charge component. |
| CHARGECOMPONENT-2 | The owner of the charge component "{0}" is missing. | Add an owner to the charge component. It is the a pricing catalog of the service provider. |
| CHARGECOMPONENT-3 | The price plan of the charge component "{0}" is missing. | Add a Price Plan to the Charge Component. |
| CHARGECOMPONENT-4 | The charge component "{0}" is set to manage multicurrencies but the currency "{1}" is set. | Check whether the charge component is marked as multicurrencies or remove the set currency. |
| CHARGECOMPONENT-5 | The charge component "{0}" is marked as monocurrency but no currency is set. | Add a currency in the charge component or in the price plan. |
| CHARGECOMPONENT-6 | The Charge Component "{0}" is set with the currency "{1}" and Price Plan with currency "{2}". | Set the currency only in one of the two places. |
| CHARGECOMPONENT-7 | The currency "{0}" of the charge component "{1}" is not a valid currency. | Set a valid currency. |
| CHARGECOMPONENT-8 | The name of the price plan is missing. | Add a name to the Price Plan. |
| CHARGECOMPONENT-9 | The currency "{0}" of the Price Plan "{1}" is not a valid currency. | Set a valid currency. |
| CHARGECOMPONENT-10 | The currency code of the Price Plan is not set. | Check the presence of a currency code in the Price Plan. |
| CHARGECOMPONENT-11 | The currency code "{0}" of the Price Plan is not a valid currency code. | Check the validity of the currency code in the Price Plan. |
| CHARGECOMPONENT-12 | The rate component of type "{0}" is invalid. | Check the validity of the rate component. |
| CHARGECOMPONENT-13 | The usage rate name is not set. | Check the presence of a name in the usage rate. |
| CHARGECOMPONENT-14 | The usage rate "{0}" does not contain any rate component. | Check the presence of a rate component in the usage rate. |
| CHARGECOMPONENT-15 | The recurring rate name is not set. | Check the presence of a name in the recurring rate. |
| CHARGECOMPONENT-16 | The recurring rate "{0}" does not contain any rate component. | Check the presence of a rate component in the recurring rate. |
| CHARGECOMPONENT-17 | The recurring rate "{0}" is marked as proratable but does not contain any prorata. | Check the presence of a prorata in the recurring rate. |
| CHARGECOMPONENT-18 | The one-shot rate name is not set. | Check the presence of a name in the one-shot rate. |
| CHARGECOMPONENT-19 | The one-shot rate "{0}" does not contain any rate component. | Check the presence of a rate component in the one-shot rate. |
| CHARGECOMPONENT-20 | The counter description has no name. | Check the presence of a name in the counter description. |
| CHARGECOMPONENT-21 | The counter description "{0}" has no initial value. | Check the presence of an initial value in the counter description. |
| CHARGECOMPONENT-22 | The counter description "{0}" is duplicated. | Check that the counter description name is unique. |
| CHARGECOMPONENT-23 | The transient counter description has no name. | Check the presence of a name in the transient counter description. |
| CHARGECOMPONENT-24 | The transient counter description "{0}" has no initial value. | Check the presence of an initial value in the transient counter description. |
| CHARGECOMPONENT-25 | The transient counter description "{0}" is duplicated. | Check that the transient counter description name is unique. |
| CHARGECOMPONENT-26 | One parameter does not have any name. | Check that the parameter name is not empty. |
| CHARGECOMPONENT-27 | The parameter "{0}" has a null value. | Check that the parameter value is not null. |
| CHARGECOMPONENT-28 | The parameter "{0}" is duplicated. | Check that the parameter name is unique. |
| CHARGECOMPONENT-29 | The charging plan name is not set. | Check the presence of a name in the charging plan. |
| CHARGECOMPONENT-30 | The usage charge name is not set. | Check the presence of a name in the usage charge. |
| CHARGECOMPONENT-31 | The chargeable item name is not set in the usage charge "{0}". | Check the presence of a chargeable item name in the usage charge. |
| CHARGECOMPONENT-32 | There is no child in the usage charge "{0}". | Check the presence of a child in the usage charge. |
| CHARGECOMPONENT-33 | There are multiple children in the usage charge "{0}". | Check the presence of only one child in the usage charge. |
| CHARGECOMPONENT-34 | The rate component of type "{0}" is invalid in the charging plan. | Check the validity of the rate component. |
| CHARGECOMPONENT-35 | The recurring charge name is not set. | Check the presence of a name in the recurring charge. |
| CHARGECOMPONENT-36 | There is no child in the recurring charge "{0}". | Check the presence of a child in the recurring charge. |
| CHARGECOMPONENT-37 | There are multiple children in the recurring charge "{0}". | Check the presence of only one child in the recurring charge. |
| CHARGECOMPONENT-38 | The rate component of type "{0}" is invalid in the usage charge "{1}". | Check the validity of the rate component. |
| CHARGECOMPONENT-39 | The rate component of type "{0}" is invalid in the recurring charge "{1}". | Check the validity of the rate component. |
| CHARGECOMPONENT-40 | The rate component of type "{0}" is invalid in the one-shot charge "{1}". | Check the validity of the rate component. |
| CHARGECOMPONENT-41 | The one-shot charge name is not set. | Check the presence of a name in the one-shot charge. |
| CHARGECOMPONENT-42 | There is no child in the one-shot charge "{0}". | Check the presence of a child in the one-shot charge. |
| CHARGECOMPONENT-43 | There are multiple children in the one-shot charge "{0}". | Check the presence of only one child in the one-shot charge. |
| CHARGECOMPONENT-44 | The default charge name is not set. | Check the presence of a name in the default charge. |
| CHARGECOMPONENT-45 | There is no child in the default charge "{0}". | Check the presence of a child in the default charge. |
| CHARGECOMPONENT-46 | There are multiple children in the default charge "{0}". | Check the presence of only one child in the default charge. |
| CHARGECOMPONENT-47 | The rate component of type "{0}" is invalid in the default charge "{1}". | Check the validity of the rate component. |
| CHARGECOMPONENT-48 | The usage charge "{0}" already exists in the charging plan "{1}". | Check the uniqueness of the usage charge name. |
| CHARGECOMPONENT-49 | The charging plan "{0}" has several usage charges using the chargeable item class "{1}". | Check the uniqueness of the chargeable item class in the charging plan. |
| CHARGECOMPONENT-50 | The usage rate "{0}" already exists in the price plan "{1}". | Check the uniqueness of the usage rate name. |
| CHARGECOMPONENT-51 | The price plan "{0}" has several usage rates using the chargeable item class "{1}". | Check the uniqueness of the chargeable item class in the price plan. |
| CHARGECOMPONENT-52 | The usage rate "{0}" is invalid because component tree is invalid. | Check the validity of the rate components in usage rate. |
| CHARGECOMPONENT-53 | The recurring rate "{0}" is invalid because component tree is invalid. | Check the validity of the rate components in recurring rate. |
| CHARGECOMPONENT-54 | The one-shot rate "{0}" is invalid because component tree is invalid. | Check the validity of the rate components in one-shot rate. |
| CHARGECOMPONENT-55 | The rate component has an empty name. | Check the presence of a name in the rate component. |
| CHARGECOMPONENT-56 | The rate component "{0}" must have exactly "{1}" children but has "{2}" children. | Add or remove children. |
| CHARGECOMPONENT-57 | The rate component "{0}" has an undefined child at index "{1}". | Add or remove erroneous children. |
| CHARGECOMPONENT-58 | The rate component "{0}" is invalid. | Check the validity of the rate component. |
| CHARGECOMPONENT-59 | The mapping table class "{0}" defined in the parameter "{1}" does not exist in the SAP CC system. | Specify the identifier of an existing mapping table class for additional information value. |
| CHARGECOMPONENT-60 | The mapping table "{0}" defined in the parameter "{1}" does not exist in the SAP CC system. | Specify the identifier of an existing mapping table for additional information value. |
| CHARGECOMPONENT-61 | The range table class "{0}" defined in the parameter "{1}" does not exist in the SAP CC system. | Specify the identifier of an existing range table class for additional information value. |
| CHARGECOMPONENT-62 | The range table "{0}" defined in the parameter "{1}" does not exist in the SAP CC system. | Specify the identifier of an existing range table for additional information value. |
| CHARGECOMPONENT-63 | The additional information named "{0}" defined in the parameter "{1}" is not supported. | Check the validity of the parameter. The supported values are: dataType, mappingTableClass and rangeTableClass. |
| CHARGECOMPONENT-64 | The additional information value "{0}" defined in the parameter "{1}" is not a valid data type. | Check the validity of the parameter additional information. |
| CHARGECOMPONENT-65 | The additional information value "{0}" requires that parameter "{1}" is of type string. | Most probably you defined the wrong type. Check the type and correct it to string. |
| CHARGECOMPONENT-66 | The rate component "{0}" defines no child but has "{1}" child(ren) defined. | Remove all children. |
| CHARGECOMPONENT-67 | The rate "{0}" is invalid because it contains an allowance event sender component while the charging plan dictionary of the charge component is not typed. | Remove the allowance event sender component from the rate. |
| CHARGECOMPONENT-68 | The rate "{0}" is invalid because it contains an allowance property introducer component while the charging plan dictionary of the charge component is not typed. | Remove the allowance property introducer component from the rate. |
| CHARGECOMPONENT-69 | The rate "{0}" is invalid because it contains a create allowance component while the charging plan dictionary of the charge component is not typed. | Remove the create allowance component from the rate. |
| CHARGECOMPONENT-70 | The property at index {0} does not have a name. | Set a name for the property to introduce. |
| CHARGECOMPONENT-71 | The property "{0}" is configured as a context property but does not specify the name of a context property. | Set the name of a context property in the property to introduce. |
| CHARGECOMPONENT-72 | The property "{0}" specifies an invalid context property: "{1}". | Set the name of a valid context property in the property to introduce. |
| CHARGECOMPONENT-73 | The property "{0}" does not specify a value. | Set a value in the property to introduce. |
| CHARGECOMPONENT-74 | The property "{0}" specifies an invalid type. | Set a valid type in the property to introduce ("decimal", "string", or "date"). |
| CHARGECOMPONENT-75 | The property "{0}" is specified more than once. | Rename one of the duplicate properties. |
| CHARGECOMPONENT-76 | The public holiday "{0}" does not exist. | Use a valid public holiday. |
| CHARGECOMPONENT-77 | The data type additional information is missing in the parameter {0}. | Specify the data type additional information for the parameter. |
| CHARGECOMPONENT-78 | A no access function that contains a "bestEffortReservation" property is only allowed in a charge component, in a pricing macro or in an allowance logic. | Remove the "bestEffortReservation" property from the no access function. |
| CHARGECOMPONENT-79 | The property type of the source "{0}" is unknown. | Set the type as follows: 0 for a Number, 1 for a String, 2 for a Date, 4 for a Multi-valued String, or 5 for a Multi-valued Number |
| CHARGECOMPONENT-80 | The property type of the target "{0}" is unknown. | Set the type as follows: 0 for a Number, 1 for a String, 2 for a Date, 4 for a Multi-valued String, or 5 for a Multi-valued Number |
| CHARGECOMPONENT-81 | The conversion between the source property type "{0}" and the target property type "{1}" is not allowed. | Set a source type that can be converted into a target type. |
| CHARGECOMPONENT-82 | The field separator "{0}" must exactly contain one character. | Set the field separator to one character |
| CHARGECOMPONENT-83 | The field separator is mandatory for converting source type "{0}" into target type "{1}". | Add the field separator, or change the source or the target type. |
| CHARGECOMPONENT-84 | The decimal separator is mandatory for converting source type "{0}" into target type "{1}". | Add the decimal separator attribute, or change the source or the target type. |
| CHARGECOMPONENT-85 | The decimal separator "{0}" must exactly contain one character. | Set the decimal separator to one character |
| CHARGECOMPONENT-86 | The thousand separator is mandatory for converting source type "{0}" into target type "{1}". | Add the thousand separator, or change the source or the target type. |
| CHARGECOMPONENT-87 | The thousand separator "{0}" must contain at least one character. | Set the thousand separator to at least one character |
| CHARGECOMPONENT-88 | The field separator and the decimal separator must be different. | Set the field separator and the decimal separator to different values. |
| CHARGECOMPONENT-89 | The field separator and the thousand separator must be different. | Set the field separator and the thousand separator to different values. |
| CHARGECOMPONENT-90 | The decimal separator and the thousand separator must be different. | Set the decimal separator and the thousand separator to different values. |
| CHARGECOMPONENT-91 | The date format pattern is mandatory for converting source type "{0}" into target type "{1}". | Add the date format pattern, or change the source or the target type. |
| CHARGECOMPONENT-92 | The date format pattern "{0}" is invalid. | Set a valid date format pattern. |
| CHARGECOMPONENT-93 | The field to use "{0}" is not supported. | Set a valid field to use between -1 and 16. |
| CHARGECOMPONENT-94 | The start offset "{0}" must be greater than 0. | Set the start offset to a value greater than 0. |
| CHARGECOMPONENT-95 | The start offset "{0}" must be lower than or equal to the stop offset "{1}" plus one. | Set the start offset to a value lower than or equal to the stop offset plus one. |
| CHARGECOMPONENT-96 | The stop offset "{0}" must be greater than or equal to -1. | Set the stop offset to a value greater than or equal to -1. |
| CHARGECOMPONENT-97 | Property "{0}" of type "{1}" is required by the component but does not exist in the context. | Declare the missing property or remove the invalid reference from the logic component. |
| CHARGECOMPONENT-98 | Property "{0}" of type "{1}" is required by the component but is declared in the context with a different type. | Fix the logic component to reference a property of the expected type. |
| CHARGECOMPONENT-99 | Property "{0}" exists in the context but does not meet the constraints of the component. | Change the logic component to reference an appropriate property (table ID, counter, etc.). |
| CHARGECOMPONENT-100 | Property "{0}" of type "{1}" is referenced by the component but has no valid category. | Fix the XML envelope that contains the incorrect pricing logic. |
| CHARGECOMPONENT-101 | The source property is mandatory. | Set a source property |
| CHARGECOMPONENT-102 | The parameter "{0}" cannot reference the mapping table "{1}" because this mapping table has an agreement ID. | Select a mapping table without agreement ID. |
| CHARGECOMPONENT-103 | The parameter "{0}" cannot reference the range table "{1}" because this range table has an agreement ID. | Select a range table without agreement ID. |
| CHARGECOMPONENT-104 | Recurring rate "{0}" is configured for a 4-4-5 calendar. The only supported frequency type is month. | Set the frequency type to month. |
| CHARGECOMPONENT-105 | Recurring rate "{0}" is configured for a 4-4-5 calendar. The only supported frequency periods are 1, 3, 6 and 12. | Set the frequency period to 1, 3, 6 or 12. |
| CHARGECOMPONENT-106 | The prorata component is configured for a 4-4-5 calendar. The only supported frequency type is month. | Set the frequency type to month. |
| CHARGECOMPONENT-107 | The prorata component is configured for a 4-4-5 calendar. The only supported frequency periods are 1, 3, 6 and 12. | Set the frequency period to 1, 3, 6 or 12. |
| CHARGECOMPONENT-108 | The charge component "{0}" must not contain any prepaid charging reference because the Prepaid Accounts Management feature is disabled. | Remove all prepaid charging references from the charge component. |
| CHARGECOMPONENT-109 | Overspending on prepaid account is not available because the Prepaid Accounts Management feature is disabled. | Change the overspending parameters. |
| CHARGECOMPONENT-110 | The Switching Comparator component is not available because the Prepaid Accounts Management feature is disabled. | Remove the Switching Comparator component from the charge. |
| CHARGECOMPONENT-111 | The Default Reference component is not available because the Prepaid Accounts Management feature is disabled. | Remove the Default Reference component from the charge. |
| CHARGECOMPONENT-112 | The frequency of recurring rate "{0}" is not valid. | Set a valid frequency in the recurring rate. |
| CHARGECOMPONENT-113 | The frequency of prorata component "{0}" is not valid. | Set a valid frequency in the prorata component. |
The SAP CC system fills in the error message dynamically with relevant information. {0} marks such an information entry.
