Oracle Fusion Cloud Transportation and Global Trade Management 26A Weekly Update Bundle: OTM_26A-20260508

39228688

You cannot add a custom action to a screen set using a manager layout link. This used to work earlier.

Issues have been fixed related to editing an action on a screen set. You can now add a custom action to a screen set using a manager layout link.

39088754

If you go to Sourcing > Setup > CRT Configuration > New, enter the required fields, and click on the CRT Configuration Details tab at the bottom, nothing happens and you cannot create a CRT (Carrier Response Template).

An issue with rate queries has been fix and you can now create a new CRT Configuration.

39108469

A field screen set with query=P_BID and a custom screen set is not honored in the "View Related Bids" SmartLink. That action is using the public P_BID screen set instead.

Now, the field screen set for P_BID works for the "View Related Bids" SmartLink.

39165839

When a transmission is sent without necessary content, such as with a transmission body or status elements without detail content, the application does not always return the error: "400 Bad Request Status Code".

When the application processes transmissions without necessary content, the application will return an "400 Bad Request Status Code" error. For example, the error is returned for transmission body or elements, such as statuses, that are missing the required details..

38960727

The application fails to support multiple reloads for a shipment when a default accessorial does not have a rate factor rule.

The rating logic has been updated to support multiple reloads even when no rate factor rule is mapped to the default accessorial.

39027204

When you download a document content as a PDF file, the application fails to process the request, and displays the following error: "The document content could not be retrieved".

You can now successfully download the document content as a PDF file without encountering retrieval errors.

39080630

Shipment cost rounding does not function correctly when processing certain small decimal values.

The shipment cost rounding logic has been updated to eliminate precision errors associated with small decimal intervals when using the double data type.

An optional feature "USE IMPROVED RATING ROUNDING" has been introduced to toggle between the existing and the improved rounding logic.

By default, this optional feature is enabled for new users and disabled for migrated users.

38982172

When navigating to Business Process Automation > Reporting > Oracle Analytics Publisher, you get a "Transportation Intelligence is not enabled" error.

Navigation to Oracle Analytics Publisher from Oracle Transportation Management does not result in an error anymore.

Note: If you run only BI Publisher reports and do not use Analytics or Data Visualization, then you should remove the properties glog.analytics.ti.enabled and glog.analytics.gti.enabled from the custom property set. These properties will enable you to run ETL, which is unnecessary. You should add these properties only if you use Analytics or Data Visualization. 

39005185

The Generate Ship Units action changes the weight of the line item as expected but does not change the ship unit weight the first time.

When the line item is edited the second time, the weight of the line item is as expected, however, the ship unit weight changes to the old value.

Re-added the logic that recalculates the weight and volume on an order release line when the count is changed. This is controlled by a new property, glog.ejb.orderreleaseline.deriveMissingData with a default value of false.

With this change, ship unit weight/volume calculation will be correct when running the Generate Ship Units action, because it is based on the values on the line item.

39022665

Notifications for the SHIPMENT - APPOINTMENT SCHEDULED event are not sent when the Stylesheet Profile has the Raw XML option selected along with an out XML profile. As a result, the application displays an exception in the logs.

Notifications will now be sent for the event when the Stylesheet Profile has the Raw XML option selected and an out XML Profile is configured.

39046970

Populate correct values for hasMore, limit, and count to child collection resources. Also populate the "totalResults" attribute in child collection resources.

The REST API now returns correct values for the following informational attributes associated with child collection resources:

• hasMore: Indicates whether additional child records remain beyond the current page.

• limit: The maximum number of child records returned per request.

• count: The number of child records returned in the current response.

In addition, a new informational attribute has been added:

• totalResults: The total number of child records associated with the parent resource (across all pages).

The REST API returns up to 1000 child records per child collection, per parent resource, per request. If a given child collection contains more than 1000 records for that resource:

• hasMore is set to true

• a "next" link is included in the response for that child collection.

