Archived resolved issues in 2025

1. Set the value of the yfs.overrideTransferScheduleForProc property to true.
2. Configure a carrier service for a node transfer schedule.
3. Create and schedule a sales order. A procurement transfer order is created.
4. Schedule the procurement transfer order.

Solution: This issue is resolved. Now, the transit time that is configured for a carrier service is used.

Solution: This issue is resolved. The Capacity Purge agent is enhanced to include a new IgnoreLeadDaysForInactive parameter. When you set the value of the property to Y, the agent purges the consumption and consumption detail records for inactive resource pools without considering the lead days. For more information, see Purge or delete the consumption data of inactive resource pools.

Solution: This issue is resolved. The option to round off to 2 decimals is added to the LINE_SUBTOTAL, TOTAL_TAX, and TOTAL_AMOUNT attributes of an invoice.

1. Create an item, ITEM_1 and 2 ship nodes, NODE_1 and NODE_2.
2. The NODE_1 and NODE_2 ship nodes contain the transfer schedule relationship from NODE_1 to NODE_2 with the transit time as 2 days.
3. Configure the Use Item Based Allocation and Optimize Supply selection to Maximize Availability item-based allocation rules.
4. For NODE_2, configure the receipt processing time for future supply as 1 day.
5. Adjust the on-hand supply at NODE_1 and create a sales order with 2 quantity for ITEM_1 and NODE_2, and schedule the order. A procurement transfer order is created.
6. Adjust the on-hand inventory with 1 quantity at NODE_2.
7. Call the findInventory API for ITEM_1 and NODE_2.
8. The findInventory API returns the ship date as current date+3 days, instead of using the existing on-hand supply and returning the ship date as current date.

Solution: A new yfs.donotConsiderRecptTimeForProc property is introduced with a default value that is set to false. If you change the default value to true, the findInventory API returns the ship date as current date.

Solution: This issue is resolved. In a return order, for the bundle items even when you split the component lines across multiple order lines the quantities are cumulatively calculated. Also, the bundle parent is updated with the correct quantity.

1. Set the property, yfs.useNodeLocaleTimeForCapacityCheck=true.
2. Set the installation locale in the Coordinated Universal Time (UTC) time zone and create a store with a locale in the JST time zone.
3. Create a resource pool at the store with the unit of measure as RELEASE, and set a sufficient capacity for the resource pool.
4. Implement the OMPGetExternalCostForOptionsUE user exit and set NodeProcessingDate="" in the user exit output template at the Assignment element.
5. Adjust inventory for an item at a node.
6. Create an order and schedule it when the time in UTC is past 15:00 hours such that the JST date is the next day.

Solution: This issue is resolved.

Solution: If you modify the value of the yfs.searchIndexCacheTimerTask.infoLog property, ensure that you restart the server to avoid performance issues during the search catalog index.

Solution: This issue is resolved. An option is provided to enable the Gift Flag Modification at the order line level until the status is Shipped.

Solution: This issue is resolved. The attributes from the YFS_REFERENCE_TABLE table can be included in the order outline with a special customization task. For more information, see Adding attributes to the outline template.

Solution: This issue is resolved. The getStoreAvailability API is enhanced by introducing a new attribute, IsProcurementAllowed to evaluate procurement through procurement sourcing rules. For more information, see the Javadoc.

Solution: This issue is resolved. The Transaction-Id header is not set until the Retry property is enabled.

Solution: This issue is resolved.

Solution: This issue is resolved.

Solution: This issue is resolved.

Solution: This issue is resolved.

Solution: This issue is resolved.

Solution: This issue is resolved.

Solution: This issue is resolved. When the output of the OMPGetExternalCostForOptionsUE user exit is processed during the releaseOrder transaction, the actual promise line is read instead of the summary line.

Solution: This issue is resolved. When the Asynchronous Request Processor agent is run with multiple threads, a record is processed one time until the condition that is defined in the ReprocessIntervalInMinutes attribute is satisfied.

Solution: This issue is resolved.

Solution: This issue is resolved.

Solution: This issue is resolved. Set the value of the yfs.searchIndexCacheTimerTask.infoLog property to true to include additional information logs in the Search Index Cache timer task.

Solution: This issue is resolved. The RTAM now does not process inventory item records that are purged by any other process.

Solution: The funds from a return order are considered in the calculations of the exchange order so that the appropriate event gets triggered.

Solution: The yfs.useScheduleBasedETAForSupply property is introduced. When you set the value of this property to true, the expected time of arrival for the PLANNED_TRANSFER supply record is calculated based on the transit time of the transfer and expected time of arrival at the receiving node.

Solution: This issue is resolved. The correct payment method is now applied to the invoiced amount.

Solution: This issue is resolved.

Solution: The getAlternateStoreAvailability API is enhanced and now considers the unplanned inventory for an item across multiple nodes in a single API call.

1. Go to Global Inventory Visibility > Inventory Rules .
2. Click the Monitor rules tab.
3. On the Distribution Group To Use For Node Level Monitoring drop-down list, click the Configure Monitor Rule Distribution Group icon. The Monitor Groups Distribution Groups window opens.
4. On the Distribution Group To Use For Node Level Monitoring panel, remove a subscribed distribution rule.

However, the subscribed distribution rule does not get removed.

Solution: This issue is resolved. You can successfully remove the subscribed distribution rule.

Solution: This issue is resolved. In a multistop scenario, when you set the property yfs.yfs.overrideTransferScheduleForProc=true and configure the carrier service pickup schedule on the origin node, the carrier service pickup schedule is considered for the estimated time of shipment (ETS) calculation at the origin node.

Solution: This issue is resolved. In the manageCouponPolicy API Javadoc, the references to the related documents are updated.

