#MULTIVALUE on ratios with navigation attributes

Dear All,
I have some problem with table where I put only navigation attributes and ratios... the colomns ratio is "MULTIVALUE" value..
I would like aggregate ratio on the table...
Workaround ? Solution ?
Thanks
Cédric
BO edge 3.1 SP3
SAP BW EHP4

Hi Igno,
I agree that it still says that in the best practise (dated back in 2009!), but in my experience in the past years it doesn't work that well. Unless you tailor your BEX query one to one with a report that is... Not the intention of a universe i.m.h.o.
For standard aggregation keyfigures I always set the aggregation to sum. So I only use database delegation if I really need it because it would not be possible for WebI (for example counts like number of stores with sales).
Note that I also make sure that I retrieve data on the level that I need (by checking the number of rows retrieved for instance and comparing that with the number of lines in the report. So the database will do all of the aggregation it can do already!
So you do NOT get the sum a second time! You get it only once, only who handles the summing within the results is different, with database delegated, it is BW, with sum it is WebI. For a plain sum it is Webi and summing within the retrieved results can be handled by WebI perfectly fine (and will match with sums by BEX where you have them) !!!
Letting BW handle the aggregations means it will retrieve all the extra aggregation points it can find in the report, but only if it can!
In this particular case the attribute country of the customer is not a known aggregation level for BEX, so it cannot calculate it.
Also if you create webi based groupings of dimension objects, or even want to re-format one (like month) it does not work.
Furthermore, if you read my post correctly I do not mention "GROUP BY" but I do say grouping.
For totals you will always have a certain grouping/combination of dimensions (whether you call them dimension objects (in WebI) or characteristics (in BEX)). I state that to calculate an aggregation for that combination the BEX query needs to have knowledge about it. If it has not, it cannot calculate...
So I say it should be the preferred way to let WebI handle the aggregation,
unless it cannot do this correctly, not the other way around.
Thanks,
Marianne

Similar Messages

Inconsistencies with Navigation Attributes

Hello all,
We are experiencing some inconsistencies with navigation attributes. Attributes are flagged as navigational on the InfoObject Level and also selected in the InfoProvider's Navigation Attributes folder. However some of them are showing in the Query as Navigation Attributes while other's don't. The same process was followed for all of them. Any ideas why this might happen?
Thank you so much!

Take the "Company", "Area" and "Department" out from the attribute list of the Org Unit !!
then delete "Company", "Area" and "Department" one by one ..
And then try deleting orgunit ..
Regards.

Selection generated with Navigational Attribute and store forecast profile

Hi,
Our business has a requirement that will require for the solution a Forecast Profile to be stored against a selection which was generated with a navigational attribute in the selection. I have found two SAP Notes 329707 and 394076 shown below which point to BAdi /SAPAPO/SDP_FCST5 method SEL_CHANGE to do the job. Can anyone help me in understanding what coding we need to do within the BAdi to get this to work. Does anyone have an example?
SAP Note 329707
Method:
    SEL_CHANGE (as of SCM 4.1)
    This method can be used to change the selection to be stored in
    in the generated selection table. Navigation attributes can be
    removed, such as the function of assigning a forecast
    profile to the selection can also be allowed for selections with
    navigation attribute without a basic characteristic.
    Parameter
     IV_PAREAID      Importing Type /SAPAPO/TS_PAREAID
     CT_SELECTION    Changing   Type /SAPAPO/TS_IOBJ_SELECTION_TAB
Sample code:
    DATA: lv_tabix     TYPE sytabix.
    DATA: lt_chars     TYPE /sapapo/dm_int_chars_tab.
    DATA: ls_chars     TYPE /sapapo/dm_int_chars.
    DATA: ls_selection Type /SAPAPO/TS_IOBJ_SELECTION.
    IF iv_pareaid = 'PAREA1'.
      CALL FUNCTION '/SAPAPO/TS_PAREA_SINGLE_GET'
        EXPORTING
          iv_pareaid   = iv_pareaid
        IMPORTING
          et_chars     = lt_chars
        EXCEPTIONS
          not_found    = 1
          OTHERS       = 2.
      CHECK sy-subrc EQ 0.
      LOOP AT ct_selection INTO ls_selection
                          WHERE iobjnm NE '9AVERSION'.
        lv_tabix = sy-tabix.
        READ TABLE lt_chars INTO ls_chars
                            WITH KEY iobjnm = ls_selection-iobjnm.
        IF sy-subrc EQ 0 AND NOT ls_chars-atrnavfl IS INITIAL.
           DELETE ct_selection INDEX lv_tabix.
        ENDIF.
      ENDLOOP.
    ENDIF.
SAP Note 394076
As of Release SCM 4.1, you can use the method SEL_CHANGE of the BadI /SAPAPO/SDP_FCST5 to process the selection before saving it to the generated selection tables. This allows you to save selections with navigation attributes, for example, where the selections do not have a specified basis characteristic. You simply need to delete the navigation attributes from the selection.

Is all the Navigational attribute checked for display during cube creatiion?
Prathish

Create restricted key figure with navigation attributes

Hi,
I need to create a restricted key figure using attributes of 0BP_COMPET.
On my report is :
Competitors (0BP_COMPET)
Quantity
Active Competitors = Expiry Date of Minority Status greater than or equal to system date
Inactive Competitors = Expiry Date of Minority Status less than to system date
Note : Expiry Date of Minority Status is a navigation attribute of 0BP_COMPET and system date is generate by variable 0DAT - Current Calendar Day (SAP Exit).
How can i apply the formula?
Thanks

Here's a good How to Document that explains what you are trying to do ....
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/72f4a790-0201-0010-5b89-a42a32223ffc
It is called How to.... Calculate with Attributes.
Brian

Data issue with Navigational Attribute in the report

Hi Experts,
We have a report which has Material and Material Group in the report. Material Group is a navigational attribute of 0Material. We have some 31 material groups in the ODS. However, the report is diaplaying only 3 material Groups. If I use Material Group directly( not as an attribute of material) then it is displaying all the 31 material groups correctly.
We have a hierarchy which is loaded through Flat file on Material Group. We need the hierarchy to be displayed for all the material groups in the ODS. Please let me know what could be causing this issue?
Thanks and Regards,
Kavitha Jagannath

Hello Kavitha,
Check if the Material Masterdata is having these Material groups. If not then load this Material masterdata and activate it.
As your query is using Material group as Navigational attribute then the data should come from this Material Masterdata.
If your Material has only 3 of th eMat Groups then report will show only 3. Better update this Material masterdata.
Regards,
Pratap Sone

Problem with Navigation Attributes when upgrading from BI 3.1 to BI 7.0

Hello,
I have the following problem that occured regarding queries during the upgrade from BI 3.1 to BI 7.0:
As far as the queries are concerned it is not possible in the 7.0 system to completely rebuild them according to the queries in 3.1. More specifically this refers to a certain number of navigation attributes that cannot be integrated into the query. In this case the following error message appears: "Error in BW: Missing mapping partprov cha <-> multiprov cha". Moreover, this error message only appears when you try to include navigation attributes into the query that are all attributes of the same specific InfoObject.
I have already checked in the 7.0 system if the relevant objects have the status 'active' and if the identification between the Multiprovider and the InfoObjects used is correct. So, is there anybody who may has another idea why this error message appears respectively who experienced the same/similar problem?
Thanks in advance & Regards

Hello Martin,
yes, I've also checked the identification in the MultiProvider for the navigational attributes. There is nothing missing.
I've also reactivated the objects.
Do you may have another idea?
Thanks and regards, Ines

Infoset - Query with navigational attribute as filter

Dear all,
We have created an InfoSet linking an InfoObject 0COORDER to an Info InfoCube containing order data.
We have used a Left outer join to link 0COORDER tol 0COORDER in the InfoCube. The purpose is to be able to report on all 0COORDER even if they have no transaction data.
When creating a query we get a list of all 0COORDER as expected. The problem arises when we try to use the navigational attribute "Status" from the InfoObect 0COORDER as a filter in the query. This does not work at all.
Does anyone know what we are doing wrong here ? We are using BEx Query Designer 7.0.
Kind Regards,
Mikkel

Hi Mikkel
When you say that your Status field does not work at all, what is the error you are getting? Are you able to see this field in the query designer. If that is not the case that means your "status" is not chosen in the infoset design.
If you are able to see it in the designer then please let us know what is the exact error you are getting.
Thanks.

How to Get Navigational attributes of dso in Report ...

Hi i have a dso with many fields ,
In the report i need to get some navgational attributes which are in dso..
How to Get Navigational attributes of dso in Report ..??
Thanks All..

hai naiduz,
in the dso u find folder with navigational attributes, there select the Navigation check box the fields which u need in the report.
and further if ur dso through multiprovider and also identify them at multi provider level.
then u will be able to see the fields at query designer level, then u can use the nav. fields u need in the report.
regards,
Vj

RSDRI_INFOPROV_READ and navigational attributes

Hi experts,
can you please share your knowledge and experience with me?
the issue:
within a custom ABAP program i am calling function module RSDRI_INFOPROV_READ with standard parameters. this works fine only if no characteristics or basic characteristics selection is applied. But the call will fail in case we select on navigational attributes of characteristics.
is there any experience in the field or at SAP about this restriction, or maybe some helpful workaround?
Many thanks for your feedback and assistance!
Cheers, Harry

Hello everybody,
I face the same problem that RSDRI_INFOPROV_READ doesn't work with navigational attributes. It throws an exception. I did some debugging and found out the following:
At some point in the call stack, the method CL_SQL_PARAMETERS->SET_PARAM_STRUCT is invoked.
This Method reads the structure of the fields:
cl_abap_typedescr=>describe_by_data_ref( struct_ref ).
struct_ref is filled with /BIC/V<Cube>2
This dictionary structure does not contain any navigational attributes.
Then, there is a loop on the InfoObjects that were transferred to RSDRI_INFOPROV_READ with the parameter I_TH_SFC (also nav. attributes). Within the loop, the fields are "compared" to the components of the structure /BIC/V<Cube>2:
READ TABLE sdescr_p->components ASSIGNING <comp>
WITH KEY name = <cf>.
Since the nav. attributes are not contained in the internal table sdescr_p->components an exception is raised and the function terminates with an error.
By the way, this problem only occurs after we have upgraded to BI 7.0.....
Can anybody help?
Thanks a lot!
Cheers
Michael

Use of planning characteristics vs navigation attributes in APO DP

I am using APO DP V5.
I have a product characteristic.
Products are grouped into 'product groups'.
I want to be able to run stat forecasts at the 'product group' level, and also adjustments via key figures at the 'product group' level.
For the 'product group', I could set up a planning characteristic or a navigation attribute.
What are the pros/cons of setting up a planning characteristic or navigation attribute, bearing in mind the need to forecast and make adjustments at this level?
Thanks in advance...

Hi,
The pros for using navigatyion attribute are quite easy: it will give you far more flexibility.
For example in case of change of hierarchy, you will not need to run realignment.
It simplify in the same way the data loading.
Now the cons: there is still some limitations: you can without any problem run stat forecast and adjustment for a navigation attribute. The only limitations I can remember are for promotion and store the assigment of a forecast profile to a selection (see /SAPAPO/MSDP_FCST2 - Assign Forecast Profiles to a Selection ).
this point might, or not, be the issue for you: do you plan to use the automatic forecast profile selection? If yes, then I suggest you to test it with navigation attributes; but as far I know it will fail. (note: I think there is workaround with a badi implementation, but can't remember which one now)
I hope it helps
Julien

Navigational attribute and FOX in IP

Hi,
I have experienced a strange behavior of a FOX.
This is a copy from ACTUAL InfoCube to PLAN InfoCube, keyfigures are different.
In the ACTUAL one, we have only cost center and profit center as navigational attribute. In plan, we have both. Here is the fox (operand is KF, infoprovider, profit center) :
{KF1, ACTUAL, PC01} = {KF3, PLAN, #}.
I doesn't work in IP (no data are read from the reference). We tested it in BPS and it works.
For me, this is the right syntax since profit center is not is the ACTUAL cube.
After that, we removed profit center from the operand (PC01 is a constant in the filter).
Here is the new fox (operand is KF, infoprovider) :
{KF1, ACTUAL} = {KF3, PLAN}. This fox is not supposed to work because it should try to read reference data with profit center PC01. But it works !!!
After saving data, we noticed that the fox copies every records from the ACTUAL cube with navigational attribute profit center = PC01.
Did you ever experience that or I missed something ?
The system seems to take into account the value of the navigational attribute.
Thanks

Hi Jaques,
I guess you have a MultiProvider and you have mapped the Characteristic PC from the plan cube and the navigational attribute from the actual cube both to the characteristic in the multiprovider.
Then it is correct, that the sytsem does the selection on the char in plan and the nav in actual.
regards
Cornelia

Navigational Attribute in BEx

Hi,
I have a problem with navigational attribute in BEx reporting. Product hierarchy 1 to 4 (0PRODH1 to 0PRODH4 referencing 0PROD_HIER) is a navigational attribute in 0MATERIAL. In query from an ODS I am able to include them and able to filter on it using a variables, but I am not able to get subtotal on the basis of PRODH3, but able to subtotal on the basis of PRODH1 & PRODH2.
I run RSRV on 0MATERIAL & 0PROD_HIER and there is no error on it.
If anybody know how to rectify this issue pls reply.
Thanks
EV

Try this:
My experience is that the property of showing subtotals in bex, is pointing at the characteristic to the left in your report of the one you are changinin .
If you have
Fiscal year, profit Center , Customer , Product,
And want subtotals on the two first. BUT NOT Customer and product..
The property show subtotals should be choosen for the first three.
Fiscal year, profitcenter AND customer.
Hope this helps.

Use of navigation attributes in APO DP

I am trying to clarify how navigation attributes compare with full planning characteristics in APO DP (V5).
In general, I know that navigation attributes are used for selection and navigation in APO DP.
But suppose I have a navigation attribute called 'product type' for planning characteristic 'product'. Isn't it also possible to forecast and make adjustments at the 'product type' level.
If the answer is yes, what is the real difference between the use of navigation attributes and planning characteristics?
Thanks for any help with this.
Bob Austin

You do not see difference in Attribute and characteristics in the interactive planning screen. So you should be able to create selections and do general navigation
just a little more detail on the difference between nav attributes and planning char
But creating forecast profiles might be a problem- Selections with navigational attributes do not create forecast assignment table entries. As of SCM4.1, the attribute information can be stripped out of the selection via BADI, allowing an assignment entry to be created.
Maintenance of CVCs also have to be done differently. Navigational attributes are not same as CVCs. Instead they point at the value of another characteristic. We create master data for nav attrib in the Admin workbench. Also If you plan to use navigational attributes on standard characteristics, say in 9AMATNR, then you could have issues in SNP since SNP does not support Nav attrib
Also realignment of Navigational attributes is not a standard process but can be done.

Navigation attributes in APO DP

I am using APO DP V5.
I have a planning characteristics of product and customer. I also have a characteristic of 'product group'. I am trying to clarify the <u>real difference</u> between modelling this characteristic as a planning characteristic or as a navigation attribute of product.
Based on my testing, using product group as a navigation attribute, I can select by product group and apply fixing and disaggregation.
So, what is the 'added value' of modelling 'product group' as a planning characteristics?
Any feedback appreciated.
Thanks, Bob Austin

To quote OSS note 413526
When defining a planning area you have the option of using either basic
characteristics or navigation attributes. With regard to the design the
following aspects should be considered:
Navigation attributes:
===========================================================
The use of navigation attributes adversely affects performance during
data selection and during navigation in the interactive planning. The
number of used navigation attributes is important and not the different
specifications of a navigation attribute.
It is very easy to realign the planning objects since only the master
record table of the affected InfoObject has to be changed.
Navigation attributes can not be used as a characteristic during the
definition of a fixed aggregate.
During the disaggregation a navigation attribute can never represent the
lowest planning level.
Navigation attributes can not be used in the promotion planning, in
other words an 'assign object' is not possible for navigation attributes.
Basic characteristics:
===========================================================
In comparison with navigation attributes, the exclusive use of basic
characteristics improves the performance.
It is possible to realign the planning objects, but this is more
complicated.
Basic characteristics can be used during the definition of aggregates.
Both navigation attributes and basic characteristics can be used during the
data extraction.
It is therefore not possible to give a clear-cut recommendation for or
against navigation attributes.

APO Demand Planning - Navigational Attributes BADI

Hi,
I have an issue in that I need a Navigational Attribute to be able to store the GUID for a Forecast Profile to a Selection. In standard, only a selection with Key Characteristics can do this. It is not practical for us to use a Key Characteristic because the realignment would take to long therefore it needs to be a Navigational Attribute.
Having read the note "Use of planning characteristics vs navigation attributes in APO DP " dated 19/10/2009 in SAP Solutions » SCM - APO Forum, it indicates that there is a BADI work around to enable this to be done but cant remember which one.
Does anyone know the BADI can be used to achieve this?
Thanks
Mark

Prabhat
Please refer to OSS note 413526 for a comparison of Navigational Attributes v/s basic characteristics. While most planning tasks can be done with navigational attributes there are a few limitations.
Rishi Menon

#MULTIVALUE on ratios with navigation attributes

Similar Messages

Maybe you are looking for