IBM Support

IBM Sterling Order Management 21.2 Release Notes

Release Notes


Abstract

Resolved issues for IBM Sterling Order Management, IBM Sterling Store Engagement (Legacy), and IBM Sterling Call Center in the Release 21.2 and the subsequent minor updates.

Content

21.2 Minor update 2
Defect Case Number Description
591944 Internal
The value of the InPerson flag is set to null during the carry line invoicing. Therefore, the carry line invoice is considered as a not-in-person invoice.
Solution: The value of the InPerson flag is set to "Y". Now, the carry line invoice is considered as an in-person invoice.
592088 Internal
When the Sterling Inventory Visibility Phase 2 integration is enabled, the following error occurs if a work order is created for a value added service.
Failed to invoke IVIntegrationApi : Remote response: 400: Invalid demandType passed
592091 Internal IBM Sterling Store Engagement (legacy) is enhanced to perform shipment-based batch picking in stores that do not have Store Inventory Management (SIM) enabled, that is, either the Store Inventory Configuration settings in Applications Manager is set to SIM not enabled or the manageOrganizationHierarchy API is called with a value of 00 for the StoreInvConfig attribute.

The following APIs are enhanced:
  • getStoreBatchList API - To filter the batch list based on delivery method and department.
  • createStoreBatch API - To read the application name from the API input.
  • getStoreBatchDetails API - To return ExpectedShipmentDate, DeliveryMethod, and IsMixedBatch on StoreBatch and to support multiple totes for SORT_WHILE_PICK batch picking.
  • registerBatchPick API - To pick and unpick serialized product, to pick and unpick multiple quantities, to stop updating shipment status after the batch is completely picked, and to pick products in multiple totes per shipment.
  • recordShortageForBatchPick API - To handle custom shortage and to stop updating shipment status after the batch is completely picked.
592097 TS005838995
For serial tracked item, when inbound shipment is received that contains the ShipmentTagSerial information for shipment line, multiple supply updates are observed for a single line.
Solution: Set the yfs.SyncTagSerialKeyWithMessageLineKey=true custom property to enable the consolidation of supply when only serial information is available on the shipment line.
592101 TS005578713 In Sterling Business Center, if the master data upload fails due to the YIF_INCORRECT_RECORD_LENGTH error, the CSV file that you have downloaded does not contain any failure content.
592118 TS005696903
An error message is displayed in an incorrect screen of Sterling Call Center while validating item for large orders with more than 20 lines.
Solution: The validateItemForOrdering API returns error lines on the Add Products page that prevents you from going to the next page for large orders with more than 20 lines.
592119 TS005190943 In Sterling Store Engagement (Legacy), in the Add product page, a user cannot select item variants because of the unused attributes in the item variants.
592146 Internal If you configure inStorePaymentRequired=Y and call the changeOrder API, the InPerson and PostponedAmount are not populated in the charge transaction table. Therefore, when you call the requestCollection API, the order status does not change to "Authorized".
592149 Internal The order header charges and taxes are not allocated in the correct InPerson and NotInPerson columns.
592165 TS005935984
Deleting a parent item throws an exception when you try to cancel a promotion item from the Fulfillment Summary screen of Sterling Call Center.
Solution: You can now delete any parent item in a free gift scenario. The YFS10137 modification error is displayed only when expected.
592168 TS004809243 If the invoice publishing is set to At Creation, the handleRefunds API is called even when it has zero amount to refund and it in turn calls the OMPConfirmRefundDistributionUE user exit with incomplete data.
592184 Internal In the customer pickup flow, customer pickup shortages are updated in the shipment line along with the backroom pick shortage. Cumulative shortage of the backroom pick and the customer pickup is displayed in the shipment summary.
592185 TS006001622
When you call multiAPI, which includes multiple managePricingRuleSellerAssignment API calls, the application does not generate the ASSIGNMENT_ID. Due to this, when you attempt to insert a record in the YPM_PRICING_RULE_ASSIGNMENT table, the 'Record Already Exists' error message is displayed.
Solution: When you call the managePricingRuleSellerAssignment API, a unique ASSIGNMENT_ID is generated, which ensures that the unique constraint is not violated when inserting any record in the YPM_PRICING_RULE_ASSIGNMENT table.
592188 Internal When the Sterling Inventory Visibility Phase 2 integration is enabled, the bearer token is masked if the verbose trace is enabled.
592191 TS005957634
Temporary reservation that is created as part of the ScheduleOrder or releaseOrder is not sent in the demand update that is sent to Sterling Inventory Visibility when the order enterprise is different from that of the inventory organization.
592196 TS006002311 In Sterling Store Engagement (Legacy) and Sterling Call Center, language pack is not applied to the 21.2 release image.
21.2 Minor update 1
Defect Case Number Description
590063 TS003927921
When you use IBM Sterling Inventory Visibility as your inventory management system (phase 2), and perform the following steps, an order is backordered because the reservation attempt fails while scheduling an order:
  1. Go to IBM Sterling Inventory Visibility and reserve an item at a node that has one quantity.
  2. Reservation is created for one quantity of the item at the node level.
  3. Create an order by using the createOrder API and by passing the reservation information in the OrderLineReservation element of the createOrder API input.
  4. Call the ScheduleOrder API to schedule the order.
