IBM Support

IBM Sterling Order Management 20.3 Release Notes

Release Notes


Abstract

Resolved issues for IBM Sterling Order Management in the Release 20.3 and the subsequent minor updates.

Content

20.3 Minor Update 4
IBM Sterling Order Management
Defect Case Number Description
589329 Internal
Issue: Certain automated probes were failing because the heartbeat.jsp was not accessible when the IBMid was enabled for IBM Sterling Call Center and IBM Sterling Store Management.

Resolution: Deployment configuration is updated to expose heartbeat.jsp same as the Console user interface, where it is accessible even when the IBMid is enabled.
591209 TS004417114
The search catalog index builds a cache from the latest active index during the server startup. The cache includes YCMOpenBitSet instances with bits equal to the total number of active catalog items. Such instances of YCMOpenBitSet are created for each active category and attribute allowed values in the catalog. For a huge catalog with large number of categories, the YCMOpenBitSet instances can start consuming more memory and might result into out of memory errors.

All instances of YCMOpenBitSet are added to ehcache for cache management. By default, ehcache is configured to keep 10000 cache elements (YCMOpenBitSet in this case) in memory. Ehcache can be configured to keep lesser number of elements in memory to free up memory for other processes. Ehcache keeps only the configured number of elements in memory and evicts the remaining elements to disk by using the configured eviction policy. However, when the evicted elements are required to be restored, ehcache fails to do so and hence cannot return the elements from disk.
Solution: Ehcache can now deserialize the evicted objects successfully for further use.
591494 TS004822004 In the output xml of importShipment API, the /Shipment/Containers/Container/ContainerDetails/ContainerDetail/ShipmentLine element is missing.
591606 Internal A null pointer exception is thrown while running the requestCollection API.
20.3 Minor Update 3
IBM Sterling Order Management
Defect Case Number Description
589911 TS003709176
IBM Sterling Order Management is enhanced to prevent authorization reversal when a payment method is suspended and the authorization reversal strategy is enabled.

Ideally, with authorization, reversal is enabled. If a payment method is suspended then existing non-usable authorizations are reversed.

To override the authorization reversal strategy, the yfs_payment. SUSPEND_EXP_AUTH_REVERSAL column is added, which can be updated with changeOrder or collection user exit. This flag overrides the  authorization reversal strategy for a suspended payment method.
If yfs_payment.SUSPEND_EXP_AUTH_REVERSAL is set to Y and the payment method is suspended, system does not create authorization reversal against the suspended payment method. This flag is triggered only when yfs_payment.suspend_any_more_charges is set to Y or B.  For more details, see API Javadoc.
To update the reason code for payment method and charge transaction executions, the following two columns are also added.
  • yfs_payment.reason_code
  • yfs_charge_transaction.reason_code
590589 TS003979820 In the IBM Sterling Call Center application, while applying promotions for the free gift coupon, promotion gets applied and the GWP item gets added even though the price is less than the qualifier amount that is defined in the coupon.
590731 TS003976751 The index is updated for yfs_audit to improve audit purge performance.
590909 TS004122696
If the Auth Reversal strategy is Reverse when Expired, while cancelling the order, the Auth expiration date is set to a very high date and the reversal of Auth does not happen.
Solution - Added the logic to not update the Auth expiration date to a high date when the Auth Reversal strategy is Reverse when Expired.
590927 TS004227647 The IBM Knowledge Center is updated for the Reverse Excess option. For more information, see Configuration options.
590950 TS004329831
In the changeOrder API, when the OrderLineRelationship element is present in the input xml, the PipelineId that is set for the OrderLine element is not considered during update.
591202 TS004477013
Node capacity locking does not work when server time zone is different than the time zone of the node.
Solution - The node capacity locking now works for node in different time zone when the yfs.useNodeLocaleTimeForCapacityCheck property is set to true.
The nodecapacity.maxLockRetry yfs property is added to configure the number of attempts to lock for availability check.
The IBM Knowledge Center is updated with more information for this property. For more information, see Node capacity locking.
591417 TS004659745
Shipment details are not displayed in the call center shipment tracking page when there is a shipment with shortpick and the shorted quantity is cancelled.
591486 TS003999721 The Order history purge tables list is updated in the IBM Knowledge Center.
20.3 Minor Update 2
IBM Sterling Order Management
Defect Case Number Description
590047 TS003914417
For Advanced Exchange order, if there is pending transfer in amount from a Return order, then the distributed amount is set up correctly. However, the distributed amount calculation is not designed to consider pending transfer in amount from a Return order, which causes some problems.

