Dimension value based on cell referece

Hi,
I've a requirement with GLAccount and Trading partner in rows. I need to derive the trading partner based on the property of GLAccount.
Note: This inputschedule is dynamic (ACCOUNTS may change depending upon the selection).
Example: GLAccount is in Cell A and Trading Partner is in Cell B. Following is the formula applied on Trading Partner to derive based on the property of GLAccount.
Issue: Cell reference A1 is static in the formula. It is always refering to the GLAccount of cell A1. Ex: If Account1 Property value is I_NONE and others are T100
Result:
Account1 I_NONE
Account2 I_NONE
Account3 I_NONE
Expected result:
Account1 I_NONE
Account2 T100
Account3 T100
Formula on Trading Partner : Following formula cell reference is not dynamic to refer the corresponding GLAccount cell.
=EPMOlapMemberO(IF(EPMMemberProperty(,A1,"DIMLIST")="","I_NONE","T100"),"[TRADINGPARTNER].[PARENTH1].[I_NONE]","NONE","","000")
I appreciate your help.
Regards,
Saila

Vadim,
Thanks for the reply. I know we can do this functionality by adding a poperty.
Client doesn't want to have a seperate property which needs to be manually maintained for any new account.
I remember we can do it in 7.5 in row key range by applying this kind of formula.
Just wondering if can do it in 10.

Similar Messages

Dynamic setting of the dimension values.

Summary:
How can I programmatically control the dimension values displayed in ‘Selected’ window of ‘Edit worksheet’ wizard. of Oracle BI Discoverer plus for OLAP 10.12.48
My objective is to dynamically set the dimension values for a particular dimension based on some criteria.
Requirement:
1.The user should be able to select one of the pre-defined options.
2.Based on the option selected by the user, the necessary business logics need to be applied and then resets the dimension values. The ‘Selected’ window of ‘Edit Worksheet’ should be refreshed.
3.Based on the option the short description & long description should be changed
Existing Application Implementation:
We already implemented this logic in oracle express 6.3.4 as follows.
1.Radio buttons are provided to select the display option
2.Whenever the option is changed, a program is executed in the Express objects. This program evaluates the option, applies the necessary business logics and displays the dimension values based on the option chosen. View is then refreshed to reflect the new dimension values. Note that this process does not affect the total “available dimension” values. The total number of “available dimension” values remains the same. It just manipulates the values in the ‘Selection’ object.
3.The formula of the short description and long description is modified. This formula checks the option and based on it changes the description
Issues I faced to Implement this logic in Oracle BI Discoverer plus for OLAP 10.1.2.48
1. No provision to add radio buttons, hence were trying to implement the functionality with a dimension.
2. No options available for applying business rule and setting the desired dimension values.
3. No ‘event’ available to refresh the views
How can I achieve this in Oracle 10g discoverer plus for olap 10.1.2.48
Thanks,
Natarajan

I think this is not possible.
When you give this settings while creating the SMARTForm, SMARTForm will generate a FM based on that settings. And it is not possible to change those settings at runtime.
We have some constriants like this for dynamic paradigm in SMARTForm. Like, we can provide shading or Box color for the cell.
Regards,
Naimesh Patel

Value based hierarchy (parent-child)

Does anybody have any experience in modeling a parent-child dimension ( value based hierarchy instead of level based ) in OBIEE?
Swapan.

I've done some work with this, and it hasn't been easy going. There is no built-in ability to form a hierarchy of measure columns, at least nothing that can be predefined as the drill for a fact column. For example: I have 220 details of expense that have an exact arrangement with 5 levels and subtotals. Besides the expense detail there are say 4 dimensions, so the expense detail would be the 5th dimension. I have both arrangements in my rpd: 4D and 5D. They can be used together or separately. The 4D basically has 1000's of measures and there is no relationship between them besides the display arrangement in Answers. The 5D has a 5 column dimension that can drill the expense column from Total_Expense down to the 220 rows of detail expense.

Assigning a Numeric Value in a Cell Based on Text in Another Cell