The "next" link targets the specific child collection resource and can be used to fetch the next page (up to 1,000 additional child records) by issuing another REST request to the URL provided. Paging continues until all records for that child collection are retrieved.

This behavior is controlled by the optional feature ENABLE RETRIEVAL OF UPDATED CHILDREN PAGE DETAILS, which is disabled by default.

38963969

The Re-transmit Tender action on a shipment for which a tender is accepted, is not working after 26A upgrade.

The Re-transmit Tender action now works for a shipment for which is a tender is accepted.

38958541

An optional feature is required to prevent any issues that might occur while correcting the XPath of invoice line items for bill and voucher.

An optional feature “FIX XPATH FOR INV OR BILL LINE ITEM FLEX FIELDS,” which provides fallback logic, has been added to avoid issues that might occur while correcting the XPath for invoice line items in bill and voucher.

When the optional feature is enabled, out XML profile uses the following path to fetch the flex field attributes: Payment/PaymentModeDetail/GenericDetail/GenericLineItem/CommonInvoiceLineElements/*

When the optional feature is disabled, the flex field attributes can be fetched using the earlier path: Payment/PaymentModeDetail/GenericDetail/GenericLineItem/*

By default, this optional feature is disabled for migrated users and enabled for new users.

38981347

The SQL ID stored on saved queries for the new SQL Performance feature should only be updated on first use. It is being updated each time the saved query is run.

Fixed loading and caching issues to properly cache the SQL ID on saved queries and update the SQL ID field only on first use.

Opting all customers back into the optional feature SUPPORT SQL PERFORMANCE IDS after the patch.

38987386

When an agent is modified while also updating multiple DIRECT SQL UPDATE agent action updates, the agent action can become corrupted. This is due to a caching problem where the cached sequence of the updated action no longer matches the sequence modified on agent update.

Resolved collisions between agent edits and updates of DIRECT SQL UPDATE for SqlId storage.

38721578

When splitting a shipment by order movement, and the split-off order movement is left unplanned, the split-off order movement planning status remains "OM_PLANNING_PLANNED - FINAL" instead of "OM_PLANNING_UNSCHEDULED".

When the shipment is split by order movement, and the split-off order movement is left unplanned, the order movement planning status will now be changed to "OM_PLANNING_UNSCHEDULED".

38818437

The XML output for both the bill and the voucher common invoice line items, fails to include attributes related to flex fields. As a result, any information stored in the flex fields is omitted from the generated XML.

The XML generation logic for common invoice line items in both the bills and the vouchers has been updated to include all relevant flex field attributes.

Previously, flex field attributes were available under:
Payment/PaymentModeDetail/GenericDetail/GenericLineItem/*

Now, flex field attributes can be found under:
Payment/PaymentModeDetail/GenericDetail/GenericLineItem/CommonInvoiceLineElements/*

To retrieve flex field attributes, use the new XML path in the out XML profile.

38851229

An inefficient algorithm on metric storage delays application startup time for metric types with thousands of sub-components.

Fixed metric storage to remove exponential growth in access and storage times.

38916739

A transaction acknowledgement message fails for tender offer transmissions with the following exception: "java.sql.SQLException: ORA-14400: inserted partition key does not map to any partition."

The issue has been resolved.

38916741

When specifying a saved query as part of an inbound integration XML (IntSavedQuery) to create locations in an order base, it fails.

You can now use an IntSavedQuery together with other location data as part of inbound integration, to either insert or update locations.

38954386

Migration of multiple printer configuration is failing when migrating from Oracle Analytics Server to Oracle Analytics.

Now, printer configurations will be migrated as expected.

38967226

The hourly recurring process, Collect SQL Performance, encountered the following issues:

1. The SQL Use Case was exceeding 1000 characters due to a parsing error of the /* OTM <Category>-<Use Case> */ hint in cursor cache SQL. This was due to additional, long commented out portions of SQL.
   
   The application needs to be made reluctant to avoid hitting user comments.

