2 facts in a single gauge/ pie

Hi,
I have 2 facts. One is the estimated time and other is the actual time taken. My requirement is to show the actual as a slice of estimated time
But if I click on the pie in the results view, it shows 2 pies corresponding to these 2 facts. I want the pie to show estimated time and actual time as a slice of it.
Any suggestions are appreciated.

Here you go...
In my example, I'm taking Region, Estimated Time, Actual Time.
Now in answers create 2 measures:
1) Actual Time % = (Actual Time/ Estimated Time) * 100
2) Estimated Time - Actual Time % = (Actual Time/ Actual Time) * 100 - (Actual Time/ Estimated Time) * 100
Now, use these above 5 columns in pie chart:
Check the checkbox for region as Legend axis
Check the checkboxes for Actual Time % & Estimated Time - Actual Time % as Pie Values axis
** Make sure in Pie Chart Advance Properties you show value as 'Actual Value' and NOT 'Percent Value'
This will give you Actual Time % as a slice of complete estimated time which is 100 % here. Rest slice is Estimated Time - Actual Time %. In total pie can be just 100%. So, here Actual Time % + Estimated Time - Actual Time % = 100%.
You are calculating Actual Time % as total of 100 %(Estimated Value)
Hope this helps

Similar Messages

Multi fact columns to Single fact column

Hi,
We have fact table which stored the data in monthly wise fact columns.
Ex:
Jan
Feb
Mar
Apr
May
Jun
July
Aug
Sep
Oct
Nov
Dec
100
200
150
250
223
1212
171
12123
31123
112
2113
1123
150
223
222
142
1354
1567
452
763
41733
441
1211
1213
333
222
55
256
455
445
752
4752
45214
114
8122
4555
My requirement, We have convert all month fact columns into a single month fact column.
How to achive this. Kindly Let me know.

It rather seems that you don't understand his input or the concept of LTSs.
You create 12 LTS, each using the same physical table as a source.
Then you create one single column called "Monthly Value"
Then you map the "Jan" column from the first LTS into the column
Then "Feb" from the second LTS
etc.
Bob's your uncle

Best way to combine multiple fact tables in single mart

Hi, quick question that I think I know the answer to, just wanted to bounce it off everyone here to make sure I'm on the right track.
I have a HR datamart that contains several different fact tables. Some of the facts are additive across time (i.e. compensation - people get paid on different days, when I look at a month I want to see the total of all pay dates within that month). The other type of fact is more "status over a set of time" - i.e. a record saying that I'm employed in job X with a salary of Y from a given start date to a given end date.
For the "status over time" type facts, if I choose January 2009 (month level) in the time dimension, what I'd really like to see is the fact records that were in place "as of" the last day of the month - i.e. all records where the start date is on or before 1/1/2009, and whose end date is on or after 1/1/2009. Note that my time dimension does go down to the day level (so you could look at a person "as of" the middle of the month, etc. if you're browsing on a day-by-day basis)
I've set up the join between the time dimension and the fact table as a complex join in the physical layer, with a clause like "DIM_DATE.DATE >= FACT.START_DATE AND DIM_DATE.DATE <= FACT.END_DATE". This seems to work perfectly at the day level - I have no problems at all finding the proper records for a person as of any given day.
However, I'm not quite sure how to proceed at the month level. My initial thought is:
a) create a new LTS for the fact table at the month level
b) in the new LTS, add the join to the time dimension
c) in the new LTS, add a where clause similar to LAST_DAY_IND = 'Y' (true for the last day of each month).
Is this the proper way to do this?
Thanks in advance!
Scott

