customs management u.s.€¦ · what's new customs management version 19.2.2 customs...

Customs Management U.S.

Release Notes

Customs Management

Release: 19.2.2 Date: August 30, 2019

© 2017-2019 BluJay Solutions Ltd. All rights reserved.

DISCLAIMER This document is the property of BluJay Solutions and the information contained herein is confidential. This document, either in whole or in part, must not be reproduced or disclosed to others or used for purposes other than that for which it has been supplied without BluJay Solutions’ prior written permission, or, if any part hereof is furnished by virtue of a contract with a third party, as expressly authorized under that contract.


Table of Contents

1. What's New Customs Management Version 19.2.2 ...................... 4

2. Important Documentation Notes ................................................. 4

3. Alerts, Requirements, Updates & Notes ....................................... 5

4. Customs-Centric TMFF – CM-US – Sage Integration ..................... 5

5. Other Features and Enhancements - Summary ............................ 6

6. Defect Fixes and Minor Compliance Updates ................................ 9


What's New Customs Management Version 19.2.2

Customs Management Version 19.2.2 includes the following:

Important Documentation Notes

Instructions for Entering Section 301 and 232 Tariff

Requirements

▪ The following document is being distributed to customers: "Instructions for

entering section 301 and 232 tariff requirements within Customs Management – US version 19.0.1.2 or higher".

▪ This document provides information on the order of the tariffs and where the values and weights are inputted on several Trade Remedy scenarios based of

the information released in CSMS #18-000624. It also provides some troubleshooting hints for discovering why the duty may not be calculating

correctly.

SQL Scripts and Excel Release Notes

The following are recent updates to the CM-US documentation:

• Release Notes for both Epic/Story Jiras (New Features and Enhancements) and Bugfix Jiras (Defect Fixes and Minor Compliance Updates) are now available in

Excel spreadsheet format by clicking the following link:

CM-US_1922_Release_Notes.xls

Additional Considerations for the Excel Release Notes:

o Excel must be installed on the machine running the CM-US application in

order to download or open the Excel file.

o Due to restrictions on the server running the Help, the Excel file is in the

older .xls format.

• Additional documentation notes:

o A new set of Help topics under "Processing an In-Bond shipment" is added

under Features > In-Bond. These are converted and updated from the

older, legacy KC Help linked to from the Accessing Help topic.

o Salesforce Customer Case ID Numbers are added to Release Notes for

which this information is available.

Links to documents referenced here can be found in the “What’s New?” Help.


Copyright

Please note that the Copyright and Trademarks topic is now moved to a

position following the "Features" section.

Alerts, Requirements, Updates and Notes from Previous

Releases

When the following Security Preference is not set manually, the associated

CM-US functionality behaves as though it were set with a value of "Y": ALLOW_ES_SEND_FOR_AUDIT_FATAL. This enables an ES message to be

sent to Customs even it if includes Fatal Validation warnings. To disable this functionality so as not to send ES messages with Fatal warnings, this

Preference must be manually set to "N". For more information on the logic behind this functionality, see the following Release Notes for earlier CM-US

versions:

• Version 4.0.0 (Internal ID KECI-881)

• Version 4.2.0 (Internal ID KECI-881)

The following Alerts, Requirements, Updates and Notes can be found in the

Help topics and Release Notes for the previous CM-US releases:

• Enhanced Credit Checking

• Changes to ACE RM Transaction for ACH Payment Authorization

• CM-US/Sage Integration – Customer and Vendor CSV for Sage

• CM-US\TMFF Integration – Duplicate Customers and Vendors

• New Alternate Billing XML Extract

• New Alternate Shipment XML Extract

• New Add/Update ABI Importer 5106 Functionality

• New Validation (89358 - "Section 301 Trade Remedies")

• Changes to CATAIR Chapters for Daily and Monthly Statements

• Changes to Disposition Codes

• Steel and Aluminum Tariff Exclusions

• Important Standalone ISF Notice

• ACE Reconciliation Go-Live

• NMFS - Seafood Import Monitoring Program (SIMP) Trade Policy Updates

• Important Alerts, Notices and Notes from Previous Release (v17.2.2)

Customs-Centric TMFF – CM-US – Sage integration

Overview

CM-US is now integrated with both the BluJay Solutions Transportation Management (TMFF) system and the Sage Accounting System. This is the


