Oracle Transportation and Global Trade

Management 20A Release Notes

Scope and Application | Action Required | Known Issues | Features and
Enhancements | Corrections | Parameters and Properties | Deprecated |
Obsolete | Technical Support

Scope and Application

This document is intended for Oracle Transportation and
Global Trade Management Cloud users, application
consultants, support analysts, and project managers. It
assumes a working knowledge of Oracle Transportation and
Global Trade Management Cloud from a system
administration and user perspective.

Action Required
 Run the Validate All Stylesheets action from the Stylesheet
Content page to ensure that any custom stylesheets that you
have uploaded to the system are proper XML and will be
processed correctly by the system. If one of your custom
stylesheets is not valid, you must re-load it using the Stylesheet
Content page.
 The database view "view_shipment_order_release" has been the
root cause of many performance issues. This view has been
removed from the application to avoid these issues in the future.
It is necessary to review your custom SQL (Saved Queries, Direct
Sql Update, Reports) and replace any occurrence of
view_shipment_order_release with SQL that joins the shipment
and order_release table.

Note: The system will not create this view for new customers but
it will not drop for existing customers who have this view. The is
in case existing customers have agents and other customizations
based on this view.

 If there are custom time zones added in CUSTOM property set

(glog.timezone.<time zone ID> property) then add custom time
 zone into MISSING_TIME_ZONE table via CSV load process. See
issue 29061549.

Known Issues
BI Publisher Reports
If a user with the BI Author role creates a BI Publisher report under the
Custom folder and a user with the role of BI Consumer role logs into
OTM, the user with the role of BI Consumer is unable to see the report
in the Custom folder. This issue is only for BI Publisher reports.

Workaround
You can work around this issue by providing the BI Consumer role
permissions to see the report in OBIEE:

1. Log into OTM in one of the following ways:

 Login to OTM using DBA.ADMIN and go to Transportation
Intelligence > Catalog.
 Login to direct OBIEE SSO URL and go to Catalog tab.
2. Navigate to Custom folder and select BIP Reports.
3. Click on Permissions and provide the BI Consumer role
permissions to the see the report.
Transportation Intelligence
The translations for the TI pre-defined dashboards are based on 6.4.3
translations. This will be fixed in the next version of OTM.

Features and Enhancements

For the list of features and enhancements, see the New Features
Summary and What's New guides.

Corrections
 Oracle Transportation Management Cloud Service
 Oracle Freight Payment, Billing and Claims
 Oracle Transportation Management (base product)
 Oracle Transportation Operational Planning
 Oracle Logistics Network Modeling
  Oracle Forwarding and Brokerage Operations
 Oracle Transportation Sourcing (includes Rate Maintenance)
 Oracle Transportation Intelligence
 Oracle Fleet Management
 Oracle Global Trade Management
 Oracle Trade Compliance
Oracle Transportation Management Cloud Service
 

Issue Summary Resolution

Number
 
Oracle Transportation Management Cloud Service
2808290 Remove on-premise external Public data related to
1 service engines from OTM on premise external
Cloud. service engines has
been removed.

2890496 Increase default thread counts Changed the default

3 for transport queues. The number of transport
default thread counts for threads for both the
Services and HTTP Transport Services and HTTP
are too small. queues to 4.

2989549 SSL cert diag/collector needed Add diagnostic new

3 for dynamically loaded collector to list
certificates. installed custom CA
certificates.

2992665 Update Getting Started Guide Added descriptions of

5 with: how to configure
1. Customer should publish a Sender Policy
MX record in DNS for the Framework to be
domain they intend to use compatible with Oracle
in FROM. This MX should Cloud deployments of
accept SMTP traffic to OTM.
handle hard bounces
 (OOO / invalid recipients).
2. Add our master SPF
record
spf_c.oraclecloud.com to
their domain's DNS
record. This will enable
SPF checks to pass and
hence prevent our SMTP
gateways from getting
bad reputation.
2995644 Make the new SSL cert
5 diag/collector viewable online
by a user with an Admin role.
3011489 There is an error when you
5 view the Pickup Summary
report the first time via the
OTM menu (Transportation
Intelligence > Catalog > Shared
Folder > Pickup summary
report). If you close the tab and
re-run same steps, the report
opens as expected.
SSL CERTIFICATES
diagnostic collector is
now available to
DBA.ADMIN role users
at the Configuration
Collection and Collect
Diagnostic Logs UIs.
OTM/GTM does not
support access in
BiPublisher reports
(either custom reports
or those provided by
OTM/GTM) from the TI
or GTI catalog. If you
go to either
Transportation
Intelligence > Catalog
> My Folders or Global
Transportation
Intelligence > Catalog
> My Folders, you may
see an error. Since this
support will not be
added to TI or GTI, the
following note was
added to several TI,
GTI, and report help
topics:  Note: You

3018498 You get a blank page when
9 opening a report in PDF format.
(Business Process Automation
> Report Manager > Pickup
Summary report.) Switch to
HTML format, and the report
opens. This happens in Internet
Explorer (IE).
3053282 As part of the upgrade to OTM
1 19c, the INTEGRATION IN
custom data queue parameters
(like batch size, thread count,
etc.) were getting overwritten
by the default value.
Oracle Freight Payment, Billing and Claims
Issue Summary
Number
cannot access BI
Publisher reports from
the catalog! This
functionality is not
supported.
This is fixed. The
report opens correctly
in PDF format in IE.
As part of the upgrade
to 19c, the
INTEGRATION IN
custom data queue
parameters (like batch
size, thread count, etc.)
were getting
overwritten by the
default value. This is
fixed. The
INTEGRATION IN
custom data queue
parameters (like batch
size, thread count, etc.)
will be retained and
will be used for all
inbound processing.
Resolution
Oracle Freight Payment, Billing and Claims
289525 There are transactional
36 issues while creating credit
notes and consolidated
credit notes. The saving of
the credit note and the
creation of order release bill
records are not in the same
transaction. Similarly the
creation of order release bill
records does not seem to be
happening for consolidated
credit notes.
294689 When creating a
70 consolidated invoice,
SmartLinks are not working
when a parent invoice is
accessed from the results
screen.
296233 Change the cost in the UI
70 using a different currency
preference. In the
SHIPMENT_COST table, the
COST_BASE is stored with
the latest EXCHANGE_RATE
available ignoring the
EXCHANGE_RATE_DATE
specified in the table. This is
seen in SHIPMENT and
INVOICE_LINEITEM for
COST_BASE columns.
298216 Allocate an order by line
36 level. Generate the Voucher
XML. You cannot find tag
This issue is resolved.
Creating a bill credit note
and adding entry in the
join table
order_release_bill are now
made in a single
transaction. Entry is not
added in the join table for
invoice credit note. Entry
for the consolidated
credit note in
order_release_bill join
table is not required as
the child credit notes
have already been
entered in the table.
Fixed the issue with
SmartLinks when
selected from parent
invoice, which is created
using the Consolidate
Invoice action.
This issue has been fixed
and now the appropriate
EXCHANGE_RATE_DATE
will be used to set the
COST_BASE.
The
ReleaseAllocShipmentDet
ail tag is now shown
 ReleaseAllocShipmentDetail
in the XML output. However,
if you allocate at the order
level, the
ReleaseAllocShipmentDetail
is found in the XML output.
300213 There's a display issue when
68 removing the "Cost Type"
and "Description" from the
Invoice Manager Layout. The
values are visible, but in
different columns than
expected.
301148 Unable to run "Resolve
58 Claim" action for more than 9
claims. You get a
"java.lang.NullPointerExcepti
on".
301977 Add general ledger details to
89 order base line allocation.
305326 Created a new remark
12 qualifier with data query type
of CLAIM, but it is not visible
in the Claims screen. A
similar remark qualifier for
order release is visible.
Oracle Transportation Management (base product)
Iss Summary Resolution
ue
Nu
when the allocation is
done at the order release
line level.
Resolved the alignment
issue when fields are
removed from the Line
Items grid of the Invoice
Manager Layout.
The exception is resolved
when running the action
"Resolve Claim" on 10 or
more claims.
General ledger details are
now assigned to the order
base line when cost is
allocated on shipment,
invoice, or bill.
Fixed the issue to display
newly created remark
qualifier with data query
type of CLAIM in the
Claims screen.
mb
er
Oracle Transportation Management (base product)
258 Label "As OF" is missing
239 from the Turkish
44 translation.
274 When creating a custom
234 event, raising the event
22 via a parent agent event
also raises the ORDER -
DATES MODIFIED event.
274 When the Out XML Profile
319 Template is used for
76 generating the XML
output, the response
generated contains only
the Shipment Header.
280 Using an external rating
427 engine for rate evaluation,
02 you may see a
NullPointerException
(NPE). After the NPE,  this
rate offering is ignored
and the evaluation moves
on to the next available
Resolved the issue with missing
the translation in Turkish. "As
Of" is now translated.
Fixed handling of custom events
within the event tree. Raising a
custom modification event
should now only trigger listeners
to that event and any event
explicitly declared as a parent to
it.
Out XML Profiles for the reply to
a RemoteQuery/ShipmentQuery
were not being applied correctly
when the profile was based on
an XML template. This has been
resolved.
Note: XML Templates always
need to contain a Transmission
XML document even if they are
to be used for a
RemoteQueryReply which would
normally be returned in a
TransmissionAck.
Fixed the null pointer exception
which was occurring when the
OTM rating happens with an
external rating engine defined at
the rate offering.
 rate.
280 Ad an invocation check
433 for qdlogs.
74
288 The "Business Number
876 Named Range Event -
30 Warning Threshold count"
did not take effect and did
not send an email when a
range is closed and a new
range is added.
289 Modify the feature to
047 upload Transmission via
74 Direct Load (DirLoad) to
more closely integrate
with how the core
integration application
functions.
Added a validation check to the
list of configuration or
performance collectors sent to
qdlogs from OTM. If a collector is
not a valid collector in the
database, it is skipped. This
protects OTM from collector
injection.
The "Business Number Named
Range Event - Warning Threshold
count" was looking at pooled
count of closed ranges as well as
active ranges. Modified warning
thresholds to exclude closed
ranges.
DirLoad has been modified to be
more closely integrated with how
the core integration application
functions. Direct Load is the
process whereby new business
objects can be pre-loaded more
efficiently without having to
trigger any workflow that would
otherwise be needed for
subsequent business processes.
Prior to this change DirLoad
processing did not correctly set
the completion status of the
transmission and this is now
resolved. Additionally, there is a
new Event Group for which,
depending on volume, the
number of threads can be
configured in the usual manner.
Refer to the Integration Guide for
DirLoad processing and the
system configuration

289 OTM has unnecessary
460 methods that, for
78 scalability, send out
unnecessary JMS
messages between
servers.
289 You get a javascript error
527 when you choose a value
76 for stop alternation break
on SMC discount.
289 Remove
532 "isHandlingUnitStackable"
45 from the item inbound and
outbound schema.
289 In view mode, the
532 secondary charge rule
58 does not show records
added in contracts on the
secondary charge grid.
289 When send an interface
587 transmission with invalid
41 records, the entire
transmission fails. Only
the transmission of the
invalid records should fail.
289 Getting a null pointer
871 exception on console
87 while attaching a
document to a tracking
event. No functional loss
documentation for thread group
tuning.
Removed the unnecessary
methods to reduced overhead of
order release updates in a
scalability environment.
The javascript error is no longer
seen when the value for stop
alternation break is changed.
Previously deprecated element
"isHandlingUnitStackable" under
Packaging from Item schema has
been removed permanently. Any
existing integrations using this
element should use the
replacement element
"IsAllowMixedFreight" instead.
Fixed so now secondary charge
rule view screen is showing the
contracts for a secondary charge
correctly.
To fix, we added better handing
of default values for the
web_service_type value for SOAP
web services.
Whenever a document is
attached to a tracking event, the
event TRACKING EVENT -
DOCUMENT ATTACHED is raised.
The event was throwing a null
 though. pointer which has been fixed.

290 Set the minimum pool size Revised connection pool sizing
058 for OTM pools to be the to ensure initial capacity is the
84 same as the maximum same as maximum capacity. This
capacity in Cloud. improves performance and
avoids contention when
shrinking pools.

290 Document management UI The "Used As" field on the

249 is not showing "Used As" Document View/Edit UI was
63 field for existing showing up blank or, in some
documents. cases, not showing up at all.
This is fixed and the "Used As"
field value is populated correctly.

290 While creating a new To fix, the Batch Process screen

377 batch process, when you has been modified to properly
07 enter process parameters, handle multi-page process entry.
the "Search For" drop For a process requiring two
down appears as null. pages, adding the process to a
Batch Process will force you to
fill out the first page and then
switch to the second. Previously,
Batch Process did not properly
handle multi-page processes and
only showed the second page.

290 Unable to see new fields This is now fixed and the
417 when we export required tags are present.
33 consolidated documents.
The Document Export
XML should have
consolidated related
document tags.

290 The UTC pl/sql package is The UTC PL/SQL package has
615 used for date conversion been modified to use database
49 from UTC to local or local SQL functions instead of JAVA to
to UTC. UTC package may do date conversions. List of
be used in user defined database time zone names can
reports and queries. Note be found in v$timezone_names
 that UTC package is not view. Database time zone file
used by application to do version can be found in
any date conversion. UTC v$timezone_file.
package is using Oracle MISSING_TIME_ZONE table holds
database JAVA to do date custom time zone offset.
conversion. The Users may use
dependency on JAVA MISSING_TIME_ZONE table to
should be removed. over-ride database time zone
offset or add missing time zone
offsets. UTC package will look
into MISSING_TIME_ZONE table
for time zone offset at first, if it
doesn't find time zone in the
MISSING_TIME_ZONE then it will
derive offset using SQL
functions. MISSING_TIME_ZONE
table can be updated by CSV
load process.

291 On the Workbench, when The time total will now show the
350 a time column is selected UOM. The UOM is based on user
16 for totaling, the total is preference settings. This
shown in hours and the behavior is similar to the OTM
time is rounded to the finder.
nearest hour, without a
UOM.

291 Have a business monitor Fixed the sequence order in

393 with 42 saved queries. business monitors.
34 When you call up the
monitor, the saved
queries are not ordered
the same as the sequence
numbers in the Business
Monitor manager. They
are ordered
alphabetically.

291 When generating a CMS The issue occurred when a

722 (content management document was uploaded via
93 system) parameter which integration, the CMS was
 uses BN (business anything other than DATABASE
number) to generate the and the owner data query type
parameter value and the was ITEM. This is now fixed.
owner data query type is
ITEM, a SQL error is
thrown.

291 DB.XML is being uploaded To prevent unintended

723 that is causing repeated performance impact to a running
33 server outages due to server, the volume of data that
stuck threads and can be submitted in any one
memory issues. DB.XML import request or
Migration Project Object Group
import will be limited to 5 MB
(megabytes). It will be possible
for extreme use cases to
increase this limit up to 10 MB
but this requires a System
Administrator role. The limit is
not exact as whites pace and
comments are not counted but
as soon as 1 character more
than the limit is detected when
reading the import request data,
the request will be rejected and
an exception logged on the
server to record the reason for
rejection.

291 Diagnostics are triggering Added configurable limits to the

933 an out of memory issue. Open Processes screen:
26  glog.process.walker.maxDe
pth: This determines the
maximum depth of tree
nodes to display on the
screen. If exceeded, the
parent node is shown with
a right error to denote
deeper nodes. Default: 100

292 When adding a document
570 and selecting a "Link
45 Document" which has
already been linked to a
different business object,
the error message needs
to be modified.
292 For Cloud instances,
983 remove the capability of
46 setting the login page
logo.
293 The charge multiplier
355 options namely -
91 "Smallest Individual Break
Comparator" and "Largest
Individual Break
Comparator" are not
working properly and are
giving inconsistent results
when evaluating rates.
294 Shipment is not being
329 built due to the rate geo
48 sequence number being
too big. Create a rate
record from UI setting a
high rate geo cost
sequence number. When
OTM  tries to commit
 glog.process.walker.maxNo
des: This determines the
maximum number of tree
nodes to display on the
screen. If exceeded, the
previous sibling or parent
node is shown with a down
error to denote more nodes.
Default: 500
Now a proper error message is
displayed when you try to link
the  document via web action
"Add Document".
By default, the login page logo
variable has been removed.
The charge multiplier options
namely - "Smallest Individual
Break Comparator" and "Largest
Individual Break Comparator"
were not working properly. They
have been fixed.
The error stemmed from OTM
only being able to store numbers
up to 10 digits. Changed the data
type of the rate geo cost
sequence number column to
resolve the issue.
 shipment, it fails at the
shipment cost level and
the error indicates that
sequence number is too
high.

295 Bad formatting on finder Updated code to fix bad

348 results screen for double- formatting on finder result for
74 byte character languages. double-byte character languages.

295 The Action drop-down is The Action drop-down list

418 not visible as it should be appears now.
84 when adding the action to
any sub-group on any
object type.

295 Applied a VPD on a list of Fixed finder results to show all

526 favorite locations so that favorites that have not been
49 one location cannot be excluded by the applied VPD.
read. If an order is
created and the list of
favorites is pulled to
select a location, only the
favorite locations listed
before the "VPD location"
are available. The rest of
the locations are no
longer available when
they should be.

295 Unable to add a value to Fixed so you can now add or

535 or remove a value from a remove values in this scenario.
58 fixed list when editing a
manager layout.

295 Cannot see full screens Fixed to show a scroll bar when
536 when on Android and iPad. the window size is small.
89 For example, cannot see
the domain or the Help
icon.

295 Update the Cloud Cloud Administration Guide was

978 Administration Guide with updated to include the
60 information on the EXTERNAL_SYSTEM_SERVICE
EXTERNAL_SYSTEM_SER table in the P2T section.
VICE table in the P2T
section.

296 Upload XML to update the The User Preference Integration

184 User Preference for a XML will now process
37 User ID. You get a successfully. The
java.lang.NullPointerExce NullPointerException is no longer
ption and the seen, and updating the User
transmission is in ERROR Preference for a User ID now
status. works correctly.