Hi Scott,
I think you're on the right track but I don't think you need the last part. Let me generalize the situation to the following tables
DAILY_FACT (
DAILY_FACT_KEY NUMBER, -- PRIMARY KEY
START_DATE_KEY NUMBER, -- FOREIGN KEY TO DATE DIMENSION FOR START DATE
END_DATE_KEY NUMBER, -- FOREIGN KEY TO DATE DIMENSION FOR END DATE
DAILY_VALUE NUMBER); -- FACT MEASURE
MONTHLY_FACT(
MONTHLY_FACT_KEY NUMBER, -- PRIMARY KEY
MONTH_DATE_KEY NUMBER, -- FOREIGN KEY TO DATE DIMENSION, POPULATED WITH THE KEY TO THE LAST DAY OF THE MONTH
MONTHLY_VALUE NUMBER); -- FACT MEASURE at MONTH LEVEL. DATE_KEY is at END of MONTH
DIM_DATE(
DATE_KEY NUMBER,
DATE_VALUE DATE,
DATE_MONTH VARCHAR2(20),
DATE_YEAR NUMBER(4));
DIM_DATE_END (ALIAS OF DIM_DATE for END_DATE_KEY join)
Step 1)
Make the following three joins in the physical layer:
a. DAILY_FACT.START_DATE_KEY = DIM_DATE.DATE_KEY
b. DAILY_FACT.END_DATE_KEY = DIM_DATE_END.DATE_KEY
C. MONTHLY_FACT.DATE_KEY = DIM_DATE.DATE_KEY
Note: The MONTHLY_FACT DATE_KEY is joined to the same instance of the date dimension as the START_DATE_KEY of the DAILY_FACT table. This is because these are the dates you want to make sure are in the same month.
Step 2)
Create a business model and drag DIM_DATE, DAILY_FACT and DIM_DATE_END into it.
Step 3)
Drag the physical table MONTHLY_FACT into the logical table source of the logical table DAILY_FACT.
Step 4)
Set DAILY_VALUE and MONTHLY_VALUE to be aggregates with a "SUM" aggregation function
Step 5)
Drag all required reporting columns to the Presentation layer.
Step 6)
Create your report using the two different measures from the different fact tables.
Step 7)
Filter the report by the Month that joined to the Start Date/Monthly Date (not the one that joined to the end date).
Step 8)
You're done.
The act of combining the two facts into one logical table allows you to report on them at the same time. The strategy of joining the START_DATE_KEY and the MONTH_DATE_KEY allows you to make sure that the daily measure start date will be in the same month as the monthly fact table.
Hope that helps!
-Joe
Edited by: Joe Bertram on Jan 5, 2010 6:29 PM

Two facts in a single olap

Hi gurus
We r facing a problem with Eis. We are having two fact tables,By using this two fact tables how can we build a Olap Model

Stalin,
Yes, this is possible. Essentially, you are performing a join on the tables in your block which means you have to fully qualify each column in the block so Forms knows which column belongs to which table. For detailed information take a look at the Oracle White Paper: Basing a Forms Data Block on a Join. This works quite well and the tables your block is based on is fully updatable, whereas if you were to create a view and base your block on the view, most likely your view would not be updatable.
Hope this helps,
Craig B-)
If someone's response is helpful or correct, please mark it accordingly.

Multiple Facts in single subject area

Hi everyone,
Is there an optimal way to get multiple facts into a single subject area? The only way I've managed to get multiple facts into a single subject area is to go the route of creating hierarchies for all dimensions, setting up all the content levels for both the fact and dimension tables and finally creating aggregated measures for all the fact tables. However, when you setup these different hierarchies and content levels, the queries which are generated tend to get fairly nasty and seem to be slow. Another pesky issue is that I've had to create pseudo columns for all facts, so that if a report is using one dimension from FACT A and one dimension from FACT B, then you have to include this pseudo column from both facts so that OBIEE knows which tables are involved in the query. Without including these pseudo columns in the report, the OBIEE engine gets a little confused and puts up an error.
I'd prefer to find a better way to do the multiple fact implementation without having to have the massive queries and pseudo columns, but I'm not sure what the other options out there are. Anyone know the best way to accomplish this?
-Joe

