Oracle Fusion Cloud Transportation and Global Trade Management 24C Weekly Update Bundle: OTM_24C-20241129

36519357

If you attempt to use the OPC (Oracle Public Cloud) URL, Oracle Transportation Management should present a page that shows the new OCI (Oracle Cloud Infrastructure) URL, and then automatically redirect to the presented URL after a set period of time. The presented URL should be clickable so that you can immediately go to the URL.

If you log in using the legacy URL, you will be presented with a temporary screen that displays the following message and then automatically redirects to the new URL. In preparation for the 24C update, please bookmark the new URL when you encounter this page:

"The current Oracle Global Trade and Transportation Management Cloud Service URL is being deprecated. You will be redirected to the new URL http://newURL in xx seconds. Please bookmark the new URL to avoid this message."

For more information, see Oracle Public Cloud OTM/GTM GEN1 URLs Will Be Deprecated in Release 24C (Doc ID 3017369.1).

37248689

When you run the action "Manage Appointments" on a location and search for a shipment group, shipment groups are not displayed on the dock manager for service providers when they have a user preference with the parameter "SHOW ASSIGNED UNTENDERED SHIPMENTS OF SERVPROV" set to false.

Now, shipment groups will be displayed in the dock manager even if the parameter "SHOW ASSIGNED UNTENDERED SHIPMENTS OF SERVPROV" is set false.

37213963

When attempting to submit an event in the Oracle Transportation Management mobile layout after removing the signature field, the screen freezes, preventing further actions. The issue resolves itself when the signature button is re-added.

An event can now be added in the mobile application even with the following turned off in the mobile layout:

• "photos": false

• "signature": false

37238096

Customer is exporting finder set result records. Finder set has reference number based column mapped on the Result tab. This reference number is supposed to capture some ID values prefixed with one or more zeros, i.e. leading zeros.

When the records are getting exported from the finder set, on the downloaded file those leading zeros are not displayed, i.e. only the non zero values are being populated.

The outcome is same irrespective of the value of login configuration parameter Export Format.

Now, when exporting the results from finder set/workbench:

• The Excel spreadsheet will preserve leading zeros, even for numeric string values.

• Date/Time columns will always be exported with their values if they are not empty, regardless of the time format selected in user preferences.

36971632

When attempting to modify accessorial costs in a custom Workbench using Mass Update, you are unable to enter decimal points (.).

This issue occurs only when the language preference is set to German. When the language preference is changed to English, the issue does not occur. 

An issue existed with the German language in that the comma (,) was not allowed in unit of measurement fields as a separator. When using a decimal point (.) instead it was misunderstood. 
Now, the comma is a valid value if the language uses a comma as a decimal point.

37092606

When you select multiple shipments and run the action "Change Equipment Group", the equipment group does not change on all of the shipments. For example, if you selected five shipments, the equipment group is changed correctly on four of the shipments only, and the cost of that one failed shipment gets doubled. This failed shipment and double cost issue occurs when you set up an automation agent triggered by the action. This issue does not occur if there is no agent.

You can now select multiple shipments and change the equipment group successfully by running the action "Change Equipment Group".

37224077

Bulk plan process takes more time than expected when unassigning an order release.

Performance is improved, and the bulk plan process completes successfully without any errors.

37224078

Bulk plan process takes more time than expected during shipment planning.

Performance is improved, and the bulk plan process completes successfully without any errors.

36988151

In the Enhanced Workbench, when you use attribute number fields and edit or enter values in those fields, Workbench shows values with precision only till three decimal places.

Fixed the issue where precision for more than three decimal places was not considered when displaying values in attribute number fields in an Enhanced Workbench.

37169747

Ship unit quantity propagation using the agent action "ORDER RELEASE - MOD - PROPAGATE CHANGES" is not working when you update the ship unit quantity to zero and add a new ship unit line to the same order release.

Ship unit quantity propagation now works correctly if you update the ship unit quantity to zero and add a new ship unit line to the same order release when multiple orders are on the shipment.

37187640

Shipment actuals inbound transmission fails with a timeout error after 30 mins of processing if there are more than usual number of ship unit lines on a shipment. In this case, the shipment has 1600 order releases, and each order release has one ship unit line. When you upload the XML, the action fails with an error after about 30 minutes of processing.

Shipment actuals process runs faster now and when you upload the XML, the action processes successfully in about 10 minutes.

36981549

When running the action "Recalculate Shipment Cost", if the dates are in the past, the application is intermittently displaying the following error: "Error creating Stop Order Bundle for Shipment Stop XXX.YYYYYY. Order movements that are picked up/delivered at this stop do not have overlap time windows."

