KCT-17538

C.O Port Codes Enhancement

What’s Existing:

When Shipments are pushed from Customs Management, leading zero(s) of Port Codes are not being sent in shipment XML. Due to this, the port code values are not being persisted in Control Tower as they are not meeting the requirements of standard length which is 4 digits for D codes and 5 digits for K codes.

What’s New:

Control Tower verifies if the values of the below listed fields meet the requirements of standard length.

If they do not meet the requirements, leading zero(s) will be added to the Port Codes at the time of conversion by WSO2 (shipment XML to Customs XML).

Below are few examples of how leading zero(s) are added during conversion process by WSO2:

D Codes:

•<distPortEntry>401</distPortEntry> converted to <PortOfEntry>0401</PortOfEntry>

•<distPortEntry>1001</distPortEntry> as is <PortOfEntry>1001</PortOfEntry>

K Codes:

•<PortLading>3504</PortLading> converted to <PortOfLading>03504</ PortOfLading>

•<PortLading>57035</PortLading> as is < PortOfLading>57035</ PortOfLading>

KCT-17544

DM Integration Enhancement

What’s Existing:

When document index notifications are pushed from Customs Management, Control Tower has been receiving few index files that are not related to any shipment.

The non-shipment index files are being piled up in the folder and WSO2 is trying to reprocess them which is slowing down the processing of shipment related index XML files.

What’s New:

When Control Tower receives index XML files that are not related to any shipment, they will be moved to a separate folder.

Control Tower considers non-IE file type code indexes as non-shipment indexes when references are not available in the indexing XML.

Below are two such examples of non-IE type code indexes:

•<FileTypeCode>IC</FileTypeCode>

•<FileTypeCode>IV</FileTypeCode>