Solution - Fix is provided to correctly handle pending transfer in amount that comes from a Return order to Advanced Exchange order.
590634
TS004078481
The Launching Sterling Store Engagement from another application topic in IBM Sterling Store Engagement Knowledge Center is updated with the following note:
IBMid-enabled Sterling Store Engagement screens cannot be embedded within other web applications.
590833 TS003519802
The Regions and region schema topic in the IBM Sterling Order Management Knowledge Center is updated with the following information related to extending Sterling Order Management to include custom ZIP code and region data:
You can extend the optional SQL data that is provided by default with Sterling Order Management to include custom ZIP code and region data. For more information, see Adding custom optional SQL data.
590853 TS004280062 RTAM publishes an alert for SHP even when the node level availability monitor rule does not have the SHP delivery method configured.
590929 TS004326465 Refund charges for an imported order are not considered during its return order.
590969 TS004242310
When you configure the following, system creates a reversal for the complete authorization even when a partial authorization is used for charging:
  1. Enable Use same Authorization multiple times.
  2. Disable partial reversal supported.
  3. Set the authorization reversal strategy as Reverse Excess.
Solution: Perform the following steps:
  1. Create order for $100.
  2. Authorization with auth id A1 $100 is taken.
  3. Invoice for $50.
  4. Charge for $50 against A1 created consuming $50 authorization.
  5. Cancel $10 from the order.

Run requestCollection and authorization reversal for auth id A1 of $100 is created.

591009 TS004371531 Inventory purge agent purges the demand record even when the record has a valid reference in the yfs_inventory_demand_dtls table.
591152 TS004500145 A null pointer exception is displayed, when a user performs the following sequence of actions:
  1. Enables the dynamic distribution logic in the financial rules.
  2. Creates an order and moves it to the Shipped status.
  3. Creates a return order with ProcessPaymentOnReturnOrder=N.
  4. Purges the Sales Order and the Return Order.
  5. Restores the Sales Order.
  6. Calls the getOrderList API for the Sales Order with the output template that has @ChargeTransactionDetail element.
591153 Internal Inconsistent demand updates are observed when the  SyncInventoryDemand API is called to update same Item-Node-Date-DemandType but with a different OrganizationCode.
591214 Internal
Inventory Purge agent is enhanced to merge and eventually purge demand and supply records when multiple records for a unique combination exist. The records are merged only if they qualify under the purge criteria.
You must set yfs.purge.MergeDemandSupplyMultiRec=true in the database properties to enable this feature.
591245 TS004562740
In Sterling Business Center (SBC), the width in the drop-down list does not expand dynamically with the longest organization name.

Note: Using very long organization names might lead to unexpected behavior.
591256 TS004581113 Inventory Purge removes the reservation based on reservation ship date instead of the reservation expiry day.
20.3 Minor Update 1

