Questions on the Dimension attribute

1. when I look at the "Attribute" terminology on the link, it says "an attribute provides additional descriptive information about a dimension and/or specific breast of this dimension members... ", but on AWM help, he says"attributes provide information that is typically no additives on the individual dimension members. "I am confused with the word"additional"and"no additive. They have opposite meanings?

2. it is a good example in the explanation of "Attribute" terminology on the link, for example, he said "in a database of representative of the shoes, you can use a shoe color attribute to select all boots, sneakers and slippers that share the same color. By adding these attributes of types to your data model professional users can answer questions such as: what colors were the most popular in the dresses of the women in the summer 2005? How this compares with the previous summer? ». What happens if we define color as a level, not an attribute in the hierarchy under the product level? What happens if we define color as a dimension, not an attribute? I have to say that the purpose of setting the attribute intrigues me a lot.

3. There is an option when creating/updating an attribute: Index. AWM help, he said "Select this option to improve the performance of the queries based on the attributes.". What is a 'attribute-based queries? And when we can use?

4. There is an option when creating/updating an attribute: attribute values are multilingual. If I check it "Long Description" attribute, for example, there are only LONG_DESCRIPTION (AMERICAN) and LONG_DESCRIPTION (ENGLISH) could be mapping. Is there a way to make more than two languages? At the same time, there was still a LONG_DESCRIPTION column in the view of dimension and hierarchy. What language data will be exposed in the view, LONG_DESCRIPTION (AMERICAN) or LONG_DESCRIPTION (ENGLISH)?

5. to AWM help, he said "You need to map all the attributes of their data sources.". In fact even if I don't maps all attributes, the size of maintenance process always work well. So why he uses the word 'MUST' here?


Thank you
Satine

Satine,

As you have discovered, AW physical objects are not in the object view. To see the list of objects in an AW you use OLAP DML, which you can make by using the call of PL/SQL dbms_aw.execute. I'm going to assume that your AW is called GLOBAL in this example, but obviously you need to change this to your own.

-Activate output Server (or you don't see any results)
Set serverout on

-Attach the aw
dbms_aw.execute exec ("' aw attach global")

-the list of all the objects of the AW
exec ('listnames') dbms_aw.execute

-This example lists only things like ' PRODUCT % '.
dbms_aw.execute exec (' like ListeNoms ' PRODUCT %''))

-This example lists only dimension of objects
exec ("ListeNoms size") dbms_aw.execute

