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)

Similar Messages

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

Essbase Studio Drill-through for Recursive Hierarchy - Generation 1

I'm using Essbase Studio 11.1.2.3 to build an ASO cube. All my hierarchies are recursive (parent-child). I would like to define a drill-through report and I understand that I have to use the Advanced Settings option to specify my intersections. Now one of my dimensions is optional for the users - they don't have to specify a member (they can leave it at the highest level - dimension name on the spreadsheet). Under 'Advanced Settings' for DT report in Studio I have to specify a Generation value of 2 or greater than 2. How do I enable drill through in cells where one of the dimension is at Gen1 ? Specifying the level number didn't work. I think if you specify Level in 'Advanced Settings', drill through is allowed only if that specified level of the dimension is chosen, if Gen 2 is specified, then drill through is allowed as long as the dimension-members specified are at or above Gen2. But what about Gen1?

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)

SmartView 11.1.2.2-drill down with attribute dimensions

In Smartview 11.1.2.2.300, we have noticed that if we exclude attribute dimensions from our report, then we are able to drill down to Bottom level on all our reports; but if there are attribute dimensions listed, then it throws errors. Is it an option to drill down to bottom level, while keeping the attribute dimensions in the report? Thanks.
Edited by: 937685 on Jan 17, 2013 9:35 AM

According to Oracle that still relates to a timeout error: SmartView Error "XML Load Error: DTD is prohibited [ID 1059964.1]
Update the registry on the client machine with the following settings:
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings]
"ReceiveTimeout"=dword:00075300
"KeepAliveTimeout"=dword:000493e0
"ServerInfoTimeout"=dword:000493e0
You may need to reboot, I've seen it make a difference without the need.
Is this an FDM connection?
Anyway try that.
Steve

Template SQL for EIS Drill-Through

I am trying to figure out the command that I need to add to my template SQL in an EIS drill-through report that will exclude all rows that have a 0 value in my data column when the report is executed. Does anyone have an example of how this can be done?

The $$dimension-COLUMN$$ represents the column that contains your member name in your table and the $$dimension-MEMBERCOLUMN$$ represents the member.
When you run the drill-through report the $$dimension-MEMBERCOLUMN$$ will be replaced by the member referenced in the cross-section.
e.g. if you launch your drill-though on a cell where the product ID is 100-10 then the drill-though will only pull out data for product 100-10
SELECT......WHERE SKU IN (100-10)
Gee

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

Problem with EIS drill through reporting