Hi Wildmight,
You are exactly right.
Here's an example of what I'm trying to accomplish. We have a TIME SHEET fact table which has things like a work date, an employee ID, a work order number and the hours which were worked. The work orders can be against one or more pieces of equipment. There is a second fact table which models the one to many relationship between work orders and equipment.
The model would look a little like this:
Join on WORK ORDER NUMBER Join on WORK ORDER NUMBER
TIME SHEET FACT <-----------------------------------------------WORK ORDER Dimension ----------------------------------------------> WORK ORDER EQUIPMENT FACT
We would like to create a report that shows the number of hours from the time sheets fact grouped by the piece of equipment from the work order equipment fact. I've been able to setup this report using the method I described in my first post, but like I said, the generated SQL is massive and seems somewhat unnecessary.
I think I'd have to say the grains of the facts are different since they providing to different pieces of information.
I haven't done too much multiple LTS experimentation. I'm working from a single data warehouse source which should be robust enough to handle any reporting requirements. Even though I know OBIEE can do some clever combining of tables using the LTS; if data sets need to be consolidated, I'm trying to keep that work in the database via ETLs in order to keep the work that OBIEE has to do down to a minimum.
-Joe

Content Tab: None of the fact tables are compatible with the query request

Hi All,
**One thing I am not clear yet of all my years with OBIEE is working with the content tab in BMM.**
I have made a rpd the joins in physical layer as shown below:
https://picasaweb.google.com/114804305606242416264/OBIEEError#5663056545119428530
And the BMM layer as:
https://picasaweb.google.com/114804305606242416264/OBIEEError#5663056519553812930
Error I am getting when i run a request from the 3 columns from the selected 3 tables is:
Dim - Comment Code Details
Fact - Complaint
Dim - Service Details
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14020] None of the fact tables are compatible with the query request Sr Num:[DAggr(Fact - Complaint.Sr Num by [ Dim - Service Details.Sr Cat Type Cd, Dim - Comment Code Details.Cmtcode name] )]. (HY000).
I get no error for consistency.. I read everywhere and I know i need to set the appropriate aggregation levels in the various dims and facts LTS properties to help OBIEE understanding our model, but how to do that.. how do i decide... how should I approach, what should be the aggregation level, what details.
When i click More button i see different options: Copy, Copy From, Get Levels, Check Level, what do these mean.
Aggregation Content, group by - Logical Level or Column which one should i choose and how should I decide.
Can anyone explain the Content Tab in details and from scratch with some example and why we get these errors.... I know many people who are well versed with many other things related to RPD but this. A little efforts of explaining from you guys will really be appreciated.
Thanks in advance,
Dev

Hi Deepak,
Option 1:
My tables in physical layer are joined as below:
D1--> F1 <--D2--> F2 <--D3
Same way i model it in BMM
D1--> F1 <-- D2--> F2 <--D3
Here D1 is non Conformed Dimension for F2 and D3 is non Conformed dim for F1. Later create Dimensional hierarchies, I tried setting up the content levels
I go Sources>content tab of Fact F1 I set
Dimensions----------- Logical level
D1---------------------- D1 Detail
D2---------------------- D2 Detail
D3---------------------- D3 Total
then, I go Sources>content tab of Fact F2 I set
Dimensions----------- Logical level
D1---------------------- D1 Total
D2---------------------- D2 Detail
D3---------------------- D3 Detail
Then, I also go in all the dimensions and set their content levels to Details, but it still gives me errors not sure where I am going wrong in setting the content levels.
I need to know whether the way I have modeled it in BMM is right,
Option 2:
I can combine the two facts in a single Logical Fact or the above design should also work.
(F1&F2)<--D1, D2 , D3 joined separately using complex logical joins.
what will be the content tab details?
Thanks,
Dev

How to handle single, double quotes

