Unable to create attribute dimension in Essbase Studio
Hi All,
As per the process,I am create an Attribute for an dimension as below
Hierarchy
Family(gen1)
SKU(gen2)
Attribute1(gen1)
SKU(gen2)
Attribute2(gen2)
SKU(gen3)
Here the issue i am unable to create an 2nd attribute parallel to first on i mean attributes are not creating as sliblings.
Please advise
Thanks,
SatyaB
I think I understand what you are asking. I think your example is something like
Products
---Colas
-----Coke
-----Diet coke
Bottle (attribute)
---Coke
Can (attribute)
---Diet coke
This is not the way attributes work, you would have a column in your soruce perhaps called container_type that has the relationship
Container_type
Sku
So the rows would look like
Sku----Family-----container_type----other properties
coke...Colas........Bottle............XXXXXX
Diet Code..Colas...Can.............XXXXXXX
This could be in your primary table or a joined table
Similar Messages
-
How to create an attribute dimension in Essbase Studio?
I cannot figure out how to create an attribute dimension using Essbase Studio. The online help states that I need to "Find the Attribute settings grouping in the center" of the member properties dialog box. I suspect that I'm having a problem figuring this out because I don't have the attribute dimension properly defined in the relational data source or in the mini-schema. I've tried creating a table with no key relationship to the other tables and with no logical joins defined, but that doesn't seem to help. Any ideas?
so in the 11.1.1 version you would click on the member name in the hierarchy you added to the Essbase model and in the center pane of the general tab should be the attributes settings section.
If I had a dimension called stores wth two groupings unser it region and store_type, I would click on store_type and add the attribute info -
Hierarchical attribute dimension with Essbase Studio
Hi everybody,
I need to load product dimension which is organized in a relational parent-child table like this:
(parent_code, member_code, member_alias, brand, consolidation, formula)
Every product has a brand and I need to load brand as attribute dimension. The thing is Brand is not flat but it has its own hierarchy. For Brand I have another relational table where data is organized parent-child like this:
(brand_parent, brand_child, brand_alias).
I need to do this load with Essbase Studio but I do not known how to create the Product hierarchy in cube schema in order to load the hierarchical parent-child attributes. Documentation and tutorials only show examples for flat attributes. I thought of these two ways but not sure if will work:
case 1) Product hierarchy like this:
Parent_code
Member_code
Brand_parent
Brand_child
Member_code
case 2) Product hierarchy like this:
Parent_code
Member_code
Brand_parent
Brand
Member_code
Has anyone had to this? How did you do it?
Any help will be very appreciate.
Thank you,
DanielaI've not tried it, but you should be able to build the attribute hierarchy within the product hierarchy. sort of like
Parent Code
---member Code
Brand Parent
---Brand Code
-----Member Code.
A couple of things
1. Remember to create the self join between Parent_code and Member code
2. IF this does not work, I suggest creating either a user defined table or a view that just gives you distinct brand parent and Brand Code. Join the Brand Code to the product table on brand_code = brand code and use that table to build that hierarchy. -
Unable to create Measures dimension in proper relationshipin Essbase Studio
I am planning to build measure hierarchy in Essbase studio with TBCSample(SQL Server 2005) which is came by default with Essbase Studio installation
I built the hierarchy with parent child relationship.
However the hierarchies is not coming in the proper order
Generally Sales,COGS should come under “Margin ” and it should be under “Profit”
Eg: Profit
Margin
Sales
COGS
However it is showing differently in “Preview” mode.
Profit
Margin
Margin
Sales
COGS
When I deployed the cube I got the below errors because of the duplicate members
The error file is located on the server at: E:\Hyperion\products\Essbase\EssbaseStudio\Server\.\ess_japihome\data\TBCSampl.TBCSampl_03-29-11_23-16-00.err
\\Record #6 - Member name (Measures) already used
Measures Inventory
\\Record #7 - Member name (Measures) already used
Measures Profit
\\Record #8 - Member name (Measures) already used
Measures Ratios
\\Record #9 - Member name (Margin) already used
Profit Margin
\\Record #14 - Member name (Total Expenses) already used
Total Expenses Marketing
\\Record #15 - Member name (Total Expenses) already used
Total Expenses Misc
\\Record #16 - Member name (Total Expenses) already used
Total Expenses Payroll
Please let me know how to resolve this issue
Database: SQL Server 2005
EPM Version : 11.1.1.3
Thanks,
SatyaBopen the minischema and in the graphic go to your measures table. highlight either the parent or child member and right click. select create join. In the screen that comes up, selet the other column from the same table. It will create the join. You wnat an inner join. You can also click on the member and drag and drop the join line to the child member to create the join
-
Create Attribute Dimension by rule file
Hi,
How can we create an attribute dimension and associtae members of sparse dimension with members of attribute dimension by using a rule file?
There is no option of 'Attribute' under dimension type in dimension propertites.
Plz help on it.
Atul KFirst you have to create a standard dimension and made the storage setting sparse.
Then, you can create another dimension of type Attribute and associate it with the standard sparse dimension.
Then you can write rule files for attributes.
If you are assigning the attribute dimension MKT_TYPE to the standard dimension MARKET and the generation 4 is the last.
The typical rule file is like this:
Gen4, MARKET MKT_TYPE 4, MARKET
New york Big Market
Washington Small Market -
Create Attribute Dimension - Numeric
Hi,
11.1.2.2 - ASO
Have a Customer dimension about 500K leaf level members. Want to create a numeric attribute dimension named 'Cust_ID' and the values would be 1 to 500K or so. I create the dim, manually create two sample leaf level children ( 1 and 2). I keep getting this error:
1: Attribute level 0 member name must match attribute format name setting
I can't figure out where to change this. On base dim or attrib dim. I have never created a numeric attribute dim before.
ThanksI just forced save and re-opened and then verified and it verified. I knew something weird like that was happening. Looks like a bug.
-
Unable to create logical dimension in bmm layer
Hi all,
I am not able to create a logical dimension hierarchy in the bmm layer of the rpd.
when I right click on the table I am not able to find the create logical dimension option in the popup window.
could you please help me out in this?
In the logical table we have data from sql statement also.
Thanks!Create Dimensions is only available if the selected logical table is a dimension table (defined by 1:N logical joins) and no dimension has been associated with this table.
To create a dimension automatically, the Administration Tool examines the logical
table sources and the column mappings in those sources and uses the joins between physical tables
in the logical table sources to determine logical levels and level keys.
Hope you have defined the Logical join in BMM before looking for this option. If joins are not defined, this option won't come.
Refer http://download.oracle.com/docs/cd/E10415_01/doc/bi.1013/b31770.pdf
Page 133, Creating Dimensions Automatically
Hope its useful -
Hi All,
I have requirement to build a product dimension where I am thinking to opt for attribute dimension.
I my current outline we have Products
Product manfc
Nike
small
medium
large
Rbk
small
medium
large
Ex large
ETC
Here Sizes small, medium are Level 0.
Now we want Sizes not to be concatenated in the same dimension. So we thought of opting Attribute dimension. Is our approach correct??? Please AdviceAs Glenn pointed out, if a product can be more than one size then a single attribute dimension will not work.
But if you are dealing with a small number of sizes then you can get away with making an attribute dimension for each size. Then you can assign any, none or all to each product as you need.
Product (associated attributes: SizeA, SizeB, SizeC, SizeD)
--Nike (attibutes: Small, Medium, Large)
--Rbk (attributes: Small, Medium, Large, Extra Large)
SizeA (attribute)
--Small
SizeB (attribute)
--Medium
SizeC (attribute)
--Large
SizeD (attribute)
--Extra Large -
Space is attribute Dimension in Essbase
Hi -
I had a similar problem for data in the past. I created a thread and then I ended up using MAXL.
Now I have similar situation. I have an Essbase Dimension Employee which has Attribute Employee Status. When I try to extract Metadata out of essbase with its attributes the process failing because of the space in the field Employee Status. Has anyone faced this issue. Whats the work around for this issueI am answering my own question.
I am able to fix the issue by using double quote in the name. Syntax is Employee."Employee Status" -
Create Attribute Dimension via the JAVA api
<p>Does anyone know how to create an attribute dimenions via theJava API ?</p><p> </p><p>I can set the dimension type to attribute via<b>setAttributeDimensionDataType</b> but I don't know how toassociate the attr. dimension with a sparse, normal dimension(which is mandatory).</p><p> </p><p> </p>
Hi Marco,<BR><BR>It is in the IEssCubeOutline interface. Here is sample code from the CreateOutline.java sample code that ships with EDS:<BR><BR> IEssCubeOutline otl = ... <BR><BR> IEssDimension product = otl.findDimension("Product");<BR> otl.associateAttributeDimension(product, caffeinated);<BR><BR>Tim<BR>
-
I have a Cost Center dimension with 10,500 members. I want to quickly tag these cost centers with 2 attributes. 1st is the first 3 characters of the string(8 in total) as company and the 4th position as dept. How can I do this in an automated way since the dimesnion is already large and I dont want to have to tag them individually
Open a new load rule, associate the outline, go to Options|Dimension Build Settings|Dimension Build Settings Tab and set the Cost Center dimension build method to 'level', I bieleve you will need to check Allow Property Changes, then click OK.<br><br>Go to File|Open Data File, and open your datafile. You may have to change the delimeter option in the load rule depending on how you saved the data file (to get the columns to populate the columns in the load rule editor).<br><br>Go to View|Dimension Building Fields.<br><br>Go To Field|Properties|Dimension Building Properties tab, and set the field properties..<br><br>The first column will be the Level 0 for Cost Center. The second column will be the attribute. <br><br>Validate and save the load rule.<br><br>Open the outline, and click File|Update Outline. Specify the load rule and the data file, then OK. ***verify the outline before saving it, and of course do all of this in a development copy of the database first**.<br><br><br>
-
Hi!
I tried to create some Attributes to my Entities in the RON, but it doesn't work.
I always got that following ERROR-Message:
RME:2105; Oracle error occurred...
ORA-06550: line 9, column 13:
PLS-00302: compoment 'FORMAT' must be declared
ORA-06550: line 9, column 3:
Thanks
UweI Have tried this several times and never did it throw any error to me.
Could you tell me what version of designer are you using and whether the format field in the property paletter while creating an attribute is a mandatory or not?
Regards
Sat -
Essbase Studio Alternate Hierarchy Creation error
Hi All,
I'm using Essbase Studio to create an alternate hierarchy. I have a dim which has shared members and I'm getting the following error msg during cube deployment:
1. Record #1- Member Name (SKU) already used i.e. the member for which I m trying to create shared member
I m following the same procedure mentioned in the user guide i.e.
Step1: create a copy of the dimension element that you want to designate as a shared member(Renamed SKU_copy with SKU_Diet). By making a copy, the binding expression for this element is the same as the original dimension element (SKU_Diet).
Step2: when you create the second hierarchy in the chain, which is the alternate hierarchy, add a user-defined membas the parent and add the new dimension element (SKU_Diet) as the child, which will be the shared member.
Even I m able to see the shared members (SKU_Diet) under user defined member "Diet" under the preview window (both by key binding and caption binding) as wel..
But I m unable to see the shared members in EAS console after deploying the cube from Essbase Studio to EAS Console.
I m not able to understand what I m missing exactly,.and suggest me other ways as well for creating alternate hierarchies in Essbase Studio.
Thanks in advance..!!looks like similar issue..
https://forums.oracle.com/thread/1555956
It will work in genaration 2 not in genration 1.
Thanks,
mady -
Essbase Studio :: Measure Hierarchy :: "accounts not from fact"
Hello,
I am trying to build a Measure dimension in Essbase Studio not from fact table, but from parent-child metamodel table.
[http://docs.oracle.com/cd/E17236_01/epm.1112/est_user/frameset.htm?ch10s03s02s05.html]
Here I've read that I should add loose measure creating cube schema to Measures/Measure Hierarchy field.
What loose measure? I added column from fact table. In Essbase metamodel it created Measure dimension with that one member.
Is it even possible to create measure dimension not from fact table?
Thanx in advance,
L00ka
Edited by: 990463 on Feb 26, 2013 7:40 AMThe approach to take is to create a hierarchy from your measures table, then use the data column from your fact table to populate the measures box in the schema. When building the Essbase model, select the accounts dimension manually.
Oracle recommend that you build the measures dimension directly from your fact table, the above approach deems it a loose measure, that is it isn't based off the fact table.
Steve -
Loading Attribute Dimension - Hyperion Planning
Hello Everyone,
I appreciated a lot informations that I found here. I red the http://john-goodwin.blogspot.com/2008/11/odi-series-loading-essbase-metadata.html
about loading attribute dimension on Essbase, but when I try to execute the same steps using Hyperion Planning Adapter in ODI, I cannot see the option inside the model to reverse also all dimension attribute, hence I cannot load members on my dimension attribute. Do you know how can I develop the attribute dimension load on Hyperion Planning?
Regards,
Wallace Galvão
BrazilHi,
You first need to create the attribute dimension in planning, ODI does not create dimensions.
Once you have created your attribute dimension you can reverse the planning application again and the attribute dimension should be created as a DataStore
Cheers
John
http://john-goodwin.blogspot.com/
Maybe you are looking for
-
Hi All, I have some understanding of key mapping internal functionality. my question is ... should I use this key mapping feature from all look up tables, main table while importing from remote systems? should all my feilds have REMOTE KEY enabled.
-
Site-to-ste VPN with overlapped subnet.
Hi Friends I have to set up site to site VPN with overlapped network ASA 5540 and checkpoint what is the best parctice to achive tis goal Thanks in advance
-
Replacing a root pool disk example
Replacing a root pool disk has several use cases: 1. Replace a small disk with a larger disk 2. Replace a failed disk with a replacement disk 3. Outright move a rpool to a different disk because you want to The easiest way is to attach the replacemen
-
Stream or syncing from an iPod?
After my 18 month old Airport Express inevitably packed up and stopped working I decided to upgrade to AppleTV. To be honest unless I'm missing something AppleTV doesn't seem to be able to do half the stuff I'd hoped for. Is there anyway I can get th
-
Hi, My MDB reads the message from the queue and invokes a session bean for some operation. My problem is, if the operation in session bean fails, the message in the queue should not be deleted. For Eg. MDB reads the message in the queue and passes to