Use short description on OLAP dimension member in disco for OLAP

Hi All,
I've noticed in the spreadsheet add-in you can decide under "query options" whether to use the Long or Short Description when displaying a dimension member. How do you do the same in discoverer PLUS for OLAP ? I cant find it anwhere.
Cheers,
Brandon

This feature is not available in Disco :-( Logged as an enhancement request.
Keith

Similar Messages

Any setup reqd for Disco for OLAP to attach multiple AWs per schema...

I have a schema with two AWs - A, B (created the new AW - B recently). 
When i log on to Discoverer Plus for OLAP via an App Server (givign the schema user/pass), i do not get to pick the AW B explicitly. 
All Measure folders/cubes from both AWs A and B are displayed and i can choose the cube from AW B. However after all the worksheet creation steps are done, the worksheet query fails with the error -- 
======================================== 
oracle.dss.dataSource.common.OLAPException: null 
java.lang.NullPointerException 
java.lang.NullPointerException 
oracle.dss.dataSource.common.QueryRuntimeException: BIB-9009 Oracle OLAP could not create cursor. 
 
======================================== 
D4O Diagnostic test gives the following: 
 
oracle.dss.d4o.common.D4OException: BIB-9009 Oracle OLAP could not create cursor. 
oracle.express.ExpressServerExceptionError class: OLAPI
Server error descriptions: 
DPR: Unable to execute the query, Generic at TxsOqCursorManager::fetchInitialBlocks 
OES: ORA-34224: Analytic workspace <<schema>>.<<AW_B>> is not attached. 
, Generic at TxsRdbResultSet:absolute() 
 
======================================== 
The dimension selections etc (intermediate steps of the wizard) are working on the right data/hierarchies.. So the second AW did get attached. 
If i create a worksheet based on cubes present in AW #1: A, then it works fine. 
Is there any special settings/program... ONATTACH, AUTOGO kind... which is required while using multiple AWs within a schema? 
The schema has olap_user and olap_dba roles as well as access to the Discoverer Catalog via iAS Discoverer Admin. 
Thanks in advance for any help. 
Shankar 
Message was edited by: 
user498007 
Trying to make it readable... Didn't retain line breaks. Now it does. 

Discoverer for OLAP should see all measures and dimensions that you have access to. You never need to explicitly attach an AW.
You are correct in thinking that the AW did get attached if you get to a point in the Workbook Wizard where data is displayed. The error messages are not meaningful to mean. I would guess that it is the result of some sort of metadata error. You might see if AW 'A' is causing any sort of confict by revoking SELECT on AW$A (you'll need to do this as a different user than the owner of the AW) an then attempting to view AW 'B'.

How to export data from Elimination Value dimension member by HAL HFM adapter?

Good day! Is it possible to export HFM 4.0.5 data with HAL from the <Elimination> Value dimension member? In 3.* versions it wasn't and there is Known Issue in the "HFM 3.* Adapter Read Me" file: "The Hyperion Financial Management Adapter exports data using the <entity currency> Value dimension member. The documentation erroneously states that there is a port available for the Value dimension" But there is not such point in the same file for HFM 4.0.5 AND there is Value port in the HFM 4.0.5. Adapter. Thanks! Regards, Georgy 

In the first approch, try to change the exporting parameter type REF TO DATA.
Try like:
CLASS lcl_test DEFINITION.
PUBLIC SECTION.
 DATA: t_mara TYPE HASHED TABLE OF mara WITH UNIQUE KEY matnr.
 METHODS:
 constructor,
 get
 IMPORTING
 if_matnr TYPE matnr
 EXPORTING
 ea_mara TYPE REF TO data.
ENDCLASS. "lcl_test DEFINITION
START-OF-SELECTION.
DATA: lo_test TYPE REF TO lcl_test,
 lr_data TYPE REF TO data.
FIELD-SYMBOLS: <fa_mara> TYPE ANY,
 <f_field> TYPE ANY.
CREATE OBJECT lo_test.
lo_test->get(
 EXPORTING
 if_matnr = '000000000077000000' " << Replace Your Material
 IMPORTING
 ea_mara = lr_data ).
ASSIGN lr_data->* TO <fa_mara>.
ASSIGN COMPONENT 'ERSDA' OF STRUCTURE <fa_mara> TO <f_field>.
<f_field> = space.
WRITE: 'Done'.
CLASS lcl_test IMPLEMENTATION.
METHOD constructor.
 SELECT * INTO TABLE t_mara
 FROM mara
 UP TO 10 ROWS.
ENDMETHOD. "constructor
METHOD get.
 FIELD-SYMBOLS: <lfs_mara> LIKE LINE OF me->t_mara.
 READ TABLE me->t_mara ASSIGNING <lfs_mara> WITH KEY matnr = if_matnr.
 GET REFERENCE OF <lfs_mara> INTO ea_mara.
ENDMETHOD. "get
ENDCLASS. "lcl_test IMPLEMENTATION
Regards,
Naimesh Patel

Dynamic Description in Analysis for OLAP

hi.
I am trying to create an application in Analysis for OLAP where I am trying to populate the Dynamic description based on the value entered by the user.
It works in Bex queries, however I don't see the description populated when I create a analysis for OLAP report over the same Bex query. in fact I dont see the description of any bex query. is it not possible? I am using BO 4.1
Regards,
Mahesh

Hi Kathi,
finally we solved the porblem. i guess you are working with IE 8.0?
*if so, add the BO-Server (http://server.com) to your lokal intranet sites (inside the IE 8.0).
*also check document mode in IE 8.0 is set to Quirks Mode (under ''Tool/Developer Tool'') when opening the analyis olap report
then it should work.
regards
Tom

Dimension Member Naming Constraints

SSM Forum,
Are there any constraints for identifying dimension member names?
For example, "No asteriks or semi-colons are allowed, and dimension member names must be less than 20 characters long."
Thanks a lot,
Jason

Jason,
I am going to suggest a 60 character limit, but certainly encourage fewer characters. An issue here is when displaying in various areas of the interface, especially when building metric sets in Entry and Approval, you may get the member name truncated to fit the available real estate in the interface.
My recommendation, especially when having similiar member names that are very long, is to place the differentiator at the beginning rather than the end of the name of the name.
Regards,
Bob

BI Addin Query- Using Dimension Member ID?

When we query OLAP cubes via Excel Add-in by default for each dimension member we see the Long description. So example the for business unit we see the description - HEDGE_FUNDS instead of the member ID e.g. 13408 in this case.
We have option to display either Short or long description in report but there is no such option to select member_id instead of long description during querying.
So for example while querying we want to select Member ID and see Member ID's in dimension selection instead of Long description? Is anybody aware if this is a feature available in Excel addin. We are using version 10.1.2.3

You should load the member id as long description to display it. I dont think** there is any other way.
Generally the requirements is like users would like to see long description as the codes are some numbers or alphanumeric values which cannot be recognised by end users(hard to remember) so the best approach is to load the long description as id_description. This change should be done in the dimensin view which is source for the dimension.
Thanks
Brijesh

Use short label in disco PLUS for OLAP report

Hi All,
I've noticed in the spreadsheet add-in you can decide under "query options" whether to use the Long or Short Description when displaying a dimension member. How do you do the same in discoverer PLUS for OLAP ? I cant find it anwhere.
Cheers,
Brandon

Hi Brandonm,
You currently do not have this option in Plus to have use the Short, Long labels.
I think this is planned for a future version, maybe in 11 we will have this.
Regards
Roelie

Performance issue:Show id and Description for same dimension member

Hi,
I am connecting a cube to another reporting system and i need to show the id of member resulting of a query.My first thought was to use this kind of code (bellow) however when i do the same thing with many dimension (many cross join ),it slow down a lot
my query.So how can i have in the same DImension member showing a description and id ? I also have a lot of statement,so i can't have just two columns in the dimension or i will need to duplication the mdx and i could drop down the performance.
So i am trying to get as a result
Dim1 | Dim2| Dim3| Measure
1 50
32 25.2
and also be able to get
Dim1 | Dim2 | Dim3
| Measure
NameElement1Dim1 NameElement50Dim2
NameElement32Dim3 25.2
Thanks in advance
with MEMBER [Measures].[IdElement] as
<element>.currentmember.properties("KEY")
select
CROSSJOIN({[Measures].[IdElement]},{[METRIC].[Description].[All]}),
CROSSJOIN({[Measures].[value]},{<listmetricmdx>})
} on columns,
<pointofview>
<element_and_function>
<TimeBreakdown>
} on rows
<list_filter_clause>
) as list
where ((ElementName is null AND IdElement=0) OR (ElementName is not null))
<list_condition_metric>
but i have multiple

