Troubleshooting Process

When filing your export data with AES, you will receive a response. If your filing is correct and includes all the required data in the proper format, AES will accept the filing and send back a response code and an ITN which is your confirmation number. If there is a problem with your submission and it is not accepted, you will need to troubleshoot the issues, make changes and retransmit your data to AES.

There are a few things you can do when troubleshooting an issue:

  • If there is an issue, AES will send back a response code and severity related to that code. To find more detail about a response code and how to resolve the corresponding issue, you can refer to the ‘Appendix A – Commodity Filing Response Matrix’ document which is available on the Customs and Border Protection (CBP) website. This document includes details for each response code including the severity, the reason you received the response code, and the resolution.
  • The "ANSI X-12: 601 – Export Shipment Information" document is the EDI specification which CBP uses to support electronic filing of data. This EDI implementation guide provides the details of the data which CBP wants to be submitted for export filing with AES. This document is available on the CBP website.
  • The "GTM - AES X12 601 Mapping.xlsx" document provides the details of how the data which needs to be filed with AES is mapped to Global Trade Management Cloud. You can see the data element from the ‘ANSI X-12: 601 – Export Shipment Information’ document, where the data resides in the Global Trade Management Cloud database, and where the data should be entered on the Global Trade Management Cloud user interface.
  • As part of troubleshooting, these three documents can be used together to determine what the issue is, how to resolved it, and where the data resides in Global Trade Management Cloud. For example, you submit a filing to AES from Global Trade Management Cloud. You receive a response back from AES with a response code of 116. You do not receive back the ITN. To troubleshoot this, you can:
  • Look up Response Code 116 in the "Appendix A – Commodity Filing Response Matrix" document provided by CBP. This document shows the following: This image shows an explanation of Response Code 116 which can be used for troubleshooting.
  • If you are looking for more detail about the Related Company Indicator, you can refer to the "ANSI X-12: 601 – Export Shipment Information" document and search for "Related Company Indicator". This document shows the following:This image shows an excerpt from the ‘ANSI X-12: 601 – Export Shipment Information’ document which describes the ‘Related Company Indicator’.

    You can see that AES wants to know if ‘…during the fiscal year, either the USPPI or foreign ultimate consignee reported, owned 10% or more of the other’s voting securities’.

  • If you want to see where this data resides in Global Trade Management Cloud, you can use the "GTM – AES X12 601 Mapping.xlsx" document. In this document, search for "Related Company Indicator". This document shows the following:This images shows an excerpt from the ‘GTM – AES X12 601 Mapping.xlsx’ document. Specifically the entry for ‘Related Company Indicator’.

When you do this search, you can see that AES expects this data to be sent in the BA101 element. There are two possible codes: “N” – NO Companies are NOT related or “Y” – YES Companies related. You can also see that this data should be populated on the Declaration as a remark with a qualifier of ‘RELATED COMPANY’. You can verify if the ultimate consignee is related to the USPPI, add this data to Global Trade Management Cloud and retransmit to AES.

For a copy of either the ‘ANSI X-12: 601 – Export Shipment Information’ and ‘Appendix A – Commodity Filing Response Matrix’ documents, please go to the CBP website at http://www.cbp.gov. For a copy of the ‘GTM – AES X12 601 Mapping.xlsx’ document, please go to My Oracle Support and refer to the Oracle Transportation Management and Global Trade Management Version 6.x Documentation and Training Resources (Doc ID 796594.1) note.