Fixes by fix pack version

Solution: The application is enhanced such that when pricing rule is null, it stops populating the output attribute values for the attribute RejectedPricingRules.

• YFS_RES_POOL_STD_CAPCTY_PERD
• YFS_RES_POOL_DOW_CAPCTY
• YFS_RES_POOL_CAPCTY_OVERRIDE

  To enable caching for the listed tables, complete the following steps.

  1. Set following properties in customer overrides.
     • dbclassCache.YFS_RES_POOL_STD_CAPCTY_PERD.class=com.yantra.shared.dbclasses.YFS_Res_Pool_Std_Capacity_PeriodDBCacheHome
     • dbclassCache.YFS_RES_POOL_DOW_CAPCTY.class=com.yantra.shared.dbclasses.YFS_Res_Pool_Dow_CapctyDBCacheHome
     • dbclassCache.YFS_RES_POOL_CAPCTY_OVERRIDE.class=com.yantra.shared.dbclasses.YFS_Res_Pool_Capcty_OverrideDBCacheHome
  2. Build and deploy the EAR.

Solution: The application is enhanced to add a Carrier Service Code selection box to choose the carrier service code. Additionally, a Shipping Charge textbox is added to add the shipping charge and carrier service option to calculate the ShipOrderTotal coupon successfully.

The getApplicablePricingList API is fixed to handle custom pricing rule when YPMGetApplicablePricingRuleListUE is enabled.

For more information about the workload segregation feature, see workorder segregation feature.

Order attributes: IsLargeOrder, IsVeryLargeOrder, OrderSegregationFilter

Release attributes: IsLargeRelease, IsVeryLargeRelease, ReleaseSegregationFilter

These indicators are also available as condition builder attributes so that you can easily add conditions in your order processing model. For more information about these attributes, see condition builder attributes.

Solution: The conditional checks of RejectedPricingRules are updated such that it is considered for further processing even if it is empty, provided that there is a rejected pricing rule available.

Solution: The conditional checks of RejectedPricingRules are updated such that it is considered for further processing even if it is empty, provided that there is a rejected pricing rule available.

Solution: The log4j2 issue is fixed such that the timer logic is bypassed if timer logs are not enabled.

Solution: Updated the Javadoc for getChargeTransactionRequestList API. Also, removed the ChargeTransactionDetails tag.

1. Creates a node STORE_1 with two capacity resource pools, one each for PICK and SHP deliveryMethod. Standard capacity is defined.
2. Adjusts inventory for ITEM_1 at STORE_1.
3. Creates reservation RSV_1 for two promise lines from ITEM_1 at STORE_1 with different DeliveryMethod - PICK and SHIP. Here, one capacity is consumed for both resource pools against inventory reservation.
4. Calls the createOrder API with two order lines - node STORE_1 and ItemID ITEM_1, along with the reservation information. The delivery methods on lines are SHP and PICK.

The inventory reservation is removed but capacity consumption is incorrectly consumed.

For more information about the getResourcePoolCapacity API, see Javadoc.

Solution: The fulfillmentType response is added to the getCompleteOrderDetails request template. Due to this, the fulfillmentType response is directly passed to the createInputforFindInventory method, which returns the updated value from the createInputforFindInventory method.

For more information about the manageCapacityReservation API, see Javadoc.

It is recommended that you set a string value for this property. For example, ycd.ui.wsc.angularJs.cacheburst=v1.0.

Solution: The application is now enhanced such that the invoice processing does not run into an infinite loop.

Solution: The jboss-deployment-structure.xml is updated to add the missing package and the Application Manager now works as expected.

Solution: The manageCapacityReservation API is enhanced to update capacity during transaction commit similar to order and inventory reservation APIs. If yfs.yfs.persitCapacityAdjustments is set to true, you can pass PersistCapacityAdjustments="Y" in manageCapacityReservation API such that capacity is updated only when a transaction is committed. For more information about the manageCapacityReservation API, see Javadoc.

Solution: The Hot SKU feature is enhanced to handle deadlock error by rolling back the complete transaction.

Solution: A new property yfs.workorder.backorderAfterApptEndDate is added. When it is set to Y, the releaseOrder API moves the product line to backordered status if work order appointment is expired. The default value of yfs.workorder.backorderAfterApptEndDate is N.

Documentation is updated for yfs.properties file.

Solution: The application is enhanced to invoke YFSGetExternalInventoryForItemListUE user exit when segment information is present on order lines. User exit is called once for each product item, if segment information is present.

Solution: The ordered_quantity attribute is now updated correctly during the drop ship order, such that the total value is shown against a line having bundle item.

Solution: The special characters ($^*) are added to the regular expression such that the password now accepts special characters in SMA.

• What's New
• What's Changed
• Customizing log4j2 configuration
• Migrating to log4j2

Solution: The payment collection logic is enhanced such that the order processing does not run into an infinite loop and performs efficiently.

Solution: A void check is carried before using a pricing rule, so that the NullPointerException is resolved.

Solution: A validation is added for the filter class entry to avoid overwriting the web.xml when merging extended web.xml with the out of the box web.xml. The validation ensures that the correct filter classpath is reflected in the final web.xml.

Solution: Data extract is enhanced such that it checks whether a column exists for the fed input and the cases (uppercase, title case, and lowercase) of the input.

• Inventory management yfs.properties
• Inventory purge

Solution: The application is enhanced to perform an auto compression of data before inserting it into database, when database is DB2, data size is more than 1 MB, and the column supports data compression.

