Transports issue regarding navigational attribute

Hi,
I used to have some navigational attribues in somecubes and Multiprovider but as per the latest requirement from the customer again converted them as display attributes in masterdata so that automatically removed from cubes and multiprovider with out even our interventions as we know..
So assigned to transport request and transporting into further systems then we r getting error as
"Navigation attribute XYZ does not (actively) exist
Message no. R7748"
but when i do check of cube it does not give any error but when i am transporting it is again loooking for those navigational attributes in target system..
I am not sure why it is giving problem like this ...Just i am guessing is it because i did not remove navigational attribute flag first from cube instead of just master data directly ...but that should not be a problem as per my knowledge...
Can any experts reply to me asap if you come accross this kind of problem ....
Thanks & Rgards,
BRK

Editted as I understand the solution now.
If you want to delete navigational attributes from a multi provider, cube and master data it needs to be done in the order:
- remove navigational attribute from MultiProvider
- remove navigational attribute from Cube
- set navigational attribute to be display attribute on InfoObject
If you don't follow this order e.g. just set navigational attribute to be a navigational attribute on master data then you get problem where every time you transport cube it says nav. attribute is inactive even though (as far as you can see) the nav. attribute does not exist.
btw, if you have dug yourself into a hole then you need to re-create the navigational attribute on the InfoObject and then add it back to the cube and multiprovider - transport this and then follow correct order.
Edited by: Mark Roberts on Oct 15, 2008 6:49 PM

Similar Messages

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

Issue regarding 0MATERIAL_ATTR - Attribute not Updated for Some Materials

Hi All,
As per requirement, I had enhanced 0MATERIAL_ATTR DS with one customer field MRP Controller.
After enhancing 0MATERIAL_ATTR, I had made necessary changes in related objects like 0MATERIAL Info Object & related transformation for this new attribute.
After making changes, when I had done Repair full request for 0MATERIAL_ATTR, newly added attribute had not updated for all material, other attributes were updated correctly but MRP controller had not updated for some records.
I am confused with why attribute(MRP controller) updated in some Materials & for some materials its not updated.
I had checked in PSA, data for this added attribute is come in PSA but not updated in data target (0material).
I had also activated master data by running Attribute change run but still problem persist.
Please help.
Regards,
Divyesh Khambhati

Hi Venkatesh,
I had write code in CMOD for MRP controller.
As data is coming fine till PSA but its not updated in Data Target (0MATERIAL) .
if I take one example..
For exp Material XYZ has two entries in PSA table, one is updated during delta load & recent one which come though Repair Full request.
Now newly adder attribute MRP controller available in recent request of Repair Full but that is blank in case of prior delta update.
I am confused because MRP controller attribute is updated for some Material but for some material its remain blank.
please help.
regards,
Divyesh Khambhati

How to use Navigational attributes in BEx

Hi experts,
I have searched many threads regarding navigational attributes in BEX.
But unable to find any info.
How the navigational attributes are used in BEx query designer.
What is the difference between characteristics and Nav attr in Query designer.
Every one n saying Nav attr are used for drill down purpose.
What exactly is this drill down .
Please send me any related documents also.
Please answer me.
Thanks in advance
Sundar

Hi,
Characteristic attributes can be converted into navigation attributes. They can be selected in the query in exactly the same way as the characteristics for an InfoCube. In this case, a new edge/dimension is added to the InfoCube. During the data selection for the query, the data manager connects the InfoProvider and the master data table (u2018joinu2019) in order to fill the Query.
Navigational attribute is like any other master data attribute except that we can navigate (filter, drill down and selection) in reports on this characteristic.
Drilldown means after you executed the query , you want to see further detailed data with particular combination ,
in that case you navigate further or do restiction that is drilldown.
If you restict a navigational attribute in Query , then it behaves like a normal characteristic and not as a navigation attribute.
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a63e7e07211d2acb80000e829fbfe/content.htm
Also check the link:
http://help.sap.com/saphelp_nw70/helpdata/en/43/f234619e3c4c5de10000000a155369/frameset.htm
Regards,
Amit

Navigational Attribute Transported but not reflected.

Hi,
Couple of Navigational Attributes were transported from Dev to QA.
But its not reflecting in QA now.
In the Transport Log its giving the warning message message as,
Navigation attribute ZABCLOC_ZZLINETYPE1 is deleted (not in characteristic ZABCLOC)
Navigation attribute ZABCLOC_ZZABCLOC1 is deleted (not in characteristic ZABCLOC)
Please let me know, how to transport the required Navigational Attr from one system to another system
Thanks,
Sowrabh

if the primary object is not active then u will face issues..
here as its quality u can try deleting the P table content of the Infoobject and then try activating that infoobject in the Quality system with the program.. some this like it starts with RSDG or RSVDIOBJ Activate.. u can try this in ur system...
and then try reimporting it with the overwrite mode.. this is will solve ur issue.
thanks
Vishnu

Navigational attributes are not visible after transport

hi,
i have created five new info objects and added these to 0custome as navigational attributes,then i have switched thes on as navigational attributes in 0sold_to info object.every thing is working fine in deveopment.
when i transport these into quality, for 0customer i am able to see these new info objects as navigational but in 0sold_to these new info objects are visible as display attributes.I want tehse to be as navigational attributes..
can any one tell me where have i gone wrong..
thanks in advance..
satish

Hi,
The SAP Best Practice says that while transport
Request 1: Select the Necessary objects of Info Provider
Request 2: Select Data Flow before and Afterwards
if you practice this you will not miss any objects
regards
Happy Tony

Navigational attributes-- transport

Hi All,
I want to make infoobject zzbam as a navigational attribute of 0vendor.Could anyone let me know can we see the cahnges after transporting the 0vendor to PRD.
many thanks,
Manjula

Hi Manjula,
Yes, you can see the changes in 0Vendor after transporting, in transaction RSD1. But to make it navigational, you need also to select it in an InfoProvider. Otherwise, what you are doing is enabling it to be navigational.
Hope this helps.
Regards,
Diego

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.

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

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.

Performance issue... navigational attribute used

hi ,,
if navigational attrributes are used sytem performnce incerases or decreases ?
if so why?
regards
snigdha

Hi
Navigational attributes require additional table joins at runtime (in comparison to dimension characteristics) but usually the decision for dimension characteristics or navigational attributes is based on business requirements rather than on performance considerations. If your aggregates contain navigational attributes, a change run must be scheduled every time this master data is loaded.
Dimensional attributes generally have a performance advantage over navigational attributes for query operations. Fewer tables are joined to access the values of dimensional attributes than navigational attributes; therefore less overhead is seen during query execution. The requirements should be carefully analyzed to determine whether a certain attribute needs to be navigational or if dimensional or display attribute

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

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.

Variable for navigational attribute affected fiscper input variable

Dear Friends
Initially, the query is having an input variable for fiscper. The query was able to run properly.
When i add a input variable for a navigational attribute to the same query which is based on multiprovider, the fiscper input variable is no longer seen.
So, I removed the global filter for the navigational attribute and it is ok again. I fixed a value for the navigational attribute at filter level is also fine.
Please advise what could be the cause. Thank you so much.
Best regards
Bass

Hi Bass,
Again seems to be a strange issue, if you have two independent characteristic with two different input enabled variables then there is no reason for the variable to not to show up on selection screen.
Once you add the new variable and save the query just make sure that you have earlier variable as it is and check the query properties popup and see the fiscper variable sequence in the variable list.
Regards,
Durgesh.

Transports issue regarding navigational attribute

Similar Messages

Maybe you are looking for