Hi Vincent,
In your query, you use CrossJoin in it. Crossjoin function will cause the performance issue if there are a lot of properties that need to be displayed. If you cross-join medium-sized or large-sized sets (e.g., sets that contain more than 100 items each),
you can end up with a result set that contains many thousands of items—enough to seriously impair performance. For the detail information, please see:
http://sqlmag.com/data-access/cross-join-performance
In your MDX query, ensure only retrieval the required data. Here are some useful links for your reference.
Configure memory setting:
http://social.msdn.microsoft.com/Forums/en/sqlanalysisservices/thread/bf70ca19-5845-403f-a85f-eac77c4495e6
Performance Tuning:
http://www.microsoft.com/downloads/details.aspx?FamilyID=3be0488d-e7aa-4078-a050-ae39912d2e43&displaylang=en
http://www.packtpub.com/article/query-performance-tuning-microsoft-analysis-services-part2
Regards,
Charlie Liao
TechNet Community Support

Oracle OLAP:Same member values across dimensions

We had an enquiry from a client which mentions:
Per Essbase the same dimension member value cannot exist across multiple dimensions. e.g. if we have a account dimension with member 1001 , it is not possible to have product dimension with same member value 1001. This is essentially because Essbase implements it like a shared member. Apparently Essbase Excel-addin will not know what dimension to search for if both have same values.
As per our understanding there is no such limitation in Oracle OLAP both during cube build or querying via Excel Add-in. i.e we can have account dimension with member 1001 and same member value can exist in a product dimension. Please advise and if anybody has any reference to any documentation in this regard please let us know.

