OLAP Universe : Objects LOV pointing to master table in BW

The LOV's generated were pointing to master table in BW. Say like we have Material dimension along with LOV's generated by Universe based on Bex is poingting to Master table in BW. "0Material.Level 0". when we refresh or search for a purticular Material we are getting two errors: Partial Results and No Value found.
I checked in the Parameter and we dont have any restriction bringing the number od rows. Can anybody advise how to show all the Materials in LOV's. I tried using delegated search option in the Object properties. But doing that we loose Search option
and showing LOV. Because it expects User to key-in the Material Number.
Thanks
Pats.

Hi,
I believe that under universe option Under control uncheck every thing and export the universe and this will resolve the issue. If not then go to following SDN link try to apply the solution provided in this section to see if you get your issue resolved.
[Large volume data - WebI document fails;
Bashir Awan

Similar Messages

BW OLAP universe object with Aggregate

How to create an BW OLAP universe object with Aggregate to a higher level than the underlying query?
The objective is to synchronize 2 queries by Contract Agreement quantity range and part of the calculation is to obtain the contract total quantity in one of the queries that is by Year and Month. For that query I need the total quantity for the contract.
Example;
Contract #    Year    Month     Qty
1             2011    1         230
6             2011    2          50
14            2011    3         124
u2026
25            2011   12          87
                 Total Qty --> ?
The following syntax gives the total quantity by contract / Year / Month, not the overall contract quantity. I could not find any MDX reference to use to solve this.
The dimension is [0SALESDEAL].[LEVEL01]
<EXPRESSION> AGGREGATE({[0SALESDEAL].CurrentMember:[0SALESDEAL].CurrentMember},[Measures].[DBKTD232QCONV8CVZYB17B5P0]) </EXPRESSION>
Thanks,
Marco
Edited by: Marco R on Dec 6, 2011 3:25 AM
Edited by: Marco R on Dec 6, 2011 3:27 AM
Edited by: Marco R on Dec 6, 2011 3:31 AM
Edited by: Marco R on Dec 6, 2011 3:33 AM
Edited by: Marco R on Dec 6, 2011 3:35 AM

Hi Andrew,
Looking at your statement I get the feeling you want this as a dimension/characteristic.
Since an expression has to be numeric and a characteristic in BW cannot be numeric, this will not work.
Only measures/keyfigures are possible.
The direction from SAP is to push any modeling to the BW query or even BW itself.
Hope this helps,
Marianne

Universe object that points to certain field according to the user PVL

Hi universe designing experts !
Marianne solved a problem I have in [this|Web Intelligence: Hide / Show object according to InfoView Locale; post. I wanted to replace an object/column in a report according to the users locale. This was done at report level with a selection containing the getPreferredViewingLanguage() function in WebI.
My question now is, could I somehow define in the universe an object that, according to the PVL of the report viewer, points to a different field in the database ?
We have description fields in the databse for different languages.
Thanks in advance !
P

Hi Marianne
Thanks again for your response.
Marianne Loenen wrote:
> If you want a solution for this written down, you need to give the database you use.
We are using an Oracle 10g database.
Marianne Loenen wrote:
> In Oracle there is a system view v$nls_parameters in which you can lookup stuff like that.
> It's a one row view, so you can use a (select xxx from v$nls_parameters) as column in any query.
OK I didn't know that. But I don't think that I could use this variable in this situation. Please correct me if I'm wrong...
What I want to do is this:
A user with Preferred Viewing Language nl_NL and a user with PVL en_GB are requesting the same report. In that report there is a field with a description about another field. The descriptions are 2 different columns in the database. You showed me before (thanks again) how I could switch the 2 field according to a users PVL that I could query from the system ( getPreferredViewingLanguage() ). I want, if possible, to do this at Universe level so I only have to drag 1 single object in the query that corresponds to the right column according to the report viewers PVL... So the en_GB guy will see English descriptions and the Dutch guy will see the Dutch descriptions all from the same object...
Would be cool if that was possible...
Thanks again for helping !
P

OLAP universe object parsing issue

Hi,
We have recently upgraded to Business Objects XI 3.1 sp3 with SAP 7.1 sp5 and SAP integration kit and all the transports are done for installation.
Using enterprise authentication i am logging into universe designer and then created a connection using SAP BW client on BEx query by providing all the login parameters (sap login usr name and pwd, application server name etc).
Universe is created and everything is fine, but when i tried to create a calculated measure i am unable to parse object.
i created a simple measure like
<EXPRESSION>(@Select(Key Figures\Orders) * @Select(Key Figures\Quantity))</EXPRESSION>
when i parse i am getting " XML expression is correct,however the MDX expression is not parsed in this process. (UNV 00050)"
when i used this calculated measure in webi, column is empty.how ever other objects are working fine in webi report and i could able to perform all calculations in webi.
Can any one tell me what could be the issue with object parsing.
Thanks,
Harsha

Hi,
I tried all the syntaxes but still the measure is not parsing, before upgrading In BO XI 3.1 sp2 i have created calculated measures and there was no issue.but after the upgrading to BO XI 3.1 sp3 i am not able to create calculated measures in universe I am using BEx query as source i have created some RKF's and CKF's in BEx, and i need to create some measures in universe as per reqmt.
I ran the report including the measure with below formula
<EXPRESSION>(@Select(Key Figures\Orders) * @Select(Key Figures\Quantity))</EXPRESSION>
MDX generated is as below:
WITH MEMBER [4IVR0WPP0WQB4EFAXRVX90OQ4].[BD4D9550-F4CD-4289-AA,CC,A4,21,82,3B,1B,EB] AS ' ([4IVR0WPP0WQB4EFAXRVX90OQ4].[4IW2HB8NU8VBIMMCXYNRQZNZG] *
[4IVR0WPP0WQB4EFAXRVX90OQ4].[4IW2HBO0W62QJVP99MSGB3LF0]) ' SELECT { [4IVR0WPP0WQB4EFAXRVX90OQ4].[BD4D9550-F4CD-4289-AA,CC,A4,21,82,3B,1B,EB],
[4IVR0WPP0WQB4EFAXRVX90OQ4].[4IW2HB8NU8VBIMMCXYNRQZNZG], [4IVR0WPP0WQB4EFAXRVX90OQ4].[4IW2HBO0W62QJVP99MSGB3LF0] } ON COLUMNS , NON EMPTY
[CS_LOCN].[LEVEL01].MEMBERS ON ROWS FROM [MP_003_BO] SAP VARIABLES [!V000006] INCLUDING [0FISCPER3].[001] : [0FISCPER3].[008] [0P_FYEAR] INCLUDING
[0FISCYEAR].[Z12010] [!V000003] INCLUDING [CS_VAC].[020]
here the MDX is incorrect the calculated measure is appearing before the SELECT statement in above MDX.
I would like to know that any MDX driver is missing and also how to debug this issue.
Thanks,
Harsha

