Oracle Fusion Cloud Transportation and Global Trade Management 25C Release Notes

32108478

An erroring agent is failing to record the error to the Agent Action Log because of "ORA-12899: value too large for column". This message should be truncated before writing it to the table.

During automatic agent execution, error messages are truncated when needed to prevent errors.

32158253

While clicking the "Get Buy Rate" button for rapid order release with same pickup and delivery location, the application expects the PC Miler to calculate the distance as 4.99 miles. However, it is only returning 4 miles, excluding the decimal portion.

Added a note to Help "When specifying the units in "Same Source Destination Distance" parameter on the external distance, it is important to include a space between the value and the unit. For example, the value should be formatted as "4.99 MI." If no space is provided between the value and the unit, a number format error will be displayed."

33579870

When running the cost allocation method "ERU COUNT CARRIED DISTANCE", the cost allocation fails for small orders which consume less than 1 ERU (e.g., 0.5 ERU) with the following error: "Allocation cannot be performed: total amount for ERU COUNT CARRIED DISTANCE is zero, which would result in a division by zero error."

The application rounds down small values, causing 0.5 ERU (Equipment Reference Unit) to be considered as 0 (zero) during calculations.

The application now supports decimal values when "ERU COUNT DIRECT DISTANCE" or "ERU COUNT CARRIED DISTANCE" metrics are using decimal values while allocating the cost. This will help correct handling of small ERU quantities in cost allocation, thus avoiding division by zero errors.

34987731

If the "USE RATE RECORD COST GROUPS" is set to false or is not configured in the user preferences, the rounding type for the rate geo cost group is incorrectly saved as "No Rounding".

Incorrectly saving of rate geo cost group as "No Rounding" will not occur. The rounding related fields will be added to display the current values when "USE RATE RECORD COST GROUPS" is set to false or not configured in the user preferences.

35770639

While running the "Approve Invoice" action to approve an invoice, a note column prompt appears, and you are only allowed to enter up to 50 characters in the note column. Any input exceeding this limit is not accepted.

The character limit for the note column is now increased to 2000.

36030568

In the "Add Document" action, clicking the "Upload" button multiple times causes the document being uploaded multiple times instead of just once.

The application will now upload the document only once even if the "Upload" button is clicked multiple times in the "Add Document" action.

36426925

The email address length in the Service Provider manager is restricted to 50 characters. Any address longer than that is not being accepted.

The limit of email address length is now changed to 2000 from 50 characters.

36756111

"The "Bulk Reporting" action is not designed for batch process but it is included as a process action option for the batch process. When selecting "Bulk Reporting" as a process action and clicking the Info icon next to the "Process Parameters" field, the application displays a "404 Error" error.

This action has now been removed from the batch process options. So, it will no longer show up in the batch process.

36763082

While executing the "Quote to Order" action on a quote, the packaged item "DEFAULT" is set on the ship unit on the order release.

Before executing the "Quote to Order" action, the packaged item ID can manually be selected for each item in the quote. If a packaged item is selected before running the action, it will appear on the converted order. Otherwise, "DEFAULT" packaged item will be set on the ship unit on the order release.

36935803

You get an error when clicking on Generate an XML for TenderOffer.

Go to Business Process Automation > Integration > Integration Manager > Generate an XML Template. Select TenderOffer in XML Element ID. The Object ID to query is a Shipment.GID. Click Submit.

The file that gets generated shows the following error: "[031222] java.lang.ClassCastException: glog.integration.schema.generate.Shipment cannot be cast to glog.integration.schema.generate.GLogXMLTransactionType"

When you Generate an XML Template, the application now restricts the "Include Data" option for the TenderOffer XML Element. In order to do that, TenderOffer has been removed from XML ElementID list when the Use XML Schema checkbox is not selected. The TenderOffer option is available in the drop-down list when this checkbox is selected.

36999485

A Shipment Actual XML with Replace Child using SEquipmentGidQuery instead of a SEquipmentGid element results in shipments where the shipment equipment is empty.

Updated the schema documentation to clarify that shipment equipment information should always be passed in when performing a Replace Child operation on shipment with ship units as a managed child.

37221091

In the damage claim, the URL provided in the remark text for the remark qualifier "URL" is displayed as a hyperlink in Edit mode but appears as a plain text in View mode.

