Tips on How to Resolve AES Fatal Errors

April 19, 2013

AES Broadcast #2013031

Tips on How to Resolve AES Fatal Errors
FEF

  

 

 

 

Fatal Error Response Code: 128







 

 

Fatal Error Response Code: 632





When a shipment is filed to the AES, a system response message is generated and indicates whether the shipment has been accepted or rejected. If the shipment is accepted, the AES filer receives an Internal Transaction Number (ITN) as confirmation. However, if the shipment is rejected, a Fatal Error notification is received.

To help you resolve AES Fatal Errors, here are some tips on how to correct the most frequent errors that were generated in AES this month.

 

 

Narrative: Port of Export Unknown

Reason: The Port of Export Code reported is not valid in AES.   

Resolution: The Port of Export Code must be valid in AES.  Valid Port of Export Codes reportable in AES are contained in Appendix D -  Export Port Codes.

Verify the Port of Export Code, correct the shipment and resubmit.   

 

Narrative: 2nd Unit of Measure Code / Schedule B/HTS Mismatch

Reason: The Unit of Measure reported for the 2nd Quantity does not match the Unit of Measure for the 2nd Quantity required for the Schedule B/HTS Number reported. 

Resolution:  Each Schedule B/HTS Number has a predetermined unit(s) of measure to describe quantities.  The unit(s) reported must match exactly those unit(s) prescribed by the Schedule B/HTS Number reported.