Oracle Fusion Cloud Transportation and Global Trade Management 25A Weekly Update Bundle: OTM_25A-20250404
Note: Update bundles may include security issues as required.
Note: Update may include technology stack version changes and critical patch updates as required.
Enhancements
Oracle Transportation Management
| Issue Number | Summary | Resolution | 
|---|---|---|
| 20250131 | ||
| 37282733 | If an order contains multiple ship units that has to be picked up and delivered to different locations, the ship unit activities and stops are sent in the request to Oracle Business Network. However, there is no clear relationship to explain which ship unit corresponds to each stop. For example, if there are two stops and four ship unit activities (Pick-up, Pick-up, Drop-off, Drop-off), there is no way to determine which activities correspond to which stops. As a result, only the first two activities are considered, based on the number of stops. To establish a relationship between the ship unit activities and stops, a new Rate Basis Items (RBIs), "Ship Unit Stop Number," needs to be introduced. This will define the stop numbers for each of the ship units. | To fix this issue a new Rate Basis Item, Ship Unit Stop Number, has been introduced which retrieves the stop numbers of the ship units. | 
Corrections
Oracle Transportation Management
| Issue Number | Summary | Resolution | 
|---|---|---|
| 20250404 | ||
| 37751911 | A change was made in 25A to use a default HTTPS Handler instead of explicitly specifying the HTTPS Handler. This HTTPS Handler class is used to create the HTTPS connection to another server. It was later realized that the default handler fails to connect to a server that does not provide a full certificate chain. Having a server return a full certificate chain is best practice in the security industry but not a requirement. | Reverting the changes made in 25A that causes an SSL certificate validation error. This validation error occurs when the target system does not return the full certificate chain. Note: As a best practice, is it recommended to return the full certificate chain and any target systems should be updated to return the full certificate chain if they currently do not. | 
| 37767162 | The translation text for some labels incorrectly contain question marks. | The translation text has been corrected. | 
| 20250328 | ||
| 37556176 | If you copy the SHIPMENT manager layout, change the Calculate Totals field to READ ONLY, and use the layout from a screen set, the scroll bar on the side of the screen is removed. | The scrolling issue on the Shipment manager caused by the read-only status of Calculate Totals field is fixed. | 
| 37637277 | The OAUTH authentication is failing when retrieving a new access token. Oracle Transportation Management expects a numeric value for the "expires_in" attribute in the access token, which indicates the duration in seconds after which the token will expire. The Azure OAUTH implementation is returning new access tokens which use a string rather than numeric values for the "expires_in" attribute. Oracle Transportation Management cannot process the string value for the "expires_in" attribute. | Oracle Transportation Management now supports string values for the "expires_in" attribute in new access tokens. A string value for the "expires_in" attribute in an access token must only contain digits (e.g. "3599") and correspond to a numeric value indicating the token's expiration duration. | 
| 37641023 | An error is shown during ETL when executing the table INCR_W_OPEN_TENDER_CARRIER_PERFORMANCE_F. | This issue is now resolved. The table INCR_W_OPEN_TENDER_CARRIER_PERFORMANCE_F will be executed without an error during ETL. | 
| 37675623 | The "Version" and "Optional Until" fields on the IMPROVE DATA QUEUE HANDLING OF CONNECTION ERRORS optional feature are reversed. | Corrected the "Version" and "Optional Until" fields on the IMPROVE DATA QUEUE HANDLING OF CONNECTION ERRORS optional feature. | 
| 37691644 | If you create multiple release instructions while running the action "Order Base Line Packing" multiple times on order base lines, and delete any release instruction, and again run the "Order Base Line Packing" action, the application faces an error. | The application now considers the release instruction with the highest sequence number and then adds 1 (one) and uses that as the next sequence number for the order base line. This resolves any issues that may occur if the order base line has multiple release instructions, and some of the release instructions have been deleted. | 
| 37693516 | When the optional feature "ALLOW SSU CREATE AND UPDATE WITH SHIPMENT VIA REST" is enabled, there is an error when you create a shipment child resource, such as reference numbers. | This issue has been resolved. | 
| 37710285 | The source and destination tags on the order movement do not populate values when you plan a multi-stop order release. | The source and destination tags now populate correct values when you plan a multi-stop order release. | 
| 20250314 | ||
| 37565011 | The application only tracks shipments having allocation types that are used in planning. | The application now supports allocation types that are not used in planning. As a result, commitment allocations with allocation types other than SHIPMENT, Twenty-Feet Equivalent Unit (TEU), Forty-Feet Equivalent Unit (FEU), and Equipment Reference Unit (ERU) will also track the number of shipments allocated to them. | 
| 37584320 | When you try to upload rates using rate load definition, the application creates accessorial cost even if there are empty values in the appropriate cells of the spreadsheet, and the upload fails with an error. | The application does not create accessorial cost if there are empty values in the cells, and now the rates upload successfully. | 
| 37619438 | Database connection instability can result in excessive delay in data queue processing and loss of data queue threads. | Added the optional feature, IMPROVE DATA QUEUE HANDLING OF CONNECTION ERRORS, to better handle possible connection timeouts and instability in data queue polling. This feature is opted out by default. When opted in, network timeouts are reduced from 15 minutes to 15 seconds for data queue polling. Timeout on the poller query is reduced from 5 minutes to 10 seconds. This ensures that a connection in a bad state will be reestablished within 15 seconds. Oracle recommends using the optional feature. To allow more granular control of data queue connection handling, the following properties can be used when the optional feature is opted out: 
 Note: Any connection timeouts and reestablishment logging is now available in the exception log. | 
