Attribute dimension build method

Hi All,
Please do let me know the process to build the attribute dimension using rules file. I tried it following the same way as any other normal dimension but donot get the property associated to the attribute dim. We want this process to be automated as we rebuilt the ourline each time during the load. Pleaes help.
Thanks,
Praveen

Have a read of the section :- Building Attribute Dimensions and Associating Attributes
http://download.oracle.com/docs/cd/E12825_01/epm.111/esb_dbag/dotdimb.htm#dotdimb1060796
Cheers
John
http://john-goodwin.blogspot.com/

Similar Messages

Best Method in Dimension Building

Hi All,
Please advice me on the Best dimension Building Method( Parent child/Generation/ Level Methods) and also let me know when these dimension building methods can be used.
I know this is a pretty simple question. But, I am still looking for better clarity on these methods.
Thanks for your replies in advance.
Regards,
Upendra. :[email protected]

Parent Child absolutely for reason 1 alone. Our source system (SAP) went through a period where it seems like every week the hierarchy depth grew. I got tired of revising the load rules to accommodate new levels. Finally hit upon the idea of transforming a level based metadata file into a PC file. No more headaches with new levels: if they want a 100 level depth hierarchy <heaven forbid>, I can quickly transform it into a simple PC file.
Message was edited by:
dwelden

Creating Attribute Dimensions

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. 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). Go to View|Dimension Building Fields. Go To Field|Properties|Dimension Building Properties tab, and set the field properties.. The first column will be the Level 0 for Cost Center. The second column will be the attribute. Validate and save the load rule. 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**.

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

How to Build Attribute Dimension Dynamically & Load with LCM?

Hi, I'm trying to modify the existing outline at cilent's site. For some reason, when I pulled the outline with extractor, it didnt come out in the format that is compatible with Outline Load Utility. I was told to use LCM so I may still load with minimal to no modification to the existing structure of outline.
So can I build dimensions dynamically in EXCEL then load with LCM and push to Planning?

The log came back with many unrecognized headers in the outline. I spoke to Oracle Support many times, and they said that the format of our outline is improper for Outline Load Utility to read.
Since the outline has already been incorporated, we are not allowed to many any significant changes. That is why we were advised to use LCM.
I tried to use a sample of one of the existing attribute dimensions in XML as the base and build the new attribute but it failed. I would appreciate if you can provide steps by steps resources to show how to add new attributes to the existing outline.

Building Attribute Dimensions in VB

I am writing a VB program to update an attribute dimension. I have followed the documented approach to populate the ESB_MBRINFO_T structure but continue to get errors 8 - ESB_OUTERROR2_ILLEGALDATATYPE and 64 = ESB_OUTERROR2_ATTRDIMNOTASSOCIATED.
The code is
Public Function esbMoveOrAddMember(rsChild As String, _
rsParent As String, _
rsAlias As String) As Integer
Dim sts As Long
Dim stsInfo As Long
Dim hChild As Long
Dim hCurrentParent As Long
Dim hParent As Long
Dim uNewMemInfo As ESB_MBRINFO_T
Dim szAlias As String * ESB_MBRNAMELEN
esbMoveOrAddMember = 0
If esbFindMember(rsParent, hParent) Then 'Find Parent
If esbFindMember(rsChild, hChild) Then 'Find member
' Found parent and child so see if a move is needed
' Get the current parent handle
stsInfo = EsbOtlGetParent(mhOutline, hChild, hCurrentParent)
If hParent <> hCurrentParent Then
sts = EsbOtlMoveMember(mhOutline, hChild, hParent, ESB_NULL)
If sts <> 0 Then
esbMoveOrAddMember = 1
Call essGetAndDisplayMessage(sts)
End If
End If
Else
'Good Parent, new member so add it
Call SetupAttributeMemberForAdd(rsChild, uNewMemInfo)
sts = EsbOtlAddMember(mhOutline, uNewMemInfo, ESB_NULL, hParent, hChild)
If sts <> 0 Then
esbMoveOrAddMember = 2
Call essGetAndDisplayMessage(sts)
End If
End If
Else
esbMoveOrAddMember = 3
sts = 5
End If
'* Set the alias of the child member
If sts = 0 And hChild <> 0 And Len(rsAlias) > 0 Then
szAlias = rsAlias
sts = EsbOtlSetMemberAlias(mhOutline, hChild, "", szAlias)
If sts <> 0 And sts <> 1060023 Then
esbMoveOrAddMember = 4
Call essGetAndDisplayMessage(sts)
End If
End If
End Function
Sub SetupAttributeMemberForAdd(rsChild As String, uMemInfo As ESB_MBRINFO_T)
With uMemInfo
.szMember = rsChild
.usConsolidation = ESB_UCALC_NOOP
.fTwoPass = ESB_FALSE
.fExpense = ESB_FALSE
.usConversion = ESB_CONV_NONE
.usTimeBalance = ESB_TIMEBAL_NONE
.usSkip = ESB_SKIP_NONE
.usShare = ESB_SHARE_DYNCALCNOSTORE
.usStorage = ESB_DIMTYPE_SPARSE
.usCategory = ESB_CAT_ATTRIBUTE
.usStorageCategory = ESB_STORECAT_ATTRIBUTE
.Attribute = ESB_ATTRMBRDT_NONE
End With
End Sub
Any help will be appreciated as Oracle support is none so far.