Hi there,
You are correct - there is no such limitation in Oracle OLAP.
A dimension value must be unique in any given dimension but can be repeated in other dimensions.
I do not have any documentation but this is really easy to prove using the OLAP worksheet in AWM, eg:
aw create test
define dim1 dimension text
maintain dim1 add 'MEMBER1'
report dim1
define dim2 dimension text
maintain dim2 add 'MEMBER1'
report dim2
aw detach test
aw delete testI hope this helps
Thanks,
Stuart Bunby
OLAP Blog: http://oracleOLAP.blogspot.com
OLAP Wiki: http://wiki.oracle.com/page/Oracle+OLAP+Option
OLAP on OTN: http://www.oracle.com/technology/products/bi/olap/index.html
DW on OTN : http://www.oracle.com/technology/products/bi/db/11g/index.html

Change description of dimension member based on selection in other dimension

Problem
Let’s say that I have two dimensions Dim Account and Dim Company.
Dim Account consists of Account and Account Description. Each Account has one description for each Company.
I want the description in Dim Account be based on which Company that is selected.
So if Company 1 is selected the description should be set to Account_Company1_Desc if Company2 is selected Account_Company2_Desc should be selected and so on…
If more than one company is selected, the Account_General_Desc should be used.
I would be very grateful if anyone has
an idea of how this problem could be solved.
Best Regards
AL

Hi AL_T,
According to your description, you want to have the description show general_desc when selection multiple companies. Right?
In this scenario, since each company has one description, we should already build the relationship between company and company_desc. However, in Analysis Services, it's not supported to apply MDX expression to make a relationship dynamically. And we
can't make it show different members of a dim based on number of another dimension member selection in query. So your requirement can't be achieved currently.
Regards,
Simon Hou
TechNet Community Support

