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.

8 July 2025 (Release 25.2.6.1-10.0.2506.1)

Case number	Description
Internal	Issue: When the node capacity locking is enabled, excessive locking is observed for `YFS_RES_POOL_CAPACITY_LOCK` table during `scheduleOrder` transaction. Solution: This issue is resolved.
TS017915766	Issue: The `YFS_INVENTORY_TAG` table is queried multiple times for the same record within a single transaction. Solution: This issue is resolved. A transaction-level cache has been implemented to store and reuse the records that are fetched from the `YFS_INVENTORY_TAG` table that reduces redundant queries and improving performance.
TS018925517	Issue: The findInventory API takes more time when large number of nodes qualify for sourcing. Solution: This issue is resolved and the findInventory API is updated to improve performance.
TS019341824	Issue: An exception occurs when a user creates a currency conversion in Applications Manager - Internationalization > Currency conversion. Solution: This issue is resolved.

2 July 2025 (Release 25.2.6.0-10.0.2506.0 - Patch 2)

Case number Description

TS019612802

Issue: If the subservice name in an integration service such as in the JMS receiver is saved with a leading or trailing space, it is not trimmed. So, when the Sub_flow_name field of the sub_flow record is stored after trimming the space, the RunTimeId attribute in the config_xml field of the same record retains the space as is.

Solution: If a new service is created or an existing service is saved from Applications Manager, leading or trailing spaces in the RunTimeId attribute and in the subservice name of the integration receiver is trimmed and stored in the database.

23 June 2025 (Release 25.2.6.0-10.0.2506.0 - Patch 1)

Case number

Description

TS019612802

Issue: The subservice name in an integration service, such as the JMS receiver, if saved with leading or trailing spaces, is saved with spaces and the extra spaces are not trimmed. So, a regression in behavior is observed with the service execution as part of validations that are done in server enhancements in the 25.2 release.

Solution: This issue is resolved. As part of this patch, fixes are made so that service execution can work even if the subservice name in a JMS receiver is saved with leading or trailing spaces.

6 June 2025 (Release 25.2.6.0-10.0.2506.0)

Note: There are database schema changes in the current release.

