Bex Query's(Composite Provider) Navigational Attribute Error

Hi All,
We have created a BEx query on top of a Composite Provider. In the Composite Provider, we have a few common Navigation Attributes in all Info Providers.
Whenever we tried to show a particular Navigational Attribute (G_TIC9030) in BEx query (RSRT), we will receive the error messages as below.
This problem doesn't occur if we created another test query on each Info Providers of Composite provider. All test queries are able to return result and are showing all the navigational attributes without any errors.
Any idea on how to fix this?
Regards,
Kang

As discussed Kang this looks like the problem described in OSS Note 2019244.
It's not unusual to find a few of these problems in testing.

Similar Messages

Error while executing BEx Query on Composite Provider

Hi,
We have a BW on-HANA system, patch level SAPKW73105.
We have created a Composite provider based on the union of two DSOs, two infoobjects, one SPO, and there are a couple of joins with two other DSOs, on the top of that we built a BEx query.
While executing the BEx query, sometimes (depending on the filter values), We got the following error message
"Attribute engine failed;Error executing physical plan: exception 6900: AttributeEngine/Parallel/DimensionFilter.cpp engine failed; $function$=getValidFemsPA;"
"Error 6,900 has occurred in the BWA/SAP HANA server"
"Error reading the data of InfoProvider @3ZSDRPCP5"
"Error while reading data; navigation is possible"
"Row: 59 Inc: MAP_TREX_EXCEPTION Prog: CL_RSDRH_TREX_STORAGE"
(Attached error message)
Ii We browse the composite provider data using the "display data" option in the RSA1, data is displayed without issue, the problem only appears during the BEx query execution and only with some filter vaues.
Any idea on how to fix the issue.
Thanks,
Federico

He's on 7.3 EhP1, which is on SPS12 today. It got pretty stable by SP08, SP09. SP05 was pretty early on, and had a lot of bugs in the HANA views.
7.4 is on SP07 like you say, and most of our customers run at least SP06 - before then, you had to apply a bucketload of SAP notes. I would recommend customers apply SP08 with care because it's a feature release so will have a bunch of new features, which will no doubt need corrections.

Delete navigation attributes - error when reactivating MPOS

Hi Gurus
I have deleted some navigation attributes, and when I try to reactive the MPOS I get an error - however logging has not been switched on initially so I cannot see what's wrong. I have tried to run all possible consistency check on the MPOS, none showed any error. Have you encountered somewhat the same issue?
I hope you can help me
normally you have some good answers
Best regards,
Anders Thinggaard

Are you atleast getting any error messages on the screen when you try to activate the MPOS? How do you know you are getting an error?
Let us know the error messages which will be helpful in diagnosing the problem.
cheers,
Srinidhi

"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

Behavior of BEx Query Attributes for webi on OLAP universe: Including 1 attr to Query!

My webi report is based on an OLAP universe (.unv) which is based on a BEx Query. I need an attribute field from an info object. But when I include that attribute in my BEx query in free characteristics pane…… Every single attribute in that info object comes over to the universe.
Is this the expected behavior?
How can I ensure only the attribute wanted comes over and not all the attributes of the info-object.
I am using BO 4.0SP4.

Attribute level restriction of an InfoObject is not possible in BEX Query and the same reflects in the Universe.
You can use attributes of an infoObject which you wanted on WEBI Report Level.
---Raji. S

Showing navigation attributes in the same column of a query

Hi,
I would like to know if there is a way to define a query such that TWO navigation attributes that reference the same underlying characteristic can be displayed in the SAME column rather than TWO separate columns.
I will describe an example scenario to clarify the requirement. We are using a BI Content InfoCube (0COOM_C02) that has the navigation attributes 0COSTCENTER__0PROFIT_CTR and 0WBS_ELEMT__PROFIT_CTR activated. Both of these attributes reference the characteristic 0PROFIT_CTR. The InfoCube contains transaction data for Cost Centres and WBS Elements.
The requirement is to define a query that summarizes the data by profit centre. At the moment, in order to combine Cost Centre and WBS (Project) data in the same query by Profit Centre, both navigation attributes need to be selected, resulting in the following output:
0COSTCENTER__0PROFIT_CTR......0WBS_ELEMT__PROFIT_CTR......AMOUNT
PC01...............................................Not assigned...................................10,000
PC02...............................................Not assigned...................................20,000
PC03...............................................Not assigned...................................12,000
PC04...............................................Not assigned....................................2,000
Not Assigned....................................PC02..............................................5,000
Not Assigned....................................PC03..............................................8,000
Not Assigned....................................PC05..............................................30,000
Not Assigned....................................PC06..............................................50,000
However, the desired result is to display only one profit centre column using the two profit centre navigation attributes as shown below:
PROFIT CENTRE......AMOUNT
PC01..........................10,000
PC02..........................25,000
PC03..........................20,000
PC04............................2,000
PC05..........................30,000
PC06..........................50,000
Is there a way to achieve the above result using the two navigation attributes only, without having to add 0PROFIT_CTR as a characteristic to the InfoCube?
Any suggestions would be appreciated.
Thanks,
Mustafa.

Hi Mustafa,
You have to use enhancement RSR00001 in the transaction CMOD to start developing your code.
For more information how the customer exit variables are processed, refer to the documentation:
http://help.sap.com/saphelp_nw70/helpdata/EN/f1/0a56f5e09411d2acb90000e829fbfe/frameset.htm
A short example can be found here:
http://help.sap.com/saphelp_nw70/helpdata/EN/1d/ca10d858c2e949ba4a152c44f8128a/frameset.htm
This should help.
Regards,
Daniel

Bex Query report error in cal month /year column

Hi Experts,
We have a bex query on virtual provider with only one column in it i.e 'cal year / month'( This virtual provider ahs been created from planning area). I'm having the problem with this column.
In the excel output of this report the cal year /month is displaying as follows.
01/0000 02/0000 03/0000 04/0000 05/0000 06/0000 07/0000 08/0000 09/0000 08/2008 09/2008 10/2008 11/2008 12/2008 01/2009 02/2009 03/2009 04/2009 05/2009 03/2010 04/2010 05/2010 06/2010 07/2010 08/2010 09/2010 10/2010 11/2010 12/2010 01/2011 02/2011 03/2011 04/2011 05/2011 06/2011 07/2011 08/2011 09/2011 10/2011 11/2011 12/2011 01/2012 02/2012 03/2012 04/2012 05/2012 06/2012 07/2012 08/2012
I'm not getting why the first 9 columns its displaying as 01/0000 02/0000 03/0000 04/0000 05/0000 06/0000 07/0000 08/0000 09/0000 .
It should display as
08/2008 09/2008 10/2008 11/2008 12/2008 01/2009 02/2009 03/2009 04/2009 05/2009
06/2009 07/2009 08/2009 09/2009 10/2009 11/2009 12/2009 01/2010 02/2010 03/2010 04/2010 05/2010 06/2010 07/2010 08/2010 09/2010 10/2010 11/2010 12/2010 01/2011 02/2011 03/2011 04/2011 05/2011 06/2011 07/2011 08/2011 09/2011 10/2011 11/2011 12/2011 01/2012 02/2012 03/2012 04/2012 05/2012 06/2012 07/2012 08/2012
My data source is fetching the correct data including this cal year/ month.
Thanks in advance for your help.
Regards,
Brahma Reddy

I assume you are running Crystal for enterprise 4.0 SP02 Patch 08 !!
According to OSS note 1651521 , This issue has been fixed in FP3 which is planned to be released in first quarter of 2012 !!!!!! ouch !!!!!
I am facing same issue , Pls let me know if you already solved it.
Regards,
Miraj Desai.
Edited by: Anne Howard on Nov 29, 2011 6:58 AM

BI7 : BRAIN 667 error when modifying a KF in BEX query

Hello,
When we modify a KF (standard or calculated) property in a Bex query, we have a Brain 667 error (Query handle xxxx is invalid . Message no. BRAIN667).
When it's run from the WAD, the error message is BRAIN 282.
Does any body know what's this about ?
Thanks;
MGH

We are already in SP9 and applied many notes related to SP10.
The fact is that we have a BW 3.5 (vers. 3500.11.051) Bex and not a BI7 Bex.
We have a BI7 with BW 3.x functionalities.
MGH

Drilldown in BeX Query Designer

Hello,
I am new in SAP. I am having problem creating Drill down. I have this report where all the data is Transactional data. So I haven't created any Master Data. So I won't be able to use Navigational Attribute for Drill down purpose and I don't want to use Hierarchy. Is there any possibility of getting the Drill down in BeX Query Designer? Any help will be appreciated.
Warm Regards,
Debayan

Hi Debayan,
first of all, what is your requirement to create a drill down?
A drill down in BEx query means showing additional information from report output. There are 3 ways to drill down a query in BEx
1. Master data-Navigational Attributes
2. Master data- Hierarchies
3. Free characteristics
As you dont have any master data in the report (which is very strange) you can use the additional characteristics provided in the 'Free characteristics' to see how the drill down works in BEx.
Please share your exact requirement.
Hope this helps.
-Swati.