Now, the action "Recalculate Shipment Cost" will not check time window emphasis while setting early pickup date on order movement. When the time window is in the past, the dates on the order movements will be used.

37092228

When formulating TiHi capacity, lines are sometimes splitting, via TiHi, into two ship unit records rather than into one ship unit with the correct count. There is a rounding off issue when the application is trying to determine if a ship unit is fully packed or not.

A new property, "glog.business.order.packing.utilizationRoundingUpThreshold", is added to avoid the rounding issue with a default value of 0.0. When utilization = 1, or utilization + this threshold >= 1, a packed ship unit is considered as full.

Set this property to a very small value like 0.000000001 to avoid any rounding errors.

37102244

When uploading a rates spreadsheet containing a typo in a certain column (e.g. Equipment Group Profile ID) and then downloading the Failed Rates spreadsheet, per online help, the last column is supposed to contain a relevant error message, and a comment in the cell with the error. However, the error message that comes in the last column is "An Undefined Error Has Occurred. Please Try Again Later." Furthermore, there is no comment indicating the error in any cell.

Now, the correct error message is shown in the comment cell of the Failed Rates spreadsheet.

37131574

When you run the action "Modify Tender", the XML tag <ExpectedResponseDt> is missing for the outbound tender offer XML.

Now, the XML tag <ExpectedResponseDt> will be available on the outbound tender offer XML when you run the action "Modify Tender".

37154717

The "Build Secondary Charge Shipments" action fails to execute when a load point is present on the order release, leading to a shipment reference number violation.

The load point shipment reference number qualifier will now be modified to allow multiple updates.

Additionally, the application will now update the load point reference number on the shipment when it already exists, rather than removing and adding a new one.

36959039

When you change the time range in the Dock Scheduling Gantt chart after adding a resource, the slots are misaligned.

Slots are no longer misaligned on Dock Scheduling Gantt chart when time range is changed.

37058448

When you run the "Finalize All" action on rates with accessorials, the user is updated for all accessorials instead of just the accessorials included with the finalized rates.

Now, when you run the "Finalize All" action, the appropriate accessorial costs are updated.

36827041

Order releases in a sub-domain do not appear in the Oracle Transportation Management Mobile Web Application.

Order releases will now appear in the mobile application even if they are in a sub-domain.

36922252

When attempting to upload a document to the Oracle Transportation Management Mobile Web Application that has a special character in the XID, agents with the DOCUMENT - CREATED event fail.

The DOCUMENT - CREATED agent will now work when a document is uploaded while adding an event in the mobile application.

36929528

In the 24C What's New document, the steps to enable the "ALLOW DATA DICTIONARY FOR DBA ADMIN ROLE ONLY" feature mistakenly references a different optional feature.

The What's New document has been corrected with accurate navigation steps for the "ALLOW DATA DICTIONARY FOR DBA ADMIN ROLE ONLY" feature.

36946341

The object ID does not populate in the Transmission Manager when sending an outbound transaction line transmission.

Now, when an outbound transmission is sent on a transaction line with the communication method as "REST", the object ID is displayed against the transaction record of the related transmission in the Transmission Manager.

36979378

If an order release has multiple shipments and a document is uploaded to one shipment and linked to all other shipments, an issue arises when unassigning the order release. While deleting the shipment with the parent document, the application tries to delete the document first; but it results in an exception as the document has references in its linked documents. However, the shipments along with other linked documents and the shared content are deleted.

A new property "glog.document.deleteLinkedDocument" is introduced to handle the issue. When the property is enabled, the linked documents of the document are deleted first followed by the document. While deleting the linked documents, the document content will not be deleted as it is referenced by its parent document.

36983661

When exporting a list of shipments from the shipment finder set, the Excel spreadsheet incorrectly shows two different date formats.

When exporting the results from a finder set, the Excel spreadsheet was not writing the date time and number values in Date Time/Number format; instead, they were written as strings, causing them to be incorrectly interpreted as numbers and date values. This issue has been resolved.

36987346

When you run the action "Merge Shipment Ship Unit", you see an error though all the basic criteria to merge the shipment ship units are met.

If the shipment contains orders that are not compatible, compatibility check is skipped for the shipment when you run the action "Merge Shipment Ship Unit" on that shipment.

37004529

After setting property "glog.currency.displayPrecision.<currency GID>" to "0" (zero), we can see that the UI honors the property setup. All shipment cost fields on the Financial tab show integer values (i.e., without decimal).

However, the change is not applied for costs displayed as hyperlinks in the Costs section on the Financials tab.

