BluJay Solutions Parcel 21.1.0 - User Guide

Error Message

Description

Missing customer id

Customer id is blank or null in request.

Note: Only used if hosted mode of operation.  Not applicable in on-premise mode of operation

Missing owner id

The ownerId tag is blank or missing from the request.  This is the division, DC (location), company, or other terminology used for this purpose.

Missing transaction reference

The Transaction ref is blank or null.

Missing source app

The Source application is blank or null.

Missing time

The Time is  blank or null

Note: When sending a request via OL, this field is auto-populated so should not generate this error.

Missing submission type

Customs message submission type is blank or null.

When sending via OL, this will be automatically set based on the country of Export so should not generate this error.

Missing country of despatch code

Country of dispatch code is blank or null.

Filing cannot occur via CFM without this element.

When sending via OL, this field is populated from the Exporter Address country code.

Shipment owner id doesn't match the owner id in the header

Shipment payloads owner id does not match the owner id in the header of the request.

Note: You must make sure that both of these owner ids  match.

Shipment transaction reference doesn't match the transaction reference in the header

Shipment transaction reference does not match the transaction reference in the header of the request.

Note: You must make sure that both of these transaction reference tags match.

Unsupported customs filing action <ACTION_NAME>

Unsupported filing action for the country of dispatch (origin) has been sent.  You must send a valid filing action that is supported for the country of dispatch.  For example if the country of dispatch is US, the valid filing actions are FULLDEC or REPLACEDEC.

Invalid customs filing action <ACTION_NAME>

Invalid customs filing action.  The filing action you have sent with the request is not a recognized value from the available values of CFM.Invalid customs filing action.  The filing action you have sent with the request is not a recognized value from the available values of CFM.

Country of despatch code <COUNTRY_CODE> is not supported

Unsupported country of dispatch code Country Code.

The country of dispatch code specified is not supported at this time for CFM.  You must specify a valid supported code.  For Example US or PR.

Note: On the OL this is taken from the Exporter Address country code.

Submission type <TYPE> not supported for country <COUNTRY>

The submission type is not supported for the country of dispatch specified.

Note: On OL this is automatically set, so should not generate this error.

Invalid XML

Any of these tags have not been specified: ExportCustomerDetails, ExportCustomsMessageHeader leaving the XML for the request invalid.

Empty or malformed Shipment

No Shipment provided (<Shipment> tag not included in the request) or malformed xml.

Empty or malformed ExportCustomsMessageHeader

No ExportCustomsMessageHeader provided (<ExportCustomsMessageHeader> tag not included in the request) or malformed xml.

Failed to set the selectors on message <SELECTOR>

Error setting the properties to identify a message in the submission list

Note: If you receive this error message, you need to check the CFM error logs to see what is going wrong.

Error adding the message to the submission list <SELECTOR>

Message couldn't be added to the submission list

Need to check the CFM error logs to see what is going wrong.

Missing configuration file for customer id <CUSTOMER_ID>

Configuration file customerid.xml not found.

This is for hosted mode of operation only, when a customer ID is sent within the request that does not exist.  In on-premise mode this should not happen unless someone deletes the default configuration file.  If this happens, the system will report this error using a customer ID of '”defaultcustomer.”

Missing configuration for customer id <CUSTOMER_ID>

Configuration file contains no configuration at all (config=null). When a customer ID is sent within the request but the customer’s configuration is incomplete or in on-premise mode of operation, the default customer configuration file has been edited and sections incorrectly removed.

Invalid XML in the configuration file for customer id <CUSTOMER_ID>

Error parsing the configuration file for the customer (or the default configuration file for on-premise mode).

Error parsing configuration file: customer id mismatch

Configuration file doesn't contain attribute: customerId="CUSTOMERID"

Error with the configuration file for the customer, or default configuration file in on-premise mode.

Unable to initialize configuration file parser

Error initializing the parser. Could not read file.

Note: This is a serious error; check CFM error logs

Missing drop location

The configuration's drop location for AES filing is missing from the configuration.  The configuration for the customer or the default configuration for the system needs to be reviewed.

Note: This is for AES filing only for US exports.

Missing return location

The configuration's return location for AES filing is missing from the configuration.  The configuration for the customer or the default configuration for the system needs to be reviewed.

Note: This is for AES filing only for US exports.

Invalid drop location

The drop location for AES filing is invalid as specified in the configuration.  The configuration for the customer or the default configuration for the system needs to be reviewed.

Note: This is for AES filing only for US exports.

Invalid return location

The return location for AES filing is invalid as specified in the configuration.  The configuration for the customer or the default configuration for the system needs to be reviewed.

Note: This is for AES filing only for US exports.

Error performing validation

The System could not find or run the AES validation routine.  Check the error logs for issues.

Failed to write EDI drop file

The system could not send the AES file to the drop location for the configuration.  This could be due to the system not being able to see or have access to the configured drop location.

Error Message

Description

Missing or Invalid Related Company - value must be Y or N

None.

