EPMA for Attribute dimension

What is the column field heading for Attribute dimension.
for example if I have Entity dimension and I have a Geography Attribute dimension attached to it and I have a Color Attribute dimension attached to it as well
What would be the column names for the 2 columns in the entity section be?
I'm using the Oracle Excel EPMA file to create the ads but I could hardcode it as well.

Hi,
The column headers should be Geography and Color. You should also define the associations between entity and these attribute dimensions in associations sheet.
Actually, these columns should appear automatically after you define the association.
Cheers,
Alp

Similar Messages

Drill through for Attribute dimensions

Hi,
How to enable drill thrus for Attribute dimension members. I have included the Attribute dimension in Drill thru intersections, but still I am not able to do drill thrus on Attribute dimension members. Is there any other settings I need to do in Metaoutline?
Thanks
Kannan.

Yep, this is a limitation. I suggest you create two reports one that takes your "optional" dimension out and a second one that has it in. if they don't need the dimension, select the first report and if they need the filter then the second. I m always a little leery with recursive hierarchies and Gen 2 or 3 sine they create a list of level 0 members under the selection in the query and there are limits to the number of members in an in clause and at high levels in the hierarchy it is easy to surpass it (In Oracle it is 1000 members)

Calculation issue on attribute dimension

The issue that I'm facing with is as below. I have two pass calc on some of the measures in the outline. Since I'm not doing any calculation on the attribute dimension, when I drill down using this dimension it pops up an error message
"Two-pass calc skipped on member [X] in attribute calc"
Please advise on how to resolve this.
Thr formula has @CURRMBR. The DBAG says that If a member formula contains a run-time dependent function associated with an attribute member name, and the member with the formula is tagged as two-pass, calculation skips the member and issues a warning message.
It also says that Two-pass calculation member property is unavailable for attribute dimensions.
So does it mean that every two pass calc member is skipped?
I'm a bit confused.. how does it work?
Is there a resolution for my issue? Please confirm if there is a way to get this two pass calc done for the formula with @CURRMBR.
Thanks.
null
.

Hello,
I will give it a try:
<>
Attribute dimensios are calculated dynamically. They provide a different view on the members of the associated dimension which they belong to. There are 5 different calculation functions in the rollup of the members on the base dimension (sum, min, max, count, average).
So this is within the associated dimension (sparse) which is linked to the attribute dimension (virtual).
The accounts dimension is always involved in displaying figures. The attribute calculation e.g. sum is done last. So the dynamic calculations have to be done first. This message is likely a warning message that the value displayed is not the result of the two-pass calculation, but from the attribute calculation.
You might review the storage setting of the member. Often the @currmbr is also not necessary in the formula when considering the calculation order of the members.
Hope this helps a bit.
Regards,
Philip Hulsebosch
www.trexco.nl

Creating Attribute dimension

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 Advice

As 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

EPMA for Planning

If I create a planning app in EPMA, can I bypass EPMA for building dimensions and just use Essbase load rules to build the dimensions?
Jz

Just to expand
The metadata is stored in the Planning/EPMA relational database and when you do a refresh database .... your essbase metadata... e.g dimensions gets overwritten
PD

How to design Flat file for loading attribute dimension in a planning application

Dear Gurus,
I have a requirement to extract attribute dimensions from an essbase application and load it to another planning application. I have a dimension called Program and two attribute dimensions Sales Manager, Accounts manager associated with Program dimension in Essbase application. I will Extract these dimensions using Essbase outline extractor. After Extracting the attribute dimensions I have to load these dimensions to planning applications using outline load utility. Kindly guide me how to design the flat file for loading attribute dimensions in planning application.
Thanks and Regards
SC

You could dig through the docs and try to figure out the file format manually, or you could do this the easy way. Simply use the Outline Load Utility to export your attribute dimension from Planning. The export file format is the same as the import file format. You might have to manually add a couple of test members to your attribute dimension so that your export file has some content. Then simply update the file you exported, and import it.
(I am assuming you have already manually created the Attribute dimension in Planning, and that you simply need to add members to it.)
Hope this helps,
- Jake

OLAP query returning "name" rather than "key" attribute for a dimension

Hello,
I am busy with a project that involves drawing data from an OLAP cube (in SAP BW), then transforming and contextualising for use in an EMI environment. The project runs on MII 12.1.
The standard OLAP connector and OLAP queries have been used (would prefer not to go the route of creating a call to the OLAP XMLA web service directly). One of the important dimensions is returned as a name (descriptive text) rather than a key (the cost element code itself), preventing us from reliably applying business rules to classify cost elements. Categorising cost elements based on their text descriptions is not a sustainable solution.
The output needs to allow for two dimensions (cost element and an equipment identifier) against which individual cost values will be listed. It appears that the two dimensions must both be on the "x-axis", as result columns are automatically renamed, e.g. C000001, C000002, etc. If anyone knows of a way to suppress this renaming behaviour, please let me know.
Is it possible to force the "key" attribute to be returned instead of the "name" attribute? I have identified two preferred options:
1. MDX syntax of the query itself
2. configuration of the OLAP connector
I have not found a way to do this through MDX syntax, but would welcome any suggestions.
Alternatively, perhaps there is a non-standard way of configuring the OLAP connector so that the key rather than the name attribute is returned for all dimensions. Has anyone anything, e.g. chosen a non-standard ColumnNameAttribute or DataTypeAttribute, in this regard?
Thanks,
Marc Chaplin

