Hot Fix Release Notes
	Product	Selling and Fulfillment Foundation, 9.0
	Date	Tuesday, February 22, 2011
List of Defects Addressed
Hot Fix ID	9.0-HF19
Defect ID	239524, 239525, 239645
Case ID	Internal
Description	The Selling and Fulfillment Foundation: Installation Guide must be updated with the information about the JAXB Web Service and Selling and Fulfillment Foundation: Customizing APIs Guide must be updated with the information about how to update the datatypes.xsd with custom data-types.

Solution: The requisite information has been provided in Chapter “Deploying Selling and Fulfillment Foundation" of the Selling and Fulfillment Foundation: Installation Guide and Chapter, “DTDs, XSDs, and Complex Queries” of the Selling and Fulfillment Foundation: Customizing APIs Guide.
Defect ID	240910
Case ID	00276417
Description	While closing a future Manifest on current date, the system hangs and connection leak is observed.
Hot Fix ID	9.0-HF18
Defect ID	238044
Case ID	00216044
Description	The Selling and Fulfillment Foundation: Mobile Application User Guide must be updated with the information about the "No Open Tasks" screen.

Solution: The requisite information has been provided in Chapter, “Performing System-Directed Tasks’ of the Selling and Fulfillment Foundation: Mobile Application User Guide.
Defect ID	238200
Case ID	00262515
Description	The application must be enhanced to improve the performance of the confirmShipment API by leveraging the "DoInventoryUpdateOffline" flag based on yfs property.

Solution: The DoInventoryUpdatesOffline = Y is now passed in the confirmShipment API from the closeManifest API based on the new yfs property, yfs.closeManifest.doInventoryUpdatesOfflineOnConfirmShipment = Y.
Defect ID	238545
Case ID	00261741
Description	When a user performs the following actions, the system prompts the user to enter the purchase order information:
1.	Creates a purchase order for a receiving node
2.	Logs in to the Sterling Mobile application.
3.	Selects the "Receive" menu.
4.	In the “Criteria” screen, enters the purchase order information.
5.	In the “Location” screen, scans the receiving information.
6.	In the “Case/SKU Entry” screen, scans a case and the received item for the purchase order.

Defect ID	239385
Case ID	00254595
 Description	The information about pierbridge integration required for printing the Pickup Summary Label Print must be updated in Selling and Fulfillment Foundation: Properties Guide.

Solution: The Selling and Fulfillment Foundation: Properties Guide has been updated with the requisite information.
Defect ID	239838
Case ID	00267730
Description	When a user performs the following actions, the system does not display the list of the outbound containers associated with the shipment:
1.	Creates a shipment for an item
2.	Packs the shipment in multiple outbound containers.
3.	Adds the outbound containers to an inventory pallet through the ‘Build Inventory Pallet’ activity.
4.	In the “Outbound Shipment Detail” screen selects the "Containers" option.
Defect ID	240078
Case ID	00271141
Description	When a user performs the following actions, the system throws "Cannot Suggest Task to user" exception:
1.	Configures a task type to perform the Pick Into Container, Pack While Pick, and System Suggested Containerization.
2.	Configures the Pick Location Assignment to pick from multiple zones and associates the above configured task type for picking.
3.	Creates a shipment, adds it to a wave, and releases the wave such that the pick tasks are created from multiple zones.
4.	Containerizes the wave.
7.	Logs in to the Sterling Mobile application.
5.	Selects the "Outbound Picking" option.
6.	Scans the Container Number and picks inventory from the first zone.
7.	Deposits the container in an in-transit zone to allow other users to pick inventory from the remaining zones.
If another user scans the same container to proceed with picking and pass activity on outbound containers, the system throws the exception.
Defect ID	240130
Case ID	00271264
Description	When a user performs the following actions, the system throws a "WMS00056: There is no inventory for put away at the Source Location" error:
1.	Creates a purchase order for an item
2.	Logs in to the Sterling Mobile application.
3.	Selects the receipt and putaway options.
4.	Scans the order and clicks "Enter".
8.	Scans the equipment and clicks "Enter".
5.	Scans the item ID and tabs out.
6.	In the "Quantity" screen, scans the quantity and tabs out. Leaves the Disposition Code field and clicks "Enter".

Defect ID	240229
Case ID	00271593
Description	When a user searches for shipments by date range in the "By Wave" resource of Outbound Shipment Search” screen, the application List screen does not correctly list the outbound shipments based on the date range.
Defect ID	240353
Case ID	00268051
Description	In the following scenarios, the system throws “update failed” error while creating a wave:
•	When shipping calendar is defined at the node level.
•	When the qualifying shipments dates are older than the current date.
•	When the NEXT_ALERT_TS field in the YFS_SHIPMENT table is updated by the Shipment Monitor agent.
•	When the createWaveforNode API is invoked or the CREATE_WAVE_SHIP_GROUP agent is run.          

Defect ID	240739
Case ID	00275100
Description	While performing Close Manifest, the system tries to call the confirmShipment API even for shipments that have uncontainerized quantity, even if all the containerized quantity has already been added to manifest. The system must check the Is Pack Process Complete at shipment level before confirming.
Hot Fix ID	9.0-HF17
Defect ID	239158
Case ID	00266180
Description	If an exception exists in the JMS Consumer service, the reply to a Queue message contains only the input XML and does not contain any information about the exception.
Defect ID	239356
Case ID	00268525
Description	When a user performs the following actions, the system incorrectly cancels the tasks:
1.	Creates a shipment for an item.
2.	Includes the shipment in a wave and releases the wave.
3.	Containerizes the wave, such that multiple containers are created for the item.
4.	Modifies the container and removes the item quantity from the shipment line.
Defect ID	239684
Case ID	Internal
Description	While building the EAR with JAXB Webservices for the receiveIntransitUpdates API, the system throws a JAX bean compilation error.
Defect ID	239689
Case ID	00269809
Description	When the following conditions are met, the system does not honor Pick Location Assignment configured for the item correctly:
1.	Configures an item I1 with alternate UOM as CASE and PALLET with conversion quantities as 1 and 720 EACH respectively.
2.	Configures Pick Location Assignment to pick quantities in UOM of PALLET from Zone Z1 with task type as T1.
3.	Configures Pick Location Assignment to pick quantities in UOM of CASE from Zone Z2 with task type as T2.
4.	Configures Pick Location Assignment to pick quantities in UOM of EACH from Zone Z3 with task type as T3.
5.	Adjusts 40, 30 and 20 quantities of inventory for I1in Z1, Z2 and Z3 respectively.
6.	Creates a shipment for item I1 with 5 quantities.
7.	Includes shipment in wave and releases the wave.
The system creates a task from Z3 with task type as T3 instead from Z2 with task type as T2.

Defect ID	239701
Case ID	00270223
Description	When a user performs the following actions, the system throws an "YCM0002 - Mandatory Parameters for the Operation are missing” error:
1.	Navigates to WMS > System Administration > BarCodes.
2.	Configures a new barcode source in the ‘Adhoc Move Pick’ Bar Code Type, for example, "Container” and associates it with Bar Code Validation Source as CartonNo.
Ensures that the inventory for item 1 is available in the Pack location or Pack station.
3.	Creates and packs the shipment S1 for Item1. 
4.	Logs in to the Sterling Mobile application.
5.	Selects Adhoc Move option and clicks “Go”.
6.	Scans the Pack location and tabs out.
7.	Scans the Container Number associated with the container SCM generated in the Pack station.
Hot Fix ID	9.0-HF16
Defect ID	230661
Case ID	00220524
Description	The system forces a user to scan Item ID twice when it tries to perform inventory sorting after the inventory is received in the dock.

Solution: 
A user must create a new resource from the RF_Inventory_Sorting and must change the Java Server page parameter from the /rf/wms/sortinventory/frmSortInventory.jsp to /rf/wms/sortinventory/frmSortInventory.jsp?AutoSort=Y.
Defect ID	237896
Case ID	00254595
Description	A user must be able to perform the following sequence of actions:
•	On calling the closeManifest API, the Pickup Summary Barcode Report must get printed.
•	Ability to reprint the Pickup Summary Barcode Report for any of the closed Manifests on any day.
•	Ability to either print the Pickup Summary Barcode Report directly to any desired printer.
Defect ID	238095
Case ID	00261949
Description	When the following conditions are met, the system do not honor the Pick Location Assignment configured for an item:
1.	Configures an item with an alternate UOM as CASE and PALLET with conversion quantities as 10 and 720 EACH respectively.
2.	Configures the Pick Location Assignment to pick quantities in UOM of PALLET from Zone Z1 with task type as T1.
3.	Configures Pick Location Assignment to pick quantities in UOM of CASE from Zone Z2 with task type as T2.
4.	Configures Pick Location Assignment to pick quantities in UOM of EACE from Zone Z3 with task type as T3.
5.	Adjusts 40, 30, and 20 quantities of inventory for I1in Z1, Z2, and Z3.
6.	Creates a shipment for item I1 with 30 quantities.
7.	Includes shipment in a wave and releases the wave.
The system creates a task from Z1 with task type as T1 instead of creating from Z2 with task type as T2.
Defect ID	238281
Case ID	Internal
Description	Using the JAXB Webservices the time taken for invoking the APIs is very high as compared to Simple Webservices.
Defect ID	238282
Case ID	Internal
Description	The system throws a NullPointerException while building the client for JAXB Webservices.
Defect ID	239217
Case ID	00267722
Description	When a user performs the following sequence of actions, the system throws a "YDM00292 - Cannot add a manifested container to another container" exception:
1.	Creates a shipment for an item.
2.	Includes the shipment in a wave.
3.	Releases and containerizes the wave.
4.	Invokes the getTrackingNoAndprintLabel API to update the manifest and tracking number information on the containers.
5.	Packs the containers.
6.	Performs the pallet build operation to include the containers in the pallet.

Defect ID	235496
Case ID	00239304
 Description	 Functionality to automatically weigh containers during manifesting must be provided.

Hot Fix ID	9.0-HF15
Defect ID	234882, 238450
Case ID	00242189
Description	In Business Center, the “Customer Entitlement Details” screen must be enhanced to display the paginated list of items assigned to an entitlement detail rule. 

Solution: The “Customer Entitlement Details” screen has been enhanced to display the paginated list of items assigned to an entitlement detail rule. 

The Business Center: Item Administration Guide has been updated with the requisite information.
Defect ID	236037
Case ID	00231966
 Description	When a user calls the getOrderDetails API or getOrderLineDetails API and sets the dynamic template of these APIs using the file name of the template, the system throws “ClassCastException".
