28
See What's Coming in Oracle Transportation Management and Oracle Global Trade Management Release 6.3.4 Release Content Document

Release Content Document - OTM & GTM 6.3.4

Embed Size (px)

Citation preview

Page 1: Release Content Document - OTM & GTM 6.3.4

See What's Coming in

Oracle Transportation

Management and Oracle Global

Trade Management

Release 6.3.4

Release Content Document

Page 2: Release Content Document - OTM & GTM 6.3.4

2

TABLE OF CONTENTS

ORACLE TRANSPORTATION MANAGEMENT ............................................................................................. 4

ORACLE TRANSPORTATION MANAGEMENT (BASE PRODUCT) ................................................................................................. 4 Flex Fields Added for Order Release Line and Order Release Ship Unit ............................................................................. 4 Network Routing Through Point Settlement Using Secondary Charge Shipment.............................................................. 4 RIQ Network Rate and Route - Secondary Charge Shipments ........................................................................................... 4 RIQ Rate and Route - Re-Rate Shipments to Check Rate Expiration Dates ........................................................................ 5 Provide Agent Action to Insert Agent Status into I_LOG TABLE ......................................................................................... 5 e-Location Now Supports Connecting to ALK’s Hosted Mapping Service .......................................................................... 6 Oracle Spatial Validate Address Regional Options for Province vs Province Code ............................................................ 6 Kewill Address Validation Configuration ............................................................................................................................ 6 Promote to Production Enhancements.............................................................................................................................. 6 Glog.properties are now Editable Through the UI ............................................................................................................. 7

FINANCIALS .................................................................................................................................................................. 7 Invoice Added to Action Definition .................................................................................................................................... 7

TRANSPORTATION OPERATIONAL PLANNING ....................................................................................................................... 7 New Bulk Plan Performance and Tuning Section Added to Help ....................................................................................... 7 Continuous Move Enhancements ...................................................................................................................................... 8 Optimize Equipment for Ground Schedule Shipments ...................................................................................................... 9 ERU Capacity Check When Adding Orders to Schedule Instances ..................................................................................... 9 New Action – “Show Network Routing Options – Ocean” ............................................................................................... 10 3D Load Configuration Solution Quality Improvements - Tolerances .............................................................................. 11 First Leg Split Pallet Logic ................................................................................................................................................. 11 Support Via Points on Network Routing Leg .................................................................................................................... 11 Re-drive and Time Definite Service .................................................................................................................................. 11 Commitment Allocation - Allocation Group ..................................................................................................................... 12 Special Service Time Based Accessorial Costs Considered for All Rate Services .............................................................. 12

FUSION TRANSPORTATION INTELLIGENCE ......................................................................................................................... 12 Network Model Data Translations Added ........................................................................................................................ 12

ORACLE FLEET MANAGEMENT ....................................................................................................................................... 13 Create Asset Inventory Record in Object's Domain ......................................................................................................... 13

ORACLE TRANSPORTATION SOURCING ............................................................................................................................. 13 Flex Fields Added to Project ............................................................................................................................................. 13 Manual Awards Report .................................................................................................................................................... 13

ORACLE GLOBAL TRADE MANAGEMENT ................................................................................................. 14

GLOBAL TRADE MANAGEMENT (BASE) ............................................................................................................................ 14 Item Template - Copy Remarks Based On Qualifier ......................................................................................................... 14 Quantity Qualifier Type Filter for UOMs Displayed ......................................................................................................... 14 Agent Action Contact Notification Added ........................................................................................................................ 15 Grid Flattening Supported for Product Classification Data on Trade Item ....................................................................... 15 Detect Invalid Classification Performance Improvements ............................................................................................... 15 RPLS – Comprehensive How To and Configuration Documentation ................................................................................ 15 RPLS - Support Bi-Direction Match Capability for Dice Engine ......................................................................................... 16 RPLS - Separate Workflow Thread Group for Transaction Party Screening and Contact (Batch) Party Screening ........... 17 RPLS - Agency Code Management ................................................................................................................................... 17 RPLS - Null Match % ......................................................................................................................................................... 18 RPLS – Review Match Factor Action ................................................................................................................................. 18 RPLS - Contact - Name or Address Modified Event .......................................................................................................... 19 Generate Trade Item Structure Component Sequence Number ..................................................................................... 19

Page 3: Release Content Document - OTM & GTM 6.3.4

3

Content - Purge Product Classification Data / Purge by Data Version (PC & RPL) ........................................................... 20 Content - Override Checkbox to “Force” the Download of Data Content ....................................................................... 20 Content – Notes Type Provided for Munitions List .......................................................................................................... 20 Content - Breakout Notes from Description for ECCN codes ........................................................................................... 20 Content - Update GIDs for all HTS and ECCN Codes......................................................................................................... 20

TRADE COMPLIANCE .................................................................................................................................................... 21 View related transactions from License Manager ........................................................................................................... 21 Service ID Value Now Displays on View Page of Policy .................................................................................................... 21 Service Preference Configuration: Lookup Product Classification Specify Classification Status ...................................... 21 Display Item Name on Transaction Line finder results .................................................................................................... 21

CUSTOMS MANAGEMENT ............................................................................................................................................. 22 Customs Commercial Invoice ........................................................................................................................................... 22 AES Filing Update AES EDI Template to Accommodate Regulation Changes ................................................................... 23 AES Filing Architecture Revised........................................................................................................................................ 23 AES Filing - Rules for Submitting HTS US or Schedule B ................................................................................................... 24

GLOBAL TRADE INTELLIGENCE (GTI)................................................................................................................................ 25 Product: Global Trade Intelligence (GTI) .......................................................................................................................... 25 Soft Deletes for GTI – Automation Agents ....................................................................................................................... 26 Trade Direction from Transaction Line Classification Added to GTI................................................................................. 26 Customs Shipment and Customs Shipment Line added to GTI ........................................................................................ 27

Page 4: Release Content Document - OTM & GTM 6.3.4

4

ORACLE TRANSPORTATION MANAGEMENT

ORACLE TRANSPORTATION MANAGEMENT (BASE PRODUCT)

