Hot Fix Release Notes
	Product	Selling and Fulfillment Foundation, 8.5
	Date	Thursday, June 09, 2011
List of Defects Addressed
Hot Fix ID	8.5-HF49
Defect ID	196796
Case ID	Internal
Description	The application must be enhanced such that a user can configure multiple item attributes for the container category classification. Based on the configuration, the system-suggested containerization must occur. Currently, only one item attribute can be associated to a container category classification purpose.
Solution: The number of container category classification purposes has been increased from one to five. The users can configure five different item attributes, one each for a container category classification purpose. The application will consider these configured attributes during containerization.
Defect ID	196808
Case ID	Internal
Description	The Sterling Warehouse Management System: Configuration Guide and the Catalog Management: Configuration Guide must be updated with information about the enhanced container category classification purposes.
Solution: Information about the enhanced container category classification purposes has been updated in the following locations:
•	In  the Sterling Warehouse Management System: Configuration Guide, the field value description of  “Overpack when containerization category is in” and “Only for items with containerization category in” present in Table 9-12, “Pack Planning Window” under Section 9.5, “Defining Pack Planning” has been modified. Also, the screenshot of “Pack Planning” present in Section 9.5, “Defining Pack Planning” has been updated.
•	In the Catalog Management: Configuration Guide the description of the “Reserved for Items having the following Containerization Categories” field value present in Table 4-17, “Container Attributes Tab” under Section 4.1.2.13, “Defining a Product Item’s Container Attributes” has been modified.
•	In the Catalog Management: Configuration Guide the description of the “Container Category” field present in Table 4-28, “Classification Purposes Definitions” under Section 4.6.2, “Defining Classification Purposes” has been modified. Also, the screenshot of the Container Attributes tab present in the “Item Details” window has been updated.

Defect ID	246022
Case ID	00303058
Description	When the consolidateToShipment API is invoked to create a shipment, the Work Order Key and Work Order Appointment Key field does not get updated in the YFS_SHIPMENT table.
Defect ID	246207
Case ID	00212554
Description	The input of the getItemListForOrdering API must be exposed as an input element so that the application considers the service item as additional input criteria to determine a product item associated with a service line.
Defect ID	246332
Case ID	00311158
Description	When a user searches for unmanifested containers through the Sterling Application Console by selecting "Unmanifested containers only" in the container search by status view, the system does not return the list of unmanifested containers.
Defect ID	246347
Case ID	00310395
Description	When a user calls the createOrder, scheduleOrder, releaseOrder API, the input XML of the GetDeliveryLeadTimeUE user exit does not contain "SellerOrganizationCode".
Hot Fix ID	8.5-HF48
Defect ID	243334
Case ID	00283218
 Description	When a user performs the following sequence of actions, and calls the getPossibleSchedules API for the entire order, the system displays the ProdAvailDate value as blank for the second orderline:
1.	Configures the sourcing rules and defines procurement between nodes with some transit days.
2.	Associates the delivery service with the product.
3.	Schedules the order, the order goes to the ‘Procurement Purchase Order Created’ status.
4.	Creates a second order line with the same item as that of the first order line.
5.	Associates the order line with the same delivery service and consolidates the delivery service with the same work order.
Note: If an order consist a ship node and receiving node as the same organization is an invalid configuration. This might lead to exceptions during scheduling the order and the order might not be scheduled properly. Ensure that the ship node and the receiving node on the order are different.
Defect ID	245356
Case ID	00304001
 Description	In an agent when a message is put into the JMS queue, the system creates a new connection and session, and therefore, results in performance degradation.

Solution: The following properties have been added in the yfs.properties to resolve this issue:
•	agent.bulk.sender.enabled - The default value of this property is set to false. If a user set this property is set to true, the JMS messages are put in the internal JMS queue in batches. All the messages received from the 'getJobs' method are divided into batches and each batch is sent to the JMS Queue, using a single JMS connection or session. This improves the performance of the agent server.

Note – If a user enables the session pooling, the sessions will be reused among different batches. Otherwise, a new session will be created for each batch of the messages.

•	agent.bulk.sender.batch.size - The default value of this property is set to 1. This property will determine the batch size, the number of messages to be sent to the JMS queue using the same QueueSender object. The optimum value of the property may vary between different JMS vendors.

The requisite information has been included in the “yfs.properties” section of the Selling and Fulfillment Foundation: Properties Guide
Defect ID	245456
Case ID	00304742
Description	The tasks that are cancelled by the system do not have valid cancellation audits information.
Hot Fix ID	8.5-HF47
Defect ID	216368
Case ID	Internal
    Description	When the findInventory API is invoked with mergeNode in the input XML, the delivery date in the interaction element of the output XML does not get populated.
Defect ID	219787
Case ID	Internal
    Description	In the input XML of the OMPProcessRoutingExternallyUE user exit, the Unique Option Number is not populated.
Defect ID	219592
Case ID	Internal
    Description	When a user calls the findInventory API with multiple sourcing sequences and a small value of maximum records, the options element does not have solutions that can fulfill all the promise lines.
	Maximum records should be less than or equal to the number of solutions that cannot fulfill all the promise lines.
Defect ID	240727
Case ID	00260777
Description	A user should be able to invoke the routing logic externally. 

 Solution: A new user exit, OMPProcessRoutingExternallyUE, has been introduced to call the routing logic externally. The corresponding fixes have been made in the findInventory API and other promising or scheduling APIs to handle calls to the OMPProcessRoutingExternallyUE user exit.
Defect ID	241331
Case ID	00278809
    Description	The ON SUCCESS event XML of the scheduleOrder API must publish the SuggestedOption element.
Defect ID	244470
Case ID	00296433
    Description	The Real-Time Availability Monitor agent when run in a multi-threaded mode results in performance degradation.
Solution: A new JVM level caching has been introduced.
Hot Fix ID	8.5-HF46
Defect ID	235723
Case ID	Internal
    Description	When the quantity of an item in the shipment line is reduced, the system throws an ‘Invalid Item’ exception.
Defect ID	244809
Case ID	00298667
    Description	When the getWorkOrderList API is invoked, it locks the YFS_ORDER_HEADER table.
Defect ID	244986
Case ID	00299622
    Description	The DeleteUser process goes into an infinite loop resulting in the crash of the application server.
Defect ID	245023
Case ID	00297407
    Description	When a user configures the following services and calls the ShipmentHistoryPurge service in a verbose mode, the system throws an SQL exception.
•	OrderPurgeService
•	OrderHistoryPurgeService
•	ShipmentPurgeService
•	ShipmentHistoryPurgeService

Hot Fix ID	8.5-HF45
Defect ID	242920
Case ID	00282877
    Description	The Real-Time Availability Monitor agent when run at the enterprise level results in performance degradation.
Defect ID	242959
Case ID	00288375
    Description	When copying groups from the system group, some permissions are missing in the copied groups.
Solution: The code that copied the permissions, stored the permission hierarchy in a data structure in such a manner that some permissions were lost, if they shared the same CONFIG_SEQ_NO in the YFS_BASE_CONFIG_TASK table. The application has been enhanced to use a unique BASE_CONFIG_TASK_KEY attribute to copy the appropriate permissions.
Defect ID	243281
Case ID	Internal
 Description	When a user performs the following sequence of actions, the system displays an “ErrorDescription="Ship node cannot be determined based on the order lines and sourcing configuration" error message:
1.	Configures Distribution Group, DG1 with N1, N2, N3 in order of priority.
2.	Configures Distribution Group, DG2 with N4, N5, N6 in order of priority.
3.	Configures Sourcing Rule, Seq 1 that has DG1 of three nodes in hundred miles.  
4.	Configures Sourcing Rule, Seq 2 that has DG2 of three nodes in hundred miles.
5.	Optimizes the Date as the Optimization Type.
6.	Configures DS1 as Delivery Service.
7.	Ensures that the inventory is available on all the nodes of DG1 and DG2. 
Distance returned from the YFSGetDistanceForNodeListUE user exit is more than 100 miles for all the nodes of DG1 and less than 200 for DG2.
8.	Creates an order for ITEM1 and associates it with DS1. 
9.	Calls the generateWorkOrder API to create a workorder.
Defect ID	243447
Case ID	00290714
    Description	When payment processing is performed in an asynchronous mode and refunds are processed on a paid Sales Order, the system creates an additional CHARGE record in YFS_CHARGE_TRANSACTION table.
Solution:  A new ’ReducePendingAsyncronousAmounts’ flag has been added to the input xml of the recordExternalCharges API. The flag must be set as "Y" and valid requestAmount must be passed. 
For more information about the recordExternalCharges API, refer the Selling and Fulfillment Foundation: Javadocs.
Defect ID	244309
Case ID	00293341
    Description	When a user attempts to deploy the changes to a target database using the Configuration Deployment Tool, the system displays an error if there are some changes in the existing records of the YFS_PERSON_INFO table in a source database.

Defect ID	244350
Case ID	00289194
 Description	When a user performs the following sequence of actions, the changes does not get reflected:
1.	Creates a listener in the sales order pipeline that picks up Procurement Purchase Order created status and drops into both Procurement Purchase Order Created and Procurement Purchase Order Shipped.
2.	Changes in the expected delivery date of the shipment is reflected only on the procurement purchase order, but is not reflected on the sales order.
        Defect ID	244700
Case ID	00177010
    Description	The system only looks for the /template/prints/label/ folder instead of /global/template/prints/label/ folder, when a user extends the PrintDocumentSet API template for a specific print label and adds the extended template in the /global/template/prints/label/ folder.
Defect ID	244707
Case ID	00296166
    Description	The SQL injection vulnerabilities is observed in the Sterling Multi-Channel Fulfillment Solution, 8.5.
Hot Fix ID	8.5-HF44
        Defect ID	240750
Case ID	00275399
     Description	The system creates a user session (HttpSession which is holding UserData) for each of the Interop Http Servlet call (for api/flow execution) passing either token or userid/password in the following scenarios:
•	The default value of the yfs.interop.disable.session.creation.ontoken property is set to false. However, if the user set the value to true in the customer_overrides.properties user session will not be created if a token is passed to interop servlet for api or flow execution. 
•	When the yfs.interop.disable.session.creation.onpassword property is set to true in customer_overrides.properties, the user session is not created if the userid or password is passed to interop servlet for api or flow execution.
Defect ID	242776
Case ID	00271372
    Description	If some exceptions are present in the YFS_INBOX table that is associated with a queue, and if the queue is deleted, a NullPointerException is thrown while searching for the exceptions in the Exception console.
Solution: A validation check has been provided in the Application Manager. Therefore, when a user attempts to delete a queue that is associated with an exception in the YFS_INBOX table an error message is displayed.
Defect ID	243109
Case ID	00281594
 Description	When a user performs the following sequence of actions, the order is partially scheduled:
3.	Sets up a sourcing rule that picks the node from the distribution group.
The distribution group has two nodes, N1 and N2.
4.	Sets up a scheduling rule with ‘Line Ship From Single Node’ and ‘Optimizing on Date’ check boxes are selected.
5.	Creates an order for quantity 5.
6.	Runs the scheduleOrder API by passing maximum records as 5.
Out of quantity 5, quantity 3 is partially scheduled from N1 and quantity 2 is backordered.
Defect ID	243425
Case ID	00265629
 Description	When a user performs the following sequence of actions, the system must not call the getParcelSCACSummary API:
1.	Creates a user group and revokes the permission for inner panel ‘YDMD601I02’ (Carrier Summary).
2.	Creates a user and assigns the user group created in step 1.
3.	Logs in to the application as a new user created in step 2.
4.	Navigates to the Manifest Console.
5.	Clicks “Search” and confirms that the ‘YDMD601I02’(Carrier Summary) inner panel is not displayed. 
        Defect ID	244438
Case ID	Internal
     Description	If the Selling and Fulfillment Foundation 8.5 is installed in multi-schema environment and the installation is on HF32 or below, if a user attempts to install a HF between HF33 and HF43, then the hot fix installation fails during data migration.
Solution: This issue has been resolved in the Selling and Fulfillment Foundation 8.5-HF44. A user can bypass this issue by installing HF44 or above.
Hot Fix ID	8.5-HF43
Defect ID	234909, 242530
Case ID	00229451
    Description	The application must be enhanced to enable a user to specify the distance criteria while defining a Distribution Group for the delivery service items.
Solution: The requisite information has been included in the “Defining Distribution Groups for Delivery Service Items” section of the Sterling Distributed Order Management Configuration Guide.

Defect ID	236652
Case ID	00245411
Description	When a user configures the Standard FXRS Integration and implements the YCSShipCartonUserExit to blank out the ‘PickupDate’ attribute, the system defaults it to current date instead of passing the blank value to the integration server.

Solution: A new attribute, ‘RetainBlankPickupDate’ has been exposed in the YCSShipCartonUserExit. When a user sets the value of the ‘RetainBlankPickupDate’ attribute to ‘Y’ and 'PickupDate' to 'BLANK', system will not default the attribute to the current date. Currently, this is supported only for Fedex Adaptor.
Defect ID	242136
Case ID	00282678
 Description	When a user performs the following sequence of actions, the Release agent does not honor the node notification time configuration:
1.	Sets up 'Release an order to this node 2 system days before expected time of shipment' for node N1.
2.	Sets up procurement rule for N1.
3.	Creates a listener on the sales order (SO) pipeline that listens to the ‘Receipt Closed' status of the Purchase Order (PO) pipeline and moves the SO line from the created PO status to the shipped PO status.
4.	Associate a delivery service with the item.
5.	Runs the ReleaseOrder API.
Defect ID	242348
Case ID	00284516
 Description	When a user performs the following sequence of actions, all the orderlines gets backordered:
1.	Adjusts inventory for an item and reserves the same by calling the reserveItemInventory API.
2.	Creates an order and consumes the reserved inventory through the OrderLineReservations attribute of the changeorder API.
3.	Implements the YFSGetAvailabilityCorrectionsForItemListUE user exit.
4.	Calls the scheduleOrder API.
Defect ID	242569
Case ID	00284151
Description	Although a user creates a return order without the Line Type, in application console, the return order line displays the Line Type.
Defect ID	243318
Case ID	00278916
Description	When a user enables the ON_SUCESS event of the changeOrder transaction, which invokes the recordCollection and getOrderDetails API’s in the same transaction boundary, the updated fields of the yfs_charge transaction is not displayed in output.
Defect ID	243414
Case ID	00240328
 Description	When a user performs the following sequence of actions, the system displays an incorrect date in the received location:
1.	Configures a buyer, seller, and receiving node (node1).
2.	Creates user1 for node1. 
The user must belong to Netherland locale.
3.	Logs in as user1.
4.	Creates an inbound shipment with a time-sensitive item.
5.	Confirms the shipment and ships the shipment.
6.	Logs in to the Sterling Mobile application.
7.	Navigates to Receive > Purchase Order. In the “Order Detail” screen enters the shipment number and ship by date as "01 06 2011".
In the received location the date is displayed as 31 05 2011 instead of 01 06 2011. Due to this the date in the putaway location is also displayed as 31 05 2011.

Defect ID	244142
Case ID	Internal
Description	The Sterling Distributed Order Management Configuration Guide must be updated with information about the sourcing template enhancement.
Solution: The requisite information has been included in the “Defining Sourcing Template Details” section of the Sterling Distributed Order Management Configuration Guide.

Hot Fix ID	8.5-HF42
Defect ID	241008
Case ID	00274406
 Description	When a user performs the following sequence of actions for processing an order, the Schedule Order agent runs into an infinite loop:
1.	Selects the "Allow Reservation during scheduling" check box in the Scheduling rules.
2.	Creates an order with a delivery service associated to the item.
3.	Creates a workorder.
4.	Takes an appointment forcefully by selecting the "Ignore product availability" option under Overrides.
5.	Runs the Schedule Order agent.
The record is deleted and again inserted, instead of getting updated. Due to this, the Schedule Order agent runs into an infinite loop.
Defect ID	241916
Case ID	00278919
 Description	When a user performs the following sequence of actions, the system throws a NullPointerException:
1.	Enables the ON_RELEASE_CREATION_OR_CHANGE event of RELEASE.0001 transaction. 
2.	Defines a service within the event.
The service calls the changeRelease API. 
3.	Enables the ON_SUCCESS event. 
4.	Extends the event xml to include the entire xml as given in the Selling and Fulfillment Foundation: Javadocs.
5.	Creates an order.
6.	 Schedules the order and releases it.
Defect ID	242223
Case ID	00283112
 Description	When a user performs the following sequence of actions, the system creates an additional CHARGE record in the YFS_CHARGE_TRANSACTION table:
1.	Creates a sales order
2.	Schedules the order and releases it.
3.	Creates a shipment.
4.	Creates a shipment invoice and collects the payment through an asynchronous payment method.
5.	Creates a return order for the same sales order.
6.	Refunds the sales order after creating invoice through an asynchronous payment method by invoking the recordExternalCharges API.
Defect ID	242303
Case ID	00280755
Description	For the existing YFS_TRANSACTION_LOCK records with PURPOSE column having data with trailing white spaces, on invoking the addContainerToManifest API, the system throws a "java.lang.reflect.InvocationTargetException" error and fails to restore the Transaction Lock.
Hot Fix ID	8.5-HF41
Defect ID	240626
Case ID	00269937
Description	The application performs incorrect partial procurement when an order is scheduled and if appointment is present on the delivery order.
Defect ID	241411
Case ID	00279450
Description	The application displays a Null Point Exception when ConfirmAssignmentUE user exit is implemented, and the order is created and scheduled with multiple pack items, in a single transaction boundary.
Hot Fix ID	8.5-HF40
Defect ID	235720
Case ID	Internal
Description	The Selling and Fulfillment Foundation: Localization Guide must be updated to indicate that the application supports search by localized value.
Solution: The requisite information has been provided in the Selling and Fulfillment Foundation: Localization Guide.
Defect ID	239378
Case ID	00265676
  Description	An incorrect authorization and charge records are created by the requestCollection agent when payment is handled asynchronously.
Defect ID	240251
Case ID	00270413
Description	The queryTimeOut parameter passed as an API input is ignored by the internal logic, if the query being executed has a "for update" clause in it.