Defect ID	236581
Case ID	00252682
Description	When a user performs the following sequence of actions, the system does not allow a user to unpack a shipment:
1.	Creates an order. 
2.	Schedules and releases the order.
3.	Includes it in a shipment.
4.	Navigates to Pack station > Container Details.
The “Container Details” screen is displayed.
5.	In the Container properties panel, clicks ‘Unpack Container’.
6.	Clicks “Remove Quantity”.
7.	Clicks “Save”
The system displays the  error message “ErrorDescription="Delete failed. The record to be deleted could either not be found or it was already deleted or updated by another transaction.".
Defect ID	237068
Case ID	00254139
 Description	While pick fencing the system does not consider the inventory status configured in the Outbound Pick Location Assignment rules.
Defect ID	237763
Case ID	00258270
Description	 If all the eligible shipments have shipment lines less than the configured max number of shipment lines, certain times the system create waves by not abiding the wave size constraint by shipment lines.
Defect ID	237821
Case ID	Internal
Description	The Sterling Sensitive Data Capture Server: PA-DSS Implementation Guide and Sterling Sensitive Data Capture Server: Configuration Guide must be updated with the installation instructions for displaying all the files that are created as part of the installation process.
Solution: The requisite information has been provided in the Sterling Sensitive Data Capture Server: PA-DSS Implementation Guide and Sterling Sensitive Data Capture Server: Configuration Guide.
Defect ID	237854
Case ID	00259882
Description	 If the Text Load service is used to transfer a file from an input directory to a working    directory, and if the working directory is not accessible during the file processing, the system deletes the file from the input directory.
Defect ID	237893
Case ID	00216044
Description	To perform outbound picking, when a user navigates to the "No Open Tasks" screen and clicks “OK”, the user is redirected to the Main Menu page instead of Outbound Pick menu option.
Defect ID	237894, 238043
Case ID	00239523
Description	 The Cycle Count functionality on the Sterling Mobile Application must allow a user to enter a start location.

Solution: When a user logs in to the Sterling Mobile Application and navigates to the “Cycle Count” screen, user can enter the start location. Based on this, the system suggest the next optimal task.

The requisite information has been provided in the Selling and Fulfillment Foundation: Mobile Application User Guide.
Defect ID	238046
Case ID	00261181
Description	When a user performs the following sequence of actions, the task moves to the ‘Held’ status:
1.	Creates two outbound pick tasks from the Forward Pick location (T1 ,T2).
2.	Enters the quantity as zero against T1.
3.	Creates a pend-in for the item as in T1.
4.	Includes the yfs.suggesttask.onshortpick.tasktypelist=tasktype in the Customer Overrides properties file.
5.	Logs in to the Sterling Mobile Application. 
6.	Navigates to the “Outbound Pick” screen.
The System suggests task T2.
7.	Completes  task T2.
Task T1 moves to the ‘Held’ status.
Defect ID	238123
Case ID	00261906
Description	When a user prints the shipment Bill Of Lading for an outbound shipment, the out-of-the- box Bill Of Lading Print services read the Customer Purchase Order number information from the order line instead of the shipment line.

Solution: If the information is present on the shipment line and an order is not present on the system, copy the Customer Purchase Order number information from the shipment line to the order line element. 

Hot Fix ID	9.0-HF14
Defect ID	216926
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	221443, 221442
Case ID	Internal
 Description	The security vulnerability related to token value must be fixed.
Defect ID	235306
Case ID	00245195
 Description	The getLocationList API java docs and the default templates do not contain the newly added attributes, MinQty and MaxQty at the SKUDedication level.
Defect ID	237016
Case ID	00254752
 Description	The JMS consumers configured in the service definition framework in the Applications Manager User Interface are not able to copy the Request JMS MessageID into the Response JMS Correlation ID. The JMS consumers is also not able to configure the 'time to live' attribute for the response message.

Solution: In the Applications Manager, new fields have been added in the following services:
•	Asynchronous JMS receive service - The "Reply Correlation ID should be same as Request JMSMessage ID" check box and "Reply Time to live" text box.
•	Synchronous JMS Send and Receive service - The "Is Reply Correlation ID should be same as the Request JMSMessage ID?" checkbox.

For more information about the yfs.jms.replytoqueue.forcesoapspec and yfs.jms.replytoqueue.timetolive properties, refer the Selling and Fulfillment Foundation:Javadocs.
Defect ID	237179
Case ID	00223527
 Description	When a user logs in to a different system and changes the time zone to US Central time, the start no earlier time is populated as US Eastern time instead of  US Central time in the “Create Count Request’ screen.
Defect ID	237290
Case ID	00254453
 Description	If multiple shipments exist in the system, and a user calls the consolidateToShipment API to pass the shipments for customization, the shipments are not passed.
Defect ID	237433
Case ID	00257692
 Description	The executeCollection API does not honor the time stamp of the collection date because of which it picks up the charge transactions with a future collection date.
Defect ID	237441
Case ID	Internal
 Description	In the Sterling On Demand application, when a user selects multiple records in any of the List screens to view the details, the ordering of the detail pages are inappropriate. Due to this, the duplicate pages are displayed in the corresponding Detail screen.
Defect ID	237482
Case ID	00253913
Description	When a user performs the following sequence of actions, the requestCollection agent is picking the orders for processing which are on payment hold and throws an exception:
1.	Creates a payment hold to prevent the requestCollection agent.
2.	Creates an order and confirms it.
Puts the order on hold.
3.	Runs the requestCollection agent.
Defect ID	237620
Case ID	Internal
 Description	The system logs off the users from the mobile device sporadically on the Solaris 10 platform that runs on the AMD Opteron Processor.
Defect ID	237647
Case ID	00255779
 Description	In the following scenarios, the system displays "No record found for the passed inputs" error message:
	
	Inbound Order Scenario:
	
1.	Creates an inbound shipment, INBS1 for an item SZ1 having 2 quantities with the receiving node as N1.
2.	Records the container details by providing the pallet ID, P1 and the serial numbers, SR1 and SR2.
3.	Starts the receipt and receives the inventory for serials SR1 and SR2.
4.	Performs the putaway task to pack inventory at a location.
There are two units of SZ1 in the pack station.

Transfer Order Scenario:
	
1.	Creates a transfer order shipment for an item SZ1 to move the inventory from node N1 to N2.
2.	Packs the shipment and confirms the shipment from node N1.
3.	Receives the transfer order shipment from node N2.
4.	Performs the putaway task to pack inventory at a location. 

Outbound Scenario:
	
1.	Creates an outbound shipment with ship node as N2 for the same item SZ1 and SZ2.
2.	Changes the shipment status to “sent to node”.
3.	Packs the shipment into a pallet. 
4.	Scans the item ID. The “Serial Number” pop-up window is displayed.
5.	Scans the serial numbers, SR1 and SR2.
6.	Clicks ‘Save”.

Hot Fix ID	9.0-HF13
Defect ID	230599
Case ID	Internal
 Description	The changes should be made to support zero down time while activating a new search catalog index.
Defect ID	232371
Case ID	Internal
 Description	The incremental build of catalog search index does not update the changes correctly in certain scenarios.

Known Issues: The pricelist effective dates are not considered when determining which items need to be updated in an incremental build.

Workaround: A user should mark the past pricelist as 'INACTIVE'.
Defect ID	232686
Case ID	00233132
Description	The following issues are noticed while extending the “Field Sales” screen:
•	The message "this.overlayEditor is undefined" is displayed in the console.
•	The message “component.getEI() is undefined” is displayed in the console.
•	The message “sb is undefined” is displayed in the console.

Defect ID	234016
Case ID	Internal
 Description	When multiple appsServers are running and if a user activates a new index, it may result in an incorrect cache loading period. This information, must be updated in the Catalog Management:Concepts Guide.

Solution: The Catalog Management:Concepts Guide has been updated with the requisite information.
Defect ID	234225
Case ID	00234627
Description	The getInventorySnapShot API must support batching.
Solution: The getInventorySnapShot API is enhanced to support two new attributes ‘LastInventoryItemKey’ and ‘MaximumNumberOfItems’.
When these attributes are passed in the input along with shipNode, the API fetches records ahead of the passed ‘LastInventoryItemKey’ attribute with the number of records restricted to ‘MaximumNumberOfItems’ attribute value passed in the input.
Note: The attributes are honored only if ShipNode is passed in the input.
Defect ID	234361
Case ID	Internal
 Description	The information about recommendations and timings based on the configuration when performing full and incremental catalog index must be updated in the Catalog Management:Configuration Guide, Catalog Management:Concepts Guide, Selling and Fulfillment Foundation:Properties Guide.

Solution: The Catalog Management:Configuration Guide, Catalog Management:Concepts Guide, Selling and Fulfillment Foundation:Properties Guide has been updated with the requisite information.
Defect ID	234693
Case ID	Internal
 Description	The information about loading the cache at the 10th minute interval must be updated in the Selling and Fulfillment Foundation:Properties Guide.

Solution: The Selling and Fulfillment Foundation:Properties Guides have been updated with the requisite information.
Defect ID	235635
Case ID	Internal
 Description	The ScheduleOrder API does not work as expected in the following scenario:
•	When there is segmented inventory for the items in an order.
•	When there are multiple order lines in an order.
Defect ID	236272
Case ID	Internal
 Description	The merged datatypes.xml created during the hot fix installation corrupted entries for the data types that had multiple child elements, such as 'Enum' or 'DBType'.
Solution: The issue has been fixed for data types having child elements, 'Enum' or 'DBType'. While extending the datatypes.xml, a user cannot update the following attributes:
•	The 'Value' attribute of an existing 'Enum' XML element.
•	The 'Name' attribute of an existing 'DBType' XML element.
As, the above attributes are used to uniquely identify the ‘Enum’ and ‘DBType’ xml elements for a data type.

Defect ID	236316
Case ID	00242189
 Description	The getEntitlementRuleDetailItemList API must be exposed to retrieve Entitlement Rule Detail item records based on the input criteria.

	Solution: The getEntitlementRuleDetailItemList API has been exposed.
For more information about the getEntitlementRuleDetailItemList API, refer to the Selling and Fulfillment Foundation:Javadocs.
Defect ID	236598
Case ID	00252912
 Description	When a user performs the following sequence of actions on a  pallet(00100000000000120001) having a child shipping container(100000000123), the system displays an "error - "Container_Scm/Case_ID_is_invalid" error message:
1.	Logs in to the Sterling Mobile Application. 
2.	Selects the ‘Undo Container Build’ option. 
3.	Scans the pallet scm(00100000000000120001 ) in the "Container SCM" field and scans the container number (100000000123). 
4.	Clicks “Go”.
Defect ID	236637
Case ID	Internal
Description	The localization issues in the application have been fixed, and the relevant documents have been updated.
Defect ID	236703
Case ID	00253728
 Description	When a user prints the Shipment Bill Of Lading for the outbound shipment, the out-of-the-box Bill Of Lading Print Services reads the NMFC information only from the order line.

 Solution: If the information is present on the shipment line and order is not present on the system, the NMFC data must read from the shipment line.
Defect ID	237049
Case ID	00197160
 Description	The following columns must be resized to avoid upgrade impact for the customers upgrading on DB2 database from Release 9.0:
1.	In the YFS_ITEM table, the ‘DESCRIPTION’ column must be changed to 500 bytes.
2.	In the YFS_ORDER_KIT_LINE, YFS_ORDER_LINE, and YFS_SHIPMENT_LINE tables, the corresponding mappings of the item table must be resized.
3.	In the YFS_ORDER_LINE and YFS_ORDER_KIT_LINE tables, the ‘CUSTOMER_ITEM_DESCRIPTION’ column must be resized to 500 bytes.
Defect ID	237120
Case ID	00253189
Description	 When a SKU dedicated location is set up with the minimum and maximum quantity and "Replenish the locations up to maximum quantity for dedicated items" and "Replenish when inventory goes below minimum quantity for dedicated items" is enabled in PLA, the system cancels a wave if demand is available at the forward pick location, but not available in the bulk location to fulfill the maximum quantity for replenishment.
Defect ID	237208
Case ID	00254837
Description	When multiple warehouses contain waves with the same wave number and if one of the warehouse user opens the “Wave Summary” screen using the Selling and Fulfillment Application Console, the system displays an incorrect value for NoOfShipmentLines, NoOfSKU, and NoOfProfiles fields.
Defect ID	237289
Case ID	00235222
Description	The Sterling Mobile Application logs out, when a user selects the "Build Pallet" menu.
Defect ID	237333
Case ID	00256729
Description	While creating a wave, the optimum waves are not getting created and the number of waves is limited.
Defect ID	237354
Case ID	00253539
 Description	When performing a pick task using the Sterling Mobile Application, if inventory is not available at the source location to execute the task, the system suggests an alternate pick location and moves the task to "Held" status, if the alternate pick location suggestion fails. 

 Solution: The application has been enhanced to automatically suggest the same task even if inventory does not exist for certain task types. The ‘yfs.suggesttask.onshortpick.tasktypelist’ property that must to be set to comma-separated values of the task types in the yfs.properties file has been provided. 

Note: If the ‘yfs.suggesttask.onshortpick.tasktypelist’ property is not set or the task is not of the task type mentioned in the list, the system will retain the current behavior.
Hot Fix ID	9.0-HF12
Defect ID	222817
Case ID	Internal
Description	The tracking number is not getting printed on the Return labels.
Defect ID	227032
Case ID	Internal
Description	When a user performs the following sequence of actions, the system throws "An OpenShip Index (542) was not specified" exception:
1.	Creates a returnable item and sets the return label printing at the SKU level.
2.	Configures a carrier other than FEDX that integrates with FXRS server to print return labels.
3.	Creates freight terms for an enterprise.
4.	Creates a shipment with the returnable item. Uses the configured carrier.
5.	Packs the shipment into multiple containers.
6.	Invokes the addContainerToManifest API for a container.
Defect ID	228624
Case ID	Internal
Description	The system throws “YFC0009: Update failed” exception, when the changeShipmentContainer and getTrackingNoAndPrintLabel APIs are invoked in a single transaction boundary to update a shipment container.
Defect ID	229005
Case ID	00211040
 Description	The information about copying the web.xml to eardata/smcfs/extn must be removed from Section 3.3, “Preparing the Development Environment on WebLogic” of the Selling and Fulfillment Foundation: Customization Basics Guide.

Solution: The Selling and Fulfillment Foundation: Customization Basics Guide has been updated with the requisite information.

Defect ID	229559
Case ID	Internal
Description	The system throws an update failed exception when the following APIs are invoked in a sequence and in a single transaction boundary:
•	addToContainer
•	changeShipmentContainer
•	addContainerToManifest

Defect ID	234878, 236132
Case ID	00210406
Description	The application must limit the number of accepted waves in order to maximize  the possibility of consolidation opportunities.
Solution: The application has been enhanced to limit the number of accepted waves in order to maximize the possibility of consolidation opportunities.

Note: The requisite information has been updated in the section "Defining a Shipment Group’s Advanced Parameters" of the Sterling Warehouse Management System: Configuration Guide.
Defect ID	235497, 235867
Case ID	00237411
 Description	Package-level manifesting is not supported.
Solution: A new property ‘yfs.manifest.manifestAtContainerLevelForDomesticParcelShipment’ has been introduced. 
By default, the ‘yfs.manifest.manifestAtContainerLevelForDomesticParcelShipment’ property is set to ‘N’.
The ‘Put container on hold on Carrier Server while generating tracking number and Ship or Release the Hold on the container while Manifesting the container’ checkbox has been introduced. This checkbox can be selected in the Parcel Carrier Preferences depending on whether a user wants to hold a container (at Pierbridge) while generating the tracking number and label, and ship or release the container while manifesting.
If the ‘yfs.manifest.manifestAtContainerLevelForDomesticParcelShipment’ property is set to ‘Y’ and the ‘Put container on hold on Carrier Server while generating trackingnumber and Ship or Release the Hold on the container while Manifesting the container’ checkbox is selected, the system enables package level manifesting. Due to this, the getTrackingNoAndPrintLabel, addContainerToManifest, CloseManifest, and RemoveContainerFromManifest APIs are impacted.
For more information about the getTrackingNoAndPrintLabel, addContainerToManifest, CloseManifest, and RemoveContainerFromManifest APIs, refer to the Selling and Fulfillment Foundation:Javadocs.

Notes: 
•	The requisite information has been updated in the section "Creating a Parcel Carrier Preference” of the Sterling Warehouse Management System: Configuration Guide and section “yfs.properties” of the Selling and Fulfillment Foundation Properties Guide.
•	Pierbridge Shipment Server 6.5.97 must be used in order to use this feature.
Defect ID	235696
Case ID	00242711
 Description	When a user invokes the sendRelease agent for a scheduled and released order, the system throws "YFS10537:Invalid Charge Category" exception.
Defect ID	235763
Case ID	00245753
 Description	When a user performs sort inventory operation through WinCE mobile application, and sorts inventory for item quantity more than the location quantity, the system throws "WMS00019: Not enough quantity for inventory operation" exception and does not allow the user to proceed with task cancellation.
Defect ID	236274
Case ID	Internal
Description	The buildjaxclient.sh and buildJaxWsClient.xml are missing in the platform component for JaxB Webservice related fixes.
Defect ID	236334
Case ID	00250725
Description	When a user performs the following sequence of actions, the system does not create containers as expected during wave containerization:
1.	Configures PLA with task type as Pick Into Equipment, Apply label, Pack While Pick, and System Suggested Containerization.
2.	Configures an item with alternate UOM as Case and conversion quantity as 1.
3.	Creates a shipment for the configured item.
4.	Includes the shipment in wave.
5.	Releases the wave and containerizes the wave.

Defect ID	236390
Case ID	Internal
 Description	When a user creates a shipment and packs it, at the time of packing it  the addToContainer API is called due to which the system performance is slow when the query is fired on the YFS_SHIPMENT_Container table while calling the addToContainer API.
Defect ID	236400
Case ID	Internal
Description	The system does not honor node configuration, while retrieving task types from the getNextDepositLocation API.
Defect ID	236421
Case ID	Internal
Description	When a user performs the following sequence of actions, the system locks the transaction twice:
1.	Creates a shipment.
2.	Create two containers for a shipment.
3.	Packs the container.
4.	Adds the first container to a manifest. The system opens a new manifest and locks the transaction. 
5.	Adds the second container to the manifest. The system again locks the transaction.

Solution: The system locks the transaction if a new manifest is opened.
Defect ID	236569
Case ID	00252758
 Description	When a user calls the consolidateToShipment API  it changes the ‘PackAndHold’ flag status on the shipment from ‘N’ to ‘Y’, if two or more order releases with different shipment dates are consolidated into a single shipment.
Hot Fix ID	9.0-HF11
Defect ID	228808
Case ID	00209953
 Description	A user is not able to implement a password policy rule for logging into the system.
Solution: The application has been enhanced such that a hashmap object(PasswordPolicyResultMap) is set in the HTTPSession, if the password policy rule is implemented. A user can write a customization logic to intercept the request and access the PasswordPolicyResultMap. The values in this map can be used to redirect to ChangedPasswordLink. 
Defect ID	232229
Case ID	00214687
Description	Authorizations are chosen randomly for charging that may result in mismatch of an authorization and charge amount.

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

        Defect ID	232230
Case ID	00230997
 Description	The application must be enhanced to support Reverse Authorizations. New fields must be exposed in the executeCollection user exit to pass information regarding reversals that is to be reported into the system.
Defect ID	232511
Case ID	00233262
 Description	When a user logs in to Sterling Mobile Application and selects the ‘Undo Container Build’ option, the system converts the outbound containers to inventory containers. Due to this, the user needs to again pack the shipment.
Solution:  A user must create a new resource from  the RF_Undo_Container_Build and must change the Java Server Page parameter from /rf/wms/undobuild/frmUndoContainerBuild.jsp to 
                           /rf/wms/undobuild/frmUndoContainerBuild.jsp?RetainContainer=Y. 
 
When a user selects the ‘Undo Container Build’ option, the system will retain the     container as outbound container instead of converting it to an inventory container. The shipment and the container will be in the ‘Packed’ status, and the container and container details will not be deleted. 
Defect ID	234511
Case ID	Internal
Description	The Sterling Distributed Order Management: Configuration Guide, the Selling and Fulfillment Foundation: Product Concepts Guide, and the Sterling Selling and Fulfillment
                        Suite: Glossary Guide must be updated with the information about Reverse Authorization.