2. A use case with more than 1000 characters was failing the batch insert due to column length restrictions. The use case needs to be truncated if it's more than 1000 characters.

3. The switch from batch insert to one-by-one insert failed with duplicate key errors due to issues with commit and rollback of the batch attempt.

1. Improved handling of OTM hints to avoid user comment collisions.

2. Restricted use case length to avoid column size limitations.

3. Improved error recovery on batch inserts.

38976832

After the 26A patch upgrade, when "REST" is used as the communication method and when the content-type is not set for the response, outbound OTM transmissions are failing.

Note: This issue does not happen when the content-type is set appropriately for the transmission response.

This issue has been resolved.

38840139

The following uses of email do not account for an external SMTP host:

• Integration: Transmission error emails

• Procurement: Build Lane Summary

• Procurement: Extend

• Procurement: Pull Shipments

• ETL: Run ETL

• ETL: Run Targets

• ETL: Run User ETL

• Reports: Email distribution

• Documents: Email distribution

All uses of email now take into account the specification of an external mail SMTP host in glog.mail.smtp.external.host.

38866375

An issue occurs in the shipment rating process where accessorial costs applied per stop activity are incorrectly allocated. Specifically, when rating a shipment, the application fails to assign the cost reference details correctly to the individual accessorial costs if the charge multiplier option is set to "Collect all costs separately". This leads to the allocation not working properly for the accessorial costs.

Fixed the cost reference details issue for accessorial costs. The allocation for accessorial costs will work as expected.

38643748

Introduced the optional feature "DISPLAY DETAILED COST BREAKDOWN IN SHIPMENT GROUP" which is enabled by default.

When it is enabled, the application will display the detailed cost breakdown of all the cost types across the shipments in the shipment group.

If the optional feature is disabled, the Financials tab will remain visible on the shipment group. However, no cost types including their detailed breakdowns will be displayed at the shipment group level.

38651217

When withdrawing a tender, the application prompts for a decline reason code. Once you select the code and click OK, the tender withdrawal event is populated in the IE_SHIPMENTSTATUS table, but the reason code is not being captured.

Reason code will now be populated in the IE_SHIPMENTSTATUS table for a withdrawn tender.

38651872

Provide a basic way for Oracle Transportation Management to be able to default the Federated User attribute.

By setting the new glog.security.user.idcs.everyUserFederated property, Oracle Transportation Management will default the Federated User attribute, if not specified.

This IDCS Federated User attribute is used during the IDCS User Synchronization; so, when that user is synchronized from OTM to IDCS, it will not trigger a new user email from IDCS.

glog.security.user.idcs.everyUserFederated=[(false)|true]

For backward capability, the default value for this property is false, so that the user will not become federated by default.

If the Federated User attribute is not specified in csv, dbxml, or XML interface, then the glog.security.user.idcs.everyUserFederated property will be used. Otherwise the Federated User attribute value specified will be used.

38655730

When the Delivery Appointment checkbox is selected on the order, the order does not plan via the XDock (cross-dock) defined in the itinerary. Instead, it gets planned as a direct shipment.

This issue is fixed.

38655736

Getting the following error when running ETL: "F_SHIPMENT_ORDER_RELEASE_COST ERROR Log: Errored during the execution of INCR_F_SHIPMENT_ORDER_RELEASE_COST"

INCR_F_SHIPMENT_ORDER_RELEASE_COST ETL mapping load query has been optimized. You can now run ETL without an error.

38677965

The user encountered a "Read_Record_Failure" error when shipment deletion was triggered either directly or through shipment actions. The issue occurred because the application found no tender records. This happens only when an incorrect shipment status is set, indicating the shipment is in tendered state.

The application will now properly handle the absence of tender collaboration records, and will allow for shipment deletion when no active tender record exists for the shipment.

38693726

You cannot create a new Rate Load Definition when the optional feature "INCLUDE PERIOD IN XID RESTRICTED CHARACTERS" is opted in because the GID and XID in the RATE_LOAD_TEMPLATE_RR_D and RATE_LOAD_TEMPLATE_RO_D tables contain periods ".".

