Dissagregation not Possible,No Reference Data Found.

[Former Member]

Hi Team,

Though the input query allows to input the data at node level but it is not consistent in that behavior.

Some times it works and sometimes it is not and giving the below warning/error :

Disaggregation not possible, no reference data found.

No Data records found for distribution.

Is this the normal behavior or is it some thing that can be set to rectify this?

I have the key figures set to Planning on Totals: Disaggregate Value Entered. and  Distribution: Analogue Distribution(Self reference).

The weird thing is it always expects the characteristic ( that char that the transaction record is dependent on) to be in the rows along with the hierarchy.When I remove this then the input doesn't work and if I add it and since that char has multiple rows,

Some times it allows the input at node level and sometimes it gives me that error.

Like for example:

Hierarchy           P1         P2                  

Account1        50000      8000   

        A1           50000      8000    

           AA2      28000      3000

           AA3      22000      5000

Account2         20000      1800

        B4            20000      1800

          BB2        14000       800

          BB3         6000       1000

Every transaction record of account is associated with a functional area (like Alloc , MKTG).

SO, in the above query, it is always expecting the Functional area to be in the rows along with the Hierarchy.

Also a single account (Account1) could be tied to MKTG and ALLOC.

So if I include the functional rea along with the hierarchy then two rows will display and some times it works when I input the data at node level without this functional area and some times it doesn't.

Is this the normal behavior of the input query to have the dependent char in the rows for the node level input to work?

Please advice.

Thank you.

[gregor_dieckmann]

Hi,

as always, check note 994853 (attached PDF document) about disaggregtion, e.g. there you can find how the 'disaggregation list' is defined so that you might simulate this with the query you are using by adding characteristics to rows and some dynamic filters.

Regards,

Gregor

[Former Member]

Thank you Gregor.

I will read through that document.

[Former Member]

Hi Gregor,

I went through the document and it talks about the key figure to set to SUM or NO2 but I don't see this NO2 as one of the options in BW ?

Also it is mentioned that there has to be reference data to be able to disaggregate?

What exactly does this mean?

In my scenario ,the PLAN CUBE does not have any data so through input query 1 I entered the amount for P8 (period) and using the Allocation Factors Input query when I enter the value 25 (percentage) and click save then it comes back with the message "Disaggregation not possible, no reference data found"

What reference data is it in the above case?

In the Query, I set the Key Figure(allocation %) to 'disaggregate the value entered' and "Analogue Distribution in reference to P8 (above amount value).

Please advise on this error as I have to present this to business and nothing seems to be working  consistently.

If you can share your email address, I can send you the details of the requirement and the issues.

Any help is highly appreciated.

Thank you.

[gregor_dieckmann]

Hi Preddy R,

now you are mixing a lot of topics also from other SDN threads.

The topics seem to be:

1. - When are cells in the result set of a query input-ready?
2. - What is NO2 aggregation?
3. - What is disaggregation?

All three topics are explained in the documentation, inculding examples. Use your favorite search engine (e.g. restricted to help.sap.com) to find it. All these topics are very basic and to fulfil customer requirements one has to combine these features in the 'right' way. This is what consultants have to do, it is not the purpose of an SDN thread to provide ready to use solutions for customer projects.

Having read the above mentioned note you should be able to answer why disaggregation may fail. The most elementary reason is that there is no data to disaggregate to and you say your planning cube is empty. The question is not why disaggregation fails but why should it work? What does it mean to disaggregate a value to an empty set (of records)?

This topic also indicates that you should think about the data model of the application, the amount of planning data to be created, etc.

Regards,

Gregor

[Former Member]

Thank you Gregor.

I guess I'm trying to understand more from the disaggregation perspective.

If we do not have any plan data in the plan cube and trying to use the input query to enter some data for the first time then how does the disaggregation work here.

I will look more at the data model and requirements.

Thank you for your help.