Hot Fix Release Notes
	Product	Sterling Multi-Channel Fulfillment Solution, 8.0
	Date	Friday, March 12, 2010
List of Defects Addressed
Hot Fix ID	8.0-HF70
Defect ID	214148
Case ID	00145831
    Description	When a user calls the findInventory API with mergeNode in the input XML, the delivery date in the interaction element of the output XML does not get populated. 

Defect ID	210220
Case ID	00132600
    Description	When payment processing is done in asynchronous mode, and refunds are processed on a paid Sales Order, the system creates an additional CHARGE record in YFS_CHARGE_TRANSACTION table.
Defect ID	213343
Case ID	00141257
Description	In Oracle 10g, if NLS_LENGTH_SEMANTICS is set to CHAR, then the number of bytes per CHAR varies on the encoding used. If an encoding is used for which the number of bytes per CHAR is more than 4, dbverify generates a lot of unnecessary alter scripts.

	Solution: A new property in the jdbc.properties "dbverify.Oracle.numberOfBytesPerChar=" has been exposed. If NLS_LENGTH_SEMANTICS is set to CHAR, set this property to the number of bytes used per character by the encoding used in database. By default, the value used is 4.

Hot Fix ID	8.0-HF69
Defect ID	209325
Case ID	00128252
Description	The supported version of the BEA WebLogic Application server is incorrectly mentioned as 10.x in the Sterling Multi-Channel Fulfillment Solution Installation Guide.
Solution: The correct version of the BEA WebLogic Application Server has been included in Table 2-2, "Supported Application Server Tier" in Chapter 2, "System Requirements" of the Sterling Multi-Channel Fulfillment Solution Installation Guide.
Defect ID	210209
Case ID	00132696
    Description	When a user invokes the confirmShipment API from the node that has initiated the Physical Count process, the system throws a generic YFSException without any error description, instead of an YFCException with an error code.
Defect ID	211027
Case ID	00132514
Description	When a user performs the following sequence of actions, the order line moves to the “Scheduled” status instead the “AwaitingChainedOrderCreation” status:
1.	Creates a Sales Order. 
2.	Schedules the order
The order moves to the “Scheduled” status (In a Drop Ship scenario the order goes to the “Awaiting Chained Order Creation” status.)
3.	Implements the YFSGetAvailabiltyCorrectionsForItemListUE user exit.
4.	Adds a new line to the order.
5.	Schedules the order. 
The new line that is added goes to “Scheduled” status.
Defect ID	212234
Case ID	00138344
Description	When a user performs the following sequence of actions, the system throws a null pointer exception:
1.	Implements the orderRepricingUE user exit.
2.	Extends the orderRepricingUE user exit template to include the <LineTaxes> element.
3.	Creates a Sales Order.
4.	Moves the Sales Order to “Shipped” status.
5.	Creates a return order for the Sales Order created in Step 3 such that the order lines in the return order contains the tax information.	
Defect ID	212583
Case ID	00135667
Description	When a user implements the beforeCreateMoveRequestUE user exit as a service, uses the XSL to transform the input of the createMoveRequest API, and releases the wave to enable the creation of replenishment for the wave, the system displays an out-of-memory error message.
Defect ID	213111
Case ID	00140799
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.
2.	Schedules the order 
In a Drop Ship scenario, the order goes to the “Awaiting Chained Order Creation” status. 
3.	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.
Demand for the substitute item is created.
4.	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.

Hot Fix ID	8.0-HF68
Defect ID	207888
Case ID	00123121
Description	The cache for the YFS_SOURCING_RULE_HDR and YFS_SOURCING_RULE_DTL tables does not get disabled even after the tables are disabled in the “customer_overrides.properties” file.
Defect ID	208768
Case ID	00121496
Description	In the Sterling Mobile Application, the modified JSP files placed in <INSTALL_DIR>\repository\eardata\yantra\war\extn\rf\wms\count\<jsp files> are not getting picked. Instead the system picks up the out-of-the-box JSP files.

Defect ID	212127
Case ID	00135663
Description	When a user performs the following sequence of actions, system throws a null pointer exception:

1.	Creates a Forward Pick location and a Bulk location. 
2.	Dedicates the Forward Pick location for an inventory.
3.	Adjusts inventory for only the Bulk location.
4.	Creates a Replenishment strategy from the Bulk location to the Forward Pick location.
5.	Implements the WMSOverridePickLocationAssignmentUE user exit.
6.	Creates a shipment for the inventory present in the Bulk location.
7.	Creates a wave, and includes the shipment in this wave.
8.	Calls the releaseWave API to release the wave.

Defect ID	210319
Case ID	00129953
Description	If a cursor is not set on any of the columns in a table either programmatically or manually, when the table viewer UI is updated programmatically, a null pointer exception error is thrown at the YRCTableNavigationController.setCursorSelectionTheme() method.

Hot Fix ID	8.0-HF67

Defect ID	200358
Case ID	Internal
Description	When an enterprise inherits its configuration from another enterprise, the Freight Terms are not inherited properly if a user tries to add a container to the manifest.
Defect ID	209279
Case ID	00130273
Description	When a user performs the following sequence of actions, the Organization Code in the Supply element in the input of the YFSGetAvailabilityCorrectionsForItemListUE user exit is replaced with the Organization Code of the Item element instead of the Inventory Organization Code of that item, where the supply is available:

1.	Creates ORG1 and ORG2, which are Inventory as well as Catalog organizations. 
2.	Creates two nodes each for both the organizations, for example, N1 and N2 for ORG1, and N3 and N4 for ORG2.
3.	Creates another organization, SELLER1, which is the parent of ORG1 and ORG2, and whose Inventory organization and Catalog organization is ORG1.
4.	Configures ORG1 to consume the inventory of ORG2.
5.	Creates two different items, for example, I1 and l2 for ORG1 and ORG2 with the same Global Trade Item Number.
6.	Adjusts the inventory such that 1 quantity each of the item l1 is present in the N1 and N2 nodes, and 1 quantity each of the item l2 is present in the N3 and N4 nodes.
7.	Implements the YFSGetAvailabilityCorrectionsForItemListUE user exit such that the output is similar to the input.
8.	Creates two Distribution Groups, DG1 consisting of the N1 and N2 nodes of ORG1, and DG2 consisting of the N3 and N4 nodes of ORG2.
9.	Configures the Sourcing Rules for SELLER1 such that DG1 is the first sequence and DG2 is the second sequence.
10.	Calls the findInventory API and checks the input of the YFSGetAvailabilityCorrectionsForItemListUE user exit.
The YFSGetAvailabilityCorrectionsForItemListUE user exit is called twice. In the first run of the YFSGetAvailabilityCorrectionsForItemListUE user exit, the two supplier elements for DG1 have the Organization Code as ORG 1, but in the second run of the YFSGetAvailabilityCorrectionsForItemListUE user exit, the Organization Code is replaced by SELLER1.
Defect ID	210270
Case ID	00130027
Description	The getATP API does not get the correct inventory picture when the Vendor Manage Inventory functionality is enabled.

	Solution: If a ship node is specified or “ConsiderAllNodes” attribute is passed as Y in the input XML of the getATP API, and the Vendor Manage Inventory functionality is enabled, the getATP API gets the correct inventory picture.
Defect ID	210290
Case ID	Internal
Description	When a user performs the following sequence of actions, the system displays the “Class Cast Exception” error message while reprinting the Carrier Label:
1.	Creates a shipment with a valid Frieght Term and Carrier, for example, "PREPAID" and FedEx Ground respectively.
2.	Implements the YCSreprintCarrierLabelUserExit user exit to override the Pierbridge connection parameters and Shipment Account number.
3.	Packs the shipment and adds the containers to manifest.
4.	Reprints the Carrier Labels, that is, both the Forward and Return Labels.

Hot Fix ID	8.0-HF66

Defect ID	209472
Case ID	00130284
Description	When a user performs the following sequence of actions, the system does not convert the user's locale time into installation locale time, and displays incorrect results:
1.	Logs in as a user whose locale is different from the installation locale.
2.	Enters the date as the search criteria, for example, Order Date, or Requested Ship Date, or Requested Delivery Date.
3.	Clicks Search.

Defect ID	209477
Case ID	00127524
Description	When a user logs in to the application after a timeout, the system gets locked, but the client stays open behind the scenes. If the user wants to reuse the client, system prompts for re-entering the password, and if the user enters a wrong password, the client hangs up and stops responding.

 Solution: If a user enters a wrong password to log in again, the client does not hang up, but it displays login dialog box indicating that the password is invalid.

Defect ID	200483
Case ID	00048432
Description	A user should be able to invoke routing logic externally. 

 Solution: A new user exit, OMPProcessRoutingExternallyUE, has been introduced to call routing logic externally. The corresponding fixes have been made in the findInventory API and other promising or scheduling APIs for them to be able to handle calls to the OMPProcessRoutingExternallyUE user exit.

Hot Fix ID	8.0-HF65
Defect ID	191977
Case ID	00039217
Description	When a user performs the following sequence of actions in the Serial Entry pop-up window while kitting, the system always displays the “Remaining Serials” value as 1: 
1.	Creates a work order to kit more than 1 unit of the kit item.
1.	Confirms the work order.
2.	Enters the total quantity of the work order as the quantity being confirmed.
3.	Clicks “Save”.
Then Serial Entry pop-up window is displayed, to scan the serial of the kit item, but it shows the remaining serials as1 and the scanned serials as 0. After scanning the serial for kit, the Serial Entry pop-up window is displayed to scan the serial of the component items, when the serials for component items have been scanned, the Serial Entry pop-up window is displayed to scan the serial for kit item.

Solution: The application has been enhanced to display the actual serial number, the total quantity that has been confirmed as entered by the user, and the scanned serial number as 0 in the Serial Entry pops-up window while scanning the kit item and the value of remaining serials is decreased by 1 and value of scanned serials is increased by 1.

Defect ID	206824
Case ID	00118795
 Description	The SQL that is generated based on the input XML throws a syntax error, if a user enters search criteria to search for an order.
Defect ID	207753
Case ID	00124251
Description	When a user performs the following sequence of actions, the “validatebuttonclick()” method is called twice in the “Payment Method” screen: 
1.	Launches Customer Order Management Client.
2.	Creates an order.
3.	Selects the “Change Payment Method” from the related task.
4.	Clicks “Add payment method” button.
5.	Selects the payment method as “Check”.
6.	Using the extensibility tool, marks “Validation required” as “Yes” for the “Apply” button.
7.	Saves the changes, and repeats steps 2 to 5.
8.	Clicks “Apply”.

Defect ID	208292
Case ID	00122292
 Description	When a user performs the following sequence of actions, the bundle parent line does not display the correct quantity: 
1.	Create a sales order in a drop ship scenario.
2.	Schedules the order. 
Order goes into the Awaiting Chained Order Creation status.
3.	Creates a chained order using the createChainedOrder API. 
A drop ship PO is created.
4.	Schedules and releases the PO.
5.	Cancels some quantity from the PO.

Defect ID	208466
Case ID	00127797
 Description	The InputXML and OutputXML links of Java Docs do not work for the generateSerialNumbers API and getSerialNumbers API.

Defect ID	208627
Case ID	Internal
 Description	The dbverify script generates unnecessary alter scripts in the IndexDrops, TableChanges, and IndexAdds SQLs in Oracle 11g.

Defect ID	209116
Case ID	00122279
Description	The YFS_Location table should be extended by adding a column to store replenishment quantity for the SKU.

 Solution: The application has been enhanced, a new button ‘Extended Attributes’ has been added in the “Location Details” screen. 
  For more information about extending attributes, please see Section 4.1.1 of the Sterling Multi-Channel Fulfillment Solution:Customization Guide.

Defect ID	209186
Case ID	00129406
Description	When a user calls the getItemListforOrdering API for an Item, YFSGetExternalPricesForItemListUE user exit is not called.

 Solution: The application has been enhanced now the YFSGetExternalPricesForItemListUE user exit will get called.

Hot Fix ID	8.0-HF64

Defect ID	194468
Case ID	Internal
Description	When a user performs the following sequence of actions, the Receiving Node and Ship Node displays a blank value: 
1.	Creates an enterprise with only one Child Organization.
2.	Logs in to the Sterling Multi-Channel Fulfillment Solution application as an enterprise user and navigates to Inbound.
3.	In the “Inbound” screen that is displayed, clicks ‘Create Shipment’.
Also, attempt to create a shipment from the “Outbound” screen.
Defect ID	206207
Case ID	00115694
 Description	In the Draft order status, when a user calls the changeOrder API to change the order quantity and UOM for an order line, in such scenario the ‘PricingQty’ and ‘Line Total’ becomes zero for an order line.
Defect ID	206543
Case ID	Internal
 Description	When a user creates an adjustment invoice for an Orderline after it is shipped and invoiced, the “Adjustment Invoice Details” screen does not show the line for which the adjustment invoice was created. 
Defect ID	206548
Case ID	Internal
 Description	When the reserveItemInventory API is run in multithreaded mode to reduce and increase the reservation quantity of a Reservation ID created earlier, deadlocks might occur occasionally.
Defect ID	206715
Case ID	00113324
Description	When a user performs count task using mobile device, in some of the “Count” screens the location being counted is not displayed.

Solution: The application has been enhanced to provide an “INFO” button in the Sterling Mobile Application Count screen where Location being counted was not shown when a user clicks the “INFO” button. The location being counted is displayed in the Sterling Mobile Application Count screen.
Defect ID	207341
Case ID	Internal
 Description	When a user makes a change in the Carrier Org Details and saves it, the “YFS_SCAC” table is updated with an incorrect Organization Code for the Carrier that is changed.

Defect ID	207549
Case ID	00122302
 Description	When a user scans serial range for an item that is serialized in the Serial pop-up window, the system throws "Serial_Has_More_than_one_translations" error message. 

Hot Fix ID	8.0-HF63
Defect ID	187616
Case ID	00045422
    Description	The application should be able to get information about the availability from an external system. 
Solution: The application has been enhanced such that a new user exit YFSGetExternalAvailabilityUE has been introduced. The output of this user exit will be used by the system to determine the availability of the item requested in the input.
The YFSGetExternalAvailabilityUE user exit is called by the system whenever availability information is required.
A user must perform the following actions:
1.	Implement the YFSGetExternalAvailabilityUE user exit.
2.	Add a new enterprise-level property. This property will be required for being put into the yfs.properties in the following format;
<EnterpriseCode>.IsAvailabilityExternal=Y
For example, DEFAULT.IsAvailabilityExternal=Y
Add an entry for each enterprise for which the user exit is implemented in the above format.
3.	Extend the template of the findInventory API to include all the attributes required in the output template of the YFSGetExternalAvailabilityUE user exit.
Note: The consolidation of orderLineReservations will not take place, if the YFSGetExternalAvailabilityUE User Exit is implemented.
 
Defect ID	203420
Case ID	00104104
Description	When a user tries to perform the count task in the “Count Criteria” and “SKU Quantity Entry” screens, the “GO” button overlaps the “INFO” button. 

Defect ID	204043
Case ID	00052814
Description	When a user runs the manageLoad API in multithreaded mode with each thread trying to add two different shipments to the same load, multithreading is not achieved because one of the thread locks the load to which shipments are being added. In such a scenario, the other threads cannot work on the same load.
	
	Solution:  The manageLoad API has been enhanced to take the AddOnlyShipmentsToLoad flag in its input. If the AddOnlyShipmentsToLoad flag is passed as Y in the input of the manageLoad API, the manageLoad API will not lock the load and will only add the shipments to the load.

Defect ID	204905
Case ID	00105906
Description	When a task is completed by moving a single segmented inventory from an LPN or a location to another location that has Inventory Transition rules defined, the application creates an inventory mismatch between the Distributed Order Management and the Warehouse Management System.
Defect ID	206713
Case ID	00113072
Description	When a user tries to create a new count request from the “Count Result List” screen, no link is being created between the original count request and the new count request.
Solution: The application has been enhanced to pass the “OriginalCountRequestNo” and “OriginalTaskID” attributes in the input of the createCountRequest API, when the count request is being created from the “Count Result List” screen. Users can implement the “WMSBeforeCreateCountRequestUE” user exit to have the appropriate link between the original count request and the new count request being created, by prefixing the subsequent count requests with the original count request number.

Defect ID	206714
Case ID	00113070
Description	When a new count request has been created from the “Count Result” screen variance records should be deleted and variance should not be accepted.
Solution: The application has been enhanced to modify the “Variance Accepted” field of the count result records to I (Ignore) by calling the deleteCountResultRecordsForATask API. Even if a user accepts the variance for such records by mistake, the acceptVariance API has been enhanced to not accept the variance for such records.
Defect ID	207195
Case ID	Internal
    Description	When a user tries to on-board a new enterprise and models it as another existing enterprise by selecting the “Model the enterprise as existing relationship” check box, it does not display the already on-boarded enterprises, if the total number of enterprises is more than 75.

Hot Fix ID	8.0-HF62
Defect ID	203943
Case ID	Internal
Description	When the reprintCarrierLabel, addContainerToManifest, and getTrackingNoAndPrintLabel APIs are invoked, the output does not give the label image URL even if the Printer Type of the output is set to Client in the Pierbridge server.
Solution: The label fields now get populated as PierbridgeLabelURL" under the container element of the API output where applicable.
Defect ID	205042
Case ID	00108456
  Description   When a user tries installing 8.0-HF57, the HF installation fails, throwing an ORA-12899 error. This is because Dbverify does not generate the alter script correctly if NLS_LENGTH_SEMENTICS is set to CHAR in Oracle database. 
Defect ID	205718
Case ID	00109216
Description	When a user performs the following sequence of actions, the order goes to Reserved status instead of Scheduled status: 
1.	Under scheduling rules, selects the “Ship Line Complete” and “Allow Reservation During Scheduling” flags.
2.	Implements the “YFSGetAvailabilityCorrectionsUE” User Exit, such that the input XML is returned as the output XML.
3.	Creates an item with “Procurement Allowed” flag unchecked.
4.	Creates an order for 10 quantities for the item.
5.	Adjust the inventory for the item for 5 quantities.
6.	Schedules the order.
7.	Order goes to partially Backorder status.
8.	Adjust the inventory for 5 more quantities, so that the order can be fulfilled. 
9.	Schedules the order again.

Solution: Now the order gets scheduled. The implementation of the “YFSGetAvailabilityCorrectionsUE” User Exit should not change the value of the OrganizationCode attribute of the supply element passed in the input XML.

Hot Fix ID	8.0-HF61
Defect ID	204465
Case ID	00081458
Description	When a user performs the following sequence of actions, the findInventory API does not return a valid solution:
1.	Creates Org1. Sets up inventory org, catalog org, enterprise and seller. Node1 is set up under Org1.
2.	Creates Org2. Sets up the inventory org, catalog org, enterprise and seller. Node2 is set up under Org2.
3.	Sets up Org2 such that it consumes the inventory of Org1.
4.	Sets up Item1 in the catalog of the Org1 with GTIN as Item1. Unit of measure is set as EACH-1.
5.	Sets up Item 2 in the catalog of the Org2 with GTIN as Item1. Unit of measure is set as EACH-2.
6.	Calls the findInventory API for Item 2 for Org 2 at Node1.
Solution: Now, when the findIventory API is invoked it returns the Item1 from Node1.
Defect ID	204810
Case ID	00110849
Description	When a user tries to modify an extended attribute for a manifested container using the changeShipmentContainer API, the application throws the ‘YDM00281-Cannot modify some of the attributes as the container is already manifested’ exception error message.
Defect ID	205607
Case ID	00114188
Description	When the adjustInventory API is invoked with an extra space in the ShipNode attribute of the input XML, it creates a new record in the YFS_INVENTORY_SUPPLY table instead of increasing or decreasing the quantity in existing supply record.
Defect ID	205652
Case ID	00101721
Description	A user is not able to release the return order because the scheduleOrder API does not schedule an order having bundles in which the components of the bundle does not have correct ratio.
Defect ID	205885
Case ID	00113044
Description	In the “Variance Details” panel of the “Count Result Detail” screen, the “Serial No.” level does not have original location break-up.
Solution: The original location break-up has been included in the “Serial No.” level of the “Variance Details” panel.
Hot Fix ID	8.0-HF60
Defect ID	149205
Case ID	Internal
Description	The getWorkOrderList API should be able to search for the purged work orders.

Solution: A new "ReadFromHistory" flag has been provided in the input XML of the getWorkOrderList API. When this flag is set to "Y", the records from the history tables are fetched. A new "Search History" check box has been provided in "Search" screens pertaining to work orders in the Sterling Multi-Channel Fulfillment Solution Applications Console. When this check box is selected, all the purged records from the history tables are fetched. The "View Details", "Cancel", "Confirm" actions and so on are not permitted for the purged work orders.
Note: When the "ReadFromHistory" flag is set to "B", the work orders from both the current table and the history table are fetched. Currently this is supported in the back end only.
Defect ID	201841
Case ID	Internal
Description	When a user performs the following sequence of actions, the order line which has been cancelled when the SplitLine API is called to replace the Item ID, still appears in the order in backordered status:
1.	Creates an order.
2.	Schedules the order.
3.	Releases the order.
4.	Calls changeRelease API to backorder the release.
5.	Calls SplitLine API to modify the Item ID.
The SplitLine API adds an order line with different items to an order, but the original order line which has been replaced using the SplitLine API appears in the order in backordered status. This order line should not appear in the order as it has been already cancelled by the SplitLine API.
Defect ID	201916
Case ID	Internal
Description	When the Execute Collection agent is run on an SQL Server database, starting the Health Monitor registers the following YFC0003 exception error message: ErrorDescription="[NTSERV64]Column name 'YFS_CHARGE_TRANSACTION.CHARGE_TRANSACTION_KEY' is invalid in the ORDER BY clause because it is not contained in an aggregate function and there is no GROUP BY clause."

Defect ID	201919
Case ID	Internal
Description	When a user performs the following sequence of actions, the value of the TaxExemptionCertificate attribute is shown as null resent in the Database:
1.	Implements the YFSOrderRepricingUE User Exit.
2.	Calls the createOrder API, but in the createOrder XML the ‘TaxExemptionCertificate’ attribute must not be present.
3.	The CreateOrder API will invoke the YFSOrderRepricingUE, where the value of attribute is set as TaxExemptionCertificate.
4.	The output of the YFSOrderRepricingUE user exit has the TaxExemptionCertificate attribute  stamped (TaxExemptionCertificate="TEC111")
Defect ID	201922 
Case ID	Internal
Description	When a user creates an order with a certain unit price, and if the amount is pre-collected using a payment method, the application updates the “MaxChargeLimit” attribute of the payment method to the pre-collected amount even if the “UnlimitedCharges” attribute is set to “Y”. In addition, the user does not pass any value for the “MaxChargeLimit” attribute in the input XML of the payment method.
Solution: The application has been enhanced such that when an order is created with pre-collected amount, the “MaxChargeLimit” attribute will be set to zero in the payment method if the user does not pass any value for the “MaxChargeLimit” attribute, and the “UnlimitedCharges” attribute is set to “Y”.

Defect ID	202822
Case ID	00089748
Description	The getTrackingNoAndPrintLabel API should be able add containers to a manifest of the desired date.

Solution: The application has been enhanced such that the “ManifestDate” attribute has been added as an input to the getTrackingNoAndPrintLabel API. 
Therefore, even if input is not passed in the getTrackingNoAndPrintLabel API, containers will get added to current day manifest. If a particular date is passed in the input, any open manifest for that date will be searched. If open manifests are found, containers will get added to the manifest. Otherwise, a manifest will be opened for that date and containers will get added to that manifest.
Defect ID	202823
Case ID	00088051
Description	The application should be enhanced so that it enables a user to override the ShipperAccountNumber for more than once, currently when a user calls YCSshipCartonUserExit user exit to override the ShipperAccountNumber for the second time; the system throws an "Invalid Manifest Number" error message.

Solution: The application has been enhanced such that the functionality on the outside remains the same. Internally, there will be two copies of the manifest if a user tries to override the shipper account number twice.
Defect ID	204636
Case ID	Internal
Description	The Java docs are not updated in most of the YCS User Exits.
Defect ID	205044
Case ID	00111994
Description	When a user runs audit purge agent to purge records in the YFS_AUDIT table and if the number of records is greater than the 'No of records to buffer' value, then in such case some of the records will not get purged.

 Solution: This issue occurred due to incorrect ordering of the records fetched from database. As a fix, ‘ORDER BY’ primary_key has been added in the SQL query to fetch the records eligible for purging.
Defect ID	205309
Case ID	00113062
Description	The Real Time Availability Monitor (RTAM) does not raise correct alerts when supply at nodes is of INFINITE availability type. Items that are monitored are having Node Level ATP Monitor Rule selected.

Hot Fix ID	8.0-HF59
Defect ID	200309
Case ID	Internal
Description	When a user attempts to create a shipment for which neither the PRO No. nor the BOL No. is defined, the system populates the PRO No. and BOL No. fields with 0 (zero). The system then attempts to locate a matching load for this shipment, and attaches the wrong load.  
Solution: The application has been enhanced such that the confirmShipment API, the changeShipment API, and the createShipment API takes the OverrideAddnOfShipmentsToLoad flag in their respective inputs XMLs. If the OverrideAddnOfShipmentsToLoad flag is passed as ‘Y’ the system will not try to find a matching load for the newly created shipment.
Defect ID	202752
Case ID	Internal
Description	The reprintCarrierLabel API and the getFreightCharge API do not have user exits and hence cannot be used to override the connection parameters.
Defect ID	203893
Case ID	00101186
Description	In the input of the YFSGetAvailabilityCorrectionsForItemListUE some of the attributes are populated with incorrect values.
Defect ID	204139
Case ID	00024429
Description	The application should be enhanced such that it enables a user to on-board multiple enterprises. The Search icon adjacent to the “Select the Enterprise” tab should be able to display a list of all the enterprises irrespective of the number of whether the enterprises have to be on-boarded.
Solution: The application has been enhanced such that the Search icon will display a list of all the enterprises irrespective of whether they have to be on-boarded.
Defect ID	204375
Case ID	00108899
Description	The scheduleOrder is not creating a FUTURE_AUTH record in the YFS_Charge_Transaction table when the authorized amount is more than the total amount of the order.
Defect ID	204522
Case ID	00109452
Description	When a user scans a serial number that falls beyond Int datatype (Long) in the “Serial Range Enter” screen, the “ERROR INV80_040:From Serial number is greater than To Serial number” error message is displayed.
Defect ID	204527
Case ID	00100411
Description	The application should be enhanced to provide a user with an option to create count requests for all the locations either by Location option or by Aisle, Bay, or Level option.
                        However, if a value is provided for only Zone, and neither the Location option nor the Aisle, Bay, or Level option is selected, the count request should be created for all the locations under the specified zone.

Solution: The application has been enhanced to enable a user to create count requests by Aisle, Bay, or Level numbers in the “Create Count Requests For Location Range” screen. Zone ID has also been added as an optional criteria. In addition, the “Create Count Requests For Location Range” screen has been renamed as “Create Count Requests For Location Group” screen.
Defect ID	204743
Case ID	Internal
Description	When a user performs the following sequence of actions, the “Wave Summary” screen does not display the #Shipment Profiles value:
1.	Creates a shipment.	
2.	Assigns a lane and releases the wave.
3.	Creates a batch for the wave.
4.	Navigates to the “Wave Summary” screen.
Defect ID	204872
Case ID	00111042
Description	When a user tries to install Sterling Multi-Channel Fulfillment Solution 8.0-HF57 on a DB2 database, the dbverify process fails with a "java.lang.reflect.InvocationTargetException".
Defect ID	205139
Case ID	00100411
Description	Information about creating count requests for all the locations either by Location option or by Aisle, Bay, or Level option must be added to the Sterling Warehouse Management System User Guide.
Solution: The requisite information has been included in Section 14.2, “Create Count Request for Location Group", in Chapter 14, "Create Count Request Screens" and Section 15.3, “Count Request Search By Location Group”, in Chapter 15, “Count Console Screens” of the Sterling Warehouse Management System User Guide.
Defect ID	204509
Case ID	00108935
Description	When adding data to a table in the setModel() method call, the viewer.refresh() method is being called by the application. This method is used to display the images stored in the server. If an image server is not configured for any column in the table, the viewer.refresh() method need not be invoked, thus enhancing the performance of the application.
Solution: The application has been modified to call the viewer.refresh() method only if a valid image server is configured for a column in the table.
Hot Fix ID	8.0-HF58
Defect ID	197939
Case ID	Internal
Description	The application does not allow the users to connect to multiple Pierbridge instances.
Solution: The application has been enhanced such that users can connect to multiple Pierbridge instances. However, users should implement this feature through various User Exits at API level.
Defect ID	202891
Case ID	00092419
Description	The application does not move the “Parent Line” of a bundle order to “Shipped” status, even if after all the components of the bundle order have been shipped.
Defect ID	203121
Case ID	00102469
Description	When the Inventory Purge agent or Reservation Purge agent run they delete the inventory reservation records but does not raise the Reservation Change event.

Solution: The application has been enhanced such that the Reservation Purge agent and Inventory Purge agent will raise the Reservation Change event.	
Defect ID	203390
Case ID	00103299
Description	When a user performs the following sequence of actions, the “Wave Summary” screen displays the first batch number instead of the correct number of batches:
1.	Creates two shipments.
2.	Creates waves for both the shipments.
3.	Assigns lanes and then releases the waves.
4.	Creates batches for both the waves.
5.	In the “Wave Summary” screen, selects both the waves and clicks “View Details”.
6.	Clicks the Batch No. hyperlink.

Defect ID	203712
Case ID	00101259
 Description	When an agent is configured to work with the JBoss Messaging queue, the Trigger agent script triggers the agent to GET more messages into the execution queue even though the queue has more than one messages still waiting to be executed by the respective agent.

Solution: The trigger agent script will not trigger the agent to GET more messages until all the messages already present in the queue have been processed.
Defect ID	203823
Case ID	00103390
   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 YFSGetAvailabilityCorrectionsUE.
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 move to “Reserved” status, the other five quantities move to “Backordered” status. 
6.	Schedules the order again.
Defect ID	203846
Case ID	00106334
Description 	When the YFS_PERSON_INFO table is extended with multiple extended attributes, the table sometimes inserts different records for two order lines even if both the order lines contain the same “PersonInfoShipTo” attributes.
Defect ID	203891
Case ID	00105264
    Description    When the getCategoryList API is invoked and the Orderby element is passed to sort a list by CategoryID, the list gets sorted by CategoryKey. 
Solution: The application will sort a list based on the attributes passed in the Orderby element. If the Orderby element is not passed it will sort the list based on the CategoryKey.
Defect ID	204033
Case ID	00107386
Description    The application does not validate the count of the duplicate serials scanned in the “Serial” pop-up window.
                         
                        Solution: The application has been enhanced such that the valid serials scanned should only be considered.

Hot Fix ID	8.0-HF57
Defect ID	156748
Case ID	Internal
Description	When a user has been inactive for a period of time that is less than the time specified in the "yfs.reopentask.time" property, for example, if the "yfs.reopentask.time" time is set to 1 hour, and the user has been inactive for 30 minutes, the ReopenTask agent should not clear the AUTO_USER_CONSTRAINTS record for this user.
Defect ID	167810
Case ID	Internal
Description	In DB2 database a SQLException error can occur if the ReOpen Task Agent is run. This happens because the TASK_KEY column is of type CHARACTER (24) and the value being compared is an INTEGER type value in DB2.
Solution: The ‘TASK_KEY’ value will be enclosed within single quotes. The correct format will be passed in the SQL Query.
Defect ID	170341
Case ID	Internal
Description	In a DB2 environment, when a user creates two shipments in the multithread mode with the same “Ship To” and “Bill To” addresses, one of the shipments is successfully created, but the other shipment fails, and the application throws an "Invalid Bill To Address Key" error message.
Defect ID	170347
Case ID	Internal
Description	The count task slows down when it is executed through the Sterling Mobile Application.
Solution: Indexes have been added to the following tables to improve the performance of the Sterling Mobile Application:
•	YFS_Shipment
•	YFS_Count_Request
•	YFS_Count_Result
•	YFS_Task.
Defect ID	176990
Case ID	Internal
Description	The application does not plot the real-time graph of the number of messages in the JMS queue that is being monitored by the Health Monitor in the System Management Console. Only the threshold value of this queue is being plotted.
Solution: The application has been enhanced to plot both the threshold value and the number of messages in the monitored JMS queue.
Defect ID	195824
Case ID	Internal
Description	When shipments are added to a load, and the “Load Detail” screen is opened from the “List” screen, the “Load Detail” screen takes a long time to load. This is because the getShipNode API is being called for each LoadStop when it should be called either once or twice depending on the origin or depending on the destination of the load. In addition, the getShipNodeList API is called with ShipNode as blank.
Solution: The ship node will be passed in the input of the getShipNodeList API. This will reduce the time taken to load the “Load Detail” screen.
Defect ID	195834
Case ID	Internal
Description	When a user performs the following sequence of actions with more than 75 queues for an enterprise, the queue name is not displayed in the “Exception Type Details” screen. However, the database records contain the correct queue for this exception type:
1.	Creates an exception type for the enterprise.
2.	Searches a queue and assigns the queue to this exception type such that the number of the queue is 76 or higher in the searched list of queues.
3.	Closes and re-opens the exception type details screen.
Solution: The queue name will be displayed in the “Exception Type Details” screen irrespective of the order or serial number of the queue in the queue list.
Defect ID	197985
Case ID	00084762
Description	When the JBoss Messaging Service is used for JMS along with the JBoss Application Server instead of the default JBoss MQ, and the Health Monitor is run, the Health Monitor Console registers errors. In addition, the Health Monitor is unable to monitor the JMS queues, because of which the System Management Console does not display the status of the queue messages.
Solution: A new “JBoss Messaging” option has been provided in the System Management Console screen in addition to the existing “Default JBoss MQ” option. If the “JBoss Messaging” option is configured with the JBoss Application Server, the Health Monitor will not register any errors. 
Defect ID	200338
Case ID	Internal
Description	When a user performs the following sequence of actions, the application displays only the first ten characters of the Item ID in the “Product Number” field in the Packing slip, and truncates the remaining characters:
1.	Ensures that an item exists, with the Item ID containing more than ten characters.
2.	Navigates to the Outbound Shipment Console, and selects the Print option.
3.	Selects the PrintPackList service, the required printer, and the number of copies.
4.	Generates the Packing slip.
Solution: The application has been enhanced such that if the Item ID has more than ten characters, the rest of the characters will be displayed in the next line in the “Product Number” field in the Packing slip.
Defect ID	200793
Case ID	00090311
Description	Certain screens of the application display the short description of an item in the “Description” field, whereas other screens display the long description of an item in the “Description” field. This inconsistency must be rectified.
Solution: The application has been rectified such that the short description of an item will be displayed in the “Description” field of the following screens:
•	Location Inventory List
•	Location Inventory Details
•	Count Request List
•	Count Request Details
•	Count Result List
Defect ID	202624
Case ID	00100624
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 the 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 the IBA.
Solution: The application has been rectified such that the IBA will not process the demands that are in “Released” status.
Defect ID	202747
Case ID	00096978
Description	When loading the “Report Record Receipt” screen for a shipment that contains a large number of shipment lines, the application slows down. This performance issue is caused because the getShipmentDetails API is invoked multiple times for each shipment line for fetching the same result.
Solution: This issue has been fixed. When loading the “Report Record Receipt” screen, the getShipmentDetails API will be invoked for the findReceipt API and the getReceiptDetails API. However, the getShipmentDetails API will be invoked only once for one shipment line of the shipment, and not for the remaining shipment lines. Therefore, in case of large shipments, the application will exhibit better performance.
Defect ID	202881
Case ID	00102127
Description	When a user performs the following sequence of actions, the application displays an incorrect count quantity in the “Count Quantity” screen:
1.	Configures a serial-tracked item and adjusts inventory for this serial-tracked item in a location.
2.	Configures a count task type with the "Capture Inventory Attributes" option enabled.
3.	Associates the count task type configured in step 2 with a count strategy.
4.	Creates a count request for the location, and releases the count request.
5.	Logs in to the Sterling Mobile application, and navigates to the Count menu.
6.	Scans the location, item, and the serial numbers.
7.	Clicks the "Rescan Serial" button in the “Count Quantity” screen.
8.	Scans the serial numbers again.
Defect ID	203285
Case ID	Internal
Description	When a user performs the following sequence of actions, the application throws a "Scan Item/Serial" exception:
1.	Configures batch picking to use cart as the equipment.
2.	Creates a shipment for an item.
3.	Includes the shipment created in step 2 in a wave, and releases the wave. Pick tasks are created for the wave, and a batch is created for this wave.
4.	Logs in to the RF device, inducts a cart to the batch created in step 3.
5.	Navigates to the "Cart Pick" screen, and scans the cart ID. The application displays the pick task and prompts the user to pick the item.
6.	Clicks on "Exception" button without scanning the item and the quantity.
Hot Fix ID	8.0-HF56
Defect ID	200187
Case ID	00069533
Description	When the Real-Time Availability Monitor is configured, the Manage Inventory Alerts feature mandates a user to run an update SQL query on a transaction table.
Solution: This hot fix rules out a user from having to run the SQL query. The following changes in behavior are exhibited by the application:
•	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 operations that use the manageInventoryAlerts API.
Defect ID	200331
Case ID	Internal
Description	When a user performs the following sequence of actions, the application displays a “Cannot pick more than task quantity” error message:
1.	Configures the following Batch Picking Task Types: “Cart Pick”, “Pick into Case”, and “Pack While Pick”.
2.	Enters a serial number range when confirming a batch.
3.	Confirms a batch for two different ranges of serial numbers.
Defect ID	200860
Case ID	00083727
Description	When kitting a serial-tracked item and a serialized item into a kit, if an incorrect serial number is entered in the “Serial Number” field, the application does not immediately display an error message. However, the application displays a "WMS00233: Inventory does not exist or Inventory Status cannot be uniquely determined." error message at the end of the entire scanning process.
Solution: Instant validation will be performed against the output of the translateBarCode API.
Defect ID	202368
Case ID	00096803
Description	When trying to migrate the extended tables or custom tables, the Configuration Deployment Tool (CDT) displays a “NoSuchMethodException” error message.
Defect ID	202473
Case ID	00100420
Description	When a user searches for an enterprise in a search console screen with more than 21 enterprises, and from the search results, if the user selects any enterprise other than the first 21 enterprises, the application incorrectly displays the first enterprise of the search result as the default value in the search console screen.
Hot Fix ID	8.0-HF55
Defect ID	155523
Case ID	Internal
Description	When the getIntegrationErrorList API is invoked with an output template, the API does not honor the output template that is passed, and returns all the attributes.
Defect ID	161535
Case ID	Internal
Description	When a user logs in to the Sterling Supply Chain Mobile Application in the LXE MX7 device, navigates to the SORT inventory module, scans the SORT station, and presses the “Tab” key, the system does not access the sort inventory module in the LXE MX7 device.
Defect ID	163451
Case ID	Internal
Description	The “Create Count Request For Location Range” agent does not process a message if the message is inserted when the agent is processing another message.
Solution: The agent has been enhanced to process all the messages irrespective of whether the agent is processing another message when a new message is inserted.
Defect ID	168216
Case ID	Internal
Description	When a wave is cancelled because of inventory shortage for all the shipments belonging to this wave, and the number of shipments in this wave is greater than the value configured in the "yfs.cancelwave.offline.shipmentcount.greaterthan" property, the Has_Node_Exceptions Flag on all these shipments should be set to Y.
Defect ID	182880
Case ID	Internal
Description	When a user configures the application as follows, and performs cart pick using equipment, the application takes a long time to determine the target location for the outbound cart pick tasks:
•	Putaway strategy is configured for the “PACK” activity group.
•	Mix constraints are not defined for the putaway zone.
•	Putaway zone is configured for "Minimize number of locations / SKU".
•	Ensures that the configured putaway zone has inventory for items other than the items being considered for putaway.
Defect ID	184608
Case ID	Internal
Description	When a user performs the following sequence of actions, the application modifies the open header charges and taxes to zero:
1.	Ensures that a partially invoiced order exists with open header charges and taxes.
2.	Invokes the changeOrder API and cancels the open quantity.
Solution: A new “Invoice Open Header Charges/Taxes On Invoice Complete” flag has been included. If this flag is set to “true”, all the open header charges and taxes will be invoiced when the order moves to the “InvoiceComplete” status. The RecalculateHeaderTaxUE user exit will be called with InvoiceMode="ON_INVOICE_COMPLETE".
Defect ID	184623
Case ID	Internal
Description	The Sterling Distributed Order Management Configuration Guide must be updated with information about the "Invoice Open Header Charges/Taxes On Invoice Complete" check box included in the Others tab in the Financial Attributes screen.
Solution: The "Invoice Open Header Charges/Taxes On Invoice Complete" check box and its description has been added to Table 19-1, "Others Tab" in Section 19.4, "Defining Additional Payment Rules" in Chapter 19, "Configuring a Document's Financial Components" of the Sterling Distributed Order Management Configuration Guide.
Defect ID	195834
Case ID	Internal
Description	When a user performs the following sequence of actions with more than 75 queues for an enterprise, the queue name is not displayed in the “Exception Type Details” screen. However, the database records contain the correct queue for this exception type:
4.	Creates an exception type for the enterprise.
5.	Searches a queue and assigns the queue to this exception type such that the number of the queue is 76 or higher in the searched list of queues.
6.	Closes and re-opens the exception type details screen.
Solution: The queue name will be displayed in the “Exception Type Details” screen irrespective of the order or the serial number of the queue in the queue list.
Defect ID	196097
Case ID	00078508
Description	If a LONG or LOB type value is present before a VARCHAR2 > 4000 chars in an insert statement, Oracle registers an “ORA-24816: Expanded non LONG bind data supplied after actual LONG or LOB column” error message.
Solution: The behavior of the application has been changed to dump the large OUTXML into a file.
Defect ID	196605
Case ID	Internal
Description	When a user performs the following sequence of tasks, the application creates system suggested outbound cases for the shipment:
4.	Configure the following Batch Picking Task Types: “Pick Into Pallet”, “Pack While Pick”, and “Use System Suggested Containerization”.
5.	Create a shipment, include the shipment in a wave, and release the wave.
Solution: The application has been enhanced to support shipping of system suggested outbound pallets.
Defect ID	197715
Case ID	00081497
Description	When the findInventory API is invoked with the VMI functionality enabled, the findInventory does not give availability of item that does not have any record in YFS_INVENTORY_ITEM for consuming inventory org using inventory of item of consumable inventory org.
Solution: The adjustInventory API has been enhanced so that when inventory is adjusted for an item belonging to a consumable inventory org, the API can also insert record in the YFS_ITEM_INVENTORY table for items belonging to the consuming inventory org that has the same GTIN number as the item for the consumable inventory org. Only after this fix is applied, the findInventory/getATP APIs would give correct availability for item belonging to consuming inventory org, for which there is no supply and demand, but the supply has been adjusted for item having the same GTIN number belonging to the consumable inventory org.
Defect ID	197983
Case ID	00076761
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 the 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	199395
Case ID	Internal
Description	When the getExceptionListForOrder API is invoked, the application does not display alerts that are unrelated to the order in the “Alert Search” screen.
Defect ID	199475
Case ID	00085050
Description	When installing a hot fix, the application displays an unknown option or illegal argument error.
Note: If you are using Windows OS with JRockit JRE, and not able to start the HF installer, you must install the Foundation80-HF55 or above and carry out the following manual steps BEFORE applying the HF:
1.	Open the INSTALL_DIR\bin\tmp.cmd.in file, search for the -Xmn&Windows.INIT_AGE;m string, and replace the string with empty space.
2.	Open the INSTALL_DIR\bin\ServiceInstaller.cmd.in file, search for the -Xmn&Windows.INIT_AGE;m string, and replace the string with empty space.
3.	Go to INSTALL_DIR\bin directory and run the setupfiles.cmd command.

Defect ID	200086
Case ID	00090224
Description	If the length of an error code is greater than the length of the corresponding error pop-up window in the RCP application, the complete error code and the “Close” button is not visible unless the user stretches the error pop-up screen.
Solution: The application has been modified to wrap the error code if the length of an error code is greater than the length of the corresponding error pop-up window.
Defect ID	200628
Case ID	00091389
Description	The application must be enhanced such that the menu from the Sterling Call Center and Store application can be copied to a custom menu.
Defect ID	201014
Case ID	00092231
Description	When a large number of organizations are administered by a parent organization, if a valid user of the parent organization logs in, and tries to open the “User Details” screen for any other user of the parent organization, the Configurator screen blanks out and the server crashes with an out-of-memory error.
Hot Fix ID	8.0-HF54
Defect ID	155105
Case ID	Internal
Description	When unpacking a time-sensitive item, the system displays an “Expiration Date Entry” popup window even when the Ship By Date attribute is unique for the item in the container.
Defect ID	155127
Case ID	Internal
Description	When the container that is being unpacked has inventory with the same Ship By Date attribute, the system displays the “Expiration Date Entry” screen.
Defect ID	155531
Case ID	Internal
Description	When a user tries to modify the location dedications for a node that has more than 75 organizations associated with it, the related editable tables do not handle the “Organization” field. In addition, the system converts the drop-down list to a text field and does not display the “Look Up” icon adjacent this text field.
Solution: The “Look Up” option has been enhanced to be consistent with the behavior of the other fields in the same editable table. The “Organization Search” pop-up window has been exposed with an “Enterprise Look Up” option.
Defect ID	156672
Case ID	Internal
Description	When a user performs the following sequence of actions when counting through the Sterling Supply Chain Mobile Application, the system does not unfreeze the location that has been frozen for variance:
1.	Configures the pick exception to “Freeze Location for Pick”.
2.	When picking from the location, enters the pick exception to freeze the location for variance that was configured in step 1.
3.	Creates a count request for the frozen location.
4.	Cancels the count request created in step 3.
Defect ID	156734
Case ID	Internal
Description	When the system-defined containerization is not enabled, and if a user tries to pack a case or pallet that has a serialized item in an outbound container, the inventory moves from the case or pallet to the container.
Defect ID	163459
Case ID	Internal
Description	To facilitate better performance of the “Create Count Request For Location Range” agent, the "Number of Records To Buffer" parameter for this agent should be set to 5000.
Solution: The "Number of Records To Buffer" parameter for the “Create Count Request For Location Range” agent has been set to a default value of 5000.
Defect ID	199379
Case ID	Internal
Description	The changeShipmentContainer API must populate the ReasonCode and the ReasonText information in the yfs_audit_header when this API is invoked to modify the shipment line quantity by modifying the container details quantity.
Defect ID	199383
Case ID	Internal
Description	When a user performs the following sequence of actions, the application does not complete the count task even when the user performs the "Complete" action:
7.	Creates an LPN in a location with inventory for an item.
8.	Logs in to the Sterling Mobile application, and performs a "Manual Count" operation.
9.	Scans a location and counts the LPN created in step 1 in the location.
10.	Completes the manual count.
Defect ID	199402
Case ID	Internal
Description	When a system-defined containerization is configured, and serial-tracked and serialized items are being packed, the application does not validate the value of the serialized item scanned in the “Serial” pop-up window.
Defect ID	199426
Case ID	Internal
Description	When a user performs the following sequence of actions, the application containerizes one of the shipments twice such that the container quantity of this shipment is twice the shipment line quantity:
1.	Releases a wave that contains two shipments such that a single or multiple item pick tasks are created for this wave.
2.	Invokes the containerizeWave API to create containers for the wave released in step 1.
Defect ID	199894
Case ID	00089669
Description	The application console does not provide an interface that enables a user to enter the serial number of a serial-tracked item for a shipment line.
Solution: The application console has been enhanced such that the user can enter the serial number of a serial-tracked item in the “Shipment Line Details” screen.
Hot Fix ID	8.0-HF53
Defect ID	155490
Case ID	Internal
Description	A deadlock is observed in the YFS_TASK table when multiple users are packing using Pack HSDE.
Defect ID	155505
Case ID	Internal
Description	A deadlock is observed in the YFS_NODE_TRAN_ATTR table when operations such as wave release, physical count, and inventory adjustments happen at the same time.
Defect ID	157224
Case ID	Internal
Description	When an RF user scans a Cart ID that is already associated to a batch in the “Induct Cart” screen, the system throws a “Cart Already Inducted” error message.
Solution: The system has been enhanced to display the error message along with the batch number to which the cart is already associated.
Defect ID	167774
Case ID	Internal
Description	When two Cart Pick users try to induct their carts at the same time, one of the users fails with a deadlock.
Defect ID	167777
Case ID	Internal
Description	When the replenishment tasks are configured to be completed in three steps, and multiple users have logged in to the system to complete the replenishment tasks, deadlocks are visible in the YFS_Location_Inventory table when users try to complete the second and the third steps of the replenishment tasks.
Defect ID	170376
Case ID	Internal
Description	When a user invokes the receiveOrder API to receive a multi-line, multi-container shipment that has the shipment lines distributed in multiple containers, the application throws an “Overage Not Allowed” error message even if the shipment lines are available for receiving.
Defect ID	176431
Case ID	Internal
Description	The Task Purge agent has performance bottlenecks.
Defect ID	176436
Case ID	Internal
Description	When a user tries to pack an outbound shipment for an item that has multiple tags at a pack location, the application does not invoke the translateBarCode API to validate the tag number that is entered in the “Pack” screen.
Defect ID	176987
Case ID	Internal
Description	When a user performs the following sequence of actions, the application creates a new task from L2 with C1 as the suggested LPN:
1.	Configures the replenishment tasks to be created from a zone with "Do not Split Cases or Pallets" and "Round Up to a Case or a Pallet" enabled in the replenishment strategy.
2.	Ensures that a case, for example, C1, exists at a location L1 with 10 units of an item, and similarly, a case, C2, exists at location L2 with 10 units of the same item.
3.	Creates a shipment with less than 10 units of the item mentioned in step 2, includes the shipment in a wave, and releases the wave.
4.	The application creates a replenishment task for 10 units of the item at location L1, with C1 as the suggested LPN.
5.	When executing the replenishment task, the user scans an execution exception code that is configured to suggest an alternative pick location.
Defect ID	192593
Case ID	Internal
Description	When a user performs the following sequence of actions, the invoice is not collected against the payment method that has the same MaxChargeLimit as the amount in the invoice, that is, the first invoice is not collected against the second payment method:
1.	Creates an order with multiple invoices and multiple payment methods.
2.	Ensures that the MaxChargeLimit on the second payment method matches with the amount of the first invoice.
3.	Invokes the processOrderPayments API.
Defect ID	195633
Case ID	00068518
Description	The application must be enhanced with an event that can be configured to publish the reservation changes for the INVENTORY_CHANGE transaction whenever there is a change in the inventory reservation.
Solution: A RESERVATION_CHANGE event has been introduced for the INVENTORY_CHANGE transaction.
Defect ID	195844
Case ID	Internal
Description	When the getOrderDetails API is invoked, the output XML of this API does not contain the “TaxableFlag” attribute under the <LineTax> element.
Solution: The “TaxableFlag” attribute has been added under the <LineTax> element in the output template of the createOrder API, the changeOrder API, and the getOrderDetails API.
Defect ID	195946
Case ID	00076994
Description	When a routing guide is configured for a buyer organization, and the findInventory API is invoked, this API does not determine the carrier based on the routing guide that is configured for the buyer organization.
Solution: The findInventory API has been enhanced such that the value passed in the CustomerId in the input XML will be used to determine the routing guide for the buyer organization.
Defect ID	196592
Case ID	00080573
Description	The JMS Monitoring Group does not display the correct information pertaining to the JBoss queue in the System Management Console.
Defect ID	196792
Case ID	Internal
Description	The application must be enhanced such that scanning of the corresponding location and item is mandatory when a cart pick operation is performed using the Sterling Mobile Application. Currently, the application does not display an error message if the item and the location are not scanned during cart picking.
Defect ID	197024
Case ID	00034477
Description	The “Count” screen and the “Putaway Deposit” screen in the RF must be enhanced to display the “DisplayItemId” field and the “DisplayItemDescription” field.
Defect ID	197774
Case ID	00080653
Description	When a new child organization is added to a seller node, the application displays a “Node Organization cannot have child organization” error message.
Defect ID	199010
Case ID	Internal
Description	When a user purges the batch tasks from the history table, and runs the Task History Purge Agent, the application registers a null pointer exception.
Defect ID	199204
Case ID	00086306
Description	When a user runs the Person Info Purge agent against the YFS_PERSON_INFO table that contains a large number of records, a couple of queries that do not use the index on the MODIFYTS column in the YFS_PERSON_INFO table are fired. Because of this, the performance of these queries is slow.
Solution: The queries have been modified such that in an Oracle database, the index on the MODIFYTS column will be used.
Defect ID	199386
Case ID	Internal
Description	When a user performs the following sequence of actions, the application registers an "Invalid status change" exception during deposit:
1.	Adjusts inventory for an item in an LPN 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.
3.	Deletes the LPN and adjusts inventory in another LPN at another location.
4.	Logs in to the Sterling Mobile application to complete the task started in step 3. The application suggests another location to pick the inventory from through the Suggest Alternate Location mechanism.
5.	Picks inventory from the location suggested by the application, and tries to deposit the inventory.
Defect ID	199398
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 enabled.
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 the inventory from through the Suggest Alternate Location mechanism. The new task will be created from another location with the suggested LPN (C2) information, but the quantity remains the same as that of the LPN (C1).
Defect ID	199407
Case ID	Internal
Description	When a user performs the following sequence of actions, the application does not stamp the correct 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 the inventory from through the Suggest Alternate Location mechanism. The new task will be created from another location without the suggested LPN (C2).
Defect ID	200505
Case ID	00091859
Description	The application does not allow a user to log in to the Sterling Store Inventory Management client if the LoginThroughBrowser attribute is set to “Y” in the locations.ycfg file. 
Hot Fix ID	8.0-HF52
Defect ID	149679
Case ID	Internal
Description	When a user performs picking operations using the Sterling Mobile Application, scans the start location, and picks and deposits inventory from the start location to another location, the system should suggest that the next inventory be picked from the scanned start location instead of the last deposit location.
Defect ID	155108
Case ID	Internal
Description	The Sterling Warehouse Management System Configuration Guide must be updated with information about the "Expired Inventory" event included in the “Location Monitor Rule Details” screen.
Solution: Information about the  "Expired Inventory" event has been added to Table 4-19, "List of Valid Events" in Section 4.8.1, "Creating a Monitoring Rule" in the Sterling Warehouse Management System Configuration Guide.
Defect ID	155486
Case ID	Internal
Description	The Sterling Supply Chain Visibility PCA application confirmShipmentFromEDI API throws a null pointer exception when the “Ship Node” attribute is sent in the input parameter.
Defect ID	170345
Case ID	Internal
Description	When a large wave is released in a DB2 environment and a user frequently refreshes the “Wave Summary” screen, the Cancel Shipment transaction that is running concurrently tries to cancel the shipment that is included in the wave. Thus, deadlocks appear between the YFS_Wave table and the YFS_Shipment table, and the wave takes a long time to release.
Defect ID	190020
Case ID	Internal
Description	The application must be able to delete the containers associated to a shipment created by wave containerization if either the shipment is removed from the wave, or the wave is cancelled.
Defect ID	192590
Case ID	Internal
Description	When a user invokes the changeLoadStatus API, a deadlock occurs with the following error message:
"[NTSERV64]Transaction (Process ID 80) was deadlocked on lock resources with another process, and has been chosen as the deadlock victim. Rerun the transaction."
Defect ID	193162
Case ID	00055869
Description	When the Real Time Availability Monitor agent is run against large volumes of data, the agent registers a null pointer exception.
Defect ID	193646
Case ID	Internal
Description	When the getLPNDetails API is called for a pallet that has more than 100 child cases, and each child case has inventory for a serial-tracked item, one of the child cases in the pallet does not display the serial information in the output XML of this API.
Defect ID	195679
Case ID	00074233
Description	When the getCompleteItemList API is invoked, the API fetches those child items that are in unpublished or held status.
Solution: The child items in unpublished status are fetched only if the GetUnpublishedItems attribute is set to “Y”. The default value of this attribute is “N”. 
Defect ID	195685
Case ID	00077409
Description	When the createOrder API is invoked, the RecalculateHeaderTaxUE user exit is invoked even if the header charge is not present in the order.
Defect ID	195847
Case ID	Internal
Description	When a user performs the following sequence of actions, the containerizeWave API does not stamp the wave information on a shipment container, and subsequently the containers associated with a shipment that is created by wave containerization are not deleted if either the shipment is removed from the wave, or the wave is cancelled:
1.	Configures a task type to perform pick into equipment. 
2.	Associates the task type configured in step 1 when configuring the pick location assignment. 
3.	Creates a shipment, includes the shipment in a wave, releases and containerizes the wave.
Defect ID	196803
Case ID	Internal
Description	When a user performs the following sequence of actions, the application fires a query on the YFS_SHIPMENT_CONTAINER table with a join on the YFS_SHIPMENT_LINE. This query takes a large amount of time. In addition, the JOIN to YFS_SHIPMENT_LINE is not required:
1.	Enables the ON_SUCCESS event of the CONTAINERIZE_WAVE transaction.
2.	Enables the verbose trace for the containerizeWave API.
3.	Creates a shipment, includes the shipment in a wave, and releases and containerizes the wave.
Defect ID	197087
Case ID	00074791
Description	The Sterling JavaDocs must be updated with information about only the “Generic” pagination strategy being supported in a multi-component service.
Solution: The following note has been added in the description of the "IsFlow" attribute in the input XML under getPage API:
“Only 'GENERIC' strategy is supported while paginating a Service."
Defect ID	197137
Case ID	00081147
Description	When the yfs_charge_name table is extended, and the manageChargeName API is invoked, the manageChargeName API does not stamp the correct value of the extended attribute.
Defect ID	197324
Case ID	Internal
Description	When a user performs the following sequence of actions, the registerTaskCompletion API registers a “WMS00014: CaseId/PalletId doesn’t exist” exception:
1.	Moves a task to “In-progress” status by picking the inventory for an item from a multi-SKU LPN.
2.	Moves other SKUs from the multi-SKU LPN such that the LPN is deleted when it becomes empty.
Solution: The ProcessAllTasks and CompleteInprogressTasks flags have been exposed in the moveLocationInventory API. These flags, when enabled, prevent the auto completion or auto cancellation of tasks that are associated to an LPN when the LPN is deleted after moving the corresponding inventory.
Defect ID	197607
Case ID	00083878
Description	When a user performs the following sequence of actions, the “Deposit” screen does not display the item ID that is to be deposited:
1.	Creates two items such that each item has a different UOM.
2.	Receives the two items created in step 1 in a receiving dock such that putaway tasks are created for the two items to separate bulk locations.
3.	Logs in to the RF device, navigates to the putaway option in the RF menu, and picks up both the items in an equipment.
Defect ID	197653
Case ID	00069533
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 this API, see 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.
Note: The new records inserted by the Real Time Availability monitor into the YFS_INVENTORY_ALERTS table will have the IS_DEFAULT_DISTRIBUTION_GROUP field set to “Y”. A script has been provided with this hot fix to update the existing records in this table. If the Real Time Availability Monitor has been configured, this script must be run immediately after installing this hot fix.
Defect ID	197704
Case ID	00084028
Description	When a user performs the following sequence of actions, a "Permission Denied" message is displayed in the Routing Guides panel of the “Shipment Planning” screen:
1.	Creates a user group having permission to Logistics Management > Application > Sterling Multi-Channel Fulfillment Configurator > Logistics  > Shipment Planning, and creates a user for this group.
2.	Logs in as the user created in step 1, and navigates to Applications > Logistics Management > Logistics > Shipment Planning.
Solution: The permission ID for this resource has been changed to the same as that for the “Shipment Planning” screen. In addition, the permission ID in the “Carrier Services” screen of the routing guide has been changed to that of the permission ID of the “Shipment Planning” screen.
Therefore, after this fix is applied, the user must have the new permission to view the “Carrier Services” and “Shipment Planning” screens.
Additional permissions must also be provided to the user in the following:
•	To set the carrier services in the Create Routing Guideline tab: Logistics Management > Applications > Sterling Multi-Channel Fulfillment Configurator > Cross Application > Carrier Services.
•	To change or create calendar/Publish date: Platform > Applications > Sterling Multi-Channel Fulfillment Configurator > Participant Modeling > Participant Setup.
Defect ID	197984
Case ID	00083980
Description	The Configuration Deployment Verification Tool fails to restore the attributes of the extended columns within a record during a rollback.
Defect ID	198017
Case ID	00083992
Description	When a user performs the following sequence of actions, the application schedules the order line instead of backordering it:
1.	Creates an order by passing the Requested Cancel date in the order header level.
2.	Ensures that the Requested Cancel date is not passed in the order line level such that the Requested Cancel date passed in the order header level in step 1 is considered for scheduling.
3.	Passes a valid Requested Ship date that has a larger value than the Requested Cancel date that was passed in the order header level in step 1.
Defect ID	198130
Case ID	Internal
Description	The Sterling JavaDocs must be updated with information about the “NoOfCopies” attribute in the reprintCarrierLabel API, and the corresponding OnSuccess event.
Defect ID	198866
Case ID	Internal
Description	The Sterling JavaDocs must be updated with information about only the “Generic” pagination strategy being supported in a multi-component service.
Solution: The following note has been added under the getPage API in the Sterling JavaDocs:
By default, only 'Generic' strategy is supported by List APIs. Support for any other strategy for an API has to be evaluated and documented by the respective API.
Defect ID	199429
Case ID	Internal
Description	When the acceptTasks API is invoked through the recordPhysicalCount API in the Sterling Inventory Management application, the acceptTasks API registers a null pointer exception.
Hot Fix ID	8.0-HF51
Defect ID	154536
Case ID	Internal
Description	The performance of the serial-picking task should be enhanced for shipments with multiple lines of serial-tracked items.
Defect ID	154544
Case ID	Internal
Description	When a user unpacks a serial tracked item, the system throws a “WMS00013: Serial Tracking Mandatory” error message for that item.
Defect ID	156772
Case ID	Internal
Description	When a node has more than 75 participating enterprises, the “Enterprise Look Up” icon in the Sterling Warehouse Management System Configurator for a Node/Enterprise combination is disabled.
Defect ID	159830
Case ID	Internal
Description	When a user cancels a shipment from the Sterling Application Console, the system retains the empty container after the outbound container is converted to an inventory container.
Defect ID	168248
Case ID	Internal
Description	When a user completes a task created for a paper-based count request for a location at the classification level, the Items panel in the “Record Count Result Details” screen does not display the amount of system inventory present in a location for the items that are grouped under this classification.
Defect ID	193099
Case ID	00068431
Description	The reprintCarrierLabel API does not raise a configured ON_SUCCESS event.
Solution: The reprintCarrierLabel API has been enhanced to raise an ON_SUCCESS event, and publish the PrintBuffer attribute and PrinterPreference element in the ON_SUCCESS event.
Defect ID	195729
Case ID	00077537
Description	When more than 75 enterprises exist in the application, and a user tries to create a new organization, the application does not allow the user to create the new organization, and displays a “Primary enterprise must be specified” error message.
This issue exists even if the “Organization Is An Enterprise” option in the “Create Organization” pop-up window is selected during the process of creating a new enterprise.
Defect ID	196046
Case ID	00077748
Description	When a user tries to cancel all the orders that are in the “Created” status by selecting the corresponding check boxes in the “Order List” window, the application cancels the corresponding order without prompting the user to enter the cancellation reason code. 
Defect ID	196396
Case ID	00078546
Description	When the receiveOrder API, closeReceipt API, changeOrder API (To change an existing sales order to an exchange order of the return order), and the createOrderInvoice API are invoked in a single transaction boundary, the TRANSFER_IN charge type for an exchange order and the TRANSFER_OUT charge type for a return order are not inserted in the YFS_CHARGE_TRANSACTION table.
Defect ID	196446
Case ID	Internal
Description	The INBOXPRG record is not available in the YFS_AGENT_CRITERIA_TEMPLATE database table after a user completes the migration from Release 7.x to Release 8.2. Because of this missing record, upgrading the same database to Release 8.5 results in an upgrade failure.
Solution: A factory setup has been provided for the missing database record. If a user has migrated from Release 7.x to Release 8.2, and later wishes to migrate to Release 8.5 or later versions, this hot fix must be applied to restore the missing database record.
Defect ID	196787
Case ID	Internal
Description	When the supervisory override functionality is enabled in the RCP application, connection leak and end-of-file (EOF) exceptions are registered in the backend console.
Defect ID	196898
Case ID	00080648
Description	When the -DhideStoreCustomerMessage=true argument is added in the sop.ini file of Sterling Inventory Management, Release 7.2, the application does not hide the customer message.
Defect ID	197281
Case ID	Internal
Description	When a user performs the following sequence of actions, the Create Count Task agent does not create the corresponding count tasks:
1.	Configures a count strategy for a node with the CREATE_COUNT_TASK_79 TransactionId, and associates it to a task type.
2.	Creates a count request for an item classification for an entire node.
3.	Runs the Create Count Task agent for the count request created in step 2.
Defect ID	198082
Case ID	00077748
Description	The Sterling Distributed Order Management User Guide must be updated with information about entering the reason code and the reason text in the "Modification Reason" screen when canceling an order.
Solution: The requisite information has been added to the description of the "Cancel" action in Table 10-6, "Order List" in Section 10.6, "Order List", and in Table 10-7, "Detailed Order List" in Section 10.7, "Detailed Order List" of the Sterling Distributed Order Management User Guide.
Hot Fix ID	8.0-HF50
Defect ID	155475
Case ID	Internal
Description	When a user runs the MINE_PRODUCTIVITY agent with a blank agent criteria, this agent pushes too many messages into the queue, thus slowing itself down.
Defect ID	156778
Case ID	Internal
Description	When a user cancels a count request, the cancelCountRequest API cancels the count request without checking for any in-progress count tasks for that count request. Also, the system does not provide a user with the functionality to cancel the in-progress count tasks.
Solution: The cancelCountRequest API has been enhanced to throw an error when a user tries to cancel a count request that has in-progress count tasks.
Defect ID	157267
Case ID	Internal
Description	When executing a count operation through the Sterling Mobile Application, the system does not calculate the sum of the counted quantity when an item is counted multiple times in a location.
Defect ID	167771
Case ID	Internal
Description	The Asynchronous Request Processor agent begins to slow down as the YFS_ASYNC_REQ table fills up.
Solution: The following indexes have been added to the table to improve the performance of the get jobs for this agent:
•	YFS_ASYNC_REQ_I99  (SERVICE_NAME,TRAN_REQ_NO,ASYNC_REQUEST_KEY)
•	YFS_ASYNC_REQ_I98  (PRIORITY,TRAN_REQ_NO,ASYNC_REQUEST_KEY)
Defect ID	167780
Case ID	Internal
Description	When the Outbound Pick Task Type is configured to “Dispatch Tasks Only When Inventory is Available”, the releaseTask agent moves the tasks to “Held” status even if the corresponding tasks are completed.
Solution: The application has been enhanced to verify whether the task is in the Completed, Canceled, or In-Progress status before the task is updated by the releaseTask agent, so that the releaseTask agent ignores such tasks.
Defect ID	170343
Case ID	Internal
Description	When the application creates a new task, for example, move task, count task, pick task, replenishment task, and so on, the application does not stamp the Task Key in the new Task Status Audit record.
Defect ID	181020
Case ID	Internal
Description	The application must be enhanced with the capability to control the logic involved in determining the sequence of the tasks to be derived from the getNextTask API.
Solution: A new “OrderBy” child element has been provided in the input XML of the getNextTask API. The user or an external application can invoke the getNextTask API by providing attributes in the <OrderBy> element as a criterion for sequencing the tasks. The getNextTask API will return the tasks based on the criteria provided in the input followed by the default system criterion.
For example, if the user or an external application invokes the getNextTask API with the input criteria as <OrderBy><Attribute Name=”WaveNo”/><OrderBy>, the application will derive the tasks based on the ORDER BY clause as follows:
WaveNo,TaskPriority,ReferenceSortSequence,FinishNoLaterThan,SourceSortSequence,SourceLocationId,ItemId,SerialNo
For more information about the “OrderBy” child element, see the Sterling Javadocs.
Defect ID	193928
Case ID	00063473
Description	When the Configuration Deployment Tool is run with the “Rollback Data to Version Label” option, not all the values in the YFS_ROUTING_GUIDE_DETAIL table are restored.
Defect ID	193958
Case ID	00067309
Description	If the user login auditing feature is enabled, at every login instance, a query fetches the records from the YFS_USER_ACT_AUDIT table based on the User ID and the Session ID of the logged-in user. This query consumes a lot of time if the number of records in the table is large.
Solution: A new index has been added in the YFS_USER_ACT_AUDIT table for the USER_ID column to increase the responsiveness of the query.
Defect ID	194158
Case ID	00041826
Description	When the recordInvoiceCreation API is invoked to create a DEBIT_MEMO for an imported order that has line charges and taxes, the API does not handle the line taxes.
Solution: The application has been enhanced with a new <LineTaxList> element. This element is introduced in the input XML and the template XML of the recordInvoiceCreation API.
Defect ID	194430
Case ID	00065940
Description	If an item attribute has a Japanese half-size character, a "javax.servlet.ServletException" is registered after an SKU is scanned in the Pack station.
Defect ID	194447
Case ID	00072716
Description	When a user performs the following sequence of actions, the application does not refund the line level taxes:
4.	Ensure that neither the YFSRecalculateHeaderTaxUE user exit nor the YFSRecalculateLineTaxUE user exit is implemented.
5.	Add tax at the line level.
6.	Ship and invoice the item.
7.	Invoke changeOrder API to create a full refund. Ensure that the changeOrder API has at least one tax element with zero tax amount and zero tax percentage.
Solution: The tax amount will also be included in the Create Adjustment invoice.
Defect ID	194848
Case ID	00070125
Description	When a user performs the following sequence of actions, the application displays a “Permission Denied” error message in the Routing Guides panel of the “Outbound Constraints” screen:
1.	Navigates to Application Rules Side Panel > Security > Groups, and creates a new user group in the “Group Details” window that is displayed.
2.	In the Permissions tab of the "Group Details" window, navigates to Platform Permissions > Applications > Sterling Multi-Channel Fulfillment Configurator, and grants permission to the following:
•	Distributed Order Management Tree
•	Cross Application > Logistics > Outbound Constraints
3.	Saves the configurations.
4.	Creates and assigns a new user to the user group created in step 1.
5.	Logs in as the new user created in step 4, and from the Configurator, navigates to Applications > Distributed Order Management > Cross Application > Logistics > Outbound Constraints.
Solution: This issue has been rectified. The following additional permissions must be granted to the user:
•	To set the carrier services in the Create Routing Guideline tab:
Logistics Management > Applications > Sterling Multi-Channel Fulfillment Configurator > Cross Application > Carrier Services.
•	To change or create calendar/Publish date:
Platform > Applications > Sterling Multi-Channel Fulfillment Configurator > Participant Modeling > Participant Setup.
Defect ID	194854
Case ID	00070954
Description	A user who is assigned to multiple user groups does not have complete access to order lines because the read-only permission for the inner panels takes precedence over the write permission on the console UI.
Defect ID	195460
Case ID	00069337
Description	When the task type allows user to choose from a list of tasks, the application does not display the tasks that have a lower pick sequence.
Defect ID	195540
Case ID	00076850
Description	The application does not allow a user to cancel an order if the orderRepricingUE user exit is implemented, and the order has header charges and taxes.
Solution: The order can be cancelled when the orderRepricingUE is implemented and order has header charges and taxes.
Defect ID	195659
Case ID	00077361
Description	When the INVGetDemandCorrectionsUE user exit is implemented to return the input XML as the output XML, and a user navigates to the “Inventory Details” screen for an item for which demand exists, the application crashes with an “Out of Memory” error message.
Defect ID	195906
Case ID	00077679
Description	The application prints the document even if the document contains more than a million nodes.
Solution: A new yantra.document.suppress.huge.doc.alert property has been included in the yfs.properties file. A user can override the same property in the customer_overrides.properties file with the value of the yfs.yantra.document.suppress.huge.doc.alerts property set to either true or false.
If the value of this property is set as true, the document will not be printed, and instead, a "Please disable/set yantra.document.suppress.huge.doc.alerts to N/False to print the offending document with more than one million nodes" warning message will be displayed.
If set to false, the application will retain the default behavior.
Defect ID	195915
Case ID	00078121
Description	When a user performs the following sequence of actions, the application displays an "Either Node or country value is mandatory" error message:
1.	Navigate to Configurator > Platform > Region Definition > Region Schemas, and create a new region schema.
2.	Create more than 75 regions for the region schema created in step 1.
3.	Navigate to Configurator > Logistics Management > Logistics > Shipment Planning, and select the region schema defined in step 1 from the "Shipment Planning" window.
4.	In the "Shipment Planning" window, create and save a new routing guide.
5.	Open the routing guide created in step 4, and add a new routing guideline in the "Routing Guide Details" window.
6.	Select the "Node" option in the "When shipping from" panel.
7.	Select the "Region" option in the "And shipping to" panel, and click the "Look Up" button.
8.	In the search result window, select a region other than the regions between one and 75, and click "Save".
9.	Navigate to Configurator > Logistics Management > Cross Application > Carrier Services, add a carrier service and click "Save".
Solution: The "Either Node or country value is mandatory" error message will not be displayed.
Defect ID	196644
Case ID	Internal
Description	The application registers a null pointer exception in a large number of test cases.
Solution: WMSContainerizationUtils.java has NPE in the private void getExtnOnLPNHeaderElem(YFCElement lpnElem, YFS_Shipment_Container oShipmentContainer) method.
Hot Fix ID	8.0-HF49
Defect ID	154499
Case ID	Internal
Description	The changeTask API must allow the “ShipByDate” attribute for a task to change when the inventory for the task is changed to another “ShipByDate” attribute.
Defect ID	154531
Case ID	Internal
Description	In the “Putaway Preference Details” screen, the system should populate the Product Class drop-down list irrespective of the number of product classes defined.
Defect ID	155228
Case ID	Internal
Description	If the YFS_SHIPMENT_CONTAINER table is extended with a column that stores a “Number” data type, and a user attempts to delete a shipment container, the system throws a “ClassCastException” error message.
Defect ID	155492
Case ID	Internal
Description	When a user decreases the value of the Ship By Date attribute from 01/01/2500 to any other lower date for a time-sensitive item, the system throws a “FEFO or ship by date needs to be passed” error message.
Defect ID	157261
Case ID	Internal
Description	When the system is configured as follows, and a user releases a wave for two shipments that have different SKUs, the system does not allow the user to perform the second step, that is, the putaway task, in item pick, if the number of user constraints across the move request exceeds the configured value:
•	Configures for a multistep item pick task type.
•	Restricts the number of users who are working on the subsequent putaway tasks to one.
Solution: The system will not insert auto user constraint records if the task references are blank.
Defect ID	160525
Case ID	Internal
Description	When a user deposits an inventory container at a staging location, and if there are any subsequent open tasks for this container, the system should not allow the user to pick more inventory into this container.
Defect ID	161902
Case ID	Internal
Description	When a user logs in to the RCP PCA in the single sign-on mode and invokes the getOrderLineList API, the system throws an “Invalid Session” error message.
Solution: The system has been enhanced to use the Request.getHeader instead of the Request.getParameter.
Defect ID	181229
Case ID	Internal
Description	During the Pick process, when a user scans the serial number of an item in the Sterling Mobile Application and tabs out of the screen, the application accepts the serial number without validating the existence of the serial number at the location.
Defect ID	181849
Case ID	Internal
Description	When a user performs the following sequence of actions, the application prompts the user to pick one of the tasks instead of prompting the user to pick one less than the total shipment quantity:
1.	Configures batch picking to use cart as the equipment.
2.	Creates a shipment for a few units of a serial-tracked item.
3.	Includes the shipment created in step 2 in a wave, and releases the wave.
4.	The wave is containerized such that two containers are created for the shipment, two pick tasks are created for the wave, and a batch is created for this wave.
5.	Logs in to the RF device, inducts a tote to the batch created in step 4, and builds a cart for this tote.
6.	Navigates to the “Cart Pick” screen and scans the cart ID.
7.	The application consolidates both the pick tasks and prompts the user to pick the total shipment quantity.
8.	The user scans a serial and then scans the cart location.
Defect ID	182895
Case ID	Internal
Description	When a user enters a duplicate serial number, the application does not validate the serial number immediately after it is entered. After the user specifies the slot location, the application displays a “WMS00014" - CaseId/PalletId exists at a different location” error message.
Defect ID	191576
Case ID	00061748
Description	When a user performs the following sequence of actions, the application displays a Javascript error:
1.	Navigates to Internet Explorer 7.0 > Tools > Internet Options > Advanced, and selects the “Disable script debugging” check box.
2.	Comments out the “yfcDoNotPromptForChanges” in a .jsp file, for example, the order_detail_orderentry.jsp file.
3.	Navigates to the “Order Details” screen, and provides information in the required fields.
4.	Navigates away from the “Order Details” screen such that the application displays a pop-up window prompting the user to save the changes.
5.	Clicks the “Cancel” button in the pop-up window.
Defect ID	193100
Case ID	00068430
Description	The ON_SUCCESS event of the addContainerToManifest API and the ON_PACKAGE_SUCCESS event of the getTrackingNoAndPrintLabel API do not publish the PrinterPreference element.
Defect ID	193383
Case ID	00068559
Description	When an input XML is formed for the getShipmentList API using a complex query, the SQL statement that is generated has an incorrect structure, and does not fetch the corresponding records.
Defect ID	193402
Case ID	00066927
Description	When a custom error code registers a YFSException, the application does not retrieve the error message for this exception.
Defect ID	193818
Case ID	00057557
Description	The PrintMoveTickets.xsl file contains the gettasklist service, but the isNumeric flag is not set to “Y” in the “SourceSortSequence” attribute in this service. Because of this, the batch sheet printed by the application is not sorted on the basis of the pick sequence.
Defect ID	194145
Case ID	00044965
Description	When a user performs the following sequence of actions, the application does not display item I2 in the RF Console:
1.	Ensures that three items, for example, I1, I2, and I3 exist with the UOM as, for example, UOM1, UOM2, and UOM3 respectively.
2.	Ensures that the putaway strategy is defined appropriately.
3.	Dedicates a location each for I1, I2, and I3 in a target zone.
4.	Adjusts eight quantities of I1, I2, and I3 in a source location.
5.	Logs in to the RF device, and selects the “Adhoc Move” option.
6.	Scans the source location, scans the three items mentioned in step 1, and enters the quantity as one for each item.
7.	Navigates to the “Deposit” screen, and deposits I1.
Defect ID	194537
Case ID	00072995
Description	When a user performs the following sequence of actions, the application does not set the value of the Pending_Transfer_In to the refund amount specified in the return order:
1.	Navigates to Sterling Configurator > Document Specific > Sales Order > Financials, and enables the "Disassociate Payment Processing of Advanced Pre-Paid Exchange Order from Return Order" field in the Others tab of the “Financial Attributes” screen.
2.	Creates a draft exchange order with the "ADVANCED Pre-Paid" exchange type.
3.	Ensures that the Pending_Transfer_In is set to zero in the draft exchange order.
4.	Modifies the exchange type in the draft exchange order to “ADVANCED” exchange type from "ADVANCED Pre-Paid" exchange type.
Solution: The Pending_Transfer_In will be set to zero if the exchange type is modified to "ADVANCED Pre-Paid" exchange type from either “ADVANCED” or “REGULAR” exchange types.
Defect ID	194841
Case ID	00073451
Description	When a user creates an order, enters an apostrophe in the “City” field of the “Bill To Address” screen and schedules the order, the schedule agent fails. The application registers an exception with the error code as “YFS10310" and the error description as "YFS: User Exit Failed".
Defect ID	194843
Case ID	Internal
Description	When a user configures the application to prevent payment processing at either the enterprise level or the document level, and creates an invoice for an order, the application displays a “YFS: No Record Found” error message.
Defect ID	194982
Case ID	00074641
Description	When the importOrder API and the recordInvoiceCreation API are invoked for an order, the application executes a query that performs a redundant scan of the entire YFS_PAYMENT table.
Hot Fix ID	8.0-HF48
Defect ID	156639
Case ID	Internal
Description	When a user performs the following sequence of actions for a count operation, the input XML to the translateBarCode API needs information about the previously scanned Location and the License Plate Number (LPN):
1.	Creates an LPN with inventory for an item.
2.	Creates a count request and creates count tasks.
3.	Scans Location, LPN, and item.
Defect ID	161909
Case ID	Internal
Description	When the -Dshowssopreferencedlg parameter is set to false, the –DdefaultEnterprise and –DdefaultNode parameters are not being read from the SOM.ini file.
Solution: If the EnterpriseName and Node parameters are not specified in the SOM.ini file, the default parameters will be read from the SOM.ini file.
Defect ID	161913
Case ID	Internal
Description	The additional cookies that are set in the server are missing in the single sign-on mode.
Solution: The system has been enhanced to pass the additional cookies that are added by a third party when invoking any API.
Defect ID	162828
Case ID	Internal
Description	When multiple RCP PCA clients with different versions are run on a single server, only the first client works.
Defect ID	163506
Case ID	Internal
Description	When a user who does not have permission to view a procurement order tries to view the procurement order, an error message is displayed in an incorrect format.
Solution: The task name that is displayed in the error message in the scenario described here has been localized. The application will add localized bundle entries to all the tasks. When a user attempts to execute a task without the requisite permission, the name of the localized task will be displayed in the error message.
Defect ID	182832
Case ID	Internal
Description	When using an integration server, or an agent, or services that use JMS components to receive messages from MQ Series, Version 5.3, if the MQ GET option is disabled, a “Max active channels reached” error message is observed in the MQ logs. If the MQ GET is re-enabled after this error, the message reception process may either not start on its own, or it takes a long time before it starts to receive messages on its own.
Defect ID	186015
Case ID	00023638
Description	The application must be enhanced to integrate with the Pierbridge Carrier Server for tasks such as generating prints, adding carton to manifest, and so on. For more information about this enhancement, see the Sterling Parcel Carrier Adapter Guide.
Defect ID	186991
Case ID	00023638
Description	Information about the Sterling Pierbridge Adapter must be included in the corresponding documents.
Solution: Information about the Sterling Pierbridge Adapter has been included in the following documents:
•	Sterling Parcel Carrier Adapter Guide
•	Sterling Multi-Channel Fulfillment Solution Installation Guide
•	Sterling Warehouse Management System User Guide
•	Sterling Warehouse Management System Concepts
•	Sterling Multi-Channel Fulfillment Solution Integration Guide
•	Sterling Multi-Channel Fulfillment Solution Upgrade Guide
•	Sterling Multi-Channel Fulfillment Solution Glossary
Defect ID	189133
Case ID	Internal
Description	When the containerizeWave API is invoked with the removeShipmentFromWave API in the single transaction mode, the removeShipmentFromWave API registers an “YFC0009: Update failed. The record to be updated could either not be found or it was already deleted or updated by another transaction" error message.
Defect ID	190018
Case ID	Internal
Description	When a user performs the following sequence of actions, the getExceptionListforOrder API does not return the alert:
1.	Extends the YFS_ORDER_HEADER table.
2.	Creates a data security group.
3.	Creates an alert that is not associated with an order.
4.	Invokes the getExceptionListforOrder API without an <Order> element.
Defect ID	190023
Case ID	Internal
Description	When a user performs the following sequence of actions, the application tries to create charge requests for the adjusted amount:
1.	In the Sterling Configurator, navigates to Cross Application > Financials > Payment Rules.
2.	In the “Payment Rule Details” screen that is displayed, ensures that the “Settlement Required” check box and the “Authorization Required” check box are not selected, and the “Collect external through AR” is selected.
3.	Navigates to Document Specific > Sales Order > Financials > Financial Attributes.
4.	In the “Financial Attributes” screen that is displayed, selects the “Do Not Allow Debit And Credit Invoices To Settle Each Other” check box in the Others tab.
5.	Creates a sales order and associates a payment method with this sales order.
6.	Creates a credit memo for the completely invoiced sales order.
Defect ID	191286
Case ID	Internal
Description	When a user implements the YFSGetInvoicePricingQtyUE user exit and invokes the createOrderInvoice API with the <TaxBreakUp> element in the output template, the TaxBreakUpList is inserted into the database, but the output XML is not populated with the same.
Defect ID	191531
Case ID	00052782
Description	When a user performs the following sequence of actions, the application displays a "No kit lines found" error message. In addition, if the chained order is cancelled the corresponding parent line, that is, the kit component line, is cancelled, but the order does not move to the “Shipped” status even though only one line remains:
1.	Creates a bundle item with two kit components, for example, ITEM1 and ITEM2.
2.	Creates a sales order for the bundle item with a chained order in one kit component line.
3.	Schedules, releases, and ships the other kit component line.
4.	Cancels the kit component line that has a chained order in the sales order created in step 2.
Defect ID	191739
Case ID	00034855
Description	The application sporadically moves a completed task to “Held” status during task suggestion in the Sterling Mobile application.
Defect ID	191917
Case ID	00064288
Description	When the changeOrder API is invoked for a completely invoiced order in order to change the unit price with the tax value and tax percentage value as zero, but without header level taxes and charges, the adjustment invoice is not created.
Defect ID	191975
Case ID	00064494
Description	When a node is created using the copyNode API, and is then deleted, this API does not allow the re-creation of a node with the same name.
Defect ID	192057
Case ID	00064352
Description	The behavior of the “Can multiple users work simultaneously in a location” drop-down list in the Task Execution Preferences tab of the “Zone Details” screen is erratic.
Defect ID	192925
Case ID	00064404
Description	When the createOrder API is invoked, the inventory reservation created with a custom demand type is not consumed in an order line.
Solution: If the ReservationID is passed in an order line, the matching inventory reservation will be used regardless of the demand type. Inventory reservations are sorted based on shipment dates, and only one reservation will be consumed at a time. The ReservationID must be passed in either the <OrderLineReservation> element or the order line.
Defect ID	193133
Case ID	00066935
Description	When purging tasks that have an associated batch, the Task Purge agent registers a null pointer exception.
Defect ID	193192
Case ID	Internal
Description	The dbverify tool does not generate the ALTER scripts if a column is modified from the “char” datatype to the “varchar” datatype in a DB2 database.
Defect ID	193231
Case ID	00067380
Description	When a user performs the following sequence of actions, the findInventory API goes into an infinite loop:
1.	Implements the YFSGetAvailabilityCorrectionsUE user exit.
2.	Configures the Lead Days as ten, and the UseUnPlannedInventory as "Yes".
3.	Creates an item and ensures that zero inventory exists for this item.
4.	Invokes the findInventory API passing the values of the ReqEndDate and the ReqStartDate such that they occur within the lead days of the item configured in step 2.
Solution: A new "IsUnplannedSupply" flag has been introduced. This flag indicates whether the supply is from an unplanned inventory or not in the input XML and output XML of the YFSGetAvailabilityCorrectionsUE user exit. The user must ensure that the output of the YFSGetAvailabilityCorrectionsUE user exit will return the same value of this attribute as passed in the input.
Defect ID	193650
Case ID	Internal
Description	When the application has been extended to use the supervisory override functionality in the login dialog box, if a user clicks the “Options” button in the login dialog box during the login process to display the Locations panel, and selects a location, the application does not honor the selected location.
However, if a user logs in without using the supervisory override functionality in the login dialog box, the application accepts the locations selected by the user.
Solution: The “Options” button in the login dialog box will be disabled if a user is logging in as a supervisor.
Defect ID	193829
Case ID	Internal
Description	The Sterling Multi-Channel Fulfillment Solution Performance Management Guide incorrectly states that Sterling Call Center and Store supports the processing of large orders.
Solution: Information about the Sterling Call Center and Store application supporting the processing of large sales orders has been removed from Section 23.2.4.1, "Best Practices" in Chapter 23, "General Recommendations" of the Sterling Multi-Channel Fulfillment Solution Performance Management Guide.
Defect ID	193974
Case ID	00070394
Description	When a user performs the following sequence of actions, the XML published by the ON_RELEASE_CREATION_OR_CHANGE event for the second release does not contain the status quantity attribute:
1.	Configures the application to invoke the changeRelease API when the ON_RELEASE_CREATION_OR_CHANGE event succeeds.
2.	Includes StatusQuantity in the template of the ON_RELEASE_CREATION_OR_CHANGE event.
3.	Creates a chained purchase order with two order lines for different ship nodes.
4.	Invokes the scheduleOrder API with the “Release Immediately” flag enabled.
5.	The purchase order is scheduled and released such that the two order lines are released separately.
Defect ID	194175
Case ID	00070641
Description	The OMPConfirmRefundDistributionUE user exit displays an error if a credit memo and a debit memo are not settled together.
Hot Fix ID	8.0-HF47
Defect ID	193188
Case ID	00069053
Description	The application must be enhanced to read the extended attributes of the order lines that are passed in the output XML of the YFSOrderRepricingUE user exit.
Defect ID	193289
Case ID	00067934
Description	When a user performs the following sequence of actions, the application registers a null pointer exception:
1.	Implements the OrderRepricingUE user exit, and the RecalculateHeaderTaxUE user exit.
2.	Extends the orderRepricing.xml to include the <LineTax> element, and the <HeaderTax> element.
3.	Creates and ships an order.
4.	Invokes the createShipmentInvoice API, and adds the header tax using the RecalculateHeaderTaxUE user exit.
Hot Fix ID	8.0-HF46
Defect ID	156631
Case ID	Internal
Description	When a user configures a multistep replenishment task type with different outstaging and instaging task types and performs the following sequence of actions, the system creates the subsequent instaging tasks by picking up the task type from putaway preferences and not as the outstaging task type mentioned in the multistep replenishment task type configuration:
1.	Creates a replenishment task for the multistep replenishment task type.
2.	Completes the replenishment from the source location to the outstaging location of the source.
3.	Completes the outstaging task from the outstaging location to the instaging location of the target location.
Defect ID	176763
Case ID	Internal
Description	The saved searches in any search console screen are not displayed in any defined order.
Solution: The list of the saved searches in the entire search console screen is displayed in an alphabetical order.
Defect ID	177141
Case ID	Internal
Description	When a batch has more than 10 pick tasks for an item that is to be picked from a single location, the application consolidates only 10 tasks per trip, thus forcing the user to complete the batch picking task in multiple trips.
Defect ID	177193
Case ID	Internal
Description	The application does not raise an alert if the number of messages in a JMS queue that is being monitored attains or exceeds the threshold value configured in the Health Monitor group in the System Management Console. This is observed when monitoring the BEA WebLogic queue.
Defect ID	178019
Case ID	Internal
Description	When creating a move request with multiple move request lines in the Yantra Application Console, if one of the move request lines contains an invalid item, the application displays the expected “ WMS00209: Invalid Item” functional error message, and erases all the move request lines entered for the move request. As a result of this, the user has to re-enter all the move request lines.
Defect ID	181017
Case ID	Internal
Description	When a user performs the following sequence of actions, the application displays a null pointer exception:
1.	Configures batch picking using the cart equipment.
2.	Ensures that the node user does not belong to any data security group.
3.	Includes a shipment in a wave, releases the wave, and creates a batch for this wave.
4.	Inducts a tote against the batch created in step 3 using the “Induct Tote” activity.
5.	Builds a cart for the tote inducted in step 4 using the “Cart Build” activity.
6.	Navigates to the “Wave Summary” screen, and clicks the hyperlink pertaining to the number of batches.
Defect ID	181031
Case ID	Internal
Description	When a user tries to log in to the Sterling Customer Order Management PCA, and if the application displays a custom error message generated by an external authentication system in the “Log In” screen, the size and position of the “Cancel” button is modified.
Solution: The text of the custom error message will henceforth be wrapped in the “Log In” screen, as a result of which, the size and location of the “Cancel” button will not change.
Defect ID	185891
Case ID	Internal
Description	The Sterling Customer Order Management PCA must be enhanced with the capability to customize the login dialog box.
Solution: A new “IYRCLoginDialog” interface has been provided to customize the middle composite of the login dialog box that contains the User ID and Password controls with additional controls. An implementation needs to be provided for the YRCLoginDialogExtn extension point using the IYRCLoginDialog interface. The implementation should update the login input document with the requisite attributes or add additional attributes or both.
When customizing the login dialog box, the module ID of the extension is the module ID of the application for which the login dialog box is being customized. The module ID of Sterling Customer Order Management PCA’s COM client is “ycd”, and the module ID of the SOM client is “sop”. If the implementation is absent, the application will display the default login dialog box.
In addition, the following conditions must be adhered to when extending the login dialog box:
•	The login dialog box extension will have an additional, mandatory "LoadOrder" attribute. When multiple login dialog box extensions exist for the same application, the “LoadOrder” attribute will decide which customization of the Login Dialog must be picked up. The Login Dialog extension with the highest value of the “LoadOrder” attribute will be selected and loaded.
•	The extension of the Login Dialog must be performed in a separate and independent plug-in that does not include any other customizations, such as those pertaining to bundles, commands, and so on.
The Sterling JavaDocs have been updated with information about the “IYRCLoginDialog” interface.
Defect ID	186808
Case ID	Internal
Description	The Sterling Multi-Channel Fulfillment Solution Customization Guide must be updated with information about the YRCLoginDialogExtn extension point.
Solution: A new section, Section B.6, "YRCLoginDialogExtn Extension Point", has been added to Appendix B, "RCP General Concepts Reference", in the Sterling Multi-Channel Fulfillment Solution Customization Guide.
Defect ID	187558
Case ID	00044920
Description	When a user logs in to the Sterling Customer Order Management PCA with a password that contains the “$” character, the login fails, and the application exits.
Solution: The Sterling Customer Order Management PCA has been enhanced such that the application does not exit when a user password containing "$" or any other special character is used.
Defect ID	188099
Case ID	00048828
Description	When a user performs the following sequence of actions, the onhand inventory is consumed:
1.	Configures a node with the Item-Based Allocation option enabled.
2.	Ensures that a demand exists for an item in the future, for example, ten days, at the node configured in step 1.
3.	Ensures that onhand inventory is available for the item, and additional inventory is expected earlier than the demand date in step 2.
4.	Runs the IBA agent.
Solution: A new “Optimize Supply Selection To Maximize Availability” flag has been introduced in Global Inventory Visibility > Inventory Rules > Other Rules. If this flag is enabled the inventory that will be arriving on a date that is nearest to the demand date, that is, the inventory arriving on a date that is earlier than or the same as the demand date will be considered first.
Defect ID	189171
Case ID	Internal
Description	When a user logs in to the Sterling Applications Console as a node user, navigates to any of the “Inventory Reports” screen, and selects the “Enterprise” option instead of the “Across Enterprise” option, the application displays the primary enterprise of the logged-in node user as the default enterprise in the “Enterprise Selection” drop-down list. This occurs even if this primary enterprise is not an inventory organization, and therefore does not exist in the output of the getOrganizationList API.
In the “Inventory Reports” screen, the application must display only those enterprises that are inventory organizations.
Solution: The application has been modified such that the primary enterprise of a corresponding node user, or the enterprise of a corresponding enterprise user will be displayed as the default enterprise in the “Enterprise Selection” drop-down list.
The application will display the primary enterprise as the default enterprise only if this enterprise exists in the output of the getOrganizationList API.
Defect ID	190348
Case ID	00056023
Description	The application must be enhanced with the capability to include the Sterling Call Center and Store menu hierarchies in the existing Sterling Multi-Channel Fulfillment Solution extended menus such that a user can be assigned to menu groups of both the applications.
Solution: A new action has been enabled for the menu tree, using which a user can copy a system-defined menu to a pre-existing custom menu group. The menu that is being copied will be copied to the same application for which it was defined.
In addition, if a sub menu is copied to a custom menu group, the sub menu will be copied under the application tree.
Defect ID	191031
Case ID	00061236
Description	When a user performs the following sequence of actions, the value of the extended price and the taxes of the line that was marked as “For information only” is displayed as zero:
1.	Creates an order with suitable line unit price, line charges and line taxes.
2.	Marks the price as “For information only”.
3.	Creates a shipment invoice for the order created in step 1.
Defect ID	191760
Case ID	00063776
Description	The Agent and Integration servers display a "Yantra failed to initialize" error message because of problems in loading the encryption property, and continue further without stopping.
Solution: The Agent and Integration servers will not start in the scenario described here.
Defect ID	192163
Case ID	00065370
Description	Database blocking locks cause the Web service calls to a custom service to take more than 200 seconds when invoking the findInventory API.
Defect ID	192183
Case ID	Internal
Description	When a user performs the following sequence of actions, the quantity for C1 is displayed as zero:
1.	Adjusts the inventory in a case, for example, C1, in a location.
2.	Creates and executes a count request at the Item Classification level.
3.	Logs in to the Sterling Mobile Console.
4.	Counts the item in a case, for example, C2.
5.	Completes the count task, and logs in to the count console to view the variance.
Defect ID	192353
Case ID	00048828
Description	The Sterling Global Inventory Visibility Configuration Guide must be updated with information about the new “Optimize Supply Selection To Maximize Availability” flag has been introduced in Global Inventory Visibility > Inventory Rules > Other Rules.
Solution: Information about the “Optimize Supply Selection To Maximize Availability” flag has been added under “Supply Optimization”, in Table 3-9, “Other Rules Tab”, in Section 3.5, “Defining Additional Inventory Rules” in Chapter 3, “Configuring Inventory Rules” of the Sterling Global Inventory Visibility Configuration Guide.
Hot Fix ID	8.0-HF45
Defect ID	147669
Case ID	Internal
Description	When the getWaveSummary API is invoked to obtain the shipment containers from a wave, a query in this API performs a full table scan, thus leading to performance degradation.
Solution: The query has been re-written to prevent a full table scan.
Defect ID	154501
Case ID	Internal
Description	The system should validate the assignment of alerts to the users and not assign alerts to a user irrespective of the enterprise or the data security group.
Defect ID	160529
Case ID	Internal
Description	When a user performs the following sequence of actions, the system suggests the cancelled shipment for packing at the pack station:
1.	Picks the inventory for a shipment from a pick location into a case, and deposits the case at the pack station.
2.	Cancels the shipment before the packing commences.
3.	At the pack station, scans the Case ID created in step 1.
Solution: The system has been enhanced to throw a "Shipment is Cancelled" error message in the scenario described here.
Defect ID	177202
Case ID	Internal
Description	When a user performs the following sequence of actions, the JVM loads a large number of objects, resulting in increased memory consumption:
1.	Ensures that a wave with a large number of shipment lines, for example, 50000, exists.
2.	Navigates to the “Wave Search” screen and searches for the wave mentioned in step 1, such that the search results are displayed in the “Wave List” screen.
3.	In the” Wave List” screen, selects the wave mentioned in step 1, and clicks the “View Summary” action button.
Solution: If the “wms.wavesummary.donotshowestimatedcasesandvolume” property is set to “Y” in the yfs.properties file, the output of the getWaveSummary API will not contain the “TotalVolume” attribute in the “OverallSummary” element. The “QuantitySummary” element will contain only the “TotalQuantity” attribute. This will prevent the JVM from loading a large number of objects, and result in reduced memory consumption.
Defect ID	181855
Case ID	Internal
Description	The modifyUserHierarchy API does not permit a user to pass the “UsergroupId” parameter when modifying the UserGroupList.
Solution: The application has been enhanced to accept the “UsergroupId” parameter as a unique input parameter to the UserGroupList.
Defect ID	182838
Case ID	Internal
Description	When the move requests are created at the LPN detail level, and the putaway tasks are executed, the application persistently fails to suggest a task to the user from the available tasks.
Defect ID	182918, 191305
Case ID	Internal
Description	The criteria parameters of the transaction exception monitor provide an option of filtering the monitoring for the “QueueId” parameter of an enterprise, but do not have the option to filter the monitoring based on the “QueueGroup” parameter of an enterprise. As a result, multiple criteria must be specified to monitor multiple queues.
Solution: A “QueueGroup” parameter has been provided as a criteria parameter. To filter the monitoring of all the queues that belong to a group, a user must specify the “QueueGroup” parameter and the organization in the criteria parameters. If both the “QueueId” and “QueueGroup” parameters are specified along with the organization, the “QueueId” parameter is ignored, and only the “QueueGroup” parameter is used by the application.
Defect ID	185370
Case ID	00037829
Description	When a user performs the following sequence of actions, the page number is displayed as “null of null”, and no search results are displayed:
1.	Creates a new entity in Resources.
2.	Invokes the getItemList API with pagination strategy and the getItemDetails API.
3.	Enters the search criteria in the screen, but with an invalid search filter.
Defect ID	187763
Case ID	Internal
Description	When a shipment that is a part of a batch is removed from a wave such that the task corresponding to this shipment is in “Cancelled” status, and if the batch number of this batch is scanned in the “Pack HSDE” screen, the application returns all the shipments from the batch, irrespective of the status of the tasks pertaining to the shipments.
Defect ID	188100
Case ID	00047597
Description	When the findInventory API is invoked for an item, the API considers all types of demands across several enterprises when computing the available quantities of the item. A handle must be provided with which a user can modify the demand picture, just as the supply picture can be modified by implementing the INVGetSupplyCorrectionsUE user exit. 
Solution: A new INVGetDemandCorrectionsUE user exit has been introduced, using which a user can add, modify, or delete the demand records. For more details about this API, see the corresponding section in the Sterling JavaDocs.
Defect ID	189144
Case ID	Internal
Description	The application must be enhanced with the capability to escalate the un-assigned alerts through the Unresolved Alerts escalation configuration. Currently, the Unresolved Alerts escalation configuration only escalates alerts that have been assigned to a specific user.
Solution: A new "yfs.queue.unresolvedAlerts" property has been added in the yfs.properties file.
To escalate an alert even if the alert is not assigned to a specific user, set the value of this property to “Y”. The default value of this property is “N”.
Defect ID	189147
Case ID	Internal
Description	In the “Agent Criteria Details” pop-up screen, only the name of the queue is displayed in the Queue drop-down list. Therefore, multiple queues with the same name but different organizations cannot be differentiated. However, the Queue drop-down list in the Alerts component in the Services displays the name of the queue along with the corresponding organization.
Solution: The Queue drop-down list in the “Agent Criteria Details” pop-up screen displays both the name of the queue and the corresponding organization.
Defect ID	189150
Case ID	Internal
Description	When a user tries to view a wave summary, the Sterling Application Console sporadically throws a Null Pointer exception.
Defect ID	189153
Case ID	Internal
Description	When an Alert component is used in a Service, the name of the queue is not configured. Only the ExceptionType is configured. The following details should be picked from the ExceptionType configuration:
•	Queue Id/Key
•	Priority
•	Follow up Date (computed based on follow up hours)
•	Expiration Days
•	Description
Defect ID	189523
Case ID	00053678
Description	The UI mapping for the “Use Case” field and the “Use Pallet” field is not working properly in the “Task Type” screen of the Sterling Mobile Application. These fields are displayed as “Mobile_Use_Pallet” and “Mobile_Use_Case” respectively in the “Task Type” screen.
Defect ID	190071
Case ID	00057175
Description	When a user performs the following sequence of actions, the YFS_LOAD_SHIPMENT table contains an entry for the inbound shipment IS-2 of E2, but the load key value is the same as that of IS-1 of E1:
1.	Creates two enterprises, for example, E1 and E2.
2.	Navigates to Cross Application > Logistic rules, and enables the “Allow addition of shipments not available on system to a Load” option for E1.
3.	Repeats step 2 for E2.
4.	Navigates to Supply Collaboration > Document Specific (in this case, purchase order) > Inbound Logistics > Shipment Modification > Shipment Modification Rules, and enables the "Include in Load" shipment modification rule for the Shipment Created modification level.
5.	Creates an inbound shipment, for example, IS-1 for E1.
6.	Adds a shipment to the load for E1, and creates another shipment, for example, IS-2 for E2.
Solution: A new DoNotMixEnterprisesInLoad arttribute has been exposed in the changeShipment API, the createShipment API, and the confirmShipment API.
If the DoNotMixEnterprisesInLoad attribute is set to “Y”, and the "ALLOW_ADDITION_OF_SHIPMENT_NA_YANTRA_TO_LOAD" rule is enabled, the application will not mix the shipments belonging to different enterprises in a load.   
By default, this attribute is set to “N” to retain the existing behavior, and for backward compatibility.
Defect ID	190419
Case ID	00058958
Description	When two users, for example U1 and U2, two equipments, and two in transit locations for these equipments are configured, and a pallet or a case is available in one of the equipments, the application incorrectly allows the second user, U2, to pick into the same pallet or case that is present in the other equipment.
Solution: The application displays a “Cannot Pick Inventory Into A Container Present At Storage or In transit Location” error message in the scenario described here.
Defect ID	190599
Case ID	00059630
Description	When the callImportOrder API is invoked with the PersonInfoBillTo attribute under the PaymentMethod in input XML, the PersonInfoBillTo value is not stored in the YFS_Person_Info table. 
Solution: The value of the PersonInfoBillTo attribute will now be stored in the YFS_Person_Info table.
Defect ID	190668
Case ID	00059372
Description	When a user performs the following sequence of actions, the application registers a "java.lang.reflect.InvocationTargetException" exception:
1.	Navigates to Configurator > Participant Setup, selects the role Carrier, and deletes all the default carriers.
2.	Navigates to Applications > Logistic Management > Logistics > Shipment Planning, and creates a new routing guide.
3.	Enters the name and number of the routing guide created in step 2, and clicks Save.
Defect ID	190875
Case ID	00059046
Description	When a user selects the “Authorize Before Scheduling and Delay Reauthorization Until” option in the “Payment Rules” screen, and if the RecalculateHeaderTaxUE user exit adds an extra tax amount when the shipment invoice is created, the order is not picked up by the payment collection agent to process the extra tax amount.
Defect ID	190896
Case ID	00055476
Description	When a user performs the following sequence of actions, the application incorrectly creates a task for Item-001 for three quantities. However, the application correctly generates a task for Item-002 for seven quantities:
1.	Configures a retrieval strategy to pick an item from a bulk location, and deposit the item at a VAS location.
2.	Configures two physical kits, for example, KIT1 that contains Item-001, and KIT2 that contains Item-001 and Item-002.
3.	Adjusts KIT1 with 10 quantities of Item-001 and adjusts seven quantities of Item-002, both at the bulk location.
4.	Creates a work order for dekitting KIT1.
5.	Completes the retrieval tasks such that KIT1 with 10 quantities of Item-001 is at the VAS location.
6.	Confirms the work order for dekitting, and dekits only seven quantities of Item-001 from KIT1.
7.	Cancels the De-Kit work order such that the work order moves to “Completed” status, and the VAS location contains three quantities of Item-001 in KIT1 and seven quantities of Item-001.
8.	Generates a kitting work order for KIT2 with seven quantities of both Item-001 and Item-002.
Defect ID	190899
Case ID	00057815
Description	A NumberFormatException is registered by the changeShipment API if a logicalkit shipmentline is removed from the original shipment after the original shipment is completely split into a new shipment.
Defect ID	191076
Case ID	00061325
Description	When a user invokes the findInventory API, the API uses the default distribution rule even if a sourcing rule is configured. This degrades the performance of this API.
Defect ID	191309
Case ID	Internal
Description	The getWaveSummary API registers a Null Pointer Exception if two nWMS nodes generate the same wave number, and the getWaveSummary API is invoked for the wave of one nWMS node, for example:
Node > N1 and Wave No > 100
Node > N2 and Wave No > 100
Defect ID	191966
Case ID	Internal
Description	The Sterling JavaDocs must be updated with details of the DoNotMixEnterpriseinLoad flag that has been exposed in the changeShipment API, the createShipment API, and the confirmShipment API.
Hot Fix ID	8.0-HF44
Defect ID	149207
Case ID	Internal
Description	When a user exit is configured to implement a service that throws a YFSException, the “Error Code” and “Error Description” is not displayed properly.
Defect ID	154058
Case ID	Internal
Description	When a user performs the following sequence of actions, the Create Count Task agent slows down:
1.	Configures a product line with the classification purpose specified as “Count Classification”.
2.	Configures multiple items belonging to the classification specified in step 1.
3.	Creates a count request at the product line level.
4.	Runs the create count task agent.
Defect ID	154064
Case ID	Internal
Description	When a user tries to complete the count tasks for an item classification through the Yantra 7x Mobile Application, the system throws an "Out Of Memory" exception.
Defect ID	154526
Case ID	Internal
Description	When a user accepts the count for a request that is at the item classification level, the system slows down.
Defect ID	163444
Case ID	Internal
Description	In the screens containing an editable table with a drop-down list, if the focus of the cursor is on the drop-down list, and a user clicks on any other screen or its related task, the user interface does not function correctly.
Defect ID	165142
Case ID	Internal
Description	When a user performs the following sequence of actions, the application throws an "ORA-00932: inconsistent datatypes: expected DATE got NUMBER" error message:
1.	Navigates to Platform > Process Modeling > General > General > Transactions, and configures the YCPExportPurgeAgent, YCPImportPurgeAgent, CPStatisticsPurgeAgent, YCPUserActAuditPurgeAgent, and YCPUserActivityPurgeAgent purge agents.
2.	Starts the agent server and the Health Monitor.
Solution: The ‘MODIFYTS’ value will be enclosed within single quotes. The correct format for the date will be passed in the SQL query.
Defect ID	177210
Case ID	Internal
Description	Information about enabling Anonymous Admin Lookup in the BEA WebLogic Console should be provided in the Sterling Supply Chain Applications System Management Guide.
Solution: The requisite information has been added as a note at the end of Section 3.11, "Monitor Group Details", in Chapter 3, "System Management Console Screens", in the Sterling Supply Chain Applications System Management Guide.
Defect ID	181225
Case ID	Internal
Description	When a user performs the following sequence of actions, the containerizeWave API does not invoke the WMSOverrideContainerizationCategoryUE user exit:
1.	Implements the WMSOverrideContainerizationcategoryUE user exit.
2.	Configures the task type as “Pick Into Equipment” and “Deposit in Pack Station”.
3.	Configures pack planning as “SCM Required with Content”, “Apply SCM on all Shipping Units”, and “Use System Suggested Containers”.
4.	Creates a shipment and includes the shipment in a wave with the shipment group having the task type that is configured in step 2.
5.	Assigns a lane to the wave, and releases the wave.
6.	Invokes the containerizeWave API.
Defect ID	181232
Case ID	Internal
Description	The application displays alerts of other nodes to the user instead of displaying only those alerts pertaining to the user’s node.
Defect ID	182817
Case ID	Internal
Description	When the retrieveShipment API is invoked, the application creates putaway tasks for an outbound shipment that contains zero shipment lines.
Defect ID	182855
Case ID	Internal
Description	For services that use the XSL Component, the XSL is cached in the memory to improve performance, after it is used for the first time. This XSL is cached in the form of a template object, which is created using a third party transformer.
When a service is invoked multiple times for different input XML files, with the template object present in the cache, the heap size increases continuously because of a significant increase in the size of the cached template object.
Solution: The application has been enhanced to cache the XSL Component as a java String object, instead of as a template object.
Defect ID	183954
Case ID	Internal
Description	When a user performs the following sequence of actions, the application displays a "Zone-Enterprise constraint violated" error message during the wave release operation:
1.	Configures two enterprises and a node.
2.	Creates two dedicated zones in the node configured in step 1, with each zone dedicated to one enterprise.
3.	Configures one PLA UOM condition for a shipment group. The shipment group comprises two PLA rules, with each rule pointing to one of the zones configured in step 2.
4.	Creates an item in each of the enterprises configured in step 1, and ensures that the item has the same Item ID in both the enterprises.
5.	Creates two shipments for the two enterprises with the order lines having the item configured in step 4.
6.	Includes the two shipments created in step 5 in a wave, and releases the wave.
Defect ID	186777
Case ID	Internal
Description	When generating putaway tasks, the application generates a null pointer exception if the getNodeInventory API calls the getLPNList API.
Defect ID	187775
Case ID	Internal
Description	When a user performs the following sequence of actions, the application displays an "INV10029 -INV: Missing Inventory Identifier Attribute" error message:
1.	Creates a serial-tracked, tag-controlled item, for example, ST01 with the batch number as the tag identifier.
2.	Adjusts inventory for ST01 in a pack location with a serial number, for example, TAG01S1, and a batch number, for example, TAG01B1.
3.	Creates another serial-tracked, tag-controlled item, for example, ST02 with the lot number as the tag identifier.
4.	Adjusts inventory for ST02 in a pack location with the serial number as TAG01S1, and a lot number, for example, TAG01L1.
5.	Creates a shipment for ST02 with quantity as 1.
6.	Scans the shipment at the pack station, and clicks “New Case”.
7.	Scans ST02 in the “Item” field, and scans TAG01S1 in the “Serial” field.
Defect ID	188941, 189579, 189625
Case ID	00043743, 00048157, 00053078
Description	When a user performs the following sequence of actions, the amount from the return order is refunded to the payment method defined in the exchange order. Also, the return order invoice does not contain the collection details:
1.	Ensures that a return order and an advanced prepaid exchange order exist.
2.	Invoices and collects both the return order and the exchange order.
Solution: The application has been enhanced with a new "Disassociate Payment Processing of Advanced Pre-Paid Exchange Order from Return Order" rule in the Others tab of the Financial Attributes page, which can be accessed by navigating to Sterling Configurator > Document Specific > (Document Type) > Financials.
If this rule is turned on, the payment link between an advanced prepaid order and a return order will be decoupled. The amount from the return order will be refunded to the payment method of the corresponding sales order. In addition, the return order invoice will contain the requisite collection details.
Defect ID	189130
Case ID	Internal
Description	When the value of the “Description” attribute in the input XML of createException API is not provided, it’s value should be defaulted to the description corresponding to the value of the ExceptionType attribute provided in the input XML.
Defect ID	189237
Case ID	00052771
Description	When an item classification is deleted from a classification hierarchy, the classification is also deleted from the corresponding item details.
Defect ID	189899
Case ID	Internal
Description	When the recordInvoiceCreation API is invoked, with the values of the tax amount and the tax percentage as zero, the TaxBreakUpList is incorrectly inserted into the database.
Defect ID	190019
Case ID	Internal
Description	When the header level charges and taxes are changed for a completely invoiced order, all the order lines of this order are displayed in the adjustment invoice.
Defect ID	190187
Case ID	00056984
Description	When the changeOrder API is invoked to change the unit price of a completely invoiced order that has the values of the tax amount and the tax percentage as zero, the adjustment invoice is not created.
Defect ID	190593
Case ID	00053078
Description	The Sterling Distributed Order Management Configuration Guide must be updated with information about the "Disassociate Payment Processing of Advanced Pre-Paid Exchange Order from Return Order" field in the Others tab of the Financial Attributes page, which can be accessed by navigating to Sterling Configurator > Document Specific > (Document Type) > Financials.
Solution: Information about the "Disassociate Payment Processing of Advanced Pre-Paid Exchange Order from Return Order" field and its description has been added to Table 19-1, "Others Tab" in Section 19.4, "Defining Additional payment Rules" of the Sterling Distributed Order Management Configuration Guide.
Hot Fix ID	8.0-HF43
Defect ID	155510
Case ID	Internal
Description	The new “-Dshownaviagtorasmenu” argument that has been provided in the Sterling RCP Infrastructure is incorrectly spelled.
Solution: The spelling has been corrected to “-Dshownavigatorasmenu”.
Defect ID	159509
Case ID	Internal
Description	When the system is configured for “Number Of Days To Execute Purge > 0”, and a large number of shipment records need to be purged, the Shipment Purge agent slows down and takes a long time to perform the database transactions.
Solution: A new functionality has been added, which allows a user to choose a time window within which the Shipment Purge agent should purge the shipment records. Also, the Shipment Purge agent will proceed to the next time window of the same length when the current purge process is complete.
Defect ID	182886
Case ID	Internal
Description	When a large number of shipment records are purged, the application takes a long time to perform a complete table scan.
Defect ID	185896
Case ID	Internal
Description	When a user performs the following sequence of actions, the application fails with an update error during deposition of the last case from the pallet:
1.	Creates a pallet with multiple cases.
2.	Creates a deposit exception code that allows the user to perform a partial deposit.
3.	Creates a move request for the pallet created in step 1.
4.	Commences deposition of the cases from the pallet, and enters the deposit exception code created in step 2.
Defect ID	187756
Case ID	Internal
Description	The ON_SUCCESS event is not available for the SENT_TO_NODE.0006 transaction for the “Transfer Order Delivery” process type.
Solution: The application has been enhanced with the ON_SUCCESS event for the SENT_TO_NODE.0006 transaction such that a user can configure this event as required.
Defect ID	189126
Case ID	00048679
Description	When a user creates an adjustment invoice with the IsPriceForInformationOnly = “Y” for a bundle item, and invokes the changeOrder API, the adjustment invoice considers the change in the unit price of the bundle item in the unit price calculations even if the IsPriceForInformationOnly attribute is set to “Y”.
Defect ID	189322
Case ID	00044919
Description	When the importShipment API is invoked, it does not populate the OrderHeaderKey attribute in the YFS_SHIPMENT table.
Solution: When the OrderHeaderKey attribute is not passed at the shipment level in the input XML of the importShipment API, the API will populate this attribute based on the OrderNo, DocumentType, and the EnterpriseCode attributes only if the shipment is a “Single Order” shipment, that is, the IsSingleOrder attribute is passed as “Y” in the input.
Hot Fix ID	8.0-HF42
Defect ID	166776
Case ID	Internal
Description	The “TransactionalLineId” attribute does not work for the “ShipTogether” dependency rule between the order lines.
Solution: A “DependentOnTransactionalLineId” attribute has been added to the changeOrder API and the createOrder API.
Defect ID	167795
Case ID	Internal
Description	When a user performs the sequence of actions described here, the cursor moves to the end of the text box instead of remaining at the beginning of the text in the custom text box:
1.	Adds a custom text box to an existing screen.
2.	In the extension behavior class, implements the getBindingData method for this custom text box.
3.	Initiates the YRCTextBindingData object inside this method.
4.	Ensures that the setAllCaps method is set to “true”.
5.	Logs in to the Sterling Order Management System client and enters text in lower case in the custom text box. (When the user enters the text, the typed characters are automatically converted to upper case.)
6.	Moves the cursor to the beginning of the entered text and enters another character. (This character is also converted to upper case, after which the cursor moves to the end of the text.)
Defect ID	181042
Case ID	Internal
Description	When a serial tracked kit containing serial tracked components is de-kitted, the parent kit key references are not reset in the component serial records in the database.
Solution: The application has been enhanced to remove the parent kit reference from the kit components when de-kitting a serial kit with serial components.
Defect ID	181858
Case ID	Internal
Description	When a custom sorter is implemented using the “IYRCViewerSorter” class, and if a user right-clicks a sortable column in a table, a ClassCast exception occurs.
Defect ID	185893
Case ID	Internal
Description	The application must be enhanced such that a statement is logged in the log file in the client side or server side if an API is invoked in the secure mode. This helps a user to be certain that the API is invoked in the secure mode.
Solution: When an API or a command is invoked in the secure mode, a “Trying to open secure connection for command: commandname” trace statement will be logged in the log file.
Defect ID	185930
Case ID	Internal
Description	When a listener has multiple valid pickup statuses, the relevant pickup status must be selected based on the status (the status with the largest value must be picked first), and the expected ship date.
Defect ID	187061
Case ID	00047035
Description	When a user logs in to the application as a node user, and selects the Warehouse Management application from the Applications menu of the Sterling Multi-Channel Fulfillment Solution Configurator, a null pointer exception is registered.
Defect ID	187375
Case ID	00049133
Description	When a screen is extended by adding custom buttons, and the theme binding, for example, an image, of the custom buttons are changed to a value other than the out-of-the-box value, the application persistently displays the custom buttons with the out-of-the-box theme binding.
Defect ID	187526
Case ID	00049700
Description	When a report is executed for the first time from the Sterling Console, Cognos displays an "RSV-DST-0005 - The requested format is not supported" error message. However, if the report is executed again, the report is displayed correctly.
Defect ID	187552
Case ID	Internal
Description	When a user performs the following sequence of actions, the application displays a “Circular dependency exists” error message:
7.	Creates an order with two order lines.
8.	Creates a dependency between the order lines created in step 1 such that the second order line is dependent on the first order line.
9.	Invokes the splitLine API to move the first order line to a new order line.
Defect ID	187578
Case ID	00049772
Description	When a user performs the following sequence of actions, the application moves the order to Partially Scheduled status instead of Scheduled status:
6.	In the Sterling Configurator, navigates to Cross Application > Order Promising > Sourcing And Scheduling > Scheduling Rules.
7.	In the “Scheduling Rules Details” screen that is displayed, selects the “Ship from Single Node” check box and the “Line Ship from Single Node” check box in the Constraints panel, and the "Priority" check box in the "Optimize On" panel.
8.	Ensures that the INVGetExternalSupplyUE user exit is implemented.
9.	Creates an order.
10.	Creates an order line reservation for partial order quantity on two different dates.
11.	Schedules the order.
Defect ID	187894
Case ID	Internal
Description	The resolveException API must either be enhanced with either a built-in logic for processing 5000 records at a time, or must expose the MaximumRecords attribute. Currently, this API registers an “Out Of Memory” error.
Solution: The resolveException API has been enhanced to limit the number of exceptions to be resolved using the MaximumRecords attribute in the API input. For more details about this API, see the corresponding section in the Sterling JavaDocs.
Defect ID	188878
Case ID	Internal
Description	When a user performs the following sequence of actions, the application registers a servlet exception:
1.	Creates a batch for references.
2.	Confirms the batch from the Sterling Console.
3.	Navigates to the pack station, and scans the batch number in the “Scan Identifier” field.
4.	Scans the TargetCaseID in the “SKU” field.
Hot Fix ID	8.0-HF41
Defect ID	154003
Case ID	Internal
Description	When the getDockAppointmentList API is invoked for a date range beyond 30 days, the API throws an “Out of Memory” exception.
Defect ID	155488
Case ID	Internal
Description	When a user performs the following sequence of actions, the system throws an “Out of Memory” exception, and the WebLogic server crashes:
1.	Configures about 10 Dock Locations and applies the Node Calendar(s) to each Dock Location.
2.	Takes more than 15 appointments for a few days.
3.	Logs in to the console as a node user and navigates to the “Dock Appointment Details” screen.
4.	Queries for more than 5 Dock Locations and more than 10 days from the start date using the "Starts with" option in the “Location ID” field.
Also, when the getDockAppointmentList API with Query Type= “FLIKE” is invoked, the getServiceResourceCapacity API is also internally invoked with the same Query Type, and the getServiceResourceCapacity API slows down.
Solution: A list of Service Resources is fetched based on the user input within the getDockAppointmentList API. The getServiceResourceCapacity API is invoked on each of the elements in the list. The outputs from all these calls on the list elements are consolidated, and the consolidated output is returned in a single XML file.
Defect ID	161906
Case ID	Internal
Description	When a user receives the expected containers through an inbound shipment, the system receives the containers against incorrect shipment lines.
Defect ID	176742
Case ID	Internal
Description	When calendars are setup for all the dock locations, and the dock appointment day map is loaded in the Sterling Console, the application throws an “Out of Memory” exception error message even if a query type for the location is not passed.
Defect ID	179059
Case ID	Internal
Description	When the application is configured with the Item-Based Allocation (IBA) agent, the IBA agent does not create order line reservation.
Defect ID	182682
Case ID	Internal
Description	If a large Inventory Item Classification exists, that is, a very large number of items are categorized under the same Item Classification, and a user performs a count at the Item Classification level, the application displays an allocation request for a large amount of memory at java.lang.StringBuffer.append.
Defect ID	182908
Case ID	Internal
Description	When a user performs the following sequence of actions, the application does not display any inventory for the search criteria entered by the user:
1.	Configures a serial-tracked item.
2.	Creates an LPN with the serial-tracked item configured in step 1 at a location.
3.	Breaks the LPN created in step 2.
4.	Navigates to Location Inventory Console > By Additional Attributes, and searches for the serial number of the serial-tracked item.
Defect ID	185366
Case ID	00037478
Description	When a user performs the following sequence of actions, the application displays a pop-up window prompting the user to enter the International Transaction Number (ITN) for the domestic shipment:
1.	Creates a domestic shipment, for example, S1, for a serialized item.
2.	Includes S1 in a wave, assigns a lane for the wave, and releases the wave.
3.	Completes picking for S1, and deposits the case at a pack station.
4.	Scans the shipment S1 in the “Scan Identifier” field, and the case ID of the case that was deposited in the pack station in the SKU field.
Defect ID	185759
Case ID	Internal
Description	When a user performs the following sequence of activities, the modified primary serial number is lost after the TranslateBarCode API is invoked for the secondary serial number:
1.	Configures a custom translator that modifies the serial numbers during the serial scan operation.
2.	Scans the primary serial number of a serialized item in the pack station for an outbound shipment, and tabs out.
3.	Enters the secondary serial number in the Jtxt field.
Defect ID	185899
Case ID	Internal
Description	When a user enters a parent pallet ID in the "Pallet ID / Case ID" field in the Receiving HSDE screen and tabs out, the application immediately sets the "Pallet ID / Case ID" field to blank.
Defect ID	186091
Case ID	Internal
Description	If the input to the getPage API contains an empty “Template” element, the application registers a null pointer exception.
Defect ID	186784
Case ID	Internal
Description	The retrieveShipment API fails to create retrieval tasks for a shipment that contains a shipment line with a “CountryOfOrigin” attribute if the inventory in the node is not associated with this “CountryOfOrigin” attribute.
Defect ID	186814
Case ID	Internal
Description	When a user performs the following sequence of actions, the application displays a “Not enough quantity” error message:
1.	Creates a return order for a sales order, and associates a pickup service to the return order.
2.	Creates an exchange order for the return order created in step 1, and associates a delivery service to the exchange order.
3.	Creates a work order for both the return order and the exchange order created in steps 1 and 2 respectively.
4.	Completes the return order, and tries to cancel the exchange order.
Defect ID	187295
Case ID	00048624
Description	When creating indexes in the table columns defined in the XML files of the PCA, the dbverify tool displays an “Index column not found in table definition" error message.
Hot Fix ID	8.0-HF40
Defect ID	149181
Case ID	Internal
Description	When the changePriceSet API is invoked, the JVM crashes because the system tries to load the entire price set.
Solution: A new manageItemPriceSet API has been provided. This API handles the price set at the ItemPriceSet level. The user can create, modify, and delete the ItemPriceSet for a price set. For input and output XML, please refer to the Sterling Javadocs.
Defect ID	152037
Case ID	Internal
Description	When a sales order which has a work order, is delivered, the “ConfirmShipment” attribute is not being set to “Y” in the XML file published for the DEMAND_CHANGE event.
Defect ID	157226
Case ID	Internal
Description	The Sterling Distributed Order Management Configuration Guide must be updated with information about the Work Order Product and Delivery Association Rule.
Solution: Description of the Work Order Product and Delivery Service Association Rule has been added, and the vas_rules.gif file (screenshot for VAS Rules: Work Order) has been updated in Section 21.6.2 "Setting Up Value-Added Services Other Rules", in Chapter 21, "Configuring Value-Added Services" of the Sterling Distributed Order Management Configuration Guide.
Defect ID	161462
Case ID	Internal
Description	When counting through the Yantra Mobile Application, the system throws a "WMS00054: Node not passed" exception message if the user is unassigned from the current count task either through the reopen task agent or through the Yantra Application Console.
Defect ID	168073
Case ID	Internal
Description	The application should be enhanced with a provision to enable a user to perform putaway tasks based on the inbound shipment number.
Solution: The “Putaway Criteria” screen has been enhanced to accept the "Task List Number" attribute in which a user can enter an inbound shipment number. The application will suggest putaway tasks based on the inbound shipment number entered by the user.
Defect ID	180632
Case ID	00018873
Description	When a user performs the following sequence of actions, string sorting occurs instead of numeric sorting for the pick sequence: 
1.	Configures several locations, for example, DL1, DL2, and so on with the corresponding pick sequences, for example, 1, 2, and so on.
2.	Adjusts the inventory in the locations configured in step 1.
3.	Creates a shipment, includes it in a wave, assigns a lane for the wave, and releases the wave.
4.	Invokes the createbatchforreferences API.
5.	Navigates to the Wave Console, selects the wave released in step 3, and clicks “Print”.
6.	Selects the PrintWave service name, assigns a printer, and clicks “OK”.
Defect ID	184347
Case ID	00036625
Description	When a user performs the following sequence of actions, the move operation corrupts the inventory picture:
1.	Configures a zone with an Inventory Status = to Inventory Status: QC & Supply Type = HELD transition rule.
2.	Moves inventory from a location to the location configured in step 1 such that the status of the inventory changes to QC, and that of the supply type to Held.
Defect ID	184596
Case ID	Internal
Description	When the application is configured to raise an alert on release of a wave, and if a user releases a wave without the requisite inventory to fulfill the shipments in the wave, the inbox records of the alert do not contain the Ship Node key.
Defect ID	184940
Case ID	Internal
Description	When a user performs the following sequence of actions, the application passes the “Bill To” information from the order header level instead of the payment level in the input to the YFSCollectionCreditCardUE user exit:
1.	Enables payment processing and credit card payment type.
2.	Implements the YFSCollectionCreditCardUE user exit. 
3.	Creates an order, adds the payment type as Credit Card, and enters the Bill To address for the credit card.
Solution: The application has been enhanced such that if the Bill To address is overwritten at the payment level, the updated Bill To information will be used to populate the Bill To address in the input to the YFSCollectionCreditCardUE user exit.
Defect ID	185310
Case ID	00039259
Description	When a user performs the following sequence of actions, all the lines are moved to the same status even if the drop status of the removeFromReturn listener is different in the sales order pipeline for the bundle item and the normal item:
1.	Creates a new “ShippedExt” extended status of the Shipped status.
2.	Adds the “ShippedExt” drop status to the removeFromReturn listener.
3.	In the removeFromReturn listener details, changes the drop status to "ShippedExt" for the sales pipeline pertaining to the bundle item.
4.	Creates an order with the bundle item.
5.	Creates a return order for the order created in step 4, and cancels the return order.
Defect ID	185902
Case ID	Internal
Description	When the YFSGetExternalInventoryUE is implemented, and a user invokes the getWorkOrderAppoinmentOptions API with the requisite inventory and capacity available, the application does not display any slot as available for an order if the order has been backordered from a node, and the user tries to re-take the appointment for the order.
Solution: The application has been enhanced such that the quantity in the “backorder from node” status will be ignored when calculating the total quantity for an order line that is in a valid status.
Defect ID	185906
Case ID	00043736
Description	When the routing guide is configured for regions that can be identified with postal zip codes, the determineRouting API does not return any carrier even if the correct parameters are passed in the input to the determineRouting API.
Solution: The parameter corresponding to a region must be passed in the input XML in the ShipTo element to search for that region. For example, if a region can be identified by the zip code, pass the country and zip code in the input XML. If no region-matching preference is configured, the region will be matched based on the zip code.
Defect ID	186025
Case ID	00043985
Description	When a user performs the following sequence of actions, the application displays the value of the total received quantity as zero in the “Shipment Details” screen:
1.	Configures a bundle item with two components, for example, two numbers of item I1 and three numbers of item I2.
2.	Creates an inbound shipment for two quantities of the bundle item.
3.	Confirms the shipment, receives the order, and closes the receipt.
Solution: A new Received Quantity column has been added in the “Shipment Line Details” screen to populate the received quantity. The Quantity column will now display the total receivable quantity, and the Received Quantity column will display the number of received components.
Defect ID	186045
Case ID	Internal
Description	The manageOrganizationHierarchy API fails if the input contains the ScacAndService attribute value with a single quote.
Solution: The manageOrganizationHierarchy API has been fixed to overcome the single quote present in the ScacAndService attribute value.
Defect ID	186314
Case ID	00043888
Description	When a user performs the following sequence of actions, the application displays an "ORA-00933: SQL command not properly ended" error message:
1.	Configures a tag-controlled item with at least one tag identifier.
2.	Creates an outbound shipment for the tag-controlled item, includes it in a wave, assigns a lane for the wave, and releases the wave.
Defect ID	186331
Case ID	00042554
Description	When a user performs the following sequence of actions, the application does not prompt the user to scan the SKU in the LPN, and instead, prompts the user to deposit the LPN at the target location:
1.	Configures a putaway task type in the "yfs.deposit.units.separately.for.tasktypes" property.
2.	Ensures that a single SKU on an LPN is received, and a putaway task of the task type configured in step 1 is created for the single SKU LPN.
3.	Logs in to the Sterling Mobile Application, executes the putaway task, and scans the LPN in the “Pick” screen.
4.	Navigates to the “Deposit” screen, and tries to deposit the single SKU.
Defect ID	186852
Case ID	00045441
Description	When a user performs the following sequence of actions, the application displays a "WMS00023: Inventory Status not passed and transition is not specified for blank status" error message:
1.	Configures an item to be FIFO tracked in an inventory. 
2.	Ensures that the inventory for the item configured in step 1 is present in the pick location and has a certain FIFO number.
3.	Creates a shipment, includes it in a wave, assigns a lane for the wave, and releases the wave.
4.	The “Pick Into Inventory Case” task type, and the “Pack While Pick” task type is enabled for the wave.
5.	Completes the task using the Sterling Apps Console by passing the pack location as the target location and the target case ID. 
6.	Tries to delete the shipment container.
Defect ID	186949
Case ID	00042606
Description	The "deployer.sh -t entitydeployer" fails with an SQL exception in IBM AIX environments.
Hot Fix ID	8.0-HF39
Defect ID	155478
Case ID	Internal
Description	When the system is configured with a large number of nodes and a user creates or modifies a count program in the Sterling Warehouse Management System, the system throws an “Out of Memory” exception error message.
Solution: The Sterling Warehouse Management System has been modified so that the system will not load all the organizations belonging to the enterprise in the model of the count program.
Defect ID	156704
Case ID	Internal
Description	When the Load pipeline is configured with extended statuses and the receiveIntransitUpdates API is invoked, the system does not raise the ON_SUCCESS event that is configured under the RECEIVE_INTRANSIT_UPDATE transaction when the BOL is confirmed.
Defect ID	156730
Case ID	Internal
Description	When a user performs the following configurations and confirms a packed container through the “Confirm Carton Pack Complete” transaction in Weigh Station, the system prints the consignment docket twice:
3.	Configures a service to invoke the changeShipmentContainer API. (Start > changeShipmentContainer API > End)
4.	Configures the ON_SUCCESS event of the Confirm Carton Pack Complete transaction to invoke the service configured in step 1.
5.	Configures ON_SHIPMENT_PACK_PROCESS_COMPLETE event of CHANGE_CONTAINER_STATUS transaction to perform docket printing.
Defect ID	160453
Case ID	Internal
Description	The system locks a receipt record from the YFS_RECEIPT_HEADER table when the translateBarCode API is invoked for a serialized item received against a receipt.
Defect ID	161567
Case ID	Internal
Description	The user is unable to unpack a child container from the parent container in the “Pack HSDE” screen.
Solution: The user can unpack the child container from the parent container by scanning the parent container in the “Scan Identifier” field and the child container in the “SKU” field in the “Pack HSDE” screen. Also, the user should have UCC128 Code as the barcode source in the Pack SKU Barcode Type.
Defect ID	161572
Case ID	Internal
Description	Even after a child container is unpacked from a parent container, the child container remains as an outbound container.
Solution: The system has been enhanced so that when a child container is unpacked from a parent container, the child container becomes an inventory case or pallet.
Defect ID	162022
Case ID	Internal
Description	When a parent LPN contains multiple child LPNs, and if one of the child LPNs is deleted using the deleteLPN API, the system tries to update all the LPNs in the parent pallet, resulting in a performance overhead. The system should update only the parent pallet.
Defect ID	162820
Case ID	Internal
Description	When the number of nodes is large, and a user navigates to Sterling Supply Chain Applications Configurator > Warehouse Management and selects the “Show All Nodes” radio button in the “Configure WMS” pop-up window, the Configurator hangs and throws a null pointer exception.
Solution: The number of nodes that are retrieved from the database by the system has been restricted.
Defect ID	164393
Case ID	Internal
Description	When the receiveOrder API is invoked for shipments, for a Sterling Networked Warehouse Management System node, the application does not update the transaction cache for these shipments.
Defect ID	165135
Case ID	Internal
Description	The Sterling Global Inventory Visibility Configuration Guide must be updated with the information about the new "Ignore Prereserved Capacity" flag provided in the "Capacity Rules" window.
Solution: A new "Ignore Prereserved Capacity" column has been added to Table 8-1, "Capacity Rules Window", and the screenshot of the "Capacity Rules" window has been updated in Section 8.1, "Defining Capacity Rules" in Chapter 8, "Configuring Resource Capacity" of the Sterling Global Inventory Visibility Configuration Guide.
Defect ID	167702
Case ID	Internal
Description	When a user who has access to multiple stores performs the following sequence of actions, the application displays the details of the home store in the “UserNamespace” utility:
11.	Logs in to a store other than the home store.
12.	Because of session timeout, the user logs in to the same store again.
Defect ID	168209
Case ID	Internal
Description	When both the following conditions are true, and two users invoke the changeRelease API simultaneously, a deadlock scenario may take place:
1.	First user invokes the changeRelease API that has the OrderHeaderKey and the OrderReleaseKey in the input XML of the API.
2.	The second user invokes the changeRelease API that has the ReleaseNo, EnterpriseCode, DocumentType, and OrderNo in the input XML of the API.
Defect ID	169342
Case ID	Internal
Description	When a user performs the sequence of actions described here, the application truncates the “Quantity Confirmation” screen and the user is unable to see the “Item Quantity” field:
1.	Creates two time-sensitive items, for example, T1 and T2.
2.	Adjusts the inventory in the location, for example, L1 in a warehouse for T1 and T2 as follows:
•	L1 - T1 -  Quantity: 2  and  ShipByDate: 10/30/2008
•	L1 - T1 -  Quantity: 3  and  ShipByDate: 11/01/2008
•	L1 - T2 -  Quantity: 2  and  ShipByDate: 10/29/2008
•	L1 - T2 -  Quantity: 3  and  ShipByDate: 11/01/2008
3.	Creates a shipment, for example, S1, with the quantity as 2 for T1 and T2.
4.	Adds S1 to a shipment group that has “Batch Pick” as the pick strategy and Task Type details as follows:
•	Perform task using the BatchPick Activity.
•	Product is picked into an inventory case.
•	Use QVC-CART as the primary equipment type.
•	Perform task using a mobile device.
•	Dispatch tasks as soon as they are generated.
•	Use the Sterling Warehouse Management System application to plan trips by batching the tasks.
•	The number of shipments allowed per location in the equipment is 1.
•	Use pick sequence for picking.
•	Use putaway sequence for putaway.
5.	Releases the wave and invokes the createbatchforreferences API. (The application displays the two open tasks that are created for S1 and the batch number.)
6.	Logs in to the LXE device and inducts a cart. (The application displays the “Cart Pick” screen.)
7.	Enters the pick location, item ID, item quantity, and tabs out to navigate to the next screen.
8.	Enters the tote ID in the “Target LPN” field and clicks the “Go” button to navigate to the next screen.
9.	Enters the ShipByDate value and clicks the “GO” button. (The application displays the “Quantity Confirmation” screen.
10.	Tries to enter the item quantity for the ShipByDate value entered in step 9.
Defect ID	170044
Case ID	Internal
Description	The Sterling Distributed Order Management Configuration Guide should be updated with information about providing Oracle Hints to increase the performance of the scheduleOrder agent.
Solution: A new sub-section "Providing Oracle Hints" has been added to Section A.2.29, "Schedule" of Appendix A, "Time-Triggered Transaction Reference" in the Sterling Distributed Order Management Configuration Guide.
Defect ID	170337
Case ID	Internal
Description	When a user performs the following sequence of actions, the application loads all the lines in the order, which in turn slows down the performance of the getOrderLineList API:
1.	Creates an order with an order line.
2.	Associates a provided service with the order created in step 1.
3.	Invokes the getOrderLineList API without a template, and with the “OrderLineKey” attribute in the input.
Note: The purpose of this fix is to enhance the performance of the getOrderLineList API and not to load all the order lines, unless required.
When a user invokes the getOrderLineList API with the “OrderLineKey” attribute for an order line that has a normal item, and the order has multiple order lines, all the order lines will not be loaded if all the following conditions are met:
•	The output template is passed to the getOrderLineList API.
•	The “OpenQty” attribute is not passed in the output template.
•	The output template does not contain the <OrderStatuses> element.
If conditions other than those mentioned in this list exist, the getOrderLineList API will load all the lines in the order and there will be no significant improvement in the performance of this API.
Defect ID	176316
Case ID	Internal
Description	When a user performs the following sequence of actions, the application consumes a large amount of time to process the input values. In addition, multiple APIs were sometimes invoked out of context:
5.	Ensures that the system suggested containers are created prior to packing.
6.	In the “Pack HSDE” screen, enters the Shipment Container Marking (SCM) of the container and tabs out.
7.	Enters the SKU ID and tabs out.
Defect ID	176377
Case ID	Internal
Description	When a user performs the following sequence of actions, the application does not provide any response to the user:
1.	Configures a weighing scale device for a Sterling Networked Warehouse Management System node.
2.	Uses the out-of-the-box class implementation for the weighing scale device.
3.	Associates the weighing scale device to a pack station.
4.	Configures the pack station for both packing and weighing.
5.	Associates the same location to both the pack stations/weigh stations.
6.	Associates the weighing scale device to the second pack station in the alphabetical order.
7.	Navigates to the “Pack HSDE” screen.
8.	Scans the pack station ID and the case ID.
9.	Clicks the “Weigh” button.
Defect ID	176886
Case ID	Internal
Description	When a user navigates from the “Pack HSDE” screen to the “Manifest HSDE” screen and back to the “Pack HSDE” screen using the out-of-the-box manifest client JSP, the debug flag is set to “Y”. This causes a large number of debug traces to be logged, thus degrading the performance of the “Pack HSDE” screen.
Defect ID	178056
Case ID	Internal
Description	The YFS_LANGUAGE_DESCRIPTION table must be enhanced to be extensible such that the localized descriptions of the item details can be stored.
Defect ID	180550
Case ID	00023785
Description	When a user performs the following sequence of actions, the application releases the order against future inventory:
1.	Configures an item with a certain quantity of on-hand inventory, and additional quantity of inventory arriving at a future date.
2.	Ensures that the order can be released only against the on-hand inventory.
Defect ID	181046
Case ID	Internal
Description	When a serial-tracked item is shipped as part of another shipment, and has the “AtNode” attribute set to “N”, the application does not have any provision for shipping the serial-tracked items that are tracked only in returns and outbound.
Solution: The application has been enhanced to not validate the inventory of the serialized item at the node.
Defect ID	183172
Case ID	00033019
Description	When a user performs the following sequence of actions, the total amount in the exchange order is authorized against a payment type even if the application has not transferred the amount from the return order:
1.	Creates a return order.
2.	Creates a regular exchange order, and invokes the changeOrder API to convert the exchange order to an advanced exchange order.
3.	Runs the processOrderPayements.
Solution: The defer credit functionality has been disabled for advanced exchange orders. The pending “Transfer In” amount will be considered for calculation instead of the deferred credit. This fix is applicable only for the new advanced exchange orders or the advanced exchange orders created through Sterling Call Center and Store. The advanced exchange orders created previously through the Sterling Multi-Channel Fulfillment Console will exhibit a change in behavior.
Defect ID	183958
Case ID	Internal
Description	When a user performs the following sequence of actions, the application does not enable the refund of the credit memo immediately:
1.	Ensures that the “Deferred Credit on Return Required” check box in the “Payment Rule Details” pop-up window is not selected.
2.	Ensures that a credit memo that has a pre-collected amount with the “HoldAgainstBook” attribute set to “Y” exists on a sales order.
3.	Invokes the processOrderPayments API.
Solution: A new “Allow Immediate Refund From Hold Amount” check box has been included in the “Payment Rule Details” pop-up window. If this check box is selected, the refund will be enabled immediately in the scenario described. The “Allow Immediate Refund From Hold Amount” check box is mutually exclusive of the “Deferred Credit on Return Required” check box.
Defect ID	183962
Case ID	Internal
Description	The Sterling Distributed Order Management Configuration Guide must be updated with information about the new "Allow Immediate Refund From Hold Amount" flag that has been included in the Payment Rule.
Solution: Information about the "Allow Immediate Refund From Hold Amount" flag has been added to Table 7-2, "Payment Rule Pop-Up Window", in Section 7.3.1, "Creating a Payment Rule", in Chapter 7, "Configuring Cross Application Payment Components" in the Sterling Distributed Order Management Configuration Guide. The screenshot of the Payment Rule Details screen has been updated.
Defect ID	183972
Case ID	00023292
Description	When a shipment is changed from a higher shipment status to a lower shipment status with the AcceptOutOfSequenceUpdates attribute set to "Y", the application does not include the drop status in the audits.
Defect ID	184769
Case ID	00036600
Description	When the createOrder API is invoked, the inventory reservation created with a custom demand type is not consumed in the order line reservation that has same demand type.
Solution: It is not mandatory for the demand type used in the order line reservation to be of the same demand type used for inventory reservation. This is because the demand type passed in the order line reservation is the demand type to be placed if the reservation is successful. It does not represent the demand type that is to be considered for inventory reservations.
If the reservation ID is passed in the order line reservation, the matching inventory reservation should be used regardless of the demand type. The inventory reservations are sorted on the basis of the shipment date, and only one reservation is consumed at a time.
Defect ID	184912
Case ID	00036592
Description	The getPersonInfoList API does not sort the results based on the OrderBy attribute.
Defect ID	184920
Case ID	00036660
Description	The pagination of services, excluding the out-of-the-box APIs, fails with a "Could not resolve the API name" error message on the console list UI.
Defect ID	185214
Case ID	00032133
Description	When a user performs the following sequence of actions, the application suggests a location from the same zone as that of the original target location:
1.	Configures a deposit exception code to suggest an alternative deposit location.
2.	Enters the deposit exception code configured in step 1 during deposition of the inventory as part of the putaway tasks. 
Solution: A new "yfs.consider.other.zones.for.alternate.deposit" property has been provided. This property must be set to “Y” if other zones must be considered as an alternative deposit location. The default value of this property is “N”.
The user must implement the WMSGetPreferenceZoneListUE user exit to return a list of zones that will be considered in the suggestion for an alternative deposit location.
Defect ID	185601
Case ID	Internal
Description	The application does not broadcast the cache to other servers if the “yantra.statistics.persist.interval” property is set to more than 30 minutes.
Hot Fix ID	8.0-HF38
Defect ID	150670
Case ID	Internal
Description	When a user performs the following sequence of actions, the "CauseAppointmentChange" parameter is not reset to "N" even if the modifyWorkOrder API successfully takes up the appointment:
1.	Implements the “YFSGetExternalCapacityUE” user exit such that whenever the generateWorkOrder API is invoked, no capacity is returned, but whenever the modifyWorkOrder API is invoked, the exact capacity is returned.
2.	Configures the ON_SUCESS event of the “Create Work Order” transaction to call the modifyWorkOrder API to take up an appointment.
3.	Calls the generateWorkOrder API to create a new work order.
Defect ID	156627
Case ID	Internal
Description	When a delivery service is associated to a product in the catalog and the generateWorkOrder API is invoked, the user is not able to create a work order when the order is in the “Procurement Transfer Order Created” status.
Defect ID	157259
Case ID	Internal
Description	When the changeOrder API is invoked to change the receiving node of a transfer order that is in “Created” status, the system throws an "Order cannot be modified in current status" exception.
Solution: The system has been enhanced with a new modification rule to enable or disable the option of changing the receiving node of a transfer order that is in “Created” status. This rule is provided in Configurator > Supply Collaboration > Transfer Order > Fulfillment > Modification Rules > Change Receiving Node > Order.
Defect ID	157263
Case ID	Internal
Description	When a service is configured to raise an alert for a return order, the system does not display the hyperlink to the Alert ID in the “Return Alert” screen when navigating from the Return Console.
Defect ID	161503
Case ID	Internal
Description	When a user performs the following sequence of actions, the system displays the incorrect value of the “Quantity” attribute:
1.	Logs in to the Sterling Supply Chain Mobile Application in the LXE MX7 device.
2.	Inducts a cart and performs a Cart Pick.
3.	Selects the Cart Pick module.
4.	Selects the Source Location and the Item ID.
Defect ID	178015
Case ID	Internal
Description	The application allows a user to change the Zone ID of a location even if this location contains pend-in inventory.
Solution: In this scenario, the application displays a "WMS00064: Operation not permitted on Locations having Inventory" exception error message.
Defect ID	178773
Case ID	00019389
Description	When a user performs the following sequence of actions, the application permits mixing of inventory that belongs to different shipments in a single slot in a cart:
1.	Adds a new "DummyCaseID" source under the Cart Location barcode type with the translation sequence number as 1.
2.	Configures the Pick Location Assignment (PLA) to perform batch pick.
3.	Configures the Batch Pick Task Type with "Number of shipments allowed per location in the equipment is 1", and "Apply license plate number while picking".
4.	Creates two shipments, includes them in a wave, releases the wave, and creates a batch for the wave.
5.	Inducts the batch into a cart, and picks shipments into the cart.
Defect ID	180295
Case ID	00023536
Description	When a user performs the following sequence of actions, the application displays only two shipments with the OrderAvailableOnSystem set as either Yes or No:
1.	Creates two shipments with the OrderAvailableOnSystem set as Yes.
2.	Creates two more shipments with the OrderAvailableOnSystem set as No.
3.	Searches for the shipments created in steps 1 and 2.
4.	In the search results page, cancels one of the four shipments displayed in the shipment list.
5.	Selects the appropriate cancellation reason code, and clicks the “Save” button.
Defect ID	180422
Case ID	Internal
Description	When a user exit is implemented and enabled in the Configurator, the application does not pass the correct get next task element to the user exit.
Defect ID	181014
Case ID	Internal
Description	The application does not permit a user to add taxes with a charge category discount at the order header level.
Defect ID	181684
Case ID	Internal
Description	When a user performs the following sequence of actions, the application displays the reference attribute value as blank in the ChargeSummary tag:
1.	Invokes the changeOrder API on a fully invoiced order.
2.	Ensures that the input XML has lineCharges with the reference value as NOT NULL.
3.	Invokes the getOrderInvoiceDetails API for the adjustment invoice created by the application in step 2.
Defect ID	182625
Case ID	Internal
Description	When a user performs the following sequence of actions, the application displays a “WMS00004: CaseId/PalletId does not exist” error message:
1.	Configures a task type as follows:
•	Perform task using Activity OrderPick
•	Pick directly against equipment
•	Use FORKLIFT as the primary equipment type
•	Apply license plate number during the picking operation
•	Pack while pick
•	Use system containerization
•	Perform pick task using the mobile device
•	Dispatch tasks as soon as they are generated
•	Use pick sequence for picking
•	Use putaway sequence for putaway
2.	Creates an LPN, and adjusts the inventory.
3.	Creates a shipment such that a full LPN pick is performed, includes it in a wave, assigns a lane for the wave, and releases the wave.
4.	Logs in to the Sterling Mobile Application, and scans a pallet.
5.	Scans a new case and the item ID.
6.	Navigates to the “Deposit” screen.
Defect ID	182883
Case ID	Internal
Description	When a user creates an extended status of Cancel Order, and navigates to Modification Rules for Sales Order > Change Promotion, the application does not display the extended status of Cancel Order.
Defect ID	182892
Case ID	Internal
Description	When the “Cancel lines on inventory shortage” rule is set up, and an order that has work orders and order lines is in “Delivered” status, the application throws a java.lang.StackOverflowError error if the scheduleOrder API is invoked.
Defect ID	182901
Case ID	00031639
Description	When a user performs the following sequence of actions, the inherited disposition code is not used as the default value in the HSDE screen:
1.	Creates an enterprise, for example, E1, that inherits the properties from the DEFAULT enterprise.
2.	Configures E1 as a participating enterprise for a node, for example, N1, that has the DEFAULT enterprise as the primary enterprise.
3.	Configures a “GOOD” disposition code for the DEFAULT enterprise in the Supply Collaboration module.
4.	Loads N1 / DEFAULT, performs the following configurations for the receiving preference, and clicks the “Save” button: 
•	Shipment entry allowed 
•	Build Case / Build Pallet > Optional 
•	Disposition Code Details > Associate Disposition code for receipt without QC as GOOD from the drop-down list.
•	Map the disposition code to the inventory status.
6.	Opens the Receiving HSDE at the shipment or receipt level, or scans any of the two cases in the Receiving HSDE directly.
Defect ID	182914
Case ID	Internal
Description	If a sales order is purged before the associated transfer order is purged, the application throws an “Invalid Order” exception when purging the transfer order from the history table.
Defect ID	182917
Case ID	00032134
Description	When a user performs the following sequence of actions, the application does not display the inherited reason codes in the reason codes list even if the enterprise inherits the configuration from another enterprise:
1.	Creates an enterprise, for example, E1, that inherits the properties from the DEFAULT enterprise.
2.	Configures E1 as a participating enterprise for a node, for example, N1, that has the DEFAULT enterprise as the primary enterprise.
3.	Configures a “GOOD” disposition code for the DEFAULT enterprise in the Supply Collaboration module.
4.	Loads N1 / DEFAULT, performs the following configurations for the receiving preference, and clicks the “Save” button: 
•	Shipment entry allowed 
•	Build Case / Build Pallet > Optional 
•	Disposition Code Details > Associate Disposition code for receipt without QC as GOOD from the drop-down list.
•	Map the disposition code to the inventory status.
5.	Creates an inbound shipment from the N1/E1 combination.
6.	Starts the receipt of the shipment created in step 5, enters the disposition code configured in step 4, and moves the receipt to "Receipt In Progress" status.
7.	Opens the receipt again and adjusts the item quantity.
8.	In the “Modification Reason” pop-up window, clicks the “Reason Code” look-up icon.
Defect ID	183003
Case ID	00021334
Description	The Sterling Mobile Application terminals must be enhanced to display the minimum number of system-pickable inventory and task quantity when executing tasks of the following configuration:
•	A ship node must have at least one task type configured such that it satisfies the following conditions:
•	Activity code as "Replenishment".
•	Generated tasks will be released based on the target location capacity.
•	Equipment must be used when performing pick operations.
•	The picker must perform tasks of Outbound, Replenishment, or Retrieval activity codes.
Defect ID	183343
Case ID	00030675
Description	When more than 1000 orders are created, with each order having only one order line, and the getOrderLineList API is invoked with the value of "MaximumRecords" being passed as more than 1000, the getOrderLineList API locks YFS_ORDER_HEADER for some of the orders.
Defect ID	183579
Case ID	00020099
Description	If a discrepancy exists in a receipt, and a user invokes the closeReceipt API to close this receipt, or triggers the Receipt Complete agent, the application incorrectly closes the receipt.
Solution: The system has been enhanced to invoke a new YFSBeforeCloseReceiptUE user exit from the closeReceipt API and the Receipt Complete agent.
If the YFSBeforeCloseReceiptUE user exit is implemented and invoked from the closeReceipt API with the CanReceiptBeClosed attribute passed as “N” in the output of the YFSBeforeCloseReceiptUE user exit, the application will display a “Receipt cannot be closed” error message.
In addition, if the YFSBeforeCloseReceiptUE user exit is invoked from the Receipt Complete agent with the CanReceiptBeClosed attribute passed as “N” in the output of YFSBeforeCloseReceiptUE user exit, the application will ignore this receipt and continue to process other receipts.
Defect ID	183714
Case ID	00031667
Description	When a user performs the following sequence of actions, the application allows the user to remove 3 units from the shipment:
1.	Navigates to Sterling Warehouse Management System > Receiving > Document Specific > Purchase Order > Receipt Modification Rules > Group By Status > Received > Receipt, and enables the Disallow modification for Unreceive option.
2.	Creates an inbound shipment with the quantity as 10 units, and confirms the shipment.
3.	Starts the receipt for the shipment confirmed in step 1, and receives all 10 units as loose SKUs.
4.	Closes the receipt such that the inbound shipment moves to the "Receipt Closed" status, and the receipt moves to the "Received" status.
5.	Navigates to Receipt Summary > Items panel, and selects the record.
6.	Clicks “Adjust Receipt”, and selects the inventory status. 
7.	Specifies the quantity to receive as 3 units, and clicks on Adjust.
Defect ID	184647
Case ID	Internal
Description	When the Apply price change to invoiced quantity option is enabled, and the charge per line and charge per unit are added to a partially invoiced quantity, the charge per line is invoiced even if the order line is only partially invoiced.
Hot Fix ID	8.0-HF37
Defect ID	164009
Case ID	Internal
Description	When a user performs the following sequence of actions, the getWorkOrderAppointmentOptions API displays the slot as available even though the YFSGetExternalResourceCapacityUE user exit returns the information that no capacity is available for that slot. The application incorrectly uses the prereserved capacity to display the slot as available:
1.	Implements the YFSGetExternalResourceCapacityUE user exit. (The YFSGetExternalResourceCapacityUE user exit returns the information that no capacity is available.)
2.	Ensures that a work order that has an appointment exists.
3.	Invokes the getWorkOrderAppointmentOptions API to request the capacity availability to change the appointment of the work order.
Solution: A new "Ignore prereserved capacity when recomputing appointment options" flag has been exposed in the “Inventory Capacity Rules” screen in the Sterling Supply Chain Applications Configurator. If this flag is selected, the application will not consider the prereserved capacity for capacity calculations.
Defect ID	175974
Case ID	00019032
Description	After a sales order is created with header charges and is invoiced after upgrading to Sterling Multi-Channel Fulfillment Solution, Release 8.0, and the getOrderInvoiceDetails API is invoked, the application displays an “Invalid Charge Category” error message.
Defect ID	176739
Case ID	Internal
Description	The application does not permit a user to update the expiry date of a credit card.
Solution: The application has been updated such that the user can change the expiry date of a credit card at any time. The “AllowPaymentMethodInfoOverride” payment method level flag must be set to “Y” when changing the expiry date.
The “Order Payment Information” screen in the Sterling Console has been modified as follows:
7.	The “Expiration Date” field is editable.
8.	A new “Change Payment Information” check box has been included. This check box must be selected if the user wants to change the expiry date of a credit card.
Defect ID	177199
Case ID	Internal
Description	When a user performs the following sequence of actions, the scheduleOrderLines API throws a “Null Pointer” exception:
8.	Creates a sales order with one order line and an associated delivery line.
9.	Ensures that inventory does not exist for the item.
10.	Creates a work order.
11.	Takes an appointment for a date in the future.
12.	Invokes the scheduleOrderLines API to schedule the sales order created in step 1.
Defect ID	178025
Case ID	Internal
Description	When creating a batch for a set of tasks belonging to a task type and associated to an equipment, the application assigns the tasks in a random sequence to the slots that are defined in the equipment.
Defect ID	178047
Case ID	Internal
Description	When a user creates an order with two standalone provided services in two different ship nodes, and invokes the generateWorkOrder API with the ConsolidatePSLinesWithSameAddress set to “Y”, the application displays a "Mismatch on the ship nodes of work order and the lines added to the work order" error message.
Defect ID	180287
Case ID	00023540
Description	When a user performs the following sequence of actions, the application displays the cancellation codes of both the enterprises in the “Cancellation Reason Codes” drop-down list in the “Cancel Selected Shipments” screen:
7.	Creates two enterprises in the Configurator.
8.	Configures the modification reason codes for sales order and transfer order for the two enterprises created in step 1.
9.	Creates a shipment for one of the enterprises.
10.	Logs in to the Sterling Application Console as a node user.
11.	Navigates to the Outbound Shipment Console, and searches for the shipment created in step 3.
12.	Clicks the “Cancel” button in the “Shipment Details” screen to cancel the shipment.
Solution: The enterprise code is included in the input XML of the getCommonCodes API to enable the filtering of the reason codes at the enterprise level.
Defect ID	180470
Case ID	00021488
Description	When a user confirms a work order, the VAS station requires the user to enter the serial number with the corresponding lot and item information of one kit at a time. Thus, if there are a large number of kits, the confirmation process becomes laborious. Therefore, the application must be enhanced with the capability to allow the confirmation of multiple units of serial-tracked kits in a VAS station.
Defect ID	180854
Case ID	00024900
Description	When a user completes a task, ensures that the requisite serial number is displayed in the “Task Detail” screen, and clicks “Save” in the “Complete Task” screen, the application displays a “Serial tracking mandatory for the Item” error message.
Defect ID	181236
Case ID	Internal
Description	When a user performs the following sequence of actions, the application does not assign the correct pipeline to the order:
1.	Defines a new Hub rule for the “productline” attribute.
2.	Creates a new item with the “productline” attribute as defined in step 1.
3.	Creates an order for the item defined in step 2 in the Sterling Supply Chain Applications Console.
Defect ID	181817
Case ID	00027530
Description	When a user performs the following sequence of actions, the application sets the expected ship date to an invalid future date:
1.	Creates a purchase order.
2.	Invokes the changeOrderSchedule API, sets the expected delivery date to HIGH_DATE, and the expected ship date to a specific date.
3.	Invokes the changeOrderSchedule API again and sets the expected delivery date to HIGH_DATE, but does not provide the expected ship date.
Defect ID	181841
Case ID	Internal
Description	When a user creates a return order with header charges, creates an exchange order, and cancels the return order, the application does not update the value of the “Pending Transfer In” amount to zero.
Defect ID	182034
Case ID	00027232
Description	When a user performs the following sequence of actions, the application displays the calendar one day ahead of the current date:
1.	Creates a new locale in the Configurator such that the locale details are specific to United Kingdom.
2.	Navigates to the “Order Search” screen, and clicks the “Calendar” hyperlink.
Defect ID	182690
Case ID	00024430
Description	When an agent is hosted on a JVM that is configured with a large number of threads and connected to a relatively slow JMS server, the agent fails to obtain the processing message after the first few initial batches.
In the scenario described here, the user has to re-trigger the agent manually in order to restart the agent.
Hot Fix ID	8.0-HF36
Defect ID	161992
Case ID	Internal
Description	When an item-level count task is assigned to a user through the Sterling Application Console, the “UnitOfMeasure” field is blanked out.
Defect ID	165151
Case ID	Internal
Description	The Confirm Shipment agent throws an "Invalid user" error message when a shipment has open tasks that have to be cancelled.
Defect ID	169354
Case ID	Internal
Description	The releaseWave agent goes into an unbounded recursion that causes a heap dump when acquiring a transaction lock on a database whose table space is full.
Defect ID	176748
Case ID	Internal
Description	When a user performs the following sequence of actions, the application does not differentiate between the lot numbers of this product class, and a task for the LPN quantity of this product class moves to “In-progress” status:
1.	Configures a tag-controlled item with the lot number as the tag identifier.
2.	Ensures that inventory for the item configured in step 1 exists in pallets such that the pallets have the tag-controlled item with mixed product class lot numbers.
3.	Creates a shipment for the tag-controlled item of a product class for which the mixed lot numbers are stored in the pallets.
4.	Includes the shipment created in step 3 in a wave, and releases the wave.
5.	The user scans the pallet in the “Outbound Pick” screen.
Solution: The application has been enhanced to display the “Item Entry” screen in which the user must scan the appropriate Item ID, scan the lot number, and the appropriate quantity for this lot.
Defect ID	176759
Case ID	Internal
Description	When a user performs the following sequence of actions, the application throws a "No record found for passed inputs" error message again:
1.	Configures a 2D bar code by setting up an external bar code service.
2.	Ensures that the inventory for a tag-controlled item exists in LPNs such that the pallets have mixed product class and mixed tag identifiers for an SKU.
3.	Creates a shipment for the SKU mentioned in step 2 for a particular product class, includes this shipment in a wave, and releases the wave.
4.	The application generates the outbound pick tasks.
5.	The user navigates to the “Outbound Pick” screen in RF, scans the pallet, and scans the 2D bar code for the wrong product class and tag identifier.
6.	The application throws a "No record found for passed inputs" error message.
7.	The user navigates back to the “Item Entry” screen, and scans the correct 2D bar code for the corresponding product class and tag identifier.
Defect ID	176978
Case ID	Internal
Description	When a user performs the following sequence of actions, the Sterling Mobile Application displays a “WMS00119: Cannot deallocate location inventory” exception error message:
1.	Ensures that an LPN that contains inventory for a tag-controlled item having multiple lots exists at a pick location.
2.	Creates a shipment for the item mentioned in step 1 for the quantity present in the LPN, includes the shipment in a wave, and releases the wave.
3.	Logs in to the Sterling Mobile Application and scans the LPN.
Defect ID	178170
Case ID	00020627
Description	When a user performs the following sequence of actions, the Sterling Mobile Application throws a null pointer exception:
1.	Configures an order pick task with the “Pack While Pick” task type and the “Apply Label” task type.
2.	Adjusts the inventory at a location.
3.	Creates a shipment, includes it in a wave, assigns a lane for the wave, and releases the wave.
4.	Logs in to the Sterling Mobile Application, performs the pick task, and navigates to the “Deposit” screen.
Defect ID	179448
Case ID	00020796
Description	When a user performs the following sequence of actions in the Sterling Warehouse Management System, Release 8.0, the application does not assign P2 to print the output of ReceivingWorkSheet from S2. Instead, P1 is always selected. In other words, only one printer is assigned irrespective of the associated dock station:
1.	Configures two receiving docks, and associates the dock locations to two dock stations, for example, S1 and S2.
2.	Associates two printers, for example, P1 and P2, to the dock stations, S1 and S2, respectively.
3.	Ensures that only one printer associated with one dock station. Otherwise, the application will return the all the printers that are associated with the workstation, which, in turn, may not honor the set criteria.
4.	Enables an event that has the “YNW_PrintReceivingWorkSheet_80” out-of-the-box service in order to print the receiving worksheet at the start of the inbound shipment receipt.
5.	Creates an inbound shipment, confirms the shipment, and starts the receipt of the inbound shipment.
6.	Selects S2 for receiving the inbound shipment.
Note: The scenario described here will work correctly only after applying Sterling Warehouse Management System, Release 8.0, hot fix 3.
Defect ID	179967, 181806
Case ID	00019092, Internal
Description	When a user invokes the reserveAvailableInventory API for few quantities of an item that has zero inventory, and sets the “UseUnplannedInventory” attribute as “Y”, the application reserves the inventory, but does not provide the user with information about the quantity of the item reserved from the unplanned inventory. In addition, the value of the “productAvailabilityDate” attribute is not displayed in the output of the API.
Defect ID	182016
Case ID	Internal
Description	When an item has a preferred substitute, the “ItemID” attribute in the UnavailableLines does not have the correct value. In addition, a new “NewItemId” attribute must be included in the findInventory API.
Defect ID	180072
Case ID	00023708
Description	The getInventorySnapshot API takes a large amount of time to process the records in the YFS_INVENTORY_DEMAND table. Therefore, this API must be optimized to improve the performance.
Defect ID	180096
Case ID	00022657
Description	When a user performs the following sequence of actions, the application displays the “Save Changes” pop-up window even if the user has not made any changes in the “Fulfillment Summary” screen:
1.	Ensures that the “Display Shipping and Delivery Fulfillment Options Separately” check box is unselected in the “Order Entry” configuration screen in the Sterling Customer Order Management Configurator.
2.	Ensures that an item that has only the shipping and pickup fulfillment options allowed exists.
3.	Logs in to the Sterling Customer Order Management client, adds a customer, and adds the item mentioned in step 2 to an order.
4.	Selects “Shipping” as the fulfillment method, and proceeds to the “Fulfillment Summary” screen.
5.	Clicks “Previous” in the “Fulfillment Summary” screen.
Solution: The application has been improved such that the “Save Changes” pop-up window will not be displayed if no changes are performed in the “Fulfillment Summary” screen.
Defect ID	180193
Case ID	00022476
Description	When a user performs the following sequence of actions, the application does not populate the “Reference” attribute in the “linecharge” element:
1.	Ensures that the input XML of the changeOrder API has line charges, with the value of the “Reference” attribute as “NOT NULL”.
2.	Invokes the changeOrder API for a completely invoiced order.
3.	Invokes the getOrderInvoiceDetails API for the adjustment invoice created by the changeOrder API in step 2.
Defect ID	180244
Case ID	00019997
Description	The application does not transfer the control to the custom implementation for the YRCRelatedTasksDisplayer Extension point, and instead executes the default implementation for the YRCRelatedTasksDisplayer Extension point.
Solution: The application has been improved such that the custom implementation is executed instead of the default implementation for the YRCRelatedTasksDisplayer extension point.
Defect ID	180560
Case ID	00017731
Description	When a user tries to deposit two or more SKUs from a pallet to a location, the application provides only one option to the user to deposit the SKUs in a single operation.
Solution: The application has been enhanced such that the user can configure the "yfs.deposit.units.separately.for.tasktypes" property to provide a list of task types. The user can use a suitable task type in the list to deposit each SKU separately.
When depositing such tasks, the user must scan the SKU, and deposit each SKU separately.
Defect ID	180604
Case ID	00024415
Description	When the template of the getOrderList API contains the “OrderStatus” element and at least one of the following attributes, and a user invokes the API, blocking locks occur:
•	StatusDescription
•	ShipNode
•	ProcureFromNode
•	ReceivingNode
•	MergeNode
•	ExpectedDeliveryDate
•	ExpectedShipmentDate
•	<Details> node under </OrderStatuses>
Defect ID	181098
Case ID	Internal
Description	When the replenishment task type is configured to “Apply License Plate Number While Picking”, and a user performs a replenishment task by picking an inventory from the pallet or case through the Sterling Supply Chain Mobile Application, the system does not mandate the scanning of the pre-printed license plate.
Defect ID	181159
Case ID	00025357
Description	When a user performs the following sequence of actions, the application blanks the secondary serial numbers from the target location:
1.	Configures Outbound picking.
2.	Completes the pick tasks through the Console for a serial-tracked inventory with the secondary serial numbers enabled.
Hot Fix ID	8.0-HF35
Defect ID	164013
Case ID	Internal
Description	The Sterling Mobile application throws a “This operation cannot be processed in current task status” exception message when the user rejects a task that is not in the “Suggested” status in the application.
Defect ID	167783
Case ID	Internal
Description	The system does not allow selective packing of shipments based on the shipmentType attribute of the shipment in item-based packing.
Solution: The shipment translator of the translateBarCode API has been enhanced to recognize the shipmentType attribute passed in the shipmentContextualInfo child tag.
Defect ID	167813
Case ID	Internal
Description	When a user performs the following sequence of actions, the application disregards the Standard Carrier Alpha Code (SCAC) value that is blank, and displays all the records: 
1.	Navigates to the “Load List” screen from the “Load Summary Details” screen.
2.	Selects the load summary record that has the “Carrier” field as blank, and clicks the “View Details” hyperlink.
Defect ID	168219
Case ID	Internal
Description	If an inventory that has a user-defined FIFO number belonging to a FIFO-tracked item is present in a case, and a user performs an ad hoc move for this inventory, the system throws a “WMS00153: Inventory mismatch error” message.
Defect ID	168222
Case ID	Internal
Description	When a count task results in a variance, the “Count Request Summary” screen displays the "Net Variance Value" as the "Net Variance Qty".
Defect ID	168239
Case ID	Internal
Description	The application does not have the provision to capture the information pertaining to the Country of Origin (COO) for an item when packing the inventory in the pack station.
Solution: A new boolean resource parameter called “CaptureCOO” has been exposed in the “Pack HSDE” screen. When a user sets the value of this parameter to “Y”, the system will prompt the user to enter the COO when packing loose inventory.
Defect ID	173332
Case ID	00006555
Description	When a user creates locations with infinite and non-infinite capacities in a node and copies the node, the application creates similar locations in the new node, but does not update the node keys for the locations with infinite capacity.
Solution: The query for updating the locations has been enhanced to select the locations with infinite capacity.
Defect ID	176403
Case ID	Internal
Description	When packing a shipment at a pack location by clicking the "Pack Shipment" button in the “Shipment Details” screen, the application does not prompt the user to enter the “CountryOfOrigin” attribute.
Defect ID	176815
Case ID	Internal
Description	The application must be enhanced with the capability to define the cut-off time for all the transfer schedules for each day of a week. In addition, a user must be able to override the cut-off time for specific days.
Solution: The manageNodeTransferSchedule API and the manageNodetranferScheduleOverride API have been enhanced to accept the cut-off time for each day, and for specific days.
If the cut-off time is unavailable, the application will use the value provided in the “yfs.transferPreparation.minTimeReq” system property.
Defect ID	176837
Case ID	Internal
Description	The following APIs must be enhanced to support hang-off for the YFS_SHIPMENT_LINE table:
•	createShipment
•	confirmShipment
•	changeShipment
•	changeShipmentContainer
•	getShipmentDetails
•	getShipmentList
•	getShipmentContainerDetails
•	getShipmentContainerList
•	getShipmentLineList
•	getShipmentListForOrder
Defect ID	177360
Case ID	00019594
Description	The application incorrectly allows a user to adjust the inventory for a bundle parent item.
Solution: The application has been enhanced to display an error message if a user tries to adjust the inventory for a bundle parent item.
Defect ID	178625
Case ID	00020917
Description	When a user performs the following sequence of actions, the move request created by the application has release failures:
1.	Configure a serial-tracked kit is with serial items.
2.	Enable the ON_SKU_PROCESS_COMPLETE / SERIAL_PROC_COMP event to create a move request.
3.	Complete the work order.
Defect ID	178687
Case ID	00021517
Description	When a user performs the following sequence of actions, the application creates a redundant procurement purchase order or procurement transfer order instead of scheduling the order, even if the inventory is available on hand:
1.	Configure the sourcing rules to create a procurement purchase order or a procurement transfer order for an item when scheduling an order for this item.
2.	Create an order for an item that does not have on hand inventory.
3.	Schedule the order created in step 1, and the application creates a procurement purchase order.
4.	Receive the procurement purchase order such that inventory is available on hand.
5.	Release the order and creates a shipment.
6.	Cancel the shipment through the Console, and selects the option to backorder the cancelled quantity.
7.	Try to schedule the order again.
Note: If the order line has the “Procure from node’” option stamped on it, the procurement order will be created irrespective of the quantity of the available on hand inventory.
Note: This fix will affect only those orders that are backordered after applying the fix.
Defect ID	179853
Case ID	00023203
Description	The application throws a null pointer exception if the “Target” element is not passed in the input XML of the splitShipment API.
Hot Fix ID	8.0-HF34
Defect ID	165157
Case ID	Internal
Description	The performance of the PrintDocumentSet API is adversely affected when it is invoked for multiple printDocumentSet elements in a single transaction. The printer/server connection is opened and closed for each element, even if the print request was sent to the same server.
Solution: The connections will be opened only once per API transaction per server. When the PrintDocumentSet API completes all the elements, all the connections will be closed.
Defect ID	170654
Case ID	Internal
Description	The JSP login console should be enhanced to display a detailed error message when a user login fails.
Solution: The console screen can now be configured to display the details of the login error by setting the “yfs.console.login.error.showDetail” property in the yfs.properties file to “Y”. The default value of this property is “N”.
Defect ID	172661
Case ID	00014456
Description	The Sterling Mobile Application must be enhanced to provide a user with the ability to change the source location when performing a pick operation.
Solution: The “Pick Location Confirmation” screen has been enhanced with a valid pick execution exception code. The user must pass this exception code to change the source location when performing a pick operation.
Defect ID	176853
Case ID	Internal
Description	When a user performs the following sequence of actions, the application does not display all the fields in the “Pick Location Assignment” pop-up window because of the large number of UOMs:
8.	Creates a large number of UOMs, for example, 50.
9.	Navigates to Configurator > Packing > Activities > Retrieval Strategy Details > All Items, and clicks the “Add New” icon to display the “UOM Condition” pop-up window.
10.	In the “UOM Condition” pop-up window, clicks the “Modify” icon to display the “Pick Location Assignment” pop-up window.
Defect ID	177182
Case ID	Internal
Description	When a user performs the following sequence of actions, the application repetitively throws a "Secondary Serial #1: {0} must be entered" error message:
1.	Configures a kit with two serial-tracked items.
2.	Performs de-kitting on the kit created in step 1.
3.	Skips the secondary serial number and tabs out to move the control to the “Close” button.
4.	Tabs out again to transfer the control from the “Close” button to the “Serial Number” field.
Defect ID	177368
Case ID	00020344
Description	The application must be enhanced with the capability to permit a user to implement and invoke the extended database API methods without creating a service for each of the methods.
Solution: The multiAPI has been enhanced with the capability to also invoke the extended database APIs. The “IsExtendedDbApi” attribute must be included in the API tag in the multiAPI input, and set to “Y” to invoke the extended database APIs.
Defect ID	177706
Case ID	00020504
Description	When a user extends the “Alerts List” screen by adding a column of fixed width through the Extensibility tool, and performs a search operation, the application resizes the extended column.
Solution: A new “Resizable” check box has been added to the LayoutSetupWizardPage. If this check box is selected, the table column can be resized. This check box is selected by default for the newly added table columns. For an existing table column, the resizable property is picked up from the getResizeable method pertaining to the column.
Defect ID	177880
Case ID	00020478
Description	When a custom implementation of the DataFormatter extension point is provided for the “Ordered Quantity” field, the YRCDataFormatter causes a NumberFormatException.
Defect ID	178052
Case ID	Internal
Description	When the ON_SUCCESS event is configured for the CHANGE_ORDER transaction, and a shipment is created for an order, the application invokes the ON_SUCCESS event. The ON_SUCCESS event is invoked even if the user cancels the shipment.
Defect ID	178112
Case ID	00020929
Description	When a custom implementation of the DataFormatter extension point is provided for the “DayPhone” attribute, which also has an extension point in the Sterling Call Center application, the application incorrectly picks the implementation in the Sterling Call Center.
The custom implementation of the extension for the “DayPhone” attribute must override the implementation in the Sterling Call Center.
Defect ID	178119
Case ID	00019971
Description	When the REALTIME_ATP_MONITOR agent is run, SQL statements are being logged even if the trace is not enabled.
Defect ID	178143
Case ID	00020184
Description	When installing Web services on the Sterling Multi-Channel Fulfillment Solution with the Sterling Networked Warehouse Management System installed on the IBM WebSphere Application Server, the installation fails with a “Class could not be located” error message.
Defect ID	178182
Case ID	Internal
Description	When a user performs the following sequence of actions, the application enables the “Add Association” option and the “Modify Association” option for users having read only permissions:
1.	Creates a user and assigns “Read Only” permissions to the Product Management module.
2.	Logs in to the application as the user created in step 1.
3.	Navigates to Product Management > Item > Item Details, and clicks the Association tab.
Defect ID	178416
Case ID	00004831
Description	When a user performs the following sequence of actions, the application displays an “ORA-01795: Maximum number of expressions” error message:
1.	Creates a large number of vendors, for example, more than 1000, for an enterprise.
2.	Configures the vendors created in step 1 to serve as both sellers and nodes.
3.	Creates a reservation for an item under a vendor using the createOrder API.
4.	Invokes the getReservation API for any vendor.
Defect ID	178418
Case ID	Internal
Description	The application does not propagate a change in the trailer number of the load to the shipments associated with the load.
Defect ID	178421
Case ID	00020920
Description	When a user performs the following sequence of actions, the application displays an "Inventory for the SKU does not exist in the location or case/pallet to perform the inventory operation" error message:
1.	Creates the following inventory statuses:
a.	Normal (N)
b.	Held (Q)
c.	Repaired (A)
2.	Creates a location, for example, L1, in a zone, for example, Z1.
3.	Configures the inventory status transition rules for Z1 as follows: 
d.	From blank to N
e.	From Q to A
4.	Invokes the changeLocationInventoryAttributes API multiple times to move the status of the inventory in L1 through the following cycle:
N - Q - A - N
Defect ID	178501
Case ID	00021643
Description	The yantra.ear build fails on the JBoss server after application of the Hot Fix 33.
Defect ID	178795
Case ID	Internal
Description	When a serial tracked kit containing serial tracked components is de-kitted, the parent kit key references are not reset in the component serial records in the database.
Solution: De-kitting a serial kit with serial components will remove the parent kit reference from the kit components.
Hot Fix ID	8.0-HF33
Defect ID	155104
Case ID	Internal
Description	When a user performs the following actions during packing using the “Pack HSDE” screen, the system throws a "WMS00227: Inventory for the SKU does not exist" exception: 
1.	Configures the Pick Location Assignment (PLA) to perform the item pick operation and dynamically slots the inventory from the pack staging area to the pack area.
2.	Sets the task type to “Pick into Inventory Pallet”.
3.	Creates two pallets in bulk location with two different “Ship By Date” attribute for the time-sensitive item.
4.	Adjusts inventory for the item at pack location with a shipping date that is different from the dates mentioned in step 3.
5.	Picks one of the pallets and deposits the pallet in the pack staging area.
6.	Scans an inventory pallet in the “Pack Initiation” screen.
7.	Selects an item to be packed for a shipment from the pallet.
Defect ID	155502
Case ID	Internal
Description	When the addToContainer API is invoked to pack a time-sensitive item, a query on the YFS_SHIPMENT_TAG_SERIAL table is called with the table column CONTAINER_DETAIL_KEY=“null”. This is a redundant query and must not be called.
Defect ID	156790
Case ID	Internal
Description	When a node has more than 75 participating enterprises and a user tries to onboard an enterprise for the node, the “Model Enterprise” field does not populate the selected enterprise in the text box.
Solution: The user can manually populate the selected enterprise in the text box using the “Search” screen.
Defect ID	157353
Case ID	Internal
Description	When a user runs the Inventory Purge agent, and a record in the yfs_inventory_demand table is updated after the Inventory Purge agent has picked up the record, but before the yfs_inventory_demand table is purged, the Inventory Purge agent causes a discrepancy in demand.
Defect ID	161505
Case ID	Internal
Description	The WAVE_RELEASE transaction throws an "Out of Memory" exception when a wave with more than 50,000 shipments is released.
Defect ID	161964
Case ID	Internal
Description	When a user performs the following sequence of actions, the drop-down list in the “Onboard New Enterprises” pop-up window displays the number of enterprises that are to be on-boarded as 75 instead of the 80 that are available for on-boarding:
1.	Creates more than 75 enterprises for on-boarding, for example, 80 enterprises.
2.	Ensures that the “Seller” check box in the “Roles and Participation” tab is selected, and creates an nWMS node and launches this node from the Configurator, with the application as “Warehouse Management”.
3.	Clicks the “Onboard New Enterprises” icon. (The system launches the “Onboard New Enterprises” pop-up window).
Solution: A “Look-Up” menu has been provided that displays the list of enterprises that have been on-boarded and the enterprises that are yet to be on-boarded.
Defect ID	161989
Case ID	Internal
Description	When a user tries to create count requests for more than 5000 locations through the “Create Count Requests for Location Range” menu, the system considers only 5000 locations, and throws error messages.
Solution: A CreateCountRequestForLocationRange synchronous service has been provided. This service will send a message containing the criteria passed by the user from the user interface to the JMS queue. A new Create Count Request For Location Range transaction has been added to listen to the JMS queue for messages. The user should run the Agent Server associated with the criteria ID.
Defect ID	163446
Case ID	Internal
Description	The “Create Count Request For Location Range” transaction does not have an event that can be used to determine whether the agent has processed all the locations.
Solution: A “Locations Processed” event has been added to the “Create Count Request For Location Range” transaction. This event will publish the agent criteria. This event will be raised after all the locations in the locations range have been processed for count request creation. This event will be raised even if the count request creation fails for some of the locations.
Defect ID	163995
Case ID	Internal
Description	The application should have a provision to count an item inside an LPN, which systematically has SKU other than that suggested for the count.
Defect ID	164001
Case ID	Internal
Description	The application should have a provision to count the misplaced item inside an LPN, which systematically has SKU other than that suggested for the count. When a user accepts the variance for the count, the application should adjust the inventory inside the LPN for the misplaced item.
Defect ID	164007
Case ID	Internal
Description	When a user performs the following sequence of actions, the releaseTask agent releases the tasks in the low-priority wave even if a high-priority wave that has an item in common with the low-priority wave is in “Released” status:
1.	Selects the "Dispatch Task When Inventory is available for Pick" check box in the “Task Type Configuration” screen and sets the yfs.releasetask.ignore.wavesequence property to “Y”.
2.	Ensures that the inventory for a wave with low priority is available in the pick location.
3.	Releases a wave of high priority that has an item in common with the low-priority wave.
4.	Ensures that the tasks for both the waves are in the “Held” status.
5.	Runs the releaseTask agent.
Defect ID	165774
Case ID	00004393
Description	The Saved Search feature does not work in the context of the out-of-the-box reports.
Note: Unlike the saved search behavior in the console screens, the report will not be automatically executed when creating a saved search for a report screen.
Defect ID	166778
Case ID	Internal
Description	When a user performs the sequence of actions described here, the application creates replenishment tasks from the bulk zone to the location of larger size code for both the shipment lines:
1.	Configures the forward pick zone to contain a location that is divided into two location size codes, one larger than the other.
2.	Creates a wave with two shipments, with each shipment containing one item.
3.	Ensures that the item that comes first when both the items are arranged in alphabetical order cannot fit in the location with the smaller size code because of a larger dimension, but will fit in the location with the larger size code.
4.	Ensures that the item that comes second when both the items are arranged in alphabetical order will fit in the location with the smaller size code.
5.	Releases the wave that was created in step 2.
Defect ID	167768
Case ID	Internal
Description	Issue 1: The application does not have the provision to restrict the shipment group determination when creating an outbound shipment.
Issue 2: The Create Wave For Shipment Group agent does not have the provision to determine the shipment groups of shipments that are not associated to any shipment group and re-determine if the shipment is already associated with a shipment group.
Solution: Issue 1: A new "yfs.determine.shipmentgroup.for.shipment" property has been exposed such that, when set to "N", it will prevent the shipment group determination during shipment creation.
Issue 2: The Create Wave For Shipment Group agent has been enhanced to determine the shipment group for those shipments that do not have any shipment group associated with them and re-determine if the shipment is already associated with a shipment group. For more information about this agent, see Section A.2.12 “Create Wave For Shipment Group” in the Sterling Warehouse Management System Configuration Guide.
Defect ID	167801
Case ID	Internal
Description	When a user performs the following sequence of actions, the getShipmentList API takes 20-40 seconds to perform a query:
1.	Ensures that shipments exist in a wave.
2.	Navigates to the wave console.
3.	Prints the wave.
Solution: IgnoreOrdering="Y" has been added to the input of the getShipmentList API.
Defect ID	170027
Case ID	Internal
Description	When a user performs the sequence of actions described here, the application throws a concurrent modification exception error:
1.	Configures two locations in a forward pick zone such that one of the locations has a smaller location size code than the other.
2.	Ensures that a wave with three shipment lines with one item each exists such that when all the items are arranged in an alphabetical order, the item that comes first cannot fit in the location with the smaller size code because of one its dimensions. (However, this item can fit in the location with the larger size code. Also, all the other items can fit in the location with the smaller size code.)
3.	Releases the wave.
Defect ID	170389, 176084
Case ID	Internal
Description	When a user configures more than 75 enterprises for a node and tries to add a new shipment selector in Pick > PickPlanning, the application does not display the “Lookup” icon in the “Enterprise Code” field in the “Shipment Selector” screen.
Solution: The “Lookup” icon has been added to the “Enterprise Code” field in the “Shipment Selector” screen so that the user can search for an enterprise.
Defect ID	171540
Case ID	00012740
Description	When a user adds two new load shipments to an existing load of 10,000 load shipments, the manageLoad API slows down.
Defect ID	175952
Case ID	00018157
Description	When a user performs the following sequence of actions, the application displays an "Inventory does not match" error message:
1.	Configures an item with more than one UOM.
2.	Creates a count request at the item level, and releases the count request.
3.	Logs in to an RF device, and scans the Item ID of the item configured in step 1.
4.	The application requests the user to scan the UOM of the item.
5.	Scans the UOM of the item configured in step 1.
Defect ID	176122
Case ID	00017185
Description	The application must be enhanced with an API that has the capability to add new item alias types.
Solution: A new manageCommonCode API has been exposed. For more details about this API, see the corresponding section in the Sterling JavaDocs.
Defect ID	176342
Case ID	00019204
Description	When the INVGetExternalSupplyUE user exit is implemented, and the findInventory API is invoked with checkInventory set to “N”, the API performs a redundant call to the INVgetExternalSupplyUE user exit.
Defect ID	176683
Case ID	00019530
Description	When a user performs the following sequence of actions, the icon pertaining to the extended attributes is inactive, and the user cannot open the “Item Instruction Details” pop-up window:
1.	Creates a user and assigns “Read Only” permissions to the Product Management module.
2.	Creates an extended attribute for the YFS_ITEM table.
3.	Logs in as the user configured in step 1.
4.	Navigates to Product Management > Item Details.
Defect ID	176711
Case ID	00019969
Description	When a user performs the following sequence of actions, the application does not display the “Item Instruction Details” pop-up window in the read only configuration. However, when full access is enabled, the “Item Instruction Details” pop-up window is displayed:
1.	Creates a user and assigns read only permissions to the Product Management module.
2.	Creates an item with item instructions.
3.	Logs in as the user configured in step 1.
4.	Navigates to Product Management > Item Details.
5.	Opens the item created in step 2, and selects the Item Instructions tab.
6.	Double-clicks the listed item instruction.
Defect ID	176752
Case ID	Internal
Description	When a user performs the following sequence of actions, the application moves the drop status of the new delivery service line to “Created” instead of to an extended status of the “Created” status:
1.	Configures the service pipeline of a sales order to move the drop status of an order to an extended status of the “Created” status.
2.	Creates an order with two product lines, for example, P1 and P2, and associates both P1 and P2 with a delivery service.
3.	Creates a single work order and moves P1 to the “Completed” status.
4.	Invokes a multiAPI that has the changeWorkOrder API as the first API and the modifyWorkOrder API as the second API. The multiAPI removes P2 from the work order.
5.	Invokes the generateWorkOrder API.
Defect ID	177098
Case ID	Internal
Description	An enhancement was provided in HF29 to correlate an exception message displayed on a screen, with the exception message printed in the log trace. This enhancement associates a unique numeric identifier with each of these exception messages, and suffixes the error description of an exception message with a unique numeric ID.
A control must be provided with this enhancement such that the user can disable the association of a unique numeric ID with the error description of an exception.
Solution: A new yfs.exception.disable.uniqueExceptionId flag has been exposed in the yfs.properties file. This flag is set to “N” by default. If the user does not want to append the unique numeric ID to the error description of an exception, this flag must be set to “Y”.
Defect ID	177109
Case ID	00015082
Description	When a user performs the following sequence of actions, the “Value Details” screen hangs, and the application server crashes:
1.	Ensures that a large number of items exist for an enterprise, and all the items are associated with a classification.
2.	Navigates to Configurator > Product Management > Classification Hierarchy.
3.	Right-clicks a classification value, and selects "Value Details" from the drop-down menu.
Solution: The application has been enhanced to display a maximum of 100 item records. The user can right-click the “Item ID” column and search for more items if necessary.
Defect ID	177245
Case ID	00019969
Description	The application does not display the “Item Instruction Description” button in the Product Management > Item Details to the user if the user belongs to a group that has read only permissions to the Product Management module.
Defect ID	178180
Case ID	Internal
Description	In the Sterling JavaDocs, the “Database Extensibility Support” property is set to “Yes”. However, the associated YFS_COMMON_CODE table and the YFS_COMMON_CODE_ATTRIBUTE table are not extensible.
Solution: The “Database Extensibility Support” property is incorrectly set to “Yes” in the Sterling JavaDocs. The property must be set to “No”.
Hot Fix ID	8.0-HF32
Defect ID	149177
Case ID	Internal
Description	When a user, while confirming a work order for kitting a serial tracked item that is “Always Tag Controlled” with the “Tag Attributes” defined, enters the serial number of the parent item, the system prompts the user to enter the tag identifier. The system should also prompt the user to enter the tag attributes.
Defect ID	161545
Case ID	Internal
Description	The system has to be enhanced to log a reason for the failure of the work order release when the releaseWorkOrder API is invoked for a work order that does not have the “Preferred Location” assigned for its work order activity.
Defect ID	161922
Case ID	Internal
Description	When a user performs the following sequence of actions, the system does not permit the user to override the suggested task:
1.	Configures three items with the UOM as each, pallet, and case respectively.
2.	Ensures that the three items are available at the same location and creates move request for each item.
3.	Logs in to the RF device, navigates to putaway, and scans an item.
4.	Tries to override the item suggested by the system and scan another item from the three items that was configured in step 1.
Defect ID	162810
Case ID	Internal
Description	When inventory that is received against a receipt number is moved using the Ad-hoc Putaway task option, the system does not retain the receipt number at the destination location.
Solution: If the receipts are not being mixed, and when inventory received against a receipt number is moved using the Ad-hoc Putaway task option, the receipt number will be retained at the destination location.
Defect ID	167807
Case ID	Internal
Description	The application should be enhanced to provide a user with a provision to accept a putaway task that is suggested to another user.
Solution: In the Putaway menu resource, an "AutoAccept" Boolean parameter should be passed in the URL. When this parameter is passed as “N”, the application will retain the task in “Open” status if the task is suggested to a user, and will accept the status when the user starts the pick process.
Defect ID	168617
Case ID	00007757
Description	A new API must be introduced in the application to fetch the list of departments pertaining to a given organization.
Solution: A new getDepartmentList API has been included in the application. For more information about this API, see the corresponding section in the Sterling JavaDocs.
Defect ID	172267
Case ID	Internal
Description	The Sterling Multi-Channel Fulfillment Solution Installation Guide and the Sterling Multi-Channel Fulfillment Solution Localization Guide must be updated with information about using the AL32UTF-8 character set or the UTF-16 character set for the Japanese locale.
Solution: The Sterling Multi-Channel Fulfillment Solution documentation has been updated as follows:
•	A note has been added to Section 2.3, "Database Overview" in Chapter 2, "Localizing the Sterling Multi-Channel Fulfillment Solution" of the Sterling Multi-Channel Fulfillment Solution Localization Guide.
•	A note has been added to Section 5.2, "Installing Oracle (UNIX/Linux)" in Chapter 5, "Installing and Configuring Database Tier Software on UNIX/Linux" of the Sterling Multi-Channel Fulfillment Solution Installation Guide.
•	A note has been added to Section 6.4, "Installing Oracle (Windows)" in Chapter 6, "Installing and Configuring Database Tier Software on Windows" of the Sterling Multi-Channel Fulfillment Solution Installation Guide.
Defect ID	174352
Case ID	00016358
Description	The application must be enhanced with the capability to void the return order invoice and the manually created sales order adjustment invoice.
Solution: The voidInvoice API has been enhanced to void the return order invoice and the manually created sales order adjustment invoice.
Note: The return order invoice can be voided only if it is not associated with the corresponding exchange order or if the exchange order is entirely cancelled.
Defect ID	174943
Case ID	00017147
Description	When a user performs the following sequence of actions, the application does not display an “Is Location Empty?” confirmation message:
1.	Creates a location with a location size code.
2.	Adjusts the inventory for an item at the location created in step 1.
3.	Creates an outbound shipment for the item, includes it in a wave, and releases the wave.
4.	Performs the pick operation through the Sterling Mobile Application such that all the inventory is removed, and the location is empty.
Defect ID	175126
Case ID	00009446
Description	When the loadInventoryMismatch API is invoked for items that are not defined in the catalog, the application processes the items, and the records are inserted into the YFS_INVENTORY_SUPPLY_TEMP table.
Solution: A new "ValidateItems" flag has been included in the input XML of the loadInventoryMismatch API. The API will insert the item into the YFS_INVENTORY_SUPPLY_TEMP table only if this flag is enabled, and the item is defined in the catalog.
Defect ID	175370
Case ID	00014339
Description	When the getPossibleSchedules API is invoked, the API locks the items in the YFS_INVENTORY_ITEM table, and the locked items are not sorted by ITEM_ID, PRODUCT_CLASS and UOM. Therefore, deadlocks may occur if the getPossibleSchedules API is invoked multiple times involving the same items.
Defect ID	175374
Case ID	00016175
Description	When a user performs the following sequence of actions, the application displays a “java.sql.SQL.Exception: Conversion failed when converting datetime from character string” error message:
1.	Creates an outbound shipment, and completes the pick operation.
2.	Navigates to the pack station, and scans the shipment.
3.	Clicks the “New Case” or “New Pallet” button.
Defect ID	175396
Case ID	00018324
Description	When indices are created in the columns that are defined in the ycp_tables_additions.xml file, the application server start script fails with an "Index column not found in table definition" error message.
Defect ID	175407
Case ID	00017897
Description	When a user performs the following sequence of actions, the application does not retain the FIFO information from the inventory in the target zone:
1.	Configures the replenishment strategy to replenish a zone from another zone.
2.	Performs replenishment at a zone through the Sterling Mobile Application by moving an LPN in a zone containing inventory with FIFO information to another zone that does not track LPN.
Solution: All non-unique inventory attributes such as FIFO, COO, Receipt information, and so on will be retained in the scenario described here.
Defect ID	175455
Case ID	00016844
Description	The YCPMassageApiOutputUE user exit must be enhanced to provide the input to an API as an argument.
Solution: The YCPMassageApiOutputUE user exit has been enhanced to provide the input to an API as an argument in addition to the output and the API name. For more information about the updated method signatures, see the corresponding section in the Sterling JavaDocs.
Defect ID	175610
Case ID	00018314
Description	The “Recompute Cost” option is not disabled in the Sterling Configurator > Product Management > Products > Items screen even if the user belongs to a group that has read-only permissions to the Product Management > Products > Items screen.
Defect ID	175631
Case ID	Internal
Description	When a user tries to customize an existing screen by adding an external panel through the Extensibility tool, the application throws a null pointer exception.
Defect ID	176022
Case ID	Internal
Description	When the LocalizedStringReconciler tool is run in the IMPORT mode in Microsoft SQL Server, the tool displays a "The data types text and varchar are incompatible in the equal to operator" SQL exception error message.
Solution: The data type for the YFS_LOCALIZED_STRINGS.ORIGINAL_DESCRIPTION column and the YFS_NONLOCALIZED_STRINGS.VALUE column has been changed to NonUnicode-Text-2000 and NonUnicode-Text-4000 respectively, for the Microsoft SQL Server.
Defect ID	176814
Case ID	Internal
Description	The following screens in the Sterling Multi-Channel Fulfillment Solution have been rectified for errors pertaining to localization:
Inventory
•	Inventory > Physical Count
•	Count Request > Count Result List > Net Variance Quantity
•	Create Physical Count Plan > Create Physical Plan 
Outbound
•	Wave Summary > Shipment Profiles
•	Wave Summary > Wave Audit
•	Outbound > Resource Planning > RR Capacity > Packing > Capacity > Resource Pool Details > Capacity Details > Shortage
•	Outbound > Outbound Shipment > Search
•	Wave Summary > Draft Quantity
VAS
•	VAS > VAS Station > Component Items
Mobile Application
•	RF > Receiving > PO > Serial Range Entry
•	RF Retrieval > Pick Serial Items > Pick Qty
Hot Fix ID	8.0-HF31
Defect ID	152884
Case ID	Internal
Description	The system should check whether a work order is cancelled or not before totaling the released quantity for the work order, so that the inventory allocated to the cancelled work order is released for use by other work orders.
Solution: The SUM (summation) query is changed to exclude the cancelled work orders when totaling the released quantity, thus freeing the inventory allocated to the cancelled work orders.
Defect ID	155468
Case ID	Internal
Description	When a user invokes the getNextTask API for an item level count task with more than 1000 organizations associated with a node, the system throws the following error message:
“<Error ErrorCode="ORA-1795" ErrorDescription="ORA-01795: maximum number of expressions in a list is 1000" ErrorRelatedMoreInfo="">”
Solution: The Oracle query has been modified as follows:
IN (  <1000 records>… ) OR <KEY> IN (  <1000 records>… ) OR <KEY> IN  (  <1000 records>… ) and so on.
Defect ID	156642
Case ID	Internal
Description	A new configuration should needs to be exposed for an enterprise in order to indicate whether the "CauseAppointmentChange" flag should be maintained by the system or externally. If it is to be maintained externally, the product should not set or reset this flag in any scenario. The "CauseAppointmentChange" flag should be exposed in the createWorkOrder API and the modifyWorkOrder API.
Note: If the "CauseAppointmentChange" flag is to be maintained externally by an enterprise, for example E1, set E1.CauseApptChangeMaintainedExternally=Y in the yfs.properties file.
Defect ID	156660
Case ID	Internal
Description	Under the following conditions, the SEND_INVOICE agent of return order incorrectly invokes the PUBLISH_INVOICE_DETAIL event configured for sales order:
1.	User has configured both the SEND_INVOICE agents of sales and return order to run from the same AgentServer.
2.	System has some invoices for both sales and return order, which are not yet processed by the SEND_INVOICE agent.
3.	Only SEND_INVOICE agent of return order is executed.
Defect ID	156662
Case ID	Internal
Description	Under the following conditions, the SEND_INVOICE agent of return order picks up both the sales order and the return order and the SEND_INVOICE agent of sales order picks up both the sales order and the return order:
1.	User has configured both the SEND_INVOICE agents of sales and return order to run from the same AgentServer.
2.	System has some invoices for both sales and return order, which are not yet processed by the SEND_INVOICE agent.
3.	Only SEND_INVOICE agent of return order is executed.
Defect ID	156693
Case ID	Internal
Description	When a user performs the following sequence of actions, the system displays the same output. (That is, the system displays the same 5 records that were picked up by the API when it was first invoked instead of the next 5 records):
1.	Creates, for example, 10 order lines.
2.	Invokes the getOrderLineList API with the “MaximumRecords” attribute set to, for example, 5.
3.	The user enters the value of the “LastOrderLineKey” of the Output XML of the API invoked in the previous step in the “OrderlineKey” attribute of the second Input XML
4.	Repeats step 2.
Solution: A new OrderByOrderLineKey flag has been introduced. If the value of this flag is set to “Y”, the retrieved records will be sorted according to the order line key.
Defect ID	161501
Case ID	47049
Description	When an order has a work order with an existing appointment, and the complete quantity on the order line is scheduled or released, and if a user invokes the getWorkOrderAppointmentOptions API, passes the ReqShipDate in the override element to reschedule an appointment to a date that is earlier than the current appointment date, the system does not return any available slots even if capacity is available for the queried slots.
Solution: A new, "Allow appointment date change to an earlier date after schedule" flag has been exposed in the Configurator under the VAS Rules. If this flag is selected, and the ReqShipDate is passed as a date that is earlier than the expectedShipDate, the slot availability is displayed according to the requested capacity.
Defect ID	161994
Case ID	47546
Description	When a user performs the following sequence of actions, the system throws a null pointer exception:
1.	Configures a shipment group to create item pick tasks having the task type configured to “Pick Into a Pallet” and “Complete Tasks in Multiple Steps”.
2.	Creates two shipments, with each shipment having one shipment line with 10 units, includes this shipment in a wave of the shipment group configured in step 1, and releases the wave.
3.	Completes the first step of the item pick task by picking inventory into a pallet, deposits the pallet at the staging location, and packs the shipments by scanning the pallet in the pack station. (The first shipment is packed successfully).
4.	Tries to pack the second shipment.
Defect ID	164015
Case ID	45947
Description	When a user enters an exception code to suggest an alternative pick location with or without short picking, the new task that is created is immediately assigned to the current user.
Solution: When a user enters an exception for suggesting an alternative pick location with or without short picking, the new task that is created will not be assigned to any user.
Defect ID	164018
Case ID	47200
Description	When a user enters an exception code to suggest an alternative pick location, the application updates the current task with the alternative location.
Solution: The application has been enhanced to cancel the current task when a user enters an exception code to suggest an alternative pick location, and create a new task with the alternative pick location as the source.
Defect ID	165178, 174898
Case ID	47585, 47585
Description	When a user creates a new country code from the Platform > Internationalization > Countries screen, creates a new locale, and then searches for the recently created country code, the application does not display the new county code in the search result.
Defect ID	167749
Case ID	Internal
Description	When a user performs the following sequence of actions, the system throws a "java.lang.UnsupportedOperationException" exception error message:
1.	Creates more than 75 location size codes and an equal number of locations.
2.	Navigates to Configurator > Warehouse Management System > Warehouse Layout > Location Search Console > Location Details, and tries to view the details of a location.
Defect ID	171973
Case ID	00004494
Description	The application must be enhanced to honor the JMSReplyTo property.
Solution: A new "Process Reply To Queue" check box has been added in the Runtime property tab of the JMS Receiver. Therefore, if a message has a queue as JMSReplyTo, the application will send the message to this queue after successful completion of the flow. The ReplyTo queue should have the same connection properties as that defined in the Runtime property tab.
A customer can define a default queue for the service by setting a queue name in the new "Default Reply To Queue Name" text box. Therefore, if a message does not contain the JMSReplyTo property, but the “Process Reply To Queue” check box is selected, the reply message will be sent to default queue.
Defect ID	174017
Case ID	00016404
Description	When the startHealthMonitor.sh script is run, it fails with an "USE_AGENT_JAVA=1: is not an identifier" error message.
Defect ID	174510
Case ID	00017121
Description	The dbverify tool does not generate ALTER scripts for the changes made in the datatype of a column in the Oracle database.
Defect ID	174589
Case ID	00017251
Description	When a user performs the following sequence of actions, the application throws a null pointer exception message:
1.	Enters both Case ID and Item ID in the moveRequest line.
2.	Creates two cases and adjusts two different items.
3.	Creates two move requests with the case IDs of the two cases that were created in step 2.
4.	Tries to execute the move task through the RF console.
Defect ID	175002
Case ID	00017443
Description	When sourcing rules are used, and all the ship nodes maintain supply externally for the order lines, the scheduleOrder API throws a null pointer exception when invoked.
Defect ID	175057
Case ID	00017298
Description	The payment method of a sales order does not have the same status as that of the payment method of a master order.
Defect ID	175304
Case ID	00018168
Description	When sourcing rules are used, and a few ship nodes maintain supply externally for the order lines, the scheduleOrder API throws a null pointer exception when invoked.
Defect ID	175555
Case ID	Internal
Description	The localization defects in the Sterling Multi-Channel Fulfillment Solution have been fixed.
Hot Fix ID	8.0-HF30
Defect ID	138507
Case ID	Internal
Description	The createWave API is slow when invoked on a DB2 database due to the following reasons:
•	Degradation of a query that fetches the shipments and shipment lines
•	Extra, expensive validations done during a wave creation for shipments 
Note: These validations are required for those shipments that are eligible for wave creation but have not yet been included in wave. However, for those shipments that are currently being processed for wave creation, these validations are not required. Therefore, they have been removed.
Defect ID	155214
Case ID	Internal
Description	When a user performs the sequence of actions described here, the system does not resolve the error. However, selecting the “Today” button in the Calendar pop-up window resolves the error:
•	Logs in to the Sterling Store Inventory Management PCA client.
•	Navigates to Inventory > View Inventory Audit. (The system displays the “Find Audit Information” screen with today’s date as the default date in the “From Date” field.)
•	Enters a valid date except for the last character of the year, for example, an alphabet as the last character of a year - 02/14/200a. (The system throws a “You must specify a valid date” error message in the user message panel with the theme of the data highlighted in red.)
•	Clicks the Calendar icon and selects a date. (The system alters the value in the “From Date” field to 02/14/0200. However, the system still displays the error message and theme of the data highlighted in red.)
Defect ID	156674
Case ID	Internal
Description	When a user completes packing a SKU, the system moves the cursor to the “UOM” field instead of displaying the cursor in the “SKU” field for the next successive scan.
Defect ID	157255
Case ID	Internal
Description	When a user completes packing an SKU, the system automatically moves the cursor to the “UOM” field instead of to the “SKU” field for the next successive scan.
Defect ID	164984
Case ID	Internal
Description	In Conditional Monitoring Rules, if a condition is returned such that an alert is not raised, the NextAlertTs must be set to HIGH_DATE. Also, if a milestone has already been met, the NextAlertTs must be set to HIGH_DATE for the “Milestone Not Reached Within Comparison Milestone” condition.
Solution: In Conditional Monitoring Rules, if a condition is returned such that an alert is not raised, and if the “yfs.monitor.stopprocessing.ifcondition.eval.false” property is set to True in the yfs.properties file, the NextAlertTs will be set to HIGH_DATE.
Defect ID	165190
Case ID	47493
Description	When an item is configured to have substitutes, and item substitution is allowed at the node level, and if a user invokes the findInventory API for the item with the quantity greater than that currently available onhand, such that the substitutes are used, the findInventory API provides inconsistent results and does not honor the substitution priority.
Defect ID	166773
Case ID	00003439
Description	When more than 500 ChargeNames exist for a ChargeType for DocumentType=0005, and if a user creates an order and invokes the changeOrder API to add header charges to the 501st ChargeName, the application displays an "YFS10346: YFS:Invalid Charge Category and Charge Name Combination" error message.
Defect ID	169348
Case ID	Internal
Description	When a user performs the following sequence of actions, the application does not propagate the “BillToID” attribute and the “CustomerPONo” attribute to the Shipment Advice:
1.	Create a sales order by passing the “BillToID” attribute and the “CustomerPONo” attribute.
2.	Schedules and releases the sales order.
3.	Runs the “Send Release” transaction (Transaction ID SHIP_ADVICE) to generate the Shipment Advice.
Solution: The “CustomerPONo” attribute in the Shipment Advice will be populated from the order release. If the “CustomerPONo” attribute in the order release is blank, this attribute will be populated from the order line. If the order release has multiple order lines and each order line has different “CustomerPONo” values, then the “CustomerPONo” attribute will be set to blank in the Shipment Advice. If the “CustomerPONo” attribute in all the order lines are blank, the “CustomerPONo” attribute will be populated from the order header.
Defect ID	170065
Case ID	00004866
Description	When a user performs the following sequence of actions, the details of the tax breakup are not inserted into the YFS_TAX_BREAKUP table:
1.	Implements the “OMPGetInvioceNoUE” user exit.
2.	Creates a sales order for an item and authorizes the sales order.
3.	Invokes the recordInvoiceCreation API with the tax breakup information in the input XML of this API.
Defect ID	171805
Case ID	00009323
Description	The application must have an option to enable a user to override the item dimensions that are used in the system-defined containerization, and in the computation of the weight of the container, or shipment, or both.
Solution: A new “YDMGetOverridenAttributesForShipmentLineItemUE” user exit has been provided, which will be invoked for each distinct SKU that is being containerized as part of the containerizeWave API or the postPickContainerization API. For more information about this user exit, refer to the corresponding section in the Sterling JavaDocs.
Defect ID	172379
Case ID	00012885
Description	When yantradocs.ear is deployed, the Sterling Online Help works only in the “en_US” locale and not in the other locales. The application must be enhanced to provide the user with the capability to change the default language-country code.
Solution: A new “yfs.onlinehelp.path.overrideforlocale.<USER-LOCALE-CODE>” property has been provided. This property will override the “yfs.online.helppath” property in the yfs.properties file. If the “yfs.onlinehelp.path.overrideforlocale.<USER-LOCALE-CODE)” property is undefined, the application will consider the value of the “yfs.online.helppath” property and append it with “en_US”, which is the default language-country code.
Defect ID	172974
Case ID	00014810
Description	When a user performs the following sequence of actions, the application generates an incorrect inventory picture:
1.	Configures a zone with inventory status as “QC” and the supply type as “Held”.
2.	Overrides the deposit location through an “Adhoc Move” operation from the RF.
3.	Overrides the deposit location suggested by the application to the location configured in step 1.
Defect ID	172982
Case ID	00014667
Description	When multiple e-mail addresses have been provided, the application does not send an e-mail if any of these e-mail addresses is invalid.
Defect ID	173149
Case ID	00015130
Description	When a user performs the following sequence of actions, the application does not consider the requested segment or segment type:
1.	Configures the “Batch Pick”, “Pick into Inventory Pallet”, and the “Pack While Pick” task types.
2.	Invokes the registerBatchCompletion API.
3.	Navigates to Task > Confirm Batch, and completes the batching tasks.
Defect ID	173450
Case ID	00014219
Description	When the Configuration Data Versioning Tool (CDVT) is run, and if any change is performed in the resource permissions of a user group in the source database, the CDVT displays an “RECORD_ALREADY_EXISTS” error message.
Defect ID	173475
Case ID	00015621
Description	The Configuration Deployment Tool considers the lock ID of the deleted record and therefore displays an invocationTargetException error.
Defect ID	173625
Case ID	00015662
Description	When a user creates a return order, specifies the ship node at the order header level, and invokes the changeOrder API to change the ship node at the order header level, the application displays a "YFS: Setup for order modification permissions missing" exception error message.
Hot Fix ID	8.0-HF29
Defect ID	147035
Case ID	Internal
Description	The Shipment Container Marking (SCM) is not completely displayed in the “Inventory Inquiry Container List” screen. In addition, only two of the containers are visible at a time in the container list.
Solution: In the “Inventory Inquiry Container List” screen, the font size is decreased to accommodate all the 20 characters of the container SCM. Also, the height of the screen is increased to display more containers at a time.
Defect ID	155102
Case ID	Internal
Description	When a user tries to cancel a return order that is derived from sales order and the return order has a work order with appointment, the system throws a “Not enough Quantity” exception.
Defect ID	156621
Case ID	Internal
Description	When the Sterling Multi-Channel Fulfillment Solution is run on a DB2 database and the shipments are created concurrently, the system encounters a deadlock when firing a query on the YFS_Person_Info table.
Defect ID	160509
Case ID	Internal
Description	When a record is inserted into the YFS_LOCATION_INVENTORY table in a DB2 database using the adjustLocationInventory API, and if a user invokes the changeLocationInventoryAttributes API for this record before the record is committed, the changeLocationInventoryAttributes API enters into an infinite loop, and the application server crashes.
Solution: The changeLocationInventoryAttributes API has been enhanced to throw an “Unknown Error” message in the scenario described here.
Defect ID	160532
Case ID	Internal
Description	When a user performs the following sequence of actions, the system does not display the Synchronous/Non-Real-Time services under the “Look Up” criteria in the Execution Exception screen:
•	Creates three synchronous services, Synchronous/Real-Time, Asynchronous/Non-Real-Time, and Synchronous/Non-Real-Time.
•	Navigates to Execution Exception and tries to associate all the services.
Solution: The Search Element for the form has been modified to display only the Synchronous/Real-time and Synchronous/Non-Real-Time services.
Defect ID	164012
Case ID	Internal
Description	The Sterling Warehouse Management System User Guide should provide information about the Wave Audit feature. In addition, information about all the wave audits being purged when the wave is purged should be added to the Sterling Warehouse Management System Configuration Guide.
Solution: The documents have been updated with the requisite changes as described below:
•	Added a new Section 30.15, "Wave Audit" to Chapter 30, "Wave Console Screens" in the Sterling Warehouse Management System User Guide.
•	Added the following new note in section A.3.3.11, "Wave Purge" in Appendix A ,"Time-Triggered Transaction Reference" in the Sterling Warehouse Management System Configuration Guide:
Note: When a wave is purged, all the audits related to the wave are also purged.
Defect ID	167096
Case ID	Internal
Description	When a user creates a large number of orders and invokes the getOrderList API, the application throws a timeout error in the “Purchase Order Search” screen.
Solution: The application will not display a timeout error.
Note: This fix is specific to Oracle database. In addition, this attribute is specific to a customer. Hence, this attribute is not present in the input XML of the getOrderList API. As part of this fix, a new “OracleHint” attribute is exposed in the root element of the input XML of the getOrderList API. This attribute can be used to pass the Hint to Oracle when querying in the YFS_Order_Header table.
For example, if you use the Hint: parallel(YFS_ORDER_HEADER 8) full(YFS_ORDER_HEADER), the input to the getOrderList API is:
<Order DocumentType="0001" EnterpriseCode="DEFAULT" ShipNode="N1" OracleHint ="/*+ parallel(YFS_ORDER_HEADER 8) full(YFS_ORDER_HEADER) */"   />
Defect ID	168214
Case ID	Internal
Description	When you select the “Write to Log File” check box for the SUPPLYTEMPPRG purge agent, and run the agent to purge records, the log file that is created contains no data.`
Defect ID	168664
Case ID	00008243
Description	When a user packs a shipment or closes a container, the pre-existing ITN number at the shipment header level is not used as default in the “ITN Entry” pop-up window.
Defect ID	171788
Case ID	Internal
Description	When a sales order has two order lines with charges and taxes defined in these order lines, and if the splitLine API is invoked to split the first line, the taxes in the first line are set to zero.
Solution: The application has been enhanced to calculate the tax according to the tax percentage defined for the order line.
Defect ID	172161
Case ID	Internal
Description	The application does not display the IP address of the client in the “Audit” screen when performing the order and shipment audits.
Solution: The IP address of the client will be captured and displayed in the audit screens for orders and shipments for the HTTP requests that are routed either through the console screens or through the RCP clients. For the order audit, the IP address of the client will be displayed in the “Order Audit Detail” screen, and for the shipment audit, the IP address of the client will be displayed in the “Shipment Audit” screen.
The new configuration options listed below have been introduced in the yfs.properties file:
9.	A user can use the “yfs.clientip.reader” property to set a custom implementation java class to read the IP address of the client from the HTTP request object. A default out-of-the-box “‘com.yantra.yfs.util.YFSClientIPReaderImpl” implementation has been provided. To write your own implementation class, implement the “com.yantra.yfs.japi.util.YFSClientIPReader” interface. For more information about this interface, see the Sterling JavaDocs.
10.	When using the default out-of-the-box implementation, the following properties can be used to read the IP address of the client from the HTTP request:
f.	yfs.clientip.httprequest.ipHeaderAttribute - This property can be used to set the request header name that stores the IP address of the client. If the value of the configured header is present in the request, this value will be used as the IP address of the client.
g.	yfs.clientip.httprequest.useForwardedFor – This property will be used if the “yfs.clientip.httprequest.ipHeaderAttribute” property is not configured, or the value is not present in the request. The default value of this property is “N”. If set to “Y”, the value of the request header “X-Forwarded-For” is read to obtain the IP address of the client.
If the “yfs.clientip.httprequest.ipHeaderAttribute” property and the “yfs.clientip.httprequest.useForwardedFor” property do not yield a value for the IP address of the client, the “remote attr” property that is available in the HTTP request object is used to obtain the IP address of the client.
Defect ID	172164
Case ID	Internal
Description	When a user accesses the application, the IP address of the user is not recorded in the log files.
Solution: The IP address of the user is recorded in a separate configurable log file in addition to the existing application log file. A separate logger configuration is provided in the “log4jconfig.xml.in” file.
11.	A new “LOGIN_CLIENT_IP_DETAILS” appender tag is introduced in the “log4jconfig.xml.in” file. The log file can be configured to record the IP address of the user.
12.	A new “com.yantra.yfs.ui.backend.YFSLoginIPLogger” category tag is introduced. This category tag uses the appender tag that is mentioned above.
The “LOGIN_CLIENT_IP_DETAILS” appender tag and “com.yantra.yfs.ui.backend.YFSLoginIPLogger” category tag will be created in the “log4jconfig.xml” file, which is included in the resources.jar file.
Defect ID	172376
Case ID	Internal
Description	In a multi-JVM scenario, when updates occur, the cache is cleared simultaneously. This may sometimes result in a deadlock.
Defect ID	172578
Case ID	00014135
Description	When a user performs the following sequence of actions, the executePaymentTransactions API throws an “OMP80_0052” error message:
11.	Implements the YFSCollectionCreditCardUE user exit such that the user exit returns the “AuthTime” attribute in the “YYYYMMDDTHH:MM:SS” format.
12.	Ensures that a sales order exists with a price, charge, tax, and a payment method.
13.	Invokes the executePaymentTransactions API.
Defect ID	172983
Case ID	00010798
Description	The application should provide a way to correlate the exception message displayed on the screen, with the exception message printed in the log trace. In case of multi-user scenarios, non-availability of this feature results in confusion during administrator and user co-ordinations.
Solution: The application has been enhanced to associate a unique numeric identifier with each exception message. The error description of the exception will be suffixed with a unique numeric ID.
Defect ID	173054
Case ID	00013461
Description	The application must be enhanced to raise the CNF_LOCN_EMT_AFTER_PICK event of the PICK_AND_RETRIEVAL transaction if both the application and a user confirm that the pick location is empty.
Solution: The input to the CNF_LOCN_EMT_AFTER_PICK event will include a new “LocationConfirmedEmpty” Boolean parameter to indicate the response of the user. This parameter will be set to "Y" if the user confirms that the pick location is empty, and "N" if the pick location is confirmed as not being empty.
Defect ID	173373
Case ID	Internal
Description	The localization defects in the Sterling Multi-Channel Fulfillment Solution have been fixed.
Hot Fix ID	8.0-HF28
Defect ID	150705
Case ID	Internal
Description	When multiple users invoke the removeShipmentFromWave API at the same time on a DB2 database, a deadlock or timeout may occur on the YFS_SHIPMENT table.
Defect ID	155497
Case ID	Internal
Description	When a count request is completed for a location that has the “freeze for variance” condition enabled, the system does not remove/unfreeze the location.
Defect ID	159825
Case ID	46725
Description	When picking through the Sterling Mobile Application, the system mandates a user to scan the LPN each time the user picks inventory from the LPN to complete a task.
Defect ID	160434
Case ID	45859
Description	The Yantra Mobile Application UI error messages needs to be enhanced to include the serial numbers in the error messages that are displayed when executing the outbound pick tasks.
Defect ID	160444
Case ID	Internal
Description	The UI and the unreceiveOrder API need to be enhanced to enable a user to unreceive an LPN or item even if the receipt is closed. Also, if the inventory is received against a purchase order, the purchase order status should be changed to the previous status.
Defect ID	161469
Case ID	47269
Description	When releasing a count request for a particular classification, the application does not consider the classification attributes defined for an item, which are overridden at a node.
Defect ID	164004
Case ID	45962
Description	When a user accesses the queue through the JMS component in the Sterling Service Definition Framework (SDF), the system throws a security exception when the Queue is secured at the Application Server level.
Solution: The following two properties have been exposed in the yfs.properties file to address this issue. The properties should match the username and password set up for the queue:
13.	sci.queuebasedsecurity.userid=<USER_ID>
14.	sci.queuebasedsecurity.password= <PASSWORD>
Defect ID	166612
Case ID	00003645
Description	The Sterling Synchronous-JMS Transport should be enhanced to set the “replyToQ” attribute in the request JMS message as the configured response queue.
Defect ID	166775
Case ID	47278
Description	The Sterling Warehouse Management System Configuration Guide should be updated with information about the new "Create Count Requests for Location Range" time-triggered transaction.
Solution: A new section A.2.8, "Create Count Requests for Location Range" has been added to Appendix A, "Time-Triggered Transaction Reference" of the Sterling Warehouse Management System Configuration Guide.
Defect ID	167792
Case ID	Internal
Description	When picking from an LPN through the Sterling Mobile Application to complete a task, the system mandates that the user scan the LPN by scanning a 2D barcode each time the user picks inventory with quantity less than the task quantity.
Defect ID	168521
Case ID	Internal
Description	The application must be enhanced with the capability to pass user credentials to the secure servlets.
Solution: The following properties in the /resources/yifclient.properties directory have to be overridden with the correct values:
15.	#yif.httpapi.userid=<user ID for BASIC authentication>
16.	#yif.httpapi.password=<password for BASIC authentication>
If setting these properties in the properties file creates a security risk, these properties can also be formed in the calling code.
Note: Use of this feature will require an implementation for Base64Xerces as a pre-requisite. The implemented class must be specified as “base64_xerces_class” property in the noapp.properties file.
Defect ID	171231
Case ID	Internal
Description	The Sterling Multi-Channel Fulfillment Solution Localization Guide must be updated with information about using the Dbasefilename parameter in the LocalizedStringReconciler tool for the factory setup.
Solution: Information about using the Dbasefilename parameter in the LocalizedStringReconciler tool for the factory setup has been added at the end of Section 2.4.1, "Localization for a Multi-Language Installation" in Chapter 2, "Localizing the Sterling Multi-Channel Fulfillment Solution" of the Sterling Multi-Channel Fulfillment Solution Localization Guide.
Defect ID	171511
Case ID	00011877
Description	When a user performs the sequence of actions described here, the application does not allow the user to delete the item:
14.	Ensures that an item with the same name and two different UOMs exists. (One of the UOM is a valid UOM and the other is an invalid UOM, that is, it is not present in the YFS_ITEM_UOM_MASTER table.)
15.	Adjusts the inventory for the item with the valid UOM.
16.	Navigates to the Configurator and tries to delete the item with the invalid UOM. 
Solution: The application has been enhanced such that the user cannot create an item with an invalid UOM.
Defect ID	171609
Case ID	Internal
Description	The system does not generate the correct sequence numbers for sequences that are implemented as tables for the SQL Server and the MySQL databases.
Defect ID	171818
Case ID	00012975
Description	When a user performs the following sequence of actions, the audits for the order line in the “Order Audit” screen do not contain the modification level and the modification type of the status change:
•	Creates a custom status, for example, 1100.100, that is extended from the “Order Created” status.
•	Ensures that a sales order exists in “Created” status.
•	Invokes the changeOrderStatus API to move the status of the order line to 1100.100 
Defect ID	171870
Case ID	Internal
Description	The YCPMassageApiOutputUE user exit, if implemented, provides a handle to modify the output of any API before the output is returned. A disclaimer stating that this user exit should not be used to remove any existing attributes in the API output must be added to the Sterling JavaDocs.
Solution: The following note has been added in Sterling JavaDocs for the massageApiOutputBeforeReturning method in the YCPMassageApiOutputUE user exit:
Note: The method should be used strictly for validation purposes and capturing extra data only. One should not remove any of the elements or attributes in the output xml.
Defect ID	172028
Case ID	00005131
Description	A new type of order called master order should be exposed in the application. The master order enables users to specify a series of orders, and time intervals at which these orders will be shipped and charged to customers. 
The master order is typically created for a customer to purchase a series of products for shipping. For example, a customer can place an order for a product that is to be supplied for a period of six months. The product will be shipped to the customer each month, and the customer will be authorized and billed each month.
Solution: An out-of-the-box solution has been provided with this hot fix.
Defect ID	172611
Case ID	00005131
Description	The Master Order and Continuity Engine functionality must be documented in the following documents:
17.	Sterling Multi-Channel Fulfillment Solution Platform Configuration Guide
18.	Sterling Multi-Channel Fulfillment Solution Glossary
19.	Sterling Multi-Channel Fulfillment Solution Product Concepts
20.	Sterling Distributed Order Management Configuration Guide
Solution: The details of the documentation updates are as follows:
21.	In the Sterling Multi-Channel Fulfillment Solution Platform Configuration Guide:
1.	Added Master Order as an example for document types and updated Figure 2-13, "Associated Document Types Window", to include the Master Order (corrected the Master Order number to 0007 from 0011) in Section 2.3.2, "Viewing the Document Types Associated with an Application", in Chapter 2, "Navigating in the Configurator".
2.	Added Master Order Fulfillment to the list of process types in Section 4.1, "Document Type Configuration", in Chapter 4, "Configuring Process Models".
3.	Added the Completed (3700) status as available for configuration for the Master Order in Section A.3.3.16, "Order Purge", in Appendix A, "Time-Triggered Transaction Reference".
4.	Added Actual Next Iteration Date as a system date type that can be monitored by the order monitor in Section A.5.6, "Enhanced Order Monitor", Appendix A, "Time-Triggered Transaction Reference".
5.	Corrected the Master Order number to 0007 from 0011 and added the document type, document number, and description for the Master Order in Table E-1, "Document Types", in Appendix E, "Document Types".
6.	Added the Master Order Fulfillment condition builder attribute to the list of condition builder attributes, and added a new Section F.7, "Master Order" in Appendix F, "Condition Builder Attributes".
22.	In the Sterling Multi-Channel Fulfillment Solution Glossary:
7.	Added the term Master Order under "M", in Chapter, "J - M".
23.	In the Sterling Multi-Channel Fulfillment Solution Product Concepts:
8.	Added Master Order to the list of document types in Section 4.1, "Base Document Types and Document Types", in Chapter 4, "Process Modelling Concepts".
9.	Added details of Master Order Fulfillment to the process type pipelines and derived process types in Table 4-1, "Order Fulfillment Base Process Types", in Section 4.2, "Process Type Pipelines", in Chapter 4, "Process Modelling Concepts".
10.	Added Master Order to the list of process-type pipelines and added a new Section 7.3.4, "Master Order Pipeline" in Section 7.3, "Order Pipelines", in Chapter 7, "Order Management'.
24.	In the Sterling Distributed Order Management Configuration Guide:
11.	Added Master Order as an example for document types and updated Figure 2-13, "Associated Document Types Window" to include Master Order in Section 2.3.2, "Viewing the Document Types Associated with an Application", in Chapter 2, "Navigating in the Configurator".
12.	Added Next Iteration Date to the list of system dates that cannot be deleted, in Section 17.7.1.3, "Deleting a Date Type", in Chapter 17, "Configuring an Order Document's Fulfillment Specific Components".
13.	Added the Completed (3700) status as available for configuration for the Master Order in Section A.3.3.16, "Order Purge", in Appendix A, "Time-Triggered Transaction Reference".
14.	Added Actual Next Iteration Date as a system date type that can be monitored by the order monitor in Section A.6.6, "Enhanced Order Monitor", Appendix A, "Time-Triggered Transaction Reference".
15.	Added description and modification levels to the Change Iteration modification types in Table B-1, "Order Documentation Modification Types", in Appendix B, "Order Modification Types".
16.	Added the Master Order Fulfillment condition builder attribute to the list of condition builder attributes, and added a new section, Section C.7, "Master Order" in Appendix C, "Condition Builder Attributes".
Hot Fix ID	8.0-HF27
Defect ID	141915
Case ID	Internal
Description	The system hangs and throws an “Out of memory” exception when a user cancels a wave that has more than 20,000 shipments using the Sterling Supply Chain Applications Console.
Solution: The wave cancellation process is enhanced to run in offline mode when the wave is not released yet and has more shipments. A new “yfs.cancelwave.offline.shipmentcount.greaterthan” property has been provided in the “yfs.properties” file. When a user cancels a wave that has more shipments than the value configured in this properties file, the wave cancellation process will run in the offline mode. The cancel wave agent picks this wave, removes all of the shipments from the wave, and cancels the wave.
For more information about this property, see Section A.2.20, “Cancel Wave”, in the Sterling Warehouse Management System Configuration Guide.
Defect ID	154077
Case ID	Internal
Description	When the getNodeInventory API is invoked under the following conditions, the API consumes a large amount of temporary database space and returns incorrect records:
1.	Create an item classification and associate more than 1000 items with the classification.
2.	Adjust inventory for few of these items at the location.
3.	Invoke the getNodeInventory API for the classification that was created in step 1.
Defect ID	156668
Case ID	Internal
Description	When a user configures the inventory cost calculation and invokes the adjustInventory API, the inventory organization is not published for the ADJUST_INVENTORY.INVENTORY_VALUE_CHANGE event.
Solution: A new “OrganizationCode” attribute has been added to the XML file that is published by the ADJUST_INVENTORY.INVENTORY_VALUE_CHANGE event for the inventory organization.
Defect ID	156690
Case ID	Internal
Description	When the invoice of a shipment is voided and the shipment is unconfirmed and cancelled, and a user tries to view the collection summary, the getOrderDetails API throws a “Null Pointer” exception.
Note: The “Null Pointer” exception will be thrown for the older orders, that is, the orders that were created before this fix was applied, when the getOrderDetails API is invoked.
Defect ID	157270
Case ID	Internal
Description	When the “GenerateWorkOrderUE” user exit is implemented and the generateWorkOrder API is invoked for a product line that has a provided service associated with it, and this product line is consolidated with an existing work order that has another product line and a delivery service, an association between the delivery service and the newly added product line is not created.
Defect ID	157360
Case ID	Internal
Description	When the voidInvoice API and the unconfirmShipment API are invoked in the multiAPI mode, the system throws an “YDM77_00001: Cannot unconfirm the shipment” error message.
Defect ID	160706
Case ID	45782
Description	When a user performs the following sequence of actions, the system throws an “Invalid Line” error message:
1.	Implements the “generateWorkOrderUE” user exit to return output=input.
2.	Invokes the generateWorkOrder API for a sales order. (The sales order has a work order in “Completed” status. A product line that requires delivery exists on the sales order.)
Solution: When the “generateWorkOrderUE” user exit is implemented, the output of this user exit has a "CreatedOrModified" flag for each of the work order elements. All the work orders that have this flag set to "N" will not be processed after this enhancement. The output of the generateWorkOrder API will display all the work orders on the order.
Defect ID	164780
Case ID	00003475
Description	The input struct of the “RecalculateHeaderTaxUE” user exit contains only the header level address even if the “Ship To” address in the shipment invoice is different from the “Ship To” address in the order header.
Solution: The input struct of the “RecalculateHeaderTaxUE” user exit will have a template-controlled “eMemo” parameter. The RecalculateHeaderTaxUE template is located in the “<INSTALL_DIR>/repository/xapi/template/merged/api/extn” directory. This template can be used to extract all the required information about a shipment invoice from this parameter. If this file is not found, there will be no change in the behavior of the application.
For more information about extending templates, see Section 8.2.10, “Extending an Output XML Template” in the Sterling Multi-Channel Fulfillment Solution Customization Guide.
Defect ID	166222
Case ID	00004996
Description	The “mail.jar” and “activation.jar” third-party files that are shipped with the product as part of the EMAIL component of the Service Definition Framework are not registered in the classpath in the “AGENTDynamicClasspath.cfg”, “APPDynamicClasspath.cfg”, and “dynamicClasspath.cfg” files.
Solution: When installing the hot fix, the “mail.jar” and “activation.jar” third-party files will be registered in the “AGENTDynamicClasspath.cfg”, “APPDynamicClasspath.cfg”, and “dynamicClasspath.cfg” files.
Defect ID	168086
Case ID	Internal
Description	The “ant_InstallPCAs.xml” file contains entries to migrate the Sterling Store Inventory Management PCA 7.1 from Sterling Supply Chain Application 7.11 to Sterling Multi-Channel Fulfillment Solution 8.0.
Solution: The “SOP” entries have been removed from the “ant_InstallPCAs.xml” file so that Sterling Store Inventory Management PCA 7.1 will not be migrated to Sterling Multi-Channel Fulfillment Solution 8.0.
Defect ID	168341
Case ID	00005071
Description	A handle should be provided to the output of an API such that the output can be modified before it is returned.
Solution: A “YCPMassageApiOutputUE” user exit has been introduced. If this user exit is implemented, all the API calls will pass through this user exit before returning the output. Based on the name of the API, a user can selectively modify the output for the required APIs. For more information about this user exit, see the Sterling JavaDocs.
Defect ID	168796
Case ID	00003964
Description	When a user invokes the changeOrder API and modifies the value of the “TaxExemptFlag” in the header level of a sales order, the “RecalculateHeaderTaxUE” user exit and the “RecalculateLineTaxUE” user exit are not invoked.
Defect ID	169481
Case ID	00006792
Description	When a user tries to paginate a custom service with the “setPaginationRequired” flag set to “true”, the application displays a “Could not find service getPage” error message.
Solution: The pagination of the custom service occurs without any invalid service error messages. The out-of-the-box "getPage" is of type "API".
Note: A workaround to add or configure the "getPage" service to invoke a "getPage" API was suggested when this defect was raised. This workaround is no longer required. Any additional changes made with regard to this workaround should be removed after incorporating this hot fix.
Defect ID	170038
Case ID	Internal
Description	The performance of the scheduleOrder agent is slow when this agent is configured and run.
Solution: The scheduleOrder agent has been enhanced to use Oracle Hints that are specified in the “yfs.properties” file. These Oracle Hints will be used in the SQL queries fired by the scheduleOrder agent. The user should provide the correct Oracle Hints to optimize the performance of this agent.
For more information about Oracle Hints, see Section A.2.29, “Schedule” of Appendix A, “Time-Triggered Transaction Reference” in the Sterling Distributed Order Management Configuration Guide.
Defect ID	170307
Case ID	00010840
Description	The executePaymentTransactions API should be enhanced to pass the “orderNo” attribute and the “orderHeaderKey” attribute to the required collection user exits, for example, “YFSCollectionCreditCardUE” user exit.
Defect ID	170771
Case ID	00011332
Description	When the “Apply price change for invoiced quantity” rule is enabled and a sales order is invoiced, the application does not update the tax amount in the order or order line, and the adjustment invoice is not created.
Solution: When the “Apply price change for invoiced quantity” rule is enabled for the “Sales Order” document type, and if there is a change in the tax amount in a sales order, the adjustment invoice will be created based on whether the order is fully invoiced or partially invoiced.
Note: If the tax amount is used and if the tax percentage is either zero or does not correspond to the tax amount, the application will recalculate the tax amount based on the percentage when creating the invoice. To override this behavior, the “recalculateHeaderTaxUE” user exit and the “recalculateLineTaxUE” user exit must be implemented. The tax information returned by these user exits will be the delta taxes, that is, the difference between the current tax and the invoiced tax.
Defect ID	170824
Case ID	00007260
Description	When a user performs the following sequence of actions, the application does not invoke the “RecalculateHeaderTaxUE” user exit to recalculate the new taxes that are based on the new charges even if the header charges are changed by the output of the “RepricingUE” user exit:
1.	Implements the “RecalculateHeaderTax” user exit and the “RepricingUE” user exit.
2.	Creates an order.
3.	Invokes the changeOrder API to add a new line to the order that was created in step 2.
Defect ID	171005
Case ID	00011664
Description	When a user cancels a move request or task, the application does not remove the lines that have zero quantity from the “Inventory Details” screen.
Defect ID	171176
Case ID	00011326
Description	The application throws a null pointer exception when a synchronous service with an API component has a template that contains an XML root element as the node in the Service Definition Framework.
Defect ID	171707
Case ID	Internal
Description	The Sterling Distributed Order Management Configuration Guide should be updated with information about providing Oracle Hints to increase the performance of the scheduleOrder agent.
Solution: A new sub-section "Providing Oracle Hints" has been added to Section A.2.29, "Schedule" of Appendix A, "Time-Triggered Transaction Reference" in the Sterling Distributed Order Management Configuration Guide.
Hot Fix ID	8.0-HF26
Defect ID	166485
Case ID	00004936
Description	The application should be enhanced with the functionality to postpone a payment to a future date when Payment is enabled.
Solution: The application has been enhanced with the requisite functionality. The main changes in the Sterling JavaDocs and the Yantra Console user interface are as follows:
1.	The “PaymentDetails” element in the “PaymentMethod” element has been deprecated from the createOrder API, changeOrder API, and the recordExternalCharges API. The “PaymentDetailsList” element has been provided such that multiple payment details can be passed for a single payment method.
2.	A new “CollectionDate” field has been provided in the input XML file of the createOrder API, changeOrder API, and the recordExternalCharges API. For further details, see the Sterling JavaDocs.
3.	The “CollectionDate” has been exposed in the Yantra Console for the “Charge” pop-up window and the “Authorize” pop-up window. The “Amount” field has been renamed as “Processed Amount”. The “Requested Amount” field has been exposed such that the user can enter the amount to be charged or authorized on a future date.
4.	The executeCollection API will not process the charge or authorization values until the collection date has been attained. The user should always pass the amount that is to be charged or authorized in the future in the “Requested Amount” field.
Defect ID	168060
Case ID	Internal
Description	When a user defines 240 locales in the Configurator and ensures that two bundle.properties files exist in the Resources folder for different “language + country code” combinations, the BEA WebLogic server crashes with an “Out of Memory” exception message because of the presence of a very large number of objects in the com.yantra.yfc.util.YFCI18NUtils component.
Solution: Earlier, the “ycpbundle.properties” file was loaded by the application for each locale without considering the language and the country of the locales, resulting in the same message being duplicated.
A new “yfs.bundleProperties.multipleLoad” property that is set to “Y” has been added to the “yfs.properties” file. The system now checks whether a “bundle.properties” file, for example, /resources/ycpbundle_jp_JP.properties for a locale with language as “jp” and country as “JP”, exists for the “Locale_jp_JP” locale. If the “bundle.properties” file is not present, the messages are not loaded for that locale and the “cpbundle_en_US.properties” file is used to display the literals for that locale.
Defect ID	169013
Case ID	00008455
Description	When a user configures a BundleParent item, invokes the importOrder API, and passes the BundleParent item, the application throws an "Invalid Kit Code" error message.
Defect ID	169909
Case ID	Internal
Description	The supported version of the BEA WebLogic Application server is incorrectly mentioned as 10.x in the Sterling Multi-Channel Fulfillment Solution Installation Guide.
Solution: The correct version of the BEA WebLogic Application Server has been included in Table 2-2, "Supported Application Server Tier" in Chapter 2, "System Requirements" of the Sterling Multi-Channel Fulfillment Solution Installation Guide.
Defect ID	170013
Case ID	Internal
Description	When a user enables inventory costing, creates a price program, and invokes the getItemListForOrdering API with the complete output template, the API occasionally throws a “NumberFormatException” error message for the service items.
Defect ID	170133
Case ID	00010430
Description	When a user invokes the scheduleOrder API to schedule an order that contains distinct segment for distinct items, only one order line is scheduled; the remaining order lines are backordered even if enough inventory is available to meet the demand.
Defect ID	170135
Case ID	00010431
Description	When a user invokes the releaseOrder API to release an order that contains distinct segment for distinct items, only one order line is released; the remaining order lines are backordered even if enough inventory is available to satisfy the demand.
Defect ID	170528
Case ID	00011042
Description	When a user performs the following sequence of actions, the getShipmentLineList API locks the YFS_ORDER_HEADER table:
4.	Creates an order.
5.	Creates a shipment for the order.
6.	Invokes the getShipmetLineList API.
Hot Fix ID	8.0-HF25
Defect ID	142320
Case ID	Internal
Description	When a user invokes the getPutawayLocations API multiple times in a single transaction, allocations done by the previous API calls are not considered by the subsequent API call. 
Solution: If the ClearInventoryCache attribute is passed as “N” in the API input, all of the previous allocations are cached and used by the subsequent API calls.
Defect ID	151128
Case ID	Internal
Description	When complete inventory is reduced from a Case/Pallet, the Case/Pallet should be deleted.
Defect ID	154497
Case ID	Internal
Description	When a user performs the following sequence of actions, the system throws a "WMS0080_307 Target LPN must be passed" error message:
1.	Configures the Pick Location Assignment (PLA) to perform a batch pick.
2.	Configures the Pick Exception with "Suggest Alternate Location" and "Freeze for Picking" enabled.
3.	Creates a shipment, includes it in a wave, releases the wave, and creates a batch for the wave.
4.	Inducts the batch in a cart and performs a short pick without entering any quantity and by providing the pick exception code.
Defect ID	156676
Case ID	Internal
Description	When a user picks partial quantities of tag-controlled items from a case or pallet directly on to an equipment for a consolidated pick task, and tries to deposit the items at the pack station suggested by the system, the system throws the following error message:
"WMS00227: Inventory for the SKU does not exist in the location or Case/Pallet to perform the inventory operation."
Defect ID	157272
Case ID	Internal
Description	When the system is configured as follows, and a user picks inventory for a task without scanning an equipment, and by scanning the same LPN multiple times during pick, the system throws a "License plate cannot be allocated as it has already an allocation against it.” error message:
5.	Configures the "Pick Into Equipment" task type.
6.	An “In progress” task exists for the source LPN being scanned.
Defect ID	159847
Case ID	45191
Description	The Sterling Warehouse Management System Inventory APIs have been enhanced to log the audits for the creation and consumption of the inventory with source inventory status, whenever the source inventory status is different from the target inventory status in the Inventory Transition Rules.
Defect ID	160515
Case ID	47312
Description	When the releaseWave agent and the Shipment_Monitor agent are run simultaneously, if the Shipment_Monitor agent updates the Next_Alert_Ts of a shipment that has been included in a wave before the releaseWave agent does so, the releaseWave agent throws an “Update Failed” error message because it tries to update a shipment object that no longer exists.
Solution: The system has been enhanced in such a way that when a shipment is included in a wave, and this wave is currently being processed, the Shipment_Monitor agent will not pick this shipment for monitoring.
Defect ID	160521
Case ID	47297
Description	When a user performs the following sequence of actions, the system moves the pick tasks from “Held” status to “Open” status even if the forward pick location is configured as Frozen for Pick or Frozen for Variance:
1.	Configures the outbound pick task type to dispatch tasks only when the inventory is available for picking.
2.	Configures the forward pick location as Frozen for Pick or Frozen for Variance.
3.	Creates pick tasks for a shipment from the forward pick location, and moves these tasks to “Held” status.
4.	Invokes the releaseTask agent.
Defect ID	161510
Case ID	47405
Description	When a user performs the following sequence of actions, several shipments come out of the wave because the locations cannot be dynamically slotted due to faulty Trans Location attributes, for example, records with pend-in weight/volume values of 0.0001, despite no tasks being assigned to these locations:
1.	Configures the dynamic slotting to be performed from the forward pick zone.
2.	Creates items with dimensions such that the volume/weight value has four decimal places.
3.	Includes shipments with the items created in the previous step in a wave such that the demand is not fulfilled by the quantities present in the forward pick location.
Solution: When updating or inserting the Tran Location Attributes for a location, all the computations will be compared after scaling the values, that is, 0.0001 will be evaluated as 0.0000.
Defect ID	162787
Case ID	47677
Description	When a user picks inventory having multiple ShipByDate for a time-sensitive item on to a pallet, and deposits the pallet in a location that maintains a single ShipByDate, the system throws a "WMS0002 : No Records Found" exception message.
Defect ID	165147
Case ID	48169
Description	When a user performs the following sequence of actions, the application does not create tasks for all the item quantities that are included in the wave:
1.	Configures the Item Pick to pick inventory from the Bulk Location to the Pack Staging Location, and for the Pack Staging Location to have infinite capacity.
2.	Ensures that the replenishment task or the outbound pick task for an item from the Pack Staging Location to any other location in the warehouse exists in “Open” status.
3.	Creates shipments for the item, includes them in a wave, and releases the wave.
Defect ID	168353
Case ID	00007081
Description	When a user performs the following sequence of actions, the application throws an "YCPSlvFailedException" error message:
1.	Configures the sourcing rules.
2.	Creates, schedules, and releases an order in a shipment.
3.	Splits the shipment into two.
4.	Cancels both the shipments that were created in step 3 with the option to back order the quantity of the cancelled shipments.
5.	Tries to reschedule the order.
Note: This fix will work only for those shipments that are cancelled after deploying this fix.
Defect ID	168511
Case ID	00007549
Description	When a user creates a new transaction that is not derived from an abstract transaction, and tries to associate a service that can trigger this transaction, the application displays an “Out of Memory” error message.
Defect ID	168591
Case ID	00008120
Description	When a user creates a shipment with the expected shipment date and expected delivery date stamped on it, and invokes the splitShipment API to split the shipment into two, the expected shipment date and expected delivery date of the new shipment are set as HIGH_DATE.
Solution: The new shipment will have the same expected shipment date and expected delivery date as that of the original shipment.
Hot Fix ID	8.0-HF24
Defect ID	152033
Case ID	Internal
Description	When a user performs the following sequence of actions, the system throws a “No Tasks to Associate” error message:
1.	Configures the “Induct Cart” screen in the Sterling Supply Chain Mobile Application to induct cart, with the “MandateBatch” attribute set to “N” and the “StartPick” attribute set to “Y”.
2.	Tries to induct the cart by scanning the Cart ID in the “Induct Cart” screen.
Defect ID	152880
Case ID	Internal
Description	When a user performs the following sequence of actions, the system throws a "WMS0080_307 Target LPN must be passed" error message:
5.	Configures the Pick Location Assignment (PLA) to perform batch pick.
6.	Configures the Pick Exception with "Suggest Alternate Location" and "Freeze For Picking" enabled.
7.	Creates a shipment, includes it in a wave, releases the wave, and creates a batch for the wave.
8.	Inducts the batch in a cart and performs a short pick by entering the quantity as zero and providing the pick exception code.
Defect ID	154014
Case ID	Internal
Description	When a user performs the following sequence of actions, the system throws a “No Open Tasks” error message:
1.	Configures the “Induct Cart” screen in the Sterling Multi-Channel Fulfillment Solution Application to induct cart, with the “MandateBatch” attribute set to “N” and the “StartPick” attribute set to “Y”.
2.	Creates a shipment, includes it in a wave, releases the wave, and creates a batch for the wave.
3.	Logs in to the Mobile Application, selects the “Induct Cart” option, scans the cart, and picks and deposits the inventory for the batch.
4.	Creates another shipment, includes it in a wave, releases the wave, and creates a batch for the wave.
5.	Selects the "Induct Cart" option and scans the same cart as in step 3.
Defect ID	156633
Case ID	Internal
Description	When a pick task type is configured to constrain the number of users for the pick task, and when a user, who has performed a few pick tasks for a shipment through the Sterling Mobile Application is deleted from the system and another user logs in to perform the remaining pick tasks for the same shipment, the system throws a null pointer exception.
Defect ID	156644
Case ID	Internal
Description	When picking through the Sterling Mobile application, if a user reports a short pick exception that involves the suggestion of an alternate pick location, the system moves the task to “Held” status if the alternate pick location suggestion fails. The system needs to be enhanced to automatically cancel such held tasks for certain task types.
Solution: The system behavior has been enhanced. The "yfs.canceltask.onshortpick.tasktypelist" property that needs to be set to comma-separated values of the task types in the yfs.properties file has been provided. If this property is not set or the task is not of the task type mentioned in the list, the system will retain the current behavior.
Defect ID	156753
Case ID	Internal
Description	When a user performs the following sequence of actions, the system throws a “Status is not a valid pipeline pickup status for the transaction” error message:
1.	Creates a count request and the count tasks for this count request.
2.	Completes the count tasks so that the count request moves to the “Count Task Completed with Resolvable Variance” status. (The system creates a record in the YFS_TASK_Q table for the count request reference with the transaction_id as “AUTO_ACCEPT_VARIANCE”)
3.	Cancels the count request.
4.	Runs the AUTO_ACCEPT_VARIANCE agent.
Solution: When the AUTO_ACCEPT_VARIANCE agent is run for a count request that is in a state that can be purged, the system automatically deletes the task queue record from the YFS_TASK_Q table for a given count request reference instead of processing that task queue record.
Defect ID	160448
Case ID	46888
Description	When a user packs a container that belongs to an enterprise, and scans the SCM of a container that belongs to another enterprise, the shipment and container details, for example, shipment number, item details, and so on are not being populated in the Pack HSDE.
Defect ID	160709
Case ID	47092
Description	When a user performs the following sequence of actions, the releaseTask agent does not release the pick tasks for the second wave’s batch even if the inventory is available for this batch:
1.	Configures the PLA to pick the inventory from the Forward Pick Zone, with TaskType configuration as "Dispatch Tasks only when Inventory is available to Pick".
2.	Creates two waves of the same priority, containing a shipment each. (Both these shipments have two items; one distinct item and one item that is common between the shipments.)
3.	Ensures that the inventory for the distinct item of the first shipment is not available at the Pick Location.
4.	Releases the first wave and creates a batch for the first wave. 
5.	Releases the second wave and creates a batch for the second wave. 
6.	Invokes the releaseTask agent.
Solution: If the “yfs.releasetask.ignore.wavesequence” property is set to “Y” in the yfs.properties file, the system will ignore the wave sequence when releasing the tasks. Hence, if there are two waves of the same priority, but different sequence numbers, the system will release the tasks for the wave that has a higher sequence number even though the tasks for the wave with the lower sequence number are not yet released.
Defect ID	160976
Case ID	Internal
Description	Information about optimal handling of orders having a large number of order lines should be provided in the Sterling Multi-Channel Fulfillment Solution Performance Management Guide.
Solution: A new, Section 23.2.4, "Guidelines for Processing Large Orders" has been added to Chapter 23, "General Recommendations" of the Sterling Multi-Channel Fulfillment Solution Performance Management Guide.
Defect ID	161984
Case ID	47260
Description	When performing cart pick through the Sterling Mobile Application, the system should display the RF menu when a user clicks the "Back" button in the "No Open Tasks" screen after a batch picking is complete.
Defect ID	165054
Case ID	48011
Description	When a user performs the sequence of actions described here, the application does not move the inventory to the count location:
1.	Ensures that a serial-tracked item exists.
2.	Adjusts the inventory for a serial item, say SI1, for 3 units, with the inventory status as INV in location 1 of zone 1.
3.	Creates a count request for location1 of zone 2 (zone 2 does not contain any inventory).
4.	Counts 2 numbers of SI1 in location 1 of zone 2 and confirms the count. (Because the inventory is not available in location 1 of zone 2, the count request status moves to the “Count Tasks Completed with Unresolvable Variance” status.)
5.	Runs the Create Variance Tasks agent. (During the execution of the variance tasks, the application asks the user to enter the serial numbers for the item SI1.)
6.	Enters two serial numbers that are present in location 1 of zone1, and the different inventory status as “N”, and confirms the count. 
7.	Runs the Auto Accept Variance agent.
Defect ID	166875
Case ID	Internal
Description	The application should be enhanced to support encrypted properties. An interface should be implemented to provide the decryption logic, and automatically decrypt data within the property manager.
Solution: A new “propertyencrypter.class” property in the “security.properties” file has been exposed. The encrypter/dycrypter class pointed to by this property should extend the “com.yantra.yfc.util.YFCEncrypter” system interface. The value of the property should have the suffix “encrypted:”.
For example, for the “yfs.dblogin.datasource.name=value” property, the encryption should be defined as “yfs.dblogin.datasource.name=encrypted:<encrypted value>”. The system will decrypt the property based on the logic provided in the encrypter/dycrypter class.
Defect ID	166973
Case ID	Internal
Description	The Sterling Multi-Channel Fulfillment Solution Installation Guide should be updated with recommendation about using the JBoss Messaging provider instead of the JBoss MQ Messaging provider.
Solution: The document has been updated with the requisite information. The following changes have been carried out in the Sterling Multi-Channel Fulfillment Solution Installation Guide:
7.	Version number of JBoss Messaging provider has been updated in Table 2-2, "Supported Application Server Tier", and a note has been added at the end of Table 2-2, "Supported Application Server Tier", in Section 2.3, "Application Server Requirements", of Chapter 2, "System Requirements".
8.	A list of .jar files that must be included if JBoss JMS is used has been added after step 4 in Section 14.4.1, "Setting Up the Runtime Utilities" of Chapter 14, "Configuring Utilities".
Defect ID	167143
Case ID	00006036
Description	When asynchronous payment processing is enabled and the payment APIs are invoked, the application does not move the status of an order to “REQUEST_CHARGE” when the payment is processed on the order.
Solution: A new, “yfs.OrderPaymentStatus.BCrequired” property has been provided in the “yfs.properties_ysc_ext.in” file. This property should be set to “N” to move the status of an order to “REQUEST_CHARGE” when payment is processed on the order in asynchronous mode. The default value of this property is “Y”.
Defect ID	167438
Case ID	00006267
Description	When a user performs the sequence of actions described here, the application throws a "java.util.ConcurrentModificationExceptionerror" message:
1.	Creates a draft order and confirms the draft order. (The application applies a preconfigured hold, for example, Hold A, on the draft order.)
2.	Configures an action, which, on the ON_SUCCESS event of the change_order, will call a service. (This service will call a method through an extended API, which validates the status to be resolved and puts a new hold, for example, Hold B.)
3.	Tries to resolve Hold A.
Hot Fix ID	8.0-HF23
Defect ID	152863
Case ID	Internal
Description	When a user performs the following sequence of actions with zero inventory in the zones pointed by the Pick Location Assignment (PLA), the system creates replenishment tasks for the shipments that have been removed from the wave due to inventory shortages:
1.	Configures a shipment group to perform order pick PLA.
2.	Configures the replenishment strategy to replenish the zones pointed by the PLA rule mentioned in step 1.
3.	Releases a wave with only some shipment items having inventory in the warehouse.
Defect ID	153971
Case ID	Internal
Description	When a user performs the following sequence of actions through the Yantra Console Application, the system throws a "WMS00002: No record found for passed inputs" exception:
1.	Receives multiple serial items against multiple receipts at a location.
2.	Purges the receipts and the receipt history.
3.	Creates shipments for the items, includes the shipments in a wave, and releases the wave.
4.	Picks and packs the serial items for the shipments.
5.	Confirms the shipments.
Defect ID	153995
Case ID	Internal
Description	The system should not allow an “Adhoc Move” operation for a serial item that is not present at a node.
Defect ID	160528
Case ID	47317
Description	The “BeforePrepareForDepositUE” user exit has only the Task Key and the Task ID in the input. The Task Type attributes should also be included in the input to the “BeforePrepareForDepositUE” user exit.
Solution: The “BeforePrepareForDepositUE” user exit has been enhanced and made template driven.
Defect ID	161497
Case ID	47104
Description	When a user performs the sequence of actions described here, the system throws a null pointer exception:
1.	Ensures that a work order level hold exists on the work order creation.
2.	Creates an order that has a product line, an associated product pre-service line, and a delivery service line.
3.	Tries to invoke a multiAPI that has the getOrderFulfillmentDetails API as the first API and the getWorkOrderAppointmentDetails API as the second API. (The getWorkOrderAppointmentOptions API omits the product pre-service line from the input XML.)
Defect ID	161522
Case ID	Internal
Description	The SourceCaseId attribute and the SourcePalletId attribute are missing from the template of the “beforePrepareForDepositUE” user exit.
Defect ID	163989
Case ID	Internal
Description	When a user performs the sequence of actions described here, the application updates the shortage quantity to match the actual quantity of the shipment if the shipment has been removed out of a wave because of the failure of dynamic slotting for the item under consideration. Also, this scenario is the only reason for the removal of the shipment from the wave.
1.	Configures dynamic slotting in the pick location assignment configuration for a shipment group.
2.	Releases the wave for this shipment group.
Defect ID	166201
Case ID	00004742
Description	When multiple number of users, for example, 20, log in to the application concurrently, the application throws an “Out of Memory” error message.
Defect ID	166737
Case ID	00005900
Description	When a user performs the sequence of actions described here, the drop-down “Fulfillment Type” field in the “Sourcing Rule for Product Being Shipped” screen is displayed as a text box:
1.	Navigates to DOM > Cross Application > Order Promising > Sourcing and Scheduling > Fulfillment Type, and creates more than 75 entries.
2.	Navigates to Product Being Shipped > Sourcing Rules and clicks the “Add” icon in the “Product Sourcing Rules Search” screen. (The application displays the “Sourcing Rule for Product Being Shipped” screen.)
Defect ID	167067
Case ID	00006237
Description	When a user performs the following sequence of actions, the application throws an “Invalid Country passed” error message:
1.	Enables the Inventory Costing Required option and the Node Maintains Inventory option.
2.	Configures the Costing Method as Average Cost and the Standard Cost Computation Rule as Replacement Cost.
3.	Defines unit cost, primary supplier, posting classification, and a seller’s price program.
4.	Invokes the modifyItem API with the ComputeUnitCost attribute set to “Y”.
Defect ID	167071
Case ID	00006146
Description	When a user adds a link with static text in a new column in a non-editable table, the application does not transfer the control to the linkSelected method if the user clicks the link.
Defect ID	167620
Case ID	00004769
Description	When a user performs the following sequence of actions, the application does not delete the pipeline record from the target database:
1.	Creates an order pipeline in the source database and ensures that this order pipeline is not present in the target database.
2.	Runs the Configuration Deployment Tool (CDT) to compare the source database and the target database.
3.	Deploys the new configuration on the target database and ensures that the order pipeline that was created in step 1 is present in the target database.
4.	Deletes the order pipeline from the source database.
5.	Runs the CDT again to compare the source database and the target database.
6.	Deploys the new configuration on the target database.
Hot Fix ID	8.0-HF22
Defect ID	159834
Case ID	Internal
Description	When a user performs the following sequence of actions, the system associates the product line to a new work order instead of the existing work order:
1.	Creates an item, for example, ITEM1, and associates a delivery service line, for example, DS1, and a provided service line, for example, PS1, to this item.
2.	Creates an order with ITEM1, DS1, and PS1.
3.	Invokes the generateWorkOrder API with the "ConsolidateToExistingWorkOrder" flag set to "Y".
4.	Schedules and releases the work order.
5.	Backorders the product line and removes the product line from the work order so that the work order now contains only PS1.
6.	Invokes the generateWorkOrder API again, with the "ConsolidateToExistingWorkOrder" flag set to "Y".
Solution: This issue has been fixed. Order consolidation will occur only when the product line is associated with the provided service line in an existing work order.
Defect ID	161525
Case ID	Internal
Description	When a user performs the following sequence of actions, the application creates a case or pallet deposit task with the target location stamped on it, but does not invoke the “beforePrepareForDepositUE” user exit for the new task:
1.	Configures the Outbound Pick Task type as Pick into Inventory Case or Pallet.
2.	Tries to complete the Outbound Pick task by picking the inventory for a shipment into a case or pallet and clicking the “Go” button.
Defect ID	163442
Case ID	41885
Description	When a user schedules a product line that requires delivery, and has a ship node assigned to the product line, but does not have a work order, the product line does not move to the “Reserved” status.
Solution: The system has been enhanced to move the product line to the “Reserved” status when a user schedules a product line that requires delivery, and has a ship node and an associated service line assigned to the product line.
Defect ID	163997
Case ID	Internal
Description	When a user performs the following sequence of actions, the application does not create a procurement transfer order for a sales order when the NOINV sourcing control is passed at the order line level for the ship node, and inventory is available at the procurement node:
1.	Configures the sourcing rule for procurement and the products that are being shipped.
2.	Ensures that a transfer schedule exists between the ship node and the procurement node.
3.	Requests the delivery date and ship date on an order line after the transit days.
4.	Schedules the sales order.
Defect ID	163999
Case ID	Internal
Description	When a wave that has been released is cancelled, the application creates two wave audit records for each shipment that is removed from the wave.
Solution: The application has been enhanced to create only one wave audit record for each shipment that is removed from the wave that is cancelled after release.
Defect ID	165669
Case ID	00004326
Description	The getPage API does not support pagination for Synchronous Services.
Solution: The getPage API now supports pagination for Synchronous Services. For details, see the information pertaining to the getPage API in the Sterling JavaDocs.
Defect ID	166347
Case ID	00005167
Description	When a user performs the following sequence of actions, the application sets the disposition code as “No QC Required” instead of “QC Required”:
1.	Ensures that two disposition codes exist, for example, “QC Required” and “No QC Required”.
2.	Ensures that a receiving preference exists at the item classification level, with the “QC Required” disposition code set to “Y”.
3.	Configures an item with the item classification that was set up in step 2.
4.	Receives a shipment containing the item that was configured in step 3 from the “High Speed Data Entry” (HDSE) screen and scans the item.
Solution: This issue has been fixed. The unit of measure will be passed as input to the getReceivingPreference API.
Defect ID	166457
Case ID	00005383
Description	When a user performs the following sequence of actions, the application does not suggest the available location for putaway even if the capacity of this location is equal to the capacity of the pallet:
1.	Configures an item with 2 decimal places for the length, width, and height values.
2.	Configures a location with a Location Size Code such that 100 units of the item that was defined in step 1 will fit in this location.
3.	Configures the putaway preferences to consider the location that was defined in step 2 as the first priority.
4.	Creates a move request for a pallet that contains 100 units of the item that was defined in step 1, and releases the move request.
Defect ID	166537
Case ID	00004710
Description	When a user tries to enable validation for the “Quantity” field in the “Add Items” screen in the Sterling Customer Order Management PCA using the extensibility feature, the application does not display the pop-up window that contains the “Validation Required” check box.
The application exhibits this behavior for all the attributes that are mandatory.
Defect ID	166570
Case ID	00005645
Description	The XML file generated by the out-of-the-box XSD generator contains namespaces that cause the application to throw an “Invalid XML” error message, even if the namespace validation is set to “N”.
Solution: A new “USETARGETNS” flag has been exposed in the sandbox.cfg. If this flag is set to “False,” the generated XSD file will contain the namespace in the annotation element. If no value is set, the generated XSD will contain namespaces.
Defect ID	166599
Case ID	00005551
Description	When a user performs the following sequence of actions, the application throws a “WMS00016: Serial already exists” error message:
1.	Creates an item, for example, L1, and configures the item as serial-tracked and serialized.
2.	Creates an inbound shipment for L1 with the quantity as 2 units.
3.	Confirms the shipment.
4.	Starts the receipt of the shipment by entering the dock location, for example, D1, and clicks the “Save” button.
5.	Receives the shipment by scanning L1, enters the serial numbers of the 2 units of L1 when prompted by the application, and clicks the “Close” button.
6.	Selects the appropriate disposition code and clicks the “Save” button.
7.	Navigates to Inbound > Inbound Receipt Console > Receipt Summary, selects “Items”, and clicks the “Adjust Receipt” button.
8.	Selects the dock location D1 and clicks the “Inventory Status” button.
9.	Enters 1 as the unreceive quantity in each line and clicks the “Adjust” button.
10.	Enters the appropriate Modification Reason code when prompted by the application.
Defect ID	166744
Case ID	00005477
Description	The isFlow attribute that is set to “Y” has been added to the input XML in order to support pagination of services in the getPage API.
Defect ID	166749
Case ID	00005931
Description	When a user tries to split or delete a container from a transfer order shipment that is in “Shipped” status, the application throws a “Set up for order modification permission missing” error message. This is because the Undo Pack Shipment Complete event, Transaction, Drop Statuses, Status Modification Type, and Status Modification Details are missing from the Transfer Order Process Model.
Hot Fix ID	8.0-HF21
Defect ID	149196
Case ID	Internal
Description	When a user performs the following sequence of actions, the Yantra 7x Mobile Application updates a new task with the task type configured from the Pick Location Assignment instead of the current task type:
1.	Creates a shipment, includes it in a wave, releases the wave, containerizes the wave and creates a batch for the wave.
2.	Changes the task type for the tasks in the batch created in Step 1.
3.	Inducts a tote against the batch using the “Induct Tote” activity.
4.	Builds a cart for the tote using the “Cart Build” activity.
Defect ID	149206
Case ID	Internal
Description	When a user performs the following sequence of actions, the getWorkOrderAppointmentOptions API throws a null pointer exception:
1.	Creates a return order having an associated exchange order.
2.	Creates a common work order which includes lines from the return order and the exchange order that were created in step 1.
3.	Invokes the getWorkOrderAppointmentOptions API after omitting the lines from the return order and the exchange order.
Defect ID	154017
Case ID	Internal
Description	The manageWave API fails for a large number of shipments if the shipment hold types are configured for the Order Delivery process type.
Defect ID	154070
Case ID	Internal
Description	When a user performs the following sequence of actions, with the inventory for an item not available in both the bulk and forward pick zones, the Wave Release agent sporadically throws a “java.util.ConcurrentModificationException” exception and the wave remains in the ”Accepted” status:
1.	Configures the Pick Location Assignment (PLA) to perform an order pick and picks the inventory from the pick zone.
2.	Configures the PLA to perform a pick from the dedicated location and use dynamic slotting.
3.	Configures the PLA with the pick fence factor to pick from the pick fence zone.
4.	Creates a shipment, includes it in a wave, and releases the wave.
Defect ID	154491
Case ID	Internal
Description	When a user performs the following sequence of actions, the getWorkOrderAppointmentOptions API does not calculate the capacity for the return lines:
1.	Configures a delivery service (DS) whose quantity depends on the product line quantity.
2.	Associates the DS with a returnable item.
3.	Ensures that a resource pool exists that has some slots with zero capacity.
4.	Ensures that a return order (product + DS) and a corresponding exchange order (product + DS) exist in “Draft” status.
5.	Invokes the generateWorkOrder API for the return order and the exchange order.
6.	Invokes the getWorkOrderAppointmentOptions API and omits all the lines in the exchange order in the input XML of this API.
Defect ID	155083
Case ID	Internal
Description	The system should be enabled to read and pass the RCP Client properties to the server.
Solution: The Sterling Supply Chain Applications Customization Guide, Release 8.0 has been updated with a new section describing the version-based communication between the client and the server. The updated document is released with this hot fix.
Defect ID	155103
Case ID	Internal
Description	A work order does not move to the “Work Order Completed” status when its standalone provided services line is delivered and other lines are cancelled.
Defect ID	157217
Case ID	Internal
Description	When a user performs the following sequence of actions, the application does not remove the association between the product line and the delivery service line:
1.	Creates an item and a delivery service and associates the two.
2.	Ensures that a work order exists for an order that has a product line and a delivery line.
3.	Removes the product line from the work order.
Solution: Product has to be enhanced to automatically remove the associations between the prod and the delivery service line.
A new flag "Automatically remove association between product and delivery service lines" that has a default value of “N”, has been provided under DistributedOrderManagement > VAS > VASRules. The flag should be set to “Y” to automatically remove the associations.
When this flag is not selected in the Configurator, there will be no change in the functionality.
Defect ID	160228
Case ID	Internal
Description	The Sterling Multi-Channel Fulfillment Solution Installation Guide should be updated with the information about the DB2LOCK_TO_RB parameter.
Solution: Information about the DB2LOCK_TO_RB parameter has been added to Section 5.3, "Installing DB2 (UNIX/Linux)" in Chapter 5, "Installing and Configuring Database Tier Software on UNIX/Linux", of the Sterling Multi-Channel Fulfillment Solution Installation Guide. The updated document is released with this hot fix.
Defect ID	161514
Case ID	47350
Description	When a user performs the following sequence of actions, the system does not remove the associated delivery service from the exchange order:
1.	Creates a return order and an exchange order with a product item.
2.	Associates a delivery service for both the product items created in step 1.
3.	Creates a common work order for both the orders created in step 1.
4.	Deletes the product item from the exchange order that is present in the common work order.
Defect ID	161912
Case ID	47676
Description	When a user performs the following sequence of actions, the application incorrectly suggests a task from another batch:
1.	Configures a new resource for the RF Induct Cart with MandateBatch set to “N”.
2.	Configures Batch Picking using cart equipment.
3.	Creates two shipments and includes them in two different waves.
4.	Assigns lanes to the waves, releases the waves, and creates a different batch for each wave.
5.	Navigates to the “Induct Cart” screen and scans a cart ID.
6.	Moves the task that is suggested by the system to the “In-Progress” status and logs out of the RF.
7.	Logs in again to RF, navigates to the “Induct Cart” screen, and scans the same cart ID that was scanned in step 5.
Solution: The application has been enhanced to throw an error message if all the tasks for the current batch that are inducted into a cart are either canceled or not completed by the user.
Defect ID	162785
Case ID	47635
Description	When dynamic slotting is configured for the second and subsequent wave releases, the application considers the previously slotted locations to minimize the number of locations. The application should have a provision to not consider the previously slotted locations for the subsequent wave releases.
Solution: A new "yfs.allow.reuse.previouswave.slots" property has been provided in the yfs.properties file. This property is set to “Y” by default. If this property is set to “N”, the application will not consider the previously slotted locations for the subsequent wave releases.
Defect ID	163374
Case ID	Internal
Description	The “Getting Around” page in the Sterling Multi-Channel Fulfillment Solution Online Help is not being merged for the PCAs.
Defect ID	164728
Case ID	Internal
Description	When the Length Checker tool is run, if multiple entry definitions exist for the same entity, the Length Checker tool generates a MissingLength.txt file that contains a large number of literals.
Defect ID	164822
Case ID	00003676
Description	When a user invokes the scheduleOrder API to schedule orders that contain the same items and multiple order lines, the application encounters a deadlock on the YFS_INVENTORY_ITEM table if the user invokes this API more than once simultaneously.
Defect ID	165141
Case ID	Internal
Description	The application throws WMS0169 error when picking inventory into an inventory case or pallet without scanning an equipment.
Defect ID	165489
Case ID	00003616
Description	When a user performs the following sequence of actions, the average value and inventory value are not synchronized after the inventory is moved from one product class to the other:
1.	Enables Average Costing.
2.	Ensures that an item with two product classes, namely GOOD and BAD exists at a node; the GOOD inventory having higher value than the BAD inventory.
3.	Invokes the changeLocationInventoryAttributes API to move inventory from one product class to the other.
Solution: A new “Allow Average Cost and Inventory Value sync when adjusting inventory” rule has been provided under the Standard Cost Computation Rule in the “Other Rules” tab of the “Inventory Rules” screen. If this rule is enabled, the application will synchronize the average cost when inventory is moved.
Defect ID	165826
Case ID	00003616
Description	The Sterling Global Inventory Visibility Configuration Guide should be updated with the information about the new “Allow Average Cost and Inventory Value sync when adjusting inventory” flag that has been provided under the Standard Cost Computation Rule in the “Other Rules” tab of the “Inventory Rules” screen.
Solution: The requisite information has been added to the description of the Standard Cost Computation Rule field in Table 3-9, “Other Rules Tab” in Section 3.5, “Defining Additional Inventory Rules” of the Sterling Global Inventory Visibility Configuration Guide. The updated document is released with this hot fix.
Defect ID	165918
Case ID	00004925
Description	The Sterling Multi-Channel Fulfillment Solution Upgrade Guide should be updated with information about the support provided for a multi-hop upgrade process from Yantra, Release 7.3 (or higher) to Sterling Multi-Channel Fulfillment Solution, Release 8.0.
Solution: Information about the multi-hop upgrade process has been added to the initial part of Chapter 1, “Performing a Migration Assessment” of the Sterling Multi-Channel Fulfillment Solution Upgrade Guide. The updated document is released with this hot fix.
Defect ID	166098
Case ID	00005090
Description	When a user performs the following sequence of actions, the application displays the target pallet ID in the “Target Case ID” field and the “Target Pallet ID” field in the “Confirm batch With Details” screen instead of displaying the target pallet ID only in the target pallet ID field:
1.	Configures the Pick Planning as Batch Picking with the task type as Pick Into Inventory Pallet and Pack While Pick.
2.	Creates a shipment, includes it in a wave, releases the wave, and creates a batch for the wave.
3.	Navigates to the “Confirm Batch” screen, enters the batch ID, target pallet ID, total time required to complete the batch, and clicks the “Confirm Batch With Details” button.
Defect ID	166195
Case ID	Internal
Description	When the getAlertStatisticsForUser API is repetitively invoked for more than 100 times, the API fails and the application throws an "ORA-01000: maximum open cursors exceeded" exception message.
Defect ID	166805
Case ID	Internal
Description	The Sterling Supply Chain Applications Customization Guide should be updated with information about the enhancement that enables the application to read and pass the version number of the COM client to the server.
Solution: In Chapter 6, “Customizing the Sterling Rich Client Platform Interface” in the Sterling Supply Chain Applications Customization Guide, a new Section 6.3.23, “Version-Based Communication between Client and Server” has been added. The updated document is released with this hot fix.
Hot Fix ID	8.0-HF20
Defect ID	156649
Case ID	Internal
Description	The application should be enhanced for the following:
9.	Allow dynamic naming of the related task menu, based on the context of the current screen. Currently, with a resolution of 800 by 600 pixels, the task menu is displayed with the generic name “Tasks” irrespective of the screen in use.
10.	A new command-line parameter (-D option) should be provided to indicate whether the related task menu in a lower resolution of 800 by 600 pixels should be displayed as a sub menu based on the group name or have a flat structure, that is, display all the options in a single menu.
Solution: The application has been enhanced to dynamically name the related task menu based on the screen. The related task menu names are resource bundle-driven and the syntax of the entry key is <TASK_ID>_TASK_MENU. For example, if the task name is YCD_TASK_QUICK_ACCESS, the entry in the bundle should be YCD_TASK_QUICK_ACCESS_TASK_MENU=Quick Access. If the appropriate entry is not present, the related task menu takes the generic name "Tasks".
A new "showtasksassubmenu" -D option has been added. If the value of this argument is set to True, the tasks are displayed as sub menus. If the value is set to False, the tasks are displayed as a flat structure. The default value of this argument is True. The new -D option will take effect only when the related tasks are displayed at the top of the screen and not on the left as in screens with a resolution of 1024 by 768 pixels.
Defect ID	157929
Case ID	Internal
Description	The YIF API JavaDoc does not contain information about all the APIs that are extended by the YIF API.
Defect ID	159844
Case ID	Internal
Description	When the value of the “yfs.install.displaydoublequantity” property is set to “N” in the yfs.properties file, the system displays the values for the “Collected Amount” field in the “Payment Information” screen for a sales order in the Yantra console as an integer, instead of a decimal value.
Defect ID	162039
Case ID	Internal
Description	Currently there is no configuration option to control the audit for the change order status.
Solution: An option to suppress the audits for the change order status has been provided at the configurator level instead of the API level.
The audits for the changeOrderStatus API can be suppressed by navigating to Distributed Order Management > Document Specific > Transfer Order > Fulfillment > Order Modification > Modifications Requiring Auditing > Details > Modification Requiring Auditing list and moving the “Change Status” modification type from the “Subscribed” column to the “Available” column.
Defect ID	164714
Case ID	48162
Description	The new “boolean isExtendedControlVisible(String controlName)” method that was previously exposed for the “Save Against Customer” option in the “Add New Payment method” pop-up screen has to be renamed.
Solution: The method previously exposed to check visibility of Out of the Box controls that are extended using the RCP Extensibility Tool has been renamed to isExtendedControlHidden. This method has the following signature:
boolean isExtendedControlHidden(String controlName)
Here, controlName is the name of the Out of the Box control against which the visibility has to be verified. The method returns the Boolean value "true" if the control is hidden using extensibility.
Defect ID	164993
Case ID	00004162
Description	When the “YFSGetLineChargesForShipmentUE” user exit has been implemented, the input struct passed to this user exit should contain the following parameters:
11.	shipmentKey
12.	shipmentNo
13.	shipNode
14.	sellerOrgCode
Defect ID	165385
Case ID	Internal
Description	When the outbound picking and multi-line shipment tasks are configured, and a user scans the Item ID instead of the pallet, the application throws an irrelevant “Quantity not passed in the input” error message.
Hot Fix ID	8.0-HF19
Defect ID	155080
Case ID	Internal
Description	When a user logs in to the Sterling Customer Order Management PCA application and performs the following sequence of actions, the system displays the date (that is, the month, date, and year values) with the date and month values interchanged:
1.	Selects the “Advanced Order Search” screen.
2.	Enters the “Month”, “Day” and “Year” values in the “mm-dd-yyyy” format in the “Order Date From” field. For example, 03-01-2008 to indicate March 01, 2008 (That is, the user enters the month, date, and year values separated by a hyphen).
3.	Tabs out of the “Order Date From” field. (The date 03-01-2008 entered by the user changes to 01/03/2008)
Note: This defect is present in the Sterling Customer Order Management PCA because of a Foundation issue.
Defect ID	155082
Case ID	Internal
Description	When the evaluateDynamicBinding method is computed for any of the Text, Styled Text, Label or Link controls, the layout of the parent composite of the corresponding control is not reset. Because of this, the labels are displayed as right-aligned instead of left-aligned, and the partial string is displayed on the control.
Solution: An additional relayoutParent(String controlName) method has been exposed in the YRCExtentionBehavior.java file. Another relayoutScreen() method has also been added to refresh the screen. These two methods can be used to refresh the parent composite of the control or the entire screen, when required.
Defect ID	156619
Case ID	Internal
Description	When a user creates a standard label on an existing screen using the RCP extensibility tool, the extended label does not get wrapped, and the system does not display the entire label.
Solution: The “yuix” file has been modified to accept either of the following style specification formats:
15.	<SetData name="YRCExtnTextStyle" value="BORDER"/>
16.	<styles>
<style style="BORDER"/>
</styles>
After this fix, if the “yuix” file is modified, the style specification, including the styles of the controls that were added or modified before this fix, will be stored in the second format provided in the preceding list.
Defect ID	162143
Case ID	Internal
Description	When a user enters the Item ID, Location, and Reason values in the corresponding fields in the “Adjust Inventory” screen of the Store Inventory Managament 7.2 PCA, and tabs out, the applications throws a “java.lang.NoSuchMethodError: com.yantra.yfc.rcp.foundation.containers.store.screens.YRCStoreCustomerMessage.getInstance()” error message.
Solution: This issue has been fixed at the infrastructure level by adding additional methods in the IYRCMessageDisplayer.
Defect ID	163926
Case ID	Internal
Description	The application should be enhanced to have the capability to create a shipment for an order line that does not exist in the system, but the order corresponding to the shipment exists.
Defect ID	164188
Case ID	48198
Description	When a user performs the following sequence of actions, the application throws an “OMP10079: Quantity greater than the allowed over shipment percentage limit” error message:
1.	Configures a listener in the Sales Order pipeline after the “Include In Shipment” transaction, which listens to an extended “Created” status in the Shipment pipeline and drops to an extended “Included in Shipment” status.
2.	Ensures that an order exists in “Shipped” status.
3.	Invokes the changeShipmentStatus API with the AcceptOutOfSequenceUpdates flag set to "Y", in order to move the shipment to “Created” status.
Defect ID	164236
Case ID	Internal
Description	When the yfs.property yfs.releaseWave.handleShortages property is set to RemoveShipmentsFromWave, if a shipment is removed because of shortages when releasing a wave, the HAS_NODE_EXCEPTIONS flag is not set to “Y” for the shipment that is removed.
Defect ID	164266 
Case ID	48397
Description	When a user performs the following sequence of actions, the application throws a “WMS00002: No record found for passed inputs” error message:
1.	Configures an item that is serial tracked and FIFO tracked.
2.	Adjusts two serial items, with the item configured in step 1 in a location, and navigates to the “Change Location Inventory Attributes” screen.
3.	Enters a serial number and changes the FIFO number.
4.	Clicks “Save”.
Defect ID	164535
Case ID	00003612
Description	When a user performs the following sequence of actions, the application displays the target LPN number in both the “Target Pallet ID” field and the “Target Case ID” field in the “Complete Batch” screen:
1.	Configures Batch Picking with task type as Pick Into an Inventory Case/Pallet.
2.	Confirms a batch from the “Confirm Batch” screen by entering the target LPN number and clicking the “Confirm Batch With Details” button.
Solution: This issue has been fixed. If the task type is Pick Into Inventory Case, the target LPN number will be displayed only in the “Target Case ID” field in the “Complete Batch” screen. Similarly, if the task type is Pick Into Inventory Pallet, the target LPN number will be displayed only in the “Target Pallet ID” field in the “Complete Batch” screen.
Defect ID	164725
Case ID	00003577
Description	When a user performs the following sequence of actions, the application throws a "YFS10136: YFS: Setup for order modification permissions missing" error message:
1.	Creates a transfer order for an item with the Quantity as one, and confirms the order.
2.	Adds a new line with another item that has the Item Description and the Item Short Description defined, and the Quantity as one.
3.	Clicks “Save”.
Solution: A new status modification rule for transfer order has been introduced. The new rule can be accessed by navigating to Supply Collaboration > Document Specific > Transfer Order > Fulfillment > Order Modification > Modification Rules > Change Item Description > Line for the following statuses: Draft Order Created, Created, Reserve, Being Negotiated, Accepted, Back Order, Scheduled, Unscheduled, and Awaiting Chain Order Creation.
By default this rule is set to the "Ignore" status.
Defect ID	164727
Case ID	00003657
Description	When a move request is released with the Requested Quantity as zero and the Activity Group as replenishment, the application incorrectly generates a putaway task instead of a replenishment task.
Defect ID	164815
Case ID	00003899
Description	When a user performs the following sequence of actions, the INSPECT_RECEIPT transaction throws a “WMS00002: No record found for passed inputs” error message:
•	Configures an item that is serial tracked and FIFO tracked.
•	Receives the inventory against a receipt for the item configured in step 1.
•	Inspects the receipt through the Sterling Application Console.
Defect ID	164877
Case ID	00004059
Description	When a user performs the following sequence of actions, the application completes the pick tasks without actually moving the inventory:
3.	Configures OutBound picking.
4.	Ensures that an item exists only in a pallet and no other inventory is present.
5.	The RF user scans the Item ID in place of the LPN.
Defect ID	165357
Case ID	00004252
Description	When a user performs the following sequence of actions, the RELEASE_WAVE transaction cancels the wave and marks the shipment with inventory shortage:
1.	Configures an item that is serial tracked and FIFO tracked.
2.	Adjusts inventory for the item that was configured in step 1 at a location.
3.	Configures the pick location assignment to point to the zone of the location that was mentioned in step 2.
4.	Creates shipment for the item with the shipment line having requested serial number.
5.	Creates a wave for the shipment that was created in step 4 and releases the wave using the pick location assignment that was configured in step 3.
Hot Fix ID	8.0-HF18
Defect ID	162957
Case ID	47947
Description	The splitShipment API should be enhanced to split the inbound and transfer shipments. 
Solution: This issue has been fixed. The quantity that has not yet been received can be split from the shipment.
Defect ID	163370
Case ID	48162
Description	A user is unable to hide the “Save against customer” check box in the "Add New Payment Method" pop-up window.
Solution: A new “boolean isExtendedControlVisible(String controlName)” method has been added in YRCBaseBehavior to check the visibility of a control that has its visibility modified only through the RCP extensibility tool. This method has the following signature:
boolean isExtendedControlVisible(String controlName)
Here, controlName is the name of the control against which the visibility should be verified. This method returns the boolean value "true" if the control is visible.
Defect ID	163388
Case ID	48126
Description	When a user performs the sequence of actions described here, the ShipNode attribute in the input to YFSRecalculateLineTaxUE user exit is blank:
1.	Creates two ship nodes, Node 1 and Node 2.
2.	Creates a distribution group that contains both the nodes that were created in step 1.
3.	Creates a sourcing rule for the “Product being Shipped” and ensures that this sourcing rule sources from the distribution group that was defined in step 2.
4.	Ensures that inventory for an item exists in Node 1 and Node 2, with quantity as 1 for each of the nodes.
5.	Ensures that an order for this item exists, with quantity as 2, and that the ship node is not specified in the order line.
6.	Schedules and releases the order. (The application creates two release orders.)
7.	Creates a shipment for the first release order and confirms it.
8.	Invokes the createShipmentInvoice API.
Defect ID	163485
Case ID	48039
Description	When a user performs the following sequence of actions, the application throws a null pointer error. Also, if the shipment was created from an order, the Lock ID audit information is displayed in the “Shipment Audit” screen:
1.	Navigates to Distributed Order Management > Document Specific > Sales Order > Outbound Logistics > Shipment Modification > Shipment Modification Requiring Auditing. 
2.	Clicks the “Modify” icon and removes all the values in the “Modification types” panel.
3.	Navigates to Distributed Order Management > Document Specific > Sales Order > Shipping preferences > Transaction Rules tab.
4.	Ensures that the “Order available on system” rule is set to “No”.
5.	Creates an outbound shipment without passing the order information.
6.	Tries to view the shipment audits from the “Shipment Audit” screen.
Note: The Lock ID audit information will not be displayed in the “Shipment Audit” screen. This ensures that the “Shipment Audit” screen is in sync with the other audits, such as ModifyTs, Action, Modifyprogid, Modifyuserid, and so on, that have been suppressed in this screen.
Defect ID	163559
Case ID	48054
Description	For the Synchronous JMS component, the application generates the JMS-correlation-id (or MESSAGEID) that contains 40 characters on the request message. But the maximum value recommended by IBM-MQ is 24 characters due to which a timeout occurs and the application fails to get the response.
Solution: A new yfs.restrict.flowmessageid.lengthto24 property has been exposed. If this property is set to “Y”, the application will restrict the length of correlating attributes such as MESSAGEID and JMS-Correlation-ID to 24 characters.
Defect ID	163675
Case ID	48225
Description	The RCP JavaDocs is not available in Sterling JavaDocs for Sterling Multi-Channel Fulfillment Solution, Release 8.0
Solution: The JavaDocs pertaining to all the RCP classes has been incorporated in Sterling JavaDocs for Sterling Multi-Channel Fulfillment Solution, Release 8.0. This is available at \xapidocs\core_javadocs\rcp\com.
Note: The RCP JavaDocs will not be accessible from the console Online Help option.
Hot Fix ID	8.0-HF17
Defect ID	158239
Case ID	Internal
Description	The validation formats the erroneous quantity and the application does not display the quantity as entered by a user.
Solution: A new isCellInError(Element ,String) method has been added in the IYRCCellModifier.java file. This method returns the boolean value “true” if the editable cell in a table is in error.
Defect ID	160038
Case ID	47250
Description	The application should provide the user with the ability to override the default “Web Services Description Language (WSDL) style, which is the “rpc” style, for Web services on the JBoss application server.
Solution: The buildEAR script has been enhanced to receive a new -Djboss-java2wsdl-style parameter, using which the user can override the default “rpc” style. The valid values for the -Djboss-java2wsdl-style parameter are “rpc” and “document”.
Defect ID	161982
Case ID	Internal
Description	When a user performs the following sequence of actions, the application displays a "Mismatch on the ship nodes of work order and the lines added to the work order" error message:
1.	Creates an order for a product line.
2.	Marks the Delivery Method as DELIVERY from the “Line Details” screen for this order.
3.	Adds a standalone, provided service line that has a different ship node, to the order.
4.	Invokes the generateWorkOrder API with the ConsolidateToExistingWorkOrder flag set to "Y".
Defect ID	162469
Case ID	48010
Description	When the “Receiving HSDE” screen is used to enter the serial number and secondary serial number for an incoming shipment, and a user uses the Shift+Tab key combination to edit a previously entered value, the application throws a "Secondary Serial #2: {0} must be entered" error message in a pop-up window.
If the user clicks the “OK” button in the pop-up window, the application enters into an infinite loop and displays the pop-up window repetitively.
Defect ID	162473
Case ID	47854
Description	When a user extends the table in the “Advanced Add Item” screen by adding custom columns, and applies the theme, the application does not apply the theme to the extended columns.
Solution: The color theme can be applied to the extended columns. This enables the developer to change the font, the foreground color, and the background color of the extended columns.
Defect ID	162844
Case ID	47820
Description	When a user performs the sequence of actions described here, the application moves the order to the “Scheduled” status instead of the "Awaiting Chained Order Creation” status. However, if the user clears the “Get External Supply” real-time flag for the node and tries to schedule the order, the application moves the order to the “Awaiting Chained Order Creation” status.
1.	Creates an enterprise as a legal entity, with the inventory organization as “DEFAULT”.
2.	Creates a node for the enterprise that was created in the previous step, and enables the “Get External Supply” real-time flag for this node.
3.	Implements the INVGetExternalSupplyUE user exit.
4.	Sets the sourcing rules to allow the creation of the chained order.
5.	Creates a sales order and tries to schedule the order.
Defect ID	163010
Case ID	48128
Description	When a user performs the sequence of actions described here, the output of the findInventory API displays the availability from the first node even if it arrives at a later date than the second node. Also, the priority of the second node is incorrect.
1.	Configures two distribution rules, each with a distribution rule that has a set of common nodes.
2.	Ensures that the priorities of the nodes are different in the two distribution rules.
3.	Configures the sourcing rule to use only the ONHAND supply for the FIRST distribution rule and All Supply for the SECOND distribution rule.
4.	Ensures that future supply exists in both the nodes, with the first node having the necessary supply for a date that is later than that of the second node
5.	Invokes the findInventory API.
Defect ID	163062
Case ID	Internal
Description	The application should be enhanced to permit the user to suppress the overage verification when confirming a shipment.
Solution: If the value of the OVER_SHIP_PERCENTAGE column in the YFS_SHIPMENT_PREFERENCE table is negative, the application will skip the overage and overship validations.
Defect ID	163104
Case ID	48083
Description	When the YFSGetSupplyCorrectionsUE user exit is implemented, and a user creates and schedules an order, the “OrderReference” attribute in the input of the YFSGetSupplyCorrectionsUE user exit is missing.
Defect ID	163163
Case ID	Internal
Description	When a load that has multiple load stops is created, and none of the stops have been reached yet, and a user tries to take the dock appointment for a node, which is one of the load stops of the load, the application throws an “Index Out Of Bounds” exception message.
Hot Fix ID	8.0-HF16
Defect ID	151124
Case ID	Internal
Description	When a user performs the following sequence of actions, the system throws an error message:
1.	In the Yantra Capacity Console, selects the resource pool and clicks “Standard Capacity”.
2.	In the “Standard Capacity” screen, clicks “Create New”, enters a period, and clicks “Save”.
3.	In the “Current Standard Capacity Details” screen, selects a day that is grayed out, enters the capacity, and clicks "Copy Capacity".
Defect ID	152870
Case ID	Internal
Description	When a user performs the following sequence of actions, the system uses the authorizations corresponding to a payment method even after the payment method is suspended:
1.	Enables Payment Processing for the seller organization and implements the YFSCollectionCreditCardUE user exit.
2.	Creates a sales order with the payment method as credit card.
3.	Invokes the processOrderPayments API to move the order to “Authorized” status. 
4.	Suspends the credit card payment, and then invokes the processOrderPayments API. (The order moves to the “Authorized” status).
Defect ID	153448
Case ID	Internal
Description	When the changeOrder API is invoked twice in the same transaction boundary to cancel the lines belonging to a work order, the new status audit that is created by the first API is also displayed by the subsequent APIs as NewStatusAudit="Y".
Defect ID	156440
Case ID	Internal
Description	The system should be enhanced to pick up the extension provided by the Sterling Customer Order Management plug-in for the Menu Displayer extension point, and to pick up the extension provided by the Infrastructure only when there are no other extensions defined for a given extension point.
Defect ID	156646
Case ID	Internal
Description	When a user creates a sales order with order line reservation, the system incorrectly inserts OPEN_ORDER demand in the YFS_INVENTORY_DEMAND_DTL table instead of RSRV_ORDER demand. Thus, when the sales order is scheduled, the system does not process or remove the OPEN_ORDER demand, and hence, this demand remains beyond the order lifecycle in the YFS_INVENTORY_DEMAND_DTL table.
Solution: The entry in the YFS_INVENTORY_DEMAND_DTL table will be correct. There should be only one entry for the SCHEDULED demand type after scheduling.
Defect ID	156651
Case ID	Internal
Description	When a user confirms a return order that is derived from a sales order, which in turn has two lines and different ship nodes, and invokes the startReceipt API and the receiveOrder API for both the order lines, the receiveOrder API of the second order line throws a “Cannot receive in transit shipment” error message.
Defect ID	156934
Case ID	Internal
Description	When using the Genetic Algorithm (GA) to solve a problem, some sections of the code are repetitive, which leads to performance issues in the GA platform. Also, a method to force stop the GA should be provided.
Solution: An extra hook has been provided to limit the elapsed time of run of the GA, and the code has been corrected to avoid immature convergence to a non-optimal solution.
Defect ID	157850
Case ID	47268
Description	The RCP PCA does not call the evaluateDynamicBinding method for the controls added through extensibility.
Defect ID	157996
Case ID	Internal
Description	When the yfs.donot.validate.contactinfo.countrycode property is set to “Y” in the yfs.properties file, the “Address Details” screen in the Yantra Configurator > Platform > Participant Modeling > Participant Setup > Organization Details > Primary Information tab should display the value of the COUNTRY column from the YFS_PERSON_INFO table in the “Country” field instead of the Country Short Description value.
Defect ID	158749
Case ID	Internal
Description	When the calendar of a resource pool is an inherited calendar, the user should be able to adjust the standard capacity for the resource pool.
Defect ID	159415
Case ID	Internal
Description	The system should have the ability to carry out case-insensitive retrieval of data for extended columns.
Solution: The “ForceUpperCase” attribute supports case-insensitive search on varchar columns. To enable this capability, the entity definition should expose a new “ForceUpperCase” attribute that is set to "true" for the columns that need to be case-insensitive.
When building the database classes, in buildWLS.xml, buildWS.xml, or buildJBoss.xml, the “yfs.db.ForceUpperCase” system property that is passed to the generator classes in the db-init task should be set to “Y”.
Note: If any data that needs to be case-insensitive exists in the column, you should manually convert all the existing data to upper case before making the column case-insensitive.
Defect ID	161872
Case ID	47938
Description	When a user performs the following sequence of actions, the system does not allow the user to deposit the pallet:
1.	Configures two equipments as locations and points them to separate locations.
2.	Configures the pick task type as Batch Pick and Pick Into Pallet, and the pack constraints as No SCM Required.
3.	Creates an in-progress task with an equipment, and another pick task with the Pick Into Pallet configuration.
4.	Completes the task from the Task Controller and tries to deposit the pallet.
Solution: The system has been enhanced to pass the equipment ID along with the user ID and node.
Defect ID	161974
Case ID	Internal
Description	When the bundle items and sourcing rules are configured, the optimization based on the shipment for bundles does not work when the ShipToAddress is passed at the PromiseLine level of findInventory API.
Defect ID	161976
Case ID	47878
Description	When a user uses "Adjust Receipt" to unreceive all the items at the receipt level from a received container, thus effectively unreceiving the entire container, the system does not clear the LPN Pend Move records.
Defect ID	162272
Case ID	Internal
Description	The license for a third-party jar file that is being used to display the Map in the “Fulfillment Network Model” in the Configurator will expire on September 16, 2008. This fix includes the updated license jar file in the product.
Defect ID	162472
Case ID	47937
Description	If a move request for a serial-tracked item that is loose and inside an LPN is created without passing the source location, and when this move request is released, it fails and throws an "Unable to find inventory for serial" exception message. The system gets and identifies the source location, but is unable to process it further.
Solution: The relevant location will be stamped on the move request line.
Defect ID	162507
Case ID	48024
Description	When a user performs the following sequence of actions, the amount gets collected against the voided invoice instead of the respective invoice:
1.	Enables the payment and implements the YFSCollectionCreditCardUE user exit.
2.	Ensures that an order, which has a voided invoice, exists.
3.	Invokes the requestCollection API.
Hot Fix ID	8.0-HF15
Defect ID	156503
Case ID	46640
Description	The optimization of the cost and the number of shipments does not work when the same ShipToAddress is passed at the Promiseline level of the findInventory API for different items. However, the optimization works correctly when the ShipToAddress is passed at the Promise level of the findInventory API.
Defect ID	157868
Case ID	Internal
Description	The Ytimestamp.getYTime() method performs unnecessary initialization of a variable, which in turn affects the performance of the system adversely.
Defect ID	158165
Case ID	Internal
Description	The copyright information in the Java Documentation should display the date range as “1999-2008” instead of “1999-2006”.
Defect ID	158218
Case ID	Internal
Description	If a department is associated with an organization, the Configurator throws an error when a user modifies the department or the organization, and tries to save it.
Defect ID	158906
Case ID	47406
Description	When an asynchronous multithreaded service is configured to read the messages from an MQ queue and invoke the createOrder API for a high volume of records, a few of the create order messages fail and throw a null pointer exception.
Defect ID	158993
Case ID	Internal
Description	The system throws an exception when creating an agent criterion with a trigger interval if another server is created with a specified termination time.
Defect ID	159357
Case ID	Internal
Description	When the task type is configured as Pick to Inventory Container and BatchPick is enabled, and a user completes a BatchPick task that has multiple pick tasks to an inventory container through the Sterling Mobile Application, the system forces the user to scan the inventory container for the next pick task even if the pick task belongs to the same batch.
Defect ID	159603
Case ID	47562
Description	When a user creates an order with a bundle item and invokes the findInventory API or the getPossibleSchedules API for this order, the nodePriority attribute is displayed as blank instead of zero for the bundle parent in the output XML of these APIs. As the nodePriority attribute is a decimal field, XSD validation fails for the output XMLs.
Solution: The system has been enhanced to display the nodePriority attribute for normal items and bundle components as "0.00" instead of a blank field. The bundle parent item will also be set to "0.00" instead of being blank.
Note: If these APIs are already being used in any customizations that deal with bundle items, evaluate the impact of this fix before applying the HF because the bundle parent item will now be displayed as "0.00" instead of a blank field.
Defect ID	159613
Case ID	47560
Description	When a user first invokes the loadInventoryMismatch API and then the syncLoadedInventory API, the data published by the INVENTORY_CHANGE.ON_INV_SYNC_SUCCESS event contains the “<InventoryItem/>” element instead of the “<Item>” element as mentioned in the Java Documentation. Also, the INVENTORY_CHANGE.ON_INV_SYNC_SUCCESS.xsd fails in this scenario.
Solution: The Java Documentation has been enhanced to display the “<InventoryItem>” element. The XSD file will now have the “<InventoryItem/>” element.
Defect ID	159619
Case ID	45620
Description	The ShipNodes list should be exposed as a criteria parameter for the Inventory Monitor agent.
Solution: The ShipNodes parameter has been added to the agent criteria template. The user should enter comma-separated shipNode values. The AllowedOverriddenCriteria parameter has also been added to the agent criteria template. The default value of this parameter is " " (blank). It should be set to "Y" in the agent criteria for the trigger agent to override the criteria attributes.
Defect ID	160007
Case ID	Internal
Description	When a user performs the following sequence of actions, the system updates the status date of the YFS_ORDER_RELEASE_STATUS record even if there is no change in the status quantity for the order:
1.	Configures “Receiving Preference” with over receipt percentage.
2.	Creates a return order and moves the order to Release status.
3.	Creates a receipt for the return order.
4.	Receives all the items by invoking the receiveOrder API. 
5.	Unreceives all the items by invoking the unreceiveOrder API.
6.	Invokes the receiveOrder API again to receive more quantity than is available in the order.
Defect ID	160300
Case ID	Internal
Description	The scheduleOrderLines API does not schedule the lines that have the same PrimeLineNo and SubLineNo but different extended statuses or when using partial quantity.
Defect ID	160406
Case ID	47697
Description	The JMS component in the Service Definition Framework throws a security exception when the queue is secured at the application server level.
Solution: The following properties have been exposed in the yfs.properties file to address this issue. They should match the user name and password that have been set for the queue.
•	sci.queuebasedsecurity.userid =<USER_ID> 
•	sci.queuebasedsecurity.password = <PASSWORD>
Note: This enhancement is applicable only for the IBM WebSphere Application Server.
Defect ID	160621
Case ID	47731
Description	When a user performs the following sequence of actions, the system displays all the condition properties in the “Condition Details” pop-up window, including the properties that do not belong to this condition:
1.	Creates a dynamic condition, enters a class name and a property name-value.
2.	Creates a HoldType with the following condition: “Only for orders satisfying the condition”.
3.	In the condition definition selects dynamic condition, and enters class name, condition ID, name, and group.
4.	Ensures that the properties are not entered.
5.	Opens the HoldType and clicks the “Condition Details” button.
Defect ID	160624
Case ID	47734
Description	In the Sterling Mobile Application, when a user is manually assigned several tasks through the Task Console, these tasks get unassigned when the user logs out of the application.
Defect ID	160646
Case ID	45620
Description	The Sterling Multi-Channel Fulfillment Solution Platform Configuration Guide and the Sterling Global Inventory Visibility Configuration Guide should be updated with information about the AllowedOverriddenCriteria parameter and the ShipNode parameter.
The Sterling Multi-Channel Fulfillment Solution Installation Guide should be updated with information about overriding the agent criteria attributes in the Inventory Monitor.
Solution: The Sterling Multi-Channel Fulfillment Solution documentation has been updated as follows:
•	Information about the AllowedOverriddenCriteria parameter and the ShipNodes parameter, including descriptions, have been added in Table A-249, Inventory Monitor Criteria Parameters, in Section A.5.3, "Inventory Monitor", of Appendix A, "Time-Triggered Transaction Reference" in the Sterling Multi-Channel Fulfillment Solution Platform Configuration Guide and the Sterling Global Inventory Visibility Configuration Guide.
•	Information about overriding the agent criteria attributes in the Inventory Monitor in Trigger Agent has been added in Section 14.4, "Runtime Utilities", Chapter 14, "Configuring Utilities", of the Sterling Multi-Channel Fulfillment Solution Installation Guide.
The updated documents are released with this hot fix.
Defect ID	160879
Case ID	47757
Description	When the ReCalculateLineTaxUE user exit is implemented and the ShipToAddress is added to an order line, the system does not invoke the ReCalculateLineTaxUE user exit.
Defect ID	161323
Case ID	47808
Description	When a user performs the following sequence of actions, the authorized amount on an order does not become zero:
1.	Enables payment processing and implements the YFSCollectionCreditCardUE user exit.
2.	Suspends the payment method.
Hot Fix ID	8.0-HF14
Defect ID	156384
Case ID	Internal
Description	The LocalizedStringReconciler Tool should replace the variables before loading to the database. Also, the string length checker should replace the variable before validation.
Defect ID	156629
Case ID	Internal
Description	When the system is configured to purge the transfer order after the sales order is released, and if a user invokes the changeOrderStatus API to change the status of a sales order to an extended status of the Released status, the system throws a “YFS 10009: Invalid line” error message.
Defect ID	157924
Case ID	45283
Description	The getItemStatusRulesList API and the manageItemStatusRules API should be exposed.
Defect ID	158082
Case ID	Internal
Description	The display text for the radio buttons and check boxes can be DBlocalised. This additional feature is provided by the following two new methods;
•	YRCButtonBindingData, isDBLocalised()
•	setDBLocalised(boolean isDBLocalised)
Note: This fix is only for buttons that have source binding, that is, only for radio buttons and check boxes. The text on simple buttons cannot be DBLocalised.
Defect ID	158202
Case ID	Internal
Description	When a user performs the following sequence of actions, the hold type does not prevent ADD_Line modification:
1.	Create a hold type that prevents ADD_LINE modification.
2.	Ensures that an order is in “Held” status.
3.	Invokes the changeOrder API to add a line to an order that is in the Draft Order status.
Defect ID	158225
Case ID	47370
Description	When a user performs the following sequence of actions, the system does not return any availability for the corresponding bundle item and component even if sufficient inventory is available for the component:
1.	Selects the “DeliverTogether” option for the bundle parent item. 
2.	Ensures that only one component exists for the bundle Item.
3.	Invokes the findInventory API.
Defect ID	158313
Case ID	47227
Description	Adding the server.properties file in the JVM arguments in the IBM WebSphere application server causes the server to become unresponsive.
Defect ID	158725
Case ID	47415
Description	When a user performs the following sequence of actions, the system throws a "YDM00046: Shipment is completely planned" error message:
1.	Selects the “Remove Shortage Quantities from Wave” in the Wave Release Schedule.
2.	Creates a shipment such that the inventory required to fulfill this shipment is unavailable at the pick location.
3.	Adds the shipment that was created in step 2 to a load, includes it in a wave, and releases the wave. (The system creates a new shipment for the shortage quantity).
4.	Tries to add the new shipment created by the system in step 3 to the load that contains the original shipment.
Defect ID	158905
Case ID	47436
Description	The system allows a user to pick inventory using the Sterling Mobile application even if sufficient inventory is unavailable at the source location of the task being executed.
Defect ID	158947
Case ID	47429
Description	When a user navigates to Configurator > Item Details > Extended Attribute pop-up window, and provides a classification value to the extended attributes by clicking the “Search” icon in the “Extended Attributes” pop-up window, the system does not store this classification value in the database.
Defect ID	159216
Case ID	47506
Description	If the system is configured as follows, the system does not populate the order information in the output XML of the INVENTORY_VALUE_CHANGE event when receiving inventory:
•	The “Maintain Inventory Cost” flag in Node configuration is selected.
•	The “Inventory Costing Required” flag with Costing Method as “Average Cost” in the Global Inventory Visibility > Other Rules screen is selected.
•	The INVENTORY_VALUE_CHANGE event of the INVENTORY_COST_CHANGE transaction is enabled.
Defect ID	159333
Case ID	47147
Description	The system needs to be enhanced to invoke an ON_SUCCESS event when a shipment that has been included in a wave is removed from that wave.
Solution: An ON_SUCCESS event has been added to the REMOVE_SHIPMENT_FROM_WAVE transaction. This event will be invoked when a user removes a shipment from wave through the Sterling Application Console.
Defect ID	160000
Case ID	47593
Description	The system throws a null pointer exception when a user creates a monitoring rule for order fulfillment.
Defect ID	160080
Case ID	Internal
Description	The Sterling Customer Order Management Add-In package that is shipped with the Sterling Multi-Channel Fulfillment Solution needs to be updated with the add-in changes performed in Sterling Customer Order Management PCA7.5 for recertification.
Hot Fix ID	8.0-HF13
Defect ID	150525
Case ID	Internal
Description	The maximumRecords attribute does not work when it is passed at the root level in the getExceptionListForUser API input XML file.
Defect ID	152144
Case ID	Internal
Description	When a date is selected from an editable cell in the Configurator, the system throws a null pointer exception.
Defect ID	153377
Case ID	Internal
Description	The Sterling Multi-Channel Fulfillment Solution does not differentiate between the various data types when the query structure is complex, and throws an “Invalid Date Format” exception message.
Defect ID	154495, 158108, 158136
Case ID	Internal, 47346, 47346
Description	In the IBM WebSphere environment, CORBA connections do not get released, and their numbers increase constantly, leading to the leakage of JMS connections across the system.
Defect ID	154830
Case ID	Internal
Description	When a currency symbol is displayed in any RCP PCA screen, the system throws a null pointer exception if the “Currency” attribute and “CurrencyKey” attribute are not the same.
Defect ID	155823, 157061
Case ID	Internal, Internal
Description	The Sterling Multi-Channel Fulfillment Solution Upgrade Guide should provide information about the SQL command used for populating the add-in version numbers of the migrated PCAs.
Solution: The Sterling Multi-Channel Fulfillment Solution Upgrade Guide has been updated with the required information. A note that describes the SQL command with an example has been added to step 3 in Section 2.9.1 "Before History and Transaction Migration" of Chapter 2 "Upgrading to Release 8.0". The updated document is released with this hot fix.
Defect ID	157510
Case ID	47148
Description	When a user performs the following sequence of actions, the SPLIT_SHIPMENT transaction and the related event are not available for the Transfer Order Shipment Wave release:
1.	Enables the SPLIT_SHIPMENT transaction event from the process modeling of the transfer order, and configures the “Splitting from Wave Release Schedule” screen.
2.	Releases a wave for the transfer order shipment containing ten quantities of an item when the forward pick location has only five quantities of this item.
Defect ID	157552
Case ID	Internal
Description	The Sterling Multi-Channel Fulfillment Solution Upgrade Guide needs to be updated with a note about adding the .jar files before upgrading to the Sterling Multi-Channel Fulfillment Solution, Release 8.0 from the Sterling Call Center and Store, Release 7.4 that is installed on the Sterling Supply Chain Applications, Release 7.9.
Solution: The Sterling Multi-Channel Fulfillment Solution Upgrade Guide has been updated with the required information. A note that describes the .jar files that need to be copied has been added at the end of step 3 in Section 2.9.1 "Before History and Transaction Migration" in Chapter 2 "Upgrading to Release 8.0". The updated document is released with this hot fix.
Defect ID	157594
Case ID	47102
Description	The system allows a user to pick multiple batches continuously when performing the batch pick tasks belonging to two different batches using the Sterling Supply Chain Mobile Application, with the PLA set to honor the batch pick.
Solution: The user has the permission to deposit the inventory when a single batch is completely picked.
Note: This has been fixed for Pack planning when “SCM not required”. The batch pick task type should have the maximum number of users as one.
Defect ID	157602, 157860
Case ID	47189, 47189
Description	The system is unable to read the override files present in the “repository/xapi/template/merged/mobilescreens/override” directory.
Defect ID	157643
Case ID	47242
Description	The system throws an “Invalid Line” error message when a user tries to unreceive a container from the “Receipt” screen with the Average Costing feature enabled for the enterprise. This occurs because the system passes the Receipt Line List and the Receipt Line Object as null when entering the audit element for reducing the location inventory.
The user configures the system as follows to enable the Average Costing feature:
1.	Navigates to Applications > Global Inventory Visibility > Inventory Rules > Others tab.
2.	Selects the Inventory Costing Required radio button and the Average Cost radio button from the Costing Method.
3.	Navigates to “Inventory Types and Considerations” screen and selects the Costing Required flag for the HELD and ONHAND supply types.
4.	From the Participant Modeling screen where Inventory is received, navigates to the Receiving Node screen, and clicks the Details hyperlink in this screen.
5.	Selects the Maintain Inventory Cost flag in the Node Attributes tab.
Defect ID	157848
Case ID	47249
Description	When a move request is released with the target location and the source LPN having matching dimensions, but in different units, the system incorrectly converts the item dimension and fails to put away the item to the target location.
Solution: The system has been enhanced to use the Yantra comparator instead of the Java comparator.
Hot Fix ID	8.0-HF12
Defect ID	149018
Case ID	46719
Description	When two seller organizations have the same inventory organization, and the cancelReservation API is invoked to allow the second seller organization to consume the reservation created by the first seller organization, the demand picture of the item becomes incorrect.
Defect ID	153399
Case ID	Internal
Description	When a user repetitively refreshes the "View my Alerts and Queues" screen through which the getAlertStatisticsForUser API is invoked, the system throws an "ORA-01000: maximum open cursors exceeded" exception message.
Defect ID	154976
Case ID	Internal
Description	The search labels should be left aligned in the search screens where the search panels are aligned vertically.
Defect ID	155174
Case ID	45455
Description	When an order is awaiting inventory, authorizations can expire and trigger multiple reauthorizations that lock up the customer’s credit line and cause expense to the seller. 
Solution: To reduce the cost of these transactions, two configurable payment rules have been provided. These rules offer the following delayed reauthorization options:
•	Delay in Reauthorization: Delays reauthorization after the initial authorization is been created. When the initial authorization expires, no reauthorizations occur until a configured number of hours before the release date.
•	Schedule without Authorization: Prevents initial authorization and waits until a configured number of hours before the release date to perform an authorization.
Defect ID	155211
Case ID	Internal
Description	When a user includes a shipment in a load and invokes the changeShipment API to change the shipment attributes in a single transaction boundary, the changeShipment API throws a "Cannot modify Ship To Address if shipment belongs to a load" exception.
Defect ID	155614
Case ID	46668
Description	The executePaymentTransaction API should be enhanced to be able to authorize payment methods in any order for the requested amount.
Solution: The enhancement for the executePaymentTransaction API has been documented in Section 11.8.1 “Payment -Related APIs” of Chapter 11 “Payment Systems” in the Sterling Multi-Channel Fulfillment Solution Product Concepts Guide.
Defect ID	155915, 157583
Case ID	44771
Description	The Synchronous JMS component should have the ability to correlate the request and response messages using JMSCorrelationID.
Defect ID	157040
Case ID	47002
Description	When a user performs the following sequence of actions, the system throws a "YCP0178 No printer is configured to print the specified document." error message:
1.	Activates the out-of-the-box ON_SUCCESS event of the printWave transaction.
2.	Creates two ship nodes and configures Printing for only one of these ship nodes.
3.	Assigns two waves that are in “Batched” status and have the same wave number, one each to the two ship nodes.
4.	Triggers the printWave agent for the ship node that has the Printing configured.
Defect ID	157078
Case ID	47019
Description	The system behavior needs to be enhanced to allow a user to perform partial pick if any replenishment task type has been configured for a node to release tasks based on the "Target Location Capacity".
Defect ID	157215
Case ID	47020
Description	The replenishment tasks do not honor the “round up to pallet” flag that is configured in the replenishment strategy if an alternate UOM has not been configured for the item being replenished.
Defect ID	157249, 157585
Case ID	47058
Description	If an asynchronous service is configured to read the messages from the message queue and invoke the scheduleOrderLines API, a null pointer exception is thrown in the integration server log when the service starts to process the initial messages form the queue.
Hot Fix ID	8.0-HF11
Defect ID	99926
Case ID	Internal
Description	When a user performs the following sequence of actions, the system throws a “YFS: Order cannot be modified in current status” error message:
1.	Configures a standalone provided service.
2.	Configures the Modification Rules setup to allow the cancellation of the sales order at the header level.
3.	Creates a sales order with the standalone provided service that was configured in step 1.
4.	Creates a work order for the standalone provided service that was configured in step 1.
5.	Creates an appointment and confirms the sales order.
6.	Tries to cancel the sales order at the header level.
Defect ID	99962
Case ID	45657
Description	The Sterling Multi-Channel Fulfillment Solution Customization Guide needs to be corrected for a missing hyphen in the argument list.
Solution: The Sterling Multi-Channel Fulfillment Solution Customization Guide has been updated with the necessary rectifications. The updated document is released with this hot fix.
Defect ID	100680
Case ID	Internal
Description	When the changeShipment API is invoked with the “BackorderRemovedQuantity” flag set to “Y”, and the quantity of the bundle shipment lines is set to zero, the changeShipment API does not back order the order lines for the bundled components.
Defect ID	100846
Case ID	Internal
Description	The system displays “cache refresh” messages even if the cache is disabled for a given table.
Defect ID	100872
Case ID	Internal
Description	If the console mode is either MIXED or ALL, each module should be enhanced to enable a user to specify the alignment of the panels in the search screens, as either vertical or horizontal, through a separate parameter.
Defect ID	101374
Case ID	Internal
Description	When the application is configured as follows, and the changeOrder API is invoked to add a new line to a sales order, the system throws an “Order cannot be modified in current status” error message even if the sales order is not in “Cancelled” status:
•	A sales order exists with two product lines, and one of the product lines is in “Cancelled” status.
•	The modification rules are configured to allow the addition of lines to an order that is in the “Created” status, and disallow the addition of lines to an order in “Cancelled” status.
Defect ID	101395
Case ID	Internal
Description	When the findInventory API is invoked for requesting items in large quantities, for example, if the requested quantity is 999999999, the findInventory API does not return any available choices even if partial inventory is available.
Defect ID	101763
Case ID	Internal
Description	The Sterling Multi-Channel Fulfillment Solution Localization Guide should provide information about IMPORTTEST functionality of the LocalizedStringReconciler Tool.
Solution: The Sterling Multi-Channel Fulfillment Solution Localization Guide has been updated with the necessary rectifications. The updated document is released with this hot fix.
Defect ID	101784
Case ID	Internal
Description	The Sterling Multi-Channel Fulfillment Solution Localization Guide should be updated with information about providing factory setup currency for each released Language Pack.
Solution: The Sterling Multi-Channel Fulfillment Solution Localization Guide has been updated with the necessary rectifications. The updated document is released with this hot fix.
Defect ID	102065
Case ID	Internal
Description	The Sterling Selling and Fulfillment Suite Integration Guide needs to be updated with more information about potential order integration issues.
Solution: The Sterling Selling and Fulfillment Suite Integration Guide has been updated with the necessary rectifications. The updated document is released with this hot fix.
Defect ID	102077
Case ID	Internal
Description	If one or more PCAs are installed on the Sterling Multi-Channel Fulfillment Solution, the yfc-cognos-package parameter and the yfc-cognos-folder parameter have duplicate values in the web.xml file.
Defect ID	102236
Case ID	Internal
Description	The Sterling Multi-Channel Fulfillment Solution Glossary needs to be updated with the new terms that have been introduced in Sterling Call Center and Store.
Solution: The Sterling Multi-Channel Fulfillment Solution Glossary has been updated with the new terms. The updated document is released with this hot fix.
Defect ID	102363
Case ID	Internal
Description	When the number of dock appointments for a particular consumption date increases, the response time for the manageDockAppointments API increases correspondingly.
Solution: The performance of the manageDockAppointments API has been improved for the described scenario.
Defect ID	102558
Case ID	Internal
Description	When a user deletes a dock that has appointments, the related appointments are not deleted. If the user creates an appointment for a date that is the same as the appointments pertaining to the deleted dock, the system throws an “INV71_6: INV: Invalid service resource” error message.
Solution: The application has been modified to query the database for the deleted service resource with a combination of Res_Pool_Key and Ser_Res_ID. This overrides the error and allows the query to call the database. If the query does not find a record in the YFS_SERVICE_RESOURCE table, the appointment is not added to the resultMap.
Defect ID	102629
Case ID	Internal
Description	When a user performs the following sequence of actions, the agentServer throws an “YFS: Invalid Charge category” error message:
1.	Creates a new Charge Category and configures the PUBLISH_SHIP_ADVICE event of the sendRelease transaction to publish data.
2.	Creates an order that has charges as configured in step 1.
3.	Schedules and releases the order.
4.	Runs the sendRelease agent.
Defect ID	103176
Case ID	Internal
Description	The Sterling Multi-Channel Fulfillment Solution Upgrade Guide needs to be updated to contain information about localizing the new factory setup after the customer upgrades from a localized Sterling Multi-Channel Fulfillment Solution release.
Solution: The Sterling Multi-Channel Fulfillment Solution Upgrade Guide has been updated with the necessary rectifications. The updated document is released with this hot fix.
Defect ID	103177
Case ID	Internal
Description	The Sterling Multi-Channel Fulfillment Solution Installation Guide needs to be corrected for formatting properties.
Solution: The Sterling Multi-Channel Fulfillment Solution Installation Guide has been updated with the necessary rectifications. The updated document is released with this hot fix.
Defect ID	103200
Case ID	46816
Description	When a user performs the following sequence of actions, the system calls the putAuditElement() method with “null” value for the order line and the audit element for the inventory adjustment is not being populated with the Order Line Key. Therefore the DB query to get the same fails:
1.	Enables unit costing.
2.	Enters order line level cost.
3.	Unreceives an order after receiving LPN inventory through a purchase order. (The system throws an “Invalid Line” error message.)
Defect ID	103249
Case ID	46820
Description	If the Platform module in the Configurator is loaded for an organization which is administrated by the Default enterprise, the system does not allow the user to close the service that contains conditions.
Defect ID	103252
Case ID	46676
Description	The Sterling Multi-Channel Fulfillment Solution Customization Guide should provide an example about extending an event or xsl template. Also, information about the path to be given in the Service Definition Framework needs to be provided.
Solution: The Sterling Multi-Channel Fulfillment Solution Customization Guide has been updated with the requested examples. The updated document is released with this hot fix.
Defect ID	103264, 103491
Case ID	46756, Internal
Description	When the classification hierarchy for the extended attributes is defined, and a user performs the following sequence of actions, the system does not display the “Search” icon in the “Extended Attribute” pop-up window:
1.	Creates an extended attribute of an item.
2.	Navigates to Product Management > Products > Items > Item Details.
3.	Clicks the “Extended Attributes” button that is displayed at the top of the “Item Details” screen.
Defect ID	103266
Case ID	Internal
Description	When an entire release line that has a sales order in “Released” status is cancelled using the changeRelease API, the audits are not being logged.
Defect ID	103575
Case ID	46863
Description	If a user exit can be overridden for a document type but not for an enterprise, and this user exit has an implementation for one document type, the system invokes this implementation for all the document types.
Defect ID	103636
Case ID	46948
Description	When a user performs the following sequence of actions, the changedQuantity attribute in the XML published for the INVENTORY_CHANGE.ON_INV_SYNC_SUCCESS and the INVENTORY_CHANGE.ON_INV_MISMATCH events has both positive and negative values, which do not conform to the changedQuantity datatype in INVENTORY_CHANGE.ON_INV_SYNC_SUCCESS.xsd and INVENTORY_CHANGE.ON_INV_MISMATCH.xsd:
1.	Configures the INVENTORY_CHANGE.ON_INV_SYNC_SUCCESS and INVENTORY_CHANGE.ON_INV_MISMATCH events.
2.	Invokes the syncLoadedInventory API.
Hot Fix ID	8.0-HF10
Defect ID	100909
Case ID	Internal
Description	In the Sterling Multi-Channel Fulfillment Solution Customization Guide, Release 8.0, and Sterling Multi-Channel Fulfillment Solution Installation Guide, Release 8.0, the information about how to make selective SSL calls only for certain commands or sensitive APIs should be removed.
Solution: The Sterling Multi-Channel Fulfillment Solution Customization Guide, Release 8.0, and Sterling Multi-Channel Fulfillment Solution Installation Guide, Release 8.0, has been updated with the necessary rectifications. The updated documents are released with this hot fix.
Defect ID	100965
Case ID	45402
Description	The system should provide the ability to override the default wsdl style of rpc for webservices on the Websphere application server.
Solution: The buildEAR scripts have been enhanced to take a new “-Dwebsphere-java2wsdl-style” parameter with the use of which the user can override the default of rpc style. The valid values for the parameter will be rpc and document. Also, for style value rpc, the -use value will be set to encoded, and for style value of document, the -use value will be set to literal.
Defect ID	101471
Case ID	Internal
Description	The Sterling Multi-Channel Fulfillment Solution Installation Guide, Release 8.0 should be updated with the information about localizing the new factory setup after upgrading the Sterling Multi-Channel Fulfillment Solution.
Solution: The Sterling Multi-Channel Fulfillment Solution Installation Guide, Release 8.0 has been updated with the necessary rectifications. The updated documents are released with this hot fix.
Defect ID	101919
Case ID	Internal
Description	The Sterling Multi-Channel Fulfillment Solution Installation Guide, Release 8.0, should be updated with information about the multi-byte character support flag.
Solution: The Sterling Multi-Channel Fulfillment Solution Installation Guide, Release 8.0, has been updated with the necessary rectifications. The updated document is released with this hot fix.
Defect ID	102337
Case ID	45906
Description	When the INVENTORY_CHANGE.ON_INV_SYNC_SUCCESS event is invoked, the XML published by the event does not conform to the INVENTORY_CHANGE.ON_INV_SYNC_SUCCESS.xsd.
Defect ID	102699
Case ID	46669
Description	The EmptyAssignmentReason attribute of the YFS_getPossibleSchedules_output.xsd has an insufficient maximum length of Text-40. Because of this, this XSD does not conform to the output XML of the getPossibleSchedules API when the value obtained in the EmptyAssignmentReason attribute exceeds 40 characters length.
Solution: The EmptyAssignmentReason attribute’s maximum length has been changed to Text-100.
Defect ID	102736
Case ID	46179
Description	When the following configurations are true and a purchase order arrives at NodeA after 10 days, then on invoking the findInventory API for the item, the unplanned inventory is used for the item. The incoming purchase order is not considered even though the second sequence in sourcing rules is set to Use All Inventory:
1.	Create a sourcing rule that has two sequences. Both the sequences use a distribution group that has one common node.
2.	The first sequence has a distribution group that has one node, for example, NodeA, and the Use Future Inventory is set to 5 days for this sequence.
3.	The second sequence has a distribution group has two nodes, for example, NodeA and NodeB, and has Use All Inventory checked.
4.	Lead Days for the item is configured to a number greater than 5 days in the “Item Details” screen.
Defect ID	102762
Case ID	46584
Description	When a user creates an order with order line reservation, the product availability date of this order line reservation should use the existing reservation that has the reservation date as some future date. However, the product availability date is using the system date, which is incorrect.
Defect ID	102818
Case ID	46718
Description	When the YFSConfirmAssignmentsUE is implemented and a user invokes the scheduleOrderLines API, the system throws a “Null Pointer” exception.
Defect ID	102902
Case ID	46709
Description	When the “Outbound Batch Pick” task is configured to “Dispatch tasks only after manual release”, and a user performs the following sequence of actions, the system throws an “YCP0145: Unable to include Task in the Batch” error message:
1.	Creates a shipment, adds it in a wave, assign lanes for the wave, and releases the wave. The system creates the “Batch Pick” task having the above configuration.
2.	Tries to create a batch by invoking the createBatch API.
Defect ID	96043
Case ID	Internal
Description	When a user performs the following sequence of actions, the system throws an “Order cannot be modified in current status” error message:
1.	 Creates a sales order with two lines. Schedules and releases both the lines.
2.	Invokes the changeOrder API to cancel the first line and the changeRelease API to change the second line at the same time.
However, when these API’s are invokes separately, modifications are done successfully. Cancellations and backordering should also happen in a multiAPI call.
Defect ID	98040
Case ID	Internal
Description	When a user invokes the getRoutingGuideList API by passing the output template that contains the ScacAndService child element for each of the RoutingGuideDetailCarrier elements, the system returns the duplicate ScacAndService child elements for each of these RoutingGuideDetailCarrier elements.
Defect ID	99005
Case ID	Internal
Description	The Sterling Multi-Channel Fulfillment Solution Installation Guide, Release 8.0, should be updated with information about installing and using the Language Pack.
Solution: The Sterling Multi-Channel Fulfillment Solution Installation Guide, Release 8.0, has been updated with the necessary rectifications. The updated documents are released with this hot fix.
Hot Fix ID	8.0-HF9
Defect ID	99006
Case ID	Internal
Description	In Section 2.3, “Database Overview”, of the Sterling Multi-Channel Fulfillment Solution Localization Guide, Release 8.0, step 2 under “String Length Checker” contains incorrect directory name and entities.
Solution: The Sterling Multi-Channel Fulfillment Solution Localization Guide, Release 8.0 has been updated with the necessary rectifications. The updated document is released with this hot fix.
Defect ID	99007
Case ID	Internal
Description	In Section 2.3, “Database Overview”, of the Sterling Multi-Channel Fulfillment Solution Localization Guide, Release 8.0, step 6 under “String Length Checker” contains an incorrect prefix.
Solution: The Sterling Multi-Channel Fulfillment Solution Localization Guide, Release 8.0 has been updated with the necessary rectifications. The updated document is released with this hot fix.
Defect ID	99143
Case ID	Internal
Description	When a user performs the following sequence of actions, the system throws a null pointer exception:
1.	Creates a transfer order shipment without the ship node information on the shipment. 
2.	Logs in to the Sterling Application Console and views transfer order shipment though the Outbound Shipment Console.
Defect ID	99299
Case ID	Internal
Description	The reopen task agent does not honor the "Number of records to buffer" parameter configured in the “Criteria parameters" of this agent.
Defect ID	99829
Case ID	Internal
Description	In Section 2.4.1, “Localization for a Multi-Language Installation”, of the Sterling Multi-Channel Fulfillment Solution Localization Guide, Release 8.0, step 3 contains an incorrect word.
Solution: The Sterling Multi-Channel Fulfillment Solution Localization Guide, Release 8.0 has been updated with the necessary rectifications. The updated document is released with this hot fix.
Defect ID	99830
Case ID	Internal
Description	The Sterling Multi-Channel Fulfillment Solution Localization Guide, Release 8.0 should be updated with information about converting the translations to the escaped Unicode format.
Solution: The Sterling Multi-Channel Fulfillment Solution Localization Guide, Release 8.0 has been updated with the necessary rectifications. The updated document is released with this hot fix.
Defect ID	99843
Case ID	Internal
Description	An extension point, YCP_BEFORE_GET_NODELIST_EP, for handling the input to the getShipNodeList API needs to be exposed.
Defect ID	100645
Case ID	Internal
Description	The “Create Batch” button in the Task Console does not work on a Mozilla Firefox browser.
Defect ID	101055
Case ID	Internal
Description	When a user performs the following sequence of actions, the event configured for the sales order is triggered:
1.	Configures the DELETE_ORDER event of the ORDER_CHANGE transaction for a sales order.
2.	Invokes the deleteOrder API to delete a return order.
Defect ID	101062
Case ID	Internal
Description	The DELETE_ORDER event needs to be added in the ReturnOrder, TransferOrder and the PurchaseOrder process types.
Defect ID	101072
Case ID	Internal
Description	When the return order is cancelled and a user tries to change the price at the return line level, the system throws the following exception:
“You cannot change the price of an order after invoicing is complete”
Defect ID	101768
Case ID	Internal
Description	The Sterling Selling and Fulfillment Suite Integration Guide, Release 8.0, does not contain information about the unavailability of Absolute Shipping Discounts in the integrated mode in the Sterling Multi-Channel Selling Solution.
Solution: The Selling and Fulfillment Suite Integration Guide, Release 8.0 has been updated with the necessary rectifications. The updated document is released with this hot fix.
Known Issue: The absolute shipping discounts can cause discounts equal to or more than the total shipping charges in Sterling Call Center and Store. In Sterling Call Center and Store, all the possible shipping discounts that qualify for an order are applied to the order. If shipping discounts are more than the shipping charges, the remaining discounts will be applied to the order sub-total. This can occur only when the shipping discount is an absolute discount. Therefore, using absolute shipping discounts in integrated mode is not recommended.
Defect ID	101772, 102409, 102458
Case ID	Internal
Descriptions	When the True and False links of a condition component are localized, the following screens throw an "All conditions must have a true and false outgoing link" error message when saving:
•	Pipeline
•	Hub UI
•	Event Handler
•	Monitor
Defect ID	101885
Case ID	46175
Description	When the RecalculateLineTaxUE user exit is configured to add taxes to the order line and the createShipmentInvoice API is invoked, the invoice is generated with the correct amount that also includes the new taxes added by the RecalculateLineTaxUE user exit, but the order is not updated with the new taxes added to the lines.
Defect ID	102012
Case ID	44225
Description	When a user tries to create a load that has the same stop node occurring more than once with different sequence numbers during the execution cycle of the load, the system throws a “YFC0001: Record already exists in the database” error message.
Defect ID	102046
Case ID	Internal
Description	Multiple currencies per storefront or enterprise are not supported in the integrated mode. Currency determination is different between the Sterling Multi-Channel Selling Solution and the Sterling Call Center and Store applications when multiple currencies are available in a given storefront or enterprise. Until the differences are resolved, it is recommended that one currency per storefront or enterprise in the integrated mode be used.
Defect ID	102210
Case ID	Internal
Description	The Sterling Selling and Fulfillment Suite Integration Guide, Release 8.0, does not contain information about the potential field length mismatch with Product Synchronization, User Synchronization, and Order Integration when integrating the Sterling Multi-Channel Selling Solution and the Sterling Multi-Channel Fulfillment Solution.
Solution: The Selling and Fulfillment Suite Integration Guide, Release 8.0 has been updated with the necessary rectifications. The updated document is released with this hot fix.
Defect ID	102228
Case ID	46123
Description	When the system is configured as follows and the findInventory API is invoked to request availability for an item for which the first distribution service group (DSG) is unable to fulfill the entire requested amount, the output displays availability from the unplanned inventory even if the requested quantity can be fulfilled by the remaining DSGs:
10.	Multiple distribution groups are added to the sourcing rules.
11.	Each DSG has a collection of ship nodes.
12.	The “Use Unplanned Inventory” option is selected for the item.
Defect ID	102238
Case ID	Internal
Description	The Sterling Selling and Fulfillment Suite Integration Guide, Release 8.0 should be updated to provide information about customer segmentation for the new customers created in Sterling Call Center and Store.
Solution: The Sterling Selling and Fulfillment Suite Integration Guide, Release 8.0 has been updated with the necessary rectifications. The updated document is released with this hot fix.
Defect ID	102242
Case ID	Internal
Description	The Sterling Selling and Fulfillment Suite Integration Guide, Release 8.0 should be updated for the following inaccuracy in Table 1-1, “Integration Points in the Sterling Selling and Fulfillment Suite” of Chapter 1, “Integration Overview”: "Order changes occurring in the Sterling Multi-Channel Selling Solution are communicated to the Sterling Multi-Channel Fulfillment Solution."
Solution: The Sterling Selling and Fulfillment Suite Integration Guide, Release 8.0 has been updated with the necessary rectifications. The updated document is released with this hot fix.
Defect ID	102289
Case ID	Internal
Description	Audits are created when records are inserted into the YFS_LOCALIZED_STRINGS and YFS_NONLOCALIZED_STRINGS by running the localizedstringreconciler.xml file in Import and Switch mode respectively.
Defect ID	102423
Case ID	46387
Description	When the system is configured as follows and the findInventory API is invoked to request the availability options for the item whose supply is maintained externally, the output of the findInventory API returns full availability without considering the demand in the Sterling Multi-Channel Fulfillment Solution:
•	The ship node maintains supply externally and the YFSGetExternalSupplyUE user exit is implemented. 
•	Demand exists in the Sterling Multi-Channel Fulfillment Solution for the item that receives information from the implemented user exit.
Hot Fix ID	8.0-HF8
Defect ID	95026
Case ID	43948
Description	The system should be enhanced to enable a user to extend the YFS_PERSON_INFO table.
Defect ID	100414
Case ID	Internal
Description	When invoking the getUserlist API with the DSG/team configured for a user, the system should not list the users who have been configured to be inaccessible in the DSG/team definition. Also, the system should list all the users matching the input criteria when no DSG/team is configured.
Defect ID	101347
Case ID	45341
Description	When a user performs the following sequence of actions, the system creates an invoice with the full amount for the bundle even though the components are not completely shipped:
1.	Navigates to Sterling Distributed Order Management > DocumentSpecific > SalesOrder > Financials > FinancialAttributes > Others.
2.	Ensures that the “Create Shipment Invoice For Bundle Parent on invoicing Of All Bundle Components” option is selected.
3.	Ships the bundle components in multiple shipments, with one bundle component completely shipped and the other component partially shipped.
4.	Invokes the createShipmentInvoice API.
Defect ID	101502
Case ID	46056
Description	The system should be enhanced to support the definition of column names in lower case in the entity extensions.
Defect ID	101735
Case ID	46070
Description	When a user performs the following sequence of actions, the system creates a task for only one item instead of the entire pallet:
1.	Configures an item, for example, Item1, for which the Alternate UOM attribute is not defined. Also, item dimensions are mentioned.
2.	Creates a new Location Size Code with constraint on pallet for one package.
3.	Associates the new Location Size Code created in the previous step to a new empty location, for example, FP02.
4.	Adjusts a pallet with 10 quantities of Item 1 in another location, for example, FP01, which has a separate Location Size Code.
5.	Creates a move request for the pallet configured in the previous step with the source location as FP01. Ensures that the “Target Location” field is blank when creating the move request.
6.	Ensures that the putaway strategy is defined appropriately.
7.	Creates a move task after releasing this.
Defect ID	101751
Case ID	46174
Description	The system is configured for the Item-Based Allocation (IBA) agent. When the inventory picture is not correct for an Item-Node combination before the IBA agent is run, the IBA agent still processes the Item-Node combination, irrespective of the inventory picture. 
Defect ID	101839
Case ID	46267
Description	When a user performs the following sequence of actions, the getItemUOM API unconditionally returns the last element if a matching record is not found:
1.	Creates two zones, for example, Z1 and Z2.
2.	Assigns a location, for example, L2 to the zone Z2, which is dedicated for an item, for example, I1, with the UOM set to EACH.
3.	Assigns a location, for example, L1 to the zone Z1, which has 10 units of item I1 in the pallet P1.
4.	Configures the target zone as Z2 in the putaway preferences. 
5.	Creates a move request with exceptions for P1.
6.	Removes the dedications for the location L2, thus releasing the move request.
Solution: The getItemUOM API has been modified to return only the relevant matching UOM and to return a null value if a matching record is not found.
Defect ID	101996
Case ID	Internal
Description	The Sterling Selling and Fulfillment Suite Integration Guide, Release 8.0 should be updated to provide information about Pricing Integration. Also, a reference to the Sterling Call Center and Store Implementation Guide, Release 8.0 should be provided for the same.
Solution: The Selling and Fulfillment Suite Integration Guide, Release 8.0 has been updated with the necessary rectifications. The updated document is released with this hot fix.
Defect ID	102115
Case ID	46214
Description	When a user invokes the changeOrder API to add another order line with an OrderLineReservations record for an order that already has an order line in Scheduled status, and then invokes the releaseOrder API for that order, the OrderLineReservations record for the new order line gets deleted even though the order line is unscheduled.
Hot Fix ID	8.0-HF7
Defect ID	95851
Case ID	Internal
Description	The Sterling Mobile Application does not display the product version number of the Sterling Multi-Channel Fulfillment Solution.
Defect ID	96236
Case ID	Internal
Description	When the sc.console.mode property is set to “Mixed” or “All”, the report generation screens do not work on the Mozilla Firefox browser.
Defect ID	96357
Case ID	Internal
Description	When the sc.console.mode property is set to “Mixed” or “All”, the Switch View does not work in the search screens.  
Defect ID	97240
Case ID	Internal
Description	When a shipment without a trailer number is created in the Sterling Yard Management System PCA, and a trailer checks in with this shipment number as the reference number, the shipment record in the yfs_shipment table is not getting updated with the trailer number.
Solution: Extension point is provided in the YDMDataFilter file for additional data filters for the Sterling Yard Management System PCA when invoking the getShipmentList API.
Defect ID	97456
Case ID	Internal
Description	When a user performs the following sequence of actions, the screen takes a long time to refresh:
1.	Opens a screen that has a table.
2.	Adds numerous order lines until one page or multiple pages of records are filled.
3.	Ensures that each line has at least one editable field.
4.	Navigates to a focusable field in the table.
5.	Presses the “Enter” key.
Defect ID	97614
Case ID	Internal
Description	When the YFSOrderRepricingUE User Exit is implemented for the changeOrder API, and the changeOrder API is invoked for an order that impacts pricing, the API does not honor the Reset ="Y" flag that is passed from the YFSOrderRepricingUE, and therefore does not reset the order's header charges or line charges.
Defect ID	97701
Case ID	Internal
Description	The Resource Permission Configurator does not list the resources for the Sterling Yard Management System PCA.
Defect ID	97747
Case ID	Internal
Description	The Pallet/Case Putaway takes a long time to create tasks when there are a large number of locations with the same SKU.
Solution: Performance has been improved to create putaway tasks faster. The Recalculate Location Dimensions Agent has been fixed to mark the location as Location Full, based on the Location Capacity Constraints.
Defect ID	97961
Case ID	Internal
Description	When releasing a wave which has a huge number of shipment lines, the shipments were getting loaded for each shipment line causing the system to throw an "out of memory" error. 
Defect ID	97965
Case ID	Internal
Description	The HFInstallation should refer to the INSTALL_DIR environment variable instead of YFS_HOME when referring to the Sterling Supply Chain Application installation directory.
Defect ID	98069
Case ID	Internal
Description	For system definined containerization, the getNodeInventory API is invoked with a wrong template and the system throws a null pointer exception when processing the output.xml file.
Defect ID	99141
Case ID	Internal
Description	When a user performs the following sequence of actions, the system throws a “YFS10131: YFS: Not Enough Quantity” error message:
1.	Creates a return order having two lines from a sales order that has only one line.
2.	Authorizes and releases the return order.
3.	Creates the return shipment and confirms the shipment.
4.	Starts the return receipt for the return shipment and receives the two return lines. Also ensures that the return receipt is not closed.
5.	Uses the multiAPI APIs to perform the following sequence of actions:
a.	unreceiveOrder API – To unreceive the first return line.
b.	receiveOrder API – To receive the first return line again.
c.	unreceiveOrder API – To unreceive the second return line.
d.	receiveOrder API – To receive the second return line again.
e.	closeReceipt API – To close the return receipt.
Defect ID	99202
Case ID	Internal
Description	The generateTruncateTransactionData.xml file generates a truncate table SQL script for the “SI_VERSION” system table.
Defect ID	99595
Case ID	Internal
Description	The number of characters that can be entered by the user in the “Notes Reason” field is limited to 20 by the Configurator, but the database field, for example, ReasonCode in the “Order Details” screen, can hold up to 40 characters.
Defect ID	99643
Case ID	Internal
Description	When closing case or pallet when receiving, the system throws a "com.ibm.db2.jcc.b.sqlException" exception message on DB2.
Defect ID	99783
Case ID	Internal
Description	When a user working for a Networked Warehouse Management System node invokes the manageDockAppointment API with an invalid location ID, the system throws a null pointer error.
Solution: The system now throws an "Invalid node and location ID combination" error message.
Defect ID	99908
Case ID	Internal
Description	When the “Cancel Work Order” modification for work order created status is disabled, and a user cancels an order line that is a part of a work order, the system throws a "OMP11057: Cannot cancel the order line as it belongs to a work order, which cannot be cancelled" error message.
Defect ID	99918
Case ID	Internal
Description	When a user performs the following sequence of actions, the system throws an “YFS: Invalid Order” error message:
1.	Configures the ON_SUCCESS event of CreateDraftOrder to raise an alert.
2.	Creates a draft order. (The system raises an alert.)
3.	Removes the draft order by invoking the ChangeOrder API with Action=”REMOVE”.
4.	Clicks the “Alert” hyperlink in the Alert console.
Note: After the fix is applied, the alert gets closed when the order is removed. To remove the alert completely from the database, trigger the INBOXPRG transaction.
Defect ID	99973
Case ID	Internal
Description	When a user configures the system to “allow stop delivery for orders in shipped status” and “do not allow stop delivery for orders in return created status”, the manageStopDeliveryRequest API, when called to update successfulQty after return is created for the order, throws a "Not Enough Quantity” exception.
Defect ID	100351
Case ID	Internal
Description	When the manageDockAppointment and manageLoad APIs are invoked to update the same Load Stop record, the system may throw an “YFC0009: Update Failed” error message.
Defect ID	100200
Case ID	Internal
Description	In Section 2.5.3.1.2, Create a Synchronous Service for Order Integration of Chapter 2, Configuration, of the Sterling Selling and Fulfillment Suite Integration Guide, Release 8.0, the cross-reference for the Table 2-9 Service Properties is incorrect.
Solution: The Selling and Fulfillment Suite Integration Guide, Release 8.0 has been updated with the necessary rectifications. The updated document is released with this hot fix.
Defect ID	100740
Case ID	Internal
Description	When multiple APIs are invoked and a timeout occurs, the application hangs.
Defect ID	100748
Case ID	Internal
Description	The Sterling Selling and Fulfillment Suite Integration Guide, Release 8.0, should be corrected for the following inaccuracies:
•	In Section 2.5.3.1.2, Create a Synchronous Service for Order Integration of Chapter 2, Configuration, the procedure to configure the newly created synchronous service for order integration incorrectly refers to the JMS component.
•	In Section 4.1.1, Synchronous and Asynchronous Order Creation, order creation in synchronous mode is incorrectly described as directly invoking the createOrder API.
•	In section 4.1.1, Synchronous and Asynchronous Order Creation, the concept information for order creation in synchronous mode is repeated twice.
Solution: The Selling and Fulfillment Suite Integration Guide, Release 8.0 has been updated with the necessary rectifications. The updated document is released with this hot fix.
Defect ID	100863
Case ID	Internal
Description	When building an EAR, the HFInstaller should use buildear.sh/cmd, rather than the buildEAR.xml file.
Defect ID	101211
Case ID	Internal
Description	The copyright date in the “Login” screen needs to be updated to 2008.
Defect ID	101260
Case ID	Internal
Description	The “ProNo” attribute passed in the input to the Sterling Supply Chain Visibility (SCV) application' manageLoadFromEDI API is not being updated in the YFS_LOAD table and YFS_SHIPMENT table.
Solution: A new GenerateProNo flag that is set to "N" will be passed by the SCV application’s manageLoadFromEDI API, which will allow the “ProNo” attribute passed in the input to the SCV’s manageLoadFromEDI API to be updated in the YFS_LOAD table and YFS_SHIPMENT table.
Defect ID	101262
Case ID	46039
Description	When a user simultaneously removes an order line and adds another order line to a return order that is in draft status, the system throws an “Order cannot be modified in current status” error message.
Defect ID	101276
Case ID	45979
Description	When a user enables the Average Costing feature by performing the following steps and completes the following sequence of actions described subsequently, all the five Inventory Audit References are being set as "Reference_1" and are being read as "Reference1" in the Inventory Audit Element:
1.	Navigates to Applications > Global Inventory Visibility > Inventory Rules > OTHERS tab and clicks the “Inventory Costing Required” radio button and the “Average Cost” radio button from the “Costing Method” screen.
2.	Navigates to Inventory Types and Considerations and clicks the “Costing Required” flag for the HELD and ONHAND supply types. 
3.	Navigates to Participant Modeling > Receiving Node Details where the inventory is being received, and clicks the “Maintain Inventory Cost” flag in the “Node Attributes” tab.
Following is the sequence of actions referred to in the first paragraph:
1.	Define PLA to pick the inventory from the Forward Pick Location.
2.	Configure Order Pick.
3.	Create an item.
Solution: The Inventory Audit References are now being set as "Reference1", "Reference2", "Reference3", "Reference4", "Reference5" in the Inventory Audit Element so that the read operation is successful.
Defect ID	101618
Case ID	Internal
Description	A new INVENTORY_EXPIRATION event has been added to the Location Inventory monitor in the Sterling Warehouse Management System. This event will monitor the entire expired inventory in the configured zones, and will invoke a service to create a move request for that inventory.
Defect ID	101903
Case ID	Internal
Description	The Sterling Multi-Channel Fulfillment Solution Upgrade Guide, Release 8.0 should be updated to assist the user when upgrading the Sterling Multi-Channel Fulfillment Solution as part of the PCA upgrade.
Solution: The Sterling Multi-Channel Fulfillment Solution Upgrade Guide, Release 8.0 has been updated. The updated document is released with this hot fix.
Hot Fix ID	8.0-HF6
Defect ID	95025
Case ID	43946
Description	The Sterling Multi-Channel Fulfillment Solution, Release 8.0 does not have the ability to add hang-off tables to the YFS_CUSTOMER_CONTACT table and the YFS_CUSTOMER_ADDNL_ADDR table.
Defect ID	96886
Case ID	Internal
Description	When the getOrderInvoiceList API is invoked from the backend, a Data Security Group filter element is appended to the input of the getOrderInvoiceList API.
Defect ID	97580
Case ID	Internal
Description	When all the following conditions are true and when the monitor processes the order or shipment after the first milestone is met and before the second milestone is reached, and a specific timeframe (for example, 24 hours) has not elapsed since the first milestone is met, the monitor incorrectly raises an alert.
•	The monitor is configured for the "Milestone has not reached after another milestone" rule.
•	The monitor is configured to raise an alert if the second milestone is not reached before a specific timeframe has elapsed since the first milestone is met.
Defect ID	97712
Case ID	Internal
Description	When multiple users simultaneously perform shipment confirmation and packing of different shipments belonging to a single wave, the system encounters a deadlock.
Defect ID	97741	
Case ID	Internal
Description	When a user performs the following sequence of actions when updating the Lock ID, the system throws a “YFC0009 Update Failed" error message:
•	HAS_EXCEPTIONS of CONTAINERIZE_WAVE transaction calls a custom API, which in turn calls the removeShipmentFromWave API, which removes the shipment from the wave.
•	The user invokes the containerizeWave API.
Defect ID	97743
Case ID	Internal
Description	When the system displays the fusion charts in https mode (that is, the application runs on a secure connection), a warning message pops up asking whether the user wants to view secure and non-secure items.
Defect ID	97749
Case ID	Internal
Description	When a user performs the following sequence of actions, the Sterling Mobile Application throws a “DB2 SQL error: SQLCODE" exception:
4.	Configures the user skills for a Data Security Group and sets the aisle constraint for the data security group.
5.	Logs in to RF as a user of the Data Security Group configured in step 1.
6.	Logs in to RF and navigates to the Outbound Picking option.
Defect ID	97781
Case ID	Internal
Description	The Reopen_Task agent should clear the AUTO_USER_CONSTRAINTS records for tasks that are in the “Open” status if the user performing a task for that reference is inactive.
Defect ID	98185
Case ID	Internal
Description	The getReservation API does not fetch the reservations when invoked with a different enterprise in a multi-branded scenario.
Defect ID	98197
Case ID	Internal
Description	When a user schedules a sales order with more than 1000 lines and the scheduled sales order moves to the "Procurement Transfer Order Created "status, the system throws the following Oracle exception:
"ORA-01795: maximum number of expressions in a list is 1000".
Defect ID	99315
Case ID	Internal
Description	All the transactions belonging to the count document type needs to publish the count request status in the event xml files.
Defect ID	99555
Case ID	Internal
Description	The attempt to log in to the Sterling Multi-Channel Fulfillment Solution application fails when the application that is deployed on the IBM WebSphere or JBoss is configured to connect to an Oracle database through a data source configured on the application server.
Defect ID	99611
Case ID	Internal
Description	Issue 1: When all the following conditions are true and when the monitor processes the order or shipment after a specific timeframe (for example, 24 hours) has elapsed since the first milestone is met and then the second milestone has also been met, the monitor incorrectly raises an alert: 
•	The order monitor or the shipment monitor is configured for the "Milestone has not reached after another milestone" rule.
Issue 2: When the following condition is true and when the monitor processes the order or the shipment after the first milestone is met and after a specific timeframe (for example, 24 hours) has elapsed since the first milestone is met and before the second milestone is reached, the monitor raises a new alert as expected. But when the monitor reprocesses the order or shipment after the second milestone is reached, it does not close the alert raised earlier:
•	The order monitor or the shipment monitor is configured for the "Milestone has not reached after another milestone" rule.
•	The monitor is configured for auto-resolve alerts.
Defect ID	99883
Case ID	Internal
Description	The Sterling Multi-Channel Fulfillment Solution Installation Guide, Release 8.0 should be updated to provide information about enabling the HTTP API Tester in the development environment.
Solution: The Sterling Multi-Channel Fulfillment Solution Installation Guide, Release 8.0 has been updated. The updated document is released with this hot fix.
Defect ID	100266
Case ID	Internal
Description	The system throws an update failed error in some scenarios, when the changeOrderStatus API, changeOrder API, and the changeOrderSchedule API are invoked in the same transaction boundary.
Defect ID	100713
Case ID	45917
Description	When the “customerList” screen in the Sterling Multi-Channel Fulfillment Solution Configurator is closed after creating a new customer definition and if the screen is reopened again, the system does not display the recently created records.
Defect ID	100732
Case ID	Internal
Description	When a user performs the following sequence of actions, the system throws an “Invalid Line” error message:
1.	Creates a sales order with a procured transfer order.
2.	Purges the transfer order after it is received and closed.
3.	Cancels the sales order.
Hot Fix ID	8.0-HF5
Defect ID	96108
Case ID	Internal
Description	For bundle component lines that are unavailable, the getFulfillmentOptionsForLines API returns an incorrect value for the “HasUnavailableQuantity” flag.
Defect ID	97703
Case ID	Internal
Description	In the shipment_search_by_status.jsp file, the bindings starting with “xml:/Shipment/ShipmentHoldType/” are incorrect.
Solution: The correct bindings are “xml:/Shipment/ShipmentHoldTypes/ShipmentHoldType” to match the input to the getShipmentList API.
Defect ID	97786
Case ID	Internal
Description	When a sort task user performs the following sequence of actions, the system incorrectly suggests pick task to the sort task user:
1.	Creates outbound shipment of an item, includes it in a wave, and releases the wave.
2.	Creates inbound shipment for the same item and receives the shipment.
3.	Selects the "Sort Inventory" option from the Yantra Mobile Application and scans the item to sort.
Defect ID	98174
Case ID	Internal
Description	In the “Dock Schedule Details” screen, the system should display the last invalid slot as an unavailable slot.
Defect ID	98191
Case ID	Internal
Description	In the “Inventory Inquiry” screen in RF, when an item description contains characters in the Japanese locale, the item description is displayed incorrectly.
Defect ID	98307
Case ID	Internal
Description	The manageStopDeliveryRequest API throws a "not enough quantity" exception even when the quantity is available.
Defect ID	98906
Case ID	Internal
Description	The Sterling Multi-Channel Fulfillment Solution Customization Guide, Release 8.0 and the Sterling Multi-Channel Fulfillment Solution Installation Guide, Release 8.0 should incorporate the properties of RCP Dev mode.
Solution: The Sterling Multi-Channel Fulfillment Solution Customization Guide, Release 8.0 and the Sterling Multi-Channel Fulfillment Solution Installation Guide, Release 8.0 have been updated. The updated documents are released with this hot fix.
Defect ID	99076
Case ID	Internal
Description	When the scheduleOrder API is invoked for an order that has an order line with order line reservations and has the “EarliestScheduleDate” attribute set to a certain time in the future, the OrderLineReservations record for the order line gets deleted even though the order line is not scheduled.
Defect ID	99135
Case ID	Internal
Description	The query fired by the YFSExecuteCollection agent for retrieving the records to process should return a sorted result to enable the processing of older records.
Defect ID	99148
Case ID	Internal
Description	The “CountryOfOrigin” (COO) attribute should be stamped on the new LPN after finishing the move tasks for an LPN with a valid COO attribute and also after finishing packing into a new LPN.
Defect ID	99610
Case ID	Internal
Description	The following documents should be corrected for the missing graphic for the "Load Rules for Another Organization" icon in Chapter 2, Navigating in the Configurator:
•	Sterling Distributed Order Management Configuration Guide, Release 8.0
•	Sterling Global Inventory Visibility Configuration Guide, Release 8.0
•	Sterling Logistics Management Configuration Guide, Release 8.0
•	Sterling Multi-Channel Fulfillment Solution Platform Configuration Guide, Release 8.0
•	Sterling Product Management Configuration Guide, Release 8.0
•	Sterling Reverse Logistics Configuration Guide, Release 8.0
•	Sterling Supply Collaboration Configuration Guide, Release 8.0
Solution: The documents have been updated with the necessary rectification. The updated documents are released with this hot fix.
Defect ID	99974
Case ID	Internal
Description	When installing the PCA on Foundation 8.0, the PCA Online Help files are not getting merged.
Defect ID	100012
Case ID	45659
Description	In the “YFSRecalculateLineTaxUE” user exit, the “sShipNode” attribute is being passed as blank irrespective of whether the ship node is stamped or not on the order line.
Defect ID	100407
Case ID	Internal
Description	The following security issues have been addressed:
•	The Configurator and the System Management console can be launched by typing the URL directly in the browser even if the user who is logged-in does not have permission to open the Configurator or the System Management Console.
Solution: User authentication has been enabled in the Configurator and the System Management console when these applications are initiated from a browser window.
1.	The EAR contains the HTTP API Tester and other test files by default.
Solution: If you want to include the test files and the HTTP API Tester, pass an extra java parameter “-Ddevmode=true” while building the EAR during deployment. It is strongly recommended that this property should not be used when building a production EAR as it opens up a security threat.
•	The passwords are written to the log files when the “verbose” or “debug’ option is turned ON for the Login API
Solution: User passwords will not be recorded in the log files.
•	No authentication check is performed in YantraConfigServlet.
Solution: User authentication check has been enabled in YantraConfigServlet.
•	The Cognos Callback Authentication Servlet is vulnerable to an SQL injection.
Solution: This security loophole in the Cognos Callback Authentication Servlet has been closed.
Defect ID	100410
Case ID	Internal
Description	The following RCP usability features have been addressed:
•	Ability to display the help content in a floating panel.
•	The Customer Message, Related Task View and Icons are exposed to change the look and feel of an application. 
•	Ability of an application to perform few operations based on user preference.
Defect ID	100412
Case ID	Internal
Description	The following issues have been addressed: 
•	Security Fix: The command level validation should be done at the server level.
•	Notification: After filter is applied on a table, the behavior needs to be notified.
•	Version Detail: The platform version details from the server should be displayed in the “About” dialog box.
•	Model update after filter: After a model is updated, the filter needs to be applied on the table filter data.
Defect ID	100642
Case ID	Internal
Description	When installing the Platform patch for 8.0-HF5, the installation fails while processing XAPI.
Solution: The installation of the Platform patch is successful if the installation is performed again after the installation fails at the first attempt.
Hot Fix ID	8.0-HF4
Defect ID	97714
Case ID	Internal
Description	When the ON_SUCCESS event of the createdDraftReturn transaction is configured to invoke the changeOrder API, and if a return order is then created for a sales order, the sales order does not change to the “Return Order Created” status.
Defect ID	98024
Case ID	45132
Description	The Sterling Multi-Channel Fulfillment Solution Installation Guide, Release 8.0 should be corrected for the following inaccuracies:
•	In Section 5.2, “Installing Oracle (UNIX/Linux)”, the arguments for the parameters “cursor_sharing” and “optimizer_mode” in step 3 are incorrect.
•	In Section 6.4, “Installing Oracle (Windows)”, the arguments for the parameters “cursor_sharing” and “optimizer_mode” in step 3 are incorrect.
Solution: The Sterling Multi-Channel Fulfillment Solution Installation Guide, Release 8.0 has been updated with the necessary rectifications. The updated document is released with this hot fix.
Defect ID	98188
Case ID	Internal
Description	When a user performs the following sequence of actions, the sales order creates a new entry in the YFS_INVENTORY_DEMAND table with DEMAND_TYPE as OPEN_ORDR instead of consuming the previously created reservation (E1) resulting in incorrect inventory picture:
1.	Configures two seller organizations (E1 and E2) to have the same inventory organization.
2.	Reserves inventory of an item in E1 and creates sales order for the same item in E2 using the reservation in E1.
Defect ID	98762
Case ID	45250
Description	The Sterling Multi-Channel Fulfillment Solution Upgrade Guide, Release 8.0 should be corrected for the following inaccuracies:
•	In Section 2.4.1, “Preliminary Steps”, the arguments for the parameters “cursor sharing” and “compatible” are incorrect.
•	In Section 2.10.4.2, “Text Search Tasks on DB2 Database”, the Note after step 4 should refer to dropping text search indices from the DB2 database and not the Oracle database.
•	In Section 2.10.4.3, “Text Search Tasks on SQL Server”, the Note after step 5 should refer to dropping text search indices from the SQL Server database and not the Oracle database.
Solution: The Sterling Multi-Channel Fulfillment Solution Upgrade Guide, Release 8.0 has been updated with the necessary rectifications. The updated document is released with this hot fix.
Defect ID	99036
Case ID	45411
Description	When all the following conditions are true for bundles, the output of the findInventory API does not return any available assignments: 
•	Bundles are fulfilled in the Delivers Together mode.
•	One of the components uses unplanned inventory and the other component has the complete inventory that is required to fulfill the requested quantity.
•	Scheduling Rule is configured as “Line Ship Complete”.
Defect ID	99160
Case ID	Internal
Description	The WSDL file that is generated for the exposed Web Services does not contain the fault code corresponding to the application exception. The system will not allow the declaration of YFSException as WSDL.fault because the same is a runtime exception.
Solution: The application has been enhanced to declare the YIFWebServiceException as the fault code in the generated WSDL file. Web Service clients are now expected to catch the YIFWebServiceException for handling any application exceptions.
Defect ID	99563
Case ID	Internal
Description	When all the following conditions are true, the output of the findInventory API returns incorrect promiseLine choices: 
•	Bundles are fulfilled in the Deliver Together mode.
•	The ShipToAddress element is passed in the input.
Hot Fix ID	8.0-HF3
Defect ID	95904
Case ID	Internal
Description	When upgrading from version 7.3 to version 8.0 on the MS SQL Server 2005, a Create Statement for the YFS_SEQ_YFS_SHIP_ADVICE_NO table is generated even though this table already exists in the previous version.
Defect ID	96020
Case ID	Internal
Description	When upgrading from version 7.3 to version 8.0 on the MS SQL Server 2005, the “YFS_INBOX_REFERENCES_I2” index creation fails because the “YFS_INBOX_REFERENCES_I2” index exceeds the maximum permitted length of 900 bytes.
Defect ID	96022
Case ID	Internal
Description	In the MS SQL Server, dbverify creates unnecessary ALTER SQL statements because the default values in columns which were earlier char are now nchar.
Defect ID	96024, 96022
Case ID	Internal
Description	The dbverify tool creates unnecessary ALTER SQL statements for MS SQL Server when any of the following conditions are true:
•	When the data type of a column having a default value with trailing spaces is changed from char to nchar.
•	When the metadata corresponding to the default value for the date column has “(" and ")" surrounding it.
Defect ID	96389, 96766
Case ID	Internal
Description	When the triggeragent.sh and startIntegrationServer.sh are run, the system throws a "USE_AGENT_JAVA=1 is not an identifier" error message.
Defect ID	98495
Case ID	45256
Description	The HFInstaller for the 8.0HF1 build fails with an ANT error when building a EAR with Web Services in the IBM WebSphere Application Server environment.
Defect ID	98558
Case ID	45304
Description	When building an application EAR for IBM WebSphere with the “nowebservice” parameter set to “false”, the buildEAR scripts throw a “java.lang.NoClassDefFoundError: com.yantra.api.YSCApi” exception.
Defect ID	98588
Case ID	45306
Description	The Sterling Multi-Channel Fulfillment Solution Installation Guide should provide instructions for adding custom JAR files when building yantra.ear. 
Solution: Instructions for adding custom JAR files has been provided in Section 13.1.2, Installing Third-Party JAR files of Chapter 13, Configuring Utilities, in the Sterling Multi-Channel Fulfillment Solution Installation Guide.
Hot Fix ID	8.0-HF2
Defect ID	96289
Case ID	Internal
Description	When a user invokes the getPossibleSchedules API for a product item that uses unplanned inventory and if the same product item has a delivery service associated with it, a “ClassCastException” error is thrown.
Defect ID	96912, 97391
Case ID	Internal
Description	The Service Definition Framework should allow the configuration of Exception Type for the Alert Flow Component through system arguments. Also, the “ExceptionType” field available under the General tab of the Alert Flow Component should be made optional if the Exception Type is defined through system arguments. The system will throw an error when raising an alert if the “Exception Type” field is not configured either through “ExceptionType” field or through system arguments.
Defect ID	97753
Case ID	45013
Description	When a user invokes the findInventory API for a bundle item, which is in Deliver Together mode, and whose requested quantity cannot be fulfilled, the findInventory API output allocates two assignments for the parent bundle. Both the assignments have the quantity that can be fulfilled, instead of the empty assignment having the quantity that cannot be fulfilled.
Defect ID	98233
Case ID	43174
Description	When a user performs the following sequence of actions, the Ship Date on the order is set to the current date: 
•	Performs inventory reservation against future inventory.
•	Creates order with OrderLineReservations, which consumes the inventory reservation.
•	Schedules the order. 
Note: When installing the hot fix, and subsequently building the EAR with web services for WebSphere, the application server will fail with a “class not found” error. This is a pre-existing issue in the product starting with the base release. Please contact Customer Support for work around solutions if you encounter this issue.
Hot Fix ID	8.0-HF1
Defect ID	96486
Case ID	Internal
Description	The Deliver Together Bundle is being released with limited functionality which will always fulfill bundle components in a ratio, when considering availability across multiple nodes (unlike Ships Together where it is always against the same node). However the Deliver Together Bundle will not ensure that the components are delivered on the same date.  
There is also a need to document the following limitations of the Deliver Together Bundle functionality: 
•	N-level bundles are not supported.
•	Dynamic bundles are not supported.
•	Bundles with Delivery service lines or Provided service lines are not supported.
Solution: In the Product Management Configuration Guide, Chapter 4: Configuring Products, Section: 4.1.2.13.1, a new screenshot has been added for the Deliver Together Bundle functionality. Also, the existing description has been modified to include the functionality and limitations of the "Delivers Together" radio button. The revised document is released with this hot fix.
Defect ID	96691
Case ID	Internal
Description	When a user invokes a service for the “End Of File” message for a file adapter, the system throws the following error message: 

 “Missing right parenthesis” 
Defect ID	96839
Case ID	Internal
Description	The Cache Manager does not clean up the old cached records properly, eventually causing the system to throw the following error message:
 "Out of Memory"

Defect ID	96959
Case ID	Internal
Description	When building the EAR with Web services, the buildear.xml file should point to the correct location of the namedwebservices.xml file, which is located in <INSTALL_DIR>/repository/eardata/platform/webservices.
Defect ID	97417
Case ID	45010
Description	When no components are available for a bundle that is configured as Deliver Together, the output of the findInventory API should display the bundle parent line as one of the unavailable lines.
Defect ID	97675
Case ID	44987
Description	When creating a deployable application EAR for the IBM WebSphere Application Server, the WSDL file that is generated does not contain the fault information pertaining to the YFSException.
Defect ID	97710
Case ID	Internal
Description	When installing the nWMS_Add-in.jar for AIX/WebSphere 6.1 using the InstallService scripts, the installation fails, and the system throws the following error message: 
“java.lang.NoClassDefFoundError: com.sterlingcommerce.woodstock.install.utils.UninstallInfo error”