FLEX FIELDS ADDED FOR ORDER RELEASE LINE AND ORDER RELEASE SHIP

UNIT

Use Flex Fields (20 VARCHAR2 columns, 10 date columns and 10 number columns) on the Order Release Line

and Order Release Ship Unit.

The following fields have been added to the Order Release Line and Ship Unit tables:

20 Varchar2 fields

10 Date fields

10 Number fields

3 Currency fields

NETWORK ROUTING THROUGH POINT SETTLEMENT USING SECONDARY

CHARGE SHIPMENT

This feature provides you with the necessary Secondary Charge Shipment rule changes and rate basis changes to

support the generation and rating of Secondary Charge shipments to support the calculation of handling and

holding charges incurred at a through point (cross dock) location.

Previously the cost based planning logic handled calculating through point (cross dock) related

charges using handling shipments.

Network routing now uses Secondary Charge shipments to calculate and hold the charges related to

through points (cross docks).

Changes made to the Secondary Charge Rule include:

o The ability to Calculate Ship Unit Duration – for the purposes of calculating the charges for

holding time at a through point

o Additional Criteria

Involved Party

Contact Profile

Rate Offering

Rate Record

Shipment Type

Perspective

o Additional RBIs have been provided to calculate ship unit level handling and holding charges

RIQ NETWORK RATE AND ROUTE - SECONDARY CHARGE SHIPMENTS

Configure RIQ (Network Rate and Route) to generate secondary charge shipments that can be included the RIQ

results.

Page 5: Release Content Document - OTM & GTM 6.3.4

5

You can now configure RIQ (Network Rate and Route) to include secondary charges in the RIQ

results.

To include secondary charge shipments in RIQ (Network Rate and Route) the “RIQ UI CREATE

SECONDARY CHARGES” parameter should be turned on. This parameter that can be found

under the “RATE INQUIRY UI CONFIGURATION” section.

RIQ RATE AND ROUTE - RE-RATE SHIPMENTS TO CHECK RATE EXPIRATION

DATES

This enhancement provides you with the option to configure RIQ Rate and Route to check the effective dates of

rates in multi-leg shipment scenarios considering each shipment’s start date.

Previously RIQ Rate and Route checked the validity of possible rates based on the “order” start date

instead the shipment's start date.

This enhancement provides the user with a new planning parameter "Re-rate All Shipments In RIQ"

that when set to true (the default is false), will re-rate the shipments and select only those rate records

that are effective for all shipments in the RIQ generated options.

Note - This feature is only for RIQ Rate and Route Find option.

PROVIDE AGENT ACTION TO INSERT AGENT STATUS INTO I_LOG TABLE

OTM agent’s can now write to the I_LOG table so that the information written to the i_log table can be sent back

to the user’s Integration layer in the Transmission report.

For integration processes, the I_TRANSMISSION_NO and I_TRANSACTION_NO have now

been added to the process propagation.

Once the workflow for a transmission is started the transmission number is now available to all

processes triggered by the transmission flow.

Once the workflow for a transaction is started the transaction number is also available to all

processes triggered by the transaction flow.

When available, the transmission number can be accessed through the agent variable $transmission.

Similarly, the transaction number can be accessed through the $transaction variable.

The agent action LOG TO TRANSMISSION REPORT is now available whenever the LOG action

is run. This action checks to see if $transmission is available (i.e. the process firing the agent was

triggered by an inbound transmission). If so, the action adds a record to the I_LOG table for

$transmission and $transaction. The action takes the parameters:

o Message Class (required). This is a drop list with the values 'Information', 'Warning' or 'Error',

mapping to the I_LOG.I_MESSAGE_CLASS values I/W/E. If set to Error, the integration

subsystem will mark the entire transmission as FAILED.

o Message Text (required). This is the free-form remarks the agent writes to

I_LOG.I_MESSAGE_TEXT. It can be up to 2000 characters long.

o Message Code (optional). This is a text code, describing the type of message being sent to

I_LOG.I_MESSAGE_CODE. If left blank, it is set to 'TRANSACTION_MESSAGE'.

Written By (optional). This is the originator of the I_LOG record, written to

I_LOG.WRITTEN_BY. If left blank it is set to 'Agent <agent GID>' where <agent GID> is the

GID of the agent invoking the action.

Page 6: Release Content Document - OTM & GTM 6.3.4

6

E-LOCATION NOW SUPPORTS CONNECTING TO ALK’S HOSTED MAPPING

SERVICE

You now have the option to use a locally installed version of Oracle's spatial e-Location service to connect to the

ALK Map hosted mapping service to provide mapping data/map tiles for display purposes.

ALK Map is a subscription based mapping service that OTM clients can subscribe to for their mapping and distance engine requirements.

ORACLE SPATIAL VALIDATE ADDRESS REGIONAL OPTIONS FOR PROVINCE VS

PROVINCE CODE

Those who use Oracle Spatial for location address validation now have some additional External Distance Selector

options that can be used to handle the different address standards regarding Province Code versus Province. For

North and South American countries address validation will be done using Province_Code, for all other countries

the Province field will be used for address validation purposes.

Before this change the External Distance Selector options for Oracle Spatial would only send the Province_Code for address validation.

With this change – the External Distance Selector options of ORACLE_SPATIAL_ADDRESS_WESTERN_EUROPE and ORACLE_SPATIAL_LAT_LON_WESTERN_EUROPE will send the Province field from the location record for address and latitude longitude validation purposes.

With this change – the External Distance Selector options of ORACLE_SPATIAL_ADDRESS_USA_CAN and ORACLE_SPATIAL_LAT_LON_USA_CAN will send the Province_Code field from the location record for address and latitude longitude validation purposes.

KEWILL ADDRESS VALIDATION CONFIGURATION

Additional configuration has been added to the Kewill Flagship API configuration to allow you to determine if

address validation should or should not be performed.

A new parameter 'KEWILL ADDRESS VALIDATION' has been added under RATES to configure the address validation flag for KEWILL.

o Set the parameter to 'true' to validate a given address.

o Set the parameter to 'false' to skip address validation.

