Value against Attribute dimension

Hi All,
I have an employee dimension and there are attributes assigned to each employees like Employee ABC has Grade1 and so on.
Now I need to calculate measure called 'Base Salary' which is Mid Point Salary for Grade 1 multipied by Multiplier.
I have Midpoint salary and Multiplier as measures. However I am not sure if I can input values against attribute members like Grade1, Grade2 and use in business rules or formula.
Since attribute is not a real dimension, I think I cannot make it hold value as Grade1 may point to different employees.
Let me know your views.
Cheers,

1. You are correct you can't store data at attribute level.
2. If you know your multiplier, you can write code as follows:
Fix
@IDesc(Employee) and @attribute("Grade 1")
DESTINATION = "MIDPOINT SALARY" * Multiplier
EndFix;
Hope this helps.
Venu

Similar Messages

Time Dimension Type allows different values in attributes - Bug or Feature?

Not sure if this is a bug or a feature.
But if one has multiple hierarchies on a Time dimension. You have the ability to specify different values for member attributes in different hierarchies.
Example.
Hierarchy A has MIN_ID for it's Member and uses MIN_END_DATE for it's END_DATE
Hierarchy B has MIN_ID for it's Member and uses SESS_END_DATE for it's END_DATE
As per this post and David Greenfield's comment:
Dimension Sort issue when multiple mappings for different hierarchies
"Are you attempting to map the same attribute, SORT, to different columns in the two hierarchies? Put another way, 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 since a member must have the same value for the attribute regardless of the hierarchy."
Unlike a user dimension, a time dimension appears to allow this and it appears to work as intended. Is the behavior in this case intended to be different between a user and time dimension?

I think that this is not a bug. There is an incompatibility in design which prevents you from using the same attribute differently for both hierarchies.
NOTE: Unlike parent relationship which depends on <dimension, dimension hierarchy>, Dimension Attribute is dependent on <dimension> alone, not dependent on <dimension, dimension hierarchy> combination. Hence it can only take on 1 value for 1 dimension member.
I think that the time dimension only appears to allow this. The key thing to check is for Time Dimension members which are common to both the hierarchies. Only one of the mappings will take effect (usually the hierarchy which is loaded last will remain in the aw/usable for queries, reports.. it would have over-written the earlier attribute value loaded as per the earlier hierarchy load).
Visualize a dimension as a long list of members which are built up contiguously on a per hierarchy, per level process using the mapping information saved. Once a member is defined (created) via Hierarchy A, it wont be created once again while loading Hierarchy B but is instead updated or redefined based on Hierarchy B's mapping info.
Assuming the dimension load attempts to load Hierarchy A first and then Hierarchy B,
* Dimension load for Hierarchy A will define the various members using MIN_ID and set the END_DATE attribute to value=MIN_END_DATE
* Dimension load for Hierarchy B will re-define the various members using MIN_ID and re-set or over-write the END_DATE attribute to value=SESS_END_DATE
* In this case, it looks like all members are common for both hierarchies (as both members are mapped to same column MIN_ID) and you would end up with END_DATE=SESS_END_DATE.
Actually whether all members are common to both hierarchies or not depends on the quality of data in your snowflake/star table: if parent level for Hierarchy A as well as Hierarchy B is setup fine then the members will be same set (overlapping in whole). If some rows for MIN_ID have parent column for Hierarchy A setup correctly but parent column for Hierarchy B =null or invalid value then that member will exist in Hierarchy A alone and would contain END_DATE=MIN_END_DATE as the corresponding update along Hierarchy B would fail due to hierarchy data quality issues (join from current level to parent level).
As regards a solution to your problem, you should not use the same attribute "SORT" for dual purpose (both hierarchies). Instead define attributes SORT_A and SORT_B and make them enabled for Hierarchy A, Hierarchy B respectively and map/use them appropriately in your reports.
HTH
Shankar

Excel Addin - Attribute dimension values