Solution: The logic has been enhanced to look for another parameter "TimeoutLockedUpdates". A value of "Y" or "True" irrespective of case for TimeoutLockedUpdates will now force the logic to use the queryTimeOut for queries with "For update" clause. 

The "TimeoutLockedUpdates" is read from the context using the specified methods.
Defect ID	240571
Case ID	00272843
Description	When a user performs the following sequence of actions, the alert raised by the Real-Time Availability Monitor agent has FutureAvailableQuantity=ZERO for the bundle parent:
1.	Creates a bundle item with components.
2.	Configures an ATP monitor rule for an activity.
3.	Adjusts the onhand and future inventory, such that an inventory activity is created.
4.	Invokes the Real-Time Availability Monitor agent.

Defect ID	240670
Case ID	00271397	
Description	When a user calls the changeRelease API for an order, by passing the OrderNo, DocumentType, EnterpriseCode, and SelectMethod="WAIT" in the input xml, the changeRelease API does not honor the SelectMethod="WAIT. It locks the YFS_ORDER_HEADER table with NOWAIT.
Defect ID	240988
Case ID	00276631
Description	When the getRourcePoolCapacity API is invoked, the AllocatedConsumption attribute is not populated for the parent slot in the “Detailed Capacity” console.
Defect ID	241136
Case ID	Internal
Description	In the Selling and Fulfillment Foundation: Javadocs the ShipNode element is missing in the output templates of the changeOrder API.
Defect ID	241137
Case ID	Internal
Description	In the Selling and Fulfillment Foundation: Javadocs the AttributeReference element is missing in the output templates of the getitemlist and getcompleteitemlist APIs.
Defect ID	241419
Case ID	Internal
Description	The Selling and Fulfillment Foundation: Installation Guide must be updated with the supported version of Oracle Database.
Solution: The requisite information has been provided in the Selling and Fulfillment Foundation: Installation Guide.
Hot Fix ID	8.5-HF39
Defect ID	236479
Case ID	00248356
Description	The Sterling Mobile application logs out, when a user encounters a dynamically loaded menu or screen during execution.
Defect ID	236578
Case ID	Internal
Description	The application must be enhanced so that the client applications can implement PA-DSS as per the standards.
Defect ID	238932
Case ID	00266077	
Description	The addContainerToManifest API currently acquires the Transaction Lock with SCAC and ShipNode. Due to this the system performance is slow during peak seasons.

Solution: The Transaction Lock is now acquired with Shipper Acc No, SCAC, and ShipNode.  
Defect ID	239601
Case ID	00259332	
Description	When multiple orders with corresponding work orders are consolidated in a single shipment, if  the ChangeShipment API is invoked it throws an "Either Work Order Key or Work Order Appointment Key incorrect" exception, as the work order key and the work order appointment key is stamped on the shipment header

Solution: The work order key and the work order appointment key will get stamped on the shipment header if there is a single order is in a shipment. When multiple orders with corresponding work orders are consolidated in a single shipment, the value of the work order key and the work order appointment key will be null in the YFS_SHIPMENT table.

Defect ID	239621
Case ID	00269901
Description	When a user performs the following sequence of actions, the newly split line does not copy the unit price from the original line. Instead, it gets the value from the price program:
1.	Navigates to DOM > Document specific  > Sales Order > Fulfillment > Fulfillment Rules.
2.	Checks for "A line can be fulfilled from a single Node only" flag and "For a line with firm pre-defined shipnode” flag. 
If the line is partially backordered or unscheduled, splits it into two separate lines so that a different ship node can be selected for the new line.
3.	Checks the Default Split line template. 
4.	Ensures that the UnitPrice attribute in the LinePriceInfo attribute is enabled.
5.	Configures the price program and price lists for an item.
6.	Adjusts inventory so that Node1 (N1) has 2 quantities of the item.
7.	Creates an order for 4 quantities. 
8.	Adds list price and unit price to an order line.
9.	Schedules the order, which splits the order line into two for the back ordered quantity.

Solution: The "IsPriceLocked" flag has been introduced in the "Default Split line template". Both "UnitPrice" and "IsPriceLocked" must be enabled in the "Default Split line template" for the system to retain the unit price of the original line on the split line.

Note:
If the "IsPriceLocked" flag is set to ‘N’ or blank, even if the "IsPriceLocked" is enabled in the template, the system will get the value for unit price on the split line from the price program.

Defect ID	240058
Case ID	00272111
Description	When a user performs the following sequence of actions, the system throws a "record already exists in the database" error message:
1.	Launches the Applications Manager.
2.	Navigates to the Applications > Platform > Process Modeling > Load > Load Execution > Transactions > Purge Load History > Time Triggered > LOADHISTPRG details.
3.	Modifies the runtime properties.
4.	Saves the changes.
The user is not able to save the changes made to the runtime properties for LOADHISTPRG agent criteria, as it points to the wrong flow key ‘LOADPRG’.

Hot Fix ID	8.5-HF38
Defect ID	239101
Case ID	00265296
Description	A user is not able to reset the item service association skill using the manageItem API.

Defect ID	239277
Case ID	00268078
Description	When a user performs the following sequence of actions, the system throws an exception and stalls the payment:
1.	Creates a payment hold to prevent the payment collection.
2.	Creates an order and confirms it.
3.	Runs the requestCollection agent.
The requestCollection agent picks up an order that is on HOLD.
Hot Fix ID	8.5-HF37
Defect ID	235412
Case ID	00099006
Description	In the Shipping Preferences, the ‘Overship Percentage’ field must allow a user to enter value more than 999%.

Solution: The DataType for the "Overship Percentage" field has been changed such that the user can enter a value more than 999%. 
Defect ID	237789
Case ID	00227801
Description	The AwaitingDeliveryRequest and HasDeliveryLines attributes must be exposed at the OrderLine level of the getOrderLineList API output.
Defect ID	237946
Case ID	00256433
Description	If a user creates more than 75 enterprises in Participant Modeling and tries to select an enterprise to onboard at a node, the ‘Select the Enterprise’ drop-down list does not display all the  enterprises.
Defect ID	238146
Case ID	00261036
Description	When a user invokes the restoreOrder  API, it throws an “ANSWER_SET_KEY is an Invalid Column” exception.
Defect ID	238187
Case ID	00255284
Description	When a user performs the following sequence of actions, the bundle relationship is lost when relationship type is attached with a bundle component:
1.	Creates a bundle parent and adds the bundle component, for example, TV and DVD.
2.	Creates an item, for example TVWarranty, which has the relationship type as ‘WARRANTY’.
3.	Calls the creteOrder API to create an order that has the bundle component TV with relationship type as ‘WARRANTY’ and item as TVWarranty.
The bundle relationship of the TV and the bundle parent item is lost when the relationship type is attached to the TVWarranty item.
Defect ID	238560
Case ID	00263727
Description	When a user performs the following sequence of actions, the system throws a “WMS00056: There is no inventory for put away at the Source Location" error message:
1.	Creates a Purchase Order for an item
2.	Logs in to the Sterling Mobile application.
3.	Selects receipt and putaway.
4.	Scans the order and clicks “Enter”.
5.	Scans the equipment and clicks “Enter”.
6.	Scans the item ID and tabs out.
7.	In the “Quantity” screen, scans the quantity and tabs out. The Disposition Code field is left blank and clicks “Enter”.
Hot Fix ID	8.5-HF36
Defect ID	203172
Case ID	Internal
Description	The name of a sub-service is configured in a service in the Sterling Configurator with more than 40 characters such that the service registers an exception.
If the exception occurs during the execution of the service, the application goes into an infinite loop, and registers SQL exceptions continuously when trying to insert a record into the YFS_INBOX table.
Defect ID	204585
Case ID	Internal
Description	The Statistics Purge agent does not completely purge all the eligible records in the YFS_STATISTICS_DETAIL table.
Defect ID	225504
Case ID	Internal
Description	The ItemAttributeGroupTypeList and PrimaryInformation elements must be exposed under the ChildItem element in the getItemList API output.
The ShipnodePersonInfo element must to be exposed under ShipNode in the getUserHierarchy API output.
Defect ID	235728
Case ID	Internal
Description	When creating a chained order synchronously against future supply, the inventory item on the procurement order is the original selling item and not the actual inventory item.
Defect ID	235730
Case ID	Internal
Description	When creating a chained order synchronously, if a user uses the actual inventory item on a purchase order, the system throws an ‘Invalid Node’ error.
Defect ID	235740
Case ID	Internal
Description	When a user calls the createChainedOrder API for a selling item to create chained order, the chained order is not created with the correct order lines.
Defect ID	237405
Case ID	00249184
Description	When a user triggers the Real Time Inventory Monitor agent and publishes the alerts, the alert xml for the bundle parent is published along with the component, but the OnhandAvailableQuantity is displayed as ZERO.

Defect ID	237667
Case ID	00257577
Description	When a user performs the following sequence of actions, the system throws an error while cancelling the order:
1.	Configures procurement rules for an order with fulfillment method as delivery.
2.	Creates an order with fulfillment method as 'Delivery'. 
3.	Sets an appointment.
4.	Schedules the order.
5.	Cancels the order.
Defect ID	237731
Case ID	00258677
Description	The Real Time Inventory Monitor agent runs slowly.
Defect ID	237774
Case ID	00258689
Description	When a user creates an order with multiple OrderLines containing the same Item ID and ShipNode, the number of scheduled quantities is incorrect.

Hot Fix ID	8.5-HF35
Defect ID	199387
Case ID	Internal
Description	A user should be able to prioritize the tasks.
	
Solution: The getNextTask API has been enhanced to take ‘TaskPriority’ as the input   and return tasks as per the priority.
Defect ID	203175
Case ID	Internal
Description	When the moveLocationInventory API is called in multi-threaded mode, it successfully passes for the first time, but fails the second time with an error "ORA-0, Could not find entity”.
Defect ID	204582
Case ID	Internal
Description	When a user performs the following sequence of actions, the application displays an "Operation cannot be processed in current status" error message if the Allocate Task agent does not start and clear the draft tasks:
1.	Configures delayed allocation for a node in the wave release schedule.
2.	Ensures that a task for the node configured in step 1 exists in a draft location having a regular location as its target location.
3.	Logs in to the RF device and performs an ad_hoc move for an item from one location to another location.
If the Allocate Task agent is not running, the application waits for the Allocate Task agent to start and clear the draft tasks for the configured time.
Solution: A new "yfs.override.pendingallocations.for.adhocmoves" property has been provided. If the value of this property is set to “Y” and if the user performs an adhoc move, the 0020 application will not wait for the Allocate Task agent to start and clear the draft tasks. Instead, the application will allow the user to complete the adhoc move.

The requisite information has been updated in the Chapter, " Property Files Reference” of the Selling and Fulfillment Foundation: Properties Guide.

Defect ID	219813
Case ID	Internal
Description	The registerTaskCompletion API does not consider the AssignedToUserId passed in the input while fetching records from the YFS_USER_AISLE table.
Defect ID	231478
Case ID	00221040
Description	When the multi-stop functionality and caching is enabled, if a user calls the findInventory API to determine the shortest path between the ship node and the receiving node, it throws a null pointer exception.
Defect ID	238042
Case ID	00219425
Description	The Sterling Multi-Channel Fulfillment Solution Installation Guide must be updated with information about SUSE Linux 11 support for RCP Client.
Solution: The requisite has been provided in the Sterling Multi-Channel Fulfillment Solution Installation Guide.
Hot Fix ID	8.5-HF34
Defect ID	199377
Case ID	Internal
Description	The changeShipmentContainer API must populate the ReasonCode and the ReasonText information in yfs_audit_header when this API is invoked to modify the shipment line quantity by modifying the container details quantity.

Solution: The ReasonCode and ReasonText information must be passed in the <Container> element of the API input for populating the values in the YFS_AUDIT_HEADER table.
Defect ID	199396
Case ID	Internal
Description	When a user performs the following sequence of actions, the application does not stamp the correct quantity on the task:
1.	Configures a Pick Exception code with the "Suggest Alternate Location" option and replenishment strategy with splitting is not allowed.
2.	Adjusts inventory for an item in an LPN, for example, C1, in a location.
3.	Creates a shipment, adds the shipment to a wave, and releases the wave such that a task is created from the location mentioned in step 2 with the suggested LPN as C1.
4.	Adjusts inventory in another LPN, for example, C2, in another location, with a different quantity.
5.	Logs in to the Sterling Mobile application and enters the pick exception configured in step 1.
The application suggests another location to pick inventory through the Suggest Alternate Location mechanism. The new task is created from another location with the suggested LPN (C2) information, but the quantity remains the same as that of the LPN (C1).
Defect ID	199401
Case ID	Internal
Description	When a system-defined containerization is configured, serial-tracked, and serialized the items are packed, the application does not validate the value of the serialized items scanned in the “Serial” pop-up window.

Defect ID	199411
Case ID	Internal
Description	When a user performs the following sequence of actions, the application does not stamp the suggested LPN information on the task:
1.	Adjusts inventory for an item in an LPN, for example, C1, in a location.
2.	Creates a shipment, adds the shipment to a wave, and releases the wave such that a task is created from the location mentioned in step 1, with the suggested LPN as C1.
3.	Deletes C1 and adjusts inventory in another LPN, for example, C2, in another location, with a different quantity.
4.	Logs in to the Sterling Mobile application to complete the task started in step 3.
The application suggests another location to pick inventory through the Suggest Alternate Location mechanism. The new task will be created from another location without the suggested LPN (C2).
Defect ID	234305
Case ID	00222298
Description	In the “Status Inventory Type Details” pop-up window,  while adding a Status Inventory Type for Transfer Orders, the ‘Status’ drop-down list displays a limit of 75 items.

Solution: A look-up option has been added to search and add statuses, if there are more than 75 statuses. Otherwise a usual drop-down will be displayed.
Defect ID	235192
Case ID	00239558
Description	When a user selects the "Save as" option in the ‘Resource Pool List”screen to create a new resource pool from the existing one, the additional capacity limits for a resource is not getting copied.
Defect ID	235473
Case ID	00244861
Description	When a user creates a HangOff table that has history, creates a synchronous service to insert a record into the table and calls the getOrderList API to get data for the HangOff table with ReadFromHistory="B", the system throws an error.
Defect ID	235629
Case ID	00170780
Description	When a user performs the following sequence of actions, the system throws an “YFS10048 YFS: Invalid Node” error:
1.	Ensures that a service item is associated with a product item.
2.	Creates an order for an item.
3.	Associates the item with a delivery service item.
4.	Ensures that the ShipNode is not passed at the order or order line level.
5.	Invokes multiAPI in which the generateWorkOrderAPI is the first API and the changeOrder API is the second API, such that the changeOrder API passes a valid value for procureFromNode and shipNode at the order line level. 

Defect ID	225725
Case ID	00186851
Description	When the BeforeCreateShipmentUE user exit is implemented, some of the output xml attributes are lost.
Defect ID	235925
Case ID	00247998
Description	When a user performs the following sequence of actions, a user is not able to resize the “Region” column in “Resource Pool Details” screen:
1.	Navigates to the Global Inventory Visibility > Resource Capacity > Resource Pool.
2.	In the “Resource Pool Details” screen, selects any resource pool.
3.	Clicks the “Regions” tab.
4.	Selects the “Service specific regions” option.

Defect ID	236701
Case ID	00238007
 Description	The Modification Rule does not exist for the 'Change Appointment' modification for a return order that is in the "Released’ status. When a user logs in to the Sterling Call Center and Sterling Store application and  navigates to the ‘Service Fulfillment Summary’ screen, the 'Change Appointment' modification is always ‘DISABLED’ for order line that is ‘Released’ status and above.
Solution: The Modification Rule for the "Change Appointment" modification for a return order has been extended to 'Released' and 'Included in Shipment' status.

Defect ID	237051
Case ID	00253987
Description	When a user performs the following sequence of actions, the shipment is removed from the wave and the ‘Wave Number’ is displayed as blank in the “Shipment Details” screen:
1.	Adjusts the inventory in two locations, L1 and L2 having 4 quantities each.
2.	Creates 3 shipments, S1, S2, and S3 for the inventory with 2 quantities each.
Before  picking the shipment S1, changes the inventory status at L1 to CH (count held) and making it unavailable. If the user picks the first task, the system cancels the current task, and creates a new task for location L2. 
While picking the first task, enters the first shipment number as the task reference in the “Task List” console.
Hot Fix ID	8.5-HF33
Defect ID	203178
Case ID	Internal
Description	When a user creates more than 100 LPNs ,adjusts loose SKUs in more than 200 locations, and invokes the getNodeInventory for the whole node, the application registers a java.lang.IllegalArgumentException error message.
Defect ID	203184
Case ID	Internal
Description	When a shipment that has containers associated to multiple shipment lines of the same item is split by moving a container to another shipment, the application fails when packing the container.
Defect ID	228935
Case ID	Internal
 Description	During any Hot Fix installation, the factory setup installation does not honor the LOAD_FACTORY_SETUP property in sandbox.cfg.
Solution: If the LOAD_FACTORY_SETUP property in sandbox.cfg is set to ‘False’,                       then the factory setup will not be installed during the Hot Fix installation.
Defect ID	229502, 236129
Case ID	00147712
 Description	The history of all the inventory transactions, which includes inventory updates to supply types that are both ONHAND and non-ONHAND (such as, Pending Sellable, On Order, Intransit and so on) between the WMS/Vendors and OMS must be available.
It can be achieved by the Sterling Inventory Audits, which provides inventory Audits only for Supply Types that is ONHAND type.

	Solution: The adjustInventory API is called internally by the inventory APIs whenever a change in supply is requested. For the inventory updates, the adjustInventory API is enhanced to log audit if 'Is Audit Enabled' flag is set to 'Y' for the Supply Types. 
To support the backward compatibility, the out-of-box Onhand Supply Types has 'isAuditEnabled' flag  checked.
In addition to this behavior, if the 'Enable Audit' check box is selected for the SupplyType, and if the INVENTORY_CHANGE.INVENTORY_CHANGE event is enabled, the event or alert will also be raised for the SupplyType.

Note: The requisite information has been updated in the Chapter, "'Configuring Inventory Types and Considerations” of the Sterling Global Inventory Visibility: Configuration Guide.
Defect ID	234448
Case ID	00149682
 Description	The getOrderPrice and getItemPrice APIs must be enhanced to provide a PricelistName attribute.

	Solution: A new PricelistHeader xml element has been added to the SelectedPricelistLine element of the getOrderPrice and getItemPrice APIs. 