PROMOTE TO PRODUCTION ENHANCEMENTS

This enhancement provides you with additional options for moving export projects and also provides the user

with the ability to use a local package file for Migration Project Import instead of a package file already residing on

the application server.

You now have the ability to Email and FTP Exported Migration Project Package Files.

o This enhancement provides the you with the ability to export the package file via email and FTP

from the Migration Project Export process. Email is specified on the Notification tab on the

Contact Manager. FTP is set up on the Migration Project Export page. A new event,

MIGRATION PROJECT - EXPORT SEND PACKAGE FILE, has been created.

Page 7: Release Content Document - OTM & GTM 6.3.4

7

You now have the option to upload a local migration project package for import.

This enhancement provides the ability to use a local package file for Migration Project Import instead of a package file already residing on the application server. Use the Migration Project Import page to facilitate importing files.

GLOG.PROPERTIES ARE NOW EDITABLE THROUGH THE UI

This enhancement provides you with Persistent Property Management which allows the user to manage Glog

properties in the OTM database/via a UI instead of in property files.

Glog.properties can now be managed using the Property Sets page.

o The Property Sets page groups properties and allows the user to set values in the properties,

along with adding or removing properties from the set.

A log is maintained to track all changes to the property set.

FINANCIALS

INVOICE ADDED TO ACTION DEFINITION

The Invoice object has been added to the list of Action Definition objects that can be configured to run a report

as a manual action.

The set of available Action Definition IDs has been extended to include the Invoice.

TRANSPORTATION OPERATIONAL PLANNING

NEW BULK PLAN PERFORMANCE AND TUNING SECTION ADDED TO HELP

A new “Bulk Plan Performance and Tuning” section has been added to the set of topics covered in the “How

To/Configuration Topics” section of Help. The new information provides the user with an excellent overview of

the bulk planning process and includes information for solution quality tuning and performance tuning.

Topics covered by the new “Bulk Plan Performance and Tuning” section include:

Overview

o Bulk Plan Performance and Tuning Overview

Data Setup

o Bulk Plan Data Setup

o Locations and Bulk Planning

o Equipment Groups and Equipment Types in Bulk Planning

o Transport Modes and Service Providers in Bulk Planning

o Rate Offerings and Rate Records in Bulk Planning

o Rate Service and Bulk Plan

o Carrier Capacities and Commitments in Bulk Planning

o Location Capacities and Bulk Planning

Page 8: Release Content Document - OTM & GTM 6.3.4

8

o Itineraries and Bulk Plan

o Itinerary Legs and Bulk Planning

Bulk Plan Processes and Routing

o Bulk Plan Processes

o Bulk Plan Cost Based Routing

o Bulk Plan Network Based Routing

Solution Quality Tuning

o Bulk Plan Solution Quality Tuning

o Bulk Plan Tuning Order Bundling Logic

o Bulk Plan Tuning Direct Shipment Building

o Bulk Plan Tuning Container Optimization Logic

o Bulk Plan Tuning Continuous Moves Logic

o Bulk Plan Multi-stop Shipment Logic

Bulk Plan Tuning Multi-stop Shipment Logic

Bulk Plan Multi-stop Shipment Saving Algorithms

Bulk Plan Multi-stop Shipment Complete Enumeration Algorithm

Bulk Plan Multi-stop Shipment Column Generation Algorithm

Bulk Plan Multi-stop Shipment Common Scenarios

o Performance Tuning

Bulk Plan Performance Tuning

Understanding the Bulk Plan Run

Bulk Plan Multi-threading

Multi-threading Logic

Bulk Plan Partitioning

o Diagnostics

Bulk Plan Diagnostics

Bulk Plan Logs

Container Optimization

o Object and Method Instrumentation

CONTINUOUS MOVE ENHANCEMENTS

This feature provides additional solution quality improvements for continuous move/dedicated fleet planning.

The Continuous Move Link Shipment Action allows the user to select more than two shipments to

be considered for continuous move tour generation.

o The selected set of shipments is now displayed on the input screen and can be sequenced.

Lower wait time in continuous move tour. Re-drive for continuous move tours have been enhanced

to minimize the wait time in- between shipments.

Additional information has been provided on the bulk continuous move summary page. New fields

provided on the bulk continuous move summary page:

o Status Submitted/Running/Completed

o Parameter Set ID

Page 9: Release Content Document - OTM & GTM 6.3.4

9

o Number Of Shipments Considered (in the Algorithm) Some selected shipments might be

excluded because they are on CM. This number shows the shipments that actually go into the

algorithm.

o Number Of Shipments Failed to be Linked (Not added to DB just on UI) (Number Of

Shipments Selected) - (Number Of Shipments Failed to be Linked)

o Number Of Continuous Moves Created

o Total Cost Before

o Total Cost After

o Total Empty Distance Sum of All Empty Distances in a CM added over all CMs

o Total Loaded Distance

o Total Distance Before

o Total Distance After

o Total Time of All continuous Moves

o Total Number of CM with 2 shipments

o Total Number of CM with 3 shipments

o Total Number of CM with 4 shipments

o Total Number of CM with 5 shipments

o Total Number of CM with more than 5 shipments

o Description

OPTIMIZE EQUIPMENT FOR GROUND SCHEDULE SHIPMENTS

This feature provides you with the ability to automatically assign the best equipment group (including combo

equipment) when the action to release a detachable ground schedule is run.

Previously you were required to configure an agent to call the agent action "Assign Best Equipment

group" to switch to a better equipment group than the equipment group defined on repetition

schedule template.

Now OTM will automatically invoke the "assign best equipment group" logic when the "release

schedule instance" action is run.

o Note OTM will only invoke the "assign best equipment group" logic to pick the best equipment

group considering the equipment_group_profile defined on the leg if the following conditions

are met:

Schedule instance is a detachable trip;

The Is fixed equipment group flag on the schedule instance template is unchecked

The Equipment group defined on repetition schedule is included in the equipment group profile

defined on the leg.

ERU CAPACITY CHECK WHEN ADDING ORDERS TO SCHEDULE INSTANCES

