This page describes the content of this Service Release and contains the following sections:
Service Release-Specific Installation Instructions describes additional installation instructions (supplementing the standard service release installation instructions) that are specific to this service release.
Database Changes describes any structural changes that were made to the GC3 database and migration notes, if applicable.
Integration Changes summarizes changes to the standard GC3 XML interfaces.
Corrections describes defects that were reported and fixed in the release.
Enhancements lists all the enhancements in this release (excluding those that were customer-specific and not included in the core product).
Updated Files lists all files that have changed.
Customer Support provides contact information if you need assistance with this service release.
Service Releases are cumulative in their content and any corrections/enhancements from previous service releases are also included. You should also review previous release notes for release-specific installation instructions as well.
This topic is intended for GC3 users, DBAs, systems administrators, application consultants, support analysts, and project managers. It assumes a working knowledge of GC3 from a system administration and user perspective.
There are no service release-specific installation instructions for this release. Refer to the standard service release installation instructions.
Note: If you are using location capacity functionality, there may be an issue with this functionality on the Linux platform. If you experience a problem using Linux, you can do the following; however, you should only do this if you are running Linux and encounter a problem.
Edit the following file on your GC3 application server(s):
<gc3_install_dir>/weblogic/config/gc3domain/weblogic.conf
After the line:
wrapper.java.additional.19=-Djava.security.policy=%WL_HOME%/server/lib/weblogic.policy
You then need to restart GC3 for the change to take effect.
In certain high memory usage scenarios, there may be a performance degradation with the new JVM version which requires additional tuning of the JVM. If you have an issue, contact Customer Support.
There are no database changes for this release.
Changes to the integration processing logic can be found below in their respected correction or enhancement description. Changes to the XML schema are as follows:
There are no integration changes for this release.
Issue Number |
TAR Number |
Summary |
Resolution |
5865095 |
6113821.994 |
Search criteria on saved query changes from 'not same as' to 'begins with' |
When refining a query that included a "not same as" operator, that value will remain "not same as" on the re-query. |
5877014 |
6138643.992 |
"Secure Resource by Planner" action missing in action menu for direct buy shipment |
Fixed the shipment view URL in the action result page. |
5915833 |
5998194.993 |
No auto-consolidation for subsequent shipments of dynamic trips |
There were a couple different problems in the code that were preventing the consolidation of two shipments that were on the same shipment graph when the shipment graph also contained a DB shipment (eg. Ground Schedule). These issues have been fixed, thereby allowing this consolidation. |
5925669 |
6140492.993 |
Null pointer exception encountered when service time is infeasible |
The Null Pointer Exception was encountered because the Max Wait Time for a stop had a null value. The code was changed to treat the Max Wait Time as zero when no value is provided. |
5929356 |
6049546.992 |
Multistop failing for order movements (a->b + b->c) |
When building multistop shipments with the Multistop LIFO planning parameter turned Off, a potential multistop shipment had to result in a distance savings over the pair of uncombined shipments. If the distance savings was zero, it was not considered. This was changed to allow the consideration of multistop shipments that result in zero distance savings. Note: A couple years ago, a similar change was implemented, but it only applied to LIFO shipments. With the new changes, LIFO and non-LIFO shipments will both allow zero distance savings. |
5945824 |
6159456.994 |
Build shipment on leg ignores order release constraints |
When creating an order movement, the temporary leg that holds the order movement constraints previously copied everything from the original leg. This would override the order release constraints in some cases. This has been changed so that the temporary leg has no constraints defined initially except the Mode Profile ID. Mode Profile ID is not null in the database. So it is initialized to the value on the order release if specified. Otherwise, it is copied from the original leg. When Transport Mode ID is specified on the order release, it will override the mode profile on the temporary leg if the Mode Profile ID on the leg is the same as the one on order release. |
5962464 |
6219075.993 |
When using the "payant pour" method of rating, OTM selects higher threshold of weight |
UOM value used for the "Payant Pour" calculations no longer use the Math.ceil() function to truncate the value of the MAX of the previous cost bucket. This was causing 200 to be incorrectly increased to 201 in the calculations. |
5962630 |
6198171.993 |
Increase bean count for Order Movement Reference Number |
Order Movement Reference Number bean count has been increased from 50 to 200. |
5982373 |
6258306.992 |
Shipments using dynamic schedules do not have commercial terms copied from order |
INCO terms on order should be copied to dynamic trips as well as consol shipment now. |
5986868 |
6245992.993 |
Shipment reference qualifiers from all domains are shown even if property is set |
Fixed. With this fix, the list of the reference number qualifiers in the drop down list on the shipment event screen will be those visible to the ADMIN user of the shipment domain, regardless of the current user. |
5989379 |
6109375.993 |
Smart link connections between Buy Shipments and Order Releases do not show all orders included in shipments but only the one where you start to arrive to shipment. |
Fixed. All order releases are now returned. |
6008892 |
|
Broadcast tender notification error. When a broadcast tender is accepted, both the winner and the losers are notified. However the messages to the losers should have said "tender withdrawn", not "bid accepted" as shown in the log. |
When a broadcast tender is accepted, both the winner and the losers are notified. With the fix, the messages to the losers now correctly states "Withdraw Broadcast Tender on Shipment ...", not "bid accepted". |
6014149 |
6118568.994 |
Unable to restrict users from seeing queries without bouncing the web server |
Webserver cache was not being cleared when a saved query was updated. This was causing incorrect queries to appear in a finder even when they were marked not 'use in finder'. The code has been changed to clear the cache when a saved query is saved. |
6024886 |
6251095.993 |
E-mail subject line is getting truncated |
The subject line for order release status now says "ORDER RELEASE "ID"- STATUS RECEIVED". |
6025030 |
6249009.994 |
Saved query field limitation if "use in finder" is selected |
The finder was using the default max characters of the picklist. This is now fixed. |
6026733 |
6252854.993 |
Secondary charge incorrectly displayed on shipment group and financials overview |
This was a currency conversion issue. The Secondary Charge Shipment Cost now displays correctly. |
6032833 |
6288228.992 |
Secondary charge shipments have incorrect date |
Changed business logic to copy the arrival and departure dates of the primary shipment to the secondary charge shipment if the location type is "Source to Destination". |
6041905 |
6284723.992 |
When using NMFC class 125.0 in LTL SMC rate, get numberformat exception in rate inquiry |
Fixed issue in rate inquiry where rates were not found for queries with NMFC commodities and NumberFormatException was found in logs. |
6058776 |
6264234.994 |
Gross volume is incorrectly calculated after split |
Add forced recalculation in "split shipment to direct" action to automatically recalculate shipment weight/volume based on s ship units. |
6060238 |
6277127.993 |
Build multistop shipment from 'split shipment' by order movement fails |
The selected order movement was a temporary order movement and it was supposed to be deleted after being planned to shipments, but the logic was still trying to set its status to planned final. This is fixed so that the status of an order movement is set to planned final only when it is not temporary. |
6062133 |
|
Racgrid throws a null pointer exception when base rate record not found |
Rating engine no longer throws a NullPointerException if there is no base rate record defined for a specified master rate. Instead, the rate is flagged as Infeasible. |
6062265 |
6270480.993 |
Auto calculation release method does not calculate weight through the logic |
Fixed. When AutoCalc is selected as Releasing Method and planning parameter Auto Calc Weight Volume is true, OTM calculates the weight and volume based on the packaged item / packaging unit / transport handling unit's weight/volume. |
6080702 |
|
Invoice_equipment_seal.seq_number after 4.5 to 5.0 May migration |
Two issues have been fixed for dbupdate_50b. One is the warning on creating sequence: INVOICE_EQUIPMENT_DETAIL_SEQ_N and the other is the SQL command not properly ended error in running update49740data causing the seq_number in table invoice_equipment_seal not being populated. |
6081343 |
6288154.992 |
'Amount to Pay' value on voucher header not matching with invoice line |
A rounding problem in the 1.4.1 JDK (fixed in 1.5) causes occasional currency rounding issues in OTM. The problem occurs when one of the individual numbers being added is between 2621 and 5242 and has four decimal places ending in 75 (ex. nnnn.xx75). A workaround has been added to OTM to resolve this until the JDK issue is fixed. The workaround can be disabled by setting the glog.business.costFractionDigits.jdkRoundingFix.enabled property to false. |
6125129 |
5982334.992 |
Shipment manager layout assigned to a buy shipment screen set, cost type blank |
The Shipment Cost Type is no longer blank in the Shipment Cost grid on the Shipment Financials tab. The correct option name is also displayed in the grid instead of the option value. |
6131252 |
17606524.600 |
Rate rounding incorrect |
Rate Engine now rounds numbers correctly per the Rounding Interval value |
6151669 |
6330872.994 |
When using custom notification tags on a stylesheet profile, and if this is used in a Milestone monitor message, the tag is not translated |
Custom tags are translated for notifications from Milestone monitors. Note: Make sure that the following property is set to true: glog.notify.supportsSubjectTags |
6186968 |
6372916.993 |
Commodity code gives problems in order template when used. |
Commodity Code now shows the XID rather than the GID. |
6241904 |
|
Net weight per ship unit is not getting saved during an order base creation |
When creating an Order Base by Ship Unit with Releasable checked and AUTO CALC enabled, the order base ship unit weights and volumes may be zeroed out. |
There are no enhancements for this release.
glogserver.jar
glog\gc3webapp\WEB-INF\web.xml
glog\config\maps\ui\*
glog\oracle\insert_security_roles.sql
weblogic\config\gc3domain\applications\GC3App.ear
apache\htdocs\html\help\webhelp\en\*
apache\htdocs\xsl\comm\Fields.xsl
apache\htdocs\xsl\customer\ordreltemplate\CustomerOrdRelEntry.xsl
apache\htdocs\xsl\order\view_OrderReleaseShipUnitData.xsl
apache\htdocs\xsl\uic\ServerActionResult.xsl
apache\htdocs\xsl\uic\shipment\ForceSplitMergeBySShipUnitsInput.xsl
glog\glog_resources\glog.ejb-metadata.properties
glog\oracle\script8\content_glogowner\STYLESHEET_PROFILE.csv
glog\oracle\script8\content_glogowner\TRANSLATION_D_NOT_en.csv
glog\oracle\script8\content_glogowner\TRANSLATION_NOT.csv
glog\oracle\script8\content_glogowner\V50BP_STYLESHEET_PROFILE.csv
glog\oracle\script8\create_dbupdate_50b.sql
glog\oracle\script8\dbpatch_50b.sql
glog\oracle\script8\dbupdate_50b.sql
Contact Oracle support if you need assistance with this service release:
Internet:
https://metalink.oracle.com/
Phone support is provided based on the country you are located in. To find the support number for your region please go to the following link. http://www.oracle.com/support/contact.html
You should also have the following logs available before you call Customer Support:
dbpatch__<version>_<dbsid>_<date>.log (adds/updates data due to minor enhancements or fixes)
update_content.log (inserts/updates PUBLIC data included in the service release)
Copyright © 2001-2007 Global Logistics Technologies, Inc. All Rights Reserved.