Resolved issues

You can review the fixes that are addressed in each fix pack version.

Note:
  • If you are installing fix pack 10.0.2206.2 or later, the underlying fix pack installer that is used is not a delta package jar anymore. The installer is now a full installer jar.
  • For more information about the installation instructions for any fix pack, see the Fix_Pack_Installation.txt file that is available within the fix pack installer zip.
    Important: You must always back up your existing runtime directory before starting the fix pack installation.

Version numbering for Continuous Delivery support policy

Effective from June 2022, the product lifecycle policy for IBM® Sterling™ Order Management System Software has changed from Standard support to Continuous Delivery support. A new Continuous Delivery version numbering scheme is introduced. The first update to include the numbering is in Q2 2022 which is 10.0.2206.0 where first two digits remain 10.0. The third digit indicates major quarterly updates including two-digit year followed by the two-digit month. The fourth digit indicates minor updates and increments sequentially from 0 for each major update.

For more information about adopting Continuous Delivery support policy, see Adopting Continuous Delivery support policy.

To review the fixes that are addressed in each fix pack version that are released before 2025, see Archived resolved issues.

6 July 2026 (Release 10.0.2607.0)

Case number Description
TS022219622 Issue: During automatic sales order creation from contract delivery schedules, sales orders were not created when the customer associated with the contract was inactive. In such scenarios, the system generated a generic error alert. However, the alert did not include the contract order number or delivery schedule number. As a result, users were unable to quickly identify the affected contract schedule and determine the reason for the order creation failure.

Solution: It was incorrect to consider the contract orders of an inactive customer and process them altogether before eventually reaching an exception scenario during sales order creation.

This issue is now resolved. The automatic sales order creation agent ignores delivery-scheduled lines generated for contract orders belonging to inactive customers and does not attempt to create sales orders for them. Additionally, when a user attempts to create orders manually from a contract order, the system validates the status of the associated customer. If the customer or customer contact is inactive, the system displays an error message indicating that the Customer or Customer Contact is Inactive.

5 June 2026 (Release 10.0.2604.2)

Case number Description
TS021623798 Issue: On the DST end day, orders scheduled after 11:00 PM resulted in backorders when the Maximum number of days order can be shipped/delivered beyond its requested date configuration is set to 0.

Solution: This issue is resolved. To ensure proper handling of orders during the DST switch period, enable the yfs.adjustTimeStampForDstSwitch property.
TS021913722 Issue: During shipment consolidation, the Expected Delivery Date (EDD) is being recalculated when timestamp values are provided that resulted in the existing shipment's delivery date/time being unintentionally modified.

Solution: This issue is resolved and the consolidation logic is enhanced to retain the original Expected Shipment Date (ESD) and Expected Delivery Date (EDD) that prevents the unintended timestamp updates during shipment consolidation.
TS021920470 Issue: The API Javadocs generation fails to produce the expected index.html file due to the presence of non-ASCII characters in Javadoc source comments that results in incomplete API documentation output.

Solution: This issue is resolved and the affected Javadoc source files are updated the to remove unsupported characters and ensure compatibility with ASCII-based environments that enables successful generation of the complete API documentation including the index.html file.
TS021992168 Issue: For orders in a partial status, the status description is displayed in mixed languages because the Partially prefix was derived from the Hub Organization locale while the status description itself was derived from the logged-in user's locale.

Solution: This issue is resolved and the locale conversion logic is updated so that the entire status description, including the Partially prefix and status description is consistently derived from the logged-in user's locale and eliminates the mixed-language status displays.
TS021921826 Issue: The tag attributes are not getting updated in the YFS_INVENTORY_TAG table for Purchase Orders and Transfer Orders under certain over-receiving scenarios.

Solution: This issue is resolved.
TS022144285 Issue: The getSupplyDetails API throws a null pointer exception when invoked with an output template that did not include the <SupplyDetails> element.

Solution: This issue is resolved.
Internal Issue: In automatic sales order creation from contract schedules, the requested delivery date (ReqDeliveryDate) was not consistently updated at the order header level for orders created per grouping.

Solution: This issue is resolved. The automatic order creation logic has been enhanced to ensure that the requested delivery date is consistently derived and populated for automatically created orders. The ReqDeliveryDate on the order header is now always derived from the requested delivery date of the delivery scheduled line.

4 May 2026 (Release 10.0.2604.1)

