› kc › customs_managemen… · web viewsalesforce customer case id numbers are added to...

Customs Management U.S.

Release NotesCustoms ManagementRelease: 20.1.1Date: April 13, 2020

© 2017-2020 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 Contents1. What's New Customs Management Version 20.0.0.....................42. CM-US Documentation............................................................4 3. TRR Exclusion Tariffs Added Since 20.0.0 Part 2........................54. New Consumer Product Safety Commission Updates & Notes .…..75. New Validations for Tariff Number Order ………………………………146. Alerts, Requirements, Updates & Notes...................................167. TMFF – CM-US – Sage integration............................................188. Other Features and Enhancements..........................................189. Defect Fixes and Minor Compliance Updates............................21


What's NewCustoms Management Release Version 20.1.1Customs Management Help now includes the CM-US 20.1.1 Release topic: “What's New Customs Management Release Version 20.1.1”. (This is now the Landing Page for the CM-US Help.)This set of Release Notes is essentially a copy of this Help topic. An Excel version of the 20.1.1 Release Notes is also available.)

CM-US DocumentationGetting Help and Using ItTh e What's New" topic is the landing page for the Customs Management US Online Help. To hide or display the Table of Contents panel giving you full access to the extensive set of CM-US Online Help topics, click the TOC toggle button to the left:

For additional options, click the horizontal bars (collapsed menu) icon () at the upper right of the Help window to display the following menu:

Excel Release NotesThe 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 available in Excel spreadsheet format by clicking the following link in the What’s New? Help topic

· 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 Salesforce Customer Case ID Numbers are added to Release Notes for which this information is available.

o SQL scripts associated with this release are available separately from Support by request.

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.

Trade Remedy Requirements Exclusion Tariffs Added/Modified Since 20.0.0 Part 2Customers can now add new Trade Remedy Exclusion Tariff records without deleting/reloading the master table records. For customers who have already loaded the Master Trade Remedy spreadsheet provided by BluJay Customer Support need to update the Trade Remedy table on their systems to reflect tariff remedy exclusions announced via the Federal Register since v. 20.0.0 was released. The spreadsheets listed below (available from Customer Support) enable customers to load only those trade remedy table records they do not yet have in place, and to delete associated 8-digit records. For a list of previous modifications and available files, see the What's New topic for v. 20.1.0.The following alternatives are available:

· Customers can use a SQL script to delete all records from their current TRR table, and then use the spreadsheet that includes all records to upload the complete TRR table.

· Alternatively, customers can carry out the following steps:o Find records that were added since the previous release and delete those

records. (If you have the Trade Remedy Requirements Purge utility, you can use this to delete these records.)

o Use the spreadsheet we supplied with just the records to be added with this release and upload them using TRADE_REMEDY upload mapping.

o If for one of the spreadsheets the client added the same records that we are adding, they can skip that spreadsheet. They don’t have to delete those records or use our spreadsheet to add them.

o Have your database administrator (DBA) run the SQL script that deletes TRR records that need to be deleted.


o Have your database administrator (DBA) run the SQL script that modifies existing TRR records.

(Internal IDs KEC-21732 [Epic], KEC-21879 [Story])

Section 201 Tariff SpreadsheetsThe following spreadsheets are provided for updating (adding and deleting) Section 201 tariffs:

· Quota TRR.xlsx – Spreadsheet of new records to add (Version 1 - Current).· Section 201 records to be deleted.docx – Word file list of Section 201 records

to delete (Version 1 - Current).

Tranche 3 Exclusions UpdateThe following table lists the additional files (since the 20.1.0 release) for Tranche 3 Exclusions that enable customers to load only those trade remedy table records they do not yet have and delete associated 8-digit records.

Tranche 3 Exclusions Identifier

Filename Description

84 FR 61674 HTS 9903.88.34

84FR61674 99038834.xlsx Spreadsheet of New Records to add.(Version 1 - Current).

99038834.xlsx Trade Remedy Records to delete.(Version 1 - Current).

84 FR 61674.pdf Federal Register Notice.(Version 1 - Current).

84 FR 65882 HTS 9903.88.35

84FR65882 99038835.xlsx Spreadsheet of New Records to add (Version 2 - Current).

99038835.xlsx Trade Remedy Records to delete.(Version 1 - Current).