296 Contention in finalize Removed finalizer overhead from

234 method. every connection object. This
16 overhead will only be added
when leak detection is enabled
for the connection's data source.

296 When a release Release modifications will now

315 modification comes with a be propagated to the shipment.
60 line update, the change is
not propagated to the
shipment due to the
following error "Cannot
delete the
SHIP_UNIT_LINE_T
record.".

296 Stack overflow error when When data query custom events
505 interrupting a data query. were published without
16 interested parties or agents, the
process tree would grow
arbitrarily deep in the thread of
execution. Added a placeholder
to maintain process interest in
these events to avoid the
memory buildup.

296 There is a shipment stop Fixed the one year wait time
563 date issue with Relay issue on the shipment stops
44 Shipment In Transit -
Force. Enter the Relay
location ID. The Shipment
Stop shows 365 days of
wait time. Have a location
that has a calendar with a
7 day cycle. If the
calendar is removed from
the shipment there is no
issue.
296 Clarify the link between
776 the Cloud Getting Started
64 Guide and the Cloud
Administration Guide.
While there currently is a
link, it is not as visible as
it could be. Create a
chapter in each guide to
specifically reference
what content exists in the
other guide, and then link
to that guide in the Cloud
library.
296 When you click the help
821 link for either the AWR or
25 AWR SQL screen, you get
an error.
296 Retrieving all records in a
821 query object is not thread-
27 safe.
296 Agents are generating
946 intermittent errors of
43 "Named bind variable
$CHILD_EVENT_GIDS not
defined.".
296 In Purge Diagnostic Logs,
when the location calendar does
not have any activities defined
on them. Set the property
"glog.optimization.scheduling.dri
veSimulator.suppressWaitTimeIf
WorkPeriodNotDefined" to true to
suppress the wait time caused
due to unavailability of work
periods on the calendar. The
default is false.
The Cloud Getting Started and
the Cloud Administration Guides
were updated. In the Admin
guide, a chapter was inserted as
Chapter 1. This includes a link to
the Getting Started Guide.
Similarly, a chapter was
appended to the Getting Started
Guide referencing the content
found in the Admin guide. Links
are present in both guides and
will open the latest guide on
docs.oracle.com.
Fixed the help links on the AWR
input screens.
Resolved thread-safety issue
when retrieving all records via
query-by-example.
Resolved a possible race
condition between agents /
notification that would allow an
agent to be run without
assigning CHILD_EVENT_GIDS
properly.
Removed Hour and Minute
948 the "Older Than" drop support from Purge Diagnostic
31 down allows D/M/S, Logs. Added a minimum value of
however, the 1 day.
purgeQDLogs script only
allows days. Also, if days
is zero, the purge doesn't
do anything.  
We should only prompt for
Days, and validate that
the value is greater than
or equal to 1.

297 OTM rate inquiry is slow Cached the corporation primary

012 when running a rate keys and the performance is
87 inquiry via Ask Oracle. It improved.
takes between 20-30
seconds to return a rate if
we specify a Contact (i.e.
Customer) as a constraint.
Without that constraint,
the rate query comes
back in 2-3 seconds.

297 Any user, as well as Fixed so now when you manually

105 carriers, can schedule an
30 appointment by dragging
and dropping to blocked
slots when using the
workbench.
block the slots and try to drag
and drop a shipment stop onto
the blocked slot in workbench,
the appointment will not be
scheduled.

297 A null pointer exception is Fixed the issue so loading of

106 seen for actions that special service will not cause a
60 require special service to null pointer exception.
be loaded.

297 Shorten length of certain Following column size reduced to

165 fields to handle 1000 characters (shown as
18 replication. table_name.column_name):
 OB_LINE_ATTRIBUTE.ITEM_
FEATURE_VALUE
 OB_SU_CONTENT_ATTRIBU
TE.ITEM_FEATURE_VALUE
 ORDER_RELEASE_LINE_ATT
RIBUTE.ITEM_FEATURE_VA
LUE
 APP_ACTION.ALLOW_CAUS
E_MSG_GID
 APP_ACTION.ALLOW_SOLU
TION_MSG_GID
 APP_ACTION_CHECK_ACCE
SS.ALLOW_CAUSE_MSG_GI
D
 APP_ACTION_CHECK_ACCE
SS.ALLOW_SOLUTION_MSG
_GID
 AUTO_ASSIGN_TYPE.VALU
E1_TRANSLATION_GID
 AUTO_ASSIGN_TYPE.VALU
E2_TRANSLATION_GID
 AUTO_ASSIGN_TYPE.VALU
E3_TRANSLATION_GID
 ERROR_HELP.ERROR_TRAN
SLATION_GID
 EXTERNAL_ENGINE_PARAM
_VALUE.TRANSLATION_GID
 ORACLE_ERROR.ERROR_TR
ANSLATION_GID
 ORACLE_ERROR.SOLUTION
_TRANSLATION_GID
 STATUS_FUNCTOR.SAVED_
CONDITION_CAUSE_GID
 TRANSLATION.TRANSLATI
ON_GID
  TRANSLATION_D.TRANSLA
TION_GID
 VALID_VALUE.TRANSLATIO
N_GID
 VALID_VALUE_TYPE.TRANS
LATION_GID
The following column size is
reduced to 949 characters:
TRANSLATION.TRANSLATION_XI
D.

297 Performance issues in the Create index on following

194 business monitors. We table/columns:
81 have two business  Table:
monitors (GTM_OKS GTM_ITEM_CLASSIFICATIO
PERIODIC and N
GTM_OKS_QEND) which
are timing out without  Columns:
displaying the results. GTM_PROD_CLASS_TY
PE_GID,
DOMAIN_NAME,
GTM_PROD_CLASS_TY
PE_GID
 Table:
GTM_PARTY_SCREENING_C
OMMENT
 Columns:
CONTACT_GID,
PARTY_SCREENING_S
EQUENCE,
PARTY_COMMENT_SE
QUENCE
 Table:
GTM_PROD_CLASS_CODE
 Column:
GTM_PROD_CLASS_TY
PE_GID
  Table: GTM_TRANSACTION
 Column:
GTM_TRANSACTION_
XID
 Table: ITEM
 Column: ITEM_NAME
 Table: ITEM_REMARK
 Column: ITEM_GID
REMARK_TEXT
 Table: REGION_DETAIL
 Column: REGION_GID

297 When trying to customize Statuses now show correctly for

607 the Screen Set, the SKU and
62 LOCATION_ASSET_INVEN LOCATION_ASSET_INVENTORY
TORY, OTM is showing finder sets.
Status Values instead of
Status Type.

297 Prevent uploading PUBLIC Prevented Manager Layouts and

611 Manager Layouts, Finder even Finder Sets and User Menu
04 Sets and User Menu Layouts from accepting records
Layouts using the in the PUBLIC domain. For
Migration Project. example, users can corrupt
public manager layouts if
included in a migration project.

297 Changes to manager Resolved so now the isTemplate

787 layout field can be set to read only to
53 "ORDER_RELEASE_WO_ST make mandatory fields or not.
OPS not honored if some
fields are read only or
hidden.

297 Update the OTM Updated the translation files.

902 translation files to a
53 translation basis of 19A
for supported languages.
297 Add Dutch translations
904 with a translation basis of
23 19A.
297 When running Rate Inquiry
910 from a copied screen set,
99 you get an error.
297 Having a screen set
911 configured to display
20 precision as 2, the
precision is not respected
for the results screen. The
result screen shows the
value from
glog.currency.displayPreci
sion.
297 When you try to run
951 allocations based on
45 weight, a null pointer
exception is seen if no
weight is set for the
allocation metric.
298 Deprecate and disable
024 XML credential parser for
61 inbound integration.
298 The default for
Added Dutch Translation and
support for the translation into
OTM.
This issue is fixed. The issues
was caused by setting the
precision of a view field which
had a label attribute specified.
Setting the precision of a view
field which had a label attribute
specified will no longer add a
new label attribute.
You can now set the screen set
result precision to 2 and it will
save and work correctly.
Fixed so now when you tries to
run allocations based on weight,
an exception is seen rather than
a null pointer exception if no
weight is set for the allocation
metric.
Added new optional feature
'DISABLE MESSAGE
CREDENTIALS' to disable
capability to send credentials in
a message body and instead
force authentication using HTTP
Basic Authentication over TLS or
WSS for SOAP Web Services.
This is part of increased security
measures.
Modified
032 glog.dataqueue.blockTran
83 sport is true, it should be
false.
298 Allow delete of order
093 release lines as a root
68 resource via REST API.
298 Null transmission body
108 error loading
79 TransmissionAck XML.
298 Unable to configure Auto
188 Assignment Rule -
83 Definition tab.
298 French accent characters
216 appear as question marks
27 in the error message for
an action check not
displaying in the screen
set result.
298 When adding a new
216 shipment ship unit to a
53 shipment where the ship
unit is not currently on the
shipment and there are
other shipment ship units
associated with the ship
unit on a parallel
shipment with a
downstream shipment,
the order movement
created for the new
shipment ship unit did not
have its Destination Tag
set.
glog.dataqueue.blockTransport
so that data queues no longer
wait on transport queues by
default.
Update and delete capability has
been added to REST
orderReleaseLines.
The capability to send an
inbound TransmissionAck in
response to an outbound
Transmission had been disabled
in error. This fix reinstates the
previous capability.
Fixed the issue.
Fixed to show the error message
properly and no longer show a
question mark when using
French.
This is fixed, so that the new
order movement's Destination
Tag is set to match the Source
Tag of the order movement
associated with the downstream
shipment.
298 When processing An exception message was
216 MessageAck element into showing in the log file when an
61 OTM using WMServlet inbound MessageAck XML
with basic authentication, message was received although
the message processes processing of the message
without any issue but in continues successfully. The
OTM Web Log gets an exception message has been
error. suppressed.

298 Update the ACL topic in Updated the ACL topic in the
217 the REST API Guide so REST API Guide so that consols
33 that consols are are correct.
corrected. The ACL for
consols should be "REST -
Consol - Update" and
"REST - Consol -View".

298 Order release planning Fixed so OMD - Edit Shipment

454 status does not reflect and OMD - Propagate Changes
30 changes. An order is will correctly set the order
planned, tendered, and release status to
tender accepted, with the PLANNING_UNSCHEDULED if the
parameter set - OMD SMD order is no longer on a shipment
WITHDRAW TENDER and/or order movement.
BEFORE REMOVING
SHIPMENT set to TRUE. A
modification is sent for
the order setting the
quantities to 0, and
running the agent action
and OMD-EDIT SHIPMENT.
Shipment tender is
withdrawn, the shipment
and order movement are
deleted as expected.
However the Order
Release PLANNING
remains in
PLANNING_EXECUTED -
FINAL. It is should be
updated to
 PLANNING_UNSCHEDULE
D to show the order is no
longer planned on a
shipment. Same behavior
is seen with ORDER
RELEASE - OMD -
PROPAGATE CHANGES.

298 Interim point stop not If the itinerary leg (domestic)

682 inserted for domestic specifies an interim point with
45 shipments. When the option "BEST", the interim point
itinerary is Country to was not getting inserted when
Country (USA to USA), and the shipment was built. Now it is.
the itinerary leg specifies
an interim point with
Option "BEST" the interim
point does not get
inserted when the
shipment is built.
However, if the itinerary is
USA to Canada, the
interim point is inserted.

298 In a web/app environment, Added patch property resolution

723 glog.properties includes to both web-tier and app-tier
79 both property branches.
glog.webserver.properties
and
glog.appserver.properties.
As both of these files
include
glog.common.properties,
we end up with common
properties on two parallel
branches of the subtree.
This is problematic with
patch properties since
only
glog.appserver.properties
is including patch
 properties.

298 An agent error is thrown An open cursor was causing the

783 when receiving tracking issue. Fixed issue to now close
53 event notification. the query and stop the cursor
leak.

298 Count returned as zero for Fixed the issue with data query
783 data query but the long when no records matched the
80 running task keeps saved query. The batch process
running. now completes normally.

298 Many objects are in Added an optional feature,

901 "waiting" status inside AGENT LOOP LOCK
10 Object Deadlock for more SUPPRESSION, to control
than 6 days. whether Data Type Association
actions and FOR actions lock the
parent record as well as each
child record. If the Optional
Feature is enabled, the parent
locks are suppressed. This
optional feature was
implemented via two properties:
 glog.objectLock.locks.activ
ity.FOR (AGENT) = false.
This was an existing
property in OTM.
 glog.agent.dta.lockParent =
false. This is a new
property to control Data
Type Association lock
behavior. The default is
true.

298 The Public The broken links have been

914 ASK_ORACLE_MENU has fixed.
80 broken links. Either
nothing happens or you
get a 403 error.

298 Roles listed in user role Open Settings and Actions. Click
917 drop-down should be the "User Role" drop-down. The
41 alphabetized. values are now sorted
alphabetically.

299 When deleting a single Fixed the issue that when

029 Favorites table from deleting a favorite table from
92 Configuration and Favorite page, other favorite
Administration all of the records were also deleted.
records for Favorites are
deleted when viewing
Favorites from the unified
global header.

299 Would like to increase the You can now increase the
069 number of user roles in number of records returned in
15 the drop-down list of the the User Role drop-down list.
Settings and Actions pop- This is enabled with the new
up. glog property
"glog.webserver.userrole.droplist
.limit". The default value is 1000.

299 Have a shipment with You now have the option to

137 both the weight and configure that when you have a
74 volume as zero. The shipment with both the weight
Loaded Distance is and the volume as zero, the
calculated, although it Loaded Distance is calculated as
should be zero. At the zero. In order to use this
shipment stop level, the functionality, you need to specify
distance type is also whether a zero weight and
'Deadhead'. If both the volume shipment should have
weight and the volume are only unloaded distance via the
zero on an order release property:
then it is considered a glog.business.shipment.isZeroWe
Deadhead move i.e. ightVolumeShipmentUnloaded =
loaded distance on the false (the default).
shipment should be zero.

299 Update the Cloud Added the following text to Cloud

137 Administration Guide to Admin Guide: "Transportation
98 add a reference to the and Global Trade Management
OTM REST API Cloud provides multiple public
 documentation in the REST APIs that can be used to
Cloud Admin Guide. access data stored in
Transportation and Global Trade
Management Cloud and
construct integrations to other
systems. You can make many
types of HTTP requests using
Oracle REST APIs. You can
easily make requests to view,
create, update, or delete
records. Where possible a REST
API should be used in preference
to the Transmission XML via
SOAP or HTTP. REST is
eventually intended to support
synchronous and asynchronous
messaging for almost all
resources which is an expansion
of the Transmission XML
capabilities. However, these
capabilities will be added over
the next few updates to the
REST API so in cases where the
feature is not yet available the
Transmission XML message must
be used. For detailed
instructions on how to use REST
APIs, see the REST API for
Transportation and Global Trade
Management Cloud Guide.".

299 There is an untranslated Adding the missing translation.

273 label (label.qdObiee) in
10 collect diagnostic logs.

299 When editing a copy of the Issue with editing a copy of the
321 Order Release without Order Release without Stops or
19 Stops or Order Release in Order Release in Manager Layout
Manager Layout, the add has been resolved.
item button in the second
grid of the Line Item tab
 does not work. When this
button is clicked nothing
happens. This was
encountered when trying
to resolve why an added
field was not displaying
on this screen.

299 The report parameter type The report parameter type

404 "Finder (No Operator)" has "Finder (No Operator)" was
42 been deprecated and redundant since the support for
should be removed. parameter operators stopped.
This parameter type was working
exactly as "Finder" and hence
this option has been removed
from the Parameter Type drop-
down list when defining a report
parameter.

299 Report parameter type This is fixed. Now the report is

405 Finder - List Only - is generated successfully.
87 unable to identify the
object GID when running
the report.

299 Fix all leaked nested Fixed two issues that could
427 cursors. impact cursor resources:
68 1. When loading custom agent
events, a nested cursor
looking for child events
wasn't recovered until all
events were processed. It's
now recovered once done
with its parent event.
2. When loading web services,
a nested cursor looking for
web service parameters
wasn't recovered until all
web services were
processed. It's now

299 Support cursor tracking
428 and diagnostics for active
18 Grid Link pools.
299 Scalability startup fails on
550 initial web notifications.
89
299 Need to set the order
563 release line field
61 Splittable to No for the
order release lines that
are built from the
aggregate order bases.
299 After setting property
963 glog.dock.v5compatible to
35 true (the default is false),
OTM creates multiple
appointments for the
same Shipment using the
shipment action
"Schedule Appointment".
OTM should replace
existing appointments
with the newly created
one.
299 When planning hazmat
963 and non-hazmat orders,
44 inconsistent shipment
consolidation happens.
Hazmat and non-hazmat
recovered once done with
it's web service.
Added leak detection support to
all dynamic Grid Link pools.
To fix this issue, we removed the
functional security requirement
for signed servlets related to
Scalability. These are called
prior to the system fully loading
and can only support data
security. As simple notifications,
they have no need for functional
security.
The Splittable flag on the order
release line is now set to No
when order release lines are
built from an aggregate order
base.
This is resolved and the
appointments are now getting
scheduled properly.
Previously, while consolidating a
pair of shipments into one, the
merged shipment was not being
reevaluated for hazmat
attributes. This was leading to
 orders are combined when