Unable to use Free Text-Short Description

Hi,
I'm unable to use the short description free text field for the Purchase requisition and the system only allows the Purchases against material master (material number) and the short text is greyed out.
Please help.

The field Selection key were changed as per advise and unfortunately the desired field were still grey-out.
My observation is that the these fields are somehow linked to Document Types and this is was evident once changing to different Doc types (eg.Framowork or Other Related Requisition types).
Your help is still awaited.

How do i show descriptions instead of dimension values at presentations ?

We are facing a problem that could be a BIBeans problem or could be an OLAP problem, please inform if to change forum:
We are using jdev 903/BIB903 accessing an AW created at Oracle OLAP 9205 with AWM.
All our dimensions were created at OWB 10g and deployed to RDBMS following the general rules below:
DIM X
ID_X - sequence primary key
CD_X - original key from source systems
DS_X, NM_X, and so on - description fields and hierarchy fields related to this record.
i.e.:
SQL> desc dim_rota
Name Null? Type
ID_ROTA NOT NULL NUMBER(6)
CD_EMPRESA NOT NULL NUMBER(2)
CD_FILIAL NOT NULL NUMBER(2)
CD_ROTA NOT NULL VARCHAR2(3)
NM_FILIAL NOT NULL VARCHAR2(40)
NM_ROTA NOT NULL VARCHAR2(30)
CD_SETOR NOT NULL VARCHAR2(1)
ID_SETOR NOT NULL NUMBER(6)
NM_SETOR NOT NULL VARCHAR2(30)
this dimension has 1 hierarchy with 2 levels called SETOR and ROTA.
when we generated the AW using AWM, each field (except ID) is created as a variable dimensioned by DIM_ROTA, as shown below:
->listby dim_rota
35 objects dimensioned by or related to DIM_ROTA in analytic workspace AW1
DIM_ROTA_CD_EMPRESA
DIM_ROTA_CD_FILIAL
DIM_ROTA_CD_ROTA
DIM_ROTA_CD_SETOR
DIM_ROTA_CREATEDBY
DIM_ROTA_FAMILYREL
DIM_ROTA_GID
DIM_ROTA_INHIER
DIM_ROTA_LEVELCOLMAP
DIM_ROTA_LEVELREL
DIM_ROTA_NM_FILIAL
DIM_ROTA_NM_ROTA
DIM_ROTA_NM_SETOR
DIM_ROTA_ORDER
DIM_ROTA_PARENTREL
ID field was concatenated with level name to generate the dimension value - so, for the following relational record:
SQL> select id_rota, cd_rota, nm_rota from dim_rota where ID_ROTA = 233;
ID_ROTA CD_ROTA NM_ROTA
233 A99 A99-Consig. Sup. Setor A
we have at multidimensional side:
->LIMIT DIM_ROTA TO 'ROTA.233'
->rpr dim_rota
DIM_ROTA
ROTA.233
->dsc dim_rota_nm_rota
DEFINE DIM_ROTA_NM_ROTA VARIABLE TEXT <DIM_ROTA DIM_ROTA_HIERLIST ALL_LANGUAGES>
LD IMPLEMENTATION NM_ROTA Attribute for DIM_ROTA Dimension
->rpr down dim_rota w 30 dim_rota_nm_rota
ALL_LANGUAGES: AMERICAN_AMERICA
-------DIM_ROTA_NM_ROTA-------
------DIM_ROTA_HIERLIST-------
DIM_ROTA ROTA
ROTA.233 A99-Consig. Sup. Setor A
here comes our question: how do we show at BIBeans designer/presentations the related descriptive fields and NOT the dimension values themselves?
thanks in advance,
Flavio

There a re two additional attributes that need to be mapped within OWB for each dimension:
Long Description - this is used by the presentation beans and query and calc builder to replace the dimension values with more meaningful/end-user friendly descriptions
Short Descriptions - this can be used where the long description is too long for display purposes. In BI Beans 10g Release 2 (due out soon) you will be able to select between long/short descriptions when using many of the new tags.
These new attributes will be automatically picked up by the OLAP Bridge in OWB and automatically added to the OLAP catalog.
Hope this helps
Business Intelligence Beans Product Management Team
Oracle Corporation

