Hot Fix Release Notes
	Product	Selling and Fulfillment Foundation, 9.0
	Date	Wednesday, November 17, 2010
List of Defects Addressed
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.