My Oracle Support Banner

AES Filing Response Not Updating on Custom Declaration Due to Document Tracking Number Mismatch (Doc ID 2667273.1)

Last updated on MAY 06, 2020

Applies to:

Oracle Customs Management Cloud Service - Version 20.1 and later
Oracle Trade Compliance Cloud Service - Version 20.1 and later
Oracle Global Trade Management Cloud Service - Version 20.1 and later
Information in this document applies to any platform.

Symptoms

Document Tracking Number mismatch between Declaration Document and AES Response XML. This is causing AES Filing Response not updating on Custom Declaration.

The 'DOCUMENT_TRACKING_NUM' on the Document does not match with the Document Tracking Number on the AES XML. Since the AES response comes with the Tracking number from the AES XML, the matching does not happen with the document.

EXAMPLE:
---------------
Declaration: D-0000001
Document: <Domain_Name>.D-0000001-AES_FILING-0003
DOCUMENT_TRACKING_NUM: 116003

The AES XML shows
P_DOCUMENT_TRACKING_NUMBER>116004

Both are mismatching, which is causing issue, due to which the AES responses are not updated on the declaration.
NOTE: This issue ONLY happens when you run the 'Generate Document' UI action on the Declaration level.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.