For more information about the getOrderPrice and getItemPrice APIs, refer the Selling and Fulfillment Foundation:Javadocs.

Defect ID	235716
Case ID	00246860
Description	When a user performs the following sequence of actions, the system locks the transaction twice:
1.	Creates a shipment.
2.	Create two containers for a shipment.
3.	Packs the container.
4.	Adds the first container to a manifest. The system will open a new manifest and locks the transaction. 
5.	Adds the second container to the manifest and the system again locks the transaction.

Solution: The system will lock the transaction if a new manifest is opened.

Defect ID	235744
Case ID	00246810
 Description	The CreateException API fails for a Reprocessible Service when the exception references value contains a ":" character.
Hot Fix ID	8.5-HF32
Defect ID	224513
Case ID	Internal
 Description	When the ON_STATUS_CHANGE event of the Change Order Status transaction gets raised and the custom class calls the getOrderDetails API from a service running on the Integration Server, the ON_STATUS_CHANGE event returns the order status as 'Partial_Status' even if the order is in ‘Extended Released’ status.

Defect ID	228818
Case ID	Internal
Description	When shutdown is issued on a running agent (or a service involving JMS), if one or more consumer threads are stuck indefinitely or for a long time, the shutdown thread that will wait for the consumer thread to finish, is not able to complete the shutdown task.
Solution: A new "yantra.shutdown.wait.timeout"  property has been exposed. Users can specify the maximum time that the shutdown thread should wait for the consumer to finish the current task, in the event of a shutdown. The time-out indicates the time that the shutdown thread will wait for the consumer thread to complete the transaction, before proceeding with the shutdown. 
If the consumer thread does not finish before the specified time (elapsed time since shutdown/CTRL+C), the shutdown thread will proceed further with the shutdown issuing a rollback on the session/message.
The default value for this property is 0, which maps to an indefinite wait.
Defect ID	233151
Case ID	00236357
Description	When the getIntegraionErrorList API is called through the getPage API with pagination strategy as NEXTPAGE, the results are not obtained. 
Solution: The getIntegraionErrorList' API has been enhanced to support the NEXTPAGE pagination strategy through the getPage API.
Defect ID	234452
Case ID	00239967
Description	The system does not honor the User Interface timeout configured in the yfs.yfs.ui.queryTimeout property.

Defect ID	234667
Case ID	00241050
Description	When a user calls the getNodeInventory API having PendInQty and PendOutQty as an input, a select query with distinct clause is fired on the YFS_NODEINVENTORYDTL_VW, because of which the YFS_NODEINVENTORYDTL_VW runs for a long duration that causes performance issues.
Solution: A new select distinct query is fired on the YFS_NOPNDMV_NODEINVDTL_VW.

Defect ID	235185
Case ID	00243117
 Description	The Real Time Availability Monitor raises duplicate events when run in a multithreaded mode with more than 10 threads.
Defect ID	235255
Case ID	00244855
 Description	When a user creates a shipment and packs it, at the time of packing it  the addToContainer API is called due to which the system performance is slow when the query is fired on the YFS_SHIPMENT_Container table while calling the addToContainer API.
Defect ID	235478
Case ID	00245294
Description	The getItemListForOrdering API must be enhanced to be able to search an item in multiple languages.
Solution: The getItemListForOrdering API has been enhanced to read ItemLocaleList element in the input. A user will be able to pass localized values in the input of the getItemListForOrdering API to search for an item. 
For more information about the getItemListForOrdering API, refer the Selling and Fulfillment Foundation: Javadocs.
Defect ID	235548
Case ID	00246683
Description	The system does not honor node configuration while retrieving the task type from the getNextDepositLocation API.
.
Defect ID	235785
Case ID	00247374
Description	During wave release, the application allocates more inventory than what is available in a location, if a shipment in a wave has a shipment line with the “CountryOfOrigin” attribute.
Hot Fix ID	8.5-HF31
Defect ID	205203
Case ID	Internal
   Description	When a user performs the following sequence of actions, the entire order quantity is moved to the “Reserved” status, even though the available inventory is lesser than the requested quantity:
1.	Configures the Scheduling Rules. 
2.	In the “Scheduling Rules” screen, selects the “Ship Line Complete” flag and the “Allow Reservation During Scheduling Rules” flag.
3.	Implements the YFSGetAvailabilityCorrectionsUE user exit.
4.	Creates an order with 10 quantities of an item. However, the on-hand inventory is only five quantities.
5.	Schedules the order.
While five quantities are moved to the “Reserved” status, the remaining five quantities are moved to the “Backordered” status. 
6.	Again schedules the order.
Defect ID	227317
Case ID	00204741
Description	The getInventoryAudit API must support the NEXTPAGE pagination strategy.
Solution: The getPage API fetches the paginated Inventory Audit records with the NEXTPAGE pagination strategy. 
For more information about the getPage API, refer the Selling and Fulfillment Foundation: Javadocs.
Defect ID	224513
Case ID	Internal
 Description	When the ON_STATUS_CHANGE event of the Change Order Status transaction is raised and the custom class calls the getOrderDetails API from a service that is running on the Integration Server, the ON_STATUS_CHANGE event returns the order status as 'Partial_Status', even if the order is in the ‘Extended Released’ status.
Defect ID	232220
Case ID	Internal
 Description	An incorrect Transfer Order is created when the USE_INVENTORY_ITEM_CHAINED_ORDER_CREATE rule is set to ‘Y’ for a Transfer Order. Also, if there are multiple OrderLineSchedules for an OrderLine an incorrect Transfer Order is created.
Defect ID	232304, 232306
Case ID	Internal
 Description	The hang offs record including the Order Line Schedules, are incorrectly copied from the Sales Order Line to Chained Order Line when splitting across multiple inventory items. Due to this, an exception is thrown in some scenarios.
Defect ID	232602
Case ID	00228810
   Description	When a user performs the following steps, the “manage Pricing Rule” screen throws an 'Record already exists in the database" error:
1.	Launches the Sterling Business Center.
2.	Navigates to the Pricing > New Pricing Rule
3.	Creates a pricing rule of type "Item Quantiy'.
4.	Configures a rule to have 3 or more attributes and saves it.
5.	Again saves the rule by updating the customer assignments as "applicable for all customers". 
6.	Attempts to activate the rule.

Defect ID	232650 
Case ID	00225488
 Description	The generateWorkOrder API throws an invalid customer errror in the following conditions:
•	When a ship node user logs in to another ship node and navigates to the ‘Change Fulfillment Options” screen, and clicks “Next” during the order entry flow while creating an order. 
•	When a team is not defined at the node level, but defined at the hub level and the node users have been assigned to a team which has access to all nodes.

Defect ID	233932
Case ID	Internal
 Description	When a user calls the createShipment API using the Read Availability Across Items Sharing the Same Attribute feature, the actual inventory is placed on the shipment. However, the inventory gets updated for the original ordered item.
Defect ID	234534
Case ID	Internal
Description	In a paginated console screen, by default the sorting is of “Server Side Sorting” type. A user must be provided with the capability to sort data in the screen.
Solution: To switch to the client-side sorting (local sort on the displayed page), change the “sc-ui-pagination-sorting-type” parameter to “client” in the web.xml file.
Note: All sorting performed on this screen will be lost if the user navigates away from this screen.

Defect ID	234620, 207414
Case ID	00239790
   Description	The ScheduleOrder API creates a Procurement Transfer Order instead of a Procurement Purchase Order when the YFSGetAvailabilityCorrectionsUE user exit is implemented.

Defect ID	234717
Case ID	00239373
 Description	The ScheduleOrder API does not work as expected in the following conditions:
•	When there is a segmented inventory.
•	When an orderline contains items that belong to the segmented inventory.
•	When the YFSGetAvailabilityCorrectionsForItemListUE user exit is implemented.
Defect ID	234997, 233951, 233825
Case ID	00240055, 00236031, 00235457
 Description	The executeCollection API does not honor the time stamp of the collection date because of which it picks up the charge transactions with a future collection date.
Defect ID	235162
Case ID	00236085
 Description	A store user is not able to view the expected on date on the “Order Summary” screen for appointments taken from a different store.

Hot Fix ID	8.5-HF30
Defect ID	232232
Case ID	00229573
Description	The system broadcasts cache refresh for the YFS_Item table and YFS_PriceList_Line table even when the cache is disabled, resulting in performance issues.
Defect ID	232926
Case ID	00198004
Description	When a user performs the following steps, an exception - "Delete failed. The record to be deleted could either not be found or it was already deleted or updated by another transaction" is displayed:
1.	Configures a price list in which the price of the item is configured as $10.
2.	Configures the "Item quantity price rule". For example, if you buy 2 or more items you get a discount of $2.
3.	Configures an order line level hold to be applied on Change Price.
4.	Calls the createOrder API with a single order line for the item quantity greater than or equal to 2.
5.	Calls the changeOrder API to remove the order line.
Defect ID	232307
Case ID	Internal
Description	Some elements and notes related to the Read Availability Across Items Sharing the Same Attribute feature are not documented in the Selling and Fulfillment Foundation: Javadocs.
Defect ID	233051
Case ID	00235554
Description	The system throws an "ORA-01438: value larger than specified precision allowed for this column" database error when YFS_INBOX consolidation_count reaches 99999 (maximum limit of CONSOLIDATION_COUNT column in the YFS_INBOX table).
Solution: If the consolidation count reaches the maximum limit of 99999, a new record is created in the YFS_INBOX table.
Defect ID	233156
Case ID	00230269
Description	Order statuses are not displaying localized values when the -Dlocalecode argument is used to switch to another locale other than the current locale of the user.
Solution: When the -Dlocalecode vm argument is specified in the com.ini file, the locale is switched to the locale specified in the argument. All database localized strings appear in the locale specified in the vm argument and not the locale of the user.
Defect ID	233224
Case ID	00221520
Description	In Unix-based systems, when the DbVerify command is run with multiple database hosts in the JDBC URL, an error is displayed.
Hot Fix ID	8.5-HF29
Defect ID	228957
Case ID	00208500
Description	The getFulfillmentOptionsForLines API does not consider the ProcurementFromNode value stamped on an order line when calculating the availability for inventory.
Defect ID	229501
Case ID	00198385
Description	The syncLoadedInventory API is enhanced to support passing the list of "supply types" that are to be synchronized, such as PO, PO_PLACED, INTRANSIT, and so on.
Solution: The input to the syncLoadedInventory API has an additional SupplyTypes element with a list of SupplyTypes. If SupplyTypes is passed, the syncLoadedInventory API considers only these SupplyTypes for syncing. Otherwise backward compatibility is retained.
Defect ID	231674
Case ID	00220483
Description	When a user performs the following steps, item-based allocation leaves a zero quantity record in the yfs_inventory_reservation table. Due to this, the records do not get deleted from the table:
1.	Adjusts inventory for an item as PO_PLACED for 25th October.
2.	Reserves available inventory for the item. For example, 1 unit.
3.	Adjusts inventory for an item as PO_PLACED for 20th October.
4.	Triggers and runs the item-based allocation. Item-based allocation updates the reservation with the new product availability date.
5.	Runs cancelReservation API for that quantity.
Defect ID	231884
Case ID	00201119
Description	The getInventorySnapShot API must support batching of the output.
Solution: The getInventorySnapShot API is enhanced to support two new attributes ‘LastInventoryItemKey’ and ‘MaximumNumberOfItems’.
When passed in the input along with shipNode, the API fetches records ahead of the passed ‘LastInventoryItemKey’ attribute with the number of records restricted to ‘MaximumNumberOfItems’ attribute value passed in the input.
Note: The attributes are honored only if ShipNode is passed in the input.
Defect ID	232220
Case ID	Internal
Description	Incorrect Transfer order gets created when the USE_INVENTORY_ITEM_CHAINED_ORDER_CREATE rule is set to Y for a Transfer order and multiple OrderLineSchedules that exists for an OrderLine,
Defect ID	232221
Case ID	Internal
Description	The word “When” is spelt incorrectly as “Whe” for the rule USE_INVENTORY_ITEM_CHAINED_ORDER_CREATE in the following label location: Supply Collaboration >Document Specific > Purchase Order > Fulfillment > Transaction Rules > Synchronize Items panel.
Defect ID	232233
Case ID	00229135
Description	In the Applications Manager, if a synchronous JMS service is created and the name of the response/request queue is given in parameterized form instead of an absolution JNDI name, the synchronous JMS service throws an error.
Solution: The response/request queue name can be provided as a parameter. The value of this parameter is read from customer_overrides.properties. For example, if the response queue name is set as ${queue_name} in the Applications Manager and customer_overrides.properties has the value as yfs.queue_name=response/Queue, the response queue name is dynamically read as "response/Queue".
Defect ID	232291
Case ID	00225468
Description	When running the integration server, if the length of the MESSAGE_ID parameter of a JMS message is more than 40 characters, the integration server throws an error.
Defect ID	232313
Case ID	Internal
Description	When the “Read Availability Across Item Sharing The Same” attribute is enabled and a shipment is created from an order release that has inventory items, the product class information is missing from the shipment lines.

Defect ID	232347
Case ID	00228490
Description	In the Sterling Business Center application, when a user performs the following steps, the items are not added to the category:
1.	Adds items to a category by clicking the “Add” button on the “Category Details” screen. The item search pop-up window is displayed.
2.	Executes a saved search on this item Search pop-up window such that the saved search contains the advanced search criteria. The search results are displayed.
3.	Selects one or more items and clicks the “Select” button in the pop-up window to add the selected items to the category. The pop-up window remains open.
Defect ID	232468, 232628
Case ID	Internal
Description	The user interface to create locales in the Applications Manager does not provide the ability to create locale with a variant.
Defect ID	232937
Case ID	00233201
Description	An AlreadyClosedException or IllegalStateException error is thrown by the Integration server, if the JMS session pooling provided by the application is enabled by setting the property yfs.yfs.jms.session.disable.pooling=N in the custom_overrides.properties file.
Defect ID	233157
Case ID	00235433
Description	The getInventorySnapShot API must support batching of the output.
Solution: The output of getInventorySnapShot is enhanced to fetch the highlighted attributes shown below:
<InventorySnapShot ...>
<ShipNode LastInventoryItemKey="". ...>  <!-- This indicates the last inventory item key of the output XML-->
       		 <Item InventoryItemKey="".../>   
Hot Fix ID	8.5-HF28
Defect ID	228896
Case ID	00181391
Description	The following APIs must be exposed as transactions, and each of the APIs must have an XML document published by the ON_SUCCESS event that contains information about the attributes that are changed by the corresponding APIs.
•	createException
•	changeException
•	assignException
•	resolveException
•	unAssignException
Solution: All the listed APIs are exposed as transactions with an ON_SUCCESS event. The XML document published by the ON_SUCCESS event contains the current value of the Inbox attributes, and the corresponding older values in an Oldvalues element. The Oldvalue element is present under each Inbox element. By comparing the current values with the old values, the changed attributes of the corresponding API can be determined. 

Note: This XML document is controlled by a template.
Defect ID	229223
Case ID	00214628
Description	When a user packs inventory for serialized and tag-controlled items using the Pack HSDE screen on a client machine that has multiple Java Runtime Environments (JRE 1.5 and JRE 1.6) installed, the system fails to set focus on the Serial field in the Serial Entry Screen.
Defect ID	230106
Case ID	00218382
Description	The createWorkOrder API fails when a user attempts to create a new work order and simultaneously takes an appointment when the product line is not available.
Solution: A new attribute IgnoreProductLines is exposed in the createWorkOrderAPI. When this flag is set to “Y”, the system ignores the product lines. Due to this, the product availability is not considered while taking appointments. For more information about the createWorkOrderAPI, refer to the Selling and Fulfillment Foundation: Javadocs.
Defect ID	231220
Case ID	00224252
Description	During the scheduleOrder API call, the sourcing regions were cached based on the country and zip code provided in the ShipToAddress. If there is more than one order line, and the zip code is not present in the ShipToAddress XML element of the order line, the API provides incorrect shipping nodes for the second order line onwards. 

Solution:  When the zip code is not provided, the sourcing region caching is based on the combination of country, state, city, and addressline6 that are specified in the ShipToAddress XML element.

Defect ID	231358
Case ID	00221131
Description	When the splitLine API is called for a released return order, an “<Error ErrorCode="YFS10136" exception is displayed.
Defect ID	231401
Case ID	00225496
Description	Based on the pricing rules configured, the 'Test Pricing' link in the Sterling Business Center application ignores the attribute based pricing rule for the unpublished items.
Defect ID	231774
Case ID	00228173
Description	When a user performs the following sequence of actions, the “Record Count Results” screen does not display any item records:
1.	Creates a count request for a location and item that has inventory in an inventory container in that location.
2.	Clicks the Complete button to complete the count tasks.
Defect ID	232068
Case ID	00229693
Description	When printing the Pack List in socket mode, special characters such as German umlauts are printed incorrectly because of the UTF-8 encoding. For example, ‘Dräger’ is printed as ‘DrÃ¤ger’.

Solution: The character encoding standard for prints is externalized through the ‘yfs.encoding.standard.for.prints’ property to encode German
umlauts. This property can be used for changing the encoding standard. The default standard set for the property is UTF-8. 

Note: An appropriate encoding standard should be used to print German characters.
Defect ID	232400
Case ID	Internal
Description	When printing the Pack List in socket mode and setting ‘yfs.encoding.standard.for.prints=’, a java.io.UnsupportedEncodingException error is displayed:
Solution:  If we do not set any value for this property, then default encoding which is set at the JVM level is used. The default standard set for the property is UTF-8.
Hot Fix ID	8.5-HF27
Defect ID	218243
Case ID	00139813
Description	The application must be able to define multiple inventory items for a selling item.
Solution: The application has been enhanced to check inventory availability of the ordered item across multiple fulfillment items in a catalog. This enhancement allows multiple vendors to supply inventory for the ordered item.

 Changed Behavior Between 8.5 and Earlier Releases: 