View table and Master table don't match

I am setting up Materialize view replication between two systems connected over a WAN. The number of rows in the master table does not match the number of rows in the Table at the view site. Is there a way I can monitor/watch or otherwise see what replicated transaction are being applied to the view. I know that rows are added to and deleted from this table over the course the the day.

If the master table is always changing, the two tables will never match completely. Take the following scenario:
time 0: Insert row A in master table
time 1: Begin refresh of remote MV
time 2: Insert row B in master table
time 3: End refresh of remote MV
At this point, the master table will have two rows (A & B) while the remote table only has row A. If there is a materialized view log on the master table, row B will be present in the log and will replicate on the next refresh. I'm not aware of any utility that lets you view the data in the materialized view log in a particularly human-readable form, however-- that data is stored in a RAW column.
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

Query performance on materialized view vs master tables

Hi,
I am afraid of strange behavior in db, on my master tables UDBMOVEMENT_ORIG(26mil.rows) and UDBIDENTDATA_ORIG(18mil.rows) is created materialized view TMP_MS_UDB_MV (UDBMOVEMENT is synonym to this object) which meets some default conditions and join condition on these master tables. MV got about 12milions rows. I created MV to query not so huge objects, MV got 3GB, master tables toghether 12GB. But I don't understand that even physical reads and consistent gets are less on MV than on master tables, the final execution time is shorter on master tables. See my log below.
Why?
Thanks for answers.
SQL> set echo on
SQL> @flush
SQL> alter system flush buffer_cache;
System altered.
Elapsed: 00:00:00.20
SQL> alter system flush shared_pool;
System altered.
Elapsed: 00:00:00.65
SQL> SELECT
2 UDBMovement.zIdDevice, UDBMovement.sDevice, UDBMovement.zIdLocal, UDBMovement.sComputer, UDBMovement.tActionTime, UDBIdentData.sCardSubType, UDBIdentData.sCardType, UDBMovement.cEpan, UDBMovement.cText, UDBMovement.lArtRef, UDBMovement.sArtClassRef, UDBMovement.lSequenz, UDBMovement.sTransMark, UDBMovement.lBlock, UDBMovement.sTransType, UDBMovement.lGlobalID, UDBMovement.sFacility, UDBIdentData.sCardClass, UDBMovement.lSingleAmount, UDBMovement.sVAT, UDBMovement.lVATTot, UDBIdentData.tTarifTimeStart, UDBIdentData.tTarifTimeEnd, UDBIdentData.cLicensePlate, UDBIdentData.lMoneyValue, UDBIdentData.lPointValue, UDBIdentData.lTimeValue, UDBIdentData.tProdTime, UDBIdentData.tExpireDate
3 FROM UDBMOVEMENT_orig UDBMovement, Udbidentdata_orig UDBIdentData
4 WHERE
5 UDBMovement.lGlobalId = UDBIdentData.lGlobalRef(+) AND UDBMovement.sComputer = UDBIdentData.sComputer(+)
6 AND UDBMovement.sTransType > 0 AND UDBMovement.sDevice < 1000 AND UDBMovement.sDevice>= 0 AND UDBIdentData.sCardType IN (2) AND (bitand(UDBMovement.sSaleFlag,1) = 0 AND bitand(UDBMovement.sSaleFlag,4) = 0) AND UDBMovement.sArtClassRef < 100
7 AND UDBMovement.tActionTime >= TO_DATE('05/05/2011 00:00:00', 'dd/mm/yyyy hh24:mi:ss') + 0.25 AND UDBMovement.tActionTime < TO_DATE('05/05/2011 00:00:00', 'dd/mm/yyyy hh24:mi:ss') + 0.5
8 ORDER BY tActionTime, lBlock, lSequenz;
4947 rows selected.
Elapsed: 00:00:15.84
Execution Plan
Plan hash value: 1768406139
| Id | Operation | Name | Rows | Bytes |TempSpc| Cost (%CPU)| Time |
| 0 | SELECT STATEMENT | | 7166 | 1238K| | 20670 (1)| 00:04:09 |
| 1 | SORT ORDER BY | | 7166 | 1238K| 1480K| 20670 (1)| 00:04:09 |
| 2 | NESTED LOOPS | | | | | | |
| 3 | NESTED LOOPS | | 7166 | 1238K| | 20388 (1)| 00:04:05 |
|* 4 | TABLE ACCESS BY INDEX ROWID| UDBMOVEMENT_ORIG | 7142 | 809K| | 7056 (1)| 00:01:25 |
|* 5 | INDEX RANGE SCAN | IDX_UDBMOVARTICLE | 10709 | | | 61 (0)| 00:00:01 |
|* 6 | INDEX UNIQUE SCAN | UDBIDENTDATA_PRIM | 1 | | | 1 (0)| 00:00:01 |
|* 7 | TABLE ACCESS BY INDEX ROWID | UDBIDENTDATA_ORIG | 1 | 61 | | 2 (0)| 00:00:01 |
Predicate Information (identified by operation id):
4 - filter("UDBMOVEMENT"."STRANSTYPE">0 AND "UDBMOVEMENT"."SDEVICE"<1000 AND
BITAND("SSALEFLAG",1)=0 AND "UDBMOVEMENT"."SDEVICE">=0 AND BITAND("UDBMOVEMENT"."SSALEFLAG",4)=0)
5 - access("UDBMOVEMENT"."TACTIONTIME">=TO_DATE(' 2011-05-05 06:00:00', 'syyyy-mm-dd
hh24:mi:ss') AND "UDBMOVEMENT"."TACTIONTIME"<TO_DATE(' 2011-05-05 12:00:00', 'syyyy-mm-dd
hh24:mi:ss') AND "UDBMOVEMENT"."SARTCLASSREF"<100)
filter("UDBMOVEMENT"."SARTCLASSREF"<100)
6 - access("UDBMOVEMENT"."LGLOBALID"="UDBIDENTDATA"."LGLOBALREF" AND
"UDBMOVEMENT"."SCOMPUTER"="UDBIDENTDATA"."SCOMPUTER")
7 - filter("UDBIDENTDATA"."SCARDTYPE"=2)
Statistics
543 recursive calls
0 db block gets
84383 consistent gets
4485 physical reads
0 redo size
533990 bytes sent via SQL*Net to client
3953 bytes received via SQL*Net from client
331 SQL*Net roundtrips to/from client
86 sorts (memory)
0 sorts (disk)
4947 rows processed
SQL> @flush
SQL> alter system flush buffer_cache;
System altered.
Elapsed: 00:00:00.12
SQL> alter system flush shared_pool;
System altered.
Elapsed: 00:00:00.74
SQL> SELECT UDBMovement.zIdDevice, UDBMovement.sDevice, UDBMovement.zIdLocal, UDBMovement.sComputer, UDBMovement.tActionTime, UDBMovement.sCardSubType, UDBMovement.sCardType, UDBMovement.cEpan, UDBMovement.cText, UDBMovement.lArtRef, UDBMovement.sArtClassRef, UDBMovement.lSequenz, UDBMovement.sTransMark, UDBMovement.lBlock, UDBMovement.sTransType, UDBMovement.lGlobalID, UDBMovement.sFacility, UDBMovement.sCardClass, UDBMovement.lSingleAmount, UDBMovement.sVAT, UDBMovement.lVATTot, UDBMovement.tTarifTimeStart, UDBMovement.tTarifTimeEnd, UDBMovement.cLicensePlate, UDBMovement.lMoneyValue, UDBMovement.lPointValue, UDBMovement.lTimeValue, UDBMovement.tProdTime
2 FROM UDBMOVEMENT WHERE
3 UDBMovement.sTransType > 0 AND UDBMovement.sDevice < 1000 AND UDBMovement.sDevice>= 0 AND UDBMovement.sCardType IN (2) AND (bitand(UDBMovement.sSaleFlag,1) = 0 AND bitand(UDBMovement.sSaleFlag,4) = 0) AND UDBMovement.sArtClassRef < 100
4 AND UDBMovement.tActionTime >= TO_DATE('05/05/2011 00:00:00', 'dd/mm/yyyy hh24:mi:ss') + 0.25
5 AND UDBMovement.tActionTime < TO_DATE('05/05/2011 00:00:00', 'dd/mm/yyyy hh24:mi:ss') + 0.5 ORDER BY tActionTime, lBlock, lSequenz;
4947 rows selected.
Elapsed: 00:00:26.46
Execution Plan
Plan hash value: 3648898312
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
| 0 | SELECT STATEMENT | | 2720 | 443K| 2812 (1)| 00:00:34 |
| 1 | SORT ORDER BY | | 2720 | 443K| 2812 (1)| 00:00:34 |
|* 2 | MAT_VIEW ACCESS BY INDEX ROWID| TMP_MS_UDB_MV | 2720 | 443K| 2811 (1)| 00:00:34 |
|* 3 | INDEX RANGE SCAN | EEETMP_MS_ACTTIMEDEVICE | 2732 | | 89 (0)| 00:00:02 |
Predicate Information (identified by operation id):
2 - filter("UDBMOVEMENT"."STRANSTYPE">0 AND BITAND("UDBMOVEMENT"."SSALEFLAG",4)=0 AND
BITAND("SSALEFLAG",1)=0 AND "UDBMOVEMENT"."SARTCLASSREF"<100)
3 - access("UDBMOVEMENT"."TACTIONTIME">=TO_DATE(' 2011-05-05 06:00:00', 'syyyy-mm-dd
hh24:mi:ss') AND "UDBMOVEMENT"."SDEVICE">=0 AND "UDBMOVEMENT"."SCARDTYPE"=2 AND
"UDBMOVEMENT"."TACTIONTIME"<TO_DATE(' 2011-05-05 12:00:00', 'syyyy-mm-dd hh24:mi:ss') AND
"UDBMOVEMENT"."SDEVICE"<1000)
filter("UDBMOVEMENT"."SCARDTYPE"=2 AND "UDBMOVEMENT"."SDEVICE"<1000 AND
"UDBMOVEMENT"."SDEVICE">=0)
Statistics
449 recursive calls
0 db block gets
6090 consistent gets
2837 physical reads
0 redo size
531987 bytes sent via SQL*Net to client
3953 bytes received via SQL*Net from client
331 SQL*Net roundtrips to/from client
168 sorts (memory)
0 sorts (disk)
4947 rows processed
SQL> spool off
Edited by: MattSk on Feb 4, 2013 2:20 PM

I have added some tkprof outputs on MV and master tables:
SELECT tmp_ms_udb_mv.zIdDevice, tmp_ms_udb_mv.sDevice, tmp_ms_udb_mv.zIdLocal, tmp_ms_udb_mv.sComputer, tmp_ms_udb_mv.tActionTime, tmp_ms_udb_mv.sCardSubType, tmp_ms_udb_mv.sCardType, tmp_ms_udb_mv.cEpan, tmp_ms_udb_mv.cText, tmp_ms_udb_mv.lArtRef, tmp_ms_udb_mv.sArtClassRef, tmp_ms_udb_mv.lSequenz, tmp_ms_udb_mv.sTransMark, tmp_ms_udb_mv.lBlock, tmp_ms_udb_mv.sTransType, tmp_ms_udb_mv.lGlobalID, tmp_ms_udb_mv.sFacility, tmp_ms_udb_mv.sCardClass, tmp_ms_udb_mv.lSingleAmount, tmp_ms_udb_mv.sVAT, tmp_ms_udb_mv.lVATTot, tmp_ms_udb_mv.tTarifTimeStart, tmp_ms_udb_mv.tTarifTimeEnd, tmp_ms_udb_mv.cLicensePlate, tmp_ms_udb_mv.lMoneyValue, tmp_ms_udb_mv.lPointValue, tmp_ms_udb_mv.lTimeValue, tmp_ms_udb_mv.tProdTime
FROM tmp_ms_udb_mv WHERE
tmp_ms_udb_mv.sTransType > 0 AND tmp_ms_udb_mv.sDevice < 1000 AND tmp_ms_udb_mv.sDevice>= 0 AND tmp_ms_udb_mv.sCardType IN (1) AND (bitand(tmp_ms_udb_mv.sSaleFlag,1) = 0 AND bitand(tmp_ms_udb_mv.sSaleFlag,4) = 0) AND tmp_ms_udb_mv.sArtClassRef < 100
AND tmp_ms_udb_mv.tActionTime >= TO_DATE('05/05/2011 00:00:00', 'dd/mm/yyyy hh24:mi:ss') + 0.25
AND tmp_ms_udb_mv.tActionTime < TO_DATE('05/05/2011 00:00:00', 'dd/mm/yyyy hh24:mi:ss') + 0.5
ORDER BY tActionTime, lBlock, lSequenz
call count cpu elapsed disk query current rows
Parse 1 0.04 0.10 0 0 0 0
Execute 1 0.00 0.00 0 0 0 0
Fetch 596 0.17 27.07 2874 8894 0 8925
total 598 0.21 27.18 2874 8894 0 8925
Misses in library cache during parse: 1
Optimizer mode: ALL_ROWS
Parsing user id: 60
Rows Row Source Operation
8925 SORT ORDER BY (cr=8894 pr=2874 pw=0 time=27071773 us)
8925 MAT_VIEW ACCESS BY INDEX ROWID TMP_MS_UDB_MV (cr=8894 pr=2874 pw=0 time=31458291 us)
8925 INDEX RANGE SCAN EEETMP_MS_ACTTIMEDEVICE (cr=68 pr=68 pw=0 time=161347 us)(object id 149251)
SELECT
UDBMovement.zIdDevice, UDBMovement.sDevice, UDBMovement.zIdLocal, UDBMovement.sComputer, UDBMovement.tActionTime, UDBIdentData.sCardSubType, UDBIdentData.sCardType, UDBMovement.cEpan, UDBMovement.cText, UDBMovement.lArtRef, UDBMovement.sArtClassRef, UDBMovement.lSequenz, UDBMovement.sTransMark, UDBMovement.lBlock, UDBMovement.sTransType, UDBMovement.lGlobalID, UDBMovement.sFacility, UDBIdentData.sCardClass, UDBMovement.lSingleAmount, UDBMovement.sVAT, UDBMovement.lVATTot, UDBIdentData.tTarifTimeStart, UDBIdentData.tTarifTimeEnd, UDBIdentData.cLicensePlate, UDBIdentData.lMoneyValue, UDBIdentData.lPointValue, UDBIdentData.lTimeValue, UDBIdentData.tProdTime, UDBIdentData.tExpireDate
FROM UDBMOVEMENT_orig UDBMovement, Udbidentdata_orig UDBIdentData
WHERE
UDBMovement.lGlobalId = UDBIdentData.lGlobalRef(+) AND UDBMovement.sComputer = UDBIdentData.sComputer(+)
AND UDBMovement.sTransType > 0 AND UDBMovement.sDevice < 1000 AND UDBMovement.sDevice>= 0 AND UDBIdentData.sCardType IN (1) AND (bitand(UDBMovement.sSaleFlag,1) = 0 AND bitand(UDBMovement.sSaleFlag,4) = 0) AND UDBMovement.sArtClassRef < 100
AND UDBMovement.tActionTime >= TO_DATE('05/05/2011 00:00:00', 'dd/mm/yyyy hh24:mi:ss') + 0.25
AND UDBMovement.tActionTime < TO_DATE('05/05/2011 00:00:00', 'dd/mm/yyyy hh24:mi:ss') + 0.5
ORDER BY tActionTime, lBlock, lSequenz
call count cpu elapsed disk query current rows
Parse 1 0.03 0.06 0 0 0 0
Execute 1 0.00 0.00 0 0 0 0
Fetch 596 0.76 16.94 3278 85529 0 8925
total 598 0.79 17.01 3278 85529 0 8925
Misses in library cache during parse: 1
Optimizer mode: ALL_ROWS
Parsing user id: 60
Rows Row Source Operation
8925 SORT ORDER BY (cr=85529 pr=3278 pw=0 time=16942799 us)
8925 NESTED LOOPS (cr=85529 pr=3278 pw=0 time=15017857 us)
22567 TABLE ACCESS BY INDEX ROWID UDBMOVEMENT_ORIG (cr=17826 pr=1659 pw=0 time=7273473 us)
22570 INDEX RANGE SCAN IDX_UDBMOVARTICLE (cr=111 pr=111 pw=0 time=112351 us)(object id 143693)
8925 TABLE ACCESS BY INDEX ROWID UDBIDENTDATA_ORIG (cr=67703 pr=1619 pw=0 time=8154915 us)
22567 INDEX UNIQUE SCAN UDBIDENTDATA_PRIM (cr=45136 pr=841 pw=0 time=3731470 us)(object id 108324)

Olap universe lov restriction on detail object key

Hi,
I created a restriction on dimension lov in SAP olap universe using 0PLANT dimension on Orders keyfigure as below
<EXPRESSION>(@Select(Key Figures\Orders),[0PLANT].[1000])</EXPRESSION>
this syntax works but webi results are not matching with BEx.
Values of BEx RKF and formula object (
=[Orders] Where([L01 Plant] = "1000")
)created in webi are matching.
I am trying to create restriction on detail key object, like
<EXPRESSION>(@Select(Key Figures\Orders),[0PLANT].[LEVEL01].[[20PLANT]].[Value].[1000])</EXPRESSION>
above measure is giving error when i run the webi query.
here both L01 Plant and L01 Plant Key are having same lov as 1000,but i wanted check exact values with detail key syntax.
Can anyone please tell me the syntax for using detail objects keys for restriction in Select Clause.
Thanks,
Harsha

Hi,
why are you not creating this as a restricted key figure in the underlying BEx Query ?
Ingo

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

LOV Filtering on OLAP universe

Hi
i have a BOXI 3.1 SP2 FP2.6 universe on top of a bex query (BW BI 7 SP5)
my bex query contains a variable 'ready for input' which give me a prompt condition on BO universe.
My BO condition has the default LOV <Variable name> which gives me 2 hidden objects <Variable name> and <Variable name>Base.
this hidden object displays a list of values on prompt in my report. i want to filter the list of values on 2 single values (from the whole list).
I know i can define the 2 single values directly in my prompt by filling the 'value ' and 'key'. But my 'value ' are static.
I'd rather to limit the list of the LOV directly on the hidden objects <Variable name> or <Variable name>Base of the universe on the 2 key of my requested items
is it possible ?
thanks in advance,
Rgds,

Ingo, you mentioned in this posting that the functionality required is not supported for OLAP universes ... is this still the case in 3.1 ?
WE have a similar challenge here where we need to restrict the list of Vendors that is presented to the user to only Merch Vendors. I need to do this in a BEx Query, as there is a 2nd variable which returns a list of articles based on the selected Vendor, so need the selected Vendor to be available in the Post-Popup variable exit code.
I have implemented the RSR_VARIABLE_F4_RESTRICT_BADI in BW, which correctly limits the list of values in teh Vendor dropdown when the BEx query is run in RSRT / web, but in WebI this list of values doesn't apply.
Cheers,
Andrew

Cascading LOV in OLAP UNIVERSE

Hi.
I got a problem with a lov in webi.
I have created an OLAP Universe buitl on a SAP BW 7.0 infocube and I created a hierarchy and a cascading list of value but when I go to my WEBI report it doesn`t works, it isn`t filtering the objects by the hierarchy, it duplicates the same information for all the object's concepts.
For example i got a LEVEL 1 concept u201CBuenaventurau201D and it shows in LEVEL 2 u201CEGRESOSu201D and u201CINGRESOSu201D the problem is that it show the same for all the LEVEL 1 concepts and it should only show "EGRESOS" and "INGRESOS" for LEVEL 1 concept "Buenaventura" because is the only one that has information.
Can anybody pls tell me why is having this behavior.
Thanks and regards,
Julio
Hola.
Tengo un problema con una lista de valores en cascada en un universo olap que lee un infocubo de BW 7.0. Cree una jerarquía en el universo y una lista de valores en cascada, pero cuando voy al reporte WEBI y hago un prompt a la lista de valores no me filtra por concepto, repite la misma información para todos los conceptos.
Por ejemplo tengo en el NIVEL 1 el concepto "Buenaventura" y me muestra en NIVEL 2para este concepto "EGRESOS" e "INGRESOS", el problema es que me muestra lo mismo para todos los conceptos del NIVEL 1 cuando sólo deberian aparecer para "Buenaventura".
Alguien me podría explicar por favor por qué se comporta así.
Gracias y Saludos,
Julio

Hi Julio,
As of now the cascading list of values are not supported in the universe created on top of SAP BW (Bex Queries).
In the below thread Eric has mentioned that he has got this confirmed from SAP:
Link: [Re: OLAP castcading prompt]
Regards,
Rohit

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

Adding mandatory filter with own LoV to BW OLAP Universe

Dear all,
I want to add a own filter with custom LoV to a characteristics-filter in an OLAP Universe. This filter does not exist in the BEx Query, so I have to do it manually.
So when the prompt shows up in WebI, the User should be able to select the Values from the custom LoV, for example:
- Tokio
- London
- Paris
The filter has to be mandatory and Tokio should be preselected. I was testing some things with the filter-XML, but always got errors. Can somebody tell me how this works?
Thank you for help in advance!
B. Wegner

Hi,
There are a few steps involved, I would suggest approaching them one at a time.
First, try to set up a filter (condition in the universe) to only show data for Tokyo (no prompt). Ensure you can get this to work.
Next, try and turn this condition into a prompt, but just define the LoV in the prompt syntax, not a separate object. Check that this works.
Next, try and split out that LoV into it's own object that populates from the characteristic in the BEx query. This will be the tricky part (maybe), if possible, get a filter created in the BEx query (make sure it's set as 'ready for user input') so that you see how the LoV gets created.
As a last resort, have a look in the manual: http://help.sap.com/businessobject/product_guides/boexir31SP3/en/xi31_sp3_sap_olap_univ_en.pdf
Hope that helps.

Universe object that returns the number of rows in table?

Is it possible to create a Universe object to support the following SQL query:
SELECT * FROM (SELECT ROWNUM rownum1 FROM TABLE) WHERE rownum1 = (SELECT (MAX(ROWNUM)) FROM TABLE)

Amr,
Hey dude, welcome back, long time no hear from you.
You were on the right track with "number of rows", but here is the correct syntax:
=NumberOfRows([Query 1])
Thanks,
John

Olap universe(creating new object)

All,
I am using bo 4.0 version and i have created an olap universe on top of bex query.i am new to olap universe.
I have a need to create a new customized object in my olap universe out of two existing objects.As of now i am creating variables in my webi report generated out of the olap universe to fit my need.Instead i want to create a condition object or some kind of object in the universe itself.
how can i do this?Any ideas or suggestions.
For ex:
my requirement looks like this,not exactly the same as indicated below but similar.
existing objects
city object has certain values 'hyd','new york'
currency objecthas 'rupee','dollar'
new person object out of the above mentioned existing objects
if city='hyd' and currency='rupee' then 'indian' else 'non indian'
how can i do this?Any ideas or suggestions.
Regards,
Reji.
Edited by: reji2011 on Dec 7, 2011 11:10 PM

Hi,
there's a function builder / formula editor in Universe Designer, with OLAP universes this uses MDX syntax with XML markup.
to build up some logic, you need to use the "IIF" operator.
regards,
H
p.s. in BI 4.0, route-one should be the BICS BEx connection, not the OLAP .unv ..

BW LOV in OLAP Universe

Hi All,
I have a little problem with BW variable (individual values, required) in query where in my OLAP universe it turns prompt in the following sturcture:
BW BEx
Infoobject Year/Month (0CALMONTH)
Variable 0PCALMON
BO Universe
Class Year/Month
Dimension L01 Year/Month
Hidden dimension Lov Year/Month Base
My report makes the search or should seek direct the LOV that contains the year in infoobject BW ("JUL 2011", "AUG 2011", ...) but it does not return expected. It simply returns "01.0000", "02.0000", "11.0821", "SEP 1787" ... and only at the end of LOV it returns the correct values or are in the InfoCube ("JUL 2011, AUG 2011", ...)
I'm using BO XI 3.1 SP3 and BW 7
Any suggestions ?
Tks,

Hi,
These values come straight out of the BW masterdata.
My guess is you still have some old invalid values there.
Note that whenever you see the key version in stead of the formatted version,
it means no text was found associated with this key (in the current language).
Hope this helps (better late then never right),
Marianne

OLAP Universe : Objects LOV pointing to master table in BW

Similar Messages

Maybe you are looking for