The URL provided for the remark qualifier “URL” will now be displayed as a hyperlink in View mode.

37492618

Several of the geography-related queries across the application are beginning to experience performance issues, most of which are due to VPD and can be mitigated with a configurable active table. Active table configurations are required for major tender queries that are used in actions involving tender processes to resolve such performance issues.

Added active table configurations for the tender queries, which can be controlled by the following properties:

• glog.business.action.ShipmentExecutionActionExecutor.getMatchedServprovForOpenTender.activeTable

• glog.server.workflow.tender.autotender.AutoSecResProfile.getAutoSecureResourceByLaneProf.activeTable

• glog.server.workflow.tender.LaneTenderInfo.getLaneTenderInfo.activeTable

• glog.server.workflow.tender.LaneTenderInfoResponseTime.getLaneTenderInfo.activeTable

37492631

Several of our geography-related queries across the application are beginning to experience performance issues, most of which are due to VPD and can be mitigated with a configurable active table. Active table configuration is required for actions involving order management to resolve such performance issues.

37517470

Provide the ability to stop all or any particular Inbound Integration End Points from using the HTTP Basic Authentication method, which will be enforced regardless of users and associated Access Control Lists.

You can now configure the application to stop all or any particular Inbound Integration End Points from using the HTTP Basic Authentication method. This ability can be configured to stop all, stop based on the integration type, and stop based on specific HTTP application endpoint.

See the Security guide and the glog.security Properties help for a complete list of properties that allow disabling basic authentication rules.

37524386

When uploading a document manually, the "Document ID" field accepts a maximum of 50 characters. However, it accepts more than 50 characters when uploading via the transmission service.

The length of the "Document ID" field is now increased to support up to 80 characters in both the "Upload Document" and the "Document Manager" screens.

37561571

Add the ability to create saved query requests for shipment groups.

Custom action queries and savedQueries support have been added for shipmentGroups. The role required for this is REST - Shipment - View.

37576357

When configuring an external system, there are two constraints: Max Bytes per Transmission and Max Transactions per Transmission. When Max Bytes is set to a value which is lower than the transmission size, the XML is not completed with an ending tag and an unclear error message is given (Invalid ExtSys Configuration). There is a similar case when Max Transactions is also set to a lower value.

Added new exceptions, to make the message clearer:

• "Transaction count {transactionCount} exceeds the maximum number of transactions {maxTransactionCount} configured per transmission."

• "Transmission size {transmissionSize} exceeds the maximum number of bytes of {maxTransmissionSize} configured per transmission."

37614284

If a spot bid tender record on the Online Booking and Tendering screen has at least two service providers, the remark qualifier on one service provider causes duplicate SHIPMENT TENDER - TENDER BID RECEIVED event when submitting bids from another service provider.

Added the property "glog.webserver.opentender.ignoreExistingRemarkQualifierEvent". Set this property to true to avoid duplicate SHIPMENT TENDER - TENDER BID RECEIVED event being raised when submitting bids from a service provider if the previous service provider has a remark qualifier for spot bid tender on Online Booking and Tendering screen. The default value is false.

37614734

When a document XML is staged, the following exception pops up: ”An item with criteria group IDs=[DOCUMENT: <DOCUMENT_GID>, Integration: <NUMBER>], sequence=<NUMBER> already exists in group DOCUMENT: <DOCUMENT_GID>”.

When the document is being staged, both the agent action and polling threads are adding it to data queue, generating the error message.

Despite the message, the document is staged and processed successfully.

This has been resolved.

37641063

The "View Tracking Events" and "Track and Trace" SmartLinks display all tracking events, including the hidden ones, without considering user preference.

The display of hidden tracking events is now controlled by the user preference "Display Hidden Shipment Events," similar to the "View Shipment Tracking Events" web action.

37641071

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.

37643628

If you create multiple release instructions for an order base line, delete any release instruction, and run the "Order Base Line Packing" action, the application displays an error.

The application considers the release instruction with the highest sequence number and then adds 1 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.

37645502

When running the "Allocate Shipment" action, memory leak happens, which eventually leads to "Out of Memory" exception.

Fixed memory leak issue while executing allocation of shipment or voucher.

37651026

