Exception Reports

During calculation, you can generate the following two exception reports:

• Transaction exception report—lists transaction rows that did not receive an assignment during the calculation. See an example.
• Behaviors exception report—lists behaviors that were not assigned to any transaction during the calculation. See an example.

The reports are written to the library that you specify during calculation.

The following graphic shows a calculation that produces one row in the transaction exception report and one row in the behavior exception report:

Viewing the Exception Reports

To view the exception reports you can navigate to them directly in the folder in which they are stored. Or, you can preview them from the Profitability Management rich client. To preview them:

1. After calculating, click Details in the Calculation Result window.
   
   
2. Scroll down to the name of the exception tables.
3. Select the name of the table that you want to preview, and right-click.
4. Select Copy to Clipboard.
   
   
   
5. Close the Calculation Result window.
6. Select View View Table.
   
   The View table window opens.
7. Select the library containing the exception report.
8. Paste the clipboard contents into the Table name field.
   
   Note: Do not include an extension with the name.
   
9. Click View.
   
   
   
   The first 1,000 records of the exception report are displayed. If the exception report contains more than 1,000 records, then you must use a different SAS editor to view it.

Example of a Transaction Exception Report

In the following picture you can see that there are fewer columns in a transaction exception report than in the corresponding calculated transaction table. This is because calculation adds columns to the transaction table in the output directory. If a transaction row does not receive an assignment during calculation, then these columns are not added.

Example of a Behavior Exception Report

An exception report lists the behaviors whose rule did not trigger any assignments. In the following picture you can see an exception report listing two behaviors, 20004 and 20005, and the rule associated with each of those behaviors. Each of those rules failed to trigger any assignments in the transaction table (which you can see is ABMCost).

See also:

• Calculate a Model