Hi,
I have a dataset which contains single- and doubble quotes.
But when using the DS in javascript, I have problems in handing strings containing single- and doubble quotes.
<td onclick="myFunction('{TITLE}');">{TITLE}</td>
{TITLE} is equal to: I'm working with spry.
Spry replaces it in the code as: <td onclick="myFunction('I'm working with spry');">I'm working with spry</td>
Which leads to a quote error in the functionCall onclick().
I've tried to solve the problem by escaping these special characters in PHP;
- addslashes() > solves the javascript error, but give a readable text: I\'m working with spry
- htmlspecialchars() > no change in existing problem.
Any clues how to solve this.
Thanks,
Pieter

Hi Pieter,
When writing text in an HTML document I always use entity references (like ‘ for a single quote) for special characters to not only overcome the sort of problem that you are faced with, but this is also good practice for normal rendering of text in most languages including HTML, XML and JS.
You could also use character reference (like ’ for a single quote) with the same result, but DW has inbuilt functions to help with entity reference.
Having said this, and assuming that you cannot or it is impracticable to change the data within the database, why not have two fields in your dataset, one called JS_TITLE and the other just TITLE and use each one accordingly.
This still does not satisfy the fact that the single quote for rendering purposes is not represented by a reference, but that is another matter.
Gramps

Multiple fact tables using one measure

Hi Experts,
Multiple fact tables using single measure .For example Measure name is amount . This measure is using 5 fact tables. By using this info , i have to create bmm layer document . In bmm layer documents columns are like logical table name ,column name, logical sourc name . could you please help me out to draft the document ?

Hi ,
My question is five fact tables are there, day level two different fact tables , period and week fact tables are there .
Above all tables are using single measure . how to design these fact tables with measure in bmm layer ?
Please kindly give reply .
Thanks in advance.

Pie chart using httpservice

hello guys i am using a httpservice for giving dataprovider
to pie chart ..When this service return a single record ,pie chart
do not show anything instead of showing 100%...
problem occurs when my service return this..
<?rss version="2.0"?>
−
<data>
−
<SalesReport>
<status>Assigned</status>
<inquiry>22</inquiry>
</SalesReport>
</data>
otherwise it's work fine.......if it return
<?rss version="2.0"?>
−
<data>
−
<SalesReport>
<status>Assigned</status>
<inquiry>22</inquiry>
</SalesReport>
<SalesReport>
<status>New</status>
<inquiry>12</inquiry>
</SalesReport>
</data>
Here is my code .... Please help me .....
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="
http://www.adobe.com/2006/mxml"
layout="absolute"
backgroundGradientColors="[#ffffff, #808080]"
creationComplete="init();">
<mx:Style>
<mx:Script >
<![CDATA[
import mx.binding.utils.BindingUtils;
import mx.rpc.events.ResultEvent;
import mx.collections.ArrayCollection;
import mx.controls.Alert;
[Bindable]
public var reportData10A:ArrayCollection;
[Bindable]
public var reportData10A1:ArrayCollection;
[Bindable]
public var comboData10A:ArrayCollection;
public var fromMonth10A:Number;
public var techID:Number;
public var salesPerson10A:String;
[Bindable]
public var comboData10A1:ArrayCollection;
public function mytest10A():void
salesPerson10A = salesPesronCombo.selectedLabel.toString();
var salesPID:Number = mytest10A2(salesPerson10A);
fromMonth10A = monthFromCombo10A.selectedIndex + 1 ;
techID = TechnologyCombo.selectedIndex+1;
var str:String ="
http://reena-new:3021/reports/specperson_spectech?year="+yearCombo10A.selectedLabel+"&pers on="+salesPID+"&month="+fromMonth10A+"&techid="+techID;
Alert.show(str);
reportService10A.url="
http://reena-new:3021/reports/specperson_spectech?year="+yearCombo10A.selectedLabel+"&pers on="+salesPID+"&month="+fromMonth10A+"&techid="+techID;
reportService10A.send();
reportData10A = new ArrayCollection();
reportData10A =
reportService10A.lastResult.data.SalesReport;
public var i:Number;
public var salesPersonId:Number;
public function mytest10A2(str:String):Number
for(i=0;i<comboData10A.length;i++)
if(comboData10A.name==str)
salesPersonId = Number(comboData10A.id);
break;
return salesPersonId;
public function init():void
this.comboData10A = new ArrayCollection();
this.reportData10A = new ArrayCollection();
this.comboData10A1 = new ArrayCollection();
//reportService10A.url="
http://reena-new:3021/reports/specperson_spectech?year=2008&person=1&month=04&techid=1";
reportService10A.url="my.xml";
reportService10A.send();
comboService10A.send();
ComboService10A1.send();
public function getData10A(event:ResultEvent):void
reportData10A = new ArrayCollection();
reportData10A= event.result.data.SalesReport;
//Alert.show(reportData10A.length.toString());
public function getComboData10A(event:ResultEvent):void
comboData10A = new ArrayCollection();
comboData10A = event.result.data.SalesPerson;
public function getComboData10A1(event:ResultEvent):void
comboData10A1 = new ArrayCollection();
comboData10A1 = event.result.data.technology;
]]>
</mx:Script>
<mx:HTTPService id="reportService10A"
showBusyCursor="true"
result="getData10A(event);" />
<mx:HTTPService id="ComboService10A1"
showBusyCursor="true"
url="
http://reena-new:3021/reports/techlist"
result="getComboData10A1(event)" />
<mx:HTTPService id="comboService10A"
showBusyCursor="true"
result="getComboData10A(event);" url="
http://reena-new:3021/reports/personlist"/>
<mx:Canvas id="report10A" height="75%" width="70%" x="0"
y="100"
verticalScrollPolicy="off" horizontalScrollPolicy="off">
<mx:PieChart id="pie10A" x="0" y="25" width="350"
dataProvider="{reportData10A}"
showDataTips="true"
>
<mx:series>
<mx:PieSeries
field="inquiry"
labelPosition="callout"
nameField="status"
/>
</mx:series>
</mx:PieChart>
<mx:Legend dataProvider="{pie10A}" />