1. Creates a Transfer Order by passing RecievingNode and ReqDeliveryDate attributes and keeping ShipNode as blank.
2. Returns blank output for the YFSGetDeliveryLeadTime user exit when ShipNode is blank.

Solution: You must set the yfs.promising.doNotPushShipDate property to Y to stop pushing ETS to ReqDeliveryDate.

When the application is upgraded from V9.5 to V10.0, the Sales Order value in the App Console changes to Order.

Solution: The value of Sales Order in ycpapibundle.properties under key 0001_Order is modified.

• Close manifest

1. Place an order for ITEM_1 at STORE_1 that has no inventory.
2. Schedule the order. It backorders against the STORE_1.
3. Adjust the inventory for ITEM_1 at ship node, STORE_1.
4. Run the item-based allocation (IBA) agent so that the inventory is reserved. The YFS_INVENTORY_DEMAND_DTLS table does not have any entry at this point.
5. Schedule the order.

1. Create two nodes STORE_1 and STORE_2. Transfer relation exist from STORE_2 to STORE_1 with 1 day transit.
2. Define a capacity resource pool STORE_1 with two slots; S1 from 07:00:00 to 16:00:00 and S2 from 16:01:00 to 23:59:59, with capacity at S1 as 2 and S2 as 10.
3. Adjust inventory for ITEM_1 at STORE_2 for 5 quantities.
4. Create procurement rules to source at STORE_1 from STORE_2.
5. Configure GetDeveliverLeadtimeUE to override transfer schedule for STORE_2 to STORE_1 with LeadTime="3" and OverrideTransferSchedule="Y".
6. Create and schedule the order for 5 quantities.

1. Set the node, install.localecode, and DB locale to CST (UTC-6).
2. Configure the node such that it does not maintain a shipping calendar.
3. Configure the value of Maximum number of days order can be shipped/delivered beyond its request date scheduling rule as 0.
4. Call the findInventory API between 23:00:00 and 23:59:59 hours on the day of DST switch. For example, on 11/01/2020 at 23:03:00 in CST time zone.

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.

1. Server and DB locale are set to UTC and node locale to UTC+9.
2. Node has a shipping calendar of 08:00:00 to 22:00:00 with single shift and is working all days.
3. Node has inventory capacity available for the entire week; default slot is 00:00:00 to 23:59:59.
4. Scheduling rule has Maximum no. of days order can be scheduled before its ship date set to 0.
5. Node has sufficient inventory and node capacity for the order to be scheduled.
6. A single-line order is created on the current day at 17:48 server time (UTC).
7. The changeOrder API is called on the same day at 17:48 server time (UTC) to change requested ship date to next day at 23:15:00.
8. The scheduleOrder API is called at CD 23:16 server time (UTC).

Solution: For a payment type, a new Sterling Business Center configuration setting named Link Payment Refund To Settlement Transactions is introduced. When you configure this setting, link to corresponding settlements transactions is provided during the refund.

Solution: The application is enhanced such that the custom property, sequence is overridden with the default sequence value.

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.

1. Creates a node STORE_1 with two capacity resource pools, one each for PICK and SHP deliveryMethod. Standard capacity is defined.
2. Adjusts inventory for ITEM_1 at STORE_1.
3. Creates reservation RSV_1 for two promise lines from ITEM_1 at STORE_1 with different DeliveryMethod - PICK and SHIP. Here, one capacity is consumed for both resource pools against inventory reservation.
4. Calls the createOrder API with two order lines - node STORE_1 and ItemID ITEM_1, along with the reservation information. The delivery method on lines are SHP and PICK.

The inventory reservation is removed but capacity consumption is incorrectly consumed.

Solution: In the multiple shipments scenario, validation is added to check if the reversal is required and if not required, the reversal is stopped.

1. Enables the IBM Sterling Inventory Visibility integration phase 2.5.
2. Creates a distribution group and assign three nodes to the group with the following priorities:
   • NODE1 - Priority 10
   • NODE2 - Priority 20
   • NODE3 - Priority 30
3. Sets the sourcing rule to source inventory from the distribution group.
4. In the scheduling rule, sets Optimize On to Cost, Number of Shipments.
5. Creates an order with three lines such that each line is for 1 quantity of the same item. For example, ITEM1.
   • Line1: ITEM1 - Quantity 1
   • Line2: ITEM1 - Quantity 1
   • Line3: ITEM1 - Quantity 1
6. Calls the scheduleOrder API to schedule the order.
7. Schedules the order by calling the scheduleOrder API.

Solution: The value is not set to in_person=Y for return invoices.

Solution: The application is enhanced to first sort the tenders so that the suspended tenders move at the end. Hence, the transfer out or distribution are generated first for non-suspended tenders.

Solution: The value of the inPerson flag is set to “Y”. Now the carry line invoice is considered as an in-person invoice.

Failed to invoke IVIntegrationApi : Remote response: 400: Invalid demandType passed

• Batch picking
• Configuring shipment-based batch picking
• Implementing shipment-based batch pick in Store Inventory Management (SIM)-disabled stores
• Picking products in batches based on shipments in Sterling Store Inventory Management (SIM)-disabled stores

Solution: Set the yfs.SyncTagSerialKeyWithMessageLineKey=true custom property to enable the consolidation of supply when only serial information is available on the shipment line.

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.

Solution: You can now delete any parent item in a free gift scenario. The YFS10137 modification error is displayed only when expected.

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.