In the Enhanced Workbench, a combined detail table has two views: grouped and ungrouped. The pagination does not adjust when switching from the grouped view to the ungrouped view. This can cause incorrect row counts.

This issue has now been fixed.

37670213

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:

• glog.dataqueue.poller.networkTimeout = the network timeout, in milliseconds, for cached connections on the data queue thread, applied only while in the poller lock.

• glog.dataqueue.networkTimeout = the network timeout, in milliseconds, for cached connections on the data queue thread. This will impact both the poller and the executor. We include it in case there are issues with setting/resetting the poller network timeout.

• glog.sql.query.timeout.dataQueue = a new fetch timeout, in seconds, for poller queries. Note that the query timeout should be less than the network timeout.

• glog.dataqueue.forceAllConnectionsResetOnReopen = true, if a connection time out on one thread should force connection reestablishment on all other threads.

• glog.dataqueue.eventThreadInterruptionsOnly = true, if data queue threads should only allow interruption from OTM configuration changes like Data Queue inactivation and Data Queue thread count change.

Note: Any connection timeouts and reestablishment logging is now available in the exception log.

37670215

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.

37670217

On an Enhanced Workbench if you use a screen set that allows for a partial match in the Mass Update window, you may see the following issue: "The value [value] entered for field [field name] does not match a valid record".

The issue has been fixed and the error is no longer seen.

37680806

OAUTH access tokens are cached so that they can be reused for services rather than constantly requesting new tokens. The tokens are currently cached based on the authorization service URL and scope. When the credentials for a service are changed or if a new external system is created for the same service but with different credentials, the old cached token is still used until it expires, since authorization service URL and scope are unchanged, instead of requesting a new token based on the new credentials.

OAUTH access tokens will now be cached based on the External System ID. Any changes to an external system including changes to URLs, scope, and credentials will remove any tokens in the cache associated with that external system and a new access token will be requested.

The OAUTH access token cache, OAuthAccessTokenCache, can be seen and cleared via the App-Tier Caches diagnostic tool.

The CACHE ACCESS TOKENS BY EXTERNAL SYSTEM optional feature activates this functionality and is on by default. Disable the optional feature to not use this functionality.

37686992

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.

37692142

Unable to view migrated menus in the Menu Manager if the menu is in a sub-domain.

Migrated menus that are in a sub-domain now open as expected.

37706739

SShipUnits can only be updated/created/deleted when provided in the payload with a shipment. They cannot be updated/created/deleted directly. This exception must be explained with a message in the REST API documentation.

A description can now be added for any REST operation and it will be displayed in the REST API documentation. Text describing the functionality of SShipUnits has been added.

37709976

In an Enhanced Workbench shipment manager, the scrollbar disappears when the Calculate Total and Fixed Distance fields are set to read only.

The scrolling issue is fixed.

37716208

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.

37734051

During a PATCH operation with the includeChildren parameter (which allows users to PATCH parent and child records simultaneously), mismatched primary keys for objects in the PATCH payload and existing records gives a Null Pointer Exception.

If the primary key is provided in the payload and it exists in the database, then the application will perform the PATCH operation with the existing object. Otherwise it will create a new child object.

To control this behavior, a new property glog.fusion.cil.restapi.config.patchParent.allowAddChild is added. If false, new child objects will not be added for new primary keys. If true, new child objects will be added. The default value is false.

37735529

Enable the VPD optimization properties by default.

Added the optional feature MINIMIZE VPD DATABASE ROUNDTRIPS ON READ.

This enables the following properties to minimize VPD calls into the database for multi-layered read operations.

• glog.vpd.maintainState=true

• glog.vpd.optimizeDefaultUserRoleRestore=true

• glog.local.defaultTransactionAttribute=Hold

• glog.local.allowHold.EntityGets=true

Previously, you had to set these properties in the CUSTOM property set.

Note that these optimizations are enabled by default. They significantly help performance without any observed impact on functional behavior. If you think the optimizations are impacting your solution, opt out of the optional feature to confirm the difference. Then contact Support to report any differences observed.

If you already set these properties in the CUSTOM property set, opting out of MINIMIZE VPD DATABASE ROUNDTRIPS ON READ will have no impact unless the properties are also removed from the CUSTOM set.

37753073