Customs-centric solution for companies whose business is focused on Customs work. CM-US can now be used in conjunction with either one or

both of these systems. For more information on the details of this

integration, see the following Help topics:

• Under Previous Releases – Versions 18.2.1 - 19.0.2.

• Under Features > Extracts/Integration > TMFF-CMUS-Sage integration

o Overview

o Preferences and System Parameters

Sage-CM-US Integration

o Using Sage Integration

o Sage-CMUS Process Flow

TMFF-CM-US Integration

o Using TMFF Integration

o TMFF-CMUS Process Flow

o TMFF-CMUS Validations

• The TMFF Job Export and associated CM-US EDI Shipment XML are now included in the Process Queue under the Process Subtype Codes

SHIPMENT_TMFF and JOB_TMFF for Process Code EXTRACT. The following SQL script is updated to support this enhancement: PURGE_PARAMS-KEC-

18062.sql (Internal ID KEC-18062)

Important Note: See the following documents for detailed information on

setting up Customs-Centric TMFF/CM-US/Sage integration with the Accord

system that passes data to Sage:

• Vendor_Ad-Hoc_query_Create_csv_for_Accord

• Vendor_csv_Headings.xls

Other Features and Enhancements - Summary

Note: Internal IDs for this section are for Epics and Stories unless otherwise indicated. Where only the Story is listed, it is under the 19.2.2 Project Epic

KEC-20445.

ABI Processing

• An SE12 record is added to the SE message for an ACE Cargo release for

required Additional Bond data, effective September 21, 2019. (Additional Bond data is included when "9" is selected from the "Bond Type" drop-down list in the "Additional Bond" section on the Optional Data screen displayed by clicking

the Optional Data button in the button bar at the bottom of the Shipment Header.) A new Security Preference ACE_CR_SE12_EFFECTIVE_DT is provided

for this functionality. When this Security Preference is set to the effective date, the system inserts the SE12 record in the SE message with the data entered in the "Surety", "Producer Account" and "Bond Amount" fields (immediately


below the "Bond Type" drop-down) for all shipments with this data created on or after the effective date. the deployment date is not known at this time.

Therefore, we have set the Security Preference ACE_CR_SE12_EFFECTIVE_DT to 12/31/2099. Once CBP announces the deployment date, a Tech Alert will be

sent notifying clients of the effective date. Beginning on the effective date, the system will insert the SE12 record. The following SQL scripts are modified to

support this update:

o SECURITY_PREFERENCES-KEC-20455.sql

o PREFERENCE_KEYS-KEC-20455.sql

(Internal IDs KEC-20419 [Epic], KEC-20455 [Story])

• For an ACE Cargo Release Shipment with Entry Type 86 ("Section-86") and without PGA data, the system no longer includes the IOR (Importer of Record)

Type in positions 22-24 nor the IOR IRS No. in positions 25-36 of the SE10 record of the SE message. This information is not required in this case.

(Internal ID KEC-20439)

Extracts/Integration

• The system now correctly validates and displays errors for uploaded TMFF billing lines that use a charge code with a GL Number not set up in the GlOtherXRef table, if the Sage Accounting system is being used and the

preference REQUIRE_GL_OTHER_SETUP is set to Y. In this situation, when the user selects the Prepare Invoice check box on the Billing screen, the system

now displays the following error in a pop-up notification: "GL Code [Code Number] for Charge Code (N) not in GL Cross Reference." Previously, the system did not check to make sure the GL Numbers on Charge Codes for TMFF

Billing lines were set up in the GlOtherXRef table, resulting in TMFF Billing lines in the CM-US Billing XML being sent to Sage without the OtherComputerGlNo

from the Cross Reference table. (Internal ID KEC-19799 [Story])

• Leading zeroes are now removed from the value in the <ChrgCode> section

(under <ChargeCodeInformation>) of the TMFF Charge Extract XML. For example, if the figure in the "Charge" field on the Charge screen

(Maintenance > Reference > Billing > Charge) is 0020, this is rendered in the TMFF Charge Extract XML as <ChrgCode>20</ChrgCode>. (Internal ID

KEC-20402 [Story])

General/Infrastructure/Performance

• In compliance with COBRA User Fee Changes that go into effect on October 1,

