cognos - Cognos 双重计数

Question

我有下表：

Billing Account Number  Credit Alert Number Account Balance Full Date
00005884                1-400WHA            13111.80        2013-08-12
00005884                1-4WTV4E            13111.80        2013-08-12
00005884                1-4TG3WJ            13111.80        2013-08-12
00005884                1-43GBO9            13111.80        2013-08-12
00005884                1-5X817T            13111.80        2013-08-12
00005884                1-4AFO7S            13111.80        2013-08-12
00005884                1-50PJWY            13111.80        2013-08-12
00017988                NULL                105.86          2013-08-12
00018713                NULL                118.00          2013-08-12
00020032                NULL                7316.06         2013-08-12

正如你所看到的，我有一个重复Billing Account Number以及那个Account Balance。在 Cognos 中，我只引入Billing Account Number并且Account Balance它会自动总结出Account Balance哪个是错误的。如何设置行列式以防止重复计算？

如果我将常规聚合规则设置为度量平均值Account Balance，那么它将适用于大多数报告，但仍会中断其他已选择列的报告等。

Answer 1

Determiantns
Determinants are set on framework manager.
I don't know how your model looks like, but it is good practice to put determinants definitions on database layer (physical tables mapping and relation).
You can find a great example in the great_outdoors_warehouse sample model. (located in c10_directory\webcontent\samples\models\great_outdoors_warehouse).
Just make sure you have installed Cognos samples where you installed framework manager.
In this model, under Database view->Go data->GO_TIME_DIME, right click on and choose Edit Definition. In the Determinants tab, you will see:
So, I guess you should put the Billing Account Number as the key, and then Account Balance as an attribute and mark it as group by.
Just bare in mind, that order of the determinants do matter.
So, you must put this defintion (Account Number) before the Uniquely Identified deteminant (if such exist).
A great Cognos documentation regarding determinants can be found here:
Framework manager user guide - determiantns

Alternative solution
A second option would be, change its usage type from fact to attribue: AFAIK, by default it will not sum up in a list report.
For saftey, you can change the aggregate rule to unsupported.