When setting up a rate cost on the Rate Basis Item (RBI) Shipment Service Provider Reference Number, the list of values displays the Shipment Reference Numbers instead of the Location Reference Number Qualifiers.

The value for the RBI Shipment Service Provider Reference Number Qualifier will now be correctly redirected to Location Reference Number Qualifier.

37758031

Add support for native Oracle TIMESTAMP and TIMESTAMPTZ classes to maintain compatibility with agent ASSIGN statements using Oracle Timestamp functions such as to_timestamp().

Added support for native Oracle TIMESTAMP and TIMESTAMPTZ classes in DIRECT SQL UPDATE statement with Agent variables. Note that any difficulties in using a TIMESTAMP ASSIGN result in a DIRECT SQL UPDATE statement can be resolved by adjusting your SQL to ensure the ASSIGN statement receives a DATE result (e.g. by casting the SQL to a date).

37762482

Use a custom screen set for buy shipment and search for any shipment. On the custom finder result page, edit the value of "Total Net Volume" from 500 to 400 CUFT (cubic feet), and save the changes. Now, when you perform the "Recalculate Shipment Cost" action, the value of "Total Net Volume" is still 500 CUFT, which is the original value.

Now, when you use a custom screen set for buy shipment and edit the "Total Net Volume" field and run the "Recalculate Shipment Cost" action, the application retains the changed value correctly.

37781763

When a spot bid tender is awarded with documents and the property "glog.tender.copyDocuments" is set to false, the old tender is marked as "withdrawn", and a new tender is created with linked documents from the older tender. In View mode, clicking on the document ID in the new tender opens the Document manager, showing a "Used By" link and a "Related Document ID". If you log in as a "SERVPROV USER" and click on the "Related Document ID", it opens the document from another domain that shares the same "Document ID". This issue occurs only in View mode, not in Edit mode.

The "Related Document ID" will now redirect to the document view screen of the correct domain.

37798184

The glog.fusion.cil.restapi.config.disableDefaultChildRefResourceExpansion property defaults to false and is causing timeouts. Set the default to true.

Changed the glog.fusion.cil.restapi.config.disableDefaultChildRefResourceExpansion property to default to true so that default expansion of child resources will not happen and cause timeouts.

37798449

Performance issue with the "Move Order to Shipment" action happens in a scenario where the application has multi-leg itineraries and shipments may be linked to multiple other shipments due to order cross-consolidation at cross docks or similar intermediate locations. In such cases, the "Move Order to Shipment" action takes significantly longer to complete and may appear to get stuck. This is because the logic attempts to load far more shipment-related data from the database than necessary.

The performance issue with the "Move Order to Shipment" action has been resolved. The logic will now load only the necessary shipment-related data.

37801899

Change the default value of the glog.integration.webservice.enforceUNT property to true. This is required in order to upgrade to OIC (Oracle Integration Cloud) Gen3.

The default value for the glog.integration.webservice.enforceUNT property is now set to true.

37802002

The Oracle Transportation Management-Warehouse Management integration recipe that is published in OIC (Oracle Integration Cloud) store uses an integration saved query called S_EQUIPMENT_2. However, this integration saved query was not published and the integration would fail if this is not explicitly created.

The integration saved query "S_EQUIPMENT_2" is now seeded in the public domain. This is used in the Oracle Transportation Management-Warehouse Management integration recipe published in OIC (Oracle Integration Cloud) store.

37827632

Provide a way to navigate to the Business Intelligence (BI) Publisher URL when migrated or provisioned with Oracle Analytics Cloud. Add a menu item to the Business Process Automation > Reporting menu which links to the "xmlpserver" URL directly.

Added a menu item "Oracle Analytics Publisher" under Business Process Automation > Reporting. Clicking this link will navigate to bipublisher/xmlpserver home page.

37845264

Add indexes on the DRIVER_TYPE table to improve performance.

Added indexes on the DRIVER_TYPE table to enhance driver assignment performance in fleet management.

37854442

Add the ability to filter appointment options using an API based on the location resource type (Dock Door or Dock Worker).

Added a request body attribute "locationResourceTypeGid" for the "getAvailableAppointments" API to filter and display appointment options based on the location resource type GID. The same attribute is also added in the response body.

37862368

Improve bulk plan performance by adding indexes to the database tables.

Added two indexes on LOCATION table to enhance bulk plan performance.

