Filter by NAV Attrib in IProvider

Hi all.
I have a navigational attribute in characteristic & enabled in a InfoCube. I want to filter by this NAV attrib. in BEx. How can I manage this? I mean I see the sort possibility, but don't have any ideas how to filter by navigational attribute.
thanx in advance

Hi
Make sure that u have switched on the Nav attribute in the Infoobject -> attributes tab... and also in the cube........
Navigational wont be depend on the main charactristic..........
Khaja

Similar Messages

Nav attrib in master data

Hello,
i can't see any values for sales dist which is nav attrib of 0sold_to. All my r/3 transactions capture cutomer values in 0sold_to object.
0sold_to is created with reference 0customer.
0customer also has sales dist as nav attrib.
My reports and cubes don't show any values for sales dist. i want sales dist to be picked up from customer master data and displyed in reports.
i have loaded 0customer master data and it(master data for 0customer) shows values for sales dist.
i have not loaded 0sold_to seperately(as it is reference to 0customer).
Please suggest....
thanks

Hello A.H.P,
thanks a lot. i could also assign points to the earlier post today. there seemed to be a problem in assigning yesterday.
anyways, can u please elaborate on the need to run attribute change run? also do we need to select the infoObjects(which ones) in the attrib change run screen or do i need to run it for all objects availble?
also how do i use transaction rsrv? i have never used it before!!
thanks

Key Figure as Nav Attribute

Hi,
I'm working on BW3.5, and one puzzling requirement we've recently had is to provide a report on number of repaired assets by diameter bands.
There are some standard diameter bands given, like "<=5in or <=90mm", ">5in to 18in or >90mm to 500mm." *
This kind of a report is not possible by putting a KF into a cube/ODS and putting a condition on it because conditions would work at the entire report level. I could have done it by modelling the diameter as a NUMC characteristic (with the unit in another Z-characteristic) but the trouble is that diameter can be in decimals, for instance 3.75 inches. Bringing that into a NUMC characteristic will give it a nonsensical value of 375.
So I was thinking of a Key Figure as nav attrib of the asset itself. But once you include a KF as a characteristic attribute, BW does not allow the KF (and its corresponding unit) to be used as Nav Attribs. The button to switch it on as a Nav Attrib doesn't appear at all for that particular KF.
Maybe I'm missing something here. Can anyone give me a pointer?
Regards,
Suhas

Hi,
You cannot make a KF attr as nav attr. But you can use a formula variable processed by replacement path to pull in the value of this KF attr into the query and use it in a calculation. There is also a How To doc for this...you can find it on SDN.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/72f4a790-0201-0010-5b89-a42a32223ffc
-Vikram

Problem making an infoobject navigation attrib in multiprovider

Hi
I have a bespoke infoobject ZPNLATTRB assigned as a navigation attribute of 0ACCOUNT master data. I could successfully switch this infoobject as nav attrib in the cubes and dso. However when I tried to switch this infoobject as nav attrib in the multiprovider (containing those cubes and dso), I received an error 'Assignments for InfoObject 0ACCOUNT__ZPNLATTRB have not yet been maintained'.
The Diagnosis says:
The MultiProvider definition contains an InfoObject that has not been assigned to the relevant InfoProviders.
The Procedure says:
Choose Identification and highlight the assignment for InfoObject 0ACCOUNT__ZPNLATTRB, or remove the InfoObject from the MultiProvider.
I don't reckon I need to map the nav attrib ZPNLATTRB as its value is derived through 0ACCOUNT.
Please help.
Many thanks,
Anthony

Hi Sarah
Yes, thanks, I've managed to assign the nav attrib ZPNLATTRB in the multiprovider.. it took me some time to look for the 'assign'.
I have a further question relating to this. In my multiprovider I have included 2 cubes and an infoset and in this infoset I've included a write-opt. DSO. I had to create an inner join between my DSO and the 0ACCOUNT master data in order for the ZPNLATTRB to appear in the multiprovider for assignment between the infoset and the 2 cubes for this nav attrib.
I'd like to avoid using inner joins in my infoset as it slows down reporting. Do you know of a better way to design this model?
Please let me know.
Many thanks,
Anthony

Reviewed documentation on Reporting: I will appreciate some clarification