they should not be based
on the rate configurations.
300 When the parameter "Plan
004 with Carrier Commitment"
45 is set to true, the
retendering process is
selecting a service
provider and rate
offering/service time that
results in a time infeasible
shipment when the
service provider has an
alternative feasible
solution.
300 The agent action
004 Recalculate Shipment
77 Stop Times fails with an
error.
300 Update the "Oracle
066 Transportation and Global
95 Trade Management Cloud
Integrating with Oracle
Integration Cloud Guide"
with information on how
to integrate with
Warehouse Management
Cloud.
300 Update the help topic
068 Rate Offering Attributes.
15 There is reference to the
use of "Logic
Configuration" on the
Miscellaneous table. This
incorrect and inconsistent
results in shipment planning.
This issue has now been fixed.
Infeasible carriers were not
filtered out properly. Fixed to
now check the feasibility of the
carrier before assigning a
service provider to a shipment.
Recalculate Shipment Stop
Times and Recalc Estimated
Stop Times now work for SAW
shipments.
Added a new section to the
Sample Integrations chapter of
the "Oracle Transportation and
Global Trade Management Cloud
Integrating with Oracle
Integration Cloud Guide". This
section is titled "Warehouse
Management System
Integrations" and refers to the
My Oracle Support note
(2565961.1) where the WMS-OTM
integration is handled.
Updated the Rate Offering
Attributes help topic to remove
the reference to Logic
Configuration since it is no
longer applicable.
 has been deprecated and
should be removed. There
is no use in OTM for this
field.

300 Trying to customize the Incorrect pseudo column Level

098 Screen Set - Value (P) has been removed and
37 "LOCATION_ASSET_INVEN so cannot be selected as a
TORY". Added "Level(p)" column on the screen set.
as Column. Even though
the database has values
for it, it is not showing
them in screen set.

300 The Message Hub The Message Hub Manager has

218 Manager is missing from been added to the DBA.ADMIN
75 DBA.ADMIN, but is menu.
present in other
user/domains like
GUEST.ADMIN. The
documentation says it
should be available to all
users.

300 Remove Java language Removed Java language from

266 from Appendix A Appendix A messages.
95 messages in the
Integration Guide.

300 Language characters Fixed to show error message

442 issue with Internet properly and no longer showing
52 Explorer. the question mark (or other
special characters) on finder
result page for French.

300 The Dropped the index on

516 ITEM_REMARK.REMARK_T ITEM_REMARK.REMARK_TEXT.
09 EXT column is too big for
the index.

300 When creating a custom When creating a custom

538 shipment screen set, the shipment screen set, the
81 "Column" section within "Column" section within the
the "Default Criteria" tab "Default Criteria" tab no longer
contains duplicate values contains duplicate values.
(Example: Destination
Location ID). You don't
know which duplicate
value is the correct
column to choose for the
default criteria.

300 Unable to set the reserved Modified the behavior of the

626 property Thread Diagnostic screen:
01 glog.threadLocal.allowCro 1. Changed the default of
ssThreadLookup. glog.threadLocal.allowCros
sThreadLookup to false to
avoid the overhead of
tracking open processes by
thread.
2. Allowed
glog.threadLocal.allowCros
sThreadLookup to be set to
true in a property set.
Tracking of open processes
by thread will begin once
this property is set to true;
it will end if this property is
set to false.
3. Modified the Thread
Diagnostics screen to
suppress Process filtering
and display if
glog.threadLocal.allowCros
sThreadLookup is false.

300 We have an agent Changed the data source of

686 listening to the Shipment Shipment Removed Before
29 Removed Before Persist Persist topic from INTERNAL to
INTERNAL agent event. USER when shipments are
But the agent is fired deleted from UI. The issue no
 when the user selects a longer occurs.
shipment and clicks
"Delete" from the UI.

300 When trying to set the The properties starting with

686 property "glog.reqdoc." were made
63 "glog.reqdoc.dqtFromFind reserved in 6.4.3 release. So the
erSet", the following properties starting with
message is displayed: "glog.reqdoc.dqtFromFinderSet"
"The following properties were made reserved. These
are reserved and cannot properties are now marked as
be set or removed in a reserved exceptions so they can
Property Set.". be set or modified if required.

300 Cached entity beans are Added proper support for the
806 not updated in a combined web/app server to
65 scalability environment. determine JMS notification of
cached entity beans.

300 Tiered rating is not Cost based on shipment count is

813 counting shipments calculated correctly while using
29 correctly. tiered rating.

301 Bulk plan fails when the This issue is now resolved. Bulk
021 parameters CHECK plan will no longer fail when the
58 LOCATION CAPACITY and parameters are both set to
HOLD AS LATE AS TRUE.
POSSIBLE are both set to
TRUE.

301 When a release Changes will now be propagated

148 modification contains to the shipment when fields
78 changes for dates and line other than quantity, such as
updates for declared dates and declared value, are
value, the change is not changed.
propagated to the
shipment.

301 On a custom Manager Fixed so the validation in this

154 Layout, click Fix Errors. scenario will be executed.
98 Then click Finish without
changing the value
 previously entered on the
flex field. The validation
on flex field is not
executed.

301 Time zone causes Modified so that the Set

205 infeasible appointment Appointments action sets the
44 times error when the time in the correct time zone.
action Set Appointment is
run in the Shipment Stops
screen for a selected
stop.

301 When using the Use XML Removed "Schedule" from the
208 Schema check box, you XML Element ID drop-down list in
35 see the option "Schedule" Integration Manager > Generate
in the Select the XML XML Template screen.
Element ID drop-down
list. The Schedule
interface used to be a part
of Batch Balancer/Wave
Management functionality
which was deprecated
long ago. This particular
drop down was
overlooked. The
"Schedule" option should
be removed.

301 For Thai, Japanese, and Fixed to make sure global header
208 Russian users, nothing icons are enabled for Russian,
89 happens when you click Thai, and Japanese users.
the global header icons.
This includes Settings and
Actions to sign out.

301 In a multi-stop shipment, For a multi-leg itinerary scenario,

268 OTM is ignoring the order when an existing order is moved
27 release Delivery Date to the first leg shipment and a
when an order is moved to multi-stop shipment is created,
a shipment. OTM does not the early pickup date of the
 honor order dates on a
shipment.
It seems that OTM applied
driving time to the second
stop departure and just
unloaded at the third stop,
when in fact it should
have arrived and waited
at the third stop and
departed with the order
early delivery date.
301 An error is thrown when
268 trying to upload a
46 document to a location.
301 Error initializing
275 properties for
04 glog.integration.servlet.tr
ansmissionstageerror.incl
udetransmissiontext
(property set).
newly created order movement
should not be removed. This was
the cause of the issue. The issue
is now fixed.
The Upload Document action
requires a directory to be
present so that the uploaded file
can be temporarily written there.
The action did not check if the
directory was present before
attempting to write the file. This
caused an error if the directory
was not present. This has been
fixed. The folder will be created
automatically if it does not exist.
Modified property set validation
as follows:
1. When trying to upload a
PROP_INSTRUCTION record
via CSV or DbXml where
INSTRUCTION = 'INCLUDE',
the KEY representing a
PROP_INSTRUCTION_SET_
GID must map to a valid
property set.
2. When loading properties on
startup (or due to a cache
refresh), only a missing
CUSTOM or
APP_WORKFLOW_THREADI
NG property set will be
 fatal to property setup. Any
other property set specified
in an INCLUDE
PROP_INSTRUCTION record
will log a non-fatal
exception to the log if
missing.

301 AppMachineFailoverQuery Removed

482 is still installed to the AppMachineFailoverQuery from
73 ACR_ENTRY_POINT table. staged CSV.
This ACR record was
removed during a past
migration, but never
removed from the base
CSV file.

301 When deleting an order For order movement planning, if

594 there is an error "Cannot the original shipment ship units
42 delete the on order movements are split
SHIP_UNIT_LINE_T record. while planning, and if multistop
A S_SHIP_UNIT_LINE_T is turned on, and MULTISTOP
record references it in its DISABLE SAME OD PAIRING =
SHIP_UNIT_GID, true, OTM did not delete the
SHIP_UNIT_LINE_NO original shipment ship units. This
column.". The issue is has been fixed.
created during planning.
Create an order
movement from an order
release. While planning,
due to size, the order
movement is planned onto
x shipments. The original
shipment ship unit should
be deleted and a new one
created, but the original
shipment ship unit is not
deleted.

301 When trying to propagate The exception was due to using

594 changes from an order the custom action to trigger the
61 release to a shipment agent. This is fixed. The
after modifying details exception no longer occurs and
(such as quantity, weight, the functionality works as
etc.), you get an expected.
exception. We use a
custom action which
triggers an agent to
propagate the changes.

301 Update documentation to Updated the Cloud

731 specify that template data Administration Guide and the
50 is not purged. Data Purge help topic with this
note: "Note: Templates are not
deleted when you purge data.".

301 Loaded Distance field This issue is now resolved.

734 value on the Online Fields on the Online
50 Booking/Tendering page is Booking/Tendering page now
displayed in miles display based on the preference
whereas the user configured.
preference is set to
kilometers.

301 The field Flexible The Rapid Order Release screen

734 Commodity Qualifier is now works correctly with the
53 removed from the "Enter field Flex Commodity Qualifier
Units to be Shipped" removed.
section on the Rapid
Order Release manager
layout. Go to the Ship
Date on the Rapid Order
Release page and click
the calendar. It does not
display.

301 The rate cache remains This issue is now resolved.

734 intact even when the Cache is refreshed even when
56 inactive rate record is the RateGeo is inactive.
modified.

301 Block updating DBXML and CSVUtil no longer

856 otmSystem and guest by support updating of reserved
30 CSVUtil or DB.XML. GL_USER records, i.e.,
otmSystem and guest.

301 TopicInterface does not Added support for a Topic

934 trigger the desired topic. interface request to be
64 immediately executed or
published. If published, there
may be a small delay in
processing the topic as it's made
available to all servers in the
cluster. The request behavior is
controlled by the following
property:
glog.integration.Topic.loadBalan
ceAcrossServers = true|false]
If true, the topic is published for
all servers; if false, it is executed
on the current server.
Added an optional feature, LOAD
BALANCE TOPIC INTERFACE,
that controls whether the topic
is executed or published.

301 In the Report Designer Added instructions for custom

938 Guide, clients are reports to ensure they are
29 instructed to place their migrated.
custom reports in a
"custom" folder. These
references need to
consistently be to a
"Custom" folder. The case
is very important and has
caused issues with a
recent notification to
regarding the custom
reports.

301 Login with your user name The web server configuration
998 and password and you was updated to resolve this
39 may get the following intermittent error seen after a
 error "403 - Forbidden. successful login to the OTM front
You don't have permission end.
to access /favicon.ico on
this server.".

302 In the help topic Fixed the first line. It now reads
172 Allocation Method, the as follows: "Weight direct
02 description for Weight distance is the weight of an
Direct Distance says order on a shipment multiplied by
"Weight direct distance is the direct distance between its
the weight of an order or origin and destination.".
shipment divided by the
direct distance between
its origin and destination."
That's wrong. It should
say multiplied by - not
divided.

302 When you click on the Fixed to remove the invalid

224 SmartLink, Track and character error. Now the
48 Trace, on a shipment, SmartLink displays correctly.
OTM does not display any
information. It just
displays a blank screen.
In the console logs, you
see an exception.

302 When trying to send a Made the ClearCaches topic

229 CacheRefreshTopic for compatible with scalability.
96 ClearCaches in a SCA
environment, we get an
error. This has to do with
the way Cache Refresh
topics are persisted for
POF.

302 Null pointer error in rate A null pointer was being thrown
277 distance when the when looking up distance using
80 properties are not set. PCMiler. This has been fixed.

302 When you try to remove To fix the issue, changed the
344 the appointment from the Save button to avoid multiple
52 Dock and Yard Managers
screen, you get an error
'Object type is not
supported'. Happens in
Internet Explorer 11.8 and
11.
302 Update the External
344 Programming Interface
61 Guide to include the new
external service engine
(ESE) web service feature
added in 19C.
302 When trying to delete the
376 old tables in a workbench,
20 which was updated to
contain tables with
multiple links to other
tables, the following error
appears: "An Undefined
Error Has Occurred.
Please Try Again Later.".
302 On the Trade Transaction
513 screen, the "View Party
02 Screening Results"
hyperlink does not have
the underline like previous
versions. Also, the new
screen opens in the
existing window instead
of a new one.
302 The new Logistics
591 Pipeline screen set has a
59 label that is not
translated.
submits in Internet Explorer.
Added the following
topics/sections in the External
Programming Interface Guide:
1. Section 3: External Service
Engine (ESE)
2. Service Time Engine
section under Appendix:
WSDLs
The issue was found with
migrated layouts that are based
on the old taskflowParameter
savedQueryGid. The issue was
resolved by loading the
masterDetail list. This does not
affect newer layouts after 19B.
Fixed the "View Party Screening
Result" hyperlink issue. Also, the
link is now fixed to open again in
a new window.
The translation name for the new
Logistics Pipeline screen set has
now been added.
302 The new Logistics
593 Pipeline finder results is
22 missing the check box.
302 Javax.elException when
603 editing, saving and
41 viewing a shipment group.
302 Finder results error when
637 selecting All to see more
19 than the 20 records
returned to the screen.
This happens when using
a user-defined driver
screen set, not when
using the public screen
set.
302 When the order release
689 has multiple line items,
53 the line items' ship unit
quantity is not the same
as the order release line
item quantity. The
quantity of the line items
are interchanged when
the ship unit is built.
302 There is no help for "Parse
934 Stylesheet Content". It
27 needs to be added.
Fixed the following:
1. Logistics Pipeline finder
now has a check box for
each result field.
2. The result is sorted by
ascending order of
shipment ETA.
3. The Shipment IDs in the
result field are now
clickable links.
There was an issue with
secondary charges. This is fixed.
You can now view and edit this
shipment group.
Fixed the finder result error
which happened to certain
drivers with a driver calendar.
When ship units are built from
multiple line items in the Order
Release page, the line's
packaged items and quantities
are now correct and will no
longer be interchanged
intermittently.
Added the help topic "Stylesheet
Profile Actions and SmartLinks"
and linked it to the UI.
303 On the Scheduled
001 Performance Collection
14 Finder, the tab heading
label (finder_tab.schedule)
is missing an English
translation.
303 When trying to insert an
122 actual shipment
20 transmission using
transaction codes "RC" on
parent and "U" on child
shipment for multi-leg
planned orders, you get an
exception.
303 Set a threshold on
125 process control data
78 query record counts.
303 The value for
144 "glog.ratingengine.ratewa
89 rexl.username" custom
property is not getting
updated.
303 In the CUSTOM Property
243 Set, I edited password
21 property
glog.ratingengine.ratewar
exl.Username. Changed
only the
description. Asterisks
were saved in the value
Added the missing translation.
When consolidating Multiple
Shipment using Shipment actual
with propagation, new SSU will
be added to the upstream and/or
downstream shipments that's
related to the order that SSU
belongs to.
Added a maximum record count
for data queries. The property
glog.dataquery.maxCount
controls how many matching
records a data query can
support. If the matched count
exceeds this maximum, the data
query is aborted and an
exception is written to the log.
The default is 100,000.
The CarrierConnectXL user name
and password changed values
are now getting reflected in the
application when modified via
property sets.
OTM now gives an error if only
edit the description on a
password property (because it's
trying to save asterisks as the
property value). You  have to set
the description AND the value.
 field to the wallet.
Asterisks shown on the
screen because of
masking should not be
saved to the wallet.
303 Re-drive routine could not
338 find the related second
94 leg shipments.
303 Configured event does not
339 honor the setting even
32 when there is a reason
condition included. When
the event is triggered the
selected Responsible
Party, Status, and Reason
fields should be marked
as required.
303 When a Shipment Group
409 Rule uses involved party
31 qualifier as a criterion,
shipments with the same
value for that qualifier are
not placed into shipment
groups during bulk plan.
Expected these shipments
to be placed into
shipment groups.
303 In user preferences,
409 selected Chinese as the
35 language and Taiwan as
the country. The Action
icons in the Results pages
are not displayed
The re-drive routine failed to link
shipments when shipment ship
units (SSU) shipunit GIDs were
null. Corrected the logic so that
ranges on SSUs are ignored and
only Order Release Line GIDs are
checked at SSU Line level.
This issue is now resolved and
the Responsible Party, Status,
and Reason fields are all marked
as required fields.
When shipment groups are
created during bulk plan,
shipments matching a shipment
group rule having same involved
party qualifier will now be placed
into a shipment group.
This issue is now fixed and the
tool bar icons display properly in
the Finder and Result pages
when the selected language is
Chinese and the country is
Taiwan.
 properly.

303 Update the help topic Modified content in help topic

440 SMC Carrier Connect for How to Set Up an SMC3 Rate.
56 cloud and on-premise as
the implementation is
different.

303 Barcode font upload fails This issue is now fixed. You can
558 in OTM BI Publisher. now upload custom fonts
37 successfully from the OTM BI
Publisher.

303 Order base changes made This is fixed. Order base changes
558 via integration trigger an made via integration will no
39 agent with agent action longer fail with a NPE and the
ORDER BASE - MOD - EDIT shipment ship units will no
SHIPMENT. The agent longer be removed.
action results in a null
pointer error (NPE) and
the shipment ship units
being removed from the
shipment.

303 Secure Action on the The Secure Action on the Action

611 Action Manager is giving
05 the error "a user already
exists with the name null.
this operation cannot
proceed.".
Manager now works properly.
The issue that caused the error
has been fixed.

303 Plan two orders onto one Unaffected shipment ship units
661 shipment. Using RC should no longer be deleted from
50 transaction code, modify the shipment in this scenario.
the first order by adding a
new order release line
(leaving the other line
untouched). Another ship
unit on the shipment gets
deleted. This happens
when the SHIP UNIT MIN
IMPACT parameter is set
 to true.

303 When entering multiple Fixed the problem. The value in

763 values in a numeric the last row is no longer saved to
84 custom column in the the previous rows.
result set of the Buy
Shipment UI, the value in
the last row is saved to
the previous rows.

303 The behavior of CSVUtil Documented new behavior for

769 (both within the web app database import/export of CLOB
15 and as a stand-alone fields in the Data Management
command-line utility) has Guide.
been changed with
regards to CLOB fields.
These changes should be
documented.

303 Create a custom screen Fixed the javascript error that

874 set. Add a field on the occurred when trying to make
41 results tab User Defined inline edits on  a field on Finder
Attribute Currency1 and Result page, using French.
made editable. Attach the
screen set to a custom
menu. Then access the
screen set with a user
preference language of
French. When you edit the
Currency1 field, you get
an error.