How do i show descriptions instead of dimensions at BIBeans ?

We are facing a problem that could be a BIBeans problem or could be an OLAP problem, please inform if to change forum:
We are using jdev 903/BIB903 accessing an AW created at Oracle OLAP 9205 with AWM.
All our dimensions were created at OWB 10g and deployed to RDBMS following the general rules below:
DIM X
ID_X - sequence primary key
CD_X - original key from source systems
DS_X, NM_X, and so on - description fields and hierarchy fields related to this record.
i.e.:
SQL> desc dim_rota
Name Null? Type
ID_ROTA NOT NULL NUMBER(6)
CD_EMPRESA NOT NULL NUMBER(2)
CD_FILIAL NOT NULL NUMBER(2)
CD_ROTA NOT NULL VARCHAR2(3)
NM_FILIAL NOT NULL VARCHAR2(40)
NM_ROTA NOT NULL VARCHAR2(30)
CD_SETOR NOT NULL VARCHAR2(1)
ID_SETOR NOT NULL NUMBER(6)
NM_SETOR NOT NULL VARCHAR2(30)
this dimension has 1 hierarchy with 2 levels called SETOR and ROTA.
when we generated the AW using AWM, each field (except ID) is created as a variable dimensioned by DIM_ROTA, as shown below:
->listby dim_rota
35 objects dimensioned by or related to DIM_ROTA in analytic workspace AW1
DIM_ROTA_CD_EMPRESA
DIM_ROTA_CD_FILIAL
DIM_ROTA_CD_ROTA
DIM_ROTA_CD_SETOR
DIM_ROTA_CREATEDBY
DIM_ROTA_FAMILYREL
DIM_ROTA_GID
DIM_ROTA_INHIER
DIM_ROTA_LEVELCOLMAP
DIM_ROTA_LEVELREL
DIM_ROTA_NM_FILIAL
DIM_ROTA_NM_ROTA
DIM_ROTA_NM_SETOR
DIM_ROTA_ORDER
DIM_ROTA_PARENTREL
ID field was concatenated with level name to generate the dimension value - so, for the following relational record:
SQL> select id_rota, cd_rota, nm_rota from dim_rota where ID_ROTA = 233;
ID_ROTA CD_ROTA NM_ROTA
233 A99 A99-Consig. Sup. Setor A
we have at multidimensional side:
->LIMIT DIM_ROTA TO 'ROTA.233'
->rpr dim_rota
DIM_ROTA
ROTA.233
->dsc dim_rota_nm_rota
DEFINE DIM_ROTA_NM_ROTA VARIABLE TEXT <DIM_ROTA DIM_ROTA_HIERLIST ALL_LANGUAGES>
LD IMPLEMENTATION NM_ROTA Attribute for DIM_ROTA Dimension
->rpr down dim_rota w 30 dim_rota_nm_rota
ALL_LANGUAGES: AMERICAN_AMERICA
-------DIM_ROTA_NM_ROTA-------
------DIM_ROTA_HIERLIST-------
DIM_ROTA ROTA
ROTA.233 A99-Consig. Sup. Setor A
here comes our question: how do we show at BIBeans designer/presentations the related descriptive fields and NOT the dimension values themselves?
thanks in advance,
Flavio

There a re two additional attributes that need to be mapped within OWB for each dimension:
Long Description - this is used by the presentation beans and query and calc builder to replace the dimension values with more meaningful/end-user friendly descriptions
Short Descriptions - this can be used where the long description is too long for display purposes. In BI Beans 10g Release 2 (due out soon) you will be able to select between long/short descriptions when using many of the new tags.
These new attributes will be automatically picked up by the OLAP Bridge in OWB and automatically added to the OLAP catalog.
Hope this helps
Business Intelligence Beans Product Management Team
Oracle Corporation

