55CU4RU7 Release Notes

8/4/2019 55CU4RU7 Release Notes

1/8

Oracle Transportation Management Release Notes 5.5Consolidated Update #4 Roll Up #7 (5.5 CU4 RU7)

This page describes the content of this Roll Up and contains the following sections:

Scope and Application lists who would benefit from reading this article.

Roll Up-Specific Installation Instructions describes additional installation

instructions (supplementing the standard consolidated update installationinstructions) that are specific to this roll up.

Enhancements lists all the enhancements in this release (excluding those

that were customer-specific and not included in the core product).

Corrections describes defects that were reported and fixed in the release.

Updated Files lists all files that have changed.

Technical Support provides contact information if you need assistance withthis roll up.

Note: Consolidated updates are cumulative in their content and anycorrections/enhancements from previous consolidated updates are also included. You

should also review previous release notes for release-specific installation instructionsas well.

Scope and Application

This document is intended for Oracle Transportation Management users, DBAs,system administrators, application consultants, support analysts, and project

managers. It assumes a working knowledge of Oracle Transportation Management

from a system administration and user perspective.

Roll Up-Specific Installation Instructions To install, please copy the jar file into a temporary directory and run: java

-jar .

To uninstall: java -jar uninstall.

To see the special instructions run: java -jar readme.

The system will have to be restarted before any changes will take effect.

Patch Version Requirement: Oracle Transportation Management 5.5 CU4

Required Patches: None

Note: Before installing the file please make a backup of all files.

Note: Do not use EZPatch

For Linux Users:

Note: In addition to this Roll Up patch, you need to download and apply patch

#7522898 from MetaLink.


2/8

Parameters and Properties

Following are the new properties for this release update. There are no new

parameters.

glog.scalability.thisMachineURL - This property is used to bind the port to

a specific IP/host name. We get this IP/host via the appserver OTM property.If the appserver property is invalid for some reason, we'll parse

glog.scalability.thisMachineURL. We now bind the activate port to the currenthost. The host name is parsed from this property along with the base RMI

port. For non-scalability users, the installer sets this property to:$appserver.protocol$$appserver$:$appserver.port

so the host is driven by the appserver property. For scalability users,thisMachineURL may have been modified to reflect the current scalability

host.

glog.settlement.allocation.verboseLogging - When set to TRUE, limitsallocation logging of ship units and ship unit lines to a maximum of 5. If more

than 5, then the fifth item will be followed by an ellipsis ("..."). The default isFALSE.

glog.tender.cbTimeZoneStopLocationBased: Controls whether time zone

values are saved with the values of the location (TRUE) or the user preferencevalues (FALSE). Default is FALSE.

Enhancements

There are no enhancements for this release update.

Corrections

Issue

Number

TAR Number Summary Resolution

7217620 6898094.993 Consol-deconsolidationshipment scenario not

working as desired

The issue is that, in a multileg itinerary, theconsolidation of orders on a leg was unnecessarily

constrained when, on the subsequent leg, the ordersare on different schedule shipments with different

start times. This can prevent consolidation where it

is supposed to occur.For example, orders were unable to consolidate on

the second leg, even though they were actually on

the same flight, because on the third leg one orderwas on a flight and the other on a voyage with

different start times.The issue has been fixed, and consolidation will no

longer be overly constrained in this case.

7702675 7223987.993 Show routing options

gives different resultsbetween optimize and

show options.

Before the fix, service provider GID, transport mode,

rate offering, and rate geo were not properlypopulated onto shipment (via LegOption) when

CaculateRate is unchecked on the itinerary. This isnow fixed.

7829960 7366925.992 RateWare is returningrates in CAD (Canadian

The link to SMC Rateware will now use the currencyGID on the base rate offering to determine the


3/8

currency) as expectedbut OTM is treating this

as USD.

currency of the results returned from a ratingrequest.

7833604 File not found error on

performing 'ready to

ship' and 'confirm toship'

There is no longer a "File Not Found" error when

performing the 'Ready to Ship' and 'Confirm to Ship'

actions.

8139518 7136971.994 Planning not adhering

to service providerconstraint

Modified to check the service provider on the rate

offering and rate record of the itinerary leg to matchwith the service provider constraint on the order.

8201658 7304590.993 When creating aninvoice the weight is

shown correctly butwhen saved shows

incorrectly. UOM andBase mix-up.

When saving an invoice/bill the Weight and Volumefields were always being saved with the default UOM.

This has been fixed to save the correct UOM.

8204749 Commercial Invoice ByOrder report cannot be

formatted: throws

elasticity errors, due tolarge data and is not

published on the userinterface.

To resolve the issue, the report has been checked forelasticity of various columns to accommodate large

data; elasticities of various columns have been