84 FR 65882.pdf Federal Register Notice(Version 1 - Current).

84 FR 69012 HTS 84FR69012 99038836.xlsx Spreadsheet of New


9903.88.36 Records to add (Version 2 - Current).

99038836.xlsx Trade Remedy Records to delete(Version 1 - Current).


85 FR 549 HTS 9903.88.37

85FR549 99038837.xlsx Spreadsheet of New Records to add (Version 2 - Current).

99038837.xlsx Trade Remedy Records to delete(Version 1 - Current).


New Consumer Product Safety Commission Updates/For products defined by certain HTS codes, the Consumer Product Safety Commission (CPSC) now conducts an inspection of incoming "products of interest", resulting in a new set of Review messages via ACE, indicating the status of a shipment requiring inspection, either at the port or at the importer’s premises. trade will receive additional messaging through ACE. In compliance with this process, CMUS is adding new Tracing Dates to reflect the status of shipments undergoing this process. Additionally, the SO message and receive file are updated with these changes, so that the system processes the SO receive file in a way that reflects the CPSC updates. (KEC-21490 [Epic])A new PG Agency Code (CPS) is added to the Pg Agency Codes Maintenance table (Support > P > Pg Agency Codes) for the Consumer Product Safety Commission. The following SQL script is included for this enhancement: PG_AGENCY_CODES-KEC-21610.sql (Internal ID KEC-21610)

New Tracing DatesThe following new Tracing Dates are added to the Tracing Dates Master maintenance table (Support > T > TF-TZ > Tracing Dates Master) to track the status of the CPSC inspection:

· 94120 – CPSC Under Review


· 94121 – CPSC Hold Intact· 94122 – CPSC Rejected Per Review· 94123 – CPSC May Proceed· 94124 – CPSC Do Not Devan· 94125 – CPSC Move to Secure Hldng fclty· 94126 – CPSC Intensive Exam/Sample

The following SQL script is included for this enhancement: TRACING_DATES_MASTER-KEC-21608.sql (Internal ID KEC-21608 [Story])

New ABI Return CodesThe following table lists and describes the new ABI Record Types for ABI Return Codes 01, 02, 04, 06, 07, 08 and 11 added to the Abi Record Codes Maintenance table (Support > A > A-AdH > Abi Return Codes) in conjunction with the new Tracing Dates listed above in support of the new CPSC inspection protocol.

ABI Record Type

ABI Return Code

Tracing Date No. Description

SO70CPS 1 94120CPSC Under Review

SO70CPSHD 1 94120CPSC Under Review

SO70CPS 1 94123

CPSC Under Revw Delete Prev may Proceed

SO70CPSHD 1 94123


SO70CPS 2 94121 CPSC Hold Intact

SO70CPSHD 2 94121 CPSC Hold Intact

SO70CPS 2 94123

CPSC Hold Intact Delete Prev May Proceed

SO70CPSHD 2 94123 CPSC Hold Intact Delete Prev May


ABI Record Type

ABI Return Code


Proceed

SO70CPS 4 94120

CPSC Rej per Revw Delete Prev Under Revw

SO70CPSHD 4 94120

CPSC Rej per Revw Delete Prev Under Revw

SO70CPS 4 94121

CPSC Rej per Revw Del Prev Hold Intact

SO70CPSHD 4 94121

CPSC Rej per Revw Del Prev Hold Intact

SO70CPS 4 94122CPSC Rejected per Review

SO70CPSHD 4 94122CPSC Rejected per Review

SO70CPS 4 94123


SO70CPSHD 4 94123


SO70CPS 6 94124CPSC Do Not Devan

SO70CPS 7 94123CPSC May Proceed

SO70CPSHD 7 94123CPSC May Proceed


ABI Record Type

ABI Return Code


SO70CPS 8 94121

CPSC Move to Secure Hldng Fclty

SO70CPS 11 94126CPSC Intensive Exam/Sample

The following SQL script is included for this enhancement: ABI_RETURN_CODES-KEC-21609.sql (Internal ID KEC-21609)

Additional Status CodesThe following additional Status Codes are added to the Dashboard Work Trans Status Maintenance screen (Support > D-DI > Dashboard > Work Trans Status) for the new CPSC protocols based on the Tracing Dates created for the ABI Return Codes. When these new status codes are received from Customs, they are also available for users on the Dashboard Work Management screen:

· CPSC Do Not Devan· CPSC Hold Removed· CPSC Intensive Exam· CPSC May Proceed· CPSC Rej per Review· CPSC Under Review

The following SQL script is included for this enhancement: DASHBOARD_WORK_TRANS_STATUS-KEC-21621.sql (Internal ID KEC-21621)

Dashboard Work ManagementThe following additional Status Codes are added to the Dashboard Work Trans Status Maintenance screen (Support > D-DI > Dashboard > Work Trans Status) for the new CPSC protocols based on the Tracing Dates created for the ABI Return Codes. When these new status codes are received from Customs, they are also available for users on the Dashboard Work Management screen:

· CPSC Do Not Devan· CPSC Hold Removed· CPSC Intensive Exam· CPSC May Proceed· CPSC Rej per Review


· CPSC Under ReviewThe following SQL script is included for this enhancement: DASHBOARD_WORK_TRANS_STATUS-KEC-21621.sql (Internal ID KEC-21621)

Updated Reason and Sub Reason CodesThe Pg Status Reason Codes Maintenance table (Maintenance > Reference > PGA > PGA J-R > Pg Status Reason Codes) and the Pg Sub Reason Codes Maintenance table (Maintenance > Reference > PGA > PGA J-R > Pg Status Reason Codes) are updated to include the modified and new Reason and Sub Reason codes, as described in the following table:

Status Reason Code

Sub Reason Code

Description Add/Change Note

14 111 CANCELED MANUFACTURER FACILITY REGISTRATION

Description changed

14 155 MISSING, INVALID, OR EXPIRED FWS IMPORT/EXPORT LICENSE NUMBER

Description changed

14 172 MISSING OR INVALID MARKINGS O

Description changed

14 175 MISSING OR INVALID FWS QUANTITY OR UNIT OF MEASURE

Description changed

14 176 FWS CORPORATE ACCOUNT PAYMENT IS OVERDUE

Description changed

14 178 INVALID FWS COUNTRY OF SPECIES ORIGIN

Description changed


Status Reason Code

Sub Reason Code

Description Add/Change Note

14 183 INVALID UNITS OF MEASURE FOR COMMODITY

Added new Code

26 108 MISSING REGISTRATION

Added new Code

26 109 REGISTRATION NOT ON FILE

Added new Code

26 110 MISMATCH IN REGISTRATION

Added new Code

26 111 CANCELED MANUFACTURER FACILITY REGISTRATION

Added new Code

26 112 MANUFACTURER FACILITY REGISTRATION INVALIDATED BY FDA

Added new Code

26 120 INVALID COUNTRY OF SHIPPING

Added new Code

26 158 MISSING CARRIER NAME

Added new Code

The following SQL scripts are included for this enhancement:· PG_STATUS_REASON_CODES-KEC-21622.sql· PG_SUB_REASON_CODES-KEC-21622.sql

(Internal ID KEC-21622)


New Validations for Tariff Number OrderWhen there are multiple HTS numbers in a line in the Invoice Lines Tariff grid on the Commercial Invoice screen, they must be in a certain order. The correct HTS sequence is specified in CSMS# 18-000624, as follows:

1. Chapter 98 (if applicable).2. Chapter 99 number(s) for additional duties.3. For trade remedies, first report the Chapter 99 HTS for Section 301, followed

by the Chapter 99 HTS for Section 232 or 201 duties (if applicable), followed by the Chapter 99 HTS for Section 201 or 232 quota (if applicable).

4. Chapter 99 number(s) for REPLACEMENT duty or other use (for example, MTB or other provisions).