Missing or Invalid Mode of Transport - value must be one of A,AC,S,SC,SB,R,RC,J,JC,M,AU,P,H

None.

Missing or Invalid Country of Destination

None.

Missing Transaction Reference

None.

Missing or Invalid Vessel Flag (required for MOT S,SC,SB)

Only if mode of transport is Sea.

Missing or Invalid VesselBookingNumber (required for MOT S,SC,SB)

Only if mode of transport is Sea.

Missing or Invalid US State Of Origin

None.

Missing or Invalid SCAC Carrier Code

Only for non air modes of transport.

Missing or Invalid IATA Carrier Code

Only for air modes of transport.

Missing Conveyance

None.

Missing or Invalid RZWaiver - value must be Y or N

None.

Missing or Invalid QQHazmat - value must be Y or N

None.

Missing or Invalid Departure Date (YYMMDD)

None.

Missing or Invalid Port Of Loading

None.

Missing or Invalid Port Of Discharge

Only for Sea modes of transport.

Invalid InbondType - value must be one of 36, 37, 62, 63, 67, 68, 70

None.

Missing Entry Number for Inbound shipment

Only when inbondtype is 36, 37, 62, 63, 67 or 68.

Invalid Routed Transaction - value must be Y or N

None.

Foreign Trade Zone (FTZ) not specified for Inbound type 67 or 68

Only when inbondtype is 67 or 68.

Missing VID Equipment Initial

Only if used vehicle records provided.

Missing VID Equipment Number

Only if used vehicle records provided.

Missing or Invalid Party Type - value must be one of EX,CN,IC,FW

None.

Missing Exporter (USPPI)

None.

USPPI is missing required information: Party Name, Party IDType (24 or ZZ), Party IDNumber, Contact FirstName, Contact LastName, Contact Phone, Address Line1, City, State Code, Zip Code and Country Code are required

None.

Missing Consignee

None.

Consignee is missing required information: Party Name, Address Line1, City and Country Code are required

None.

US Forwarder is missing required information: Party Name, Party IDType (1 or ZZ), Party IDNumber, Contact FirstName, Contact LastName, Contact Phone, Address Line1, City, State Code, Zip Code and Country Code are required

Only if a Forwarder address is supplied.

Consignee is missing required State Code information

None.

Invalid Country Code for party type: xx

None.

Invalid State Code for party type: xx

Only if party country is US or MX.

Invalid Zip Code for US party type: xx

Only if party country is US.

No commodity lines - at least one is required

None.

Missing or Invalid Commodity Type - value must be A or B

None.

Commodity is missing required information: Line No, Commodity Code, Quantity/UOM, Declared Value/Currency, and Description are required

None.

Missing or Invalid commodity origin: (F)oreign or (D)omestic

None.

Missing or Invalid weight code - AES only supports K for Kilograms

None.

Missing or Invalid Reporting Quantity

None.

Missing or Invalid Gross Weight

None.

Gross Weight is less than the reported quantity

Only when reported quantity UOM is KG.

Invalid License Qualifier - if set; valid values are 1 or 2

None.

Licence exemption indicator must be '2' when the license type is 'S00', 'SCA' or 'SAG'

None.

Licence exemption indicator must be '1' unless license type is 'S00', 'SCA' or 'SAG'

None.

Invalid ECCN number (format: NANNN)

If Export License type is not "E01" and ECCN is not "EAR99".

Missing or Invalid Export Info Code

None.

Missing or Invalid First UOM Code

None.

Missing or Invalid Second UOM Code

None.

Missing or Invalid Commodity Code (type A)

When using HTS codes.

Missing or Invalid Commodity Code (type B)

When using Schedule B codes.

Commodity and First UOM Code mismatch

None.

Commodity and Second UOM Code mismatch

None.

Missing or Invalid Export License Type

None.

Invalid DDTC USML Category

Only if items fall under Directorate of Defense Trade Controls (DDTC) categories.

Invalid DDTC UOM Code

Only if items fall under Directorate of Defense Trade Controls (DDTC) categories.

Invalid DDTC Quantity

Only if items fall under Directorate of Defense Trade Controls (DDTC) categories.

SCA - Canadian ITAR Exemption Scenario requires country of destination 'CA'

License type code SCA only applicable if country of destination is Canada.

ITAR export licence number missing or invalid

When export license type code is one of following: S05, S61, S73, S85, S94.

Message Type

Message

Special Circumstances

Warning

The despatch date has passed

None.

Warning

Requires confirmation that the XX party country is US

Blank country code on a party.

Information

Declared Value less than minimum value

None.

Exemption Code

Condition

NOEEI 30.36

Country of destination and consignee country code are Canada (CA) and no commodities require a license. For example, no DDTC fields are populated, ECCN is EAR99 and license type is C33, and license number is NLR or blank/null.

NOEEI 30.37(a)

No commodities require a license. For example, no DDTC fields are populated, ECCN is EAR99 and license type is C33, license number is NLR or blank/null, and the total declared value for all commodities reported in submission is less than $2500 USD.