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

Similar Messages

  • How to filter records in EIS drill through using template SQL

    Hi,
    I'm looking for an option to filter records in EIS drill through using Template SQL.
    For eg: If we user runs drill through on 2011, it should restrict display of Jan & Feb and should display records for other months.
    I tried using NOT IN clause, but got an error.
    Can any one help me in understanding how this needs to be defined in template SQL
    Thanks in advance

    Hi Glenn,
    I'm able to filter the records for specific periods.
    However, I'm facing another problem now.
    When I try to run drill through I get 'OLAP_error (1192025): Unknown Error: Not a valid Entry' error.
    This is happening when I include condition as ((($$ab.ACCOUNT_CODE-COLUMN $$) IN ($$Account-VALUE$$)))
    Here, ACCOUNT_CODE is field from Account dimension table and 'Account' is the name of the dimension.
    If I remove this statement and run drill through, it runs but shows data for all accounts (irrespective of the Account selected)resulting in incorrect data.
    Our RDBMS is Oracle. Can you please help me with this
    Thanks

  • EIS drill through reports in Analyzer

    I'm having trouble pulling SQL drill through reports defined in EIS when using Analyzer. I can pull the report when I'm in Excel, but when I go into Analyzer and double click, I get the related content box to open, but no links to the drill through report.<BR><BR>I did some searching on the Hyperion support site and found an entry in the knowledge base that said the Grid API option had to be turned on for this functionality to work. Of course there was no mention of how to turn the Grid API on and I have not been successful in finding anything in the install guide or the admin guide.<BR><BR>I'm using Essbase 7.1.5 with EIS 7.1.2 and Analyzer 7.2.5.<BR><BR>Is anyone using Analyzer to successfully pull EIS drill through reports?<BR>Did you have to turn on the Grid API option?<BR>How is this feature turned on?<BR>Or, any other suggestions?<BR><BR>TIA

    <p>Hi,</p><p> </p><p>I am also facing few issues related to AIS:</p><p> </p><p>I am unable to use Drill Through</p><p> </p><p>(1) Smart View: It is asking for Connections and i am unable toprovide Shared Services Provider Information. It throws an error.In case i use URL as add feature then it asks for credential butstill no luck</p><p> </p><p>(2) Then i tried to used Add-In Excel and (This is my 1st time):When i double click on the data figure based on Intersaction leveli defined, it is taking me LRO's and now i don't know hoe toproceed further</p><p> </p><p>Can anybody help me?</p>

  • *****EIS : Drill through Report Error while excel data retre

    Dear All,
    could you please help me in the below error . When i tried to get the drill through reports in excel add-in ,
    i am getting the below error . When i had look into EIS log, its generating dynamic query for this drill through reports .
    [NCR][ODBC Teradata][Teradata Database] Syntax error- expected something between the word '<<Databasename>>' and the word 'ai'.Unable to get catalog string.
    Thanks in advance .
    M

    You are saying the dynamic query was generated, did you copy the query and tried to execute it in the database client. Check the SQl for any errors and also in the did you see any SQL errors?

  • 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

  • EIS drill through - transactional data

    Currently on Essbase 6.5.4.We currently have a need to be able to "drill down" to General Ledger transactional data that is stored in our data warehouse. (i.e A/P trasactions etc..) Is this possble through EIS without having to populate Essbase outlines or Essbase data via EIS?Thank You

    You can do it two ways. 1) Through EIS drill-through. This will allow you to pull in other information that isn't or can't be in the outline (like adresses, product owner...). The draw back is that it produces an unstructured output and support is not universal. 2) Hybrid Analysis. This is for mor granular data that you do not want to load into Essbase. The dimensional members will be in Essbase, but the data will only reside in your source system. You can now have a significantly larger/more granular outline without impacting load and calc times. The drawback is that it is an extension of the cube and must be constrained by the dimensions (can not bring in other types of data that is not in the Essbase outline).Rich [email protected]

  • EIS Drill-Through to Transactional Data

    Hi!Is there a quick way to retrieve transactional fact data(non-summarized)from the fact table when drilling through in the Essbase Spreadsheet Add-in ? Have set up a drill through report through EIS, but it doesn't retrieve fact table columns even though the Template SQL was modified. Thanks in advance

    We have two SQL tables, Detail and Summary. In EIS, our Model has both tabels joined as the fact table. When you create the Drill Thru report you select the fields from the Detail table but the SQL logic still looks at the summary table. Note for excel, when you drill thru make sure each record in detail is unique or excel will suppress. we had to add a field to get all record to display in excel.

  • EIS Drill Through Essnet error message.

    We are using EIS to anable drill through from Excel. I've just set up some new drill through reports, and they work fine except when you try and drill through at GEN 1 on a particular sparse dimension. The dimension isn't specified in the "OLAP intersections Levels" as we want the report to show all results for that dimension.
    The error message that gets returned is {ESSNET MESSAGE} - in a box with ESSDTU in the left hand corner.
    Thanks
    Paul

    You are saying the dynamic query was generated, did you copy the query and tried to execute it in the database client. Check the SQl for any errors and also in the did you see any SQL errors?

  • Problem with EIS drill through reporting

    Hello,<BR><BR>Please help me with this.<BR><BR>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<BR><BR>ESSDTU<BR>{ESSNET MESSAGE} Network error [10054]: Cannot Send Data<BR><BR>Following is the information in the server log file:<BR><BR>[Thu Jul 13 4:39:04 PM 2006] /IS/Listener/0/Informational/1051001/Build-EIS71B168<BR>Received client request Login<BR><BR>[Thu Jul 13 4:39:04 PM 2006] /IS/Coordinator/0/Informational/0/Build-EIS71B168<BR>Executed client request 'Login' in 0 seconds<BR><BR>[Thu Jul 13 4:39:04 PM 2006] /IS/Worker/1152826749/Informational/0/Build-EIS71B168<BR>Initialization completed, 'Worker' service is online.<BR><BR>[Thu Jul 13 4:39:04 PM 2006] /IS/Worker/1152826749/Informational/0/Build-EIS71B168<BR>Received client request Get Drill-Through report<BR><BR>[Thu Jul 13 4:39:04 PM 2006] /IS//0x0/1152826749/Informational/0/Build-EIS71B168<BR>Successfully loaded the OLAP Model 'OM1'<BR><BR>[Thu Jul 13 4:39:05 PM 2006] /IS//0x0/0/Informational/1051034/Build-EIS71B168<BR>EssbaseAPI: Logging in user [User1]<BR><BR>[Thu Jul 13 4:39:05 PM 2006] /IS//0x0/0/Informational/1051035/Build-EIS71B168<BR>EssbaseAPI: Last login on Thursday, July 13, 2006 4:24:33 PM<BR><BR>[Thu Jul 13 4:39:06 PM 2006] /IS/Worker/1152826749/Informational/0/Build-EIS71B168<BR>Executed client request 'Get Drill-Through report' in 2 seconds<BR><BR>[Thu Jul 13 4:39:07 PM 2006] /IS/Worker/1152826749/Informational/0/Build-EIS71B168<BR>Received client request Get Drill-Through report attributes<BR><BR>[Thu Jul 13 4:39:07 PM 2006] /IS/Worker/1152826749/Informational/0/Build-EIS71B168<BR>Executed client request 'Get Drill-Through report attributes' in 0 seconds<BR><BR>[Thu Jul 13 4:39:07 PM 2006] /IS/Worker/1152826749/Informational/0/Build-EIS71B168<BR>Received client request Get Drill-Through report data<BR><BR>[Thu Jul 13 4:39:07 PM 2006] /IS/Worker/1152826749/Informational/0/Build-EIS71B168<BR>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<BR><BR>[Thu Jul 13 16:39:16 2006] /IS/Server///Informational/0<BR>Unknown flag [JDBC DSN] found, ignoring it/Build-EIS71B168<BR><BR>[Thu Jul 13 16:39:16 2006] /IS/Server///Informational/0<BR>Found Q command line parameter and a value of 128 is set to it/Build-EIS71B168<BR><BR>[Thu Jul 13 16:39:16 2006] /IS/Server///Informational/0<BR>Setting configuration variable, server home, to 'c:\ibm\db2olap\is'/Build-EIS71B168<BR><BR>[Thu Jul 13 16:39:16 2006] /IS/Server///Informational/0<BR>Setting configuration variable, temporary directory, to 'C:\DOCUME~1\malkar\LOCALS~1\Temp'/Build-EIS71B168<BR><BR>[Thu Jul 13 16:39:16 2006] /IS/Server///Informational/0<BR>Setting configuration variable, log file name, to 'c:\ibm\db2olap\is\log\olapisvr.log'/Build-EIS71B168<BR><BR>[Thu Jul 13 16:39:16 2006] /IS/Server///Informational/0<BR>Setting configuration variable, Essbase message database, to 'C:\ibm\db2olap\bin\essbase.mdb'/Build-EIS71B168<BR><BR>[Thu Jul 13 16:39:17 2006] /IS/Coordinator/0/Critical/2002003/Build-EIS71B168<BR>Invalid session identifier, please log in to Essbase Integration Services Server again.<BR><BR>[Thu Jul 13 16:39:28 2006] /IS/Coordinator/0/Critical/2002003/Build-EIS71B168<BR>Invalid session identifier, please log in to Essbase Integration Services Server again.<BR><BR><BR>Please let me know if this is something to do with the EIS limitations or some setting<BR>Thanks<BR>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.

  • 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

  • SQL statement in Drill-Through

    Hi, when you make a drill-through in excel add-in, is some way to get sql statement in excel? without open the EIS console.
    I need this because Drill-through don't work well in a metaoutline with filter IN, so the user can use the query to execute the sql statement directly in the database.

    there is no functionality to get the SQL that is about to be executed in Excel. There is a way to edit the columns or add filtering, but you really don't get the SQL statement.
    You would have to design it yourself. You could grab the sql statement that is generated in the metaoutline and bring it into excel and have a macro that does the replacements.

  • EIS drill through report build

    Hi,<BR><BR>I want to create multiple drill through reports using EIS. But looks like I need to create all the required reports before I build and load the cube. Once I have built the cube using EIS, I cannot go in the metaoutline and add new drill through reports. Is this true, or am I missing something? <BR>So whenever I need to add new reports for drill through, do I need to build the cube all over again?<BR><BR>Thanks<BR>RMP

    No, you can open your metaoutline and build your drill through report and then run an update that just refreshes the drill through reports without having to rebuild or reload the cube.

  • ITS Enablign for BPC drill through

    I am looking for document on how to enable ITS on ECC, BW servers so that BPC drill through can be connected.
    Can any one tell me where to find the document for ITS enabling.

    Hi,
    With SAP BPC M you don't have the ability to do drill trough into ECC.
    Or at least nothing straight forward. You can build connection to extract data from from ECC into SQL table and after that to provide ability to do drill trough into this sql table but it isn't a direct connection to ECC system.
    Kind Regards
    Sorin Radulescu

  • EIS Drill through reports should be disabled at #MISSING data cell

    Hi,
    I have working on Oracle Essbase Integration server(EIS) 11.1.1.3. I have developed the 2 drill-through reports.
    Every thing is working fine. Using smart view, users are able to access the drill-through report.
    As an another requirement, if there is no data(#MISSING) for any member combination in Essbase, Drill through report should not be enabled for this combination in smartview at retrieve.
    How can I handle this requirement? In OLAP Intersection levels, only dimensions’slevel/generation can be specified.
    Please help me on this. It is very urgent for us. Quick help will be highly appreciated.
    Thanks & Regards,
    Mohit Jain

    Hi Gary,
    I think its the latter. I've been asked on more thant one project to code things that prevent users from doing things that otherwise wouldn't make sense to do. Within the last year I was actually asked to configure things "as if I was providing functionality for 2 ^nd^ graders". At least, based on experience, this is how I relate to the OP's request.
    I agree, its absolutely silly (and frustrating ) that users would try to drill through on a #missing cell and not see anything. What's worse, depending on where the drill through goes, and how its set up, users might drill on #Missing and actually see data! Yikes! Now in an experiential sense, the users can expect to see data where data ought not be.
    So sometimes its just easier to just remove the button altogether than to have to explain when and why it can be used, and why when it's not used that way it did what it did. And users being part of the driver behind project requirements, don't want to hear "because you're not supposed to".
    Hopefully the OP will clarify and we can provide what s/he's looking for.
    regards,
    Robb Salzmann

  • EIS Drill Through Reports

    Hi,
    Working with Drill Through reports on essbase 9.3.1. I have defined 10 drill thru reports in EIS because of mulitple hierarchies in some dimensions that needed to be specified. I created 1 from scratch and then copied it and modified OLAP intersections as needed, typically it was just 1 dimension that I needed to delete and re-add using a different child.
    Some simple drill thru retrievals are working just fine, while others are causing me to receive an error...
    {ESSNET MESSAGE} Network error [10054]: Cannot Send Data
    Why would some report retrievals work, and others get this message?
    Any ideas?
    TIA,
    Robert

    Not a problem.. http://timtows-hyperion-blog.blogspot.com/2007/12/essbase-api-error-fix-geeky.html
    Remember, you have to reboot the machine(s) where you make changes for them to take effect.. If your EIS server is also Windows (and on a different server), do the same thing there.
    We see this issue all the time with the Outline Extractor as it makes many, many requests to the Essbase server (and each one uses a port that is not released by Windows for some time).. In fact, I am currently writing some new caching functionality into our Dodeca-Essbase server and am putting a configurable delay into the code so the code doesn't call the server too quickly (but, of course, this is something that runs in the background, so performance isn't a huge issue in that case)..
    Let us know if it fixes your issue.
    Tim Tow
    Applied OLAP, Inc

Maybe you are looking for