Determination of size "on the disc" objects AW is not directly supported by the OLAP DML language to my knowledge, but the following query may work for you. Once more, replace 'global' with the name of your AW. (More precisely, to replace the table named ' aw$ global "with your aw table.)

define lines110 500 pages
Col aw_object for a70

Select objname |': ' | aw_object partName, round (sum (dbms_lob.getlength ('AWLOB')) / 1024,3) KB
AW$ global
where extnum = 0
Objname group, partname
order by objname, partname

David

Tags: Business Intelligence

Similar Questions

  • No data is recovered to add the Dimension attribute in Excel

    Hi Experts,

    IAM facing the question below when retrieving values for an attribute dimension in excel, add in.

    We have three types of regime, namely AAAA/BBBB/CCCC, which have been refreshed to Essbase. BENAMER will get data on YYYY revenues and employee data of the CCBC through an XREF function.

    While recovery data on revenues for the attribute ATTRI1 to the size of the merge attribute member, if we collect of AAAA, he has no problem while when pull us the BENAMER, at the business unit level parent values extracted successfully, but when we drill down to a profit of level 0 Center then values are not recovered. Attributes are associated with level 0 of the dimension of the base members. The above works fine when extract us data from a data form by using the connection of planning.

    Any help is appreciated on the above.

    Thank you.

    So your fragmented senior level members are dynamically calculated?

    I wonder if it is interacting with the order of the attribute size calc and not rewarding as you wish.

    The SER60 has a lot of good things about the attributes: http://download.oracle.com/docs/cd/E10530_01/doc/epm.931/html_esb_dbag/dattrib.htm

    You can think of to senior level members in the function stored/never share and see if you get the result you're looking for. If the function is sparse, I should think long and seriously if I really want these members to be calculated dynamically due to the impact on retrieval performance.

    Kind regards

    Cameron Lackpour

  • Add the dimension attribute

    Hello

    Anyone know how to add the attribute dimension on Hyperion Planning?

    Thanks in advance.

    Kind regards
    Stephan

    Hello

    If you have more than 1 size of the attribute associated with a dimension, then when you reverse the planning application in the dimension you will get a column for every dimension of the attribute.

    So if you have a TestAttrib1, TestAttrib2 associated with the entity, reverse dimension model.

    Look in the entity of the inverse model dimension, you will see the TestAttrib1 and TestAttrib2 columns.

    Now in your workload file, you can load into the columns in your source file.

    Ok?

    See you soon

    John
    http://John-Goodwin.blogspot.com/

  • question on the [ILO] attribute definition for the products in the file MXI (bug?)

    Hello

    When I set the attribute [bit] of a product in xmi (set to 64) of the file and create the package, Adobe extension manager CS6 refuses to install on a 64-bit system (saying :) because it is a 64-bit extension!

    I tried in two different environments (Vista and 8-64 / CS6) with the same result!

    Is this a bug (known?) or I do something wrong?

    <product version="8" maxversion="8" primary="true" name="InDesign" platform="win" bit="64"/>

    Any idea would be appreciated, thx, mim

    The attribute bits, the version of Win32 or Win64 of the product for which this extension can be installed. It has nothing to do with the Windows operating system architecture. Since InDesign CS6 has 32-bit version of Lara, you don't have to specify as "64" bit, even if you use 64-bit Windows.

    From CC, InDesign has 32-bit and 64-bit version on Windows. But they have the name of different product, "InDesign" and "InDesign64" respectively. So if you only want to create 64-bit InDesign CC extension, you can specify:

    The 'primary' attribute is no longer used on the CC. The name of the product of InDesign on Mac is still 'InDesign', 'dilated' and 'bit' attributes are not necessary to specify in this case.

  • Question about the Dimension b110

    I have this message moves to the right forum:

    I tried to start my Dell Dimension B110 and I get a blue screen with this message:

    STOP: 0X0000008E (0XC0000005, EB6, 0XF94A57CA 0X00000000 0XBF803)

    Win32k.sys - address BF803eb6 base at BF800000, date stamp 47e0e106

    I tried to boot in safe mode and tried to restore with no luck.  So what is happening with this computer? Any help would be greatly appreciated.

    Message edited by tomahawk264 on 03/10/2008 11:56

  • Question on the % NOTFOUND attribute slider

    Here is my PL/SQL:

    OPEN FOR C_original_demo
    ' SELECT pro_flags, spo_flags, proemp_flags, spoemp_flags
    OF test.original_demo
    WHERE id_number = "< any id > ';
    EXTRACTION c_original_demo
    IN v_pro_flags, v_spo_flags, v_proemp_flags, v_spoemp_flags;

    IF c_original_demo % NOTFOUND THEN
    v_pro_flags: = '0000000000000000000000000';
    v_spo_flags: = '0000000000000000000000000';
    v_proemp_flags: = '00000000000000000000';
    v_spoemp_flags: = '00000000000000000000';
    END IF;

    When the code runs, it bombs on an ID that doesn't have a record in the original_demo table, if his tent of extracting any data in my variables. But which is not what the % NOTFOUND logic is supposed to prevent? I use it wrong?

    Thanks for the help,
    ivalum21

    Hello

    I think that must be reported

    ID_NUMBER NUMBER(some value) 
    

    Thank you

  • ATTRPARENT dimension of the text attribute to several levels of construction with a rules file

    Hello

    My first post here.

    I'm trying to create the dimension generation rule to create a dimension of the multilevel text attribute and then combine with the basic dimension.

    So far, it is difficult.

    With regard to my experience:

    -J' have a relatively basic understanding of the rules of charge both with regard to the data loads and define the updates - I find this quite confusing area and the documentation does not help that much

    -J' only started using dimensions attribute, so for me it's a new concept, but we are already quite useful in certain applications

    -J' I try to automate the process of construction of dimension attribute, and then associating attributes with the basic dimension

    I use the following documentation as a guide:

    Building size attribute and associate attributes

    http://docs.Oracle.com/CD/E12825_01/EPM.111/esb_dbag/frameset.htm?dotdimb.htm

    and / or

    Work with the attribute multi-level Dimensions

    http://docs.Oracle.com/CD/E26232_01/doc.11122/esb_dbag/frameset.htm?ch21s06s05.html

    (essentially the same source in both cases)

    The ultimate goal is to replicate one of our existing recently created attribute dimensions of a cube to another.

    I built a few versions of the required flat file and the corresponding rules file, but none worked.

    I tend to get the following validation error message:

    This field is defined as an ATTRPARENT. The following column must be a field of association attribute type.

    As I got stuck so I gave to the current actual attributes and moved on to experimenting with the sample / base cube.

    I built a flat file that is supposed to create a new dimension of text attribute named ABC with two attributes level structure:

    ABC

    A

    AA

    AB

    B

    BA

    BB

    and associate it with the dimension of the product in the following way

    200-10 AA

    200-20 AB

    200-30 BA

    200-40 BB

    The flat file looks like this:

    "AA"      "A"         "200-10"               "A"         "AA"      "200"

    "AB"      "A"         "200-20"               "A"         "AB"      "200"

    "AB"      "B"         "200-30"               "B"         "AB"      "200"

    "BB"       "B"         "200-40"               "B"         "BB"       "200"

    and the rule file has 6 matching columns with titles as follows:

    Level0, LEVEL1 ABC, ABC Level0, product ATTRPARENT0, ABC ABC0, LEVEL1 product, product

    all agree with what the documentation says.

    The first 2 columns are intended to define and create the dimension of the attribute, while the 4 next make association...

    I couldn't the above rules file to validate.

    The same validation error message appeared as previously:

    This field is defined as an ATTRPARENT. The following column must be a field of association attribute type.

    However when I tried to actually update the outline of the mistakes of dimbuild.err file has been created which gives some additional clues:

    \\ATTRPARENT column 4 must precede a numeric or datetime column attribute association

    Now... Finally the interesting part...

    Back to the documentation...

    I don't mind if the size of the attribute is generated and then those associated with step or in two separate steps.

    I try to do both tasks in one step only because that's what the documentation seems to suggest attributes at several levels.

    First of all I read:

    Note:

    If you work with a multilevel dimension attribute or with a dimension of the attribute of the digital type, Boolean, or date, the rules file requires an additional field. See working with Dimensions of the multilevel attribute.

    Yes, I work with a dimension of the multilevel attribute so the above statement applies (I guess) and so I'm going to see what works with several levels attribute Dimensions has to say.

    Then, I read:

    When an attribute is part of a digital multi-level, Boolean, or dimension attribute date, the source data must include columns for all generations or the size of the attribute levels.

    Fair enough... so I do what they say... my attribute dimension is at several levels, so I can assume that the statement above applies...

    So, I build my rule in accordance with the guidelines above.

    And then, as we have already mentioned, I get the error message about ATTRPARENT and when I read, it turns out that ATTRBPAREN cannot be used for numeric or date attribute dimensions !

    I'm totally confused at this point.

    What about the attribute text multi-level dimensions ?

    They are several levels but they are NOT numeric or date those!

    The documentation does not seem to tell what to do in this case...

    Anyone build something like that?

    What is the thing that I'm missing?

    What about

    I'm glad that you got to work. I tested and that is to create the dimension attribute and associate it with the rule of the load.

    You could ignore the construction size manually. Remove the attribute dimension. The rule1 go for the Dimension settings under the definition of Dimension tab. Then right-click on the product and change the properties. On the attribute tab, add 'Test' or whatever you want to call the attribute, and assign the text type. He adds the attribute and associate it with the basic dimension when it create the hierarchy. Note that the rules could actually be reversed where you create members of level 0 and then more later to create the hierarchy.  Of course you must pass the size of the attribute association to the other rule

  • ESBase Studio question - how to set up the dim attribute?

    I installed Essbase Studio, but has not found a place to create the dimensions of the attribute and rather than associate the dimension attributes to standard dimension? Please notify. Any expert can tell me? JohnGoodwin? GlennS_2? CL?

    Published by: user2571802 on January 9, 2010 20:10

    Hello

    Create a hierarchy as usual and add your columns for your dimension attribute, overview make sure your hierarchy is correct.
    Change the hierarchy you want to map the dimension attributes to add the mapping of attributes to the hierarchy. (then member of attribute maps to the dimension member)
    (don't forget to do a relational ship between members of dimension for the attribute members in your source)
    There is an example of adding the mapping to a hierarchy on page 126 of the user's guide of the Regional (multistring with Dimensions of the attribute hierarchy) service
    In the dimension of some model > essbase properties > click the attribute member, and then select the attribute settings. (this will not appear until you have successfully added the mapping of the attributes in the hierarchy to set up)

    See you soon

    John
    http://John-Goodwin.blogspot.com/

  • sum of a column of the dimension

    Hello
    If my requirement of report said we get SUM (Treasury of column) of the dimension table then can we do it? I have undersatnd that function must be used for measures in fact table. What are we doing to reach the sum of the columns in the dimension table? The report tries to compare the sum (column done) sum (dimension columns). Earlier when I used the sum on the column dimension function he gave no precise results. Please advice.

    Unfortunately, I could not explain this matter in a simple unique way, without seeing exactly the report and generated queries

    In the simple table, OBIEE is supposed to do something like this (I assume you put the attribute of the year, money and a measure of 'real')

    "+ select +".
    + Year +.
    + Sum (cash) +.
    + Sum (fact measure) +.

    + Of +.
    + time_dim_table, +.
    + cash_dim_table, +.
    + fact_table +.

    + where (joins).
    + Group by year +.
    "

    You can check if the physical demand looks like this, in order to understand the results.

    In the PivotTable, it's totally different.
    Your physical demand will be no aggregation: so what will:

    "+ select +".
    + Year +.
    + Cash +.
    + Sum (fact measure) +.

    + Of +.
    + time_dim_table, +.
    + cash_dim_table, +.
    + fact_table +.

    + where (joins).
    + Group by year, money +.
    "

    But, OBIEE then apply logic calculatiosn to display goods results in the PivotTable.
    Who can explain the different results.

    But don't forget that told you right: avoid the aggregation on the dimension attributes. You can sometimes has good results (ex: using the pivot, or other), but it's not really the best way to make your reports. If you often need a "sum (cash"), create a new table of logic made with the 'picture of cash' (even if it is also a dimension table).

  • Setting security using the dimensions of the attribute &amp; UDA

    Hi all

    We have a fairly unique requirement which we are struggling to implement searching around the planning documentation, forums, etc., but I hope that someone here has come across and successfully implemented.

    Ideally, we would like to the next of Essbase filter to implement in our planning application:

    WRITING: (@IDES (CostCentre) AND @ATTRIBUTE (Active), @ATTRIBUTE (Enabled), (@UDA(Account,Open) AND @UDA (Account, ExternalAcct))
    NONE: @IDES (Account), @IDES (CostCentre), @IDES (AnalysisCode)

    We cannot find a way to implement this filter in planning as there doesn't seem to be an easy way to assign access to a combination of 2\more dimensions.

    My questions are the following:
    1 can be implemented this definition of the filter in the planning?
    2. If Yes, what is the best way to apply this filter?

    Thanks to a bouquet.
    JBM

    Hello

    It looks like a cell-level security, and it is not supported by planning.

    Thank you
    JM

  • dimension of the hierarchical attribute with Essbase Studio

    Hello world

    I need to load the product dimension that is organized in a parent-child relational table like this:
    (parent_code, member_code, member_alias, mark, consolidation, formula)

    Each product has a mark and I need to load brand as a dimension of the attribute. The thing is the brand isn't flat, but it has its own hierarchy. For the brand, I have another relational table, where the data are organized parent-child like this:
    (brand_parent, brand_child, brand_alias).

    I do this load with Essbase Studio but I know is not how to create the Product hierarchy in the cube schema in order to load the parent-child hierarchical attributes. Documentation and tutorials only show examples of dishes attributes. I thought of these two ways, but do not know if will work:

    hierarchy of case 1) product like this:

    Parent_code
    Member_code
    Brand_parent
    Brand_child
    Member_code

    hierarchy of case 2) product like this:

    Parent_code
    Member_code
    Brand_parent
    Brand
    Member_code

    Someone had to do this? How did you do?
    Any help will be much appreciated.

    Thank you
    Daniela

    Hello Daniela,
    Please see the following post. One of my colleagues ran into the same issue, and his post was answered in the post below.
    ESBase Studio question - how to set up the dim attribute?

    Thank you
    Daniel
    http://dvepm.com

  • Member add dimension to the existing attribute problem

    Hi - I currently have a dimension of the attribute and the type is numeric. I did not build this BSO cube, but I need to add a member in there "0000". I am trying to add this in environmental assessments, when I first add a child and type 0000, it automatically removes the 3,000 and leaves me with only 0. When I manually in the properties to add back the 000 and then check the outline, it will give me an error message "0: setting of the format name attribute must match attrirbute member of level 0. Other members of this dimension is also 4 digits.

    The same problem happens when I try to add the 01/01/1900 to my date attribute dimension. This attribute is of type Date. When I try to check the outline, I get an error message 'the attribute member name does not match the setting for the attribute type. Date attribute should be specified in the format xx-xx-yyyy ".

    I've never added members to the dimensions of the before attribute, I thought it would be like adding a new Member to any other regular dimensions.

    These two questions make sense to me. If you set an attribute like digital, I think it translated 0000 to 0. After all, it is a numeric value. You say that your other values are 4 digits. Do you mean like 1234 or 0012. I expect the former to work, but not the last.

    In regards to your date, I know more casual it is, but there is a minimum date allowed. For some reason a while in 1970 glue in my heard (of course, I was stuck in the 1970s for years). I thinl you also cannot have a longer date the 2043.

  • The Dimension members based on the attribute filtering

    Hi all

    In Hyperion Planning 11.1.2.2 classic Application, is there a way by which we can display values of members on data based on the attribute form; for example

    If we have the dimension entity having the list of universities and corresponding attribute category have values as medical, General and engineering.

    I want only members of entities on form having value attribute equal to the General category.

    Check this box: Selection of members

    See you soon... !!

    Rahul S.

  • Formula of writing on the Dimension of the attribute with the data type Date

    Hi all

    I have a Dimension of the employee who has Joining_Date as a Dimension attribute. I loaded the data in the format "yyyy-mm-dd".
    I have a scenario to calculate not joins in a month. For this I created a member like joinies and I tried to get the Date in the beam using @ATTRIBUTEVAL (Joining_Date) to perform the calculation on it. But when I see the essbase/planning addin data get different value.

    Ex: For an employee ' 05/10/2006' is the attribute value, but he excel make me '1147219200 '.


    Please, help us address this scenario.


    Thank you and best regards,
    Combot

    Published by: 923621 on April 3, 2013 03:57

    It is not a different value. That's how Essbase stores date. This is the number of milliseconds after January 1, 1970

    Use datepart with attributeval for the year, month, day of the week

    Concerning

    Celvin

    http://www.orahyplabs.com

    Please check the answers as useful/correct as appropriate

  • Question related to the JSTL attributes

    Hello

    I am new to JSP and JSTL and needed to define the var attribute < C:SET / > tag to some time of execution attribute value but var does not support the rtexpr. Is there a reason why var and scope of the JSTL attribute do not appear to accept the value of rtexpr? Also if anyonce can suggest the solution so it would be great.

    Thank you
    Niraj Rouault

    Hi Andrew,

    I believe that by means of "rtexpr" expression of the run time. From my understanding of your question, you have a variable in JSP to assign a value to an expression that must be evaluated at run time. In this case, EL can be used. Please see the link below:

    http://docs.Oracle.com/javaee/5/tutorial/doc/bnahq.html

    Also note that you phrase your question thoroughly rather than use the abbreviated expression. This would help to get a quick and accurate response.

    Kind regards
    Amit

Maybe you are looking for