Oracle Fusion Cloud Transportation and Global Trade Management 25C Weekly Update Bundle: OTM_25C-20251212

38300431

Post-action check is unavailable for all appointment related actions in the application, including "Schedule Appointment" and "Remove Appointment." This limitation prevents the application from handling certain business scenarios that require validation or further processing after an action is performed.

Post-action check is now enabled for appointment related actions in the application using an audit action "ADD APPOINTMENT".

38468527

Support ORDER BY clause in work queue.

Added the "gtm.workqueue.handleOrderByClause" property for this enhancement.

When set to false, work queue will display an error when an "order by" clause is present in the saved query.

When set to true, work queue will support the "order by" clause in the saved query given the SQL is in the format (only using spaces and not tabs) 

The expected SQL format is:

select  <optional hints /*+ > <list of columns with/without- distinct/unique keyword> from <comma-separated table_names with alias> where(optional) <can include subquery/exists/not exists/union etc> order by(optional)

Note:
The first table after "from" keyword should be the table name of the object type for which the saved query is created, followed by the standard alias for that table.

There should be only one "order by" clause, at the end of the query.

The default value of the property is false.

38294445

Require work queue support for trade transaction, declaration, declaration line, and trade item structure.

Work queue is now supported for the business objects trade transaction, declaration, declaration line, and trade item structure.

38711330

When you download multiple files attached to a shipment with the same file name, the application displays the following error: "An Undefined Error Has Occurred."

While downloading multiple files with the same file name, the application will now append a version number to each duplicate file name (e.g., filename-v1, filename-v2).

Additionally, if the file name is null, it will be generated using its document GID with invalid characters (\ and .) replaced by underscores (_).

38464382

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.

38552527

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.

38555088

Provide a basic way for the Oracle Transportation Management to IDCS User Synchronization to be able to provide a Federated User attribute so that when that user is synchronized from OTM to IDCS, it will not trigger a new user email from IDCS.

By setting the new glog.security.user.idcs.everyUserFederated property, during the Oracle Transportation Management to IDCS User Synchronization, the IDCS Federated User attribute will be provided so that 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.

Note that when synchronizing a user from OTM to IDCS, if the IDCS user is already a federated user, OTM will not change this user to a non-federated user regardless of this property setting.

38613250

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.

38628852

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.

38526731

Clicking the “View tracking event” SmartLink on a shipment custom screen set does not load the tracking events. The screen displays indefinite loading.

This issue is now resolved, and you will be able to view the tracking events without an issue. Clicking the SmartLink will not consider the "Hidden" flag.

38548085

The error message, "User no longer holds the object", is displayed when setting the party or the restricted party status in Workbench.

Now, when a Work Queue is created on any object other than the contact, and the contact and the party-restricted party match is linked to the Work Queue based on the saved query, the actions to set the status on the contact and the party-restricted party match will not show the error.

38560299

The "Mark Claim Reviewed" action fails to execute when users select more than nine claims simultaneously.

The "Mark Claim Reviewed" action now works correctly when users select more than nine claims simultaneously.

37964637

Data model creation and report generation in BIP (Business Intelligence Publisher) server is failing due to pre-process function issue. This issue occurs only for the specific scenario where a user is created in a sub-domain, and is trying to access BI Publisher.

This issue has now been fixed.

38418792

The application fails to clear the Transport Handling Unit Profiles cache after loading the data from the database.

The application will now clear the Transport Handling Unit Profile cache successfully whenever a profile is created, updated, or removed. This ensures that the application will always use the most current profile data.

38446604

If you were migrated from Oracle Analytics Server, BI Publisher scheduled jobs would be in a paused state after the migration.

If you were migrated from Oracle Analytics Server, BI Publisher scheduled jobs will now be in an Active state after migration. However, these scheduled jobs will not get executed. You should manually pause the jobs and then resume them from the UI after migration.

38460286

During address validation, the application shows the wrong country code from the initial request when displaying possible address matches, even if a different country code is returned in the response.

An optional feature "ENABLE COUNTRY CODE VALIDATION FOR HERE GEOCODING " has been introduced to address the issue. When the optional feature is enabled, the application will compare the country code from the original request with the country code returned in the validation response. If the two country codes do not match, the application will display an error message alerting you of the discrepancy.

38489578

The namespace added for the "EMAIL COMPLIANT HTML" optional feature in an earlier release was not excluded from the resulting HTML. It is rejected by mail servers or mailboxes.

Excluded the namespace from the resulting HTML.

38534726

Unable to add new agent actions while creating a new agent or editing an existing one. The application also fails to insert the new agent action when clicking on the "+" button.

You will now be able to add new agent actions while creating a new agent and editing an existing agent.

38540734

Notifications are not in the contact's language.

Notifications are now sent in the language of the contact.

38447978

The application incorrectly matches the invoices to wrong shipments even when there is a check on source and destination locations defined in the invoice matching criteria.

The application will now match the invoices to the correct shipments when matching criteria is based on source and destination check.

38462788

The application incorrectly displays a warning message when the spot bid tender is awarded to the service provider with the lowest bid.

38479632

After migrating to Oracle Analytics Cloud, you are unable to run any report if the report file format is Excel (.xls).

You will now be able to run any report with Excel (.xls) file format.

38446373

When audit fields like insert user, insert date, update user, and update date are included in the result fields of a finder set and when you try to export table data from workbench, the audit fields are not exported.

The audit fields are now exported.

38382706

When updating an order release, the application encounters the error "ORA-01407: cannot update (???) to NULL at" while executing the "Order Release-Mod-Propagate Changes" agent action on inbound order release transmission.

The error when using the "ORDER RELEASE - MOD - PROPAGATE CHANGES" agent action occurred when there was a mismatch between the ship unit line number and the shipment ship unit line number. The error has been fixed.

38392422

Unable to create a new quote because the UI is timing out due to too many ship unit specifications existing, which were all loaded.

The ship unit specifications are no longer loaded during UI initialization.

You can now create a quote as expected.

38402838

When using auto-complete on a pick list, if the initial auto-complete search returned too many records, the application does not send additional requests to further filter results. The result is that auto-complete stops working.

Now, when using auto-complete on a pick list, the application will continue sending queries in order to properly display the auto-complete list regardless of the number of records returned.

38337731

When exporting data from workbenches, duplicate columns, incorrect formatting, and incorrect data occur.

Exporting data from workbenches now works without an issue.

38289831

During Service Provider Assignment (SPA), the application may select a carrier that is not part of the commitment allocation. This happens when the shipment option does not share the same interval, leading to incorrect carrier assignments.

The issue has been fixed by improving how commitment allocations are evaluated. Set the optional feature "SPA CORRECT SHIPMENT EARLY START DATE" to FALSE for the fix to work.

Note: SPA may not consistently honor commitment allocations unless this fix is applied, which ensures proper adherence.

38157376

The application does not display shipment tracking events from the "View Related Tracking Event" SmartLink, including copied events and events without shipment IDs that are matched to a shipment using "LEGACY SHIPMENT MATCHING".

An error is displayed when appending a search or creating a new search from the SmartLink after clicking the "Refine Query" or the "New Query" button.

Copied shipment tracking events and those matched using "LEGACY SHIPMENT MATCHING" will now be displayed properly.

No error will be displayed when appending a search or creating a new search from the SmartLink after clicking the "Refine Query" or the "New Query" button.

38206603

The order release action "Sync Shipped Quantity with Order" does not work correctly when the shipment ship unit does not specify the order release ship unit GID. Oracle Warehouse Management System sends in shipment actuals that do not have the order release ship unit GID on the shipment ship unit and their order movements are not created with the correct total package count.

The order release action "Sync Shipped Quantity with Order" only works for order releases with one ship unit per line order configuration. If the order release ship unit GID is missing from the shipment ship unit, the application can now derive the order release ship unit from the ship unit line and order release ship unit line, and create new order movements with the correct total package count.

38225547

An agent created with a custom shipment event based on the "Change Voyage Schedule" shipment action is triggered when the agent event is executed with the admin role, but it is not triggered when you use a custom user role with custom VPD.

The agent was not triggered because the data on the involved parties was being removed and re-added to the shipment, even when the values were not changed. Now, the data on the involved parties is retained when the values are not changed during the "Change Voyage Schedule" action, and the custom event is triggered with custom user role.

38225549

Audit Trail for voyage is not working.

Resolved the issue where Audit Trail was not recording changes for voyage.

38225554

38257874

The application does not display shipment remarks when you click the "View Related Remarks" SmartLink on the Buy Shipment screen.

Shipment remarks will now be displayed when when you click the "View Related Remarks" SmartLink on the Buy Shipment screen.

38275814

The application displays a Null Pointer Exception during bulk planning of multi-stop shipments when using a rate distance with the distance type set to "LOOKUP". This type requires the application to query the database for distances, such as when utilizing an external distance engine with cache control type set to "LOOKUP" or "SAVE".

Bulk plans for multi-stop shipments will now successfully use a rate distance with the distance type "LOOKUP" without triggering an exception.

38289482

When you change the order of the stops using the "Resequence Stops" action on shipments with appointments already scheduled on the stops, the appointment information screen continues to display the stop number that existed prior to the resequence.

Added a new property "glog.appointment.resequenceShipmentStops.updateApptStopNumber" to fix the issue with the appointment stop number on resequencing of shipment stops. The default value of the property is true (the corrected behavior).

37917742

Labels for new translation language are not reflecting on notifications.

The new translation languages are not appearing on the Language spoken drop-down list on the following UIs:

• Location accessed via Shipment Management > Location Manager

• Buyer accessed via Brokerage and Forwarding > Customer Management > Buyer

• Shipping Agent accessed via Brokerage and Forwarding > Shipping Agent Management > Shipping Agent Manager

• Customer accessed via Brokerage and Forwarding > Customer Management > Customer

Labels for new translation languages are now reflecting on notifications.

37981840

Data is not being loaded in the Green Dashboard. Instead, the following error is displayed: "View Display Error. Error generating view. Error getting cursor in GenerateHead."

Emission data is now correctly loaded and displayed in the Green Dashboard.

38001011

The font file is missing in the font mappings of the Business Intelligence (BI) Publisher.

Migrated custom fonts in BI Publisher. Note that only the font files are migrated and NOT the font mappings.

38016995

If you create a screen set that includes a Flex Field Attribute that is marked as NOT editable, and add the screen set in an Enhanced Workbench has a grouped table, the Flex Field attribute is not displayed as a column in the Enhanced Workbench.

Now, when a field is marked as NOT editable in the screen set, the column is correctly displayed in the Enhanced Workbench that has a grouped table.

38017002

When using the "Edit Quantities" action on shipments that have an order release line with packed item count of 0 (zero) and an equipment reference unit defined, a "java.lang.NumberFormatException: Infinite or NaN” error is seen.

You can now run the "Edit Quantities" action without any issues.

38017004

The Received Ship Unit Count is populating as 0 (zero) from OTM mobile application to web application when no data is entered in the Received Ship Unit Count field. Previously it would populate as null. Events triggered by a non-null value in that field are occurring as a result.

This has been resolved and any events triggered by a non-null value will not occur.

38024990

The REST GET call returns links for sub-resources, such as lines or reference numbers. When the line ID or reference number data contains a forward slash or uses a sub-domain, the generated links use the encoded version of the slash, which causes an error.

Modified the generation of links returned during a REST call to retain the forward slash in an unencoded format.

38027759

Consider a scenario where you decline a tender and the shipment gets re-tendered to the next service provider. If you again decline the tender with the same Tender Collaboration ID (even though its tender acceptance status is rejected), the new service provider’s tender is mistakenly declined.

The application now returns an error instead of declining the outstanding tender for the new service provider.

38033333

XSLT transformation with the REST communication method is not working for TenderOffer messages.

If a carrier uses the HTTPPOST communication method, this works as expected.

If a carrier uses the REST communication method, this is NOT working as expected.

Fixed the stylesheet transformation issue for REST/XML for TenderOffer.

38052229

When processing inbound transmissions and sending acknowledgements, the query that runs as part of this process could cause performance issues when there are very large number of records in the corresponding table that logs the transmission report details.

The query has been optimized to improve performance.

38096543

Outbound Voucher XML displays the VAT (Value Added Tax) rate in an exponential format instead of a readable decimal value.

The VAT rate will now be displayed as a standard decimal value rather than in exponential format.

38096581

After executing an action on an order release, the "Run Analytics" button is not working on the same object in Workbench.

This issue has been resolved. Now, every time a user clicks "Run Analytics", the object refreshes and the latest Analytics reportdisplays.

38096608

The application does not allow transit time calculation based on the rate service defined at shipment stops.

A provision is introduced to select the rate service, rate distance, and route code from shipment stops. A new optional feature, "USE INFO ON STOP FOR TRANSIT TIME RBI," when enabled, will allow the application to use information from shipment stops for transit time calculation, if available.

38097225

When the "Add Shipment Tracking Event" action is removed from the shipment screen during customization, it cannot be re-added.

This issue has been resolved. Now, the application will correctly recognize this action as a shipment action.

38099754

When trying to open the Enhanced Workbench with a layout defined in a sub-domain in a new window from the springboard or global search, you see the following error: "Error Loading - Forbidden".

You can now open an Enhanced Workbench layout defined in a sub-domain in a new window from the springboard or global search without an issue.

38115431

Even if data exists in the database tables, the Number of Stacking Layers and the Number of Loading Rows are not displayed on the Shipment Equipment view screen.

Fixed the issue of not displaying the Number of Stacking Layers and the Number of Loading rows on the Shipment equipment view screen.

38116287

When performing the "Adjust Shipment Cost" action on a shipment, every time you click "OK", an additional cost line is being inserted. As a result, multiple cost lines are added if you click "OK" multiple times.

The "OK" button will now be disabled after the first click to prevent multiple shipment cost adjustment requests from being submitted.

38120597

After upgrading to Oracle Analytics Server 7.6, migration of report schedule job in Business Intelligence (BI) Publisher is not taking place.

In Oracle Analytics Server 7.6, the approach to migrate job data during upgrades from n-1 to n version has been changed. Job data will be present in the UI after upgrade.

Note: BI Publisher scheduled jobs will be in a paused state after the upgrade. You should resume the jobs from the UI after upgrade.

38126731

Encountering the following error with the FedEx Rate API while attempting to rate an international shipment: "The carriage value cannot exceed the customs value. The carriage value is optional. Please refer to the FedEx Service Guide."

Additionally, values in weight, length, width, and height fields need to be rounded and restricted to only two decimal places.

To prevent this error, the application was updated to correctly calculate the declared value at the package level, based on the package count.

In addition, the application will round off and limit the values in weight, length, width, height, and volume fields to two decimal places.

38131839

The "Build Rates" action assigns the Rate Quality ID to all service providers. It is expected that only the backup service providers should be assigned the Rate Quality ID.

Now, only the backup service providers are assigned the Rate Quality ID.

38700184

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.

38568910

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 ML training and prediction processes. To enable this fix, set the property glog.ml.train.enableSvd.pc=true in the CUSTOM property set.

Note: Intermittent issues might be observed regarding training and prediction when using SVD. These will be addressed via issues 38687565 and 38687593.

38609207

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.

38622824

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.

38655853

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

38576931

The application encounters shipment building failure due to an error in the Service Provider Assignment (SPA).

A new property "glog.business.serviceprovider.serviceProviderOptimizer.useEnhancedFullyAllocatedLaneSlackPenalty" has been introduced to provide control over the enhanced slack penalty logic within the SPA. The default value is true.

38490705

When running a bulk plan with the "What-If" Scenario selected, the application fails to display the emission calculations. Conversely, the emission calculations are displayed correctly when the "What-If" Scenario box is not selected.

The application will now correctly display the emission calculations when running a bulk plan with the "What-If" Scenario selected.

38508619

When the property "glog.business.order.loadPlannedAndNROMs" is set to true, the order movement (specifically, the ship unit split off count) part of the screen becomes disabled or it disappears during the split order functionality.

The UI element for the order movement ship unit split off count will now be intentionally disabled when the property "glog.business.order.loadPlannedAndNROMs" is set to true. This ensures that the earlier unexpected disabling/disappearance of the element is prevented during split order operations.

38429785

The "Perform Training" action may fail with the following exception: "Start script failed for container..."

More memory has been allocated for Product Classification machine learning training.

38454754

There are two related issues affecting the location compatibility in the application:

1. The application displays an exception when initially checking location compatibility for locations with no "Corporation ID". After the initial error, the application incorrectly ignores the location compatibility for the same location in every subsequent check.

2. When you update the "Corporation ID" on a location, the application's cache is not refreshed. As a result, the application continues to run with the outdated data, failing to recognize the new corporation ID setting.

The multi-stop logic will now correctly handle location compatibility for all locations, including those without a corporation ID. Additionally, whenever a "Corporation ID" is updated on a location, the application will refresh its cache. This will ensure that the application always executes using the most current location data.

38365955

Bulk Plan can fail with a Null Pointer Exception (NPE) when the Service Provider Assignment is enabled (if the "PLAN SHIPMENTS WITH CARRIER COMMITMENT" parameter is set to true). This happens when a shipment has a cheaper option for a mode not included in the profile specified by the "MODE PROFILE ID FOR CARRIER COMMITMENT" parameter.

The bulk plan will now successfully complete without generating an exception.

38317814

When using FEU (Forty-Foot Equivalent Unit) or TEU (Twenty-Foot Equivalent Unit) capacity type, the location capacity does not limit the shipments. The expectation is that once maximum capacity has been reached, the application either will not plan an order movement, or it will plan the order movement the next day.

This issue has been fixed.

38346989

When configuring a fallback rate service, the application uses it even in cases where there are Hours of Service (HOS) violations or other service time infeasibilities. Ideally, in such cases, the order should fail to plan instead of falling back while planning.

The fallback to a secondary rate service will only occur when the lane is not configured with a service time on the primary lookup-type rate service (i.e., when the lane-service time setup is missing for the primary rate offering).

If the primary rate service has a lane service time configured, fallback will not be triggered in the following infeasible scenarios:

1. Hours of Service (HOS) rule violations.

2. Location calendar constraints.

3. Service time on the lane is shorter than the difference between Late Delivery Date and Early Pickup Date, even if the overall transit time falls within the range that the fallback rate service could accommodate.

This logic will apply exclusively to lookup-type primary rate services and will be governed by the property "glog.business.rate.rateoffering.applyFallbackOnlyWhenLaneUnavailable". The default value of this property is false.

For all other rate service types, the existing fallback behavior will remain unchanged.

Additional Considerations:

1. Ensure the parameter "FALLBACK RS NUM OF DAYS" is configured correctly.

2. Set the property "glog.business.rate.rateoffering.useFallbackRSForRIQOnly" to false in order to allow fallback logic to be applied during regular planning (not just rate inquiry).

38219528

The application intermittently displays a Null Pointer Exception while bulk planning. The same issue is also observed in Logistics Network Modeling planning intermittently.

This issue has been addressed by using the combined shipment built during evaluation in the iterative savings algorithm. Additionally, log lines will be added to capture any failure messages. This behavior will be controlled by the new property "glog.optimization.merge.columngenerationmerge.setCombinedPairableOnCluster".

Note: There is a potential impact to solution quality which will be fixed with the superseding issue 38315062.

38225552

When you bulk plan an order release with the network routing PERFORM ORDER REMNANT ROUTING logic parameter set as TRUE, you get a Null Pointer Exception (NPE) if the source or the destination is empty.

Resolved exception that occurred during the running of a bulk plan.

38289430

When attempting to split an order release using the shipment option before bulk planning for the second drayage and ocean shipment, the ship unit details (count, weight, and volume) of the order movement network routable leg are not updated. This leads to alignment issues. This occurs when the "Network Routable Order Movement" is unassigned.

Additionally, splitting an order release using the order movement option displays a Null Pointer Exception.

The application now fetches the shipment graph when performing a "Split Order" action, even if the Network Routable Order Movement is unassigned. This functionality is controlled by a new property "glog.business.order.loadPlannedAndNROMs". By default, the value of this property is false.

Note: This fix will only apply when the order is split using the shipment option, not the order movement option.

In addition, the application will now function correctly when splitting an order release using the order movement option.

38295576

The issue occurs when using network routing and bulk planning multiple order releases that are constrained to different itineraries, all of which share the same routing network. The network routing logic is unable to handle the same network appearing in multiple itineraries, causing it to select only one itinerary. As a result, any order constrained to a different itinerary fails to plan, since the network routing logic incorrectly assumes that the network can only be assigned by one itinerary.

The orders constrained to different itineraries that share the same network, will now be planned in the same bulk plan.

38052234

When calendar events are not internally sorted by start time, it causes the application to fail to identify the correct intersection of time ranges. As a result, driver calendar events are not processed correctly.

This issue has now been fixed.

38052236

The bulk plan results screen does not display accurate results. These include incorrect number of orders planned/failed, number of shipments created, and order movements planned. 

The issue is likely to occur when planning shipments using Network Routing with Multi-Pass and having orders that can fail on the first pass.

The statistics, including the number of orders planned/failed, shipments and order movements, will now display the accurate results.

38082262

Capacity is being consumed by orders not requiring an equipment, causing orders requiring equipment to fail to plan.

This issue occurs during order release bulk planning under the following scenarios:

1. A multi-leg itinerary or network is defined.

2. The final leg reuses equipment from the previous leg and allows multi-stop.

3. The final leg supports two different equipment groups.

4. One of the equipment groups (the smaller one) has a capacity limit enforced through a capacity limit group on the final leg.

5. The orders planned require at least two shipments on the final leg. For example, two orders, each of which fits individually on a truck of either equipment group, but cannot be combined on the same truck.

6. Both shipments are eligible to use either equipment group.

7. Network Routing and Dynamic Clustering are enabled.

8. The property "glog.optimization.networkrouting.createNewLegOptionsForReuse" setting as false (default value is true), is required due to equipment reuse described in point # 2.

In this scenario, an issue arises due to Dynamic Clustering not considering all eligible equipment groups for the final leg. As a result, the Network Routing capacity limit logic incorrectly assumes that both orders must use the smaller equipment group. If capacity is limited (e.g., only one resource is available for the smaller group), the logic fails to route one of the orders, even though both the orders are eligible for multiple equipment groups.

A new Network Routing logic parameter "USE MULTIPLE ITERATION SOLVE" has been introduced to address this issue. By default, its value is set to true (retains existing behavior). It is recommended to set the parameter to false for this scenario.

This parameter can be set to false when the routing problem (which legs to use) is not also an equipment group selection with capacity problem. If there is one final leg option with all the available equipment groups, then there is no need for the Network Routing Multiple Iteration Solve (which is used to decide which leg to use, based on capacity).

Note: This issue will not occur in scenarios where multiple final legs are defined, each associated with its own capacity group. In such cases, the new parameter "USE MULTIPLE ITERATION SOLVE" should remain set to true (default).

38131828

Unassigning an order release from a shipment takes longer time due to SQL query retrieving unnecessary TIHI data.

After order releases are unassigned, shipment ship units that remain on the shipment do not need to recalculate weight and volume unless a shipment ship unit is repacked. The application is streamlined to skip the recalculation of weight and volume on such shipment ship units to avoid SQL query that retrieves TIHI information for data such as Transport Handling Unit and Packaged Item.

38133542

For any transport mode type, the application filters out shipments that take more than 20 days in ETA (Estimated Arrival Time) training. But this is not ideal for Ocean transport mode type, and as a result, the training fails.

Users can perform training for non-TL mode types when their shipments take more than 20 days in ETA.

38400377

The "Optimize Driver Assignment" action fails to assign certain shipments to drivers. This issue occurs when the time required for a driver to drive from their next available location to the shipment's pickup location is longer than the shipment's available pickup window.

Earlier, the application incorrectly forced the driver's repositioning trip (from next available location to the shipment's start) to begin at the shipment's early pickup time, and ignored the driver's next available time. This fix will properly address the shipment's assignment to begin as early as the driver's next available time, even if this time precedes the shipment's scheduled pickup window. This ensures that drivers will be correctly assigned even if the travel time to the first pickup is long.

38376208

While attempting a bulk plan for a group of shipments, the "Optimize Work Assignment" action fails to create work assignments for any of the shipments, including the valid ones even if a single shipment among them has an invalid rate record.

If the property "glog.business.workAssignment.reCostColumnsWhileUsingCGinWA" is set to TRUE, the application will now remove the shipments with invalid rate records before generating work assignments. This will ensure the application successfully creates work assignments for all valid shipments in the initial run, without being halted by a single invalid one.

38610089

38211283

If the Rate Service does not include any HOS Rule Sets, the run-time of the Scenario Bulk Plan may increase.

This performance issue has been fixed.

38571819

When you run the "Upload Document" action on a campaign and update the document type by selecting from the drop-down list, the "DOCUMENT - MODIFIED" agent event on DOCUMENT does not get triggered.

The "DOCUMENT - MODIFIED" agent event on DOCUMENT is now triggered when the document type is updated via the "Upload Document" action.

38447794

The following error is encountered when selecting a single or multiple items and then running the "Assign Item Classification" action: "The classification Code does not exist". The same code can be assigned without an error when editing the item.

The issue does not occur when you select HTS US from a pick list.

Now, you can enter the product classification type and the product classification code and click Submit even without selecting from the Search list or the auto-complete drop-down list.

The application will pick the correct product classification type if the XID is unique; else, it will show a page where you can select the product classification type.

38189200

Enabling the "PREFER CLASSIFICATION CODE OVER CODE GID" optional feature causes "Out of Memory" error when item classification is being used on the Landed Cost Simulator.

On the Landed Cost Simulator, on selecting an item for product information, the application was loading all classification codes and giving an error when the "PREFER CLASSIFICATION CODE OVER CODE GID" was opted-in. This is now resolved.

Now, the application loads only the classification codes of the selected item.

38099829

When an order release transmission is sent from Oracle E-Business Suite to Oracle Transportation Management, it triggers mass deletion of GTM_PARTY_CODE information against certain parties causing the ULTIMATE CONSIGNEE setup to be removed against the party. As a result, AES filing failures happen.

This issue occurs only with XML transmissions sent from Oracle E-Business Suite.

When an order release transmission was sent from Oracle E-Business Suite to Oracle Transportation Management with "Replace Child" as transaction code, GTM_PARTY_CODE information against involved parties was deleted even if the involved party had a transaction code of "Insert/Update".

Now, the application uses the involved party's transaction code if present; else, it picks the parent (order release) transaction code.