Dimension values limited to 1000

BI Beans return an error when my dimension values are upper 1000.
Is this an exception of BI Beans?
How can I manage that dimensions that have over 1000 unique values?
Regards,
Xochitl

Searching our bug database, there does seem to be an issue where a list of more than 1000 dimension members is passed to OLAPI to create a SQL query. This does not imply that dimensions cannot be greater than 100 values, only that when parsing a dimension list there should be less than 1000 values in the list. Typically this would in fact be the case, as you would not want to return 1000 dimension members to a user. It is more normal that a user would start at a high or intermediate level and drill down to lower levels of details. Hence, each drill is likely to return a subset of the dimension values which would normally be less than 1000 values. So the workaround is to ensure that each dimension member has less than 1000 children when drilling to the next level down the hierarchy.
The bug reference for this is 2973142 and this issue is fully resolved in 10g. It seems there may be a backport for 9.2.0.4.1 on Solaris 64Bit, Patch 3001943.
No other platform ports are available at this time.
Business Intelligence Beans Product Management Team
Oracle Corporation

Similar Messages

  • 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

  • To change the approval limit for Extended attribute PO Value limits

    Hi,
    We are on SRM 4.0, in PPOMA_BBP for a local purchasing organisation we want to change the approval limit let us say from 100 to 50 but the system is presenting this field as non editable( In stabdard values sub screen)
    In Extended attribute tab in organisation structure after selecting the PO Value limits in SRM 4.0 we see two sub screens
    a) Standard values
    b) Local values
    We want to change the approval limit in standard values sub screen from 1000 to 500, which system is presenting as noneditable.
    Regrds
    Vivek

    Hi
    Refer these links.
    http://help.sap.com/saphelp_srm50/helpdata/en/5a/af5efc85d011d2b42d006094b92d37/frameset.htm
    http://help.sap.com/saphelp_srm50/helpdata/en/8b/4fa9585db211d2b404006094b92d37/content.htm
    http://help.sap.com/saphelp_srm50/helpdata/en/fa/fa7d3cb7f58910e10000000a114084/frameset.htm
    http://help.sap.com/saphelp_srm50/helpdata/en/7f/0fea380bfe6161e10000000a11402f/frameset.htm
    Incase it does not helps, pls let me know.
    Regards
    - Atul

  • Best Practices - Dynamic Ranking, Dimension Values to Return, etc.

    The pinned post says non-technical questions belong on the Business Forum. I can't find an Endeca-specific business forum. If there is one, please tell me where to find it.
    My question is about dynamic ranking and the initial display of only the top N dimension values with a "More..." option to see the rest of them.
    What's the current wisdom on this from a usability point of view? Use it, don't use it? If using it, show how many values initially?
    Or, if not using it, you instead set up a hierarchy of dimensions so that the user never has to look at 50 choices for something?
    This is not a technical question. What is the current wisdom? What are the best practices?
    Thanks!

    Dynamic ranking is a good choice only if all choices cannot be further grouped. In my practice most of the content can be normalized and restricted to a very limited set of options. Dynamic ranking with "more" is an easy way out and seems like a lazy take on content management.

  • Internationalize dimension values

    Hi,
    I need to internationalize dimension values (i.e. month names in a time dimension). I get the dimension values in a QDRMember objet (with dataacces.getMemberQDR), but I don't know how to change the value.
    This is my code:
    DataAccess dataaccess = event.getDataAccess();
    QDR qdr = dataaccess.getMemberQDR(DataDirector.ROW_EDGE,0,k,DataAccess.QDR_WITH_PAGE);
    QDRMember member= qdr.getDimMember(myDim);
    Object oldValue = member.getData();
    member.setData(newValue);
    dataaccess.submitChanges();
    I change the member data (with member.setData), but the old value is displayed instead of the new value.
    Is this correct? Is there any other way to internationalize dimension values?
    Thanks in advanced...

    Searching our bug database, there does seem to be an issue where a list of more than 1000 dimension members is passed to OLAPI to create a SQL query. This does not imply that dimensions cannot be greater than 100 values, only that when parsing a dimension list there should be less than 1000 values in the list. Typically this would in fact be the case, as you would not want to return 1000 dimension members to a user. It is more normal that a user would start at a high or intermediate level and drill down to lower levels of details. Hence, each drill is likely to return a subset of the dimension values which would normally be less than 1000 values. So the workaround is to ensure that each dimension member has less than 1000 children when drilling to the next level down the hierarchy.
    The bug reference for this is 2973142 and this issue is fully resolved in 10g. It seems there may be a backport for 9.2.0.4.1 on Solaris 64Bit, Patch 3001943.
    No other platform ports are available at this time.
    Business Intelligence Beans Product Management Team
    Oracle Corporation

  • 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

  • Own number format Y-Axis (value divided by 1000)

    Hello everybody,
    in WebI I have a quite simple chart.
    In Y-Axis I show the values. How can I divide these values divided by 1000?
    I have found the advanced format menu. But don't know the syntax how to make my own number format for this.
    So for Example my value shown now is: 15.900.000 but it should be 15.900,00
    Any workaround is welcome. But I would prefer not to touch the Universe and stay in WebI.
    best regards Harry

    Hi Harry,
    There is no functionality to create a Custom Format Number and 
    Enhancement Request ADAPT01130144 has been created.
    Regards,
    Sarbhjeet Kaur

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

    Is it possible to sort dimension values in order different from alphabetic. &#1058;&#1086; 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 ???

  • Execution of a planning function with the used dimension values in a crosstab

    Hello,
    would like to execute planning functions within Design Studio but I don't really know how I combine this execution with the used dimension values in a crosstab for the .
    Here the requirement:
    3 Planning functions which should use the same filter (all values of all dimensions in the crosstab) and which should run one after another:
    // open data slice
    PF_1.execute();
    // generate combinitions
    PF_2.execute();
    // close data slice
    PF_3.execute();
    Many thanks in advance.
    Kind regards,
    Tobias

    Hi Arun,
    in general it is not possible to nest planning functions. The inner function would update the data in the plan buffer without the outer function knowing about it. Also the inner function might be on a different aggregation level which would make things very tricky.
    Alternatively you can include ABAP logic into a FOX formula:
    http://help.sap.com/saphelp_nw70/helpdata/en/47/94eb78b6394befe10000000a42189d/frameset.htm
    Or just create the complete logic in one ABAP planning function type.
    Regards,
    Marc
    SAP NetWeaver RIG

  • Using dimension values in calculations of cubes

    hi ,
    I am trying to build a calculated measure using a dimension values like for example
    if a dimension is portfolio
    having values L,X and C values
    and the calculated metrics is like to be calculated only for L and for others it should show 0.
    I created something like this
    sum({[Portfolio Cd].[Portfolio Cd].&[L]},[Measures].[Annual Intr Amt Pl L])
    the problem is that when this metric is drawn to check the values against this dimension it show same values for all the portfolios
    where as it should show 0 for  X and C .
    Can anybody suggest a solution to this .?
    thanks in advance

    Hi,
      Try using a CASE statement in your Calculated measure as shown in below sample
    WITH MEMBER MEasures.SalesAmount
    as
    CASE
    WHEN [Product].[Category].CURRENTMEMBER.MEMBER_CAPTION = "Accessories" THEN SUM([Measures].[Internet Sales Amount])
    ELSE 0
    END
    SELECT [Product].[Category].[Category] ON 1
    ,MEasures.SalesAmount ON 0
    FROM [Adventure Works]
    Best Regards Sorna

  • How to calculate variance between two dimension values

    Hello:
    I have built a cube in Analytical workspace (9.2.0.5) with 3 dimensions. Time, Product & Scenario. I am using BI Beans (thick client) for the presentation layer. What I need is the ability to calculate the variance between two dimension values of same measure. For example, if My scenarios are 'Actual' and 'Budget', when I present the results on the screen for any measure (e.g Total Sales), I should be able to calculate & display the difference between 'Actual' & 'Budget' values of that measure.
    I have more than 7 scenarios and more than 40 measures. It could even be the difference between two product categories. How do I do it either in AW or at BI Beans Level?
    Thank you very much for your help.
    regards
    Suresh

    You want to look at qualified data references in the OLAP DML references. Basically, any data reference may be qualified by specifying a dimension name and value:
    sales(time 'jan92')
    forces the dimension TIME to the member 'jan92', no matter whether 'jan92' is in status or not. The resulting expression is essentially no longer dimensioned by the dimension TIME.

  • PO value limits - approval limits local vs standard

    Hi Experts,
    I have the following problem: for reporting purposes I need to identify an user approval limit.
    Looking in the organizational structure --> extended attributes --> Po value limits I find two values:
    - Standard values - Approval limit;
    - Local values - approval limit.
    What is the difference between them? Which one should I use?
    Other question is, how can I get this information? I am going to table HRP5503 and I can only get the local values.
    Thanks in advance,
    Francisco

    Any help on the above query is appreciated. I am facing the somewhat similar issue. For some of the users standard value field is there and for others its not present under PO value limits(only local value field available). Can someone tell me the root cause for this? Is this role dependent ??

Maybe you are looking for