Skip to Content
avatar image
Former Member

Composite Provider cannot be used as the base of an aggregation level

I am trying to create an aggregation level on top of a very simple composite provider:

I have an aDSO with a couple of attributes in the union node that is write enabled. I have a join to a calculation view to get customer information and that is it.

I read that you cannot use Composite Providers for input enabled queries on a join that links to what you're trying to update, but that shouldn't be the case here as I have the union on the write enabled DSO.

Does anyone have any insight into why I'm unable to create this aggregation level?

UPDATE: I was reading this blog and thus the reason for thinking my solution below would work. I know one note mentions not being able to use a join for an input ready provider in a Composite Provider, but by attaching the input DSO by union, should this not work?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Dec 06, 2017 at 10:16 PM

    Hi Ashley,

    Can you post the screen shot of the error.

    -- Selva.

    Add comment
    10|10000 characters needed characters exceeded

  • Dec 07, 2017 at 03:01 PM

    Hi,

    it seems that you get message RSPLS142 (read the long text). The question is whether your HCPR (CompositeProvider) is consists of providers P (planning), R (reporting) with HCPR = P JOIN R or whether you have something like HCPR = P UNION (R1 JOIN R2) with R1,R2 reporting providers? The first is not possible as a basis of an aggregation level.

    Regards,

    Gregor

    Add comment
    10|10000 characters needed characters exceeded

    • Hi,

      your use case seems to be equivalent to 'navigation attributes', so you may add CustomerSoldTo as an attribute in CustomerNumber master data table or you use a HANA view as a basis for CustomerNumber and map/use CustomerSoldTo as a navigation attribute. Then you need only the aDSO and no JOIN in the CompositeProvider.

      Planning does not support joins in CompositeProviders with planning base providers since - in the general case - it is not clear how to 'split' the records to the planning enabled base provider.

      Regards,

      Gregor