You can now create a rate load definition when the  "INCLUDE PERIOD IN XID RESTRICTED CHARACTERS" optional feature is opted in.

38748689

An order is split into two order movements: one unplanned shipment ship unit order movement, and another planned order movement with the shipment ship unit present on the shipment. When you delete the planned shipment ship unit (either by setting the ship unit count to zero in the XML or via UI), it results in an exception.

Now, the planned shipment ship unit is deleted as expected, and the unplanned order movement shipment ship unit count is updated correctly.

38755302

When there is a failure in allocation, the application fails to raise an error message, even though the failure is recorded in the application log.

When the optional feature "RAISE ERROR ON ALLOCATION FAILURE" is enabled, the application will now raise the error message when there is a failure in allocation.

38765340

When a shipment actual is processed to increase the ship unit count on a planned order movement, the unplanned order movement's ship unit count is not decreased. This causes the total ship unit count on the order to be out of sync.

Introduced the property glog.business.shipmentactual.syncWithOrderOnCountIncrease to keep the unplanned order movement's count in sync with the planned order movement in case you are performing a ship unit count increase. The default value of this property is false. When the property is set to true, the unplanned order movement's count is accordingly decreased to keep the total ship unit count in sync with the order ship unit count.

38772251

In the Integration Guide, the OAuth2 documentation needs to be updated to match the new IDCS user interface.

Updated Chapter 4: Security - OAuth2 to match the new IDCS user interface.

38780998

While performing Award Bid action for a spot bid, an incorrect alert message is displayed prompting to enter a reason code since the selected bid is not the lowest bid even when the lowest bid was selected. This happens due to currency conversion rounding off. You see a small variation of around .000X during conversion between different currencies when the entered amount and the user’s preferred currency are different.

Fixed the issue of incorrect alert being displayed even when awarding the spot bid tender to the lowest bid. Removed the property glog.tender.spotBid.lowestBidPrecision which was previously added for the same issue.

38839500

Shipment start time fails to consider depot start time during order release planning, whereas it is correctly included during order movement planning. This inconsistency leads to inaccurate shipment scheduling when depot stops are involved.

A new property "glog.business.shipment.includeDepotStopForEarliestPossibleStartTime" has been introduced to fix this issue. When true, depot stop times are consistently included when calculating the earliest possible start time for a shipment. By default, the value is true.

38839502

When scheduling reports from a child domain, the generated file names are exceeding the character limit. This occurs either due to domain name being repeated twice, or the child domain name being added for the report GID resulting in excessively long file names.

A new property "glog.bipreports.schedule.filename.avoidDuplicateDomain" has been introduced to fix the file name length issue. When set to true, the application will only use the primary domain name and the report ID, effectively removing duplicate domain prefixes from the file name. By default, the property is set to false to maintain existing behavior.

38839506

After applying a weekly patch, Business Intelligence (BI) Publisher scheduled jobs are in a "Paused" state.

This issue has now been resolved. After applying a weekly patch, scheduled jobs will be in an "Active" state, reports will be scheduled as expected, and job history will be created as expected with correct status.

39233518

After the 26A upgrade, some bulk plans select an unexpected service provider and do not apply the expected rate cost behavior when rates from the effective date are present.

Bulk planning is corrected so that valid rate costs are applied consistently, including scenarios where rates from the effective dates are used, restoring expected service-provider selection.

38841904

When bulk planning orders without an Equipment Group ID constraint, the application creates two separate shipments instead of a multi-stop shipment. However, the application correctly generates a multi-stop shipment if users apply an Equipment Group ID constraint.

The application will now correctly create multi-stop shipments during bulk planning, even when the Equipment Group ID is not constrained.

39040133

The application displays a Null Pointer Exception (NPE) during bulk planning when Service Provider Assignment (SPA) is active under specific configuration parameters.