changed to 'expand', to allow them to accommodatelarge data.

8205538 Ship units lost when

splitting an ordermovement off a

shipment

Modified so that the to-be-splitoff ship units are not

removed from the order movement if they constitutethe entire order movement, because the order

movement itself (along with the SSUs) will be split

off from the shipment

8207518 7332837.992 On accepting thetender, the result page

been displayed showsthe Shipment ID. When

the Shipment ID isclicked, it picks the

application defaultfinder set instead of the

user default finder set.

The user default screen set shall be selected.

8211768 App server to app

server communicationerrors

When an app server restarts, it updates network

topology on each app server and webserver in thescalability network. This has been fixed to update not

only routing maps but also global machine lists usedfor diagnostics.

8217416 7319618.992 Rate inquiry issue:When there is an

Infeasible Solution for

any leg of the

When backtrackDrive is on, if service time infeasibleor no solution, keep driving until a feasible solution is

found or order early pickup is reached. If an

infeasible solution is found, treat it as no solution


4/8

shipment, client wantsthe result to be the

same as no solutionthat is "No Rate and

Route Found" message.

8223697 7316017.994 When using ContainerOptimization withPATTERN BASED

OPTIMIZE, theequipment is not being

fully utilized.

OTM was picking STANDING NESTED instead ofSTANDING STRAIGHT in some cases. Modified thecode that compared these two solutions to further

look at the remnant length and width to decidewhether STRAIGHT or NESTED is better. The change

resulted in one equipment when the scenario wastried again. Also added an exception when the

diameter of the cylindrical ship unit is mistakenly notspecified.

8234546 6834008.993 Retender going to moreexpensive carrier -first

preferred

Fixed. After retender servprov with equipmentgroup, the next cheapest rate will be used.

8239001 TAllocation.toString()

method can log

excessive output insome of the loops,

especially withconsolidated invoices

when there are many

shipments and/or manyship units.

The following has been implemented to reduce the

amount of data written when calling the

TAllocation.toString() method.glog.settlement.allocation.verboseLogging=false.

When this property is set to true, logging works as inthe past.

8247766 7339140.993 When an order releaseis copied that contains

Ship Units, the "NewLine Item" button

should not bedisplayed. This button

should be removed.

New Line Item button will no longer appear on theLine Item tab when copying an existing order

release.

8255875 Cleanup object lock on

restart of an appserver.

When an application server restarts, it now:

1. Clears any OBJECT_LOCK records it owns.

2. Notifies all other scalability servers that the locks

are now available. This allows any waiting servers tosecure the locks and continue transmission

processing.

8255878 Need ability foradministrator to

manually re-route

integrations from afailed server.

Added process control topic Report Server Failure tothe Configuration & Administration Process Control

Management. This topic allows the user to select a

Scalability application server and report its failure.This, in turn,

1. Sets any FRESH transmissions owned by theapplication server to REDO. A Redo process running

on other machines in the cluster will pick up these


5/8

transmissions.2. Clears any OBJECT_LOCK locks held by the failed

machine.3. Notifies all scalability machines that object locks

held by the failed machine are now available. Thisshould allow for transmissions running on the failed

machine to be processed by the active machine(s). Itshould also allow for transmissions blocked on the

active machines to run to completion.

8255881 Weblogic is allowing

JMS messages to floodinto OTM before the

App servers (inScalability) are fully

started. This leads toexcessive exception

logging.

Suppressed handling of JMS messages if OTM is not

past startup. If JMS logging is turned on, eachsuppressed message will still be logged, but no

exception or handling will occur.

8270369 7427816.992 Ready To Ship actionscreen shows wrong

UOM (Value of FT withUOM = M) or (Value of

INCH with UOM = M perthe customer settings).

Used template for picking values based onpreferences. The Ready to Ship, Order Base and

Order Base Ship Unit show the right values postconversion to the new user preference.

8272689 7343157.993 An order release is

configured to include aLoad Configuration

Profile that has aconfiguration to restrict

certain loadingpatterns. This is

configured on the orderrelease's ship unit.

When the shipment iscreated for this order,

the loading patternused is violating the

maximum number ofstacking layers defined

on the LoadConfiguration Profile

assigned to the Order

Release.

Issue has been fixed. Maximum number of stacking

layers is no longer violated.

8275056 Object_lock tablerequires index.

Index on object_lock.owner_sequence has beenadded.

8275102 Object_lock cleanupprocess should be

staged.

Staged a recurring process to remove unknownobject lock records. The process removes unowned

records, older than 1 day. It runs every day at 0500

UMT.


6/8

8289529 7427481.992 Unable to upload anyfile to a document Get a

null pointer exceptionerror.

'Attach Document' UI action for '.jpg' file resulting ina Null pointer exception is fixed.