| 37639737 | Using the Finder Set for a partial match in the Mass Update window for Enhanced Workbench throws the following error: "The value ***** entered for field ******* does not match a valid record". | This issue is now resolved. | 
| 20250307 | ||
| 37645345 | When running the action "Allocate Shipment", memory leak happens, which eventually leads to "Out of Memory" exception. | Fixed memory leak issue while executing allocation of shipment or voucher. | 
| 20250228 | ||
| 36634591 | Unable to bid on spot rates and broadcast tenders in the mobile application when the service provider is in a sub-domain. A "Bid could not be submitted." error appears in this situation. | You will now be able to bid on spot rates and broadcast tenders in the mobile application when the service provider is in a sub-domain. | 
| 37383278 | When you run a rate inquiry for passenger flights, the application does not return results. | Introduced a new property "glog.riq.useKnownShipper", which is set to true by default. When you run rate inquiry, the application returns results for passenger flights also. If you want to change to the old behavior and do not want to see the results of passenger flights, set the property to false. | 
| 37418186 | The validation for flex commodity code when processing Rate Inquiry using REST custom action is failing. It is not validating the flex commodity code as per the flex commodity qualifier provided. | When processing Rate Inquiry using REST custom action, the flex commodity code will be validated as per the flex commodity qualifier provided. | 
| 37530141 | The application creates duplicate supplemental bills when you click the "OK" button multiple times or press the "Return" key in quick succession in the input screen of the action "Create Supplemental Bill". | The application will now prevent the duplicating process by disabling the "OK" button after the first click. | 
| 37530144 | When you have edited the conditional booking details twice, the application automatically accepts the tender. | Added the property "glog.webserver.tender.allowAcceptForCBWhenTenderUpdatable" to resolve this issue. When the property is set to true, the application does not automatically accept the tender when you edit the conditional booking details. By default, the property is true. | 
| 37543864 | When an invoice exceeds the tolerance limit at either the header or the line level, the auto-approval process removes all cost references. However, in manual approval, the application displays an error directly instead of removing the cost references. | When a failed invoice from the automation agent is manually reapproved, the matched shipment costs are correctly displayed on the Approve Invoice screen. | 
| 37544724 | When the property "glog.integration.shipment.shipmentstop.includeLocation" is true and you tender a shipment, the Stops tab of the Online Booking/Tendering screen does not display the location details. | When you tender a shipment, and if the property "glog.integration.shipment.shipmentstop.includeLocation" is true, the Stops tab now displays the location details. | 
| 37555492 | On the Restricted Party Screening enhanced workbench, the work queues in the drop-down list used to populate the workbench are not in alphabetical order. | In the drop-down list, the work queues are now shown in alphabetical order. | 
| 37569568 | When using the agent action "ORDER RELEASE - MOD - EDIT SHIPMENT" for an order release with a PLANNING_SELL status value of PLANNING_SELL_UNSCHEDULED, an error is received referencing the status. | The issue is now resolved. The error message will no longer be received. | 
| 37597638 | When a failed invoice from the automation agent is manually reapproved, the matched shipment costs appear as unmatched on the "Approve Invoice" screen. | To resolve the issue, a new property "glog.invoice.approval.lineitem.isCompareDescription" has been introduced. When it is set to true, if a failed invoice from the automation agent is manually reapproved, the matched shipment costs will be displayed correctly on the "Approve Invoice" screen. | 
| 20250131 | ||
| 32624325 | The analyzer report should only display unwanted log files. This will help identify and disable them, as they can significantly impact performance. | The analyzer report's log settings now filter and display only unwanted log files. | 
| 35136145 | When a charge is missing in the accessorial cost template specified within the rate factor rule, the Rate Factor In Memory logic fails to evaluate the corresponding accessorial cost. | This issue has now been resolved. | 
| 37276270 | While creating secondary charge shipments, the involved parties are copied from both the secondary charge rule and the order. However, they should only be copied from the secondary charge rule. | The involved parties will now be copied only from the secondary charge rule when secondary charge shipments are created. This behavior is controlled by the optional feature "COPY INVOLVED PARTIES FROM SEC CHARGE RULE". | 
| 37279207 | For ALK maps, if the data region is 'WW' for world-wide and not passed to the ALK routing service, the ALK map plots incorrectly which leads to misaligned shipment plotting. | To address this issue, a new property "alk.useWorldWideRegion", has been added. Its default value is false. To use the world-wide data region and resolve the misaligned shipment plotting, set this property to true. | 
| 37310581 | When you run the action "Manage Appointments" on a location and search for a shipment group, shipment groups are not displayed on the dock manager for service providers when they have a user preference with the parameter "SHOW ASSIGNED UNTENDERED SHIPMENTS OF SERVPROV" set to false. | Now, shipment groups will be displayed in the dock manager even if the parameter "SHOW ASSIGNED UNTENDERED SHIPMENTS OF SERVPROV" is set false. | 
| 37315643 | On the Dock scheduling Gantt, calendar slots are misaligned when time range falls in the daylight savings time period of the stop location. Misalignment can also occur for 1 hr 30 minutes slot time intervals and some other specific intervals. | This issue is resolved now to get slots aligned correctly as per calendar irrespective of slot time interval and time range period used. | 
| 37321452 | When an order is constrained by an equipment group ID and the "Get Buy Rates" option is clicked, the rates fail to display. However, if the order release is constrained by an equipment group profile ID and "Get Buy Rates" is clicked, the rates are displayed as expected. | The rates will now be displayed successfully when the order is constrained by an equipment group ID and the "Get Buy Rates" is clicked. | 
| 37327554 | When you select the "Allow Find" and "Allow View" check boxes on a user-defined attribute on a buy shipment screen set, the check boxes are not saved. | This issue is now fixed. | 
| 37335736 | The Oracle Transportation Management report output is generated in ".txt" format instead of the expected ".csv" format when scheduled. | The Oracle Transportation Management report output will now be correctly generated with ".csv" extension when the format selected is CSV for a report when scheduled. | 
| 37335738 | The application displays an error when the shipment cost detail has more than 4000 characters. | No error will now be displayed if the shipment cost detail has more than 4000 characters. The message is now trimmed to 4000 characters if it has more than 4000 characters. | 
| 37335743 | Connection leak happens with ground schedules and the following error is displayed: "otm:IMessageText = CAUGHT THE FOLLOWING EXCEPTION WHILE PROCESSING TRANSACTION: [2338935] weblogic.jdbc.extensions.PoolLimitSQLException: weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool otm-local-jts to allocate to applications, please increase the size of the pool and retry". | This issue is now resolved. Connection will be closed to avoid connection leak when working with ground schedules. | 
| 37338913 | Entered a rate load definition with a template rate offering and inventory party details. After saving, the template rate record ID is not shown in the Rate Load Definition edit page. | The template rate record ID is now shown as expected on the Rate Load Definition edit page. | 
| 37339819 | When the username contains a slash (/), the slash is replaced in :xdo_user_name with "_" (underscore). However, when using :xdo_user_name for a username with a slash in a preprocess function, the function fails as the username has been modified and is no longer recognized. For example, the username: mydomain/myname becomes mydomain-_-myname, and the preprocess function fails. Therefore, data source access fails. This issue prevents Oracle Transportation Management preprocess function vpd.fnc_set_user_r(:xdo_user_name) to work. | This issue is now resolved. Preprocess function is working fine and both data model and report creation/generation are working as expected. | 
| 37357148 | When you run the action "Order Base Line Packing" in a customized manager layout copied from PACKING_OB_LINE, choose a "Transport Handling Unit" (THU) from the drop-down list, and then save the details, THU is not populated in the Release Instructions section. | When you choose a THU from the drop-down list in a customized manager layout copied from PACKING_OB_LINE, the THU appears in the Release Instructions section and that value is saved correctly upon clicking "FINISHED". | 
| 37366005 | An incorrect currency value defaults on the mobile application. | The Open Spot Bids and Submitted Spot Bids boxes will now use the service provider's user preference values in the mobile application. | 
| 37383278 | When you run a rate inquiry for passenger flights, the application does not return results. | Introduced a new property "glog.riq.useKnownShipper", which is set to true by default. When you run rate inquiry, the application returns results for passenger flights also. If you want to change to the old behavior and do not want to see the results of passenger flights, set the property to false. | 
| 37413485 | Pseudo fields added to a finder Results tab do not display the correct results even when the user has custom VPD applied. | Pseudo fields added to a finder Results tab will now display the correct results even when the user has custom VPD applied. | 
| 37418075 | If you change the equipment group for a shipment and subsequently make changes to the shipment, the workbench mapping of routes/stops intermittently does not refresh. | Now, the intermittent issues where workbench mapping of routes/stops did not refresh has been resolved, and it refreshes correctly. | 
| 37432813 | Ground schedule is configured in such a way that the shipment should be created as Pickup > Dropoff > Pickup > Dropoff. When the parameter "MULTISTOP ALLOW PICKUP AND DROPOFF AT SAME STOP" is set to false and orders are planned to a ground schedule shipment, the shipment stops are Pickup > Dropoff > No stop type > Dropoff. | When two stops on a repetition schedule have the same location but different activities, the shipment will now list the location as separate stops. | 
| 37440100 | Under rare conditions, currency exchange rates for older invoice dates can incorrectly use the current rate. This occurs when a different currency is inadvertently requested that either has no exchange rate or only one older than the invoice date. | Added an optional feature, "IMPROVE HISTORICAL CURRENCY RATE RETRIEVAL", to better allow for sparse currency rate population. When opted in, this feature resolves this issue with a small amount of memory overhead. | 
| 37440712 | Receiving error when you run a query, then change the user role, which is linked to a custom VPD, which results in fewer records than the original query. Using breadcrumbs to return to the original query results ends up in an error. | Added a new property, "glog.webserver.finder.results.use_breadcrumb_fix, to fix the issue when you get an error clicking on the breadcrumb link while using custom VPD. The property should be set to true. The default is false. | 
| 37443470 | When you propagate ship unit quantity using the agent action "ORDER RELEASE - MOD - PROPAGATE CHANGES", changes on the order release lines do not propagate line insertion to the shipment ship unit. When a ship unit line update contains a change in line number, the application generates a line delete and a line insert/update. The line delete is propagated to the shipment ship unit correctly, but the line insert/update is not processed. This results in the affected shipment ship unit containing no line afterward. | Now, ship unit quantity propagation using the agent action "ORDER RELEASE - MOD - PROPAGATE CHANGES" propagates the order release line number change correctly such that the corresponding shipment ship unit line will be deleted, and new shipment ship unit line will be added. | 
| 37443478 | The query fetch size can only be configured for a few select use cases. | To provide the ability to increase the query fetch size which will reduce database round-trips and improve large query performance, we have added an optional feature INITIALIZE FETCH SIZE WITH DEFAULT FETCH SIZE. The default fetch size is initialized to the value defined by the property "glog.sql.query.fetch.default". The default is 100. | 
| 37464316 | Using the label manager to change translations is no longer reflected until a system restart. | Reverted translation handling to 24C behavior: you can once again make a test change of a translation via the Label Manager and immediately see the impact on the system. | 
| 37467980 | You can face a timeout issue ("504 bad gateway" error) while performing the action "Change Service Provider". | Following properties are introduced to resolve the issue: glog.business.action.shipment.FindRelatedCommitmentAllocationAction.activeTable: This property specifies the table to be used as active table while finding related commitment allocation data for actions such as "Change Service Provider" or "Show Network Routing Options". glog.business.action.shipment.FindRelatedCommitmentCountAction.activeTable: This property specifies the table to be used as active table while finding related commitment count data for actions such as "Change Service Provider" or "Show Network Routing Options". | 
Oracle Transportation Operational Planning
| Issue Number | Summary | Resolution | 
|---|---|---|
| 20250314 | ||
| 37634791 | When you run the action "Perform Prediction" on shipments, the prediction fails for certain lanes with the following errors: 
 | Fixed the prediction payload. You can now run the prediction successfully. | 