Updated fields in the Costs sections to show value in integer when the property "glog.currency.displayPrecision.<currency GID>" is set to "0".

36954094

Mass update and inline edit on the Enhanced Workbench are not working properly for mandatory fields or columns marked as constraints.

Now inline edit validates for columns marked as constraining. Multiple constraining columns will only show a validation for a single column.

No changes were made to mass update. Additional functionality will need an enhancement request.

37032944

When you un-archive a report in Analytics, you receive a "Virus Scanner is not reachable" error.

The virus scanner issue has been resolved.

36880722

Formulate region is not working with "City" created in the PUBLIC domain.

Since the region details consist of the combination of "US3ZIP" or "US5ZIP" in the hierarchy, you are required to provide both a "Low Range Value" and a "High Range Value." If multiple records exist in the "Geo Hierarchy" with combinations such as US3ZIP or US5ZIP along with other levels like "City," the application will select the first hierarchy entry, which may sometimes be "City." However, "City" does not include start and end offsets. As a result, the application displays an error stating that it requires the start and end offset, even though you have already provided the "Low Range Value" and "High Range Value" in the region details.

The records in "Geo Hierarchy" will be iterated to check whether at least one component contains a start offset and an end offset when a low range value and high range value are provided. If there is no such component found, an error will be triggered.

36949627

In Sourcing, when running the "Build Shipment Set" action using criteria, shipments that do no respect the criteria are included in the shipment set.

This issue has been fixed.

36958613

Post upgrade the power data screen shows the error: "javax.json.stream.JsonParsingException: Invalid token=EOF at (line no=1, column no=0, offset=-1). Expected tokens are: [CURLYOPEN, SQUAREOPEN]".

This happens when if you modify OTM delivered PUBLIC menus by creating and adding your own POWERDATA_LAYOUT menus.

Fixed issue when migrated PUBLIC menus contain user-defined POWERDATA_LAYOUT menus.

36965717

Post upgrade, receiving a "500 Internal Server Error" when trying to export data from a development instance.

The issue has been resolved.

37005585

If you open more than 20 OTM/GTM pages in a new window by right-clicking and selecting Open in New Window from either the Springboard or Navigator menus, then open a page in a new window from another pages menu, you may see a page expiration error.

This issue has been fixed.

37010499

The following errors appear randomly when opening or using Enhanced Workbenches: "Too many POST requests received from stripe" or "Too many GET requests received from stripe".

Reduced requests count when loading Enhanced Workbench.

36833890

When there is no calendar assigned to the resources, the Workbench Dock Scheduling Gantt chart shows resources with appointments incorrectly aligned.

The issue has been fixed.

36968740

When you run the action "Generate Ship Units", the ship units are not generated correctly when multiple order release lines each make a full pallet. For example, two lines with different packaged items that are both full pallets are added to the same ship unit.

Now ship units are generated correctly, and multiple order release lines that make a full pallet will be added to separate ship units.

36874589

Current outbound traffic to Oracle Integration Cloud (OIC) endpoint hosted in OCI is going over a Services Gateway rather than a Network Address Translation (NAT) Gateway. In this case, you should open a service request to change that traffic to go out of the NAT gateway instead of the Service Gateway.

Added the following note to the "IP Allow List for Outbound Integration" section of the Administration Guide.

"Note: There is an exception to this routing for traffic outbound to Oracle Integration Cloud endpoints. The traffic is going over the Service Gateway rather than the NAT Gateway by default. In this case, you need to open a Service Request with Oracle Transportation and Global Trade Management to change the routing of that traffic to go out of the NAT gateway instead of the the Service Gateway."

36878094

Go to Contract and Rate Management > Contract Management > Rate Record > Rate Costs tab, and click Add a Cost to create a Rate Record. The Rate Cost tab does not display this rate correctly after saving it.

The Rate Cost tab will now display the rate correctly after creating and saving a Rate Record.

36892555

Provide an option to hide the "Save" button on the Appointment Options booking screen.

Added a new property "glog.appointment.showOptions.hideSaveBtn" to hide the "Save" button on the Appointment Options booking screen.

The default value is false. Set it to true to hide the button.

36892648

When updating a rate factor source through the REST API, the patch operation fails and OTM responds with: "400 - Bad Request".

Updating a rate factor source using the REST API has been fixed to allow the effective date to be used with a PATCH operation.

36893773

Data Export current setting for the property "glog.sql.query.maxTimeout.dataReplication" is 300 seconds. This is causing many data export requests to timeout for the customer.

Changed the value of the property "glog.sql.query.maxTimeout.dataReplication" from 300 to 1800 seconds.

36799335