Apologies for the formatting above
Part 1:
Hello,
I am busy with a project that involves drawing data from an OLAP cube (in SAP BW), then transforming and contextualising for use in an EMI environment. The project runs on MII 12.1.
The standard OLAP connector and OLAP queries have been used (would prefer not to go the route of creating a call to the OLAP XMLA web service directly). One of the important dimensions is returned as a name (descriptive text) rather than a key (the cost element code itself), preventing us from reliably applying business rules to classify cost elements. Categorising cost elements based on their text descriptions is not a sustainable solution.
The output needs to allow for two dimensions (cost element and an equipment identifier) against which individual cost values will be listed. It appears that the two dimensions must both be on the x-axis, as result columns are automatically renamed, e.g. C000001, C000002, etc. If anyone knows of a way to suppress this renaming behaviour, please let me know.

EPMA/Planning custom dimension member attributes question

I have a custom dimension associated to an attribute dimension that I am setting via dataloader. Can I query on members with missing values of an attribute?
For example,
Dimension: Product
Attribute: Color Members: Red, Green, Blue, Yellow
Should it also include a Color member “Other” and require that every Product member have the Attribute Color set to one of the members?
Thanks for your help -

Hi,
If you are requiring to do analysis on other areas then it is probably best practice to create another attribute which will store this information, as you mentioned you could just create a member called "Other"
Cheers
John

EPMA for Essbase (Is this product for real?)

Hi All,
Just curious if anyone else is having the same issues with EPMA (with Essbase 11.1.1.3) that we experience each month. I have no faith in this product and I am always terrified that unintended changes will go through to Production. It doesn't seem like this product is fit for the marketplace.
Here are a few of the issues we experience:
1. Partition files in EAS must be renamed in order to have a successful deployment.
2. Member order changes. If we position a member in the middle of a member hierachy, it will end up at the bottom of that list after being deployed.
3. If we make changes to Attribute dimensions, they sometimes won't show up after being deployed and we must re-deploy 2 more times to have them show up.
4. We get various error messages after deployment referring to formula mistakes even though these formulas do work.
5. The hierachies appear to be jumbled up and members look to be in the wrong place. We logout, and log back in and everything goes back to normal.
6. It is very difficult to compare what we have deployed in Development to what we have in Prod so that we isolate what changes are going through.
All of these issues basically compound and make it so that we waste days reviewing our work just to make sure EPMA doesn't wreck our metadata. Making changes in the EAS Console is a breeze but I just don't know of a way to push the changes to all 5 of our apps in Dev, QA and Prod in an efficient manner.
Please let me know if there are patches / solutions to fix these issues or if this is what everyone goes through. I just assumed the majority of companies were on EPMA but after seeing these errors, I am starting to wonder. I can't imagine bringing our HFM apps into EPMA with this kind of performance.
Thx,
Mike

According to another post, EPMA isn't really used that much for purely Essbase. I don't use it myself so the actual benefits are unclear. Folks have suggested if you are just using it as a place to store dimensions to share across applications, then you can just do that using an SQL database or similar - which is kinda what we do. I think it gets better if you are using HFM and planning. Maybe the latest version is better?

EPMA Validation Error: dimension removed or deleted since first deployment

Dear experts,
Our deployment is on EPMA and we were able to successfully deploy the Planning application before. Then we tried to update the dimension by loading UDA to each members, after which, we hit this error at validation:
Error : The xxxx dimension has been removed or deleted since the first successful deployment of the application.
We did have UDA dimension in it before the update and all dimensions in the applications are shared from the library.
Our application is on 11.1.1.3 and we have tried to removed all associations and redo it, but still hit this error. As there are many members being assigned with UDA, wonder if it's possible to solve the error without deleting the UDA dimension and recreate it?
Any input help, please kindly help!
Thanks!!
Edited by: 845931 on Apr 5, 2012 4:20 PM