</mx:Canvas>
<mx:Canvas x="0" y="0" height="90" width="100%">
<mx:HBox y="30" id="combo10A" x="0" >
<mx:Label text="Sales Person" fontSize="12"/>
<mx:ComboBox width="100" id="salesPesronCombo"
change="mytest10A()();"
dataProvider="{comboData10A}" labelField="name">
</mx:ComboBox>
<mx:Label text="Technology" fontSize="12"/>
<mx:ComboBox width="100" id="TechnologyCombo"
change="mytest10A()();"
dataProvider="{comboData10A1}" labelField="name">
</mx:ComboBox>

this is the answer ................
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="
http://www.adobe.com/2006/mxml"
layout="absolute"
backgroundGradientColors="[#ffffff, #808080]"
creationComplete="init();">
<mx:Script>
<![CDATA[
import mx.binding.utils.BindingUtils;
import mx.controls.Alert;
import mx.rpc.events.ResultEvent;
import mx.collections.ArrayCollection;
[Bindable]
public var xmlResult:XML;
public function init():void
Alert.show("we are here");
myService.url="my.xml";
myService.send();
public function onResult(event:ResultEvent):void
xmlResult = new XML
xmlResult = XML(event.result);
Alert.show(xmlResult);
]]>
</mx:Script>
<mx:HTTPService id="myService" url="my.xml"
result="onResult(event)"
resultFormat="e4x"/>
<mx:PieChart id="pie10A" x="0" y="25" width="350"
dataProvider="{xmlResult.child('SalesReport')}"
showDataTips="true"
>
<mx:series>
<mx:PieSeries
field="inquiry"
labelPosition="callout"
nameField="status"
/>
</mx:series>
</mx:PieChart>
<mx:Legend dataProvider="{pie10A}" />
</mx:Application>
Thanks

