Problem Note 43793: Corrections included in Hot Fix 71ABM02 for functional errors in SAS® Activity-Based Management
Hot Fix 71ABM01 provides corrections for the following list of functional issues identified in the 7.1 release of SAS Activity-Based Management:
- A Read Access Violation error might occur when generating an OLAP fact table that includes a large number of numeric attributes.
- Some operations might fail with an error stating that the <commons-lang.jar> file is missing.
- A Count Rows operation launched from Generate Cubes might fail and/or might not return an operation summary.
- The first attempt to create an Entered Cost Element might fail if the database server is Oracle 11g R2.
- New model creation might fail if the database server is Oracle 11g R2.
- Importing model data might fail if the database server is Oracle 11g R2.
- Users are not prevented from modifying a model during a Calculate Costs operation.
- Exporting a very large model to XML might fail in a 64-bit operating system environment on the host.
- Cube generation might fail if Oracle 11g is the database server and Microsoft SQL Server Analysis Services is the OLAP server.
- Exporting model data to a Microsoft SQL Server database might fail if the database name contains a space character.
- Report generation might fail when the SAS Activity-Based Management mid-tier is installed on the same host as the SAS Forecast Studio web server.
- OLAP fact table generation might fail with the error Attribute named <attribute_name> not defined when a model contains certain characters.
- OLAP cube generation might fail with metadata errors for some models if the database server is Oracle 11g.
- Different values for 'None' dimension members in OLAP cubes might result in different cost totals from those seen in the 6.4 release of SAS Activity-Based Management.
- A calculation might create duplicate Sales Volume-based assignments between the same source and destination accounts.
- Certain driver formulas that are valid in the 6.4 release of SAS Activity-Based Management might fail to drive costs in release 7.1.
- Revenue values that exist in the model do not appear in the multistage contributions OLAP cube.
- Rules-based drivers used in systems of reciprocal assignments might not be evaluated properly.
- Users might not be able to log on to SAS Activity-Based Management 7.1 if the license has entered the warning period. This might also occur if no valid SMTP server was defined during the mid-tier configuration steps.
- Calculation fails with the error Cannot load calculate code.
Operating System and Release Information
| SAS System | SAS Activity-Based Management | Linux for x64 | 7.1 | | 9.2 TS2M3 | |
*
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.
This note contains a list of the functional issues addressed in the 71ABM02 hot fix for the 7.1 release of SAS Activity-Based Management on Linux 64-bit.
| Type: | Problem Note |
| Priority: | medium |
| Date Modified: | 2011-07-28 14:13:14 |
| Date Created: | 2011-07-20 15:21:35 |