Case number	Description
TS017010118	Issue: The performance of the specific queries on `YFS_PERSON_INFO` table is impacted by the OOB index `PERSON_INFO_I4`. Solution: This issue is resolved. The index `PERSON_INFO_I4` is removed from the product. However, this index is not removed from the Order Management System database when the customer upgrades to this release version since index drops are suppressed as a part of upgrades in Order Management System. The customer can request for a manual drop of this index, if required. Tip: If this index is needed for some other functionality, it is advised for customer to add this as a custom index.
TS017698512	Issue: During scheduling in an IV integrated environment, if the schedule API call fails and transaction is rolled back, overpromising is observed intermittently for short duration of time. Solution: This issue is resolved.
TS018187889	Issue: The input to `YFSGetAvailabilityCorrectionsForItemListUE` does not include the XPath element Items/Item/Supplies/Supply/InventoryTag/Extn even when `getAvailabilityCorrectionsForItemList` template is included. Solution: This issue is resolved.
TS018322478	Issue: Sterling Order Management System retrieves the capacity for nodes with no inventory. Solution: This issue is resolved. A new property `yfs.readResourcePoolsForNodesWithInventory` is introduced. When the property is set to true, the product does not retrieve capacity for nodes with no inventory.
TS018623916	Issue: The receiveOrder API is not updating tag attributes in the `YFS_INVENTORY_TAG` table. Solution: This issue is resolved.
TS018716245	Issue: The FindInventory API output displays mismatched Estimated Time of Shipping (ETS)/ / Estimated Time of Delivery (ETD) and `ProductAvailDate` when following steps are performed: Create `NODE1` and `NODE2` with shipping calendar and working hours from 01:00 to 23:59 and Sunday as non-working. Mark May 22 and May 23, 2025 as holiday in the node shipping calendars. Create node transfer schedule from `NODE1` to `NODE2`. Mark Sunday as cannot ship and default transit time as 2 days, daywise override for Sunday to Thursday as 0 transit time, and Friday and Saturday as 3 days transit time. Create node transfer schedule and mark the following overrides: For May 20, 2024 - 4 days transit time For May 21, 2025 - 5 days transit time Adjust inventory at node `NODE1` for an item. Call the `FindInventory` API with `ShipNode` as `NODE2` and `ProcureFromNode` as `NODE1` and `ReqStartDate` as May 24, 2025. The `FindInventory` output is observed as follows: At `NODE1`, assignment `shipDate` is May 21, `NODE2` assignment `shipDate` is May 24, `ProductAvailable` date at `NODE2` is May 26. he `FindInventory` output is expected as follows: At `NODE1`, assignment `shipDate` is May 20 and at `NODE2` assignment `shipdate` is May 24. Solution: This issue is resolved. A new property `yfs.considerNodeHolidayDuringBackwardCalculationOfProc` is added with default value as false. If you set the property to true, during backward shipdate calculations, the product considers shipnode holidays from shipping calendar even if they are not marked in the node transfer schedules.
TS018921804	Issue: The reserveItemInventoryList API does not allow to update `ReservationExpirationDate` for the reservation that has past `ShipDate`. Solution: This issue is resolved.
TS019143912	Issue: In the Entity Relationship Diagram (ERD) documentation, the `ACTIVATE_FLAG` column in the `YFS_SHIP_NODE` table should be deprecated. Solution: This issue is resolved. In the Entity Relationship Diagram (ERD) documentation, the `ACTIVATE_FLAG` column in the `YFS_SHIP_NODE` table is deprecated.
Internal	Issue: For orders created from a contract, the contract order ID is stored in the `CONTRACT_ID` column of the `YFS_ORDER_HEADER` table. This column's data type does not align with the corresponding column in the `YFS_CONTRACT_ORDER` table. When SBA is enabled, the contract order key is stored in the `CONTRACT_ID` column of the `YFS_SBA_ORDER_LINE_STATUS` table. This column's data type does not align with the corresponding column in the `YFS_CONTRACT_ORDER` table. Solution: This issue is resolved. The contract order ID is stored in the new column `CONTRACT_ORDER_ID` of the `YFS_ORDER_HEADER` table for orders created from a contract. When SBA is enabled, the contract order key is stored in the new column `CONTRACT_ORDER_KEY` of the `YFS_SBA_ORDER_LINE_STATUS` table.

2 May 2025 (Release 25.1.3.2-10.0.2503.2)

Case number	Description
TS015917795	Issue: In the multi-colony setup where enterprise transactional records are on different colonies, the getPage API does not work properly from page 2. Solution: This issue is resolved.
TS017830654	Issue: The getPossibleSchedules API throws an `Invalid Delivery Method CARRY` exception in IV calls when called with `CARRY` line in an IV integrated environment. Solution: This issue is resolved. The getPossibleSchedules API is fixed to ignore the generating promise line when the delivery method is `CARRY`.
TS018194727	Issue: The loadInventoryMismatch API fails when the system process messages for same item with different nodes in multithreaded mode with same `YFS_INVENTORY_TAG` record insertion. Solution: This issue is resolved.
TS018279801	Issue: The `OrderBy` element does not work in `getOrderInvoiceList` call. Solution: This issue is resolved. The getOrderInvoiceList API is enhanced to support the `<OrderBy>` element. For more information, see getOrderInvoiceList API documentation.
TS018362995	Issue: The following information is not available in the manageNodeTransferSchedule API javadocs: `Only integer value for transit time is supported during transit time calculations in Promising APIs.` Solution: This issue is resolved. The manageNodeTransferSchedule API javadocs is updated.
TS018695289	Issue: In an IV Integrated environment, `getAvailableInventory` API call does not honor the `ReqEndDate` attribute is passed in API input. Solution: This issue is resolved.
TS018712644	Issue: When the `iv_integration.largeOrder.batchMode.enable` property is enabled in an IV integrated environment, the reservation fails intermittently due to unavailable lines even though the item is available. Solution: This issue is resolved.
TS019107328	Issue: When an invalid line error is thrown during order line cancellation with the order line key that is not present in the system, the order line key is not displayed in the error stack. Solution: This issue is resolved. The order line key is displayed in the error stack.