Solution: Added the following sections in the Sterling Supply Chain Applications Product Concepts Guide:
•	Reverse Authorization
•	Reversal of Authorization
•	Authorization Reversal Window
•	Configuration Options
•	Do Not Reverse
•	Reverse When Expired
•	Reverse Authorization Settlement Scenarios
•	Authorization Amount and Settlement Charge Match
•	Expired Authorization
•	Authorization Amount and Settlement Charge Differ
•	Manual Adjustment of Authorizations
Added a new field ‘Reversal of Authorization’ in Table 12-5, of Chapter 12, “Payment Systems”.
Added the following fields in Table 7-1, of Chapter 7, "Configuring Cross-Application Payment Components" of the Sterling Distributed Order Management Configuration Guide:
•	Authorization Reversal Strategy
•	Do Not Reverse
•	Reverse When Expired

Added the description of “reverse authorization” in the Sterling Selling and Fulfillment
Suite:Glossary Guide.
        Defect ID	235038
Case ID	Internal
Description	When a user performs the following steps, the system moves the shipment to "Sent To Node" status and deletes the shipment container details for the container:
1.	Creates multiple outbound shipments. 
2.	Packs each shipment into its respective container.
3.	Creates a load and adds both the shipments to the load.
4.	Builds the load container by adding the outbound containers to a load container.
5.	Performs the "Undo Container Build" action to remove the shipment container from the load container.
Defect ID	235043
Case ID	Internal
Description	When a user performs the following steps, the system moves the shipment to "Sent To Node" status and deletes the shipment container details for the container:
1.	Creates multiple outbound shipments. 
2.	Packs each shipment into its respective container.
3.	Creates a load and adds both the shipments to the load.
4.	Builds the load container by adding the outbound containers to a load container.
5.	Performs the "Undo Container Build" action to remove the shipment container from the load container.
Defect ID	235272
Case ID	00243741
Description	If there is large number of locations with many capacity constraints defined, the system takes a long time to release a wave. 

       Defect ID	235557
Case ID	00243857
 Description	When a configurable model returns only a top level SKU with no other SKU in the BOM configuration, the Sterling Web application stops with java.lang.StackOverflowError.

Hot Fix ID	9.0-HF10
Defect ID	220399, 233161
Case ID	00171512
 Description	The system should have a provision to replenish a dedicated location to the maximum quantity for an item during demand-based replenishment.
Solution: 
•	The SKU Location Dedication configuration has been enhanced to configure the minimum quantity and maximum quantity for the dedicated item.
•	The Pick Location Assignment (PLA) configuration has been enhanced to configure "Replenish the locations up to max quantity for dedicated items".
When a SKU dedicated location is set up with maximum quantity and "Replenish the locations up to max quantity for dedicated items" is enabled in PLA, the system replenishes the dedicated location to the maximum quantity for an item during demand-based replenishment.

Note: The requisite information has been updated in the Section "Pick Location Assignment Rule (Order Pick) Pop-Up Window" of the Sterling Warehouse Management System: Configuration Guide.

Defect ID	227379, 233162
Case ID	00191893
 Description	The system should have a provision to replenish a dedicated location to the maximum quantity for an item during min-max replenishment.
Solution:  
•	The SKU Location Dedication configuration is enhanced to configure minimum quantity and maximum quantity for the dedicated item
•	Location Inventory Monitor Alert repository is enhanced by providing a new alert "Inventory Below Minimum Qty"
When a SKU dedicated location is set up with minimum and maximum quantity and the location inventory monitor agent is triggered for "Inventory Below Minimum Qty" alert, the system replenishes the dedicated location to the maximum quantity for an item during min-max replenishment if the inventory in location is below the minimum quantity for the item.
		  
Note: The requisite information has been updated in the Section “Setting Up a Location's Dedication” of the Sterling Warehouse Management System: Configuration Guide.

Defect ID	229825
Case ID	00214051
Description	When a user performs the following sequence of actions, the system throws a "WMS000184: Zone doesn't track license plates" error:
1.	Configures a task type with pick into equipment and apply label.
2.	Configures a Forward pick zone which does not track LPN.	
3.	Configures Pick Location assignment and associates the task type configured in step 1.
4.	Creates a shipment, includes it in a wave and releases the wave so that the task is created from a zone as configured in Step 2.
5.	Logs in to Sterling Mobile Application and selects the "Outbound Pick" activity.
6.	Scans the equipment, location and label.
Defect ID	231629
Case ID	00215831
Description	When a user performs the following sequence of actions, the system should consider an SCM scanned in the pick criteria as a label and should not prompt a message for entering the label again in the SKU entry screen:
1.	Configures the task type to perform “Apply license plates during picking", "Pack While Pick", and "Use System Suggested Containerization".
2.	Creates a shipment, includes it in a wave, releases and containerizes the wave.
3.	Generates container labels for the shipment.
4.	Logs in to the Sterling Mobile Applications and selects the Outbound Pick Activity.
5.	Scans the SCM label in the criteria screen.
6.	Picks inventory for the suggested task associated with the SCM.
Defect ID	232115, 233163
Case ID	00230050
 Description	 If the inventory in a location goes below the minimum quantity for an item in the location, the system should replenish the dedicated location to the maximum quantity for an item during demand-based replenishment.
Solution:  
•	The SKU Location Dedication configuration is enhanced to configure the minimum quantity and maximum quantity for the dedicated item.
•	The Pick Location Assignment (PLA) configuration is enhanced to configure "Replenish the locations up to max quantity for dedicated items".
•	The PLA configuration is enhanced to configure "Replenish when inventory goes below minimum quantity for dedicated items".
When a SKU dedicated location is set up with the minimum and maximum quantity and "Replenish the locations up to maximum quantity for dedicated items" and "Replenish when inventory goes below minimum quantity for dedicated items" is enabled in PLA, the system replenishes a dedicated location to the maximum quantity for an item during demand-based replenishment if the inventory in the location goes below the minimum quantity for the item in the location.

Note: The requisite information has been updated in the Section "Pick Location Assignment Rule (Order Pick) Pop-Up Window" of the Sterling Warehouse Management System: Configuration Guide.
Defect ID	232539
Case ID	00232328
Description	When a user performs the following sequence of actions, the system does not the raise the SHIPMENT_PICKED event:
1.	Configures a task type with Voice Pick enabled.
2.	Configures Pick Location assignment and associates the task type configured in step 1 with it.
3.	Creates a shipment, includes in a wave, and releases the wave.
4.	Completes the task for the wave.

Defect ID	232604
Case ID	00229058
Description	The information about assigning a different colony for an existing organization with an enterprise role must be provided in the Selling and Fulfillment Foundation Multitenant Enterprise Guide.
Solution: The requisite information has been updated in the “Add an Enterprise to a Colony'' of the Selling and Fulfillment Foundation: Multitenant Enterprise Guide.
Defect ID	232684
Case ID	00230794
Description	The sender component in the Service Definition Framework in the Application Manager that puts the messages into a secured JMS queue does not honor all the security parameters set in the JMS Security Properties tab. The receiver component that receives the messages from a secured JMS queue does honor all the security parameters set in the JMS Security Properties tab.
Solution: Both sender and receiver components are working in the similar manner. The sender component also honors the JMS parameters set provided in the  JMS Security Properties tab in the Application Manager.

Defect ID	233000
Case ID	00234070
Description	In the Websphere application server, the EAR deployment fails because a regular IBM jar for JMS containing "ejb" which is installed using Install3rdparty utility, the build EAR script assumes this jar to be an EJB. Due to these reasons an improper EAR is created.

Solution:  A new check has been added that will add only valid ejb jar to the application.xml.

Defect ID	234026
Case ID	00237463
Description	When a user performs the following sequence of actions, the system displays the tasks of all the waves:
1.	Creates a shipment, includes in wave W1, and releases the wave.
2.	Creates a shipment, includes in wave W2, and releases the wave.
3.	Logs into Sterling Application Console and views the wave summary for W1.
4.	Navigates to the “Wave Summary” screen and clicks "No Of SKUs" hyperlink.
Defect ID	234058
Case ID	00217532
Description	When a user performs the following sequence of actions, the system does not allow a user to associate a Location Size Code to the user:
1.	Configures more than 75 Location Size Codes for node N1.
2.	Configures more than 75 Location Size Codes for node N2.
3.	Creates an equipment type for N1 and associates one of the location size code created in step 1.

Defect ID	234066
Case ID	00215637
Description	When a user performs the following sequence of actions, the system must consider an LPN label scanned in the ‘Case/SKU’ entry as printed label and should not prompt a message for entering the UOM of an item:
1.	Creates a Purchase Order (PO) for an item.
2.	Clicks the ‘Report/Record Receipt’ action to start the receipt for the order created in step 1.
3.	Prints the LPN labels for the PO.
4.	Generates LPN labels for the PO by selecting "Print Case/Pallet LPN" menu.
5.	Logs in to Sterling Mobile Application and selects the Receive Activity.
6.	Scans the PO and Location during receiving.
7.	Scans the printed LPN label in the Case/SKU entry screen.
Defect ID	234067
Case ID	00215829
Description	When the following conditions are met, the system must consider a single-SKU LPN pick as a full LPN pick and should not prompt a message for entering the SKU details.
•	If the "Apply license plates during picking" is enabled for the task type.
•	If the picked LPN is a system-suggested LPN for the task.
•	If the quantity of the LPN is less than or equal to the quantity of the task.

Defect ID	234172
Case ID	00228842
 Description	There should be a provision to prevent the system from creating pallet containers during pre-pick system containerization for a parcel shipment that has an item with ‘PALLET’ as an alternate Unit of Measure (UOM) configured.
Solution:  A new property "yfs.prevent.palletlabel.for.parcelshipment.tasktypelist" has been provided. A user must configure this property with the list of comma separated task types to prevent the system from generating pallet labels. If the task for which the containers are being created is associated to this task type list, the system will not generate pallet labels for the same.
Defect ID	234617
Case ID	00241111
 Description	The consolidateToShipment API does not propagate special services from order to shipment.
Defect ID	234737
Case ID	00241636
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	234760
Case ID	00242429
 Description	The consolidateToShipment API does not consolidate order releases to a shipment based on the special services of the order release.
Defect ID	234939
Case ID	00241990
 Description	The application must support the "ON_SUCCESS" event for the CANCEL_TO_SHIPMENT transaction of transfer order.

Defect ID	234977
Case ID	00242929
 Description	The consolidateToShipment API does not populate an extended attributes from an order to shipment.
Defect ID	235010
Case ID	00243545
 Description	The system should have a provision to replenish a dedicated location to the maximum quantity and rounded off to an alternate Unit of Measure (UOM) for an item during demand-based replenishment.
