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

16484281

The DBA.ADMIN user role should have a separate Access Control List.

The DBA.ADMIN user role now has a separate Access Control List called DBA_ADMIN. This change will not impact existing user privileges.

32409780

The application displays "SQLIntegrityConstraintViolationException" in the logs when attempting to copy involved parties on to an object.

The application will not try to insert duplicate involved parties while copying the involved parties on to an object. This ensures that the exception will not be displayed in the logs.

32409801

The application displays "SQLIntegrityConstraintViolationException" in the logs when attempting to copy reference numbers on to an object.

The application will not try to insert duplicate reference numbers while copying the reference numbers on to an object. This ensures that the exception will not be displayed in the logs.

34520885

Description on Rate Record Cost Operand for Rate Record Cost Operand ID:SHIPMENT.EQUIPMENT.EQUIPMENT_TYPE_GID is not updated. The users still see that as Equipment Group Type ID - the same that they see on rate cost of rate record Equipment Type ID.

Changed the description on Rate Record Cost Operand for Rate Record Cost Operand ID:SHIPMENT.EQUIPMENT.EQUIPMENT_TYPE_GID from Equipment Group Type ID to Equipment Type ID.

35176918

The application incorrectly validates negative cost deviations on invoice lines against the Invoice Approval Rule's allowable overall deviation amount. Instead of checking the absolute value of the negative deviation, the application performs a direct comparison of the negative value against the allowable amount.

The application will now check the absolute value of the negative cost deviation amount against the allowable amount defined in the invoice approval rule under overall deviation amount.

35477974

1. When the same object appears multiple times in a Grouped Table (either multiple parent related to the same child, or vice versa), and Mass Update is run against them, and then one of the related objects is not selected, the update is undone.

2. When a Grouped Table has enough records where only some of them are displayed, and Mass Update is run, then the "More" or "All" button is clicked, the update is undone.

Both of these cases are working correctly now.

35592802

An unsupported content type exception occurs when the response content type is returned as "application/vnd.oracle.resource+json;charset=utf-8;type=status", rather than "application/vnd.oracle.resource+json;type=status".

The responseContentType is parsed and only the "type", "subtype", and "type parameter" must be retained. For reference, this is the syntax for a media type - <type>/<subtype> ; <parameter>=<parameter_value>.

35951550

The application incorrectly passes the address line 1 during the calls to the External Distance Engine (EDE) instead of the primary address line sequence for that specific location.

The application will now pass the designated primary address line sequence during calls to the EDE.

36658478

When multiple VAT (Value Added Tax) rates are defined in VATCODE, the application does not pick up the latest effective rate.

When multiple VAT rates exist (some with and some without effective/expiration dates), the application cannot clearly determine the truly "latest" effective VAT rate.  When defining multiple VAT Rates, users must provide both the effective and expiration dates. When these dates are provided correctly, the application will successfully pick up the latest effective rate. 

36870915

The application does not load the default CUSTOMER layout after creating a custom manager layout for CUSTOMER screen.

The default CUSTOMER layout will now be loaded after creating a custom manager layout for CUSTOMER screen.

37283687

AWR (Automatic Workload Repository) reports are not using all of the available screen space.

Fixed the issue so AWR reports now display optimally.

37646694

Business data purge history record shows the incorrect status of COMPLETED and shows an incorrect end time, even though the purge job continues to run.

The Purge History now shows the correct status and end time.

37651188

Gateway timeouts waiting for Collect Diagnostic Log completion are misleading customers into believing the diagnostics are not being collected.

The default logging of the Collect Diagnostic Log utility has been suppressed in order to stop the application from waiting on completion and incurring gateway timeouts.

37734427

When the optional feature "DEPRECATE HERE ENGINE V7" is enabled, HERE Geocoding V7 is incorrectly deprecated.

Enabling the optional feature "DEPRECATE HERE ENGINE V7" will now deprecate HERE Routing V7 but not HERE Geocoding V7.

37890281

Standardize unexpected application errors into a friendly error message, and remove any additional details not needed.

All unexpected application errors have been standardized into a more friendly error message on the user interface and through the Log Viewer functionality.

