12
Description:
Codelist violation
Explanation:
The value you entered is not part of the required business or technical codelist.
For example, a field that only allows the values 0 or 1 (CL027) contains 2.
Step-by-Step Solution:
Review the data element triggering the error.
Check the required codelist for allowed values.
Replace the invalid value with one from the approved list.
Validate the declaration again.
Resubmit.
13
Description:
Condition violation (missing)
Explanation:
A mandatory data group or item is missing when it is required (“R”).
Example: Declared number of seals is 2, but no seals were actually declared.
Step-by-Step Solution:
Identify which required field or data group is missing.
Review the related condition rule (Cxxxx or Txxxx).
Add the missing mandatory data.
Validate your declaration.
Resubmit.
14
Description:
Rule violation
Explanation:
A rule (Rxxxx or Txxxx) is violated, causing an invalid value.
Example: First goods item number is 2 — item numbering must always start at 1 and increase sequentially.
Step-by-Step Solution:
Check the rule being violated.
Verify numbering or values for each goods item.
Correct the invalid value or sequence.
Validate the declaration.
Resubmit.
15
Description:
Condition violation (not allowed)
Explanation:
A data element is present even though it must not be present (“N”).
Example: Declared number of seals is 0, but seals are included anyway.
Step-by-Step Solution:
Check which field is incorrectly included.
Review the related condition rule (Cxxxx or Txxxx).
Remove fields that must not be declared.
Validate the declaration.
Resubmit.
26
Description:
Duplicate Message ID
Explanation:
The message identifier has already been used in a previously processed message.
Step-by-Step Solution:
Check the Message ID used in the submission.
Generate a new unique Message ID.
Resubmit with the corrected ID.
50
Description:
Transitional constraint violation
Explanation:
A transitional constraint (Exxxx or Bxxxx) is violated — missing groups, too many repetitions, incorrect values, or format errors.
Example: Declaration includes 10,000,000 packages, which exceeds allowed format.
Step-by-Step Solution:
Review the transitional rule specified.
Correct missing or excessive data groups.
Ensure values meet the allowed format.
Validate all fields again.
Resubmit.
51
Description:
EDI violation post downgrade
Explanation:
After conversion from Legacy → To-Be, the EDIFACT message is syntactically invalid.
Step-by-Step Solution:
Review the downgraded EDI message.
Correct syntax issues flagged by CD906C.
Regenerate the EDI file.
Resubmit.
52
Description:
Functional violation post downgrade
Explanation:
After the downgrade conversion, the message is semantically incorrect (e.g., formatting, sequencing, business rules, codelist issues).
Step-by-Step Solution:
Identify the violated rule (Rxxx, Cxxx, TRxxxx).
Correct semantic or business logic errors.
Validate the updated message.
Resubmit.
90
Description:
Unknown MRN
Explanation:
The MRN does not exist for the destination. Used only where no negative response exists.
Step-by-Step Solution:
Recheck the MRN entered.
Confirm movement exists in the system.
Correct any typing errors.
Resubmit with a valid MRN.
92
Description:
Message out of sequence
Explanation:
The message cannot be processed because it is not expected in the current state.
Step-by-Step Solution:
Identify the current movement state.
Verify whether the message type is allowed at this stage.
Wait for or trigger the required preceding messages.
Resubmit the correct message in sequence.
93
Description:
Invalid MRN
Explanation:
The MRN format is invalid — for example, incorrect check digit.
Step-by-Step Solution:
Verify the MRN structure against the NCTS format.
Recalculate or confirm the MRN check digit.
Correct any formatting errors.
Resubmit.
Business Rules
BR20004 — Capabilities Validation
Definition:
This rule checks whether the Holder of the Transit Procedure has the capability to submit a Transit Declaration.
Related Error Code: 12
Rule ID: BR20004
BR20005 — Representation Validation
Definition:
This rule checks whether the Representative has the capability to represent the Holder of the Transit Procedure.
Related Error Code: 12
Rule ID: BR20005
BR20006 — LRN Uniqueness Validation
Definition:
This rule validates the uniqueness of the Local Reference Number (LRN) in a Transit Declaration.
If no LRN exists:
Error Code: 13
Rule ID: BR20006If the LRN already exists:
Error Code: 14
Rule ID: BR20006
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article