Joins with multiple fact tables

Hi Experts,
i have one doubt in joins
we have two dimensions D1 and D2,
D1 is having A1 and A2 columns
D2 is having B1 and B2 columns
two facts F1 and F2 these are joined like D1 to F1 D1 to F2 and D2 to F1, D2 to F2
D1----->F1
D1------>F2
D2-------->F1
D2-------->F2
if i selected A1 and B1 in a request from which FACT table will get the data and why can you please explain
please help me
reg,
Jell

Hi All,
I have a similar requirement where I have 4 multiple fact tables and we can't combine all those facts into one single fact table. In that case how can a query work with multiple common and uncommon dimensions and measures from multiple fact tables, if it doesn't work that way - can you please explain how can we expect a query to work with multiple fact tables.
For eg: D1– Dim
D2 – Dim
D3 – Dim
D4 – Dim
F1 –Fact
F2 – Fact
F3 – Fact
D1 -> F1
D2 -> F1,F2
D3 -> F2
D4 -> F1, F3
In this case if we want to query from D1,D2,D3, F1, F2 or D1,D2,D3,D4,F1,F2,F3. Kindly please explain how it can be modeled in BMM or what are the limitations. I have done with two fact tables in past and didn't had issues but this is kind of a vast implementation. Your help is appreciated.

DW FACT table/Structure ??

Hi Everybody,
It is a great forum. Thanks for your replies/suggestions to my earlier posting. I am hitting FACT tables design by several folks over the period of time. It is puzzling me. I like to bounce this table in this forum to get your ideas/thoughts. As per FACT table definition, it need to contain single (instance) of FACT described by multiple dimensions. Here is the FACT structure I found in my situation.
DIM_KEY1 )
DIM_KEY2 )--> Foreign Keys to DIM Table
DIM_KEY2 )
TRANS_ID ----> Degenerate Dims
TRANS_TYP_CD )
TRANS_S_CD )
SRC_TYE_CD ) -----> Type codes derive multiple instances of FACTS from
ADJ_TYP_CD ) single fact table, based on type code combinations
DB_CR_CD )
TRANS_AMT ---> Fact
It looks like multiple fact tables (instances) forced into single fact table, where it fall under single super type/sub type structure of logical data-model. Here are my questions.
1)     Did any one work with such fact tables?
2)     Does it a acceptable design in star schema approach?
3)     What are the impacts in queries/ETL?
Thanks in advance.
RI

Hi,
Not clear with ur explination on the Fact but here are some general tips...
The instance in a fact table is decided by the keys from the DIM table and also the dates (effective and term dates) in case u maintain history.at any point in time (between effective and term date) we should have have only 1 instance live (current record).The type_cd does not matter and should not be used to create or distinctly identify an instance of a fact.
Regards
Bharath

Matching a filter value with mutiple fact columns

Hello,
I have been given following requirement to implement in OBIEE dashboard. There is a dimension table which stores Sales Rep IDs and their names. Fact table stores the Sales opportunities identified by these sales reps. Now they can work on the opportunity in any role...say as consultant or primary rep or some other role. Lets call it Role1, Role2 and Role3. The requirement is when user selects a Sales rep name in the filter; the dashboard should show all those opportunities on which he worked in any of the capacities i.e.Role1 or 2 or 3.
My Fact table has following columns
Role1_Sales_Rep_ID
Role2_Sales_Rep_ID
Role3_Sales_Rep_ID
The Dimension has
Sales_Rep_ID
Sales_rep_Name
I tries putting following condition ion physical layer join
Dim.Sales_Rep_ID = fact.Role1_Sales_Rep_ID
Or Dim.Sales_Rep_ID = fact.Role2_Sales_Rep_ID
Or Dim.Sales_Rep_ID = fact.Role3_Sales_Rep_ID
but the RPD gives an error saying that Dim.Sale_Rep_ID used more than once. Please help me solve this scenarion or please suggest any alternate solution.
Thanks,
Vivek.