For all users, any unexpected application error will now be: "A system error has occurred. Details can be retrieved via Collect Diagnostic Logs."

All additional error details are no longer accessible on the user interface or through the Log Viewer functionality. You will need to work with Support to find a resolution.

37909711

Unable to scroll through the generated HTML report from the customized action with action definition as "RUN_REPORT_SHIPMENT".

You can now scroll through the generated HTML report when running the report using customized action with action definition as "RUN_REPORT_SHIPMENT".

37912744

A driver that was unassigned from a shipment shouldn't be able to view the shipment and add events to it.

Added the "glog.mobile.addevent.checkShipmentAccess" property. When it is set to true, the mobile application verifies that the user still has access to a shipment they are viewing before allowing an event to be added. The default value is false.

37916310

Reduce the maximum size of the metric threshold email recipient field from 2000 characters to 256 characters.

The maximum size of the metric threshold email recipient field was reduced from 2000 characters to 256 characters.

37944421

When an agent of type "DOCUMENT" is created and the "Set Indicator" agent action is added to it, the application displays the following allowed indicator values: R(Red), Y(Yellow), G(Green), O(Orange), B(Blue), and W(White).

However, if the indicator is set to O, B, or W, the application displays the "java.sql.SQLIntegrityConstraintViolationException" error each time the agent is triggered.

All the values displayed in the application will now be valid for use with the "SET INDICATOR" agent action for an agent of type "DOCUMENT".

37970087

37996136

The "ORDER RELEASE - MOD - PROPAGATE CHANGES" agent action is failing when sending an order release update, adding a release line for an order release that has already had lines removed and added.

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

37997609

There is no Domain field when creating a new Rate Unit Break Profile.

You will now be able to select a domain when creating a new rate unit break profile allowing you to create the data in the desired domain.

38010578

Exporting a migration project is failing with "maximum open cursors for session exceeded".

A property "glog.integration.dbxml.numOfExpressions.{entityName}" is available to reduce the number of open cursors to avoid the exception.

Set it to a numeric value less than 100 for the resource that experiences the issue.

For example, glog.integration.dbxml.numOfExpressions.location=20. The entity name is the table name for the primary resource seeing the issue, and the value will vary and is determined through trial and error based on the data export requirements.

38016538

The Transportation Intelligence table E_LOAD_REJECTS, which stores errors generated during ETL process, needs to be partitioned.

The table E_LOAD_REJECTS is now partitioned. E_LOAD_REJECTS data older than three months will be removed at the end of every month. This applies to ETL failures.

38016997

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

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

38017003

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.

38017005

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.

38027760

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.

38033334

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 style sheet transformation issue for REST/XML for TenderOffer.

38052114

The application is deleting the order base line release instruction sequence number on the related order release line when values such as weight, volume, or transport handling unit are updated using the UI.

Added the column OB_LINE_REL_INSTR_SEQ to the order_release_line query so that the value of this column can be retrieved and saved to the order release line.

38052230

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.

38074357

A report is configured with the option "Off-line Database" selected from the Report Database drop-down list. A custom action is also created to run ths report.

When the report is executed through the "Report Manager" screen, it correctly connects to the offline database. However, when the same report is triggered using the custom action, it runs on the application OLTP (Online Transaction Processing) database instead.

Reports configured with Report Database set to "Off-line Database" will now correctly use the offline database when executed through a custom action.

38074367

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.

38074369

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.

38087077

Asynchronous delete is not possible for child resources such as shipment ship unit reference numbers.

Asynchronous delete via BATCH is now enabled for child resources.

38096545

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.

38096582

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

Now, every time a user clicks "Run Analytics", the object will refresh and the latest Analytics report will be displayed.

38096609

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.

38099755

When trying to access the Enhanced Workbench in a new window, the application displays the 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.

38099813

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 (_).

38099999

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.

38111760

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.

38116288

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.

38124889

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.

38126732

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.

The application will now correctly calculate the declared value at the package level, based on the package count.

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

38131841

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.

38148097

Data is not properly propagated to downstream shipments when the ship unit is bulk-splittable and a new equipment is added.

Downstream shipments will now correctly receive shipment actuals when new Shipment ship units related to the same order release (planned on the shipment) with bulk-splittable ship units are added.

