Oracle Transportation Management Release Notes 5.5 Consolidated 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 installation instructions) 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 with this roll up.

Note: Consolidated updates are cumulative in their content and any corrections/enhancements from previous consolidated updates are also included. You should also review previous release notes for release-specific installation instructions as 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 <filename>. To uninstall: java -jar <filename> uninstall. To see the special instructions run: java -jar <filename> 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.

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 current host. 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, limits allocation 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 is FALSE. glog.tender.cbTimeZoneStopLocationBased: Controls whether time zone values are saved with the values of the location (TRUE) or the user preference values (FALSE). Default is FALSE.

Enhancements
There are no enhancements for this release update.

Corrections
Issue TAR Number Number 7217620 6898094.993 Summary Resolution

Consol-deconsolidation The issue is that, in a multileg itinerary, the shipment scenario not consolidation of orders on a leg was unnecessarily working as desired constrained when, on the subsequent leg, the orders are 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 order was 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. Show routing options gives different results between optimize and show options. Before the fix, service provider GID, transport mode, rate offering, and rate geo were not properly populated onto shipment (via LegOption) when CaculateRate is unchecked on the itinerary. This is now fixed.

7702675

7223987.993

7829960

7366925.992

RateWare is returning The link to SMC Rateware will now use the currency rates in CAD (Canadian GID on the base rate offering to determine the

currency) as expected currency of the results returned from a rating but OTM is treating this request. as USD. 7833604 File not found error on performing 'ready to ship' and 'confirm to ship' 7136971.994 Planning not adhering to service provider constraint When creating an invoice the weight is shown correctly but when saved shows incorrectly. UOM and Base mix-up. Commercial Invoice By Order report cannot be formatted: throws elasticity errors, due to large data and is not published on the user interface. Ship units lost when splitting an order movement off a shipment 7332837.992 There is no longer a "File Not Found" error when performing the 'Ready to Ship' and 'Confirm to Ship' actions. Modified to check the service provider on the rate offering and rate record of the itinerary leg to match with the service provider constraint on the order. When saving an invoice/bill the Weight and Volume fields were always being saved with the default UOM. This has been fixed to save the correct UOM.

8139518

8201658

7304590.993

8204749

To resolve the issue, the report has been checked for elasticity of various columns to accommodate large data; elasticities of various columns have been changed to 'expand', to allow them to accommodate large data.

8205538

Modified so that the to-be-splitoff ship units are not removed from the order movement if they constitute the entire order movement, because the order movement itself (along with the SSUs) will be split off from the shipment

8207518

On accepting the The user default screen set shall be selected. tender, the result page been displayed shows the Shipment ID. When the Shipment ID is clicked, it picks the application default finder set instead of the user default finder set. App server to app server communication errors When an app server restarts, it updates network topology on each app server and webserver in the scalability network. This has been fixed to update not only routing maps but also global machine lists used for diagnostics. When backtrackDrive is on, if service time infeasible or 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

8211768

8217416

7319618.992

Rate inquiry issue: When there is an Infeasible Solution for any leg of the

shipment, client wants the result to be the same as no solution that is "No Rate and Route Found" message. 8223697 7316017.994 When using Container Optimization with PATTERN BASED OPTIMIZE, the equipment is not being fully utilized. OTM was picking STANDING NESTED instead of STANDING STRAIGHT in some cases. Modified the code that compared these two solutions to further look at the remnant length and width to decide whether STRAIGHT or NESTED is better. The change resulted in one equipment when the scenario was tried again. Also added an exception when the diameter of the cylindrical ship unit is mistakenly not specified.

8234546

6834008.993

Retender going to more Fixed. After retender servprov with equipment expensive carrier -first group, the next cheapest rate will be used. preferred TAllocation.toString() method can log excessive output in some of the loops, especially with consolidated invoices when there are many shipments and/or many ship 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 in the past.

8239001

8247766

7339140.993

When an order release New Line Item button will no longer appear on the is copied that contains Line Item tab when copying an existing order Ship Units, the "New release. Line Item" button should not be displayed. This button should be removed. Cleanup object lock on When an application server restarts, it now: restart of an app 1. Clears any OBJECT_LOCK records it owns. server. 2. Notifies all other scalability servers that the locks are now available. This allows any waiting servers to secure the locks and continue transmission processing. Need ability for administrator to manually re-route integrations from a failed server. Added process control topic Report Server Failure to the 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 the application server to REDO. A Redo process running on other machines in the cluster will pick up these

8255875

