Release Notes
Abstract
Resolved issues for IBM Sterling Order Management in the Release 21.1 and the subsequent minor updates.
Content
21.1 Minor update 2
Defect | Case Number | Description |
589438 | TS003596491 |
Problem: When chargePerUnits are used to apply discounts, discount is applied on full sales order quantities even when some quantity is returned and invoiced.
Solution: Discounts are applied only on non-returned quantities. This fix has been made property based to retain the original behavior. Property name=yfs.invoice.lineChargePerUnitConsideration Values - Default value = 0 0=Full sales order line quantities are considered. Original and default behavior. 1=Non-returned sales order line quantities are considered to apply the discount. In customer_overrides.properties, add the following entry. yfs.yfs.invoice.lineChargePerUnitConsideration=1 |
591479 | TS004797309 |
When IBM Sterling Inventory Visibility integration phase 2 is enabled, capacity is not consumed correctly if reservations are created by using the reserveAvailableInventory API.
|
591531 | TS004871195 | The cancelReservation API must be allowed with IBM Sterling Inventory Visibility integration phase 2 enabled such that it can cancel reservations that are created in Inventory Visibility along with adjusting capacity in Sterling Order Management. |
591786 | TS005042885 | Inconsistency in the behavior where product browsing is not working as expected if you browse for an item by using the shortcut in the home page. However, if you navigate by using the product browsing option under related tasks list, the search works correctly. |
591859 | Internal | With IBM Sterling Inventory Visibility integration phase 2, the list of deprecated OMS API for new customer implementation must also be applicable for environments migrating from Global Inventory Visibility to Sterling Inventory Visibility integration phase 2. |
591878 | TS005372131 | In IBM Sterling Call Center, for a scheduled order that has multiple order lines or reshipped order with scheduled status, in the Change Fulfilment Summary page, when you select checkboxes for multiple order lines and click Change level of service, an Unhandled Exception for Change Level Of Service Modification error message is displayed. |
591927 | TS004797309 | Documentation is updated as the cancelReservation API is enabled for Sterling Inventory Visibility integration - Phase 2. For more information, see Deprecated Sterling Order Management APIs and events. |
21.1 Minor update 1
Defect | Case Number | Description |
591312 | Internal | When an alert is created while running the Enhanced Order Monitor agent, the MonitorRuleKey is added to the InboxReferencesList element for alerts. |
591324 | Internal |
The getAlertStatisticsForUser API is enhanced to support CountAlertsGeneratedAfterInHours and CountAlertsGeneratedBeforeInHours attributes in the API input to count recent and stale alerts in a queue, and to support MonitorRuleList in the API output to count alerts that are generated by monitor rules.
For more details, see getAlertStatisticsForUser API Javadoc.
|
591415 | TS003914417 |
Problem: Multiple charges are created for exchange order during creation of Adjustment and then invoicing the Return order because the adjustment amount is added or subtracted from the exchange order total during the Return Order invoicing.
Solution: The application checks whether the exchange order contains undistributed adjustments during the Return order invoicing. If undistributed adjustments are available, the adjustment amount is again added or subtracted from the exchange order total.
|
591549 | TS004846568 | In an Inventory Visibility-integrated environment, application incorrectly adds 'Receipt Processing Time for Future Inventory (Days)' to the ONHAND supply, resulting in an incorrect availability picture. |
591639 | TS004809243 |
Problem: When publish invoice is set to At Creation, the handleRefunds API is called even if it has zero amount to refund and it in turn calls UE OMPConfirmRefundDistributionUE with incomplete data.
Solution: The handleRefunds API is not called if the invoice has zero amount to refund. |
591771 | TS005067598 |
Problem: When the cash and carry option is not selected, the "Invalid delivery method" error occurs while scanning the product in quick checkout portlet.
Solution: When the cash and carry option is not selected, while scanning the product in quick checkout portlet, the store associate is navigated to the Product details page with the Available in store option being disabled.
|
591776 | TS005078561 | The entries in the YFS_FREIGHT_TERMS table are ignored from insertion during the upgrade mode installation. |
591797 | Internal |
The getShipNodeList API is enhanced to support EnterpriseOrgList in the API input. For more details, see getShipNodeList API Javadoc.
|
591825 | Internal | Multiple alerts are generated per order and monitor consolidation pair. |
591826 | TS005250888 | In Sterling Business Center, the Ship order total pricing coupon is not getting created. |
591832 | TS005263445 |
The output of getOrderList and getOrderDetails APIs for Tax element attributes Reference1, Reference2 and Reference3 is updated for backward compatibility to have underscore Reference_1, Reference_2 and Reference_3.
Set the below property in customer overrides to change the tax reference attributes in api output.
yfs.yfs.order.bcTaxReferences=Y |
591860 | TS005042933 | Override price pop up hangs intermittently. |
591861 | TS005318774 | The yfs.applyChildContainerQueryOptimization property is not available under the System Administration Tool (SMA) after upgrading to the 21.1 release because of the additional ## PROPERTY_END. |
591870 | Internal | A NullPointerException occurs in the manageItem API when Store Inventory Management (SIM) is enabled and an item is added in the Published status with blank InventorParameters. |
591873 | Internal | In the getItemAvailabilityStore API, the WSC_STORE_GET_CACHED_INV rule is used to determine whether item availability must be checked in cached inventory by invoking the getAvailabilityCache API. With this update, when Inventory Visibility is enabled, item availability is always checked with Inventory Visibility and the WSC_STORE_GET_CACHED_INV rule must be ignored. |
591879 | TS005340297 | In the getTrackingNoAndPrintLabel API call, the open manifest date is set in the store's timestamp such that when a store user calls the closeManifest, it is compared with the store's timestamp. |
Defect | Case Number | Description |
506319 | Internal |
The getTransactionSummary API needs an ability to do rolling count for a year when the StartDate is specified.
Solution: The StartDate and RollingCount attributes are added in the getTransactionSummary API input. If RollingCount is Y and StartDate is passed, then the API computes orders that are created from the month and year of the StartDate for one year. |
518745 | Internal |
Performance improvement in the payment collection agent.
The AuthorizationExpirationDateWindowInDays agent criteria is added for the PAYMENT_COLLECTION agent. Setting this criteria to a positive non-zero number would add an additional where clause for the Payment_Collection agent to pick orders having AUTHORIZATION EXPIRATION DATE between the current date and current date - AuthorizationExpirationDateWindowInDays.
Example: AuthorizationExpirationDateWindowInDays=10, if the current date is 9/12/2016. The agent would only process orders having AUTHORIZATION_EXPIRATION_DATE between the current date such as 9/12 and currentDate - 10 such as 9/2/2016.
For documentation updates, see Payment collection.
|
545701 | Internal |
Problem: Attributes are missing in the input of the OMPGetSourcedFromNodesExternallyUE user exit for the Procurement scenario.
Solution: The application is enhanced to display Original Line Ordered Quantity for the chained lines in the input of the OMPGetSourcedFromNodesExternallyUE user exit. The user exit template must be extended to include OriginalLineQuantity under the <PromiseLine/> element. |
547574 | 43803,082,000 |
Problem: YFSGetItemNodeCostForSourcingUE is called when RTAM is run with yfs.rtam.algorithm as 00 or 01.
Solution: YFSGetItemNodeCostForSourcingUE is not called. |
550226 | Internal |
The product is enhanced to support the associations that are not defined in Catalog Management.
To enable this feature, you must set the yfs.yfs.order.maintainProductServiceAssociationExternally=Y property in customer overrides.
|
556449 |
This enhancement allows you to purge order data in your own external system as opposed to the history tables. If the PurgeOrderToExternalDataStoreUE user exit is enabled, then XML representation of order details is passed to the user exit so that it can be stored externally. If you do not implement the UE, then order details are purged to the history tables by default.
For documentation updates, refer the following links: |
|
558586 | Internal | Repricing is considered when the confirmDraftOrder API is called on external orders that removes externally added promotions. |
555940 | 00249,227,000/40169,211,788 |
Incorrect RTAM availability alerts are observed when the following sequence of actions are performed.
|
567432 | Internal | The changeOrderSchedule API has been enhanced to support SelectMethod in the API input. For more details on this attribute refer to API Java documentation. |
570782 | Internal |
Enhancement for tag attribute remove feature on an order line when an item is "sometimes tag-controlled".
Solution: The Action attribute is added under the OrderLineInvAttRequest element for the changeOrder API. For more information, refer Javadoc.
|
573367 | Internal | The getResourcePoolCapacity API is enhanced to support the passing of callingOrganizationCode in the input. |
576649 | Internal |
The getOrderList API is enhanced to return a list of orders based on TotalAmount and Currency as input criteria.
For more details, see the getOrderList API Javadoc. |
579526 | Internal |
Problem: Product is not honoring the ON HAND only sourcing rule detail configuration.
Solution: Product has been enhanced to consider future inventory window attribute from sourcing rule details. Based on the number of days that are set in the Future Inventory window, the available supplies are now filtered. |
580153 | Internal | When the consolidateAdditionalInventory agent is run for the yfs_inventory_demand_addnl records that are created because of a hot SKU, orphaned records are observed in the YFS_INVENTORY_DEMAND_DTLS table. |
580763 | Internal | Inventory Purge is deleting Demand and Supply without considering the retention days. |
583812 | Internal |
The YFSConfirmAssignmentsUE is enhanced to populate the procurement information in the UE input provided the Procurements element is part of the UE input template.
For more information about the YFSConfirmAssignmentsUE input template, see Javadoc.
|
586400 | Internal | Multiple entries for the RESERVED status is observed in YFS_ORDER_RELEASE_STATUS when a user retries scheduling an order and there is no change in the expected date. |
587622 | Internal |
If confirmRefundDistributionUE is not implemented, and the payment method is set to Suspended for Charge and Refund, the application initiates a refund.
Solution: Call the changeOrder API to set the value of SuspendAnyMoreCharges to A. All refunds that are processed for the new or existing payment methods are suppressed. |
587636 | Internal |
Configuration: NA
Condition: NA Operation: Invoking recordExternalCharges to cancel an asynchronous refund CHARGE.
Solution: The recordExternalCharge API is enhanced to cancel a pending asynchronously closed refund CHARGE. The input flag CancelPendingAsynchronous should only be used to record the fact that response for an asynchronous request will not be received. This API expects the RequestAmount to be passed as less than 0 to cancel a positive authorization or positive settlement requests. When trying to cancel an asynchronously closed negative transaction, a reverse AUTHORIZATION or refund CHARGE pass the RequestAmount as positive.
Refer to the Javadoc for more details.
|
588350 | TS002964115 |
The YFSGetDeliveryLeadTimeUE user exit is enhanced to override the consideration of node transfer schedule between two addresses. To enable this feature, set the yfs.yfs.overrideTransferScheduleForProc=Y property in customer_overrides.properties file. To override the transfer schedule for a pair of address, pass the OverrideTransferSchedule="Y" attribute when the UE is called.
Additionally, if the feature is enabled, the UE is called for each combination of address in the procurement determination so that the transfer schedule can be overridden. This feature is not supported for multi-hop transfers.
|
590090 | Internal |
When Transfer Schedule is Overridden from YFSDeliveryLeadTimeUE, the node cut off time is still considered from a node transfer schedule between ProcureFromNode and ShipNode in ETS calculation.
|
590110 | TS003868409 |
IBM Sterling Order Management is enhanced to enable the ORDER_CHANGE ON_ADJUSTMENT_INVOICE_CREATION event.
|
590120 | Internal | The Customer Account Payment type is enhanced to reverse the unused authorization when a customer account is suspended. You must configure the ReverseUnusedAuthWhenSuspended flag for the payment type. When the requestCollection and executeCollection APIs are run, the open authorized amount that is not collected gets reversed. |
590843 | Internal | The application is enhanced such that the orderModified UBX event is not published for certain modification types when applied to an order or order line. Users can configure the yfs.ubx.integration.order.changed.event.ignoremodtypes property and specify the modification types for which the event must not be published. The property considers a list of modification types separated by comma. |
590985 | TS004362213 |
When an enterprise user or a store user logs out from a store and logs in to a different store, "StoreId" that is passed as part of LoginURL of the Sterling Store Engagement UI is not retained in the URL after logout. As a result, the “Click here to login again” link, which is displayed upon logging out from Sterling Store Engagement, does not work as expected.
|
591109 | Internal |
In the refund configuration, when yfs_payment.suspend_any_more_charges is set to B for an order and the payment type is configured to refund to the same payment method, then the payment method gets suspended for refunds.
If the payment type is configured to refund to a new payment method, the system configures a new payment method for generating refunds.
Solution: The yfs.payment.supressAllRefundsIfPaymentSuspended property is added. To suppress all the refunds when yfs_payment.suspend_any_more_charges is set to B, ensure that the value of this property is set to Y in customer overrides. By default, the value is set to N.
The valid values for yfs_payment.suspend_any_more_charges are N, Y, B, and A. However, the value A that suppresses all refund processing for both new or existing payment methods is deprecated. Therefore, to suppress all refunds, set yfs_payment.suspend_any_more_charges to B and set the value of yfs.yfs.payment.supressAllRefundsIfPaymentSuspended to Y in customer overrides. |
591315 | TS004652652 |
The bundle keys for Days, Minutes, and Hours that are displayed in the Sterling Store Engagement UI are duplicated and the correct literal is not displayed.
Solution: The bundle keys are changed to be unique and correct literals are displayed now. If you have customized the literals for these keys, you must also customize the new keys.
|
591607 | TS004390799 |
The SkipPositiveIfAuthReversalExists criteria is added to the Payment Execution agent that allows delay of a payment collection for the payment methods that have pending refunds.
By default, the value of the SkipPositiveIfAuthReversalExists criteria is set to "N". If you set the value to "Y", and if the following conditions are met, a pending positive charge is ignored by getJobs().
ChargeType="AUTHORIZATION" RequestAmount > "0.00" Status="OPEN" And a negative charge for the same payment method on the same order. ChargeType="AUTHORIZATION" RequestAmount < "0.00" Status="OPEN" UserExitStatus != "INVOKED" After processing all charges with RequestAmount < "0.00", the corresponding positive charges are processed as normal. |
591667
591709 |
Internal |
Fusion charts now support Javascript instead of Flash. Therefore, in the Sterling Business Center and IBM Sterling Order Management user interfaces, fusion charts are upgraded to Javascript.
The documentation is also updated accordingly. For more information, see Creating chart dashlets. |
591669 | Internal |
In an Inventory Visibility-integrated environment, the getPossibleSchedules API checks the availability of products against Inventory Visibility for all order lines in the order. Currently, Inventory Visibility does not support the CARRY delivery method. Hence, item availability checks with Inventory Visibility for CARRY delivery method fail and store associate is not able to place an order in store. This happens when order contains only CARRY lines.
Solution: The isf.ycd.suppressCarryAvailabilityCheckToIV property is added to suppress calls to Inventory Visibility for the CARRY delivery method. If a store order contains only CARRY order lines and the yfs.isf.ycd.suppressCarryAvailabilityCheckToIV property is set to Y, CARRY line availability checks are not made to Inventory Visibility. This property is set to Y by default.
|
591694 | TS005001814 | In procurement sourcing rules with template distribution group, node filtering, which is based on the Idle Asset or Minimum Available Capacity flags, is not working. |
[{"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"}}]
Was this topic helpful?
Document Information
Modified date:
12 May 2021
UID
ibm16416177