8308157 7369620.992 When creating a

custom screenset, thecustomized actions arenot used when creating

orders and shipments.

Added the finder set GID to the request for 'Create

Another'. The customized actions are now used.

8311659 Activate port needs to

bind to specific IP formultiple apps on one

box.

We now bind the activate port to the current host.

The host name is parsed from the:glog.scalability.thisMachineURL property along with

the base RMI port. For non-scalability users, theinstaller sets this property to: $appserver.protocol$

$appserver$:$appserver.port so the host is driven bythe appserver property. For scalability users,

thisMachineURL may have been modified to reflect

the current scalability host.

8324205 In Cooperative Routing,

setting the minimumtime between

shipments parameteron the fleet results in

no cooperative routes

being built.

The issue is that the CR Solver was applying the Min

Time Btw Shipments constraint to the first legdeadhead, which is between the start depot and the

start of the first forecast in the CR route. In fact, itwas applying this constraint even when there was no

start depot (in which case the deadhead time is zero,

and thus always lower than any min).The resolution is that the Min Time Btw Shipments

constraint will never be applied to the first deadhead(start depot to first forecast start) or to the last

deadhead (last forecast end to end depot). The sameis true of the Min Distance Btw Shipments. This is

the case regardless of whether there are start/enddepots or not. The Max Time Btw Shipments

constraint will still apply to the first and lastdeadheads, as it did before this fix.

8334817 7405053.992 When an order (withoutorder movement) is

added to a shipmentthen no order

movement is created. Ifthe order is planned to

an order movement andthe order is added to a

shipment, the ordermovement is not linked.

In the first case, an order movement will be created.In the second case, a new order movement will be

created and linked to the shipment.

8338545 7427816.992 The 'calculate totals'and 'copy values'

buttons are broken in

the ready to ship

Index value was not passed correctly so it wasbroken. This has been fixed.


7/8

screen.

8339217 7172691.993 Receive an error when

running clientutil.py

There was an AttributeError error when using the

csvImport command in the ClientUtil.py pythonscript. This issue was caused by changes in internal

functions in python for the more recent versions. The

logic has been updated to use a different function toretrieve the default encoding.

8408129 7512226.992 Unable to install

German, EuropeanSpanish or European

French translations infull install

Added the translations that were missing. Can now

install German, European French, and EuropeanSpanish translations.

8408356 The field 'declaredvalue' on the Order

Release Line or ShipUnit Line is restricted to

8 digits. Consequently,the value cannot be

declared if it exceeds

100 million.

Declared Value on Order Release Line Details cannow accommodate up to 11 digits.

8432211 7414885.994 Even after configuring a

custom job screen setto show up whenever

Job screens are being

accessed, Public JobScreen set is still

shown.

Call to retrieve default Finder Set was missing, so

was picking Public one. Now fixed to pick default.

8432792 Unable to edit ordermovements.

When trying to edit an order movement, screenwhich is not displayed earlier is now displaying.

8443530 7419068.993 Localization of end time

on conditional bookingsecure resources by

planner is wrong

Action "Secure Resources By Planner" is run on a

shipment with conditional booking fields as Pick-upand Delivery times. These times were stored with

user preference timezones rather than the first andthe last stop location timezones. Added a property

glog.tender.cbTimeZoneStopLocationBased (defaultfalse) which when set as true, saves these time

values with location timezones.

Issues Resolved in RU7 for problems faced in SCI:

1. The following error is received when processing integration:

Exception java.sql.SQLException: ORA-00933: SQL command not

properly ended - BUG 7007116 - ADD FLAG TO CONTROL SQLPARSING FOR INTELLIGENT CACHE REFRESH IN DIRECT SQL UPDATE


8/8

2. If you are doing a lot of integration, then yes, this bug is of concernand will start to exceed the Maximum Cursors. + Apply Patch 8668288

- Bug 8668288 - MAXIMUM OPEN CURSORS EXCEEDED ERRORS AREOCCURING DURING INTEGRATION

3. The GMT conversion is not happening when we entered the date

through SCI screen (shipment stop) - Bug 9138014 - STOP TIMES NOTCONVERTED TO GMT (UTC)

4. Bug 6715909. European language translations are not available

Time to install : Since the patch involves changes in all layers (App/Web/DB), we

have to check it in QA before commenting.

Level of testing : Functional (by taking 8 default domains and do normal testing)

Impact : Since the patch involves changes in all layers (App/Web/DB), we have tocheck it in QA before commenting.

Ground work: We need to take backup of all file system level files and DB objectsbefore applying this patch.

Other parties: An ICR needs to be created as part of process to implement thischange in prod.

55CU4RU7 Release Notes

Documents

Transcript of 55CU4RU7 Release Notes