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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Hot Fix ID	8.5-HF7

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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