1. When the SPA parameter PLAN SHIPMENTS WITH CARRIER COMMITMENT is set to true.

2. When the SPA parameter USE PRIORITY IN SPA is true (or shipment preference criteria are utilized).

3. When SPA MAX DAYS TO CONSIDER is set to 2 or higher.

4. When a shipment has the option to start on a day with availability of no lower-priority shipment, while also having the option to start on the following day.

The issue is now fixed. The application will allow the bulk plan to continue successfully, preferring to give limited resources to higher priority shipments as designed.

38673107

Introduced the property "glog.business.networkrouting.alwaysApplyCapacityUsageOnLeg" to address this issue. When the property is set to true (which is the default), the shipments on the capacity limit leg will correctly count towards the appropriate capacity usage, even if a different leg that shared the equipment is planned first.

Note: This fix addresses only the scenario when Network Routing is turned on. It does not necessarily address scenarios where the different legs that share equipment all have capacity limits.

38877601

The "Propose Classification Code" action results show the codes as inactive even though they are active.

The issue occurred as the query for description was using language name instead of code if the default language was set. The action results will now show the required codes as active.

38868560

Unable to navigate and sign in to the application due to a network routing performance issue.

Changes have been implemented to resolve a network routing performance issue encountered during the replan task within the action "Show Network Routing Option". Users will now be able to log in or navigate across other pages in the application without any network routing performance issue.

38635674

During training for planned transit time prediction, you may see that the "Series object has no attribute columns" error .

Added new checks to capture the error and added user-friendly log messages.

38651221

After executing the "Split Order Release" action on an order movement, the order movement status incorrectly reverts from OM_PLANNING_PLANNED_FINAL to OM_PLANNING_UNSCHEDULED.

The application will prevent unnecessary status changes and maintain shipment graph integrity for planned order movements.

38662691

If there are no features that contribute to training, the training completes without providing any valuable feature importance.

If there are no features that contribute to training, the training now fails with exception: "No predictive features detected. This can happen if your dataset contains only highly similar, constant, or non-informative features. Please review your dataset to ensure it includes features with sufficient variation and predictive value.".

38727002

An exception is encountered when attempting to plan a multi-stop shipment that has special services on stops and special service references on those services.

The multi-threading bulk plan no longer throws the exception. All shipments are now successfully planned as expected.

38745836

Unable to move multiple orders to a shipment when performing the "Move Order to (Existing) Shipment" action.

The "Move Order to (Existing) Shipment" action will now work as expected when moving multiple orders to the shipment simultaneously.

38781002

When an order is moved to an existing shipment, the application incorrectly adds unnecessary stops at the order's source location. This is caused by the Last-In, First-Out (LIFO) sequence checker if consecutive pickups occur at the same physical location. The checker fails to recognize them as identical, incorrectly triggering a LIFO violation by treating the second pickup as an intermediate stop.

The LIFO sequence checker will now consider only the last pickup stop when consecutive pickups occur at the same physical location. This issue occurred when running the "Add Order to Shipment" action, not the Bulk Plan operation as the bulk plan logic correctly handles stop and pickup consolidation. With this fix, the application will now validate the LIFO sequence when multiple pickups occur at the same source.

38839504

In the public Machine Learning Analytics workbench, you see the "Missing saved query name or saved condition" error.

The typo in the saved query used to fetch the scenarios related to a Machine Learning Project is now fixed. In the public Machine Learning Analytics workbench, you can now use the Machine Learning Projects and Scenarios regions without errors.

38733990

When the equipment type assignment fails for one driver assignment, the application fails to process the whole optimization and no drivers are assigned.

A new property "glog.business.fleetassignment.continueWhenOneDriverAssignFails" has been introduced to fix the issue. When the property is set to true, the application will process the whole optimization and other driver assignments can succeed even if the equipment type assignment fails for one driver assignment. By default, the property is false.

38916751

