Randomly sorting dimension values in 11g

Hi, I know how (for a text dimension) to easily allow users to sort in ascending or descending order. I also know how to enforce a "default" sort order in the logical layer using a numerical column, etc.
But I have Brio users that are used to picking up and drag / drop dimension values into whatever random order they want. Is there any way to mimick this in OBIEE (without asking the to create a hidden column where they put a huge case statement to figure out the order, etc.)? I know this wasn't possible in 10g, just wanted to know if there's some way to do it in 11g (doesn't seem to be, but maybe I'm missing something)
Thanks!
Scott

No, that's moving entire dimensions around on a pivot table - not sorting members within a dimension.
Let's say I have a time dimension with values Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec. For whatever reason, a user wants a table / pivot / whatever to show the dimension members in this order: Jul, Apr, Oct, Feb. Those values aren't sorted either alphabetically or by date order. So how would a user get this to happen?
Thanks,
Scott

Similar Messages

  • Sorting dimension values

    Is it possibe to sort dimension values in hierarchy in order diffirent from alphabetic?

    When you define a dimension you should notice on the first tab an option to set the type of dimension. The options are: User and Time. For a Time dimension you need to select type Time and this will automatically sort the members into calendar order for you. However, your source table does need to contain some additional metadata such as Time span (number of days for each time period; week=7, month=28 or29 or 30 or 31 Quarter=90 or 91 and Year = 365 or 366) and End Date for each time period. These two additional attributes are used for both sorting and to enable the time based calculations such as:
    Year To Date
    Prior Period
    Future Period
    Moving Total
    Moving Max
    Moving Min
    Does that help?
    Keith Laker
    Oracle EMEA Consulting
    OLAP Blog: http://oracleOLAP.blogspot.com/
    OLAP Wiki: http://wiki.oracle.com/page/Oracle+OLAP+Option
    DM Blog: http://oracledmt.blogspot.com/
    OWB Blog : http://blogs.oracle.com/warehousebuilder/
    OWB Wiki : http://wiki.oracle.com/page/Oracle+Warehouse+Builder
    DW on OTN : http://www.oracle.com/technology/products/bi/db/11g/index.html

  • Is it possible to sort dimension values in order different from alphabetic?

    Is it possible to sort dimension values in order different from alphabetic. То use this sorting in BI Beans. In 10g r2 with awm 10.2.0.2. I try to add attribute like it was show in this forum, but nothing changes.

    Could be usefull if you use java AW api... here's the java code I'm using to create the sort_order attribute
    Dimension myDim = yourAW.findDimension("DIMNAME");
    Attribute myAttr = myDim.createAttribute();
    myAttr.setName("freename");
    myAttr.setClassification("DEFAULT_ORDER");
    myAttr.setIsDefaultOrder(true); // TO NOT FORGET
    myAttr.setDataType("INTEGER");
    myAttr.Create(AWConnection);
    globalAW.Commit(AWConnection);
    It creates a variable - integer - that defines the default order of the dim values. I'm viewing it with AWM and BIBeans. The order is respected with Level-based and Value-based hierarchy but my hierarchies are really simple and unique for all the dimensions.
    BUT !!!! Be carefull, if you don't have any hierarchy in your dimension, you must have at least one level - the default NONE level. Otherwise, it won't work ???

  • Awm 11g - sorting dimension

    Hi,
    I've searched in the forum and found this thread
    Sorting Dimension Values in 11g AWM
    but it doesn't answer my question.
    I have a Dimension (that happens to be a time dimension not defined as such) defined as a time dimension with values like JAN07, FEV07, MAR07, and when listing the members they appear as FEV07, JAN07, MAR07.
    I created an attribute with integers that match the desired order (assigned them to the lowest hierarchy level) and selected it for "sort attribute".
    In the dimension's property window, we can define a "sort attribute". This however does not change any of the results.
    Even checking the actual data in the created view, shows a view column named dim_order. This does not reflect the defined "sort attribute".
    Anyone has any idea how to workaround this? The mentioned workaround in the thread works (I believe) for a time dimension. And for other dimensions?
    Thank you for your time.
    Best Regards,
    João Pinela.
    Edited by: Pinela on Sep 12, 2011 4:10 PM
    Edited by: Pinela on Sep 12, 2011 8:07 PM
    Edited by: Pinela on Sep 12, 2011 8:33 PM

    There were a number of problems in this area.
    Release 10g had the ability to order dimensions based on a custom attribute, but this feature did not make it to the rewritten 11.1 code. This missing code was added for release 11.2, but there were a few bugs. Here are some that I know about
    Bug 11694245 Custom sort order doesn't work for initial dimension compile
    This was an odd case where the custom order was ignored the first time a dimension was built, but was used for subsequent builds. It did not happen consistently and appears to have been fixed as of release 11.2.0.2.
    Bug 11694194 OLAP API queries don't respect dimension custom order
    This was a display issue in the AWM hierarchy viewer. The order had been applied, and you could see the correct values through the HIER_ORDER column in the hierarchy view, but AWM still showed dimensions listed alphabetically. I expect this is what you have hit. It has been fixed in the newly release 11.2.0.2 OLAP B Patch (patch number [url http://aru.us.oracle.com:8080/ARU/ViewCheckin/process_form?bug=12813874]12813874 )

  • Is there possibility to add dimension value into hierarchy using dml or spl

    1 Is there possibility to add dimension value into hierarchy using dml or spl?
    If such possibility exists how to do that.
    2 Is it possible to sort dimension values inside one branch of the hierarchy?

    What version of OLAP are you using and how did you create your AW (e.g., AWM)?
    Assuming that you're used either AWM or the Java API for AWs in 10g, there isn't an OLAP DML for adding a dimension member to a dimension (and have all the meta data kept in sync); you must load dimension members using AWM the Java API for AWs.
    So, make your changes in the the dimension table and process that table.
    For sorting, you can add a sort attribute to the dimension. Add the sort attribute to the model, indicate that it's used for sorting, add the sort attribute to your dimension table and maintain the dimension.

  • How to Sort Dimension in Pivot Table via Order Column which is changing like Factual values

    Hi,
    Recently in of our product offerings we got stuck on this following question:
    How to Sort Dimension based on the Order Value which Keeps Changing with Factual Values??
    We have a data source laid out as (example)
    In the above the “Order” columns are changing per
    Company/(DimensionA) for DimesnsionB.
    Instead what we want is: (But only if we can get the following result without putting the “Order” Column in the “Values” Section. 
    If there are any configurations that we can make to our power pivot model for the similar data set so that the
    DimesnionB in this case can be sorted by the Order column, would be greatly helpful to us. 
    Sample File:
    http://tms.managility.com.au/query_example.xlsx
    Thanks
    Amol 

    Hi Amol,
    According to your description, you need to sort dimension members in Pivot Table via order column, and you don't want the order column show on the Pivot table, right?
    Based on my research, we can sort the data on the Pivot table based on one of the columns in that table, and we cannot sort the data based on the columns that not existed on the Pivot table. So in your scenario, to achieve your requirement, you can
    add the column to pivot table and hide it.
    https://support.office.com/en-gb/article/Sort-data-in-a-PivotTable-or-a-PivotChart-report-49efc50a-c8d9-4d34-a254-632794ff1e6e
    Regards,
    Charlie Liao
    TechNet Community Support

  • Limiting Dimension Values to Dimension Values used on Specfic Day

    If I have a dimension with thousands of values. And within my cube, on a given day only a few of those dimension values are actually used. How can I limit the scope of my dimension values to be only the values that exist on that given day?

    You can check OLAP DML Programs chapter (chapter 4 in 11g doc set) in Oracle OLAP DML Reference document. It's part of the standard olap documentation.
    Also regd the parameterization question:
    The code as pasted below is already parameterized. By parameterization, do you mean something other than passing value from front-end to the back-end (database)?
    Typically the front end report/query will refer to a series of time dimension values -- say, 16-Jul-2012 to 22-Jul-2012 for time. The report would reference a measure with a formula referring to an olap dml program. This program is called repeatedly for each cell and the appropriate dimension member values are passed as input to the program.
    argument _tm time  <-- implies that the program accepts time dimension value (corresponding to a single cell) as input and works off the same in its calculation.
    limit time to _tm   <-- usually this is done within a tempstat context to make such changes temporary for calculation w/o affecting external time dimension status. This allows the program to set the context of calculation to current cell (say 18-Jul-2012)
    "hence what follows for the rest of the program acts on the restricted status in order to calculate the current cell's value corresponding to time dimension value = 18-Jul-2012.
    That's also why the same program can return a different value for each cell (different return value for 18-Jul-2012 compared to return value for 21-Jul-2012) although it's being looped over dimension status implicitly.
    HTH
    Shankar

  • Partial Update - Unknown Dimension Value ID

    Hello Old Endeca Friends,
    I am getting a lot of these sorts of errors when I perform a partial update:
    ERROR     04/25/13 16:56:21.115 UTC (1366908981115)     DGRAPH     {dgraph,update}     Record change references unknown dimension value id 4294484500     [recspec=`UPI:100224148']
    I am using MDEX 6.4 and PS 6.1.3. The dimension value ids in question seem to be in the autogen_dimensions.xml, but the dgraph doesn't seem to recognize to know about them. Why?
    Any further insight would be appreciated. "Just run a baseline" is not a good answer, I need to do partials every hour throughout the day.

    Thanks for the input, everyone.
    It looks like my issue was that my state file had a set of updated dimensions but my dgraph did not.
    I had a baseline extract with properties X, Y and Z (let's say) and I was adding in new dimensions A and B. I moved my state files from my test environment to my production environment with entries on dimensions A and B. I started getting partial data for dimensions A and B and processing it. However, my dgraph knew nothing about A and B. So, although forge created the dim vals fine and the state files were modified appropriately, my dim val updates and adds on my dgraph failed because my dgraph had never processed a baseline extract with dimensions A and B.
    Once I ran a baseline with dimensions A and B, partial updates went fine and have now processed dozens without issue.
    Unfortunately, I only get baseline data once a week, so it took me a bit of time to realize what was going on.

  • Sorting Measure Value Hierarchically

    Hi All,
    I am writing a java application for the OLAP browsing using oracle OLAP API. I am finding hard time in sorting the measure values. I am able to sort the measure values by a single dimension, for example sorting the unitCost by the product hierarchically. . But i can't find any way to sort the measure by two dimension for example soring unitCost by product and region hierarchically. Can somebody provide me the sample code or the link for doing this? Any help would be greatly appriciated
    Regards
    shankar

    Hi Shankar,
    I don't understand your question. In OLAP, we commonly order dimension values, not measure values. We often order dimension values BY measure values. Could you provide a brief example of the output you are trying to create?
    Have you looked at the documentation? Chapter 7 of the "OLAP Developer's Guide to the OLAP API" has some good sorting examples.
    Geof

  • Sort Dimension descending using developer tool

    Hi,
    i have a alpha-numeric property in endeca, we need to sort it descending, can we achieve this using developer studio.
    i was able to sort it ascending order, not seeing any field in developer studio to sort descending order
    Thanks,
    Tijo

    Hi Mathew,
    If you want to sort dimension in descending order one way to do this is add following in "appname.refinement_config.xml"
    <REFINEMENTS NAME="price" SORT_TYPE="NUMERIC" SORT_ORDER="DESC">
    <STATS NUM_RECORDS="FALSE"/>
    </REFINEMENTS>
    This way we get dimension values in descending order.
    Please Note Whenever you have the pipeline in the developer studio this mapping gets removed, so you need to add it again before you run the baseline.
    HTH
    MS

  • How to limit  dimensions values of querybuilder

    Hi,
    I want to learn how to limit dimension value in query builder. i want, the user who run the querybuilder can not see a dimension value which i do not want to display.
    For example,
    The time dimension has "2000" and "2001" values as default which is defined in database. Normally when i run the querybuilder for create new presentation or calculation, In the dimensions panel of the querybuilder display all values of each of dimension. The user can select values which she/he want from that list.
    But i want to limit values which the user can see in the dimensions panel of the querybuilder. for this time dimension example, i want to hide "2001" value from the user. How can i do it. if there is any sample code, please share.
    Thank you very much for your helps.
    ilknur

    Thanks Thomas, excellent suggestions as always.
    If anybody wants more information regarding Thomas' suggestions please refer to
    Oracle9i OLAP Developer's Guide to the OLAP DML for the AW Permit command.
    In sumamry: To create permission programs, you define two programs with the names permit_read and permit_write. In these programs, you can specify PERMIT commands that grant or restrict access to individual workspace objects. In addition, you write these programs as user-defined functions that return a Boolean value, and the return value indicates to Oracle OLAP whether or not the user has the right to attach the workspace.
    For relational security there is an excellent tutorial on the database pages of OTN, follow this link:
    http://otn.oracle.com/obe/start/index.html
    then follow the links for Oracle9i Database Release 9.2.0.2 - Security - Creating Label-based Access Control. This module describes how to use Oracle Label Security to setup security based on label policies
    These security layers should be transparent to the OLAP metadata layer, therefore, once you have implemented your chosen security method your BI Beans application will only need to connect with the appropriate user to inherit the security layer. For more information see the Security section of the BI Beans Help:
    http://otn.oracle.com/bibeans/903/help/
    BI Beans product Management Team
    Oracle Corporation

  • Few dimension values used in FACT tables.

    Hello all,
    We are trying to know if somebody faced this issue earlier. We have dimension tables containing 5 million records, but the fact table uses hardly 30k of these dimension values. The fact table contains 350 million records, so is there any way to improve the performance of the query in such a scenario, where hardly 20% of dimension values are actually used by the FACT tables.
    Thanks and Regards,
    Upendra

    nilanjan chatterjee wrote:
    Hi,
    >
    > The data for the parent members should be available in the SQL tables.
    > For example, 2011.TOTAL is parent member. You should not have any data for this member in your database. If it is there, it might have come somehow (may be an import). But this is not right. You might want to remove these records. But be sure that you dont delete the records for the base level members.
    >
    > Hope this helps.
    I guess you meant should not, right ?

  • Dimension values display order and record details

    Hi All,
    I have explicitly ordered my dimension values to be in a logical order instead of alphabetical. Ex: Small, Medium, Large. This works great in the navigation tree but when I view a specific record and it  has those 3 dimvals they are listed in alphabetical order.
    Is there a when doing a record query to ask Endeca to respect the same display order as in the nav query?
    Thanks,
    Luc

    We are used to add two dummy records in each dimension.
    We add the following data:
    We use '-1' (surr-key) for Invalids and '-2' for Unknown.
    Easy way to populate these dimensions is to add a script together with all objects when you release new functionality. Beware you use the same descriptions.
    Even better is to think of a more general solution (more easy to maintain) and store these values in a support table. In such a table you will be able to add more columns to get more details per row. Use this reference table when you load youre dimension. Also you will find the opportunity to add more error handling cases. Especially when you add the dimension in this support table.
    Regards
    Moscowic

  • 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

  • Sort variable values in selection box in BEx web report.

    Hello friends,
    In my BEx web report I have cal/month selection. When I do dropdown to select values it starts with 01/1960 and I have to click 10 times to get to 01/2006, 02/2006 and so forth.
    Is there a way to sort these values so I can get most current cal/month in first list?
    Thanks in advance.
    Regards,
    BJ

    I would consider changing the read mode for the dropdown box.  Are all of those dates actually relevant?  Check out the properties of the dropdown box in WAD. 
    Thanks,
    Jeff

Maybe you are looking for