When you update an order via integration using "RC" (Replace Children) transaction code, the existing order ship unit remark qualifiers (where "Updates Allowed" is set to "One, Update") are duplicated instead of updating the existing value.

Now, when you update the order via integration using the "RC" transaction code, the existing order ship unit remark qualifiers (where "Updates Allowed" is set to "One, Update") will update the existing value.

36839983

Following an upgrade, the UTC (Universal Time Coordinated) function is repeatedly executing the following query resulting in a lengthy completion time:

SELECT ADJ_FACTOR FROM MISSING_TIME_ZONE WHERE TIME_ZONE_GID = :B1

The Report SQL query's performance was affected when it used the UTC package.

The UTC function ran a query to retrieve missing time zone data for each row internally, resulting in slow performance. This slow down was apparent when UTC function was executed hundreds of thousands of times during query execution.

Modified the UTC package to utilize caching, which in turn improves performance.

36649429

When changing the time range on the Appointment Gantt chart, the slots that are blocked by a calendar are shown incorrectly.

Calendar blocked slots are now shown correctly even though the time range is changed.

36649433

When you try to schedule shipment appointments on the Dock Manager by searching for appointments for the previous/next day using the links "Previous Unscheduled", "Next Unscheduled" and "Next", the application does not retrieve the dates correctly.

When you search for appointments for the previous/next day using the links 'Previous Unscheduled', 'Next Unscheduled' and 'Next' on the Dock Manager, the application displays the dates correctly.

Created a new property,  "glog.appointment.useOneDayDurationForPrevAndNextAction," which is false by default. When you set this property to true, a duration of one day is used instead of appointment display length for the Previous/Next actions on the Dock Manager.

36649463

When you release a schedule instance, the application does not take the rate offering constraint of the order movement into account when the order movement was manually created. So, when you find the rate, the application would choose the least feasible cost from all available rates of this service provider rather than the constraint.

The application will now fetch and consider the rate offering constraint of manually created order movements.

36649465

An intermittent issue is seen when you try to perform search on the Spot Bid screen.

Added new log ID TenderDebug to analyze the issue.

36658723

When you run the action "Re-transmit Spotbid Tender", you get the list of service providers. If the number of service providers are more than 10000 and you select one or few service providers from the list to send the spot bid, the application displays an error.

Added support for the property "glog.webserver.opentender.handleMoreServProv" for the action "Re-transmit Spotbid Tender/Re-transmit Broadcast Tender" to enable re-transmission if the number of service providers is more than 10000.

36690120

When you withdraw a spot bid tender, the notification sent to the additional contacts from the agent is sent with transaction code IU (Insert and Update) instead of transaction code D (Delete).

Now, when a spot bid tender is withdrawn, the transaction code D is sent to the additional contacts.

36694889

The application fails to copy the value from the Equipment Type ID from the original equipment to the new equipment while performing the equipment fleet action "Copy Equipment". As a result, the screen is blank.

The application will now copy the value from the Equipment Type ID from the original equipment to the new one while performing the equipment fleet action "Copy Equipment".

36725554

The application encounters performance issues with bulk plan due to "RETRIEVE GROUND SCHEDULES AND CONSOLS" consuming a significant amount of time when handling a large volume of ground schedules and shipments.

Now, the ground schedule retrieval query is optimized to improve performance.

36753881

Require an optional feature to minimize the total number of shipment ship units that remain after a ship unit count reduction is applied.

Added the optional feature "SMD OPTIMIZE SHIP UNIT COUNT REDUCTION" in shipment actual. When you opt for this feature, the total number of shipment ship units, that remain when you apply a ship unit count reduction, is minimized.

36759136

On the Shipment Tracking Event screen, the View button is not available for the "Ship Unit ID" field under the Ship Unit Received Quantities section.

A new property "glog.trackingevent.sShipUnits.useDropListWithRefnum" has been introduced to address this issue.

When this property is set to true, the drop-down list will show a combination of the shipment ship unit ID and a reference number qualifier specified by the property "glog.trackingevent.sShipUnits.displayRefnum" along with its associated reference number value, but the View button will not be displayed.

When the property is set to false, the drop-down list will only show the shipment ship unit ID, and the View button will be available.

36759143

Performance issue is encountered when loading the table W_SHIPMENT_STATUS_D, and it fails with an error.

Performance is optimized for loading W_SHIPMENT_STATUS_D table by:

1. Limiting the number of rows fetched from source with a join to subquery including only the delta shipments.

2. Including an EXISTS clause instead of a join to filter the READY_TO_LOAD_SHIPMENTS.

3. Removing the incremental date check on the SHIPMENT table.

36797454