Hello, Please help me with this. We are using Drill Through reports with EIS 7.1 and Essbase 7.1 in AIX environment. (These are the IBMDB2 Olap versions, not directly from Hyperion.) For some reports when retrieved on a member with more number of children, the Integration server gets killed and we get the following error ESSDTU {ESSNET MESSAGE} Network error [10054]: Cannot Send Data Following is the information in the server log file: [Thu Jul 13 4:39:04 PM 2006] /IS/Listener/0/Informational/1051001/Build-EIS71B168 Received client request Login [Thu Jul 13 4:39:04 PM 2006] /IS/Coordinator/0/Informational/0/Build-EIS71B168 Executed client request 'Login' in 0 seconds [Thu Jul 13 4:39:04 PM 2006] /IS/Worker/1152826749/Informational/0/Build-EIS71B168 Initialization completed, 'Worker' service is online. [Thu Jul 13 4:39:04 PM 2006] /IS/Worker/1152826749/Informational/0/Build-EIS71B168 Received client request Get Drill-Through report [Thu Jul 13 4:39:04 PM 2006] /IS//0x0/1152826749/Informational/0/Build-EIS71B168 Successfully loaded the OLAP Model 'OM1' [Thu Jul 13 4:39:05 PM 2006] /IS//0x0/0/Informational/1051034/Build-EIS71B168 EssbaseAPI: Logging in user [User1] [Thu Jul 13 4:39:05 PM 2006] /IS//0x0/0/Informational/1051035/Build-EIS71B168 EssbaseAPI: Last login on Thursday, July 13, 2006 4:24:33 PM [Thu Jul 13 4:39:06 PM 2006] /IS/Worker/1152826749/Informational/0/Build-EIS71B168 Executed client request 'Get Drill-Through report' in 2 seconds [Thu Jul 13 4:39:07 PM 2006] /IS/Worker/1152826749/Informational/0/Build-EIS71B168 Received client request Get Drill-Through report attributes [Thu Jul 13 4:39:07 PM 2006] /IS/Worker/1152826749/Informational/0/Build-EIS71B168 Executed client request 'Get Drill-Through report attributes' in 0 seconds [Thu Jul 13 4:39:07 PM 2006] /IS/Worker/1152826749/Informational/0/Build-EIS71B168 Received client request Get Drill-Through report data [Thu Jul 13 4:39:07 PM 2006] /IS/Worker/1152826749/Informational/0/Build-EIS71B168 Drill Through Report for Essbase Server:Server1.corp.com Application<img src="i/expressions/face-icon-small-happy.gif" border="0">T1 DB<img src="i/expressions/face-icon-small-happy.gif" border="0">B1 User:User1 [Thu Jul 13 16:39:16 2006] /IS/Server///Informational/0 Unknown flag [JDBC DSN] found, ignoring it/Build-EIS71B168 [Thu Jul 13 16:39:16 2006] /IS/Server///Informational/0 Found Q command line parameter and a value of 128 is set to it/Build-EIS71B168 [Thu Jul 13 16:39:16 2006] /IS/Server///Informational/0 Setting configuration variable, server home, to 'c:\ibm\db2olap\is'/Build-EIS71B168 [Thu Jul 13 16:39:16 2006] /IS/Server///Informational/0 Setting configuration variable, temporary directory, to 'C:\DOCUME~1\malkar\LOCALS~1\Temp'/Build-EIS71B168 [Thu Jul 13 16:39:16 2006] /IS/Server///Informational/0 Setting configuration variable, log file name, to 'c:\ibm\db2olap\is\log\olapisvr.log'/Build-EIS71B168 [Thu Jul 13 16:39:16 2006] /IS/Server///Informational/0 Setting configuration variable, Essbase message database, to 'C:\ibm\db2olap\bin\essbase.mdb'/Build-EIS71B168 [Thu Jul 13 16:39:17 2006] /IS/Coordinator/0/Critical/2002003/Build-EIS71B168 Invalid session identifier, please log in to Essbase Integration Services Server again. [Thu Jul 13 16:39:28 2006] /IS/Coordinator/0/Critical/2002003/Build-EIS71B168 Invalid session identifier, please log in to Essbase Integration Services Server again. Please let me know if this is something to do with the EIS limitations or some setting Thanks Kris

Normally if the drill through report fetches a wrong combination of members or huge amount of members than the way it was designed in the Drill through Report template. The database may fail due to improper query. Check the database and table status. Also fetch the report with proper combination of members.

EIS drill-through performance is slow!!!!