Hi,
Your error "ESB_OUTERROR2_ILLEGALDATATYPE and 64 = ESB_OUTERROR2_ATTRDIMNOTASSOCIATED." indicates problem with attribute dimension association
kindly check is there any duplicate member in attribute dimension.
or same attribute dimension is associated with some other dimensions

Dimension Build - Change Member Names

Does anybody know if there is a way to revise outline member names through a load rule without affecting (losing) the data associated with those members? I have a .txt file with the current parent names, child names, aliases, properties, formulas, attributes and UDAs for the Products dimension. I would like to revise all of the level 0 member names without having to do so manually in the outline. Any help would be appreciated.

You can do this a couple of different ways.You can go into the outline itself through app manager, and witht he FILE drop down, update the outline at that point using your load rule.You could also automate this function with an esscomand script preforming and incremental dimension build (INCBUILDDIM).Randy Rehmer, Cincinnati Bell

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,
Daniela

I'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.

Does essbase studio support Parent/Child build method

Hi,
I am trying to build essbase outline from Essbase studio where my source data is in Parent child format. Dimension hierarchies are not built correctly with this build method.. all members are appearing as siblings... could you please confirm if essbase studio does support Parent Child build method... so that i can try to fix the bugs at source if there are any. Thanks for your help in advance.
Regards,
Praveen

HI John and Glenn,
Thank you very much for your help. I have now built essbase outline with recursive hierarchies.
I have total 11 dimensions and 1 fact table. During the cube schema built, chosen fact table column 'Amount' into measures/measure, 11 hierarchies into hierarchy section... and one dimension as "Account" dim from the 11 dims. The data load is failing with the below error:
Failed to deploy Essbase cube.
Caused by: Failed to load data into database: CurrrASO.
Caused by: Cannot get async process state. Essbase Error(1003007): Data Value [8.23326e+007] Encountered Before All Dimensions Selected, [1] Records Completed
The native sql issued by Studio does not contain the dimension column which is designated as Account dim. I have used custom sql (included one column from each of the 11 dims) but here the data value is also treated as member name and all the records are rejected.
Member 37356.617844 Not Found In Database
[2] Mar USD No Segment FY07 Actual-Detail E345 D310 R00 P0000 PL000 7306 37356.617844
I cant open the rules files in AAS console to check what was going on.. so need your help to understand where i am going wrong.
Thanks,
Praveen
Edited by: user8627339 on Dec 22, 2010 10:26 PM

Load hierarchical attribute dimensions with Integration Services?

