Retreival of dimension of the attribute on spreadhsheet

Similar Questions

• 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

• Dimension of the attribute on the same dimension

  Is it possible to associate an attribute of the same dimension in OSB?

  The example that I'm talking about is:

  I have an Employee dimension

  I want to put an attribute used for 'Manager '.

  The Associate Manager is also the Employee dimension.

  I don't want to reproduce the Employee dimension unnecessarily if I can just do an attribute.

  I'm using EPMA well and on the 11.1.2.2.500 version.

  Thanks in advance.

  No, you can't do it.  You must create a dimension attribute that contains all employees who are also responsible.

  The Essbase view you are not increasing the size of the cube by adding the dimension of 'Manager' (as you probably know) attribute.

• Dimension of the attribute

  Hello!
  
  Is it possible to share the same size of attribute with more than a basic dimension?
  
  Thank you!
  Victor

  "A dimension attribute can be associated with the single dimension of Basic."

  Might be useful to have a read of http://docs.oracle.com/cd/E17236_01/epm.1112/esb_dbag/dattrib.html

  See you soon

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

• Setting security using the dimensions of the attribute & 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

• 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

• 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.

• Planning of the attributes to dates 11.1.2.2 and start and end in a cell

  Hello. In planning 11.1.2.2., can I use dimensions of the attribute, like I would in a cube Essbase BSO?

  Also can I enter a start date and an end date entry in two different account (for example, start_date and end_date) members?

  Thank you

  
  

  Hello

  Yes, I think you can use it.

  And you can change the account date data type member. Then use these accounts in the planning Web form. Form will give you the opportunity to select the Date...

  VB...

• Inability to deploy the size of the attribute for the first time in EPMA 11.1.2.1

  In EPMA planning an application I manually added the local dimension of the attribute with few members and associated with a local custom dimension. During the deployment of the application, I get an error: "an Exception occurred in the Application deployment.: Hyperion Essbase has failed with an error code: 1060114. I know that according the Essbase error code cannot create the attribute dimension.
  
  Please advise on the solution.
  
  Thank you
  Yuri

  Might be useful to have a read of the following document on the Oracle Support - "Planning Refresh fails with the error"calculations of attribute dimension cannot be created"[ID 1408609.1].

  See you soon

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

• construction of the attribute

  Hi gurus,
  
  We can build attributes in many ways
  
  
  trying to optimize the size of the renovation:
  
  even if we use defferred restructuring, if the size of the attribute is in btw scripts restructuring takes place. I want to just what optimize.
  
  background:
  case: we can build separately from attributes in a single charge rule and we can associate them in another rule of load.
  Case2: we build the attribute at the time to associate
  
  
  
  question:
  
  I can use the CAS2, but the question is whether I can load the alias to an attribute dimension at the time to link the members of a diension attribute it to the standard dimension?
  
  
  any suggestion?
  
  Thank you
  Dolar

  To minimize the restructuring, you can put all your dimension building in a single import dimensions statement by separating them with commas. in this way you restructure only once.
  I have never tried to add an alias to the dimension of the attribute when linking (in older versions, you might not even an alias for an attribute if I remember correctly) but I guess you can't do.

• 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.

• Time Dimension type to different values in the attributes - Bug or feature?

  Not sure if this is a bug or a feature.
  
  But if there is a time dimension hierarchies. You have the option of specifying different values for member attributes in different hierarchies.
  
  For example.
  
  A hierarchy has MIN_ID for its members and uses MIN_END_DATE for its end_date
  
  Hierarchy B has MIN_ID for its members and uses SESS_END_DATE for its end_date
  
  According to this message and a comment by David Greenfield:
  
  Gender issue when several mappings for different hierarchies
  
  "You try to map the same attribute, SORT, on different columns in two hierarchies? In other words, what do you expect the same Member to have different values for the attribute in the two different hierarchies? If so, then this is a problem because a member must have the same value for the attribute independently of the hierarchy. »
  
  Unlike a dimension of the user, a time dimension seems to allow this and it seems to work as expected. Behavior in this case is the difference between a user and the time dimension?

  Your description of the structure of the dimension is very clear, but I have a question about system requirements. When you say you want to the time running from 17:00 to 16:59, do you mean that the calculation must spand day? for example "5:00 PM: Jan 1, 2012" to "4:59 PM: 2 Jan 2012".» If so, then this you is impossible by making a loop only the dimension of time-seconds. Or do you really mean it must wrap around the same day. for example "5:00 PM: Jan 1, 2012" at "11:59 PM: 1 Jan 2012", then again to "00:00 AM: 1 Jan 2012" to "4:59 PM: 1 Jan 2012"?»»»

  If you want the calculation for the period of days, then I think you need to spend TIME on the DATE dimension level. You can leave some MINUTES in the second dimension, which can be a dimension of standard user. You must then two levels of the DAY (with different members) in the date dimension - each with a different set of the child. You can assign the TIME_SPAN to the TIME level 1.

• DisplayImageFile() does not change the dimensions of the image control

  Hello

  I put in an image with DisplayImageFile() control image + assigning to the attribute of control ATTR_FIT_MODE = VAL_SIZE_TO_IMAGE. The image size is larger, then the size of the control and I want the control to resize to the size of the image.

  It works fine except when I ask the dimensions of the control with GetCtrlAttribute (panel, control, ATTR_HEIGHT, & height), I get the original size (before calling DisplayImageFile())...

  It seems I missed something basic...

  Environment: LAB Windows CVI 2012, Windows 7

  Thanks in advance

  Ramy

  I don't know if you still experience this problem or not, but I came across this discussion now and wanted to point out that this could happen if your picture controls if it is covered by another control or is it hidden altogether (and there might be other similar situations that I can't think of right now).

  When this happens, the CVI runtime can pull the image directly on the image. Instead, he plans an asynchronous action that will redraw this section of the Panel from the back to the front (if it's just overlapped, not hidden). It is only in the later action that the image is applied to the control, and it is only then that the control is resized to fit the image. This may seem immediate to the casual observer, but, because it is asynchronous, you can't try to get new size immediately after calling DisplayImageFile, because the image is not yet in control at that moment.

  Ironically, this occurs only if the control has already been set to the image size at the time you call DisplayImageFile. If this isn't the case, then the new size is applied when you later change the mode made programmatically. Whereas if the adjustment mode has been already updated the image size, trying to programmatically set the same value of the image size has no effect and nothing happens then.

  If this is what is happening, one way around this would be to call ProcessDrawEvents or ProcessSystemEvents immediately after the call to DisplayImageFile. Unless the control or Panel has been hidden way explicit, which will require the drawing action will take place at this time, and you should then be able to get the new size of control at any time after that.

  Luis

• Empty drop down list - planning - Web Forms - Dimensions in the axis of the Page

  Hello

  The drop-down menu that appears when you click on one of the dimension in the axis of the web forms page appears empty. The problem is unique to the single dimension when used with Alias Web form that a single application a plan type and a single instance. The special dimension has more than 1,500 members of level zero and has a seven-digit code and description of words 2 to 5 in the alias.

  I tried to rebuild the shape / LCM for instance different but nothing has worked. I think that this could be attributed to the problem in the JavaScript for menu drop-down. But I have no knowledge on javascripts so abstained.

  Feel free to ask all the questions and thanks in advance.

  Thank you

  RJ

  Finally with the help of the Oracle, I found the problem. The problem was some control characters in the names of aliases which are not visible in the user interface. Somehow these characters in the name of the alias has been added during the transfer files on the remote server or the load control metadata.

  changed ODI reloaded code execution on the target data store, metadata, and the problem is solved.

  See you soon.