Solution:  
•	The SKU Location Dedication configuration is enhanced to configure the minimum quantity and maximum quantity for the dedicated item.
•	The Pick Location Assignment (PLA) configuration is enhanced to configure " "Replenish the locations up to max quantity for dedicated items".
When a SKU dedicated location is set up with maximum quantity and "Replenish the locations up to max quantity for dedicated items" is enabled in PLA and round off to alternate UOM is configured in Replenishment Strategy, the system replenishes a dedicated location to the maximum quantity with round off for an item during demand- based replenishment.
Defect ID	235012
Case ID	00243551
Description	When the following conditions are met, the system must consider a single-SKU and LPN pick as a full LPN pick, and the system should not prompt a message for entering the SKU details.
•	If the "Apply license plates during picking" is enabled for the task type
•	If the picked LPN has the same SKU and quantity as the system-suggested LPN for the task.
•	If the quantity of the LPN is less than or equal to the quantity of the task.
Defect ID	235198
Case ID	00239185
 Description	While configuring the Outbound Pick task type, the system does not provide an option to associate the resource to the task type.

Hot Fix ID	9.0-HF9
Defect ID	227128
Case ID	Internal
 Description	The system should mark one of the quotes associated with an opportunity as the primary quote. 
Solution:  The system behavior is enhanced to identify the first quote created for an opportunity as a primary quote. There can be only one primary quote for each opportunity. If a user wants to change the primary quote to some other quote of an opportunity, the user has to call the manageOpportunity API.
Defect ID	227874
Case ID	Internal
 Description	There is an event in order fulfillment that is raised whenever the status of an order is changed. This event is not exposed for quotes.
Solution: Factory setup has been provided so that the event is available for quotes.
Defect ID	227980
Case ID	Internal
 Description	When browsing the entitlement screens in Sterling Business Center, the getEntitlementRuleList API writes input and output XMLs to the log file when the log_level is in the INFO mode.
Defect ID	228855
Case ID	Internal
 Description	The Item Details > Manage Attributes screen launches slowly when there are items with attributes that have 3000 allowed values. 

Solution: A new API getAttributeallowedValueList has been introduced that returns a list of allowed attribute values for a given attribute. It also supports pagination to handle attributes with large number of allowed values.
Defect ID	229503
Case ID	Internal
 Description	Various performance related fixes are made to enhance the performance of the manageEntitlementRule API when deleting the entire entitlement rules or when deleting the entitlement rule details with large number of entitlement details items.
Defect ID	229792
Case ID	Internal
 Description	The getItemListForOrdering API performance is very slow when accessing items with assigned attributes that are configured to have more than 3000 allowed values.
Defect ID	230368
Case ID	Internal
 Description	The Search Catalog Index incremental build does not update the facet list (attributes marked to be used for filter) correctly. Only facets for items that are changed are included. Facets for items that have not been updated are not included in the facet list after an incremental build.
Defect ID	230671
Case ID	Internal
 Description	It is necessary to limit attribute allowed values returned/shown on the Web Channel user interface.

Solution: The searchCatalogIndex API is enhanced to return the number of assigned attribute values per facet based on the business rule “Number of Assigned Attribute Values To Display For Search Facets”. This is a catalog organization level rule and the default value is 8.

Note: The requisite information has been updated in the Section “Defining Catalog Rules” of the Selling and Fulfillment Foundation: Catalog Management Configuration Guide.
Defect ID	230956
Case ID	Internal
 Description	Data security has been added to the manageEntitlementRuleAssignment API and removed from the getEntitlementRuleList and getAssignedEntitlementList APIs.
Defect ID	231206
Case ID	Internal
    Description	The getItemDetails and getCategoryDetails APIs do not return the TotalNumberOfRecords attribute under the <AttributeAllowedValueList> element if the <AttributeAllowedValue> element is removed from the output template.
Defect ID	231507
Case ID	Internal
 Description	Performance improvement fixes are made to the searchCatalogIndex API, building of catalog index, and loading of catalog index cache when a catalog contains attributes more than 3,000 allowed values.
Defect ID	232435
Case ID	Internal
 Description	Users with login IDs that have 40 to 50 characters are unable to log in to the system when the installation rule “Allow the display user ID to be used across enterprises” is turned off.
Defect ID	232510
Case ID	00232813
 Description	When an item attribute is associated with a value using manageItem API, the system takes too long for validating if this is an allowed value for that attribute.

Solution: This validation is made optional with the help of the "ValidateAdditionalAttributeValues" API flag. For more details about this flag, please refer to the Selling and Fulfillment Foundation: Javadocs of the manageItem API.
Defect ID	233186
Case ID	Internal
 Description	In Sterling Business Center, the following screens launch slowly:
Pricing Administration module
1.	Pricelist Summary
2.	Pricing Rule Details
3.	Coupon Details
Item Administration module - If there are text attributes with large number of allowed values, the following screens launch slowly: 
1.	Manage Properties in attribute management 
2.	Manage Attribute Values for an item 
3.	Manage Attribute Assignment for category in catalog management
Solution: 
The Pricing Administration module has been enhanced to improve the performance of the screen.
The Item Administration module has been enhanced to improve the performance of the screen. Additionally, the following screens have been modified:
•	Manage Properties - The allowed values are displayed in a grid with pagination support.
•	Manage Attribute Values and Manage attribute assignment – 
o	For a text attribute with less than or equal to 30 allowed values, the values are displayed in a drop down.
o	For a text attribute with more than 30 allowed values, a text field with a lookup icon is displayed. This lookup icon can be used to launch the allowed value search pop-up window from which the user can select the values.

Hot Fix ID	9.0-HF8
Defect ID	228894
Case ID	00197160
 Description	The following columns must be resized:
1. In the YFS_USER table, the DISPLAY_USER_ID column must be increased to 150 bytes. 
2. In the YFS_ITEM table, the SHORT_DESCRIPTION column must be increased to 200 bytes
3. In the YFS_ITEM table, the DESCRIPTION column must be increased to 1000 bytes.
4. In the YFS_ORDER_KIT_LINE, YFS_ORDER_LINE, and YFS_SHIPMENT_LINE tables, the corresponding mappings of the item table must be resized.

After applying this hot fix, the behavioral changes are as follows:
1.	The application supports creation of Login IDs up to 150 characters when the installation rule "Allow the display user ID to be used across all enterprises" is enabled.
2.	The user interface in Sterling Business Center and the Applications Manager do not support the resized columns.
3.	Users with login ID length between 40 and 50 characters cannot log in to the application.

Defect ID	231308
Case ID	00218452
 Description	When the changeOrder API is invoked, line adjustments overridden by the YPMOverrideGetOrderPriceUE are not reflected on the order.

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

Hot Fix ID	9.0-HF7
Defect ID	216937
Case ID	Internal
 Description	After creating and packing a shipment, when a user navigates to the “Container Details” screen, the details corresponding to the “Qty” and “Packed qty” fields are shifted to the left of the column.
Defect ID	216941
Case ID	Internal
Description	When a user runs the CREATE_WAVE_SHIP_GROUP agent, the system displays an “ORA-1841” error message. 
Solution: Query should not have SYSDATE in quotes.
Defect ID	216945
Case ID	Internal
 Description	After creating and packing a shipment, when a user navigates to the “Container Details” screen, the “Description” field is not populated in the “Container Details” screen.
Defect ID	219616
Case ID	Internal
Description	When a user performs the following sequence of actions, in the “Adjustment Cost” screen the adjustment quantity and adjustment cost are displayed incorrectly:
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	224666
Case ID	00191982
Description	Catalog Search must be enhanced for handling customer entitlement rules with large number of individual items.
Solution: In Release 9.0, entitlement rules can support a large number of individual items. To support entitlement rules that include large numbers of items, the index building functionality for the Catalog Search has been enhanced. 

 Changed Behavior Between 9.0 and Earlier Releases: 
If individual items are included in existing entitlement rules, the Catalog Search index must be rebuilt.  After the index is rebuilt, it contains a list of primary keys of the entitlement rule details to which an item entity belongs.

Known Issues: When entitlement rules have large number of items and getAssignedEntitlementList and manageEntitlementRule APIs are called with default output templates, application server crashes.

Workaround: Remove the EntitlementRuleDetailItem element from the output template of the getAssignedEntitlementList and manageEntitlementRule APIs.

Note: The requisite information has been updated in the Section “Extending a Catalog Search” of the Selling and Fulfillment Foundation: Extending the Database Guide and Section "Catalog Index Building" of the Catalog Management Concepts Guide.
Defect ID    229955
Case ID     Internal
Description     When a user performs the following sequence of actions, the system throws a null pointer exception:
1.	Creates an inbound order.
2.	Creates an inbound shipment.
3.	Creates a load for the shipment without a load stop.
4.	Purges the order.
5.	Calls the changeshipment API or marks the shipment as delivered.
Defect ID	230447
Case ID	00218121
Description	When a user performs the following sequence of actions, the system displays an "YFS10379: Template not found" error message while raising an event and the transaction rolls back:
1.	Configures the Routing Guide rules.
2.	Configures the ON_SUCCESS event for the ROUTE_SHIPMENT.0001 transaction.
3.	Creates an outbound shipment and moves the shipment to ‘Awaiting Routing’ status.
4.	Executes the ROUTE_SHIPMENT.0001 transaction.

Hot Fix ID	9.0-HF6
Defect ID	227209
Case ID	00166855
 Description	An enhancement should be provided so that a user can configure the ‘Wave Size Constraint’ on ‘Number of Shipment Lines’.
Defect ID	228936
Case ID	Internal
Description	During a hot fix installation, the factory setup installation during the hot fix installation does not honor the LOAD_FACTORY_SETUP property in sandbox.cfg.
Solution: If the LOAD_FACTORY_SETUP property in sandbox.cfg is set to ‘false’, the factory setup will not be installed during the hot fix installation.
Defect ID	219771
Case ID	Internal
    Description	When a document processing is in progress the system displays "Not able to get a Connection" SQLException error message.
Defect ID	230574
Case ID	00220795
 Description	When the manageEntitlementRuleAssignment API is invoked the system throws "API Security Violation" error message, when the api.security.enabled property is set to ‘Y’.