take out the _nospam for email responses....my problem is I'm having horrible performance on an EIS drill-through (SQL 2000 repository). For a query that takes 17 seconds to execute from query analyzer (and from EIS as I can see in the logfile), it takes approx 15 minutes to return the recordset back to the Excel add-in. Is this a bug? It appears that there are hundreds of unnecessary queries being executed after the actual data retrieval that is causing the slowdown. See my logfile with <<<comments inserted>>> below:[Mon Oct 07 16:28:02 2002] /IS/Listener/0/Informational/1051001/Build-I620P0B068Received client request Get Drill-Through report[Mon Oct 07 16:28:02 2002] /IS/Worker/0x0/1034026331/Informational/0/Build-I620P0B068Successfully loaded the OLAP Model 'exp_mod_2.0'[Mon Oct 07 16:28:02 2002] /IS/Worker/1034026331/Informational/0/Build-I620P0B068Executed client request 'Get Drill-Through report' in 0 seconds[Mon Oct 07 16:28:04 2002] /IS/Listener/0/Informational/1051001/Build-I620P0B068Received client request Get Drill-Through report attributes[Mon Oct 07 16:28:04 2002] /IS/Worker/1034026331/Informational/0/Build-I620P0B068Executed client request 'Get Drill-Through report attributes' in 0 seconds[Mon Oct 07 16:28:04 2002] /IS/Listener/0/Informational/1051001/Build-I620P0B068Received client request Get Drill-Through report data[Mon Oct 07 16:28:04 2002] /IS/Timer/0/Informational/0/Build-I620P0B068Initialization completed, 'Timer' service is online.[Mon Oct 07 16:28:04 2002] /IS/Worker/0x0/1034026331/Informational/0/Build-I620P0B068dbo.vw_dim_accts table added to from list due to filter based on that table.[Mon Oct 07 16:28:04 2002] /IS/Worker/0x0/1034026331/Informational/0/Build-I620P0B068dbo.vw_dim_org_div_reg table added to from list due to filter based on that table.[Mon Oct 07 16:28:04 2002] /IS/Worker/0x0/1034026331/Informational/0/Build-I620P0B068dbo.exp_drill table added to from list due to filter based on that table.[Mon Oct 07 16:28:04 2002] /IS/Worker/0x0/1034026331/Informational/0/Build-I620P0B068SELECT DISTINCT a.fiscal_year, a.acct_period, a.company, g.r_system, a.system, g.orig_program, g.reference, a.acct_unit, a.sub_account, a.account, g.acct_amount, g.gltrans_description, g.apdistrib_description, g.invoice, g.base_inv_amt, g.je_type, g.po_line_nbr, g.po_num, g.poline_descr, g.quantity, g.r_item, g.source_code, g.vendor, g.vendor_vname, g.posting_date, g.effect_date, g.update_date, g.r_date, g.cmt_text, g.auto_revFROM dbo.gltrans_sum a, dbo.vw_dim_accts b, dbo.vw_glcalendar c, dbo.vw_dim_org_div_reg d, dbo.vw_dim_org_dist e, dbo.vw_dim_org_AU f, dbo.exp_drill gWHERE a.account = b.gen4AND a.fiscal_year = c.fiscal_yearAND a.company = c.companyAND a.acct_period = c.acct_periodAND a.acct_unit = f.AUAND a.company = g.companyAND a.fiscal_year = g.fiscal_yearAND a.acct_period = g.acct_periodAND a.acct_unit = g.acct_unitAND a.account = g.accountAND a.sub_account = g.sub_accountAND a.system = g.systemAND e.region = d.regionAND f.dist = e.distAND (((b.gen3 = 'RENT&UTILEXP')))AND (((a.company = 4)))AND (((a.fiscal_year = 2002)))AND ((({fn SUBSTRING({fn MONTHNAME(c.per_end_date)}, 1, 3)} = 'Sep')))AND (((d.region = 'API')))GROUP BY a.fiscal_year , a.acct_period , a.company , g.r_system , a.system , g.orig_program , g.reference , a.acct_unit , a.sub_account , a.account , g.acct_amount , g.gltrans_description , g.apdistrib_description , g.invoice , g.base_inv_amt , g.je_type , g.po_line_nbr , g.po_num , g.poline_descr , g.quantity , g.r_item , g.source_code , g.vendor , g.vendor_vname , g.posting_date , g.effect_date , g.update_date , g.r_date , g.cmt_text , g.auto_rev[Mon Oct 07 16:28:04 2002] /IS/Worker/0x0/1034026331/Informational/0/Build-I620P0B068NativeSQL:SELECT DISTINCT a.fiscal_year, a.acct_period, a.company, g.r_system, a.system, g.orig_program, g.reference, a.acct_unit, a.sub_account, a.account, g.acct_amount, g.gltrans_description, g.apdistrib_description, g.invoice, g.base_inv_amt, g.je_type, g.po_line_nbr, g.po_num, g.poline_descr, g.quantity, g.r_item, g.source_code, g.vendor, g.vendor_vname, g.posting_date, g.effect_date, g.update_date, g.r_date, g.cmt_text, g.auto_revFROM dbo.gltrans_sum a, dbo.vw_dim_accts b, dbo.vw_glcalendar c, dbo.vw_dim_org_div_reg d, dbo.vw_dim_org_dist e, dbo.vw_dim_org_AU f, dbo.exp_drill gWHERE a.account = b.gen4AND a.fiscal_year = c.fiscal_yearAND a.company = c.companyAND a.acct_period = c.acct_periodAND a.acct_unit = f.AUAND a.company = g.companyAND a.fiscal_year = g.fiscal_yearAND a.acct_period = g.acct_periodAND a.acct_unit = g.acct_unitAND a.account = g.accountAND a.sub_account = g.sub_accountAND a.system = g.systemAND e.region = d.regionAND f.dist = e.distAND (((b.gen3 = 'RENT&UTILEXP')))AND (((a.company = 4)))AND (((a.fiscal_year = 2002)))AND ((({fn SUBSTRING({fn MONTHNAME(c.per_end_date)}, 1, 3)} = 'Sep')))AND (((d.region = 'API')))GROUP BY a.fiscal_year , a.acct_period , a.company , g.r_system , a.system , g.orig_program , g.reference , a.acct_unit , a.sub_account , a.account , g.acct_amount , g.gltrans_description , g.apdistrib_description , g.invoice , g.base_inv_amt , g.je_type , g.po_line_nbr , g.po_num , g.poline_descr , g.quantity , g.r_item , g.source_code , g.vendor , g.vendor_vname , g.posting_date , g.effect_date , g.update_date , g.r_date , g.cmt_text , g.auto_rev[Mon Oct 07 16:28:21 2002] /IS/Worker/1034026331/Informational/0/Build-I620P0B068Executed client request 'Get Drill-Through report data' in 17 seconds<<< this time (and the result set) is consistent if I execute the above query directly against the repository>>>[Mon Oct 07 16:28:21 2002] /IS/Listener/0/Informational/1051001/Build-I620P0B068Received client request Get Drill-Through report data[Mon Oct 07 16:28:21 2002] /IS/Worker/1034026331/Informational/0/Build-I620P0B068Executed client request 'Get Drill-Through report data' in 0 seconds<<< repeats the last two entries over and over for the next 12 minutes >>>[Mon Oct 07 16:40:23 2002] /IS/Listener/0/Informational/1051001/Build-I620P0B068Received client request Get Drill-Through report data[Mon Oct 07 16:40:23 2002] /IS/Worker/1034026331/Informational/0/Build-I620P0B068Executed client request 'Get Drill-Through report data' in 0 seconds[Mon Oct 07 16:40:23 2002] /IS/Listener/0/Informational/1051001/Build-I620P0B068Received client request Logout[Mon Oct 07 16:40:23 2002] /IS/Worker/1034026331/Informational/0/Build-I620P0B068Executed client request 'Terminate' in 0 seconds[Mon Oct 07 16:40:23 2002] /IS/Coordinator/0/Informational/0/Build-I620P0B068Executed client request 'Logout' in 0 seconds[Mon Oct 07 16:42:58 2002] /IS/Listener/0/Informational/1051001/Build-I620P0B068Received client request Get Log File.

