Aggregates and navigational attributes

[Former Member]

I'm trying to create an aggregate for a query that displays cost element, cost center, and business area (which is a nav. attribute of cost center). I know that you shouldn't create an aggregate containing both a characteristic and a nav. attribute of that characteristic.

Which aggregates should be created for this query? If I create one aggregate with cost element and cost center, would business area automatically be covered? Or would I need one aggregate with cost element and cost center, and a second aggregate with cost element and business area?

I would have BW propose an aggregate for this query, but it's based off a multiprovider.

Thanks,

Jason

[Former Member]

Why not create an aggregate with cost center, cost element and business area? Let the BW do the aggregate handling, it should be fine.

Best regards

Dirk

[Former Member]

I would create an aggregate with all three, but I read that you aren't supposed to create aggregates with a characteristic and its nav attribute. (Business area is a nav attribute of cost center.)

So it looks like I can just create an aggregate with cost element and cost center.

Now if I have another query with only cost element and business area, would it still be best to use an aggregate with cost element and cost center, or in this case would it make more sense to have a separate aggregate with cost element and business area?

[Former Member]

> Now if I have another query with only cost element

> and business area, would it still be best to use an

> aggregate with cost element and cost center, or in

> this case would it make more sense to have a separate

> aggregate with cost element and business area?

This depends on the number of cost centers per business area and the quality of the first aggregate. If the first aggregate still has some million records and the cc per bus area is 20:1 you might want to create another aggregate. If the first aggregate leaves some 10.000 records there is no need for another aggregate.

Best regards

Dirk

[Former Member]

After some trial and error, it looks like if you create an aggregate on a characteristic limited on hierarchy, it won't bring in the nav attributes of that characteristic. I tried creating an aggregate with the characteristic limited by hierarchy and the navigational attribute, but it has very poor valuation.

[Former Member]

Hi Jason,

Were you successful in creating an aggregate with a char and its own nav. att eventually? and is this the aggregate that has poor valuation.

What do you mean by poor valuation?

Thanks,

Reddy

[Former Member]

I was able to create an aggregate with the characteristic (limited by hierarchy) and its own nav attribute, but the mean value was 1, which (as I understand it) means that it is providing no performance benefit.

By poor valuation, I was referring to the Valuation column in the aggregate maintenance screen. For this aggregate, it showed 5 minus signs.

The "select aggregate" screen in RSRT (shown when running a query with Select Aggregate checked under Execute + Debug) would probably help create the correct aggregate, but the "Not Possible Because" column cuts off the text. For example, it says:

"____Characteristic 0COSTCENTER is compressed, but not in the"

...which is not much help. Does anyone know how to see the full text?

[Former Member]

Hello Jason,

If you execute the query in RSRT in Debugging and displaying the statistical data. Which figures do you have for QDBSEL and QDBTRANS? For both Queries please with and without and aggregate...

Thanks

Michael

[Former Member]

There are two similar queries I'm working with: one built off a multiprovider (0cca_c11 and 0ps_c04), and one built off only 0ps_c04. For the multiprovider query, I get a GETWA_NOT_ASSIGNED short dump (You attempted to access an unassigned field symbol - data segment 45) after the display aggregates found screen.

For the 0ps_c04 query, I get QDBSEL: 10455, QDBTRANS 4161. This is using an aggregate with a mean value of 10.

If I could see the full text of the "Not Possible Because" column in the Select Aggregates screen, that would help me determine why the report is not using aggregates with higher valuation.

[Former Member]

Hello Jason,

you need a Aggreagte for cost element, cost center.#

If I create one aggregate with cost element and cost center, would business area automatically be covered? --> yes

Kind regards

Michael