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.
To continue your troubleshooting investigations, select the error code signaled in the operation response replied by the SAP CC system:
| Error Code | Message | Action |
|---|---|---|
| MONITORINGPLAN-1 | The ID of the monitoring plan is missing. | Add an ID to the monitoring plan. |
| MONITORINGPLAN-2 | The owner of the monitoring plan "{0}" is missing. | Add an owner to the monitoring plan. |
| MONITORINGPLAN-3 | The description of the monitoring plan "{0}" is missing. | Add a description to the monitoring plan. |
| MONITORINGPLAN-4 | The status of the monitoring plan "{0}" is missing. | Add a status to the monitoring plan. |
| MONITORINGPLAN-5 | The monitoring plan "{0}" must at least declare one spending status mapping. | Add at least one spending status mapping that configures the generation of a spending status. |
| MONITORINGPLAN-6 | The ID of the spending status description in the spending status mapping at index {0} is missing. | Add a spending status description ID to the spending status mapping. |
| MONITORINGPLAN-7 | The ID "{0}" of the spending status description in the spending status mapping at index {1} is unknown. | Specify the ID of an existing spending status description to the spending status mapping. |
| MONITORINGPLAN-8 | The ID "{0}" of the spending status description in the spending status mapping at index {1} is already used by the spending status mapping at index {2}. | Specify another ID of the spending status description in the spending status mapping. |
| MONITORINGPLAN-9 | The name of the counter in the spending status mapping at index {0} is missing. | Specify a counter name from the counter name dictionary to the spending status mapping. |
| MONITORINGPLAN-10 | The name "{0}" of the counter in the spending status mapping at index {1} is unknown in the counter name dictionary. | Specify an existing counter name to the spending status mapping. |
| MONITORINGPLAN-11 | The name of the parameter in the spending status mapping at index {0} is missing. | Specify the relevant parameter name to the spending status mapping. |
| MONITORINGPLAN-12 | The parameter name "{0}" in the spending status mapping at index {1} is unknown. | Specify the name of an existing parameter to the spending status mapping. |
| MONITORINGPLAN-13 | The parameter "{0}" at index {1} in the monitoring plan is not used in a spending status mapping. | Link the parameter or remove it from the monitoring plan. |
| MONITORINGPLAN-14 | The monitoring plan is missing in the create operation. | Specify a monitoring plan in the create operation request. |
| MONITORINGPLAN-15 | Cannot create the monitoring plan: The monitoring plan "{0}" already exists. | Specify another monitoring plan in the create operation request. |
| MONITORINGPLAN-16 | The monitoring plan is missing in the modify operation. | Specify a monitoring plan to the modify operation request. |
| MONITORINGPLAN-17 | The monitoring plan "{0}" does not exist. | Specify another monitoring plan to the modify operation request. |
| MONITORINGPLAN-18 | The mandatory filter is missing in the search operation. | Specify a filter in the search operation request. |
| MONITORINGPLAN-19 | An unknown error occurred during the execution of the monitoring plan search operation: {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. |
| MONITORINGPLAN-20 | The ID of the monitoring plan is missing in the delete operation. | Specify the relevant monitoring plan ID in the delete operation request. |
| MONITORINGPLAN-21 | Cannot delete the monitoring plan: The monitoring plan "{0}" does not exist. | Specify another ID of monitoring plan to the delete operation request. |
| MONITORINGPLAN-22 | Error while deleting the monitoring plan "{0}". The monitoring plan is still activated in one provider contract. | First delete all contract items referencing the monitoring plan. |
| MONITORINGPLAN-23 | The monitoring plan "{0}" cannot be modified because the specified owner {1} does not correspond to the owner {2} existing in the monitoring plan. | Change the owner to the owner of the monitoring plan or create a new monitoring plan for the specified owner. |
| MONITORINGPLAN-24 | The status of already released monitoring plan "{0}" cannot be set back to open. | Set the status of this new monitoring plan to released or obsolete. |
| MONITORINGPLAN-25 | The status of already obsolete monitoring plan "{0}" cannot be set back to open. | Set the status of this new monitoring plan to released or obsolete. |
| MONITORINGPLAN-26 | The status of already obsolete monitoring plan "{0}" cannot be set back to released. | Set the status of this new monitoring plan to released or obsolete. |
| MONITORINGPLAN-27 | The text description of the monitoring plan "{0}" cannot be modified because the monitoring plan has been released or is obsolete. | Create a new monitoring plan. |
| MONITORINGPLAN-28 | The additional information "{1}" cannot be removed because the monitoring plan "{0}" has been released or is obsolete. | Create a new monitoring plan. |
| MONITORINGPLAN-29 | The additional information "{1}" cannot be added because the monitoring plan "{0}" has been released or is obsolete. | Create a new monitoring plan. |
| MONITORINGPLAN-30 | The description of the additional information "{1}" cannot be modified because the monitoring plan "{0}" has been released or is obsolete. | Create a new monitoring plan. |
| MONITORINGPLAN-31 | The type of the additional information "{1}" cannot be modified because the monitoring plan "{0}" has been released or is obsolete. | Create a new monitoring plan. |
| MONITORINGPLAN-32 | The date value of the additional information "{1}" cannot be modified because the monitoring plan "{0}" has been released or is obsolete. | Create a new monitoring plan. |
| MONITORINGPLAN-33 | The number value of the additional information "{1}" cannot be modified because the monitoring plan "{0}" has been released or is obsolete. | Create a new monitoring plan. |
| MONITORINGPLAN-34 | The string value of the additional information "{1}" cannot be modified because the monitoring plan "{0}" has been released or is obsolete. | Create a new monitoring plan. |
| MONITORINGPLAN-35 | The user technical identifier "{1}" cannot be removed because the monitoring plan "{0}" has been released or is obsolete. | Create a new monitoring plan. |
| MONITORINGPLAN-36 | The user technical identifier "{1}" cannot be added because the monitoring plan "{0}" has been released or is obsolete. | Create a new monitoring plan. |
| MONITORINGPLAN-37 | The description of the user technical identifier "{1}" cannot be modified because the monitoring plan "{0}" has been released or is obsolete. | Create a new monitoring plan. |
| MONITORINGPLAN-38 | The parameter "{1}" cannot be removed because the monitoring plan "{0}" has been released or is obsolete. | Create a new monitoring plan. |
| MONITORINGPLAN-39 | The parameter "{1}" cannot be added because the monitoring plan "{0}" has been released or is obsolete. | Create a new monitoring plan. |
| MONITORINGPLAN-40 | The description of the parameter "{1}" cannot be modified because the monitoring plan "{0}" has been released or is obsolete. | Create a new monitoring plan. |
| MONITORINGPLAN-41 | The string value of the parameter "{1}" cannot be modified because the monitoring plan "{0}" has been released or is obsolete. | Create a new monitoring plan. |
| MONITORINGPLAN-42 | The spending status mapping "{1}" cannot be removed because the monitoring plan "{0}" has been released or is obsolete. | Create a new monitoring plan. |
| MONITORINGPLAN-43 | The spending status mapping "{1}" cannot be added because the monitoring plan "{0}" has been released or is obsolete. | Create a new monitoring plan. |
| MONITORINGPLAN-44 | The name of the counter in the spending status mapping "{1}" cannot be changed because the monitoring plan "{0}" has been released or is obsolete. | Create a new monitoring plan. |
| MONITORINGPLAN-45 | The parameter name in the spending status mapping "{1}" cannot be changed because the monitoring plan "{0}" has been released or is obsolete. | Create a new monitoring plan. |
| MONITORINGPLAN-46 | The status of new monitoring plan "{0}" must be open. | Set the status of this new monitoring plan to open. |
| MONITORINGPLAN-47 | Error(s) while validating the monitoring plan "{0}". | Check the nested errors in the error stack. |
| MONITORINGPLAN-48 | The name "{0}" of the counter in the spending status mapping at index {1} is already used by the spending status mapping at index {2}. | Change the name of the counter in the relevant spending status mapping. |
| MONITORINGPLAN-49 | The parameter name "{0}" in the spending status mapping at index {1} is already used by the spending status mapping at index {2}. | Change the parameter name in the spending status mapping. |
| MONITORINGPLAN-50 | The Parameter at index {0} is empty. | Replace it by a valid Parameter or remove it. |
| MONITORINGPLAN-51 | The name of the Parameter at index {0} is missing. | Add a name to the Parameter. |
| MONITORINGPLAN-52 | The name "{0}" of the Parameter at index {1} is already used by the Parameter at index {2}. | Change the name of the Parameter. |
| MONITORINGPLAN-53 | The type of the Parameter "{0}" at index {1} is missing or unknown (the only supported type is string). | Add a type to the Parameter or change it to the only supported one: string. |
| MONITORINGPLAN-54 | The description of the Parameter "{0}" at index {1} is missing. | Add a description to the Parameter. |
| MONITORINGPLAN-55 | The value of the Parameter "{0}" at index {1} is missing. | Add a value to the Parameter. |
| MONITORINGPLAN-56 | Error while validating the Parameter "{0}" at index {1}. | |
| MONITORINGPLAN-57 | The Parameter additional information "{0}" at index {1} is unknown. | Remove this additional information or replace it with a known one. |
| MONITORINGPLAN-58 | The data type of the Parameter is missing or unknown (the only supported type is rangeTableId). | Add a data type to the Parameter or change it to the only supported one: rangeTableId. |
| MONITORINGPLAN-59 | The Parameter is a Range Table ID but no Range Table Class is defined. | Add the Range Table Class additional information. |
| MONITORINGPLAN-60 | The Parameter points to an unknown Range Table Class "{0}". | Change the value to a known Range Table Class. |
| MONITORINGPLAN-61 | The Parameter points to the Range Table Class "{0}" which does not have a single output column of type string. | Change the value to a Range Table Class with a single output column of type string. |
| MONITORINGPLAN-62 | The Parameter points to an unknown Range Table "{0}". | Change the value to a known Range Table. |
| MONITORINGPLAN-63 | The Parameter points to the Range Table "{0}" which is not an instance of the previously defined Range Table Class "{1}". | Change the value to a Range Table which is an instance of the previously defined Range Table Class. |
| MONITORINGPLAN-64 | The parameter cannot reference the range table "{0}" because this range table has an agreement ID. | Select a range table without agreement ID. |
The SAP CC system fills in the error message dynamically with relevant information. {0} marks such an information entry.