1. Create NODE_1, a node that works from 00:00:00 to 23:59:00.
2. Create CAR_SERVICE, a carrier service that delivers only on weekdays and transits all days.
3. Create a carrier pickup at NODE_1 for CAR_SERVICE from Monday to Friday at 18:00.
4. Create BUNDLE_1, a deliver together bundle item that contains two components, COMP_ITEM_1 and COMP_ITEM_2.
5. The inventory for components is only available on a future date on any Saturday or Sunday.
6. The delivery lead time UE is implemented to return 20 lead days for the pair of address.
7. Call the findInventory API for item BUNDLE_1.

Solution: The application does not support capacity adjustment in a non-working slot. Therefore, during scheduling, if ExpectedShipmentDate for an order is rescheduled because of the availability in a non-working slot, the order is back ordered.

1. Crete a return order.
2. Create an advanced exchange order.
3. Call the processReturnOrder API for the return order.
   Note: Before you create an invoice on a return order ensure to cancel the exchange order.
4. Verify that the exchange order contains Transfer In with only the request amount and not credit amount. Now, cancel the exchange order.
5. Call the requestCollection API for the exchange order. A Transfer Out is created for the exchange order with a credit amount.

Solution: For payment collection, the ON_RFO_CREATION event is introduced. This event XML contains the RFO reason codes and other details.

Solution: The platform is now enhanced to customize the cached attribute.

Solution: The application is enhanced to fix the incorrect status that is returned on calling the getCompleteOrderLineDetails API.

1. Launch Sterling Inventory Visibility and reserve an item at a node that has one quantity.

   A reservation is created for one quantity of the item at the node level.

2. Create an order by using the createOrder API and pass the reservation information in the OrderLineReservation element of the createOrder API as input.
3. Call the scheduleOrder API to schedule the order.

Solution: If you have already reserved item quantity before creating an order, the scheduleOrder API must not create reservations in Sterling Inventory Visibility.

1. Go to Products > Item Classification and create a classification hierarchy.
2. Assign 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 associate a product item.
4. In 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. In Safety Factor based on Delivery Method, set Onhand Safety Factor for all the three delivery methods.
7. Go to Manage Classification Values and delete the value from the Item Type field under Organization Classification. Click Save.
8. Go to Manage Inventory Information, clear the Onhand Safety Factor checkbox under Promising, and click Save.
9. Switch to Onhand Safety Factor type from Percent to Units, and click Save.

Solution: The following properties are added to handle the pipe characters (|||) for untagged controlled items while synchronizing supply and demands from Sterling Order Management System Software to Sterling Inventory Visibility.

When you sync inventory to Sterling Inventory Visibility for the first time, ensure to set the value of these properties to Y in the customer_overrides file. By default, the value is set to N.

A new custom property yfs.solver.ExcludeRejectedChoiceFromRoutingUE is introduced and must be set to true to observe the change in behavior.

1. Create a time-sensitive item, say ITEM_1, with the default expiration days as 0.
2. Adjust supply for ITEM_1 at NODE_1 for one quantity with ShipByDate="2021-10-31" and another quantity with ShipByDate="2021-12-31".
3. Create an order with 2 lines for ITEM_1 at NODE_1 with one quantity on each line.
4. On Line 2, modify MinShipByDate="2021-12-31".
5. Schedule the order.
6. Line 2 is back-ordered.

Solution: Changes are made to consider reservation as a valid supply during the scheduling of the line if smart sourcing is enabled.

Solution: Pass the root node as X-XAPI-Tag in the HTTP header of the request. For more information about the X-XAPI-Tag, see IBM Documentation.

Solution: While integrating with parcel carrier systems, ensure that you configure the yfs.shipcartondoc.attr.length property to set the length of ConsigneeEmailAddress and ShipperEmailAddress attributes in the ShipCarton XML. The default value of the property is set to 35.

Solution: This issue is resolved such that the error state no longer persists after a new user logs in through SSO with access permissions.

In customer overrides, set yfs.yfs.webxmlvalidation.disabled=Y to disable certain validations that are performed when building the EAR.

For more information about the getAlertStatisticsForUser API, see Javadoc.

For more information about the getShipNodeList API, see Javadoc.

For more information about migration, see Migrating from Sterling Global Inventory Visibility to Sterling Inventory Visibility.

Configuration: NODE1 locale is PST and NODE2 locale is ETS. Both nodes are working from 08:00 to 16:59 in there respective locales. End Of Shift is enabled for both nodes.

1. Adjust inventory for ITEM_1 at STORE_1. Capacity resource pool exist at STORE_1 with slot groups.
2. Create Reservation RSV_1 for ITEM_1 by using the reserveAvailableInventory API. A capacity is consumed at this step.
3. Cancel Reservation RSV_1. The capacity consumption is not removed.

1. Application Install locale or time zone is set to UTC, which is GMT+00:00 and the locale or time zone of the node, NODE1 is Chile, which is GMT-04:00.
2. NODE1 has a working calendar of 09:00 to 20:00.
3. Inventory capacity is defined for NODE1.
4. The yfs.useNodeLocaleTimeForCapacityCheck property is set to true.
5. If the current working date and time at NODE1 is 2020-04-30 08:00, and if the findInventory API is called with ReqEndDate="2020-04-30T23:00:00" and ReqStartDate="2020-04-30T00:00:00", the findInventory API fails to find inventory availability.

Bundle items get back-ordered when fourth integration is enabled because Sterling Order Management System Software attempts to create a temporary reservation for the parent item, which does not have inventory in fourth as it is just a logical item.

This issue is resolved such that OPEN_ORDER is passed instead.

• getOrgRelationshipTypeList
• getNodeTypeList
• getSourcingConfig
• manageAllocationRule
• manageSourcingConfig