2019, new records are created for the following User Fee Codes with a Date Effective of 10/01/19: 1, 41, 42, 50, 52, 54, 61, 63, 65, 72, 74, and 86. These

codes are listed with descriptions on the User Fees Reference screen (Maintenance > Reference > Import > User Fees Reference). See also the Release Note for the related Jira KEC-20523. The following SQL script is

modified to support this update: USER_FEE_RATES-KEC-20473.sql (Internal

ID KEC-20473)


Maintenance Screens

• Per CBP Guidance, the following updates are made to the values in the Tariff Calc Flags Maintenance table (Support > T > T-TE > Tariff Calc Flags) for

Tariff No. 9903.88.12 (Product Exclusions related to Chinese technology

transfer, intellectual property, and innovation):

o "Date Effective" 08/23/2018

o "Date Expiration" 07/31/2020

o "Tariff No Stop Four" 9903

o "Calc 99 Flag" S

o "Subject to 250 Limit" Check Box selected

o "Informal Restricted" Check Box selected

o "Group Processing" R

See the following CBP bulletin for more information on these exclusions:

"CSMS # - GUIDANCE: Seventh Round of Products Excluded from Section 301 Duties (Tranche 2)". The following SQL script is modified to support this update: TARIFF_CALC_FLAGS-KEC-20551.sql (Internal IDs KEC-20440 [Epic],

KEC-20551 [Story])

Partner Government Agencies

• A new General Preference AUTO_UPDATE_APHIS_COMMON_NAME is now available and works as follows when set to "Y". The "Specific" and "General"

fields in the Common Names section on the Product/Components sub-tab of the APHIS/Core tab on the Partner Government Agencies screen now allow users to enter names not included in the lists accessed by clicking the look-up

buttons [?]. If a user enters a name not in the existing list, the system now turns the field orange to indicate this but allows the value to be entered.

Additionally, the system adds this name to the corresponding database and pop-up list. CM-US now provides this enhancement because there exists no good official data source for these names. (Internal IDs KEC-20416 [Epic],

KEC-20415 [Story])

Reconciliation

• When a Customer is set up for any type of Blanket Reconciliation on the Recon sub-tab of the Customer Details Import Data tab, the system now

automatically flags that Recon type for that Customer on the Shipment Send screen, including the "Recon NAFTA" check box for all shipment types, manually created and with EDI Upload/Lights Out Entry/Hands-Free

Processing. (Internal ID KEC-20096; Case IDs: 02498562, 02498562)

Shipment Processing

• For Shipment Entry Type 86 ("Section-86") the system no longer returns Validation 1929 ("Line missing required entity info for ACE C/R") if the Buyer

(code "BY") is not specified for Release Type "ACE Cargo Release" in the Party


Role fields on the ACE Cargo Release and Line Parties pop-up screens. (These screens are displayed by clicking the Parties button in the button bar at the

bottom of the Shipment Header and the Parties button on the Commercial Invoice screen respectively.) A value for this Party Role is not required for this

Entry Type. The following SQL script is modified to support this update: ENTITY_CODES-KEC-20441.sql (Internal IDs KEC-20328 [Epic], KEC-20441

[Story])

• For Shipment Entry Type 86 ("Section-86"), the system now automatically selects the "Send As Planned Port" check box immediately beneath this field as

required for all Entry Type 86 shipments. Previously, the system returned Validation 1823 ("Send_As_Planned_Port of Shipment_Header must be Y") if

the user left this check box blank for this entry type and the Preference

DEFAULT_SEND_PLANNED_PORT was not set to "Y". (Internal ID: KEC-20438)

Defect Fixes and Minor Compliance Updates

This table lists the issue number and the category in which the release note

appears below this table. Scroll below this table to read the release notes.

Note: Release notes in this section include customer-reported issues, issues where SQL scripts are modified or created, performance issues and

requested documentation.

Inter-

nal

ID

Category

Summary

Description

Release Note

KEC-

19312

Ad-Hoc

Query

AdHoc -

ENTRY_NO_CONTROL - all

fields need to be added. There

are only two

now.

All the database fields are

now added to the Entry No Control folder under the

Shipment category in the Ad-Hoc Query (Tools > Ad-hoc

Query) Search tree. (Case

IDs: 02341806, TFS 155926)