38149447

Set a smaller fetch size for queries with nested cursors to improve performance.

Limited the number of open cursors by propagating the fetch size across all queries.

This is controlled by the property glog.sql.query.fetch.cursor. It defines the cursor fetch size. Default value is 10.

38159887

A "400 content error in message body" response is seen when you perform a table data export with a space before columns in the select list.

This issue has been resolved.

38165609

The automatic collection of the LONG RUNNING SQL metric component should be removed to reduce overhead.

The automatic collection of the LONG RUNNING SQL metric component has been removed to reduce overhead. Users may re-enable it via the Metric Component screen.

38168504

When the External Distance Engine (EDE) parameters such as the PCMILER USE_CUSTOM_SPEED parameter are added or modified, the application fails to invalidate the corresponding cached data in the Rate Distance object. Consequently, the EDE continues to use the old cached values until you manually clear the entire cache.

Now, whenever EDE parameters are either changed or added, the application will trigger a targeted cache refresh that clears only the data related to EDE, and does not affect any Rate Distance cache.

38168566

The expansion of child reference resources is not constrained correctly when using the expandChildRefs=true query parameter, causing performance issues.

The performance issues have been resolved, and the expansion of child reference resources has been modified to be constrained correctly when using the expandChildRefs=true query parameter.

38170180

When a status update is performed on a shipment through REST API, the related agent which should be triggered based on the status value is not triggered.

When a status update is performed on a shipment through REST API, the related agent will be triggered based on the status value.

38178024

When an invalid attribute is used during a POST/PATCH, the response does not contain as much useful information as it could.

It would be helpful to include the invalid attribute name as part of the error detail message.

Improved the error description when an invalid attribute is used during a POST/PATCH operation. The error description detail now identifies the invalid attribute that caused the error.

38180946

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.

38181943

After upgrading to the Autonomous Database (ATP), the reports that use the "Archive" report database type generate an error. For example, this message is displayed for the Global Trade Management custom report - GTM Transaction (OLPC) Archive Report: "PublicReportService::generateReport for reportAbsolutePath [Report Name] failed: due to Table or view does not exist". The report was working fine before the autonomous database upgrade.

The error was caused by missing privileges to read data from Oracle Transportation Management tables. Correct privileges granted privileges to read the Oracle Transportation Management table data.

38225548

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.

38225551

Audit Trail for voyage is not working.

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

38225555

When you run the "Build Shipment Set" action, the ship unit data is not loaded along with shipment data in the Shipment Set Criteria page.

Now the ship unit data loads successfully along with shipment data in Sourcing when the "Build Shipment Set" action is run on Shipment Set Criteria page.

38241914

The date entered on the Event screen reverts to the current date when you tap the Signature field.

The Event Date will now be retained when a signature is added to an event.

38253338

When trying to enable Auto Refresh on new, existing, or copied Enhanced Workbenches, the Auto Refresh option is grayed out and not clickable. This occurs for all users whose current user role is DBA.ADMIN.

Any user whose user role is DBA.ADMIN can now use the Auto Refresh option.

38253406

The "Capacity Override Applicable" checkbox is always selected on the Shipment screen when the parameter "USE CAPACITY OVERRIDE BY SERVPROV" is set to true.

The "Capacity Override Applicable" checkbox will now only be enabled if a capacity override is defined.

38257875

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.

38257889

38267832

Oracle Transportation Management needs better handling of non-existing email sender and recipient errors. If there is a missing sender or recipient mail address, it will fill the error log during the asynchronous sending of email. Unfortunately these error messages cannot be used to identify where the email sender or recipient addresses are missing.

Oracle Transportation Management now has better handling of non-existing email sender and recipient errors. A new property "glog.mail.assertMissingEmailAddress" has been added to address this issue and control the behavior of the application when this issue occurs. This new property has three value options:

1. fail: Abort the email without auditing.

2. log: Log the error and block the email from being sent. The email will be audited as a failure and increment mail metrics.

3. send: Process the email request, but with error handling greatly improved. The email will be audited as a failure and increment mail metrics.

Note the default property value is log.

Oracle Transportation Management now also has better missing email sender or recipient address handling when processing the mail request.

