Hot Fix Release Notes
	Product	Sterling Business Intelligence
	Date	Thursday, November 5, 2009
List of Defects Addressed
Hot Fix ID	8.5-HF1
Defect ID	185328
Case ID	Internal
Description	When a CDC filter is applied on a Fact and if the Load Management is executed, the To Value of the CDC filter in the user interface of the Load Management is set to the end of the previous run of the Load Management, and not the current time. Because of this, the Load Management does not extract any records.
The Load Management functions correctly only if the To Value is manually updated.
Defect ID	196670
Case ID	Internal
Description	The scripts generated from the AW Studio Framework cannot be reused, because the "To" date in the scripts for the CDC filter is not being updated to the current date after the script is run. Therefore, the consecutive ETL runs from the same scripts will fail to pull the data created in the source after the first ETL run.
This happens only in the AW runtime, and not in the Load Management in the AA Studio Framework.
Defect ID	200705
Case ID	Internal
Description	A user is unable to create an AA project on an Oracle 11g database.
Defect ID	202357
Case ID	Internal
Description	The application incorrectly inserts the change records of an enterprise into the YFS_ORDER_TS_TAG table of the DEFAULT colony instead of the respective colony of the enterprise.
Defect ID	202421
Case ID	Internal
Description	The SO Modification Fact table contains several records with the blank modification type code.
Solution: The MODIFICATION TYPE filter has been added to filter those records that do not contain the modification type value.
Defect ID	202749
Case ID	Internal
Description	When multiple colonies are configured in a multi-schema environment, the records in the YFS_ORDER_AUDIT_LEVEL table for some of the colonies is not being loaded into the staging database. Because of this, the SO Modification Fact does not contain the data for these colonies.
Solution: The YFS_ORDER_AUDIT query subject and the YFS_ORDER_TS_TAG query subject are created inside the YFS_ORDER_AUDIT_LEVEL namespace such that duplicate relationships will not be created. The same modifications have been performed for the YFS_ORDER_HOLD_TYPE_LOG.