Unable to run bulk plan when using a large number of orders. The following error is displayed: "SQL timeout of 600 seconds triggered for defaultQuery use case".

To address the issue of running a bulk plan with a large number of orders, we have implemented an optimized query to find the order releases with inactive locations. Use of the query is controlled by a new property, "glog.business.action.useNewSelectOrWithInactiveLocation". The default value of this property is false and provides the existing behavior. If the property is set to true, the new optimized query will be used.

36830734

The "Audit" action check does not work for an invoice line item.

The "Audit" action check will now work for invoice line items. A new property, "glog.invoiceLineItem.fetchDataQueryType.override", is introduced to override data query type for an invoice line item. If the property is set to true, the action check will work for an invoice line item. By default, the property is set to true.

36839165

37259608

The action "Build Buy Shipment on Primary Leg" fails with a null pointer exception (NPE) in the scenario when you plan an order release using location profile in the itinerary, the last leg on the itinerary is the primary leg, and the property "glog.business.conopt.ConoptConverter.CheckOrderDates" is set to true.

Now, no error is displayed when you run the action "Build Buy Shipment on Primary Leg" on a primary leg.

37231668

An issue occurs when creating or modifying a shipment (such as during bulk plan or the action "Recalculate Shipment Cost"). The application tries to add all related load points to the Reference Number field under the qualifier LOAD_POINT. This field has a 240 character limit. If there are numerous associated order releases, the combined load points text may exceed this limit and cause the bulk plan or the action to fail.

Revised the load point shipment reference number to a key-value string format providing the order load points along with their occurrence count as a comma separated key-value pair. This approach will reduce redundancy while preserving all necessary information and address the issue of exceeding the character limit for the reference number. If the character limit (240) is still exceeded, any excess characters will be truncated.

37225005

37118530

The issue is that the RateServiceCache can be filled up unnecessarily when the user has many rate services with transit time data for wide open lanes, even when these rate services are not being actively used during a planning action or during bulk plan. This is applicable for rate services of "LOOKUP" or "DAY DURATION". If the user has thousands of rate service records of these types with transit time data for wide open lanes, for example, then a single new transit time query may fill the cache with thousands of entries.

The fix introduces a new property "glog.business.rateservicescheduling.restrictCachePutByRateService". When this is set to true, only the transit time data that is actively being queried will be cached. No transit time data will be cached preemptively.

37096128

When you apply shipment actuals to a shipment without shipment ship units, the application displays a null pointer exception (NPE).

When you apply shipment actuals to a shipment without shipment ship units, NPE does not occur anymore.

36973292

When applying the Service Provider Assignment (SPA) logic, the application displays a Null Pointer Exception (NPE) potentially causing the bulk plan to fail under the following conditions:

1. When SPA is turned on, i.e. the parameter "PLAN SHIPMENTS WITH CARRIER COMMITMENT" is true.

2.  Either "USE PRIORITY IN SPA" is enabled or "SHIPMENT PREFERENCE CRITERIA" is used.

3.  Multiple shipments exist, with some being prioritized over others.

4.  When "SPA MAX DAYS TO CONSIDER" is set to two or more.

5. One of the shipments has varying possible start days, with a gap between the earliest and the latest start day.

The issue has now been resolved, allowing you to successfully plan all the orders during bulk planning.

37014995

When planning a multi-leg order using Show Routing Options, you select different special services using the "Refine Options" and save it. However, the application does not save the newly selected option. It shows the same option that the application had selected previously.

For example, navigate to Show Routing Options > Show Options > Select an itinerary > Show Options > Refine Options. The following issues are observed:

1. The cheaper option is not highlighted/selected on the UI. In this case, everything on both these options are the same except for the costs.

2. When you select a different option and save, it is not getting saved. Although, this option has the same rate record, rate offering, equipment, etc. This cost also has an accessorial cost from a special service.

Both the issues are now resolved.

1. The application will now highlight the cheapest option and select it on the UI when you select different special services using the "Refine Options".

2. You can now select a different option with "Refine Options" and save it. This fix ensures that even with the same rate record, rate offering, equipment, etc., and the presence of an accessorial cost from a special service, the selected option will be retained.

37015003

Multiple orders are failing with the error "java.lang.NumberFormatException: Infinite or NaN" during bulk planning. This error occurs only if an item package count is "0" (zero) in the order release line.

The issue has now been fixed. Multiple orders will now process correctly during bulk plan.

36984776

Agent with custom event not getting triggered post upgrade.

Agent events based on shipment calculated (i.e. totals) fields will now be raised when that field changes value.

36911738