The manageSourcingRule API is also updated to support SourcingRuleName, SourcingRuleShortDescription, and SourcingRuleLongDescription attributes.

For more information about these APIs, see Javadoc.

The records are merged only if they qualify under purge criteria. To enable this feature, set yfs.purge.MergeDemandSupplyMultiRec=true in DB properties.

1. Check availability in Sterling 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.

Solution: A validation is run to verify that the order release status that is selected to move out quantity does not contain zero quantity.

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 Javadoc.

Solution: The node capacity locking now works for nodes 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.

For more information, see Node capacity locking.

In customer overrides, set yfs.yfs.order.bcTaxReferences=Y to change the tax reference attributes in the API output.

Solution: To control the exit condition, a new property yfs.calendar.maxNonWorkingDayLimit is added and the value is defaulted to 20 days.

Solution: The landed cost calculation is enhanced to consider the procurement cost for the procured quantity. To consider the procurement cost for assignment comparison, ensure to configure yfs.yfs.OptimizationCostUsageLevel=2.

Solution: You can add a custom node with com.yantra.omp.business.order.OMPSCWCMassageForBundleXML class and massageOrderXMLForBundleReservations method to the create order service definition by including it as a custom API node that breaks the bundle reservations into component level reservations and passes it to the createOrder API node.

The com.yantra.omp.business.order.OMPSCWCMassageForBundleXML class name is provided as part of the core deployment on completing the following custom implementation:

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 System Software prevents the releaseOrder API from moving the ship date for an order line to the last ship date, which meets ReqDeliveryDate.

Solution: The landed cost calculation is enhanced to consider the procurement cost for procured quantity. To consider the procurement cost for assignment comparison, ensure to configure yfs.yfs.OptimizationCostUsageLevel=2.

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.

Solution: The application is enhanced to call the scheduleOrder API that fetches the order object only after verifying the order header is not null or blank.

Solution: The event for the changeException API is triggered so that the corresponding event handlers are also invoked.

For more information about the indicator image, see Adding a service level indicator.

Solution: The process of loading the resource bundle is optimized so that when the Application server starts the resource bundle is initialized faster.

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.

Solution: The logic for calculating the TotalAltRefundedAmount is updated such that the amount is distributed even if the Sales order payment method is different from the Return order payment method.

When Reverse Excess is enabled, and if an authorization expires the application validates and reverses the authorization.

For more information about the authorization reversal strategy, see Configuration options.

• Records are fetched from the main and history tables.
• The input XML file contains MaximumRecords attribute. Whereas, the output XML file contains TotalNumberOfRecords attribute.

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.

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.

For more information about the order history purge tables, see Order history purge.

Condition: Adjust inventory for a normal item 'I1' and sometimes tag-controlled item 'I2' at location L1. Item I2 has no tag record in the system. Creates a cycle count request and task for location L1 by using the 'CREATE_COUNT_TASKS_79' agent.

Problem: In the Applications Manager, when you attempt to complete a count task through Count Program Condition Details console, the error message, 'Concurrent Modification Exception' is displayed.

• Onhand Safety Factor Quantity
• Onhand Safety Factor Percentage
• Future Safety Factor Percentage

Solution: A new yfs property, yfs.maxRetryWaitforPIcommit is introduced. Use this property to specify the maximum number of times a thread should wait for a person info record to be committed in the database. In the customer_overrides.properties file set the value of this property as yfs.yfs.maxRetryWaitforPIcommit =<Integer>. For example, yfs.yfs.maxRetryWaitforPIcommit =2. The default value of this property is set to 1.

For more information about the yfs.waitforPIcommit property, see Implementation yfs.properties.

Solution: To optimize the query while fetching the child containers from the shipment container table, in DB properties set the value of yfs.applyChildContainerQueryOptimization property to Y.

1. The Delayed authorization parameter in payment rule is enabled.
2. The order is created with the payment method as charge, not authorize.
3. The processOrderPayment API is run twice.

1. Implements YPMGetOrderPriceUE to return the additional line price in the output.
2. Creates an order.
3. Calls the repriceOrder API with ForceReprice=Y.

For more information about the yfs.persitCapacityAdjustments property, see Inventory management yfs.properties.

For example, when Line 1 is partially shipped from two nodes, node A and node B, the ship node is incorrectly displayed.

Solution: A new property, yfs.payment.supressAllRefundsIfPaymentSuspended is introduced. 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, which 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.

1. Calls the adjustInventory API for an item to adjust inventory, say 20.
2. Calls the loadInventoryMismatch API for an item-node combination with quantity 0.
3. Calls the syncLoadedInventory API to process the created inventory mismatch record.

For more details, contact IBM Support.

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.

Solution: The past records from the YFS_CALENDAR_EXCP_SHIFT table is not read.

Solution: Logging is enhanced for the Inventory Snapshot agent.

If capacity on a current date is insufficient for the ordered quantity, the order gets scheduled after the one day window.

Solution: The Reservation purge is modified to pick up the reservation record for purge if it has zero quantity or the expiration date is earlier than the current date minus retention days mentioned in the purge criteria.

For more information, see Reservation Purge.

1. Performs the nomenclature setup, such as defining the nomenclature codes, definitions, mappings, and configurations.
2. Creates a custom service to perform the translation by using the nomenclature runtime component.
3. Invokes the custom service with some valid input data which is missing from codes.

Solution: This column is not required to be shown on UI and its purpose is backend synchronization. Its updated value is fetched and used from the database directly. As part of the fix, this column value is no longer sent to the UI.