304 On the Collect Diagnostic Fixed to display missing drop

021 Logs screen, the down button on Collect
30 Configuration Collection Diagnostics Logs in Firefox.
and Performance
Collection fields have no
drop down button (i.e.
down arrow) in Firefox,
but should. It appears in
other browsers.
304 When entering multiple
025 values in a numeric
64 custom column on the
result set of a custom UI,
the system does not save
column results correctly
when the language is
French.
304 OBIEE properties in
110 CUSTOM property set are
88 not taking effect when
any value is updated.
304 Scalability scale out fails
122 while running scalability
21 diagnostics. You get an
error that the signed
servlet password failed.
304 In order configuration and
129 order base, change the
36 following labels:
 Net Weight to
Weight
 Net Volume to
Volume
304 Using an automation
244 agent with the action
Fixed the problem with inline
editing with number, currency
and other UOM columns when
entering numbers using French
format.
Fixed the custom security realm
to correctly load the CUSTOM
property set. Fixed password
properties used by the custom
security realm to properly handle
changes to password values in
the property set.
Fixed Signed Servlet to properly
propagate user-specified
password to the Signed Servlet
router.
Updated the "Net Weight" and
"Net Volume" labels to "Weight"
and "Volume" in the following
screens:
1. Order Configuration, Order
Base tab, Line section
2. Order Base Line Manager
Edit and View screens
3. Order Base Manager: Line
Item Edit screen
4. Release Lines action from
Order Base and Order Base
Line managers
The schedule appointment was
incorrectly scheduling the
15 "Schedule Appointment" appointment on a resource which
to schedule shipment did not have auto schedule
appointments to location option. This is fixed to schedule
resources. Have two appointments on resources that
location resources, one belong to resource types of auto
has "Auto Schedule" schedule enabled.
selected and one does
not. Expect appointments
to be scheduled to the
Auto Schedule resource
when this agent is
triggered. Instead the
appointment is being
scheduled to the location
resource that does not
have Auto Schedule
selected when both
resources have open slots
at this same time.

304 While doing a spot bid This was caused by a cursor leak
244 tender on a shipment, which has been fixed.
29 periodically
transmissions are not
sent out. When the
Service Provider list is
selected and confirmed,
no errors are visible but
the transmissions were
not always sent. In the
Exception log, an error is
seen.

304 Bulk plan or rating fails Addressed the issue. The

300 when there is no transit following explains the changes.
31 time returned from the  Data setup issues and
SMC Rateware XL while transit time response errors
using Carrier Connect XL. from Carrier Connect are
treated as infeasible
exceptions.
  Authentication and
authorization issues or
access issues, like not
being able to access a URL,
are treated as catastrophic
or fatal exceptions.
 When infeasible exceptions
are thrown, rating is
stopped for the particular
Rate Offering/Rate Record
(RO/RR) but will proceed
with the remaining RO/RR
combinations.
 When fatal exceptions are
thrown, the whole rating
process will stop. Since the
rating process stops with a
fatal exception, the calling
processes, like bulk plan,
will also stop because of
fatal exceptions.
 Fixed this issue to throw
fatal exceptions and in that
case the whole rating
process will stop and if it is
in a bulk plan, it will also
stop.

304 Via integration, if Creating a shipment cost

401 shipment cost reference reference does not require
73 creation is attempted sending the element
without sending in the ShipmentCostRef/SequenceNumb
mandatory element er anymore, even though
ShipmentCostRef/Sequenc mandatory per schema, as
eNumber, the following there's no easy way to know this
error is generated value up-front.
"java.lang.NullPointerExc
eption at
glog.ejb.shipment.db.Ship
 mentCostRefPK.hashCode
".
304 Creating and releasing an
401 order base line with a
74 packaged item and a
packaging unit which has
non-zero tare weight
causes incorrect weight
calculation on release.
304 Inappropriate exception
402 message is displayed
51 when bulk plan is
performed with
RatewareXL with carrier
connect.
304 When the parameter "Plan
521 with Carrier Commitment"
74 is set to true, the
retendering process is
selecting a service
provider and rate
offering/service time that
results in a time infeasible
shipment when the
service provider has an
alternative feasible
solution.
304 An error occurs when
521 sending a shipment actual
90 with the RC transaction
code to update the
shipment data (by
replacing the original ship
units with new ship units).
304 When attempting to send
581 an integration with one
Weight or volume on order base
line and order release line is not
net but gross, when packaging
unit is defined on the line. Now
both issues are fixed.
Exception messages are now
fixed for RateWareXL. When
NMFC Class is null, appropriate
error message will be displayed.
Added error messages for
initialization and connection
failures for RatewareXL.
Service providers with infeasible
rate service result are now
filtered out before assigning to
the shipment .
After modifying a planned order
using RemoveShipmentRefForRC,
a shipment modification whose
XML has a shipment ship unit
that doesn't include references
to the order's ship unit or line
will now succeed without error.
When deleting a ship unit using
agent action ORDER RELEASE -
42 ship unit removed for an
order release planned on
shipment (direct) having
two ship units, an error
occurs. This occurs when
using the agent action
ORDER RELEASE - MOD -
PROPAGATE CHANGES.
304 When using a custom
677 "Rapid Order Release"
54 screen that has the
"Splittable" check box
selected, the resulting
order does not honor the
value of the check box.
Instead, whether the
order will be splittable or
not depends on the value
of the property
glog.webserver.order.IsSp
littableDefault.
304 In the help topic Auto
744 Assignment Rule, the first
70 two paragraphs are
almost word for word
duplicates.
304 Update the Data
786 Management Guide with
84 information on
export/importing CSV
files.
304 Recover Data Query
887 lifetime memory on
80 custom event completion.
MOD - PROPAGATE CHANGES
and parameter SYNC WITH
ORDER = true, you will no longer
get a foreign key error.
In a custom "Rapid Order
Release" screen that has the
"Splittable" check box displayed,
the resulting order will now have
the value from the screen.
The value of the property
glog.webserver.order.IsSplittable
Default will be used only when
the "Splittable" check box is not
available on the screen.
The same logic applies to the
"Splittable" check box displayed
under the "Enter Items to be
Shipped" grid of the order
release line.
The help topic Auto Assignment
Rule had redundant text. Deleted
the duplicate text.
Documented how to install SSL
certificates for authenticating
external systems over HTTPS
and how to verify the
installations with the diagnostic
configuration collector.
Restructured Data Query memory
usage so that the memory used
by one custom event topic is
 released when all work
associated with that topic is
complete.
This memory optimization is
applied to all Data Query topics
by default. If, for some reason,
we need to revert to the old
memory use (e.g. to enable
Explanation), the optimization is
tied to an Optional Feature:
OPTIMIZE DATA QUERY
FOOTPRINT. If Opted Out, the
optimization is suppressed.
Note that this feature is "opt in"
both for new and existing
customers.

304 If you change the TiHi The cache issue has been fixed
905 parameters on a and the correct TiHi values are
65 packaged item, OTM does now used.
not clear the cache.
Therefore, if you generate
ship units, OTM uses the
old TiHi values.

305 The Split Order Release This issue is now fixed. The ship
004 action results in a unit line item count will be split
58 difference of one between in proportion to the ship unit
the ship unit count count split.
entered and the total For example, if a ship unit count
package count which is is 208, the ship unit line with
calculated based on order item count is 208, and split off
configuration. amount is 30. Then the multiplier
is calculated as 208/30 = 0.144
and Split Item Package Count is
calculated as 208*0.144 =
29.952. This amount will be
rounded to 30 now.
So the line item will be split as
178 and 30 and the ship unit
 count will be split as 178 and 30.

305 Added a global Accessorials added on the