An issue occurs when the "USE LOAD POINT PENALTIES IN PACKING" parameter in the Container Optimization logic is set to true. In certain cases, this can trigger a "java.lang.IllegalArgumentException" error, which disrupts the load point packing logic. As a result, orders may be split into multiple bundles, adversely affecting the solution's quality.

The issue has now been fixed. The exception will no longer occur in the load point packing logic.

36896882

When using Show Routing Options on an order, the Transit Time in the results does not add to the total transit time.

The UI has been updated to fix this issue.

36694891

The "Show Routing" option fails to select the correct rail rate after an equipment constraint is added to a specific leg on the itinerary. The application displays the error "No itineraries passed rule".

The application now correctly applies the itinerary equipment rule for each leg with its constraints. The "Show Routing" option will now pick the correct rail rate.

36710121

Application tries to diagnose an exception when bulk plan is persisting the shipment graph. Since the SEquipment GID has become null, the ShipmentSEquipmentJoin fails to persist even though the SEquipments are being persisted leading to the following exception: "java.sql.SQLIntegrityConstraintViolationException: ORA-01400".

Now, additional logging is added around the persistence of SEquipment data.

A new property "glog.business.shipment.extraShipmentUpdateLogging" has been introduced to enable this behavior. By default, the property is set to false.

36759141

The "Move Up" and "Move Down" buttons are inconsistently malfunctioning while performing the "Resequence" action.

The "Move Up" and "Move Down" buttons now function correctly during the "Resequence" action.

36830739

37181251

While assigning a driver to a shipment with a fixed stop, the application fails to calculate the service time.

The start time will now be determined by the earliest/latest shipment time windows. The Hours of Service (HOS) rule, defined as a period with its associated rest hours, will now be taken into account when setting the latest arrival time window at the driver's stop.

36609984

When "Hold as late as possible" is enabled in Work Assignment using the Column Generation logic, Work Assignment fails to generate a valid solution. However, it works fine with the Savings Merge logic.

The issue occurs in Work Assignment when using Column Generation to create a drive node. If the Resource Schedule Instance start location is different from the first stop, the current logic adjusts the earliest pickup time for the first stop to the next available time. This causes the drive to start at the wrong time, which can lead to missed stops and failure during the Work Assignment redrive at the end.

Work Assignment using Column Generation would now default "Hold as late as possible" to false. Order release constraints early/late pickup times are now considered accurately.

37065930

The "Revert Swap" action does not work on closed detachable trips.

This issue is now fixed.

36946790

When fleet assignment options costs are different only in decimal digits, cost options are not sorted correctly in ascending order.

The options are now sorted correctly by their value.

36830741

Require more information about fleet assignment.

Logs are added for fleet assignment to gather more information about driver assignment process and "Assign Driver" action.

36874689

When performing the action Shipment > Fleet Management > Assign > Equipment Type on a non-freight shipment equipment, the application successfully assigns the equipment type but displays an error message "An Undefined Error Has Occurred. Please Try Again Later".

Similarly, when performing the action Shipment > Fleet Management > Fleet Unassign > Equipment Type on a non-freight shipment equipment, the application successfully unassigns the equipment type but displays an error message.

The application now displays correct messages when assigning/unassigning an equipment type on a non-freight shipment equipment.

36725550

Moving an equipment (asset) from one location and bucket to same location and bucket de-links the asset from that bucket. This leads to the reduction of the bucket count.

Moving an asset from one location and bucket back to the same location and bucket will now be managed correctly.

Additionally, bucket count earlier was going to negative when a non-existent asset was moved from a source location. Now, this is also handled correctly and ensures that the bucket count will not go below zero.

37232465

Incorrect values are displayed for Planned Order Release and Failed Order Release counts in the Scenario Bulk Plan Results page.

When the retry count is greater than 1, the Planned Order Release and Failed Order Release counts in Scenario Bulk Plan Results page are now correctly displayed.

37143995

Capacities with more than one per day are required to update the Logistics Network Modeling (LNM) capacity tables after each shipment process.

The application now updates LNM capacities if they exist in the same scenario while persisting shipment graph and capacities.

36874649

When the Scenario Bulk Plan action is run on a modeling project, the Logistics Network Modeling simulated results do not match with the actual bulk plan results. Also, the capacity limits are being violated resulting in unexpected shipments. For instance, if the capacity limit is set to 5/day, more than 5 shipments are getting created.

This issue has been fixed.

36807435

When you run a Logistics Network modeling (LNM) project, the performance of the scenario plan is poor with data rules where there is a base scenario and a changed scenario that adds 16 ship units. It takes several hours for the LNM project to run when you work with bulk plans of 50 orders or more.