1. Mail Audit logging now handles a missing address (by not auditing).

2. Mail Audit persistence does not persist a blocked email with a missing address.

3. Mail Quota per Recipient is not impacted by an email with a missing address.

38275815

The application displays an 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.

38280924

For REST APIs, all base shapes for resources should be set as the default for the associated business object.

The base shapes for resources are now explicitly set as the default shapes.

The default shape for a resource can be overridden with a custom shape that has different attributes/children, by using the property "glog.fusion.cil.config.defaultShape.<version>.<resource name> = <custom name>"

See the "Available Custom Shapes" section of the "REST API for Fusion Cloud Transportation and Global Trade Management Business Object Resources Guide" for details.

38289483

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.

38295004

The application is not validating attribute values in a JSON payload during REST operations.

The application now enforces stricter parsing of attribute values in a JSON payload during REST operations. It validates that the attribute value matches the expected type (string/boolean/number/date/currency, etc.) for that attribute. The new stricter attribute parsing is controlled by the ENFORCE STRICT ATTRIBUTE PARSING FOR REST optional feature. This optional feature is enabled by default.

38302101

Trying to do mass update on the Shipment screenset displays a stray URL on the screen.

This issue is now resolved.

38316621

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.

38331355

The "Packaged Item ID" field of other lines are changed unintentionally when editing a line item (that is not on a ship unit) on the Line Item tab of the Order Release screen which is not associated with a ship unit.

On the Line Item tab of the Order Release screen, when editing a line that is not on a ship unit, the Packaged Item ID of other lines could have been mistakenly changed as well. That will no longer happen.

38333358

Remove unused items of Oracle Transportation Management that were tied to the deprecated legacy mobile application. These legacy items could be accidentally misunderstood to be part of the current mobile application.

Property: glog.mobile.max_session_timeout

User Preferences:

• Mobile User Order Reference Number Qualifier 1, 2

• Mobile User Shipment Reference Number Qualifier 1, 2

System Log IDs:

• Mobile

• MobileDetails

Removed the unused items.

38337639

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. Opt out of the optional feature "SPA CORRECT SHIPMENT EARLY START DATE" for the fix to work.

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

38337950

When sending a spot tender email to the contact group, not all members of the group get the tender email. The only way all members get the tender email is to enable the Broadcast to Members flag in the Contact Group screen.

All contacts will now receive tender notifications regardless of the Broadcast to Members flag on the contact group.

38371113

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

Exporting data from workbenches now works without an issue.

38391610

Data Queue tables are not getting truncated during weekends.

The application truncates the Data Queue table partitions every day instead of just weekdays.

38392423

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.

38402943

1. The REST documentation states the use of savedqueries is a HTTP POST request. However, it is a GET request.

2. Since the use of savedqueries is a GET request, the request body documentation needs to be removed.

3. Need proper documentation for the saved queries and advanced query custom actions, so that end users can distinguish between these.

4. On the Manage Collection section of the API guide, links for Paginating and Sorting are not working.

1. Changed the operation type of Saved Queries to GET (previously POST).

2. Removed request body and added query parameter details.

3. Made documentation changes on the Manage Collections page to distinguish between Advanced Queries and Saved Queries.

4. The broken links have been fixed.

38403734

Mail recipients are increasing strictness to DMARC (Domain-based Message Authentication, Reporting, and Conformance) requirements.

The SUPPORT RETURN PATH AND DMARC optional feature enhances Mail Validation to conform to the strictest mail recipient requirements. To resolve all Mail Validation warnings, consult the Configuration a Custom Domain and Sender section in the Administration Guide.

Note: This change does not block any outbound email currently accepted by recipients.

38407881

While doing RIQ NetworkRateAndRoute calls through Rest API, the result returns network legs that are not valid or inactive.

The calls now return only valid network legs.

38432673

If the "END NFR Location" option is set to "SAME AS FIRST SHIPMENT START", the work assignment process fails to work correctly when it is run. This occurs when the START Location Profile is not defined.

The application now ignores the profile locations definition on the Resource Schedule Instance (RSI) when the driver's End NFR Location option is set to "SAME AS FIRST SHIPMENT START". This change ensures the driver will correctly be routed back to the first shipment's start location even if the RSI location profile is defined.