Performance issues occur in scenario bulk plan after upgrade. The issues are the result of a feature added earlier - including accessorials in sourcing rates when applying rate record/rate offering data rules. The feature is controlled by the property, glog.business.lnm.activateSourcingAccessorialCosts and is true by default. However, setting the property to false results in errors.

Now, as a workaround, the property can be set to false without causing errors. The performance issue will be fixed in a later release.

38722820

When running over 24,000 orders in a Logistics Network Modeling bulk plan scenario, it fails to generate shipments after completing the Commit Modeling Shipment milestone.

You can now run the scenario bulk plan successfully without running into any exception.

39076420

A custom agent event is not triggered when modifying UOM (unit of measure) conversion data for an item.

The custom modification event of GTM_ITEM_UOM_CONVERSION for the agent type "ITEM" will now be triggered as expected when modifying UOM conversion data for an item.

38972399

Transaction date information is not displayed on the Trade Transaction Lines finder results page.

A "Created Date" column is now available on the Trade Transaction Lines and Declaration Lines finder results screens.

38992127

The application triggers the post download process of Detect Invalid Classification for every .zip file download. This causes redundant updates when multiple .zip files are downloaded for a HTS content in different languages.

Added a new optional feature "SUPPRESS DUPLICATE CLASSIFICATION PROCESSING" to handle this issue. When the optional feature is turned ON, during partial data load of HTS classifications, only the MASTER and the PARTS files are processed. These files have language dependent descriptions/notes of classification codes. Other redundant files are not processed.

Also, the Detect Invalid Classification process is not triggered for partial data load.

38916745

An item should be considered as wholly originating if all the components are either wholly originating or originating based on member nation status/qualified status. Currently however, if the component is not wholly originating and is only originating based on the member nation status, the finished good is not considered as wholly originating.

An item is considered wholly originating when all the immediate components are either wholly originating or originating.

Wholly originating means the component is marked as wholly originating at item origin level. Originating means the component should belong to the trade agreement member nation, and if the property "gtm.roo.leafComponent.originating.considerQualification" is true, the component should be qualified to be considered as originating.

In a finished good with a multi-level Bill of Material, the immediate intermediate component (which is a component with child components) has to be originating and qualified to be considered as originating irrespective of the property.

38916747

Loading of campaign data is causing an "Out of Memory" exception.

The issue was caused because the same campaign data was being loaded for every single line of the campaign being approved. The issue has been fixed so that now, when you run the "Approve Campaign" action, campaign data will be loaded only once instead of multiple times.

38974544

Delay promotion of the  COMPLIANCE SCREENING - IGNORE AGGREGATE FLAG optional feature.

Promotion of the COMPLIANCE SCREENING - IGNORE AGGREGATE FLAG optional feature has been changed from 26A to 27A.  You'll be able to opt-in or opt-out of this feature, as required.

38619856

Rename the "Add Additional Duty Lines" action to "Split Line for Penalty Reporting".

Also, for precise calculation of the percentage of steel or non-steel content in imported goods and for reporting the associated duties to the US Customs and Border Protection (CBP), add the action on Declaration Line business object instead of Transaction Line.

Renamed the action to "Split Line for Penalty Reporting".

Added the action on Declaration Line. Removed it from Transaction Line. To run the action, go to Customs > Declaration Lines > Actions > Compliance > Split Line for Penalty Reporting.

38759855

Improve performance of Machine Learning Training for high volume of data.

Introduced a logic parameter "MAX DEPTH" to address the issue. The parameter controls how many decisions each computation in the algorithm is allowed to make before the process stops. If the parameter value is small, the computation stays simple and general. However, in this case, the model may not include important details.

If the value is large, computation becomes very detailed and specific, causing performance issues. In this case, the model may memorize the training data instead of learning useful patterns.

Hence, it is recommended that you enter a smaller value if your data set is small or your data is noisy/inconsistent. You can enter a larger value if you have a large volume of data and the problem is complex.

The default value of the parameter is 20. The maximum value allowed is 20. You can set a value lower than 20, if required.