Solution: This issue is resolved. The option to trigger agents from the System Management Administration (SMA) application console is available. However, it is not recommended for users who are on version 2.0 as they must use Self Service to trigger agents.

1. Create two tag-controlled items, ITEM_A1 and ITEM_A2.
2. Adjust supply.
   • ITEM_A1 (GTIN: ITEM_A) | Supply: Lot 1(100), Lot 2 (100)
   • ITEM_A2 (GTIN: ITEM_A)
3. Call the reserveItemInventoryList API with ITEM_A2 and lot number Lot 1. The item quantity is reserved successfully.
   Note: As a result of performing step 3, the YFS_INVENTORY_ITEM record exists for ITEM_A2. But, the YFS_INVENTORY_TAG record for ITEM_A2 and Lot 2 does not exist because the supply or demand is not created for this combination so far.
4. Call the reserveItemInventoryList API with ITEM_A2 and lot number Lot 2. The item quantity is not reserved.

Solution: This issue is resolved. The reserveItemInventoryList API reserves the item quantity successfully.

1. For the shipping sourcing rule, create the DG_1 distribution group with STORE_1.
2. For the procurement sourcing rule, create the DG_2 distribution group with STORE_1.
3. Create a sourcing rule with DG_1 distribution group and select Onhand Inventory Selected.
4. Create a procurement sourcing rule with DG_2 distribution group enable the Use Shipping/Delivery Sourcing Rule Inventory Window flag.
5. Adjust the inventory at P_STORE_1 for an item, such as ITEM_1.
6. Call the findInventory API for ITEM_1.

Solution: This issue is resolved.

For more information, see Override transfer schedule between nodes.

Solution: In the findInventory API output, the ship date of the origin node is updated to derive from the cut-off time of the transfer schedule.

Solution: Calling the adjustInventory API with AdjustmentType as ABSOLUTE and existing Quantity and RemoveInventoryNodeControl as A or Y now inserts a record in the YFS_INVENTORY_ACTIVITY table.

Solution: Instead of a null pointer exception, a valid error with ErrorCode=INV921_001 and ErrorDescription=Invalid operation as supply and demand are kept externally is displayed.

• 593974
• 593863

• TS015346039
• TS014498696

Solution: This issue is resolved.

Solution: The SQL query that is used in the translateBarCode API is optimized, and the API does not call separate SQL query for all the inventory organizations.

Solution: The additional debug information is added to the searchCatalogIndex API logs when the category list is fetched.

Solution: This issue is resolved.

Solution: This issue is resolved.

Solution: This issue is resolved.

Solution: A limit is introduced to the failing query in getJobs. During the initial run of data extract with historical data, it helps to limit the number of records queried in the getJobs parameter in one query.

Solution: This issue is resolved.

Solution: If the HeaderAttribute element is present for authentication to support other authentication mechanism, the Token/@AuthenticationToken attribute is not mandated.

Solution: This issue is resolved.

Solution: The Show Listener Details page opens correctly.

Solution: The Next Task Queue Interval attribute now allows decimal values.

Solution: To avoid the Too many open statements error message, the SQL statement that is created by the application is closed after the SQL statement is successful.

• 593768
• 593769
• 593770
• 593771
• 593772
• 593789
• 593810
• 593811
• 593819
• 593829

Solution: The application is enhanced to support orders with large number of lines. For more information, see Handling orders with large number of order lines in the integration adapter.

Solution: The orders are not updated to the authorized payment status before the funds are collected for asynchronous payment processing when the yfs.payment.asyncChargeStopAuthTillFundsCollected property is enabled.

For more information about the yfs.payment.asyncChargeStopAuthTillFundsCollected property, see Sterling Order Management System yfs.properties file.

Solution: The ManageCapacityReservation API is enhanced to support the ConsiderOnlyActive flag in the API input. For more information, see Javadoc.

• 593822
• 593882

• TS014109268
• TS014495036

1. Adjust inventory for tag-controlled item ITEM_A1 (GTIN: ITEM_A) at NODE1 to 10 quantity for LotNumber L1.
2. Create a tagged demand for the item of 15 quantities for LotNumber L1.
3. Adjust inventory for tag-controlled item ITEM_A2 (GTIN: ITEM_A) at NODE1 to 10 quantity for LotNumber L1.
4. Start the findInventory API by using ITEM_A2 with LotNumber L1 for 10 quantity.

Solution: The yfs.aggregateSupplyOfNonRequestedTagForGTIN property is introduced. To avoid over-consumption, set the value of this property to N so that the application does not read the aggregated supply of the nonrequested tag for GTIN items.

Solution: The ModificationReasonCode attribute is stamped in the order audit for orders for which the shipment is created, even if the order is canceled.

1. Implement the OMPGetExternalCostForOptionsUE user exit.
2. Set ENABLE_SHADOW_SOLVER=Y.
3. Set yfs.yfs.solver.MaxChoiceFailures=1000.
4. Create an order and schedule the order.

Solution: The FindInventory API is enhanced to return the node, which can deliver the earliest when two nodes are eligible for procurement with same dates for delivery with different cut off time.

Solution: While modifying the work order, the canceled shipments that are associated with work order are ignored,

Solution: The printDocumentSet API is updated to handle multiple requests simultaneously and pass the correct data to the custom print adapter class.

Solution: Whenever the line schedule is updated by using the changeOrderSchedule API, the new line schedule copies the OverrideItemID, OverrideProductClass and OverrideUOM attributes from the previous line schedule.

Solution: The FindInventory API is enhanced to consider safety stock only once for each catalog organization when the inventory organization relation exists with multiple consuming inventory organizations that shares catalog from the same catalog organization.

Solution: When there is an error at any point in the custom service, the transaction will rollback and the data is not persisted for the particular record.