Oracle Fusion Cloud Transportation and Global Trade Management 26B Release Notes

38539125

Inconsistencies between agent action versions can block agent action display or modification.

Improved error recovery on agent action display and persistence. One faulty agent action no longer blocks agent action display or modification.

38597863

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..

38650278

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.

38651218

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.

38651873

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

By setting the new glog.security.user.idcs.everyUserFederated property, the 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 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.

38655731

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.

38655737

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.

38672960

The Respond by Mobile App link in the tender email is not opening the mobile application to the correct shipment.

The Respond by Mobile App link in the tender email now opens the mobile application to the desired shipment.

38673073

The last line of a location address line is not appearing in the mobile application.

Now, all lines of the address are shown.

38677967

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.

38678054

Increase the column size for SQL_FIND in the INT_SAVED_QUERY table to match the size of SAVED_QUERY TABLE.SQL_FIND_ALL (which is 4000 characters).

Increased the column size of SQL_FIND to 4000 characters in the INT_SAVED_QUERY table to match SAVED_QUERY.SQL_FIND_ALL size of 4000 characters.

38685117

Duplicate order releases are created as you can click the "Submit" button multiple times after selecting a template on the Rapid Order Release template screen.

On the template screen of Rapid Order Release, the "Submit" button will change to "Processing" once it's clicked, so that it cannot be clicked more than once.

38717281

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.

38748690

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 a user deletes 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.

38748695

38749322

DBXML does not support Replace Child on auditable objects that do not exist.

DBXML now supports Replace Child on auditable objects that do not exist. If the object is missing, the transaction code is changed to an Insert.

38765341

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.

38780999

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.

38787547

Add an optional feature for displaying detailed cost breakdown at shipment group level.

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.

38794215

Stop level weight and volume are incorrect in HD Owner when compared with the Oracle Transportation Management database.

This issue is now fixed. Stop level weight and volume are correctly reflected in the HD Owner.

38815666

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.

38825275

Minor issues are seen when entering query parameters in the pop-up window in the mobile application planner flow.

Fixed the issues with the planner flow's query pop-up window.

38839501

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.

The application will now consistently include the depot stop times when calculating the earliest possible start time for a shipment.

38839503

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.

38839507

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

This issue has now been resolved. After an update, 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.

38857799

When file management deletes a Bulk Plan Diagnostic log, the corresponding database entry in DIAG_LOG_FILE is not deleted.

The DIAG_LOG_FILE record corresponding to a Bulk Plan Diagnostic log file is now deleted if file management deletes the file. Note this means the View Diagnostics button on Shipment Planning results is no longer available, rather than producing an error.

38869805

Change the default value of the IsSync attribute for the User XML payload if the value is not specified.

The default value of the IsSync attribute for the User XML payload is now "Y" if the value is not specified.

38873009

To address the issue, a new property "glog.shipment.amount.round.useBankersRounding" has been introduced.

If the property is set to true, the application uses currency rounding when displaying the accessorial shipment costs of each cost type on the associated shipment and invoice. This prevents discrepancies where a value (such as 0.5) turns to 0 in the database but appears as 1 on the screen.

If set to false, the application reverts to standard decimal rounding (rounding 0.5 up to 1), resulting in minor value mismatch between the costs displayed on the UI and the actual currency amounts stored in the database.

By default this property is set to false.

38916740

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.

38916742

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.

38916757

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.

38945692

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.

38945693

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".

38954387

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

Now, printer configurations will be migrated as expected.

38976052

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.

38976056

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.

38987026

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.

38819779,

38819791,

38819797,

38819804,

38819813,

38819817,

38819856,

38819860,

38819863,

38819869,

38819873,

38819879,

38819884,

38819917,

38819893,

38819898,

38819907,

38819912,

38819915

Update the translation for the following languages to a translation basis of 26A:

• Chinese (Traditional)

• Chinese (Simplified)

• Dutch

• Finnish

• French (Canada)

• French (France)

• German

• Italian

• Japanese

• Korean

• Norwegian

• Polish

• Portuguese

• Romanian

• Russian

• Spanish

• Swedish

• Thai

• Turkish

Updated translation for the languages mentioned.

37992727

Even when the Delivery Appointments checkbox is selected on an order release, delivery appointment is not being created automatically for some of the shipment stop levels in case of a round-trip shipment.

Now, when creating a multi-stop shipment, if the Pickup/Delivery Appointment checkbox is enabled on an order release, the shipment stop's pickup and delivery appointment fields will be populated.

38635675

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

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

38651220

Model training with large data containing 5000 columns is causing memory utilization to reach its limit, resulting in training failure.

The fix enabled SVD to reduce the number of dimensions used in the training process. The fix will improve the time consumed and memory utilization for Machine Learning training and prediction processes. To enable this fix, set the property glog.ml.train.enableSvd.pc=true in the CUSTOM property set.

38651222

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

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

38662692

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.".

38727003

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.

38781003

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.

38815668

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.

38817517

The View Diagnostics button on bulk plan results UI does not load the complete planning diagnostics file as the file is truncated. On the UI, a message is displayed "File truncated as the file size has exceeded the limit" even though the file size is smaller than the limit.

Adjusted planning diagnostic logs to act like action logs, avoiding standard log size limits.

38839505

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.

38869368

The rate service drive algorithm allows a vehicle to arrive at a pickup stop within the order window only to wait for the location calendar to open, or conversely, arrive during location hours at a delivery stop and wait for the delivery window. Some users find the behavior as a feasible drive solution, whereas others find it undesirable as it creates fragmented idle time during the shipment. As a result, these users prefer to shift arrival times earlier to meet both constraints simultaneously, even if it increases the total duration of the wait.