The ERU capacity check has been added to the plan order to schedule instance logic so that ERUs are now

considered when adding orders to a schedule instance. The ERU capacity check applies to all schedule instance

types.

Previously OTM did not consider ERUs when adding orders to schedule instances.

OTM’s planning logic has been enhanced to now consider ERU capacity when adding orders to a

scheduled instance.

Page 10: Release Content Document - OTM & GTM 6.3.4

10

The ERU capacity check applies to all schedule instance types including Static, Dynamic as well as

Detachable schedule instance.

The ERU capacity check can be turned on and off using the “CHECK EQUIPMENT CAPACITY

IN REFERENCE UNITS” planning parameter.

NEW ACTION – “SHOW NETWORK ROUTING OPTIONS – OCEAN”

This feature provides you with additional multi-leg constraints and options to consider when generating the

routing options for a set of orders. The new “Show Network Routing Options – Ocean” action provides better

decision support and routing control for users tasked with planning a multi-leg ocean solution.

New constraints to be considered when generating options using this action:

o Primary Option Definition – By Itinerary or By Schedule and Equipment Group

o Max Primary Options, Max Supporting Options

o Voyage ID

o Itinerary ID

o Exclude Itinerary Profile ID

o Port of Load

o Exclude Port of Load Profile

o Port of Discharge

o Exclude Port of Discharge Profile

The new Routing Options Portion of the screen provides an expended/ocean centric information view into the available routing options

o Total Actual Cost

o Ship From

o Primary Shipment Source

o Port Of Load

o Port Of Discharge

o Primary Shipment Destination

o Ship To

o Commodity Code

o Service Provider ID

o Primary Voyage

o Planned Capacity Commitment Allocation

o Actual Capacity Commitment Allocation

o Commitment Count Actual

o Primary Total Cost

o Equipment Group

o Start Time

o End Time

o Transit Time

o Total Lead Time

o Vessel ID

o Primary Transit Time

o Est Arrival Time Source

o Est Departure Time Source

o Est Arrival Time Dest

Page 11: Release Content Document - OTM & GTM 6.3.4

11

o Est Departure Time Dest

o Itinerary

o Transport Mode

o Primary Rate Offering

o Primary Rate Record

Capacity Limit Capacity

3D LOAD CONFIGURATION SOLUTION QUALITY IMPROVEMENTS - TOLERANCES

This feature provides you with the ability to define dimensional tolerances for items which then allows for slightly

dissimilar sized items to be considered together when generating patterns for loading equipment using Load

Configuration and 3D Patterns.

Previously items with slightly dissimilar dimensions were not considered for loading together when

using the Load Configuration 3D patterns solution. For clients with a large number of different

items - with only slightly different dimensions - this would limit the number of patterns that would be

generated.

The Tolerances feature allows for similarly sized items with similar dimensions to be considered the

same for the purposes of generating a solution using the Pattern based 3D Load Configuration

solution. For clients with a large number of different items with slightly different dimensions the

Tolerances feature increases the number of patterns generated and should yields improvements in

solution quality.

FIRST LEG SPLIT PALLET LOGIC

This feature provides you with new planning capabilities that allow the user to control the split pallet logic in OTM

from the first leg onward.

This feature derives the pallet split decision from the first leg split decision.

If the pallet is split on the first leg this split decision will be carried through to all subsequent legs.

If the pallet is not split on the first leg then the pallet will not be split/considered for splitting in the

subsequent legs.

SUPPORT VIA POINTS ON NETWORK ROUTING LEG

This feature provides you with enhanced network routing logic that now considers via points on network routing

legs.

The network routing logic now considers the via points as an additional constraint when developing

the routing solution through the network.

RE-DRIVE AND TIME DEFINITE SERVICE

This feature provides you with the ability to re-drive upstream shipments that are linked to downstream systems

that are using the time definite rate service.

Page 12: Release Content Document - OTM & GTM 6.3.4

12

In previous versions of OTM an error would be generated whenever a user attempted to recalculate

the stop times on an upstream shipment that was linked to a second leg/downstream shipment that

was using a time definite rate service type.

With this feature you can now successfully re-drive the first leg in a multi-leg scenario when the 2nd

leg shipment uses the time definite rate service.

COMMITMENT ALLOCATION - ALLOCATION GROUP

This feature provides you with a new Allocation Group concept that provides the user with the option to manage

commitment allocations at the order level in addition to the previously available lane level commitment allocation

level.

Previously allocation commitments were managed at the lane level by carrier.

With the new Allocation Group feature multiple commitment allocations can now be utilized for the

same shipment based geographical lane.

A new Allocation Group ID has been added to the Order Release constraints tab and the

Commitment Allocation screen. The Allocation Group ID on the Order Release is used to refine the

search for applicable commitment allocation record to use when handling commitment allocation.

The Allocation Group is designed for those who need to split out the commitment allocation to

something more specific that just lane. For example - different departments within a corporation

that have different commitment allocations on the same lane, or Logistic Service Providers with

multiple customers on the same lane that require separate commitment allocations for the same

carriers on the lane.

SPECIAL SERVICE TIME BASED ACCESSORIAL COSTS CONSIDERED FOR ALL

RATE SERVICES

This feature provides you with improved rating calculation capabilities for time based special service accessorials

that use rate service options other than simulation.

Previously when the rating engine compared costs of differing rates, it only considered special service

time based accessorial costs if the rate was using a simulation rate service.

The rating engine was enhanced to use a more generic method of determining drive time for a

shipment when the rate involves time based costs. An estimated time and cost can now be calculated

for all rate service types.

FUSION TRANSPORTATION INTELLIGENCE

NETWORK MODEL DATA TRANSLATIONS ADDED

Translations were added for all network model data in FTI.

Network model translations added.

Page 13: Release Content Document - OTM & GTM 6.3.4

13

ORACLE FLEET MANAGEMENT

CREATE ASSET INVENTORY RECORD IN OBJECT'S DOMAIN

This feature provides the ability to have OTM create the asset inventory record in the domain of the related

location object.

Previously asset inventory records were created in the domain of the user creating the record.

