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 |
5432638 |
|
Add fields to the Order Movement Screen Sets (make similar to the existing Order Release) |
Can now add these fields
to an Order Movement screen set, Finder & Finder Results: |
5597767 |
|
The OM_PLANNING status isn't always set to, or staying at, OM_PLANNING_PLANNED - FINAL when planned on a shipment. |
When temporary order movement exists for a given permanent order movement, you cannot run the Move to Shipment action for the order movement. |
5663933 |
|
Two issues: |
1. This is because the screen
was converted from using the applet to using AJAX. AJAX will not return
any document with a '&' in it. We get around this by escaping the
character. |
5685533 |
|
User preferences not loading when user logs in. |
NamingDirectory wasn't being released after uploading a CSV file. This was causing problems with user preferences. This has been changed to release the NamingDirectory after a CSV upload. |
5706140 |
|
Incorrect user role list is given in both agent manager and in change user role. |
User Role cache is now cleared when a User Role is added, modified, or deleted. |
5730404 |
6038415.994 |
RIQ (rate inquiry) XML is not working with multiple transactions in the same XML |
RIQ XML with multiple transactions causing naming directory release is resolved. |
5743329 |
5988402.993 |
When using forced merge on a multistop line haul the forced merge fails. |
Made code changes so that each stop on the combined shipment is evaluated against stops on upstream and downstream shipments that have a dependency on the combined shipment's stop to ensure that the stop times are feasible. |
5757250 |
6015710.993 |
Querying buy shipments from quick links does not retrieve all the shipments. |
This was caused by objects stored in the session that were not being cleaned up. This has been fixed so that when a user searches on shipments after running a SmartLink, old criteria is not being applied. |
5762251 |
6088100.993 |
When using the action - Change Shipment Details - Change Schedule Action, the voyages listed with schedules available with proper dates, the Transit Time is listed as a negative value (-ve) |
The transit time calculation for voyages was changed to ensure that the voyage stop used as the destination has a later sequence number on the voyage than the stop for the source location. |
5837250 |
|
Multiple locations in the XSL files where glogURLPrefix has not been referred to. |
There were a few image and Javascript file references that were not properly prefixed. The OTM code base has been scanned for any missing prefixes and all occurrences have been fixed. |
5839587 |
6095101.992 |
Tender accept by ship units functionality allows use of parameters on specific service providers to invoke a different screen from Online Booking and tendering allowing user to see each ship unit and perform a partial accept. The screen is missing data in the 'Type' column. |
Spelling error in the XSL was fixed. Now able to retrieve and display the Type data. |
5842153 |
6086160.993 |
When VAT is calculated using
the VAT outcome: INTRA_EU_VAT_APPLIES, I am receiving the following error:
|
Changed logic in VAT rule engine that errored with "cause.VAT_MULTIPLE_SERVPROV_CODES" when the service provider was registered in multiple countries, but none of them were the origin country (or destination for imports to the EU). This error occurred when checking if the service provider and customer were in the same country. OTM now returns no service provider country, and the service provider and customer will be considered to not be in the same country. Also, removed an assumption that no VAT registration country was allowing the "service provider and customer" check to pass. This previously only happened if the service provider had no VAT registrations. |
5849313 |
|
Servprov has access to saved query and working list. |
A service provider can now view only his own working list, not any other user's. |
5849936 |
|
Please remove planfrom/planto note in order release screen. |
Removed planfrom/planto note in order release screen. |
5852804 |
6092006.994 |
Correct the error display "What do I do with jobs?" when trying to Calculate Provincial Tax on a bill generated from a job. |
Improved error message indicating VAT calculation is not supported for Job bills. |
5854761 |
6114446.992 |
The Volume field on accept screen ship unit grid is displaying 6 or more digits but should display 2. |
Rounding up the Weight and Volume fields to 2 decimal places and fixed the UOM. |
5859795 |
6128479.992 |
When carrier responds to the tender with pickup date changes (using Tender Response XML), OTM is not calculating / converting the time for pickup date. |
Problem -When converting the pickup date in the tender response, OTM assumes the time is in the local time of the OTM server instance's. Solution -Change has been made to the code so that shipment source location's timezone will be used for the above case when property glog.integration.tenderresponse.shipmentSourceLocationTimeZone sets to true. |
5860843 |
6110380.993 |
SmartLinks do not work for supplemental bill if original bill is consolidated. Get an error. |
Fixed the issue where the shipment action Bill Adjusted Costs was not linking the new adjustment bill to the shipment. |
5865154 |
5784128.992 |
The Assign Rate action is failing to rate because the shipment start time is near midnight of the expiration date of the rate record. The effective/expiration dates are stored and treated as UTC. During the comparison, the shipment start time is converted to UTC, which places it on the other side of midnight. |
The rate finding logic will treat the rate effective and expiration dates as decoupled from timezone, effectively treating them as occurring in the same timezone as the start time of the shipment. |
5868316 |
|
Weblogic security stack leak |
Fixed a memory leak that can occur when the DirectSQL agent action is used. This would eventually result in java.lang.OutOfMemory errors. |
5871027 |
|
User access query performance on initial log in |
The query to get the user access records for a user now uses "union all" instead of "union". This query should perform slightly better for small sets of data but significantly better for large sets of data or complex VPD data. |
5875593 |
|
Bad query in transmission acknowledgement |
This issue was logged in response to identifying a duplicate query which was run during inbound integration processing. The query was used to determine the number of errors that were generated during processing of an inbound integration XML and set the status of the Transmission. The logic has been updated to only run the query once. |
5876740 |
|
Simple tracker getting blank result screen |
Results from prior searches are removed from the session. |
5880012 |
6124010.992 |
The "partial accept quantity" for ship unit from integration is not being propagated. Thus the status not set correctly. |
When an integration XML includes the TendRespAcceptedSU element indicating partial acceptance, the tender will be marked as partially accepted. |
5880171 |
6144786.994 |
Clicking the + icon on shipment gatehouse results screen does not work |
Clicking the + icon on a Gatehouse Result Screen row now displays the row tree. |
5887958 |
6146492.994 |
When a buy shipment has an accessorial code as flow-thru and this cost is based on the stop activity=D, the sell shipment is failing to build with an error. |
You are now able to create a sell side shipment when the buy side shipment contains a flow thru accessorial charge. |
5894057 |
6164665.992 |
Auto invoice matching performance issues |
Improved performance of query that finds shipments to match to an invoice using the match rules. |
5894477 |
6160484.994 |
In an order release screen set results tab, I want to have 3 'Status' columns, each with a different status type. I set this and view the screen set. The same value for one of the types is repeated 3 times. |
If multiple grid flattened columns using the same qualifier (e.g. status type or refnum qualifier or remark qualifier) were set up for a finder, then the finder in certain cases was selecting the same qualifier value. In this example there were 3 columns using the status type qualifier and they all used the same qualifier value, thereby displaying the same result value. This has been addressed. (Not an issue in 5.5). |
5895615 |
6111760.994 |
Shipment total weight & volume are not correctly calculated when SAW- Shipment is linked to order base using agent action |
This has been fixed. |
5901673 |
6135903.992 |
Invoice/bill dates incorrect based on user preference time zone |
Invoice/Bill dates should now be correct based on the user's preference timezone. |
5917186 |
6167768.992 |
When entering a reference number on the features tab of an item, you cannot enter more than 50 characters even though the database allows for 150 characters. |
Item Refnum Value field has been changed from 50 to 150 characters. Also, Item Attribute Value was changed from 50 to 120. |
5921637 |
6115648.992 |
Get the following error when
trying to accept a tender: |
Adding all the notification staging data for TENDER_REDRIVE_INFEASIBLE . |
5942704 |
6219294.992 |
Agent action NOTIFY INVOLVED PARTY would fail when the agent is triggered by a Shipment Event. |
This has been fixed. |
5950352 |
6185686.993 |
Move to shipment action fails to add order movement |
Fixed problem with shipment loading so same original leg order movement can be put on same shipment. |
5966876 |
6138572.993 |
Order bases with order releases assigned to Milestone Monitors were failing to be updated and re-released via integration. |
Monitor profile now allows recycling of business object IDs. |
5982972 |
6257295.992 |
Unable to create a Milestone Tolerance Rule of type Shipment and using the PICKUP APPOINTMENT or DELIVERY APPOINTMENT compare fields. |
The PICKUP APPOINTMENT and DELIVERY APPOINTMENT compare fields have been fixed so that their values match those in the MONITOR_OPERAND_D table. |
5988371 |
6173307.992 |
Unable to update weight and volume on shipment header using XML |
When IsRecalcTotals field set to N in shipment XML, total gross weight and total ship unit count were not reflecting the values set in uploaded shipment XML as supposed to. Resolution. These fields were on the list of fields that always get reset back to original value after the merge with shipment XML content. It's now reflecting values in shipment XML after removing the fields from the list. |
6034034 |
215368.993 |
When trying to bulk plan
an order release, the action fails due to a service time error: |
Fixed problem in WorkPeriodSchedule that was causing improper NULL returns from NextAvailableWorkPeriod() in certain narrow timewindows |
6045380 |
6294407.993 |
Phone/fax displayed in wrong fields on tender screen. |
The generated XML driving this page had information in the wrong fields. As a result Fax was pointing to Phone2, Phone1 was pointing to Fax, and Phone2 was pointing to Phone1. This has been fixed. |
Issue Number |
Support Ticket |
Issue Summary |
Issue Resolution |
5873162 |
|
LTL-split ship unit assignment optimization |
Before LTL Split, the equipment constraints on the orders, leg, and locations are evaluated to determine which equipment to use. Use packing algorithms to enable better packing of equipment. |
glogserver.jar
glog\gc3webapp\WEB-INF\web.xml
glog\oracle\insert_security_roles.sql
weblogic\config\gc3domain\applications\GC3App.ear
apache\htdocs\xsl\comm\navigation.xsl
apache\htdocs\xsl\comm\navigation_blue.xsl
apache\htdocs\xsl\demoui\ResultButtons.xsl
apache\htdocs\xsl\invoice\InvoiceHeader.xsl
apache\htdocs\xsl\invoice\InvoiceStop.xsl
apache\htdocs\xsl\invoice\bolback\BOLBackHeader.xsl
apache\htdocs\xsl\invoice\bolback\BOLBackStop.xsl
apache\htdocs\xsl\material\ItemFeatures.xsl
apache\htdocs\xsl\order\OrderReleaseHeader.xsl
apache\htdocs\xsl\procurement\procurement.xsl
apache\htdocs\xsl\scem\MPPMilestone.xsl
apache\htdocs\xsl\scem\MPTAMilestone.xsl
apache\htdocs\xsl\scem\MPTPMilestone.xsl
apache\htdocs\xsl\scem\MonitorAgent.xsl
apache\htdocs\xsl\scem\MonitorToleranceRule.xsl
apache\htdocs\xsl\shipment\gatehouse\ShipmentGatehouse_ResultBody.xsl
apache\htdocs\xsl\tenderresp\ExecTendAcceptBySSUs.xsl
apache\htdocs\xsl\themes\themesred.xsl
apache\htdocs\xsl\themes\themessilver.xsl
apache\htdocs\xsl\uic\ViewLocationCapacityUsageAction.xsl
apache\htdocs\xsl\workflow\DefaultTenderRedriveInfeasibleHtml.xsl
apache\htdocs\xsl\workflow\DefaultTenderRedriveInfeasibleText.xsl
glog\config\glog.base.properties
glog\glog_resources\glog.uom-metadata.properties
glog\glog_resources\glog\comm\query\QueryResources_xml.properties
glog\oracle\script8\content_glogowner\LOGFILE_DETAIL.csv
glog\oracle\script8\content_glogowner\NOTIFY_FUNCTION.csv
glog\oracle\script8\content_glogowner\NOTIFY_SUBJECT.csv
glog\oracle\script8\content_glogowner\NOTIFY_SUBJECT_STYLESHEET.csv
glog\oracle\script8\content_glogowner\PLANNING_PARAMETER.csv
glog\oracle\script8\content_glogowner\PLANNING_PARAMETER_QUALIFIER.csv
glog\oracle\script8\content_glogowner\STYLESHEET_PROFILE.csv
glog\oracle\script8\content_glogowner\TRANSLATION_D_ERR_en.csv
glog\oracle\script8\content_glogowner\TRANSLATION_D_NOT_en.csv
glog\oracle\script8\content_glogowner\TRANSLATION_D_QUERY_en.csv
glog\oracle\script8\content_glogowner\TRANSLATION_ERR.csv
glog\oracle\script8\content_glogowner\TRANSLATION_NOT.csv
glog\oracle\script8\content_glogowner\TRANSLATION_QUERY.csv
glog\oracle\script8\content_glogowner\V50BP_LOGFILE_DETAIL.csv
glog\oracle\script8\content_glogowner\V50BP_NOTIFY_FUNCTION.csv
glog\oracle\script8\content_glogowner\V50BP_NOTIFY_SUBJECT.csv
glog\oracle\script8\content_glogowner\V50BP_NOTIFY_SUBJECT_STYLESHEET.csv
glog\oracle\script8\content_glogowner\V50BP_PLANNING_PARAMETER.csv
glog\oracle\script8\content_glogowner\V50BP_PLANNING_PARAMETER_QUALIFIER.csv
glog\oracle\script8\content_glogowner\V50BP_STYLESHEET_PROFILE.csv
glog\oracle\script8\content_glogowner\V50BP_TRANSLATION_D_ERR_en.csv
glog\oracle\script8\content_glogowner\V50BP_TRANSLATION_D_NOT_en.csv
glog\oracle\script8\content_glogowner\V50BP_TRANSLATION_D_QUERY_en.csv
glog\oracle\script8\content_glogowner\V50BP_TRANSLATION_ERR.csv
glog\oracle\script8\content_glogowner\V50BP_TRANSLATION_NOT.csv
glog\oracle\script8\content_glogowner\V50BP_TRANSLATION_QUERY.csv
glog\oracle\script8\content_glogowner\xml\manager_layout\invoice.xml
glog\oracle\script8\create_dbpatch_50b.sql
glog\oracle\script8\dbpatch_50b.sql
glog\oracle\script8\insert_security_tables.sql
glog\oracle\script8\pkg\pkg_purge.pkb
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)