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.

Similar Messages

Navigational attribute issue-time dependent

Hi all,
I am working with 0PA_C01, I included some additional navigational attribute(time dependent )to 0employee, but when i am checking all these navigational attribute at cube level or Report , i can find only the latest values ,for eg i added Designation as a time dependent navigational attribute for 0employee, and the designation for a employee is changing after 12.2008 from VP to SVP ,at the cube   and also in the report i can find only the latest designation for all the calmonth ie before 12.2008 also as SVP .
I checked the the time dependent Navigational attribute option to make designation as a time dependent navigational attribute ,and also ran the attribute change run .
Can anyone suggest some information to fix it?
Thanks
Sandhya

Dear Sandya,
Results correct only in your report. Time dependent attributes displyas data based on keydate. if no key date specified, system takes current date as key date and displays data.
So in your case latest data displaying. If you want to see any historic designations, you need to specify key date, which shold fall into that particular range.
Create a User entry variable for keydate and use.
Key date
Each query has a key date. For time-dependent data, the key date determines the time for which the data is selected. The default key date value is the date on which the query is executed, that is <Today>.
       1.      Click on the Key Date field. A dialog box with a calendar appears for you to select your key date.
       2.      Select a date from the calendar. If you select 01.01.1999 for example, time-dependent data is read from the 01.01.1999.
