cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Error adding amount key figure to aggregation level

arkaitz_orozko
Explorer
0 Likes
2,225

Hi all,

Actually we are working with BPC 11.0 and Eclipse is Modeling tool. We want to define and aggregation level with ZAMOUNT key figure as 0currency. The error appear when activating the aggregation level, the system gives us the next error "KEY figure 'ZAMOUNT' with currency /unit '0CURRENCY requires '1KYF_0CURRENCY''". Any idea which can be the problem?

Thnak you.

Accepted Solutions (0)

Answers (1)

Answers (1)

gregor_dieckmann
Product and Topic Expert
Product and Topic Expert

Hi Arkaitz,

you can read the long text of the message to get more information.

An amount key figure is linked to a currency characteristic, i.e. 100 EUR is modeled as 100 as key figure value and 0CURRENCY = EUR in a record. Here the question is whether 0CURRENCY is in the key of the base planning InfoProvider or in the data part. In your case it seems that you have 0CURRENCY in the data part of a direct-update DSO or DSO (advanced). It is best practice to use 0CURRENCY in the key; if you don't want this and 0CURRENCY is in the data part you also have to expose the currency characteristic as key figure 1KYF_0CURRENCY: this allows the system to determine the information where the key figure value and the currency information comes from.

Observe that in a query all characteristics are treated as key, it plays no role whether the characteristics is in a key in the basic planning provider or not. In reporting this is ok and leads to no problems. In planning this usually lead to problems, this is why characteristics from the data part can be exposed as key figures.

Example:

DB has Product as key and Amount, 0CURRENCY in the data part, assume we have on record on DB

Product | Amount 0CURRENCY
P1        100    EUR

To treat 0CURRENCY as key you can create queries that look like this

Product 0CURRENCY | Amount
P1      EUR          100 (EUR)
P1      USD          200 (USD) <- new line

but in DB you can have either the first or the second 'record' (since only Product is in key).

This is why 0CURRENCY can be exposed as key figure 1KYF_0CURRENCY; this allows to model the query as follows

Product | Amount       1KYF_0CURRENCY
P1        100 (EUR)    EUR

Regards,

Gregor