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.
Next Service Release shows the date of the next scheduled service release.
Technical 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.
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. 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.
Table |
Column |
DataType |
VOYAGE |
SERVPROV_PROFILE_GID |
VARCHAR2(101) |
Table |
Column |
DataType |
GENERAL_LEDGER_CODE |
GENERAL_LEDGER_XID |
VARCHAR2(101) |
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 service release.
G-Log Issue |
Support Ticket |
Issue Summary |
Issue Resolution |
55060.5.0 |
|
Please remove old agent action "Order Release - Mod - Propagate Ship Unit" |
Removed agent action ORDER RELEASE - MOD - PROPAGATE
SHIP UNIT. Agents referencing the action will be modified to use action
ORDER RELEASE - MOD - |
55722.5.0 |
|
Mediation blocks agent execution |
Added a new workflow property, |
56142.5.0 |
|
TransactionProcessor Issue Not Setting Transaction Status to ERROR |
Mark transaction status as "ERROR" when exception is thrown from processing the Transaction |
56682.5.0 |
|
Replace use of DCOracle2 with cx_Oracle |
Modified the python logic to use the cx_Oracle module for the db.xml functionality. |
56721.5.0 |
|
Buy Actuals from Quick Links screen does not work correctly. |
The correct Shipment GID should now be displayed from using the Quick Links. |
56729.5.0 |
|
Incorrect Total Weight and Total Volume on Order Releases |
Fixed a bug where a TransOrder XML specified ship unit
line weights and volumes |
57483.5.0 |
|
New User Level not showing up in drop-down when creating a new User Role. |
Cache is now cleared when creating a new Level. |
57582.5.0 |
|
Can Responsible Party on Order Base Event screen be changed to not cache ? |
Added support for per-user event trees. To turn on user caching instead of domain caching, set glog.eventreason.cacheBy=user |
57604.5.0 |
|
Select multiple invoices - then select Auto-approve adjusted costs. It only shows one invoice as being processed. |
Changed invoice action Auto Approve Adjusted Costs to support selecting multiple invoices. |
57645.5.0 |
|
0 cost invoices will not auto-approve |
Removed a validation that would not allow auto approval
of invoices matched to |
57663.5.0 |
16150906.6 |
Gross Weight/Volume show under Net Weight/Volume |
Logic that sums the ship unit line weights and volumes
up to the order release |
57710.5.0 |
16150980.6 |
Cannot modify an order base that has 2 ship unit lines with attribute qualifiers on them - Cannot add the ORDER_RELEASE_LINE_ATTRIBUTE record. |
Add existing column ITEM_FEATURE_VALUE as part of the
primary keys for the following
tables. So, we allow the same item has the same feature with different
values. |
57716.5.0 |
|
Rate Cost user interface throwing error when the same equipment group is in multiple domains |
Rate Geo Cost will now remember which GID you selected. |
57726.5.0 |
16151062.6 |
Cannot change equipment groups if going from 2 compartments to 1 (rail shipment) |
Cannot perform this action is either "from" or "to" equipment group has more than 1 compartment error out. |
57731.5.0 |
16151074.6 |
Add Shipment Event. Ship Unit Spec ID is missing |
In Add Shipment Event screen, the Ship Unit Spec ID field displays the value of Transport Handling Unit (THU) |
57769.5.0 |
|
Allocating cost of a NFRC shipment from Job Details is throwing a NullPointer exception |
Allocating a NFRC shipment will no longer throw a NullPointer exception in ShipmentLoader.loadSEquipments() |
57801.5.0 |
|
Saved queries are showing up in finder screen of the respective screen set. |
Updated to logic to eliminate saved query entries from finder screen which are not intended for. |
57834.5.0 |
|
Error Message when selecting more than 23 lines in Ready for Shipment Screen |
Changed the redirect url method to check the length of the primary keys if 10 or more are selected. Also, changed the Result Header stylesheet to call the regular javascript method when there is only one Action button that is displayed on the Result Screen. This method redirects to the ResultServlet. |
57848.5.0 |
|
Incorrect Planning Parameter Set Used |
Changed planning parameter helper to make sure ThreadLocal storage is only used when the calling business process specifies a planning parameter set that is different from the domain default set. |
57849.5.0 |
|
fractional negative wait time being calculated on stop |
Modified TShipmentStop's computeTotalStopTime method to round the number of seconds. |
57863.5.0 |
16151154.6 |
java.lang.NullPointerException when an agent is called twice at the same time. |
Fixed the primary key class code generator to remove the race condition that created null pointer exceptions. |
57869.5.0 |
|
Secondary charges not included on the Financial Overview for order base |
Same reason as 55142.4.5. |
57872.5.0 |
|
'Generate Excel' link on HTML report opens text window instead of MS-Excel |
Clicking on Generate to excel opens up Excel Spreadsheet. |
57874.5.0 |
|
Error with Procurement Reports generated with 'begins with' operator |
Reports Run with "Begins With" as the parameter selection come back with correct data. |
57876.5.0 |
|
Service time is failing when end of activity on rate service calendar is equal to the beginning activity on location calendar |
The main problem is shifting between LOAD and PICKUP
in the code that led to a |
57943.5.0 |
|
Some not all of the ROD scripts had hard-coded passwords, all clients don't use the default passwords so we need to make the scripts so that the clients can enter their usernames and passwords. |
No default password is used now. |
57972.5.0 |
16150114.6 |
Facility to specify content type and charset encoding in cURL linux integration command |
The client has to specify "charset=encoding"
when posting to |
57993.5.0 |
|
BolAcceptPlannedEstimate is not raised on Buy Actuals from Smart Links |
The topic BolAcceptPlannedEstimate is raised each time. |
58005.5.0 |
|
Unable To Find Shipment error accepting tender as dispatch location user |
Bug 55935.5.0. already fixed this issue. |
58035.5.0 |
16151842.6 |
Total Billed Amount on Order Release Line allows only 12 digits while database allows more - Customer needs up to 25 digits, at least for JPY values. |
The XSL version has been changed to allow 9 digits before the decimal and 6 digits after the decimal (e.g. 123456789.123456). The cust screen version was not changed since the users can customize that themselves. |
58063.5.0 |
|
Class not found exception when attempting to add a contact to a Service Provider |
Let the stylesheet point to NonPrimaryContactQueryFinderModel. |
58102.5.0 |
|
ACTION_ARG.ARG_VALUE is 4000 chars in DB but only takes 100 on screen |
Increased the max size of the text field to 4000 to correspond with the database. |
58150.5.0 |
16151956.6 |
Include ability to select the communication method when adding letter of transmittal documents. |
When adding a document to the LOT, the user can specify the communication method along with the contact. This is copied to the document party record. If no method is specified, BY CONTACT is used. |
58182.5.0 |
16152050.6 |
UOM Type is needed in Global Classification Response XML. |
Modified to accept UOM type from the response XML and save the information into order release lines. |
58237.5.0 |
16152122.6 |
SQL error when viewing Order Release Line (from ship unit) |
Fixed. The V button has been removed for order release line ID. |
58258.5.0 |
|
Need to open up getGrantedDomains for query optimization. Related to 48700.4.0 |
Opened up the retrieval of granted domains to all users. This allows status query optimization to be used by everyone. |
58328.5.0 |
16152250.6 |
Run button is missing from procurement action utility: syncDomainData |
Tested this and it is working now. |
58330.5.0 |
16151620.6 |
Equipment not assigning correctly through Agent action Book With Internal NVOCC |
When creating a buy shipment from the sell shipment, the buy shipment will honor the sell shipment's equipment group. The leg on the buy itinerary needs to be primary. |
58333.5.0 |
|
Releasing OB by Line Item using Actions is doubling the quantities. |
Fixed the doubling problem when running the Release Lines actions from the Order Base. |
58344.5.0 |
|
Using 'U' transaction code does not update Order Base Reference numbers |
Fixed the update error when passing in order refnum generic status update with transaction code "U" |
58364.5.0 |
16152206.6 |
Error when merging 3 or more shipments |
The merge problem for more than 2 shipments should be fixed now. |
58372.5.0 |
16152330.6 |
Custom Freight forwarding UI does not show Hazardous flag while the default Freight Forwarding UI does |
Hazardous flag now appears on customized Ship Unit Line screen. |
58381.5.0 |
|
Lane summary column headers are out of sync with data |
Fixed the problem with the out-of-sync columns. |
58443.5.0 |
16152332.6 |
Transport Mode on manually created Order Movement (Sell) is ignored in the Sell Shipment |
If transport mode is specified on a manually created order movement, do not overwrite it with the mode profile on the leg. |
58444.5.0 |
16152354.6 |
Payment Terms are not getting copied from Manually created Order Movement to Sell Shipment |
Fixed the null pointer error, so the apply Payment Terms logic would continue on to reach the part where it tried to get the Payment Code from the Order Release. |
58458.5.0 |
16152434.6 |
Custom FFORD - Freight Forwarding screen will not allow refnum changes |
Can now edit Freight Forwarding Cust Screen Refnums without error. |
58469.5.0 |
16152438.6 |
Using a Reference Value (P) psuedo field in a custom screen set copied from S_SHIP_UNIT PUBLIC screen set causes null pointer |
Added missing properties to file that controls grid flattened fields. |
58587.5.0 |
16152546.6 |
Adding a new Shipment Cost on a SAW using N or I transaction code fails |
Fixed the null pointer exception when passing in shipment cost with transaction code "I" and without ShipmentCostSeqno |
58592.5.0 |
|
Add back the call of VPD.expandWhereClause() to allow external predicates |
Add back the call of VPD.expandWhereClause() to allow
external predicates. |
58615.5.0 |
|
Rate offerings and corporate profiles |
Fixed problems with the cached details sometimes getting corrupted for the following objects: Corporation profiles, Flex Commodit Profiles, Itineraries, Itinerary Profiles, INCO Term Profiles. |
58618.5.0 |
|
Online Booking+tendering only displays the 'TRAILER_ID' refnum qual |
Changes made to files TenderRespAdaptor and FindTenderQuery. |
58629.5.0 |
|
Problem with FINDER_LINK table data |
When a user runs the tree node on a BUY_SHIPMENT or SELL_SHIPMENT based finder set, we search the database for FINDER_LINKs that are associated with the SHIPMENT query_table_gid. This will bring back the correct results. |
58650.5.0 |
16152542.6 |
Consolidation Type from OR 's are not getting copied to Jobs related to Sell Shipments |
The consolidation type is now set based on the first order release when a job is created. |
58658.5.0 |
|
Beans caching details cause intermittent bad results |
Fixed problems with the cached details sometimes getting corrupted for the following objects: Corporation profiles, Flex Commodity Profiles, Itineraries, Itinerary Profiles, INCO Term Profiles. |
58698.5.0 |
|
Rating engine failed when build direct, but passed for same rate in bulk plan. |
Shipment start time is being set to 1 year in the past rather than earliest possible start time the shipment can leave. This is happening (in shipment builder) when leg option start time (which is set to early pick up = 1 year in the past if null) is being assigned to the shipment start time. Changed the code so that shipment start time is gotten from another API getEarliestPossibleShipmentStartTime() that eliminates the possibility of assignment of a date one year in the past. |
58702.5.0 |
16152544.6 |
Assign Rate UI Shipment Action Removes the Vessel ID, GL Code and Payment Method Code from the Sell Shipment |
The Vessel ID (and Voyage ID) assigned to a shipment will no longer be overwritten by new service time results if those fields already have values. |
58723.5.0 |
16152588.6 |
Received Ship Unit Count shows 0 instead of NULL when received weight shows null. |
Business Logic changed from 0 to null in the EJB and
made relevant changes in XSL to view the same. |
58731.5.0 |
16152730.6 |
Auto assignment rule pre-qual criteria |
Prequal dropdown now retains current value correctly. |
58747.5.0 |
16152780.6 |
Order Release Screen Set is missing Source/Dest Country Code - 4.5 has it |
Source Country Code and Destination Country Code are once again available as an option on the Result tab of the ScreenSet UI. |
58763.5.0 |
|
Add help link to the Service Provider Insurance Policy page. |
Fixed the help link. |
58820.5.0 |
|
Add additional values to the Order Movement Finder Result Screen Set |
Fixed, now the Order Movement Ref Number and Zone fields for origin and destination can be added to Finder Result Screen. |
58821.5.0 |
16152720.600 |
Domain is overwritten when replacing the buyer template on an order release |
OTM now keeps the original domain after applying buyer template. |
58833.5.0 |
|
Potential connection leak in persistence ChildrenLookUp class |
Make GC3 persistence engine's code more connection safe in terms of resource leaking. |
58859.5.0 |
|
Display issues with the Tender Update screen |
Servprov Remarks now displayed on More shipment info
page. |
58900.5.0 |
|
Cannot change sort order in Saved queries |
The sort sequence is now being saved to the database. |
58940.5.0 |
|
Increase Consolidated invoice timeouts |
Increased the bean timeouts from 1 to 600 seconds for invoice related records to improve performance allocating a consolidated invoice. |
58942.5.0 |
|
Consolidated Invoice Allocation Performance Improvements |
Improved allocation performance, mainly for vouchers
of consolidated invoices |
58943.5.0 |
|
Order Base OMD Agent Action |
The 'Exclude Orders In Executed State' flag for the Order Base agent action 'ORDER BASE - MOD - FULL IMPACT' has been enhanced to support the ability for users to order-ride the condition for orders to be excluded via a saved query for the status functor 'FindOrWithoutReviewedExecuteBuyShipments'. |
58944.5.0 |
|
Port of Exit Value is not sent in ITL AES Transmission XML |
Added new element PortOfExit to the AES XML file. The element is mapped to database field shipment.port_exit_loc_gid. |
58975.5.0 |
|
OR OMD - Propagate Qty |
It now propagates net weight and net volume on ship unit as well as item package count, weight and volume on ship unit line. |
58977.5.0 |
|
OR OMD - Propagate Quantities Wrong results |
Propagate of count will be applied to only buy side shipments, not sell side shipments. |
59047.5.0 |
SR 5305234.992 |
deleteOrderMovements Error |
Modified the code so that only those shipments that are related to the orders to be unassigned will be checked for the RESERVATION_CLOSED status. |
59077.5.0 |
|
Need more intelligent lane summary builder |
Procurement now includes the ability to consolidate lanes while building a lane summary. |
59103.5.0 |
5314050.992 |
VOUCHER table has non-indexed-foreign-key tables |
Added indexes to resolve dead lock issue. |
59115.5.0 |
|
View Financials shows no records when there are records |
Special characters are now encoded so they will work with AJAX. |
59131.5.0 |
5327702.992 |
Rating engine was not calculating rate correctly when multiple offerings using different SMC Bases were valid. |
Rating now calculates rate correctly for multiple offerings using different SMC bases. |
59217.5.0 |
|
Add WorkPeriodSchedule to CacheClearServlet |
Added WorkPeriodSchedule to glog.webserver.servlet.cacheclear.CacheClearServlet |
59230.5.0 |
|
PackagedItemRefnum and OmrShipment should be 500 |
OmrShipmentBean is set to 500 |
59352.5.0 |
5399240.993 |
Need to update the bean count for EJB.ORDERRELEASETREVENTCONTACT to 200 |
Max Beans in Cache set to 200 for OrderReleaseTrEventContact bean. |
G-Log Issue |
Support Ticket |
Issue Summary |
Issue Resolution |
57406.5.0 |
|
Add the Service Provider Profile Field and Logic to the Vessel Schedule |
Added service provider profile GID on voyage. A voyage would be compatible with a shipment when the shipment's service provider is the same as the voyage's service provider specified in service_provider_gid on voyage or is one of the service provider specified by the servprov_profile_gid on voyage. |
57746.5.0 |
|
BeanCacheServlet enhancements |
The bean cache servlet has been enhanced to better monitor
cache performance. In addition to showing statistics for each cache, you
can: |
57903.5.0 |
16151554.6 |
Unable to copy a SELL side shipment |
A separate action for copying sell side shipment has been created. Now the sell shipment can be copied using this action. This can be accessed through sell shipment->actions->Utilities->Copy Shipment. |
58087.5.0 |
|
On Tender Decline Next Best Solution is Carrier & Carrier Equipment Option |
Merged from 4.5 patch. Added load configuration check. Also modified to keep the existing s_equipment record while just changing the equipment_group_gid on it since the 5.0 servprov_tender_equipment table is different and makes this possible. This resolved the 'orphan' s_equipment record issue in 4.5. |
58304.5.0 |
|
Increase General_Ledger_Code XID to 100 |
Make the change to size of 101 for the XID field on GL Code Edit stylesheet. |
58752.5.0 |
|
Allow for Generating Customer Bill(s) in the Revenue section of the Job. |
OTM now allows for generating Customer Bill(s) in the Revenue section of the Job by running the Generate Customer Bill action against the sell side shipments associated with the job. Note that the generated customer bills will be viewed via the sell side shipment smart links and will not be visible from within the Job manager itself. |
58753.5.0 |
|
Change the behavior of the Job Smart Links to always open in a new window |
The Job Smart Links always open in a new window now. |
58931.5.0 |
|
Provide an XSL extension function to query OTM data |
Added a set of new XSL extension functions to retrieve arbitrary data from GC3 for querying. The functions are in the namespace. |
59220.5.0 |
|
Remove pool shipments before saving from bulk plan |
The child nodes of all shipment graphs with deconsolidation
pools will be deleted in bulk plan just before persisting to the database.
Only the initial linehaul with the initial order pickups will be kept.
For the case where orders go on linehauls into the pool, and pool drop
shipments out, only the linehauls will be saved by bulkplan. This logic
is controlled by the following property: |
59283.5.0 |
|
Add new rate basis items to support externally defined shipment distance and duration |
Implemented new rate basis items as requested. This allows users to specify an externally defined actual shipment total distance as well as an externally defined actual shipment total duration and then rate against these values. This has been done by creating new rate basis items that will rate against shipment reference number values. |
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\js\assign\assign.js
apache\htdocs\js\beancache\beancache.js
apache\htdocs\js\finderset\finderset.js
apache\htdocs\xsl\accessorialcost\AccessorialCostBase.xsl
apache\htdocs\xsl\assign\AutoAssignRule.xsl
apache\htdocs\xsl\beancache\beans.xsl
apache\htdocs\xsl\beancache\caches.xsl
apache\htdocs\xsl\beancache\details.xsl
apache\htdocs\xsl\beancache\locks.xsl
apache\htdocs\xsl\beancache\mismatched.xsl
apache\htdocs\xsl\carrier\ServprovPolicy.xsl
apache\htdocs\xsl\detail\GeneralLedgerCode.xsl
apache\htdocs\xsl\document\PrepareDocumentParams.xsl
apache\htdocs\xsl\finder\ResultHeader.xsl
apache\htdocs\xsl\finderset\ActionHeader.xsl
apache\htdocs\xsl\finderset\FinderSetActions.xsl
apache\htdocs\xsl\finderset\FinderSetTree.xsl
apache\htdocs\xsl\finderset\FinderSetTreeNode.xsl
apache\htdocs\xsl\job\JobFinancial.xsl
apache\htdocs\xsl\job\NfrcRule.xsl
apache\htdocs\xsl\order\fford\FFordLineItem.xsl
apache\htdocs\xsl\order\fford\FFordShipUnitLine.xsl
apache\htdocs\xsl\rate\RateGeoCostBase2.xsl
apache\htdocs\xsl\shipment\CommLineItem.xsl
apache\htdocs\xsl\status\ShipmentDetail.xsl
apache\htdocs\xsl\tenderresp\ExecTendAccept.xsl
apache\htdocs\xsl\tenderresp\ExecTendConditionalBooking.xsl
apache\htdocs\xsl\uic\AutoApproveAdjustedCostsResults.xsl
apache\htdocs\xsl\voyage\ViewVoyage.xsl
apache\htdocs\xsl\voyage\VoyageManager.xsl
glog\oracle\script8\DbLocalTimestamp.java
glog\config\glog.appserver.properties
glog\config\glog.base.properties
glog\config\glog.pseudo-field.metadata.properties
glog\config\glog.recalc.properties
glog\config\glog.timezone.properties
glog\glog_resources\glog.ejb-metadata.properties
glog\glog_resources\glog.security.properties
glog\glog_resources\glog\comm\query\QueryResources_xml.properties
glog\oracle\script8\content_glogowner\ACTION.csv
glog\oracle\script8\content_glogowner\ACTION_ARG.csv
glog\oracle\script8\content_glogowner\ACTION_DEF_STATE.csv
glog\oracle\script8\content_glogowner\AGENT_ACTION.csv
glog\oracle\script8\content_glogowner\RATE_GEO_COST_OPERAND.csv
glog\oracle\script8\content_glogowner\RATE_GEO_COST_OP_OWNER.csv
glog\oracle\script8\content_glogowner\TIME_ZONE.csv
glog\oracle\script8\content_glogowner\TRANSLATION.csv
glog\oracle\script8\content_glogowner\TRANSLATION_D_ERR_en.csv
glog\oracle\script8\content_glogowner\TRANSLATION_D_QUERY_en.csv
glog\oracle\script8\content_glogowner\TRANSLATION_D_en.csv
glog\oracle\script8\content_glogowner\TRANSLATION_ERR.csv
glog\oracle\script8\content_glogowner\TRANSLATION_QUERY.csv
glog\oracle\script8\content_glogowner\V50BP_ACTION.csv
glog\oracle\script8\content_glogowner\V50BP_ACTION_ARG.csv
glog\oracle\script8\content_glogowner\V50BP_ACTION_DEF_STATE.csv
glog\oracle\script8\content_glogowner\V50BP_RATE_GEO_COST_OPERAND.csv
glog\oracle\script8\content_glogowner\V50BP_RATE_GEO_COST_OP_OWNER.csv
glog\oracle\script8\content_glogowner\V50BP_TIME_ZONE.csv
glog\oracle\script8\content_glogowner\V50BP_TRANSLATION.csv
glog\oracle\script8\content_glogowner\V50BP_TRANSLATION_D_ERR_en.csv
glog\oracle\script8\content_glogowner\V50BP_TRANSLATION_D_QUERY_en.csv
glog\oracle\script8\content_glogowner\V50BP_TRANSLATION_D_en.csv
glog\oracle\script8\content_glogowner\V50BP_TRANSLATION_ERR.csv
glog\oracle\script8\content_glogowner\V50BP_TRANSLATION_QUERY.csv
glog\oracle\script8\content_glogowner\V50BP_WORKFLOW_PARAM.csv
glog\oracle\script8\content_glogowner\WORKFLOW_PARAM.csv
glog\oracle\script8\content_glogowner\xml\finder_set\sell_shipment.xml
glog\oracle\script8\create_dbpatch_50b.sql
glog\oracle\script8\create_dbupdate_50b.sql
glog\oracle\script8\create_triggers.sql
glog\oracle\script8\dbpatch_50b.sql
glog\oracle\script8\dbupdate_50b.sql
glog\oracle\script8\dbupdate_rod.sql
glog\oracle\script8\pkg\create_index.pkb
glog\oracle\script8\pkg\create_index.pks
glog\oracle\script8\pkg\create_table.pkb
glog\oracle\script8\pkg\foreign_key.pkb
glog\oracle\script8\pkg\pkg_prevent_mutation.pks
glog\oracle\script8\pkg\primary_key.pkb
glog\oracle\script8\procure\procurement.pkb
glog\oracle\script8\procure\procurement.pks
glog\reports\procurement_sol_eval_by_lane.rdf
glog\reports\procurement_sol_eval_by_lane_excel.rdf
utils\integration\python\sql2xml.py
utils\integration\python\xml2sql.py
The next Service Release is scheduled for July 2006.
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-2006 Global Logistics Technologies, Inc. All Rights Reserved.