4 April 2025 (Release 25.1.3.1-10.0.2503.1)

Case number	Description
TS016928241	Issue: The Expected Shipment Date (ETS) on the order line is calculated incorrectly in the following scenario: Two nodes named NODE1 and NODE2 are created. A transfer schedule is set up from NODE2 to NODE1 with a 3-day transit time. Inventory is adjusted on NODE2 for ITEM1 with a quantity of 50. Ensure that the YFSGetAvailabilityCorrectionsForItemListUE user exit is implemented to return the input as output. An order is created with ReqShipDate of Current Date + 5 days. The order is scheduled. Solution: This issue is resolved.
TS017420917	Issue: The user is not able to modify any aspect of the routing guide after they add multiple freight term values. Solution: This issue is resolved. The manageRoutingGuide API is enhanced to update routing guide with multiple freight term values.
TS017883688	Issue: In an Sterling Intelligent Promising Inventory Visibility-integrated environment with Adapter Phase2, the getCompleteItemList API displays an error when a distribution group is not passed in the API input and is not configured in the basic configuration. Solution: This issue is resolved.
TS018034263	Issue: The order is stuck in the Reserved status in the following scenario: Two nodes named NODE1 and NODE2 are created. A transfer schedule is set up from NODE2 to NODE1 with a 3-day transit time. Inventory is adjusted on NODE2 for ITEM1 with a quantity of 50. Ensure that the YFSGetAvailabilityCorrectionsForItemListUE user exit is implemented to return the input as output. Ensure that the DS_I1 delivery service is associated with ITEM1. Create an order with `ShipNode` as NODE1 and `ProcureFromNode` as NODE2. Take the appointment for Delivery Service on current day + 5 days. The order is scheduled. Solution: This issue is resolved. The order moves to the `Procurement Transfer Order Created` status.
TS018047074	Issue: Inventory visibility reservation is not used during order creation if nonzero lead days are configured for an item. Solution: This issue is resolved.
TS018100972	Issue: The capacity is not freed from all nodes in the following scenario: A reservation is created for two items with 1 quantity each against two different nodes with a resource pool that is configured for each node of the release UOM (Unit of Measure). An order is created with two lines by using this reservation. The order is then cancelled completely. Solution: This issue is resolved. The capacity is freed from all nodes.
TS018342928	Issue: When an invalid line error occurs during the changeOrder API call, the error stack does not mention the order line key. Solution: This issue is resolved. The order line key is displayed in the error stack when an invalid line error occurs during the changeOrder API call.
TS018584241	Issue: The parent item description is displayed instead of the substitution item description in the getShipmentDetails API response after the substitution. Solution: This issue is resolved. The getShipmentDetails API is fixed to display the substitution item description in the response.
TS018643512	Issue: When the retry flag is Y from the `PAYMENT_EXECUTION` transaction user exit output, then the existing mappings in the `YFS_PAYMENT_REASON_MAPPING` table are deleted. Solution: This issue is resolved.

7 March 2025 (Release 25.1.3.0-10.0.2503.0)