Hi everybody,
I need to load product dimension which is organized in a relational table like this:
Product (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 it's own hierarchy. For Brand I have another relational table where data is organized parent-child like this:
Brand (brand_parent_code, brand_child_code, brand_child_alias).
I have used in the past Integration Services but with flat attribute dimensions.
Can I load hierarchical attribute dimensions with Integration Services? If yes, how do I do it, how do I specify the hierarchy?
Thank you,
Daniela

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.

Attribute Dimensions with Integration Services

Good evening, I'm creating an ASO Essbase model through Integration Services v9.3.1 and I am having difficulties with creating an Attribute dimension that contains a hierarchy.
We have a list of stock codes which are grouped by vendor in a dimension, each stock code has an attribute assigned to it for the buyer responsible.
The business requirement is to start from the top level of the attribute dimension, drill in to categories, then to drill in to teams, and finally to the buyer... so we effectively require 3 levels within the attribute dimension.
I have successfully created both the vendor (physical) and buyer (attribute) dimensions through EIS without problems, but when I load to Essbase all of the buyers are added at the top level of the dimension and I can't seem to specify that there should be a parent/child hierarchy to build the attribute dimension from.
Is this possible, and if so any advice you can give as to how I achieve this would be greatly appreciated.
Thanks in advance,
Graham

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.

Essbase Studio Deployment Dimension Build Errors

I have a ASO cube used to handle Subsidiary financial reporting to parent. Rather than alternate hierarchies, we use attribute dimensions for yearly differentiation. The ASO cube typically holds information for Current year + 3 prior years. This is the first year that we will achieve this as this cube was created near the beginning of 2010. Therefore, with the cube already having attribute dimension for 2010 & 2011, with the beginning of 2013 it is necessary to create the 2012 attribute dimensions. The cube has 13 anchor dimensions. Typically only 4 of these dimensions have attribute dimensions derived from them. Nonetheless, the following is the build list of the dimensions in the essbase model:
1: Financials Standard, Dynamic, Sparse
2: GL Date Time, Stored, Sparse
3: Incident Date Standard, Stored, Sparse
4: View Standard, Dynamic, Dense
5: Company Standard, Multiple-hierarchy, Sparce
6: Well location Standard, Stored, Sparse
7: Depletion Code Standard, Stored, Sparse
8: Vendor Standard, Stored, Sparse
9: Entity Standard, Stored, Sparse
10: Profit Center Standard, Stored, Sparse
11: Curr Yr Cost Obj Standard, Stored, Sparse
12: Past Yr Cost Obj Standard, Stored, Sparse
13: Measures Accounts, Dynamic, Existing
Attribute dimensions are mainly created in 4 of the Defined Hierarchies with in the cube; 1:FINANCIALS, 5:COMPANY, 6:WELL Location, & 10:PROFIT CENTER.
According to the Essbase Server log, upon deployment, the FINANCIALS Hierarchy generates 19 Dimension Build rule files with the associated SQL to pull members from our SQL Dimension Build tables obviously based on the way the Hierarchy is built as well as the joins created in the MiniSchema in the referenced Data Source. The COMPANY Hierarchy generates 5 Dimension Build rule files, WELL LOCATION generates only 1 Dimension Build rule file (this is mainly due to the fact that all the attributes generated from WELL LOCATION are built from the same table), and PROFIT CENTER Generates 3 Dimension build rule files. At this point for comparison purposes I want to include excerpts from the Server Deployment Log file depicting the dimension build rule files generated from the PROFIT CENTER Hierarchy:
Rule 1 Labeled XXXX_PRO.rul
… FROM [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_profit_center] cp_319 INNER JOIN [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_company_acct] cp_328 ON (cp_319.[profit_center_code]=cp_328.[profit_center_code]) ORDER BY cp_328.[profit_center_code] ASC, cp_328.[company_minor_acct] ASC`.
Rule 2 Labeled XXXX_PR1.rul
… FROM [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_company_acct] cp_328 INNER JOIN [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_profit_center_2010] cp_275 ON (cp_275.[profit_center_code]=cp_328.[profit_center_code_2010]) ORDER BY cp_328.[profit_center_code] ASC, cp_328.[company_minor_acct] ASC`.
Rule 3 Labeled XXXX_PR2.rul
FROM [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_company_acct] cp_328 INNER JOIN [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_profit_center_2011] cp_276 ON (cp_276.[profit_center_code]=cp_328.[profit_center_code_2011]) ORDER BY cp_328.[profit_center_code] ASC, cp_328.[company_minor_acct] ASC`.
These Dimension Build rule files are recreated nightly on 4 different production servers, each one successfully redeploying nightly with zero errors.
So now I need to add the new 2012 tables to the Data Source/MiniSchema, create the joins in the MiniSchema mimicking the joins for the 2010 & 2011 Attribute Dimensions. It would be difficult to demonstrate the joins in the MiniSchema but trust me they are there and this is proven by the additional Dimension Build rule files from the appropriate Hierarchies.
So on our test server, which is configured exactly like all 4 of our production servers, I have begun the creation of the 2012 attribute dimensions. I begin with the FINANCIALS Hierarchy adding 7 new attribute dimensions, 6 that are cross table and one that is inter-table.
At this point no changes have been made to any of the other 3 Hierarchies that contain Attribute dimensions; COMPANY, WELL LOCATION, or PROFIT CENTER. They still look exactly as they did in the current state discussed above. Upon deployment, the FINANCIALS Hierarchy generates , as expected 25 Dimension Build rule files, 6 additional because only 6 were cross table attributes, the 7th was within the anchor table and therefore would be included in the first dimension build rule file. COMPANY still generates 5 Dimension Build rule files, again as expected. WELL LOCATION still generates only the 1 Dimension rule file also as expected. Lastly, PROFIT CENTER also again only generates the 3 Dimension Rule files, however, one has materially changed as noted below:
Rule 1 Labeled XXXX_PRO.rul
…FROM [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_profit_center] cp_319 INNER JOIN [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_company_acct] cp_328 ON ((cp_319.[profit_center_code]=cp_328.[profit_center_code]) AND (cp_328.[profit_center_code]=cp_319.[profit_center_code])) ORDER BY cp_328.[profit_center_code] ASC, cp_328.[company_minor_acct] ASC`.
Rule 2 Labeled XXXX_PR1.rul (This one did not change)
…FROM [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_company_acct] cp_328 INNER JOIN [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_profit_center_2010] cp_275 ON (cp_275.[profit_center_code]=cp_328.[profit_center_code_2010]) ORDER BY cp_328.[profit_center_code] ASC, cp_328.[company_minor_acct] ASC`.
Rule 3 Labeled XXXX_PR2.rul (This one did not change)
…FROM [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_company_acct] cp_328 INNER JOIN [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_profit_center_2011] cp_276 ON (cp_328.[profit_center_code_2011]=cp_276.[profit_center_code]) ORDER BY cp_328.[profit_center_code] ASC, cp_328.[company_minor_acct] ASC`.
The change in Rule 1 above appears to now require something different from the previous deployment and when we run the deployment now it runs forever and ultimately fails, yet no changes have been made to the Hierarchy, no changes have been made to the MiniSchema involving joins to the tables used in the building of the Hierarchy, and no new tables have been added to the data source that would affect this Hierarchy.
Additionally, I have also run each of these incrementally, and the PROFIT CENTER even incrementally still makes the change to the SQL statement shown above.
So finally, to my question, Why and What caused this Dimension Build Rule file to change and ultimately led to deployment failure? Has anyone ever encountered this in Essbase Studio Deployments?

Gurus, anybody anything on this one??
I haave done a small adjustment in the dimension order by which I have eliminated the following error:
Record #40 - Error adding Dynamic calc property to member xxxxxxxxx (3320)
Record #40 - No time dimension defined
But, I have the following new error/warning (cube build successfull in this case) when I made this adjustment:
Record #427 - Error adding Attribute to member PATB4_ADJ-PDA (3320)
The adjustment I made is... I moved TIME dimension up and ACCOUNT dimension below that...so the order I have now is TIME,ACCOUNT,SCENATRIO,XXX,XXXX instead of ACCOUNT,TIME,SCENARIO,XXX,XXXXX ..*would this create any performance issues?*

Attribute dimension

Hi,
can we create groups in attribute dimension using rules file.
we can do it by manually , but i wanna do using rules files.please throw some light .
thanks
kishore

Yes you can, but you can't do in in the same rule that you assign the attributes to base dimensions in. You have to have a seperate rule to build the hierarchy

Duplicate member names allowed dimension build

I have turned on allow duplicate members in a current ASO essbase cube to test how much rework this will require to allow duplicate aliases. After I switched the property on, I was recieving errors when attempting to associate an attribute to a dimension through a dimension build rule. I realized that I needed to use qualified member names in the load file. Here is an example of the file in Parent Child AttributeValue format
[Domestic-PD].[Test_Comm-PD]     [Test_Comm-PD].[0001-PD]      [Test_Attr-MD].[Test1-MD]
So I want to associate the attribue Test1-MD to product 0001-PD below.
Domestic-PD
     Test_Comm-PD
          0001-PD
What ends up happening is something like this
Domestic-PD
     Test_Comm-PD
          0001-PD( [Test_Attr-MD].[Test1-MD]
          [Test_Comm-PD].[0001-PD]
It attaches the attribute to the correct product but then adds an additional member. I don't want it to add the additional member. Any idea on what is happening?
Thanks for any help!

It ended up working in a different format. I changed the data file to like below. I also started over, recopying the outline, turning duplicate members on, so it is possible that there was just something off with the outline earlier.
Test_Comm-PD     0001-PD      [Test_Attr-MD].[Test1-MD]
It probably will have issues if there is a duplicate member but luckily I only will have duplicate aliases.

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 build method

Similar Messages

Maybe you are looking for