In advance, thanks for your assistance. I'm trying, in vain, to assign a numeric value in a cell based on text (from a dropdown menu) in another cell. For example, in cell A5 I have a dropdown list that includes the options "blue", "red", "white", and "gold." I want cell C15 to be 2 if A5="blue"; I want C15 to be 0 if A5="red"; I want C15 to be 2 if A5="white"; and, I want C15 to be 1 if A5="gold."

Tippet,
This is a job for LOOKUP.
The expression for the Result cell is: =LOOKUP(A2, Lookup :: A1:A4, Lookup :: B1:B4)
The aux. table contains the matches that you assign for the colors.
Regards,
Jerry

Preaggregation across value based hierarchy dimension in 11g

Hi All,
I have created a cube with 6 dimensions in olap 11g. One of those six dimensions has only one hierarchy which is value based hierarchy. I have chosen level based aggregation as I know at what levels exactly users are going to query. When I was going through the dimensions to choose levels to preaggregate I noticed there were no options available for my value based hierarchy dimension ( I could see "all" option for the same case in 10g) then I tried to look for definitions of underlying objects just to make sure it will preaggregate data across my value based hierarchy dimension.
I found value set corresponding to my value based hierarchy dimension in <CUBE NAME>SOLVEAGGMAP object , which AWM uses to decide which dimension values to preaggregate but if I do rpr on that value set (rp r<CUBE NAME>SOLVE<DIMENSION NAME>_PVSET) it shows NA so my question is can I pre aggregate across value based hierarchy dimension in olap 11g?
Olap Version: 11.2.0.1
AWM version: 11.2.0.1
Thanks