Note
The key date applies only to time-dependent data.
Check: [Query Properties|http://help.sap.com/saphelp_nw04/Helpdata/EN/07/0ab63c71f41d5ce10000000a114084/frameset.htm]
Srini

Navigation attributes issues

Hi,
We have an infocube with a navigation attributes 0CUSTOMER_ORDERTYPE. The ORDERTYPE is in the master data 0CUSTOMER and updated using a program (contrary to the other 0CUSTOEMR attributes).
When we see the master data 0CUSTOMER, we see that the ORDERTYPE value for the customer number "1200" is not blanc (value is "DSM"),
BUT when we see the the infocube (listcube), ORDERTYPE value for the customer number "1200" is blanc.
For information, the ORDERTYPE is updated using a program (and not using direct loading).
Do you have any idea to explain this issue please?
Thx.

Is ORDERTYPE time dependent or time-independent attribute of 0CUSTOMER?
In the infocube, Is ORDERTYPE present as a characteristic in one of dimensions of Cube or is it enabled in the navigational attribute section.
If it is in the dimension section, then the value you see in the cube is as of the time of loading the data into the cube. It means if the data was loaded two months ago then the value reflects the value in the 0CUSTOMER master data two months ago. It may or may not be present at that time.
If it is in the navigational attribute section, then mostly the current date or the keydate us specify in the listcube main selection screen is being used to look up the value of the ORDERTYPE. Make sure 0CUSTOMER has a valid ORDERTYPE as of the respective keydate.

Navigation attribute issue

hi all..
i have problem with navigation attribute :
there's infoobject 0MATERIAL and navigation attribute ZPROLL
I have set ZPROLL as navigation attribute of 0MATERIAL in the cube.
For example data :
0MATERIAL      ZPROLL    AMOUNT
100001                  A                5
100002                  A                4
100003                  A                5
100004                  B                7
100005                  B                10
Is there a way to show the data such :
ZPROLL         Amount
A                         14
B                         17
Is navigation attribute able to be independent in query?
thanks a lot.

Hi Jane,
If you want to use ZPROLL as navigational for 0MATERIAL.
You have to enable ZPROLL as a navigational, in master data attributes of 0MATERIAL and also in the provider (cube/dso) you have to enable this ZPROLL as navigational.
Then you can use this ZROLL independently in query , you will get output as per the requirement if u remove material from query.
Thanks,
Joseph.

Issue when using Navigation attributes for filtering in BEX

Hello,
We are encountering an issue when applying filter on Navigation attributes in BEx query built on top of a BW HANA Virtual Provider.
The interface is as below :
HANA Calculation View -> SAP BW 7.4 Virtual InfoCube -> Multiprovider -> BEx Query.
We have directly mapped the base Infoobject from HANA View to BW Virtual Provider and using this in BEx query free characteristics. We also have used the navigational attribute of this Infoobject in our Report variable screen as well as an Auth relevant object.
Eg if ZMATERIAL is the base infoobject and ZMATERIAL__ZXYZ navigational attribute is used in the report variable screen and as Authorization variable.
This is causing the query to fail.
The query also fails if I apply any filter values on any Navigational attribute with error message :
"Termination message sent ERROR DBMAN (305): Error reading the data of InfoProvider"
Using the navigational attribute with authorization variable fails with below :
"Termination message sent ERROR DBMAN (099): Invalid query;Failed to find attribute ZMATERIAL__ZXYZ [...]"
Appreciate any inputs on this issue and how this can be fixed.
Thanks,
Tintu

Hi Andrey,
Thank you for your input.
Based on the OSS note , it says to import BW7.4 SP7. We are already on BW7.4 SP7
We get error "Termination message sent ERROR DBMAN (099): Invalid query;Failed to find attribute
ZMATERIAL__ZXYZ" whenever we try to apply filters on any of the navigational attribute.
Thanks,
Tintu

Navigational Attributes are not shown in query

Dear all,
I have a problem in a query. I need to present values using by using Navigational attribute in the query, the thing is that it does not recognize my navigational attribute. I have checked the characteristic in the Multiprovider and Infocube as navigational. And in the Multiprovider I have identified the navigational attribute from the right source.
What I think is strange is that I can see the navigational attribute when I see the data in infocube but not in the query. Does anyone knows what I might be doing wrong?
Best Regards and many thanks,
Mazzz

Hi
plese try to find out the data for this fields through LISTCUBE,if you gets data here for that navigation attr then it has to appear in your query designer also.
and also once again check your idetification for the navigation attr in multi provider whether its taken from write souce or not.and plese chk through your cube also for the navigatin.
in cube navigational attr has to mark then in the same way in the multi provider also
mahesh
Edited by: Mahesh Kumar on Jun 2, 2008 10:47 AM

Navigational Attribute not found on Query for an Infoset

Hi Experts,
I have created Infoset on two DSO's and when i'm trying to query on it i'm not able to find the Navigational Attribute which are selected on both of the DSO's.So in order to get the Navigational Attribute on the query of the Infoset what should i need to do.
Pls Help.
Thanks in Advance.
Amit

Hi Amit,
There is no other way to achieve this from the Infoset....
As suggested by Tulsi.. u can include them in the DSO level.. but it requires enhancement and reloading etc.. and its costly..
Or is it possible to join the master data infoobject if the design works out.. but this also depends how many number of Attributes from how many number of MD that u are looking into..!!
Thanks
Hope this helps

Unable to use Navigational Attr in the query ?

Hi experts,
We are using BEx 3.X.
We have a report based on an infoset. We want to use some navigational attributes in the query and
restrict the values of these attributes.
But we are unable to use them as navigational attr. They are displayed as display attributes only.
We are unable to restrict them. This is because the query is on Infoset.
When i use the same navigational attr in a query based on a infocube, it is displaying as Navigational Attr.
We are in BI 7 but using BEx 3.X.
How to resolve this ?
Regards,
Nishuv.

Hi,
Master Data Read
A simple master data read should be done using generic BI functionality in the update rules. Choose the
option u201CMaster Data Attribute ofu201D in the update rule details for the selected characteristic and select an
attribute by using the F4 help. With this setting, the value of the characteristic to be updated is read from the
master data table of the specified characteristic.
Characteristic Material is provided by the InfoSource.
Characteristic Material Group is not provided by the InfoSource.
Characteristic Material Group is an attribute of characteristic Material
Therefore you can fill Material Group from the master data table of Material: Select the method Master Data
Attribute from and Material as source.
The generic master data read only works for characteristics that are available in the communication
structure.
For a more complex master data read or if the characteristic is not available in the communication structure,
you have to implement the master data read yourself in a routine for the specific characteristic. If so, the
function module RSAU_READ_MASTER_DATA should be used to read the master data.
In Infoset u can use max 2 cubes......and Infoobjects 'N' number u can use.......
Thanks/Tarak

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

Unable to add Navigational attribute in Qery

Hi All,
Am a beginner in Bex queries. I need to add a Navigational Attribute, in a BEx Query. I did the following:
1. Turned ON the Navigational attribute in the Infocube.
2. As my query is on Multiprovider, i had mapped the specific field as well.
3. In the query, the 'Attribute' folder is added to the particular charcteristic in the infoprovider panel. When i try to drag to the navigational attribute into the 'Free Characrteristics', its not working out.
Am not sure about the procedure for adding the Navigational attribute into the Query. please help me in resolving this.
Thanks,
Chitra.

Hi Chitra,
Check if the navigational attribute is already there in Rows or filters area. it can't be in 2 places at a time.
First make sure the Attribute is navigational enabled at info object level.
Enable the object as navigational at IC level.
as you are using MP... you need to enable the navigational attribute in the MP and identify the object then you will be able to use the navigational attribute in the query.
Regards
KP

Integrated Planning on Navigational Attribute

Hello Experts ,
We are using BI 7.0 integrated planning.
We have a Report that is input enabled on Service . Service info Object is a characteristics in the info provider and is in the rows area of the Report . Input enabled was fine .
But I would like to bring Service which is navigational attribute of Fund center ie 0funds_ctr-bservice in the report(rows area) and want to plan against that service.
But when I bring this navigational attribute , now the query is not enabled for input . Do i have to any thing else in the Planning to make it input enabled .
Any ideas please .
Thanks

Andrey, indu,
Thanks for your reply.
Andrey,
I have put navigational attribute(Service) in the rows area and restricted with a variable . Still query is not enabled.
The query is not enabled as soon as i select Fund center in the Aggregation levels in IP.
If I remove(un check) fund center in the aggregation level , the query is input enabled . But i got to enable Fund center at aggregation level so that I can bring in Navigational attribute(service) of func cener.
Any ideas please .
Thanks

InfoSET - Characteristic restriction by navigational attribute.

Created an infoset on 3 ODS's
Checked the navigational attributes i wante in ODS. (eg 0country as attribute from ZVENDOR)
When building the query it is not possible to have the field as a navigational attribute,only as attibute.
When I want to use it as navigational attribute I have to add it to the ODS.
Only then it is available as Navigational attribute in the query.
When I Add ZVENDOR in characteristics restrictions and create a variable with replacement path "Attribute value" I get the message Replace variable with INFOOBJECT.
"Value 'I' is invalid for property 'Replace Variable With' of element 'ZVENDOR_ATTR'"
Define a valid value for property 'Replace Variable With' of element 'ZVENDOR_ATTR'
How do I resolve this variable error ?

navigational attributes are not visible in infoset, you need to include those nav-attrubetes physically in to your ods-data part to be able to navigate/filter.

Navigational Attribute in InfoSet

Guys,
I have requirement where in I need to use attribute of an attribute as a navigational attribute for a query on InfoSet.
I have InfoObject 0Employee in my Infoset. Org unit is attribute of 0Employee. and Area is in turn attribute of Org unit.
Now i want to use Area as navigational attribute in my query.
Is it possible?
Help on this would be much appreciated. and you all know I am always generous while awarding points.
Cheers
Kirk

Dear Kirk,
This is verymuch posible..see the following help document on transitive attributes..
http://help.sap.com/saphelp_bw33/helpdata/en/6f/c7553bb1c0b562e10000000a11402f/content.htm
Regards,
Hari

Navigational attributes time dependent in queries

Hello Guys,
I have a doubt, I have a master data with navigational attributes and time dependent and I need display from a query a comparative date between 2 navigational attributes; the value of the master data's attribute navigational and time dependent.
It is possible?
Thank you very much.
Regards,
Jeysi

I describe the case again:
I need display a comparative between 2 time period based in navigational attributes in a Query.
It is possible? I think that only a date is possible because the key date controls the output to the date specified or by default to today. Is it correct?, if I need keep historical information must save in the cubo each attribute neccesary for comparation to a period.
Thank you very much.
Regards,
Jeysi

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

Navigational attribute issue in query

Similar Messages

Maybe you are looking for