1. Creates two nodes N1 and N2, and also creates a node transfer schedule from node N2 to N1 with 5 transit days.
2. Configures the carrier service pick up for the service PICK_INTERNAL at node N2 where the carrier service has to pick up at 00:00:00 on the applicable days.
3. Adjusts an inventory at node N2 for 5 quantities. For example, ITEM_1.
4. Ensures that the YFSGetDeliveryLeadTimeUE is implemented to return 10 days of transit from node N2 to node N1.
5. Creates the order with the Ship node N2 and the Receiving node N1 for ITEM_1.
6. Schedules the order. ETS is the current date +1 and the delivery date is current date + 11.
7. Releases the order. The order is back ordered.

Solution: Set the yfs.yfs.useOnlyDemandDate=true property in the customer_overrides.properties file to enable additional logging and to prevent demand ship date updates to happen with the timestamps.

Solution: Fixed the API Javadoc encoding for the getOrderDetails and getCompleteOrderDetails APIs so that the API Javadoc are correctly generated and fully functional.

1. Creates a node, NODE_1 that has a working shift from 08:00 to 16:59.
2. Sets the locale for NODE_1 to UTC-4, and the install locale is UTC.
3. Creates the SG_1 slot group with the 08:00 to 16:59 slot in the hub organization.
4. Creates a resource pool for NODE_1 of the Release type with the slot group SG_1 and adjusts the capacity.
5. Ensures that there is no capacity available on the current day in NODE_1.
6. Creates two orders and schedules them such that two units of capacity are consumed on the current day +1.
7. Creates a reservation, RSV_001 with three lines that have one quantity each for ITEM_1, ITEM_2, and ITEM_3.
8. Creates an order with one line each for item ITEM_1, ITEM_2, and ITEM_3 by using the RSV_001 reservation.
9. Schedules the order.

1. The locale or time zone of the Application Install is set to UTC, which is GMT+00:00, and the locale or time zone of the NODE1 node is set to Chile, which is GMT-04:00.
2. NODE1 has a working calendar of 09:00 to 20:00.
3. Inventory capacity is defined for NODE1.
4. The yfs.useNodeLocaleTimeForCapacityCheck property is set to true.
5. If the current working date and time at NODE1 is 2020-04-30 08:00, and on calling the findInventory API with ReqEndDate=2020-04-30T23:00:00 and ReqStartDate=2020-04-30T00:00:00, the findInventory API fails to find inventory availability.

1. Creates a node, NODE_1.
2. Creates a resource pool for the UOM RELEASE on NODE_1.
3. Creates two items, ITEM_1 and ITEM_2.
4. Adjusts the inventory for QTY 100 each for ITEM_1 and ITEM_2 on NODE_1.
5. Sets the yfs.persitCapacityAdjustments property to true.
6. Creates an order with two lines each.
   Line 1 -> ITEM1 | QTY 1.
   Line 2 -> ITEM2 | QTY 1.
7. Schedules the order.
8. Calls the unscheduleOrder and the scheduleOrder API from multi API for the above created order.

The changeRelease API starts the ON_SUCCESS event twice.

In Javadoc, for the getIntegrationErrorDetails API output XML, maximum length of the ErrorString field does not match the underlying table.

Solution: A validation is run to verify that the order release status that is selected to move out the quantity does not have zero quantity.

Solution: The thread locking optimization is introduced to improve lock performance of Promising functionality.

In the scheduleOrder API, when an order is scheduled, it does not consider the sourcing rule capacity constraint if the following conditions are true:

Solution: In the application logs,the warning message is fixed by removing duplicate entries in the mashup XML file of IBM Sterling Order Management Software.

Solution: The external properties are now stored in the database and are also available in the APIs output.

In the customer_overrides.properties file, if the value of YFS_REGION.entity.transactioncache.enabled property is set to false, changes are not observed when the database property management is enabled.

Solution: The fix is present in install_foundation.jar file, which is used to install the fix packs. Ensure to manually patch the fix.

Solution: This issue is resolved by reading the calendar from the pool instead of creating a new instance every time. Also, the default calendar pool size is increased from 10 to 25. To create a new calendar each time, set the value of the yfs.calendarpool.donotuse.yfcdateutils property to true in customer_overrides.properties file and redeploy the Application Server.

During the scheduling process, the ScheduleOrder agent results in null pointer exception.

The order gets intermittently back ordered when the capacity constraint Consider Only Those Nodes That Have A Minimum Available Capacity Of <capacity>% Within The Next No Of Day(s) check box is enabled in multiple sourcing sequences having the same node but different value for constraint.

In the scheduleOrder API, when the constraint Line Ship Complete is enabled in the scheduling rule and the order line is back ordered, the SchedFailureReasonCode attribute is not stamped.

During the OMPGetReturnOrderPriceUE user exit invocation, the Charge amount related to charge breakup is not in sync with the amount in header charge, if the following conditions are true.

When you complete the following steps and start the first refund by using customization or manually, the refund sequence is not working as expected.

Solution: The total alternative refund amount is properly set to 100$ in sales order corresponding to the return order RO1.

When the effective From date of the transfer schedule is set for a future date, the transfer schedule period displays null and then fails with Null Pointer exception.

Solution: A void check is made on the transfer schedule period object before using it.

When you complete the following steps to reserve capacity, the error message, "Not enough quantity" is displayed:

1. Logs in to the IBM Sterling Business Center.
2. Creates a slot group, SG_1 for the inventory.
3. Creates a Resource Pool with purpose, "INVENTORY" and slot group SG_1.
4. Adjusts the standard capacity for all days.
5. Calls the manageCapacityReservation API to reserve capacity for the current day.