38441679

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

Now, when using auto-complete on a pick list, additional requests will be sent in order to properly display the auto-complete list regardless of the number of records returned.

38447861

The addition of Agent Audit had an issue with DBXML audit import. Agents were not being activated or inactivated to pick up new changes.

When SUPPORT AUDIT OF IMPORTED DATA optional feature is opted in, Agent Audit now properly activates and deactivates agents as directed.

38448137

Action logs are being truncated at 10 MB due to the size constraint of normal log maximum size.

Removed the constraint of Action logs on the normal log maximum size to ensure that action logs are no longer truncated at 10 MB.

38457850

When running the order release action "Move Order to Existing Shipment" with the Optimize input selected, the application incorrectly displays two base costs on the final Shipment screen.

The Shipment screen will now correctly show only one base cost after the "Move Order to Existing Shipment" action is performed.

38461203

In the 25C Audit Event enhancement, a data error applied to new customers resulted in an inability to Revert audit events. This did not impact migrated customers.

Fixed the data issue.

38463578

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.

38464304

Constrain the number of simultaneous user requests to the Open Processes Diagnostic utility.

The number of simultaneous user requests to the Open Processes Diagnostic utility has been constrained.

38478608

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.

38493763

When viewing multiple mobile layouts, you cannot click Next to see the other layouts.

You can now view multiple mobile layouts by clicking Next.

38499150

Remove the optional feature DISABLE PUBLISH FOR STAGING TRANS TYPE.

The optional feature was added to disable publishing for transmissions with the Transmission Type of "STAGING". However, that approach was not correct.

Oracle Transportation Management will now publish every transmission, even if transmission type is "STAGING". The DISABLE PUBLISH FOR STAGING TRANS TYPE optional feature was removed.

38505459

Change the default value of the property glog.fusion.cil.restapi.config.patchParent.allowAddChild from false to true.

The default value was changed to true.

38510992

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 "USE RESPONSE COUNTRY CODE FOR ADDRESS VALIDATION" 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 to the discrepancy.

38510995

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.

38511783

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.

Due to increased external email strictness, excluded the namespace from email HTML.

38533710

The application fails to clear the Transport Handling Unit Profiles cache after a profile is created, updated, or removed.

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.

38545365

The application no longer respects contact language preferences. All outbound emails are in English or the default application language.

The application now respects contact language preferences on outbound emails.

38583685

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.

38588115

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.

38588117

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

38588118

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.

38150562,

38150572,

38150581,

38150583,

38150586,

38150589,

38150593,

38150595,

38150602,

38150609,

38150610,

38150616,

38150623,

38150627,

38150630,

38150633,

38150638,

38150641,

38150651

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

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

37567554

The application displays an exception when no shipments are available to create a shipment group.

The application will now ensure that required shipments are available before creating a shipment group.

37869955

On the View Commitment Count screen, when there are 0 (zero) allocations in the table, the "actual value" displays an incorrect character.

On the View Commitment Count screen, when there are 0 (zero) allocations in the table, the "actual value" now displays the correct character.

38000595

The application allows an order release to be moved to the ground shipment even though the order release pickup and delivery dates do not match the ground shipment pickup and delivery dates.

For example, if an order release has a pickup and delivery date before a ground shipment pickup and delivery date, the "Move Order to (Existing) Shipment" action does not fail.

Added the property "glog.business.action.moveOrderOrOMToShipment.checkOrderWindowAgainstGroundScheduleStopTime" as a fix for this issue. When this property is set to true, the order will be moved to ground schedule shipment only when the arrival time of pickup stop falls within the order/order movement pickup time window, and the arrival time of delivery stop falls within the order/order movement delivery window. The default value of this property is false.

38052235

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.

38052237

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.

38116228

In scenarios where there is no feasible drive for an order due to the maximum wait time being set to "0" (zero), the application returns a drive result with "null" times. This leads to two issues:

1. In the "Show Routing Options" action, an option with "null" shipment times may appear, which is not meaningful.

2. During bulk plan, a Null Pointer Exception (NPE) is encountered which causes the entire bulk plan to fail, even if the issue affects only one order.