Hi all, I have an excel report which pulls data for our departments. Eachdepartment has a manager and the manager for the department istagged using attribute dimension. Now I want to get data for alldepartments and in second column along with it the name of themanager (i.e. the attribute dimension member name). I somehowcannot figure out a way to do this again. Any inputs into how this can be done? 

Robert, Thanks for the suggestion.Our analysts already have the report templates setup which theyuse for retrival. I am not sure if they want to do something likethat. Sometimes there might not be data in the department forthat period and then that department would be suppressed but it isneeded in the report at times.I am guessing that I might have to do some VBA stuff in thereport to allow the analysts to have this. I was just hoping to seeif someone else has found a better way to do this. I say bettersince I was looking for some that the analysts might be able to doeasily but themselves.

Essbase Attribute Dimension

When we retrieve totals on base dimension without specifing the attributes the numbers turn out right. HOWEVER when we retrieve specifying the attributes the totals consolidate everything inspite of having tilde on some of the members.

You are correct, when you retrieve and include an attribute dimension, then it will add everything regardless of the sign. eg. profit = revenue less expenses, however, throw an attribute in there and then suddenly, profit will be revenue plus expenses. Wrong.This is because attributes are always dynamically calced and they will only sum, count, min, max or avg. This means that you can't have attributes associated to dimensions that roll up with anything other than pluses(+). To make it more complicated, if you do have attributes against a standard roll-up dimension and the other dimensions have a dynamic calc member then the dynamic calcs will be a sum again regardless of the sign. So the other dimensions have to be stored values.

Preaggregation across value based hierarchy dimension in 11g

Hi All,
I have created a cube with 6 dimensions in olap 11g. One of those six dimensions has only one hierarchy which is value based hierarchy. I have chosen level based aggregation as I know at what levels exactly users are going to query. When I was going through the dimensions to choose levels to preaggregate I noticed there were no options available for my value based hierarchy dimension ( I could see "all" option for the same case in 10g) then I tried to look for definitions of underlying objects just to make sure it will preaggregate data across my value based hierarchy dimension.
I found value set corresponding to my value based hierarchy dimension in <CUBE NAME>SOLVEAGGMAP object , which AWM uses to decide which dimension values to preaggregate but if I do rpr on that value set (rp r<CUBE NAME>SOLVE<DIMENSION NAME>_PVSET) it shows NA so my question is can I pre aggregate across value based hierarchy dimension in olap 11g?
Olap Version: 11.2.0.1
AWM version: 11.2.0.1
Thanks

