Format Dimensions in Resulting Drill Across Spreadsheet, Linked Partition

Hello,
Does anyone know if / how I can format the order of the dimensions that appear in the Source of a linked partition, when drilling across from Target to Source in the essbase excel add-in? I am in version 9.3.1, using a linked partition going from aggregate storage to aggregate storage.
An example: I have Cube "A" at the intersection where I can use my linked partition to drill across to Cube "B". When I do so, the drill works as expected. However I would like to specify an order for the dimensions of Cube "B" to show up in, in the new excel worksheet. Right now I can't determine the default order that is appearing, (it is not largest dense or largest sparse first). The order is consistently the same though, regardless of the format of the intersection of Cube A when I initiate the drill across.
I want to specify an order mostly because I want to try to automatically drill to generation 2 on a dimension in Cube B that is not in Cube A. I haven't been able to do this with the Area and Mapping defintions in the partition yet. (Maybe that is my best bet) I'm hoping there is a config file or something that I can use to manipulate how the new worksheet appears.
Can't find anything in the documentation yet.
Any thoughts would be appreciated.
Thanks,
Carmen

user616766 wrote:
Does anyone know if / how I can format the order of the dimensions that appear in the Source of a linked partition, when drilling across from Target to Source in the essbase excel add-in? I am in version 9.3.1, using a linked partition going from aggregate storage to aggregate storage.I don't believe you can control the order/etc of the dimensions in the linked partition drill-through. I just took a look at both the Java API code for the IEssLinkedPartition class and I didn't see any methods/properties that give you any information about the orientation of the members (or even any mention of the members at the datapoint).
I want to specify an order mostly because I want to try to automatically drill to generation 2 on a dimension in Cube B that is not in Cube A. I haven't been able to do this with the Area and Mapping defintions in the partition yet. (Maybe that is my best bet) I'm hoping there is a config file or something that I can use to manipulate how the new worksheet appears.The second problem you will have is automatically drilling to generation 2. The classic add-in gives you no notifications, or 'events', to tell you something has happened.
Both of these issues are trivial to solve in our Dodeca product. Our 'intelligent navigation' feature allows you to navigate from a datapoint to a new view/report and will automatically package the members represented at the datapoint as a tokens that represent the point of view. The target view/report, which you can layout with the dimensionality located whereever you wish and can connect automatically to your 'linked partition' drill-through database, then places those tokens in the location you indicate when the view/report opens. As a bonus, you do not need to specify a linked partition to have this drill-through behavior. Finally, there is robust event support so you can have the zoom-in occur automatically. You can learn more about Dodeca at our website, www.appliedolap.com.
Tim Tow
Applied OLAP, Inc

Similar Messages

Drill Across Essbase/Multidimensional cubes with a conformed dimension

Hi Guys,
Does anyone have any ideas/pointers on how to implement drill across on Essbase cubes or Multidimensional sources in general.
For Eg:
Cube 1 with aggregate data at Country Level
Cube 2 with detail data at City Level
Geography is the conformed dimension here.
I need to implement drill across from the Country level in the Geography Hierarchy to go to the City level, across cubes. Facing a problem desinging it in the BMM.
Any help would be appreciated.
thanks,
jboy

We're discussing this already in your other thread? Different drill paths for a common Essbase Dimension with varied depth
Close this one please...not necessary.
Cheers,
C.

Drilling across in Hyperion Financial Reporting

Hello,
We are migrating a few reports from BO to HFR. The BO reports have a functionality to drill across another dimension. Does anyone have an idea about how to implement the drill across functionality in HFR.
Thanks,

HFR supports two kinds of "drilling"
Related content links allow you to link FR with other Hyperion products for more Ad hoc analysis.
Cell document links allow you to link actual reports or documents with a particular HFR cell.
Hope this helps,
Brian Chow

Error formula SUMCT with drill across.