For the Base rules, incorrect values are printed in the log.

Solution: Serviceability fix to print the correct Base rules in the verbose is enabled.

1. Adjusts the inventory for ITEM_1 at STORE_1.The capacity resource pool exists at STORE_1 with slot groups.
2. Calls the reserveAvailableInventory API to create reservation RSV_1 for ITEM_1.The capacity is consumed.
3. Cancels the reservation RSV_1. The capacity consumption is not deleted.

If confirmRefundDistributionUE is not implemented, and the payment method is set to Suspended for Charge and Refund, the application initiates 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.

When a user performs the following steps, an incorrect capacity consumption is observed:

1. Adjusts the inventory for ITEM_1 at STORE_1. The capacity resource pool exist at STORE_1 with slot groups.
2. Calls the reserveAvailableInventory API to create reservation, RSV_1 for ITEM_1. The capacity is consumed, and a reservation ID is provided.
3. Create an order and pass the reservation ID that you received. Another capacity is consumed.

Solution: The yfs.useDefaultCapctyConsmptnSlotDtls property is added. If you are using capacity with slot group,ensure to enable this property.

In Release 10.0, the Search Indexing capability for Order and Shipment entities is available for both sharded and non-sharded installations of IBM Sterling Order Management. In earlier releases, it was available only in a sharded instance. By default, the PLT_INDEX_CONFIG and YFS_INDEX_SYNC database tables contain the required entries to support the capability.

When you complete the following configuration for purchase orders, the ShipmentPurge agent stops purging shipments after one batch of records are processed.

Solution: The throughput of the purchase order ShipmentPurge agent is improved by adding lastMessageKey in the get Jobs () function output of the agent. Due to this enhancement, the ShipmentKey is stamped as lastMessageKey, so those dummy shipments whose order is purged, get processed for the purging process.

When you complete the following configuration step, the Store Value card should have charge up to available turned on and partially charged on the order.

In correction mode, the capturePayment API sets a wrong maxChargeLimit on the payment method, when the requested amount passed is more than the funds available on the Store Value card.

The copyHubModificationRules API does not copy the status modifications to the correct group when the Default_Group is not defined for the target organization.

Solution: Check if the Default_Group exists. If not, create a new Default_Group status modification group.

The system goes into an infinite loop and keeps refunding back when the Charge record associated with the invoice goes into 'Error' status post shipment and invoice. Set Authorization reversal as ReverseExcess and partial reversal supported, along with RSFN_DONT_CONSIDER_PENDING_CHARGES rule and DO_NOT_CONSOL_DEBITS_OR_CREDITS rule enabled.

Solution: The charge type CHARGE should be in OPEN status, without running into dynamic distribution error or creating disturbed financials.

Problem: The integration server for UBX_Server, that publishes data to UBX, throws an exception UBX0007 ErrorCode when the receiveOrder API confirms a return shipment.

Solution: The JSON data for the UBX event orderShipped is fixed to handle a return shipment created during the receiveOrder API call.

The inventory purge agent picks inventory reservation records to be purged if it has 0 quantity or a ship date that is earlier than the system date minus the purge criteria's retention days. This selection criteria might lead to incorrectly purging the inventory reservation records that are not expired.

Solution: Inventory purge is modified to pick up an inventory reservation record for purge if it has 0 quantity or an expiration date that is earlier than the system date minus the purge criteria's retention days.

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 an asynchronous request's response 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.

Operation: Invoke the confirmDraftOrder API on return draft orders.

Condition: Payment processing is enabled at organizations processing return orders. Return document type is eligible for payment updates. The return order is in Draft status and its payment status is Not Applicable.

Solution: Return order payment status during draft order confirmation should go to the Authorized status rather being in the Not applicable status. This ensures return orders go to the PAID status, when the requestCollection runs, making return order whose payment processing is done on the sales order, to be eligible for the purge process.

Solution: The UI is enhanced to pass attribute IsItemAttributeValueRule as N if the targeted rule is not defined on item attribute values.

Problem: When the Sterling Inventory Visibility integration Phase 2 is enabled, and the reserveAvailableInventory API is called without passing any value for the attribute DemandType in the input XML, then the API throws an Invalid demandType passed error.

Solution: Since with Phase 2 integration, the reserveAvailableInventory internally calls Sterling Inventory Visibility reservation API, after the fix, it passes the default demand type as OPEN_ORDER, which is supported by Sterling Inventory Visibility.

Solution: A new releaseTransaction method is added in mashup helper. This is invoked from ValidateGetTrackingNoAndPrintLabel before making the changeShipment call so that fresh record from database is fetched for update.

1. Create a sales order with two payment methods, one for 2035$ and another for 550$, and complete the order fulfillment until paid status.
2. Suspend one of the payment methods, say 2035$.
3. Create a partial return order for 2035$.

Solution: In Call Center Create Order screen, the availability column should consider the node notification and show the correct date.

1. Create an item and adjust one quantity for that item.

2. Create an order with an order line of three quantities.

3. Call the changeOrder to stamp the ShipNode in the order line.

4. Schedule the order by using the API tester. One quantity must be scheduled and other two quantities must be back ordered.

5. Unschedule the order from application console.

6. Adjust one more quantity for the same item to change the availability to two.

7. Schedule the order by using the API tester. Two quantities must be scheduled and one quantity must be back ordered.

8. Unschedule the order by using application console.

9. Schedule the order again by using the API tester.

