Skip to main content

Error codes

NCTS error codes

The following error codes can be returned by the NCTS.

Value Description Explanation Transition period applicablility
12 Codelist violation

The value of a data item is outside the predefined set of values, that is, not part of the applicable business or technical codelist.

Example: The data element with CL027 (‘0’ or ‘1’) includes the value ‘2’. It violates the CL027.

  • During

  • After
13 Condition violation (missing)

A condition (Cxxxx or Txxxx) is violated due to missing data group or data item is missing (while “R”).

Example: Violation of C0569 - Declared number of seals is “2” and no seals are declared.

(IF /*/GoodsShipment/Consignment/TransportEquipment/numberOfSeals is GREATER than “0”

THEN /*/GoodsShipment/Consignment/TransportEquipment/Seal = “R”

ELSE /*/GoodsShipment/Consignment/TransportEquipment/Seal = “N”.)

  • During

  • After
14 Rule violation

A rule (Rxxxx or Txxxx) is violated and consequently a data group or a data item includes an invalid value.

Example: Violation of R0007 - The first declared Goods item number is 2.

(Each <GOODS SHIPMENT - GOODS ITEM.Goods item number> is unique throughout the declaration. The items shall be numbered in a sequential fashion, starting from “1” for the first item and incrementing the numbering by “1” for each following item.)

  • During

  • After
15 Condition violation (not allowed)

A condition (Cxxxx or Txxxx) is violated and consequently a data group or data item is present despite it shall not be present (it is present while “N”).

Example: Violation of C0569 - Declared number of seals is ‘0’ and seals are declared.

(IF /*/GoodsShipment/Consignment/TransportEquipment/numberOfSeals is GREATER than “0”

THEN /*/GoodsShipment/Consignment/TransportEquipment/Seal = “R”

ELSE /*/GoodsShipment/Consignment/TransportEquipment/Seal = “N”)

  • During

  • After
26 Duplicate Message ID The message includes the same ‘Message identifier’ as another message already received and processed.

  • During

  • After
50 Transitional constraint Violation

A transitional constraint (Exxxx or Bxxxx) is violated. A data group is missing or too many repetitions are in the message. A data item is missing or is present despite it may not be present, or a data item includes an incorrect value (including violation of the format).

Example: Violation of E1108 – Declaration with 10.000.000 packages.

(IF <Decisive Date> is LESS than or EQUAL to <TPendDate>

THEN /*/ExportOperation/totalNumberOfPackages

format shall be set to n..7)

  • During

  • After
51 EDI violation post downgrade After the ‘downgrade’ conversion (from ‘Legacy’ to ‘To Be’) the EDIFACT message is syntactically incorrect (a CD906C is generated and sent back to the application that initiated the conversion).

  • During
52 Functional violation post downgrade

After the ‘downgrade’ conversion (from ‘Legacy’ to ‘To Be’) the EDIFACT message is semantically incorrect:

  • FMS (sequencing, optionalities, repetitions, formatting) is violated

  • Business Validation (Rxxx, Cxxx or TRxxxx and Codelist validation) is violated

  • During
90 Unknown MRN

A message is received with MRN unknown to the destination (exception is the IEx01 messages concerning movement creation). To be used only when there is no ‘negative response’.

Example: The CDx02C is received and MRN is unknown, it must be responded with negative CDx03C; not with CD906C.

But: If a message CD115C is received and MRN is unknown, it must be responded with a CD906C with code “90”.

  • During

  • After
92 Message out of sequence

The message cannot be processed, because the receiver’s states machine is not in the state that does not allow to process the received message.

Example: The NTA (office of departure) receives the message CD018C while the movement is still in the state ‘Under control’.

  • During

  • After
93 Invalid MRN

The message includes a value for the data item <MRN> that violates the structure defined in the DDCOM.

Example: The ‘Check digit’ is not valid.

  • During

Note: Messages such as IE906 and IE917 that reports functional errors or errors in XML are not supported in NCTS Phase 5. Please ensure the correct environment is being used to test your system.

Business rules

Name Code Definition

Capabilities Validation

BR20004

Capabilities Validation - This rule is checking whether the Holder of Transit Procedure has the capability to submit a Transit Declaration

Error Code 12

Rule ID BR20004

Representation Validation

BR20005

Representation Validation - This Rule is checking whether the Representative has the capability to Represent the Holder of the Transit Procedure

Error code 12

Rule ID BR20005

LRN Uniquenes Validation

BR20006

LRN Uniquenes Validation - This Rule is checking LRN Uniquenes.

If no LRN exist in the Transit Declaration

Error code 13

Rule ID BR20006

If LRN already exists

Error Code 14

Rule ID BR20006