Even if you know exactly which levels your users will query, percent based precompute (e.g. 30%) may still be faster in practice because queries are returned using 'sparse looping' instead of 'dense looping'. This was the single biggest performance advantage of 11g over 10g.
But if you still want to use level based precompute, then you should look at the XML template for the cube (as saved by AWM, for example). In it you should find something called PrecomputeCondition. This defines the set of members that are precomputed. Here is an example I just created using the GLOBAL schema
<PrecomputeCondition>
<![CDATA[
"TIME" LEVELS ("TIME"."MONTH", "TIME".CALENDAR_QUARTER, "TIME".CALENDAR_YEAR),
CHANNEL LEVELS (CHANNEL.TOTAL_CHANNEL, CHANNEL.CHANNEL),
CUSTOMER LEVELS (CUSTOMER.MARKET_SEGMENT, CUSTOMER.REGION, CUSTOMER.SHIP_TO),
PRODUCT LEVELS (PRODUCT.CLASS, PRODUCT.FAMILY, PRODUCT.ITEM)]]>
</PrecomputeCondition>The PrecomputeCondition is also visible through the USER_CUBES view.
SELECT PRECOMPUTE_CONDITION
FROM USER_CUBES
WHERE CUBE_NAME = 'MY_CUBE';You can hand modify this condition in the XML to specify an alternative 'non level based' precompute condition for any dimension. For example, if you define an attribute named 'SHOULD_PRECOMPUTE' on your PRODUCT dimension that is 1 for members to be precomputed and 0 for all others, then you can change the condition as follows.
<PrecomputeCondition>
<![CDATA[
"TIME" LEVELS ("TIME"."MONTH", "TIME".CALENDAR_QUARTER, "TIME".CALENDAR_YEAR),
CHANNEL LEVELS (CHANNEL.TOTAL_CHANNEL, CHANNEL.CHANNEL),
CUSTOMER LEVELS (CUSTOMER.MARKET_SEGMENT, CUSTOMER.REGION, CUSTOMER.SHIP_TO),
PRODUCT WHERE PRODUCT.SHOULD_PRECOMPUTE = 1]]>
</PrecomputeCondition>If you recreate the cube from the XML with this condition, then the PVSET valueset you discovered should contain all dimension members for which the attribute value is 1.   This gives you complete control over what is precomputed.   Note that AWM doesn't support this form of condition, so it won't show up if you go to the Precompute tab, but it is valid for the server. The PL/SQL below will modify the PrecomputeCondition (for the cube named MYCUBE) without going through AWM.
begin
dbms_cube.import_xml(q'!
<Metadata
Version="1.3"
MinimumDatabaseVersion="11.2.0.2">
<Cube Name="MY_CUBE">
    <Organization>
      <AWCubeOrganization>
        <PrecomputeCondition>
          <![CDATA[
           "TIME" LEVELS ("TIME"."MONTH","TIME".CALENDAR_QUARTER, "TIME".CALENDAR_YEAR),
           CHANNEL LEVELS (CHANNEL.TOTAL_CHANNEL,CHANNEL.CHANNEL),
           CUSTOMER LEVELS (CUSTOMER.MARKET_SEGMENT,CUSTOMER.REGION,CUSTOMER.SHIP_TO),
           PRODUCT WHERE PRODUCT.SHOULD_PRECOMPUTE = 1]]>
        </PrecomputeCondition>
      </AWCubeOrganization>
    </Organization>
</Cube>
</Metadata>
end;
/

Custom itemRenderer component based on cell value: error 1009

I'm working on an item renderer for a dataGrid that has different states depending on the cell and row values.
The cell value is a toggle (true or null), and sets whether content should be shown in the cell or not
The row properties determine what is shown when the cell value is true.
The dataGrid dataProvider is populated based on user id input.
I created the itemRenderer as a custom actionscript component, closely following this example:
360Flex Sample: Implementing IDropInListItemRenderer to create a reusable itemRenderer
However, my component results in Error #1009 (Cannot access a property or method of a null object reference) when a user id is submitted.
package components
     import mx.containers.VBox;
     import mx.controls.*;     import mx.controls.dataGridClasses.DataGridListData;
     import mx.controls.listClasses.BaseListData;
     import mx.core.*;
     public class toggleCellRenderer extends VBox
          public function ToggleCellRenderer()
          {super();}
          private var _listData:BaseListData;
               private var cellState:String;
               private var cellIcon:Image;
               private var imagePath:String;
               private var imageHeight:int;
               private var qty:String = data.qtyPerTime;
               private var typ:String = data.type;
          public function get listData():BaseListData
               {return _listData;}
          public function set listData(value:BaseListData):void
               {_listData = value;}
          override public function set data(value:Object):void {
               super.data = value;
               if (value != null)
               //errors on next line: Error #1009: Cannot access a property or method of a null object reference.
               {cellState = value[DataGridListData(_listData).dataField]}
          override protected function createChildren():void {
               removeAllChildren();
               if(cellState=='true'){
                    cellIcon = new Image();
                    addChild(cellIcon);
               //there is another state here that adds another child...
          //next overrides commitProperties()...
There are no errors if I don't use an itemRenderer--the cells correctly toggle between "true" and empty when clicked.
I also tried a simple itemRenderer component that disregards the cell value and shows in image based off row data--this works fine without errors or crashing. But I need to tie it to the cell value!
I have very limited experience programming, in Flex or any other language. Any help would be appreciated.

Your assumption that the xml file either loads with "true" or nothing is right.
After modifying the code to the following, I don't get the error, but it's still not reading the cell value correctly.
package components
     import mx.containers.VBox;
     import mx.controls.*;
     import mx.controls.dataGridClasses.DataGridListData;
     import mx.controls.listClasses.BaseListData;
     import mx.core.*;
     public class toggleCellRenderer extends VBox
          public function ToggleCellRenderer()
           super();
          private var _listData:BaseListData;
          private var cellState:Boolean;
          private var cellIcon:Image;
          private var imagePath:String;
          private var imageHeight:int;
          private var qty:String;
          private var typ:String;
           public function get listData():BaseListData
             return _listData;
          override public function set data(value:Object):void {
               cellState = false;
               if (listData && listData is DataGridListData && DataGridListData(listData).dataField != null){
                   super.data = value;
                   if (value[DataGridListData(this.listData).dataField] == "true"){
                       cellState = true;
          override protected function createChildren():void {
               removeAllChildren();
               if(cellState==true){
                    cellIcon = new Image();
                    addChild(cellIcon);
               //there is another state here that adds another child...
          //next overrides commitProperties()...
- didn't set the value of qty or typ in the variable declarations (error 1009 by this too--I removed this before but wanted to point out in case its useful)
- added back in the get listData() function so I could use the listData
- changed the null check
All cells are still returning cellState = false when some are set to true, even if I comment out [if (value[DataGridListData(this.listData).dataField] == "true")] and just have it look for non-null data. That shouldn't make a difference anyway, but it confirms that all cells are returning null value.
Swapping out the first if statement in set data with different variables results in the following:
[if (listData != null)] all cells return null (cellState=false for all)
both [if (value != null)] and [if (DataGridListData != null)] results in error 1009 on a line following the if, so I assume they return non-null values.
All rows have data, just not all fields in all rows, so shouldn't listData be non-null? Could it be that the xml file hasn't fully loaded before the itemRenderer kicks in?
I also realized I had removed the item renderer from many of the columns for testing, and since some columns are hidden by default only one column in the view was using the itemRenderer--hence the single alert per row I was worried about earlier.
Thanks for your help so far.

Has anyone setup BIEE with OLAP 10g using value-based dimension hierarchies

I just wanted to know if it is possible to setup BIEE with 10g using multple dimensions containing multiple value-based hierarchies?
I know this involves using the OLAP Cube View Generator to create an sql view of the cube data.
I have been able to get this to work with nine dimensions all containing a single value-based hierarchy bar one which had four value-based hierarchies. But as soon as i have multiple hierarchies in multiple dimensions it seems to go haywire and i cannot get the sql view to return correct data.
I thought i would post on the BI side to see if anyone has been successful in creating a BIEE setup like this?

The simple answer to your question,
how robust is the 11g materialised views with multiple value-based hierarchies...?is that materialized views are not supported on top of value-based hierarchies in 11g. The reason is that it is not possible to write a reasonable SQL statement that aggregates a fact over a value-based hierarchy. Such a SQL statement is necessary if we want to create a rewritable MV on top of the cube.
But I suspect this is not what you are really asking. If you are trying to set up OBIEE on top of the cube in 10g using the view generator, then you will probably want to use the "ET VIEWS" that are generated automatically in 11g. These are generated whether or not you enable materialized views on top of your cube. I am not aware of any issues with the generated value-based hierarchy view support in 11g. Members may be shared between value hierarchies and you will not need to generate or modify limit maps.

DimensionmemberList with value-based dimension

Hi,
I'm unable to use a DimensionMemberList with a value-based dimension. It works fine with level-based, however when I select a value-based dimension and hierarchy in the wizard and click on "Next" an Error pop-up appears with no message and I have to click on "Cancel" to get out of the wizard.
Has anyone encountered this behavior?

Hi Ankita,
As per my Understanding the VP column did't map to any LTS .
When ever u have multiple LTS in Dim Admin tool won't create Dimension Hierarchy manually we need to create that.
Follow these steps to resolve your Problem...
1) give the simple join in physical layer for that two tables.
2) Create one Dim table in to BMM layer drag all columns in 2 tables in to BMM Dim table so u can able to see all the columns is mapped in to their respective LTS.
3) Now u can create hierarchy manually step by step.Like Grand total Parent ----> Child level .
4) If u have any fact table joined with these dimension in physical layer give the logical joins in BMM layer and set the content levels properly.
Let me know need any detail clarification.
Thanks,
Satya

Value based dimension hierarchy in OBIEE 10G

Hi,
I am a user of OBIEE10G. I have to create a value based dimension hierarchy in my RPD. My hierarchy should be such that when I click on any VP Name, the respective employees working under him/her should be shown. But my columns of VP Name and Employee_Name are present in separate dimensions. Hence when I drag the column of VP Name to Employee dimension and then create the dimension hierarchy, I get an error of illegal cross join .
Is value based hierarchy possible in 10G?
Pls reply.
Thanks
Ankita
Edited by: 848789 on Sep 28, 2011 8:40 PM

Hi Ankita,
As per my Understanding the VP column did't map to any LTS .
When ever u have multiple LTS in Dim Admin tool won't create Dimension Hierarchy manually we need to create that.
Follow these steps to resolve your Problem...
1) give the simple join in physical layer for that two tables.
2) Create one Dim table in to BMM layer drag all columns in 2 tables in to BMM Dim table so u can able to see all the columns is mapped in to their respective LTS.
3) Now u can create hierarchy manually step by step.Like Grand total Parent ----> Child level .
4) If u have any fact table joined with these dimension in physical layer give the logical joins in BMM layer and set the content levels properly.
Let me know need any detail clarification.
Thanks,
Satya

Multiple Value Based hierarchies per MOLAP dimension

Hi,
a) Is it possible to have multiple value based heirarchies in a single MOLAP dimension in OWB and deployed to analytical workspace ?
Are there any pitfalls, that we need to be aware of...
b) Can we have a mix of Value and level based heirarchies per dimension ?
Thanks in advance,
Chakri

