AES Filing EDI Document Shows First Characters Of SCAC Code GID Instead of XID (Doc ID 2045500.1)

Last updated on JULY 20, 2024

Applies to:

Symptoms

When using an AES filing EDI document from a customs shipment related to a trade transaction, having the EDI field of a specific width, the document shows the first letters of the GID, instead of the XID.

The issue can be reproduced at will with the following steps:

Set the below properties:
gtm.aes.param.P_ALLOW_ALTERNATE_CODE_TYPE=YES
gtm.aes.param.P_CLASSIFICATION_CODE_TYPE=HTS US
gtm.aes.param.P_REPORTING_CURRENCY=TOTAL VALUE
gtm.aes.param.P_REPORTING_QUANTITY=ORDERED
gtm.aes.param.P_REPORTING_REFERENCE_NUMBER=BN
gtm.aes.param.P_REPORTING_TIMEZONE=US/Eastern
gtm.aes.param.P_IS_PRODUCTION=T
gtm.aes.param.P_TRANSMITTER_ID=999999999
gtm.aes.param.P_FILER_ID=999999999
gtm.aes.param.P_COMMUNICATION_PASSWORD=XXXXX
glog.reqdoc.reqdocCallbacks.AES_FILING=gtm.server.agent.business.transaction.AESFilingCallback

You can see the document that has been created by following the below steps:

1. Go to Trade Compliance Management, Trade Transaction, input the ID and press Search
2. Right click on it and go to View Related Customs Shipments
3. Edit it and go to Documents tab
4. Edit the document
In the BA1 section the SCAC Code is represented by the first characters from SCAC Code GID, instead of SCAC Code XID.

Cause

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