Characterisrics relationships based on Exit short dump

[former_member460654]

Hi All!

I have a weird behavior of my characteristic relationship (CR) built based on the exit class.

The model is like this: I have an aDSO like cube (A) and direct update DSO (B) included in the composite provider (CP). All fields from A and B are mapped to CP.

the CR is set on the DSO A and it uses only 3 dimensions out of 10 that are in DSO A. Those 3 dimensions are also in DSO B.

On top of my CP I have an aggregation level and on top of it the query is built.

My CR I need to restrict values in the F4 pop-up of my 3 dimensions in the input form.

When the exit class is being triggered, my logic of creating valid combinations works fine, BUT...

After that, system tries to create a cartesian product of all 3 dimensions (because of my DSO B), tries to create millions of valid combinations, and gives a short dump.

the question is "why is it doing it"? the aggregation level contains all the characteristics from the DSOs.

[gregor_dieckmann]

Hi Taras,

you contradicting yourself. If the valid combination are the same for both part providers then either you need no characteristic relationships or you need the same relationships for both part providers.

In Analysis Office the default is to use characteristic relationships in the value help in new lines, if you set 'Value Help in New Lines' to 'Master Data' then characteristic relationships will not be used in the value help.

I also don't understand the statement

...Value help can't be based on masterdata, as there are a lot of redundant combinations, that I wan't to exclude...

The value help returns only one value and not a combination of characteristic values; in other words the value help is one dimensional. The statement also seems to indicate that the valid combinations in the different part providers are really quite different.

Regards,

Gregor

[former_member460654]

Hi Gregor,

"In Analysis Office the default is to use characteristic relationships" - got it.

"you need the same relationships for both part providers" - this is exactly what I've tried and it solved my short dump.

"I also don't understand the statement" - what I meant, I can't make my value help based on masterdata as user will see full list of masterdata for each dimension. It must be CR in my scenario, to restrict a few dimensions based on selection of others.

thanks for your replies, appreciate it.

[gregor_dieckmann]

Hi Taras,

characteristic relationships have an impact on many things, not only the value help. This is just a general infrastructure. In your case it is better to used value help based on master data since for one part provider anyway all master data values contained in the query filter can be used.

In your query design a combination in a new line might be valid for one restricted key figure but not for the other (since the restriction contains the part provider).

This is why the value help should really be based on master data values.

Regards,

Gregor

[former_member460654]

Hi Gregor,

my B DSO is meant for comments, so its characteristics 99% are mirroring characteristics from DSO A. So combinations are valid for both providers. Value help can't be based on masterdata, as there are a lot of redundant combinations, that I wan't to exclude, so the workbook users won't see them.

By the way, what is a usage of this option?

my exit class is being triggered (when I press F4 in the workbook) even without this setting in the query.

Best Regards,

Taras

[gregor_dieckmann]

Hi Taras,

the system uses all restrictions in the query to process the value help. Since two part providers are used, the system creates all valid combinations for both part providers in your case, one has characteristic relationships, so the CREATE method of these relations is called and the results are combined by an inner-join. The other part provider has no characteristic relationships, so the valid combinations are controlled by the master data tables: the valid combinations is the cart. product of all involved characteristics values.

Regards,

Gregor

[former_member460654]

Hi Gregor,

thanks for the reply. Is there any procedure/recommendation for how to use characteristic relationship in my case? (when two part providers are included in the composite, and restricted KFs are used in the query).

Best Regards,

Taras

[gregor_dieckmann]

Hi Taras,

observe that the value help not called in the context of a restricted key figure but in the new line this is why the system does not know which part provider to use.

Regards,

Gregor

[former_member460654]

Hi Gregor,

shouldn't it use both providers and apply existing characteristics relationship to both of them?

there is nothing said in the documentation that CR won't work if to use restricted KFs. The only thing I saw - if the CR is set in one of the providers of the Composite Provider, it will be working on the CP level.

Is there any way to use CR with restricted KFs?

Best Regards,

Taras

[gregor_dieckmann]

Hi Taras,

it seems that you use characteristic relationships (the CREATE method) to create all valid combinations in the value help (in new lines?). As you are using a composite provider the system has to know the part provider to create the combinations, in other words as long a the part provider is not specified the system creates combination for all involved (planning enabled) part providers.

So restrict to part provider A or also use a relations that restricts the combination for provider B.

Regards,

Gregor

[former_member460654]

Hi Gregor,

Yes, you are right, I'm trying to use CREATE for value help in new lines.

I have only two key figures in my input query, and each of them is restricted with the one infoprovider. KF1 is restricted with DSO A, and KF2 is restricted with DSO B.

Best Regards,

Taras