Defect ID	230648
Case ID	Internal
Description	The information about configuring the ‘Wave Size Constraint’ on ‘Number of Shipment Lines’ must be provided in the Sterling Warehouse Management System: Configuration Guide.
Solution: The requisite information has been included in the "Defining Wave Size Constraints" and "Creating Wave Size Constraints" topics of the Sterling Warehouse Management System: Configuration Guide.

Hot Fix ID	9.0-HF5
Defect ID	213579
Case ID	Internal
Description	The information about both Oracle 10g and 11g being supported on a single node or 2 Node RAC environment must be removed from Sections 5.2.3, “Using an Oracle Database Server” and  6.5.3, “Using an Oracle Database Server (Windows)” of the Selling and Fulfillment Foundation: Installation Guide.
Solution: The Selling and Fulfillment Foundation: Installation Guide has been updated with the requisite information.
Defect ID	224623
Case ID	Internal
Description	The application must be enhanced to support the 'Stacked Column 3D Line Dual Y' combination charts in the YFCChartTypes class.
Defect ID	225152
Case ID	Internal
Description	The link to Section 4.2.6, "Defining Transactions” is not working in the following documents:
•	Catalog Management: Configuration Guide
•	Sterling Distributed Order Management: Configuration Guide
•	Sterling Global Inventory Visibility: Configuration Guide
•	Sterling Logistics Management: Configuration Guide
•	Sterling Reverse Logistics: Configuration Guide
•	Sterling Supply Collaboration: Configuration Guide
•	Sterling Warehouse Management System: Configuration Guide
Solution: In all these documents, the link has been deleted and reference to the "Defining Transactions” section of the Selling and Fulfillment Foundation: Application Platform Configuration Guide has been provided.
Defect ID	227207
Case ID	00169626
Description	An additional screen must be provided in the “Shipping Pallet Build” activity screen of the Sterling Mobile Application to display the shipment that is built through the shipping pallet build activity.

Defect ID	227208, 229061
Case ID	00191262
Description	The application must be enhanced to support 6 new Check Digit Algorithms.
Solution: The application has been enhanced to support 6 new Check Digit Algorithms.
The requisite information has been included in the “Configuring Shipping” topic of the Sterling Warehouse Management System: Configuration Guide.
Defect ID	227898, 229062
Case ID	00206044
Description	The application must be enhanced to allow a user to generate the PRO Number without any Check Digit Algorithm.
Solution: A user can select the "NO CHECK DIGIT" option to generate the PRO Number without any Check Digit.
The requisite information has been included in the “Configuring Shipping” topic of the Sterling Warehouse Management System: Configuration Guide.

Defect ID	228435
Case ID	Internal
Description	The copyright statement in the minifed javascript files of the Sterling Business Center is incorrect.
Defect ID	230032
Case ID	Internal
Description	All the documents provided in this hot fix must be updated with the new logo.
	For the entire set of documents that have new logo go to; http://www.sterlingcommerce.com/Documentation/MCSF90/PDFs.htm.

Hot Fix ID	9.0-HF4
Defect ID	215057
Case ID	Internal
Description	While starting the application server for Sterling Web Channel application, catalog information is cached into the memory during initialization. When the number of allowed values for the attributes that are used for filtering is very high, system memory consumption increases and it may run out-of-memory.
Solution: To avoid the out-of-memory issue support for a disk persistent caching mechanism called EhCache has been provided.
For more information refer the “Configuring Cache for Catalog Search Index” topic of the Selling and Fulfillment Foundation Properties Guide.
Defect ID	223084
Case ID	Internal
Description	The hidden variables are getting displayed in the User Interface on multi select API screen.
Defect ID	223504
Case ID	Internal
Description	When the “StationID” information is passed in the input of the addToContainer API, the system does not pass the information to the following events:
•	ON_SHIPMENT_PACK_COMPLETE
•	ON_SHIPMENT_PACK_PROCESS_COMPLETE
•	ON_CONTAINER_PACK_COMPLETE
•	ON_CONTAINER_PACK_PROCESS_COMPLETE
•	ON_SUCCESS
Defect ID	223513
Case ID	Internal
Description	When a user receives a serialized item against a shipment with expected segment and segment type information, the system displays "Inventory for the SKU does not exist in the location or case/pallet to perform the inventory operation" error message.
Defect ID	225144
Case ID	Internal
Description	The Selling and Fulfillment Foundation: Product Concepts Guide must be updated with the information about order taxes modification.
Solution: The requisite information has been included in the “Invoicing” topic of the Selling and Fulfillment Foundation: Product Concepts Guide.
Defect ID	225148
Case ID	Internal
Description	The Selling and Fulfillment Foundation: Installation Guide must be updated with the information about runtime utilities.
Solution: The requisite information has been updated in the Selling and Fulfillment Foundation: Installation Guide.
Defect ID	225639
Case ID	Internal
Description	The Sterling Application Manager User Interface must support addition of new resources under the Applications > Application Platform > Presentation > Resources for the Sterling applications that are built on the Sterling Foundation.
Defect ID	226598
Case ID	Internal
Description	The reference implementation of the YCDGetAppeasementOffersUE user exit in Sterling Call Center and Sterling Store must be enhanced to make the appeasement offer lists configurable.  These lists are displayed in the “Appeasement Offer” screen.
	
Solution: A new “ycd_appeasement_variable.properties” file has been added. The reference implementation of the YCDGetAppeasementOffersUE user exit has been enhanced to read the values of different offer types that must be from the “ycd_appeasement_variable.properties” file. 

The following properties are available:

•	FLAT_AMOUNT_ORDER=20
•	PERCENT_ORDER=12
•	PERCENT_FUTURE_ORDER=15,20,25
•	YCD_PREFERRED=PERCENT_FUTURE_ORDER
•	VARIABLE_AMOUNT_ORDER=Y

Notes: 
•	If there are multiple values for an offer type, they must be separated by a comma, for example, PERCENT_FUTURE_ORDER=15,20,25

•	The value of the YCD_PREFERRED property determines which offer type must be displayed as the default offer in the “Appeasement Offer” screen.
If VARIABLE_AMOUNT_ORDER=Y, the appeasement type will be displayed in the “Appeasement Offer” screen.

•	If a user does not want any offer type, the user must set the value of the corresponding appeasement offer type properties as blank. However, must ensure that no property is removed or commented out.
Defect ID	227093
Case ID	Internal
Description	When a user performs the following sequence of actions, the system creates a credit memo with an incorrect discount amount:

1.	Uses the implementation of YCDGetAppeaseOfferUE provided in the reference implementation.
2.	Searches for an Order that is eligible for appeasement, and the Order Total is $100.
3.	Clicks on “Customer Appeasement” from the Related Task panel.
4.	Selects the “Select Specific Lines for Appeasement” option.
5.	Selects a line with LineTotal as $50 and clicks Next.
6.	Select the “PERCENT_ORDER” type Appeasement, 10% on the Order Total that is $5.
7.	Clicks Next.
8.	Clicks on the “View All Invoices” task and opens the Credit Memo created in Step 6.
The Credit Memo is created for the $10 instead of $5.
Defect ID	227417
Case ID	00205783
Description	When a user runs the Configuration Deployment Tool (CDT), it does not show any differences for the YFS_GRAPH_UI table for certain records that have graph type as 'EventCondition'.
Defect ID	227513
Case ID	Internal
Description	When the following conditions are met, the releaseMoveRequest API throws ‘Class Cast’ exception;
1.	Configures an item I1 with UOM as EACH.
2.	Configures an alternate UOM as Case for the above item with conversion quantity as 8.
3.	Configures zone Z1 with location L1 associated with size code S1 having capacity constraint as 10 each.
4.	Configures the putaway preference that points to the above configured zone.
5.	Adjusts 2 quantities of I1 in location L1.
6.	Adjusts 8 quantities of I1 in another location.
7.	Creates a move request for item I1 for 8 quantities from the location L1.
8.	Releases the move request.

Hot Fix ID	9.0-HF3
Defect ID	217612
Case ID	Internal
Description	When the system test is run for more than 6 hours and automation tests are run on the Sterling Call Center and Sterling Store client for tasks such as the create order, cancel order, order search, item search, and so on, the application server crashes due to a null template being passed.
Defect ID	218097
Case ID	Internal
Description	When the verifyAddress API is called using the default implementation of the YCDVerifyAddressWithAVSUE user exit and the verifyAddressWithAVS.xml template, the ”IsCommercialAddress” and “AddressID” attributes are not returned in the output XML of the API because these attributes are not processed by the user exit.
Solution: The “AddressID” and “IsCommercialAddress” attributes have been added to the verifyAddressWithAVS.xml template.
Defect ID	218667, 218671, 218672
Case ID	Internal
Description	A security issue has been identified that may allow a cross-site scripting (XSS) attack in the Sterling Selling and Fulfillment Suite.
Solution: This security issue has been rectified in this hot fix.
Defect ID	219063
Case ID	Internal
Description	The URL of the labels is not returned in the output XML of the following APIs even when the “PrinterType” field is configured as Client on the AgileElite shipment server:
•	reprintCarrierLabel
•	addContainerToManifest
•	getTrackingNoAndPrintLabel

Solution: The “PierbridgeLabelURL" attribute, that is used to determine the URL of the labels, is returned in the output of the APIs mentioned above. 
Defect ID	223830
Case ID	Internal
Description	A user is not able to retrieve any records from a Data Access Policy enabled table, if ‘RememberMe’ or ‘Anonymous’ user feature is enabled.

	Solution: The SQL construction for ‘Anonymous’ user has been restructured, so that the SQL is formed correctly when the ‘RememberMe’ feature is enabled.
Defect ID	224615
Case ID	00193324
Description	If there are a large number of locations with many capacity constraints defined, the system takes a long time to create putaway tasks. 
Defect ID	224916
Case ID	00195975
Description	When a user attempts to pick multiple pallets that are received for putaway to various locations, a "No Open Task For the Pallet" error is thrown when a user enters or scans a different Pallet ID with a different task type than the one populated in the Sterling Mobile Application.
Defect ID	226575
Case ID	Internal
Description	The Catalog Management: Concepts Guide must be updated with a recommendation to use item-based entitlements to exclude a small set of items.
Solution: The requisite information has been included in the topic "Customer Entitlement Rules" of the Catalog Management: Concepts Guide.
Defect ID	224687
Case ID	Internal
Description	The Selling and Fulfillment Foundation: Extending the Database Guide must be updated with the information about the unsupported extending database.
Solution: The requisite information has been updated in the Selling and Fulfillment Foundation: Extending the Database Guide.
Hot Fix ID	9.0-HF2
Defect ID	217536
Case ID	00162974
Description	If an enterprise inherits configuration from another enterprise, the child enterprise will also inherit customer entitlements from the parent enterprise. The assignment of customer entitlements to customers must happen at the same enterprise level.
Defect ID	217837
Case ID	00165037
Description	If an organization is inheriting configuration from another organization and the child organization is a catalog organization, the child organization cannot configure and use its own customer entitlement rules. It can only use the customer entitlement rules that the parent has configured, if the parent organization is a catalog organization.

