This is a list of the issues addressed in hot fix 64ABM04 related to significant functionality problems in SAS® Activity-Based Management.

• The Module Hierarchy report only includes the resource module when multiple currencies are selected
• An error occurs while copying cube configurations between models when SAS Activity-Based Management uses Oracle as its database server
• The Close Window button does not close some import and export dialogs
• Multistage contributions fact tables generated with the 6.3 compatible option exclude Revenue
• OLAP views display the Reference value rather than Name for the Stages dimension
• The Resource Contributions Intermediate report export excludes accounts with only reciprocal assignments
• In specific cases, deleting a fact table or cube may fail with the error 'Root element is missing'
• When the members of the Stages dimension included in a cube configuration are not associated with any accounts, cube generation fails with the error "MESSAGE[@RESOURCEID=2147749489]"
• Cube generation fails with error 'The output length of caption for LEVEL exceeds 256 characters' when using an ODBC library with SAS OLAP Server
• Numeric values in Single-stage Contributions OLAP views with Oracle as the database server do not match prior releases or results with SQL Server as the database server
• Cube Generation fails with 'Unexpected error' for Multistage Contributions cube with 6.3 compatible option, for certain models
• Cube generation fails when using SAS OLAP Server if the host server name contains a hyphen
• Adding numeric attributes to a Single-stage Contributions cube fails
• For certain models, cube generation fails with the error 'Attribute does not exist in the model'
• Output Quantity values are incorrect in OLAP views on Multistage Contributions cubes
• Dimension levels are not displayed in the Cube Configuration wizard
• Delete Cost Element does not work normally when first and second row use same color
• Users with Read Only model access can add/remove assignments using F7/Shift + F7
• Account search including text attribute fails with 'Incorrect syntax' when using null or not null operator
• Selecting Delete Incoming and and Outgoing Assignments from the Actions list of the Search Account Results page does not delete the outgoing assignments for any selected External Unit account
• Marking an account as a behavior from the Actions list of the Search Account Results page disables the Unmark as Behavior option from the right-click context menu for that account
• Both UnitValue and TotalValue columns are incorrectly formatted when exported to a behavior table
• The Cost Flow column on the Cube tab of the Model Properties dialog does not support keyboard access
• The Contributions viewer will not display data if the selected model was calculated by executing PROC ABC outside of SAS Activity-Based Management
• Calculation does not complete normally with Oracle as the database server if the Oracle password contains diacritic characters
• Numeric values in the Contributions viewer do not reflect changes in model data since execution of the last Contributions query
• SAS® Activity-Based Management supports the Microsoft SQL Server 2005 database server, but not the Analysis Services.
• Importing a model XML file to a SAS® Activity-Based Management server that uses Oracle as its database server may fail with the error “The root transaction wanted to commit, but the transaction aborted.”
• For models with user-defined stages and assignments between accounts in non-consecutive stages, some cost visible in the model view may not be included in Multistage Contributions OLAP views for that model.
• In certain cases, accounts in a reciprocal system assign less than 100% of the cost assigned to them from accounts outside of the system
• If SAS® Activity-Based Management uses Oracle as its database server, editing entered cost elements or generating OLAP cubes may fail with a “concurrency violation” error.
• Under certain conditions, model cost calculation may fail with the error “Object reference not set to instance of object.”
• If SAS® Activity-Based Management uses Oracle as its database server, period comments beginning with non-alphanumeric characters can cause creation of new period/scenario associations to fail.
• Creation of a new cube configuration may fail with “runtime error” for some very large models.
• When using modules as stages, views of the multistage contributions cube may display summary rather than individual values for numeric attributes.
• When not all leaf-level dimension members occur at the same level, views of the single-stage contributions cube may display incorrect level labels.
• A multistage contributions OLAP view might omit non-cost measure values when “prior” stages are added to the view after “later” stages.
• Exporting Report Data for the Resource Contribution - Intermediate report template produces incorrect data.
• When exporting model data to Oracle staging tables, the row of data for any driver with a formula in excess of 128 characters will be excluded from the Driver table.
• Null values for the Revenue property of some accounts can cause inflated Revenue values for other accounts.
• If SAS® Activity-Based Management uses Oracle as its database server, the time required to produce a large multistage contributions fact table may be unexpectedly long compared with the same operation using Microsoft SQL Server as the database server.
• Cost values may not be calculated in certain cases for assignments whose driver has a formula over 245 characters long

Operating System and Release Information

A fix for this issue for SAS Activity-Based Management 6.4 is available at: