Cascading LOV in BEx Query OLAP Universe + BEx variable

Hi gurus,
we have an universe where a Cascading LOV has been defined based on a BO Hierarchy ( based on a BW hierarchy), the OLAP universe is based on a BEx query.
Now, when the users create a WebI report selecting a value from the value list, the Cascading LOV appears and the user selects the value, descending by the nodes.
We are analyzing the universe performance and we are testing to add some time BEx variables in the query ( in the current version no variables are used).
Everything works properly but when we try to select a value from the Cascading LOV and try to select a lower level the webI returns a mdx error indicanting that the time variable is not informed. (WIS 10901: A database error ocurred; MDX query can not be executed: specify a value for the variable Z... )
We thought that the mdx for the LOV get values from the MD table because in the infoobject definition, it has the Business Explorer Settings:
Query Def. Filter Value Selection = Value in Master Data Table
Query Execution Filter Val. Selectn = Value in Master Data Table
The Query Execution Filter Val. Selectn can be defined at the infoprovider also (with the provider specific Properties of the infoobject) and also at the query, whe have not modify none of them.
My first question is which settings has efect at OLAP Universes, the infoobject settings; the infocube settings or the query settings ?
Are the Cascading LOV integrated with BEx Query OLAP Universe?
Is it an application error?
Many Thanks in advanced.
Best Regards,
Nuria

Hi Ingo,
many thanks for your quick answer.
That was one of the possibilities we have analized but the problem is that the user has to inform the hierarchy level for all the reports, that kind of variables is translated in the universe as a prompt
Now we have only one universe and some business analists users create reports themselves for the business area based on that universe.
The users create WebI filters without prompts,just filtering the hierarchy node. If we add the BEx variable then the user sould inform the prompt for all the reports based on that universe.
We want to avoid that prompt, we have several hierarchies in the query for different infoobjects.
Thanks again.
Best Regards,
Nuria

Similar Messages

Crystal Reports with BEx Query using Custom Exit Variable

Hi,
We have BW BEx Query using Customer User Exit variable to derive the Fiscal Week for Last Year (called it VAR2) based on another user input variable Current Fiscal Week (called it VAR1).
VAR2 is derived from VAR1 in CMOD via some codings and thus it DOES NOT have the "Variable is Ready for Input" flag ticked in the BEx. VAR1 is user input variable, so it has "Variable is Ready for Input" flag ticked in the BEx.
When we create a Crystal Reports with the BEx Query using variable VAR2, and when we run it we got an error message saying "Failed to execute query; '[]<java.lang.UnsupportedOperationException: No Selection State Support!ZP_MI_LYPUBWEEK>'. Redesign your query or contact the data source maintainer to solve the problem". (note: ZP_MI_LYPUBWEEK is VAR2 in this case).
Could anyone please assist? Surely, CR supports BEx customer user exit variables like the above, right?. I also refer to the forum below as it seems to have a similar issue (except mine with an error message), but it does not provide a solution in it.
Crystal Reports with BEx Query using Custom Exit Variable
Thanks,
Andy

Hi Vibhav,
We have the SAP Crystal Reports for Enterprise XI4.0 Version 14.0.0. Not sure if SP0 or other SP, got to check with Basis Team later.
We tried that "mandatory" option and did not work either.
Anyway, SAP has now come back again saying it is something they will fix it in next release/version. We got a phone call from them and a reply below to our OSS.
23.08.2011 - 08:20:49 CET - Info for Customer by SAP
I have raised this issue on the Idea#s Place as an enhancement request
on the below link:
https://cw.sdn.sap.com/cw/ideas/5586
This ER contains the information of including the customer exit
variables in the report without checking the #input for ready# option.
This ER can be considered for being implemented in the future
versions. You can refer to SAP Note: 1515837 - How To: Enhancement
Request Process - "Idea Place" for more information regarding the Idea
Place.
Cheers,
Andy

Error querying OLAP universe based on BEx query

Hi all,
I have a problem extracting larger (more than 80 000 rows) amounts of data through querying an OLAP universe with WebI.
The error is:
Query 1 - NAME_OF_THE_QUERY
A database error occurred. The database error text is: Error in MDDataSetBW.GetCellData. &INCLUDE INCL_INSTALLATION_ERROR. (WIS 10901)
The error occurs when I define larger scope of analysis in the query (four levels). With more modest scope (three levels or less) it's working OK. I need larger data set (more than 200 000 rows) to be populated at night through scheduling the report. We can't afford shrink the scope of analysis because it will hit the BW server during the day when it's needed by other users.
Besides this the speed of the report refresh is very slow - more than 3 minutes per just 400 rows of data. I'm still unable to identify the source of the problem with this slowdown. Executing the same query over the web through the SAP BW BEx Viewer is much much faster - just 3 seconds. Maybe the reason for this is that the BEx viewer aggregates data on the higher level of the hierarchy rather than down to transaction level (like we do by expanding the scope of analysis).
Anyway, if anyone have ideas about the error above I'll be very grateful if you share your thoughts. Thanks!
Our environment:
BO EDGE BI 3.1, standard
SAP BW 3.0
SAP Integration Kit (all transports installed)
BW user with full access

Ingo,
Could you point me to an official SAP document regarding the 1 million cells limitation, which describes the exact version and patch level for SAP BW which removes this limitation? It will be very helpful for me because I have to convince the client to migrate BW from 3.0 to 7.01 if it will solve this limitation.
Thank you in advance!
Ivan
BTW I have installed SP2 + FP2.1 and now the SAP integration is not functional, but I have opened another thread for this problem.

Dynamic filter on time characteristics on OLAP SAP BEX query based universe

Dear all,
I'm currently working on the integration between SAP NetWeaver BI 7.0 and SAP BusinessObjects XI 3.1 FP 1.5 via integration kit.
I've built an OLAP universe on the top of a BW query based on a multiprovider that contains 10 infocubes.
Everything works fine but I need to create a filter in the OLAP universe that allows to restrict data by current date (e.g. using TIME characteristic of Infocube such as 0CALDAY or 0CALMONTH). From that filter we could start creating other conditions to compare data to different time periods.
I've already tried to use a SAP exit variable in a BW query but this kind of object would restrict query data only by current date and for example it would be impossible to browse data by previous years (to bypass this problem we could use restricted key figures with different offsets but we have too many key figures in the query and the number of restrictions
would rise exponentially).
In a relational DataBase we can do that using a "where condition" based on 'CURRENTDATE' (SQL DB2 syntax).
Now, we need to apply the same logic but translated in MDX syntax.
Is it possible to enter a dynamic filter in the OLAP universe or just fixed or promt values ?
Any advise?
Thanks in advance.
Best Regards.
M.

Hi Ingo,
1) My question is: "How can I have to manage variable in BEX queries and in the UNIVERSE in order to obtain the maximum flexibility to create reports with measures on actual day (for example) without asking the user to promt a value ?"
I want to use an unique BEX query to define an unique UNIVERSE. On this UNIVERSE I want to create many reports (actual day, previous day, and so on).
If I restrict 0CALDAY with an EXIT variable then shall I be able to create a different restrictions on the same Universe based on 0CALDAY ?
2) Another question is:
Is it possible to insert an XML / MDX filter on the OLAP Universe with dynamic derivation of the system date ?
For example:
Instead of this:
<FILTER KEY="[0FISCYEAR].[LEVEL01].[NAME]">
    <CONDITION OPERATORCONDITION="Equal">
        <CONSTANT CAPTION="Z12008"></CONSTANT>
    </CONDITION>
</FILTER>
Is it possible to insert a tag with a dynamic function to derive the system date ?
Thanks in advance.
Best Regards.

Leaf Node access in a BW OLAP Universe - BEX Query

How we can gain access in an universe to just the lowest leaf node in an bex query with hierarchies. If an infoobject has a hierarchy that is ragged, I just want to display that lowest level with a value.
Is there an MDX work around
An example is cost center or account which may be many levels.
The goal is to create a universe such that in webi or explorer, the user has to deal with one field for cost center or account and not 7 levels for each which make it very hard for the end user.
In this case the hierarchy is not important.

Hi,
I assume that you want to say XML traces rather than SQL traces.
We provide SQL for relational databases and SAP BW Infocubes/DSO through Data Federator.
The MDX generated contains only the characteristics and key figures selected in the Query Panel.
However, there were an issue where all key figures were taken into account by SAP BW server even if not all have been selected.
This issue has been fixed in a fix pack (I don't remember which one).
Regards
Didier

Cascading LOV in a Query panel (af:query)

Hi
I have a requirement to implement few Cascading LOV's in a Query panel. I have created the VO's for the LOV's with bind variable and view criteria and linked them. It works for the BC viewer. But to enable in the ADF UI, the partial trigger needs to be enabled on individual field. And the af:query encapsulates the fields and they are not exposed. Can someone help me with a solution or a pointer
Many thanks

Thanks for the pointer
Well I followed the the steps, and implemented the same for two LOV's. I'm getting "Server Exception during PPR, #1". Would be able to identify where I'm going wrong please.
FYI: I'm using a UI template that is stripped won from Oracles Dynamic tab template
1. parent LOV
<?xml version="1.0" encoding="windows-1252" ?>
<!DOCTYPE ViewObject SYSTEM "jbo_03_01.dtd">

<ViewObject
xmlns="http://xmlns.oracle.com/bc4j"
Name="QcChiptypeVViewRO"
Version="11.1.1.56.60"
BindingStyle="OracleName"
CustomQuery="true"
RowClass="com.qualcomm.qdt.fwk.model.QdtViewRowImpl"
ComponentClass="com.qualcomm.qdt.fwk.model.QdtViewObjectImpl"
DefClass="com.qualcomm.qdt.fwk.model.QdtViewDefImpl"
PageIterMode="Full"
UseGlueCode="false">
<DesignTime>
<Attr Name="_codeGenFlag2" Value="Access|VarAccess"/>
<Attr Name="_isExpertMode" Value="true"/>
</DesignTime>
<SQLQuery>
<![CDATA[SELECT QcChiptypeV.CHIPTYPE
FROM QC_CHIPTYPE_V QcChiptypeV]]>
</SQLQuery>
<ViewAttribute
Name="Chiptype"
IsUpdateable="false"
IsPersistent="false"
PrecisionRule="true"
Precision="42"
Type="java.lang.String"
ColumnType="VARCHAR2"
AliasName="CHIPTYPE"
Expression="CHIPTYPE"
SQLType="VARCHAR">
<DesignTime>
<Attr Name="_DisplaySize" Value="42"/>
</DesignTime>
</ViewAttribute>
</ViewObject>
2. Child LOV
<?xml version="1.0" encoding="windows-1252" ?>
<!DOCTYPE ViewObject SYSTEM "jbo_03_01.dtd">

<ViewObject
xmlns="http://xmlns.oracle.com/bc4j"
Name="QcMcnVViewRO"
Version="11.1.1.56.60"
BindingStyle="OracleName"
CustomQuery="true"
RowClass="com.qualcomm.qdt.fwk.model.QdtViewRowImpl"
ComponentClass="com.qualcomm.qdt.fwk.model.QdtViewObjectImpl"
DefClass="com.qualcomm.qdt.fwk.model.QdtViewDefImpl"
PageIterMode="Full"
UseGlueCode="false">
<DesignTime>
<Attr Name="_codeGenFlag2" Value="Access|VarAccess"/>
<Attr Name="_isExpertMode" Value="true"/>
</DesignTime>
<Variable
Name="chiptype"
Kind="viewcriteria"
Type="java.lang.String"/>
<ViewAccessor
Name="QcChiptypeVViewRO1"
ViewObjectName="com.qualcomm.qdt.model.lov.QcChiptypeVViewRO"
RowLevelBinds="true"/>
<SQLQuery>
<![CDATA[SELECT QcMcnV.MCN,
QcMcnV.CHIPTYPE
FROM QC_MCN_V QcMcnV]]>
</SQLQuery>
<ViewAttribute
Name="Mcn"
IsUpdateable="false"
IsPersistent="false"
PrecisionRule="true"
Precision="20"
Type="java.lang.String"
ColumnType="VARCHAR2"
AliasName="MCN"
Expression="MCN"
SQLType="VARCHAR">
<DesignTime>
<Attr Name="_DisplaySize" Value="20"/>
</DesignTime>
<Dependencies>
<Item
Value="Chiptype"/>
</Dependencies>
</ViewAttribute>
<ViewAttribute
Name="Chiptype"
IsUpdateable="false"
IsPersistent="false"
PrecisionRule="true"
Precision="42"
Type="java.lang.String"
ColumnType="VARCHAR2"
AliasName="CHIPTYPE"
Expression="CHIPTYPE"
SQLType="VARCHAR">
<DesignTime>
<Attr Name="_DisplaySize" Value="42"/>
</DesignTime>
</ViewAttribute>
<ViewCriteria
Name="QcMcnVViewROCriteriaChiptype"
ViewObjectName="com.qualcomm.qdt.model.lov.QcMcnVViewRO"
Conjunction="AND">
<Properties>
<CustomProperties>
<Property
Name="displayOperators"
Value="InAdvancedMode"/>
<Property
Name="autoExecute"
Value="true"/>
<Property
Name="allowConjunctionOverride"
Value="true"/>
<Property
Name="showInList"
Value="true"/>
<Property
Name="mode"
Value="Basic"/>
</CustomProperties>
</Properties>
<ViewCriteriaRow
Name="vcrow5"
UpperColumns="1">
<ViewCriteriaItem
Name="QcMcnVViewROCriteria_vcrow5_Chiptype"
ViewAttribute="Chiptype"
Operator="="
Conjunction="AND"
Value=":chiptype"
IsBindVarValue="true"
Required="Optional"/>
</ViewCriteriaRow>
</ViewCriteria>
</ViewObject>
3. JSF page
<?xml version='1.0' encoding='UTF-8'?>
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.1"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:af="http://xmlns.oracle.com/adf/faces/rich">
<jsp:directive.page contentType="text/html;charset=UTF-8"/>
<f:view>
<af:document id="d1">
<af:messages id="m1"/>
<af:form id="f1">
<af:pageTemplate viewId="/oracle/ui/pattern/dynamicShell/dynamicTabShell.jspx"
value="#{bindings.pageTemplateBinding}" id="pt1">
<f:facet name="copyright">
<af:outputText value="2010 Qualcomm Inc. All Rights Reserved."
id="ot10"/>
</f:facet>
<f:facet name="about">
<af:navigationPane id="np3" hint="buttons">
<af:commandNavigationItem text="About" id="cni5"/>
<af:commandNavigationItem text="Privacy" id="cni6"/>
</af:navigationPane>
</f:facet>
<f:facet name="navigation">
<af:panelAccordion id="pa1">
<af:showDetailItem text=" Asset Details" id="sdi1">
<af:panelGroupLayout layout="vertical" id="pgl1">
<af:panelHeader text=" " id="ph1">
<af:query id="qryId1"
headerText="Search Criteria (Use % as wildcard)" disclosed="true"
value="#{bindings.ImplicitViewCriteriaQuery.queryDescriptor}"
model="#{bindings.ImplicitViewCriteriaQuery.queryModel}"
queryListener="#{bindings.ImplicitViewCriteriaQuery.processQuery}"
queryOperationListener="#{bindings.ImplicitViewCriteriaQuery.processQueryOperation}"
saveQueryMode="hidden"/>
</af:panelHeader>
</af:panelGroupLayout>
</af:showDetailItem>
<af:showDetailItem text="More Info" id="sdi2"/>
</af:panelAccordion>
</f:facet>
<f:facet name="globalLinks">
<af:navigationPane id="np2" hint="buttons"
inlineStyle="text-align:right;">
<af:commandNavigationItem text="Help" id="cni4" action="noop"/>
<af:commandNavigationItem text="Sign out"
id="commandNavigationItem1"
action="noop"/>
</af:navigationPane>
</f:facet>
<f:facet name="status"/>
<f:facet name="globalToolbar"/>
<f:facet name="globalSearch"/>
<f:facet name="globalTabs">
<af:navigationPane id="np1">
<af:commandNavigationItem text="Device Query/Update" id="cni1"
selected="true" partialSubmit="false"/>
<af:commandNavigationItem text="Asset Return" id="cni3"
action="dummy" rendered="false"/>
</af:navigationPane>
</f:facet>
<f:facet name="welcome">
<af:panelSplitter id="ps1" orientation="vertical">
<f:facet name="first">
<af:panelCollection id="pc1" defaultToolbarItemDisplay="icon">
<f:facet name="menus">
<af:menu text="Options" id="m2" rendered="false">
<af:commandMenuItem text="Printable Page" id="cmi2">
<af:showPrintablePageBehavior/>
</af:commandMenuItem>
<af:commandMenuItem text="Download" id="commandMenuItem1">
<af:exportCollectionActionListener exportedId="t2"
type="excelHTML"
title="Asset Details"/>
</af:commandMenuItem>
</af:menu>
</f:facet>
<f:facet name="toolbar">
<af:toolbar id="t1">
<af:commandToolbarButton id="ctb1"
hoverIcon="/images/view_image.gif"
text="Export to Excel">
<af:exportCollectionActionListener exportedId="t2"
type="excelHTML"
title="Asset Details"/>
</af:commandToolbarButton>
</af:toolbar>
</f:facet>
<f:facet name="statusbar"/>
<af:table value="#{bindings.QcDeviceTrackingVO1.collectionModel}"
var="row"
rows="#{bindings.QcDeviceTrackingVO1.rangeSize}"
emptyText="#{bindings.QcDeviceTrackingVO1.viewable ? 'No data to display.' : 'Access Denied.'}"
fetchSize="#{bindings.QcDeviceTrackingVO1.rangeSize}"
rowBandingInterval="0"
filterModel="#{bindings.ImplicitViewCriteriaQuery.queryDescriptor}"
queryListener="#{bindings.ImplicitViewCriteriaQuery.processQuery}"
filterVisible="true" varStatus="vs"
selectedRowKeys="#{bindings.QcDeviceTrackingVO1.collectionModel.selectedRow}"
selectionListener="#{bindings.QcDeviceTrackingVO1.collectionModel.makeCurrent}"
rowSelection="single" id="t2"
columnSelection="single"
partialTriggers=":::ph1 :::qryId1">
<af:column sortProperty="Serialnum" filterable="true"
sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Serialnum.label}"
id="c28" width="103">
<af:outputText value="#{row.Serialnum}" id="ot17"/>
</af:column>
<af:column sortProperty="Assettag" filterable="true"
sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Assettag.label}"
id="c7" width="107">
<af:outputText value="#{row.Assettag}" id="ot24"/>
</af:column>
<af:column sortProperty="Chiptype" filterable="true"
sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Chiptype.label}"
id="c18" width="26">
<af:outputText value="#{row.Chiptype}" id="ot27"/>
</af:column>
<af:column sortProperty="Mcn" filterable="true"
sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Mcn.label}"
id="c11">
<af:outputText value="#{row.Mcn}" id="ot13"/>
</af:column>
<af:column sortProperty="Mcnrev" filterable="true"
sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Mcnrev.label}"
id="c8">
<af:outputText value="#{row.Mcnrev}" id="ot3"/>
</af:column>
<af:column sortProperty="Assignedto" filterable="true"
sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Assignedto.label}"
id="c15">
<af:outputText value="#{row.Assignedto}" id="ot32"/>
</af:column>
<af:column sortProperty="Location" filterable="true"
sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Location.label}"
id="c24">
<af:outputText value="#{row.Location}" id="ot19"/>
</af:column>
<af:column sortProperty="Locationfullname" filterable="true"
sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Locationfullname.label}"
id="c14">
<af:outputText value="#{row.Locationfullname}" id="ot26"/>
</af:column>
<af:column sortProperty="Locationtype" filterable="true"
sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Locationtype.label}"
id="c13">
<af:outputText value="#{row.Locationtype}" id="ot28"/>
</af:column>
<af:column sortProperty="Description" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Description.label}"
id="c21">
<af:outputText value="#{row.Description}" id="ot22"/>
</af:column>
<af:column sortProperty="Assignment" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Assignment.label}"
id="c30">
<af:outputText value="#{row.Assignment}" id="ot34">
<af:convertNumber groupingUsed="false"
pattern="#{bindings.QcDeviceTrackingVO1.hints.Assignment.format}"/>
</af:outputText>
</af:column>
<af:column sortProperty="Createddate" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Createddate.label}"
id="c1">
<af:outputText value="#{row.Createddate}" id="ot15">
<af:convertDateTime pattern="#{bindings.QcDeviceTrackingVO1.hints.Createddate.format}"/>
</af:outputText>
</af:column>
<af:column sortProperty="Lastid" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Lastid.label}"
id="c33">
<af:outputText value="#{row.Lastid}" id="ot9">
<af:convertNumber groupingUsed="false"
pattern="#{bindings.QcDeviceTrackingVO1.hints.Lastid.format}"/>
</af:outputText>
</af:column>
<af:column sortProperty="Lportfolioitemid" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Lportfolioitemid.label}"
id="c23">
<af:outputText value="#{row.Lportfolioitemid}" id="ot23">
<af:convertNumber groupingUsed="false"
pattern="#{bindings.QcDeviceTrackingVO1.hints.Lportfolioitemid.format}"/>
</af:outputText>
</af:column>
<af:column sortProperty="Lkeycontactid" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Lkeycontactid.label}"
id="c4">
<af:outputText value="#{row.Lkeycontactid}" id="ot11">
<af:convertNumber groupingUsed="false"
pattern="#{bindings.QcDeviceTrackingVO1.hints.Lkeycontactid.format}"/>
</af:outputText>
</af:column>
<af:column sortProperty="Fullname" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Fullname.label}"
id="c22">
<af:outputText value="#{row.Fullname}" id="ot6"/>
</af:column>
<af:column sortProperty="Status" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Status.label}"
id="c16">
<af:outputText value="#{row.Status}" id="ot21"/>
</af:column>
<af:column sortProperty="Qcemployeenumber" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Qcemployeenumber.label}"
id="c6">
<af:outputText value="#{row.Qcemployeenumber}" id="ot33">
<af:convertNumber groupingUsed="false"
pattern="#{bindings.QcDeviceTrackingVO1.hints.Qcemployeenumber.format}"/>
</af:outputText>
</af:column>
<af:column sortProperty="Field3" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Field3.label}"
id="c12">
<af:outputText value="#{row.Field3}" id="ot18"/>
</af:column>
<af:column sortProperty="Empdeptfullname" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Empdeptfullname.label}"
id="c27">
<af:outputText value="#{row.Empdeptfullname}" id="ot4"/>
</af:column>
<af:column sortProperty="Comments" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Comments.label}"
id="c10">
<af:outputText value="#{row.Comments}" id="ot16"/>
</af:column>
<af:column sortProperty="Builtby" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Builtby.label}"
id="c19">
<af:outputText value="#{row.Builtby}" id="ot20"/>
</af:column>
<af:column sortProperty="Mesbuild" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Mesbuild.label}"
id="c31">
<af:outputText value="#{row.Mesbuild}" id="ot2"/>
</af:column>
<af:column sortProperty="Esn" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Esn.label}"
id="c26">
<af:outputText value="#{row.Esn}" id="ot31"/>
</af:column>
<af:column sortProperty="Imei" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Imei.label}"
id="c17">
<af:outputText value="#{row.Imei}" id="ot29"/>
</af:column>
<af:column sortProperty="Macaddress" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Macaddress.label}"
id="c32">
<af:outputText value="#{row.Macaddress}" id="ot1"/>
</af:column>
<af:column sortProperty="Brf" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Brf.label}"
id="c25">
<af:outputText value="#{row.Brf}" id="ot8"/>
</af:column>
<af:column sortProperty="Brfrev" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Brfrev.label}"
id="c3">
<af:outputText value="#{row.Brfrev}" id="ot25"/>
</af:column>
<af:column sortProperty="Dacquisition" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Dacquisition.label}"
id="c29">
<af:outputText value="#{row.Dacquisition}" id="ot7">
<af:convertDateTime pattern="#{bindings.QcDeviceTrackingVO1.hints.Dacquisition.format}"/>
</af:outputText>
</af:column>
<af:column sortProperty="Datqcmainttermdate" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Datqcmainttermdate.label}"
id="c2">
<af:outputText value="#{row.Datqcmainttermdate}"
id="ot30">
<af:convertDateTime pattern="#{bindings.QcDeviceTrackingVO1.hints.Datqcmainttermdate.format}"/>
</af:outputText>
</af:column>
<af:column sortProperty="Datqcissueddate" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Datqcissueddate.label}"
id="c5">
<af:outputText value="#{row.Datqcissueddate}" id="ot5">
<af:convertDateTime pattern="#{bindings.QcDeviceTrackingVO1.hints.Datqcissueddate.format}"/>
</af:outputText>
</af:column>
<af:column sortProperty="Itlqciteclass" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Itlqciteclass.label}"
id="c20">
<af:outputText value="#{row.Itlqciteclass}" id="ot14"/>
</af:column>
<af:column sortProperty="RowID" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.RowID.label}"
id="c9">
<af:outputText value="#{row.RowID}" id="ot12"/>
</af:column>
</af:table>
</af:panelCollection>
</f:facet>
<f:facet name="second">
<af:panelTabbed id="pt2">
<af:showDetailItem text="Update Attributes" id="sdi3"
stretchChildren="first"/>
</af:panelTabbed>
</f:facet>
</af:panelSplitter>
</f:facet>
<f:facet name="innerToolbar"/>
<f:attribute name="brandingTitle" value="ITE Device Tracking System"/>
<f:attribute name="navSplitterPosition" value="450"/>
</af:pageTemplate>
</af:form>
</af:document>
</f:view>
</jsp:root>

How to Copy RPT of one BEX query to another Bex Query

Hi,
I have a Crystal Report-A1 based on one Bex Query ZABC_1. I also have another Bex Query with same output and source named ZABC_2.
Now i want the to copy A1 to A2 and have A2 referring to ZABC_2.
The only difference between the 2 queries is the selection option paramenters.
Please let me know any way forward on this.
Points will be awared for useful replies.

Hi Rajesh J Salecha,
What I understood is like :
You have two queries and both gives same results but one of the query having a parameter.
You have one report which is using query1. Now you want that report to be copied as Report2 and use Query2 instead of Query1.
If the this is the issue, then you copy Report1 as Report2 and go in Database and change the Data source location to Query2.
Hope this will help you. If my understanding is wrong then give us the work flow.
Thanks,
Sastry

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

Getting Custom LOV in SAP BW OLAP Universe

Hi,
My Requirement is to create a prompt where the end user is prompted to select a Custom group(which we have to manually put in prompt and is not available in SAP BW table) and the data should be filtered by the billing document type for that group which again we have to specify in the prompt.
This is what I have created but it's not working -
<OPTIONAL><FILTER KEY="@Select(Billing Document Typ\Billing Document Typ)">
<CONDITION OPERATORCONDITION="InList">
<CONSTANT TECH_NAME="@Prompt('Enter\Select Sales Data Type: ','A',{'Merchandise Invoice Sales':'YFX':'YLXP':'ZFX':'ZLXP','Dropship Invoice':'YFXD':'ZFXD'},multi,free,Not_Persistent)"/>
</CONDITION></FILTER></OPTIONAL>
I have seen this thing working in BO with oracle as backend but it's not working here in OLAP Universe.
Please let me know if anyone has ever faced this issue.
Thanks,
Pankaj Goswami

Hi Marvin,
When you define a filter only the Where clause is available.
When you define an object both Select and Where clause are available.
For an object the Select clause is mandatory, the Where clause is optional.
So for instance if you want to define a new calculated measure, use the Select clause if you want to filter with this new object you can set the Where clause but that means that this object will be always filtered by the Where clause definition.
The other way is to create a new filter that use the object definition to filter on what you want: in that case you can use the object for any scenario and use filter only when you need it.
Last the syntax you wrote is invalid:
<EXPRESSION>(@Select (Class\Measure),filter)</EXPRESSION>
What do you want to define? What is the purpose of this new object?
Please provide all the information you can and I will try to provide you a correct definition.
Didier

Variables from BEx Query through Universe - separated by data provider

Hi,
I have a universe that is being used multiple times within a WEBI report, however, I'd like to select the BEx Queries' variables that come through as prompts separated by query. (multiple queries, multiple prompts; one for each)
For example, I have variables that come through for Exchange Rate type, and I'd like to select query 1 as Exchange Rate Type A, and select query 2 as Exchange Rate type B. At present, the prompting only offers me one input for all data providers that is the same.
A similar functionality exists within BEx Analyzer that is a workbook setting, does something like this exist on WEBI or in the Designer?
Thanks in advance!

I am not sure if anything like what you ask exists.
In such cases I create the prompts in WEBI that gives me control to define the prompts separately for each query.
Edited by: Mathangi Kuppusamy on Sep 1, 2011 2:59 AM

How to remove Decimals in Quantity Objects in SAP BO Explorer View created on top SAP Bex Query?

Hi,
I created SAP BO Explorer report on top of SAP BEx Query.
In SAP BEx Query, Decimals were hided but when i created OLAP Universe on top that SAP BEx Query and Created Index on top of Information Space in SAP BO Explorer and then created Exploration Views. But i'm getting Decimals in my Exploration Views where as SAP BEx Query in RSRT, no decimals were appearing.
Can anyone suggest me how to remove decimals in SAP BO Exploration Views.

Hi Ramana,
I am not use how you connect to SAP BEx query (Via universe or BWA or HANA)
What I could say is BWA and HANA, you cannot adjust this
For universe, you could try in universe layer, there is note about this
For BWA and HANA, this function might be enhanced but you 'd better raise OSS to SAP to check with them
Best regards
Alex yang

Regarding Filter in Webi Report which is based on BEx query

Hi,
I am developing Webi report, in which using universe which is baed on BEx query.
Suppose BEx query contains filter on fiscal year 2010.
And I am developing Webi report on that query. So I want to know, whether my Web i report output will contain data of only fiscal year 2010, as filter is applied in BEx query.
Thanks,
Pradip Nikam

Hi,
if this is a fixed filter the data will be filtered.
if this is a variable in the BW query the user will get prompted.
ingo

Future of BEx Query and BEx Query Designer

Folks, I understand SAP's future reporting tools is BO suite. All of us need to move to the new tools which are better or more reliable in 2010. Meanwhile our customers are reluctant to use BEx tools for any new development. Being on the techi side I dont see how BEx Query will be replaced by Voyager or Polestar or WebI or Crystal. I just need to report on my multiprovider without a universe layer. Have any of you experts come across documentation that layed out future of BEx tools explaining the end of support period? I have see roadmaps for tool availability but no dates for end of support.
Thanks in advance.

AFAIK,
Bex Query designer and BEx query will continue... Polestar might be proposed as an alternative for BEx but then it is meant for ad-hoc analysis ... but BEx query and Query designer have specific query requirements also...
Voyager etc will start coming in...

-ve values in Webi Report , Run on SAP Bex query

Hi,
I am creating WebI Report on Bex Query. some of the key figures like Net Sales, Gross Margin & Operating Profit are display as -ve values.
as they are +ve values in Bex Query.
Do i need to check any options in Bex query or Universe.
I am using Business Objects XI R2 .
Please help me.
Thanks,
Anitha

this seems to be a double entry.
Ingo

Webi Report showing incorrect prompt from bex query

Hello Gurus:
I am facing a unique problem.
I have a BEx Query which has a variable. I have built implement a BADI which restricts the variable values for the BEx Query.
I have created an Universe on top of the BEx Query. And I have created a webi Report on top of the Universe.
The Webi Report when run does not use the Webi Prompt values, in other words it ignores the restrictions that I have placed on the variables. Instead it displays the whole list.
Am I missing anything. Can some please help.
Thanks
EmJay

Hi,
select at least one key figure in the webi report and then try.
Thanks,
Amit

Cascading LOV in BEx Query OLAP Universe + BEx variable

Similar Messages

Maybe you are looking for