Resolution: Column size of SERVICE_NAME in YFS_ASYNC_REQ is increased to 128 characters to match size of FLOW_NAME in YFS_FLOW.

Resolution: The update of routing source on the Load and shipment from 02 to 04 in the reported use case is prevented only when yfs.consolidate.shipments.for.preassigned.carrier property is set to Y.

Resolution: This issue is addressed. Also, the Creating a scheduling rule topic is updated to include the limitation.

Resolution: The .jar file names for MQ are updated. For more information, see About setting up runtime utilities on IBM WebSphere.

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 the Java docs.

1. Create two nodes, NODE_1 and NODE_2.
2. Create two items, ITEM_1 and ITEM_2 and adjust inventory for both the items at NODE_1 and NODE_2.
3. Create a resource pool of UOM "RELEASE" at NODE_1 and NODE_2 with the standard capacity of 1 for each day.
4. Create an order, ORDER_1 with two lines, 1 each for ITEM_1 and ITEM_2 with quantity 1.
5. Schedule ORDER_1.

   Observe that the two shipments are created as two lines that are either scheduled from different nodes or on different dates from the same node.

Problem: The security.propertyencrypter.class property is moved to yfs category. When running entitydeployer, the property value is not available as yfs category properties are loaded later and hence a class instance is not created.

Resolution:The yfs category properties are now loaded while looking for 'security.propertyencrypter.class' so that the class is picked up as expected.

Note that the fix is present in install_foundation.jar, which is used in the FP installation process itself. Hence, it cannot be patched as part of the FP and must be patched manually.

Resolution: The issue is resolved.

Problem: The createInventoryActivity API, when called with CreateForInvItemsAtNode="Y", causes the DB cursors to remain open.

Resolution: The issue is resolved.

Problem: When you configures the EDGE Deployment, multiple "java.lang.RuntimeException: ContextTracking" warning messages are displayed.

Resolution: The messages are suppressed on using the EDGE Deployment.

Problem: When transforming data using CDT, NULL values are not allowed for nullable columns.

Resolution: Replace the value with "" or "NULL" to nullify the column value during CDT transformation, provided the column is nullable.

Resolution: The issue is resolved.

Resolution: The issue is resolved.

Unnecessary authorization reversal and new authorization are created in consecutive payment API runs.

Installing Sterling Order Management System Software Professional Edition software:

• Performing a GUI-based installation
• Performing a text-based interactive installation

Installing Sterling Order Management System Software Enterprise Edition software:

• Performing a GUI-based installation
• Performing a text-based interactive installation

Solution:

Create the custom attribute and the Value Type (drown-down menu) is populated with Boolean, Date, Decimal, Integer, and Text.

Cannot get the source timestamp for demand integration with IV.

Operation:

Invoke the processReturnOrder API.

Configuration:

Implement the OMPGetReturnOrderPriceUE.

Solution:

The OMPGetReturnOrderPriceUE output is in sync with its UE implementation logic.

Solution: An extensibility property, Ignore OnDelete event on grid refresh is introduced. By default, the value of this property is set to false. When you modify the value to true, it prevents from triggering the onDelete event of JsonWriteStore.

1. Adjust inventory for an item, say ITEM_1 at NODE_1.
2. Create an order for ITEM_1.
3. Schedule and release the order.
4. Create a shipment with ExpectedDeliveryDate as future date.
5. In the Sterling Store application perform record shortage for the order line.

   The status of the order changes to Backorder.

6. Again schedule the order.

   ETS is marked as a future date.

Operation: Invoke getCompleteOrderInvoiceDetails API with the template that includes the Balance attribute in the InvoiceHeader element.

Solution: Balance should populate the difference between the total amount and collected amount.

1. Order is in the Paid status.
2. Creates a Debit memo.
3. Creates a Credit memo.
4. Runs processOrderPayments.

• Starting the applications manager
• Launching applications manager

1. Set the yfs.yfs.calcPlanRefForAllSuppressRefSettleWaitTillReturnInv=Y property.
2. Create a return order for $100.
3. Create an exchange order for $105.
4. Add a payment method to exchange order and settle $5.
5. Create an invoice for the return order. A transfer out from return to exchange is created for $100.
6. Call processReturnOrder on the return order. A transfer out of excess $5 is created from the return order to the exchange order.

To avoid the class cast exception, configure the implementation logic for YDMOverrideDetermineRoutingUE as only class and not as a service.

Operation:

The factory setup through fix pack installation process should be run to mark the Flow_Designable column in YFS_User_Exit table to N for YDMOverrideDetermineRoutingUE.

Configuration:

You cannot implement YDMOverrideDetermineRoutingUE as a service, rather implement as a java class.

Solution:

The fix pack installation process disables the Invoke through Service configuration in the YDMOverrideDetermineRoutingUE tables, as the product design exposes the YDMOverrideDetermineRoutingUE implementation as class.

Solution: Product has been enhanced to consider future inventory window attribute from sourcing rule details. Based on the number of days set in the Future Inventory window, the available supplies are now filtered.

For more information, see Inventory management yfs.properties.

1. Create a sales order with 2 quantity in an order line worth 8$ unit price, take it to completion, marking it invoiced and paid.
2. Create a return order for 2 quantities and corresponding advance exchange order only for 1 qty worth $9.9, take advance exchange order to completion and invoice the same.
3. Authorize the return order.

Solution:

With this fix, when we execute requestCollection API on exchange order, no infinite loop should happen. The nature of fix is to correct distribution happening between first partial transfer in ($8) from return order and invoice ($9.9) of exchange order.