The order releases were always fetched from the database when a ship unit data rule was added on any scenario. You can now run the scenario with ship unit data rules, and the performance of the scenario plan is at par with the performance of the bulk plan.

36765292

When you try to export planning data using Planning Data Export/Import tool and select the Export Type as Logistics Network Modeling (LNM), the application throws a Null Pointer Exception (NPE).

You can now export the planning data successfully using the Planning Data Export/Import tool when you select the Export Type as LNM.

36780165

If there are any failed orders in the scenario results when you run bulk plan scenarios, and you click on the failed orders, the application throws a bad gateway error.

You can now click on the failed orders from the scenario results when you run bulk plan scenarios. You will be redirected to the Order Release finder results page, where all the failed orders are displayed.

37243783

Populate classification code in item classification producer.

Now, the application will populate the classification code column of item classification table when the column has a value in the database.

37173901

Incorrect control code is assigned to a trade transaction. When trying to delete it, the application is not allowing to remove it since the license is already assigned.

Now, the compliance screening action will delete a control (which is no longer applicable) only if there is no license assigned to the control. In such cases the property "gtm.compliance.skipControlsWithLicenseAssigned" will be used either to throw an error or to skip control deletion.

37100134

When you use the action "Release Transaction Lines" to authorize and release a sanction control hold, the application is not adding the given authorization in trade transaction line.

The issue was caused because the action "Release Transaction Line" on transaction lines was not considering the control categories "Other" or "Sanction". Only the license control screenings were being authorized.

Fixed the issue so that the action "Release Transaction Line" will also handle cases when the control category selected is "Other" or "Sanction".

37175233

Item qualification logic is incorrectly using HTS EU codes to determine USMCA (United States-Mexico-Canada Agreement) free trade agreement eligibility.

Resolved the issue to identify the product classification type of an item during qualification for trade agreement.

The order of identification is as follows:

1. Product classification type given on the action input page.

2. Based on the country of import.

3. Based on the item's country of origin.

4. Based on the matching item origin's country of origin.

5. Based on any of the trade agreement partners.

6. Any existing classification type on the item.

Set the property "gtm.roo.component.classificationType.considerAnyType" to true to consider any existing classification type when options 1-4 do not give any valid classification data.

37184780

Made the following changes to resolve the issue:

1. Added mapping of exemption control codes for TGL/C65, SCAL/C66, ACA/C68, and MED/C69.

2. Added mapping of authorization type for NAC/C67. (You have to create an Authorization Type of NAC in the PUBLIC domain). Confirmation number would be reported in X102 using the "Authorization" field value.

3. Removed mapping of exception control code for CTP/C39, APR/C47, and KMI/C48.

4. Changed the logic for N404 (country code); when N101 is CN, country codes VI, GU, and MP will use their own country codes instead of US in N404.

5. Changed the logic for N402 (state or province code); when N101 is CN, for country codes VI, GU, and MP, values will not be populated in N402.

37247377

Compliance control rules are not being applied post upgrade.

This issue is resolved. Now, when the party group is used as a criterion in the compliance rule, involved parties on the transaction line will be matched against the party qualifiers and the parties mentioned on the party group.

36841442

Calculate de minimis for each conditional phrase with "OR" in a product-specific rule.

De minimis was evaluated when the product-specific rule evaluation failed. Now it is changed to evaluate de minimis when the tariff shift evaluation fails.

37120696

Inclusion logic should be considered for all the components irrespective of the originating status.

"HS INCLUDED VALUE" should be calculated. Add a new value qualifier "HS INCLUDED VALUE" and update the formula "HS INCLUSION" to consider "HS INCLUDED VALUE".

When HS inclusion was part of the product specific rule, only the components which were non-originating were considered for HS inclusion evaluation - whether or not the classification codes of the components were part of the inclusion range. Now, that is changed to consider the HS inclusion range with all the leaf node components irrespective of the originating status.

A new value qualifier, "HSINCLUDED VALUE" is added and calculated as part of HS inclusion, which has the value of all the included components.

The formula "HS INCLUSION" is modified to consider the value qualifier "HSINCLUDED VALUE" instead of the old qualifier "HSINCLUDED VALUE OF NON-ORIGINATED MATERIAL".

"HSINCLUDED VALUE OF NON-ORIGINATED MATERIAL" is still calculated by considering the non-originating components and included components. This may not be calculated in future. It is recommended that you discontinue using this qualifier and start using "HSINCLUDED VALUE".

37064772

Updating a trading partner item via XML upload or inbound integration fails when the partner item type is "M" or "MANUFACTURER".

Item master upload now works with partner item type as "MANUFACTURER".

36958155

