Problem Note 46099: Financial effects entered as formatted numbers sometimes result in "OpRiskFrameworkError: Not a valid number.." errors
When using the SAS® Enterprise GRC Web application to add financial effects to an incident, if you enter a formatted number (like xxx,xxx.xx), exceptions like the following might appear:
Caused by: com.sas.oprisk.framework.server.OpRiskFrameworkError: Not a valid
number at
com.sas.oprisk.framework.server.util.ParsingUtils.parseDouble
(ParsingUtils.java:317)
at
com.sas.oprisk.monitor.web.incident.forms.EffectAmountForm.setLossAmt
(EffectAmountForm.java:90)
at
com.sas.oprisk.monitor.web.incident.forms.EffectAmountForm.invertSignsForSlosh
(EffectAmountForm.java:175)
at
com.sas.oprisk.monitor.web.incident.forms.EffectAmountForm.sloshTo
(EffectAmountForm.java:468)
at
com.sas.oprisk.monitor.web.incident.actions.EffectAmountSaveAction.save
(EffectAmountSaveAction.java:46)
at sun.reflect.GeneratedMethodAccessor4536.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
com.sas.oprisk.monitor.web.actions.BaseDispatchAction.dispatchMethod
(BaseDispatchAction.java:372)
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| SAS System | SAS Enterprise GRC | Microsoft® Windows® for x64 | 4.3 | 5.1 | | 9.3 TS1M0 |
| Microsoft Windows 95/98 | 4.3 | | | |
| Microsoft Windows 2000 Advanced Server | 4.3 | | | |
| Microsoft Windows 2000 Datacenter Server | 4.3 | | | |
| Microsoft Windows 2000 Server | 4.3 | | | |
| Microsoft Windows 2000 Professional | 4.3 | | | |
| Microsoft Windows NT Workstation | 4.3 | | | |
| Microsoft Windows Server 2003 Datacenter Edition | 4.3 | 5.1 | | 9.3 TS1M0 |
| Microsoft Windows Server 2003 Enterprise Edition | 4.3 | 5.1 | | 9.3 TS1M0 |
| Microsoft Windows Server 2003 Standard Edition | 4.3 | 5.1 | | 9.3 TS1M0 |
| Microsoft Windows Server 2003 for x64 | 4.3 | 5.1 | | 9.3 TS1M0 |
| Microsoft Windows Server 2008 | 4.3 | 5.1 | | 9.3 TS1M0 |
| Microsoft Windows Server 2008 for x64 | 4.3 | 5.1 | | 9.3 TS1M0 |
| Microsoft Windows XP Professional | 4.3 | 5.1 | | 9.3 TS1M0 |
| Windows 7 Enterprise 32 bit | 4.3 | 5.1 | | 9.3 TS1M0 |
| Windows 7 Enterprise x64 | 4.3 | 5.1 | | 9.3 TS1M0 |
| Windows 7 Home Premium 32 bit | 4.3 | 5.1 | | 9.3 TS1M0 |
| Windows 7 Home Premium x64 | 4.3 | 5.1 | | 9.3 TS1M0 |
| Windows 7 Professional 32 bit | 4.3 | 5.1 | | 9.3 TS1M0 |
| Windows 7 Professional x64 | 4.3 | 5.1 | | 9.3 TS1M0 |
| Windows 7 Ultimate 32 bit | 4.3 | 5.1 | | 9.3 TS1M0 |
| Windows 7 Ultimate x64 | 4.3 | 5.1 | | 9.3 TS1M0 |
| Windows Millennium Edition (Me) | 4.3 | | | |
| Windows Vista | 4.3 | 5.1 | | 9.3 TS1M0 |
| Windows Vista for x64 | 4.3 | 5.1 | | 9.3 TS1M0 |
| 64-bit Enabled AIX | 4.3 | 5.1 | | 9.3 TS1M0 |
| 64-bit Enabled Solaris | 4.3 | 5.1 | | 9.3 TS1M0 |
| HP-UX IPF | 4.3 | 5.1 | | 9.3 TS1M0 |
| Linux for x64 | 4.3 | 5.1 | | 9.3 TS1M0 |
| Solaris for x64 | 4.3 | 5.1 | | 9.3 TS1M0 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2012-04-26 15:04:29 |
| Date Created: | 2012-03-23 09:40:01 |