Asset inventory records can now be created in the domain of the location object related to the

inventory record - as opposed to the user's domain.

ORACLE TRANSPORTATION SOURCING

FLEX FIELDS ADDED TO PROJECT

The sourcing Project manager can now be customized via Manager Layouts to use flex fields. Flex fields were also

extended to the CRT Configuration and the final generated Carrier Response Template (CRT) spreadsheet.

The following fields have been added to the P_Project table:

o 20 Varchar2 fields

o 10 Date fields

o 10 Number fields

3 Currency fields

MANUAL AWARDS REPORT

The Manual Awards Report is a new sourcing report that shows you the manual awards for each lane compared to

that of demand and the total awarded.

If the Fixed option on the solution detail record is selected, then the award is considered manual. To view the report, go to Sourcing > Reports and run the Manual Awards Report. This report will only list the equipment group for lanes with a transport mode of OCEAN.

Page 14: Release Content Document - OTM & GTM 6.3.4

14

ORACLE GLOBAL TRADE MANAGEMENT

GLOBAL TRADE MANAGEMENT (BASE)

ITEM TEMPLATE - COPY REMARKS BASED ON QUALIFIER

To improve usability the item template now uses the remark qualifier instead of the remark sequence number to

determine the remarks to be copied.

Previously, when item template remarks were copied based on the remark sequence number (instead

of the remark qualifier) the following issues were identified

o Remarks did not get copied if an existing item remark already existed with the same sequence

number as the item template remark

o The same remark qualifier could show up more than once if the remark was already on the target

item with a different sequence number.

The switch to handling template remark copies based on remark qualifier (as opposed to sequence

number) has addressed the above issues.

QUANTITY QUALIFIER TYPE FILTER FOR UOMS DISPLAYED

A Quantity Qualifier Type has been added to the definition of Quantity Qualifiers. The Quantity Qualifier Type

filters the list of UOMs shown based on the Quantity Qualifier Type selected; for example, the Quantity Qualifier

Type = Weight filters the UOMs displayed to just weight related UOMs.

The new Quantity Qualifier Type works for all Quantity Grids including:

o Transaction

o Transaction Line

o Customs Shipment

o Customs Shipment Line

o License Line

o Trade Item Structure.

Quantity Qualifier Types supported include:

o Reporting Quantity

o Length

o Weight

o Duration

o Density

o Distance

o Area

o Count

o Volume

o Quantity

o Speed

Page 15: Release Content Document - OTM & GTM 6.3.4

15

o Temperature

User defined

AGENT ACTION CONTACT NOTIFICATION ADDED

Support for the agent action ‘Contact Notification’ was extended to other GTM business objects.

The contact notification agent action can now be used across all appropriate GTM agent types.

GRID FLATTENING SUPPORTED FOR PRODUCT CLASSIFICATION DATA ON

TRADE ITEM

You now have the ability to customize/grid flatten the Product Classification grid on Trade Item Manager.

This change provides you with the ability to customize the Product Classification grid on Trade Item

Manager. You can now configure the screen to view all relevant information (Classification Code –

Attributes) on a single screen.

DETECT INVALID CLASSIFICATION PERFORMANCE IMPROVEMENTS

The Detect Invalid Classifications process - which identifies invalid classification codes on trade items with respect

to a newly downloaded Data Versions, was changed to improve performance.

To improve performance the following changes were made:

o The Detect Invalid Classification Process now raises multiple events. One event for each

Product Classification Code

o Each event Detects Invalid Classification on Multiple Items

Change allows for more Parallel Processing

RPLS – COMPREHENSIVE HOW TO AND CONFIGURATION DOCUMENTATION

A new “How To/Configuration Topic” has been added to Help. This new topic provides the user with

comprehensive documentation for all aspects of GTM’s Restricted Party Screening capabilities

The new Restricted Party Screening covers the following topics:

Overview

o About Restricted Party Screening

Global Trade Content

o GTM Content Source

o GTM Content Source

o Download Data Content

o Restricted Party List

o Restricted Party Exclusion List

o Purge Data Content

Page 16: Release Content Document - OTM & GTM 6.3.4

16

o Mark For Purge

Screening Service Configuration

o Screening Service Configuration

o Restricted Party List Filtering

o Exclusion Words

o Punctuation List

o Match Attributes Selection

o Party Manager Review Match Factor Action

Screening Restricted Parties

o Screening Restricted Parties

o Restricted Party Screening (Ad Hoc)

o Screening Service

o Party Screening

o Transaction Screening

Restricted Party Screening Resolution

o Restricted Party Screening Resolution

o Restricted Party Screening Workbench

o Restricted Party Screening Work Queue

Match Engine

o Match Engine Overview

o Exact Match

o Substring Match

o Keyword Match

o Dice

o Soundex

Metaphone

RPLS - SUPPORT BI-DIRECTION MATCH CAPABILITY FOR DICE ENGINE

You now have the ability to define the match direction (forward, reverse, both) and threshold at the individual

field level when using the Dice Engine. This capability allows you to configure GTM’s RPLS matching logic to

calculate a match factor for the forward case i.e., match factor based on party value length and/or the reverse case

where the match factor is based on the denied party value length. This enhancement improves the overall match

quality by reducing the number of false positives.

Page 17: Release Content Document - OTM & GTM 6.3.4

17

The Dice Engine now supports Reverse Matching (i.e. with respect to Denied Party)

Available options are Forward, Reverse and Both

The Match Direction and Threshold can now be set at the Individual Field Level

RPLS - SEPARATE WORKFLOW THREAD GROUP FOR TRANSACTION PARTY

SCREENING AND CONTACT (BATCH) PARTY SCREENING

A new Workflow Thread groups has been created to keep the Contract Party Screening (Batch) separate from the

Transaction Party Screening.

Previously, both screen processes shared the same thread group – in some situations the transactional

party screening would be delayed while the contract party screening process was executing.

With this enhancement the two processes can be managed independently.

The Workflow Thread Groups for Contract Party Screening are:

o glog.workflow.topic.group.gtm.server.workflow.party.ScreenParty=agentGtmRPLS

