Inbound Filing Response Processing
The government system authenticates, validates the EDI and processes it. The government responds back with success, failure, and warning messages. Inbound filing responses are modeled in Global Trade Management Cloud as tracking events. This allows filing responses, after entering Global Trade Management Cloud, to trigger notification or workflow, such as updating the statuses of the filing, updating the declaration with response codes and confirmation numbers such as the ITN.
The filing responses can enter Global Trade Management Cloud via a variety of integration mechanisms such as the standard XML integration, web services, or data queues. AES uses EDI-formatted filing responses and interfaces with GLN based on the communication method used for filing.
- Global Logistics Network: Descarte’s GLN receives the EDI Response from AES system which it sends back to (gtm.integration.aes.servlet.AESFilingResponseServlet) HTTP servlet in Global Trade Management Cloud. Customer must provide the HTTPS servlet URL, user name, and password to GLN so that GLN can configure to forward the response from AES to Global Trade Management Cloud. Descarte can configure these details in GLN as one time setup.
Tracking Event Processing
Global Trade Management Cloud ships with an automation agent for processing filing responses. The automation agent PROCESS CUSTOMS FILING RESPONSE V1 of type TRACKING EVENT is triggered when a new tracking event enters the system, or if an existing tracking event is re-processed. The automation agent, when triggered, attempts to match the tracking event to a filing document. If the matching is successful, the automation agent updates the status on the document according to the filing response status. The automation agent by default is not active. It is recommended that you use this automation agent as a template, to create your own automation agents to process filing responses.