Release Notes
Abstract
Resolved issues for IBM Sterling Order Management, IBM Sterling Store Engagement (Legacy), and IBM Sterling Call Center in the Release 21.3 and the subsequent minor updates.
Content
Defect | Case Number | Description |
IBM Sterling Order Management | ||
591822 | TS005147569 | Correct rounding logic is applied while calculating ChargePerUnit and ChargePerLine from ChargeAmount in the YFS_LINE_CHARGES table. |
591939 | Internal |
The getResourcePoolCapacity API is enhanced to read capacity availability from Capacity Cache.
Note: For more information about the getResourcePoolCapacity API, see Javadoc. |
591947 | Internal | When you complete the following steps, incorrect demand details are displayed:
|
592069 | TS005112285 | When you complete the following steps, incorrect transit time calculation is observed during procurement from STORE_1 to STORE_2:
Note: Transit days from UE are not considered in optimization and that leads to incorrect ETS. |
592138, 591183 | Internal, TS004437538 | The total number of hours in a day are incorrectly calculated when the Daylight Saving Time (DST) ends. Due to this, the findInventory API does not determine availability and displays the, Not Enough Product Choices error message, when you complete the following steps:
Solution: The yfs.adjustTimeStampForDstSwitch property is added. You can set the value of this property to Y in customer_overrides.properties to calculate the total hours in a day in accordance with the DST switch. |
592255, 592456,
592470, 592482
|
TS005298036,
Internal, Internal,
Internal
|
If unassigned demand is considered by using Distribution Group Priority Levels, alert quantities are not updated correctly by RTAM in activity-based mode.
|
592297 | Internal |
A new DeliveryMethod field is added in the input template of the INVGetSupplyCorrectionsUE, YFSGetAvailabilityCorrectionsUE, and YFSGetAvailabilityCorrectionsForItemListUE user exits.
|
592316, 592600 | TS006333190, Internal | The smart sourcing logic of IBM Sterling Inventory Visibility (phase 2) is disabled. |
592407 | TS005112285 |
When a transfer schedule is overridden by the YFSDeliveryLeadTimeUE user exit, an incorrect transit time calculation is intermittently observed for multi-stop transfers.
|
592429 | TS006333190 |
With Inventory Visibility Integration (phase 2) and later, the ReserveAvailableInventory API is enhanced to combine reservation calls to Inventory Visibility, whenever applicable. Therefore, you must set the yfs.UseAggregatedReservationsForIV property to Y.
|
592449, 592347 | TS007548721, TS005954938 | An order is backordered, when you complete the following steps:
|
592512 | TS005833140 |
When configurations are inherited from a parent organization, the config organization code where the default distribution rule is defined is used to check the item availability.
|
592519 | Internal |
When "Hot SKU optimistic lock avoidance" is enabled in the INV_Inventory_item_lock table, the records are locked for tag-controlled items that leads to excessive locking.
|
592541 | Internal | The log trace level of "Printer not found" message is changed from warning to debug. |
592543 | TS007061103 |
The unique identifier is duplicated, and not unique.
Solution: The identifier is renamed to make it unique. |
592572 | TS006479388 |
While picking an order that is shipped with a substitute item, and if shortage is recorded for all the order lines, the error message, "Invalid Itemid" is displayed.
|
592574 | TS006853035 | The order history purge is fixed to delete eligible records from the YFS_ORDER_LINE_RELATIONSHIP_H table. |
592590, 592656 | TS007151688, TS006644094 |
When an order is created with items that are used in customer entitlement, the catalog organization is passed correctly.
|
592599 | TS007698390 |
The getOrderAuditList API is enhanced to fetch records from audit history tables when ReadFromHistory is set to Y or B.
|
592648 | Internal |
When Specify Price Types is enabled in the pricing rules for the fixed price discount rule, NullPointerException occurs.
|
IBM Sterling Store Engagement (Legacy) | ||
592468 | TS006932516 | A new field, "Previously returned" is added to the Add Products to Return page, which displays the quantity of returned products for an order. |
592529 | Internal | If you extend the getStoreBatchList API mashup XML output template to include multiple attributes other than ShipmentLineKey on ShipmentLine tag, the "API security" error message is displayed on calling the createStoreBatch API. |
592539 | TS007288713 | Both BackroomPickedQuantity and BackroomPickedQty attributes are controlled by the yfs.install.displaydoublequantity flag. |
592543 | TS007061103 |
The unique identifier is duplicated, and not unique.
Solution: The identifier is renamed to make it unique. |
592544 | TS007271648 | When the login ID and display user ID are different, the “Invalid User Identifiers passed” error message is displayed in the Shipment Summary page. |
592617 | TS007616351 | The return number in desktop mode is displayed correctly. In mobile mode, the return number is displayed as a sub-heading under Return Summary. |
IBM Sterling Call Center | ||
592466 | TS006757100 |
If a followup date is extended by one day, the alert count for 'Alerts For Followup Today' displays incorrectly as it considers next day.
Solution: A new attribute, TodayDate="" is added to the getMyAlertsAndQueues mashup ID. If you extend this mashup, ensure that you take the latest code and merge all the attributes. |
592512 | TS005833140 | When configurations are inherited from a parent organization, the organization code where the default distribution rule is defined is used to check for item availability. |
592555 | TS007143066 |
If you do not define the "sequence" attribute in your customization, the "sequence" custom property is overridden with a blank value ("").
Solution: The application is enhanced such that the "sequence" custom property is overridden with the default sequence value. |
592557 | TS007067814 | In the "Edit Product on Return" page, when you click the Next button, an error message is displayed. |
592562 | TS006627378 | Loading an extended page for Return order page results in an error message. |
592567 | TS005842633 |
Earlier, the "sma" application code was added as part of context param for all the applications in web.xml.
Solution: The "sma" application code is now added as part of context param only for SMA. Therefore, duplicate application codes are not shown in web.xml. |
592592 | TS007393475 |
The "versioninfo.properties_isc_ext" and "versioninfo.properties_wsc_ext" does not contain a build number.
Solution: Absence of the build number in these files resulted in failing null check, and the version information was read from the SI_VERSION table as a fallback. The builds are fixed to update the build number in the "versioninfo.properties" file. |
Defect | Case Number | Description |
IBM Sterling Order Management | ||
590194 | TS004070196 | Incorrect capacity consumption is observed when the user performs the following steps:
The inventory reservation is removed but capacity consumption is incorrectly consumed.
|
590291 | Internal | The getOrderReleaseList API is enhanced to support <OrderBy>. |
590560 | Internal | The getShipmentList API is updated to return the correct TotalNumberOfRecords while searching ShipmentLine by OrderNo. |
590964 | Internal | The changeException API is updated to set the correct value of CREATETS for new records that are created in YFS_REPROCESS_ERROR. To retain the earlier functionality, set the yfs.reprocess.saveNewError.useOriginalCreatets property to true. |
591858 | TS005224375 | Unwanted authorization reversal takes place in case of multiple shipments scenario. Solution: In the multiple shipments scenario, validation is added to check if the reversal is required and if not required, the reversal is stopped. |
592223 | Internal | When IBM Sterling Inventory Visibility Phase 2 integration is enabled, by default, Sterling Inventory Visibility applies the safety stock calculations based on the configuration in Sterling Inventory Visibility and the IBM Sterling Order Management safety factor related configurations are ignored. |
592334 | Internal | The getReceiptDetails API is enhanced to return AllowedModifications. |
592340 | TS006462575 | The getCompleteOrderDetails API is fixed to retrieve shipments even from the history table. |
592344 | TS006228432 |
An order is backordered even if sufficient inventory is available when a user performs the following steps.
|
592394 | TS006349564 |
Order lines with the carry delivery method type are considered as in person payment processing. During the return processing of carry lines, the return order invoice that is created for carry lines is marked as in person. Payment processing of a return order invoice that is marked as in person creates multiple charges.
Solution: The value is not set to in_person=Y for return invoices.
|
592461 | TS006605573 | A Null Pointer Exception is observed when the RTAM Activity-Based Monitor processes an activity for which inventory item key is purged or removed. |
IBM Sterling Store Engagement (Legacy) | ||
592406 | TS006590990 | Line Level Partial status is not translated in the Global Search Summary screen. |
IBM Sterling Call Center | ||
592381 | TS006469112 | Incorrect search results are returned based on different time zones. |
592442 | TS006813021 | If DeliveryMethod on the orderline is 'SHP', shipment status is partially shipped, and some items are backordered and picked from a different store, "Where is my shipment?" displays incorrect LineTracking information. |
Defect | Case Number | Description |
IBM Sterling Order Management | ||
589915 | Internal |
The getOrderDetails and getCompleteOrderDetails APIs contain incorrect Javadoc encoding, and therefore, generates corrupted API Javadoc that are not fully functional.
Solution: Fixed the API Javadoc encoding for the getOrderDetails and getCompleteOrderDetails APIs so that the API Javadoc are correctly generated and fully functional.
|
590426 | Internal |
When you turn on sorting for the getStoreBatchList API, the shipment is split between batches.
Solution: The DoNotSplitShipment attribute is introduced. Ensure to set the value of this attribute to Y. Then, the getStoreBatchList API does not split the shipment into different batches. Additionally, it retains all the shipment lines of a shipment in the same batch even if the batching and sorting attributes of the lines are different. |
590051 | TS003996372 | After you migrate to Sterling Order Management, the pickup statuses are not displayed for "YCD_BACKROOM_PICK_IN_PROGRESS" and "YCD_BACKROOM_PICK" transactions. |
591064 | TS004415903 |
When an order is shipped from multiple nodes, the getCompleteOrderLineDetails API returns an incorrect ship node in LineTracking > LineBreakups > Details element.
|
591103 | TS002980242 |
When an order line has multiple shipments, the application renders line breakups with incorrect quantities in the Order Line Summary screen.
|
IBM Sterling Store Engagement (Legacy) | ||
580088 | Internal |
The information in the About window of IBM Store Engagement application contains "Sterling Store".
Solution: The information in the About window is updated. It now displays “IBM Sterling Store Engagement”. |
591286 | TS004156298 | An order contains the same SKU in two different lines. Short pick the first line and backroom pick the second line. On scanning the SKU by using registerBarCode the error message, "Customer Picked Quantity exceeds Shipment Line Quantity. Error Code: YCD00079" is displayed during customer pick. |
584498 | TS002316896 | The Search option is not available for the Pack Orders, Receive Shipments, and the Check Out portlets. |
587797 | Internal | An enhancement to backroom pick mashup layer for passing additional attributes to the change Order API call when a shortage is recorded. This enhancement is provided to support a (future) feature for business users. |
587868 | TS002970502 | In the Chrome browser, labels are incorrectly aligned in the search fields. |
588146 | Internal |
When a mashup call is initiated from UI, DB lock is acquired on the required records and worked upon. Once the actual API associated with the mashup is complete, the lock is released and the control flows back to the (massageOutput method of the) custom class associated with the mashup. While this happens, if another JVM acquires the lock on the record and modifies it, the lockId is updated. However, at the mashup later, the thread is still alive so is the context associated to the mashup call and therefore the transaction cache. If a subsequent call to change the entity is made from the massageOutput method of the mashup that uses the same context (which still has the record in transaction cache) and tries to execute the API call, the stale record from transaction cache gets picked up while the record is already updated in DB by another JVM. When API tries to commit the modifications to this stale record, Update failed. The record to be updated could either not be found or it was already deleted or updated by another transaction error is seen.
Solution: A new releaseTransaction method is added in mashup helper. This is invoked from ValidateGetTrackingNoAndPrintLabel before you make the changeShipment call so that fresh record from database is fetched for updation. |
588389 | TS003336603 |
Pagination issue with the Customer Pickup Orders screen in the Angular version of IBM Sterling Store Engagement. The UI displays only the first few pages and does not display the rest of the pages when the total number of orders is more than 30.
Solution: UI code is fixed to resolve the pagination issue to display all the orders. |
588444 | TS003393724 |
When the user clicks the back button on the Pick order or My tasks wizard, it is not redirected to the previously selected tab.
Solution: The code is modified to resolve the issue. It now redirects correctly to the previously selected tab on clicking the back button from the Pick order or My tasks wizard. |
588582 | Internal | Pagination issue in the My Tasks screen in the Angular version of IBM Sterling Store Engagement. The user interface displays only the first few records and does not display the rest of the records when the total number of orders is more than 30. |
590814 | Internal | French characters are being encoded in portlet headers of the mobile store resulting in distorted literals. |
590888 | Internal | When shipment count is greater than 1000 for the backroom pick portlet on the home screen of the application, the total count for Spanish locale is displayed incorrectly and the total count for English locale is displayed as NaN. |
591198 | Internal | In the IBM Sterling Store Engagement UI, user is unable to return total quantity when an order is over-shipped. |
591439 | Internal |
A store user cannot pick up the allowed number of items. The allowed number of items is the over-ship percentage limit.
Solution: A new rule WSC_ALLOW_OVERPICK_AT_STORE is introduced with default value as N. Setting this rule to Y enables store users to pickup items up to the over-ship percentage limit.
|
591708 | Internal | When the user logs in to IBM Sterling Store Engagement, the value of the WSC_ALLOW_OVERPICK_AT_STORE rule is logged only if the UI debug logs are enabled. |
591807 | TS004872388 | When manual packing is done for a shipment with only 1 unit, ContainerType is not stamped as Case. As a result, this container is not being received in the Receiving flow. |
592271 | Internal |
Image is broken in the user interface when users try to configure the image url with indirect URLs.
Solution: A new property "ycd.ui.imageId.encoding.reqd" is added to enable or disable URL encoding. Default value is set to 'Y' to enable the encoding. IBM Sterling Store Engagement now enables and disables the image url encoding based on this new property value. |
592319 | TS006280037 | A store user cannot pick up the allowed number of items. The allowed number of items is the over-ship percentage limit. Solution: A new rule WSC_ALLOW_OVERPICK_AT_STORE is introduced with default value as N. Setting this rule to Y enables store users to pickup items up to the over-ship percentage limit. |
592322 | Internal | In the batch list page, the logged in user name is displayed instead of assigned to user for the batch. |
IBM Sterling Call Center | ||
587548 | Internal |
In the Network tab of the Payment Confirmation page, the following images are displayed with the Status 404 Not Found error.
This error occurs when Promotion coupons are applied for both valid and invalid coupons and the application tries to retrieve the files where it references to non-existing images.
Solution: The files are now referenced from valid images.
|
587643 | Internal | DB localization is not applied for the Hold Description field of Resolve Holds screen. |
588080 |
TS003208144
|
When you create a return order for bundle order line, the add return lines screen does not show bundle parent lines. |
589302 | Internal | When a user logs on to the application as a French user, in the Customer Details screen, the localized values for CustomerClassificationCode and CustomerLevel are not displayed. |
589305 | Internal |
When a user logs on to the application as a French user, a scroll bar is displayed in the Confirm closing draft order page.
Solution: The width of the pop-up window is increased so that the scroll bar is not displayed.
|
589308 | Internal | In the Select/View pop-up window of the Change Fulfillment Options screen, the Previous and Next links are not aligned for a French user. |
589838 | TS003870139 |
In the Payment Confirmation screen, when PRICE_CHANGE is disallowed at the order header level, the Manage Adjustments link is disabled. Therefore, users cannot change the price at the line level.
|
590959 | Internal |
The Payment Summary screen is enhanced. A new link allows the user to adjust the pending amount to cover the required funds on the order, when a payment method that requires processing is on the order but sufficient funds are not provided. The Adjust Pending Amount resource permission is added to control visibility of this new link.
|
591199 | Internal | The scroll bar is not present in some sections where product or customer information is displayed. Hence if more number of records exist, related information is not available in adjacent sections. |
591247 | Internal |
The application is enhanced such that when the enterprise rule ISCCS_ALLOW_CHECK_CORRECTION is set to Y, the user can edit the request amount of a payment that has the payment type defined as CHECK.
|
591407 | TS004693893 |
When an order and the corresponding order lines are moved to be partially included in the shipment status, a user is not able to cancel the back-ordered quantity.
|
591992 | OM-1522 |
IBM Sterling Call Center is updated to show the total number of results in the Search Results pages for the following searches:
|
592030 | TS005715267 |
Order search does not display the status of draft orders.
|
592056 | TS005759561 |
In the Add items page, clicking Next without adding an item results in the following generic error message:
There are errors on the page. You cannot proceed until you fix them.
Solution: A detailed error message explaining the action to take is now displayed for the same behavior.
|
592057 | TS005696903 |
Item validation does not work as expected when the user navigates to the next page by using the pagination links in the Add items page. The user is able to navigate to the next page even if there is an error on an item on the page.
Solution: If any errors occur on a page, the user cannot navigate to the next page by clicking the pagination links. |
592067 |
TS005697061
|
When a user tries to view all invoices from the Why was I Charged view, the invoice number is passed as an input to the API and the user is not able to view all invoices.
|
592254 | TS006020793 | Order is created for item that is in stock. In IBM Sterling Call Center, when a user searches for the order and clicks Add Lines to Order, availability is displayed as out of stock. |
592345 | TS006354056 | When you open an archived order, select an order line to view the order line summary, and then navigate back to the Order summary page, an error message for an invalid order is displayed. |
Was this topic helpful?
Document Information
Modified date:
23 March 2022
UID
ibm16480711