Inter-nal

ID

Category

Summary

Description

Release Note

KEC-

19985

General/ Infrastructu

re/

Performance

Purge from SHIPMENT_HIS

TORY table is receiving java

error.

When the user selects Purge Type as “Purge History” on

the Import Purge Configuration screen

(Maintenance > System >

Import Purge Configuration), selects

Entry Type “01” (Consumption) and then

clicks the Purge Count button, the Results pop-up

dialog now correctly displays the purge count total

correctly without the system returning a Java error. This

issue is fixed. (Case IDs:

02491046, TFS 159841)

KEC-

20010

Extracts/

Integration

Don't attempt to verify that

GlOtherComput

erXref exists when verifying

Job XML data.

If the Preferences CMUS_TO_SAGE_ACCOUNTI

NG and

REQUIRE_GL_OTHER_SETUP are set to "Y", the system no

longer performs a Verification to determine

whether the GL Number (General Ledger Number) as

specified on the GL Other Computer Xref Maintenance

screen (Maintenance > Reference > Billing > Gl

Other Computer Xref) is set up for the Charge Code in

the TMFF Job Export XML. It will be checked when the

combined Bill is prepared.


Inter-nal

ID

Category

Summary

Description

Release Note

KEC-

20198

Shipment

Processing

ABI

Processing

Warehouse Re-Entry Not

Sending Est Entry Date in

11 Record.

For a Warehouse Re-entry shipment (Entry Type 22),

the system now sends a correctly calculated

Estimated Entry Date in the

AE message 11 record. Previously, this date was not

included, resulting in CBP rejection. This issue is fixed.

(Case ID: 237347)

KEC-

20269

Extracts/

Integration

Vendor

Integration Extract java

error to screen.

The Vendor Extract process

(Tools > Vendor Extract) now works correctly without

returning a Java error in certain circumstances where

the system was incorrectly processing the Vendor list.

This issue is fixed.


Inter-nal

ID

Category

Summary

Description

Release Note

KEC-

20270

Billing

Extracts/

Integration

Preparing Billing Invoice does

not trigger tracking

process queue

record for

Extracts.

Preparing a Billing Invoice now always results in a

record being added to the Process Queue (Tools >

Process Queue)

irrespective of the extract process by which a client is

billed, so that an extract is always sent to the billed

client after the bill is prepared. Previously, billing

via the ICC/SSO extract process was not being added

to the Process Queue, resulting in customers not

being billed for some invoices. This issue is fixed.

(Case IDs: 02496485,

02515232)

KEC-

20276

Extracts/

Integration

If allowEntry of

Vendor is not Y, we should

indicate that the vendor is

not active.

If the value for a Vendor in

the "Allow Entry" field on the Vendor Maintenance screen

(Support > V > Vendor) is not "Y", the system no

longer includes the <isActive> segment in the

TMFF extract XML created by selecting Tools > Vendor

Integration Extract, specifying Vendors, selecting

"TMFF Extract", and then clicking the Prepare

Extract(s) button to create

the extract or extracts.


Inter-nal

ID

Category

Summary

Description

Release Note

KEC-

20359

Extracts/

Integration

Charge Code fields changed

by TMFF user are not

updating CM-

US.

CM-US now updates Calculation Type, Unit of

Measure (UOM) and Biz Type based on the XML file

received from TMFF.

Previously, the system did not update these values in

this case.

KEC-

20360

Shipment

Processing

Validations

Validation 1420

Must specify payment due

date and/or type is firing on

section 321 ET 86 and it should

not be.

The system no longer