Solution: If the quantity is already reserved before order creation, the ScheduelOrder API must not create reservations in Sterling Inventory Visibility.
591201 TS004556551
The manageItem API fails with the YFC0009 error when you perform the following steps in Sterling Business Center:
  1. Go to Products > Item Classification, and then create Classification Hierarchy.
  2. Move 'Distinct Attributes' and 'Inherited Item Attributes' from Available Usages to Subscribed Usages.
  3. In the Classification Hierarchy, select a classification, go to Manage Items, and then associate a product item.
  4. Under Primary info, set the Effective Start Date field for the product item.
  5. Go to Manage Inventory Information for the product item and set Onhand Safety Factor (type:Percent) and Lead Days under Promising.
  6. Set Onhand Safety Factor under the Safety Factor based on Delivery Method section for all three delivery methods.
  7. Go to the Manage Classification Values page and remove the value from the Item Type field under Organization Classification, and then click Save.
  8. Go to the Manage Inventory Information page, clear the Onhand Safety Factor field under Promising, and then click Save.
  9. Switch Onhand Safety Factor type from Percent to Units, and then click Save.
591970 TS005077141
TS005177439		 Seller-specific price list is not considered in the product list page though it is considered in the product details page.
592050 Internal
When you sync supply and demands to Sterling Inventory Visibility (phase 1), Sterling Order Management sends the tag numbers to Sterling Inventory Visibility as |||.
Solution: The following properties are added to handle the pipe characters (|||) being added to untagged controlled items while synchronizing supply and demands from Sterling Order Management to Sterling Inventory Visibility.
  • iv_integration.demands.untaggedinv.tagnumber.useblank
  • iv_integration.supplies.untaggedinv.tagnumber.useblank
Default value = 'N'
Before you run the inventory sync to Sterling Inventory Visibility for the first time, ensure that these properties are set to ‘Y’ in the customer_overrides file.
After you configure these properties, for supplies and demands that contain untagged items, Sterling Order Management sends the tag numbers to Sterling Inventory Visibility as blank instead of |||.
592054 TS005693926
In Sterling Store Engagement (Legacy), incorrect SLA is displayed for Pickup orders because the threshold from Ship service indicator is used instead of the threshold from the Pickup service indicator.
Solution: Threshold is considered based on the delivery method.
592071 TS005675353
In IBM Sterling Call Center, when a user clicks search with categories in the product browsing page, a nullPointerException occurs.
592087 TS005747306 In IBM Sterling Call Center, the createReturn_getReturnFulfillmentSummaryDetails mashup response is cached and does not display the items that are added.
21.2
Defect Case Number Description
570413 Internal The Realtime Activity Based Monitor in the activity-based mode (01) is enhanced to consider only the specific activities.
As part of this enhancement, these properties are exposed, which must be configured as follows:
  • Set yfs.RTAM.ActivityPurposeToConsider= [ "," separated list of purpose ] to make RTAM activity based consider only the activities with "purpose" specified in the list in the JVM/agent server. For example, yfs.RTAM.activityPurposeToConsider=70,90.
  • Set yfs.RTAM.ActivityPurposeToExclude= [ "," separated list of purpose ] to make RTAM activity based not to consider only the activities with "purpose" specified in list in the JVM/agent server. For example, yfs.RTAM.ActivityPurposeToExclude=70.