Different Languge/Description Based on Dimension Level

Is it possible at all to have either short or long description be chosen through a function depending on a condition e.g. different level in cube?
Example. If Condition A is met than Long Description is used, Condition B is met than Short Description is used.
Edited by: user7853353 on Aug 14, 2012 2:36 PM

Not through Oracle OLAP alone. This is more of a Reporting issue and can be done via db view or using reporting tool features:
a) Mapping is restricted to a single column. So Long and Short Descriptions need to be mapped to a specific column in source table/view. If your condition is static or related to backend dimension attribute value conditions then you can define the logic in a source view and map both desc attributes to the special column.
define column green_ldesc_else_sdesc in dimension view....
case when product_alias.color = 'GREEN' then product_alias.long_desc else product_alias.short_desc end as green_ldesc_else_sdesc
Use this column to map to short_description/long_description attributes in olap aw dimension mapping.
b) In OBIEE Answers, you can expose the relevant fields in the reporting layer or Presentation layer of rpd and use it in a case statement to implement your logic.
E.g:
CASE WHEN "OLAP Presentation Layer Name"."Product"."Level Name" = 'CLASS' THEN "OLAP Presentation Layer Name"."Product"."Long Description" ELSE "OLAP Presentation Layer Name"."Product"."Short Description" END

Hyperion Dimension & Member Naming Rules.

Hi
what is Hyperion dimension and member naming rules?
Thanks

When naming applications in Essbase, follow these rules:
● For non-Unicode mode applications and databases, use no more than 8 bytes; for Unicodemode applications and databases, use no more than 30 characters.
● Do not use spaces.
● Do not use these special characters:
❍ asterisks
❍ backslashes
❍ brackets
❍ colons
❍ commas
❍ equal signs
❍ greater than signs
❍ less than signs
❍ periods
❍ plus signs
❍ question marks
❍ quotation marks (double and single)
❍ semicolons
❍ slashes
❍ tabs
❍ vertical bars
● For Planning application names in relational database environments, do not use extended characters (except for underscores).
● For aggregate storage databases, do not use DEFAULT, LOG, METADATA, or TEMP as application names.
Also, avoid use some of the reserve words that smartlist uses:
abstract, assert, boolean, break, byte, case, catch, char, class,
const, continue, default, do, double, else, enum, extends, false,
final, finally, float, for, if, goto, implements, import,
instanceof, int, interface, long, native, new, null, private,
protected, public, return, short, static, strictfp, super, switch,
synchronized, this, throw, throws, transient, true, try, void,
volatile, while.
Or not to use dynamic time series (DTS) codes:
❍ H-T-D: History-to-date
❍ Y-T-D: Year-to-date
❍ S-T-D: Season-to-date
❍ P-T-D: Period-to-date
❍ Q-T-D: Quarter-to-date
❍ M-T-D: Month-to-date
❍ W-T-D: Week-to-date
❍ D-T-D: Day-to-date
When naming dimensions, members, and aliases, follow these rules:
● For non-Unicode mode dimensions, members, or aliases, use no more than 80 bytes. For Unicode-mode dimensions, members, or aliases, use no more than 80 characters.
● Distinguish between upper and lower case only if case sensitivity is enabled.
● Do not use HTML tags in member names, dimension names, aliases, and descriptions.
● Do not use quotation marks, brackets, backslashes, or tabs. Brackets are permitted but not recommended in block storage outlines. They cause errors when converting to aggregate storage outlines.
● To begin dimension or member names, do not use these characters:
❍ at signs
❍ backslashes
❍ brackets
❍ commas
❍ dashes, hyphens, or minus signs
❍ equal signs
❍ less than signs
❍ parentheses
❍ periods
❍ plus signs
❍ quotation marks
❍ underscores
❍ vertical bars
● Do not place spaces at the beginning or end of names. Essbase ignores such spaces.
● Do not use forward slashes in member names.
● For time periods in custom calendars, do not use spaces in prefixes.

Use short description on OLAP dimension member in disco for OLAP

Similar Messages

Maybe you are looking for