Solution: Organizations can inherit customer entitlement rules from other enterprises. To enable inheritance by enterprises of customer entitlement rules, ensure that the Inherit Configuration from Enterprise option is selected in the Selling and Fulfillment Foundation Platform application.  If you enable this feature and are upgrading from an earlier release in which customer entitlement rules were configured by a child enterprise, the child enterprise’s customer entitlement rules are no longer available in Business Center. 
Defect ID	217838
Case ID	00165062
Description	Buyer users do not have the rights to order on behalf of customers from other divisions and storefronts. 

Solution: The data access policy for buyer users has been enhanced to allow the assignment of buyer users to a set of customers or to a set of customers and child customers. This type of buyer user customer assignment allows customers to place orders on behalf of other customers. 
 
For more information refer to the section “Customer Management”, in the Selling and Fulfillment Foundation: Product Concepts Guide.	
Defect ID	217840
Case ID	00165065 
Description	Customer cannot search the catalog for a product that has two different SKUs.

Solution:  The index building process for the catalog search feature has been enhanced to allow the retrieval of attribute information from external sources. Additionally, the searchCatalogIndex API has been enhanced to allow retrieval of stored attribute information from the index file directly.
Defect ID	217841
Case ID	00165072
Description	Customers can use only the data access rules provided by Selling and Fulfillment Foundation. 

Solution: Selling and Fulfillment Foundation provides the following new user exits that allow you to use your own data access rules instead of the Selling and Fulfillment Foundation access rules: 

•	YSCGetExternalDataAccessPolicyOnReadUE
•	YSCShouldAccessPolicyBeAppliedOnUpdateUE
Defect ID	218057
Case ID	Internal
    Description	The Consolidate Additional Inventory Agent occasionally crashes due to memory leaks.
Defect ID	218656
Case ID	Internal
Description	Null Pointer exceptions are encountered in the Sterling Web Channel and Sterling Multi Channel Fulfillment Suite application servers when a test is run for long duration.
Defect ID	218991
Case ID	Internal
Description	The Data security functionality must not be exposed unless it is required by the customers.
Defect ID	219133
Case ID	Internal
    Description	When a user performs the following sequence of actions, the system does not allow a different receivingNode other than the one in the release line:
1.	Creates an order with a released order line having Node1 as the receivingNode.
2.	Calls the createShipment API to create a shipment and sets the receivingNode of the shipment line to Node2.

Solution: The 'OverrideReceivingNode' attribute has been exposed for the createShipment API. If OverrideReceivingNode='Y' is passed, the system will pass different receiving nodes from that of the release line while creating the shipment. The node that is passed must be a valid node.

Defect ID	219211
Case ID	Internal
    Description	When a user performs the following sequence of actions, the createShipment API displays a null pointer exception:
1.	Creates two orders with different SellerOrganizationCodes.
The orderLines of these orders must not have any Receiving Nodes.
2.	Schedules an order and releases it.
3.	Creates a shipment and includes both the orders. Pass OverrideReceivingNode="Y" at the shipment level

Solution: The OverrideReceivingNode flag has been exposed. If OverrideReceivingNode="Y" is passed at the shipment level the createShipment API does not throw null pointer exception.

Defect ID	219418
Case ID	Internal
Descriptions	In the Business Center, the ‘Customer’ search pop-up window do not display the list of customers that does not have the ‘Bill To Address’ information.
Defect ID	219443
Case ID	Internal
Description	The Release Order agent stops processing after running for a while and locks the YFS_INVENTORY_ITEM table.
Defect ID	219649	
Case ID	Internal
    Description	If the getPage API is called simultaneously by multiple threads, the getPage API sporadically throws NullPointerException.

Defect ID	219737
Case ID	Internal
Description	When a user runs the order purge agent it does not process the orders correctly if the purge agent is run before the actual available date for that order. The Order Release Status records get purged but the order never gets purged.

Defect ID	219928
Case ID	Internal
    Description	When a user performs the following sequence of actions, the YFS_INVENTORY data is not getting purged:
1.	Sets up inventory purge agent.
2.	Sets records in the YFS_INVENTORY table that are in purgeable status.
3.	Runs the inventory purge agent.

Defect ID	220143
Case ID	Internal
    Description	During the application system test run, the agents display "weblogic.jms.common.AlreadyClosedException".
Defect ID	220514
Case ID	Internal
    Description	The entity framework must be enhanced to set the time out session on the MS SQL queries while creating the return record queries.
Defect ID	221120	
Case ID	00178229
    Description	When a user uses jvmRoute in jboss for session stickiness, the application throws an error about non-conformed JSESSIONID because of the appended jvmRoute to JSESSIONID.
Defect ID	221473	
Case ID	Internal
    Description	The CacheManager throws a NullPointerException.
Defect ID	221476	
Case ID	Internal
    Description	The StuckThread exception is thrown if many users try to log in to the Sterling Web Channel application concurrently.

Defect ID	221671
Case ID	00180360
Description	When a user creates a move request at the LPN level, the system does not consider the capacity constraints of the location that are defined.

Defect ID	221940
Case ID	00180419
    Description	The system must honor the trigger percentage configured at the zone level during putaway, if the zone is configured under the putaway preferences. 
Defect ID	221941, 223400	
Case ID	00180414
    Description	The system must pass the Inventory Type, Original Inventory Type, Putaway Quantity, and Hold Quantity attributes in the WMSCanLocationBeSuggestedUE user exit during putaway.

Defect ID	222108
Case ID	00182969
    Description	The system fails to release a Move Request for multi-SKU Pallet Putaway to a location that has location capacity constraints defined.

Defect ID	222401
Case ID	00184299
    Description	After completing the first-step putaway tasks, the system does not correctly stamp the “Task Type” for the second-step putaway tasks.
Defect ID	223092
Case ID	00180419
Description	The Sterling Warehouse Management System: Configuration Guide must be updated with the information that system must not honor the trigger percentage configured at the zone level during putaway, if the zone is configured under the putaway preferences.
Solution: The requisite information has been included in the Chapter, "Configuring Warehouse Layout ", in the Sterling Warehouse Management System: Configuration Guide.

Hot Fix ID	9.0-HF1
Defect ID	212725
Case ID	Internal
Description	In the Selling and Fulfillment Foundation: Properties Guide, the description of the property security.propertyencrypter.class incorrectly uses the form “.encrypted” instead of “encrypted:” in the following sentence:
	Properties starting with “.encrypted” are automatically decrypted at run-time.

	Solution: The sentence has been corrected, as follows:
Properties starting with “encrypted:” are automatically decrypted at run-time.
Defect ID	213147
Case ID	Internal
Description	The Selling and Fulfillment Foundation: Secure Deployment Guide is missing required JAR names in the client side CLASSPATH in the section, “Securing JMS Queues”.

	Solution: Required JAR names have been added to the client side CLASSPATH in the section, “Securing JMS Queues”.
Defect ID	214224
Case ID	Internal
Description	The Catalog Management Concepts Guide is missing information about models, configurable items, and preconfigured items, and how they relate to kit items.

	Solution: The Catalog Management Concepts Guide now contains a section about “Models, Configurable Items, and Preconfigured Items,” and how they relate to kit items.
Defect ID	214698
Case ID	Internal
Description	In case of negative inventory adjustments in an adjustment sequence, the inventory audits are incorrectly updated when one of the locations in the sequence is a virtual location. For example, if five units are removed from the inventory when the initial supply quantity is zero, the supply is incorrectly updated as +5 instead of -5.
Defect ID	215235
Case ID	Internal
Description	The Selling and Fulfillment Foundation: Performance Management Guide is missing information about tuning guidelines for the Sterling Web.

	Solution: The Selling and Fulfillment Foundation: Performance Management Guide has a new Chapter 26, “Sterling Web Tuning Guidelines,” that describes API security, application server heap sizing, optimizing static content, and enabling compression.