Even if you know exactly which levels your users will query, percent based precompute (e.g. 30%) may still be faster in practice because queries are returned using 'sparse looping' instead of 'dense looping'. This was the single biggest performance advantage of 11g over 10g.
But if you still want to use level based precompute, then you should look at the XML template for the cube (as saved by AWM, for example). In it you should find something called PrecomputeCondition. This defines the set of members that are precomputed. Here is an example I just created using the GLOBAL schema
<PrecomputeCondition>
<![CDATA[
"TIME" LEVELS ("TIME"."MONTH", "TIME".CALENDAR_QUARTER, "TIME".CALENDAR_YEAR),
CHANNEL LEVELS (CHANNEL.TOTAL_CHANNEL, CHANNEL.CHANNEL),
CUSTOMER LEVELS (CUSTOMER.MARKET_SEGMENT, CUSTOMER.REGION, CUSTOMER.SHIP_TO),
PRODUCT LEVELS (PRODUCT.CLASS, PRODUCT.FAMILY, PRODUCT.ITEM)]]>
</PrecomputeCondition>The PrecomputeCondition is also visible through the USER_CUBES view.
SELECT PRECOMPUTE_CONDITION
FROM USER_CUBES
WHERE CUBE_NAME = 'MY_CUBE';You can hand modify this condition in the XML to specify an alternative 'non level based' precompute condition for any dimension. For example, if you define an attribute named 'SHOULD_PRECOMPUTE' on your PRODUCT dimension that is 1 for members to be precomputed and 0 for all others, then you can change the condition as follows.
<PrecomputeCondition>
<![CDATA[
"TIME" LEVELS ("TIME"."MONTH", "TIME".CALENDAR_QUARTER, "TIME".CALENDAR_YEAR),
CHANNEL LEVELS (CHANNEL.TOTAL_CHANNEL, CHANNEL.CHANNEL),
CUSTOMER LEVELS (CUSTOMER.MARKET_SEGMENT, CUSTOMER.REGION, CUSTOMER.SHIP_TO),
PRODUCT WHERE PRODUCT.SHOULD_PRECOMPUTE = 1]]>
</PrecomputeCondition>If you recreate the cube from the XML with this condition, then the PVSET valueset you discovered should contain all dimension members for which the attribute value is 1. This gives you complete control over what is precomputed. Note that AWM doesn't support this form of condition, so it won't show up if you go to the Precompute tab, but it is valid for the server. The PL/SQL below will modify the PrecomputeCondition (for the cube named MYCUBE) without going through AWM.
begin
dbms_cube.import_xml(q'!
<Metadata
Version="1.3"
MinimumDatabaseVersion="11.2.0.2">
<Cube Name="MY_CUBE">
 <Organization>
 <AWCubeOrganization>
 <PrecomputeCondition>
 <![CDATA[
 "TIME" LEVELS ("TIME"."MONTH","TIME".CALENDAR_QUARTER, "TIME".CALENDAR_YEAR),
 CHANNEL LEVELS (CHANNEL.TOTAL_CHANNEL,CHANNEL.CHANNEL),
 CUSTOMER LEVELS (CUSTOMER.MARKET_SEGMENT,CUSTOMER.REGION,CUSTOMER.SHIP_TO),
 PRODUCT WHERE PRODUCT.SHOULD_PRECOMPUTE = 1]]>
 </PrecomputeCondition>
 </AWCubeOrganization>
 </Organization>
</Cube>
</Metadata>
end;
/

Verify a value against value set

Hi,
I am trying to import price list lines along with Pricing attribute values.
I have to validate the uploaded values against the pricing attribute value set, before I import them into base tables.
Value set defined is of type table validation.
I wanted to know if there are any public APIs that can be used to validate the value against the Value set values within my PL/SQL procedure
Also please point me to documentation that lists various public PL/SQL APIs
Regards,
Mrutyunjay

Hi,
You can query the fnd_flex_values or fnd_flex_value_segments_vl to find the name of the value set defined.
Another point is that the Value Set is defined of validation type Table so the values are dependent on the base tables.
There are no such API's to cater the need for Verfying a Value against a Value Set.
If u want to search for public API's go to the metalink.
Regards

Validate a value against table validation value set within PL/SQL

Hi,
I am trying to import price list lines along with Pricing attribute values.
I have to validate the uploaded values against the pricing attribute value set, before I import them into base tables.
Value set defined is of type table validation.
I wanted to know if there are any public APIs that can be used to validate the value against the Value set values within my PL/SQL procedure
Also please point me to documentation that lists various public PL/SQL APIs
Regards,
Mrutyunjay

You can find functions and procedure for Value sets in packages FND_FLEX_VAL_API or FND_FLEX_VAL_UTIL.
Example : get_table_vset_select gives you the select statement of your value set. Executing this statement will allow you to validate your values.

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

MDX query Help - filtering Measures based on values in a dimension.

Hi,
I want to get values of a aggregate measure filtered by value available in Dimension attribute.
Details:
We have a Measure called "Average Compliance" which provides an average value over certain dimensions. Now I have some target values available for different attributes.
Fact Table (there are bunch of other columns in the fact table)
Id
TargetId
InstanceId
LocationId
Compliance
1
1
1
1
0
2
1
1
2
1
3
2
1
1
1
4
2
2
1
0
5
2
1
1
1
6
2
1
1
1
Dimension
TargetId
Target Average Compliance
1
90
2
70
3
92
4
40
Now I want to get a query where I can get the "Average Compliance" which is higher then the target average compliance.
Is this achievable?
Thanks in advance.

HI,
I did give this a try. (replacing the date dimensions.)
WITH MEMBERMEASURES.mycalc AS
[Dim Measure].[Target].
CURRENTMEMBER.MEMBER_KEY
SELECT
{[Measures].[Average Compliance],MEASURES.mycalc}
ON0
FILTER([Dim Measure].[Target].[Target]
,([Measures].[Average Compliance] * 100) <
--80
CINT([Dim Measure].[Target].
CURRENTMEMBER.MEMBER_KEY)
)*[Dim Measure].[Measure Uri].[Measure Uri]
ON1
I am still seeing values for average compliance which are more than the target (I even tried setting the value to be hardcoded to 80 and I still see average compliance of 100
Thanks

Setting up Dynamic Attribute dimension.

Hi,I have a dimension for my clients and a measure dimension for sales. I want to set up an attribute dimension called Band for my Client dimension. This should be set to "Band=Large" when the sales total for the client is more than 20000 USD in the previous year (2001) or it should be set to "band=Small" if the total sales for the previous year is less than 5000 USD or else "Band=Mid" if the total sales in the previous year is between 5000 to 20000 USD. Currently, I use excel sheet from the essbase database extrace the total sales for each range and use the same as input to set the attribute dimension. Is there a easy way to do this using calc script.regardssuja.

No, there isn't. Since attributes are member based, there is no way (at least in Essbase) to dynamically assign an attribute to a member based on a data point.However, there are ways around the problem, but I can see one dilema. What if sales for a client is "large" for a member of one dimension but "small" for another? Members are not intersection based, so a client cannot be tagged as "Large" for one intersection and "Small" for another.If you want to go the attribute route, there may be a way to automate the process you described in your post - perhaps running an extract from Essbase similar to your Excel report and having a script assign the attribute value according to the sales figures.If you want to use a calc script, you could create a "BAND" member in your accounts dimension and assign it a 1 (Small) 2(Medium) or 3 (Large) depending on the sales figures.Hope that helps.Regards,Jade-------------------------------Jade ColeSenior Business Intelligence ConsultantClarity [email protected]

Attribute Dimension and association with multi level base members

I am trying to associate attribute dimension members with base members that can be at different levels (level 0 or level 1 or level 2 ).
First question - Is that possible ? Second how do I do that.
I am building the dimensions(base and attribute) members first and then trying to associate.
I get the following error message :
Base member (xxxxxxx) association level does not match base dimension association level
The base dimension looks like
Supplier
|-----Supplier Group
|---------Supplier ID (Associate this member to an attrbiute dimension)
|---------------Invoice Number
Sometimes the Supplier ID may not have a Supplier Group or an Invoice Number (hence it can be a level 0 or directly under the dimension name - Gen2)
The Attrbute Dimension looks like
Supplier Value
|---High
|---Medium
|---Low
Edited by: 816875 on 30-Nov-2010 07:01

First to clarify, base mambers by definition would all be level 0 members, but to your question, attributres can only be associated to a single level within a dimension. your problem is sometimes the supplier is level 0 and other times level 1. This can't be done.

Attribute Dimension or Alternate Hierarchy

Hello,
We have a sparse dimension that has probably around 1500 members. We need to report on these members in different views then the current hierarchy holds. Is it best to create an alternate hierarchy with these 1500 members or to tag these members with various attributes and then use the attribute in the different reports. I did some research and found that attribute dimensions often have slow FR performance since they are dynamic, however, I feel like 1500 shared members is a lot. Any tips, tricks, advice would be greatly appreciated.

Hi,
I don't think 1500 shared members is a concern in and of itself (unless you are putting them all under one dynamic parent!). You are correct there could be some response time impact with attribute dimension retrievals, but then shared members under dynamic sparse parents may present similar concerns.
I would encourage you to think about the structure and navigability desired. You should keep in mind that shared member rollups can only be used in reports consistent with the dimension they are in. One advantage of attribute dimensions over shared rollups is that, only with attribute dimensions, can you cross-tab report against the base dimension. If your users care about being able to see certain alternate groupings across the main dimension, then I would suggest going with attribute dimensions.
There are other considerations. For instance, adding a large number of shared rollups in your BSO anchor dimension (the physically last dimension with hierarchy), you put more demand on Essbase calculator cache.
Out of time for now. Just sharing some initial thoughts I hope you will find helpful.
Darrell Barr

Reporting Attribute dimension on Planning Database in HFR

Can you report attribute dimension values in Hyperion Financial Reports when connection to the Planning database connection? I am not seeing Planning Details as an option in HFR as only Planning appears. Is there something that I'm missing? I would like to report Smart List alphanumeric values on HFR but also be able to pull in the attribute dims, yet that doesn't seem possible.

Hi Alex
That sounds like a bug, I have used attribute dimensions in reporting lots of times in earlier versions and I'm sure that some of those used planning rather than essbase connections. I've not read the documentation around the subject so can't be sure but it sounds pretty fundamental so I'd be surprised if not a bug.
Worth doing a bit of digging on Oracle support or in the readme files or even raising an SR if you have that option.
Regards
Stuart

Problem adding attribute dimension

Version: 9.2
Cube: ASO
I feel like I am dropping the ball. I am trying to add an attribute to my ASO cube at the bottom of my outline. Everything I try to edit the member properties I get an "Attribute Calculations dimension can not be created". I don't have any calculations/consolidations.
When I click the database properties-->Attribute settings-->Calucation dimension names-->(try entering a name) all I get is "NULL value for member name string".
When I use ASOsamp(or any app) I can create/tag an attribute dimension though.

Hi There,
I guess you might've added a Gen1, member, i.e. a dimension, at the end of the outline & intended it to be an Attribute dimension. Correct?
If yes, after adding the member at the end,
- Before opening the dialog for member properties, tag the dimension as "Attribute" by clicking on the appropriate icon, right on the outline page.
- Associate this attr. dim to one of your sparse dims.
- Add a member to the Attribute dim. & associate it with one of the members of sparse dim.
- Now, it should let you save the outline.
Good luck!
- Natesh

Attribute Dimensions and Excel Retrieves

Dear All, I have a cube that has a sparse dimension with attributes attached (all at the same level). When I retrieve using different attributes in the retrieve the results are not consistent i.e. some of the sparse members with the same attribute are left out of the result. It appears to happen when branches of the dimension in the same area are separated by a branch with an alternate attribute value (from the same attribute dimension). I have cured this by moving the affected branches next to each other, is this something that I need to watch out for on the design side i.e. to do with the way Essbase handles attribute dimensions? Any guidance would be appreciated.

Graham,
This is definitely a supported feature in EIS/9.3.1/ASO. I have many models with this type of structure. How you set it up can vary. Usually my Attribute Hierarchies are not that deep, only two to three levels, maybe four in a rare case, so I don't usually use a parent child table to set up the hierarchy (I'm not saying that it won't work, it might, I haven't tried, but same steps should apply). In a typical model I will have my stock table which has a buyer field. Then in another table I will have my attribute structure which will have columns for buyer, teams, and categories.
In EIS OLAP model, you add your attribute hierarchy table and use a join to link it to the main stock table, joining on the buyer field (you are now going from a "star" schema to a "snowflake". Go into the properties and make sure you define all the columns as "Attributes".
Then in Metadata model, drag your categories attribute onto the outline, then drag the teams and set it as a child of categories and finally drag buyer and set as child of teams. You only set the attribute association for the buyer back to the base dimension.
When you run your dim build it will set up your attribute dimension correctly.
Some things to keep in mind, make sure you have a process that ensures for every stock code you have in the main table, you have a matching one in your attribute dim table.
Sometimes, depending on how much manipulation I need to do, instead of joining the tables in EIS I will go back to relational source and create a view that joins the two tables together, then in my OLAP model, I have one table that has three attribute columns, one column for the buyer and then the other two for team and category, from that point setting up in metadata model is the same.
Good luck, let me know if you run into trouble.

Value against Attribute dimension

Similar Messages

Maybe you are looking for