Navigational attribute in MP problem

Hi guys,
I checked a Nav. attribute in ODS and than marked the same Nav. attribute on a Multi Provider on top of it. Later on, I unmarked that nav. attribute from the ODS. The odd part is that it not that it let me do it, but that nav. attribute is still marked in MP and also I can see it in the report based on that MP. Isn't that unsual or there is some explanation.

Based on the fact that Navigational Attributes depend on the main InfoObject and not in the ODS where they're used and is part of the Multiprovider, it makes sense.
I'm sure you have the main InfoObject as part of the MP. If you remove it, you won't see the Navigational Attribute.
Regards,
Luis

Similar Messages

  • 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

  • Navigational Attribute Problem in Input Query

    Hi,
    I am having a problem in input query implementation which uses a navigational attribute. I have, for eg, only one char 'customer' in rows; i want to exclude the customers with the status D (deleted) from displaying (Status is nav. attr. of customer).  I tried this by restricting in filter, Status D-"exclude". But as soon as I do this, query no longer remains input ready! (I also tried putting the same restriction in Default Values area rather than Filter, but ended with the same result )
    I discovered that if, furthermore, I put Status in rows (with the above said restriction still remaining), query is again input ready.
    Can't we exclude values in the filter on an input query? I want to know if this is a restriction with IP or a bug?

    Hi Gregor,
    Thanks for the explanation. But this makes me wonder, because due to this restriction one of the BIG advantages queries had over the planning layouts of BPS, seems to be gone. I mean, using navigational attributes for filtering; if we have to always have a single value restriction on a nav. attr., this will really be restricting. Is it expected that this will be changed in a later SP?
    And there is another problem that is coming due to this. When I use the exclude filter and also the nav. attr. Status in rows, then the query becomes input ready, but there are warning messges displaying when the query opens saying -
    Characteristic Customer has no master data for "C1"
    Characteristic Customer has no master data for "C2"
    etc... (these are the customers with status D). We are on SP15.
    Please suggest what should I do to get rid of these messages?
    Edited by: Mayank Gupta on Apr 10, 2008

  • Navigational Attribute data is not display in Cube level and reporting

    Hello ALL
    Iam facing a problem like,I created Navigational attribute and I selected that navigational attribute in cube level also but data is not display in cube level.
    What will be the problem?Pl help me out.
    regards
    balaji

    Hi Dinesh
    You mean base characteristic means loading data after creating Navigational attribute?Is it this way,(orelse can u tell me about this base characterstic)
    Yes after making that particular attribute as a navigational attribute I loaded data in master data tables.
    How to run Attribute change run?can u give me steps
    regards
    balaji

  • BI-IP / Formula navigation attribute

    Hi,
    i have the following problem and hope somebody can help.
    I have a BI-IP planing function (Fox-Formula) which simply copies the keyfigure Amount from the characteristic company (#) to the characteristic company (8703).
    { KI_LCCUR, 8703 } = { KI_LCCUR,# }.
    this characterisic has also a navigation attribute headquarter.
    when i run the function the following error message appears:
    8703,# is invalid: Valid is 8703,DE. Characteristic "ZCompany"
    which means  to me the master data for charactersitic company 8703 and its attribute Headquarter # is not valid, which is true. But what do i need to do in order to use the right combination 8703,DE?
    Is there a way to make fox formula to find the right value for the attribute? is there a way use navigation attribute in fox formule?
    Thanks for your help in advance!
    Mike

    Hi,
    The problem can be due to the mapping in the cube.
    Please reactivate your cube.
    If you are using a multi-provider, then please check that the navigational attribute is defined in all the cubes in mulitprovider.
    Regards,
    Amit

  • Poor Performance with Webi on top of BW - Large Navigational Attributes

    We have recently developed a reporting model based on having a BW cube of approx 20 million records. This has 2 very large line item dimensions (one 14 million records, on 6 million records) that both have navigational attributes stored against them.
    We need the design to be like this because the attributes change monthly and we do not wish to do a complete drop and reload of cube data each month (this takes 10-12 hours).
    When we build a Universe on top of the cube and try Webi reporting the performance is dreadful - many reports time out completely. This happens whether or not the large line item dimensions are selected in the query. The BW query is very simple just 2 key figures and approx 30 Navigational Attributes as default values. No filters are applied.
    For example a query that just contains Calander Year and one key figure either times out after 10 minutes or fails.
    Our source of the data is Oracle tables and the same query runs in 2 1/2 minutes and the query runs in RSRT in approx 5 minutes with no problems so it is definately a problem with BOBJ to MDX to BW.
    We are on BW7.01 SP5 and XI3.1 SP2. SAP have recommend going to SP3 and using query stripping to help with this but I doubt if this will work.
    We have tried building aggregates, splitting into yearly cubes etc but nothing seems to help.
    My question is do the large navigational attributes mean Webi simply can't cope with this?
    Thanks

    Thanks for the suggestions.
    Although this did not directly help I've now found a solution.
    We had a calculated key figure in the query that doing a count of records on a huge navigational attribute. This was causing all queries to run very slowly (even if the key figure wasn't selected in Webi).
    Removing it solved the problem. Will have to find another way to  do the count key figure.
    Thanks

  • How to add Navigation attributes values via ABAP while creation of CVC

    Hi,
    I have a requirement like, I have to add navigational attributes to the cvc record while CVC creation ( /sapapo/mc62 transaction).
    There were two scenarios: 1. Usually when they load master data from BW side those navigation attributes available and when we do CVC creation it's automatically picks those values. If NOT then i have to bring Market segment and Business unit navigational attributes values from ECC via RFC function module by passing MPN and End customer division as a input.
    I am facing problem when BW side if business unit and Market segment were blank.
    Do we have any Function modules available to add navigational attributes data and should update corresponding master data tables.
    Please help me step by step process on this.
    Thanks
    Ravi
    Edited by: REDDY KALLURI on Jan 22, 2011 10:30 PM

    Michael,
    Are you intending this as a commercial solution or a work around?
    To take an existing equivalent, one would build a view in the database tailored for each grid in an Oracle Forms application. Or a separate query layered over tables for each form/grid in a Delphi or Access application? Even if it is ninety nine percent the same over half a dozen forms/grids?
    And now you've added a whole slew of "slightly different" rowSetInfos to maintain.
    So if you wanted to add a column that needs to appear everywhere... you've just increased the workload multi-fold?
    That would be a management nightmare, wouldn't it? Not to mention yet more performance cost and a slower system?
    Hmmmm..... I'm not sure I like where this is headed... someone needs to do some convincing...
    null

  • 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

  • "Error determining attribute" after adding navigational attribute to query

    Hello all,
    We are getting a "Error Error determining attribute, Abort System error in program SAPLRRK0 and form RSRDR;SRRK0f30-01-" error message when running a query after adding a navigational attribute. We tried adding the attribute of the characteristic directly in the query and this works ok. But when we try using the navigational attribute we get the error. We would like to use the navigational attribute so we can filter based on this attribute.
    We've searched for notes regarding this problem and haven't found any. Any suggestions?
    Thanks, Ron

    hi,
    Please check if  number of the fields after adding the Navigationl attribute the should not cross 50.
    Check the RSRV test for the master data whose navigational attribute u r trying to add.
    Thanks
    Mukesh

  • Navigational attribute in selection screen gives no applicable data

    Hi Gurus
    In the report i am using the navigational attribute in the selection screen.e.g Brand (attribute of material)
    My problem is whenevr i enter value in the navigational attribute (brand)  in the selection screen and execute  its says no data found.
    If i do not fill this parameter and fill only the parent attribute (material)  in the selection screen  , then i can see the results and from its properties  (drilling down )i can see the values of brand .
    If the values of brand exist why via selection screen its not giving vales, However Via material i can drill down and see brand values.
    I have done all the necessary steps to make this attribute as navigational.
    On top of this i have this same navigation attributes as one of the characterisitc in the cube.
    Thanks
    DD

    Hello,
    I've the same problem... for new nav. attributes for 0Material.
    Settings for nav. attibutes in BEx Q.D. are OK.
    But in BEx Analyzer:
    1- not display all values for this attributes. Some values are displayed, some don't.
    I try display it with and without selection screen.  The result is the same.
    2- I try to display (normal) attributes - not nav. In this case everything is OK.
    But I've 2 columns: normal attribute for all values and nav. attribute only with some values...
    (the query is something like: 0Material + 0Material_NOTnav_attr + 0Material_NOTnav_attr)
    It isn't a normal...
    I don't know... Maybe it's depend of the time?
    I can't clear all master data for 0Material, because they're used in some cubes. I had old characteristic without nav. attr. but with master data. I added nav. attr. in 0Material and activated it. Next I load master data (full method). Then I added nav. attr. in infocube, activated it, delete and load data into the cube (Init + Delta).
    If I display data for the cube in RSA1, I can see nav. attr. for all records. I can't see it in BEx Analyzer...
    Can U explain it?
    Thx,
    MSzN

  • Navigational Attribute is not properly displaying

    Hello,
    We have a "Sales Group" navigational attribute YCUST_SAL-YSALE_GRP in a BW report. We have adjusted a sales group for a customer in R3 from F10 to E49 and hte same has been pulled to BW side,.
    we have activated the master data manually and we are able to see the new data is available against the customer.
    But when we refresh teh report, for that customer we are able to see only F10 as the sales group,.
    For cross check, we have sales group display property also. where we are able to see E49.
    Please let us know why we are seeing inconsistency between display and navigational attribute for a same infoobject.
    Thanks. Karthik

    Hello,
    It seems Master data is not activated properly....
    Whether the query is fetching data from Aggregates, if so you have to do Attribute changerun for this infoobject
    goto SE38 and run this program RSDDS_AGGREGATES_MAINTAIN it will Info object name...Provide your info object and execute...
    Your problem will solve.
    Regards,
    pavan.

  • Navigational Attribute Filter value selection not showing full name

    Hi Experts,
    We are having Navigational Attribute TM Responsible. We have created variable in BEX for it. When we are searching for value selection for this in RSRT, its showing only last name and key part. But If I dont pass any values, and display the result its showing full name. Please find the screen shots.
    Customer needs full name to be available for selection in filter in above picture 1.
    Please suggest what needs to be done.
    Thanks,
    Govind

    Hi All,
    The issue is resolved. Making display as Long text at Infoobject level and at Query display level was not working. Hence I tried to change the display at Multiprovider level as shown below. This fixed the issue.
    Right click Navigational attribute -> Provider specific properties
    Made the display as Long text.
    This setting resolved the problem.
    Thanks for help and replies.
    Thanks,
    Govind

  • 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.

  • Navigational attribute issue in query

    Hi gurus,
    Here is a very tricky issue that I am facing. If anyone could please help me with a workaround for the same.
    I have an infoObject called ZDIV_CUS which is basically 0CUSTOMER with 0DIVISION compounded to it. Hence, when I load data into ZDIV_CUS, I would have one record for a unique combination of customer and division. In functional words, I would have one customer maintained for multiple divisions. ZDIV_CUS also has other navigational attributes as 0SALES_OFF, 0SALES_DIST & 0SALES_GRP. Also, I have 0MATERIAL, which has 0DIVISION as a navigational attribute in my cube.
    Hence the master data for ZDIV_CUS looks as follows -
    0DIVISION    0CUSTOMER    0SALES_OFF    0SALES_GRP    0SALES_DIST
    01           100000       L001          L01           L010100
    02           100000       L005          L08           L020150
    01           100001       L001          L01           L050150
    03           100001       L005          L02           L052542
    The transactional data in my cube is as follows -
    0MATERIAL    0CUSTOMER    0DIVISION    0SALES_OFF   0NET_SALES   0MATERIAL_DIVISION (Material master div)
    102152          100000       01           L002         110000       02
    102545          100001       02           L002         12000000     02
    The above data is all transactional except for 0MATERIAL_DIVISION which comes from material division.
    My query is built in such a way that the division comes from 0MATERIAL (restricted to variable in the selection screen). ZDIV_CUS and its navigational attributes are being used in my query. The initial display is shown as per ZDIV_CUS_0SALES_OFF (i.e. sales office from ZDIV_CUS)
    The problem is that say for eg for the above mentioned scenario, the user executes the query for division 01 and the below mentioned output comes up -
    0MATERIAL_DIVISION     ZDIV_CUS    0MATERIAL    ZDIV_CUS_0SALES_OFF     0NET_SALES
    02                     100000      102152       L001                    110000
    If we take a closer look, we would know that ZDIV_CUS_0SALES_OFF should pick up value L005 and not L001 since the division for which the query is run is 0MATERIAL_DIVISION and not 0DIVISION.
    Request help to resolve the abovementioned issue.
    Thank you,
    Sree

    Can any one answer for Issue-2. Even I am also facing the same.
    Thanks in Advance.

Maybe you are looking for