o glog.workflow.topic.group.gtm.server.workflow.adhoc.ScreenParty=agentGtmRPLS

The Workflow Thread Group for Transaction Party Screening is:

o glog.workflow.topic.group.gtm.server.agent.business.transaction.ScreenTransactionParties=agent

GtmCompliance Newly supported

RPLS - AGENCY CODE MANAGEMENT

The processing and usage of the restricted party list agency code has been enhanced to support restricted party list

agency code changes.

Previously when the agency code assigned to a denied party record was changed GTM treated the

changed record as a new entry. The creation of a new record versus updating the original record

with a new agency code created “orphan” denied party records. The problem with the “orphaned”

denied party records was that these records would show-up as potential RPLS matches.

In 6.3.4 the following changes have been made:

o The Agency Code is no longer part of the Denied Party PK

o Migration

PK Modified, the latest denied party with same entry ID and Agency Code is

retained

Page 18: Release Content Document - OTM & GTM 6.3.4

18

o An Agency Code Power Data UI has been provided which provides the user with standard

finder, finder result and new/view/edit/delete capabilities for the Agency Code list.

The Denied Party List Data Download now automatically checks the current Agency Code List to

insure that Agency Codes included in the latest download already exist in the Agency Code list – if

they do not already exist the new Agency Codes are automatically added to the list.

RPLS - NULL MATCH %

You now have the ability to configure GTM to consider null values as a match (current behavior) or as a zero

percent match (new behavior).

Previously if a denied party field did not contain a value (was null), the matching engine would

assume a match. This behavior tended to increase the number of invalid matches presented to the

user.

In 6.3.4 the following changes have been made:

o A new property has been added that allows the user to configure how the matching engine

handles null values

gtm.rpls.match.setMatchFactorTozero = false – default - provides the same

behavior as before

gtm.rpls.match.setMatchFactorTozero = true – new behavior - null values are

considered as matched with a match % of zero

Those who change this property to “true” - to take advantage of the new behavior should consider

re-evaluating their overall tolerance value setup to adjust for this change in behavior.

RPLS – REVIEW MATCH FACTOR ACTION

You now have the ability to obtain much more information about how a match factor between a party and

restricted party was calculated.

The ‘Review Match Factor’ Action provides the following information:

Displays the details on how match factor is calculated

o Forward Matching Threshold

o Reverse Matching Threshold

o Highlights the matched Word

o Modified Match Factor (based on weight age)

o Overall Tolerance Check

o Display the actual match value with tolerance values

The ‘Review Match Factor’ action is supported on the following screens

o Adhoc

o WorkQueue

o Workbench

o Review Screening Results

Page 19: Release Content Document - OTM & GTM 6.3.4

19

The Review Match Factor action:

Internally performs RPLS screening between Party and Denied Party for a specific service preference

o Note: Match Factor on ‘Review Screening Result’ UI may not match with ‘Review Match Factor

‘ UI, due to:

Changes in DPL or Party or Service Parameters

In the situation where a particular denied party is not listed in the ‘Review Screening Result’ UI, user can now use

the ‘Review Match Factor’ action to explicitly compare Party with Denied Party and determine why it’s not part of

the potential match results.

RPLS - CONTACT - NAME OR ADDRESS MODIFIED EVENT

You can now use the "CONTACT - NAME OR ADDRESS MODIFIED" event to identify Contacts where the

data related to RPLS screening (name or address) have been modified.

A new column “Name_Address_Update_Date” has been added to the Contact table

The “Name_Address_Update_Date” on the Contact is updated when the following data is modified:

o FIRST_NAME

o LAST_NAME

o ALTERNATE_NAME

o COMPANY_NAME

o LOCATION_GID

A new column “Address_Update_Date” has been added to the Location table

The “Address_Update_Date” on the Location is updated when the following data is modified:

o CITY

o COUNTRY

o PROVINCE

o PROVINCE_CODE

o POSTAL_CODE

The new “Update _Date” values on the Contact and Location tables should now be considered when

performing restricted party screening.

GENERATE TRADE ITEM STRUCTURE COMPONENT SEQUENCE NUMBER

The Trade Item Structure Component Sequence Number is no longer a required field and can be automatically

generated for the user if left blank.

The component sequence number is now optional:

if the user enters a value that value will be used (if valid)

if the user does not enter a sequence number value the system will automatically generate the

sequence number using the basis - max(existing sequence number)+1

Page 20: Release Content Document - OTM & GTM 6.3.4

20

CONTENT - PURGE PRODUCT CLASSIFICATION DATA / PURGE BY DATA

VERSION (PC & RPL)

You now have the ability to purge, by version, old product classification data and restricted party list data.

Generic Purge has now been extended to Data Version

The purge process is performed in 2 steps:

o Mark Data Version for Purge

o Purge Data Version

Purge is triggered only when the data is not used at the transaction level

CONTENT - OVERRIDE CHECKBOX TO “FORCE” THE DOWNLOAD OF DATA

CONTENT

You can now “force” the loading of data content via a checkbox on the Download Data Content process screen.

This option is intended to address situations where there is a need to reload the data due to file corruption, an un-

recoverable error or to re-set all of the data and start with a clean slate.

A new check box has been added to the Download Data Content process UI that allows the user to

force load all content available for loading.

The new check box replaces the existing property: gtm.dataload.force Reload.

CONTENT – NOTES TYPE PROVIDED FOR MUNITIONS LIST

The user now has visibility to different note types (when provided) for Munitions Lists product classification data.

The Note Type provides the user with information that allows them to better understand different types of notes

provided in the Munitions Lists (ie. Note Type = Technical Note, Note 1, Note 2, etc.).

The values in the Note Type field are provide by the Customs Info (content provider), GTM

consumes and shows the provided Note Type data.

CONTENT - BREAKOUT NOTES FROM DESCRIPTION FOR ECCN CODES

ECCN product classification code notes are now stored in the Note field.

Previously Customs Info provided the ECCN note data in the description field. In some cases the combination of

description and notes in the Description field would go beyond the 4k column limit of the Description field.