5. Chapter 99 number for other quota (not covered by #3) (if applicable).6. Chapter 1 to 97 Commodity Tariff.

CM-US now includes the validations listed below to alert the user if HTS numbers are not in the correct order. (Internal ID KEC-20031 [Epic], Case ID 02669691)

· “Ch 98 HTS not in correct position” (11684) – The user entered tariff numbers in the wrong order when using a Chapter 98 Tariff Class. The following SQL scripts are included for this enhancement:o VALIDATION_CONTROL-KEC-21653.sqlo VALIDATION_MESS-KEC-21653.sqlo VALIDATION_HELP-KEC-21653.sqlo VALIDATION_TABLE_X_REF-KEC-21653.sql

(Internal ID KEC-21653 [Story])· “Ch 99 Additional HTS not in correct position” (11685) – The user entered tariff

numbers in the wrong order when using a Chapter 99 Number with the value of the "Calc 99 Flag" field on the Tariff Calc Flags Maintenance screen (Maintenance > Reference > Import > Tariff Calc Flags) = "Additional". The following SQL scripts are included for this enhancement:o VALIDATION_CONTROL-KEC-21654.sqlo VALIDATION_HELP-KEC-21654.sqlo VALIDATION_MESS-KEC-21654.sqlo VALIDATION_TABLE_X_REF-KEC-21654.sql

(Internal ID KEC-21654 [Story])· Trade Remedy HTS not in correct position" (11888) – The user entered tariff

numbers in the wrong order when using a Chapter 99 Number with the value of the "Calc 99 Flag" field on the Tariff Calc Flags Maintenance screen = "SPI". The following SQL scripts are included for this enhancement:o VALIDATION_CONTROL-KEC-21655.sqlo VALIDATION_HELP-KEC-21655.sql


o VALIDATION_MESS-KEC-21655.sqlo VALIDATION_TABLE_X_REF-KEC-21655.sql

(Internal ID KEC-21655 [Story])· Ch 99 Override HTS not in correct position” (11687) – The user entered tariff

numbers in the wrong order when using a Chapter 99 Number with the value of the "Calc 99 Flag" field on the Tariff Calc Flags Maintenance screen = "Override". The following SQL scripts are included for this enhancement:o VALIDATION_CONTROL-KEC-21656.sqlo VALIDATION_MESS-KEC-21656.sqlo VALIDATION_HELP-KEC-21656.sqlo VALIDATION_TABLE_X_REF-KEC-21656.sql

(Internal ID KEC-21656 [Story])· “Ch 99 other Quota HTS not in correct position” (11688) – The user entered

tariff numbers in the wrong order when using a Chapter 99 Number with the value of the "Calc 99 Flag" field on the Tariff Calc Flags Maintenance screen not = "Additional/SPI/Override". The following SQL scripts are included for this enhancement:o VALIDATION_CONTROL-KEC-21657.sqlo VALIDATION_MESS-KEC-21657.sqlo VALIDATION_HELP-KEC-21657.sqlo VALIDATION_TABLE_X_REF-KEC-21657.sql

(Internal ID KEC-21657 [Story])· "Trade Remedy Section 301 HTS is in the wrong order” (11689) – The user

entered tariff numbers in the wrong order when using a Trade Remedy insert Type of A and that tariff follows a Trade Remedy Insert Type B or C tariff in the "Insert Type" field on the Tariff Calc Flags Maintenance screen. The following SQL scripts are included for this enhancement:o VALIDATION_CONTROL-KEC-21658.sqlo VALIDATION_HELP-KEC-21658.sqlo VALIDATION_MESS-KEC-21658.sqlo VALIDATION_TABLE_X_REF-KEC-21658.sql

(Internal ID KEC-21658 [Story])· Trade Remedy Section 232 or 201 HTS in wrong order” (11690) – The user

entered tariff numbers in the wrong order when using a Trade Remedy Insert Type B tariff following a Trade Remedy Insert Type C tariff in the "Insert Type" field on the Tariff Calc Flags Maintenance screen. The following SQL scripts are included for this enhancement:o VALIDATION_CONTROL-KEC-21659.sqlo VALIDATION_HELP-KEC-21659.sqlo VALIDATION_MESS-KEC-21659.sqlo VALIDATION_TABLE_X_REF-KEC-21659.sql

(Internal ID KEC-21659 [Story])


Alerts, Requirements, Updates and Notes from Previous ReleasesWhen 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 previous CM-US releases:

· Trade Remedy Requirements (TRR) Exclusion Tariffs Added Since 20.0.0· Parts Record HTS Update Tool· EDI Multi Invoice Load · Multiple Additional Declarations Can Now Be Reported per Entry Summary Line· Setting Up and Sending Auto ISF Form 830· Negating Accepted ACH Debit Authorization Transactions· New Prefixes for Product Exclusion No.· ACE Appendix PGA Updates· Expired/Eliminated PGA Processing Codes for APHIS/Core· EDI Upload for In-Bond Shipments· Updates to Importer 5106 Query· Trade Remedy Auto Add Process· Arranging Tariff Numbers in Correct Sequence for ABI Processing· Recon XML Extract· Reference - Entry Type 86· 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 integrationOverviewCM-US is now integrated with both the BluJay Solutions Transportation Management for Forwarders (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 Overviewo Preferences and System ParametersSage-CM-US Integrationo Using Sage Integrationo Sage-CMUS Process FlowTMFF-CM-US Integrationo Using TMFF Integrationo TMFF-CMUS Process Flowo 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-CentricTMFF/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 - SummaryNote: Internal IDs for this section are for Epics and/or Stories unless otherwise indicated.

Commercial Invoice· CBP recently deployed the new Entry Type 86 for entry of Section 321 low-

valued shipments through ACE Cargo Release. This new Entry Type provides greater visibility into low value shipments. As a result, a Trade Remedy is not required for Entry Type 86. (In fact, sending a 9903 number with an Entry Type 86 typically results in rejection by Customs.) CM-US is updated, so that Trade Remedy Auto Insert functionality no longer auto inserts a Chapter 99 Trade Remedy in Commercial Invoice Invoice Line Tariffs for Entry Type 86. For more information on Entry Type 86, see the Help topic "Reference - Entry Type 86" under "Processing a Shipment". (Internal ID KEC-21378 [Epic], KEC-21364 [Story], KEC-21646 [Story])o To facilitate this compliance, a new check box "Skip Trade Remedy Auto

Add" is added to the Entry Types Maintenance Screen (Maintenance > Reference > Import > Entry Types). This check box is selected by default for Entry Type 86. (Internal ID 21643 [Story])

o If the "Skip Trade Remedy Auto Add" check box is selected for Entry Type 86 (or any other Entry Type not requiring a Trade Remedy) the following Validations are disabled:- "Required Trade Remedy tariff not used" (11655)- "Required tariff no. entered. Exclusion(s) available" (11683)(Internal ID KEC-21645 [Story])

o If a Trade Remedy is manually inserted into a line for an Entry Type 86 (or any other Entry Type not requiring a Trade Remedy) the system now returns the following Validation "Trade Remedy not required for entry type [Entry Type]" (11693). (Internal ID KEC-21647 [Story])

Documentation· Per Customs requirements for spreadsheet documentation involving the Craft

Beverage Modernization Act (CBMA), the following additional allowable file types are added to the CM-US Document Image System (DIS): .xls and .xlsx. (Previously, the only allowable formats for DIS were .tiff, .pdf, .doc and .png) The additional file types are also added to the Dis Document Type Maintenance table (Support > D > D-DI > Dis Document Type). (Internal IDs KEC-19303 [Story], KEC-19514 [Story], Case IDs Incident 227154, 2594019)

EDI Upload/Lights Out Entry/Hands-Free Processing· For an EDI upload (File > Load EDI), the fields specified by the following XML

tags are now uploaded to the shipment during this process:o <dateEntryReleaseId>[yyyymmdd]</dateEntryReleaseId>o <releaseIdEntryFiler>[nnn]</releaseIdEntryFiler>


o <releaseIdNo>[nnnnnnn]</releaseIdNo>

Previously, the fields were not being uploaded during this process. The following SQL script is included for this update: EDI_INVOICE_LINE_KEC-21955.sql (Internal ID KEC-21955)

Extracts/Integration· Dashboard Work Management is added to the EDI and XSD XML templates. A

<DashBoardWorkMgmt> tag is now included directly under the <EdiShipmentHeader> tag. Dashboard Work Management is also added to the EDI Spreadsheet. This feature is for implementing changes to the Shipment XML in Web Services to allow the Dashboard Work Management record to be passed in the XML and created from the XML. (Internal IDs KEC-20218 [Epic], KEC-20953 [Story])

· CM-US now ensures that the Master Air Waybill (MAWB) No. received from TMFF or CT (Control Tower) remains correctly formatted after updates are made in CMUS. This requires removal of special characters in CMUS for CBP submission, so that the MAWB No. is completely numeric. CM-US now stores the value of MAWB in the XML received from TMFF in a new field ("Gshpid") on the Shipment Id and EDI Shipment Id Maintenance screens (described below). The value in this field is then reformatted in the strictly numeric form required by Customs when copying it to the respective shipment files. The Master and House Bills and Scacs from the incoming TMFF or CT XML are stored in other new fields (described below) added to the shipment and EDI shipment Maintenance screens. Additionally, new tags for all these new fields are added to the shipment XML files returned to TMFF or CT as described below. (Internal ID KEC-21741 [Epic], KEC-21715 [Story], KEC-21814 [Story])o The following new fields are added to the Shipment Id Maintenance screen

(Support > S > ShipmentA-ShipmentI > Shipment Id) and to the Edi Shipment Id Maintenance screen (Support > E > EDI PgP - EDI PgZ > Edi Shipment Id):- "Tmff Master Scac" (4 characters)- "Tmff Master Bill" (30 characters)- "Tmff House Scac" (4 characters)- "Tmff House Bill" (30 characters)Additionally, the following field is added to the Edi Shipment Header Maintenance screen (Support > E > EDI PgP - EDI PgZ > Edi Shipment Header) and the Edi Shipment Header AUX (Support > E > EDI PgP - EDI PgZ > Edi Shipment Header AUX) screen: "Gshpid" (30 characters). When a user creates a shipment by selecting Load EDI from the CM-US File menu, the system now copies data from these new fields on the Edi Shipment Id Maintenance screen and updates the values for these new fields on the Shipment Id Maintenance screen for this shipment. (Internal IDs KEC-21810 [Story], KEC-21811 [Story], KEC-21813 [Story])

o New tags are added to the standard CMUS shipment XML and XSD files returned to TMFF and CT to include this updated formatting. (Internal ID KEC-21812)


Maintenance Screens· The following updates are made to the Pg Omc Box Party Req Maintenance

screen (Maintenance > Reference >PGA > PGA J-R > Pg Omc Box Party Req) based on the Implementation Guide for the Office of Marine Conservation (OMC): For Box Number = "7A1" and Party Role = "AQF, the value of the "Party Req" (Party Required) field now = "O" (Optional). The following rows are removed from the table on the Pg Omc Box Country Req Maintenance screen (Maintenance > Reference >PGA > PGA J-R > Pg Omc Box Country Req):o Box Number = "7A2"/Country Cd = "FR"o Box Number = "7B"/Country Cd = "PK"

The following rows are added to the table on the Pg Omc Box Country Req Maintenance screen: o Box Number = "7A2"/Country Cd = "GF"o Box Number = "7A2"/Country Cd = "MY"o Box Number = "7A4"/Country Cd = "JP"o Box Number = "7A4"/Country Cd = "KR"

(Internal IDs KEC-21209 [Epic], KEC-21678 [Story])· Per CSMS #41538803 Guidance, the data for additional duty on imports of

Section 232 Derivative Iron, Steel and Aluminum Products is uploaded to the Trade Remedy Requirements table (Maintenance > Import > Trade Remedy Requirements). (Internal ID KEC-21998)

Defect Fixes and Minor Compliance UpdatesThis table lists the issue number and the category in which the release note appears below this table.Note: Release notes in this section include customer-reported issues, issues where SQL scripts are modified or created, performance issues and requested documentation.

[Next Page]

Key Components Summary Release Notes

KEC- Commercial All lookups to All lookups to the Trade Remedy



20804 InvoiceMaintenance Screens

the Trade Remedy Require-ments table need to use CA instead of Canadian province code.

Requirements Maintenance table (Maintenance > Import > Trade Remedy Requirements) now use CA (Canada) for the Country of Origin instead of the Canadian province code, as previously.

KEC-21051

Extracts/IntegrationSecurity Admini-stration

Vendor Integration Extract: select ALL should not limit to 999. Oracle returns an error at 1,000.

Previously, when the number of Vendors returned by the Search function on the Vendor Integration Extract popup dialog (Tools > Vendor Integration Extract) exceeded 1,000 not all Vendors would be extracted. This has been fixed. In addition, a new general preference EXTRACT_MAX_ROW_LIMIT is now provided. This Preference enables users to set the maximum number of Vendors returned. The value of this Preference can be set so that users can limit the number of Vendors in the extract for the Sage Accounting System ("Standard Vendor Extract for Sage" radio button) or TMFF ("TMFF Extract" radio button).



KEC-21144

EDI Upload/Lights Out Entry/Hands-Free ProcessingShipment Processing

EDI Uploaded Flag on Shipment Header is not getting set properly 19.2.3.

When a shipment is validated, if an EDI Invoice Upload was performed on the Commercial Invoice screen, the value of the "Edi Uploaded" field on the Shipment Header Maintenance screen (Support > S > ShipmentA-Shipmentl > Shipment Header) is now correctly set to "Y", as should be the case. (Previously, this value was not being correctly set.) This issue is fixed.

KEC-21345

Shipment ProcessingExtracts/IntegrationEDI Upload/Lights Out Entry/Hands-Free Processing

TMFF job UOM has KGS and overwrites CMUS UOM which was set to KG from Shipment.

When an EDI shipment file from TMFF with kilograms as the Unit of Measure (UOM) is received by and uploaded to CM-US, the system no longer incorrectly overwrites the value "KG" with "KGS" in the "Uom Weight" field on the Edi Shipment Header Maintenance screen (Support > E > EDI PgP - EDI PgZ > Edi Shipment Header) and in the "UOM" field on the Shipment Header. This issue is fixed.



KEC-21439

Extracts/Integration

Not all Customer records included in Customer Integration Extract for All.

An issue with missing Customer Codes on the Customer Integration Extract pop-up dialog (Tools > Customer Integration Extract) when selecting the "All Customers" and "TMFF" radio buttons (for sending extracts to TMFF) is resolved. This issue occurred when the value for TMFF_PARTY_ID was blank in the Vendor table, causing some Customers to be "overlooked" by the system and not included in the returned list or set of extracts sent. The system now checks for this condition and indicates to the user that data corrections are necessary before they can perform the extract. Once the corrections are made, the program correctly displays all Customer Codes in the grid on this dialog in this case and sends extracts for all these to TMFF. Additionally, all duplicate Customer Codes are now noted when the number of Customer Codes is 1000 or greater.



KEC-21472

Extracts/Integration

Party integration with TMFF not creating Consignee or Shipper roles when it should.

Party integration of CM-US with TMFF now includes the following tags for Consignee and Shipper Roles under the <Party Roles> section: <RoleSNO> and <Role> in the TMFF Party Master XML generated by CM-US . If the Consignee check box on the Customer Details Summary tab is selected, the system adds a value of "2" to both tags. If the "Shipper" check box on this tab is selected, the system adds a value of "1" to both tags. This enhancement enables TMFF to process these roles without requiring manual updates.

KEC-21478

Forms/ReportsCommercial Invoice

7501 no longer printing Add'l Declaration in Box 33.

The system now prints the Additional Declarations in Box 33 of the Customs Entry Summary form (CMUS Form 7501) that are entered on the Add'l Declarations popup dialog displayed by clicking the Add'l Declarations button on the CI Line Optional Data screen accessed from the Commercial Invoice screen. Previously, these items were not being printed on this form. This issue is fixed. (Case IDs 02655052, 02654455)



KEC-21542

Partner Government AgenciesABI Processing

PGA Correction sending wrong Program Code for EPA Pesticides.

CM-US now sends the correct Disclaimer Code "PS1" (Government Agency Program Code) in the PGA Corrections message (PGA Corrections button on Shipment Send tab) for the Environment Protection Agency (EPA). Previously, the system was sending an erroneous "PST" value for this code, resulting in the "CA DATA REJECTED" with "INVALID DISCLAIMER CODE PER PGA" message from Customs. This issue is fixed. (Case ID Incident 252569)

KEC-21550

Commercial Invoice

Trade Remedy - an expired tariff can mistakenly result in an auto-insert.

When the AUTO_INSERT_TRADE_REMEDY General Preference is set to "Y", the system now correctly inserts only currently active Trade Remedy Tariffs in the Tariff column of the Invoice Line Tariffs grid on the Commercial Invoice screen. Previously, some expired Trade Remedies were being auto inserted in this column, resulting in Validation errors. This issue is fixed. (Case ID Train 20.0.2.1 test)



KEC-21577

General/Infrastructure/PerformanceShipment Processing

Latency Issue Opening the file after changing the CI number via the Tools menu option (Change CI Number).

As should be the case, when the user selects Tools > Change CI Number, and then changes this number on the Change Commercial Invoice No. popup dialog, the old record is now correctly deleted from the Lock Shipments Maintenance table (Support > L > Lock Shipments). Previously, the system did not delete the appropriate record from this table in this case and caused the system to freeze if the user attempted to delete it manually. This issue is fixed. (Case ID 02660727)

KEC-21591

Billing Alternate Billing - IC Billing code is not saving after save and then Invoice Prepared.

For an Inter-Company (IC) Billing Code with the Alternate XML Billing format that enables integration with an external system, the CM-US system now displays the IC Billing Code under the "Bill To" field on the Shipment Send screen as follows. The user completes the information on this screen, selects the "Prepare Invoice" and "Create" check boxes, and then clicks the Billing Invoice button to create the Invoice. Previously, the IC Billing Code was not being displayed in this case. This issue is fixed.

KEC-21617

PartsCommercial InvoiceEDI Upload/Lights Out Entry/

Parts XML Upload. Create/Update creates new Cat Tariff Lines instead

Parts XML Upload functionality now works correctly. Previously, if the Preference NEW_LINE_SEQUENCE was set to "Y" and an existing Part Number with CAT Tariff Lines as SEQ 10, 20 was updated by the



Hands-Free Processing

of updates. CreateUpdate subaction in the XML, the CAT Tariff Lines were added as new lines with sequence numbers 100 and 200, incorrectly resulting in four CAT Tariff Lines instead of the original two. This issue is fixed.

KEC-21631

Commercial InvoiceEDI Upload/Lights Out Entry/Hands-Free Processing

EDI - issue with loading multiple tariff lines on one CI line.

For an EDI upload, the system now correctly posts values to the tariff lines on the Invoice Line Tariffs grid on the Commercial Invoice screen. Previously, lines with duplicate values were sometimes posted. This issue is fixed. (Case ID 02662443)

KEC-21668

ABI ProcessingShipment Processing

Auto ABI Statement is not working based on preference setup.

Auto ABI Statement processing now works correctly in the following case. If the General Preference AUTO_ABI_STATEMENT_AUTH_IMPORTER is set to "Y" at the Root level but the Customer Preference AUTO_ABI_STATEMENT_AUTH_IMPORTER for the Customer specified on the Shipment Header is set to "N", the system no longer incorrectly authorizes an Auto ABI statement with the value of the "Payment Type" field set to "3 - Importer" . This issue is fixed.



KEC-21736

Shipment ProcessingExtracts/Integration

Party Role with 18 is not sending when we have the same and Customer and Vendor Code which belongs to same company.

When a Customer and Vendor belonging to the same company have the same code, Party information for the Vendor with the Party XML is now created for the Customer. To indicate this, when creating the Party Roles for the customer, the system creates role 18 for the vendor in the XML code under the <PartyRole> section as follows: <RoleSNO>1</RoleSNO> <Role>18</Role> <RoleRefKey>1</RoleRefKey> Note that the value of the <RoleSNO> equals the value for this tag under the previous <PartyRole> section + 1. (Previously, Party Role 18 was not included In the Customer_TMFF.xml file sent to TMFF unless the Vendor was included.) For more information of Customer and Vendor codes with TMFF, see the Help topics under TMFF-CMUS-Sage Integration".



KEC-21862

Escalations/Exceptions

Exception Original date is either not being written or is being overwritten. when resolved is checked or unchecked.

Issues with the original Exception Date either not being written to the Shipment Dates grid or being overwritten by the wrong date are resolved. Previously, when an Exception was marked as Resolved on the Exceptions tab of the Exceptions/Escalations screen and then saved, the original Exception Date was not posted to the Shipment Dates grid (only the Resolved Date was posted). Additionally, if the Resolved check box was unselected and the shipment saved, the Exception Date was updated in the Shipment Dates grid, which should not be the case. This issue is fixed so that now both dates are correctly posted to the Shipment Dates grid and deselecting the Resolved check box only deletes the Resolved date.

KEC-21943

ABI ProcessingShipment Processing

Parts XML Upload - CreateUpdate creates new Cat Tariff Lines instead of updates.

For a shipment with CPSC data and the indicator MOVE TO SECURE HLDING FCLTY in the SO70 return message line, the system now posts the correct Tracing Date (94125 - "CPSC Move to Secure Hldng fclty") to the Shipment Dates grid and the Dashboard Work Management screen. The following SQL script is updated for this resolution: ABI_RETURN_CODES-KEC-21609.sql

› kc › customs_managemen… · web viewsalesforce customer case id numbers are added to...

Documents