Now, the drive results with "null" times will no longer be considered as valid solutions to avoid the display of invalid options in the "Show Routing Options" action and the NPE during bulk planning.

38131830

Unassigning an order release from a shipment takes longer time due to 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 recalculation of weight and volume is now skipped on shipment ship units to avoid retrieving TiHi information for data such as Transport Handling Unit and Packaged Item.

38188349

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

38225553

When you bulk plan an order release with network routing logic parameter "PERFORM ORDER REMNANT ROUTING" as TRUE, the application raises an exception if the source or destination is empty.

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

38289433

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

The application will now fetch 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.

38289536

The application intermittently encounters 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 in a future release.

38295577

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.

38366556

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

38415193

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.

38451808

Bulk Plan can fail with an exception 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.

38485827

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

The Product Classification machine learning training will no longer encounter this error.

38485828

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.

38533711

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.

38533714

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 section 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 section is prevented during split order operations.

38558905

The application incorrectly calculates continuous moves cost when using "Rate Offering" or "Order Release" domain profiles. This failure occurs because the application is unable to establish domain profile compatibility between the empty shipment (used for the empty leg of the continuous moves) and the rate offering's domain profile.

During continuous moves empty move calculation, the application created a shipment between the end of the first shipment and the beginning of the second shipment, and rated it based on the first shipment's rate offering. Before rating, the shipment checked for domain profile compatibility between the order release domain and the rate offering’s domain profile compatibility defined. As a result, the application incorrectly returned a null value for the empty shipment's domain profile, which led to a perpetual incompatibility with the rate offering domain profile.

The updated logic will fix this incompatibility by ensuring that the empty domain profile from the order release is explicitly considered compatible with the rate offering's domain profile. This domain check will now allow the continuous moves calculation to rate the empty shipment successfully and correctly determine the overall continuous moves cost.

38588119

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.

38409117

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.

38527227

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.

31834324

You can use the Planning Data Export tool to export data that includes an ACCESSORIAL_COST that is configured with a Rate Unit Break Profile.

When you try to import the same data, the import fails with the following exception: "[000148] Unknown rate_unit_break_profile_gid: <<rubp>PLAN002.RUBP_PROFILE_ID> [REBreakProfile::get()]"

Now, you can import data when the ACCESSORIAL_COST has a Rate Unit Break Profile.

37902810

When importing a Planning Data Export that includes CAPACITY_USAGE data, the USAGE column on this table is always setting to 0 (zero).

The capacity usages are now imported as is from the exported capacity usages records during the import process.

38052239

When you run the "Scenario Bulk Plan" action, the application excessively queries the database to fetch capacity usage.

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

27867093

Change the default Access Control Lists (ACL) for the following entry points to point to Order Actions, Shipment Actions, or Shipment Group Actions ACLs. These were groped to GTM ACLs but the actions exist on OTM objects.

GTM Transaction Actions
glog.webserver.util.QueryResponseServlet.action.move_order_release_to_ transaction
glog.webserver.util.QueryResponseServlet.action.order_release_view_related_transactions
glog.webserver.util.QueryResponseServlet.action.move_shipment_to_transaction
glog.webserver.util.QueryResponseServlet.action.shipment_view_related_ transactions

GTM Shipment Actions
glog.webserver.util.QueryResponseServlet.action.create_transaction_from_shipment
glog.webserver.util.QueryResponseServlet.action.remove_shipment_from_transaction
glog.webserver.util.QueryResponseServlet.action.propagate_from_shipment_to_trans

GTM Shipment Actions
glog.webserver.util.QueryResponseServlet.action.create_transaction_from_shipmentgroup
glog.webserver.util.QueryResponseServlet.action.remove_shipmentgroup_from_transaction
glog.webserver.util.QueryResponseServlet.action.propagate_from_shipmentgrp_to_trans

The default ACL of the following entries have been changed from GTM Transaction Actions to Order Actions.

Order Actions
glog.webserver.util.QueryResponseServlet.action.move_order_release_to_ transaction
glog.webserver.util.QueryResponseServlet.action.order_release_view_related_transactions

The default ACL of the following entries have been changed from GTM Transaction Actions to Shipment Actions.

