![]() | ![]() | ![]() | ![]() | ![]() |
After an alert is issued, decreasing claim counts in later runs of Emerging Issues processes can, in certain situations, result in the alert status being dropped. The problem is that the application assumes that once the claim count exceeds the critical value, then it will continue to exceed the critical value. This is only true if the claim counts do not change from one process run to another.
No workaround is possible.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Product Family | Product | System | Product Release | SAS Release | ||
Reported | Fixed* | Reported | Fixed* | |||
SAS System | SAS Warranty Analysis | Microsoft Windows Server 2003 Datacenter Edition | 4.1 | 4.2 | 9.1 TS1M3 SP4 | 9.2 TS2M2 |
Microsoft Windows Server 2003 Enterprise Edition | 4.1 | 4.2 | 9.1 TS1M3 SP4 | 9.2 TS2M2 | ||
Microsoft Windows Server 2003 Standard Edition | 4.1 | 4.2 | 9.1 TS1M3 SP4 | 9.2 TS2M2 | ||
64-bit Enabled AIX | 4.1 | 4.2 | 9.1 TS1M3 SP4 | 9.2 TS2M2 | ||
64-bit Enabled Solaris | 4.1 | 4.2 | 9.1 TS1M3 SP4 | 9.2 TS2M2 | ||
HP-UX IPF | 4.1 | 4.2 | 9.1 TS1M3 SP4 | 9.2 TS2M2 |