The Release 8.5 does not perform validations against catalog items that have the same Global Trade Item Number (GTIN). In earlier releases, the system displayed the error message "GlobalItemID already exists for another item of the organization" when more than one item in the catalog had the same GTIN. This type of validation is no longer required because Release 8.5 supports multiple items with the same GTIN to exist in the catalog.
Known Issues: 
•	While checking the availability of a selling item and an inventory item within the same findInventory API call, both the items having same GTIN displays the same total availability of the items.
•	Synchronous chained orders and DropShip chained orders are not supported with the feature "When Read Availability Across Item Sharing The Same Attribute
•	When Read Availability Across Item Sharing The Same Attribute is enabled and clicking the Create Shipment action from the Application Console for a release that has Inventory Items, the Product Class information is not set on the Shipment. 
Solution/Workaround:  none

Note: The requisite information has been updated in the Catalog Management:
Configuration Guide and Selling and Fulfillment Foundation: Product Concepts Guide.
Defect ID	231951
Case ID	00229357
Description	The application must be able to consider the node's calendar and minimum notification time to publish a matrix of all the ship dates and the corresponding available quantity.

Solution: A new rule ‘COMPUTE_AVAILABILITY_FOR_RTAM’ (Compute and Publish Availability Picture for Real-Time Availability Monitor), has been added in the Global Inventory Visibility > Inventory Rules.   
The new rule determines whether RTAM should compute and publish the availability information as part of the monitoring process and whether to consider a node's calendar and the minimum notification time while computing the availability picture.
When the rule is enabled, the availability information matrix containing ship dates and the corresponding available quantity for each date will be computed and published as part of the REALTIME_ATP_MONITOR.REALTIME_AVAILABILITY_CHANGE event.

Note: The requisite information has been updated in the following Guides;
•	Sterling Global Inventory Visibility: Configuration.
•	Sterling Reverse Logistics: Configuration.
•	Sterling Supply Collaboration: Configuration.
•	Sterling Distributed Order Management: Configuration.
•	Sterling Logistics Management: Configuration
•	Catalog Management: Configuration

Hot Fix ID	8.5-HF26
Defect ID	229269
Case ID	00211491
Description	The International Transaction Number (ITN) pop-up window should not be displayed if the ITN number is already populated at the shipment Level.
Defect ID	229853
Case ID	00217319
Description	When a user performs the following sequence of actions, in the “Details” screen of any API resources a checkbox is displayed without a label:
1.	Logs in to the application and launches the Applications Manager. 
2.	Navigates to Platform > Presentation > Resources > Resource Hierarchy.
3.	Navigates to Sterling_Supply_Chain_Applications_Console (YFSSYS00004) > Entities > Order.
4.	Creates a custom order entity and navigates to the “Details” screen of any API resources of this newly created custom entity.

Solution: The "Call in Rollback-only mode" label has been provided for the checkbox. If a user selects the checkbox for an API, the API will not be committed.
Defect ID	231023
Case ID	00222468
Description	The extended API security templates are not getting picked from the extensions global directory.
Defect ID	231046
Case ID	00224201
Description	If the multi-stop feature is enabled and large number of transfer relationship between the stores is configured, the system hangs when a user calls the findInventory API to transfer the stores.

Solution: The system will be able to calculate a direct path between the nodes and stores that have ‘NODE_TRASFER_SCHEDULE’ configured. There is no multi-stop calculation for other possible routes if a direct path is found. For a direct store to store transfer, an option to override the system-selected route through a user exit is provided.
Defect ID	231515
Case ID	00222644
Description	If the multi-stop functionality is enabled the routes with single stops are not generated by the system when the findInventory API is invoked.

Defect ID	230631
Case ID	00221222
Description	The AlreadyClosedException or IllegalStateException exception is thrown by the Integration Server.
Defect ID	230680
Case ID	00220508
Description	When a user performs the following sequence of actions, the system displays an “OMP0005: Invalid Serial number to receive” error message:
1.	Creates an inbound shipment with three shipment lines S1, S2, and S3 for a serial-tracked Item1. 
2.	Provides the actual serial numbers, SERIAL1, SERIAL2, and SERIAL3, respectively for the three shipment lines created in step 1.
3.	Confirms the shipment.
4.	Starts the receipt.
5.	Navigates to the “Receive Details” screen, and scans the item ID. 
The “Serial Number” pop-up window is displayed.
6.	Scans the serial SERIAL3 first.
Defect ID	230824
Case ID	00221071
    Description	  The CREATE_COUNT_TASKS_79 agent does not create batches of count tasks.
Defect ID	231403
Case ID	00226205
Description	When a user performs the following sequence of actions, the Sterling Mobile application forces a user to deposit the container before suggesting the next container:
1.	Configures a task type to perform Batch Pick, Pick Into Container, Pack While Pick, and System Suggested Containerization.
2.	Configures Pick Location Assignment for Batch Pick Activity and associates task type configured in step 1 to the PLA.
3.	Creates a shipment, includes the shipment in wave, and releases the wave.
4.	Containerizes the wave such that multiple containers are generated for the shipment.
5.	Batches the wave.
6.	Logs in to the Sterling Mobile application and starts the outbound picking by scanning the Batch#.
7.	Picks the inventory into the first container and clicks "Close Case".
Defect ID	231433
Case ID	00223699
Description	While printing the Pack List, special characters such as German umlauts are not printed correctly because of the UTF-8 encoding. For example, ‘Dräger’ is printed as ‘DrÃ¤ger’.
                         
                        Solution: The character encoding standard for prints is externalized through the ‘yfs.encoding.standard.for.prints’ property. 
                       This property can be used for changing the encoding standard. 
The default standard set for the property is UTF-8. 

Note: Use an encoding standard for character set appropriate for your localization language.

Hot Fix ID	8.5-HF25
Defect ID	206324
Case ID	00105295
Description	The availability of an item is based on the alert raised by the Real-Time Availability Monitor (RTAM). Therefore, when the item-node combination gets locked an alert is raised indicating that the ONHAND quantity available is zero. However, when this item-node combination is unlocked and again the inventory is available, alerts are not raised.
Solution: The syncLoadedInventory API is enhanced to delete the Inventory Node Controls while adjusting the inventory supply information. Also, the YFS_Inventory_Activity records should be inserted so that the change is picked up by the RTAM agent and an alert is raised for the availability of an item.
If Inventory Node Controls are removed manually through the manageInventoryNodeControls API, the API should insert records in the YFS_Inventory_Activity to be picked up by the RTAM agent that raises alert. The same is true for manual creation of Inventory Node Controls.
Defect ID	226463
Case ID	Internal
Description	The application must be enhanced to support Reverse Authorizations. New fields should be exposed in the executeCollection user exit to pass information regarding reversals that must be reported into the system.
Defect ID     226466
Case ID     Internal
Description     The Sterling Distributed Order Management Configuration Guide and the Selling and Fulfillment Foundation:Product Concepts Guide must be updated with the information about Reverse Authorization.
Solution: Added the following sections in the Selling and Fulfillment Foundation: Product Concepts Guide:
•	Reverse Authorization
•	Reversal of Authorization
•	Authorization Reversal Window
•	Configuration Options
•	Do Not Reverse
•	Reverse When Expired
•	Reverse Authorization Settlement Scenarios
•	Authorization Amount and Settlement Charge Match
•	Expired Authorization
•	Authorization Amount and Settlement Charge Differ
•	Manual Adjustment of Authorizations
Added the following fields in Table 7-1, of Chapter 7, "Configuring Cross Application Payment Components" of the Sterling Distributed Order Management Configuration Guide:
•	Authorization Reversal Strategy
•	Do Not Reverse
•	Reverse When Expired

Defect ID	228448
Case ID	00204919
Description	When a user performs the following sequence of actions, the unit price of the gift card to be refunded amounts to zero instead of 40 dollars. Due to which the parent sales order again gives a transfer out to the Refund Fulfillment Order (RFO) which is similar to the earlier transfer out:
1.	Creates a new item, Gift_Card without any product class, and adjusts the inventory.
2.	Chooses "Create Refund Fulfillment Order Using" option and selects Gift_Card as the Item ID in the Refund panel of Payment Type Details screen for the “Stored Value Card” Payment Type entity.
3.	Creates an order with 5 units in each order line and unit cost equals to 20 dollars each. Applies the gift card (Stored Value Card) as the payment mode.
4.	Ships the order and creates an invoice for the order.
5.	Creates a return for 2 units.
6.	Performs the return invoice creation.
7.	Calls the processOrderPayments API for the sales order on which a transfer-out happens. 
8.	Ships and invoices the refund fulfillment order.
9.	Calls the processOrderPayments API for the RFO on which a transfer-in happens. 
10.	Runs the PAYMENT_COLLECTION agent.
Defect ID	229201
Case ID	00211649
Description	The Selling and Fulfillment Foundation: Javadocs must be updated to call the YFSOrderRepricingUE user exit by the deleteOrder API.

Hot Fix ID	8.5-HF24
Defect ID	226944
Case ID	00202180
Description	When a user performs the following sequence of actions in the Applications Manager, the user is not able to add the agent criteria in the ‘Time-Triggered Transaction’ tab:
1.	Launches the Applications Manager and navigates to Platform.
2.	Loads an organization other than the DEFAULT organization.
3.	Navigates to Process Modelling > Transactions.
4.	Creates a new transaction for the enterprise by extending from an existing abstract transaction and saves it.

Defect ID	228322
Case ID	00208634
Description	When a user creates a custom JSP referring to an extended HTML file, the system selects the HTML file present in the /template/extn folder instead of selecting the HTML file present in the /global/extensions folder.
Defect ID	229128
Case ID	00214182
Description	In the Selling and Fulfillment Foundation application console, the “Order Shipment Item” screen displays interchanged values for the Product Class and Unit of Measure columns.
Defect ID	230074
Case ID	00217675
Description	When a user performs the following sequence of actions, the application updates the serial-tracked item with blank inventory item information due to which an exception is displayed during packing:

1.	Creates a serial-tracked and tag-controlled item, for example, ST01 with the batch number as the tag identifier.
2.	Adjusts inventory for ST01 in a pack location with the serial number S1, and the batch number TAG01B1.
3.	Creates another serial-tracked item, ST02.
4.	Adjusts inventory for ST02 in a pack location with the serial number as S1.
5.	Creates a shipment SHIP1 for ST01 with quantity as 1.
6.	Scans the shipment at the Pack Station and clicks "New Case".
7.	Scans ST01 in the "Item" field and S1 in the "Serial" field.
8.	Confirms the shipment SHIP1.
9.	Creates a shipment SHIP2 for ST02 with quantity as 1.
10.	Scans the shipment at the Pack Station and clicks "New Case".
11.	Scans ST02 in the "Item" field and S1 in the "Serial" field.
Defect ID	230097
Case ID	00219056
Description	When a user performs the following sequence of actions, the system does not modify or delete the value of the tag or serial number:

1.	Creates an inbound shipment for a serial-tracked item.
2.	In the “Shipment Line View Details” screen, enters the serial number and quantity.  
3.	Ships the shipment.
The status of the shipment is changed to "Shipment Shipped".
4.	Navigates back to the “Shipment Line View Details” screen.

Hot Fix ID	8.5-HF23
Defect ID	226796
Case ID	00047631
Description	A new API must be exposed for copying hub rules.
Solution: A new copyHubModificationRules API has been provided that copies the status modification from the ‘DEFAULT’ organization to the called organization for a given process type.
For more information about the copyHubModificationRules API, refer the Selling and Fulfillment Foundation: Javadocs.
Defect ID	227035, 227036
Case ID	Internal
Description	The new getAvailableInventory Foundation API for Field Sales Mobile has been introduced. The application has been enhanced to provide the ability to check inventory availability of a model item by specifying a child item or a set of attributes such as style, size, and color.

Behavior Changes
In earlier releases, if a customer checked the availability of a model item, information only about the model item was returned. Inventory information about the child items was not included, nor was information provided about the model item as defined by a set of attributes. In Release 8.5, if a customer checks the availability of a model item without specifying the child items or a set of attributes, the inventory information about the model item and all the child items is returned. For more information about the Inventory Availability of Model Items, refer to the Selling and Fulfillment Foundation: Product Concepts Guide.
Defect ID	227224
Case ID	00203697
Description	The ModifyItem API creates duplicate records in the YFS_ADDITIONAL_ATTRIBUTE table.
Solution: 
•	The 'AttributeDomainID' and 'AttributeGroupID' attributes will be stamped as 'ItemAttribute' and 'ItemReferenceGroup' respectively for all inserted or updated or deleted operations in the modifyItem API.
•	A yfs.manageItem.EnableUpdateOfAdditionalAttribute new property has been introduced in the yfs.properties_ysc_ext. If the yfs.manageItem.EnableUpdateOfAdditionalAttribute property is set to ‘Y’, the behavior of the manageItem API will be similar to modifyItem API. By default, the value of the property will be ‘N’.
•	If the 'AttributeDomainID' and 'AttributeGroupID' attributes value are passed as blank, the manageItem API will throw an error.
Defect ID	228759
Case ID	00209496
Description	When a user calls the manageItem API for an enterprise that does not exist on the system, an ‘Error Description not available for Error Code "YCM0041_50SP3"’ error message is displayed instead of displaying the correct error message.
Defect ID	228760
Case ID	00212120
Description	In the Sterling Business Center, while executing the saved search for certain advanced search criteria the system does not display the correct search results.
Defect ID	228834
Case ID	Internal
Description	When the processorderhold agent creates a hold in the first run and resolves the hold before the second run the agent does not create a hold again.
Defect ID	229029
Case ID	00213152
Description	When a user implements the beforeShipCartonUE user exit to invoke the changeShipmentContainer API in the ‘On Container Pack Process’ event, the system throws a ‘YFC0009 - Update failed’ error message while completing the pack process.
Defect ID	229059
Case ID	00213660
Description	When a shipment contains multiple items packed in one container, all the packed items are not passed to the FXRS for international shipments.
Defect ID	229087
Case ID	00208768
Description	When the TrackingNumber attribute is passed in the output XML of the YCSreturnShippingLabelUserExit user exit, the ‘Return Tracking Number’ pop-up window must not be displayed while packing a container.
Defect ID	229119
Case ID	00205207
Description	When a user performs the following sequence of actions, the ‘Tag Serial Capture’ panel is not displayed in the “Shipment Line Detail” screen:

1.	Creates an inbound shipment with ship node as blank.
2.	In a shipment adds shipment lines for a serial tracked item, clicks on any shipment line and navigates to the “Shipment Line Detail” screen.
Defect ID	229506
Case ID	00213898
Description	When a user performs the following sequence of actions, the system throws a null pointer exception:

1.	Creates a container from the “Catalog management” screen.
2.	Navigates to Classification, adds a Picking Type classification definition and binds the classification to the Container Category Classification purpose.
3.	Creates ‘Picking Type’ classification hierarchy and selects the Picking Type Classification while creating the container.
4.	Clicks “Save”.
Defect ID	229849
Case ID	Internal
Description	In the Sterling Business Center, a user is not able to create saved search with advanced search criteria for the Pricing Rules.
Defect ID	230154
Case ID	Internal
Description	All the documents provided in this hot fix must be updated with the new logo.
	For the entire set of documents that have new logo go to; http://www.sterlingcommerce.com/Documentation/MCSF85/PDFs.htm.
Hot Fix ID	8.5-HF22
Defect ID	201802
Case ID	00097347
Description	The link to Section 4.2.6, "Defining Transactions” is not working in the following documents:
•	Catalog Management: Configuration Guide
•	Sterling Distributed Order Management: Configuration Guide
•	Sterling Global Inventory Visibility: Configuration Guide
•	Sterling Logistics Management: Configuration Guide
•	Sterling Reverse Logistics: Configuration Guide
•	Sterling Supply Collaboration: Configuration Guide
•	Sterling Warehouse Management System: Configuration Guide
Solution: In all these documents, the link has been deleted and reference to the "Defining Transactions” section of the Selling and Fulfillment Foundation: Application Platform Configuration Guide has been provided.
Defect ID	225267
Case ID	00197393
Description	The Selling and Fulfillment Foundation: Installation Guide must be updated with the information about Oracle JDBC driver version.
Solution: The requisite information has been included in Chapters, "Installing and Configuring Database Tier Software on UNIX/Linux" and “Installing and Configuring Database Tier Software on Windows” in the Selling and Fulfillment Foundation: Installation Guide.
Defect ID	226869
Case ID	00195752
Description	The Sterling Business Center application must display the item short description along with item ID in the “Pricing Rule Details” screen.

Solution: The application displays a tooltip for the ‘Item’ trigger field in the following screens. The tooltip will display the short description of the item in base locale.
•	Pricing Rule Details 
•	Coupon details 
•	Test Pricing 

Defect ID	226917
Case ID	00201290
Description	The output XML of the findInventory API does not return the attribute ‘RequiredCapacity’ attribute (under AdditionalCapacityLimit).

Solution: The output XML of the findInventory API has been modified. The ‘RequiredCapacity’ attribute (under AdditionalCapacityLimit) has been replaced with the ‘Capacity’ attribute.
Defect ID     228004
Case ID     00208349
Description     When a user performs the following sequence of actions, the Item-Based Allocation (IBA) agent applies a “Hold” on the order that is in the “Released” status:
1.	Configures IBA to pick the demands that are in the “Scheduled” status.
2.	Configures an order-level hold to apply a “Hold” on an order when the reservation of the corresponding order line changes.
3.	Ensures that one order exists in the “Released” status, and another order exists in the “Scheduled” status.
4.	Runs IBA.
Solution: The application has been enhanced such that IBA will not process the demands that are in the “Released” status.

Defect ID	228112
Case ID	00208407
Description	In the “Attribute Management:Create Attribute” screen of the Sterling Business Center, the ‘Item Field’ drop-down list does not contain all of the extended item fields.
Defect ID	228198
Case ID	00208932
Description	When a user performs the following actions, the system throws "WMS00272: Item counted does not match task" exception:
1.	Configures the item classifications for count strategies.
2.	Associates the items with the configured item classifications.
3.	Creates a count request for the item classifications.
4.	Adjusts the inventory for the associated items in a location.
5.	Adjusts the inventory for other items that are not associated to these classifications in the location.
6.	Releases the count request to create a count task.
7.	Performs negative adjustment of inventory to ensure that zero quantity is available for all the items associated with these classifications in the location.
8.	Performs record count operation for the count task.