Problem in Bex Query

Hi Team,
I am facing a strange problem.
Some attributes are marked has navigational attribute in the Multiprovider level.
When I am dragging the same Multiprovider in the Bex to create a query on that, those navigational attributes are missing in the Global definition of that multiprovider in the Query designer.
Have anyone faced such an issue?
Kindly help me...
Regards,
Debjani...

HI Vikash,
We have checked both the Multiprovider and the cube and also the infoobject level.
But still I am facing this issue..
Regards,
Debjani...

Variable on Navigational Attributes in ODS

BW Experts,
I have a Navigational Attribute in my ODS. In my query design, I do not get an option to build a variable for selection on this Navigational attribute. Is it a fact with ODS that Variable cannot be built on Nav Attributes?
Thanks
Ashwin

hi Ashwin,
we have to logout and login again bex analyzer to reflect any changes on infoprovider, i guess you were opening bex and turn on ods navigation attribute and couldn't find it in bex query, then you logoff and login again and see the navigation attribute, you can have a try
hope this helps.

Data for navigational attributes # Not Assigned

Hello friends,
Our report is based on Multiprovider which is based on 5 cubes.
These five cubes has one particular Characteristics which hasnavigational Attribute .
We are using the navigational attribute directly under free characteristics Tab in Query.
We are also using Characteristic in Query - for characateristic data is shown in report.
In report we are able to see data as # Not Assigned for navigational attributes.
When we checked data at info object level for that characateristic, correct data is shown for that navigation attributes.
We have checked following settings
At characteristic level - Uncheck Attributes only
At cube level all navigational attributes are checked
In Multi provider identification table - This navigational attribute is checked for all five cubes
In Multi provider Navigational Attributes Tab - This naviagtional attributes is checked
Activation of Master data was done once again
we are not getting any other ideas, can any one please suggest us where the problem is?
Thanks
Tony.

Hi Tony
I have the exact same problem. Did you find out what the problem was?
KR Nete
Edited by: Nete Grøn Jacobsen on Jul 14, 2008 1:51 PM
I solved my problem
1. Activate the navigation attribute(s) on the underlying basiscube, from which the query displays data
2. Choose the navigation attribute(s) for all relevant basiscubes (multicube -> Change -> Button Identification)
See also:
KR Nete

Bex Query Designer and Bex Analyzer not working

Hi All,
While Login to Bex Analyzer, It is giving an error "An error occured while communicating with the BI Server"
While Login to Bex Query Designer, It is giving an error "Login Aborted".
Please help me to resolve this issue
Thanks
Irshad

Hello Irshad
Not sure if it helps but can try suggestion mentioned in this note.
https://service.sap.com/sap/support/notes/1434630
If problem persists you can upgrade your SAP GUI Patch level.
Still facing problem, please contact SAP .
Regards
Anindya

0ANSALARY problem - BEx Query

Hi All,
I have a BEx Query which Uses 0EMPLOYEE & its attributes. 0ANSALARY is one of the attributes that Iam using in the Query. I have created a Role and assigned a Test User and this Query to the role.
The 0ANSALARY appears as ANSALARY in the query when I open it with the Test User's ID, but it appears normal when I open it with my ID. System says that the Query is syntactically correct too. When I execute the Query from the Test User's ID the 0ANSALARY does not get displayed at all in the result. It looks fine when I run the query with my ID.
what could be the problem for this strange behaviour and where should I look to resolve this problem? Please let me know.
Regards,
-Ravi

Hi, I have this in the Rows (the Query does not have colums as I have merged them). And, I have not used any Template to design the Role.
Any ideas?
Regards,
-Ravi

SAP BEx query's Conditions and Exceptions on BO Universe

We are planning to create Conditions and Exception on SAP BEx Query. And provide this query to BO team for their development
Could anyone tell me in what form will these BEx objects be visible in BO-Universe ....as detail objects...or query filters and a.s.o?
Will they be Invisible? If invisible will they be atleast applied to BO-Universe.
For e,g: I know that, BEx Query filter will be applied to the underlying query but are not visible in OLAP universe.
- Anil

Hi,
Conditions and Excpetions are not supported by OLAP BAPI tehrefore they are not generated in universes or consumed at query level.
You have to create conditions on measures in universes (except top end bottom exceptions that are not supported).
Exceptions need to be done at cliient level (Webi, XCelsius, etc).
I BOE CI 4.0 conditions will be supporte by the Semantic Layer direct acces with BICS but exceptions will continue to be created at client level.
Didier

Bex Query's(Composite Provider) Navigational Attribute Error

Similar Messages

Maybe you are looking for