Hi vivek,
but the RPD gives an error saying that Dim.Sale_Rep_ID used more than once. Please help me solve this scenarion or please suggest any alternate solution. Ya the joins should be established correctly to achieve your scenerio,i.e here oneto many joins sud be established for example
take the three fact tables role1,role2,role3 and the dimension table first click the dimension table and join it to role1 so it becomes 1:N the same way again click dimension table and click the role2 and repeat the process then you can achieve what you want.
Another simpler work around is take all the fact tables into single folder/table and the important columns for your requirment.Then now 1 fact and 1 dimension so its simple for you.
Hope it helps you.
Best Wishes,
Kranthi.

Create repository from database model- snowflake facts and dimension joins

I am working on a project that has a database model similar to the image in the link below.
There are other few tables around it, but this generally represent the spine or major database model. This is not exactly a snowflake schema as there are no intrinsic hierarchy in the dimension tables. As you can see dim2 and dim4 has one to many relationship with dim3. there are joins between the fact tables as well.
From some blogs and forum threads, I found out that I can create one fact/dimension table by joining many fact/dimension tables. Is this a right approach? Any thoughts on this model please?
Thanks,
Rakesh
ps: I am using Windows XP Pro and OBIEE 10.1.4.3.1 and right now analyzing the data to create a repository.

Hi Rakesh,
As above post says you combine all fact tables into single fact table with other dimension tables so it would become a simple start schema .Go throught these blogs for further information .
http://forums.oracle.com/forums/thread.jspa?threadID=2124061&tstart=0
http://www.obinotes.com/2010/08/joins-within-logical-table-sources-in.html#comment-form
Hope it helps you.Seems your new to forum you sud follow these rules http://forums.oracle.com/forums/ann.jspa?annID=939
By,
KK

Custom needles on gauge indicator

Does anyone have a trick for making different types of needles for a gauge indicator? For example, I would like to show an instantaneous value with the standard needle along with an average or threshold value with either a line or an external, inward pointing triangle. I thought of using arbitrary scale markers and extending the tick mark, but can't seem to do that either. I can do both of these things on a slide indicator, but can't seem to do the equivalent on a gauge. I know I could probably do this with an image, but that seems like a lot of work.
Solved!
Go to Solution.

I don't think this is possible with a single gauge indicator (Only very specific LV decorations can be used as rotating needles), but it is possible (and actually quite simple) if you use two.
What you do is this:
Drop a gauge and select Advanced>>Customize in the right click menu.
Go into customize mode by clicking the wrench in the toolbar and you can now edit the individual parts of the control.
Move the circle in the middle out of the way.
Grab the middle end of the needle and move it so that the needle is now small and pointing inside.
Grab the needle itself and position in on the circurmference.
Go back to edit mode and make everything else transparent, including setting the scale style to empty.
Close the control editor and apply the changes to the original control.
Now drop another control, set them to be the same size and location and move the custom control so that it is on top.
You now have two gauges which appear as one and one has the needle on the outside.
Here's what I got after about a minute:
You can create an XControl out of this if you use it in many places, but it's probably not worth the effort otherwise.
Try to take over the world!

Need some of you Geniuses to help with an IF statement in SAP Dashboard

=IF(C12=6,'6x'!N53,IF(C12=10,'10x'!N53,IF(C12=15,'15x'!N53,IF(C12=18,'18x'!$N$53,"Not Valid"))))
This statement is pretty straight forward in excel but keeps giving me an error in Sap crystal dashboard/xcelcius
The error is all the single Gauge values.
I find that hard to believe ?? Any thoughts oh great gurus out there

HI ,
Please check your C12 Cell. you may be using some formula or maping some dynamic value using some connection. Check that cell that causing you problem . If you are dividing anything by zero you will get DIV/0 error

2 facts in a single gauge/ pie

Similar Messages

Maybe you are looking for