Shipment Actions
glog.webserver.util.QueryResponseServlet.action.move_shipment_to_transaction
glog.webserver.util.QueryResponseServlet.action.shipment_view_related_ transactions

The default ACL of the following entries have been changed from GTM Shipment Actions to Shipment Actions.

Shipment Actions
glog.webserver.util.QueryResponseServlet.action.create_transaction_from_shipment
glog.webserver.util.QueryResponseServlet.action.remove_shipment_from_transaction
glog.webserver.util.QueryResponseServlet.action.propagate_from_shipment_to_trans
glog.webserver.util.QueryResponseServlet.action.create_transaction_from_shipmentgroup
glog.webserver.util.QueryResponseServlet.action.remove_shipmentgroup_from_transaction
glog.webserver.util.QueryResponseServlet.action.propagate_from_shipmentgrp_to_trans
 

36219230

In case of delta screening, running the "Restricted Party Screening" web/agent action for a party does not remove old, expired matches.

Now, expired matches are deleted even for delta screening.

37208424

When creating a new screen set for GTM_TRANSACTION_LINE, there are two "Date" columns available.

Now, GTM_TRANSACTION_LINE and GTM_SHIPMENT_LINE screen sets will not have two "Date" fields. They will have only one "Created Date" field.

37285911

When using the Restricted Party Workbench to export Party Matched Restricted Party, the file that gets generated is corrupted and cannot be opened as expected.

The following exception is displayed: "Excel cannot open the file 'Party Matched Restricted Party.xlsx' because the file format or file extension is not valid. Verify that the file has not been corrupted and that the file extension matches the format of the file".

The downloaded file can now be opened and viewed in Excel without any issues.

37642983

The properties related to the AES (Automated Export System) and the CCI (Customs Commercial Invoice) reports should be removed from the properties file.

The properties mentioned have been removed. These properties contained values of report parameters for the AES and CCI reports. There is already support to configure these parameters as "Additional Parameters" for the respective reports.

38099830

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.

38198242

Remove the property "glog.reports.useReportAddlParams" from the application.

Removed the property and its references from the saved queries.

38230243

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.

38478610

The following exception 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.

38594635

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 on any object.

36690546

Create an overview help topic for Oracle Fleet Management to explain the process flows for the products. Also add it to the table of contents and main Fleet help pages.

Created the new help topic "About Fleet Management" with a summary of Planning Results, Driver Management, Resource Management, Power Unit Management, Dispatch Board, Visibility etc.

38148800

Remove documentation related to deprecated action "Create Trade Transaction".

Removed references to action "Create Trade Transaction" from online help.

38241310

Order routing rules fail to apply with the Override Payment Method checkbox selected in the Order Routing Rule Details page.

The Override Payment Method checkbox is not used currently. Updated same in the help topic Order Routing Rule Details.

38313902

Add the following instruction in section "Setting Emission Factor UOM Codes" between 3 (Setting Up Emission Activity Rule) and 4 (Setting Up Emission Rule with Emission Factors) of the help topic "How to Configure Emission Calculation":

"Sign in as DBA.ADMIN and navigate to Configuration and Administration > Power Data > General > Units Of Measure. Create Emission Factor UOM with UOM Type as Quantity.

Note: Emission Factor UOM should have Weight UOM in the numerator. For example, KG/T-KM which tells the kilogram of emissions per ton weight is carried in a kilometer.

If you want to convert between two emission factors, ensure that you add To Conversion and its corresponding factor in the Unit of Measure for the Emission Factor UOM field."

The suggested changes are added to the help "How to Configure Emission Calculation".

38465189

In the Administration Guide:

• You should not attempt to register Common Approved Senders in the Mail Senders screen.

• When registering an Email Domain and/or Approved Sender, it is expected that they are available in all environments (Prod, Test, Dev) for that subscription.

• Suggest using a customer specific attribute when registering a custom Approved Sender using the Common Email Domain to make sure the address is unique across customers.

Updated the Administration Guide to better explain these points.

38651267

The Data Dictionary Diagrams are no longer relevant. With the addition of the JSON output, the diagrams are no longer needed.

The Data Dictionary Diagrams have been removed.