Errors which occur when implementing operations dedicated to the management of the
initial state of charging contracts during
the migration of master data related to end customers.
A charging contract is the charging data that is part of the overall provider contract.
It is a partial view of this master data and is stored in SAP CC.
Note
Refer to the SOAP API Specifications of the SAP CC Web Services for more information about the necessary Customizing activities
to implement the customer data migration.
To continue your troubleshooting investigations, select the error code signaled in the operation response replied by the SAP CC system:
| Error Code | Message | Action |
|---|---|---|
| CONTRACTSTATE-1 | The shared counter "{0}" does not exist in the charging contract "{1}". | Change the name of the shared counter to an existing one. |
| CONTRACTSTATE-2 | The contract item "{0}" specified in the contract item state does not exist in the charging contract "{1}". | Change the identifier of the contract item to an existing contract item (customer master data). |
| CONTRACTSTATE-3 | The counter "{0}" does not exist in the charge plan "{1}" activated in the contract item "{2}" specified in the operation request. | Change the counter name to an existing one. |
| CONTRACTSTATE-4 | The specified charge activation "{0}" does not exist in the contract item "{1}" of the charging contract "{2}". | Change the identifier of the charge activation to an existing one. |
| CONTRACTSTATE-5 | The specified counter "{0}" of the charge activation "{1}" in the contract item "{2}" does not exist in the customized charge "{3}" or is always redefined. | Change the counter name to an existing one and check that the counter is not redefined. |
| CONTRACTSTATE-6 | The shared counter "{0}" specified in the operation request is referenced several times. | Use the shared counter name only once in the operation request. |
| CONTRACTSTATE-7 | The specified counter "{0}" of the contract item "{1}" is referenced several times. | Specify the counter name only once in the operation request. |
| CONTRACTSTATE-8 | The specified counter "{0}" in the charge activation "{1}" of the contract item "{2}" is referenced several times. | Specify the counter name only once in this charge activation in the operation request. |
| CONTRACTSTATE-9 | The specified counter name "{0}" is reserved for internal use only. | Do not use this counter name in the operation request. |
| CONTRACTSTATE-10 | Cannot change the charging contract "{0}". This master data does not exist. | Change the identifier of the charging contract to an existing contract. |
| CONTRACTSTATE-11 | Cannot read the charging contract "{0}". This master data does not exist. | Change the identifier of the charging contract to an existing contract. |
| CONTRACTSTATE-12 | Cannot change the state of the charging contract. The contract item "{0}" is referenced several times. | Specify this contract item only once in the operation request. |
| CONTRACTSTATE-13 | Cannot change the state of the charging contract. The charge activation "{0}" in the contract item "{1}" is referenced several times. | Specify this charge activation only once in the operation request. |
| CONTRACTSTATE-14 | The specified LastActivationDate "{0}" in the charge activation "{1}" of the contract item "{2}" is anterior to the validity start date of the contract item "{3}". | Specify a LastActivationDate posterior to the validity start date of the contract item. |
The SAP CC system fills in the error message dynamically with relevant information. {0} marks such an information entry.