Case number	Description
TS015402889	Issue: In a Sterling Intelligent Promising Inventory Visibility reservation call from Sterling Order Management System Order Schedule and release in IV-integrated environment with Adapter Phase2, the `Accessing context outside creating thread` error occurs intermittently. Solution: This issue is resolved.
TS016743014	Issue: When the payment rule is set to collect payment externally, then the infinite loop error occurs while processing refunds or discounts. Solution: This issue is resolved.
TS017012516	Issue: The orders that consist of the `NOT_APPLICABLE` payment status are not getting purged. Solution: This issue is resolved. The Order Purge Agent is enhanced to purge orders with the `NOT_APPLICABLE` payment status.
TS017186233	Issue: When multiple procurements are from the nodes with same cost, date and quantity are eligible to fulfill the request, order scheduling fails intermittently. Solution: This issue is resolved.
TS017732278	Issue: The getChargeTransactionList API does not have a limit on the maximum records that can be retrieved in the output. Solution: This issue is resolved. The getChargeTransactionList API is enhanced to retrieve the number of records based on the value that is set for the MaximumRecords attribute. Default is 5000 records.
TS017822614	Issue: In Postgres DB, IBA queries are taking longer time to run which is creating performance issues. Solution: This issue is resolved. The Sterling Order Management System application is enhanced to support IBA with `PostgreSQL` database.
TS018038757	Issue: getAvailableInventory API returns total accumulative availability and does not filter the availability to match the tag information that is provided at `PromiseLine` input. Solution: This issue is resolved. getAvailableInventory API is enhanced to return the availability based on the tag information that is provided as part of `PromiseLine` input.
TS018082167	Issue: The option to use AWS S3 sdk JAR files is not available for deploying applications. Solution: This issue is resolved. The AWS S3 sdk JAR files and the related dependent JAR files such as `jackson` and `joda-time` are added to the Application class path and are available for deploying applications.
TS018397034	Issue: In the getOrderInvoiceDetails API, when the `CollectionDetails` element is used without a child element, the stack overflow error occurs. Solution: This issue is resolved.
TS018438207	Issue: The `getExternalCostForOptionsUE` user exit is enhanced to show the capacity usage information when resource pool exists for the assignment nodes. Solution: This issue is resolved.
TS018479682	Issue: The PageSetToken attribute in the getPage API documentation is updated to provide information about maximum number of tokens that are retained in the cache. Solution: This issue is resolved.
Internal	Issue: When the following steps are performed, the Order/PriceInfo/@TotalAmount and Order/OrderLines/OrderLine/LinePriceInfo/@LineTotal attribute values are not calculated according to the unit price that is retrieved from the price list: Create a large order with BypassPricing set to `Y`. Call the changeOrder API to update an order header-level attribute such as CarrierServiceCode that is configured to impact pricing. Solution: This issue is resolved.

24 January 2025 (Release 24.3.9.2-10.0.2409.2)

