Resolved issues

Review the defects and fixes that are addressed in the updates.

Note: An issue that impacted the adjust inventory capability was identified in the 10.0.2409.1 version of Order Hub that was released on October 4, 2024. The issue is resolved, and the artifacts are updated as part of the same Sterling™ Order Management System 10.0.2409.1-Sterling-SSFF-All-Minor-Update fix pack, which was republished on 16 October 2024.

16 January 2026 (Release 26.1.1.0 - 10.0.2601.0)

Table 1. Resolved issues
Case number Description
TS020191329 Issue: In an IV-integrated environment, the unsegmented inventory is not getting considered properly when Use Enhanced Segment Based Allocation rule is enabled for inventory organization.

Solution: This issue is resolved and the unsegmented inventory is considered when the Use Enhanced Segment Based Allocation rule at inventory organization level.
TS020247475 Issue: When the Consolidation Agent runs in a multi-threaded environment, deadlocks can occur during shipment consolidation due to circular locking between orders. The parallel threads lock different orders and then wait for other locks while consolidating cross-order shipments that results in a deadlock situation.

Solution: This issue is resolved. The system is enhanced to bypass invoice handling during consolidation to eliminate circular locking dependencies and prevent deadlocks in a multi-threaded environment.
TS020529791 Issue: When an order line is canceled, the system does not delete all related order line relationships.

Solution: This issue is resolved. The cancelOrder API is fixed to remove all order line relationships for the canceled order line and its related lines.
TS020642815 Issue: The null pointer exception happens when LineCharges and AdditionalLinePrices together are provided in the CreateOrder API input. However, it works with either of one input.

Solution: This issue is resolved and both the LineCharges and AdditionalLinePrices element is supported.
TS020784861 Issue: The performance of getOrderList API during large orders gets slow due to the calls to YFS_ORDER_RELEASE_STATUS table with order by clause.

Solution: This issue is resolved. For the large orders, when getOrderList API output template does not have OrderStatus element, the order by clause to YFS_ORDER_RELEASE_STATUS table does not added that improves the performance of getOrderList API.
TS020812921 Issue: The getShipmentLineList API output template is missing in the PersonInfoMarkFor object that is required to populate specific fields in the Shipment Lines table.

When attempting to include the PersonInfoMarkFor object in the output template, the system throws an API security violation error and the required fields are not populated on the UI.

Solution: This issue is resolved. The getShipmentLineList output template is enhanced to support the PersonInfoMarkFor element to eliminate any API security violation.
TS020812921 Issue: The getOrderLineList API output currently does not return the allowed modifications information in the output and the Order Hub is not able to hide actions on lines that are not allowed.

Solution: This issue is resolved. The getOrderLineList API has been enhanced to identify the allowed modifications that can be performed for each of the lines so that the operations can be accordingly disabled or enabled in the Order Hub.
TS020814860 Issue: There are unnecessary queries during the createOrder flow when no corresponding input data existed and the related tables with no records.

Solution: This issue is resolved and the query execution is restricted to the relevant transaction tables. As a result, when no related details like references, line options, charges, or tax breakup are provided in the createOrder input and the queries to those tables are no longer triggered.
TS020819150 Issue: The cancelOrder API fails if an order line has more than one shipment and one of the shipment is already canceled.

Solution: This issue is resolved.
TS020965126 Issue: The consolidateToShipment API does not consider Expected Shipment Date and Expected Delivery Date for shipment consolidation.

Solution: This issue is resolved.

The consolidateToShipment API is enhanced to consolidate shipments based on Expected Shipment Date and Expected Delivery Date. These attributes are added in Applications Manager > Logistics Management > Logistics > Shipment Planning. When checked the consolidateToShipment API finds the existing matching shipments based on these attributes.