Navigational Attribute change

Hi Gurus,
I have one requirement like the below.....
One info object contains 15 attributes...and this is used in few data targets also.
From this info object I would like to change one attribute from display to navigational attribute, will it be affected the data targets if i change the attribute from dispaly to navigational.
Thanks your reply.
Regards,
Rams.

Hi Rams
You will not have any impact on changing the Attribute from Display to Navigational.
This will not make any changes to the Datatargets.
But if you want to amke Nav to DIsplay it will make the Datatargets to Inactive where and all that infoobject is used.
Before doing that do think its necesary or not and then proceed, hope you may be looking out for the usage for the usage of drill down option for that Attribute in the report
Regards
PBI

Similar Messages

Error while changing the Display Attribute into Navigational Attribute

Hi all.. Gud Mrng.
I was changed the attribute (product) from display attribute into navigational attribute and while save and activating the info object it is not getting activated and it is throwing the below error message.
Error Message: u201CThe Info object is being used in several data targetsu201D
My Questions:
i) Do I need to delete the data from all the data targets (where this info object is using)??
ii) Do I need to delete data only from the main info object (Zmaterial)? Is this single action enough?
Please suggest me which action I need to follow & What are the precautions need to take while changing the Display Attribute (product) into Navigational attribute of info object (Zmaterial).
Thanks in advance.
Thanks & Regards,
B Venugopal

Hi Garima
Only in case of key figures we cannot change it from display to navigational.
If the info object is a characteristics then in the General tab of the info object if you select 'attribute only' then the iobj would be a display attribute only. If you leave it unmarked then you can use the iobj as a navigational atribute.
I am sure you know that these settings only mean if a IOBJ can be used as display or navigational. To use it as a navigational within another object you will have to change the settings from 'DIS' to 'NAV' for the said info object in the 'Attributes' tab of its parent info object.
Further if you use the parent info object in any data target / infio provider you will have to further mark the info object as 'navigational' while defining the attrbute of the said data target / info provider. The info object gets displayed in the data target / info provider attribute properties as 'parent IOBJ_info object'
Cheers
Umesh

How to change an characteristic to an navigation attribute?

Hello everyone!!
Does anybody knows how to change a characteristic that is on a POS to an attribute navigation of another characteristic that is in the same POS without deactivating it?
An infocube has the same POS characteristics. So, if I do this modification, the infocube will be automatically chaged? I think not, but I want to avoid manually changing almost everything.
Thanks in advance!!
Regards

Hello Heidi
Sorry if I took so long to answer.
Unfortunately you will have do deactivate the POS and of course change all the infocubes, infosources, etc, that are involved with this change. If you deactivate your POS, all the CVC´s are eliminated, so it will be better if you backup all the data in your live cache in an backup infocube.
When you change the characteristic to an navigation attribute and also change the infocube, the data in the infocube will adjust automatically. You will have to create the CVC´s again with the new "format". But in the infocube, it won´t be necessary.
I hope it helps.
Best Regards
Angela

What the big impact change the navigational attribute

I do have infoset contained 3 DSO,
1 of the DSO have 0JOB which we need to set as Navigational Attribute..
The the most impact and precaution that I need to think before take this step..
i know that base on your experience .. hope that you could share with me ..
Point will be assign
thank you

Hi...
You can set 0JOB as navigational attribute....no probs...........
But........navigational attributes require additinal joins during query runtime........so it has an impact on the performance..........It will slow down the query performance.............moreover if u hav aggregates on the cube.......during attribute change run .....adjustment of aggregates will also slow down.........due to this we should always try to minimize number of navigational attributes..........u also consider how often the query will run.............
Hope this helps.......
Regards,
Debjani......

Is it possible to change 0currency as navigational attribute

Hi Guru's,
It is possible to make 0CURRENCY as navigational attribute.
Please Clarify.
Thanks,
Deepika

