Classification

Using Classification Code Instead of Product Classification Code GID

Purpose

To avoid the need to update product classification code GIDs every time classification details are downloaded from a third-party content provider (like Descartes), Global Trade Management (GTM) now directly uses the classification code stored across multiple objects instead of the product classification code GIDs stored in the classification table.

With this change you can avail in-line editing and mass updating of item classification data.

Also, this will change will restrict potential performance issues when data is modified via UI or integration or when processes like Update Classification Version are run.

During the Update Classification Version process, GTM detects product classification codes that are invalid and updates the classification data to the most recent data version. As part of this existing process, GTM derives the product classification code from the product classification code GID and populates the CLASSIFICATION_CODE column.

When you add or update classification data in GTM objects via the UI or integration, the CLASSIFICATION_CODE column within the appropriate table is updated.

Note: This change of supporting the CLASSIFICATION_CODE column does not impact the user interface or results of the actions/processes.

Note: In future releases, the GTM will continue to use the CLASSIFICATION_CODE column and eventually, will no longer use the product classification code GID. Oracle will document these changes as they evolve.

Configuration

The modified behavior is dependent on the following optional features:

  •  
    PREFER CLASSIFICATION CODE OVER CODE GID: Enable this optional feature for GTM to consider the new classification code value instead of deriving the classification code from the Product Classification Code GID, and proceed with the execution of action/process related to item classification.
  • DETECT INVALID CLASSIFICATION USING CODE: This optional feature will come into effect only when "PREFER CLASSIFICATION CODE OVER CODE GID" is enabled.
    1. If this optional feature is disabled:
      1. Whenever a new version of product classification type is loaded, all the product classification code GIDs belonging to the given classification type are updated in item classifications.
      2. Classification code GID is used to detect if an item classification should be marked as "Classification Invalid" or if an existing invalid classification has become valid again.
    2. If the optional feature is enabled:
      1. Transition to a new version of classification type will not change the classification code GID in item classifications.
      2. Classification code, which is usually constant for an item, will be used to detect if an Item classification should be marked as "Classification Invalid" or if an existing invalid classification has become valid again.

Impact

The following areas are affected.

Business Objects

The CLASSIFICATION_CODE column is added to the relevant tables for the following business objects which use product classification code GIDs:

  • Item Classification  
  • Product Classification Template
  • Trade Item Structure
  • Trade Item Structure Component
  • Trade Transaction Item Structure
  • Registration

    If the CLASSIFICATION_CODE column is NULL in the tables corresponding to these business objects, GTM derives the classification code from the Product Classification Code GID. When a record is saved, GTM populates this column if the data is not present.

    The field "Classification Code" is added to the finders and result pages of these business objects. The existing field "Product Classification Code" is renamed as "Product Classification Code (Deprecated)" to indicate that this field will be removed in a future release.
  • Product Classification on Transaction Line/Declaration Line: You can update the CLASSIFICATION_CODE column for this section by adding or updating classification data on the transaction line or declaration line via the UI or integration.
  • Reporting Quantity on Transaction Line/Declaration Line: you can populate the CLASSIFICATION_CODE column in the GTM_TRANS_LINE_REPORT_QUANTITY table by triggering the Convert UOMs action on the transaction or declaration.

Actions

The following actions support the CLASSIFICATION_CODE column:

Business Object

Action

Item Qualify for Trade Agreement

Item Origin

Qualify for Trade Agreement

Campaign

Approve Campaign

Campaign Lines

Approve Campaign Lines

Trade Transaction

Convert UOM

Assign License

Assign License Show Options

Create/Add to Existing Declarations

Execute Compliance Rules

Look Up Product Classification

Trade Transaction Line

Assign License

Assign License Show Options

Create/Add to Existing Declarations

Execute Compliance Rules

Look Up Product Classification

Qualify for Trade Agreement

Declaration

Convert UOM

Create/Add to Existing Declarations

Execute Compliance Rules

Look Up Product Classification

Declaration Line

Create/Add to Existing Declarations

Execute Compliance Rules

Look Up Product Classification


Integration

Inbound and outbound XMLs take input or send outbound XML element as classification code with a code derived from the product classification code GID.

Following inbound and outbound interfaces are modified:

  • Transaction Line / Declaration Line
    • Reporting Quantity
  • Item Classification Builder
  • Registration Builder
  • Structure Builder
  • Structure Component Builder
  • Transaction Line / Declaration Line Builder
    • Product Classification
    • Reporting Quantity

Agent Events

Following agent events are modified to consider the column CLASSIFICATION_CODE:

  • ITEM CLASSIFICATION - CLASSIFICATION ADDED REMOVED
  • ITEM CLASSIFICATION - CLASSIFICATION MODIFIED
  • GTM TRANSACTION LINE - CLASSIFICATION CHANGED
  • GTM SHIPMENT LINE - CLASSIFICATION CHANGED

AES (Automated Export System) Changes

  1. Document Type changes:
    1. Added new document validation rule, AES VALIDATE LINE CLASSIFICATION CODE, to the document type.
    2. Added new saved queries to the saved conditions of the following document validation rules:
      1. AES VALIDATE LINE PROD CLASS CODE
      2. AES VALIDATE USML DETERMINATION NUMBER
      3. AES VALIDATE LINE ML US NOT POST DEPARTURE
  2. Report changes:
    1. AES Filing Report considers the CLASSIFICATION_CODE column when the optional feature "PREFER CLASSIFICATION CODE OVER CODE GID" is enabled.

Saved Queries

The following PUBLIC saved queries are modified to consider the column CLASSIFICATION_CODE when the optional feature "PREFER CLASSIFICATION CODE OVER CODE GID" is enabled.

  • CCI VALIDATE HS PROD CLASS TYPE
  • CCI VALIDATE TRANS HS PROD CLASS TYPE,
  • TARIFF RATES FOR TL CLASSIFICATION CODE
  • TARIFF RATES FOR DL CLASSIFICATION CODE
  • TARIFF RATES FOR ITEM CLASSIFICATION CODE
  • PROD CLASS TEMPLATES WITH INVALID CODES
  • TARIFF RATES FOR ITEM CLASSIFICATION 

Recommendations

  • Run the "Update Classification Version" process for the commonly used product classification types. This populates the new classification code for all the objects updated via the process (except for a transaction line and a declaration line).
  • Manually change the saved queries which use the "GTM_PROD_CLASS_CODE_GID" column to use the "CLASSIFICATION_CODE" column from the respective tables.
  • Manually check the custom agent actions/custom agent events that use the “GTM_PROD_CLASS_CODE_GID“ column and change to consider the "CLASSIFICATION_CODE" column.
  • Enable the optional feature "PREFER CLASSIFICATION CODE OVER CODE GID" and check the relevant business actions/saved queries/any other customized functional areas.
     

Related Topics