- Revision History
- Overview
- Update Tasks
- Feature Summary
- Global Trade Management
-
- Transportation and Global Trade Platform
- Global Trade Management (Base)
- Trade Compliance
- Trade Agreements
-
- Classification Type Is Optional on Campaign Lines
- Improvements to Qualify for Trade Agreement Process
- Improvements to Qualify for Trade Agreement Agent Action on Item Qualification
- Support for Item Structures That Produce Batch Quantities
- Enhanced Support for Country of Origin Determination of Trade Item Structure Component
- Improvements to Creating a New or Updating an Existing Item Qualification
-
- Customs Management
- Trade Incentive Programs
-
- Trade Incentive Program
- Trade Incentive Program Type
- Trade Incentive Program Sub Type
- Entry Exit Profile
- Trade Incentive Program Rule
- Trade Incentive Program Rule - Product Specific Rule
- Item Applicable Trade Incentive Program
- Record Entries Into Programs Action
- Match Exits to Entries Action
- Trade Incentive Program Inventory
- Trade Incentive Program Inventory Movements
- Logic Configuration Enhancement
-
This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
Date | Module | Feature | Notes |
---|---|---|---|
30 AUG 2023 | Transportation and Global Trade Platform | Enhanced Workbench | Updated document. Added additional setup details for Shipment Timeline feature. |
30 JUN 2023 | Created initial document. |
HAVE AN IDEA?
We’re here and we’re listening. If you have a suggestion on how to make our cloud services even better then go ahead and tell us. There are several ways to submit your ideas, for example, through the Ideas Lab on Oracle Customer Connect. Wherever you see this icon after the feature name it means we delivered one of your ideas.
GIVE US FEEDBACK
We welcome your comments and suggestions to improve the content. Please send us your feedback at otm-doc_us@oracle.com.
DISCLAIMER
The information contained in this document may include statements about Oracle’s product development plans. Many factors can materially affect Oracle’s product development plans and the nature and timing of future product releases. Accordingly, this Information is provided to you solely for information only, is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle.
This information may not be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. Oracle specifically disclaims any liability with respect to this information. Refer to the Legal Notices and Terms of Use for further information.
This section gives you information to help you plan, deploy, and validate your update. We make frequent additions to this document, so don’t forget to check back and get the latest information before your update starts.
Review the Release Notes
The Release Notes identify required actions, known issues, corrections, new parameters and properties, renamed properties, and deprecated items.
Read the Documentation
The documentation library contains the release notes, the online help, the implementation guides, the API guides, preparation and testing recommendations, and links to other resources.
Read On My Oracle Support
Use the following resources to prepare for and validate your Oracle Engagement Cloud update.
- Doc ID 2174060.2: Information Center: Oracle Transportation Management. This document aggregates publications as well as describing documentation, support, and integration options.
- Doc ID 796594.1: Oracle Transportation and Global Trade Management Documentation and Training Resources. Describes the published documentation available. Use this document to ensure that you leverage all existing resources to learn about, install, implement, and use this product.
- Doc ID 2195580.1: Oracle Cloud Applications - Transportation and Global Trade Management Cloud: Get Started with Your Implementation. Begin with this document to start your implementation.
- Doc ID 2095528.1: Oracle Cloud Applications - Transportation and Global Trade Management Cloud: Quarterly Update Planning. Describes standard quarterly update policies and practices.
- Doc ID 2096782.1: Oracle Cloud Applications - Transportation and Global Trade Management Cloud: Quarterly Update Planning FAQs. Helps with the understanding of the upgrade process.
- Doc ID 2095509.1: Oracle Cloud Applications - Transportation and Global Trade Management Cloud: Environment Refresh Policy. Describes how to prepare for and request an environment refresh.
Column Definitions:
Report = New or modified, Oracle-delivered, ready to run reports.
UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.
UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.
Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.
Ready for Use by End Users Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features. |
Customer Must Take Action before Use by End Users Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing. |
|||||
---|---|---|---|---|---|---|
Feature |
Report |
UI or |
UI or |
|
||
Manager Layout Enabled Actions: Add Document, Copy Document, Link Document |
||||||
Data Export REST API - Updated Limits When Run Synchronously |
||||||
Support Integration Saved Query with the gtm:Contact Element |
||||||
Improvements to Qualify for Trade Agreement Agent Action on Item Qualification |
||||||
Enhanced Support for Country of Origin Determination of Trade Item Structure Component |
||||||
Improvements to Creating a New or Updating an Existing Item Qualification |
||||||
Transportation and Global Trade Platform
Improvements to Enhanced Workbench
This feature provides a set of new capabilities and features for the Enhanced Workbench. Improvements have been provided in several areas, including:
- Multiple Parents Selected Show All Details
- Favorites for Enhanced Workbench Layouts
- Personalization - Browser Based
- Table Parameters - Delete and Edit Show/Hide and New Look
- Drag/Select Text - Copy and Paste Table Text Option
- GTM - Work Queue Available
- Improve Focus Highlight Selected - Table, Gantt, Map
- Gantt - Drag and Drop - Shipment Stop Table to Appointment Gantt and Shipment Table to Driver Gantt
- Appointment Gantt - General Usability Improvements
- New Component Type – Shipment Timeline
- ALK - Map Move Order Drag and Drop
Multiple Parent Select Show All Details - Tables
This feature, when configured, will show all the Detail records for a Parent record grouped by the Parent record's ID when (multiple) Parent records are selected. You will find this feature extremely useful in any scenario where the task to be accomplished requires viewing and performing actions on a set of Detail records related to multiple Parents and having a reference to the Parent and their Detail records is beneficial.
In the example below, two Parent shipment records are selected, with this feature configured, the eight related Detailed Order Release records are displayed - grouped by their Parent records as shown below.
The view below is the same, but in this case the Detailed records are collapsed, in the collapsed view note you see the reference for the Parent and a count for the number of Detail records in this case six Detail records for Parent 24790 and two Detail records for Parent 24796.
The setup up for this example is below. The Detail Table Combined Details option supports the Multiple Parent view shown above. Note that the original Detail Table view is still supported.
Favorites for Enhanced Workbench Layouts - Enhanced Workbench Infrastructure
This feature extends the Favorites concept available on many objects in the system to the Enhanced Workbenches, you can now tag your Enhanced Workbenches as Favorites and use the Favorites designation and grouping to easily select your Favorite Enhanced Workbench from either the Workbench Layouts or from the Favorites Menu.
In the example below - the Workbench Layout dropdown now provides two groupings - Favorite Layouts - which lists the Enhanced Workbenches tagged as Favorites alphabetically and then all the rest of the Workbench Layouts are grouped under the Non-favorite Layout grouping - again, in alphabetical order.
As shown below, you can also use the Favorites icon on the Global Header to navigate to the Enhanced Workbenches you have tagged as Favorites.
Selecting an Enhanced Workbench to be a Favorite can be accomplished using the Enhanced Workbench Menu or in the Workbench Manager.
In the example below the Restricted Party Screening Enhanced Workbench has been selected as a Favorite, this is accomplished by selecting the Favorites star icon as shown.
In the example below the Workbench Manager is used to select the Enhanced Workbenches as Favorites.
Like other objects, you can also perform a search for your Favorites in the Workbench Manager Finder.
Personalization - Browser Based - Enhanced Workbench Infrastructure
This feature provides you with the ability to personalize your Enhanced Workbench for the attributes listed below. This personalization is stored in the browser and as such will be available until your browser is refreshed - for example - the browsers cache is cleared, or the computer is restarted.
Attributes that can be personalized:
- Splitter position
- Disclosed tab per pane
- Width of columns on table
- Show/Hide columns on the table
- Column rearrangement on the table
As originally configured, the Enhanced Workbench below has the following layout.
Below is the same Enhanced Workbench after it has been Personalized.
- Splitter positions changed
- SCHEDULED Tab is now the initial focus v ALL ORDERS
- Column widths changed
- Columns hidden
- Columns rearranged
After logging out and logging back in, the Personalizations are retained for the Enhanced Workbench.
Personalization Summary:
- User + Browser specific
- Saved to the user’s browser
- Default behavior – No Additional Step to Enable
Personalization is lost when
- Layout is edited
- Screen Set associated with the table is modified
- Browser is updated/cache cleared
Personalization Includes:
- Panel Splitter Positions
- Disclosed/Open Tab per Panel
- Table Column Widths
- Table Column Order/Position
- Table Columns Hidden/Show
Table Parameters - Table Toolbar Icon Management - Delete and Edit Show/Hide and Table Parameters New Look
You now have the option of configuring your tables using the Table Parameters to Show/Hide the Edit and/or Delete icons this is in addition to the other Show/Hide Toolbar Icons provided as shown below. The Show/Hide for the Edit and/or Delete icons adds the configuration option to the Table Parameters - you still have the option to configure Edit/Delete via the Screen Set.
In addition, as part of this feature the Table Parameters UI has also been updated with a new look and feel.
Edit and Delete both set to Show.
Drag/Select Text - Copy and Paste Table Text Option
This feature allows you to Toggle between having the Left Mouse button initiate a Drag and Drop action or having the Left Mouse button support the ability to Select Text for you to Copy and Paste. The Table Parameter Drag/Select Text controls this feature.
By default the Parameter is set to Drag and Drop mode, but you can toggle to Select Text mode by selecting the Drag/Select Text icon as shown below.
In the image below, the Drag/Select Text parameter is setup for the Select Text mode - allowing you to select text and cut and paste.
With the left Mouse Button in Select Text mode, for this example, the Destination Location ID is selected, then doing CTRL-C copies the select text.
Then the selected text from above can be pasted into a field, for this example the UDA 1 field is used to paste the copy issued above into the field via paste/CTRL-V.
GTM - Work Queue Available
This feature enables you to use work queues with the Enhanced Workbench. You can configure the following objects to use Work Queues with the Enhanced Workbench:
- Contacts
- Parties
- Items
- Trade Transaction Lines
For more information see the GTM What's New Feature - WORK QUEUE AVAILABLE IN ENHANCED WORKBENCH
Highlight Selected Table, Gantt, Maps
This feature improves the highlighting done across components (Table, Map, Gantts) for selected objects. In the example below, the selected shipment is highlighted in both the Gantt and the Map. The improved highlighting is provided for the Shipment, Driver, and Work Assignment Gantt.
Drag and Drop - Shipment Stop Table to Appointment Gantt and Shipment Table to Driver Gantt
This feature provides you with a Drag and Drop experience for your Shipment Table to Driver Gantt and your Shipment Stop to Appointment Gantt tasks.
In the example below - a Shipment is selected in the Shipment Table, then via a Right Click, the Action menu is invoked - selecting the action Start Drag to Gantt initiates the Drag and Drop process for the selected Shipment. Once initiated, the interaction follows the normal Drag and Drop operation - select and Drag the selected Shipment using the Left mouse, and then Drop the Shipment on the Driver who you wish to assign the shipment to.
The Drag initiated above for Shipment 02131 was dropped on the Driver 2021PERFDR109 with a 9:17 Start Time.
In the example below, a Shipment Stop appointment is scheduled using Drag and Drop. Again, the Shipment Stop is selected and the process initiated by selecting the Shipment Stop in the Shipment Stop Table using a Right Mouse Click, then selecting the Start Drag to Gantt action, and then Dragging to and then Dropping the Shipment Stop (with Left Mouse) to the desired appointment slot on the Appointment Gantt.
The Shipment Stop is dropped at the desired Slot and Time - for the selected Location Resource.
Appointment Gantt - General Usability Improvements
This feature provides some usability improvements for the Appointment Gantt.
- The Screen Set columns is now being honored in the Location Resource table portion of the Appointment Gantt. This includes honoring the following settings from the Screen Set:
- GID column width
- Sort Order
- Columns width
- The Appointment Display String is now being honored.
Other Improvements
Shipment and Order Release pseudo fields are now editable in Enhanced Workbench, providing you with equivalent behavior between the Shipment/Order Release screen set usage in the Finder and the Enhanced Workbench.
New Component Type – Shipment Timeline
This feature provides you with a new Component Type - Shipment Timeline, that can be used to display the Events for a Buy Shipment on a Timeline.
To add the Shipment Timeline to your Enhanced Workbench you will need to:
- First - Add the Buy Shipment Table to the desired workbench:
- Component Type = Table
- Object = Buy Shipment
- Then - Add the Shipment Timeline to the Enhanced Workbench:
- Component Type = Shipment Timeline
- Associated Table = Buy Shipment - the Buy Shipment will be available in the Associated Table drop down list assuming that you added the Buy Shipment to the Enhanced Workbench first.
- Save the Workbench.
- Once setup correctly - the Shipment Timeline will show the Tracking Events for the highlighted Buy Shipment in the Enhanced Workbench.
ALK - Map Move Order Drag and Drop
This feature provides - for the ALK/Trimble Map - the ability use a map based drag and drop action to move an order or orders to a shipment.
You initiate the drag and drop action by selecting the order to move with the right mouse. In the example below, order MS-0045 has been selected.
The selected order is then dragged to the desired target shipment. In the example below, the order is being moved to shipment 24324.
Before committing the move, the final input is to confirm the move. In this case move order release MS-0045 to shipment 24324.
Then the result of the move is shown after the map refreshes - as shown below - order MS-0045 is now stop 2 on shipment 24324.
The drag and drop action also supports the option for multi-select - in the example below, two orders have been selected for the move action.
This feature provides additional features and usability improvements for the Enhanced Workbench - giving you more options for implementing Enhanced Workbenches to support more use cases and users.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
NOTE: The legacy Workbench developed using Oracle Application Development Framework - ADF, has been deprecated and the supporting code for the ADF based Workbenches is scheduled to be removed from the application in an upcoming release. If you have not done so already - you should move to the new Enhanced Workbenches as soon as possible to avoid any issues.
The Enhanced Workbench relies on REST calls to access data, due to the current security infrastructure, the following additional setup is required.
- For users with any role other than ADMIN and DEFAULT the following Access Controls are necessary and can be added to the User Role or directly to the User:
- REST – Workbench
- Workbench – Create
- This is required only for Add/Delete
- Can also revoke the ability to Add/Delete
Manager Layout Enabled Actions: Add Document, Copy Document, Link Document
This feature provides you with new manager layout enabled document actions - Add Document, Copy Document and Link Document.
The original compound document action - Add Document (which supported New, Copy, and Link as options) has been deprecated and will be removed from the application in an upcoming update.
The new menu for the Documents actions is below, Add Document (replaces the old Add Document action), Copy Document and Link Document are now individual actions.
Copy Document
With the individual actions for each of the document actions - each action is now designed for the action being run. In the Copy Document action - the action has a single input - the Document to be copied.
Below is the Copy Document action input, it's limited to specifying the Document to copy.
Link Document
Like the Copy Document action, the Linked Document action is also tailored to the action's requirements.
The Linked Document action has a single input - the Document to be linked.
Add Document
For the Add Document action there are more inputs related to the action - and as such - there are opportunities to take advantage of the Manager Layout enabled capabilities to set defaults (like Document Type), hide fields, move fields and make fields read only etc.
Below is the standard New Document action input,
The New Document action result is below.
In the example below, the Add Document action has been configured using Manager Layout capabilities. In this example, the fields Effective Date, Expiration Date, Add New Revision and Annotation are hidden.
Below is the Add Document action with the fields Effective Date, Expiration Date, Add New Revision and Annotation hidden.
The Manager Layout enabled actions - Copy Document, Link Document and New Document, simplify the inputs by limiting the inputs to each of the actions and provide options to further improve usability by configuring the options using Manager Layout capabilities - i.e. hide unnecessary fields, set defaults etc.
Steps to Enable
To take advantage of the manager layout enabled capabilities provided by the new manager layout enabled actions Copy Document, Link Document and Add Document, you will need to copy the Public Manager Layouts for the action you want to configure, then with the copied version of the Manager Layout you can configure the layout as desired, - hide fields, set defaults, move fields, change labels etc. The Manager Layout functionality is accessed via Configuration and Administration > User Configuration > Manager Layout. After the Manager Layout for the Action is configured you will need to add the configured action to the desired screen set.
Tips And Considerations
NOTE: The Link Document action is not yet available for both the GTM Declaration and GTM Item Origin objects. This is consistent with the capabilities that were available previously for these objects using the now deprecated compound Add Document action, i.e., for these objects, the Link Document option/action was never implemented.
NOTE: You can add the legacy compound action Add Document - renamed to Add Document(Deprecated) to your action menu if there is a reason to do so.
To add back the deprecated Add Document action to your menu, you would need to go to the appropriate non-Public screen set and add the Add Document(Deprecated) to the object's action menus as shown below.
Data Export REST API - Updated Limits When Run Synchronously
This feature establishes a more restrictive limit for the Data Export REST API when run Synchronously. The Synchronous mode is intended to be used with a single table and with limited volumes. The general usage of the Data Export REST API is intended for Asynchronous processing.
- The more restrictive limits for Synchronous processing are now:
- Time: 30 seconds
- Size: 1MB
The new limits are intended to avoid performance issues related to running the Data Export API Synchronously.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
The limits for Asynchronous time and message size are:
- Time: 180 seconds
- Size: 1 GB
Enable Update Operations for External Statuses
This Optional Feature, Enable Update Operations for External Statuses, when enabled, adds REST Services support for Create, Update and Delete for the External Status and Status Values for the business objects listed below.
External Status and Status Value Create, Update and Delete supported objects
- Contact
- Driver
- Order Base
- Claim
- Consol
- Document
- Equipment
- GTM Campaign
- GTM License
- GTM Transaction
- Invoice
- Item
- Location
- Order Movement
- Order Release
- Power Unit
- Quote
- Shipment Equipment
- Shipment
- Tender Collaboration
- Voucher
- Work Invoice
For Create, Update and Delete a check will be done on the Status Type to confirm that it is an External Status Type. Internal Status Types will be treated as a read-only and will be skipped for Create, Update and Delete operations.
Allows for easy update/setting of External Status Types and Values on the supported objects.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
To take advantage of this feature, the External Status Types and Values must exists before they can be added to a new object.
Usability, Performance and Stability
The Property Tree provides you (the DBA.ADMIN user) with a logically grouped view into the many properties available within the system. The Property Tree provides you with a vastly improved approach for identifying and understanding the configuration options available using the properties available in the system.
The Property Tree view is available via Configuration and Administration > Property Management > Property Tree.
For this update additional Property Tree entries have been provided for:
- Client Sessions
- Finder
- Notifications
- Order
- Planning
- UI
The additional Property Tree entry - Client Session is shown below.
The additional Property Tree entry - Finder is shown below.
The additional Property Tree entry - Notifications is shown below.
The additional Property Tree entry - Order is shown below.
The additional Property Tree entry - Planning is shown below. Note that the coverage for Planning is fairly extensive - so only the 2nd level view is expanded.
The additional Property Tree entry - UI is shown below.
This feature improves visibility to and the understanding of the many available properties in the system.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
Only the DBA.ADMIN user can access and use the Property Tree page.
The Property Tree is meant to provide visibility to the more functional properties provided with the application.
UI Infrastructure Usability Improvements
This feature provides a number of UI usability improvements including:
Define Workbench Layouts for Business Monitor Queries (Optional)
In the example below the Business Monitor Query ACCEPTED SHIPMENTS has been configured with the Workbench Layout option configured.
With the configuration above, the ACCEPTED SHIPMENTS Business Monitor now includes the icon link to the Workbench Layout associated with the query.
The Link ACCEPTED SHIPMENTS will - as usual - Show Result Count and open the search results using the defined Screen Set. The Link to the Workbench will provide more context and information.
Disable Saved Query Edit in a Screen Set
This feature provides you with the option to setup your Screen Sets to allow or not allow access to editing the Saved Query on a Screen Set.
The default - unchecked - is to allow for the edit - as shown below - current behavior.
Selecting the Allow Edit Saved Query will hide/disable the Edit for Saved Queries as shown below.
“One Of” Search Supports Both Comma and Space Separated Lists as Inputs
This feature allows you to define your input list for your One Of searches as accepting Commas or Spaces or just Commas- previous behavior.
The option is available in the UI CONFIGURATION Logic Configuration as shown below. ONE OF SEARCH INCLUDE SPACE - the Default is Commas only, setting the parameter to TRUE allows Spaces or Commas.
Remove Leading/Trailing Spaces on Paste in Search Criteria
This feature - when configured - removes leading and following spaces for your Search Criteria that you pasted into the finder.
The parameter REMOVE LEADING TRAILING SPACE ON PASTE , controls this option - the default setting is FALSE - spaces are not removed.
When set to TRUE, spaces are stripped when pasted into Search criteria fields. When set to FALSE spaces will remain and be considered as part of that Search criteria
This feature provides options to improve UI Usability.
Steps to Enable
You don't need to do anything to enable this feature.
Domain Settings - Purge Only (No Archive)
This feature is provided to accommodate restrictions related to data retention, with this feature you have the ability to delete data marked for Purge without Archiving the data first - either by domain or for all domains.
You can select the Purge Only (No Archive) check box to have a domain's data not be archived when it is cyclically purged. In order to use this check box, you must work with Oracle Support. Oracle Support can set the purge capabilities two ways after you contact them.
- The first setting Support can make is to enable non-archiving purging by domain. When set that way, when you select the Purge Only (No Archive) check box, the purge will not archive data. With this setup you have domain level control for whether or not there is no archive when purging.
- The second setting enables the non-archiving purge for ALL domains. In this scenario, the Purge Only (No Archive) check box is NOT functional on the Domain Settings page, since the Support setting applies to all domains. Data in all domains will be purged without archiving.
NOTE: If you select this check box, domain data will be completely lost when the two-year purge starts. See the "Purge Only Option" section of the Administration Guide for details.
This feature accommodates restrictions related to data retention; you can now Purge data without Archiving - which eliminates the issue of retaining data for longer than intended in an Archive schema.
Steps to Enable
This feature requires a Change Request (CR) be submitted to enable this feature.
Tips And Considerations
NOTE: Once enabled, with the No Archive option (either by domain or for all domains) - domain data will be completely lost when the two-year purge starts.
Key Resources
- See the "Purge Only Option" section of the Administration Guide for details.
Improve DirLoadServlet Performance
This Optional Feature, when enabled, will improve the performance of updates through DirLoadServlet.
Feature provides will improve system performance for updates running through the DirLoadServlet.
Steps to Enable
You don't need to do anything to enable this feature.
Global Trade Management (Base)
Improvements to the Review Match Factor Action
This feature provides enhancements to the Review Match Factor action. Color coding has been added to better see which parameters match. In addition, changes have been made to the gtm.rpls.reviewMatchFactor.runForAllParameters property.
Color Coding of Match Results
Color coding has been added to the Combined Match Factor column highlighting if a parameter is a match or not a match. If a parameter is a match, the word 'MATCH' is displayed in green. If a parameter is not a match, the words 'NOT A MATCH' are displayed in red.
Changes to the gtm.rpls.reviewMatchFactor.runForAllParameters Property
In 23A, the gtm.rpls.reviewMatchFactor.runForAllParameters property was introduced to remove a limitation in the Review Match Factor action where, if the action found a parameter that was not a match, the analysis would stop. The property was set to 'true' in 23A so that the action would continue running regardless of whether all parameters matched or not. In 23C, this property is removed so that the new behavior of analyzing all parameters is the default functionality. This provides you with a clearer picture when you are analyzing a party/restricted party match via the Review Match Factor action.
The enhancement improves the user experience and makes it easier to understand the data being displayed.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- For more information on restricted party screening, please refer to the GTM Configuration/How To Topic called 'Restricted Party Screening' in help.
Support Integration Saved Query with the gtm:Contact Element
This feature enables you to find contact records using integration saved queries with the <gtm:Contact> element. This feature expands an existing capability to support contact. For example, using integration saved queries that you define, GTM can find an Involved Party Contact and then update or delete that contact record.
This feature improves the flexibility of integrations to the application.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
The use of integration saved queries is an existing capability which provides flexibility for identifying and searching for information without using a GID. You can define integration saved queries via Business Process Automation > Power Data > Integration > Integration Saved Queries.
Key Resources
- For more information on using integration saved queries, please refer to the Integration Guide.
Enhancements to the Trade Item Structure Manager
The Trade Item Structure edit page has been enhanced so that the Trade Item Structure Components are displayed on a separate tab. On the Trade Item Structure Components tab, you can see all of the components listed within a grid. This enhancement aligns the Trade Item Structure manager with other GTM managers. In addition, the Trade Item Structure Components tab supports manager layout which enables you to configure the information shown on the components based on your business needs.
On the Trade Item Structure edit page, click the Trade item Structure Components tab to see a list of the components.
When you click the pencil icon to the right of a component, you can then see the details.
This enhancement aligns the Trade Item Structure manager with other GTM managers and provides for enhanced flexibility in configuration and faster user interface loading.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
With this enhancement, the Trade Item Structure Components tab within the Trade Item Structure supports manager layouts which enables you to configure the components user interface based on your business needs.
Key Resources
- For more information on configuring the user interface, please refer to the OTM How To/Configuration Topic called 'Configuring the User Interface'. Navigate to the 'Configuring Manager Layouts' section.
Generate Certificates of Origin from Item Qualification
This feature enables you to generate a certificate of origin for your finished goods which qualify for a trade agreement. A new Generate Certificate of Origin action is available from the Item Qualification. When you trigger the action, GTM enables you to enter certain information including:
- Document Type - enter the document type associated with your certificate of origin
- Trade Agreement - populated by GTM from the item qualification record
- Country of Import - if applicable, enter the country of import
- Exporter ID - enter the ID of the exporter
- Producer ID - if applicable, enter the ID of the producer
- Importer ID - enter the ID of the importer
- Effective/Expiration Dates - enter the dates to be populated on your certificate of origin
- Issuing User ID - enter the ID of the issuing user
When you click Run, GTM matches the Country of Origin and Trade Agreement with details entered on the action. If these match, GTM generates the certificate of origin based on data in your item qualification and the information you entered on the action. If these do not match, then a certificate of origin is not generated.
For fields such as Importer, Producer and Exporter, GTM populates the report with the name and address corresponding to the ID you entered. The confirmation page displays the Item Qualification ID used to generate the certificate, the Document ID, if it is a Standard Document and a button to view the content (ie. certificate of origin) generated.
The certificate of origin includes all the pertinent information in an out of the box document.
This feature provides an easy method for users to generate certificates with fewer clicks and less setup, while helping them support their end customers needs.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
When generating the certificate of origin, GTM matches the Country of Origin and Trade Agreement with details entered on the action. If these do not match, then a certificate of origin is not generated.
Work Queue Available in Enhanced Workbench
This feature enables you to use work queues with the enhanced workbench. You can configure the following objects to use work queue with the enhanced workbench:
- Contacts
- Parties
- Items
- Trade Transaction Lines
The easiest way to enable a work queue is to copy an existing enhanced workbench. Once configured, the work queue capability works the same as in previous releases. For example, you can copy the public RESTRICTED PARTY SCREENING ENHANCED WORKBENCH which ships with GTM and configure it to be a work queue. Navigate to Configuration and Administration > User Configuration > Enhanced Workbench.
- From the Enhanced Workbench menu, click Select Layout and select the PUBLIC Workbench Layout = 'RESTRICTED PARTY SCREENING ENHANCED WORKBENCH' from the drop-down list.
- From the menu, select Copy Layout and enter a name for your new layout. Click OK.
In the new layout you've created, click the Edit icon on the top right of the Parties pane. Then click the Pencil icon.
Under Population method, select 'Work Queue'.
You can also select a Default Work Queue (optional). Click OK.
In the menu, click Done Editing.
Note that in the drop down in the Parties pane, you are now selecting a Work Queue instead of a Saved Search. If you did not set a default work queue, select a work queue from the list. In this example, a subset of the parties that require review are displayed. As with the restricted party screening enhanced workbench, you can review the list of parties that are potentially matched to restricted parties and determine if they are/are not a match.
Work Queues enable users to divide and share a common workload, ensuring that a larger team doesn't simultaneously work on the same issues or overlap their efforts.
Steps to Enable
To take advantage of this feature, you need to copy an existing enhanced workbench or create a new enhanced workbench. Once you've created the new enhanced workbench, you can enable work queue for the workbench.
- In the main pane of the enhanced workbench, click the Edit icon on the top right of the main pane. Then click the Pencil icon.
- Under Population method, select 'Work Queue'.
- When you are done editing your enhanced workbench using work queue, click Done Editing in the menu on the left.
Tips And Considerations
If you have existing enhanced workbenches for the supported objects, you can copy those enhanced workbenches and enable them to use a work queue.
Key Resources
- For more information about:
- Configuring work queues, please refer to the Master Data > Power Data > Configurations > Work Queue help topic.
- Using enhanced workbenches, please refer to the Configuration and Administration > Enhanced Workbench help topic.
- Adding an enhanced workbench work queue to the menu, please see the Configuration and Administration > User Configuration > Menu Manager help topic.
Allocate Weight by Weight on Transaction and Declaration
This feature enables you to allocate a quantity from the header to the lines based on another quantity. The Allocate Weight by Weight action is available as a manual action or automation agent action on the Trade Transaction and the Declaration. For example, if you have the gross weight of a container on the Transaction/Declaration level but the net weight for each of the lines, GTM can allocate the gross weight from the header to each of the lines based on the net weight. In this scenario, the total net weight across the transaction is 20,000 KG. This does not need to be specified at the transaction level. On each line, you specify a net weight:
- Trade Transaction Line 1 - 8,000 KG net weight (40% of total net weight)
- Trade Transaction Line 2 - 12,000 KG net weight (60% of total net weight)
GTM uses the net weight on each line to determine the gross weight for each of the lines based on the total gross weight of the transaction. On the transaction/declaration level, specify the gross weight:
- Trade Transaction - 25,000 KG gross weight
When you run the Allocate Weight by Weight action, you define the quantity qualifiers you want to use for allocation. In this example, you are allocating the GROSS WEIGHT by the NET WEIGHT.
Since GTM knows the gross weight of the entire transaction and the net weight at each line, it can calculate the gross weight for each line:
- Trade Transaction Line 1 - 40% * 25000 = 10,000 KG gross weight
- Trade Transaction Line 2 - 60% * 25000 = 15,000 KG gross weight
This feature provides for easier setup of data handling and time savings for users by reducing the data they need to enter for each declaration.
Steps to Enable
You don't need to do anything to enable this feature.
Assign Preference Criteria to Transaction Line
You can now assign the preference criteria to the transaction line as part of the trade agreement qualification process. Preference criteria provides details about how your finished good qualifies for a trade agreement. For example, is it wholly obtained, does a product specific rule apply such as tariff shift or regional value content method, is de minimis met and so on. The preference criteria is assigned as part of the Qualify for Trade Agreement action on the transaction line.
You can create the preference criteria as defined by the trade agreement within Master Data > Power Data > Trade Agreements > Preference Criteria.
Once you create the preference criteria, it can be automatically assigned to a trade transaction line using the Qualify for Trade Agreement action or agent action.
This feature allows you to capture more information relevant to the business process and correctly populate regulatory documentation that you provide to your customers.
Steps to Enable
You need to configure GTM prior to assigning the preference criteria to a transaction line.
- You need to create the preference criteria records as defined in the trade agreement. Preference Criteria is an existing object in GTM.
- Trigger the Qualify for Trade Agreement action on your item-based objects. GTM qualifies your bills of material (modeled as trade item structures) for trade agreement qualification. If successful, GTM creates or updates the item qualification record. If the preference criteria can be determined, GTM assigns the Preference Criteria and displays the Justification Code and Justification Description with more details.
- Once the preference criteria is assigned to the item qualification record, it is available to be copied to the transaction line when you run the Qualify for Trade Agreement action on the line.
Tips And Considerations
Depending on the bill of material being qualified and the preference criteria defined by government agencies, there may be times where GTM cannot automatically determine and assign the preference criteria as part of the qualification process. In this instance, you can manually assign the preference criteria.
Key Resources
- For more information on trade agreement qualification, please refer to the GTM How To/Configuration topic called Trade Agreement Qualification.
Classification Type Is Optional on Campaign Lines
This feature enables the Product Classification Type to be optional on campaign lines. For certain qualifications such as a qualification not related to a trade agreement, classification data may not be required from the suppliers. By changing this field from a read-only field to an editable field, suppliers can determine when they want to add the Product Classification Type and Product Classification Code to a campaign line.
The Logic Configuration assigned to the Campaign Type defines if a Product Classification Type should be editable. Set the Purpose = Item on the logic configuration. When a campaign is created, the Product Classification Type on the campaign lines created is editable. Make sure the Campaign Type you use on the action includes a logic configuration with a Purpose = Item.
- If you do not specify a Product Classification Type on the Create Campaign action, the Product Classification Type on the campaign and the campaign lines is null.
- If you do specify a Product Classification Type on the Create Campaign action, it is assigned to the Campaign. It will also be assigned to each campaign line. You can then update each campaign line accordingly.
By changing this field from a read-only field to an editable field, suppliers can determine when they want to add the Product Classification Type and Product Classification Code during the solicitation process.
Steps to Enable
- The Logic Configuration drives the workflow when you create a campaign. Create a logic configuration with a Logic Configuration Type = GTM CAMPAIGN CONFIGURATION. If you want the Product Classification Type to be editable on the campaign line, the Purpose should be set to Item.
- The logic configuration is then specified on the Campaign Type. The Campaign Type is mandatory when creating a campaign and defines the kind of campaign being created.
Key Resources
- For more information on campaigns, please refer to the GTM How To/Configuration Topic called 'Supplier Solicitation' in help.
Improvements to Qualify for Trade Agreement Process
This feature provides enhancements to the qualify for trade agreement process across item-based objects and trade transaction lines. Specifically, the configuration of the trade agreement including regional value content methods and formulas, has been simplified. This enhancement enables users to take advantage of data that is part of the logic or ships with GTM. In addition, enhancements have been made to the qualification report to show information that is important to you.
Simplified Trade Agreement Setup
The trade agreement configuration has been simplified, enabling you to use data that is part of the logic or ships with GTM. The following grids are impacted:
- Regional Value Content (RVC) Methods - When you run trade agreement qualification, GTM will determine which rules of origin product-specific rule to apply. All of the rule types included in the product-specific rule will be analyzed even if you do not specify a RVC Method in this grid. The RVC Methods listed on the trade agreement determine the priority order if multiple methods pass. For example, if your priority is 1- TRANSACTION VALUE and 2- NET COST and multiple RVC Methods pass, GTM will use the data related to the highest priority rule type that passes. If you do not set the priority on the trade agreement and multiple regional value content methods pass, GTM will use the data related to the last rule type that passes.
- Rules of Origin Formulae - GTM ships with formulas associated with the rules of origin rule types. If these formulas align with your use case, you can use the shipped formulas as part of trade agreement qualification. You do not need to specify them on the trade agreement. If you cannot use the formulas that ship with GTM, you can create your own formulas or copy a shipped formula, make the necessary changes, and assign it to the trade agreement. A few examples of when you may not be able to use the shipped formulas include: (1) the formulas defined by the trade agreement are different than the shipped formulas and (2) as part of your business, you use different quantity/value qualifiers than those in the shipped formula. When trade agreement qualification is triggered, GTM looks to see if a formula is defined on the trade agreement and if so, uses it. If not, GTM uses the shipped formula associated with the rules of origin rules type.
- Dependent Formulae - You can add formulas where you want GTM to perform a calculation. In previous releases, certain formulas needed to be defined for GTM to use in the qualification engine. This is no longer necessary since certain formulas are defined on the Reference Numbers grid and others have been moved to the logic. For example, it is no longer necessary to specify the Extended Value Formula and Component Extended Value Formula in this grid since those formulas are defined in References Numbers. But, you can add those formulas to the Dependent Formulae grid if you want visibility to the details of the formulas.
- Reference Numbers - The reference numbers MUST specify the two formulas that are used by the qualification engine to calculate costs across the bill of material including Value of Originating Material (VOM) and Value of Non-originating Material (VNM). The Reference Number Qualifier ID = RVC METHOD1-EXTENDED VALUE FORMULA specifies a Reference Number = Formula GID that is used to calculate the extended value. The Reference Number Qualifier ID = RVC METHOD1-COMPONENT EXTENDED VALUE FORMULA specifies a Reference Number = Formula GID that is used to calculate the component extended value.
Qualification Report Enhancements
Improvements have been made to show you additional information on the qualification report including:
- When the quantities of the finished good bill of material and/or intermediate component bill of material are greater than 1 EA, GTM displays the proper quantities across the bill of material in the report.
- Both a VOM column and VNM column have been added to the report to clearly see the values that are originating and non-originating for the finished good and it's components.
- When Rollup is applied, additional information is included in the report including the Applied Provision = ROLLUP and a Qualified Intermediate Components grid at the bottom of the report. The Qualified Intermediate Components grid includes information for each of the intermediate components bills of material included in the finished good bill of material.
In this example, a Qualification Report where ROLLUP is applied is shown:
These enhancements provide a broad set of improvements to trade agreement qualification including reducing data entry needs, simplification of formula setup, report improvements and additional logic to determine the country of origin of an intermediate good.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
In the Dependent Formulae grid:
- You do not need specify the formulas for Value of Originating Material (VOM) or Value of Non-originating Material (VNM) since they are included in the logic.
- You only need to specify the Extended Value Formula and Component Extended Value Formula if you want visibility into the formulas. GTM will determined the Extended Value Formula and Component Extended Value Formula to use in the qualification engine by the values defined in the References Numbers grid.
Key Resources
- For more information on trade agreement qualification, please see the GTM How To/Configuration Topic called 'Trade Agreement Qualification' in help.
Improvements to Qualify for Trade Agreement Agent Action on Item Qualification
When configuring agent actions for item qualifications, the Qualify for Trade Agreement Agent Action has been simplified. Since much of the data already exists on the item qualification, certain fields have been removed from the agent action. The following fields are now derived from the item qualification and no longer appear on the agent action:
- Country of Import
- Effective/Expiration Date
- Producer
- Minimum Operations Requirements Met
The enhancement to the qualify for trade agreement action on item qualification enables a more streamlined configuration and helps users to enter less data on the agent action.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
For more information on trade agreement qualification, please see the GTM How To/Configuration Topic called 'Trade Agreement Qualification' in help.
Support for Item Structures That Produce Batch Quantities
This feature adds a Quantity and UOM field to the Trade Item Structure. Previously, GTM assumed that the Trade Item Structure was related to a single finished good item. This enhancement enables you to enter a bill of material, modeled as a trade item structure, in a specific quantity. When GTM qualifies a bill of material for a trade agreement, it uses the quantity and UOM on the finished good and ensures that the calculations across the entire bill of material, including intermediate components, are performed correctly. The finished good quantity used during qualification is also shown on the qualification report.
On the Trade Item Structure, two new fields have been added: Quantity and Quantity UOM. If these fields are not populated, GTM defaults the quantity for the trade item structure is 1 EA in the qualification engine.
This feature enables support in GTM for qualifying item structures that produce batch quantities, rather than just a single unit of a finished good.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- For more information on trade agreement qualification, please see the GTM How To/Configuration Topic called 'Trade Agreement Qualification' in help.
Enhanced Support for Country of Origin Determination of Trade Item Structure Component
This feature provides enhancements when determining the country of origin for a component. When determining the country of origin of an intermediate component where an item origin record does not exist, GTM considers the country of the location on the inventory organization.
If a intermediate component does not have an item origin record defined, GTM determines the country of origin of the intermediate component in the following order and creates the item origin record:
- Country of Origin on the Trade Item Structure Component
- Country of the Location of the Inventory Organization associated with the Trade Item Structure Component (new capability)
- Country of Origin of the finished good
Country of Origin on the Trade Item Structure Component
First, GTM looks to see if a Country of Origin exists on the Trade Item Structure Component and if so, it is used when creating the item origin for the intermediate component.
If a country of origin does not exist, GTM moves to the next step.
Country of the Location of the Inventory Organization associated with the Trade Item Structure Component (new capability)
Next, GTM looks to see if a Country Code exists on the Location of the Inventory Organization on the Trade Item Structure Component and if so, it is used when creating the item origin for the intermediate component.
If a country code is not specified on the location, GTM moves to the next step.
Country of Origin of the finished good
Finally, GTM will use the country of origin of the finished good as defined in the item origin when creating the item origin for the intermediate component.
This feature uses related data records to streamline the data entering process for users saving them time and effort.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
In the PUBLIC Logic Configuration = GTM LOGIC CONFIGURATION DEFAULT, GTM does not ship with default values for the constraint sets defined in the 'Constraint Sets for Identifying Related Objects'. If you want to use this logic configuration for matching in the qualification engine, you can create a constraint set and assign it to the logic configuration. For determining the country of origin of a component, you would add the Constraint Set as the Parameter Value for the Parameter = ITEM ORIGIN FOR ITEM STRUCTURE COMPONENT.
Key Resources
- For more information on trade agreement qualification, please see the GTM How To/Configuration Topic called 'Trade Agreement Qualification' in help.
Improvements to Creating a New or Updating an Existing Item Qualification
Improvements have been made to the process when you run the Qualify for Trade Agreement action a second time. Since you already have an existing item qualification record, GTM uses the effective/expiration dates and the status of the item qualification to determine if the existing records should be overwritten or a new one created. Specifically:
- If the status of the item qualification is NOT STARTED, ELIGIBLE, or REQUIRES REVIEW, the item qualification is overwritten.
- If the status of the item qualification is DISCONTINUED, NOT QUALIFIED or QUALIFIED, the existing item qualification record is expired and a new record is created.
If you want to override this logic, you can use the 'gtm.roo.itemqf.overwrite.status' property. The property value is set to the status you want to override. If you are overriding more than one status, you can separate them by a comma.
This enhancement provides flexibility when running trade agreement qualification a second time and ensures that item qualification records are maintained for certain statuses.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
For more information on trade agreement qualification, please see the GTM How To/Configuration Topic called 'Trade Agreement Qualification' in help.
Support HOLD and HOLD RELEASE Messages Within AES Filing
The U.S. Customs & Border Protection (CBP) has update AES Filing to support 3 new response codes with a severity of Informational. The response codes are:
Response Code: 97H (SHIPMENT ON HOLD)
Narrative Text |
SHIPMENT ON HOLD |
Severity | INFORMATIONAL |
Proprietary Record ID / Data Elements | N/A |
X.12 Segment ID/Data Elements | N/A |
Reason | The shipment has been put on HOLD in AES. |
Resolution | The shipment is placed on hold by CBP for further inspection or missing documentation. Contact the CBP port at xxx-xxx-xxxx with your ITN information for further instructions on how to resolve the issue. |
Response Code: 97R (SHIPMENT HOLD RELEASED)
Narrative Text |
SHIPMENT HOLD RELEASED |
Severity | INFORMATIONAL |
Proprietary Record ID / Data Elements | N/A |
X.12 Segment ID/Data Elements | N/A |
Reason | The shipment on HOLD has been released. |
Resolution | The hold placed on the shipment has been released. The referenced shipment can be exported. |
Response Code: 26C (SHIPMENT HOLD RELEASED)
Narrative Text |
STATE OF ORIGIN / USPPI STATE MISMATCH |
Severity | INFORMATIONAL |
Proprietary Record ID / Data Elements | INPUT SC1 Record/U.S. State of Origin; Input N03 Record/USPPI State Code |
X.12 Segment ID/Data Elements | B108, and the USPPI State Code is N402 |
Reason | The U.S. State of Origin Code and the USPPI Address State Code do not match. |
Resolution | The State of Origin and USPPI State must match and be reported as the location from which the goods actually begin the journey to the port of exportas defined in section 30.6(a)(1)(ii) and 30.6(a)(4) of the Foreign Trade Regulations. Any reporting errors must be corrected and retransmitted. For further assistance, contact the Census Bureau’s Trade Regulations Branch at 1-800-549-0595, (Option 3) |
Existing Configuration - Shipment Added Response
The existing setup for a shipment added response is as follows:
- A tracking number is sent as a reference number to match the document in Global Trade Management (GTM), and the response code is sent as "A SHIPMENT ADDED".
- Once the AES response is posted to GTM, a tracking event is created.
- On the creation of the tracking event, the event "TRACKING EVENT PROCESSING REQUEST" is triggered.
- GTM ships with an automation agent “PROCESS CUSTOMS FILING RESPONSE” for the data query type “TRACKING EVENT” listening to the event "TRACKING EVENT PROCESSING REQUEST". The agent is setup in GTM to perform the following:
- Match the document by tracking number
- Set the Customs Filing Response Status on the document
- Copy the ITN number to declaration
The following is an example of the AES response sent in case a shipment is added:
ISA*03*942805249 *01* *ZZ*USCSAESTEST *01*942805249 *230323*0157*^*00405*777593775*0*T*~
GS*AG*USCSAESTEST*942805249*20230323*0157*777593775*X*004050
ST*824*777593775¼BGN*01*942805249*20230323***XT
N1*01*123 COMPANY*24*94280524900
REF*01*593775 (This is the tracking Number)
OTI*02*A1*942805249
OTI*02*B1*94280524900
OTI*02*SC1*202303231125
OTI*02*ES1*X20230323632229 (This is the ITN Number)
TED*974* A SHIPMENT ADDED
OTI*02*Y1*94280524900
OTI*02*Z1*942805249
SE*12*777593775
GE*1*777593775
IEA*1*777593775
Configuration Changes for the New Response Codes
Shipment with a Response Code of 26C
- For a shipment with a Response Code = 26C, the existing configuration can be used. Once the AES response reaches GTM, a tracking event is created. The existing agent setup continues to work and no configuration change is needed.
Shipment with a Response Code of 97H (HOLD) and 97R (HOLD RELEASE)
- Once a shipment is added, it is placed on hold. The response message will include information to contact CBP for further instructions. Once issues are resolved, the hold is released. In this case, the tracking number is sent as "000" (zero) and the ITN number generated in the Shipment Added case is sent as a reference. The following are examples of the AES responses sent for HOLD and HOLD RELEASE:
For ON HOLD:
ISA*03*942805249 *01* *ZZ*USCSAESTEST *01*942805249 *230324*1014*^*00405*000000000*0*T*~
GS*AG*USCSAESTEST*942805249*20230324*1014*1*X*004050
ST*824*0001
BGN*01*942805249*20230323***XT
N1*01*123 COMPANY*24*94280524900
REF*01*0 (This is the Tracking Number)
OTI*02*A1*942805249
OTI*02*B1*94280524900
OTI*02*SC1*202303231125
OTI*02*ES1*X20230323632229 (This is the ITN Number)
TED*97H*I A SHIPMENT ON HOLD.CONTACT XXX-XXX-XXXX
OTI*02*Y1*94280524900
OTI*02*Z1*942805249
SE*12*0001
GE*1*1
IEA*1*000000000
For ON HOLD RELEASED:
ISA*03*942805249 *01* *ZZ*USCSAESTEST *01*942805249 *230327*1037*^*00405*000000000*0*T*~
GS*AG*USCSAESTEST*942805249*20230327*1037*1*X*004050
ST*824*0001
BGN*01*942805249*20230323***XT
N1*01*123 COMPANY*24*94280524900
REF*01*0
OTI*02*A1*942805249
OTI*02*B1*94280524900
OTI*02*SC1*202303231125
OTI*02*ES1*X20230323632229 (This is the ITN Number)
TED*97R*I A SHIPMENT HOLD RELEASED
OTI*02*Y1*94280524900
OTI*02*Z1*942805249
SE*12*0001
GE*1*1
IEA*1*000000000
-
Once the AES response is posted to GTM, a tracking event is created.
-
On the creation of tracking event, the “TRACKING EVENT PROCESSING REQUEST” event is triggered.
- GTM ships with an automation agent “PROCESS CUSTOMS FILING RESPONSE” for the data query type “TRACKING EVENT”. If you are using the automation agent that ships with GTM or you have copied the automation agent that ships with GTM and created a custom agent during implementation, the agent actions should be modified as follows:
- IF: TRACKING_NUMBER_ZERO
- MATCH DOCUMENT: By Saved Query
- For the agent action “MATCH DOCUMENT: By Saved Query” based on the ITN Number, the saved query to identify the document based on the ITN Number is:
- select distinct d.document_gid from gtm_transaction gt, gtm_trans_reqd_doc gtrd, document d, ie_shipmentstatus iess,ie_shipmentstatus iess1,ie_document_response idr,ie_document_response idr1,ss_document ssd where gtrd.document_gid = d.document_gid and gtrd.document_gid = ssd.document_gid and gtrd.gtm_transaction_gid = gt.gtm_transaction_gid and idr.i_transaction_no = iess.i_transaction_no and idr.element_ref_qualifier = 'es1:internal tracking number(itn)' and idr.element_ref_value=idr1.element_ref_value and idr1.i_transaction_no = iess1.i_transaction_no and ssd.i_transaction_no = iess1.i_transaction_no and iess.i_transaction_no =$GID
- Saved query TRACKING_NUMBER_ZERO - if this saved query is used, then the document is matched by the saved query, and matched by tracking number in all the other cases.
- select i_transaction_no from ie_shipmentstatus where i_transaction_no=? and tracking_number='0'
- For the agent action “MATCH DOCUMENT: By Saved Query” based on the ITN Number, the saved query to identify the document based on the ITN Number is:
- MATCH DOCUMENT: By Saved Query
- ELSE
- MATCH DOCUMENT: By Tracking Number
- ENDIF
- IF: TRACKING_NUMBER_ZERO
- For the agent action “(TRACKING EVENT TO DOCUMENT) SET CUSTOMS FILING RESPONSE STATUS”, in order to differentiate between the AES responses in case of regular response messages and messages for ON HOLD/ ON HOLD RELEASE codes, you should configure two saved conditions – one to check where tracking number is “0” (zero), and the other to check where tracking number is not “0” (zero).
- IF : TRACKING_NUMBER_NOT_NULL
- The ITN number is copied to the declaration only when the tracking number is not null. If the saved query “TRACKING_NUMBER_NOT_NULL” is satisfied, then the ITN number is copied to the declaration. Since the ITN number is already copied to the declaration in the first step of SHIPMENT ADDED, copying of ITN number is avoided in case of on_hold.
- Saved query TRACKING_NUMBER_NOT_NULL
- select i_transaction_no from ie_shipmentstatus where i_transaction_no=? and tracking_number!='0' and tracking_number is not null
- Saved query TRACKING_NUMBER_NOT_NULL
- The ITN number is copied to the declaration only when the tracking number is not null. If the saved query “TRACKING_NUMBER_NOT_NULL” is satisfied, then the ITN number is copied to the declaration. Since the ITN number is already copied to the declaration in the first step of SHIPMENT ADDED, copying of ITN number is avoided in case of on_hold.
- IF : TRACKING_NUMBER_NOT_NULL
NOTE: GTM does not ship with these saved queries.
Business Monitor Configuration
You can configure the following saved queries in the business monitor to track shipments that are placed on hold and for shipments where the the hold has been release.
FOR ON HOLD:
select gt.gtm_transaction_gid from gtm_transaction gt, gtm_trans_reqd_doc gtrd, document d,
ss_document ssd, ie_shipmentstatus iess,ie_document_response idr, bs_status_code bsc where
d.document_tracking_num is not null and gtrd.document_gid = d.document_gid
and gtrd.document_gid = ssd.document_gid
and ssd.i_transaction_no = iess.i_transaction_no
and iess.status_code_gid = bsc.bs_status_code_gid and gtrd.gtm_transaction_gid = gt.gtm_transaction_gid
and idr.i_transaction_no = iess.i_transaction_no and idr.response_code = '97H';
FOR ON HOLD RELEASED:
select gt.gtm_transaction_gid from gtm_transaction gt, gtm_trans_reqd_doc gtrd, document d,
ss_document ssd, ie_shipmentstatus iess,ie_document_response idr, bs_status_code bsc where
d.document_tracking_num is not null and gtrd.document_gid = d.document_gid
and gtrd.document_gid = ssd.document_gid
and ssd.i_transaction_no = iess.i_transaction_no
and iess.status_code_gid = bsc.bs_status_code_gid and gtrd.gtm_transaction_gid = gt.gtm_transaction_gid
and idr.i_transaction_no = iess.i_transaction_no and idr.response_code = '97R';
As the regulations change for AES Filing, GTM is updated so that your export filing is in line with current regulations.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- For more information about updates to the AES filing regulations, please refer to the U.S. Customs and Border Protection website.
This feature enables you to effectively manage the specifics of your trade incentive programs within GTM. Examples of trade incentive programs include the IMMEX program in Mexico, Inward Processing Relief in the UK, and Temporary Import and Duty Drawback in the USA, etc. When creating the trade incentive program, GTM allows you to enter certain information including:
- Trade Incentive Program Type - group your trade incentive programs based on similar characteristics. For example, you may want to group your trade incentive programs into temporary import, bonded warehouse, free trade zone, or some other grouping that makes sense to you.
- Name - specify the name by which a trade incentive program is known. For example, Inward Processing Relief for the United Kingdom or IMMEX program for Mexico.
- Active flag - check the box for the trade incentive program when it becomes available.
- Effective and Expiration Date - specify the start and end dates of the trade incentive program.
- Status - use external status to model important conditions related to the trade incentive program.
- Regime - specify the customs regime that the trade incentive program falls under.
- Jurisdiction - specify the customs jurisdiction that the trade incentive program falls under. When you enter the jurisdiction there is no need to enter the customs regime.
- Applicable Profiles - specify the entry and exit profile pairs for the trade incentive program. Depending on the customs regulations of the country or region, you may have multiple combinations.
- Regulation Reference - specify the regulation governing the trade incentive program.
- Authorization Required - indicate whether the trade incentive program requires government authorization (for use in a future release).
- Accounting Method - identify the accounting method to be used to decrease the quantities within the trade incentive program. First In First Out (FIFO) is the only supported method in this release.
- Maintain Stock Ledger - there is no specific functionality associated with this field (for use in future releases).
- Involved Parties - specify the parties associated with the trade incentive program and the corresponding roles.
- Registrations - indicate the registrations required for the trade incentive program.
- Text Templates - provide details about the templates that are pertinent to the trade incentive program.
- Remarks - specify the remarks relevant to the trade incentive program.
- Reference Numbers - specify the reference numbers relevant to the trade incentive program.
The example below illustrates a bonded warehouse program in Mexico, highlighting the following information and characteristics:
- It is an active program.
- The jurisdiction is the Mexican customs jurisdiction.
- The accounting method to be applied when decrementing remaining quantity balances is First In First Out.
- There are two sets of entry and exit profiles:
- The entry profiles identify the trade incentive program entry declarations for which quantities need to be tracked
- The exit profiles identify those declarations that decrement the remaining quantity of the trade incentive program entry declarations
This feature demonstrates GTM's innovation by enabling multiple trade incentive programs, including temporary imports, bonded warehouses, free trade zones, and inward processing relief, to have a unified setup. GTM's generic solution remains agnostic to specific trade incentive programs, allowing for seamless global implementations. These programs create the opportunity for significant cost savings through duty deferral or elimination.
Steps to Enable
You don't need to do anything to enable this feature.
This feature enables you to group trade incentive programs based on shared characteristics. For example, Trade Incentive Program Types are Temporary Import, Bonded Warehouse, Free Trade Zone and Duty Drawback. When creating the Trade Incentive Program Type, GTM allows you to enter certain information including:
- Name - specify the name for the trade incentive program type
- Description - describe the trade incentive program type
- External reference Code - include an additional relevant reference
This feature enhances the flexibility of the trade incentive programs solution, as companies can define the grouping according to their specific business needs.
Steps to Enable
You don't need to do anything to enable this feature.
Trade Incentive Program Sub Type
This feature enables you to classify trade incentive programs into specific sub-categories. For example, you may want to have Direct ID Drawback and Substitution Drawback as sub types of the Duty Drawback program type. When creating the trade incentive program sub type, GTM allows you to enter certain information including:
- Name - specify the name for the trade incentive program sub-type.
- Trade Incentive Program Type - specify the name for the trade incentive program type
- Description - describe the trade incentive program sub type
- External Reference Code - include an additional relevant reference
By providing this level of flexibility, companies gain the ability to define sub types tailored to their specific business requirements.
Steps to Enable
You don't need to do anything to enable this feature.
This business object allows you to define the combinations of attributes in a customs declaration that establish a direct connection between the declaration and a particular trade incentive program. For example, in Mexico the combination of the regime, operation, and pedimento code identifies whether a declaration should be associated with a trade incentive program and if so, whether it is an entry or exit declaration. You can map these attributes to declaration type, declaration sub type, and procedures providing flexibility in establishing this connection. When creating the entry exit profile, GTM allows you to enter certain information including:
- Name - specify the name of the entry exit profile
- Description - describe the entry exit profile
- Profile Type - indicate whether the procedure is a required attribute in the declaration. The option Other is reserved for future use and provides no specific functionality
- Transaction Type Profile - reserved for future use and provide no specific functionality
- Declaration Type - specify the declaration type
- Declaration Sub Type - specify the declaration sub type
- Procedures - specify the procedures
- Reference Numbers - reserved for future use and provide no specific functionality
- Remarks - reserved for future use and provide no specific functionality
- User defined codes - reserved for future use and provide no specific functionality
In the Mexican scenario, the combination of the declaration type (MX-IMP), the declaration sub type (MX-DFI) and the procedure (MX-A4) tells GTM that the items on this declaration are entering the country into a bonded warehouse program.
This feature significantly simplifies the process of program determination for a given customs declaration. It provides a standardized setup that can be used across regions or countries.
Steps to Enable
You don't need to do anything to enable this feature.
This feature enables you to establish rules that outline the conditions for specific items to be included in the program, such as discharge period or matching type. When creating the trade incentive program rules, GTM allows you to enter certain information including:
- Trade Incentive Program Rule ID - identify the ID of the trade incentive program rule.
- Name - specify the name by which a trade incentive program rule is known.
- Active Flag - indicate whether the trade incentive program rule is currently in use.
- Trade Incentive Program - specify the trade incentive program to which the rule applies.
- Trade Incentive Program Sub Type - specify the trade incentive program sub type for which the rule applies.
- Product Classification Type - specify the product classification type associated with the trade incentive program rule.
- Period of Discharge Years and Months - specify the time frame the goods can stay under the program once they have entered the program. For example, 2 years, 6 months.
- Accounting Method - identify the accounting method to be used to decrease the quantities within the trade incentive program. First In First Out (FIFO) is the only method supported in this release.
- Matching Constraint Set - define the method for matching entries and exit declaration lines. For example, item id, classification code, or item id and serial number.
- Saved Query - No specific functionality has been added to this field (to be used in future releases).
- Description - describe the rule.
- Product Specific Rules – specify the rules for specific classification codes under the classification type indicated above. You can include details such as:
- Start and End Classification Code - specify the range of classification codes covered by the trade incentive program rule
- Period of Discharge Years and Months - specify the time frame the goods can stay under the program once they have entered the program
- Matching Constraint Set - define the method for matching entries and exit declaration lines. For example, item id, classification code, or item id and serial number
- Text Templates - provide details about the templates that are pertinent to the trade incentive program rule.
- Reference Numbers - specify the reference numbers relevant to the trade incentive program rule.
- Remarks - specify the remarks relevant to the trade incentive program rule.
In the example below, you can see a rule for three sets of classification codes within a trade incentive program under the Harmonized System HTS US. Each range of classification codes is assigned its own matching constraint set:
This feature offers a great level of flexibility in modeling programs that impose specific conditions on different items to be eligible under the program. It enables you to support diverse programs in different regions and countries.
Steps to Enable
You don't need to do anything to enable this feature.
Trade Incentive Program Rule - Product Specific Rule
This feature provides a new Trade Incentive Program - Product Specific Rules manager. The manager gives you visibility into specific rules for a range of classification codes under a trade incentive program rule as well as the ability to create new rules. When creating the product specific rules, GTM allows you to enter certain information including:
- Start and End Classification Code - specify the range of classification codes covered by the product specific rule.
- Period of Discharge Years and Months - specify the time frame the goods can stay under the program once they have entered the program.
- Matching Constraint Set - define the method for matching entries and exit declaration lines. For example, item id, classification code, or item id and serial number
The addition of the new manager provides streamlined access to product specific rules, eliminating the need to navigate through the trade incentive program rule screen.
Steps to Enable
You don't need to do anything to enable this feature.
Item Applicable Trade Incentive Program
This feature enables you to define items that are associated with one or more trade incentive programs. When defining the items, GTM allows you to enter certain information including:
- Trade Incentive Program - identify the ID of the trade incentive program
- Priority - assign priority levels to various programs for a specific item
- Effective and Expiration Date - the start and end dates for the item to be included in a program
In the example below, the item BIKE FRAME SET-1 falls under two trade incentive programs: the Mexican Fiscal Deposit (bonded warehouse program) and the Strategic Fiscalized Area (similar to a free trade zone program). GTM will prioritize matching an exit declaration to an entry declaration under the fiscal deposit program.
By enabling the assignment of priorities to each program, this feature greatly simplifies the process of managing items across programs.
Steps to Enable
You don't need to do anything to enable this feature.
Record Entries Into Programs Action
This action creates an Inventory Movement record and an Inventory record for the selected entry declaration line(s) under a trade incentive program. The Logic configuration associated with the declaration type helps the system to identify the date qualifier, the location or inventory organization, and the quantity qualifier to be considered in the process.
The movement record will include details such as the identification of the declaration line, associated trade incentive program, inventory organization, item, quantity, and procedure. On the other hand, the inventory record will include details such as the identification of the declaration line, associated trade incentive program, inventory organization, the item, initial and remaining quantity, and procedure. The remaining quantity and the original quantity will both be set to the quantity on the declaration line, and the status will be set to open.
You can use the Trade Incentive Program Inventory Movement and the Trade Incentive Program Inventory screens to view the results of this action.
This feature provides the ability to track entry declarations, facilitate efficient monitoring of their utilization under a program and providing support for legal reporting requirements.
Steps to Enable
You don't need to do anything to enable this feature.
For users of trade incentive programs, this action creates an inventory movement record for an exit declaration line under a trade incentive program. The movement record includes details such as the identification of the declaration line, the associated trade incentive program, the inventory organization, the item, the quantity, and the procedure. At the same time, the inventory record of the corresponding trade incentive program entry declaration will be updated by reducing its "Remaining Quantity" by the quantity of the exit declaration. The status will remain "Partially Reconciled" until the Remaining Quantity reaches zero, at which point it will transition to "Closed".
You can use the Trade Incentive Program Inventory Movement and the Trade Incentive Program Inventory screens to view the action results.
This feature helps users correctly update program inventory balances, so that users have an up-to-date view of their program usage.
Steps to Enable
You don't need to do anything to enable this feature.
Trade Incentive Program Inventory
This feature allows you to view inventory records in the context of a Trade Incentive Program. Details include the declaration line that created this inventory record, the associated trade incentive program, inventory organization, item, initial and remaining quantity, and status.
Trade Incentive Program Inventory provides a streamlined view of the remaining quantities and discharge period end dates for an entry declaration under a trade incentive program. It allows users to manage their programs proactively and make plans to optimize customs duty and taxes, and effectively mitigate compliance risks
Steps to Enable
You don't need to do anything to enable this feature.
Trade Incentive Program Inventory Movements
This feature allows you to visualize inventory movement records, including details such as the identification of the declaration line, the associated trade incentive program, the inventory organization, the item, and the quantity.
The Inventory Movements provide a history of receipts and issues that made adjustments to an Inventory, giving users transparency and traceability.
Steps to Enable
You don't need to do anything to enable this feature.
Logic Configuration Enhancement
To support the trade incentive workflows, a new grid has been added to the GTM Logic Configuration with a Logic Configuration Type = GTM DECLARATION CONFIGURATION. It includes the following parameters: date qualifier, inventory location qualifier, inventory organization qualifier, and quantity qualifier. These qualifiers will be used to identify the date, inventory organization or location, and the quantity of the declaration lines for the actions Record Entries into Programs, and Match Exits to Entries Actions.
These parameters give you the flexibility to configure the inventory recording logic and the matching logic in trade incentive programs. Specifically, the Inventory Organization and Inventory Location parameters help to model programs like Bonded Warehouse or Free Trade Zone, where inventories are tied to a specific organization or location.
Steps to Enable
You don't need to do anything to enable this feature.