Defect ID	215253
Case ID	Internal
Description	After reconfiguring a physical kit on an order in pending change mode, subsequent modifications to the line in pending change mode will throw a “Line not found” error. 
Defect ID	215486
Case ID	Internal
Description	The Selling and Fulfillment Foundation: Performance Management Guide that is compiled as part of context-sensitive help is out-of-sync with the content in the PDF, which is available on both the Online Library (http://www.sterlingcommerce.com/Documentation/MCSF90/homepage.htm) and the DVD.

	Solution: Both formats of this manual are now in sync and contain the same content.
Defect ID	215607
Case ID	Internal
Description	In a hierarchy of categories, when an item belongs to a child category of an unpublished category, the item displays in Sterling Web. In this scenario, the item should not display.

Defect ID	215619
Case ID	Internal
Description	When an item belongs to two categories, if one category is published and the other category is not published, the item will appear while browsing the parent category of the unpublished category.
Defect ID	215680
Case ID	Internal
Description	In the Selling and Fulfillment Foundation: Customizing APIs Guide, Section 5.2 contains a note with an incorrect path name for providing the template.api file during service definition.

	Solution: The note now contains the correct path name.
Defect ID	215735
Case ID	Internal
Description	In the Local Documentation Library, the topic title, “Configuring the Look and Feel of the Sterling Mobile Application" of the Customizing User Interfaces for Mobile Devices is incorrect.

                        Solution: The topic title has been changed to "Configuring the Sterling Mobile Application User Interface Components".
Defect ID	215778
Case ID	Internal
Description	In the Selling and Fulfillment Foundation: Product Concepts Guide, 
Section 7.12.1 is missing information about item validation.

	Solution: Section 7.12.1 now contains a note with item validation information about unpublished and expired items, as well as items that cannot be sold separately.
Defect ID	215906
Case ID	Internal
Description	When a computed attribute is assigned to a category, the application incorrectly displays an editable "Value" field and permits a user to enter a value for this computed attribute in the “Value” field.
Defect ID	215964
Case ID	Internal
Description	In the Selling and Fulfillment Foundation: Customization Basics Guide, 
Section 5.3 contains a note with an incorrect path name for storing database extension files.

	Solution: The note now contains the correct path name.
Defect ID	216107
Case ID	Internal
Description	The application incorrectly permits a user to modify the values of attributes that inherit default values in the Manage Attribute Values screen, and save them even if the user does not click the Override hyperlink.
Defect ID	216373
Case ID	Internal
Description	In the Selling and Fulfillment Foundation: Customization Basics Guide, 
Section 5.2 contains a note with an incorrect path name for providing the template.xsl file during service definition.

	Solution: The note now contains the correct path name.
Defect ID	216384
Case ID	Internal
Description	When a user tries to add a date range for a price list and save the changes, the application displays an "Invalid Date Format" error message. The user can add a date range for a price list by clicking the Create hyperlink or by clicking the Set Date Based Prices option from the More Actions menu in the Price List Summary screen.
Defect ID	216457
Case ID	Internal
Description	The System Management Administrator (SMA) login page contains incorrect copyright information.
Defect ID	216483
Case ID	Internal
Description	When adding a configurable product without any configuration to an order in pending change mode, a “YFS: No Kit Lines Found” error is thrown. 
Defect ID	216496
Case ID	Internal
Description	From the Business Center application, you cannot mark a derived attribute to be used for filtering. 
Defect ID	216539
Case ID	Internal
Description	In the Selling and Fulfillment Foundation: Application Platform Configuration Guide, Section 5.3 is missing information. The section needs to state that Selling and Fulfillment Foundation does not support teams with organizations across colonies.

	Solution: Section 5.3 now contains a note clarifying that enterprises and nodes assigned to a team must belong to the same colony as the team owner or creator organization.
Defect ID	216549
Case ID	Internal
Description	The Business Center: Item Administration Guide must be updated with information about the format of the URL context parameter value that is provided in the web.xml for Visual Modeler.
Solution: The format of the URL context parameter value is updated in the topic, "Initial Configurations by System Administrators", of the Business Center: Item Administration Guide.
Defect ID	216553
Case ID	Internal
Description	The Business Center: Item Administration Guide must be updated with information about the initial URL configuration setup used to preview the item details.
Solution: The initial URL configuration setup information is added in the topic, "Configuration to Preview Item Details", in the Business Center: Item Administration Guide. Additionally, information about the YCMGetWebChannelItemPreviewURLUE user exit, which can also be implemented to preview the item details, is added in this topic.
Defect ID	216560
Case ID	Internal
Description	The Visual Modeler: Application Guide should be updated with information that the storefront that is created using the Visual Modeler is meant only for model administration purposes. Additionally, in Chapter 44 “Creating Product Models”, the steps that are provided to create a configurable product are incorrect.
Solution: The Section “Storefront Administration” in Chapter 35 “Channel Administration”, and Chapter 44 “Creating Product Models” of the Visual Modeler: Application Guide have been updated with the required information.
Defect ID	216634
Case ID	Internal
Description	When the getNodeInventory API returns inventory for multiple organizations, the Item element (under the path /NodeInventory/LocationInventoryList/LocationInventory/InventoryItem/) is not shown in the output XML.
Defect ID	216672
Case ID	Internal
Description	There is a performance issue in DB2 when the validateItemForOrdering API is called on a large order during BOM XML validation.
Defect ID	216674
Case ID	Internal
Description	The getInventorySnapShot API fails in a multischema environment with the error “ORA-00942: table or view does not exist”.
Defect ID	216719
Case ID	Internal
Description	In the "Postponing Item Creation" section of the Sterling Warehouse Management System: Concepts Guide, the hyperlink provided for “Figure 10-1” is not working.

                        Solution: The hyperlink has been deleted and replaced with the text, “following figure:”
Defect ID	216744
Case ID	Internal
Description	If the Business Center application is deployed on the JBoss server in HTTPS mode, a session timeout error is thrown when you log in to the application for the first time.
Defect ID	216749
Case ID	Internal
Description	The Business Center: Customization Guide must be updated with information about setting up and configuring the extensibility environment for customizing the application.
Solution: Information about setting up and configuring the extensibility environment for customizing the application is added in the following new topics in the Business Center: Customization Guide:
•	Setting Up the Customization Environment
•	Customize Business Center Using Web UI Framework
•	Deploying Web UI Framework Customization
Defect ID	216795
Case ID	Internal
Description	In the Sterling Warehouse Management System: Concepts Guide, under the "Enterprise in a warehouse" section, the word “SKUs” is spelt incorrectly as "skis".

                        Solution: The word "skis" has been changed to "SKUs".
Defect ID	216838
Case ID	Internal
Description	The JavaScript API documentation must be updated with the Business Center JavaScript API information.
Solution: The JavaScript documentation has been updated with the required information. For more information about the JavaScript API Documentation and the URL that can be used to access it, refer to the topic "Customize Business Center Using Web UI Framework" in the Business Center: Customization Guide.
Defect ID	216861
Case ID	Internal
Description	When a user performs a count task that is created at a Location or LPN level using the Mobile Application, the system suggests the same count task even after the user skips the task using the SKIP execution exception.
Defect ID	216864
Case ID	Internal
Description	The Business Center: Item Administration Guide must be updated with the following information:
•	Searchable and Distinct Attributes options cannot be selected for attributes that belong to a category.
•	Specification and For Comparison usages are exposed only when managing the Master Catalog.
•	For Filter usage must be used only for those attributes for which allowed values have been defined.
Solution: The required information is updated in the topic, “Assign a Usage to an Attribute in a Category", in the Business Center: Item Administration Guide.
Defect ID	216867
Case ID	Internal
Description	The Business Center: Item Administration Guide must be updated with the following information:
•	For Comparison and For Filter purposes are not exposed when attributes are assigned to a classification.
•	For Comparison and For Filter purposes are not used for attributes that belong to a classification.
Solution: The required information is updated in the topic, “Assign a Usage to an Attribute in a Classification", in the Business Center: Item Administration Guide.
Defect ID	216886
Case ID	Internal
Description	In case of Item Pick tasks, a record is created in the YFS_TRANSACTION_LOCK table upon scanning the Item Id in the "Scan Identifier" field at the Pack station. However, the record does not get deleted from the table if the user logs out of the application without packing.
Defect ID	216892
Case ID	Internal
Description	In Business Center, the customer search results does not display a customer created from the Sterling Field Sales application when an email address of the customer is used as the search criteria.
Defect ID	216913
Case ID	Internal
Description	You cannot rework a quote after the quote has been approved.
Defect ID	216973
Case ID	Internal
Description	When the getNextTask API is called for a task type with the maximum number of users as 1, an SQL exception is thrown on DB2 database, and in Oracle the task is not suggested.
Defect ID	216990
Case ID	Internal
Description	The addLineToOrder API throws an “Allocated quantity not set” error when adding a line and passing an order line reservation.
Defect ID	216994
Case ID	Internal
Description	The changeOrder API throws an “Allocated quantity not set” error when adding a line and passing an order line reservation. 
Defect ID	217010
Case ID	Internal
Description	In Section 5.3 of the Selling and Fulfillment Foundation: Installation Guide, the note about setting registry variables for DB2 needs to be updated. 

	Solution: Section 5.3 now contains updated registry variables for DB2. Also, DB2LOCK_TO_RB information has been removed.
Defect ID	217081
Case ID	Internal
Description	In the Selling and Fulfillment Foundation: Installation Guide, Section 15.6 does not describe the steps for deploying the Sterling Field Sales application in the WebSphere Administration Console.

	Solution: Section 15.6 now contains steps for deploying the Sterling Field Sales application in the WebSphere Administration Console.
Defect ID	217162
Case ID	Internal
Description	In Section 10.3 of the Selling and Fulfillment Foundation: Installation Guide, the instructions for loading the language-specific factory defaults need to be updated.

	Solution: Section 10.3 contains updated instructions on loading the language-specific factory defaults.
Defect ID	217267
Case ID	Internal
Description	In the "Global Serial Number Purge Criteria Parameters" table of the Sterling Warehouse Management System: Configuration Guide, the “PurgeCode” parameter name is not documented. Also, the “Enterprise” parameter name is incorrect.

                        Solution: The “PurgeCode” parameter name and its description have been added. Also, the “Enterprise” parameter name has been changed to “EnterpriseCode”.
Defect ID	217420
Case ID	Internal
Description	Information about the URL for accessing the JavaScript API Documentation must be updated in the Business Center: Customization Guide.
Solution: The required information is updated in the topic, "Customize Business Center Using Web UI Framework", in the Business Center: Customization Guide.
Defect ID	217525
Case ID	Internal
Description	The SCUIAttributeUtils class file exists in the uishared.jar, the sbc_ui.jar, and the swc.jar files, and any modifications performed in the SCUIAttributeUtils class file is not updated in all the three .jar files. Therefore, the SCUIAttributeUtils class file must be removed from the sbc_ui.jar and the swc.jar files. In addition, the uishared.jar file must be included in the classpath for the Business Center and Sterling Web applications.
Solution: The SCUIAttributeUtils class file has been removed from the swc.jar and sbc_ui.jar files, and this class file is included only in the uishared.jar file. In addition, the uishared.jar is included in the APPSDynamicclasspath.cfg file.

Defect ID	217593
Case ID	Internal
Description	PDF files are provided only for the manuals that have changed in this hot fix, as usual. However, Online Help for the entire Selling and Fulfillment Suite is provided in a separate zip for this hot fix.

Solution: Instructions for applying the Online Help are described in the Hot_Fix_Installation.txt file provided with this Hot Fix.
Defect ID	217622
Case ID	Internal
Description	The releaseMoveRequest API succeeds with HasException flag set to "Y" even if a Null Pointer or DB exception occurs.
Defect ID	217629
Case ID	Internal
Description	When a warehouse has an LPN with multiple items from multiple receipts received into it, on invoking the getNodeInventory API for one of the receipts, the system throws an SQL exception on DB2 database.
Defect ID	218143
Case ID	Internal
Description	If you are running the Oracle WebLogic application server with JRockit as the JVM for Sterling workloads, these workloads may crash with an “illegal memory access” error. Sterling is working with Oracle to achieve a resolution for this issue.
	
	Solution: You can avoid this error by passing the command line prompt 
“-Xnoopt” to the JVM.
Defect ID	218792
Case ID	Internal
Description	In the Selling and Fulfillment Foundation: Customization Basics Guide, 
Section 5.2 contains three notes that may cause confusion about where to place extended files.

	Solution: The three notes in Section 5.2 have been updated to clearly state where to place extended files.