8255878

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. This should allow for transmissions running on the failed machine to be processed by the active machine(s). It should also allow for transmissions blocked on the active machines to run to completion. 8255881 Weblogic is allowing JMS messages to flood into OTM before the App servers (in Scalability) are fully started. This leads to excessive exception logging. 7427816.992 Suppressed handling of JMS messages if OTM is not past startup. If JMS logging is turned on, each suppressed message will still be logged, but no exception or handling will occur.

8270369

Ready To Ship action Used template for picking values based on screen shows wrong preferences. The Ready to Ship, Order Base and UOM (Value of FT with Order Base Ship Unit show the right values post UOM = M) or (Value of conversion to the new user preference. INCH with UOM = M per the customer settings). An order release is Issue has been fixed. Maximum number of stacking configured to include a layers is no longer violated. Load Configuration Profile that has a configuration to restrict certain loading patterns. This is configured on the order release's ship unit. When the shipment is created for this order, the loading pattern used is violating the maximum number of stacking layers defined on the Load Configuration Profile assigned to the Order Release. Object_lock table requires index. Object_lock cleanup process should be staged. Index on object_lock.owner_sequence has been added. Staged a recurring process to remove unknown object lock records. The process removes unowned records, older than 1 day. It runs every day at 0500 UMT.

8272689

7343157.993

8275056 8275102

8289529

7427481.992

Unable to upload any 'Attach Document' UI action for '.jpg' file resulting in file to a document Get a a Null pointer exception is fixed. null pointer exception error. When creating a Added the finder set GID to the request for 'Create custom screenset, the Another'. The customized actions are now used. customized actions are not used when creating orders and shipments. Activate port needs to bind to specific IP for multiple 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, 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. The issue is that the CR Solver was applying the Min Time Btw Shipments constraint to the first leg deadhead, which is between the start depot and the start of the first forecast in the CR route. In fact, it was 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 same is true of the Min Distance Btw Shipments. This is the case regardless of whether there are start/end depots or not. The Max Time Btw Shipments constraint will still apply to the first and last deadheads, as it did before this fix.

8308157

7369620.992

8311659

8324205

In Cooperative Routing, setting the minimum time between shipments parameter on the fleet results in no cooperative routes being built.

8334817

7405053.992

When an order (without In the first case, an order movement will be created. order movement) is In the second case, a new order movement will be added to a shipment created and linked to the shipment. then no order movement is created. If the order is planned to an order movement and the order is added to a shipment, the order movement is not linked. The 'calculate totals' and 'copy values' buttons are broken in the ready to ship Index value was not passed correctly so it was broken. This has been fixed.

8338545

7427816.992

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 python script. 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 to retrieve the default encoding. Added the translations that were missing. Can now install German, European French, and European Spanish translations.

8408129

7512226.992

Unable to install German, European Spanish or European French translations in full install

8408356

The field 'declared Declared Value on Order Release Line Details can value' on the Order now accommodate up to 11 digits. Release Line or Ship Unit Line is restricted to 8 digits. Consequently, the value cannot be declared if it exceeds 100 million. 7414885.994 Even after configuring a Call to retrieve default Finder Set was missing, so custom job screen set was picking Public one. Now fixed to pick default. to show up whenever Job screens are being accessed, Public Job Screen set is still shown. Unable to edit order movements. 7419068.993 Localization of end time on conditional booking secure resources by planner is wrong When trying to edit an order movement, screen which is not displayed earlier is now displaying. Action "Secure Resources By Planner" is run on a shipment with conditional booking fields as Pick-up and Delivery times. These times were stored with user preference timezones rather than the first and the last stop location timezones. Added a property glog.tender.cbTimeZoneStopLocationBased (default false) which when set as true, saves these time values with location timezones.

8432211

8432792 8443530

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 SQL PARSING FOR INTELLIGENT CACHE REFRESH IN DIRECT SQL UPDATE

2.

If you are doing a lot of integration, then yes, this bug is of concern and will start to exceed the Maximum Cursors. + Apply Patch 8668288 - Bug 8668288 - MAXIMUM OPEN CURSORS EXCEEDED ERRORS ARE OCCURING DURING INTEGRATION The GMT conversion is not happening when we entered the date through SCI screen (shipment stop) - Bug 9138014 - STOP TIMES NOT CONVERTED TO GMT (UTC)

3.

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 to check it in QA before commenting. Ground work: We need to take backup of all file system level files and DB objects before applying this patch. Other parties: An ICR needs to be created as part of process to implement this change in prod.