Hi Chakri
Yes, you can have multiple value based hierarchies and also a mix of value/level based.
Cheers
David

Value based hierarchies and Period dimension should only contain 2 monthl

Hi,
Can anyone tell me what is value based hierarchies. And also can anyone let me know to filter the records in AWm because in Period dimension should only contain 2 monthly values (Oct. 2008 ( 200810) and Sep. 2008 ( 200809)) it is urgent.
Thanks
vel

The following definition of a value hierarchy comes from the OLAP Developers guide
"A hierarchy defined only by the parent-child relationships among dimension members. The dimension members at a particular distance from the base level do not form a meaningful group for analysis, so the levels are not named. For example, an employee dimension might have a parent-child relation that identifies each employee's supervisor. However, levels that group together first-, second-, and third-level supervisors and so forth may not be meaningful for analysis."
Typically this means that the source table has two columns, VALUE and PARENT, where PARENT has a (logical) foreign key relationship to VALUE. An example may be EMPLOYEE, MANAGER, where MANAGERs are also EMPLOYEEs.
The simplest way to restrict the values loaded into the AW is to define a SQL view over the source table with an appropriate WHERE condition. You then use AWM to map the dimension to your new view. E.g.
CREATE OR REPLACE VIEW RESTRICTED_TIME AS
SELECT *
FROM TIME
WHERE MONTH IN (200810, 200809)