If you do not specify the property in a JVM, by default all the activities are processed by MO-1. However, you cannot specify both the properties for a JVM.
590149 TS004050683 The YFSGetDeliveryLeadTimeUE user exit is enhanced to override the consideration of node transfer schedule between two addresses during multi-stop transfers.
590338 TS004099347 The CollectionInPerson attribute is introduced in the capturePayment API that overrides the IN_PERSON flag. For more information about the CollectionInPerson attribute description, see Javadoc.
590749 TS004227969
Prevent authorization reversal when a payment method is suspended and the authorization reversal strategy is enabled. Ideally, when the authorization reversal is enabled and if a payment method is suspended, the existing unused authorizations are reversed.

Solution: To override the authorization reversal strategy, a new column, yfs_payment.SUSPEND_EXP_AUTH_REVERSAL is introduced. You can update this column either by using the changeOrder API or Collection user exit. The flag overrides the Authorization Reversal Strategy for a suspended payment method.
If the value of yfs_payment.SUSPEND_EXP_AUTH_REVERSAL is set to Y and the payment method is suspended, the authorization reversal is not created against the suspended payment method. This flag overrides the Authorization Reversal Strategy only when the value of yfs_payment.suspend_any_more_charges is set to Y or B. For more information about the yfs_payment.suspend_any_more_charges column, see Javadoc.
In addition, two more columns, yfs_payment.reason_code and yfs_charge_transaction.reason_code are introduced. You can use these columns to update the reason code when the payment method and charge transaction are started.
591111 Internal
The getOrderList API fails and a NullPointerException occurs when the following conditions are true:
  • Records are fetched from the main and history tables.
  • The input XML file contains MaximumRecords attribute whereas the output XML file contains the TotalNumberOfRecords attribute.
591146 TS004390799
A new criteria, SkipPositiveIfAuthReversalExists 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 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.
591352 Internal The payment system is enhanced to allow a configurable delay between the creation and collection of no processing required charge. The yfs.payment.delayNoProcessingChargeMinutes property is added that controls how far in the future the collection date needs to be automatically set in minutes. By default, the value is set to zero minutes. If you do not configure the property, the charge is automatically processed as normal.
591372 Internal
The Sterling Business Center application is enhanced to allow enabling and disabling of ISCCS_ALLOW_CHECK_CORRECTION rule that controls whether the Amount field of a captured check can be edited in Sterling Call Center.
The ISCCS_ALLOW_CHECK_CORRECTION checkbox is added to the Payment screen of Sterling Call Center Administration with the description, Allow Editing Of Amount Field For Check Before Funds Are Collected.
591406 TS004655170
During the optimization of cost and number of shipments, if the Minimize Number Of Shipments To Customer Through Transfers Between Shipping Nodes checkbox is enabled, the landed cost calculation for assignment comparison does not consider the procurement cost even when a node is procuring quantity for fulfillment.

Solution: The landed cost calculation is enhanced to consider the procurement cost for the procured quantity. To consider the procurement cost for assignment comparison, configure yfs.yfs.OptimizationCostUsageLevel=2.
591418 TS004732201
Scheduling does not generate assignments for a ship node that does not ship for continuously 20 days.

Solution: To control the exit condition, a new property yfs.calendar.maxNonWorkingDayLimit is added and the value is defaulted to 20 days.
591626 Internal
The releaseOrder API moves the ship date for an order line to the last ship date, which meets ReqDeliveryDate.

Solution: A new property, yfs.promising.doNotPushShipDate is added and the value is defaulted to 'N'. If you change the value to 'Y', Sterling Order Management Software prevents the releaseOrder API from moving the ship date for an order line to the last ship date, which meets ReqDeliveryDate.
591956 TS004871229
You can start using Sterling Inventory Visibility as your inventory management system for IBM Sterling Order Management.
For more information about migrating to Sterling Inventory Visibility, see Using Sterling Inventory Visibility as your inventory management system.

[{"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:
15 September 2021

UID

ibm16456297

Page Feedback