Case number Description
TS021295953 Issue: In a OMS-SIP integrated environment, the reserveAvailableInventory returns invalid output intermittently that has missing fields.

Solution: This issue is resolved.
TS021123379 Issue: The demand discrepancy observed during cancellation of Procurement PO/TO in scenarios involving substitute items.

Solution: This issue is resolved.
Internal The bundle support is added to the Sterling Intelligent Promising Optimizer integration and can be enabled by setting the property sip_integration.optimizer.bundle.support.enable to Y. For more information, see sip_integration.properties.
Internal Issue: The TagBreakup is not included in RTAM availability information.

Solution: This issue is resolved. A new yfs.yfs.RTAM.IncludeTagBreakupForNodeOrDG property is introduced to include TagBreakup in RTAM availability information. For more information, see Sterling Order Management System Software yfs.properties file.
Internal Issue: The supply updates to inventory visibility on confirmShipment is missing tag information for the time-sensitive items when the shipment line does not specify a ShipByDate and the Assume FEFO If A ShipByDate Is Not Provided rule is enabled.

Solution: This issue is resolved.
Internal The tag support is enabled with OMS-IV Phase 1 integration. For more information, see Deploying Sterling Order Management System Software for integration with Sterling Intelligent Promising Inventory Visibility.

6 April 2026 (Release 10.0.2604.0)

Case number Description
TS021298229 Issue: The row lock contention is observed in the YFS_ORDER_HEADER table when getShipmentLineList API is processed.

Solution: This issue is resolved. The SelectMethod attribute is introduced in the getShipmentLineList API input that allows control over row locking behavior with values like NO_LOCK and NO_WAIT.
TS021506635 Issue: In OMS-SIP integrated environment, the CustomIvInvokeRestAPI SDF service is failing if the input contains accented characters.

Solution: This issue is resolved.

9 March 2026 (Release 10.0.2601.2)

Case number Description
TS020873642 Issue: The AdditionalLinePrices element is not being persisted when received from the OrderRepriceUE output.

Solution: This issue is resolved. The code is enhanced to support the AdditionalLinePrices element that enables the data to persist into the database and the associated data is used in the order total calculations.

If you want to process AdditionalLinePrices element from OrderRepriceUE, enable the yfs.order.pricing.enableAdditionalLinePriceProcessingFromOrderRepriceUE property from the SMA console.
TS021379461 Issue: If the getOrderList API is invoked on a large order and template has attributes of ReturnableQty, Status, MaxLineStatusDesc, MinLineStatusDesc at the OrderLine element, the getOrderList API returns blank status fields in Status, MaxLineStatusDesc, MinLineStatusDesc and ReturnableQuantity as 0.

Solution: This issue is resolved. For the getOrderList API, the attributes of ReturnableQty, Status, MaxLineStatusDesc, and MinLineStatusDesc at the OrderLine element are correctly populated for large orders.

If want to remove order by clause to improve performance, enable yfs.order.getOrderList.skipOrderBy property from the SMA console. This property also populates the Status, MaxLineStatusDesc, MinLineStatusDesc and ReturnableQuantity fields correctly.
TS021407429 Issue: A NullPointerException is thrown when debug logging is enabled and YFSGetHeaderChargesForShipmentUE does not return newHeaderCharges in the YFSExtnOutputHeaderChargesShipment object.

Solution: This issue is resolved. The newHeaderCharges from YFSGetHeaderChargesForShipmentUE is handled properly.

6 February 2026 (Release 10.0.2601.1)

Case number Description
TS018267429 Issue: When infinite loop detected exception is thrown, the payment hold is not applied on the order when same order is processed by another process.

Solution: This issue is resolved.
TS021006603 Issue: The executeCollection API cannot handle reauthorization at expiration when the PostgreSQL database is used.

Solution: This issue is resolved and the reauthorization is handled by executeCollection API while using PostgreSQL database..
TS021089591 Issue: The findInventory API is unable to retrieve available supply data from inventory visibility when the OMS installation locale is set to a locale other than UTC In an OMS-IV integrated environment.

Solution: This issue is resolved.
TS021270086 Issue: Building extensions.jar on JDK21 toolkit for Ubuntu 22.04 fails while building the war for wsc.

Solution: This issue is resolved.
TS021298352 Issue: The getOrderList API throws ClassCastException when the output template is passed as file path.

Solution: This issue is resolved.

16 January 2026 (Release 10.0.2601.0)

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.