Customs Info has broken the notes out from the description field – making the data easier to read and consume as

well as reducing possibility of hitting the 4k column limit for notes data.

CONTENT - UPDATE GIDS FOR ALL HTS AND ECCN CODES

The GIDs provided by Customs Info for the HTS US and ECCN US product classification codes have been

changed. The new format includes the classification code itself in the GID provided. Customs Info intends to

roll this change out to all HTS and ECCN codes within GTM.

Page 21: Release Content Document - OTM & GTM 6.3.4

21

The GIDs provided by Customs Info for the HTS US and ECCN US product classification now

include the classification code itself

TRADE COMPLIANCE

VIEW RELATED TRANSACTIONS FROM LICENSE MANAGER

You now have the ability to, from the License Balance History page, to click on the Transaction Line IDs shown

in the Balance Adjustment History portion of the License Balance History page and open up the transaction line

view page.

The Transaction Line IDs shown in the Balance Adjustment History portion of the License Balance

History page are now active links which will bring the user into a view page for the related

transaction line.

SERVICE ID VALUE NOW DISPLAYS ON VIEW PAGE OF POLICY

The Service ID value now displays on the view page of the policy.

Under Trade Compliance Management > Power Data > Compliance Rule > Policy, the Service ID

that you set up when creating a policy is now displayed on the view page.

SERVICE PREFERENCE CONFIGURATION: LOOKUP PRODUCT CLASSIFICATION

SPECIFY CLASSIFICATION STATUS

This feature allows you to specify the Item Classification State (Created, Approved and Override) and decide

whether to override current line classifications. This criterion makes the policy function the same as the 'Lookup

Product Classification' action on the Transaction and Custom Shipment.

The following “State” options have been added to the Service Preference Configuration: LOOK UP

PRODUCT CLASSIFICATION

o Classification Created

o Classification Approved

o Classification Override

DISPLAY ITEM NAME ON TRANSACTION LINE FINDER RESULTS

The Item Name field has been added to the Transaction Line finder results, edit, and view pages.

The Item Name field has been added to the pages:

Transaction Line Finder

Transaction Line Finder Results

Transaction Line View

Transaction Line Edit

Page 22: Release Content Document - OTM & GTM 6.3.4

22

CUSTOMS MANAGEMENT

CUSTOMS COMMERCIAL INVOICE

This feature provides you with a standard customs commercial invoice that can be generated from a customs

shipment using standard GTM document determination and document management features. The custom

commercial invoice is shipped with a default set of mappings that the user can adjust through the customs

commercial invoice properties.

The properties listed below determine the data that is displayed when you generate a customs commercial invoice

from a customs shipment. To control the data shown in a customs commercial invoice, you can change settings in

the glog.properties file or the appropriate property set.

Property Description

gtm.cci.param.P_SHIP_FROM_INV_PARTY_QUAL Default: SHIP_FROM.

gtm.cci.param.P_SHIP_TO_INV_PARTY_QUAL Default: SHIP_TO.

gtm.cci.param.P_BILL_TO_INV_PARTY_QUAL Default: BILL_TO.

gtm.cci.param.P_ITN_REFNUM_QUAL Default: ITN.

gtm.cci.param.P_HBL_REFNUM_QUAL Default: BILL OF LADING NUMBER.

gtm.cci.param.P_LETTER_OF_CREDIT_REFNUM_QUAL Default: LETTER OF CREDIT NUMBER.

gtm.cci.param.P_PAY_TERM_REMARK_QUAL Default: PAYMENT TERMS.

Page 23: Release Content Document - OTM & GTM 6.3.4

23

Property Description

gtm.cci.param.P_TX_PKG_COUNT_QTY_TYPE_QUAL Default: PACKAGE COUNT.

gtm.cci.param.P_LINE_QTY_TYPE_GID Default: ORDERED.

gtm.cci.param.P_INVOICE_DATE_QUAL Default: INVOICE DATE.

gtm.cci.param.P_LINE_SO_REFNUM_QUAL Default: SALES_ORDER_NUMBER.

gtm.cci.param.P_LINE_PO_REFNUM_QUAL Default: CUSTOMER_PO_NUMBER.

gtm.cci.param.P_LINE_UNIT_PRICE_CURRENCY_QUAL Default: UNIT_SELLING_PRICE.

gtm.cci.param.P_TX_SUB_TOTAL_CURRENCY_QUAL Default: SUB TOTAL.

gtm.cci.param.P_TX_FRIEGHT_CURRENCY_QUAL Default: FREIGHT.

gtm.cci.param.P_TX_TOTAL_PRICE_CURRENCY_QUAL Default: TOTAL PRICE.

gtm.cci.param.P_TX_TAX_CURRENCY_QUAL Default:TAX.

gtm.cci.param.P_TX_CURRENCY_TYPE_QUAL Default: TOTAL VALUE.

gtm.cci.param.P_CLASSIFICATION_CODE_FOR_QTY No default value. Shipment line will have both the control codes but the quantity value is based on the qualifier which is specified in this property.

AES FILING UPDATE AES EDI TEMPLATE TO ACCOMMODATE REGULATION

CHANGES

The AES filing EDI template has been changed to accommodate the new foreign trade regulations (FTR) export

requirements published on March 14, 2013. These regulation changes were originally targeted to be in place in

April of 2014.

Changed areas:

Ultimate Consignee Type

License Value

AES FILING ARCHITECTURE REVISED

The architecture used to communicate between GTM and customs for AES filing has been re-architected to

eliminate the need for the client to license and setup an MQ Server on the client’s side.

The “Customs Filing Integration Guide” has been revised to reflect the new architecture and setup requirements.

The new communication is based on the JMS Integration Architecture and provides the following:

Ability to integration with other Message Services (e.g. MQ Series, Sonic MQ etc)

Asynchronous Communication

Use Java Messaging Service API

Performed as 2 step process

o OTM/GTM communicates only with WebLogic Messaging Service (OTM /GTM ownership)

o WebLogic Messaging Bridge will forward and/or retrieve messages between WebLogic

Messaging Service and Third Party Messaging Services (WebLogic ownership)