37863904

The new Synchronize Users action throws an error for any user that has mismatched case usernames.

The new Synchronize Users action will no longer throw an error for any user that has mismatched case usernames and instead perform the update.

37867876

When processing a bulk plan with a large number of order releases, the bulk plan run fails, and the following error is observed in the logs: "SQL timeout of 600 seconds triggered for defaultQuery use case."

A new property "glog.business.action.useNewSelectOrWithInactiveLocation", has been introduced to determine the version of SQL query executed during bulk planning with a large number of order releases. When the property is set to true, the application will use the optimized SQL query. When set to false, the application will revert to the older version of the SQL query. By default, this property is set to true.

37870547

The openapi.json file has schema validation issues.

The openapi.json file no longer has schema validation errors.

37877297

When you run the "Running Manifest" action for a shipment and print as a PDF (Portable Document Format), the application prints only the first page of the output.

The "Running Manifest" action will now print the entire output.

37883284

The application intermittently fails to execute the "Add Shipment Tracking Event" action for a shipment and displays the following error message: "The short code is not valid for this action."

Now, the application will reload the quick code if it is not found in the cache. Additionally, debug logs have been added to support troubleshooting efforts.

37883286

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.

37890416

Loading zipped CSV files in the background returns unclear messages.

Improved screen, log, and email responses when uploading a zip file of CSVs.

37895766

Stage a metric threshold for high heap usage.

Created two inactive metric thresholds, CPU STARVATION and CPU TIMER BEHIND, to capture heap dumps, JRA recordings, and thread dumps when Oracle Transportation Management determines the CPU poller thread is unable to get processor time. This is likely due to unsuccessful reclamation of memory or other processes using up all CPU resources.

CPU STARVATION requires the CPU - JVM STARVED metric to occur twice in an hour. CPU TIMER BEHIND requires the CPU - TIMER BEHIND metric to occur twice in an hour. (Note that CPU STARVATION is not active in standard provisioned systems).

Once one of these metrics occurs twice in the hour, it queues the HEAP DUMP metric notification profile for processing within the next five minutes. At that point, Collect Diagnostic Logs is submitted to capture the thread dumps, a heap dump and a JRA recording.

Note that when active, these metric thresholds are set up to trigger at most once every four hours.

37910274

The application does not work as expected in the following scenario:

• Two order releases with multi-leg order movements are created.

• First order release's first-leg order movement is edited to populate parent source and destination locations.

• Both first-leg order movements are planned together onto a shipment.

• Parameter "SMD SYNC WITH ORDER" is set to true.

• Shipment actual is loaded to delete order release # 1 from the shipment. As a result, the order is removed from the shipment, but its first-leg order movement is not re-created as it should be.

Now, the order's first-leg order movement will be re-created.

37910304

Incorrect currency is sent for the "Declared Value Currency" field from the application to FedEx International for a rates API request.

The application will now send the correct currency for the "Declared Value Currency" field for the FedEx request.

37960318

The displayed start time is not honored on a location-based Dock Scheduling Gantt because the calendar slots are not aligned properly.

The displayed start time is now honored.

37973685

For RIQ (Rate Inquiry) RemoteQuery, the transmission status is set to PROCESSED even though the corresponding transaction gets an ERROR status.

This issue is now fixed and the transmission status will appropriately change to ERROR when there is an error.

37771950,

37771956,

37771958,

37771964,

37771966,

37771970,

37771976,

37771980,

37771988,

37771992,

37771997,

37772003,

37772008,

37772013,

37772020,

37772027,

37772033,

37772040,

37772047

Update the translation for the following languages to a translation basis of 25B:

• Chinese (Traditional)

• Chinese (Simplified)

• Dutch

• Finnish

• French (Canada)

• French (France)

• German

• Italian

• Japanese

• Korean

• Norwegian

• Polish

• Portuguese

• Russian

• Spanish

• Swedish

• Thai

• Turkish

• Romanian

Updated translation for the languages mentioned.

37528801

In Service Provider Assignment, the application allows you to select the earliest available shipment and purge all later or less preferred options for efficiency. However, this approach eliminates cheaper shipping options.

Instead of selecting only the earliest available shipment, the application will identify the earliest shipment per shipping mode. This will ensure to retain potentially more cost-effective options while still optimizing for efficiency within each mode.