You will find it in My Oracle Support.
The contents are as below:
Applies to:
Hyperion Planning - Version: 11.1.1.0.00 to 11.1.2.0.00 - Release: 11.1 to 11.1
Information in this document applies to any platform.
Goal
You cannot delete a UDA dimension from EPMA once the application it belongs to has been deployed.
ERROR
The 'Colour' dimension has been removed or deleted since the first successful deployment of the application.
Is there some way to remove the UDA dimension (not just modify its members)? This was possible in the Classic Planning interface but is not when using EPMA.
Solution
This is a limitation of EPMA and Planning. There is no mechanism in version 11.1.1.3 and earlier to allow EPMA to remove dimensions from Planning, and because EPMA treats UDAs, Attribute Dimensions, and Smart Lists as dimensions they also cannot be removed from Planning once the application has been deployed for the first time. They can be modified, but not deleted.
In version 11.1.2 you can delete a UDA dimension in EPMA with no errors but the application will no longer validate (throwing the same error as in 11.1.1.3) and therefore cannot be deployed. However, this does offer an easy way to remove all UDAs assigned to members. If you delete and then re-create a UDA dimension in EPMA the application can be re-deployed again, even if you do not re-create any dimension associations. When you redeploy, all UDAs for this dimension are cleared from Planning and Essbase. This means that although the UDA dimension itself is required in EPMA, there is no trace of it in Planning and Essbase after redeploying.
HTH-
Jasmine.

Attribute dimensions may only be added to sparse dimensions

Hello everyone,
I got this error several times. It wouldn't be so surprising for me if my Account dimension would be set as dense. But it is set to be sparse...
Could anyone help me with this?
Maybe some details will be helpfull:
I have created an attribute dimension with only one member - "Yes". Then, I have created flat file for Account dimension with 6 custom properties, every property associated with the attribute dimension. Account dim is set as sparse, not dense. Importing flat file results ok, with no errors and warnings. Validating the application is ok.

Hi Andy,
I'm using only Plan1 and account dimension is set as sparse in this plan type.
What do you mean with "refreshing"? I'm doing redeploy of the whole application from EPMA. Or should I try refreshing the database from the application? I think the first step may be the redeploy. Or am I wrong?
Thanks,
Vlado

Attribute dimension mapping

Hi to all,
I have my application with 11 dimensions and 3 attribute dimensions... . When we generate our metada.ads for loading to the app, we see the diferent elements for the dimension SKU mapped with the attributes, but when we make the load for the dimension, we don´t have any element of the SKU dimension (product dimension) mapped with the attributes, and we have no error message........
Any suggestion?
We generate the metadata.ads through EPMA File generator in Excel 2007....
Thanks in advance
David.

Hi David,
A couple of pointers maybe:
- Have you applied the latest EPMA patches?
- What version are you on exactly? 11.1.1.3 or 11.1.2.x?
- We had a similar issue where some attribute dimension mappings werent exported caused by the fact that although the attribute dimension was associated with a base dimension in Planning, this association did not exist in EPMA. The strange thing is that we were still able to deploy the app with no errors. In our Planning app properties we do have a EDIT_DIM_ENABLED - true propery that enables to make changes to Planning directly. I think this is where the issue started.
Hope this helps.
Seb

Error While Building Attribute Dimension in ASO Cube

Hi all,
Cuurently I'm trying to bulit an ASO application in Oracle EPM 11.1.1.3
When I'm building an attribute dimension "QSize" in ASO cube ,I'm Getting some Warnings
I'm using Flat file as my source AND MY RULE FILE IS
GEN2,QSIZE, ALIAS2,QSIZE
1, ">100"
2, "100-249"
3, "250-499"
4, "500-1000"
5, "<1000"
I VALIDATED THE RULE FILES,
when i try to load the data into the essbase,Its giving me a warning stating that
Record #1 - Incorrect Syntax For Member <100 (3305)
*1 "<100"*
and i don't see the alias name for member 1
I came know that Essbase doesn't allow ">" character at the beginning of Dimension Or Member Name
Please let me know if there is Any other way,where I can Assign the alias "<100"
Thx in Advance
Regards,
RSG
Edited by: SG on Jan 22, 2011 3:03 PM
Edited by: SG on Jan 22, 2011 3:04 PM
Edited by: SG on Jan 22, 2011 3:06 PM

Could you get away with an underscore? I think that works. You will have _<100 which is not ideal but might be worth a try.
Failing that, go with GT and LT. <--This is incredibly lame, but sometimes users go for the "computer is too stupid" answer. Which in this case, is sort of true.
Regards,
Cameron Lackpour

Web Analysis data layout does not reflect newly added attribute dimension

Hi,
We newly added one new attribute dimension. If any new report creation in Web Analysis reflect that dimension. However, the reports which are old(created before the addition of new dimension), does not show the newly added dimension.
Please advice.
Thanks,
Meenakshi

Thanks for this.
I have tried assigning the new DB connection. However, still it did not work. Does the data layout displays dimensions according to reports. I mean, can we restrict the visibility of dimension at report level? Please advice.
Thanks,
Meenakshi

How to hide the Attribute dimension from Planning webform

I am in Planning 9.3.1
We are using members in row section of webform w.r.t Attribut dimension
so when we are viewing the webform- it is displaying member name followed by Attribute dimension name .
any way to hide that Attribute dimension member from the webform.
KK

In the Dimension Properties for that dimension, select "Enable custom attribute display" but dont pull the attribute from Available Dimensions to Selected Dimensions. I've given the name of the property from 11.1.1.3 version, so not sure if its the same in 9.3.1 but it'll be somewhat similar.
Cheers

EPMA for Attribute dimension

Similar Messages

Maybe you are looking for