...
1XX - Validation errors
Error code | Error name | Description | Pointer is set to | Observations | ||||||
---|---|---|---|---|---|---|---|---|---|---|
100
| Invalid message | The message is invalid, and no additional details are available for this error | Root of the message | This is the default error code for this class | ||||||
101
| Missing field | A required field is missing in the message | The pointer is set to the missing field | All requests | ||||||
102
| Invalid domain for the value | The value is outside a defined list of acceptable values | The pointer is set to the invalid field | All requests | ||||||
103
| Malformed date | A field containing a date value cannot be properly converted | The pointer is set to the invalid field | I1/I2, I7/I8, I9/I10, I11/I12, I13/I14, I17/I18, E1/E2, E3/E4, E9/E10, E11/E12, E13/E14 | ||||||
104
| Not an integer | A numeric field contains a value that is not numeric | The pointer is set to the invalid field | I7/I8, E9/E10, E11/E12, E13/E14 | ||||||
105
| Field value length exceeded | A String field contains a value with too many characters | The pointer is set to the invalid field | All requests | ||||||
106
| Invalid pattern | A String field does not match the pattern for the field defined in the XML Schema Definition of the message | The pointer is set to the invalid field | All requests | ||||||
107
| Invalid field | The specified field does not follow the order defined in the XML Schema Definition of the message | The pointer is set to the invalid field | All requests | ||||||
108
| Missing XML attribute | The specified XML tag is missing a required attribute (e.g. formatCode for all date fields) | The pointer is set to the invalid field | I1/I2, I7/I8, I9/I10, I11/I12, I13/I14, I17/I18, E1/E2, E3/E4, E9/E10, E11/E12, E13/E14 | ||||||
109
| Invalid XML attribute | The specified XML tag has an invalid attribute value (e.g. formatCode for all date fields) | The pointer is set to the invalid field | I1/I2, I7/I8, I9/I10, I11/I12, I13/I14, I17/I18, E1/E2, E3/E4, E9/E10, E11/E12, E13/E14 | ||||||
110
| Too many digits | The number has too many digits | The pointer is set to the invalid field | I7/I8, E9/E10 | ||||||
111
| Too much precision | The number has a decimal part with too many digits | The pointer is set to the invalid field | I7/I8, E9/E10 | ||||||
120
| Invalid eTIR specifications version | The version specified in the metadata fields is not the one(s) approved to function in the eTIR system | The pointer is set to the invalid metadata field | All messages | ||||||
151
| Condition C001 failure | The condition C001 is not satisfied | The pointer is set to the invalid field | I7/I8, I15/I16, E9/E10, E11/E12 | ||||||
152
| Condition C002 failure | The condition C002 is not satisfied | The pointer is set to the invalid field | I7/I8, I15/I16, E9/E10, E11/E12 | ||||||
153
| Condition C003 failure | The condition C003 is not satisfied | The pointer is set to the invalid field | I7/I8, I15/I16, E9/E10, E11/E12 | ||||||
154
| Condition C004 failure | The condition C004 is not satisfied | The pointer is set to the invalid field | I7/I8, I15/I16, E9/E10, E11/E12 | ||||||
155
| Condition C005 failure | The condition C005 is not satisfied | The pointer is set to the invalid field | I7/I8, I15/I16, E9/E10, E11/E12 | ||||||
156
| Condition C006 failure | The condition C006 is not satisfied | No pointer | This condition applies to all response messages | ||||||
157
| Condition C007 failure | The condition C007 is not satisfied | No pointer | This condition applies to response messages: E9/E10, E13/E14 | ||||||
158
| Condition C008 failure | The condition C008 is not satisfied | The pointer is set to the invalid field | I7/I8, E9/E10 | ||||||
159
| Condition C009 failure | The condition C009 is not satisfied | No pointer | This condition applies to response messages: E11/E12 | ||||||
160
| Condition C010 failure | The condition C010 is not satisfied | The pointer is set to the invalid field | I15/I16, E11/E12 | ||||||
181
| Rule R001 failure | The rule R001 is not satisfied | The pointer is set to the invalid field | I7/I8, I15/I16, E9/E10 | ||||||
182
| Rule R002 failure | The rule R002 is not satisfied | The pointer is set to the invalid field | I7/I8, I15/I16, E9/E10 | ||||||
188
| Rule R008 failure | The rule R008 is not satisfied | The pointer is set to the invalid field | I7/I8, I15/I16, E9/E10, E11/E12 | ||||||
190
| Rule R010 failure | The rule R010 is not satisfied | The pointer is set to the invalid field | I17/I18, E11/E12 | ||||||
194 | Rule R014 failure | The rule R014 is not satisfied | No pointer | I7/I8 | ||||||
195 | Rule R015 failure | The rule R015 is not satisfied | No pointer | I7/I8 |
2XX - Workflow errors
Error code | Error name | Description | Pointer is set to | Observations | ||||||
---|---|---|---|---|---|---|---|---|---|---|
200
| Invalid state | The state of an internal object is invalid, and no additional details are available for this error | Root of the message | This is the default error code for this class | ||||||
201
| Invalid guarantee status | The guarantee is not in a state that allows to perform the required operation | Root of the message | I1/I2, I9/I10, I11/I12, I13/I14 | ||||||
203
| Guarantee not cancellable | The guarantee is not in a state that allows to cancel it | Root of the message | E3/E4 | ||||||
204
| Guarantee already registered | The guarantee has already been registered | Root of the message | E1/E2 | ||||||
205
| Guarantee already cancelled | The guarantee is already cancelled or the request to cancel it has already been sent | Root of the message | E3/E4 | ||||||
210
| Operation already started | The operation is already started | Root of the message | I9/I10 | ||||||
211
| Operation already terminated | The operation has already been completed | Root of the message | I11/I12 | ||||||
212
| Operation already discharged | The operation is already discharged | Root of the message | I13/I14 | ||||||
213
| Operation not yet started | The operation is not yet started | Root of the message | I11/I12, I13/I14, E11/E12 | ||||||
214
| Operation ID already registered | The "refusal to start" is an operation on its own and must have a unique operation ID | Root of the message | I17/I18 | ||||||
215
| Operation sequence already registered | The "refusal to start" is an operation on its own and must have a unique operation sequence | Root of the message | I17/I18 | ||||||
216
| Refusal to start not authorized | The "refusal to start" cannot be performed because of the current guarantee status or because it is the first operation for this transport | Root of the message | I17/I18 | ||||||
220
| Declaration not yet received | The operation cannot be started because the declaration was not received | Root of the message | I9/I10 | ||||||
299
| Duplicate message | The same message was already received from the same source | Root of the message | I9/I10, I11/I12, I13/I14 |
...