incorrectly returns Validation 1420 ("Must specify payment

due date and/or type") for Shipment Entry Type 86

(Section 321). Entry Type 86 does not require this

payment information. This issue is fixed so that this

Validation is not returned in this case. (Case ID:

2514061)

KEC-

20361

Forms/Repo

rts

When ADA and CVD are both

on a file, only the ADA is

printing in box 39 of the 7501;

both should be

printed.

All appropriate amounts are now printed in "Other Fee

Summary for Block 39" box on Form 7501, including

AntiDumping Assessment (ADA) and Countervailing

Duties (CVD). (Previously, only three lines were

printed.) This issue is fixed. (Case IDs: 02514380,

02514380)


Inter-nal

ID

Category

Summary

Description

Release Note

KEC-

20388

Recon-

ciliation

Tracing dates 94104, 94105,

94106 were created for

recon but not

added to Tracing_dates_

master.

The following Tracing Dates to indicate whether an EDI

uploaded file is Recon flagged were created but not

added to the Tracing Dates

Master Maintenance table (Support > T > TF-TZ >

Tracing Dates Master): 94104, 94105, 94106. These

Tracing date updates have been put on hold until

further analysis can be done. The existing EDI Recon

flagging process will not set the following EDI Recon

Flagged Tracing Dates until a

future release:

• 94009 ("Recon Value flag

manually set.")

• 94103 ("Recon NAFTA flag

manually set.")

• 94010 ("Recon 9802 flag

manually set.")


Inter-nal

ID

Category

Summary

Description

Release Note

KEC-

20394

Forms/

Reports

7501 not printing IOR or

Consignee information in

boxes 25, 26;

even though

input.

The Ultimate Consignee Name and Address now

prints in Box 25 and the Importer of Record Name

and Address now prints

correctly in Box 26 of Form 7501 ("Entry Summary").

Previously, nothing was being printed in Box 25 and

incorrect information was printed in Box 26. This issue

is fixed. (Case IDs: 2515283, 2515240, 2515278,

2515264)


Inter-nal

ID

Category

Summary

Description

Release Note

KEC-

20398

Forms/

Reports

FTZ Admission needs to write

data back to shipment

header and

shipment ids for printing/defaulti

ng elsewhere

For an FTZ Admission, the system now copies data from

the following FTZ Admission fields to the corresponding

fields on the Shipment

Header Maintenance screen (Support > S>

ShipmentA-ShipmentI >

Shipment Header):

• "Gross Weight" (FTZ

Commodities pop-up

screen) to "Weight Gross"

• "Trans. Mode" to "Mot"

• "Port of Unlading" to "Dist

Port"

• "Port of Lading" to "Port

Lading"

• "Importing Carrier" to

"Carrier"

• "Conveyance Name" to

"Vessel Airline Name"

• "Quantity" to "Piece Count"

• "Units" to "Uom Weight"

• "Export Country" to

"Country Export"

• "Control Weight" (same as

"Gross Weight") to "Weight

Gross"

• "Country of Origin" to

"Country Origin"

(Case ID: 02515186)


Inter-nal

ID

Category

Summary

Description

Release Note

KEC-

20399

Extracts/

Integration

VENDOR_TMFF xml Account tag

cannot be dependent on

Financial

System Account

No.

Previously, the <Accounts> tag section was missing from

the VENDOR_TMFF XML file if the "Forwarding Party ID"

field on the CM-US Vendor

screen (Maintenance > System > Vendor) was

filled in but the "Financial System Acct No." field was

blank. However, since inclusion of the <Accounts>

tag section should not depend on the value of this

latter field, this section is now part of every

VENDOR_TMFF XML file.

KEC-

20411

Forms/

Reports

Virgin Islands

require all printed 7501s

to be in tariff

number order under each

Commercial

Invoice.

Per requirements for

shipments with a Virgin Islands connection, the

system now prints the Tariffs

in the Tariff Lines from the Commercial Invoice in

numerical order on Form

7501.


Inter-nal

ID

Category

Summary

Description

Release Note

KEC-

20426

Extracts/

Integration

In Customer_TMFF

- for Vendor, Send Vendor as

Acct No when

we have Party

Type as B.

With the Security Preferences

TMFF_CMUS_PARTY_EXTRACT and

TMFF_CMUS_ALLOW_DUP_C

UST_VEND set to "Y", in the CUSTOMER_TMFF XML

extract (Tools > Customer Integration Extract >

"TMFF" option) the Party Type is now "B" and the

Vendor is identified by the Acct No. (This is the case

where the Vendor and Customer are identical.) This

resolves a previous issue with the values in the XML in

this case.

KEC-

20430

Shipment

Processing

CM is not

calculating

check digits correctly for

manually entered entry

numbers for shipments

cleared by other

brokers.

CM-US now calculates check

digits correctly for manually

entered Shipment Entry Numbers for shipments

cleared by other brokers.



Inter-nal

ID

Category

Summary

Description

Release Note

KEC-

20433

Extracts/

Integration

CMUS is formatting

negative numbers wrong

in the Internet

Tracking shipment

extract.

For a shipment Billing Invoice downloaded as an

extract to Internet Tracking with a negative total

amount, the system now

formats this negative amount correctly as a 10-digit

number preceded by a minus sign (-) as follows. The total

amount is position 5 in the IH00 record. This amount

starts at character 25 and ends at character 35 in the

record, with two decimal places implied at the end

(without a decimal point). For example, if the total

amount is $-14.50, the system now represents this

figure in this record as -

0000001450. Previously, a negative total amount in this

case was incorrectly coded.


KEC-

20436

Shipment

Processing

Validations

Validation 1700-

Destination State is

required – this is NOT required

for ET86.

The system no longer returns Validation 1700 ("Destination

State is required") for a shipment with Entry Type 86

(Section-321) since this information is not required

for Entry Type 86. This issue is fixed. (Case ID:

02515429)


Inter-nal

ID

Category

Summary

Description

Release Note

KEC-

20437

Shipment

Processing

Validations

VALIDATION 1670 - Charges

Required - this is NOT required

for ET 86.

The system no longer returns Validation 1670 ("Charges

are required") for a shipment with Entry Type 86 (Section-

321) since this information is

not required for Entry Type

86. This issue is fixed.

KEC-

20444

Extracts/

Integration

CMUS is unconditionally

creating the IMAGE_CT

process queue record when it

creates an

IMAGE record.

New Root level General Preferences IMAGE_DM and

IMAGE_CT are added to refine the process of creating

Image subtype process queue records that direct

system-generated document images to applications

Document Manager (DM) and Control Tower (CT)

respectively. When users print a system document,

these Preferences work as

follows:

• IMAGE_CT="N" and IMAGE_DM="Y”: The Form

Queue Handler creates an IT_SHIP_FMT_EXTRACT/IMAGE process queue record

but not an IMAGE_CT

subtype record.

• IMAGE_CT="Y" and IMAGE_DM="N”: The

Form Queue Handler creates an

IT_SHIP_FMT_EXTRACT/IMAGE_CT process queue record but not an IMAGE

subtype record.

• IMAGE_CT="Y" and


Inter-nal

ID

Category

Summary

Description

Release Note

IMAGE_DM="Y”: The Form

Queue Handler creates both IT_SHIP_FMT_EXTRACT/IM

AGE and IT_SHIP_FMT_EXTRACT/IM

AGE_CT process queue

records

• IMAGE_CT="N" and IMAGE_DM="N”: The Form Queue Handler

creates neither IT_SHIP_FMT_EXTRACT/IM

AGE nor IT_SHIP_FMT_EXTRACT/IMAGE_CT process queue

records.

This determines which files

are sent to the Document Manager and which are sent

to Control Tower, depending on the customer setup. Note

that the IMAGE_DM Preference is set to "Y" by

default, and the IMAGE_CT Preference is set to "N" by

default. The following SQL scripts are modified to

support this update:

• PREFERENCE_KEYS-KEC-

20444.sql

• GENERAL_PREFERENCES-

KEC-20444.sql


Inter-nal

ID

Category

Summary

Description

Release Note

KEC-

20474

Extracts/

Integration

IT SHIP FMT EXTRACT for

CONTAINERS not updating

the process

status cd from P to Y and

deleting the dashboard

record after processing has

been completed if the XML has

an IT number.

When the XML has an IT number, the IT SHIP FMT

EXTRACT for CONTAINERS now correctly updates the

Process Status Code on the

Process Queue Maintenance screen (Tools > Process

Queue) from "P" (Processing) to "Y"

(Processing Complete) and deletes the Dashboard record

when processing is complete. (Case IDs: 2525741,

0252574)

KEC-

20541

Extracts/

Integration

Auto Billing

should not process when

GLno12 is blank

for the charges.

For Auto Billing with Sage

Integration, the system no longer processes and sends

an invoice to Sage if the Security Preference

REQUIRE_GL_OTHER_SETUP

is set to "Y" but the "Gl No 12" field on the Pre Bill Lines

Maintenance screen (Support > PR > Pre Bill

Lines) is blank. This issue is fixed. (Internal ID KEC-

20541)

customs management u.s.€¦ · what's new customs management version 19.2.2 customs...

Documents