The ALLOWANCE module groups multiple error codes that relate to errors occurring when implementing basic
operations on allowances:
To continue your troubleshooting investigations, select the error code signaled in the operation response replied by the SAP CC system:
| Error Code | Message | Action |
|---|---|---|
| ALLOWANCE-1 | The ID of the Allowance Plan is missing. | Add the ID of the Allowance Plan. |
| ALLOWANCE-2 | The owner of the Allowance Plan "{0}" is missing. | Add the owner of the Allowance Plan. |
| ALLOWANCE-3 | The description of the Allowance Plan "{0}" is missing. | Add a description to the Allowance Plan. |
| ALLOWANCE-4 | The status of the Allowance Plan "{0}" is missing. | Add a status to the Allowance Plan. |
| ALLOWANCE-6 | Error while validating the Allowance Plan "{0}". | |
| ALLOWANCE-10 | The Counter at the index {0} is empty. | Replace it by a valid Counter or remove it. |
| ALLOWANCE-11 | The name of the Counter at index {0} is missing. | Add a name to the Counter. |
| ALLOWANCE-12 | The name "{0}" of the Counter at index {1} is already used by the Counter at index {2}. | Change the name of the Counter. |
| ALLOWANCE-13 | The Counter "{0}" at index {1} does not refer to a Counter of the Allowance Plan Item. | Link the Counter or remove it. |
| ALLOWANCE-14 | The description of the Counter "{0}" at index {1} is missing. | Add a description to the Counter. |
| ALLOWANCE-15 | The initial value of the Counter "{0}" at index {1} is missing. | Add an initial value to the Counter. |
| ALLOWANCE-16 | The Parameter at the index {0} is empty. | Replace it by a valid Parameter or remove it. |
| ALLOWANCE-17 | The name of the Parameter at index {0} is missing. | Add a name to the Parameter. |
| ALLOWANCE-18 | The name "{0}" of the Parameter at index {1} is already used by the Parameter at index {2}. | Change the name of the Parameter. |
| ALLOWANCE-20 | The type of the Parameter "{0}" at index {1} is missing or unknown (the supported types are string, number, date). | Add a type to the Parameter or change it into a supported one: string, number, date. |
| ALLOWANCE-21 | The description of the Parameter "{0}" at index {1} is missing. | Add a description to the Parameter. |
| ALLOWANCE-22 | Error while validating the Parameter "{0}" at index {1}. | |
| ALLOWANCE-25 | The parameter additional information "{0}" at index {1} is unknown. | Remove this additional information or replace it with a known one. |
| ALLOWANCE-26 | The data type of the parameter is not defined. | Add this additional information or remove any additional information. |
| ALLOWANCE-27 | The parameter is a mapping table ID but no mapping table class is defined. | Add the additional information of the mapping table class. |
| ALLOWANCE-28 | The parameter is a range table ID but no range table class is defined. | Add the additional information of the range table class. |
| ALLOWANCE-29 | The parameter is a mapping table key and could not be linked to a mapping table class. | Remove the additional information of the mapping table class. |
| ALLOWANCE-30 | The parameter cannot declare additional information without a data type. | Add the additional information of a data type or remove any additional information. |
| ALLOWANCE-36 | The Allowance Plan Item at index {0} is empty. | Replace it by a valid Allowance Plan Item or remove it. |
| ALLOWANCE-37 | The ID of the Allowance Plan Item at index {0} is missing. | Add an ID to the Allowance Plan Item. |
| ALLOWANCE-38 | The ID "{0}" of the Allowance Plan Item at index {1} is already used by the Allowance Plan Item at index {2}. | Change the ID of the Allowance Plan Item. |
| ALLOWANCE-39 | No Allowance Logic is specified. | Add the Allowance Logic to the Allowance Plan Item. |
| ALLOWANCE-40 | Error while validating the Allowance Plan Item "{0}" at index {1}. | |
| ALLOWANCE-41 | The ID of the master Allowance Logic referred to by the Allowance Plan Item is missing. | Add an ID to the master Allowance Logic in the Allowance Plan Item. |
| ALLOWANCE-42 | The ID of the master Allowance Logic referred to by the Allowance Plan Item and the code "{0}" of the retrieved Allowance Logic do not match. | Contact the support. |
| ALLOWANCE-43 | The owner of the Allowance Plan and the owner of the Allowance Logic. The owner of the Allowance Plan is "{0}". The owner of the Allowance Logic is "{1}". | Set the ID the master Allowance Logic that has the same owner as the Allowance Plan. |
| ALLOWANCE-44 | The name of the Counter at index {0} is missing. | Add a name to the Counter. |
| ALLOWANCE-45 | The name "{0}" of the Counter at index {1} is already used by the Counter at index {2}. | Change the name of the Counter. |
| ALLOWANCE-46 | The name of the Counter Reference at index {0} is missing. | Add a name to the Counter Reference. |
| ALLOWANCE-47 | The name "{0}" of the Counter Reference at index {1} is already used by the Counter at index {2}. | Change the name of the Counter Reference. |
| ALLOWANCE-48 | The initial value of the Counter "{0}" at index {1} is missing. | Add an initial value to the Counter. |
| ALLOWANCE-49 | The Counter "{0}" at index {1} does not exist in the Allowance Logic "{2}". | Remove this Counter. |
| ALLOWANCE-50 | The target name of the Counter Reference "{0}" at index {1} is missing. | Add a target name to the Counter Reference. |
| ALLOWANCE-51 | The Counter "{0}" targeted by the Counter Reference "{1}" at index {2} does not exist. | Change the target name of the Counter Reference into an existing one or create a new Counter in the Allowance Plan with this target name. |
| ALLOWANCE-52 | The Counter Reference "{0}" at index {1} does not exist in the Allowance Logic "{2}". | Remove this Counter Reference. |
| ALLOWANCE-58 | The name of the Parameter at index {0} is missing. | Add a name to the Parameter. |
| ALLOWANCE-59 | The name "{0}" of the Parameter at index {1} is already used by the Parameter at index {2}. | Change the name of the Parameter. |
| ALLOWANCE-60 | The name of the Parameter Reference at index {0} is missing. | Add a name to the Parameter Reference. |
| ALLOWANCE-61 | The name "{0}" of the Parameter Reference at index {1} is already used by the Parameter at index {2}. | Change the name of the Parameter Reference. |
| ALLOWANCE-62 | The Parameter "{0}" of the Allowance Logic points to an unknown mapping table "{1}". | Change the value to a known mapping table. |
| ALLOWANCE-63 | The Parameter "{0}" of the Allowance Logic points to an unknown range table "{1}". | Change the value to a known range table. |
| ALLOWANCE-64 | The type of the Parameter "{0}" at index {1} is missing or unknown (the supported types are string, number, date). | Add a type to the Parameter or change it into a supported one: string, number, date. |
| ALLOWANCE-65 | The date value of the Parameter "{0}" at index {1} is missing. | Add a date value to the Parameter. |
| ALLOWANCE-66 | The number value of the Parameter "{0}" at index {1} is missing. | Add a number value to the Parameter. |
| ALLOWANCE-67 | The string value of the Parameter "{0}" at index {1} is missing. | Add a string value to the Parameter. |
| ALLOWANCE-68 | The type "{0}" of the Parameter "{1}" at index {2} is unsupported (the supported types are string, number, date). | Use a supported type (string, number, date) for the Parameter. |
| ALLOWANCE-69 | The Parameter "{0}" at index {1} does not exist in the Allowance Logic "{2}". | Remove this Parameter. |
| ALLOWANCE-70 | Error while validating the Parameter "{0}" at index {1}. | |
| ALLOWANCE-71 | The target name of the Parameter Reference "{0}" at index {1} is missing. | Add a target name to the Parameter Reference. |
| ALLOWANCE-72 | The Parameter "{0}" targeted by the Parameter Reference "{1}" at index {2} does not exist. | Change the target name of the Parameter Reference into an existing one or create a new Parameter in the Allowance Plan with this target name. |
| ALLOWANCE-73 | The type of the Parameter Reference "{0}" at index {1} is missing or unknown (the supported types are string, number, date). | Add a type to the Parameter Reference or change it into a supported one: string, number, date. |
| ALLOWANCE-74 | The type "{0}" of the Parameter Reference "{1}" at index {2} is not compatible with the type "{3}" of the targeted Parameter. | Link the Parameter Reference to a compatible Parameter. |
| ALLOWANCE-75 | Error while validating the Parameter Reference "{0}" at index {1}. | |
| ALLOWANCE-76 | The Parameter Reference "{0}" at index {1} does not exist in the Allowance Logic "{2}". | Remove this Parameter Reference. |
| ALLOWANCE-77 | The Parameter "{0}" of the Allowance Plan referenced by the Parameter Reference "{1}" at index {2} is not declared as a mapping table ID. | Declare the data type of the mapping table ID and the additional information of the mapping table class in the Parameter. |
| ALLOWANCE-78 | The Parameter "{0}" of the Allowance Plan referenced by the Parameter Reference "{1}" at index {2} declares an incompatible mapping table class "{3}" while the Parameter Reference is of class "{4}". | Declare the data type of the mapping table ID and the additional information of the mapping table class in the Parameter. |
| ALLOWANCE-79 | The Parameter "{0}" of the Allowance Plan referenced by the Parameter Reference "{1}" at index {2} is not declared as a range table ID. | Declare the data type of the range table ID and the additional information of the range table class in the Parameter. |
| ALLOWANCE-80 | The Parameter "{0}" of the Allowance Plan referenced by the Parameter Reference "{1}" at index {2} declares an incompatible range table class "{3}" while the Parameter Reference is of class "{4}". | Declare the data type of the range table ID and the additional information of the range table class in the Parameter. |
| ALLOWANCE-81 | The Parameter "{0}" of the Allowance Plan referenced by the Parameter Reference "{1}" at index {2} is not declared as a mapping table key. | Declare the additional information of the data type of the mapping table key in the Parameter. |
| ALLOWANCE-83 | The Parameter is declared as a mapping table ID while it does not exist in the Allowance Logic. | Remove the additional information of the data type of the mapping table ID from the Parameter. |
| ALLOWANCE-84 | The Parameter is declared as a mapping table ID but it does not have a STRING type. | Declare the parameter as a STRING. |
| ALLOWANCE-85 | The mapping table class "{0}" declared in the Parameter is incompatible with the one declared in the Allowance Logic "{1}". | Declare the right mapping table class. |
| ALLOWANCE-86 | The Parameter "{0}" at index {1} points to an unknown mapping table "{2}". | Change the value to a known mapping table. |
| ALLOWANCE-87 | The Parameter is declared as a range table ID while it does not exist in the Allowance Logic. | Remove the additional information of the data type of the range table ID from the Parameter. |
| ALLOWANCE-88 | The Parameter is declared as a range table ID but it does not have a STRING type. | Declare the parameter as a STRING. |
| ALLOWANCE-89 | The range table class "{0}" declared in the Parameter is incompatible with the one declared in the Allowance Logic "{1}". | Declare the right range table class. |
| ALLOWANCE-90 | The Parameter "{0}" at index {1} points to an unknown range table "{2}". | Change the value to a known range table. |
| ALLOWANCE-91 | The Parameter is declared as a mapping table key while it does not exist in the Allowance Logic. | Remove the additional information of the data type of the mapping table key from the Parameter. |
| ALLOWANCE-92 | The Parameter is declared with a mapping table key but has a wrong type "{0}" while it should be "{1}". | Declare the right type for the parameter. |
| ALLOWANCE-93 | The mapping table ID "{0}" is not declared whereas it is used in the Allowance Logic. | Add the corresponding mapping table ID parameter. |
| ALLOWANCE-94 | The range table ID "{0}" is not declared whereas it is used in the Allowance Logic. | Add the corresponding range table ID parameter. |
| ALLOWANCE-95 | The mapping table key "{0}" of type "{1}" is not declared whereas it is used in the Allowance Logic. | Add the corresponding mapping table ID parameter. |
| ALLOWANCE-96 | The Charged Item Mapping is missing in the Allowance Plan Item. | Set the Charged Item Mapping of the Allowance Plan Item. |
| ALLOWANCE-97 | The class of the Charged Item Mapping is missing. | Add a class to the Charged Item Mapping. |
| ALLOWANCE-98 | Error while validating the Charged Item Mapping of class "{0}". | |
| ALLOWANCE-99 | The name of the Charged Item Mapping Entry at index {0} is missing. | Add a name to the Charged Item Mapping Entry. |
| ALLOWANCE-100 | The name "{0}" of the Charged Item Mapping Entry at index {1} is already used by the Charged Item Mapping Entry at index {2}. | Change the name of the Charged Item Mapping Entry. |
| ALLOWANCE-101 | The type of the Charged Item Mapping Entry "{0}" at index {1} is missing or unknown (the supported types are string, number, date, boolean). | Add a type to the Charged Item Mapping Entry or change it into a supported one: string, number, date, boolean. |
| ALLOWANCE-102 | The Charged Item Mapping contains the "{0}" entry. This entry does not exist in the "{1}" Charged Item Class. | Remove the entry from the Charged Item Mapping or replace it by an existing property of the Charged Item Class. |
| ALLOWANCE-103 | The Charged Item Mapping contains the entry "{0}" with the type: {1}. This type is not compatible with the one defined in the Charged Item Class "{2}": {3}. | Change the type of the Charged Item Mapping entry. |
| ALLOWANCE-104 | The Allowance Plan is missing in the CreateAllowancePlanOp operation. | Add the Allowance Plan to the CreateAllowancePlanOp operation. |
| ALLOWANCE-105 | The Allowance Plan "{0}" already exists. | Use another ID or use the ModifyAllowancePlanOp operation to modify the Allowance Plan. |
| ALLOWANCE-106 | The status of the new Allowance Plan "{0}" must be set to open. | Set the status of this new Allowance Plan to open. |
| ALLOWANCE-107 | The ID of the Allowance Logic "{0}" does not match any Allowance Logic. | Set the ID of an existing Allowance Logic object. |
| ALLOWANCE-108 | The code of the charged item class "{0}" does not match any charged item class. | Set the code of an existing charged item class. |
| ALLOWANCE-109 | The Allowance Plan is missing in the ModifyAllowancePlanOp operation. | Add the Allowance Plan to the ModifyAllowancePlanOp operation. |
| ALLOWANCE-110 | The Allowance Plan with the ID {0} does not exist. | Change the ID of the Allowance Plan into an existing one or first create the Allowance Plan. |
| ALLOWANCE-111 | Impossible to modify the Allowance Plan because the specified owner {0} does not correspond to the owner {1} existing in the Allowance Plan. | Change the owner into the owner of the Allowance Plan or create a new Allowance Plan for the specified owner. |
| ALLOWANCE-112 | The description of the Allowance Plan "{0}" cannot be modified because the Allowance Plan has been released. | Create a new Allowance Plan. |
| ALLOWANCE-120 | The parameter "{1}" cannot be removed because the Allowance Plan "{0}" has been released. | Create a new Allowance Plan. |
| ALLOWANCE-121 | The parameter "{1}" cannot be added because the Allowance Plan "{0}" has been released. | Create a new Allowance Plan. |
| ALLOWANCE-122 | The description of the parameter "{1}" cannot be modified because the Allowance Plan "{0}" has been released. | Create a new Allowance Plan. |
| ALLOWANCE-123 | The type of the parameter "{1}" cannot be modified because the Allowance Plan "{0}" has been released. | Create a new Allowance Plan. |
| ALLOWANCE-127 | The counter "{1}" cannot be removed because the Allowance Plan "{0}" has been released. | Create a new Allowance Plan. |
| ALLOWANCE-128 | The counter "{1}" cannot be added because the Allowance Plan "{0}" has been released. | Create a new Allowance Plan. |
| ALLOWANCE-129 | The description of the counter "{1}" cannot be modified because the Allowance Plan "{0}" has been released. | Create a new Allowance Plan. |
| ALLOWANCE-133 | The allowance plan item "{1}" cannot be removed because the Allowance Plan "{0}" has been released. | Create a new Allowance Plan. |
| ALLOWANCE-134 | The allowance plan item "{1}" cannot be added because the Allowance Plan "{0}" has been released. | Create a new Allowance Plan. |
| ALLOWANCE-135 | The allowance plan item "{1}" cannot be modified because the Allowance Plan "{0}" has been released. | Create a new Allowance Plan. |
| ALLOWANCE-138 | The Allowance Plan "{0}" whose status is already set to released cannot be set to open. | Set the status of this new Allowance Plan to released. |
| ALLOWANCE-141 | The Allowance Logic "{0}" is unknown. | Change the allowanceLogicId into an existing Allowance Logic identifier. |
| ALLOWANCE-142 | The code of the charged item class "{0}" does not match any charged item class. | Set the code of an existing charged item class. |
| ALLOWANCE-143 | Internal server error. The Allowance Plan Item refers to no known Allowance Logic. | Contact the support. |
| ALLOWANCE-144 | The Allowance Plan Item already refers to the Allowance Logic "{0}" and cannot refer to the Allowance Logic "{1}" at the same time. | Use the Allowance Logic already referred to by the Allowance Plan Item or create a new Allowance Plan Item. |
| ALLOWANCE-145 | Internal server error. The Allowance Plan Item refers to an unknown charged item class. | Contact the support. |
| ALLOWANCE-146 | The code of the charged item class "{0}" does not match any charged item class. | Add the code of an existing charged item class. |
| ALLOWANCE-147 | The ID of the Allowance Plan is missing in the DeleteAllowancePlanOp operation. | Set the ID of the Allowance Plan to the DeleteAllowancePlanOp operation. |
| ALLOWANCE-148 | The Allowance Plan "{0}" cannot be deleted because it does not exist. | Use an existing ID for the Allowance Plan. |
| ALLOWANCE-149 | Error while deleting the Allowance Plan "{0}". The Allowance Plan is still linked to one or more Charging Contract Items. | First delete all Charging Contract Items referring to the Allowance Plan. |
| ALLOWANCE-150 | The mandatory filter in the SearchAllowancePlanOp operation is missing. | Add the filter to the SearchAllowancePlanOp operation. |
| ALLOWANCE-151 | An error occurred during the execution of the SearchAllowancePlanOp operation: {0} | |
| ALLOWANCE-152 | The code of the charged item class is empty or null. | Set the code of an existing charged item class. |
| ALLOWANCE-153 | The owner of the Allowance Plan and the owner of the Charged Item Class do not match. The owner of the Allowance Plan is "{0}". The owner of the Charged Item Class is "{1}". | Set the code of a Charged Item Class that has the same owner as the Allowance Plan. |
| ALLOWANCE-200 | The Allowance Logic has no ID. | Set the ID of the Allowance Logic. |
| ALLOWANCE-201 | The Allowance Logic "{0}" has no owner. | Set the owner of the Allowance Logic. |
| ALLOWANCE-202 | The Allowance Logic "{0}" has no allowance logic tree. | Add the allowance logic tree to the Allowance Logic. |
| ALLOWANCE-209 | The name of the recurring trigger is not set. | Set the name of the recurring trigger. |
| ALLOWANCE-210 | The recurring trigger "{0}" does not contain any allowance component. | Add an allowance component to the recurring trigger. |
| ALLOWANCE-211 | The recurring trigger "{0}" is invalid because the component tree is invalid. | Check the validity of the rate components in the recurring trigger. |
| ALLOWANCE-212 | The name of the one-shot trigger is not set. | Set the name of the one-shot trigger. |
| ALLOWANCE-213 | The one-shot trigger "{0}" does not contain any allowance component. | Add an allowance component to the one-shot trigger. |
| ALLOWANCE-214 | The one-shot trigger "{0}" is invalid because the component tree is invalid. | Check the validity of the components in oneshot allowance. |
| ALLOWANCE-216 | The counter has no name. | Set the counter name. |
| ALLOWANCE-217 | The counter "{0}" has no initial value. | Set the initial value of the counter. |
| ALLOWANCE-218 | The counter "{0}" is duplicated. | Set the counter to a unique name. |
| ALLOWANCE-219 | The parameter "{0}" is duplicated. | Set the parameter to a unique name. |
| ALLOWANCE-220 | The Allowance Logic is missing in the CreateAllowanceLogicOp operation. | Add the Allowance Logic to the CreateAllowanceLogicOp operation. |
| ALLOWANCE-221 | The Allowance Logic "{0}" already exists. | Use another ID or use the ModifyAllowanceLogicOp operation to modify the Allowance Logic. |
| ALLOWANCE-222 | The Allowance Logic is missing in the ModifyAllowanceLogicOp operation. | Add the Allowance Logic to the ModifyAllowanceLogicOp operation. |
| ALLOWANCE-223 | The Allowance Logic "{0}" cannot be modified because it does not exist. | Check the ID of the Allowance Logic. |
| ALLOWANCE-224 | The Allowance Logic owner "{0}" is not modifiable in the Allowance Logic "{1}". | Check the owner of the Allowance Logic. |
| ALLOWANCE-225 | The ID of the Allowance Logic is missing in the DeleteAllowanceLogicOp operation. | Add the ID of the Allowance Logic to the DeleteAllowanceLogicOp operation. |
| ALLOWANCE-226 | The Allowance Logic "{0}" cannot be deleted because it is referred to by the following Allowance Plans: {1}. | First delete the Allowance Plan(s). |
| ALLOWANCE-227 | The Allowance Logic "{0}" cannot be deleted because it does not exist. | Check the code of the Allowance Logic. |
| ALLOWANCE-229 | The one-shot trigger "{0}" event is not set. | Set a valid event in the one-shot trigger. |
| ALLOWANCE-230 | The event "{1}" of the one-shot trigger "{0}" is not a valid event. | Set a valid event in the one-shot trigger. |
| ALLOWANCE-232 | The Allowance Plan "{0}" cannot be deleted because it is referred to by the following Refill Logic objects: {1}. | First delete the Refill Logic object(s). |
| ALLOWANCE-233 | The Allowance Plan "{0}" cannot be deleted because it is referred to by the following Charge Components: {1}. | First delete the Charge Component(s). |
| ALLOWANCE-234 | The parameter has no name. | Set the parameter name. |
| ALLOWANCE-235 | The parameter "{0}" has no value. | Set the parameter value. |
| ALLOWANCE-236 | 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 the additional information value. |
| ALLOWANCE-237 | 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 the additional information value. |
| ALLOWANCE-238 | 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 the additional information value. |
| ALLOWANCE-239 | 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 the additional information value. |
| ALLOWANCE-240 | 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. |
| ALLOWANCE-241 | The additional information value "{0}" defined in the parameter "{1}" is not a valid data type. | Check the validity of the parameter additional information. |
| ALLOWANCE-242 | The additional information value "{0}" requires that the parameter "{1}" is of type string. | The type is wrong. Check the type and change it into string. |
| ALLOWANCE-243 | The parameter "{0}" does not define a mapping table class. | Specify the identifier of an existing mapping table class for the additional information value. |
| ALLOWANCE-244 | The parameter "{0}" does not define a range table class. | Specify the identifier of an existing range table class for the additional information value. |
| ALLOWANCE-245 | The recurring trigger "{0}" frequency is not set. | Set a valid frequency in the recurring trigger. |
| ALLOWANCE-246 | The chargeable item class ID of the usage allowance "{0}" is not set. | Set a valid chargeable item class ID in the usage allowance. |
| ALLOWANCE-248 | No allowance plan is specified. | Specify an allowance plan in the create allowance component. |
| ALLOWANCE-249 | The allowance plan "{0}" does not exist. | Specify the identifier of an existing allowance plan. |
| ALLOWANCE-250 | The allowance plan "{0}" is not released. | Specify the identifier of a released allowance plan. |
| ALLOWANCE-251 | The parameter "{0}" does not exist in the allowance plan "{1}". | Specify a parameter name that exists in the allowance plan. |
| ALLOWANCE-252 | The parameter "{0}" does not have the same type as in the allowance plan "{1}". | Specify the same parameter type as in the allowance plan. |
| ALLOWANCE-253 | The parameter "{0}" of the allowance plan "{1}" is not defined in the create allowance component. | Specify a value for the parameter. |
| ALLOWANCE-254 | The mapping table "{0}" referenced by the parameter "{1}" does not exist. | Specify the identifier of an existing mapping table. |
| ALLOWANCE-255 | The mapping table "{0}" referenced by the parameter "{1}" is not related to the mapping table class "{2}". | Specify the identifier of an mapping table related to the mapping table class. |
| ALLOWANCE-256 | The range table "{0}" referenced by the parameter "{1}" does not exist. | Specify the identifier of an existing range table. |
| ALLOWANCE-257 | The range table "{0}" referenced by the parameter "{1}" is not related to the range table class "{2}". | Specify the identifier of a range table related to the range table class. |
| ALLOWANCE-258 | The counter "{0}" does not exist in the allowance plan "{1}". | Specify a counter name that exists in the allowance plan. |
| ALLOWANCE-259 | The counter "{0}" of the allowance plan "{1}" is not defined in the create allowance component. | Specify a value for the counter. |
| ALLOWANCE-260 | The context property name "{0}" specified in the start date is not valid. | Specify a valid context property name in the start date. |
| ALLOWANCE-261 | The context property name "{0}" specified in the end date is not valid. | Specify a valid context property name in the end date. |
| ALLOWANCE-262 | The context property name "{0}" specified in the parameter "{1}" is not valid. | Specify a valid context property name for the parameter. |
| ALLOWANCE-263 | The context property name "{0}" specified in the counter "{1}" is not valid. | Specify a valid context property name for the counter. |
| ALLOWANCE-264 | The code of the charged item class is empty or null. | Set the code of an existing charged item class. |
| ALLOWANCE-265 | The code of the charged item class is empty or null. | Set the code of an existing charged item class. |
| ALLOWANCE-266 | The code of the charged item aggregation policy "{0}" does not match any charged item aggregation policy. | Set the code of an existing charged item aggregation policy. |
| ALLOWANCE-267 | The code of the charged item aggregation policy "{0}" does not match any charged item aggregation policy. | Set the code of an existing charged item aggregation policy. |
| ALLOWANCE-268 | The code of the charged item aggregation policy "{0}" does not match any charged item aggregation policy. | Set the code of an existing charged item aggregation policy. |
| ALLOWANCE-269 | The Allowance Plan "{0}" does not contain any Allowance Plan Item. | Add an Allowance Plan Item to the Allowance Plan. |
| ALLOWANCE-270 | The logic tree of the Allowance Logic "{0}" does not contain any allowance component. | Add an allowance component to the logic tree of the Allowance Logic. |
| ALLOWANCE-271 | The type "{0}" of the Parameter "{1}" at index {2} is not compatible with the type "{3}" of the corresponding Allowance Logic Parameter. | Set the correct type for the Parameter. |
| ALLOWANCE-272 | The type "{0}" of the Parameter Reference "{1}" at index {2} is not compatible with the type "{3}" of the corresponding Allowance Logic Parameter. | Set the correct type for the Parameter Reference. |
| ALLOWANCE-273 | The value of the Charged Item Mapping Entry "{0}" at index {1} is not set. | Set either a value or a property name in the Charged Item Mapping Entry. |
| ALLOWANCE-274 | The allowance plan "{0}" does not belong to the same owner as the charge component or refill logic. | Specify an allowance plan with the same owner as the charge component or refill logic. |
| ALLOWANCE-276 | The Allowance Interface is missing in the modify operation. | Add an Allowance Interface to the modify operation. |
| ALLOWANCE-277 | Error while validating the Allowance Interface. | |
| ALLOWANCE-278 | The name of the Parameter at index {0} is missing. | Set a name for the Parameter. |
| ALLOWANCE-279 | The name "{0}" of the Parameter at index {1} is already used by the Parameter at index {2}. | Change the name of the Parameter. |
| ALLOWANCE-280 | The description of the Parameter "{0}" at index {1} is missing. | Set a description for the Parameter. |
| ALLOWANCE-281 | The type of the Parameter "{0}" at index {1} is missing or unknown (the supported types are string, number, date). | Set a type for the Parameter or change it into a supported one: string, number, date. |
| ALLOWANCE-282 | The default value of the Parameter "{0}" at index {1} is missing. | Set a default value for the Parameter. |
| ALLOWANCE-283 | The type of the Parameter "{0}" at index {1} cannot be changed from {2} to {3}. | Set the same type for the Parameter. |
| ALLOWANCE-284 | The Parameter "{0}" cannot be removed. | Set the Parameter. |
| ALLOWANCE-285 | The name of the Counter at index {0} is missing. | Set a name for the Counter. |
| ALLOWANCE-286 | The name "{0}" of the Counter at index {1} is already used by the Counter at index {2}. | Change the name of the Counter. |
| ALLOWANCE-287 | The description of the Counter "{0}" at index {1} is missing. | Set a description for the Counter. |
| ALLOWANCE-288 | The default value of the Counter "{0}" at index {1} is missing. | Set a default value for the Counter. |
| ALLOWANCE-289 | The Counter "{0}" cannot be removed. | |
| ALLOWANCE-290 | The context property name "{0}" specified in the parameter "{1}" does not correspond to a parameter of type mapping table identifier. | Specify a context property name that corresponds to a parameter of type mapping table identifier. |
| ALLOWANCE-291 | The context property name "{0}" specified in the parameter "{1}" does not correspond to a parameter of type range table identifier. | Specify a context property name that corresponds to a parameter of type range table identifier. |
| ALLOWANCE-300 | The Allowance Event Class is missing in the CreateAllowanceEventClassOp operation. | Add the Allowance Event Class to the CreateAllowanceEventClassOp operation. |
| ALLOWANCE-301 | The Allowance Event Class has no ID. | Set the ID of the Allowance Event Class. |
| ALLOWANCE-302 | The owner of the Allowance Event Class "{0}" is missing in the CreateAllowanceEventClassOp operation. | Add the owner of the Allowance Event Class to the CreateAllowanceEventClassOp operation. |
| ALLOWANCE-303 | The Allowance Event Class "{0}" already exists. | Use another ID or use the ModifyAllowanceEventClassOp operation to modify the Allowance Event Class. |
| ALLOWANCE-304 | The name is missing in one of the Allowance Event Class properties. | Add a name to the Allowance Event Class property. |
| ALLOWANCE-305 | The property "{0}" of type "{1}" cannot be removed or changed from the Allowance Event Class "{2}" because it is referenced by the following Allowance Logic object(s): {3}. | Keep the property as it was created initially in the Allowance Event Class. |
| ALLOWANCE-306 | The name "{0}" of the Allowance Event Class property is already used. | Change the name of the Allowance Event Class property. |
| ALLOWANCE-307 | The Allowance Event Class is missing in the ModifyAllowanceEventClassOp operation. | Add the Allowance Event Class to the ModifyAllowanceEventClassOp operation. |
| ALLOWANCE-308 | The Allowance Event Class has no ID. | Set the ID of the Allowance Event Class. |
| ALLOWANCE-309 | The owner of the Allowance Event Class "{0}" cannot be modified | Set the owner of the Allowance Event Class |
| ALLOWANCE-310 | The Allowance Event Class "{0}" cannot be deleted because it does not exist. | Check the ID of the Allowance Event Class. |
| ALLOWANCE-311 | The parameter "{0}" specified as a sorting criterion does not exist in the Allowance Interface. | Set the name of a parameter that exists in the Allowance Interface in the sorting criterion. |
| ALLOWANCE-312 | The parameter "{0}" is specified more than once as a sorting criterion. | Set the parameter as a sorting criterion only once. |
| ALLOWANCE-313 | The parameter "{0}" is specified as a sorting criterion of type "{1}" while its type is "{2}" in the Allowance Interface. | Set the correct type for the parameter in the sorting criterion. |
| ALLOWANCE-314 | The parameter "{0}" cannot be used as a sorting criterion because it is of type "string". | Use the name of another parameter as a sorting criterion. |
| ALLOWANCE-315 | The counter "{0}" specified as a sorting criterion does not exist in the Allowance Interface. | Set the name of a counter that exists in the Allowance Interface in the sorting criterion. |
| ALLOWANCE-316 | The counter "{0}" is specified more than once as a sorting criterion. | Set the counter as a sorting criterion only once. |
| ALLOWANCE-317 | The counter "{0}" is specified as a sorting criterion of type "{1}" while its type must be "number". | Set the counter to the type "number" in the sorting criterion. |
| ALLOWANCE-318 | The sorting criterion "{0}" is unknown. | Set a valid sorting criterion. |
| ALLOWANCE-319 | The name of the event-based trigger is not set. | Set the name of the event-based trigger. |
| ALLOWANCE-320 | The allowance event class ID of the event-based trigger "{0}" is not set. | Set a valid allowance event class ID in the usage allowance. |
| ALLOWANCE-321 | The Allowance Event Class "{0}" referred to in the event-based trigger "{1}" is already used. | Use an existing but not already used Allowance Event Class in the event-based trigger. |
| ALLOWANCE-322 | The Allowance Event Class "{0}" referred to in the event-based trigger "{1}" does not exist. | Use an existing Allowance Event Class in the event-based trigger. |
| ALLOWANCE-323 | The owner of the allowance logic and the owner of the Allowance Event Class referenced by the event-based trigger "{0}" do not match. The owner of the allowance logic is "{1}". The owner of the Allowance Event Class is "{2}". | Set a chargeable item class that has the same owner as the allowance logic in the usage allowance. |
| ALLOWANCE-324 | The event-based trigger "{0}" cannot be added because the Allowance Logic is referenced more than once in the Allowance Plan "{1}". | Do not add an event-based trigger to the Allowance Logic or remove the duplicate Allowance Logic from the Allowance Plan. |
| ALLOWANCE-325 | The Allowance Event Class "{0}" referenced by the event-based trigger "{1}" is already used in the Allowance Plan "{2}" by the Allowance Logic "{3}". | Select another Allowance Event Class in the event-based trigger. |
| ALLOWANCE-326 | The event-based trigger "{0}" does not contain any allowance component. | Add an allowance component to the event-based trigger. |
| ALLOWANCE-327 | The event-based trigger "{0}" is invalid because the component tree is invalid. | Check the validity of the components in the event-based trigger. |
| ALLOWANCE-328 | Rating failure of the charge activation "{0}" in the allowance "{1}". | Fix the logic tree of the allowance logic. |
| ALLOWANCE-329 | Rating event failure of the charge activation "{0}" in the allowance "{1}". | Fix the logic tree of the allowance logic. |
| ALLOWANCE-330 | The Allowance Event Class "{0}" referred to in the allowance logic "{1}" is already used by another allowance logic. | Set the allowance logic with the Allowance Event Class not already used in another allowance logic. |
| ALLOWANCE-336 | The Allowance Event Class "{0}" cannot be deleted because it is referenced at least by one Allowance Event Sender operator or Event-Based Trigger Rate in the following: - Charge(s): {1}. - Refill Logic object(s): {2}. - Allowance Logic object(s): {3}. | First delete the Allowance Logic. |
| ALLOWANCE-337 | No Allowance Event Class is specified. | Specify an Allowance Event Class. |
| ALLOWANCE-338 | The Allowance Event Class "{0}" does not exist. | Specify the identifier of an existing Allowance Event Class. |
| ALLOWANCE-339 | The owner of the Allowance Logic and the owner of the Allowance Event Class referenced by the component do not match. The owner of the Allowance Logic is "{0}". The owner of the Allowance Event Class is "{1}". | Set an Allowance Event Class that has the same owner as the Allowance Logic. |
| ALLOWANCE-340 | The property at index {0} does not have a name. | Specify a property name. |
| ALLOWANCE-341 | The property "{0}" is specified more than once. | Specify the property only once. |
| ALLOWANCE-342 | The property "{0}" does not exist in the Allowance Event Class "{1}". | Specify a property name which exists in the Allowance Event Class. |
| ALLOWANCE-343 | The property "{0}" does not have the same type as in the Allowance Event Class "{1}". | Specify the same property type as in the Allowance Event Class. |
| ALLOWANCE-344 | The property "{0}" does not have a value. | Specify a value for the property. |
| ALLOWANCE-345 | The property "{0}" does not have a context property value. | Specify a context property value for the property. |
| ALLOWANCE-346 | The context property name "{1}" specified in the property "{0}" is not valid. | Specify a valid context property name for the property. |
| ALLOWANCE-347 | No properties can be added to the Allowance Event Class "{0}" because it is referenced at least by one Allowance Event operator in the following: - Charge(s): {1}. - Refill Logic object(s): {2}. - Allowance Logic object(s): {3}. | Specify a value for the property. |
| ALLOWANCE-348 | The type "{0}" of the parameter "{1}" at index {2} is not equal to the type "{3}" of the parameter in the Allowance Interface. | Link the Parameter or remove it. |
| ALLOWANCE-350 (Revoked) | The code of the Charged Item Class of the Allowance Plan Item "{1}" cannot be changed from "{2}" to "{3}" because the Allowance Plan "{0}" has been released. | Set the code of the original Charged Item Class. |
| ALLOWANCE-352 | The parameter additional information "{0}" at index {1} does not have a value. | Set of a value for this additional information. |
| ALLOWANCE-353 | The clause property "{0}" is unknown. | Set a valid clause property: A parameter or a counter defined in the Allowance Interface or a default Allowance property (unique identifier, activation date or expiration date) |
| ALLOWANCE-354 | The parameter "{0}" specified as a clause property does not exist in the Allowance Interface. | Set the name of a parameter that exists in the Allowance Interface. |
| ALLOWANCE-356 | The parameter "{0}" is specified as a clause property of type "{1}" while its type is "{2}" in the Allowance Interface. | Set the parameter to the correct type in the clause property. |
| ALLOWANCE-357 | The counter "{0}" specified as a clause property does not exist in the Allowance Interface. | Set the name of a counter that exists in the Allowance Interface. |
| ALLOWANCE-359 | The counter "{0}" is specified as a clause property of type "{1}" while its type must be "number". | Set the counter to the type "number" in the clause property. |
| ALLOWANCE-360 | The clause property "{0}" is defined with an operator which is invalid or not compatible with the type "{1}". | Set a clause operator compatible with the type of the clause property. |
| ALLOWANCE-361 | The clause property "{0}" is defined with the value "{1}" which is not compatible with the type "{2}". | Set a clause value compatible with the type of the clause property. |
| ALLOWANCE-363 | The parameter "{0}" specified as the origin of the generated property "{1}" does not exist in the Allowance Interface. | Set the name of a parameter that exists in the Allowance Interface as the origin of the generated property. |
| ALLOWANCE-364 | The generated property "{0}" defines its origin with the parameter "{1}" of type "{2}" while its type is "{3}" in the Allowance Interface. | Set the parameter to the correct type in the generated property. |
| ALLOWANCE-365 | The counter "{0}" specified as the origin of the generated property "{1}" does not exist in the Allowance Interface. | Set the name of a counter that exists in the Allowance Interface as origin of the generated property. |
| ALLOWANCE-366 | The generated property "{0}" defines its origin with the counter "{1}" of type "{2}" while its type must be "number". | Set the counter to the type "number" in the generated property. |
| ALLOWANCE-367 | The generated property "{0}" defines its origin with the unknown property "{1}". | Set a valid origin in a generated property: a parameter or a counter defined in the Allowance Interface or a default Allowance property (unique identifier, activation date or expiration date) |
| ALLOWANCE-368 | The parameter "{0}" specified as the origin of the generated property "{1}" is of type "string" which is not allowed | Set an origin of type "date" or "number" in a generated property |
| ALLOWANCE-369 | The generated property "{0}" defines its origin with the default property "{1}" and the type "{2}" instead of "{3}". | Set the right type of the origin in a generated property: "number" for the unique identifier, "date" for the allowance activation and allowance expiration. |
| ALLOWANCE-370 | The clause property "{0}" is defined with the type "{1}" instead of "{2}". | Set the right type in the clause property: "number" for the unique identifier, "date" for the allowance activation and allowance expiration. |
| ALLOWANCE-371 | The clause property "{0}" of type "{1}" is defined with the referenced value "{2}" which is not part of the rating context. | Set a clause value with a valid rating context property name. |
| ALLOWANCE-372 | The name of the generated allowance count property is not set. | Set a name for the generated allowance count property. |
| ALLOWANCE-373 | The Counter "{0}" cannot be added because it is already used by one or more Allowance Plans. | Set a name not already used by an Allowance Plan |
| ALLOWANCE-374 | The Parameter "{0}" cannot be added because it is already used by one or more Allowance Plans. | Set a name not already used by an Allowance Plan |
| ALLOWANCE-375 | One or more clause properties are invalid. A clause must have a name, a type, an operator, an isReferenceValue flag and a value. | Check the clause properties have a name, a type, an operator, an isReferenceValue flag and a value |
| ALLOWANCE-376 | One or more generated properties are invalid. A generated property must have a name, a type, an operator and an origin. | Check the generated properties have a name, a type, an operator, and an origin |
| ALLOWANCE-377 | The generated property "{0}" is specified more than once. | Specify the generated property only once. |
| ALLOWANCE-378 | The default allowance property "{0}" is specified more than once as a sorting criterion. | Set the counter as a sorting criterion only once. |
| ALLOWANCE-379 | The allowance search filter is missing in the search operation. | Add an allowance search filter to the search operation. |
| ALLOWANCE-380 | The attribute description "id" is missing in the allowance search filter. | Add the attribute description "id" to the allowance search filter. |
| ALLOWANCE-381 | The attribute description "id" of the allowance search filter is invalid. | Set the attribute description "id" with either a format constraint or an enumerated constraint with a single value of type string. |
| ALLOWANCE-382 | The identifier of the charging contract is empty. | Set a charging contract identifier that is not empty. |
| ALLOWANCE-384 | The end date cannot be extended if the Allowance is not active. | Keep the previous end date. |
| ALLOWANCE-385 | The start date cannot be modified after the creation of the Allowance. | Keep the previous start date. |
| ALLOWANCE-386 | The end date cannot be modified after the creation of the Allowance. | Keep the previous end date but extends the end date with the extendedToEndDateProperty attribute. |
| ALLOWANCE-387 | The start date property "{0}" is unknown in the rating context. | Set a valid rating context property name to define the start date. |
| ALLOWANCE-388 | The end date property "{0}" is unknown in the rating context. | Set a valid rating context property name to define the end date. |
| ALLOWANCE-389 | The extended to end date property "{0}" is unknown in the rating context. | Set a valid rating context property name to define the extended to end date. |
| ALLOWANCE-390 | The start date property is empty or null. | Set a rating context property name to define the start date. |
| ALLOWANCE-391 | The end date property is empty or null. | Set a rating context property name to define the end date. |
| ALLOWANCE-392 | The generated property "{0}" is defined with the operator "{1}" which is not compatible with the type "{2}". | |
| ALLOWANCE-393 (Revoked) | The Charged Item Mapping contains the entry "{0}". This entry is already defined in the Charged Item Class "{1}". | Remove the entry from the Charged Item Mapping. |
| ALLOWANCE-394 | The property "{1}" specified in the Charged Item Mapping Entry "{0}" is not allowed in an Allowance Plan. | Set the name of a property allowed in Allowance Plans. |
| ALLOWANCE-395 (Revoked) | The Charged Item Mapping does not contain the entry "{0}". This entry has no value or the value is not applicable in this context in the Charged Item Class "{1}". | Add the missing entry in the Charged Item Mapping. |
| ALLOWANCE-396 | The output property at index {0} does not have a name. | Specify a property name. |
| ALLOWANCE-397 | The output property "{0}" is specified more than once. | Specify the output property only once. |
| ALLOWANCE-398 | An output property cannot be defined for the unknown property "{0}" of the Allowance Event Class "{1}". | Specify a property name that exists in the Allowance Event Class. |
| ALLOWANCE-399 | The monitored property "{0}" does not exist in the Allowance Event Class "{1}". | Specify a monitored property name that exists in the Allowance Event Class. |
| ALLOWANCE-400 | The value of the output property "{0}" is missing. | Specify a property name. |
| ALLOWANCE-401 | The allowance event property at index {0} does not have a name. | Specify a property name. |
| ALLOWANCE-402 | The allowance event property "{0}" is specified more than once. | Specify the allowance event property only once. |
| ALLOWANCE-403 | The property "{0}" does not exist in the Allowance Event Class "{1}". | Specify a property name that exists in the Allowance Event Class. |
| ALLOWANCE-404 | The property "{0}" does not have the same type as in the Allowance Event Class "{1}". | Specify the same property type as in the Allowance Event Class. |
| ALLOWANCE-405 | The property "{0}" does not have a value. | Specify a value for the property. |
| ALLOWANCE-406 | The property "{0}" does not have a context property value. | Specify a context property value for the property. |
| ALLOWANCE-407 | The context property name "{1}" specified in the property "{0}" is not valid. | Specify a valid context property name for the property. |
| ALLOWANCE-408 | The output property name "{0}" is specified more than once. | Specify the output property name only once. |
| ALLOWANCE-409 | The unit of time of the date shift is missing". | Add a unit of time to the date shift if missing or set a valid unit of time otherwise. |
| ALLOWANCE-410 | The shift of a one-shot rate triggered on the allowance creation is not supported. | Remove the date shift of the one-shot rate. |
| ALLOWANCE-411 | The brought forward triggering of one-shot rates related to the allowance activation is not supported (date shift is {0}). | Remove the date shift of the one-shot rate or set a positive quantity to delay the one-shot triggering. |
| ALLOWANCE-412 | The delayed triggering of one-shot rates related to the allowance expiration is not supported (date shift is {0}). | Remove the date shift of the one-shot rate or set a negative quantity to brought forward the one-shot triggering. |
| ALLOWANCE-413 | The property "{1}" specified in the Charged Item Mapping Entry "{0}" is invalid. | Set the name of a valid property. |
| ALLOWANCE-414 | The type "{3}" of the property "{2}" specified in the Charged Item Mapping Entry "{0}" is invalid. The expected type is: "{1}". | Change the type of the Charged Item Mapping Entry or set another property with the expected type. |
| ALLOWANCE-415 | The reporting scope "session" cannot be used in an allowance plan item. | Remove the reporting scope "session" from the allowance plan item. |
| ALLOWANCE-416 | Unexpected error during the initialization of the Allowance Logic "{0}". | Contact the support. |
| ALLOWANCE-417 | The Allowance Event Class "{0}" cannot be modified because it does not exist. | Check the ID of the Allowance Event Class. |
| ALLOWANCE-418 | The ID of the Allowance Event Class is missing in the DeleteAllowanceEventClassOp operation. | Specify the ID of the Allowance Event Class in the DeleteAllowanceEventClassOp operation. |
| ALLOWANCE-419 | The Allowance Logic specified in the operation has no ID. | Specify the ID of the Allowance Logic. |
| ALLOWANCE-420 | The data type additional information is missing in the parameter {0}. | Specify the data type additional information for the parameter. |
| ALLOWANCE-421 | Invalid structure of the clause properties. | Check the number and the order of the clause properties. |
| ALLOWANCE-432 | The creation of allowances performed by an allowance logic is not allowed in the one-shot rate [{0}] because it is not configured with the expiration event. | Check that the one-shot rate used in your allowance logic for renewing allowances is configured with the expiration event. |
| ALLOWANCE-433 | The creation of allowances performed by the allowance logic is not allowed in the one-shot rate [{0}] because a shifted delay is used. | Check that the one-shot rate used in your allowance logic for renewing allowances is configured with a zero-shifted delay. |
| ALLOWANCE-434 | You cannot set a validity start date property in this allowance rate context. | Remove this property. |
| ALLOWANCE-435 | The Allowance Plan [{0}] cannot be deleted because it is referred by the following Allowance Logic objects: [{1}]. | First delete the Allowance Logic objects. |
| ALLOWANCE-436 | The allowance logic {0} cannot be modified because the attribute shareable has been changed from "{1}" to "{2}". | Set the attribute shareable to "{1}" in the modification operation. |
| ALLOWANCE-437 | The allowance plan {0} cannot be modified because the attribute shareable cannot be changed from "{1}" to "{2}" if the allowance plan is released. | Set the attribute shareable to "{1}" in the operation. |
| ALLOWANCE-438 | A shareable allowance plan must only contain shareable allowance logic components. | Remove any allowance logic that is not shareable or make sure that the allowance plan is not shareable. |
| ALLOWANCE-439 | Because the allowance logic is shareable, you cannot use the allowance event sender component in any trigger. | Remove the allowance event sender component. |
| ALLOWANCE-440 | Because the allowance logic {0} is shareable, you cannot use a recurring trigger in this allowance logic. | Remove the recurring trigger component from the allowance logic or make sure that the allowance logic is not shareable. |
| ALLOWANCE-441 | Because the allowance logic {0} is shareable, you cannot use an activation one-shot trigger in this allowance. | Remove the activation one-shot from the allowance logic. |
| ALLOWANCE-442 | Because the allowance logic {0} is shareable, you cannot shift the expiration of a one-shot trigger component. | Set to 0 the time shift of the activation one-shot of the allowance logic. |
| ALLOWANCE-443 | Because the allowance logic is shareable, you cannot use the persistent counters in the component {0} of the allowance logic. | Remove the counter property from the allowance logic. |
| ALLOWANCE-444 | The share identifier "{0}" of the allowance event sender component is invalid because only parameter properties are allowed. | Set a property of parameter type for the share identifier. |
| ALLOWANCE-445 | The share identifier "{0}" of the allowance event sender component does not refer to an existing parameter property. | Set a property of parameter type that exists in the rating context for the share identifier. |
| ALLOWANCE-446 | The share identifier "{0}" of the create allowance component does not refer to an existing rating context property. | Set a property name that exists in the rating context for the share identifier. |
| ALLOWANCE-447 | The counter property "{0}" that is used in the charged item mapping entry "{1}" is not allowed in a shareable allowance plan. | Set a property that is allowed in allowance plans. |
| ALLOWANCE-448 | Because the allowance logic is not shareable, you can only use the allowance event sender component in the event-based trigger to send events to shared allowances. | Remove the allowance event sender component from the event-based trigger or set a share identifier to send events to shared allowances. |
| ALLOWANCE-449 | The allowance event sender component {0} with a share identifier can only be used in the allowance logic that is not shareable. | Remove the allowance event sender component or deselect the share identifier. |
| ALLOWANCE-450 | The counterName "{0}" of a debit counter component must refer to a valid persistent or transient counter. | Change the property name of the counter. |
| ALLOWANCE-451 | The allowance validity period updater component is not allowed in the event-base trigger of the shareable allowance logic. | Remove the allowance validity period updater component from the event-based trigger. |
| ALLOWANCE-452 | The debitValueName "{0}" of a debit Counter component must refer to a valid persistent or transient counter. | Change the property name of the debit value. |
| ALLOWANCE-453 | The allowance property introducer component cannot be used in a shareable allowance logic. | Remove the allowance property introducer component. |
| ALLOWANCE-454 | The counter "{0}" that is defined as a clause property cannot be used to select shared allowances. | Remove the clause properties of counter type if they are used for shared allowances. |
| ALLOWANCE-455 | The counter "{0}" that is defined as a sorting criterion cannot be used to sort shared allowances. | Remove the sorting criteria of counter type if they are used for shared allowances. |
| ALLOWANCE-456 | The value of debit "{0}" must be equal to 0 or greater than 0. | Set the value of debit to a positive value. |
| ALLOWANCE-457 | The counter "{0}" that is used as the origin of the generated property "{1}" is not allowed with shared allowances. | Remove the counter that is used as the origin of the generated property. |
| ALLOWANCE-458 | The share identifier property name "{0}" of the component allowance property introducer does not refer to an existing rating context property. | Set a property that exists in the rating context for the share identifier. |
| ALLOWANCE-459 | The name of the debited value output is mandatory. | Set the name of the debited value output. |
| ALLOWANCE-460 | The name of the non debited value output is mandatory. | Set the name of the non debited value output. |
| ALLOWANCE-461 | In the expiration one-shot rate of the allowance logic, the renewal of allowances is only allowed for allowances that are not shared. | Check that the create allowance component is configured to renew allowances that are not shared. |
| ALLOWANCE-462 | The create allowance component cannot be used in a shareable allowance logic. | Remove the create allowance component from the shareable allowance logic. |
| ALLOWANCE-463 | The create allowance component cannot be used with a share identifier if the allowance plan is not shareable. | Remove the share identifier or set a shareable allowance plan. |
| ALLOWANCE-464 | The debit counter component must contain a debit value. | Set a debit value in the debit counter component. |
| ALLOWANCE-465 | The allowances of the charging contract "{0}" cannot be retrieved. Message: {1} | Read the message for more details. |
| ALLOWANCE-466 | The allowance event sender component {0} with a share identifier can only be used in the event-based trigger of the allowance logic that is not shareable. | Remove the allowance event sender component or move it in an event-based trigger. |
| ALLOWANCE-470 | The property "{1}" specified in the Charged Item Mapping Entry "{0}" is not available in the context of the Allowance Plan Item. | Set the name of a property available in the context of the Allowance Plan Item. |
| ALLOWANCE-471 | The parameter "{0}" cannot reference the mapping table "{1}" because this mapping table has an agreement ID. | Select a mapping table without agreement ID. |
| ALLOWANCE-472 | The parameter of the allowance plan item cannot reference the mapping table "{0}" because this mapping table has an agreement ID. | Select a mapping table without agreement ID. |
| ALLOWANCE-473 | The parameter "{0}" cannot reference the range table "{1}" because this range table has an agreement ID. | Select a range table without agreement ID. |
| ALLOWANCE-474 | The parameter of the allowance plan item cannot reference the range table "{0}" because this range table has an agreement ID. | Select a range table without agreement ID. |
| ALLOWANCE-475 | Recurring trigger "{0}" is configured for a 4-4-5 calendar. The only supported frequency type is month. | Set the frequency type to month. |
| ALLOWANCE-476 | Recurring trigger "{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. |
| ALLOWANCE-477 | The property "{1}" specified in the charged item mapping entry "{0}" is invalid because the Prepaid Accounts Management feature is disabled. | Select a valid property. |
| ALLOWANCE-478 | The frequency of the recurring trigger "{0}" is invalid. | Set a valid frequency in the recurring trigger. |
| ALLOWANCE-479 | The counterName "{0}" of a credit counter component must refer to a valid persistent or transient counter. | Change the property name of the counter. |
| ALLOWANCE-480 | The creditValueName "{0}" of a credit Counter component must refer to a valid persistent or transient counter. | Change the property name of the credit value. |
| ALLOWANCE-481 | The value of credit "{0}" must be equal to 0 or greater than 0. | Set the value of credit to a positive value. |
| ALLOWANCE-482 | The credit counter component must contain a name for the result value output. | Set the name of the result value output. |
| ALLOWANCE-483 | The credit counter component must contain a credit value or a credit value name. | Set a credit value or a credit value name in the credit counter component. |
| ALLOWANCE-484 | "{0}" is a counter of type debit. You cannot use a debit counter in the credit counter component "{1}". | Set a counter of type credit in the credit counter component. |
| ALLOWANCE-485 | "{0}" is a counter of type credit. You cannot use a credit counter in the debit counter component "{1}". | Set a counter of type credit in the credit counter component. |
| ALLOWANCE-486 | You cannot link the counter "{0}" of type "{1}" defined in the allowance plan to the counter "{2}" of type "{3}" defined in the allowance plan item. | Change the type of the counter of the allowance plan or link the counter to a counter of the allowance plan item having the same type. |
| ALLOWANCE-487 | "{0}" is a counter of type credit. You cannot use a credit counter in an allowance plan which is not shareable. | Remove the counter. |
| ALLOWANCE-488 | "{0}" is a counter of type credit. You cannot use a credit counter in an allowance logic which is not shareable. | Remove the counter or remove the type credit. |
| ALLOWANCE-489 | The operation of the counter "{1}" cannot be modified because the Allowance Plan "{0}" has been released. | Create a new Allowance Plan. |
The SAP CC system fills in the error message dynamically with relevant information. {0} marks such an information entry.