IBM Sterling Order Management
Defect Case Number Description
584961 TS002405119 The getOrderList API returns a greater number of records in the output than the page size when ReadFromHistory="B" in the input XML.
Solution: The getOrderList API is modified to fetch first orders from the main table. If the total number of qualified orders from the main table is less than the page size, it fetches orders from the history table. The total number of orders (main + history) in the page will never increase the page size.
589072 TS003620899 Segment details are not stamped during the Inventory Visibility API calls to get node availability.
589592 TS003743767 Inventory Purge agent is enhanced to merge and then purge demand and supply records when multiple records for a unique combination exists. The records are merged only if they qualify under purge criteria.
To enable this feature, set yfs.purge.MergeDemandSupplyMultiRec=true in DB properties.
589609 TS003812743
The input template for OverrideGetOrderPriceUE has missing attributes and elements when compared to the input Javadoc for the user exit. Hence, ship pricing rules and coupons are not applied due to missing information indicating whether the rules or promotions are valid.
Solution: The user exit template is updated to reconcile these two files.
589611 TS003801821
When database queries are added to SQL batch in the order move status, the queries run in a wrong sequence.
589636 TS003769833 Calculate Capacity Availability agent is enhanced to calculate and update the capacity in YFS_CAPACITY_AVAILABILITY table as per the time zone of the node.
589693 TS003651858
When an order line pricing is information only, the line price is set to zero during invoicing. If there are line charges or taxes on the line, and the line total is allowed to change after invoicing, the line total becomes the sum of the charges, and taxes are set to zero.
Solution: Line total will not change after invoicing line if it is set to IsLinePriceForInformationOnly.
589699 TS003620899 Segment details are not stamped during the creation of temporary reservations during scheduleOrder and releaseOrder.
589889 TS003683159 The Applying a sourcing template to a sourcing rule topic in IBM Sterling Order Management Knowledge Center is updated to add more details about the sourcing rule configuration. The document now states that the <number of days> in “Consider Only Those Nodes That Have A Minimum Available Capacity of <capacity>% Within The Next <number of days> Day(s)" option is calculated based on the date in the install time zone.
589968 Internal The Available on date for bundle items is shown incorrectly in IBM Sterling Call Center.
589978 TS003961032 In a setup, when Inventory and catalog organization are not the same, the GetItemListForOrdering API does not return availability if the DistributionRuleId attribute is passed in input.
589993 TS003946526 In some scenarios, such as, when hot SKU is enabled, multiple identical demand/supplies records with same item ID, unit of measure, ship node, and so on, could exist with different quantities. The snapshot sync agent sends each quantity separately, and hence, the last quantity overwrites previous quantities.
Solution: Enable the yfs.inventorySnapshot.DemandSupplyMultiRec property such that the snapshot sync agent sends the total quantities.
590025 Internal The getCompleteOrderLineDetails API returns incorrect shipnode at LineTracking > LineBreakups > Details level when order is shipped from multiple nodes. The same shipnode is stamped for all lines despite being shipped from different ship nodes.
590039 TS003927921
When Inventory Visibility integration phase 2 is enabled and the user performs the following steps:
1. Creates a custom demand type in Sterling Order Management and Inventory Visibility with the name "RSRV_OPEN_ORDER.ex", such that this demand type is an uncommitted demand type like OPEN_ORDER.
2. Calls reserveAvailableInventory API for a qty=1 for an item. This creates a reservation for qty=1 for the item at a specific node in Inventory Visibility.
3. Consumes the above reservation in createOrder API such that ship node in the reservation is stamped in the ShipNode XML attribute in the OrderLine element of API input. Also, the DemandType XML attribute is stamped with value "RSRV_OPEN_ORDER.ex" in OrderLineReservation element of the API input.
It is noticed that the createOrder API generates demands as OPEN_ORDER=+1 and RSRV_OPEN_ORDER.ex=+1 at the specific ship node, which results in Inventory Visibility showing 1 lesser available quantity.
This issue related to the availability quantity is corrected when the scheduleOrder API is called.
Solution: The createOrder API is enhanced to generate demands OPEN_ORDER=+1, RSRV_OPEN_ORDER.ex=+1, and OPEN_ORDER=-1 at the specific ship node.
590040 TS003989713
After restoring an order, the YFS_TASK_Q table entry is not generated and hence, the restored order is not available to be purged again.
590078 TS003904434 Validation condition for changeOrderInvoice API input XML is changed in the Javadoc to "Only invoice number, status or extended attributes can be changed."
590092 TS003914300 The following error occurs in IBM Sterling Call Center when creating a return for a blind order: "There are errors on page, cannot proceed until you fix them."
590111 TS004015214
If OrderLineKey is not present in the OrderLine element for sales order template, Sterling Order Management removes the OrderLineKey attribute from the OrderLine element of the return order.
Solution: For the sales order template, only the OrderLine elements of the sales order are processed, the return order elements are not affected.
590121 TS004046967
In the Add products page of IBM Sterling Call Center, when a user saves the item, navigates back to the customer selection page, comes back to the Add products page, and clicks 'Show preview', the preview panel shows 'Out of stock' even though the item is available. This issue occurs because the mashup "AddItemsLines_getCompleteOrderLineList" does not return the item availability information in the mashup output.
Solution: Mashup definition is updated to return the availability information for the item in the mashup output.
590140 TS004029443 In the Add Products page of Sterling Call Center, inconsistency is seen in the 'Available on' dates between English and Spanish locale users.
590180 TS003995766 In the Backroom pick portlet in Sterling Store Engagement, incorrect total shipment count is displayed for Spanish locale user and 'NaN' is displayed as the total count for English locale user when shipment count is more than 1000.
590189 Internal
The Sterling Order Management application is enhanced such that it now logs SQL statements. The SQL statements are added and run with the SQL batch execution.
590200, 590582 TS004055567, TS004188341 When unconsumed inventory reservation is present for the item-node combination, NullPointerException is observed in the execution of IBA agent.
590208 Internal A new audit package, SMCF-Audit, is provided for insights into report execution and execution count. You can generate weekly reports by using the sample Past Week Reports that is provided as part of this package. For more information, see Planning and monitoring operational reports usage.
590561 Internal
Authorization expiration date is set to high date causing the payment processing to be disabled when the hold is removed from the order.
Solution: Authorization expiration date is now set to current date from high date if the order hold is resolved and the payment processing is enabled for the order.
590592, 590699 TS004221709
A potential performance issue is observed while fetching child containers in the changeShipment API call. And, the parent container keys in most of the shipment container records in the database are set to blank.
Solution : Set yfs.applyChildContainerQueryOptimization=Y in DB properties to optimize the query on the shipment container table while fetching child containers.
590823 Internal The InventorySnapshot agent topic in IBM Order Management Knowledge Center is updated to include the information that you must run the Inventory Purge agent before running the InventorySnapshot agent. A new section is also added to explain how to delete additional negative demand records before running InventorySnapshot agent.
 