For more details, contact IBM Support.

Solution: The product code is enhanced to handle the model change and to allow reconfigure gracefully.

Solution: Enhanced the product code to fix the hung thread issue.

The ABSOLUTE adjustment type is not meant for supplies with INFINITE availability type.

Resolution: On deletion of a category (after certain actions like moving an item from the category), it should not be seen on the left panel of Sterling Business Center under the catalog tree.

This property is introduced to handle the case where yfs.yfs.hotsku.lockItemOnInventoryChanges=N and the modifyFulfillmentOptions API is called on a scheduled order with the last remaining quantity of an item. The Commerce Call Center application throws the error "Inventory not Available for Order Line" because the API is trying to unschedule and reserve the remaining quantity in the same transaction.

The ExpectedShipmentDate and capacity consumption are not updated correctly when the following steps are performed.

Solution:

For more information about the migration sequence, see Running data migration.

• Inventory management yfs.properties
• Hot SKU control parameters

1. Create a node, say STORE_1. Configure sourcing such that this node is considered.
2. Create ITEM_1 and adjust inventory for this item on STORE_1
3. Create a Resource pool RP_1 at STORE_1 of type RELEASE.
4. Create an order with Order Line Reservation at current date for ITEM_1 and STORE_1. Make sure that 1 capacity is consumed for Resource pool RP_1.
5. Call scheduleOrder and releaseOrder APIs in a multi-API call.

Solution : After the fix, when an order has two free gift lines applied due to promotion and both the free lines are then canceled, no error is thrown.

For more details, contact IBM Support.

1. Create an Order with one Order Line of quantity, say 40.
2. Ensure that all 40 quantities are available at 40 different nodes.
3. Call the scheduleOrder API.

Problem: If multiple supply records are available for supply are being updated, incorrect inventory picture is observed after syncLoadedInventory API.

Solution: A new property, yfs.synchLoadedInventory.MultiRec, is added. When this property is enabled, the syncLoadedInventory API calculates the inventory picture against multiple supply records.

DBClassGenerator does not use the right statement variable for the setValuesOnDeletePreparedStatement method for the numeric data type, as a result, the ‘dbclassgen’ target returns the 'cannot find symbol' error, when the data type of the primary key of an extended table is ‘NUMBER’.

Condition: Exposing properties in the format required so that the same might be managed through database. Operation: Edit sandbox.cfg file to set DATABASE_PROPERTY_MANAGEMENT=true, run setupfiles.cmd (or sh) and loadProperties.cmd (or sh). Solution: Properties introduced should be manageable in database as well when DATABASE_PROPERTY_MANAGEMENT parameter is enabled in the sandbox.cfg file.

The Installing gulp and its dependencies topic is updated with the required fixes.

Problem: The health monitor startup script does not accept JVM arguments.

./startHealthMonitor.sh -jvmargs "<jvm_arguments>"

/startHealthMonitor.sh -jvmargs "-Dabc=foo -Dxyz=pqr"

The Javadoc description for the behavior of InsertMissingAttributeAllowedValues flag is updated for the manageItem API.

The product name "IBM Sterling Order Management Suite" is changed to "IBM Order Management Software".Known Issue: Some of the screens in the Application Console and Applications Manager UI might still show the old product name. This issue will be addressed in a later fix pack.

The name "IBM Sterling Business Center" is renamed to "Business Center"

Problem: The application server startup is slow due to JMX MBean initialization, which occurs during server startup. Solution: The JMX MBean initialization, which occurs during server startup might take more time due to stale entries in the yfs_heartbeat table. This initialization can be done asynchronously in a parallel thread by setting the value of yfs.jmx.initialize.async property to true (By default, the value is set to false) in the customer_overrides.properties file. This property ensures that the server startup activity is not blocked due to JMX initialization. By default, this initialization happens synchronously during server startup.

For pricing rule assignment and pricing rule seller assignment, if the assignment id is not passed, a new assignment is created. This issue is fixed by using key fields other than the assignment id to retrieve the assignment. In case you need to have two different assignments or more with same OOB column values but different extended column values, you must pass the assignment id. Additionally, the fix makes sure that an assignment id is assigned to the assignments created because of global assignment (CreateGlobalSellerAssignment or CreateGlobalCustomerAssignment).

Creating an order with item id that contains trailing spaces fails when validate item flag is turned on.

When createOrder and generateWorkOrder APIs are called in a single transaction boundary and person info has different value for IsCommercialAddress attribute, system throws "Could not find entity (probably changed lockid)" error message.

Documentation is appropriately updated for migration steps. For more information about the migration steps, see Premigration data validation.

Problem: The CSRF token authentication error is observed when the Enter key is pressed in the report/record receipt screen, while focus is on the Receiving Quantity text box.

Solution: Both the Enter key and the Save button in the report/record receipt screen can receive items, pressing the Enter key does not throw the CSRF token authentication issues anymore.

For more details, see the getOrderList API Javadoc.

Intermittently, the optimization on Cost or Number of shipments does not return optimal solution. The problem is observed in multi-line scenario where required quantity on an order line cannot be fulfilled from any single node.

Solution: Set yfs.yfs.solver.exploreMoreNodeDateOptions=true in customer_overrides.properties to see a change in behavior.
MaximumRecords may have to be set at a higher value to see optimal solution when this property is enabled. For more information about this property, see yfs.properties file.

Solution: Initialization of entity repository is fixed to take place only once even if it is called by multiple threads.

The output of getAvailabilityCache API does not show any information about future quantity or its availability.