Defect ID	228215
Case ID	Internal
Description	The web.xml file created using the platform buildwar or buildear scripts with "SCUIFwkImpl" as the dependency contains a lot of unnecessary entries that are not required for the Sterling Mobile applications.
Defect ID	208330
Case ID	00127043
Description	The Selling and Fulfillment Foundation: Installation Guide must be updated with the information about the runtime utilities.
Solution: The requisite information has been updated in the Selling and Fulfillment Foundation: Installation Guide.
Defect ID	228436
Case ID	Internal
Description	The copyright statement provided in the minifed javascript files in Sterling Business Center is incorrect.
Defect ID	228513
Case ID	00211190
Description	A DB deadlock occurs in the YFS_ORDER_HEADER table, when Item Based Allocation (IBA) agent is run in multi-threaded mode.
Defect ID	228600
Case ID	00211707
Description	When a user invokes the getNodeInventory API by passing the PendInQty and PendOutQty attributes in the output XML template for an item for which the inventory is not available in the node, the system throws an "ORA-00936: missing expression error" exception.
Defect ID	228815
Case ID	Internal
Description	The Sterling Multi Channel Fulfillment Suite 8.5 must be certified to support Microsoft Internet Explorer 8.0.
	
Solution: The Sterling Multi Channel Fulfillment Suite 8.5 is certified to support Microsoft Internet Explorer 8.0.

For more information about the supported web browsers for access, see Section "Internet Browser and Plugin Requirements”, of the Selling and Fulfillment Foundation: Installation Guide.
Defect ID	228997
Case ID	00212809
Description	The system allows a pack station user to scan and ship a serial that is not present in a node.
Defect ID	229148 
Case ID	Internal
Description	The localization issues in the application have been fixed, and the relevant documents have been updated.

Defect ID	228811
Case ID	00211919
Description	If YFSAutheticatorEx is implemented to have custom logic for logging into the application, and if receiving preferences for a nWMS node have been configured, then during login application goes into infinite loop causing StackOverFlowException.

Solution: A template for the user data from the database can be configured as follows.
- Create directory: <INSTALL>\extensions\global\template\authenticator
- Create a template XML, named "authenticateUser.xml", and place it inside the directory       created above.
- Rebuild resources.jar.
- Recreate EAR/WAR.

Hot Fix ID	8.5-HF21
Defect ID	204604
Case ID	Internal
Description	When a user performs the following sequence of actions, the Item-Based Allocation (IBA) agent applies a “Hold” on the order that is in the “Released” status:
1.	Configures IBA to pick the demands that are in the “Scheduled” status.
2.	Configures an order-level hold to apply a “Hold” on an order when the reservation of the corresponding order line changes.
3.	Ensures that an order exists in the “Released” status, and another order exists in the “Scheduled” status.
4.	Runs IBA.
Solution: The application has been rectified such that IBA will not process the demands that are in “Released” status.
Defect ID	211825
Case ID	Internal
 Description	When a user performs the following sequence of actions, the bundle parent line does not display the correct quantity: 
1.	Creates a sales order in a drop ship scenario and schedules the order. 
The order goes into the “Awaiting Chained Order Creation” status.
2.	Creates a chained order using the createChainedOrder API. 
A drop ship purchase order is created.
3.	Schedules and releases the purchase order.
4.	Cancels some quantity from the purchase order.
Defect ID	215730
Case ID	Internal
Description	When a user performs the following sequence of actions, a wrong inventory demand is created:
1.	Creates a sales order for the parent item and schedules the order 
In a Drop Ship scenario, the order goes to the “Awaiting Chained Order Creation” status. 
2.	Calls the createChainedOrder API.
A Drop-Ship purchase order is created and the sales order is moved to the “Chained Order Created” status.
The purchase order is created for the substitute item, since inventory is available only for the substitute item.
A demand is created for the substitute item.
3.	Schedules the purchase order and releases it.
The purchase order goes to the “Released” status and the listener to purchase order pipeline will change the status of the Sales Order.
The demand for the parent item gets updated and the demand for the substitute item becomes zero.
Defect ID	226913, 226914, 224808
Case ID	00171196, 00199075, 00190524
Description	When a user runs the Configuration Deployment Tool (CDT), it does not show  differences  for the table YFS_GRAPH_UI table for certain records that have 'EventCondition' as the graph type. 
Defect ID	226239
Case ID	00198241
Description	An out-of-memory exception is thrown when a user searches inventory for a node having huge inventory records.
Defect ID	226868
Case ID	00195751
Description	In the “Test Pricing” screen of the Sterling Business Center application, the ‘Item ID’ field must be editable. 
Defect ID	227203
Case ID	00204292
Description	A null pointer exception is thrown while completing a count task for a count request created for multiple item classifications through the Selling and Fulfillment Foundation application console.
Defect ID	227279
Case ID	00204349
Description	In the Selling and Fulfillment Foundation: Javadocs, for the getOrderDetails API the following attributes should not be present in the output XML template:

•	CreditWOReceipt
•	ReturnWindow
•	IsReturnable
Defect ID	227429
Case ID	00204814
Description	When a user launches the application through start.jsp, the page is redirected to login.jsp which displays “/login.jsp?ErrorMsg=System_Timeout” message.

Defect ID	227435
Case ID	00195752
Description	The getPricingRuleDetails API must be enhanced to display the following attributes in the output XML:
•	TargetItemDesc attribute for the PricingRuleTargetItem element
•	ShortDescription and Description attributes for the PricingRuleItem element

Defect ID	227837
Case ID	00205360
Description	In the Sterling Business Center application when a user opens the “Pricing Rule Summary” screen for a Pricing Rule of ‘Item Quantity’ type, manually enters a valid item in the ‘Item ID’ field and tabs out, the Unit of Measure of an item does not get displayed, the Unit of Measure is not stored in the YPM_PRICING_RULE_TARGET_ITEM table and the pricing rule does not get applied.
Defect ID	227839
Case ID	Internal
Description	In the Sterling Business Center application, when a user opens the “Pricing Rule Summary” screen for a Pricing Rule of ‘Item Quantity’ type or ‘Combination’ type and enters valid service in the ‘Item ID’ field and tabs out, an "Invalid Item ID" error message is thrown.

Solution: The error message has been changed to “Invalid Item/Service ID", the error message will not be displayed if the valid service ID is entered.
Defect ID	227897
Case ID	00205207
Description	The Selling and Fulfillment Foundation application console does not provide an option to enter serial information for a serial-tracked item in the “Shipment Line Details” screen.
Defect ID	227991
Case ID	00207480
Description	When the following conditions are met, the system throws "WMS00002 - No Records Found" exception while creating an inbound shipment:
1.	Configures an enterprise E1 that inherits configuration from DEFAULT and participate with node N1.
2.	Configures DEFAULT to participate with node N1.
3.	Configures receiving preference for node N1 and DEFAULT.
4.	Creates an inbound shipment for E1 with receiving node as N1.	
Defect ID	228008
Case ID	00207924
Description	The system throws an update failed exception when the following APIs are invoked in a sequence and in a single transaction boundary:
•	addToContainer
•	changeShipmentContainer
•	addContainerToManifest

Hot Fix ID	8.5-HF20
Defect ID	205208
Case ID	Internal
Description	The application does not move the “Parent Line” of a bundle order to “Shipped” status, even after all the components of the bundle order have been shipped.
Defect ID	207407
Case ID	Internal
Description	A user is not able to release the return order because the scheduleOrder API does not schedule an order that has bundles in which the components of the bundle does not have the correct ratio.
Defect ID	217872
Case ID	00156335
Description	For the sendRelease agent if the ship_advice event is active and when a user runs the sendRelease agent for an order that is in ‘Released’ status which has charges and taxes; it throws an “Invalid Charge Category” exception.
Defect ID	218702
Case ID	Internal
Description	The Selling and Fulfillment Foundation: Localizing the Web UI Framework Guide must be updated with the information about the discrepancy between the application css, Platform, and extjs css files.
Solution: The requisite information has been updated in the Selling and Fulfillment Foundation: Localizing the Web UI Framework Guide.
Defect ID	221054
Case ID	00177322
Description	The Selling and Fulfillment Foundation: Customizing the Rich Client Platform Interface Guide must be updated with the information about template not getting picked up for custom API call on a product screen.
Solution: The requisite information has been included in the Table 10–2 “Namespace Element’s Attribute List” of Chapter, "Creating Commands for Rich Client Platform Applications", of the Selling and Fulfillment Foundation: Customizing the Rich Client Platform Interface Guide.
Defect ID	222325
Case ID	00183670
Description	Authorizations are chosen randomly for charging that may result in mismatch of an authorization and charge amount.

Solution: The system will sort the authorizations of a payment by auth expiration date and then looks for authorization whose open authorization amount matches the total charge amount. If the exact match is found, the authorization will be used for charging. If the total charge amount does not match the open auth amount of any of the authorizations, the earliest expiring authorization will be used for charging.

Note: The match may not be exact or optimal in some scenarios.
Defect ID	222461
Case ID	00181890
Description	When a user performs the following sequence of actions, the system creates a Sourcing Rule even if the read only permission is set:
1.	Creates a User Group.
2.	Navigates to Distributed Order Management > Order Promising > Sourcing and Scheduling > Product being shipped >Sourcing Rules.
3.	Sets the read only permission for Sourcing Rules.
4.	Logs in to the application and launches the Applications Manager.
Defect ID	223222
Case ID	00184580
Description	When a user calls the scheduleOrder API, the schedule promises differently depending on number of sales orders processed.
Solution: A new “Optimize Supply based on Earliest ETA” flag is exposed in Global Inventory Visibility > Inventory Rules > Other Rules. When this flag is checked, demands are matched first to inventory whose ETA is earlier, for example ONHAND supply. When this flag is checked, the rule 'Optimize supply to maximum availability' in IBA rules is over-ridden.

For more information about the new “Optimize Supply based on Earliest ETA” flag, refer Table 3-12 "Other Rules Tab", of the Sterling Global Inventory Visibility: Configuration Guide. 
Defect ID	224039
Case ID	00184664
Description	When a user performs the following sequence of actions, the verbose trace generated for the findInventory API is very huge (around 10000 lines):
1.	Configures the Classification purpose, Classification definition and Classification hierarchy and assigns it to 3 different items.
2.	Enables the verbose trace for the findInventory API.
3.	Adjusts inventory for the 3 items and calls the findInventory API for the 3 items.

Solution: Unnecessary timer logs are removed and the log volume has been reduced, say around 30%.
Defect ID	224408
Case ID	Internal
Description	The Catalog Management:Concepts Guide must be updated with a recommendation to use item based entitlements to exclude a small set of items.
Solution: The requisite information has been included in the topic "Customer Entitlement Rules" of the Catalog Management:Concepts Guide.
Defect ID	225461
Case ID	00190944
Description	The InstallService does not honor the custom log4jconfig file mentioned in the property 'yfs.log4j.configuration' specified in the customer_overrides.properties. Due to which the documentation merge and template merge log uses the default log4jconfig instead of the custom log4jconfig.
	
Solution: The installation processes or steps such as template merge and documentation merge will consider customer overrides to find log4jconfig.xml.

Defect ID	226212
Case ID	00200286
Description	If the verbose trace is enabled, and if a user runs the Reprocess Error Purge agent, the system throws NullPointerException.
Defect ID	226727
Case ID	00200517
Description	The system throws “YFC0009: Update failed” exception, when the changeShipmentContainer and getTrackingNoAndPrintLabel APIs are invoked in a single transaction boundary to update a shipment container.
Hot Fix ID	8.5-HF19
Defect ID	212661
Case ID	00142336
Description	The Selling and Fulfillment Foundation: Upgrade Guide must be updated with the information about restoring the system if some step in migration fails.
Solution: The requisite information has been included in the Section “Before History and Transaction Migration”, in the Selling and Fulfillment Foundation: Upgrade Guide.
Defect ID	224685
Case ID	Internal
Description	The Selling and Fulfillment Foundation: Extending the Database Guide must be updated with the information about the unsupported Extending Database.
Solution: The requisite information has been updated in the Selling and Fulfillment Foundation: Extending the Database Guide.
Defect ID	224735
Case ID	00193434
Description	A user is able to log in to the application even when the authentication class is returns an exception.
Defect ID	225117
Case ID	00196813
Description	When the processorderhold agent creates a hold in the first run, and resolves the hold before the second run, the agent does not again create a hold.
Defect ID	225163
Case ID	00197175
Description	In the multiApi API, when a user calls the getOrderDetails API followed by the changeOrder API for PLANNED_ORDER and its extended document types, the system displays an error message for CHANGE_ORDER_DATE and CHANGE_SRC_CNTRL modification types.
Defect ID	225723
Case ID	00197684
Description	The getItemAssociations API returns the item associations across the Organization if the item passed in the input XML is not present in the system.
Defect ID	225726
Case ID	00198323
Description	When a user performs the following sequence of actions, the system throws "An OpenShip Index (542) was not specified" exception:
1.	Creates a returnable item and sets the return label printing at the SKU level.
2.	Configures a carrier other than FEDX that integrates with FXRS server to print return labels.
3.	Creates freight terms for an enterprise.
4.	Creates a shipment with the returnable item. Uses the configured carrier of Step 2.
5.	Packs the shipment into multiple containers.
6.	Invokes the addContainerToManifest API for a container.
Hot Fix ID	8.5-HF18
Defect ID	212586
Case ID	00138777
Description	The Selling and Fulfillment Foundation: Upgrade Guide must be updated with the information about reconfiguring the count program.
Solution: The requisite information has been included in the Section "Post-Migration Selling and Fulfillment Foundation Configuration Tasks ", in the Selling and Fulfillment Foundation: Upgrade Guide.
Defect ID	222539
Case ID	00171827
Description	The Sterling Multi Channel Fulfillment Suite 8.5 must be certified to support Loftware Print Server 9.7 for its print functionality.
	
Solution: The Sterling Multi Channel Fulfillment Suite 8.5 is certified to support Loftware Print Server 9.7 for its print functionality.

For more information about supported third-party software, refer to Section “Third-Party Software Requirements”, of the Selling and Fulfillment Foundation: Installation Guide.
Defect ID	223150
Case ID	Internal
Description	The Business Center: Localization Guide must be updated with the information about the date format and bundle entries.
Solution: The requisite information has been updated in the Business Center: Localization Guide.

Defect ID	223469
Case ID	00171820
Description	The Sterling Multi Channel Fulfillment Suite 8.5 must be certified to support Microsoft Internet Explorer 8.0.
	
Solution: The Sterling Multi Channel Fulfillment Suite 8.5 is certified to support Microsoft Internet Explorer 8.0.

For more information about supported web browsers for access, refer to Section "Online Documentation Library”, of the Selling and Fulfillment Foundation: Installation Guide.
Defect ID	224330
Case ID	00189721
Description	If the JMS server goes down and again comes up, the Agent servers are not able to automatically reconnect with the JMS servers.

Defect ID	224566
Case ID	00193570
Description	If UsergroupId is passed in the ModifyUserHierarchy input XML, the ModifyUserHierarchy API does not honor the Reset="Y" attribute for the UserGroupLists element.
Hot Fix ID	8.5-HF17
Defect ID	213542
Case ID	Internal
Description	When a user performs the following sequence of actions, and calls the getPossibleSchedule API or the findInventory API, the system displays “Out of Memory” error message:
1.	Configures the Sourcing Rule such that a Procurement Order gets created.
2.	Ensures that only partial inventory is available in both Ship Node and the Procurement Node.
3.	Passes the “ReqDeliveryDate” attribute that is present in the Overrides element of the input XML such that the “ReqDeliveryDate” attribute falls on a nonworking day and non-transfer date of the Transfer Schedule configuration.     
Defect ID	214433
Case ID	00132187
Description	The “Pack HSDE” screen used for entering data at a high speed from an external device is slow when both client and backend are on WAN (wide area network).
Defect ID	216682
Case ID	00145003
Description	In the Sterling Business Center application, the “Item ID Trigger” field must be editable in the “Create Pricing Rule” screen and “Modify Pricing Rule” screen.

Solution: The “Item ID Trigger” field is made editable in the following screens:
•	Create Pricing Rule
•	Modify Pricing Rule
•	Create Coupon
•	Modify Coupon
Defect ID	218589
Case ID	00167246
Description	The application must be enhanced to be able to specify the distance criteria while configuring the Product Sourcing rules and filter out the appropriate nodes based on the distance criteria.

Solution: A new panel has been introduced in the “Shipping Sourcing Rule” screen. Also, a new YFSGetDistanceForNodeListUE user exit has been introduced. The distance passed in the output of the YFSGetDistanceForNodeListUE user exit is used to filter out the appropriate nodes.
Defect ID	218662
Case ID	Internal
Description	When a user adds a Delivery Service Option line in an order, the changeOrder API or createOrder API do not honor the quantity passed.
Defect ID	218952
Case ID	00170190
Description	In the Selling and Fulfillment Foundation: Javadocs, for the getCompleteItemList API, it is not clearly documented that the CurrentAvailableQty attribute must be passed under Availability in the output template when GetAvailabilityFromCache is passed as N in the input XML.

Solution: The Selling and Fulfillment Foundation: Javadocs has been updated. When GetAvailabilityFromCache is passed as N in the input XML, in the output template, the CurrentAvailableQty attribute must be passed under Availability so that the CurrentAvailableQty attribute is populated in the output XML.  

When GetAvailabilityFromCache is passed as N in the input XML, in the output template, only the CurrentAvailableQty attribute is populated under Availability.
Defect ID	219001
Case ID	00170804
Description	The system must not display the ITN capture pop-up window in the “Pack HSDE” screen, if the shipment that is packed is not an international shipment originating from the United States of America.
Defect ID	222271
Case ID	00180820
Description	In the Sterling Business Center application, a user is not able to delete the value after entering it in the "Price List Contains Item" field of the "Basic Price List Search" screen and in the "Target Item Is" field of the "Basic Pricing Rule Search" screen.
Defect ID	222563
Case ID	00183589
Description	When a user calls the createOrder API with PaymentDetailsList element for the PaymentMethod element, the system does not honor this list element and ignores the payment details.
Defect ID	222950
Case ID	Internal
Description	While running the LocalizedStringReconciler tool in Export mode, it does not ignore data for YFS_ERROR_CAUSE_ACTION from the YFS_NONLOCALIZED_STRINGS table.