We did see this at a client but the problem has since been fixed; we are not doing the EIS work, but I could ask around to see if there was anything specifid they did to fix the issue..Another symptom we saw at that client is that it took 2-3 minutes to open a modest sized outline built with EIS.. Do you see the same issue?Tim TowApplied OLAP, Inc

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

Workaround for HFM Drill-Through when using custom dimensions ( 4) in FDM

Hi all,
we have the following scenario:
- Target Custom 3 is defined as a combination of Target Product and Target Cost Center
- Target Product needs to be obtained by mapping field "PRODUCT" in the source file
- Target Cost Center needs to be obtained by mapping field "CC" in the source file
So,
One approach would be to enable Custom5 and Custom 6 dimensions in FDM, and configure sequence so these two dims are mapped before custom 3 which has a conditional map to get
values from target c4 and c5 (using varvalues...)
The issue here is that drill-through does not work as the sql query for the intersection is looking for UD5x and UD6X as NULL, N, or [NONE], and these two columns have a value as they were mapped.
Trying to solve this issue, we configured C5 and C6 as lookup dimensions so we could create the mapping tables for them although in order to import data from source file fields we used attr2 and attr3. Besides UD5 and UD6, as expected, were not displayed in the Import and Validate/Export grids
Then the idea was to update the work table with attr2->ud5 and attr3->ud6 in a event script (importaction or befprocmap..) so ud5 and ud6 are mapped.
The problem is that we noticed that ud5 and ud6 are not updated from attributes. It seems that as they are configured as lookup dims, values may be mapped but not copied from work table to tdataseg.
If this would work, then after custom3 is mapped we could set ud5x and ud6x to [none] in order the drill-through query to work.
Having all in custom 3 dim and use mappings on combinations is not desired by the customer as they want to keep product and cc mappings separately.
I was thinking to use a dummy location for product and cost center mappings and then emulate mappings using SQL but would like to avoid this.
Any other suggestion?
Thanks!