37617006

The bulk plan results are misleading when order movements that do not have ship units defined are planned with other standard order movements that do have ship units defined.

The bulk plan will now display correct results when planning multiple order movements if some of the order movements do not have ship units defined.
When planning only order movements that do not have ship units together, the entire bulk plan will fail.
When planning multiple order movements that do not have ship units with standard order movements, only the order movements without ship units will fail to plan. The standard order movements will plan successfully.

37641069

When you run the "Perform Prediction" action on shipments, the prediction fails for certain lanes with the following errors:

1. Source location time zone not in Index.

2. Failed at data processing. Details: time data does not match format.

Fixed the prediction payload. You can now run the prediction successfully.

37728434

In Embedded Machine Learning transit time estimation, the training result is not consistent for the same project and scenario when the training is run multiple times.

The same project/scenario will now have the same result each time you perform training.

37757358

The "Total Reference Units" field on the buy shipment screen does not populate the appropriate value if the parameter "Check Equipment Capacity in Reference Units" is set to false. Previously the field was populated. You need to set this parameter to "true" to populate the appropriate value in this field.

A new property "glog.business.shipment.alwaysCalculateERUTotal" is added to control the calculation of the Equipment Reference Unit (ERU) totals with the default value as false. When the default value is true, the application always calculates the ERU totals regardless of the value of the planning parameter "Check Equipment Capacity in Reference Units".

37777970

Unnecessary wait time is sometimes added to shipments with carrier capacity constraints due to an incorrect time zone conversion in the carrier capacity logic.

The service time logic will now correctly utilize the appropriate carrier capacity time windows.

37804176

The Perform Prediction status polling intermittently fails.

Polling infrastructure improved to avoid intermittent failures of the Perform Prediction status polling.

37815489

The "glog.business.rate.rateoffering.useFallbackRSForRIQOnly" property is used to control whether the application opts only the fallback rate service either for Rate Inquiry (RIQ) or for planning. By default, the property is set to true, which means the application applies only to RIQ. To enable it for planning, the property must be set to false. However, due to a typo in the code, changes to this property do not take effect unless you also modify the incorrectly named "glog.business.rate.rateoffering.useFallbackRSForRIQOnlyt" property (note the extra “t” at the end).

The typo in the property name has been corrected. The application will now correctly use the "glog.business.rate.rateoffering.useFallbackRSForRIQOnly" property.

37877300

When calculating the feasible working range, the boundary of the non-working range is incorrectly included. As a result, the application attempts to schedule the shipment at the start of the next non-working range, which eventually fails due to insufficient capacity.

A new property, "glog.optimization.scheduling.includeBoundaryTime" has been introduced to control whether to include boundary time. When the property is set to true, the application will include the start time of next range in the end time of current range. By default, the property is set to false.

37915004

When you run the "Load Data into Analytics" action for a machine learning project, the status of the action continues as "Running".

The application now correctly updates the status of the action "Load Data to Analytics" to "Completed" even if there are no new records for the saved queries that are to be loaded to analytics.

37931052

The following issues are observed related to "Network Routing":

• When dynamic clustering is enabled, and the final leg includes multi-stop shipments that share equipment with the preceding leg, the application incorrectly inflates the weight and/or volume of orders during routing. This miscalculation, especially when equipment groups are used to constrain delivery legs, can lead to selecting the wrong leg and, consequently, the wrong equipment group. Note: This issue is specifically observed in the network routing planning task model file (commonly referred to as the "mip" file).

• When routing uses capacity limits via a "Capacity Limit Group", and these limits are evaluated over multiple days (controlled by the "SPA MAX DAYS TO CONSIDER" parameter set to a non-zero value), a null pointer exception may occur. This exception can cause the bulk planning process to fail.

These issues have been resolved and should no longer occur.

37771275

The issue occurs in a scenario where an order release is split across multiple shipments, each shipment has its source location identical to its destination location, and the driver has already been assigned to one of these shipments. In this case, the driver assignment logic incorrectly assumes an upstream-downstream relationship between the shipments due to the matching locations. As a result, the driver assignment logic fails and triggers the below error message: "DRIVER ASSIGNMENT TO SHIPMENT IS NOT FEASIBLE AS THE DRIVER IS ALREADY ASSIGNED TO ONE OF THE DOWNSTREAM SHIPMENTS." This problem affects both regular Driver Assignment and Force Driver Assignment.