Defect ID	223784
Case ID	00189852
Description	When a blank value is passed in the pickup date attribute of the com.yantra.ycs.japi.ue.YCSshipCartonUserExit, the addContainerToManifest API displays "0573 - Ship date must be numeric" error message.

Defect ID	223860
Case ID	00190708
Description	The “Location Inventory Search” screen times out when a user searches inventory for an enterprise in a node that has high number of inventory records.
Defect ID	224020
Case ID	00190938
Description	In the multiApi API, when a user calls the getOrderDetails API followed by the changeOrder API for PLANNED_ORDER and its extended document types, the system displays an error message.
Defect ID	224217
Case ID	00188405
Description	When a user performs the following sequence of actions to cancel an order, the system displays "YFS10137 : YFS: Order cannot be modified in current status" error message:
1.	Creates a sales order, schedules and releases the order
2.	Creates a shipment S1 for the released order.
3.	Changes the shipment status to ‘Sent To Node’.
4.	Clicks “Pack Container”.
5.	Clicks “New Case”, packs the containers and closes the container.
The shipment moves to the “Shipment Packed” status.
6.	Navigates to the “Order Detail” screen and clicks “Cancel”.

Hot Fix ID	8.5-HF16
Defect ID	216611
Case ID	00154792
Description	When a user performs the following sequence of actions in the Applications Manager, the Team drop-down list does not display teams of all the organization in the “User Details” screen:
1.	In the Applications Manager, navigates to the Platform.
2.	Loads an organization other than DEFAULT.
3.	Navigates to the User Details > Security > Users, the team defined in the current organization team is only displayed in the Team drop-down list.

Known Issue: In the “User Details” screen, the lookup icon will be displayed adjacent to the “Team” field only if the number of entries in the Team drop-down list exceeds 20. Do not use the lookup icon to select the team as it displays incorrect data.
Workaround: A user can select a team from the Team drop-down list instead of searching for the team through the search icon.
Defect ID	218752
Case ID	00169748
Description	The application must be enhanced to copy the application menu to a custom menu.
Defect ID	221051
Case ID	00177322
Description	The Selling and Fulfillment Foundation: Customizing the Rich Client Platform Interface Guide must be updated with the information about template not getting picked up for custom API call on a product screen.
Solution: The requisite information has been included in the Chapter, "Creating Commands for Rich Client Platform Applications", in the Selling and Fulfillment Foundation: Customizing the Rich Client Platform Interface Guide.

Defect ID	221361
Case ID	00178680
Description	The Selling and Fulfillment Foundation: Installation Guide must be updated with the information about oracle version.
Solution: The requisite information has been included in Chapters, " Installing and Configuring Database Tier Software on UNIX/Linux" and “Installing and Configuring Database Tier Software on Windows” in the Selling and Fulfillment Foundation: Installation Guide.
Defect ID	221390
Case ID	Internal
Description	The Selling and Fulfillment Foundation: Customizing the Rich Client Platform Interface Guide must be updated with the information about masking of sensitive information.
Solution: The requisite information has been included in Chapters, "Rich Client Platform” and “Rich Client Platform General Concepts Reference", in the Selling and Fulfillment Foundation: Customizing the Rich Client Platform Interface Guide.
Defect ID	221786
Case ID	Internal
Description	The Selling and Fulfillment Foundation: Upgrade Guide must be updated with the information about pre-migration preparation task.
Solution: The requisite information has been included in the Chapter, "Upgrading to Release 8.5", in the Selling and Fulfillment Foundation: Upgrade Guide.
Defect ID	222020
Case ID	00178513
Description	When a user logs in to the application as an administrator user, the “User Details” screen takes a long time to open when there are a large number of nodes administered (created) by an organization.
Defect ID	222241
Case ID	00175586
Description	While re-scheduling an order, it does not backorder the transfer order that has been put on hold by IBA for backorder.

Solution: 1500 is provided as pickup status of SCHEDULE.0006 for the “TO_FULFILLMENT” process type. A user must configure 1500 as the pickup status for SCHEDULE.0006 in all the transfer order pipelines after installing the factory setup.
Defect ID	222950
Case ID	Internal
Description	While running the LocalizedStringReconciler tool in the Export mode, it does not ignore data for YFS_ERROR_CAUSE_ACTION from the YFS_NONLOCALIZED_STRINGS table.
Defect ID	223949 
Case ID	Internal
Description	The localization issues in the application have been fixed, and the relevant documents have been updated.

Hot Fix ID	8.5-HF15
Defect ID	201903
Case ID	Internal
Description	While running the Person Info purge agent for purging records from the YFS_PERSON_INFO table that have large number of records, some of the queries that were fired did not use the index on the ‘MODIFYTS’ column. Due to this, the query’s response time was slow.

	Solution: The queries have been modified for Oracle database such that the index on the ‘MODIFYTS’ column is used.
Defect ID	219430
Case ID	00168770
Description	A call center user must be able to view all active promotions of Item Quantity type or Combination type for an item and for the combination of an item and customer.
Solution: The getApplicablePricingRuleList API has been provided to retrieve the list of active promotions.
Defect ID	221460
Case ID	00160294
Description	The application must be enhanced to provide an API to create a Carrier Service Pickup Schedules for a node. The only option available is through the configurator.

	Solution: The 'manageOrganizationHierarchy' and 'getOrganizationHierarchy' APIs have been provided to support creation, updation, deletion, and viewing the Carrier Service Pickup Schedules for a node.
Defect ID	221464, 220367
Case ID	00173272
Description	In the “Pricing Rule Details” screen, the localized descriptions for Pricing Rule must be provided.
Defect ID	221522
Case ID	00177139
Description	The getOrderList API do not query the history table for the extended attributes passed at the order line level.

Defect ID	221604
Case ID	00180909
Description	The cursor count keeps increasing when the “System Management Console” screen is left open.
Defect ID	221678
Case ID	00177628
Description	When migrating extended tables or custom tables, the Configuration Deployment Tool (CDT) registers a “NoSuchMethodException” exception.
Defect ID	222540
Case ID	Internal
Description	References to MySQL must be removed from the Selling and Fulfillment Foundation: Installation Guide.
Defect ID	223205
Case ID	Internal
Description	The localization issues in the application have been fixed, and the relevant documents have been updated.