Case number	Description
TS017809477	Issue: When you compress data for columns with compression enabled, the application cannot compress special characters. Instead, a duplicate text is created. Solution: This issue is resolved. If the application fails to compress the data, the uncompressed data is saved in the database, to prevent data corruption that might occur during compression.
TS017061933	Issue: The `Order Monitor` agent stamps the future date in NEXT_ALERT_TS instead of the current date when the agent is expected to again raise alerts until a specific date. Solution: This issue is resolved. The `Order Monitor` agent now stamps NEXT_ALERT_TS as the current date when it is required to again raise alerts until a specific date.
TS017701540	Issue: For external promotions, the award description that is provided in the input is not saved. Solution: This issue is resolved.
TS017262363	Issue: When a return order includes both bundle parent and component lines, duplicate component lines are created. Solution: This issue is resolved. In the return order creation XML, the `DerivedFrom` element now retrieves the derived order based on the combination of `DocumentType`, `EnterpriseCode`, and `OrderNo`.
TS016768318	Issue: When the `yfs.useNewRoundOffPriceForConventional` property is enabled, prices are rounded off, but charges are not. Solution: This issue is resolved. When the `yfs.useNewRoundOffPriceForConventional` property is enabled, similar to prices, charges are also rounded off.
TS017537692	Issue: When the api.security.mode property is set to `LAX`, the extended elements corresponding to a hang-off table are not populated. Solution: This issue is resolved.
TS017807843	Issue: When the getTrackingNoAndPrintLabel API throws exception, it is not recorded in the log file. Solution: This issue is resolved.
TS017171817	Issue: CurrentStorePickup/Pickup/@ProcureFromNode does not reflect the correct procure from node value when IsProcurementAllowed=Y is passed in input of the getStoreAvailability API. Solution: This issue is resolved. The CurrentStorePickup/Pickup/@ProcureFromNode now reflects the correct procure from node value from where procurement is evaluated in the getStoreAvailability API output.
TS012935603	Issue: When you perform the following steps, the sourcing scenario does not work properly with optimization based on the minimum number of shipments: Scheduling rule - The `Line Ship from Single Node` constraint is enabled and optimization on cost, number of shipments. The inventory availability picture for ITEM1 and ITEM2 is as follows: ITEM1 - 7 quantity available at NODE1 and 0 quantity available at NODE2. ITEM2 - 4 quantity available at NODE1 and 5 quantity available at NODE2. Call the findInventory API with ITEM1 and RequiredQty=1 and ITEM2 with RequiredQty=5. The expected output is that `ITEM1` must have 1 quantity fulfilled from NODE1, and ITEM2 must have 5 quantities fulfilled from NODE2. But, the actual output shows that for ITEM1, 1 quantity is fulfilled from NODE1, while for ITEM2, 4 quantities are fulfilled from NODE1 and 1 quantity is marked as unavailable. Solution: This issue is resolved.
TS017589883	Issue: In an Sterling Intelligent Promising Inventory Visibility-integrated environment with Adapter Phase2, under low availability conditions, on calling the reserveAvailableInventory API, the application occasionally displays a null pointer exception. Solution: This issue is resolved.
TS016707360	Issue: When you perform the following steps, the IBA does not work as expected: In IBA Rules, configure Order Selection Rules for Inventory Allocation to have priority orders in the first sequence and non-priority orders in the second sequence. In Node 1, 1 quantity inventory is available. Create a non-priority order with 1 quantity and schedule it. The order is scheduled. Create a priority order and schedule it. The order is backordered. Run the IBA agent and then schedule the Order agent. The priority order remains in the backordered status and the non-priority order remains in the scheduled status. Instead, the priority order must move to the scheduled status and non-priority order must be backordered. Solution: This issue is resolved. A new `CONSIDER_BACKORDER_DEMAND_FOR_IBA` rule is introduced with the default value set to `N`. Ensure that you call the manageRule API to change the value to `Y` to avoid this issue.
TS017771777	Issue: After you upgrade to fix pack 2403.2, the The input XML to `YFSGetAvailabilityCorrectionsForItemListUE` does not contain all zero supply records for nodes, which are eligible from previous sequences and had zero supply. Solution: This issue is resolved. A dummy supply is added to the `YFSGetAvailabilityCorrectionsForItemListUE` input for all the eligible nodes from previous sequences and had zero supply.
TS016804990	Issue: The data extract SFTP process to customer's AWS SFTP fails when they upgrade to the latest security policies of AWS from TransferSecurityPolicy-2020-061 to TransferSecurityPolicy-2024-01. Solution: This issue is resolved. The JSch (Java Secure Channel) library is upgraded from 0.1.55 to 0.2.21, which supports the latest key exchange algorithms for SFTP and works with AWS SFTP adopting security policies from TransferSecurityPolicy-2024-01.
TS014082596	Issue: Incorrect demand updates are observed for tag items with hot SKU when the Summarize and Maintain Total Supply and Demand rule is enabled. Solution: This issue is resolved.
TS015028263	Issue: The INVENTORY_KEPT_EXTERNALLY configuration is not inherited by organizations that are positioned lower by multiple levels within the organizational hierarchy. Solution: This issue is resolved.
TS018001678	Issue: The adjustInventory API, when used with `AdjustmentType` set to `ABSOLUTE` and `RemoveInventoryNodeControl` as `A`, it incorrectly generates inventory activity records, even when there are no `yfs_inventory_node_control` records to delete and no changes to the supply picture. Solution: This issue is resolved. A new record is now created only if `yfs_inventory_node_control` records are available for deletion, and a corresponding inventory activity record is not present.
TS017915766	Issue: When capacity locking is enabled, a lock is observed for inquiry APIs, such as findInventory and getPossibleSchedules that leads to high lock contention, and thus results in slowness. Solution: This issue is resolved.
TS017704664	Issue: The capacity cache is not updated intermittently because the process for updating the cache is terminated when it encounters an error. Solution: This issue is resolved. A new `yfs.capacityAvailablity.jvmcache.maxRetry` property is added, which governs how many retries the process can go through before the cache is terminated.
TS017600444	Issue: The orphan records in the `YFS_SUB_FLOW` table leads to issues while starting a server. Solution: This issue is resolved. The subflow records with no corresponding flow records that are stamped on them are ignored during the server startup after logging an error.
TS018186552	Issue: In Applications Manager, click Application Platform. Go to Security > Groups > Group Details > Security. In the Permissions tab, when you view resource permission group, some of the listed components do not display the correct component name. Solution: This issue is resolved.