004 accessorial code (without shipment are rated when
66 selecting the "Always Recalculate Shipment Cost
Apply" check box) to a action is performed.
shipment. Ran the
Recalculate Shipment
Cost action. The
accessorial is not
evaluated. As a result, the
shipment cost is not
updated.

305 Packaged item count on a Packaged item count on split

009 ship unit line is incorrect lines will be correctly calculated
81 when the line is split in the case where packaging unit
across two ship units. ID is defined on a line but no
packaging unit count is defined.

305 Duplicate integration data Adjusted data queue startup to

070 queue threads. ensure that:
54 1. the
glog.dataqueue.blockTrans
port property does not
trigger a recreation of data
queue threads, and
2. recreation of data queue
threads, interrupts and
removes older threads -
even if they are waiting to
startup.

305 Bulk plan performance The rating of shipments happens

110 issue. in parallel threads. The rate
12 record/rate offering combinations
are divided into batches and
each batch can be processed by
more than one thread (if the
number of batches are more than
 1).
The number of batches can be
specified by the property
glog.workflow.task.desiredB
atchSize.Rating
The number of threads can be
specified by the property
glog.workflow.queueThreads
.ratingTasks
When the value of the property
above is QUEUE, the number of
batches will be equal to number
of threads.
The problem here is that, the
required data for rating (such as
accessorial codes, allocation
records, special services, etc.)
are being loaded again and again
for every rate record/rate offering
combination, which is increasing
the number of database hits and
hence creating the performance
issue.
Reduced the loading of required
data for rating for each batch
created for rating. So by default,
since there will be only one
batch now, this data will be
loaded only once.
When the number of batches
increases, for each batch the
querying of the data will occur
there by a little increase in the
number of database calls.

305 Issue with calculated Allow user to set properties to

229 fields drop down display. remove some search operations
67 Finders that include for Text Field dropdown list and
calculated fields like pick list in certain finder pages.
Driver are displaying drop This setting does NOT work for
down values incorrectly. "derived" fields, whose operators
You will see on the have already been restricted. For
Teamed Driver field that a example, for the Driver finder >
blank value is shown then Calculated tab, the field "Next
Primary Driver, Secondary Assignment Source Location ID"
Driver and Non-Team only has "Same As" option. So
Driver. such field will NOT be affected
by the properties settings. The
properties could be for the whole
query or for specific finder set,
and values are separated by ",".
The property format is:
glog.webserver.finder.invalidOpe
rators.query_name.<query_name>
=
FORBIDDEN_OPERTOR1,FORBID
DEN_OPERTOR2. This property
means all finder pages with the
query_name will remove
FORBIDDEN_OPERTOR1 and
FORBIDDEN_OPERTOR2 from
Text Field dropdown-list and Pick
List dropdown-list.
glog.webserver.finder.invalidOpe
rators.finder_set_gid.<finder_set_
gid> = FORBIDDEN_OPERTOR3
this property means the finder
page with the finder_set_gid will
remove FORBIDDEN_OPERTOR1
from Text Field dropdown-list
and Pick List dropdown-list.
The properties of query_name
and finder_set_gid can have
overlap, that does not matter.
For example:
glog.webserver.finder.invalidOpe
rators.query_name.glog.server.qu

305 There should be a way to
448 know if a system is Gen2
28 or Oracle Public Cloud.
305 This property needs to be
587 documented in help:
92 glog.properties.log.email.r
ecipients.
305 The following parameter
640 is set to a specific (or list
09 of) service providers:
DEFAULT SERVICE
PROVIDER FOR FLEET
ASSIGNMENT.
An order release is
planned onto a shipment
and is assigned to the
cheapest service provider
(which is not included in
the parameter list). This
behavior is expected. Run
the shipment action
"Repack S Ship Unit" on
ery.shipment.B uyShipmentQuery
= contains, same
glog.webserver.finder.invalidOpe
rators.finder_set_gid.BUY_SHIPM
ENT = notoneof.
Updated the Cloud Admin Guide
in the Avoid Receiving
Notifications as Spam section to
explain how to determine if the
system is Gen2 or Oracle Public
Cloud.
Updated
properties/glog/properties.proper
ties.htm . If you want to get
email notifications whenever a
property is changed, set this
property to contain the desired
email address. If you want to
notify multiple emails addresses,
define this property multiple
times. Do not place more than
one email address in a single
property definition.
For this action, and others that
call the ShipmentCostCalculator,
if the service provider on a
shipment is not a fleet provider
and the shipment does not have
a driver on it, the parameter
DEFAULT SERVICE PROVIDER
FOR FLEET ASSIGNMENT will be
ignored.
 this shipment. Instead of
selecting the cheapest
service provider, OTM
updates the service
provider based on the set
in the parameter list.

305 Created a Rapid Order This is fixed. Now when

640 Release manager layout selecting an NMFC_CODE as
22 with a fixed list of qualifier, the NMFC Class Codes
NMFC_CLASS for Flexible Finder will be correctly used for
Commodity Qualifier. the commodity code.
Created an order by ship
unit. A unit under the
Enter Units to be Shipped
section is defined with a
default value. The unit
(not the order) is saved.
Edit the unit and select
the view icon next to the
Commodity Code.
You get an error as OTM
redirects to the
Commodity screen.

305 Performance issue Fixed a potential infinite loop

694 observed with OTM. problem. Also, added extra
37 logging, with Log ID Finder, for
troubleshooting the looping issue
if it occurs again.
 

Oracle Transportation Operational Planning

 

Issue Summary Resolution

Num
ber
 
Oracle Transportation Operational Planning
2713 After merging This issue fixed. The cost is now
2482 shipments, the removed from the merged shipment.
costs should be
removed from
the merged
shipment. After
the merge, there
is no order on
the shipment,
but the rate
information is
still there.

2942 When an order The error happens when the last

1023 release is container heuristic is invoked and OTM is
planned using planning one order release with multiple
the following ship units. The issue is now fixed.
scenario, an
exception is
raised during
bulk planning:
 3D scoring
in use
 USE
PRIORITY
IN CONOPT
SORTING =
true
 Order
Releases
requiring
splitting
 Favor
Splitting in
ConOpt set

2958 User-defined Modified a note in the help topic Load

8402 patterns are not Configuration 3D Pattern to clarify this.
considered in The note now reads as follows: "Note:
container The logic configuration container
optimization optimization parameter USE PATTERNS
unless the split IN 3D must be true, and the SPLIT
option is set to OPTION must be set to be 1.Favor
"1. Favor Splitting, for load configuration 3D
Splitting". As per patterns to be used. The dimensions are
the current saved in the User-defined Pattern table
documentation, LOAD_CNFG_3D_PATTERN_D.".
only the two
following
parameters
were required to
be set USE
PATTERNS IN
3D = TRUE and
USE USER
PATTERNS IN
3D = TRUE. Help
should be
updated.

2959 Multicontainer OTM was not considering any item-to-

8313 MIP is putting an resource incompatibility while using the
item in an Multicontainer MIP packing algorithm.
incompatible Added new constraints in the
compartment Multicontainer MIP formulation to
because Conopt consider various incompatibilities that
Multicontainer exist between the items and equipment
MIP formulation (also the compartments in them).
is currently not
considering
item-to-resource
compatibility.

2960 Optimize on There were not sufficient logs to clearly

6610 network leg show how the set of valid equipment was
does not allow determined for building shipment for an
for order to plan. order bundle on a leg. Added new logs
under the "AssignEquipment" log ID to
 show how various mode/equipment
related incompatibilities are being
considered (from the order, leg,
commodities, locations etc.) to
determined the set of valid equipment.

2963 The Previously, if you changed details on a

5970 TRepSchedByLo ground service, those details were not
cMonth app-tier updated on the shipments when re-
cache is not planned the orders using the ground
updated when a service. This has been fixed.
ground service
is edited. As a
result, the
newly-saved
data is not used
until somebody
clears the
cache.

2971 When network When the shortest path algorithm was

4234 routing bulk plan something other than Enumeration, OTM
is run with failed to make the right routing decision.
shortest path The issue is fixed. Note that the shortest
and dynamic path domination logic should be disabled
clustering on, for two routes whose associated orders
OTM produces a are different.
poor routing
decision.

2974 An exclusive-use The issue was that split ship units

3250 order was split inherited the "exclusive-use" setting
during the build from the parent ship unit. This issue has
direct shipment been fixed. OTM correctly builds a multi-
process (to fit stop shipment now.
into small
equipment
compartment).
However, in
later process
like multi-stop,
 OTM fails to re-
combine those
split exclusive-
use ship units to
fit into a larger
equipment
compartment.
This results in
the creation of
more shipments.

2974 When a service This is fixed.

9810 provider has
multiple rate
offerings and the
rate offering is
not specified by
service provider
in allocation
commitment,
the cheapest
cost feasible
rate is not
always
assigned.

2975 The Move Order The issue occurred because this action
0023 Movement to was incorrectly using the combined
Shipment action weight of all orders on the shipment to
is failing to check if the equipment group capacity
move an order was exceeded. However, this incorrect
movement (that check did not account for the possibility
was initially that not all orders are on the shipment at
planned and the same time. This logic has been fixed
then unassigned so that the logic checks the maximum
from the weight on the shipment at any given time
shipment) back against the equipment group capacity.
to the same So for the business case where a large
shipment. order movement is moved to the
shipment but would be picked up after
 the original orders on the shipment are
delivered, this action will succeed even
if the combined weight of all the orders
exceeds the equipment group capacity
(because they would not be on the
shipment at the same time).
This issue and the fix also apply to
volume as well as weight.
This fix also addresses a related issue
where the order release action Move to
Existing Shipment would fail if
equipment capacity is exceeded, even if
you specify that Equipment Capacity is
to be ignored in the Criteria to be
Ignored. With this fix, this action will
succeed when you specify that
Equipment Capacity is to be ignored in
the Criteria to be Ignored, and
equipment capacity is exceeded.

2977 Wrong transit The calculation for determining the time

8428 duration on between the first stop departure and the
second stop second stop arrival was fixed for By Day
when using day rate services (Day Duration, Distance
duration and Duration, and External Days). This allows
activity on stop the proper population of the transit time
1. associated with the second stop of the
shipment.

2978 When the Property

9950 scoring and glog.optimization.packingparameters.ski
priority logic are pMultiPassScoringPriorityAlg has been
both enabled, converted to a parameter called USE
OTM is LAST CONTAINER PRIORITY HEURISTIC
performing a and added to the Container Optimization
"last container" Logic Configuration, in the CONTAINER
heuristic when OPTIMIZATION 3D SCORING section.
packing items. This parameter impacts packing when
However, the scoring and priority are both enabled.
traditional When this parameter is false (the
 behavior of default), OTM performs a "last container"
packing items algorithm, and only makes sure the last
with higher equipment is just packing the relatively
priority first may low priority algorithm. When set to true,
be applicable to OTM packs items priority group by
some scenarios. priority group.
Therefore, a
parameter
should be added
to control these
behaviors.

2980 You see double Resolved the double counting issue of

8928 counting of activity time when using a By Day rate
activity time service (day duration, distance duration,
when using a By external transit days).
Day rate service
(day duration,
distance
duration,
external transit
days).

2986 While assigning Fixed to now properly create order

8456 the driver to a movements when an order release is
shipment, the manually assigned to a schedule
following error is instance shipment. This allows the
displayed: subsequent driver assignment for the
"Verification shipment to succeed without an order
error for movement verification error.
<OrderMovemen
t> of shipment
<X>: expected
<exists>, but
was <does not
exist>." where X
is a Shipment
Number.

2989 If you run rate Fixed the cache issue that occurred
1025 inquiry once, the between sub-domains.
 date is retrieved
correctly. If you
run it a second
time from a
different sub-
domain,
incorrect results
are returned as
OTM only
checks from the
cache.

2992 Tracking events Fixed so now Canadian rail markers

7471 with shipments appear on the map.
and rail do not
show Canadian
positions on the
map.

2992 When the role is The order of shipments stops are now
7559 Rail Station, a being sent in the correct order.
shipment with a Previously, under certain conditions,
through route OTM might have sent the shipment stops
will not render. in an incorrect order to ALK.

2995 Issue with group Made changes to group packing to sort

0254 packing. the item groups from largest to smallest
Currently with (when no priority) only once and pack in
group packing, that sequence throughout.
every time OTM
starts to pack a
new equipment,
the remaining
items are sorted
largest to
smallest (when
there's no
priority). In this
case, certain
items can be
split more than
 others. At least
for the purpose
of group
packing, there
does not seem
to be any benefit
in sorting the
remaining items
every single
time a new
equipment is
packed.

2995 Network routing There were two issues that have existed
6836 logic with in Network Routing logic for a while.
expected transit 1. Order Releases with Date Emphasis
time is not PAST and late pickup or delivery
working as dates would fail to plan with
expected. There Network Routing if they were
is a wait time further in the past than the ORDER
issue. WINDOW TIME SPAN setting. This
is fixed. These orders can now plan
in the past with Network Routing.
2. When a leg has "Calculate Service
Time" unchecked, and has an
Expected Service Time, this
Expected Service Time was being
ignored in the creation of the order
movement time windows, so that
the start date of the shipment on
the next leg might be ignoring this
Expected Service Time. This is
fixed. The Expected Service Time
will now be used in order
movement time window and
shipment times when the Calculate
Service Time is unchecked.

2996 The "Relay Added a check to see if the control "Get

6576 Shipment Driver Home" is defined or not in the
 Breakdown" Fleet Assign Ignore criteria screen. This
action screen resolves the issue and brings up the
does not fully scroll bar in that "Relay Shipment
load. You have Breakdown" action page.
to maximize the
window to force
the window to
fully load.

3000 Maximum OTM now prevents the loading of

1305 Cursors errors combination equipment of circular
due to cyclical definitions.
combination
equipment group
data. OTM
should handle
this potential
data setup
issue.

3002 Experiencing The issue is a memory leak in bulk plans

2643 daily that use Network Routing (with planning
occurrences of parameter ROUTING METHOD as
the error Network Routing). This happens when
"tjava.lang.OutO network rating is multi-threaded, which
fMemoryError: is usually the case. The leaked memory
GC overhead persists after the end of the bulk plan, so
limit exceeded" that the wasted memory builds up over
and several the course of multiple bulk plans. The
stuck threads. symptom is that memory fills up with
TOrderRelease and TOrderReleaseLine
objects. This leak has now been fixed.

3011 Multicontainer Conopt Multicontainer MIP algorithm did

5650 MIP algorithm not allow splitting of SSUs in
isn't handling compartments inside the multistop logic.
count split This fix enables the Multicontainer MIP
correctly in algorithm to allow splitting SSUs by
multi-stop. count in the compartments inside the
multistop logic.
Note that splitting bulk SSUs is still not
 allowed in multistop when Multicontainer
MIP algorithm is used.

3017 Orders fail to The NPE happened when the

3457 plan with a null consolidation algorithm was set to
pointer Conopt Merge. The issue is fixed and
exception (NPE) orders now plan as expected.
when the setting
is Conopt Merge
for multi-stop
algorithm in
Multistop Logic
Configuration.

3017 Sometimes you This happened if a schedule based rate

9793 get a null service existed. It's been fixed. The
pointer exception no longer occurs.
exception when
bulk planning.

3018 Bulk plan Conopt Merge multistop consolidation

8867 partially algorithm was not working correctly with
combines half legacy non-consolidation itineraries. This
an order to form fix addressed these issues only for
multi-stop single-leg non-consolidation itineraries.
shipment. The However, for legacy planning (i.e., when
other half is Network Routing is not used), Conopt
missing when Merge will still not work for multi-leg
conopt merge itineraries. In that case, OTM will print
uses non-pool the following in the Planning logs:
cross-dock "Conopt Merge based shipment
itinerary. This is consolidation is not allowed for multi-leg
the cost based legacy planning.". For multi-leg planning,
logic with you must use Conopt Merge with
itinerary that Network Routing based planning.
has the check
box Multi-stop
itinerary
unchecked,
while leg auto
consolidation
 type is "Multi-
stop into One
Equipment".

3024 Rate record is Earlier, when the "Hazardous Rate Type"

0884 specified with on the rate record was set to "Hazardous
"Hazardous Rate Materials Only", the Rate Geo Hazardous
Type" set to Rule (rgHazRule) check was passing if
"Hazardous the shipment is hazardous, i.e. if at least
Materials Only". one item in the shipment is hazardous.
This was incorrect behavior since this
rule should pass in this case if the
shipment is entirely hazardous (i.e. it
contains hazardous materials only). This
issue has now been fixed. Similar issue
has also been fixed for Rate Offering
Hazardous Rule (roHazRule) check. Now,
when the rate record is specified with
"Hazardous Rate Type = Hazardous
Materials Only", the Rate Geo Hazardous
Rule check will fail if the shipment is not
entirely hazardous. Similarly, when the
rate offering is specified with "Hazardous
Rate Type" set to "Hazardous Materials
Only", the Rate Offering Hazardous Rule
check will fail if the shipment is not
entirely hazardous.

3024 Rate record When a rate record is constrained (with a

0932 specified with a flex commodity profile) to be compatible
commodity is with a particular commodity, say
not honored. COMMODITY-1, it is supposed to be used
to rate only COMMODITY-1 items.
Therefore this rate cannot be used for a
shipment which has COMMODITY-1 items
as well as some other items with no
classified commodity. This expected
behavior was inconsistent due to a code
issue in the Rate Geo Commodity Rule
(rgcRule) check. This issue has now
 been fixed.

3024 If you have two The Order_Base_Gid on S_Ship_Unit_Line

0965 identical order will be set so the correct order base is
bases, each with reflected.
one line, select
both and run
Release Total
Amount to
create one order
release. Then,
plan the order
release to
create a
shipment. When
you look at the 2
shipment ship
units (SSUs) on
the shipment,
you see that
they both show
the same value
for the Order
Base ID even
though each
SSU came from
a different order
base. The same
problem is seen
when viewing
the shipment
ship unit lines.

3024 Incorrect entry Due to an issue with determining the

6171 in carrier valid work period ranges, an incorrect
capacity work entry was sometimes getting introduced
period causes a in the carrier capacity work period
planning failure. ranges, which was then leading to failure
of the shipment in the drive logic. This
issue has now been fixed.
3026 Seeing an issue There was a cache issue with
3667 with incorrect "commodityIncompatibilityCache". This
commodity would occur if commodity
incompatibility. incompatibilities were in one domain and
the commodity incompatibilities in
another domain were not cached and
retrieved correctly.
Changed this cache back to being
domain based in the same
ConcurrentHashMap setup.

3026 The Shipment Added index for CM_NAME column.

4811 table has no
index on column
CM_NAME,
which is an
issue when
handling
shipment table
has a lot of
rows.

3027 Equipment This happened randomly for Cost Based

6172 reference unit Routing, when there were two ship units
(ERU) is on an order release, one with ERU/THU
exceeded when specification, and one without it. When
Splittable is gathering reference units across all ship
false. Created units on an order release, if the first ship
an order release unit seen by the code didn't have any
with two ERU specification, OTM was ignoring
shipments. One ERU specifications on subsequent ship
has an ERU/THU units for that order release.
and the other Resolved so now while planning, OTM
does not (no will look at ERUs across all ship units of
ERU/THU). The an order.
ERU value on
the ship unit
with ERU
exceeds the
limit of the
 equipment group
ERU. When the
order release is
planned onto a
shipment using
the equipment
group, it is
successfully
planned (even
though it
exceeds the
ERU).

3028 OTM fails to plan This issue is now resolved. A code

8065 a shipment change was made to properly evaluate
when you set location capacity constraints during
the CHECK service time evaluation for the Day
LOCATION Duration rate service type as well as
CAPACITY other "by day" rate service types (for
parameter to example, Distance Duration and External
TRUE and Transit Days).
Master Rate
Offering has a
Day Duration
rate service.
OTM is able to
plan a shipment
if the parameter
is set to FALSE.

3031 The log file Modified the cost to the same currency.
2247 shows that Now the consolidated and direct
different shipment costs are using the same
currencies were currency in the log file.
used in
comparison
between direct
and
consolidated
shipment cost to
 find the best
cost.
This is
confusing. It
would be better
to show the
costs in the
same currency
so that the
exchange rate
fluctuation won't
cause confusion.

3031 Getting an The error has been fixed. No need to

6101 exception while throw an exception since the results
running "Apply screen will convey that no template was
Customer applied since it was not defined.
template" on an
order release.

3031 Need check for Validations are added to check the

8064 a location role following:
when defining a 1. The source location role is defined
network routing on the source location.
leg.
2. The destination location role is
When adding a
defined on the destination location.
network routing
leg and
accidently try to
use a location
role for the
Source Location
ID that the
location does
not contain, you
get a SQL error
that goes away
when you edit
the location and
add the location
 role used onto
the network
routing leg.
Same applies to
the destination
location ID.

3032 Excessive Fixed to improve processing efficiency

9002 looping with when a shipment that utilizes period type
incorrect setting HOS rules encounters long wait time at a
for the last reset shipment stop.
time. It occurs
when wait time
at a stop is
greater than the
Min Reset
Duration
associated with
a period type
HOS rule.

3033 The Move Order The issue was that the action "Move
3936 Movement to Order Movement to Shipment" would fail
Shipment action if the resulting cost of the shipment
is failing to would be greater than the original cost of
move an order the shipment plus what the new order
movement (that movement would cost if it were sent by
was initially itself. This was due to a multi-stop check
planned and that ensures that you don't consolidate
then unassigned shipments that would be cheaper not to
from the consolidate.
shipment) back However, in the case of this action, you
to the same already decided to add the order
shipment when movement to the shipment, so this check
rates are based should be disabled. Also, the "Move
on "Shipment Order Release to Shipment" action
Handling Time". ignores this check.
This fix will disable this check, so that
the order movement can be added to the
shipment no matter the cost difference.
 Because the "Move Order Release to
Shipment" action also ignores carrier
capacity (because the shipment already
exists), for consistency this fix will
ignore carrier capacity for the "Move
Order Movement" action too. (Carrier
capacity can be not ignored if the
existing property is set to false:
"glog.business.order.ignoreCarrierCapaci
tyWhenMoveOrdersToShipment".)

3033 Memory leak Fixed a memory leak in the "Show

3937 found in Network Routing Options" action (as well
Network as a far more minor memory leak in
Routing. "Show Network Routing Options -
Ocean").

3035 When creating a The issue was that a special service with
5841 multi-leg ocean a "Default For Source/Dest" setting of "D"
order, the first (for Destination) was being treated as a
leg is failing to constraint for rate selection for a
be planned due shipment that was not going to the order
to the inbound destination (for example, it was going to
special service a crossdock).
on the order. This has been fixed for all settings (i.e.,
Without a "S" for Source, "D" for Destination, and
ground carrier "B" for both Source and Destination).
selected to
Note that these special service "Default
handle the
For Source/Dest" settings can be
inbound special
overridden at the order release level
service, there
(Order Release "Other Attributes" tab
are no rate
"Source/Destination Location" field).
records/offerings
. The first leg is
not planned until
a special service
is added to the
rate record. The
inbound special
service should
only apply to the
 last leg, so this
shouldn't
prevent the first
leg from
planning.

3037 You get an error Fixed this issue. Now the "Show Routing
6385 using the action Options" action can be used to create
"Show Routing the shipments successfully.
Options" when
these
parameters are
turned on:
 PRE-SPLIT
LARGE
ORDER
RELEASES
IN
CONTAINE
R OPT =
TRUE
 USE 3D
BASED
LOAD
CONFIGUR
ATION =
TRUE
 OPTIMIZE
COST =
TRUE

3039 The Assign Fixed to honor "get the driver home"

5620 Driver action is parameter in the Assign Driver to Work
not honored. Assignment action. This is fixed so now
Trying to the driver starts at home and returns
configure the home at the end of the work assignment.
driver set up on
daily basis
which returns
 home every day
after 9 hours of
drive time and
12 hours of work
time. Driver is
not back to
home on
shipments. (No
NFR stops were
found back to
home.)

3042 Running the Fixed both issues. The informational cost

4453 action will no longer be duplicated and the
"Recalculate "Record Not Found" error no longer
Shipment Cost" occurs.
on a shipment
that has an
informational
cost sometimes
causes that cost
to be duplicated.
Another issue is
that running the
action "Create
Spot Rate" fails
with a "Record
Not Found" error
if the shipment
already had an
informational
cost of type
Original.

3045 Unable to save a The Saved Query button on the Ask

2206 query in Oracle screens now works correctly.
container
optimization.

3045 The Show Fixed to prevent routing options with no

3297 Network Routing transit time from being returned in the
 Options (SNRO) - "Show Network Routing Options" action.
Refine Options
is currently
returning an
option that has
no transit time
(service time is
not found for
lane). You get a
null pointer error
if this option is
selected.

3053 Allow release Fixed so now OTM will not re-assign

2478 schedule equipment if detachable ground schedule
instance for is empty.
ground schedule
with no orders.

3053 There are The consolidation step in multi-leg

2617 incorrect planning used to leave large time gaps
planning dates between shipments with parameter
because of PLAN ORDERS WITH DATE EMPHASIS
redrive. PAST set to true and a primary leg after
Plan two order the first leg. This change removes these
releases with time gaps for certain scenarios. In this
two different case, the order only has a delivery time
destinations window without pickup time window. For
using the Bulk example, if you set the last leg as
Plan Buy action. primary leg, the consolidation process
A multi-leg will re-drive the leg at primary leg -1,
itinerary is primary leg -2, etc. until first leg in HOLD
configured to AS LATE AS POSSIBLE = true to
create one eliminate the time gaps between
shipment for different legs.
each leg (two
Note: HOLD AS LATE AS POSSIBLE refers
pieces of
to internal logic not the planning
equipment are
parameter.
consolidated on
each of them). In
 the last leg,
don't
consolidate the
equipment, but
create one
shipment for
each destination
(no auto-
consolidation).
The shipments
are created
correctly but the
dates for the
first 5 legs are
incorrect. There
should not be
gaps in dates
after planning.
 

Oracle Logistics Network Modeling

 

Issue Summary Resolution

Number
 
Oracle Logistics Network Modeling
2981986 When running the Scenario Increased the column
4 Bulk Plan action, a size of the order_id
"Java.sql.batchupdateexceptio column (found in the
n: ora-12899: value too large lnm_order_state back-
for column" error is seen. end table) to 101.
Scenario bulk plan will
now work as expected.

2991589 Performance issue with Reduced the number of

6 Scenario Bulk Plan. queries to the rate
offering table in a
Scenario Bulk Plan.
 This should improve the
Scenario Bulk Plan
runtime.

3024499 If you enter the operand value Updated code to show

6 for data rule instance the error "Value is not a
parameter VOLUME as ".", the valid number" when "."
UI should generate an error. value is entered.

3025862 The value for Number of Fixed the Number of

1 Periods in Modeling Bulk Plan
Specification screen should be
an integer.
Periods field in
Modeling Bulk Plan
Specification screen.
You can enter only a
positive integer in that
field.

3032757 The values on data rule The numeric data types

2 instance should be a positive supported as part of
value. data rules for all the
tables will allow you to
enter only positive
values now for all the
supported operands like
SET, INCREASE,
DECREASE, INCREASE
BY DAYS, and
DECREASE BY DAYS.
 

Oracle Forwarding and Brokerage Operations

 

Issue Summary Resolution

Number
 
Oracle Forwarding and Brokerage Operations
29878381 Open cursor detected in Fixed the open
shipmentbean related to jobs. cursor issue.
 

Oracle Transportation Sourcing (includes Rate Maintenance)

 

Issue Summary Resolution

Number
 
Oracle Transportation Sourcing (includes Rate Maintenance)
296233 During the download An additional column
94 of rates, the rate RATE_GEO_COST.DESCRIPTION
costs are has been added to the sort by
downloaded in columns in addition to the
irregular sequence following sort by columns:
impacting the 1. CHARGE_TYPE
completion of the
rate maintenance 2. CHARGE_MULTIPLIER
template. 3. CHARGE_MULTIPLIER2
4. OPER1_GID
5. LEFT_OPERAND1
6. LOW_VALUE1
7. HIGH_VALUE1
8. AND_OR1
9. OPER2_GID
10. LEFT_OPERAND2
11. LOW_VALUE2
12. HIGH_VALUE2
13. AND_OR2
14. OPER3_GID
15. LEFT_OPERAND3
16. LOW_VALUE3
17. HIGH_VALUE3
 18. AND_OR3
19. OPER4_GID
20. LEFT_OPERAND4
21. LOW_VALUE4
22. HIGH_VALUE4
23. EFFECTIVE_DATE
24. EXPIRATION_DATE
25. CALENDAR_GID
26. CALENDAR_ACTIVITY_
GID
If all the above existing sort by
columns carry the same value,
then the downloading
rate_geo_costs will be sorted by
description.

298044 We are shipping Replaced the Parameter

56 sourcing reports with operators with bind variables in
use_param_operators all Sourcing BI Publisher reports.
as Y. This is not With this change, the
correct and should procurement_solution_by_lane
be changed to have report works as follows: You can
use_params_as_bind enter a Solution ID to see all the
as Y and lane information related to that
use_param_operators scenario. You can enter single
as N. We do not want lane ID along with scenario ID for
to support parameter information for that particular
operators. lane.

298216 If you try to upload You can now upload a

82 rates in sourcing that spreadsheet with decimals in
have conditions with conditions successfully. The
decimal values (for number of decimals allowed for
example, if Weight > the values in the conditions is
21.8 TONS then now confined to 3 and you can
Apply Cost of 1000e), upload up to 3 decimal values in
 the rate will not be the Cost Parameters tab for all
uploaded. the low_value and high_value
columns.

298635 An exception is This has been resolved.

37 generated when
mark for purge job on
P_BIDS runs.

304501 When adding a Now when adding a pseudo

31 pseudo status field to status field to the results page of
the results page of a a user-defined Bid screen set, the
user-defined Bid list of status types are getting
screen set, the list of populated.
status types are not
getting populated.
 

Oracle Transportation Intelligence

 

Issue Summary Resolution

Numb
er
 
Oracle Transportation Intelligence
25930 Accessorial Code Description ACCESSORIAL_DESC
673 dimension from Shipment Order column mapping was
Release Line analysis shows missing in
null value for codes that contain F_SHIPMENT_ORD_REL_
a description defined by the COST_D table. This is
user. fixed and not the
Accessorial Code
Description dimension
display results as
expected.

29558 During ETL dataload process, Order releases planned

553 insertion into the on shipments with
 HDOWNER.F_SHIPMENT_ORD_R multiple costs will load
EL_COST_D table fails with the into hdowner as
error: "ODI-15064: The primary expected.
key
PK_F_SHIPMENT_ORD_REL_COS
T_D is not unique.". This is seen
on shipments and order releases
with allocated costs.

29832 Accepted Tender percentage Records which are

331 fact is not calculated correctly modified tenders are
in Tender Performance Reports also counted in total
when shipment contains tender count which led
modified and accepted tenders. to wrong results. This
If a tender is accepted and issue is now fixed.
loaded to HD, it has acceptance
code of A. Later if this tender is
modified and another tender is
the final accepted record, there
will be 2 accepted records in TI.

29837 There are two KPIs with Carrier Tender

900 "actual" mapped to the same Performance related
field, but different "target" KPIs now works as
mapping. However, one of the expected.
KPI always displays 0 for the
actual when the other has the
right value.

29837 Make some glog.ods. properties The glog.ods properties

959 reserved in the cloud. are now reserved in the
cloud.

29850 User-defined dashboards must You can now specify

500 be in a folder which is the dashboard path in
overwritten during an upgrade. OTM/GTM via the
This causes issues for following user
customers. preferences:
 GTI Dashboard
Path with a default
value of

29949 TI analysis using Rate Analysis
417 > Rate Record Dimensions >
Rate Quality GID does not
display any information.
30029 During an incremental ETL, the
236 procedure for the VPD tables
drops all the records in
HDOWNER and inserts the new
data. Due to this approach when
there is a timing conflict
between an active ETL run
(when the VPD tables are
dropped) and a
migration/upgrade process
(which stops the ODI service
during execution), the post
migration step on the HDOWNER
(seeded data) fails.
30238 When triggering the ETL process
202 for Transportation Intelligence,
the ETL process fails with an
exception.
30244 Accessorial Cost and
024 Accessorial Cost Details
dimensions from Shipment Line
and Shipment Order Release
Line analysis when used in
reports, take a lot of time to
load. This impacts performance
when data in the report contains
/shared/GTI
Reports/_Portal/
 TI Dashboard Path
with a default
value of
/shared/FTI
Reports/_Portal/
Rate quality information
can now be used in TI
analysis.
The approach for
loading VPD related
tables has been
modified from delete/re-
insert to insert/update
with delete.
You can now trigger an
ETL with no errors if a
previous ETL is in error
state.
The sub query to fetch
accessorial cost from
Shipment Line and
Shipment Order Release
Line analysis is
changed in all layers of
RPD which improves
performance while
 many rows.
30344 You incorrectly receive a
944 notification that custom reports
exist outside the custom folder
structure for your Cloud
environments.
30406 If you create an analysis using
390 the following fields from
Shipment Line Facts > Cost
Base Shipment Line Dimensions
folder, the Cost Type
Description column is always
blank in reports:
 FTI Shipment GID
 Cost Type
 Cost Type Description
30440 Add the TENDER_STATUS
176 column to TI.
30500 Add a Test Table Name to test
974 connection after a restart when
enabling Test Connections On
Reserve.
30527 If any update is made to OTM
575 shipment events, the ETL is run
but updates are not seen in
Tracking Event Analysis reports.
creating reports.
Changed the catalog
compare script to
resolve this.
Mapping for
COST_TYPE_DESCRIPTI
ON has been added to
F_SHIPMENT_ORD_REL_
COST_D table. Now, the
Cost Type Description
dimension will retrieve
results as expected.
Added the
TENDER_STATUS
column under the
Tender Dimensions in
the Tender Performance
Analysis folder. This
allows you to retrieve
more information for the
tender. The column has
been added in all layers
of the RPD.
Added the test table
property to WL data
sources.
As Mviews of
F_SHIPMENT_EVENT_FA
CT contain old data and
F_SHIPMENT_EVENT_FA
 Due to missing aggregate tables
for F_SHIPMENT_EVENT, data
updates are not propagated to
the reports.
CT alone contains
updated data, the
OBIEE report should use
the original source
F_SHIPMENT_EVENT_FA
CT table for queries.
Priority group values of
all Mviews of this table
are changed from 0 to 1
(1 is less priority than 0)
so that
F_SHIPMENT_EVENT_FA
CT is used always for
report.

30562 Log in as various non-English All language caption

685 users and navigate to
Dashboard. See that all but the
2nd to last tab appear in English
and not the user's language.
This happens for all non-English
users.
XML files are reverted
to previous version to
be in sync with the
English file. This now
works as expected.
Note: There is a known
issue where the
translations for the TI
pre-defined dashboards
are based on 6.4.3
translations. This will
be fixed in the next
version of OTM.

Oracle Fleet Management

 

Iss Summary Resolution

ue
Nu
mb
er

Oracle Fleet Management
293 The Hours Left on Shift (D)
503 field on the Driver custom
79 screen set assumes calendar
is in UTC and does not take
into account drivers home
terminal time zone.
298 Fleet assign actions need to
039 work for SAW shipments with
67 no shipment ship units.
Shipment equipment may or
may not be marked as freight.
298 The Revert Swap action
044 errors when shipments
57 created as a result of running
the action Relay Shipment
Swap when Get the Driver
Home is set to true.
298 Allow fleet unassign actions
682 to work for SAW shipments.
34
Fixed the issue that assumed
calendar was in UTC and did
not take into account drivers
home location time zone
while displaying Hours Left
on Shift (D) field on the Driver
custom screen set.
For SAW shipments with
Transport shipment type, the
verification done with fleet
actions (i.e. Assign Driver,
Assign Best Driver Assign
Equipment, Assign Equipment
Type, Insert NFR Stop, and
Remove NFR stop) will be
removed.
If shipment has a fixed arrival
time on the first stop and it
has at least one of the
PLANNED_ARRIVAL,
ESTIMATE_ARRIVAL or
ACTUAL_ARRIVAL populated,
OTM will use this time to
retrieve the shipment even
when this time is in the past.
The Revert Swap action was
not adding the NFR stop to
the end of the shipment when
Get the Driver Home was true
so the action failed. This has
been fixed.
The following actions are now
supported for SAW shipments:
Unassign Driver, Bulk
Unassign Driver, Unassign All,

298 Duplicate work invoices get
954 created for the same
67 shipment when cancelling
the initial work invoice after
it has been sent/received,
and then generating a new
driver work invoice.
299 If you execute the action
556 Relay Shipment In Transit -
03 Force on a shipment with a
driver assignment, the action
fails if the driver has a
subsequent Shipment
assignment. The error is "For
Relay, shipment
<SHIPMENT_GID> should be
the last Driver Assignment for
driver.".
302 HOS Rule Begin Time is set
224 to null when a shipment is
59 assigned to the driver. This is
causing the time remaining in
each rule bucket to be
calculated incorrectly when
the next shipment is
assigned to the driver.
303 When "Use HOS History" is
122 NOT checked, drivers should
28 be given fresh hours for each
shipment they are assigned.
This is only happening for 11
and 14 hour rule and is not
Unassign Power Unit, and
Switch Driver.
Note: Switch Driver in Driver
Gantt chart is not supported.
This is now fixed and the
work invoice generation only
generates a single invoice.
The error is no longer
received when the driver has
a subsequent shipment
assignment.
Resolved to allow the
previous HOS rule begin time
to be carried forward to
subsequent driver
assignments if a more recent
rule begin time has not been
encountered.
Fixed to properly ignore a
driver's HOS related history
for period based rules if "USE
HOS HISTORY" has not been
selected for the driver. This
change did not affect
 working correctly for 70 Hour
Rule.
303 The "Rerate and Redrive" and
338 "Assign" rate actions do not
98 consider driver associated
rate offering. A shipment is
planned with a rate and then
driver is assigned to the
shipment. On Driver
Assignment - Rate Offering
associated with the driver is
then associated with the
shipment. Later , if the
actions "Assign Rate" or
"Rerate and Redrive" are run
on the shipment, the rate on
the shipment changes back
to the original rate it planned
with even though the driver is
still associated with the
shipment.
303 The "Change Status" action
339 on Work Assignment fails
39 with an error.
303 When the action "Just Get
409 Driver Home" is being
22 executed on a particular
driver, an NFR stop is added
to the last assigned shipment
of the driver. The Distance
Type on the stop is being set
as bobtail.
Special services need to be
considered on the drop off
continuous based rules. They
continue to work properly for
both settings of "USE HOS
HISTORY".
In the "Assign Rate" or
"Rerate and Redrive" actions,
OTM will first use the rate
offering GID on the driver of
the shipment, if it exists.
This is resolved. You can
update the Work Assignment
status without any issue
when using the "Change
Status" action.
Added the property
glog.business.shipment.ignor
eStopSpecialServiceWhenCal
cBobtailDeadhead. The
default is true (existing
behavior) meaning special
services are ignored when
determining bobtail and
deadhead on a segment.
Set this to false to consider
 stop and then set the
distance type accordingly
(deadhead or bobtail).
304 Distance type is set as
521 "Loaded" instead of "Bobtail",
special services on the
pickup or drop off stop when
determining whether a
segment is bobtail or
deadhead.
When false, to determine
whether a segment is
deadhead or bobtail, OTM will
look beyond whether there is
a shipment equipment cover
for the segment and look at
special services for the stop
to determine whether a
segment is bobtail or
deadhead.
For example, for the segment:
NFR --- PICKUPSTOP: if there
is no shipment equipment
going thru this segment, OTM
will also look at the special
service at PICKUPSTOP. If it
is PICKLOADED, this segment
will be considered bobtail,
otherwise it will be
considered deadhead.
For the segment:
DROPOFFSTOP --- NFR: if
there is no shipment
equipment cover for this
segment, OTM will also look
at the special service at
DROPOFFSTOP. If it is
DROPLOADED, this segment
will be considered as bobtail,
otherwise it will be
considered deadhead.
The distance type between
two NFR stops is always
 91 when the property "Bobtail" if there is no
glog.business.shipment.ignor shipment equipment cover for
eStopSpecialServiceWhenCal this segment.
cBobtailDeadhead is false.

306 Location Asset Inventory is Added the following note to

174 not updated for a driver that
38 has a fixed power unit and
fixed equipment. This is not
stated in online help.
the Location Asset Inventory
manager topic: "Note:
Location asset inventory is
not updated for a driver with
a fixed power unit and fixed
equipment."

Oracle Global Trade Management

 

Issue Summary Resolution

Numb
er
 
Global Trade Management
27019 OTM/GTM user Foreign key constraint
585 management does GL_USER_GID is dropped from the
not allow the deletion GTM_AUDIT_TRAIL table. This
of a user that has a constraint was preventing the
transaction in the deletion of the user that has a
GTM Audit Trail. The transaction in the GTM Audit Trail.
following error
message is returned:
"Cannot delete the
GL_USER record. A
GTM_AUDIT_TRAIL
record references it
in its GL_USER_GID
column.".

28799 Customization of GTM This issue is resolved. Custom GTM

037 Structure manager Structure manager layout without
 layout is not working. Item ID field produces no javascript
errors.

28844 There is no field that There was no field present on the

964 displays the actual Document view/edit screens to
user that generates a display the user that has generated
document in GTM. a particular document. A new field,
"Generated By", has been added to
these screens to display the user.
This field is only visible for
documents that have been
generated and is not visible for
documents that have been
uploaded.

28983 Custom product Fixed the lookup process to

240 classification type retrieve classification codes for
and code should be custom classification types.
allowed in the
following screens:
 Campaign Line
 Item Structure
 Line Item
Structure
 Registration
 Reporting
Quantity grid in
both
Transaction
Line and
Declaration Line

28995 Re-order the fields Modified order of the fields that

027 that appear on the appear on the Party Site page.
Party Site page. In Also, added a SmartLink to "View
addition, add a Related Party Sites".
SmartLink to "View
Related Party Sites".
29172 Remove menu links The advanced layouts - Restricted
644 for advanced layout Party Screening Work Queue and
work queues and Transaction Line Work Queue - are
document how to deprecated and will be removed in
create workbench a future release.
work queues. Also removed the prior help topics
for "Using the Restricted Party
Work Queue" and "Restricted Party
Screening Work Queue", and added
a topic for "Creating a Restricted
Party Screening Work Queue".

29172 The country code The country SWAZILAND has been

997 CSV file that ships renamed to ESWATINI in the CSV
with OTM/GTM needs file. Old 2 and 3 digit codes remain
to be updated based the same. MACEDONIA, THE
on a country name FORMER YUGOSLAV REPUBLIC OF
change. SWAZILAND has also been renamed to
has renamed itself to MACEDONIA, NORTH. Country
ESWATINI. This is codes remain the same.
now globally the
correct name. Old 2
and 3 digit codes
continue to be used.
29479 In Campaign Line Line Description text field area is
235 page, move the Line moved below Item Origin in
Description text field Campaign Line new, edit, and view
area below Item pages.
Origin.
29479 Following issues Issues regarding help links are
480 were observed in resolved.
Restricted Party
Restricted Party Screening Work
Screening page:
Queue has been deprecated and
1. Clicking the the menu link is removed.
help link on Ad
Hoc Screening
Audit View page
results in an
 error.
2. Restricted Party
Screening Work
Queue page
alignment is not
correct. Title of
the page is not
seen properly.
3. Clicking the
help link In
Review Match
Factor result
page results in
an error.

29527 On the Product The translation for the UOM

355 Classification Code Description in the Required Units of
screen, in the Measure grid has been fixed.
Required Units of
Measure grid, the
translation for the
UOM Description is
incorrect. Fix the
translation.

29549 When Tariff Eligibility This issue is now resolved. Tariff

506 Screening is run for Eligibility Screening can be run on
different time periods an item with item origins of
of the same item different time periods or on
origin or for different different item origins without
item origins, the overwriting the existing trade
trade program results programs.
are overwritten.

29656 Clicking the help link This issue is fixed. Help link on the
361 on Campaign > Send Notification action input and
Actions > Send result pages will now open without
Notification page any error.
results in an error.
29762 A Document Type When the Download Document
505 with the Owned By Template action was performed on
field value as GTM a campaign line, some document
CAMPAIGN LINE is types with the Owned By field
created at the value as GTM CAMPAIGN LINE
campaign level and a were missing from the drop-down
document is added to list. Now the issue is fixed and the
this document type. action is modified to only display
While performing the document types associated with
Download Document the campaign line on which the
Template action on action is performed.
the corresponding
campaign line, the
newly created
document type is not
displayed in the drop-
down list. Also only
the document types
associated with the
campaign lines on
which action
performed should
display in drop-down
list.

29777 Add saved queries to Added the saved queries for

628 support workbench workbench:
for trade agreements.  PARTY SITES FOR PARTY
 TRADING PARTNER ITEMS
FOR ITEM
 ITEM ORIGINS FOR ITEM
 ITEM TRADE PROGRAMS FOR
ITEM
 TARIFF RATES FOR PRODUCT
CLASSIFICATION CODE
(retrieves only current rates)
TARIFF RATES FOR TL
CLASSIFICATION CODE
 (retrieves only current rates)
 TARIFF RATES FOR DL
CLASSIFICATION CODE
(retrieves only current rates)
 ITEM TRADE PROGRAMS FOR
ITEM ORIGIN TARIFF RATES
FOR ITEM CLASSIFICATION
CODE (retrieves only current
rates)
 PARTIES FOR TRADING
PARTNER ITEM

29778 Duplicate licenses When there are multiple controls on

954 are assigned to a a transaction line, the licenses will
transaction line when now be assigned properly for each
there are multiple of the control code.
control codes.

29783 Add ITEM Added the saved query ITEM

735 CLASSIFICATIONS CLASSIFICATIONS FOR ITEM to
FOR ITEM saved workbench.
query to workbench.

29795 Add product Added a public saved query "PROD

958 classification CLASS TEMPLATES WITH INVALID
template to Business CODES" which fetches templates
Monitor to see which with invalid codes.
codes in the template
are invalid and
update them
accordingly.

29804 Problems noticed Email notification via agent is now

012 while generating successfully sent from the Partner
email notifications Item. The class
through agent from PartnerItemEventContext is now
the GTM object removed.
Partner Item.

29804 Update license Added note to following help

016 management help topics:
with note about not  Licenses
supporting dynamic
creation of licenses  About License Screening
based on
transactions and/or
declarations.

29955 The "Look Up Product This issue is now resolved and the
655 Classification" action error won't be thrown when
fails with the error alphabetic codes are used with
"Multiple fixed flag. The primary
Classification Codes classification code for HTS US
are not allowed for a won't be copied from the item on
type HTS US" when override since a primary code
using alphabetic (alphabetic) already exists on the
classification codes. line.

30014 Attempting to copy Now a Location View manager

959 the layout can be copied and a new
"GTM_LOCATION_VIE manager layout can be created
W" manager layout successfully.
results in the error:
"An Undefined Error
Has Occurred. Please
Try Again Later.".

30020 Workbench saved Added the saved query REQUIRED

425 query and label DOCUMENTS FOR ITEM TRADE
issues noticed. PROGRAM and modified the query
REQUIRED DOCUMENTS FOR
CAMPAIGN LINE to fetch Required
Documents for Item Qualification
and Campaign Line respectively.
Fixed label issues.

30061 General default rate Only the non-default tariff rates will
196 is being selected be added via agent when eligibility
during tariff eligibility screening is run.
screening via agent
action.
30111 Any user should be The "Update Classification
997 able to run the Version" action can now be
"Update performed by logging in as any
Classification user.
Version" action.
Currently, the action
can only be run by a
DBA user.

30163 Fix the field issues in 1. Changed Tariff Rules of

503 Assign Classification Interpretation field from a
and Update drop-down list to a pick list on
Classification Code in Assign Classification and
Process Management Update Classification Code in
screen. The Tariff Process Management screen.
Rules of
2. Binding Rule Number is not
Interpretation field
limited to 16 characters
should be a pick list
anymore. Limit is 128.
and  the Binding Rule
Number should not be 3. Earlier an error was thrown
limited to 16 while running the "Lookup
characters. Trade Program" action when
a Supplier Site-Partner Site
constraint qualifier was not
present on the line. This issue
is now fixed.

30198 Following issues are The issues mentioned are resolved.

424 seen during Tariff
Eligibility Screening
via agent action:
1. The Product
Classification
Type field
should be made
mandatory.
2. An alert
message should
be displayed if
there is a
 mismatch
between
classification
type and trade
program profile
type.
3. Product
Classification
Type is not
visible in Trade
Program Profile
screen.

30216 For the Constraint Set Added 2 more constraints- Country

537 Type as of Manufacture and Inventory
TRANSACTION-LINE Organization. Supplier is already
TRADE PROGRAM added as Partner.
LOOKUP, add the The label in Item Origin page has
following new been changed to And/Or.
constraints:
In Transaction manager,
1. Country of import_prod_class_type_gid column
Manufacture was set to a value. On clicking
2. Supplier "Save" and then clicking
"Finished",
3. Inventory import_prod_class_type_gid was
Organization nulled out. This is now fixed.
Also, change the "OR" Added error messages for missing
label on the Item Item, Country of Origin, Import
Origin between Classification Type, Product
Inventory Classification Type and Code on
Organization and line. Added trade program eligibility
Supplier to "AND/OR". screening error messages. These
are displayed under Status column
of the action result page.
Error message is displayed if Date
Qualifier (a mandatory field in
Constraint Set screen) is not
present on the line or header.
30248 Add a check on the If Destination Location Qualifier
921 Lookup Trade SHIP_TO (set by the property
Program/Trade gtm.dutyTax.dsg.shipToLocation.lo
Program pick list to cationQualifier) is not present on
see if SHIP TO the line or header, then the Lookup
party/location is Trade Program action is not
present on a allowed and an appropriate error
transaction message is displayed.
line/declaration/line. Apart from Country of Origin,
Else, lookup trade Import Product Classification Type,
program cannot be and Qualified filtering, two new
performed. checks are added:
 check to see if classification
code on line matches the
product classification code of
the Item Qualifier
 check to see if the status of
the Item Qualifier is
QUALIFIED
Constraint name SUPPLIER SITE
has been changed to PARTNER
SITE and Partner field has been
removed.
A new constraint PARTNER has
been added with the input field
Partner.

30248 On Transaction Line Searching in the Trade Program

958 screen, click the pick list will throw the error
Trade Program pick "Destination Location Qualifier
list. It should identify {invPartyQualGid} is not present on
the trade programs the line or the header of
applicable for import transaction line {transLine}" if
classification type, SHIP_TO qualifier is not present on
classification code the line or header. Trade Program
and country of origin. pick list of transaction
Currently line/declaration line identifies trade
classification code programs applicable for the import
and country of origin classification type, classification
 are not considered for code, and country of origin of
the filtering. transaction line. If all three are
null, then all the trade programs
are retrieved.

30288 Class cast exception Fixed the problem with non-string

066 querying GTM type of pseudo fields on finder
Transactions when results.
quantity value is
populated in results.

30298 Following issues are Issue 1: There is no support for this

667 observed with now. This will be fixed in a future
Approve Campaign release.
action:
Issue 2: Additional item origin was
1. There are added when Approve Campaign
inconsistencies was performed if one of the item
with how the origin effective date, expiration
Approve date is null and other was
Campaign matching. Fixed this issue and no
action and additional item origin is created.
Approve
Campaign Line Issue 3: On running the Approve
action work. Campaign action, if the document
When we to be copied mentioned in data
approve a configuration was not owned by
campaign line, it Item Qualification, the document
does not roll up was not copied to item
to the header qualification. Now, an error is
and the header thrown in this case conveying the
remains in an IN same.
PROGRESS
status. If  we
then try to
change the
header to
APPROVED, we
get and error
because the
line, even
 though
approved, is not
in the proper
status.
2. When the
Approve
Campaign
action is
triggered, it is
adding an
additional item
origin to the
item. It occurs
when we trigger
the action from
either the
campaign or the
campaign line.
3. When we trigger
the Approve
Campaign
action, it looks
like data is not
getting copied
back to the item
qualification
record.
According to the
data
configuration
attached to the
logic
configuration,
certain details
including a
document
should be
copied back but
 are not.

30315 GtmTradeTransaction GTMTradeTransaction Log ID is

795 Log ID is not visible in now visible in Log Files.
the Log File screen.

30321 Event reason data Event reason and notify subject

241 needs to be added for data has been added for the action
Lookup Trade Lookup Trade Program (web and
Program agent agent). Agent events added are:
action.  GTM SHIPMENT - LOOK UP
TRADE PROGRAM (AGENT)
 GTM SHIPMENT LINE - LOOK
UP TRADE PROGRAM
(AGENT)
 GTM TRANSACTION - LOOK
UP TRADE PROGRAM
(AGENT)
 GTM TRANS LINE - LOOK UP
TRADE PROGRAM (AGENT)
 GTM TRANSACTION - LOOK
UP TRADE PROGRAM
 GTM TRANS LINE - LOOK UP
TRADE PROGRAM
 GTM SHIP LINE - LOOK UP
TRADE PROGRAM
 GTM SHIPMENT - LOOK UP
TRADE PROGRAM
Also, item GID displayed on top in
each tab of Item manager edit page
has been changed to display item
XID.

30321 Support new columns Added support of

268 of BINDING_RULING_NUMBER,
ITEM_CLASSIFICATIO BINDING_RULING_EFFECTIVE_DAT
N for the agent E, CLASSIFICATION_USER,
 events ITEM CLASSIFICATION_DATE,
CLASSIFICATION - REVIEW_USER, REVIEW_DATE,
CLASSIFICATION ELIGIBILITY_SCREENING_USER,
ADDED REMOVED and ELIGIBILITY_SCREENING_DATE ,
ITEM GTM_TARIFF_ROI_GID, and
CLASSIFICATION - CUSTOMS DESCRIPTION for the
CLASSIFICATION agent events ITEM
MODIFIED. CLASSIFICATION -
CLASSIFICATION ADDED REMOVED
and ITEM CLASSIFICATION -
CLASSIFICATION MODIFIED.

30331 Copy action on item This issue is resolved. Now trade

987 is also copying trade programs are not copied on running
programs. the Copy Item action.

30371 Remark qualifier for a Remark qualifier of data query type

541 trade item structure TRADE ITEM STRUCTURE is now
is not displayed in the listed in the drop-down list in the
Trade Item Structure remarks grid of the Trade Item
manager. Structure screen.

30402 Apply Item Template The issue happened whenever 10

560 is not working or more items were used for
properly after performing the Apply Item
performing Refine Template action, and later the
Query. Template is same action was performed on less
getting applied than 10 items. This happened
wrongly to previously because of the item IDs added to
searched items the session by first action request.
though Refine Query Now, code is added to remove the
is performed. cache primary keys of previous
request.

30418 GtmItemClassificatio The following have been made non-

633 n.TradeDirection is mandatory fields in integration:
mistakenly marked as  GtmItemClassificationType.Tr
required in XSD. adeDirection
 GtmItemUomConversionType.
SequenceNumber
  GtmItemUomConversionType.
GtmProdClassTypeGid
Also,
GtmItemUomConversionType.GtmP
rodClassTypeGid is deprecated.

30439 Change name of field The translation label is changed

229 from "Threshold" to from "Threshold" to "Saving
"Savings Threshold" threshold" in the Tariff Eligibility
in the Tariff Eligibility agent action screen.
agent action screen.

30439 During campaign Added check which throws specific

496 creation, getting error if trade programs are missing
generic error "Party on item and trade agreement is
Site(s) on Item is not given as a criterion during
matching with the campaign creation.
selected Partner
Item(s)" even though
the campaign
couldn't be created
because of the
missing trade
programs in the item
origins of the items.

30462 Missing trade 1. Added check during Tariff

020 agreement on item
qualification during
Tariff Eligibility
Screening when trade
agreement short
name mismatches.
The system should
throw an error when
the short name is
missing or does not
match.
Eligibility Screening which
throws error if the trade
agreement short name on
trade program does not have
a valid trade agreement.
2. Short Name field is made
mandatory on Trade
Agreement edit screen.
3. If trade agreement Short
Name field is empty on trade
program, the system shows
the message "No Trade
Agreement found" in the field
 Trade Agreement, and the
earlier check box is removed.
4. Item Description field on
Transaction Line and
Declaration Line edit/view
screens now has a maximum
length of 500.

30467 Add country code The country "THE REPUBLIC OF

602 "XK" to the country KOSOVO" with the country code
code CSV file that "XKX" and "XK" is now added to
ships with GTM. the CSV file.

30484 Slow performance of Fixed an issue to remove the

606 RPLS when exclusion words from the denied
considering exclusion parties during screening which was
words. not happening.
Though the quality is better when
compared to previous versions, the
removal of exclusion words from
each denied party during party
screening was slowing down the
RPLS processing of parties and
reducing the throughput of RPLS.
To resolve this, added two
properties.
1. gtm.rpls.globalExclusionWord
s: This property identifies the
exclusion words global list at
the App level with comma
separated exclusion words.
You can prepare a global
consolidated list of exclusion
words already used for
different service preferences
and use the global list for
exclusion.
2. gtm.rpls.useExclusionWords=
Service Preference (default):
This property will identify
whether or not to remove
exclusion words and identify
the level for exclusion words
to be removed. Following are
the four supported values:
1. No: GTM will not remove
exclusion words from
party or any of the
denied parties.
2. noExclusionFromDenied
Party: GTM will remove
exclude words on party
side but will not exclude
it from denied parties.
This was the behavior
prior to 19A. You can
use this to revert to the
old performance of
RPLS.
3. Service Preference: GTM
will remove exclusion
words defined at service
preference level from
both party and denied
parties. This is the
current behavior which
though improves the
quality of matches, can
have performance
impact.
4. Global: GTM will remove
global list of exclusion
words (identified by
gtm.rpls.globalExclusion
Words property) from
party and denied
 parties.
Recommendation: The Global level
is recommended for
gtm.rpls.useExclusionWord as it is
better than the first two options in
terms of quality and better than the
third one (current behavior) in
terms of performance.
For Global level, GTM will cache
the denied parties after removing
the exclusion words and hence the
performance is better compared to
the third option.

30578 Editing product Fixed the error in the following

619 classification throws custom manager layouts:
an error in Item 1. ITEM: Product Classification
custom manager (Edit and Add New), Add Item
layout. Origin, Add Item Qualification
2. GTM_TRANSACTION: View
Responsible Lines, Verify
Classifications
3. GTM_TRANSACTION_LINE: V
erify Classifications
4. GTM_STRUCTURE:
Documents tab
5. GTM_COMPLIANCE_RULE:
Remarks tab

Oracle Trade Compliance

 

Issu Summary Resolution

e
Num
ber

Oracle Trade Compliance
2633 The Percentage Values grid
8991 on Transaction Lines or
Declaration Lines screens
does not collapse.
2755 Add a Reports menu option
6010 to GTM high level menus for
all the GTM reports in
Reports Manager.
2892 When you try to perform any
7637 action on a record which no
longer exists in Work Queue
(i.e., it's been assigned to
another active user but still
reflects in previous user's
This issue is resolved. Now
the Percentage Values grid on
Transaction Lines and
Declaration Lines screens can
be collapsed and expanded.
Following reports are added in
the Reports menu:
1. AES_FILING,
DECLARATION_CCI
(Declaration Customs
Commercial Invoice)
under Customs > Report
Type > DECLARATION
2. TRANSACTION_CCI
(Transaction Customs
Commercial Invoice)
under Transactions >
Report Type > TRADE
TRANSACTION
3. LICENSE_ASSIGNMENT_
REPORT under Licenses
and Registrations >
Report Type > LICENSE
4. US_NAFTA_CAMPAIGN_L
INE under Trade
Agreement > Report
Type > TRADE
AGREEMENT
When the records are
assigned to a different user,
"User no longer holds the
object" error message is
displayed for the actions Add
Authorization in Transaction
 work queue), an error
message used to be
displayed in advanced
layout - "User no longer
holds the object". This is no
longer happening. So both
users are able to run action
on the same record.
For Review Match Factor
and Add Comment actions
also the message does not
work.
2895 Following issues are
9320 noticed about integration of
an item:
 Default Country of
Origin is not currently
implemented on the
item outbound.
 Item Type is not
currently implemented
on the item outbound.
 Item BOM is not
currently implemented
on the item outbound.
2965 Declaration update through
6365 XML file produces a null
pointer exception. However,
the system should display
that the classification code
provided was not active.
2967 Item structure assignment
7741 is failing.
Line work queue and the
actions Review Match Factor
and Add Comment in
Restricted Party Screening
work queue.
The error message is also
displayed for all actions in
Contact work queue.
Added default Country of
Origin and Item Type to
outbound item master XML
and deprecated
GtmItemCountryOfOrigin.
Item BOM is no longer used
and was replaced by Item
Structure. Hence outbound of
item BOM is not  required any
more.
When the classification code
provided during declaration
update through XML file was
not active or not valid, a null
pointer exception was thrown.
Now an error is thrown
indicating that the provided
code is not present.
This issue is resolved. The
child transaction line IDs
generated after item structure

2970 Add a "Trade Program" field
4313 to Transaction Line and
Declaration Line screens.
2976 Duplicate entry is added to
0752 the Control Screening
results grid on the
Transaction Line page when
trying to save a record in
the grid without editing it.
2976 The party data of
5425 transaction line was not
matching with the party
data of the license line but
still it matched and held the
wrong License Details.
2981 When performing the Add to
9849 Campaign action on
items/partner items with
multiple partner items from
a party site, duplicate
campaign lines are created.
2986 When trying to add a
6160 transaction to an existing
declaration, GTM is
assignment will now use a
new Business Number Type
and will be in the form of
Parent Transaction Line ID - 4
digit number.
Added a new field named
"Trade Program" to the
Transaction Line and
Declaration Line screens. The
field holds the trade program
short name that will be sent to
the external system to get the
duty and tax values related to
the trade program.
Now no duplicate entry is
added to the Control
Screening results grid. On
trying to save a record in the
grid without editing, the
expected error message "Edit
a grid to save the License" is
displayed.
The transaction data and the
license data is matched
appropriately based on the
constraint set configuration.
Modified the logic of action
and now no duplicate
campaign lines are created
when the action is performed.
When a transaction is added
to an existing declaration, the
quantities are now summed on
 generating a null pointer
error and displaying an open
cursor error in the logs.
2986 Estimated Landed Cost
8464 result details does not show
Merchandise Processing
Fee.
2987 Unable to enter more than
8344 13 digits in the GTM
transaction value field on
the Trade Transaction page
even though it is a number
field.
2990 Change the "Qualified"
6056 check box to a drop-down
list on campaign line and
item origins for trade
programs screens.
the declaration line. An error
message will be generated
when trying to add quantities
not of UOM type of
weight/volume/quantity.
Additionally, a transaction line
with UOM type other than the
types mentioned will not be
allowed during Build
Declaration. If Quantity UOM
Type is not
weight/volume/quantity, the
error message "Quantity UOM
type {uomType} is not
supported for Build
Declaration." will be
displayed. The open cursor
error is also fixed.
Modified the code to consider
the header level taxes while
adding the values to be
displayed in the Landed Cost
Simulator. Estimated Landed
Cost result details now show
the Merchandise Processing
Fee.
This issue is now resolved and
currency values can be
entered in the billions.
Changed the "Qualified" check
box to a drop-down list on
campaign line and item origins
for trade programs screens.
2991 In Trade Transaction Line The label is now "Trade
8285 finder, view, and edit Programs" on the finder, view,
screens a field name is and edit screens.
inconsistent. In the finder it
is displayed as Trade
Program ID. In the edit
page, it is displayed as
Trade Programs, and in the
view page it is displayed as
Trade Program. It should be
Trade Programs in all the
three screens.

2991 Search is failing when trade Transaction line finder set is

8433 program is used as input in corrected. The finder was not
the Trade Transaction Line able to search for mixed case
finder. for trade program field.

2995 Set Control Screening Set Control Screening Status

5609 Status action does not
work. It does not change
the CONTROL_SCREENING
status via the action screen
or the work queue.
action on transaction line now
successfully updates the
CONTROL_SCREENING status.

2999 Add following indexes to fix Added indexes as mentioned

6363 TM-locking related to in the issue.
insert/delete into
DOCUMENT and
GTM_TRANSACTION_REQD
OC:
 IX_DOC_CONTENT_MA
NAGEMENT_SYS on
DOCUMENT_T
(CONTENT_MANAGEM
ENT_SYSTEM_GID)
 IX_GTRQ_GTM_CRULE
_GROUP_GID on
GTM_TRANSACTION_R
EQDOC_T
 (GTM_COMPLIANCE_R
ULE_GROUP_GID)
 IX_GTRQ_GTM_CRULE
_GID on
GTM_TRANSACTION_R
EQDOC_T
(GTM_COMPLIANCE_R
ULE_GID)
 IX_GTRQ_DOCUMENT_
DEF_GID on
GTM_TRANSACTION_R
EQDOC_T
(DOCUMENT_DEF_GID)
 IX_GTRQ_TRANS_GID
on
GTM_TRANSACTION_R
EQDOC_T
(GTM_TRANSACTION_
GID)
 IX_GTRD_DOCUMENT_
GID on
GTM_TRANS_REQD_DO
C_T (DOCUMENT_GID)
 IX_IRR_DOCUMENT_GI
D on
ITEM_REQDOC_DOC_R
EVIEW_T
(DOCUMENT_GID)
 IX_IRDD_DOCUMENT_
GID on
ITEM_REQDOC_DOC_T
(DOCUMENT_GID
 IX_SRD_DOCUMENT_G
ID on
SHIPMENT_REQDOC_D
OC_T
 (DOCUMENT_GID)
 IX_SSDOC_DOCUMENT
_GID on
SS_DOCUMENT_T
(DOCUMENT_GID)
3001 Add rules of interpretation
4503 and binding rules on
product classification
template.
3013 Remove duplicate
4907 transactions from the
DEFAULT_SHIPMENT_COMP
LIANCE_STYLESHEET.XSL.
3014 Add property to use old
5948 Create Trade Transaction
action on shipment and
order release.
3015 An exception is thrown
0117 when performing Send
Notification on campaign
via web and agent actions.
3022 On sending a specific trade
7022 program in Estimate Duty
and Tax request, nullify
trade program on
transaction and declaration
line if general rate is
returned. Else throw an
error notifying that the
requested and the received
trade programs do not
match.
Added the fields "Binding
Ruling Number", "Binding
Ruling Effective Date", and
"Tariff Rules of Interpretation
ID" on product classification
template finder and manager.
Duplicate transactions are not
created anymore when an EBS
delivery XML is sent to GTM.
Added property
(gtm.deprecated.createTransa
ctionOnShipment) to opt in/out
of the old feature of creating
transaction on shipment and
order release.
Send Notification functionality
is working now on campaign
using web and agent actions.
On running the Estimate Duty
and Tax action, if a specific
Free Trade Agreement is
requested and GENERAL rate
is returned, then trade
program on line (field or
remark) is removed. If the
requested trade program is
returned, trade program is not
updated on the line. If trade
program returned is not the
 requested or the default rate,
an error is thrown - "Trade
program returned by
Descartes:
{tradeProgramReceived} is
different from the trade
program requested:
{tradeProgramRequested}.".

3031 In the Sanction Control In the Sanction Control

2249 Results grid, add Results grid, now when you
Authorization and click edit and add Authorization,
Save. You get the message and click Save, the record is
"Edit a grid to save the saved successfully. The "Edit
license". a grid to save the license"
message is only shown when
you click Save without editing
the record.

3033 Fields are not translated Labels in the Documents tab

1484 properly on the Documents of the campaign lines finder
tab of the campaign lines are now translated.
finder page.

3036 Modify product Changes are made so that

5151 classification status when the property
settings. gtm.transaction.action.useLoo
kupToUpdateRequiredClassifi
cation is set to false:
1. Running the Look Up
Product Classification
action should not change
the product
classification status.
2. Adding classification on
the transaction line
screen should not
change the product
classification status.
Only the Verify Classification

3046 Remark Qualifier field
1905 cannot be edited in the
Controls tab of the
Compliance Rule screen.
3049 The item gets removed from
4313 the transaction line which
is created from an order
release after the order is
updated.
3050 When screening orders that
0470 would typically trigger an
export control hold, an error
is displayed: "There is no
action can set
TL_PRODUCT_CLASSIFIACTIO
N status.
This property can be
controlled via a new optional
feature MANAGE STATUS BY
VERIFY CLASSIFICATION. On
opting in, the property will be
set to false. On opting out, the
property will be set to true.
It is recommended to use only
the optional feature and not
the property set to control the
property.
Status was showing as
CREATED for all statuses on
Item Classification page in
Item Manager. This is also
fixed as part of this issue.
In the Controls tab of the
Compliance Rule screen, for
action Assign Remarks (also
Assign Reference Numbers
and Assign Involved Parties),
the grid in Action Details page
could not edited. This is now
fixed. The records can be
edited now.
The item will no longer be
removed from the existing
transaction line when the
order release data is synced
with the transaction.
When there are multiple user-
defined category, type, or
code combinations at the
transaction line level and
 compliance match with the
Header and Lines." This
results in orders that should
be on hold, to be approved
incorrectly.
compliance rule level for a
single user-defined category,
the compliance rule is now
matched successfully against
the transaction line.

Note: Updates may include security issues as required.

Parameters and Properties

Parameters
The following parameters are new in this release:

 The following parameters are used for PC*Miler web services

(see the External Distance/Service Engine and Map Parameters
help topic):
 AVOIDS_AND_FAVORS_SETIDS: It is used for custom routing
preferences, such as avoiding or favoring certain roads, or
overriding road restrictions. To apply avoids and favors, use
numeric value of '-1' to apply all of the avoids and favors
associated with the API key. To apply specific SET IDs, add
set IDs as comma-separated values.
 GOVERNOR_SPEED_LIMIT: It is the maximum average road
speed to use in route calculations that overrides all other
road speeds when they are above this value. Valid value is
between 1 and 100 mph, or 1 and 161kph determined by
DistanceUnits.
 USE_CUSTOM_ROAD_SPEEDS: Allows use of custom speeds
to negotiate service times with the carriers. The values can
be Y or N. To apply this parameter set the value to Y.
Logic Configuration - Container Optimization

 ITEM GROUPING CRITERIA: Part of the PATTERN BASED

PACKING ENHANCEMENT.
 PACK FULL CONTAINERS WITH LARGE ORDERS FIRST: Also part
of the PATTERN BASED PACKING ENHANCEMENT.
  REMOVE FRAGMENT SPACE IN GROUP PACKING: Added as part
of Load configuration - Group packing.
 USE LAST CONTAINER PRIORITY HEURISTIC: This replaces the
property
glog.optimization.packingparameters.skipMultiPassScoringPriort
yAlg.
 USE SIMILARITY SORTING IN GROUP PACKING: Added as part of
Load configuration - Group packing.
Logic Configuration - Continuous Moves

 CM RETURN DISTANCE COST FACTOR: As the setting is

increased from zero (the default) the "cost" associated with
returning from the end location of the continuous moves (CMs)
last shipment back to the start location of the CM's first
shipment is increased when considering the overall cost of the
CM. The default of zero (0) has the same functionality as prior to
addition of this parameter. This is part of the Continuous Moves
Out and Back feature.
Logic Configuration - Network Routing
 USE ROUTING SOLUTION ORDER MOVEMENT CONSTRAINTS:
This parameter controls whether the choices selected by
network routing are persisted as constraints on the order
movement. The default is FALSE.
Properties
The following properties are new in this release:

 glog.agent.dta.lockParent: Controls Data Type Association lock

behavior. It defaults to true. Works in conjunction with
glog.objectLock.locks.activity.FOR. If
glog.objectLock.locks.activity.FOR and glog.agent.dta.lockParent
are both set to false, the parent locks are suppressed.
 glog.bulkplan.warning.extEngineThresholdResponseTime: This
property enables a warning to show performance-related
information regarding the External Distance Engine (EDE) and
External Service Engines (ESE) during bulk planning.
 glog.business.planningstreams.dataMaskingDefinitionID: This
property identifies the Data Masking Definition ID to be used
 when exporting planning data. The default and only possible
value is BASIC. If this value is removed, then the Apply Data
Masking check box on the Export Planning Data page will not
work.
 glog.business.planningstreams.dataobjects.includerankinmanifes
t: Controls whether to include the rank in the manifest.xml file
when exporting planning data. Exported objects are sorted by
rank. Default: true
 glog.business.planningstreams.dataobjects.includenumobjectsin
manifest: Controls whether to include the number of objects in
the manifest.xml file when exporting planning data. Default: true
 glog.business.planningstreams.exportimportcachesize: This
property defines the total number of records, across all object
types, that can be stored in cache at one time when exporting or
importing planning data. Default: 2000
 glog.business.shipment.ignoreStopSpecialServiceWhenCalcBobta
ilDeadhead: This property is used to determine if a segment is
bobtail or deadhead when using NFR stops and there is no
shipment equipment for the segment.
 glog.business.shipment.isZeroWeightVolumeShipmentUnloaded:
When you have a shipment with both the weight and the volume
zero, you can specify that the Loaded Distance is calculated as
0. To do so, use this property. See issue 29913774.
 glog.dataquery.maxCount: Controls how many matching record a
data query can support. If the matched count exceeds this
maximum, the data query is aborted and an exception is written
to the log. The default for glog.dataquery.maxCount is 100,000.
 glog.ExternalDistanceEngine.EDEType.weightRange.glog.busines
s.rate.ratedistance.external.<EDE class name>: If using the
property glog.ExternalDistanceEngine.useNewEDECache, this
property is used to set the weight ranges.
 glog.ExternalDistanceEngine.EDEType.weightRange.glog.busines
s.rateservicescheduling.external.<EDE class name>: This
property works along with
glog.ExternalDistanceEngine.useNewEDECache. It allows you to
define weight ranges if you use dynamic attributes. You get the
 ESE class name when you create the external service engine. If
using more than one ESE, each ESE should have it's own property
valued. The default is 0 LB-60000 LB.
 glog.ExternalDistanceEngine.useNewEDECache: With this
property, OTM will use caches that are EDE/ESE specific. With
these caches, OTM will reduce the hits on the EDE when
Dynamic Attributes (including Length, Width, Height, Weight and
HAZMAT) are involved. The default is false. If you use dynamic
attributes, this should be set to true.
 glog.integration.application.transOrder.addAllocationDetail:
Specifies if the outbound transaction order element should
include transaction order line allocation details. The default
value is false. Set it to true to include transaction order line
allocation details.
 glog.integration.Topic.loadBalanceAcrossServers: A Topic
interface request may be immediately executed or published. If
published, there may a small delay in processing the topic as it's
made available to all servers in the cluster. If true, the topic is
published for all servers; if false, it is executed on the current
server.
 glog.jms.durableTimeToLive.<topic name>: For durable topics,
the lifespan of a specific topic should be kept short to avoid
message buildup when a server has scheduled downtime. These
properties control topic time-to-live. A durable topic is one whose
delivery is guaranteed as long as both servers are up. Even if a
communication error occurs, or the communication channel is
temporarily unavailable, the topic will eventually get to all
servers interested in it. Default value is 60 seconds to avoid
message buildup after a server crash.
 glog.objectLock.locks.activity.FOR: Controls whether Data Type
Association actions and FOR actions lock the parent record as
well as each child record. Works in conjunction with
glog.agent.dta.lockParent. If glog.objectLock.locks.activity.FOR
and glog.agent.dta.lockParent are both set to false, the parent
locks are suppressed.
 glog.oci.connectionTimeout=<msecs>: Sets the timeout for OCI
authentication.
 glog.oci.mail.autoRefresh=<msecs>: Controls the frequency of
the auto-refresh of the Mail Senders page.
 glog.oci.readTimeout=<msecs>: Sets the timeout for OCI API
calls.
 glog.optimization.networkrouting.maximalExpansionDaysForLeg
Option: This property defines how many days to consider for leg
options in the routing decision phase of network routing.
 glog.optimization.networkrouting.maximalExpansionDaysForOrde
rRoute: This property defines how many days to consider for
order route in the routing decision phase of network routing.
 glog.optimization.networkrouting.maximalNumOfIterations: This
property is associated with the multiple pass approach. The
value set by this property defines the iteration upper bound for
the multiple pass approach.
 glog.optimization.networkrouting.useMultipleIterationSolve: This
property controls whether to use a multiple pass approach to
solve the network routing with carrier capacity.
 glog.optimization.scheduling.weekendRestrictionService: This
must be valued to use weekend restriction with HERE external
distance engine.
 glog.optimization.scheduling.weekendRestrictionTimeStepHours:
This allows more granular start time adjustments for shipments
when attempting to remove or reduce wait time introduced by
weekend restrictions with HERE external distance engine.
 glog.process.walker.maxDepth: The maximum depth of tree
nodes to display on the screen. If exceeded the parent node is
shown with a right error to denote deeper nodes. Default: 100
 glog.process.walker.maxNodes: The maximum number of tree
nodes to display on the screen. If exceeded, the previous sibling
or parent node is shown with a down error to denote more nodes.
Default: 500
 glog.RatingEngine.enableEREResetFlag: While evaluating
conditions during rating, the object used in the RBI and its
related objects are eliminated for further evaluation if a condition
fails. This is reset for every rate cost or accessorial evaluation.
But it is not being reset when the evaluation of rate cost or
 accessorial is followed by evaluation of RBI for external rating.
This is now controlled based on this property since this change
has potential to modify the overall cost. The default value of
property is 'true' which means that it will always reset the
elimination of objects before evaluating the RBI for external
rating.
 glog.startup.startupPollingSeconds: Controls the frequency of
polling the APP_MACHINE_STATE table, looking to see if the old
machines are in the S_DOWN state. Default: 10.
 glog.tender.mandatoryShipmentRefNumberQual: This property
allows you to require that a service provider enter a shipment
reference number qualifier before accepting a tender.
 glog.webserver.finder.invalidOperators.finder_set_gid.<finder_set
_gid>: You can set this property to remove some search
operations for Text Field fields and Pick List fields in certain
finder pages. For example, if you set this property to
"FORBIDDEN_OPERTOR3" then the finder page with the
finder_set_gid will remove FORBIDDEN_OPERTOR3 from Text
Field and Pick List fields.
 glog.webserver.finder.invalidOperators.query_name.<query_name
>: You can set this property to remove some search operations
for Text Field fields  and Pick List fields in certain finder pages.
For example, if you set this property to
"FORBIDDEN_OPERTOR1,FORBIDDEN_OPERTOR2" then all finder
pages with the specified query_name will remove
FORBIDDEN_OPERTOR1 and FORBIDDEN_OPERTOR2 from Text
Field and Pick List fields.
 gtm.deprecated.createTransactionOnShipment: This property
allows you to enable/disable the use of the deprecated action
Create Trade Transaction. Set the value of this property to 'true'
to enable the Build Trade Transaction action. Set the value to
'true' to enable the deprecated action.
 gtm.rpls.diceEngine.globalExclusionWords: Use this property to
specify a global list of comma separated exclusion words to be
considered while performing restricted party screening.
  gtm.rpls.diceEngine.useExclusionWords: Use this property to
specify which of the following value to be considered while
performing restricted party screening:
 Service Preference: The system will remove exclusion
words defined at service preference level from both party
and denied parties.
 Global: The system will remove the global list of exclusion
words (identified by the
gtm.rpls.diceEngine.globalExclusionWords property) from
party and denied parties.
 noExclusionFromDeniedParty: The system will remove
exclusion words from party but will not from the denied
parties.
 No: The system will not remove exclusion words from party
or any of the parties.
Removed Properties
 glog.optimization.packingparameters.skipMultiPassScoringPriort
yAlg: This property was replaced with the Logic Configuration -
Container Optimization parameter USE LAST CONTAINER
PRIORITY HEURISTIC.
 glog.integration.dirload.threadcount:The logic is now managed
with the normal application event queues and so there is no
longer a need to have a separate property to control the thread
count.

Deprecated Items
These items have been deprecated and will be removed in a future
version. You should stop using these.

 Oracle supports translation to WorldWide Spanish and no longer

supports translation to Latin American and European Spanish.
OTM has kept Latin American and European Spanish translation
strings available though they have not been updated since 6.4.2.
These strings will be removed as of 20C so ensure you are using
WorldWide Spanish.
 The GTM Restricted Party Screening Work Queue and Trade
Transaction Line Work Queue have been deprecated and
 removed from the menus. You can create new work queues using
the Workbench Designer. See the Creating and Using a
Restricted Party Screening Work Queue help topic.
 Synchronize OTM Data action

Obsolete/Removed Items
The following have been removed:

 OAQ is no longer supported.

 OTM/GTM TOIs were out-dated and have been removed. You
should see the online Help instead, especially the How To topics.
GTM
 Create Customs Shipment process and the GTM transaction
agent actions of Add Transaction to Matching Customs Shipment,
Build Customs Shipment, and Remove Transaction from Matching
Customs Shipment have been removed.

Technical Support
Contact Support, or find the Support phone number for your region.

See the Information Center: Oracle Transportation Management (Doc

ID 2174060.1) for release announcements, links to documentation and
training resources, the new features summary, the recommended
patch list, and the error correction support policy.

Any updates to the documentation are on the Oracle Help

CenterOracle Help Center.

Copyright 2001, 2019, Oracle and/or its affiliates. All rights reserved.