Thanks Satya
Your answer gave an understanding.
My Actual problem is
I have requirement to show Annual Salary which is attribute of 0Employee in the report along with currency.
Report is based on Multiprovider which contains 0Employee in one of its dimension.
And this 0EMPLOYEE_ZSALARY is part of Free Chars of Report.
As Annual Salary (0ANSALARY) is Keyfigure If I add this as attribute it will be display attribute
then it is not possible to bring it to multiprovider level and show it in the report.
So, I have created ZSALARY Characteristic added it as navigational attribute of 0EMPLOYEE but if I do
this how can I show currency along with ZSALARY.
ZSALARY Char cannot have 0CURRENCY by default as this is character not a keyfigure.
One more problem here is 0CURRENCY is also display attribute.
Any ideas please help.
Thanks,
Deepika

Unable to view Navigational Attributes in ODS

Dear All,
We have enabled Material Group as Navigational Attribute in Material. Material has been included in ODS as Key Field. In ODS also Material Group is switched as Nav Attr. Now when I check in Reports I am getting # for all Material Groups. I checked in ListCube. Here also I am getting # values.
I did master Data Activation and also did Attribute change run. Where as I am able to view values for Material Group in Material Master Data.
Regards
Ravi Y

Hi Ravi,
You could check if the X/Y table of material group are correct.
Do RSRV combination check on the info object material and material group. Run all the tests...espeially the consistency of X and Y tables..
Also, you could probably check if this is some authorization issue... that you dont have authorization to view contents of material group...(may not be the case, but worth a check )...
Sounds strange though, if all is ok and u still dont see material group. (and sometimes it cud be a refresh issue as lalit suggests....., if it has to get wierd )
Hope it helps,
Regards,
Sunmit.

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

Navigational attribute in Cube

Hi Gurus,
I want to understand one point before I am going to perform a small enhancement.
I need to set a navigational attribute in a cube(before it is not checked on "I/O") meaning make this navigational attribute behave as a char., but this cube contains data already, my question is :
can I make this change ? if yes any other additional effort?
Thanks in advance

Hi Ryan,
The attr needs to be marked and activated as Navigational Attr in the parent char first. Then you can mark it as nav attr in the cube (which contains the parent char). Does not matter if the cube contains data...you can do this activity in a cube with data. Remember to reactivate the cube's update rules and any multiproviders that it is a part of after you make this change.
Hope this helps...

Effect of Full Attribute Extract on Aggregate Attribute Change Run

Because we extract data that does not trigger the change pointer on 0CUST_SALES we do a FULL extract of this data daily instead of a DELTA. We recently created an aggregate which contains navigational attributes of 0CUST_SALES (namely Sales Office & Sales Group).
My question is does the system look to see if any information has changed between the new and old values or does it assume since there is a new version for every entry that 100% of the values have changed?
The reason I'm asking is BW appears to be rebuilding this aggregate from scratch each day instead of changing the aggregate for the few entries that actually changed.

I did a FULL extract for 0CUST_SALES in our QA system. It transferred 28617 records. When I look into the monitor > processing > data package 1 > update I see the following:
3 data records in table /BI0/XCUST_SALES marked for deletion
3 data records inserted in table /BI0/XCUST_SALES
3 data records n table /BI0/PCUST_SALES marked for deletion
3 data records inserted in table /BI0/PCUST_SALES
Different database operations were executed
When I run the attribute change I see the following messages:
The Change Run is executing
Attribute 0CUST_SALES__ZZROUTE for basic characteristic 0CUST_SALES: 2 changes
Attribute 0CUST_SALES__0BILLTOPRTY for basic characteristic 0CUST_SALES: 2 changes
Attribute 0CUST_SALES__0PAYER for basic characteristic 0CUST_SALES: 2 changes
Attribute 0CUST_SALES__ZZACGRP for basic characteristic 0CUST_SALES: 2 changes
0001 ZSD_C02    100016     Aggregates Will Be Adjusted by:Reconstruction
0002 ZSD_C02    100019     Aggregates Will Be Adjusted by:Reconstruction
After seeing this i revisited the documentation for threshold value in RSCUSTV8. Ours is BLANK! So according to the documents when it is blank the aggregate is reconstructed generally. Not what we want!!
I will change the setting to the suggested 20% to start and we'll work from there.
Thanks for your help Oliver.

Virtual infoprovider with services - Navigational attributes