A new property "glog.business.shipment.mustUseOmTagsForLinking" has been introduced to fix the issue.

When the property is set to true, the driver assignment logic will no longer use the common shipment locations to determine upstream-downstream relationships. Instead, it will rely only on the order movement tag data which will be invisible to the user, but enables the application to determine the shipment inter-relationship. In addition, the "Assign Driver" and "Force Assign Driver" actions will function properly when the property is set to true.

By default, the property is set to true.

37910307

In Logistics Network Modeling, if you run the "Scenario Bulk Plan" action , with planning parameter order routing method as Network Routing, and if there are order releases with no ship units, the action fails.

The "Scenario Bulk Plan" action with planning parameter order routing method as Network Routing fails for the order releases without ship units, but continues with the planning of subsequent order releases.

36267574

When running the "Set Control Screening Status" action and trying to set the status type "TL_CONTROL_SCREENING" for a transaction line, no option is displayed in the Status Value drop-down list. The issue occurs in the LITE domain even when the user has been granted with all read and write access from the main domain.

Statuses are now listed in the drop-down list for the "Set Control Screening Status" action on a transaction/declaration line in the LITE domain.

36469661

36525278

Control screening is taking place for every transaction line even when the compliance rule does not have the "For Transaction Line" checkbox selected. As a result, control screening performance is being affected.

Added a check to identify if the "For Transaction Line" flag is enabled for any compliance rule at group level, and if only this flag is enabled, then the application will continue screening at line level.

37287721

Create a "Status Type Filter" for a contact or a party. However, when you go to the respective manager, the Status button displays statuses other than the ones added on Manage User Access.

Added support for Status Type Filters for the following objects:

• Party

• GTM Transaction/GTM Transaction Line

• GTM License

• GTM Registration

• GTM Campaign/Gtm Campaign Line

• Item

Note: "GTM Transaction Reqdoc" is no longer supported in Status Type Filter.

37669944

Change the default value of the "Current" field on the Item Classification finder to "Yes".

Changed the default value of the "Current" field on the Item Classification finder to "Yes".

37728423

When the "PREFER CLASSIFICATION CODE OVER CODE GID" optional feature 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.

37753083

Facing performance issue while saving a trade transaction with a large number of lines (more than 200) having product classification codes. Sometimes the application times out.

On saving a transaction with large number of lines having product classification codes, the application now successfully saves the transaction without timing out.

37771277

The transaction line GIDs are not displayed in correct order in the transaction line table. Hence, whenever an outbound transmission is triggered from the application to an external system, the transaction lines are being sent in an incorrect sequence.

The transaction line IDs are now in sequence in the XML file generated for the outbound transmission of transactions and transaction lines.

37771279

License assignment uses too much SQL to retrieve a line item list.

License line items are cached instead of repeatedly loading them from the database. This will improve performance on running license assignment.

37777219

When adding Unit of Measure (UOM) conversions on an item via integration, a unique sequence number is not being generated. An existing sequence number from the GTM_Item UOM_Conversions table is used instead.

Now, new unique UOM sequence number is generated in inbound integration of an item.

37805644

Previously, Free Trade Agreement qualification process did not need all the components to be Harmonized System (HS) classified, i.e., even if some of the components were not classified, the qualification would run fine. However, currently it seems that for the qualification process to run successfully, classification for all the components has become mandatory. If not, the qualification is failing with the error "Classification Details missing on the Component".

When there is no classification code on any of the components in a structure, exception is not thrown while qualifying for a trade agreement. If the product specific rule contains tariff shift and if the qualification fails since the tariff shift is not applied, qualification status is updated as "Requires Review" with the reason code "Classification Code is missing on the component".

37829478

When running the "Assign License" action, the application should show a warning instead of an error message if there is no matching license found for the control present on the line.

Now, when running the "Assign License" and "Reevaluate License" actions, the application will show a warning instead of an error message if there is no matching license found for the control present on the line.

37829497

When running the "Unassign License" action, the application should not show error messages for the case where the line does not have any license control.