Running the action "Send Interface Transmission" on a party does not send reference numbers and remarks when the type is JSON.

The action "Send Interface Transmission" on a party uses "/contacts" API to send the JSON outbound. This API does not support reference numbers and remarks. There is another API "/tradeParties" that supports reference numbers and remarks. With this fix, we are providing the ability to use "/tradeParties" API in this scenario. The behavior can be toggled via the property "glog.integration.notification.contactEntity.isGtm".

This property is already being used to toggle the outbound XML behavior (whether to use GtmContact or Contact). The same property will now be used for JSON outbound behavior.

When the property is on, XML and JSON outbound transmission will use "GtmContact", "/tradeParties".

When the property is off, XML and JSON outbound will use "Contact", "/contacts".

36984042

During restricted party screening, party status shows "Required Review" even though the party is included in the exclusion list.

The address lines of the party contained extra spaces in the beginning, middle, and the end of text, which caused the issue. Now, a party included in the exclusion list will not show as a match during restricted party screening.

36882874

Global Trade Management contact interface Out XML Profile is not including remarks and reference numbers during transmission.

Out XML Profile now honors party remarks, reference numbers, user-defined category and code during contact integration outbound transmission.

36882877

Encountered performance issue when trying to edit/view an item with multiple item classifications. If there are multiple item classifications, classification code attributes of all the classifications are loaded and added under all the classifications. This is causing the issue.

Now, when the item UI is opened, classification code attributes are added properly under the related classification code.

36694895

On the Qualification Analysis, none of the components are showing as qualified even though some of them have valid and active qualifications.

On Qualification Analysis, even though some of the components had valid and active qualifications, they were not displayed as qualified. This is now fixed. 

Also, on running the qualification action when an item origin ID exists on the transaction line or a matching origin is found, the matching qualified item qualification's effective/expiry date was not being checked. This is also fixed. 

In both the cases, the application considers the date on header/line against the Date Qualifier given in the qualification logic configuration to check against effective/expiry dates.

36694897

Received 1-May-2024 as Early Pickup Date on an order release from XML integration. However, when a trade transaction is created, the date copied from the order is 30-Apr-2024.

Now, on running the action "Build Trade Transaction" on an order release, when Early Pickup Date/Late Pickup Date is copied from the order release to the transaction, the timezone is taken from Plan From Location if present, or else from Source location.

Similarly, for Early Delivery Date/Late Delivery Date, the timezone is taken from Plan To Location if present, or else from Destination location.

36759150

Trying to copy a trade transaction that was created from an order release, results in the error "Cannot add the GTM_TRANSACTION_REFERENCE_T record".

While copying a trade transaction that was created from an order release, the transaction retained a reference to the order release. This resulted in the unique constraint error. Now, reference of the order release will not be copied on to the new trade transaction. Hence, you will be able to copy a trade transaction without an error.

36759153

Compliance screening gets stuck when you try to screen a trade transaction with 200 lines.

Now, a trade transaction with a huge number of lines will not be stuck when performing compliance screening. This is enabled by a new property "gtm.compliance.ignoreAggregateFlag" with the default value false. If the property is set to true, compliance rule screening will be faster. If it is set to false, old behavior will continue.

36775139

A user creates  a copy of the GTM_LICENSE manager layout and deletes a field (for example, the Effective Date field).  On the customized layout, when the user clicks the Finished button after editing or creating a license, there is no response.

There was no response after you clicked Finished on the customized license page with effective and expiration dates fields hidden. This issue is now resolved. A confirmation page will be displayed after you click Finished on the customized license page with effective and expiration dates fields hidden.

36780163

When performing the qualification action on a transaction line, when the optional feature "USE QUALIFICATION LOGIC CONFIG ON DOMAIN LEVEL" is disabled, logic configuration parameters are not properly retrieved to perform qualification.

User preference level logic configuration is now retrieved along with logic configuration specified on the transaction's transaction type. If any parameter has a value in the logic configuration retrieved from the transaction, its value is overridden on the user preference level. (i.e., transaction logic configuration parameters are given priority).

36793009

On a trade transaction or a declaration, the customer enters the cost on the header in a local currency. However, once they allocate cost, the amount is added on the line and the currency is always being added as USD (United States Dollar).

This happens even if the currency exchange rates are available between USD and the used local currencies.

Now, the result of cost allocation is displayed in the local currency that was used to enter cost on a trade transaction or a declaration header.

36839774

Null Pointer Exception (NPE) is encountered during qualification when product classification code is "null" on an item structure on the transaction line.

Now, qualification on a transaction line will run without any error even when the product classification code is "null" on an item structure.