Value-based hierarchy on ROLAP dimension. Is this possible and how?

Value-based hierarchy on ROLAP dimension. Is this possible and how?
If yes, what tool I have to use. Any simple examples?

Based on my experience of OWB10gR2 the option to create a "Value Based" hierarchy is only enabled if you create an AW based OLAP model. If you want to create a ROLAP model then I do not think this is possible.
Question is why create a ROLAP model when you could get better performance and more powerful analytical features by using a multidimensional model within an analytic workspace.
Keith

Pre-compute for Value based dimensions in AWM 10g

hi,
I created a compressed partitioned MOLAP cube in OWB 10.2.0.3 based on some value based dimensions.
I selected the hierarchy in value based dimensions for pre-compute, but it did display the hierarchy in OWB.
I deployed the cube into Analytical workspace AWM 10g(10.2.0.3A).It created PRECOMPUTE(NA) in the relation statement for the value based dimensions.
Is it that value based dimensions cannot be pre-computed (at the heirarchy) in AWM 10g ?
Regards
Chakri

For reference, I believe this error was due to the deletion and recreation of a standard form AW formula without full restoration of the formula's PROPERTY values. AWXML (and hence 10g OWB/AWM) will not work correctly if you remove PROPERTY values from objects.

New calculated member based on existing measure and a dimension value

Hi
I’m trying to create a new calculated member in my cube based on an existing measure and a dimension value.
I can do it easily in DSW but I want to do it as a Calculated Member in Calculations tab from my cube.
I have a dimension called Product in which one attribute is UOM (unit of measure) and a measure called Quantity. The relationship with the fact table is “Regular”.
For each product we have a unit of measure and an associated quantity measure:
Product Name
UOM     Quantity
Product 1
          Km
         50
Product 2
          Kg
         60
Product 3
          Kw
          25
Product 4              L
15
Product 5              T
         1.5
Total                                     151.5
The calculated member I want to create is “Kw” and has to contain the value from Quantity measure when Product.UOM is “kW” and should look like this:
Product Name
UOM     Quantity
Kw
Product 1
          Km
         50