Page 24: Release Content Document - OTM & GTM 6.3.4

24

The “Customs Filing Integration Guide” has been revised to cover all aspects of this new communication

architecture.

Customs Filing with AES

o Overview

AES Requirements

Architecture

Configuring WebLogic Queues

o Creating a Message Queue in WebLogic

o Configuring a WebLogic Queue for Customs Filining

o Configuring WebLogic Queue for Filing Response

Configuring XA Data Source In WebLogic

Monitoring WebLogic Queue Using OTM/GTM Diagnostics

Configuring WebLogic Queue for Erroneous Filing Responses

Configuring WebLogic Message Bridge

o WebLogic Messaging Bridge Overview

Binding Connection Option for Communicating with IBM MQ Serries Queues

IBM MQ Client

WebLogic Messaging Bridge for Customs Filing (Outbound from OTM/GTM)

WebLogic Messaging Bridge for Filing Response (Inbound to OTM/GTM)

XA Adapter

o Installing IBM MQ Client

o Configuring WebLogic to use IBM MQ Client

o Binding File Generation

o Deploying XA Adapter

o Configuring WebLogic Messaging Bridge for Customs Filing

Source Destination

Target Destination

Configuring Bridge

o Configuring WebLogic Messaging Bridge for Customs Filing Response

Source Destination

Target Destination

Configuring Bridge

o Preserving WebLogic Configuration Changes

AES FILING - RULES FOR SUBMITTING HTS US OR SCHEDULE B

You now have the ability designate the primary and alternate product classification type to be used for AES filing

(HTS US or Schedule B). (Bug #17928816)

You can now specify the primary classification type to be used for AES filing

o gtm.aes.param.P_CLASSIFICATION_CODE_TYPE

Page 25: Release Content Document - OTM & GTM 6.3.4

25

The user can now specify the alternate classification type to be used in situations where the primary

classification type is not available

o gtm.aes.param.P_ALLOW_ALTERNATE_CODE_TYPE

GLOBAL TRADE INTELLIGENCE (GTI)

PRODUCT: GLOBAL TRADE INTELLIGENCE (GTI)

Global Trade Intelligence is a Global Trade Management product component. GTI provides configurable

dashboards and user-defined global trade performance metrics that allow you to monitor metrics against business

targets, benchmarks, and forecasts. GTI provides role-based alerting to ensure that the right personnel are notified

of exceptions and deviations from plan. When problems are identified, you have the ability to drill-down into the

supporting data to quickly pinpoint trouble spots.

GTI is a separately licensed product and requires the licensing of additional supporting technology.

GTI Dashboard or integrated business intelligence interface can now be used to analyze GTM data.

New Global Trade Intelligence menu option has been added which includes the following sub-menu options:

Dashboard

My Dashboard

Ad Hoc Query

Administration (viewable when logged in as DBA.ADMIN only)

Alerts

Data Management (viewable when logged in as DBA.ADMIN only)

Process Management (viewable when logged in as DBA.ADMIN only)

Power Data

For more details about GTI refer to the following new documentation:

GTI Reference Guide which contains the following along with other information:

o Lists of dimension and fact tables

Page 26: Release Content Document - OTM & GTM 6.3.4

26

o List of materialized views

o Reports and prompts used for the GTI Dashboard

o Configuration information for GTI

GTI ODI Interfaces Guide which contains the list of ODI packages, variables, user functions,

sequences and ODI interfaces.

gti_fact_deminsions_and_target_list spreadsheet which contains a list of all GTI facts, dimensions,

and target.

Install and configure GTI based on instructions in the following documentation:

OTM Install Guide

OTM Administration Guide

SOFT DELETES FOR GTI – AUTOMATION AGENTS

When data is deleted from GTM PUBLIC an automation agent can now mark that data as deleted in the Global

Trade Intelligence HD. The record remains in the HD, but it is filtered out in GTI.

The MARK OBJECT FOR DELETE ON HD agent inserts a record into the DEL_OBJ_FROM_HD table

when the object is deleted from Oracle Transportation Global Trade Management:

This action must be added to an automation agent listening for the OBJECT - REMOVED agent

event.

After ETL is RUN, in respective fact and dimension table del_in_oltp column would be updated

with ‘Y’.

The PUBLIC soft delete automation agents provided for GTI are:

MARK GTM ITEM CLASSIFICATION ON HD AS DELETE

MARK GTM PARTY ON HD AS DELETE

MARK GTM PARTY SCREENING ON HD AS DELETE

MARK GTM SHIPMENT ON HD AS DELETE

MARK GTM SHIPMENT LINE ON HD AS DELETE

MARK GTM TRANSACTION ON HD AS DELETE

MARK GTM TRANSACTION LINE ON HD AS DELETE

MARK ITEM ON HD AS DELETE

TRADE DIRECTION FROM TRANSACTION LINE CLASSIFICATION ADDED TO GTI

Transaction line classification Trade Direction has been added to GTI. The Import and Export Dashboards have

been enhanced to work off of this data.

Transaction line classification trade direction (Import, Export, null) have been added to GTI.

The Import and Export dashboards have been updated to reflect this change.

Page 27: Release Content Document - OTM & GTM 6.3.4

27

CUSTOMS SHIPMENT AND CUSTOMS SHIPMENT LINE ADDED TO GTI

Facts and dimensions have been added for Customs Shipment and Customs Shipment Line. This capability allows

users to create ad hoc reports based on Customs Shipment and Customs Shipment Line data in GTI.

A new subject area Customs Shipment Analysis has been added for Customs Shipments

o New customs shipment facts have been added

o New time, involved party and customs shipment dimensions have been added

A new subject area Customs Shipment Line Analysis has been added for Customs Shipment Line

o New customs shipment line facts have been added

o New time, involved party and customs shipment line dimensions have been added

Page 28: Release Content Document - OTM & GTM 6.3.4

28

R634_TransportationManagement_RCD_07Nov2014

Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

This document is provided for information purposes only, and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject

to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose.

We specifically disclaim any liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This document may not

be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of

SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered

trademark of The Open Group. 0114