| 20250228 | ||
| 37493768 | In a multi-leg scenario, the action "Assign Rate" compares the end time of the first leg shipment to the start time of the second leg shipment instead of times on the shipment stop level. | The "Assign Rate" action now looks at the times at the shipment stop level rather than at the shipment level. For example, the departure time on stop 2 of the first leg shipment should not be later than the arrival time on stop 2 of the second leg shipment. | 
| 20250131 | ||
| 37310591 | The action "Build Buy Shipment on Primary Leg" fails with a Null Pointer Exception (NPE) in the scenario when you plan an order release using location profile in the itinerary, the last leg on the itinerary is the primary leg, and the property "glog.business.conopt.ConoptConverter.CheckOrderDates" is set to true. | Now, no error is displayed when you run the action "Build Buy Shipment on Primary Leg" on a primary leg. | 
| 37345550 | Container optimization bundling parameter "CONTAINER OPTIMIZATION BUNDLING CRITERIA" is working incorrectly. When the container optimization bundling logic is turned on by setting this parameter, in some cases Oracle Transportation Management is building shipments with more than 100% utilization. | This issue is now resolved. The parameter will work as expected. | 
| 37355145 | When you predict a future shipment and want to see the predicted results in the Logistics Machine Learning (LML) shipment prediction results Data Visualization dashboard, no data is shown. | Future shipments are now loaded into hdowner, but they will not show up in sample data visualization dashboard, LML - Shipment Prediction Results. The filter "Mean Absolute Percentage Error - Predicted" is on by default and this filter's formula uses "Actual Transit Time", which is null for a future shipment. If this filter is removed, then future shipments will appear. | 
| 37382992 | The application throws a Null Pointer Exception (NPE) and causes bulk plan to fail, under the following conditions: 
 For example, during bulk planning, a higher-priority shipment can start on Monday or Tuesday while a lower-priority shipment can only start on Tuesday, and a capacity limit of one truck per day is in place. (Note: A "higher-priority" shipment contains higher-priority orders compared to a "lower-priority" shipment.) | The fix addresses the NPE and ensures that the bulk plan proceeds without failure. The updated logic prioritizes the allocation of limited resources to higher-priority shipments, as intended. | 