Hello everyone,
I have a problem with the formula SUMCT.
A formula has been defined applying the SUMCT operator to the 0???? index 0DEB_CRE_LC.
The 0COSTELMNT characteristic is on the query rows, and a hierarchy is active on the
cost element.
When the query is executed, the result of the SUMCT operator is correctely calculated.
However, if an additional characteristic (0BUS_AREA) is drilled across, the result of SUMCT
is 0 for some hierarchy nodes.
Nevertheless, the result is correct for all hierarchy nodes when the same characteristic is drilled down.

The documentation about the [percentage functions|http://help.sap.com/saphelp_nw70/helpdata/en/e2/16f13a2f160f28e10000000a114084/frameset.htm] (which is referred by the SUMCT documentation) explains that:
If a characteristic has been drilled down in both the rows and the columns, this reference is not unique. The system displays a warning and the relevant symbol for Data Does Not Exist.
[SAP Note 164352 - Norming, Normalization / Output in percent (SUMCT, %CT)|https://service.sap.com/sap/support/notes/164352] points out that:
When you use Function 'NORMING' / 'characteristic' -> 'Normalize to' -> 'Result' / 'Calculate single value as - norming...' a warning may be displayed: "Could not carry out all normings". The same message may occur when the formula operators %CT, %GT, %RT, SUMCT, SUMGT or SUMRT are used.
Norming to 'Result' is not unique in lists which are expanded twice (both horizontally and vertically) since you could do the norming for both the column totals and the line totals.
It is possible to determine the direction in which the system calculates ('calculate along the rows axis or the columns axis') for normalization or cumulation (definable in the properties of a structure element).
However, for SUMCT operations in Business Warehouse 3.X releases, there is no alternative. Changes are planned for the upcoming BW release.
Though the suggestion works for the normalization issue, it doesn't solve the SUMCT problem, even when working with BI 7.0.
Has anyone some info about this point? Are the promised changes to be released soon?
Cheers, [Davide|https://wiki.sdn.sap.com/wiki/display/profile/Davide+Cavallari]
Edited by: Davide Cavallari on Mar 3, 2008 2:52 PM

Drill across leads to 'X' in %CT function

I am using the function %CT which gives me the share of a key figure against the subtotal.
This works beautifully, except when I try to drill across.
Drill across results into u2018Xu2019 values.
Example:
          KF 1   %CT
A        2         33%
B        4         66%
Total   6       100%
KF1 can be split in Y / N by drilling across. I would expect:
          KF 1     KF1     %CT     %CT
          Y           N          Y          N
A        1           1         25%     50%
B        3           1          75%    50%
Total   4          2         100%   100%
But instead the % show u2018Xu2019u2026.
Does anybody know what the problem could be?
Thanks,
Jan.

Hi Jan
X comes when there is not assigned value.
In your case , it is unable to calculate when KF is drilled down / accross with Y/N. Thats the reason why 'X' is coming.
Cheers
Chanda

Do Not Expand on Drill Across/Down

Hi All,
I am having Two Restricted KeyFigures Called Short Term and Long Term. The Short term is restricted with Fiscal Month(Say X) for a range of one year and the Long term is restricted with the same variable but Greater than Or Equal X. So the Long term contains lots of Data as the infocube has the future data also.
Now the problem is when I do a Drill Across/Down on Fiscal Month the result exceeds the Microsoft Excel Limitations(Colunms 255).
Is there any way that Restricted KeyFigure ' Long term' should not expand when i do a drill across/down.that is how can i disable the drill across function on the Long Term Restricted key figure.
Your ideas will be appriciated with points.
Thanks

Hi,
Try this:
Take a Virtual hierarchy on Fiscal year/period characterstic (which you have taken in the free characterstic area). So it will avoid display of all Individual values at a time. User can drill down on the hierarchy , if he want to do it. That also, will alow to drill down for a specific year and not at a time all.
With rgds,
Anil Kumar Sharma .P

From Drill Down to Drill Across

Hi Forum,
I'm using drill down from parent to child of the account dimesion.
I'd like also drill across dimensions.
For example, I have a report by account and I'd like drill to flow dimension. Cause i don't want to see the flow dimension for all account. The user want to see the flow details when he means that is necessary see it (unpredictable).
Is it possible? If yes how it works?
Thanks
Best regards
Gianluca

Hi,
Im not too sure, when you say drill across dimensions....
My suggestion accoridng to my undertanding is to maintain a property called flow against in acct dimension and populate it with a "Y" for account ids for which you want to display the flow dimension.
Use simple IF formula in your control sheet or anyother excel aoning with your EVDRE sheet like below and apply the same inn your flow dimension expansion.
If Flow_Property of Acct is Y
then
Flow_ALL in Expansion .
else
flow_none.
Also, If it is not based on accounts, and you wantto kae it dynamic, populate it with Flow_None always and give the user the option of selecting which accts he wants to select a flow id.
this can be done with the help of excel macro and the same excel formula as above.
hope this helps
sridhar

Drill across (joining facts) using Discoverer

Hi,
I've read a few books and article on DW talking about drilling across. It seems a good idea to build multiple star schemas with "conforming" dimensions and then join fact tables (drill across) when needed.
I have tried this solution, and afer a few tests, got to the conclusion that it is preferable to UNION ALL the related facts using a view or a custom folder. Of course this solution is less flexible because we need to find all the required combinations of facts.
Any comments?

OK,
I have 3 dimensions : D1, D2, D3 and 2 facts : F1, F2.
Dimensions D1, D2 are related to fact F1.
Dimensions D1, D2, D2 are related to fact F2.
I want to query on fact F2 based on values of dimensions D1 and D2, and then join F1 to get corresponding measures.
When running the query I get the following error:
Invalid combination of joins using different join keys - query cannot be resolved.
I use Oracle Discoverer 9.0.2.53.12.
What would be the best way to work around this restriction?

Drilling Across in Discoverer

Discoverer 10.1.2.X
We have datamarts which have uniformly conforming dimensions and the facts and dimensions are laid out in a star schema.
Point of Sale(POS) is a separate fact table and Shipments is a separate fact table too. Stores belong to the customer dimension and Dates belong to the calendar dimension. Both POS and Shipments share the stores and calendar dimension. There is appropriate foreign key relation ship between the fact and dimension tables in the database too.
POS
\|/
|
Stores
|
/|\
Shipments
POS
\|/
|
Calendar
|
/|\
Shipments
The problem:
Now I would like to Drill across in Discoverer i.e. for a given store and date range I would like to get two measures from different facts -> POS and Shipments by day. When I execute the report from Discoverer, the query that is generated looks like the one pasted below and I don't think this is a proper query because cus_dimn_customer and day_dimn_cal_hdl do not have any relationship. The query also runs very long-
SELECT fx100 AS e100048, fx101 AS e100135, SUM (fx107) AS e100620_sum,
SUM (fx102) AS e100363_sum
FROM (SELECT SUM (o100611.quantity) AS fx107, o100611.cus_key AS fx108,
o100611.day_key AS fx109
FROM ebiprod.bil_fact_billing_v o100611
GROUP BY o100611.day_key, o100611.cus_key),
(SELECT SUM (o100357.sale_qty) AS fx102, o100357.cus_key AS fx104,
o100357.day_key AS fx106
FROM ebiprod.pos_fact_retail_sales_v o100357
GROUP BY o100357.day_key, o100357.cus_key),
(SELECT o100019.chain_code AS fx100, o100107.cal_date AS fx101,
o100019.cus_key AS fx103, o100107.day_key AS fx105
FROM ebiprod.cus_dimn_customer_v o100019,
ebiprod.day_dimn_cal_hdl_v o100107
WHERE (o100107.cal_date =
TO_DATE ('20050521000000', 'YYYYMMDDHH24MISS')
AND (o100019.chain_code = 278))
WHERE ((fx103 = fx108(+) AND fx105 = fx109(+))
AND (fx103 = fx104(+) AND fx105 = fx106(+)))
GROUP BY fx101, fx100
Questions:
1) Is this an example of Fantrap ? i.e. Discoverer detects a fantrap and creates the query accordingly to resolve the Fantrap.
2) I don't think the outer join is needed and I do not understand why the conditions created in the report cannot be applied to every nested SQL. How do I change the way Discoverer generates queries ?
3) If any one has experience in enabling Drilling across in Discoverer and how it is implemented ?
Any help would be appreciated
Thanks
Manav

The joins in the SQL are controlled by the joins made in the admin edition. A check box determines if it is outer joni, one to one, one to many. The outer join would not be present unless it was present in your Business area. Click the options tab in the join in Admin.
As for a fan trap, I have always thought of it as a cyclical join. Discoverer can't determine which path to take to get the correct information. If you have the option turned on it will not allow you to build the workbook if a join such as this is determined.
The query you attached appears to be a crosstab in-line view. Try the workbook in a page detail and see if the query time improves.
One other method I have used is a hierarchy in a DW with multipath branches. This allows for drilling from summary into detail down a predetermined path. It has worked well for me but does take some effort in design to make sure the drill down is ALWAYS true, no exceptions.
HTH.

What is the difference between drill across and drill down?

Hi Friends,
Please give a clarification about Drill across,Drill down,Drill through With Examples?
Thanks in Advance
Rani

Hi,
1 - Drill Down: When we are at a higher level of aggregation and want to go to a lower level within the same size. Ex Time Dimension: year to quarter to month ...
2 - Drill UP: When we are in a lower level of aggregation and want to go further in the same size. Ex Time Dimension: trimenstre for months to years.
3-Drill Across: When we are in a lower level of aggregation and want to go to a minor or vice versa, in different environments. Ex Dimenão Time: year quarter in a Data Mart for Essbase Dimension in Time: months in a DW in a relational database.
4 - Drill Through: When we are at a level of aggregation within any one dimension of this level and go to another in another dimension. Ex Product dimension: product name to Dimension Client: client name, or want to know what products or those that customers bought.
For more Kindly refer:
http://gerardnico.com/wiki/dat/obiee/drill
http://gerardnico.com/wiki/analytic/drill_down_up
http://gerardnico.com/wiki/analytic/drill_across
http://gerardnico.com/wiki/analytic/olap_operation
http://obieetips.blogspot.com/2009/05/obiee-drill-throughdrill-down.html
Thanks
Deva
Edited by: Devarasu on Dec 12, 2011 4:28 PM

Endeca SearchAdjustments cartridge and Dimension Search Results cartridge

Hi
In Endeca Discover demo, if search word is 'codac'
SearchAdjustments adjusts 'codac' to 'codec' (it doesn't adjusts to 'Kodac' )
Dimension Search Results find 'Kodac' dimension.
Can anyone explain each logic ? Where can I configure these behavior ?
Regards

You can find out details on the logic and configuration options in Chapter Five of the Advanced Developer's Guide here: http://docs.oracle.com/cd/E48636_01/Mdex.6412/pdf/AdvDevGuide.pdf .
HTH
Michael

Single result set across multiple tables

Hi - what's the best way to perform a single query that can pull
a single result set across multiple tables, ie., a master table
containing subject details and child table containing multiple
records with detail.
I know how to do this for two columns in the same table via
indexing, but how about across tables?
Cheers,
John

I am not sure if I understood your question, but you can use
Intermedia Text with USER_DATA_STORE to create an index with data
source from multiple tables.
(see technet.oracle.com -> products -> oracle text)
Thomas

Drill Across fields mapping with calculate field

I create a calculation field in one view, then when config drill across, i set the calculation field to mapping to a Parameter of target view
Save report
Then, i open the report in view mode, click the view which config drill across, it get JavaScript error in DrillAcrossModifierManager.js line 272, Object required

Hi,
I'm using BAM 11.1.1.4, and I have a report wich calls another report through DrillAcross.
Both reports have no calculated fields and I am receiving the same error message:
Mensagem: object required
Linha: 273
Caractere: 5
Código: 0
URI: http://server:9001/OracleBAM/13846/reportserver/scripts/drilling/drillacross/DrillAcrossModifierManager.js
Any idea about the cause of this error?
Thanks.
Luciano Gomes

Proc fails with sqlcheck=full accessing tables across a link to non 11g db

I am trying to compile programs that were upgraded from 9i to 11g and having issues whenever I try to compile code that accesses non 11g databases across a link when sqlcheck is anything other then syntax.
If I have a select such as
select distinct a.ID_NUM, b.value1, b.value2, ...
from table_a a, table_b@external_db b
where a.ID_NUM = b.ID_NUM and a.process_name='REPORTS';
This compiler sits and hangs for a few minutes then aborts. This problem occurs in Pro*C, Pro*Cobol as well as Oracle Forms.
The query works fine under sql*plus. The compiler just can't handle it.
A work around under Pro*C is to use sqlcheck=syntax when compiling any code that accesses across a link. However this isn't a good workaround since it won't catch errors such as a typo in a column. This also won't work in forms, but a work around is to convert the selects into a view. However that isn't a good workaround due to the number of queries that would need changing.
Has anyone else seen this issue and found out what needs changed in the Database for this to work. I tried searching Oracle's web site but couldn't find any solution.
Edited by: user7525803 on Jun 25, 2009 8:10 AM
Edited by: user7525803 on Jun 25, 2009 8:15 AM

ittichai wrote:
Rich,
I searched metalink for your issue. This may be a bug in 3.1 which will be fixed in 4.0. Please see Doc ID 740581.1 Database Link Tables Do NoT Show Up In Table Drop Down List In Apex. There is a workaround mentioned in the document.
I'm not sure why I never thought of searching MetaLink, but thanks for the pointer! It doesn't match my circumstances, however. The Bug smells like a view not being queried in the APEX development tool itself -- i.e. the IDE's coding needs changing, not necessarily those apps created with the IDE.
I'm working on getting you access to my hosted app...
Thanks,
Rich

How to drill across sections in Dashboards

I hav got this through this site.
(if i click on a department name in department section in dashboard, the corresponding employees details should be shown in the adjacent column/section without rendering to a new page)
http://oraclebizint.wordpress.com/2007/12/26/oracle-bi-ee-101332-drills-across-sections-in-a-dashboard/
i hav got the total thing done.
i'm doing this for an department table on department name.
for which when i drill on department name, corresponding employees list should be shown.
my problem is
1. if the dept name contains a spaces like 'Human Resources', then the URL is taking only Human and its ignoring the rest.(if it doesn't contain spaces, its showing correctly.!)
the URL looks like this
http://l3f0372:9704/analytics/saw.dll?GO&path=/shared/New/3.Emp&Action=Navigate&P0=1&P1=eq&P2=Departments.%22Department%20Name%22&P3=Human
2. the drill down can be implemented on varchar datatypes only.
but not on number types like dept_id. Is there any way to that?
Edited by: user10564344 on Nov 23, 2008 10:48 PM

Thank you Naresh for responding to my problem..
But, if we use Navigate, the drilling will be to a new page.
but the client requirement is like this.
intially there are two sections, one shows dept details and other shows emp details(of all depts)
when we click on a particular dept name, the emp details of that department only should be shown and in the same section only(i.e., without navigating to a diff page).
the procedure i'd got from the website mentioned in the earlier post worked fine with the department name containing no spaces.
but when there is a space in the department name(ex.Human Resources),, the URL is taking till Human only(due to anchor tag in column properties on dept name).here the anchor tag is used to call emp details section and pass the respective dept name called.But when a space occurs in URL, that anchor tag is taking till a space.
(ex.: http://l3f0372:9704/analytics/saw.dll?GO&path=/shared/New/3.Emp&Action=Navigate&P0=1&P1=eq&P2=Departments.%22Department%20Name%22&P3=Human )
so, how to pass a value with space using anchor tag dynamically..?
Thanks in advance..:)

Format Dimensions in Resulting Drill Across Spreadsheet, Linked Partition

Similar Messages

Maybe you are looking for