A new property "glog.optimization.scheduling.allowWaitBetweenOrdWinAndLocCalForPickup" has been introduced to fix the issue. When this property is set to true, the application prioritizes the Order Window check before the Location Calendar check under the following scenarios:

• The application may schedule an arrival at a pickup stop within the valid order window.

• If the location calendar is not yet open, the shipment will remain at the stop in a waiting state until the location calendar window opens.

When set to false, the application checks the location calendar first over the Order Window to ensure the vehicle arrives only when the location is ready to perform the pickup, resulting in eliminating unnecessary wait times.

Default: false.

38894368

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".

38954392

The issue involves a multi-leg re-use equipment scenario, where one of the legs that shares equipment also has capacity limits. When Network Routing and SPA (Service Provider Assignment) are turned on, and the leg with capacity limits is planned first, then the shipments on that leg will correctly count towards the appropriate capacity usage. However, if a different leg that shared equipment is planned first, and then the leg with the capacity limits, then the shipments on the capacity limits leg will not count towards the appropriate capacity usage.

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.

38964492

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.

38224532

When you run the "Scenario Bulk Plan" action, the application excessively queries the database to fetch capacity usage from the Logistics Network Modeling table.

Refactored capacity usage calculation logic for modeling bulk plan to minimize the database queries and improve performance.

38249830

The Logistics Network Modeling bulk plan is running slowly.

Added performance improvements for Logistics Network Modeling Bulk Planning.

38715548

In the Scenario Bulk Plan results page, the failed orders are incorrectly displayed as "0" (zero).

The Failed Order Count now displays the correct number of failed orders.

38722821

When running a large number of orders in a Logistics Network Modeling bulk plan scenario, planning can fail to generate shipments after completing the Commit Modeling Shipment milestone.

You can now run large scenario bulk plans successfully without running into any exception.

38843119

In Logistics Network Modeling, the Data Rule Set operator of the Date column is not honoring user preference for date format.

Now, the Data Rule Set operator of the Date column honors the user preference for date format.

36182190

Experiencing an issue when trying to use integration saved query for Contact interface to insert new data. In such cases, transmission is created successfully, but the following errors are displayed:

1. THE REQUIRED ELEMENT Contact.ContactGid IS MISSING

2. Error: java.lang.NullPointerException

Added support for IU (Insert/Update) transaction code with integration saved query for Contact. The IU transaction code works if the Contact record is already available, else the application displays an error.

37726976

Trying to send an outbound integration from a trade transaction line does not create a transmission. The logs show the error: "Resource not recognized: {0=null}."

The issue occurred because transaction line was not exposed as a resource in JSON. Added a new REST API for trade transaction line.

38564089

The "Review Match factor" action on party is skipping some part of the address while matching with a restricted party.

The issue was caused by a highlighting error in Keyword match engine. It is now fixed.

38748797

In a Campaign Workbench, when trying to view content for a campaign line in PDF format, the application displays it in HTML format and generates the following error: "Error - The document content cannot be retrieved."

Changed the document GID logic such that file names with special characters other than the allowed ones are replaced with "_" (underscore). You can now view content in the desired format without any error.

38809314

Changing the value of the property "gtm.dutyTax.externalSystem.name" is not refreshing the value in the memory if one had set the value as "DESCARTES_DUTY_TAX_SERVICE" earlier and invoked duty tax Analysis.

Now, duty and tax analysis, and landed cost simulator take the latest value of the property "gtm.dutytax.externalsystem.name" to connect to an external system.

38815671

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.

38844604

GTM_SHIPMENT screen set is not displaying status type and value in results.

Both the GTM_SHIPMENT and GTM_TRANSACTION objects' status types are now displayed in the drop-down list of the custom screen sets. Similarly, both the GTM_SHIPMENT_LINE and GTM_TRANSACTION_LINE objects' status types are now displayed in the drop-down list of the custom screen sets.

38869838

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.

38916746

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.

38916748

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.

38585429

The Rate Distance help topic does not specify the following: It does not say if the Distance Type is lookup and an External Distance Engine ID (EDE) is provided, it would look for distance using EDE and if EDE does not return the distance and Estimate flag is switched on, it would estimate the distance.

Updated the Rate Distance help topic with the following note: "Note: If the Distance Type is Lookup, an External Distance Engine ID (EDE) is provided, and Estimate Allowed is selected, the system looks for the distance using the EDE. If nothing is returned, the distance is estimated."

38781007

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.

38840601

Adjust the "Additional Data Access Constraints" and "Modifying Service Security Data" sections of the Security Guide to include the "USER-ADMINISTRATION" user roles.

The "Additional Data Access Constraints" and "Modifying Service Security Data" sections of the Security Guide have been modified to include the "USER-ADMINISTRATION" user roles.

38846529

The SERVPROV_TENDER_COMMENT table is missing in exclusion list of tables in the Data Export Guide.

Renamed the section of the guide to be "Tables Supported for Data Export Deletes" and added a list of tables which support deletes.

38853641

Consolidate the retrieving SSL certificates information in KB865132, KB75360, and the Administration Guide. Remove redundancies and improve cross-references.

Updated KB75360 to point directly to the Administration Guide as the solution.

Updated KB865132 with minor edits and improved the links to the Administration Guide.

Updated the Administration Guide to reference KB865132.