Hot Fix ID	8.5-HF14
Defect ID	215708
Case ID	Internal
Description	When the constraints on the Maximum Number of Users that are allowed to work on a count request are specified, the constraints are not getting honored in the context of System Suggested and User Suggested tasks.
The constraints that are specified should be honored. In addition, a different user should not be suggested tasks of a particular count request when a maximum number of users are already working on it.
Defect ID	219077
Case ID	00170731
Description	The monitoring templates are not being picked up from the <INSTALL>/extensions/global/* directory.
Defect ID	220490
Case ID	00170780
Description	When a user performs the following sequence of actions, an YFS10048 YFS: Invalid Node error is registered.
1.	Ensures that a service item is associated with a product item.
2.	Creates an order for an item.
3.	Associates the item with a delivery service item.
4.	Ensures that the ShipNode is not passed at the order or the order line level.
5.	Invokes multiAPI in which the first API is the generateWorkOrder API and the second API is the changeOrder API such that the changeOrder API passes a valid value for procureFromNode and shipNode at the line level.
Defect ID	220602
Case ID	00176581
Description	When a user performs the following sequence of actions, the application randomly displays incorrect output:
1.	Ensures that a bundle parent exists with two “ship together” components in 1:1 ratio.
2.	Adjusts inventory such that ten quantities of one component and twenty quantities of the other component are available.
3.	Invokes findInventory API for the bundle parent for twenty quantities.
Defect ID	220788
Case ID	00176926
Description	When a user performs the following sequence of actions, the return tracking numbers are not generated and the application does not print the return labels:
1.	Creates a returnable item and sets the return label printing at SKU level.
2.	Configures a carrier service to print return labels.
3.	Creates freight terms for the enterprise
4.	Implements and invokes the YCSreturnShippingLabelUserExit.
5.	Creates a shipment with the returnable item. Uses the defined carrier service and freight terms.
6.	Packs the shipment into a container.
7.	Invokes the addContainertToManifest API for the container.
Solution: The application has been rectified to handle the output of the YCSreturnShippingLabelUserExit correctly.
Defect ID	221472
Case ID	00176293
Description	The Selling and Fulfillment Foundation: JavaDocs must be updated with the correct description for the “IsManual” flag in the output XML of the changeOrder API.
Defect ID	222136
Case ID	Internal
Description	The localization issues in the application have been fixed, and the relevant documents have been updated.
Hot Fix ID	8.5-HF13
Defect ID	213166
Case ID	00116274
Description	The application must be enhanced to support multi-stop transfer.

Solution: As part of the enhancement the application will support multi-stop transfer. The enhancement enables the system to calculate all the nodes for which product will travel through as well as compute the expected shipment date and delivery date for individual legs. 

The following property is used to define the relationship type for multistoptransfer;

yfs.MultiStopTransfer=<Relationship Type> in yfs.properties
	
The properties listed below are used to maintain the cache in the multistoptransfer in yfs.properties_ysc_ext;

•	YSCMultiStopTransferCacheManager.object.size = define the size, customer can override this.

•	YSCMultiStopTransferCacheManager.skipcache = set this property to true if you want to skip the cache.

The OMPDetermineBestMultistopTransferUE user exit is called by the findInventory, scheduleOrder, getPossibleSchedules, and changeOrder APIs and other promising APIs to get the best route between the DestinationNode and OriginNode locations. 

The best route provided by the OMPDetermineBestMultistopTransferUE user exit will be used for calculating the dates and the user exit can be used to determine the best path externally.

Input to the OMPDetermineBestMultistopTransferUE user exit will be the all possible routes between source and destination. The application expects a single best route between two nodes from this user exit. If there is more than one route between two nodes in the output, application will consider only the first route.
Defect ID	216339
Case ID	00157486
Description	The Selling and Fulfillment Foundation: Upgrade Guide must be updated with the information about the history tables.
Solution: The requisite information has been included in the Chapter, "Upgrading to Release 8.5", in the Selling and Fulfillment Foundation: Upgrade Guide.
Defect ID	220548
Case ID	00176293
Description	When a user performs the following sequence of actions, the ‘IsManual’ attribute is not present in the line charges and header charges elements of the changeOrder API output:
1.	Creates an order.
2.	Calls the changeOrder API to add the line charges and header charges to it.

Also, the LineCharges and HeaderCharges elements are available in the output template of the changeOrder API.
3.	Checks the output of the changeOrder API.

Note: The fix is applicable only for the YFS_LINE_CHARGES and YFS_HEADER_CHARGES records, which is created or changed after applying the fix. The existing YFS_LINE_CHARGES and YFS_HEADER_CHARGES records will retain the current value.
Hot Fix ID	8.5-HF12
Defect ID	212904
Case ID	00139399
Description	If a user extends the YFSDataTypes.xml and yfsdatatypemap.xml in 7.x version, and upgrades to 8.5 version, the extended YFSDataTypes.xml and yfsdatatypemap.xml are not migrated to the correct location in the 8.5 installation. As a result of this the extensions do not work.

Defect ID	216742
Case ID	00149932
Description	The getInventorySnapShot API for a ship node provides only ONHAND supply picture which has multiple supplies for an item. It should also provide future inventory picture.

Solution: A new attribute 'GetFutureSupplies' has been introduced in the input xml of the getInventorySnapShot API. If 'GetFutureSupplies' flag is set to Y, the getInventorySnapShot API returns the future inventory picture.
Defect ID	217757
Case ID	00164388
Description	The Selling and Fulfillment Foundation: Installation Guide must be updated with the information about the suggested installation command parameters.
Solution: The requisite information has been included in the Chapter, "System Requirements", in the Selling and Fulfillment Foundation: Installation Guide.
Defect ID	218817
Case ID	00125614
Description	The Selling and Fulfillment Foundation: Installation Guide must be updated with the information about the supported Oracle version.
Solution: The requisite information has been included in the Chapter, "System Requirements", in the Selling and Fulfillment Foundation: Installation Guide.

Defect ID	218870
Case ID	00167651
Description	When a user performs the following sequence of actions, the “Pack HSDE” screen displays incorrect quantity in the "QuantityToPack" attribute in the "Items" panel:
1.	Creates a shipment with multiple shipment lines for an item.
2.	Packs partial quantities of a shipment line into an outbound container.
3.	Logs out from the Pack HSDE screen.
4.	Re-launches the Pack HSDE screen by clicking on "Pack/Unpack" action in the “Outbound Shipment Details” console to pack the remaining quantities. 

Defect ID	218936
Case ID	00170663
Description	The existing additional attributes of an item in the YFS_ADDITIONAL_ATTRIBUTE table are deleted when the item is saved more than once through the configurator.
Defect ID	218963
Case ID	00169329
Description	When a user upgrades from Release 7.5 SP1 to Release 8.5, while saving the details in the configurator for an item, the system displays “YFC0002 : Record does not exist in the database” error message.

Defect ID	219015
Case ID	00170685
Description	When a user navigates to the “Global Inventory Visibility” screen and configures “Current Inventory Availability Safety Factor” for ONHAND, the system does not allow the user to set the value of the “SafetyFactorPercentage” as 0.

Defect ID	219765
Case ID	00172671
Description	The Selling and Fulfillment Foundation: Installation Guide must be updated with the information about TIBCO EMS 5.0.
Solution: The requisite information has been included in the Chapter, "System Requirements", in the Selling and Fulfillment Foundation: Installation Guide.

Defect ID	209967
Case ID	00133966
Description	The Selling and Fulfillment Foundation: Installation Guide must be updated with the information about the supported Oracle version and also mention that the Oracle RAC is supported on 2-node configurations.
Solution: The requisite information has been included in the Chapter, "System Requirements", in the Selling and Fulfillment Foundation: Installation Guide.
Hot Fix ID	8.5-HF11
Defect ID	213066
Case ID	00143596
Description	The Business Center: Pricing Administration Guide must be updated with the information about the ability to setup the Pricing Rule for Item attributes.
                        
Solution: The requisite information has been included in the following topics of Business Center: Pricing Administration Guide:
•	Create an Item Quantity Pricing Rule
•	Create a Shipping Surcharge Pricing Rule
•	Modify the Conditions and Effects of an Item Quantity Pricing Rule
•	Modify the Conditions and Effects of a Shipping Surcharge Pricing Rule
Defect ID	217932
Case ID	00165248
Description	The findInventory API provides incorrect solution, if there are 2 Purchase Orders (PO) with same cost and priority that are present at different nodes, and one of the POs has an earlier Expected Time of Arrival (ETA).

Solution: When the optimization criteria considered is cost and number of shipments, the node priority is calculated as the latest priority for the provided sourcing details.
Defect ID	217947
Case ID	00159175
Description	When a user configures the Real Time Availability Monitor, the query that fetches records from the YFS_INVENTORY_ALERTS table using the parameters other than the INVENTORY_ALERT_KEY does not lock the record. Also, while updating the records the "YFC0009-Update failed" error message is displayed.
Defect ID	218038
Case ID	00158720
Description	When a user tries packing a child container inside an outbound container at the Pack Station, the system throws “YDM00025: Shipment modification rules do not permit modification of shipment in its current status” error.

Defect ID	218179
Case ID	00164714
Description	When a user performs the following sequence of actions, the application displays "WMS00023: Inventory Status not passed and transition is not specified for blank status" error message:
1.	Creates an outbound shipment for a FIFO tracked item I1 with 10 quantities.
2.	Creates a wave for the shipment and releases the wave.
3.	Completes the task using the Sterling Apps Console by picking complete LPN1 and specifies the target case ID. 
4.	Deposits it in the Pack location.
5.	Navigates to the Pack Station and Clicks “New case”.
6.	Scans the LPN1 in the SKU field and packs the shipment.
7.	Navigates to the Pack station, selects “Unpack” radio button to unpack the shipment. 
8.	Again scans the LPN1 in the SKU field.
Defect ID	218867
Case ID	Internal
Description	When a user unpacks multiple child containers from an outbound container that is created for an outbound shipment, the "ORA-936: Missing Expression" error message is displayed.

Hot Fix ID	8.5-HF10
Defect ID	217194
Case ID	00131644
Description	A user is not able to view the localized description of the value assigned to an item attribute.
Solution: The output xml of the getItemListForOrdering API has been enhanced to include the ShortDescription and the LongDescription values for item attribute assigned value.
Defect ID	217522
Case ID	00161469
Description	When a user performs the following sequence of actions, the system displays an “update failed” error message:
1.	Invokes a service on success of Complete Move Request, and the service calls the addToContainer API.
2.	Adjusts inventory. 
3.	Creates an outbound shipment. 
4.	Invokes the retrieveShipment API to create retrieval task for an item.
5.	Invokes the registerBatchCompletion API.
Defect ID	217631
Case ID	00163348
Description	The application should have the "INVENTORY_SORTING" base activity group.

Defect ID	218028
Case ID	00166446
Description	The application should support "ON_SUCCESS" event for the CANCEL_TO_SHIPMENT transaction.
Defect ID	197322
Case ID	Internal
Description	When the following conditions are met, the registerTaskCompletion API throws "WMS00014: CaseID/PalletID doesn't exist" error message:
1.	Moves a task to the In-Progress status by picking inventory for an item from a multi-SKU license plate.
2.	Moves other SKUs from an LPN such that the LPN is deleted from the system when it is empty.
Solution: The ProcessAllTasks and CompleteInprogressTasks flags are exposed in the moveLocationInventory API. This will prevent the auto-completion or auto-cancellation of tasks associated to an LPN when the LPN is deleted from the system after moving inventory.
Defect ID	218027
Case ID	00123163
Description	The Selling and Fulfillment Foundation: Customizing the Rich Client Platform Interface Guide must be updated with information about the capability to switch a locale.
Solution: The requisite information has been included in the Chapter, "Rich Client Platform", in the Selling and Fulfillment Foundation: Customizing the Rich Client Platform Interface Guide.

Hot Fix ID	8.5-HF9
Defect ID	209169
Case ID	00125801
Description	The Selling and Fulfillment Foundation: Performance Management Guide must be updated with information about jboss.PRECOMPILE_MAX_MEMORY.
Solution: The requisite information has been included in the Chapter, "Jboss", in the Selling and Fulfillment Foundation: Performance Management Guide.
Defect ID	214733
Case ID	Internal
    Description	 In the “Pricing Rule Summary” screen of the Sterling Business Center application, the “Pricing Rule description” field should allow 2000 characters.
Defect ID	215821
Case ID	00154828
Description	The Selling and Fulfillment Foundation: Configuration Deployment Tool Guide must be updated with information about the CDT "httpurl" attribute.
Solution: The requisite information has been included in the following chapters of the Selling and Fulfillment Foundation: Configuration Deployment Tool Guide:
•	Running the CDT and Setting Up the Preference Settings (GUI-Based)
•	Setting Up the Preference Settings (Text-Based)
•	Configuration Data Versioning Tool
Defect ID	215913
Case ID	00154358
Description	When a user performs the following sequence of actions, a pop-up window displays the "No open shipment (s) to pack” message:
1.	Logs in to the Selling and Fulfillment Foundation application.
2.	Navigates to the “Shipment Details” screen.
3.	Clicks “Pack Shipment”.
4.	In the “Pack” screen, selects pack station.
5.	Clicks a new case. 
6.	Packs the shipment.
7.	Clicks “Close Container”, to move the container to packed status. A pop-up window displays “pack complete for shipment” message.
8.	Clicks “OK.
Defect ID	215995
Case ID	00155989
Description	When a user performs the following sequence of actions, the system displays wrong timezone:
1.	Logs in to the Selling and Fulfillment Foundation application.
2.	Launches the 'Applications Manager'.
3.	Navigates to the Platform > Presentation > Locales.
4.	Selects ‘Canada/Newfoundland’ timezone from the timezone selection drop-down.
The timezone is displayed in the format, 'GMT-02:-30'. In the timezone displayed, the separator for the hour and minute has an extra hyphen.

Defect ID	216182
Case ID	Internal
Description	The RESOURCE_ID SBCITM00104 does not map to the same record in a fresh installation of the Selling and Fulfillment Foundation 9.0 as the one upgraded from Release 8.5. In upgraded environment the RESOURCE_ID SBCITM00104 is mapped to ‘Preview_Item_Details’ but in the fresh installation of 9.0 the RESOURCE_ID SBCITM00104 is mapped to ‘Create_Attribute_Group’.
Defect ID    216216
Case ID	Internal
Description	During HF installation for Release 8.5, sometimes the installation may fail with an Out-Of-Memory error message.
Solution: This issue has been fixed. To further reduce the memory usage during HF installation, a 'SUPPRESS_MUNGE_BACKUP' property with the value as ‘true’ can be added in the 'sandbox.cfg' file. This skips the creation of the backup files for each script during installation. As this reduces the number of unnecessary files during installation; the memory consumption is further reduced during HF installation.

Defect ID	216381
Case ID	00157096
Description	In the Selling and Fulfillment Foundation application, when a user modifies an order from the “Order Details” screen, the “Modification Reason” pop-up window is displayed. However, the pop-up window displays the reason codes that belong to all the Enterprises, instead of displaying the reason code of an enterprise to which the order belongs.
Solution: A new ‘YMRD999’ resource ID is provided for the “Modification Reason” pop-up window, when an order is cancelled from the “Order List” screen of sales order. A user must give appropriate permission for the “Modification Reason” pop-up window, when it is accessed through User Group other than SYSTEM.
Defect ID	216615
Case ID	00154799
Description	When a user performs the following sequence of actions, the log in fails:
1.	Logs in to the Selling and Fulfillment Foundation application. 
2.	Navigates to Application > Platform.
3.	Creates a Team at DEFAULT. 
4.	Selects the “All Nodes” option for Ship node access.
5.	Creates a user for DEFAULT and assigns the created team to the user.
6.	Creates “BAY” Enterprise under DEFAULT.
7.	Creates N1 and N2 nodes under BAY.
8.	Logs in to the Sterling Store client using the user credentials of the user created for “BAY” enterprise and Node N1.
Defect ID	216618
Case ID	00146516
Description	When a user performs the following sequence of actions, the “Adjustment Cost” screen in the application do not display the correct adjustment quantity or adjustment cost:
1.	Logs in to the Selling and Fulfillment Foundation application.
2.	Navigates to the "Adjust Location Inventory" screen.
3.	Enters the reason code and quantity to adjust.
4.	Clicks "Adjustment Cost" button in the "Quantity" panel.

Defect ID	216623
Case ID	00152526
Description	When a user performs the following sequence of actions, system prompts for ITN#:
1.	Logs in to the Selling and Fulfillment Foundation application.
2.	Creates an outbound shipment.
3.	Navigates to the “Shipment Details” screen.
4.	Clicks “Pack Shipment”.
5.	Clicks “Close Shipment”.

Defect ID	216830
Case ID	00159579
Description	When a user performs the following sequence of actions, the order lines are not displayed in the “Order Detail” screen:
1.	Creates an order with 3 order lines.
2.	Purges the order.
3.	Navigates to the Order Search.
4.	Selects 'history' radio button.
5.	Clicks “Search”.
6.	Clicks on the Order created in the step 1 and navigates to the “Order Detail” screen.
Defect ID	216851
Case ID	00158776
Description	The ‘EnableVerboseGc’ and ‘EnableHeapDump’ property set in the “performance.properties” is not picked up by the agent server or integration server.

Defect ID	217131
Case ID	00157554
Description	The Selling and Fulfillment Foundation application should be enhanced to be able to add Store Order Management and Customer Order Management menu groups for the same user.

Hot Fix ID	8.5-HF8
Defect ID	212428
Case ID	Internal
    Description	If there are multiple colonies and CDT is run for a specific colony, then for some tables, such as YFS_SCAC_EX, YFS_DEVICE_SUB_TYPE and so on, the records are not retrieved for the specified colony. Instead all the records are retrieved. Due to this, CDT fails as the corresponding records in the YFS_ORGANIZATION table are not found as the records do not belong to the specified colony.
Defect ID	213986
Case ID	00144886
Description	When session timeout value is changed in the web.xml, it is not affecting the session timeout of a user.

Solution: In Release 8.5, the session timeout value from the YFS_USER table will be overriding the session timeout value in the web.xml. A new context-param 'scui-suppress-user-level-sessiontimeout-override' has been added to provide an option to ignore the session timeout value from the YFS_USER table. 
If the application or customers do not want the session timeout value mentioned in the  web.xml to be overridden by the session_timeout column value in the YFS_USER table, then the application or a customer must add the following entry in the web.xml:
<context-param>
<param-name>scui-suppress-user-level-sessiontimeout-override</param-name>
<param-value>y</param-value>
</context-param>

Note: The requisite information has been included in the section, "Customizing web.xml for Session Timeout", in the Selling and Fulfillment Foundation Customization Basics Guide.

Defect ID	214232
Case ID	00148325
Description	The item configured as a provided service item is not listed in the output of the getPricelistLineList API.

Defect ID	214389
Case ID	00123127
Description	The Sterling Business Center application does not allow a user to create a Pricing Rule based on the service items.

Defect ID	214390
Case ID	00123116
Description	The Sterling Business Center application does not allow a user to add services into a pricelist. Due to this the price of the services cannot be managed through the Sterling Business Center application.
Defect ID	214931
Case ID	00138249
Description	If Install3rdparty utility is used to install a jar having 'ejb' in its name, and EAR is build. The EAR fails to deploy. This happens because during building of the EAR, the jar file is registered as an EJB even though it is just a regular jar.
Defect ID	214960
Case ID	00150150
Description	When a user creates and packs a shipment, navigates to the “Container Details” screen, the details corresponding to the “Description”, “Qty”, and “Packed qty” fields are moved towards the left of the column. 

Defect ID	214973
Case ID	00150930
Description	When a user performs the following sequence of actions; system throws the "Not Enough Quantity" exception instead of moving the inventory to the configured inventory status:
1.	Configures a PICK exception under Task Execution Exceptions with "Change inventory status for unavailable quantity" enabled.
2.	Adjusts inventory in a location for an item
3.	Creates a task to pick the inventory from the location
4.	Performs short pick by entering the exception specified in step 1  while executing the task through mobile device using equipment.
Defect ID	215395
Case ID	00152690
Description	The Selling and Fulfillment Foundation application hangs infinitely when a user attempts to adjust location inventory or while creating a wave. The system displays the “Action can't be performed" pop-up window.

Defect ID	215541
Case ID	00143247
Description	The reprocessible exception is not inserted on the database because of another exception which occurs while creating the reprocessible exception.

Solution: While creating a new exception, a Unique Exception ID is generated. 
When a new Unique Exception ID is generated, another exception occurs while fetching the IP address of the host machine, by default the IP address is set to 127.0.0.1 and proceeds with generation of the Unique Exception ID and exception.

Defect ID	215604
Case ID	00144495
Description	When a user runs the CREATE_WAVE_SHIP_GROUP agent, the system displays the “ORA-1841” error. 
Solution: From SYSDATE, remove the quotes.

Defect ID	215605
Case ID	00154166
Description	When a user configures an agent with a service to be executed at the completion of work in the “Agent Criteria Details” screen, the system displays the “YCP0427” error message when the agent is run.

Defect ID	215613
Case ID	00154219
Description	The Selling and Fulfillment Foundation: Release Notes must be updated with information about conversion of LONGs to CLOBs.
Solution: The requisite information has been included in the section, "Miscellaneous Enhancements to Back-End Architecture", in the Selling and Fulfillment Foundation: Release Notes.

Defect ID	215807
Case ID	00153606
Description	When a user passes the ProcessedAmount, RequestAmount, and ChargeAmount with negative values, and validates against YFS_recordExternalCharges_input.xsd, the validation fails.
Solution: The application has been enhanced, the data types of the ProcessedAmount, RequestAmount, and ChargeAmount has been updated to accept negative values during the validation.

Defect ID	215978
Case ID	Internal
Description	When a user performs the following sequence of actions, the getShipmentLineList API throws a null pointer exception:
1.	Creates a Return Order. 
2.	Releases the Return Order.
3.	Creates a shipment for the Return Order and ships the shipment.
4.	Calls the getShipmentLineList API with the <ReceiptLines> element in the output template before receiving the Return Order.

Defect ID	216246
Case ID	Internal
Description	If a table with history is extended at multiple levels, there is a mismatch in the number of columns in the table and its history table.

Defect ID	216512
Case ID	00123116
Description	The Business Center: Pricing Administration Guide must be updated with information about the Provided Service Items.
Solution: The requisite information has been included in the sections, "Using Item-Based Search", “Basic Price List Search”, “Basic Pricing Rule Search”, and “Add Items When Testing the Pricing Setup” in the Business Center: Pricing Administration Guide.
Defect ID	216513
Case ID	00123127
Description	The Business Center: Pricing Administration Guide must be updated with information about the Provided Service Items.
Solution: The requisite information has been included in the following sections in the in the Business Center: Pricing Administration Guide:
•	Create a Combination Pricing Rule
•	Create a Item Quantity Pricing Rule
•	Modify the Conditions and Effects of a Combination Pricing Rule
•	Modify the Conditions and Effects of an Item Quantity Pricing Rule
•	Basic Pricing Rule Search

Hot Fix ID	8.5-HF7

Defect ID	201929
Case ID	Internal
Description	When a tag tracked item having both tag identifiers and tag attributes is packed by scanning tag identifiers the tag attributes are not shown in the container details:
1.	Creates an order with tag controlled item and configures tag identifier and tag attributes for the item.
2.	Adjusts the inventory in the node (Forward Pick location) with the same batch, lot, revision numbers. 
Also, ensures to adjust the inventory in the Pack Station with the different batch, lot, revision numbers, so that while packing the tag entry pop-up window will appear.
3.	Confirms the order. 
Schedules the order and releases it.
4.	Creates a shipment and adds the shipment to the wave.
5.	Assigns lane and releases the wave.
A shipment having the tag controlled item in its shipment line will be in “Sent_To_Node” status and the required inventory is available at the Pack Station. Extra inventory for the same item is also available at the Pack Station with a different tag identifier.
6.	Navigates to the Pack Station and tries to pack the shipment.
The user is prompted to scan the tag identifier for the inventory. After scanning the tag identifier for the inventory the shipment is packed.
Defect ID	206526
Case ID	Internal
Description	The system displays incorrect time in certain time zones that use daylight saving for the dates that fall on the same day when the daylight saving starts or ends.
Solution: The application has been enhanced so that the system displays the correct time in different time zones even for the dates when the daylight saving is started or ended.
Defect ID	210114
Case ID	00134663
    Description	When a user tries to configure "Order Selection Rules" in the “Item Based Allocation Rules” screen, the “Dynamic Condition” radio button is not enabled.

Defect ID	213297
Case ID	00144795
Description	If the modified weblogic.xml file is placed in the <INSTALL_DIR>/extensions directory, it is not getting used while building the EAR.
Solution: Place the edited weblogic.xml in the <INSTALL_DIR>/extensions/<package-name>/ directory where <package-name> is the application name, for example, smcfs.

Defect ID	213382
Case ID	00143722
Description	When a user calls the getOrderDetails API and sets the dynamic template of the getOrderDetails API using the file name of the template, the system throws “ClassCastException”.

Defect ID	213388
Case ID	00143772
Description	If an API template is extended and placed under the <INSTALL_
DIR>/extensions/global/template/api directory, the extended API template is not being used by the application.

Solution: The application has been enhanced to use the extended API templates that are placed under the <INSTALL_DIR>/extensions/global/template/api directory.
Defect ID	213790
Case ID	00145939
Description	The Selling and Fulfillment Foundation: Upgrade Guide must be updated with additional LONG columns that have been changed to CLOB.
Solution: The requisite information has been included in the section, "Post-Migration Selling and Fulfillment Foundation Preparation Tasks", in the Selling and Fulfillment Foundation: Upgrade Guide.

Defect ID	213833
Case ID	00144243
Description	In the windows environment, if some database extension XML is placed in the <INSTALL_DIR>/extensions/global/entities directory and dbverify utility is run, the dbverify does not pick the database extension XML.
Defect ID	214022
Case ID	00144336
Description	When a user migrates from Release 7.5 to Release 8.5, if Oracle database is used and the property NLS_LENGTH_SEMANTICS is set to CHAR, while running dbverify utility, unnecessary alter scripts are getting generated for setting default values of the table columns.
Defect ID	214103
Case ID	00145830
Description	When LDAP authentication is configured, the first attempt to log in to the application fails, whereas the successive attempts pass through
Defect ID	214243
Case ID	00143772
Description	The Selling and Fulfillment Foundation: Customizing APIs Guide must be updated with information about template set in setAPItemplate.
Solution: The requisite information has been added to the section, “Defining and Deploying a Static Template for Output XML”, section, “Defining and Deploying a Dynamic Template for Output XML”, and section, “Sequence of Precedence for Output XML Templates” in the Selling and Fulfillment Foundation: Customizing APIs Guide.

Defect ID	215371
Case ID	Internal
Description	The Selling and Fulfillment Foundation: Installation Guide and the Selling and Fulfillment Foundation: Customization Basics Guide must be updated with information about weblogic.xml is not getting picked from the extensions folder.
Solution: The requisite information has been added to the section, "Setting Up WebLogic to Use HTTP In-Memory Session Replication" in the Selling and Fulfillment Foundation: Installation Guide and section, "Preparing the Development Environment on WebLogic" in the Selling and Fulfillment Foundation: Customization Basics Guide.

Defect ID	215434
Case ID	Internal
Description	The Selling and Fulfillment Foundation: Customization Basics Guide must be updated with information about extend output XSLs files.
Solution: The requisite information has been added to the section, “Building Resources Extensions" in the Selling and Fulfillment Foundation: Customization Basics Guide.

Defect ID	215640
Case ID	Internal
Description	The Selling and Fulfillment Foundation: Customizing APIs Guide must be updated with information about extend output XML files.
Solution: The requisite information has been added to the section, “Extending an Output XML Template” in the Selling and Fulfillment Foundation: Customizing APIs Guide.

Hot Fix ID	8.5-HF6
Defect ID	182802
Case ID	Internal
Description	The application uses a third-party API to display graphs or charts. After a chart is displayed by the application using the third-party API, a part of the heap memory is never cleared, and is unavailable to the application. This occurs because the third-party API does not release the HTTP response object.
 
 Solution: The application has been enhanced to pass a lightweight  java.io.ByteArrayOutputStream object to the third-party API.
Defect ID	208062
Case ID	00123166
Description	When a user performs the following sequence of actions in an Internet Explorer browser, the “Service Details” screen is not displayed properly. It is displayed only for a short period:
1.	Logs in to Sterling Business Center.
2.	Associates the Delivery service or Provided service with the item, and saves it
3.	Looks for the item.
4.	In the “Item Details” screen, clicks the “Manage Delivery Services” or “Manage Provided Services” or “Manage Return Pickup Services” hyperlink.
5.	Selects the appropriate check box for any of the associated service.
Defect ID	210231
Case ID	00134904
Description	The Selling and Fulfillment Foundation: Upgrade Guide must be updated with information that the Extended XSL files are not getting copied while migrating from Release 7.9 to Release 8.5
Solution: The requisite information has been included in the section, "Before History and Transaction Migration", in the Selling and Fulfillment Foundation: Upgrade Guide.
Defect ID	210307
Case ID	00133220
    Description 	When the manageVendor API is called to delete an existing vendor, the manageVendor API does not delete the organization modeled as vendor, even if the operation is passed as DELETE.

Defect ID	210428
Case ID	00135506
Description	The Selling and Fulfillment Foundation: Upgrade Guide must be updated with information that the relative path of a template in not updated while migrating from Release 7.9 to Release 8.5
Solution: The requisite information has been included in the section, "Before History and Transaction Migration", in the Selling and Fulfillment Foundation: Upgrade Guide.

Defect ID	210768
Case ID	00131150
    Description 	The Java Message Service (JMS) which drops messages into an MQ Queue through the JMS Sender service component takes time to generate message ID. The message ID that is generated contains the Internet Protocol (IP) address along with a unique number. Whenever a message ID is generated the system looks for the IP address, because of which delay occurs.

Defect ID	211132
Case ID	00138159
Description	The Selling and Fulfillment Foundation: Customizing APIs Guide must be updated with information about extend output XML files.
Solution: The requisite information has been added to the section, “Extending an Output XML Template” in the Selling and Fulfillment Foundation: Customizing APIs Guide.

Defect ID	212211
Case ID	00140691
Description	The Selling and Fulfillment Foundation: Installation Guide must be updated with information that the supported Oracle configurations are either single-node, or Real Application Clusters (RAC) 2-node.
Solution: The requisite information has been included in the section, “Technical Stack Matrix” in the Selling and Fulfillment Foundation: Installation Guide.
Defect ID	212700
Case ID	00142403
    Description 	The buildWSUtils.xml file generates the folder name as 3.0 instead of 5.0 for the entities jar location.
Defect ID	212707
Case ID	00142445
    Description 	When the getItemListforOrdering API is called for a product item, the price of the associated service item does not get computed.
Defect ID	213041
Case ID	Internal
Description	The item configurator tables are configured for both the Transaction schema and the Master schema in Release 9.0. But in Release 8.5 the item configurator tables are configured for only the Transaction schema. Because of this mismatch, the upgrade from Release 8.5 to Release 9.0 fails.
 
 Solution: The configuration has been modified such that the item configurator tables will be configured for both the Transaction schema and the Master schema. 
Defect ID	213187
Case ID	Internal
    Description 	The plist sent to the iPhone applications are not UTF-8 encoded.
Defect ID	213212
Case ID	00144162
Description	When a user performs the following sequence of actions, the MINE_PRODUCTIVITY agent throws an "ORA-00933: SQL command not properly ended" error message:
1.	Configures the Productivity Type details, ensuring that no Equipment Type is associated under the "Equipment Types" tab. 
2.	Configures the MINE_PRODUCTIVITY agent.
3.	Creates a Move Request and releases it.
4.	Completes the Move Request task.
Note: A user must ensure that the Task Type has an “Equipment Type” configured, and on completing the task the EQUIPMENT_ID should be stamped in the YFS_TASK table.

Defect ID	213502
Case ID	Internal
Description	When a user performs the following sequence of actions, the count task type is configured as "Suggest multiple tasks and allow users to choose":
1.	Creates a count request for a zone and adjusts the inventory in at least three locations of that zone.
2.	Releases the count request.
Count tasks are created.
3.	Logs in to the Sterling Mobile Application.
4.	Navigates to the “Count” screen.
5.	Clicks “Accept” tasks.
6.	Selects a task from the suggested tasks list.
The system displays the “No open tasks” message.

Defect ID	213513
Case ID	Internal
Description	When a user performs the following sequence of actions, the SHIPMENT_PICKED event is not invoked:
1.	Creates a shipment with two lines, L1 and L2. 
Two tasks, T1 and T2, are associated with each shipment. 
2.	Creates a wave.
3.	Assigns a lane.
4.	Releases the wave.
5.	Completes T1.
6.	Navigates to the “Shipment Details” screen and clicks the “Order Number” hyperlink. The “Order Details” screen is displayed 
7.	Ensures that the quantity of L2 is 0 and clicks “Save”. 
The order lines get cancelled and the shipment execution status in the “Shipment Detail” screen is displayed as "Pick Completed", but the SHIPMENT_PICKED event of the COMPLETE_TASK transaction is not invoked.

Hot Fix ID	8.5-HF5
Defect ID	209340
Case ID	00128481
    Description 	Whenever a user modifies the yfsdatatypemap.xml file placed under “INSTALL_DIR/extensions/global/template/resource” directory, and on running the command deployer.cmd/deployer.sh -t resourcejar, the system does not incorporate the modified file.

Defect ID	208870 
Case ID	00126661
 Description	When a user calls the getFulfillmentOptionsForLines API, it does not honor the following scheduling rules:
•	Ship Complete
•	Line Ship Complete
•	Ship From Single Node
•	Line Ship from Single Node

Also, the findInventory API provides inconsistent results, if the “Line Ship from Single
Node” constraint is enabled in the scheduling rule. 

Defect ID	209743
Case ID	00131673
Description	When a user configures the Distribution Group with more than 500 nodes, and runs the Real-Time Availability Monitor agent, the alerts raised for the first 500 nodes contain the correct inventory picture, whereas the alerts raised for the remaining nodes contain an incorrect inventory picture. 
Defect ID	209964
Case ID	00134075
Description	The Selling and Fulfillment Foundation: Installation Guide must be updated with information that Selling and Fulfillment Foundation supports both Oracle 10g and 11g on either Single node or 2 Node RAC environment.
Solution: The requisite information has been included in Section 5.2.3, “Using an Oracle Database Server” and Section 6.5.3, “Using an Oracle Database Server (Windows)” in the Selling and Fulfillment Foundation: Installation Guide.

Hot Fix ID	8.5-HF4
Defect ID	199910,199913, 203200
Case ID	Internal
Description	A new entity API is required for the Inventory Alert table.

Solution: A new manageInventoryAlerts API has been included in the application. For more information about the manageInventoryAlerts API, refer to the corresponding section in the Sterling JavaDocs. 
In addition, the DISTRIBUTION_RULE_ID field and the IS_DEFAULT_DISTRIBUTION_GROUP field have been added to the YFS_INVENTORY_ALERTS table. The manageInventoryAlerts API will invoke the same event as the Real-Time Availability Monitor agent when a create or update operation is successful.
•	The manageInventoryAlerts API will update the IS_DEFAULT_DISTRIBUTION_GROUP field in the YFS_INVENTORY_ALERTS table to “N” instead of the Real-Time Availability Monitor updating this field to “Y”.
•	From the output of the event, the user will be able to differentiate between the event raised by the Real-Time Availability Monitor and the manageInventoryAlerts API by using the value of the “IsDefaultDistributionGroup” attribute. If the record was inserted by the manageInventoryAlert API, the value of the “IsDefaultDistributionGroup” attribute will be passed as “N”. A blank value or “Y” indicates that the record was updated or created by the Real-Time Availability Monitor.
•	DistributionRuleId is a mandatory field for all the operations that use the manageInventoryAlerts API.

Defect ID	199928
Case ID	Internal
Description	The order lines get scheduled instead of backordered, when a user creates an order in which the Requested Cancel Date (RCD) is less than the Requested Ship Date (RSD) at the order header level, and the RCD and RSD are not passed at the order line level.
Defect ID	207693
Case ID	00121788
Description	The Selling and Fulfillment Foundation: Customizing APIs Guide must be updated with information about extending an output XML files.
Solution: The requisite information has been added to the Section, “Extending an Output XML Template” in the Selling and Fulfillment Foundation: Customizing APIs Guide.

Defect ID	208218
Case ID	00126662
Description	The extended template for Rich Client Platform is not getting picked from the <INSTALL_DIR>/extensions/global/template/< pluginID >/< formID >/namespaces folder.
 
 Solution: The template extensions will be picked from the
INSTALL_DIR/extensions/global/template/<pluginID>/<formID>/namespaces/<template_name>.xml.

Defect ID	208315
Case ID	00116038
Description	When a user changes the header level attribute of a shipment having bundle items and if the shipment has been created for an order that has workorder, the changeShipment API throws "Either Work Order Key or Work Order Appointment Key incorrect" error message.
Defect ID	208424
Case ID	00127356
Description	In Business Center, when a user adds provided services for an item, in the “Service Search” pop-up window of the “Manage Provided Services” screen, the provided services that has the "Is Return Service" attribute checked are disabled.

Defect ID	208729
Case ID	00128581
Description	The dbverify script does not generate the SQL scripts when an extension XML is placed under the <INSTALL_DIR>/extensions/global/entities folder.

Defect ID	208903
Case ID	Internal
Description	In 18F WMS system test scenario, the outbound execution related queries on YFS_TASK table take a long time to execute.

Solution: Two new indexes have been added to the task table.

Hot Fix ID	8.5-HF3
Defect ID	203566
Case ID	Internal
Description	Attempts to use PLT_DB_COLONY result in an exception with the PLT058 error code.

Solution: A new column “STATUS” has been added to table PLT_DB_COLONY. If status of this colony is not null, any attempt to use that colony will result in exception with error code PLT058.
Defect ID	203716
Case ID	Internal
Description	The system responds slowly when a user attempts to view the inventory for a known receipt during an inbound process. This is because the database views for fetching the inventory picture are not tuned to handle Receipt as the input criteria.

Defect ID	205068
Case ID	Internal
Description	An error message "The statement is too long or too complex" error message is thrown by the system, when a user performs putaway of a preassigned task in a system or load test scenario.
Defect ID	206390
Case ID	Internal
Description	While running the 18F WMS system test scenario, most of the pick users fail with 952 errors.

Defect ID	206602
Case ID	Internal
Description	If the input XML of the manageWave API contains ComplexQuery as a child element, in such scenario the manageWave API layer throws a security exception error.
Defect ID	208054
Case ID	Internal
    Description	The security vulnerability issue with respect to online help needs to be resolved.

Hot Fix ID	8.5-HF2
Defect ID	162863
Case ID	Internal
Description	In the “Group Details” screen of the Applications Manager, the Warehouse Management Permission tab is displayed twice.
Defect ID	192457
Case ID	Internal
Description	In the “Organization Details” screen pertaining to a node in the Applications Manager, duplicate reason code values are getting populated in the “Inventory Adjustment Reason Codes” drop-down list.
Defect ID	192948
Case ID	Internal
Description	When an enterprise user manifests a container belonging to a node of a different colony, the application does not display the manifest number as the default in the “Add To Manifest” screen in the Sterling Warehouse Management System.
Defect ID	194010
Case ID	Internal
Description	An “Invalid Shipment” exception is thrown when starting a new receipt for a shipment that is in the Receipt Closed status.
Defect ID	196530
Case ID	Internal
Description	An OutOfMemoryError occurs when the createBatchForReferences API is invoked with a template in which the TaskReferences element is placed as a child to the Batch element.
Defect ID	197616
Case ID	Internal
Description	In the “Resource Planning Details” screen in the Sterling Warehouse Management System, the table column header displays "&nbsp;" for the first column. The table column header must be blank.
Defect ID	198100
Case ID	Internal
Description	When counting an existing LPN or a new LPN, a null pointer exception is thrown if a user skips the LPN scan in the “Count Criteria” screen in the Sterling Mobile Application, but scans the LPN in the “Inventory” screen.
Defect ID	199093
Case ID	Internal
Description	On clicking the “Index of all Tables and Views” link in the “Entity Relationship Diagram” homepage, a “Page Not Found” error message is displayed.
Defect ID	199191
Case ID	Internal
Description	The recovery process for the Catalog Search Index Build agent does not work. When an error occurs during the index build process, and the index trigger goes into error status, the Catalog Search Index Build agent cannot reprocess the search index trigger. 

Solution: Create a new search index trigger. 
Defect ID	199251
Case ID	Internal
Description	Context-sensitive help is not working for the following screens in the Sterling Warehouse Management System:
•	Shipment Profile List
•	Define Standard Capacity
•	Resource Planning
Defect ID	199267
Case ID	Internal
Description	Context-sensitive help is not working for the “Print” dialog box in the “Print SKU” Labels screen in the Sterling Warehouse Management System.
Defect ID	199399
Case ID	Internal
Description	Appendix B, "Menu-Level Customization of the Mobile Application" of the Selling and Fulfillment Foundation: Mobile Application User Guide is not available in the Local Documentation Library.
Defect ID	200586
Case ID	Internal
Description	In the “Customer List” panel of the “Customer Search” dialog box in Business Center, if the records span across multiple pages, and you navigate to the next page, the list of customers displayed in the subsequent pages is always the same as that displayed on the first page.
Defect ID	200854
Case ID	Internal
Description	In the “Add Items to Price List” screen in Business Center, if you click either “Add All Items in Search Results” or “Add All Items in Category”, only the items displayed in the current page are added to the price list. 
Defect ID	200892
Case ID	Internal
Description	In the “Index List” panel of the “Item Catalog Index List” screen in Business Center, search indexes generated for seller organizations other than the one that is being administered by you are also displayed.
Defect ID	201023
Case ID	Internal
Description	If you are using Microsoft Internet Explorer, and you click “Show Price” in the “Test Pricing” screen in Business Center, the Line Charges/Discount Breakup details are not displayed under the “Pricing Results” panel.
Defect ID	201046
Case ID	Internal
Description	While viewing the “Price List Summary” screen in Business Center, an exception may be displayed if the server does not respond in time.

Solution: Reload the Price List Summary screen.
Defect ID	201069
Case ID	Internal
Description	When building an EAR file with Web services on IBM WebSphere 6.1, the system throws a “NoClassDefFoundError”.
Defect ID	201079
Case ID	Internal
Description	The copyPricelist throws an “ORA-12899: value too large for column” error when trying to copy price lines, and the managePricelistHeader throws an “ORA-12899: value too large for column” error when adding price list lines for the items in the catalog. These  errors are caused only when the length of the primary key exceeds 24 characters.
Defect ID	201092
Case ID	Internal
Description	The “Wave Summary” screen in the Sterling Warehouse Management System blanks out during a high concurrency scenario in a warehouse because the query on the database times out.
Defect ID	201170
Case ID	Internal
Description	When calling the syncLoadedInventory API with InsertInventoryItem set to “Y”, the system may throw an error because the generated InventoryItemKey may exceed 24 characters.
Defect ID	201171
Case ID	Internal
Description	When assigning attributes and attribute values to a category, the system may throw an error for child categories and items if the generated primary keys exceed 24 characters. 
Defect ID	 201547
Case ID	Internal
Description	On releasing a wave, when some outbound tasks already exist from the same source for the same item, multiple inventory records get created with different inventory statuses, one of which has blank inventory status. This will show incorrect pend out quantity in the “Location Inventory” screen in the Sterling Warehouse Management System.
Defect ID	201574
Case ID	Internal
Description	When the adjustment reason code has location preference (adjustment sequence of locations) associated to it, and one of the locations in the sequence does not have the inventory, negative adjustment causes inventory picture mismatch between the Warehouse Management System and the Order Management System because the Order Management System-side inventory picture gets updated wrongly. Inventory audits are also wrong.
Defect ID	201648
Case ID	Internal
Description	An error message is displayed if you enter a description containing more than 100 characters in the following boxes in Business Center:
•	In the “Coupon Description” box in the “Coupon Summary” screen.
•	In the “Pricing Rule Description” box in the “Pricing Rule Summary” screen.
•	In the “Long Description” box in the “Primary Information” screen of an item.
•	In the “Long Description” box in the “Add Asset” dialog box.
•	In the “Long Description” box in the “Asset Detail” area of the “Assets” screen.
Defect ID	201651
Case ID	Internal
Description	After a service is created with an effective end date, you cannot use a calendar to select a new effective end date beyond the original effective end date. 
Defect ID	201745
Case ID	Internal
Description	A node user cannot view the alerts pertaining to any other node even if the user has access to those nodes.
Defect ID	202025
Case ID	Internal
Description	You cannot deploy two EAR files of Selling and Fulfillment Foundation, Release 8.5 on one application server.
Defect ID	202599
Case ID	Internal
Description	When running on DB2, the Person Info Purge agent may throw a SQL exception.
Defect ID	202796
Case ID	Internal
Description	When the new Data Access Policy is enabled in the Applications Manager, a node user cannot perform the following tasks:
•	Manual count using the Sterling Mobile Application.
•	Create count request across enterprises in the Sterling Warehouse Management System.
Defect ID	203118
Case ID	Internal
Description	When running on DB2, the Shipment Purge agent throws an SQL exception.
Defect ID	203145
Case ID	Internal
Description	When the getUserHierarchy API is called for a user with a team, the server goes into an infinite loop.
Defect ID	203270
Case ID	Internal
Description	Section 2.1, “Technical Stack Matrix” and Table 2-3, “Supported Database Tier” of the Selling and Fulfillment Foundation: Installation Guide state that Oracle is supported on 2-node and 3-node configurations. This is incorrect. Oracle is supported only on 2-node configurations.
Defect ID	204064
Case ID	Internal
Description	The system responds slowly when a user attempts to view serial-tracked inventory. This is because the getNodeInventory API fetches records for both serial-tracked inventory and non-serial-tracked inventory by firing a complex database query and cropping the results to display only the serial-tracked items.
Defect ID	204126
Case ID	Internal
Description	Table 2-9, “Supported Operating Systems” of the Selling and Fulfillment Foundation: Installation Guide lists Windows 2008 and Windows Vista as the supported operating systems for installing the Rich Client Platform (RCP). This is incorrect. Windows XP and Windows Vista are the supported operating systems.
Defect ID	204386
Case ID	Internal
Description	When the receiving task is performed using the Sterling Mobile Application, and a user receives a case, the system throws an "Invalid XML Returned from Host" error message because the Sterling Mobile Application sends a malformed request to the server.
Defect ID	204902
Case ID	Internal
Description	The Sterling Warehouse Management System: Configuration Guide must be updated with information about the tasks that an Enterprise user cannot perform.
Solution: The requisite information has been added to Section 15.3, "Configuring Users" of the Sterling Warehouse Management System: Configuration Guide.
Defect ID	205066
Case ID	Internal
Description	When an enterprise consumes inventory from vendors, on releasing a wave containing shipments belonging to the enterprise, the same LPN is suggested for tasks of type Replenishment or Outbound Pick.
Defect ID	205087
Case ID	Internal
Description	When the new Data Access Policy is not enabled, in the Sterling Warehouse Management System, a node user is able to select another node and view the transactions in it.
Hot Fix ID	8.5-HF1
Defect ID	203626
Case ID	Internal
Description	The Web UI Framework’s backend must be enhanced with the capability to support requests from an iPhone client.
Solution: The Web UI Framework's back-end logic has been enhanced to handle requests from an iPhone client. To enable requests from an iPhone client, utility methods such as getPlistFromXML and getXMLFromPlist have been provided in the "SCPlistXmlUtils" class for converting property list (Plist) files to XML and XML to Plist. 
For Apache Struts action, the SCUIPlistXAPIMashupAction class and the SCUIPlistXAPIAggregatorMashupAction class are provided to invoke XAPIs for handling Plist input from iPhone clients.