Now, when you run the "Assign License", "Assign License Show Options", "Reevaluate License", and "Unassign License" actions on a transaction/line where a line does not have any control, the application will not display such lines. In this case, the application will display the message "There are no controls available on one or more transaction lines."

37877317

After enabling "Allow Prorate on Multi-Sourcing", validation and computational errors (like the following) occur during the qualification process:

1. Currency conversion issue.

2. Sub-assembly is not getting expanded.

1. Currency values were displayed in USD (United States Dollar) always. Values are now calculated and displayed properly in the expected currencies when the "Allow Prorate on Multi-Sourcing" checkbox is selected.

2. A component is considered as multi-sourced when:

   1. It is not an intermediate sub-assembly.

   2. There are more than one item origin on the related item.

   3. When the overall sourced percentage across all the item origins is 100%.

37698483

Update the following points in the help topic "How to Assign General Ledger Codes":

1. Remove "that code" from the following paragraph: "In this example, the general ledger lookup key searches invoices by their involved party, accessorial code, and then cost type. If all three lookup key values exist on the invoice then the General Ledger Code in which this lookup key is added, that code would be assigned to the appropriate invoice."

2. Add clarification for the note: "Note: Only one general ledger code can be active per domain."

3. Update the example described at the end of the topic.

1. Removed "that code" from the mentioned paragraph.

2. Removed the note from the topic.

3. Updated the example describing the steps to assign a general ledger code on an invoice.

37722077

In the "Sum Quantity and Value Line to Header" help topic, provide a description for the action.

Added the following description to the "Sum Quantity and Value Line to Header" help topic: "Execute this action to total qualifier values on each of the transaction lines/declaration lines and display the total against the same qualifier in the trade transaction or the declaration."

37806150

Update the following in the help topics "Event Group Manager" and "List of Parameters":

1. 1. Add that "CURRENT TIME SHIPMENT STOP REDRIVE CONFIG GID" is only called when Event Group Attribute is set to "D".

2. Add that "ETA SHIPMENT STOP REDRIVE CONFIG GID" is only called when Event Group Attribute is set to "E".

3. Add that "STOP ACTUAL SHIPMENT STOP REDRIVE CONFIG ID" is only called when Event Group Attribute is set to "A".

4. Update the last part of the attribute "ESTIMATE_OR_ACTUAL" in the help topic "Event Group Manager".

1. Updated the last line of "ESTIMATE_OR_ACTUAL" parameter in the help topic "Event Group Manager" as follows: "The new option, D, considers the event location (latitude, longitude) as the current location at the time of the event. The action may update stop times of downstream stops according to the parameters associated with the CURRENT TIME SHIPMENT STOP REDRIVE CONFIG GID using the Recalculate Shipment Stop Times agent action."

2. Added the following sentence to the end of the functional description of the parameter "CURRENT TIME SHIPMENT STOP REDRIVE CONFIG GID" in the help topic "List of Parameters": "This parameter is only used when a shipment redrive is triggered by an event from an event group with the ESTIMATE_OR_ACTUAL attribute set to "D"."

3. Added the following sentence to the end of the functional description of the parameter "ETA SHIPMENT STOP REDRIVE CONFIG GID" in the help topic "List of Parameters": "This parameter is only used when a shipment redrive is triggered by an event from an event group with the ESTIMATE_OR_ACTUAL attribute set to "E"."

4. Added the following sentence to the end of the functional description of the parameter "STOP ACTUAL SHIPMENT STOP REDRIVE CONFIG ID" in the help topic "List of Parameters": "This parameter is only used when a shipment redrive is triggered by an event from an event group with the ESTIMATE_OR_ACTUAL attribute set to "A"."

37846617

Clarify the difference between "client session management" and "session management" in the online help.

Updated the Client Session Management topic in the help to delineate the difference between "client session management" and "session management".

37903047

Added section "Configuring Oracle Analytics and Reporting" to the Administration Guide.

Added reference to this section to 25B Release Notes > Action Required > Oracle Analytics Cloud.

37940872

Review and restructure the Data Management Guide.

Revised the Data Management guide. Content is now organized more cleanly and broken into clear DB.XML and CSV sections.

37798455

Add the Oracle Transportation Management required Policy Statements for customers to add to their tenancy in order to use Bring Your Own Key (BYOK).

Added the policy statements to the Security Guide, in the "Break Glass Support for Environments" chapter.