Hi all,
I have a basic cube in BI system- X , and created a virtual cube in another BI system Y with services to read data from basic cube of BI system X . In BI system Y we built a report on virtual cube. This report (on virtual cube in BI system Y) is using a characteristics say Product group ( which is a navigational attributes of prodect in BI system X).
DataFlow is as under:
Basic cube in BI system X:
Product
Year
Amount
and Product group is switched on as navigational attributes in this basic cube.
Virtual cube in BI system Y:
Product group
Year
Amount
Report in BI system Y:
Product group in rows
Amount in column
This report is not working.
If I do the the following changes as follows then it works:
1.Use Product instead of product group in report
2. Switch off navigational attributes in basic cube.
We are in BW 3.5 and navigational attributes option is ticked on for virtual cube.
In summary, If I do not use navigational attributes in report and switch off navigational attributes from basic cube then report shows data.
Could you please help me to figure out the issue.
Thanks,
Harry

Thanks Naga,
Yes, I tried adding product in virtual cube as well but it did not work. Secondly, we do not want to add product in virtual cube because of data aggregation.
Most strange thing is that, once we switch on any navigational attributes on basic cube, function module stop working (paasing any data to virtual cube report). report says no appropriate data found. We are using sap standard function module "RSDRI_INFOPROV_READ_RFC". I debegged this code and no data in internal tables.
If we switch off all navigational attributes from basic/source cube this function module provide data to internal tables in code.
Why function module is behaving like that.
You guys experience/support/any clue will be appreciated highly.
Thanks,
Harry

How to see Navigation attribute in Report

Hi ,
I am working on BI7.0.
In my Query , material is a characteristic which has 3-4 Navigation attributes. But when I execute the report , I can only see Material data displayed (because only material is in the rows). I also want to see data of its attributes in report results. I dont have authorisation to change the query.
Also I am unable to open the Query in Local view (some connectivity issues).
Can you please suggest How I can drill-down those attributes.??
Also these attributes are not visible in free characteristics.
Thanks,
Su

Hi there,
To use the navegational attributes with drill down, they have to be available in either rows, columns or free characterisitic.
For that you have to edit the query. There's no other way.
But each navegational attribute is also a display attribute.
Therefore, you can after executing the query, right-click over material and select properties. You'll see a tab named attributes where you can add the avilable attributes to the left (so they will be displayed), and change the settings of each one of them (see only key, key and text, etc.), but you can't filter by any of those attributes, or do any drill down options over them. They are only display attributes.
Hope this helps.
Diogo.

# values for navigational attributes in report . (Urgent)

Hi Gurus,
I have a navigational attributes for time dependent master data. In the report I am not able to see values for that navigational attribute. I see # values for the navigational attributes. I checked the master data of main info-object. every thing looks fine.
please help me in regarding this.
thanks,
Regards,
Aarthi

Check the following two things again just to make sure you are doing everything right. These are already mentioned by Bhanu...
1) Go to the master data table (Q table or the M table) and check to see if there are M version records (OBJVERS = M). If yes, you need to activate the master data using the program RSDDS_AGGREGATES_MAINTAIN (Change Run). If there are no M version records then check the second step
2) If you do not enter any key date in the query, it takes the system date as the default key date. So check and see if any master data exists for today's date ?
Also just curious, which version and support pack level are you on ?

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

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

Attributes are not displaying in Navigational Attributes area of DSO.

Hi Experts,
I have created a DSO and have included Info Objects 0SOLD_TO & 0SHIP_TO. In the Navigational Attributes area, its attributes are not getting displayed even though the attributes are in the info object.
What are the steps needed to perform for it to display there?
Waiting for your reply,
Thanks in advance,
With Kind Regards,
Shreeem

Hi Shreem,
If you want attributes of any master objects in navigational attributes section, you have make them navigational attributes while defining base info object.
Please follow the below steps.
1) goto RSA1, search for 0SOLD_TO & 0SHIP_TO info objects and open them
2) goto edit mode of info object and goto attributes section.
3) here you will find for every object "DIS" --- this means these attributes are display attributes.
4) If you want to change any attribute to NAV, then click on "Pencil Mark".
5) Now you can see text NAV instead of DIS for that attribute.
activate the info object and goto DSO, now you will see that attribute in navigational attribute folder.
Regards,
Venkatesh

Navigational Attribute change

Similar Messages

Maybe you are looking for