Product 2
          Kg
         60
Product 3
          Kw
          25
25
Product 4              L
             15
Product 5              T
         1.5
Total                                     151.5
25
So far I tried using the MDX with “IIF” or “Case” but with no results.
What statement I should use in this case?
Thank you.

Hi Cees,
Thank you for your answer.
I never used yet the “Scope” statement and yet it’s an elegant solution.
I use it as in your example:
CREATE
MEMBER CURRENTCUBE.[Measures].[Kw]
AS NULL,
FORMAT_STRING =
VISIBLE = 1 ,
ASSOCIATED_MEASURE_GROUP =
'TR Other';
Scope [Measures].[Kw];
Scope [Product].[UOM].[kW];
This = [Measures].[Quantity];
End
Scope;
End
Scope;
…and the calculations are solid…with one exception: when I took out UOM from the query there are no more any resuts:
Product Name    Quantity    Kw
Total
It’s only working
if using UOM in the query.
I also thought that a
tulpe might be another solution as:
([Measures].[Quantity],[Product].[UOM].&[kW])
On this last one I’ve got the expected results with one exception: when I use UOM in the query all the other UOM values are listed each one of them
having the [Kw] measure calculation value.
Product Name    UOM     Quantity    Kw
Product 1              Km
         50
Product 2              Kg
         60
Product 3              Km
          25            25
Product 3              Kg
           25            25
Product 3              Kw
          25            25
Product 3              L
25            25
Product 3              T
25
  25
Product 4              L
            15
Product 5              T
         1.5
Total                                     151.5
25
…and without UOM in the query I have what I’m expected:
Product Name    Quantity
Kw
Product 1              50
Product 2              60
Product 3               25
25
Product 4
15
Product 5
1.5
Total                       151.5
25
Maybe we can work together to find a solution.
Thank you,
Oks

Can we precompute a value based dimension ?

Hi,
I do not know how to precompute/summarize a value based dimension in AWM 10g.
One of my value based dimension in AWM 10 g (10.2.0.3A) showed pre-compute already done , but the aggmap of the cube did not show any precompute clause in relation statement for this dimension.
1) Is AWM 10.2.0.3 A taking care of this internally ? How can i verify this ?
2) If not, how can i set pre-compute for a value based dimension by hand ?
(provided the precompute clause remains even after cube is maintained).
Regards
Chakri

Hi All,
Thanks for your replies.
Let me give you a background . Iam creating a cube over some value based dimensions in OWB (10.2.0.3) and then deploying them to AW .Iam loading the cube and dimensions using OWB mappings.
Any other changes or objects not possible through OWB are done directly in AWM (10.2.0.3A)
Stuart,
Yes this a duplicate thread i posted for almost the same problem statement.
David,
1st option - precompute valueset is defaulting to all members.
a) Are you talking about the valueset <DIMENSION>_PARENTREL(<VSET>)
I did an rpr on <VSET> , it just returned the hierarchy name. This vset would be there for any dimension ( even without precompute) and would just return the default heirarchy
b) or Are you referring to PRECOMPUTE(<VSET>).
As mentioned, this VSET is not coming up in the aggmap.
2nd option - Modify the XML template with the PreComputeClause to say Expressiontype="INCLUDE" instead of "EXCLUDE". You can then delete the cube and recreate it from your XML.
The Model view of AWM (10.2.0.3A) was showing the 'All' box as checked for this value based dimension, but the aggmap did not show any PRECOMPUTE clause. Also, when i checked the XML of the cube (in which the dimension is used), there was no pre-compute clause for only this dimension. This might be due to my AWM version iam using.What is your AWM version ?
How do i check if pre-compute is working ?
Here is the info about my cube :
Dimensions : TIME (Levels: Year,Quarter,Month) ,LOB,CUST and FIN
All dimension except TIME are value based.
Settings : compressed, partitioned along TIME.MONTH
I want to fully precompute TIME and LOB .
CUST and FIN should not be precomputed.
Thanks
Chakri

Dimension value based on cell referece

Similar Messages

Maybe you are looking for