Hi,
Reviewed documentation on Reporting: I will appreciate some clarification:
1. Can you help me understand what "Staging" means as used here:
A data warehouse system serves primarily to stage information from various data source
The information is staged in various forms including personalized reports, freely definable queries, and predefined reports.
2. Is RemoteCube the same as Virtual Cubes? if not, what is the difference?
3. Can you help me understand what "flexible update" means as used here:
Characteristic InfoObjects have to be included in the InfoProvider tree in the Data Warehousing Workbench to make them available as data targets for flexible updates and as InfoProviders for reporting.
4. "DataStore Objects are available for transaction data and for master data."
When do we decide to store master data in a DSO?
5. Formula Collision vs. "Exception Aggregation"
I understand what formula collision is about but is it the same as "Exception Aggregation"?
If not, do you have a real-life example to help me understand the concept of "Exception Aggregation"?
The documentation/link is not helping.
6. i. With the followin limitation on Display attribute, why not always make the attribute Navigational?
"You can show Display Attributes in a report in the drilldown. However, navigation steps are not possible. (For example, you cannot choose values from a display attribute as a filter.)"
ii. Any example where Nav Attrib does not make sense but it must be Display attrib?
Thanks

Hi Amanda,
2. Is RemoteCube the same as Virtual Cubes? if not, what is the difference?
Yes, they are one and the same.
3.Can you help me understand what "flexible update" means as used here:
Characteristic InfoObjects have to be included in the InfoProvider tree in the Data Warehousing Workbench to make them available as data targets for flexible updates and as InfoProviders for reporting.
in 3.x, you have infosources and not transformations. So you have basically two types of infosources, direct update and flexible update.
Direct update infosources do not have any update rules. These are used for master data loading since the format of data is usually fixed as in fields etc.
Flexible update datasources have update rules, which means that you can use it for loading pretty much anything. You can load master data by changing the update rules and you can use the same infosource for loading transactional data as well. What the statement means is that the infoobject has been set as an infoprovider. and therefore it can be used as a source in a query. The loading is done via flexible updates.
More info on direct and flexible updates can be found here :[3.x InfoSource Types|http://help.sap.com/erp2005_ehp_04/helpdata/EN/87/3fdf9587f211d5b2ff0050da4c74dc/frameset.htm]
5)Formula Collision vs. "Exception Aggregation"
I understand what formula collision is about but is it the same as "Exception Aggregation"?
If not, do you have a real-life example to help me understand the concept of "Exception Aggregation"?
The documentation/link is not helping.
I'm glad that you understand what formula collision is...since its a difficult concept. Exception aggregation is much simpler.
For every key figure that is present in BW, there are two types of aggregations that can be maintained.
Standard: can be sum etc.
and exception aggregation like avg etc. When you do this, you need to give a reference characteristic. By default this is time. and usually it is summation. Now when you drilldown in your query based on the ref. characteristic, the exception aggregation is used.
Eg [http://help.sap.com/saphelp_nw70/helpdata/en/d2/e0173f5ff48443e10000000a114084/frameset.htm]
6. With the followin limitation on Display attribute, why not always make the attribute Navigational?
"You can show Display Attributes in a report in the drilldown. However, navigation steps are not possible. (For example, you cannot choose values from a display attribute as a filter.)"
ii. Any example where Nav Attrib does not make sense but it must be Display attrib?
Essentially this is a preference or a personal choice basically. You can have several attributes. but keeping all of them as navigational does not help and degrades system performance as they have to be interlinked. For eg.
You have an employee ID as your characteristic.
attributes are as follows
Date of birth
division
salary stack
*** etc
now things like division,salary stack and *** could be used as filters in a query but date of birth would in general not be used as filter and hence would make no sense to use it as a navigational attribute(unless you want to find all employees whose birthday is a certain date ).
In the end, it just comes down to the requirement. If you are required to put a filter on an attribute of master data, then it needs to be a nav. attribute else a display attribute would suffice.
Hope this helps.
Regards.

ALPHA conversion error in Crystal and MDXTEST

Hello Experts,
I've a BW query which is running fine without errors But when a cross tab report is created in Crystal, we get the below error upon execution:
"Characteristic value xxx of Characteristic ZXX is not ALPHA converted"
The same error when run in MDXTEST.
The InfoObject ZPRFTCTR and all its nav attribs has got ALPHA conversion enabled. Also, I am doing alpha conv in my expert routine of this infoobject.
RSRV checks show no errors.
No error while accessing data from cubes in BW.
This error is only in Q and P not in D.
I've re-activated Infoobject and transformation and transported to Q then reloaded the master data but still the same error.
Have you guys faced this issue before? What could be causing this error. Please help.

Hi,
as this error also shows up in transaction MDXTEST it clearly indicates that the issue is already happening in the BW stack without the involvement from the SAP BusinessObjects tools.
I would suggest you post your question into the SAP BW Forum.
regards
Ingo Hilgefort

How do I display variables in a query in Bex Analyser 7.0?

Is this option gone in 7.0? I know I can insert navigation pane or filters, but how do I display what variables have been used to run a particular query?
I run a query and there is no way of telling HOW I ran it... I am surely missing something here, no?
Also, I know that SAPBExQueries sheet is gone in 7.0. I used it to override variables values and force query/workbook refresh with the new variables (as a way of automation of a report). How do I go about this in 7.0 if I don't even see the variables anywhere? What other way of forcing a workbook to refresh for, say, 10 different clients?
Thanks,
A.

Jacob,
Many thanks for your reply.
As for Bex, you said:
"So any query needs to start in a default workbook design where you got the filter and nav pane. Then you got a "Variables Screen" option."
Regardless of whether I run a stand alone query, or I insert analysis grid, nav pane and filters in the design mode, my variables are not dislayed anywhere. What do you mean by "then you got a variables screen option"? Where is it? I checked toolbars, menus, properties, I couldn't find anything. I can, of course, change variables, if that's what you mean, but I still can't display them on my worksheet. So if somebody's looking at my query they have no idea what variables I used.
As for broadcasting, sorry, it's not an option. By "say 10 clients" I meant "say 100 clients" times 20 different managers i.e. 200 different variants (seperate reports) Not possible to use a broadcaster, I am afraid, as the list of clients, managers and fiscal periods (and other variables) changes too often and we need to have the flexibility.
By looking at the new 7.0 I fear we will need to stick to the version 3.5 for that reason. Worrying...
Cheers,
A.

IP: Use of input-ready variable in planning function

Dear all,
I'm using an input-ready variable for fiscal year (0P_FYEAR) in my input ready query. It's used for restricting my columns.
I'd like to use the value of this variable in my planning function and I use VARV for that in the FOX.
However, when implementing the pl.function as a button in the BEx Analyzer I need to fill in the static parameters the VAR_VALUE_1 with a value.
If I delete this line from the static parameters my plfunction end swith an error.
I like this value of course to be filled with value of fiscal year entered by the user when starting the query.
Does anybody know how to solve this?
Kind regards, Harjan

Hi Johannes,
Thanks for all the useful information!
Another thing on using PF.
I've got two workbooks with different queries but using <u>same</u> filter.
Queries differ in keyfigures, but are on same cubes in MultiProvider.
I can run the workbooks simultaneously: no locks occur.
I've got two planning functions that make calculations on the keyfigures entered in the workbook.
However when I inplement the PF's in both workbooks and assign the dataprovider as filter, i do get locks!
So, the PF also uses the same filter, but doesn't take into account the different keyfigures.
In the fox-formula i don't have the option to make conditions on keyfigure values (field keyfigname), neither to enter them in the filter.
Do you have any thoughts on this?
<u>Second</u> point:
When i filter on a navigational attribute and execute the pf, i get errors on my pf.
It states it can't find the value of the characteristic to which the navigational attr belongs. F.i. when i filter on nav attr 'customer group' (attr of char 'customer') and execute pf, the system gives an error on the value of char 'customer'.
It states: value of characteristic customer is notincluded in the selection.
Any thoughts on this one?
Thanks in advance!
Kind regards, Harjan

0sold_toparty- 0sales_dist

Hello,
i have sales district as nav attribute of 0customer.
i want to show data for sales district by picking it from customer master in the reports.
The r/3 transactions capture 0sold_toparty (and not 0customer directly).
so i created sales dist as nav attrib of sold to party.
sold to party is (not sure) created by reference with 0customer.
Reports dont show values for sales district field.
can you please suggest?
thanks

Hello,
Just to bring it on top.
i can't see any values for sales dist which is nav attrib of 0sold_to. All my r/3 transactions capture cutomer values in 0sold_to object.
0sold_to is created with reference 0customer.
0customer also has sales dist as nav attrib.
My reports and cubes don't show any values for sales dist. i want sales dist to be picked up from customer master data and displyed in reports.
i have loaded 0customer master data and it(master data for 0customer) shows values for sales dist.
i have not loaded 0sold_to seperately(as it is reference to 0customer).
Please suggest....
thanks

Undoing the changes made to DSO

Hi
One of our developers had modified one DSO and its transformation etc long time back and since the change was put on hold did not transport it to Quality or Prod. Now we have to make other changes and transport these. Is there any way to identify the changes made before, other than manually comparing with Prod and removing one by one.
Is there any table which has change version or some other info.
Please let us know.
Thanks In Advance
Aparna

Hi Aparna,
Not sure about transformations, but you can get for the DSOs by a roundabout technique. In your DEV box, go into SE11 and open up the active data table of the DSO.
Then, follow the menu path Utilities --> Versions --> Version Management. A new screen will open up, and at the top there will be a button called Remote Comparison. Click it, and then enter your production system's ID in the Target Sys field.
It will then show you a list of differences between the production and the development DSOs. This should avoid the manual comparison bit for all the InfoObjects, though you'll still have to check manually for stuff like Nav Attribs, DSO properties etc.
Regards,
Suhas

Use of planning characteristics in APO DP

I am using APO DP V5.
In my planning object structure I have the following planning characteristics:
- product
- product group
- customer
Suppose I am extracting history data (based on despatches) from an attached ECC system.
As I see things, I have two alternatives for the extraction of 'product group':
1. Extract the product group when I extract the despatch data from ECC
2. Model the product group as an attribute (display) of the product InfoObject, maintain this attribute as part of APO master data, and then read the product group from the product master data when I extract the despatch data from ECC.
What is 'best practice' in this situation.
Thanks, Bob Austin

Bob
Both your Options being valid technically and will work you need to now judge based on the demerits of the methods based on your situation
If you expect a huge CVC population and dont to have say a million CVCs you would want to use attributes thus effectively distributing it into two tables
Your Product Group to product will be one to many i suppose so the CVCs in your MPOS will be reduced by a factor or that ratio
Now this also means that you will need to look at a join of the table if you are using you Attributes as selections. So that is going to take more time and if your client is not patient youo may not want to take that route
Also your downstream planning process and your regular maintainance of your system needs to be considered.
Attributes are good if you want them just to navigate but if you want a forecast profile or if you want a realignment based on them it might end up to be a bit of a pain. I remember we had a post from you on this one and there are a few more points that are not favorable to Nav attribs
So youo need to weigh in the advantages each of these will give you and how much weightage you place on these advantages for your situation.
If you have the Prod group in ECC and can extract it i would prefer that option. Looks straightforward that way

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.

Navigationa attribute ubavailable in query.

Hi,
I made a display attribute as navigation attribute. Made repective changes in CUBE and Multiprovider.
I can not see this nav. attribute in query. Can anyone suggest what i could have missed.
It is available in DEV system and was successfully moved to Production system. All the changes from IO till Multiprovider are there in Production too but not in query.

Hi,
After the changes, in the multiprovider and Cube, the New Nav Attrib would be available under some dimension in the query. Drag and drop it into the reqd area(Rows/Free Charac) as per ur need. Then transport the query to ur prod.
Regards,
Rahul

Editing the Valuation/Reqt Characteristics in APO

Hi All,
We are working with Variant Config (ECC) & CDP (SCM 7.0) for a Mill industry & have a requirement to be able to edit/change the Valuation/Requirement characteristics on the Receipt elements like Planned Order/Production Order in APO.
So, when we create a Sales Order, the CTP run generates planned orders on the machines for us. The sales order gets the Valuation & the Requirement characteristics, while the corresponding Planned Order gets the characteristics. We want to be able to edit the Planned Order char's to change/insert some value on char's that are blank.
Is is possible to do that in APO?
Your inputs much appreciated
Thanks

Bob
Both your Options being valid technically and will work you need to now judge based on the demerits of the methods based on your situation
If you expect a huge CVC population and dont to have say a million CVCs you would want to use attributes thus effectively distributing it into two tables
Your Product Group to product will be one to many i suppose so the CVCs in your MPOS will be reduced by a factor or that ratio
Now this also means that you will need to look at a join of the table if you are using you Attributes as selections. So that is going to take more time and if your client is not patient youo may not want to take that route
Also your downstream planning process and your regular maintainance of your system needs to be considered.
Attributes are good if you want them just to navigate but if you want a forecast profile or if you want a realignment based on them it might end up to be a bit of a pain. I remember we had a post from you on this one and there are a few more points that are not favorable to Nav attribs
So youo need to weigh in the advantages each of these will give you and how much weightage you place on these advantages for your situation.
If you have the Prod group in ECC and can extract it i would prefer that option. Looks straightforward that way

How to get exact user input in inverse expert routine?

Hi
I have created an inverse expert routine on a virtual provider with DTP for transformation from an infocube. The virtual provider is part of a Multiprovider. I have a query which fetches data from the virtual cube.
I have the hierarchy enabled for the Iobj 0cust_sales in the query and the user inputs the values during execution of the query. Is there a way by which i can get the exact input given by the user in the selection screen in the inverse expert routine?
I also have some variables on nav attribs of some fields these restrictions are not avaible in the dimensions list. Is there a method by which i can get these variable entries as well in the inverse expert routine?
Regards,
Sujai

please refer to this SAP Help and hope it can solve your question.
http://help.sap.com/saphelp_nw70/helpdata/en/45/f1f9b861c706f9e10000000a155369/content.htm

Filter by NAV Attrib in IProvider

Similar Messages

Maybe you are looking for