20.3

IBM Sterling Order Management
Defect Case Number Description
588976 Internal
A new rule, ENABLE_SHADOW_SOLVER is introduced with the default value set to N. If this rule is enabled for an enterprise, and if the OMPGetExternalCostForOptions UE template is extended to include the SuggestedOption element, the UE input XML includes the SuggestedOption element.
Note: In the OMPGetExternalCostForOptions UE output, if the value of the Overridden flag is set to Y, an additional call is made to the solver. The solver then recalculates the best node from the possible choices in the UE output. For more information about the OMPGetExternalCostForOptions UE, see Javadocs.
589061 TS003541475 The Configuring Sterling Order Management for integrating with the Sterling Inventory Visibility topic is updated to include an extra step for rebuilding the customization package. Also, the properties of customer.overrides.properties are updated. For more information about the updated properties, see Defining integration properties in Sterling Order Management.
589660 TS003825400 When a change order is run for an invoiced order, extra charge entries are created in the YFS_CHANGE_TRANSACTION table while adjusting distributed credits for negative invoices because charge entries are also considered along with invoice entries while calculating the distribution limit.
589756 TS003873872
The reserveAvailableInventory consists of two steps:
  1. Check availability in Inventory Visibility.
  2. Try to make a reservation.
For non-bundle items, the output for reserveAvailableInventory assumes that the requested or available quantity, whichever is less, is reserved.
589886 TS003927921 For new implementations that are using Sterling Inventory Visibility phase 2 integration, while consuming reservations, a new uncommitted demand type must be passed in the OrderLineReservation element of the createOrder and changeOrder APIs. For more information about the uncommitted demand type, see Handling inventory reservation.
589891 TS003887380 The ON_HAND_QTY column is updated with an incorrect value in the YFS_INVENTORY_AUDIT table when the syncLoadedInventory API is called.
589905 TS003929548
When Sterling Inventory Visibility is enabled, a NullPointerException occurs when scheduling bundle items that are configured as Ships Independently.
589969 Internal The Javadocs are updated for the output XML of the getCompleteOrderLineList API with descriptions for all attributes of the Availability element.
590019 TS003942880 The following information related to the 'Is Hazardous Item' flag is added to the Defining a product item's classifications topic in IBM Order Management Knowledge Center:
  • You can configure sourcing rules that are specific to Hazmat classes by using Item classifications.
  • You can define whether a specific carrier service can ship hazardous materials by setting the CAN_SHIP_HAZMAT value to Y.

If any of the items in a container are marked as hazardous, the container is considered to be Hazmat. 

590021 TS003487464
When RTAM is run in OP2, quick sync, with FromLastNumberOfHours set, only the first alert for each item is picked up.
590071 TS004017170 If the overall override records for eligible nodes contain more than 1000 records, resource pool capacity override is not considered for some nodes.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS6PEW","label":"Sterling Order Management"},"ARM Category":[{"code":"a8m50000000CbuEAAS","label":"Sterling Order Management System"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
16 February 2021

UID

ibm16257031