The criteria for mapping C3 is:
- If Plan = 6 Then Target C3 = SUBACCOUNT
- If Plan <> 6 AND Account IN range [70000,70999] Then Target C3 = Target CC
- If Plan <> 6 AND Account NOT IN range [70000,70999] Then Target C3 = Target CC_Target Product
Fields in the file
- PLAN
- ACCOUNT
- SUBACCOUNT
- Source CC
- Source Product
So current solution actually is to put that logic in the import format so:
- If Plan = 6 Then Source C3 = SUBACCOUNT
- If Plan <> 6 AND Account IN range [70000,70999] Then Source C3 = "RULE2"
- If Plan <> 6 AND Account NOT IN range [70000,70999] Then Source C3 = "RULE3"
In the mapping of C3, we managed a simple script mapping checking the source C3
If source c3 = RULE 2 -> Target C3 = Target CC
If source C3 = RULE 3 -> Target C3 = Target CC_Target Product
Else Target C3 = source C3 (which is SUBACCOUNT)
C5 (Cost Center) and C6 (Product) are mapped before C3.
In order to make Drill-Through working, we save UD5X and UD6X in ATTR2, ATTR3 so the user can see it, and we set then UD5X and UD6X to [None] so the Drill_Through SQL Query returns the values from FDM. If after loading the user goes to validate step, he will see [None] in C5 and C6 but actually this does not really matter as C3 has already been mapped and is the value to be loaded. If the want to review target product or target cc then they drill down to attribute information.
regards

Dimensions/Fields Displayed on Drill through screen

Is there a way to display additional dimensions/fields on the drill through screen in which you are not loading into the target system?
To elaborate, suppose I have an import file which I have the following fields: entity, account, dept, affiliate, and amount. My target system metadata has a house for all of those fields except dept because we do not load dept. So I go ahead and I set up my import format to capture all the fields except dept which I do not pull in because I wont load it. I load my data and now I drill through from my target system (click on $1000) and FDM launches and I click on the initial screen which shows the $1000 and it opens up the two lines that made up the $1000. On that screen however, I will only see the dimensions/fields that I loaded: Entity, Account, Account Description, Amount. I will not see Dept because I did not bring it in as I am not loading it. I know I can include Dept in the Import Format as an Attribute and click on the amount to show attributes but is there a way to have it on the initial screen? In other words, I want to bring in the field however I do not want to load it to the target system so it will display on the drill through screen?
Deepest apologies if I am doing a poor job articulating the question.

Hello,
Unfortunately there is no way to change the design that you see during Drillback.
The dimensions that are displayed are controlled by the dimensions that are loaded into the target system. Since the target system does not know of these dimensions it is not displayed during drillback.
Thank you,

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.

Date tool calculation dimension is causing duplicated rows in drill through

I am implementing a date tool as per:
http://www.sqlbi.com/articles/datetool-dimension-an-alternative-time-intelligence-implementation
I have my date tool dimension shell with 10 rows, a row for each calculation. I've created the scope statements in the cube. The date tool is working with the calculations I've created.
I've found a problem with drill through in Excel 2013 where it returns duplicate rows. It looks like its a cross join of rows that should be returned by the number of rows (calculations) in my date tool dimension. If I remove the date tool dimension from
the cube I have the correct number of rows so I know it's definitely the cause. I commented out the scope statements to see if that was the problem and it isn't. There must be something else on the configuration that I've missed but I can't spot it. Any ideas?
Thanks Brian
Brian Searle

Seems like this may be the issue
see
http://javierguillen.wordpress.com/2012/03/05/userelationship-and-direction-of-context-propagation/
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

Steps for Drill-through Implementation

Hi,
I am relatively new to Essbase.
We need to implement Drill-through in ESSBASE to drill down to detailed records from Cube to Database.
I have figured out that this setting is present in EIS.
But it will be good if there is any help document from ESSBASE which explains it with an example.
Please suggest if there is any such PDF or URL.
Thanks & Regards,
Gurudatta

Hi Folks,
Finally, I managed to set up the sample application and also could actually see how drill-through works in excel.
But I was disappointed as this example in sample database just provides attribute-type details on drill through.
Our requirement is to drill down to lower granularity.
For example, we will have product group in the cube outline to keep its size limited and expect that when users drill-down in excel it goes down to actual product level amounts. Unfortunately in sample database, the facts in the cube are already at the lowest level (i.e. State). I would have imagined - to match with our requirement - that cube stores fact at the level of region and goes to database for fetching the state level facts.
Is this possible in Essbase?
Thanks & Regards,
Gurudatta

Drill through for Attribute dimensions

Similar Messages

Maybe you are looking for