| 37432883 | The application takes additional processing time during bulk planning due to unnecessary database queries related to matching orders to itineraries. | Reduced the number of database queries related to matching orders to itineraries. | 
Oracle Logistics Network Modeling
| Issue Number | Summary | Resolution | 
|---|---|---|
| 20250228 | ||
| 37597642 | When you run a bulk plan scenario in Logistics Network Modeling, the application does not display the count of created shipments accurately. | The bulk plan statistics are now calculated correctly when the bulk plan scenario is run with the parameter "Order Routing Method" set to "Cost Based Routing". | 
| 20250131 | ||
| 37344914 | On the Compare Modeling Scenario Results page, the Bulk Plan IDs are shown in a random order. Instead, they should be sorted. | Now, the Compare Modeling Scenario Results page sorts by Bulk Plan ID. If you are comparing multiple scenarios, sorting is as follows: first the scenarios are sorted by Scenario ID, and then within each scenario, sorting is done based on Bulk Plan ID. | 
Oracle Global Trade Management
| Issue Number | Summary | Resolution | 
|---|---|---|
| 20250328 | ||
| 37722387 | When the optional feature "PREFER CLASSIFICATION CODE OVER CODE GID" is turned off, on adding a new product classification from the Item manager, the event "ITEM CLASSIFICATION - CLASSIFICATION CREATED" does not trigger the agent. | Now, on adding a new product classification from the Item manager, the event "ITEM CLASSIFICATION - CLASSIFICATION CREATED" is raised and the agent is triggered when the optional feature is turned off. | 
| 20250131 | ||
| 37215264 | Update the URL for the external system ENHANCED_DESCARTES_DUTY_TAX_SERVICE. | Updated URL for the external system to point to https://services.content.descartes.com/api2/landedcost. | 
| 37389144 | If an Oracle Transportation Management/Global Trade Management page contains a lot of data and you navigate to another page before the current page is fully loaded, you may see a "403 Forbidden" error. This issue is intermittent depending on how fast you navigate through the pages and can occur on different managers and with various objects. | This issue has been fixed. | 
