Physical Column

I'm trying to know the physical column for the prompt values in Dashboard's. But for prompts there are two logical table sources in turn they have two physical tables. How would I know which physical table value is using by prompt.
Is there any log for the prompts...plz let me know.
Thanks in advance...

Two ways to know the source:
1) Run the prompt (by selecting a value and hit Go button) and check the session log for the same, that would tell the source column.
2) Using presentation column right click and select related physical column.
Pls mark correct/helpful

Similar Messages

How to apply time series function on physical columns in OBIEE RPD

Hi,
I know a way to apply time series function(Ago and ToDate) by using existing logical columns as the source. I have set the chronological key and created time dimension. In the expressiion builder for the same Time Dimension appears at the Top so that we can use its level.
But I couldn't apply a time series function when i have to create a logical column using physical columns. In the expression builder for the same, Time dimension does not appear in the list. Neither can i use any column from the time dimension. Please let me know a way to do it.
Thanks.

Time series functions are - by design and purpose - only valid for derived logical columns and not useable inside physical mappings.
If you want / need to do it on a physical level, then abandon the time series functions and do it the old-school way with multiple LTS instances.

Multiple report fields from single physical column.

Hi Experts,
I have a physical table like below. Multiple records for a single customer id. The no of Address_type may increase in future.
Customer_id     Address_Type         Address
101                  Primary                   abcdefgh
101                  Secondary               234oij3mb4
101                  Billing                      mdmnweoij4
102................etc.
My Requirement on OBIEE is to display report as below.
Customer_ID, Primary_Address, Secondary_Address, Billing_Address.
101                 abcdefgh            234oij3mb4               mdmnweoij4
Multiple report fields ( Primary_Address, Secondary_Address, Billing_Address ) are derived from same physical column ADDRESS.
I tried to duplicate the Address column on the report thrice and added conditions like Address_Type = Primary/Secondary/Billing for those three fields respectively.
But only of the field is getting correct data and rest of duplicate columns are null.
Tried FILTER function on OBI Answers, but the function fails saying it should be used only on measures.
Thought the alternative would be to define multiple logical columns at BMM layer. Created multiple alias for same table at physical layer and correspondingly created LTS for each on a single logical table. Defined Fragmentation/Where conditions.
LTS1 - Address_Type = PRIMARY
LTS2 - Address_Type - SECONDARY
LTS3 - Address_Type - BILLING
Created multiple logical columns from each LTS like Primary_Address, Secondary_Address, Billing_Address from LTS1, LTS2, LTS3 respectively.
This time, am getting data for all the fields on the report but getting cartesian result.
Can someone guide me whether my approach is correct or any other alternate best approach to achieve the desired result.
Note: I have the data Address on multiple physical rows for a customer, rather Not in a single row. which is causing me problem.
Thanks...
Ramchand.

Hi Srini VEERAVALLI,
I have lot many other fields in the same report coming from other tables.
Does the Pivot table option for above mentioned Address fields affect other columns?
If Yes, Can there be any other alternative? Am thinking of Opaque View at Physical layer to bring all Addresses on a single row.
Thanks...
Ramchand.

Count Metric based on two physical columns

I have a fact table that has Beginning Inventory On Hand (BOH) Units and Ending Inventory On Hand (EOH) Units.
It also contains sales dollars and sales units and other facts. My dimensions are: Locations, Time, Products.
Locations
     All Stores
     Region
     District
     Store
Products
     All Products
     Division
     Entity
     Subdivision
     SubClass
Time
     Week
We have fact tables at the lowest level and we have aggregrate tables at certain points.
We are trying to create some count metrics in the BMM Layer. We have created a metric that will count the number
of stores that have Sales Units at each level of the product dimension. We did this by mapping the logical column
to the physical column of Sales Units. We then defined the aggregation for this metric based on dimensions. The
first thing we needed to do is Sum the Sales Units across Products, so we set the "Other" as a sum. We then need
to apply the Count Distinct, so we set this at the Location Dimension.
Based On Dimensions
Sum(Sales Units)                              - Other Dimensions
Count (Distinct Case When Sales Units > 0 then store number else null end )     - Location Dimension
This will give a final rule as follows:
Count (Distinct Case When SUM(Sales Units) > 0 then store number else null end )
This is working great. However, we now want to create a logical metric that will count the number of stores based on the evaluation of two physical columns.
Count the number of stores that have Sales Units > 0 OR EOH Units > 0.
I do not know how to evaluate two physical columns and apply a count against them.
Thanks in advance for your help.

create same column for sum(eoh)
Count (Distinct Case When SUM(Sales Units) > 0 then store number
else
case when SUM(eoh) > 0 then store number else null end
else null end )

Getting the Description of the Physical Column

Hi,
I am trying to populate the description attribute of each of the table columns in the Physical layer of my RPD. I have these descriptions stored in an Excel file. Is it possible to import these descriptions into my .rpd?
Thanks

Oh...
Do you have that structure..!!
okay, then that is individual column which gives description of selected column..
You need to import this column also in physical layer..
This is only when you select both columns in criteria.. but shows as another column of particular column...
It's not possible to get description (data) of column in description field of physical column in rpd...
Hope i am clear..
As per my knowledge, If you want you need to add it manually.. with this structure you have
Thanks & Regards
Kishore Guggilla
Edited by: Kishore Guggilla on Dec 23, 2008 8:09 PM

Business Layer:Physical Column Mapping-Brackets are removed

Hello,
I use the expression builder to add a formula to the physical column mapping but every time I click OK the brackets are removed.
Is this a bug?
e.g. this:
IFNULL("test".""."et"."V_W"."NUMBERS", 0) *
IFNULL("test".""."et"."V_W"."WEIGHT", 0)
+
IFNULL("test".""."et"."V_WHT", 0) - IFNULL
("test".""."et"."V_W"."ULDT", 0)
turns into:
IFNULL("test".""."et"."V_W"."NUMBERS", 0) *
IFNULL("test".""."et"."V_W"."WEIGHT", 0)
+
IFNULL("test".""."et"."V_WHT", 0) - IFNULL
("test".""."et"."V_W"."ULDT", 0)
Hence the multiplication (ok the above is simplified) happens in the wrong order...

Hi Metalray,
This is expected behaviour, though I am not sure why. You can usually get round it by bracketing the other parts of the expression as well, or possily putting the whole thing in brackets. I don't believe there is hard and fast rule about what does work, but I know one can usually get round, you will just have to experiment, sorry.
Regards
Ed

Physical Column Order

Is there a way to influence the physical column order when generating objects for an Oracle 11g database? It looks like the DDL that is generated has the columns in a random order. Even though I order the columns in the way I want on the columns tab of a table, when I click the review tab, the DDL generated seems to ignore any ordering I try to establish. I am using PowerDesigner 16.5 SP02. Do others see this behavior?

Hi,
I'm using 16.5. SP03 PL2 and when I create a new table with a some columns and change the order I can see the changes in the Preview tab and when I do "Generate Database" the DDL is right as well.
br
Stefan

Logical (Business) Column based on physical column value

Hello everyone,
I'm new to here. I've been more of a reader than poster so far, but hopefully, I could offer some advice too.
My question today is the following - let's say I have brought 2 columns to the physical layer (in the same table or in different, but joined - it doesn't really matter). 1 column is defining EXPENSE_TYPE (such as "Air Travel", "Car rental", "Hotel"...Another column is simply EXPENSE_AMT.
I'd like to create 3 logical columns name AIR_TRAVEL_AMT, CAR_RENTAL_AMT, HOTEL_AMT in the busines layer based on the EXPENSE_AMT and EXPENSE_TYPE (AIR_TRAVEL_AMT= EXPENSE_AMT Where EXPENSE_TYPE="Air Travel")
I know that best practices would make me create those columns in the fact table during in ETL process, however, I have no choice here now.
My question is - how do I do it (I think it could be either variable/initialization block item - or possible I could write a CASE statement?).
Is this method going to affect performance negatively?
Thank you in advance.
UPD: I think it's possible to do this using something like
CASE WHEN Expense_Type = "AirType" THEN 1 else 0
am I on correct path on figuring this one out?
Message was edited by:
wildmight

Hi Wildmight,
you´re right, you can do it with a CASE statement:
For AIR_TRAVEL_AMT:
CASE WHEN EXPENSE_TYPE="Air Travel" THEN EXPENSE_AMT ELSE 0 END
Regards.

Display values for logical columns with several physical sources

Hi all,
I'm enocuntering some strange behaviour with the values displayed for a column (when we want to add it a as a filter, and in the dialogue box select 'Show All' values).
Basically the logical column is mapped against several physical columns as the base fact table is aggregated to different levels. Additionally, one column in the fact tables has an attribute value, and these vary between the aggregated and non-aggregated table. This is not a problem.
In the production environment, when we display the all values in the filters prompt for this column we are seeing the values being taken from one fact table. Naturally this means that not all the values possible for this column are being shown (i.e. values from the aggregated fact tables are missing). Now in one of our test environment where those fact tabels have additional data loaded, the values are being taken from one of the other fact tables. Unfortunately it is not necessarily the fact table with less data.
My questions are:
a) What dictates which fact table the server will use when the query in Answers doesnt use any dimensions (i.e. we are selecting just this attribute and selecting all the possible values by which it can be filtered)?
b) Is there a way of obtaining all the values from the differente physical columns? I.e. that the display values shows the values of that logical column across all the physical fact tables? Maybe we would need to model that attribute as a logical dimension just for that attribute? Im not really sure this would work, as at the physical level the join between the dimension and fact would still have to go to only one particular fact table.
Any info or help is much appreciated.

Hi,
Aggregate tables exist at physical level and are created by ETL procedures. Although i am aware that the dimension come into play when the application needs to decide which source aggregate table to use, it is not an issue here as in our query we are not involving dimensions. We are selecting just this one columen, and then the filter option on this column, then in the dialogue box we select 'All Choices', only the values from one of the source tables is being shown.
This is not a probelm within reports, i think it is a product limitation in that in that option to list all values a user can filter by, it is not possible to display all the values from the different fact tables to which that column is mapped.
Has anyone else encountered this behaviour?

Why logical column in terms of other logical columns and not physical sourc

Hello
Can someone shed some light that in what scenario ..defining a logical column in terms of other logical column is beneficial compared to defining logical column in terms of physical sources?
I found something on google that said defining in terms of logical columns is like one time thing. I dont understand, even if you define in terms of physical source that' too one time.
In both the case we build an expression specifying which logical or physical columns.
Thank you

well logical columns from physical source, if in logical fact table you can set aggr rules. Logical columns based on other logical columns you can not. Logical columns based on other logical columns will inherit the aggr rules. So for instance, if you create col1 and col2. Both based off physical and both having sum aggr rule. If you create logical column col3 based off these two as such "col1"/"col2" it will produce the following sum(col1)/cum(col2). Now if you really wanted sum(col1/col2) then you should have made col3 based off physical as col1/col2 with aggr rule of sum.
Also of some note, all logical columns based off physical will be performed in the inner most query. So for my example above to get col3 where it is logical col1/logical col2 or sum(col1)/sum(col2) the physical query will be:
select D1.c1/D1.c2
from (
select sum(col1) as c1,
sum(col2) as c2
from tableA
) D1
So my short summary of this, is what or how do you want your sql to be created. Based on this can you lead you to your answer of whether to use logical col based on physical or other logical columns. And unltimately, check the sql generated from your work to ensure the sql queries generated are what you want and expect.
I hope this helps!

Two physical logical source formulas for on logical column

I have two fact tables :
1. W_SERVICE_REQ_F(opened_dt_wid, assigned_dt_wid, closed_dt_wid, QUEUE_WID, SERVICE_REQ_WID): grain is one row per service request
2. W_SERVICE_REQ_DAY_A(DATE_WID, QUEUE_WID, NUM_OPENED, NUM_CLOSED, num_assigned)
The goal is to answer NUM_OPENED, NUM_CLOSED per queue in a day and be able to drill-down to those service requests.
Physical model:
Common_Date.row_wid = W_SERVICE_REQ_F (Opened_Dt).opened_dt_wid
Common_Date.row_wid = W_SERVICE_REQ_F (Closed_Dt).closed_dt_wid
Common_Date.row_wid = W_SERVICE_REQ_DAY_A.DATE_WID
Queue_d.row_wid = W_SERVICE_REQ_F.QUEUE_WID
Queue._drow_wid = W_SERVICE_REQ_DAY_A.QUEUE_WID
Service_req_d.row_wid = W_SERVICE_REQ_F.SERVICE_REQ_WID. (there is no join between Queue_d and Service_req_d)
BMM Fact and LTSs:
I have W_SERVICE_REQ_DAY_A, W_SERVICE_REQ_F (Opened_Dt), W_SERVICE_REQ_F (Closed_Dt) as LTSs of "Fact - Service Request" in that order.
BMM Fact logical columns (measures):
# Closed
# Opened
Question:
I want to configure each of the above logical column with two physical columns of different aggregate forumlas. (to ensure queries that dont need service req number hit a table) (similar to http://www.gerardnico.com/wiki/dat/obiee/fragmentationlevel_based).
SUM(W_SERVICE_REQ_DAY_A.NUM_CLOSED)
COUNT("W_SERVICE_REQ_F (Closed_Dt)".SERVICE_REQ_WID)
Can someone help in configuring one logical column with two physical column sources with different aggregate formulas?
This is what I tried:
In # Opened Properites->Data Type, mapped it to both W_SERVICE_REQ_F (Closed_Dt).ROW_WID and W_SERVICE_REQ_DAY_A.NUM_CLOSED
In # Opened Properties->Aggregation tab, selected 'Default aggregation rule' as Count Distinct. In the bottom, Logical table sources override as follows:
W_SERVICE_REQ_DAY_A : SUM("Fact - Service Request"."# Closed")
W_SERVICE_REQ_F : COUNT("Fact - Service Request"."# Closed")
Should it be done in a different way?
PS: OBIEE 10.1.3.4.
added OBIEE version: Feb 3, 2012 4:40 PM

I have two fact tables :
1. W_SERVICE_REQ_F(opened_dt_wid, assigned_dt_wid, closed_dt_wid, QUEUE_WID, SERVICE_REQ_WID): grain is one row per service request
2. W_SERVICE_REQ_DAY_A(DATE_WID, QUEUE_WID, NUM_OPENED, NUM_CLOSED, num_assigned)
The goal is to answer NUM_OPENED, NUM_CLOSED per queue in a day and be able to drill-down to those service requests.
Physical model:
Common_Date.row_wid = W_SERVICE_REQ_F (Opened_Dt).opened_dt_wid
Common_Date.row_wid = W_SERVICE_REQ_F (Closed_Dt).closed_dt_wid
Common_Date.row_wid = W_SERVICE_REQ_DAY_A.DATE_WID
Queue_d.row_wid = W_SERVICE_REQ_F.QUEUE_WID
Queue._drow_wid = W_SERVICE_REQ_DAY_A.QUEUE_WID
Service_req_d.row_wid = W_SERVICE_REQ_F.SERVICE_REQ_WID. (there is no join between Queue_d and Service_req_d)
BMM Fact and LTSs:
I have W_SERVICE_REQ_DAY_A, W_SERVICE_REQ_F (Opened_Dt), W_SERVICE_REQ_F (Closed_Dt) as LTSs of "Fact - Service Request" in that order.
BMM Fact logical columns (measures):
# Closed
# Opened
Question:
I want to configure each of the above logical column with two physical columns of different aggregate forumlas. (to ensure queries that dont need service req number hit a table) (similar to http://www.gerardnico.com/wiki/dat/obiee/fragmentationlevel_based).
SUM(W_SERVICE_REQ_DAY_A.NUM_CLOSED)
COUNT("W_SERVICE_REQ_F (Closed_Dt)".SERVICE_REQ_WID)
Can someone help in configuring one logical column with two physical column sources with different aggregate formulas?
This is what I tried:
In # Opened Properites->Data Type, mapped it to both W_SERVICE_REQ_F (Closed_Dt).ROW_WID and W_SERVICE_REQ_DAY_A.NUM_CLOSED
In # Opened Properties->Aggregation tab, selected 'Default aggregation rule' as Count Distinct. In the bottom, Logical table sources override as follows:
W_SERVICE_REQ_DAY_A : SUM("Fact - Service Request"."# Closed")
W_SERVICE_REQ_F : COUNT("Fact - Service Request"."# Closed")
Should it be done in a different way?
PS: OBIEE 10.1.3.4.
added OBIEE version: Feb 3, 2012 4:40 PM

Logical Column Mapping to Multiple Physical?

I am "learning" OBIEE still and a consultant today showed me something that totally blew my mind
In the OBIEE Admin tool (in verson 10) there are 3 layers displayed. The physical, business management and presentation layer.
I was under the impression that columns would be "mapped" one to one from each layer
The consultant proved me wrong and showed me that in fact, when making a logical column that you can have it "map" to two physical column names
Since every minute with the consultant is $$$ I tried to google around to find out why and how is this so but havent been able to find anything
Could someone explain to me why this would be done?
For example I have the logical column named "Home Faculty" and it is mapped to two physical columns "Faculty Short Desc" & "Main Faculty"
How would OBIEE know which one to use when?
Or does it simply "merge" the data between the two columns into one?

In this case equi join.
When you are using OBIEE try to see wrt fact table with Table 1 and 2 and follow as I suggest earlier.
When you use Fact,Table 1 and 2
Physical Layer Joins would be like:
Fact join with Table 1
Fact join with Table 2
In BMM I can make 3 tables
Like
Fact
dim 1
dim 2
Other case would be
Physical Layer Joins would be like:
Fact join with Table 1
Fact join with Table 2
Table 1's A1,A2 equals Table 2's A1,A2
In BMM I can make 2 tables
Like
Fact
dim sourcing 1 and 2
a) 1 mapping with 2
b) dim with LTS 1 and 2
Hope this helps
If I made it more confuse ;) send me email with US mobile# will call you back
If helps mark

Add a new column into repository

hi
In BI11g, how to add a new column into repository?
Thanks
kavi

Hi kavitha,
If your adding a new column to the physical layer or BMM layer the process is same as 10g.
Steps:-
1) Right click table where you want to add the column.
2)Select new object >>physical column/BMM column
3) Enter your choice labelling and data type,if needed formula.
4) Click ok and you can see the column being added on to the table.
CHeers,
KK

How To Create Logical column For Lastyear To Till Date

Hi All,
I Have to calculate Lastyear to Till Date for Logical Column.
Ex:I have Time Dime and Fact column and Dimension columns.
jan 2011 to oct 2012.
Please Let me know.
Thanks,
Abhi

Looks like you are not reading my messages
Since you are doing on logical columns getting this error.
Try this using physical columns then count from aggregate tab
CASE WHEN "Oracle Data Warehouse"."Catalog"."dbo"."Fact_W_SRVREQ_F_Open_Date"."OPEN_DT_WID" > 20110101 THEN "Oracle Data Warehouse"."Catalog"."dbo"."Fact_W_SRVREQ_F_Open_Date"."SR_WID" END
The same you can go with your variable
Or else the same can do by duplicating the existing Fact - CRM - Service Request"."# of SRs" and just add above code.
or just use the below you dont use sum since already aggregation is happend for # of SRs
CASE WHEN "Core"."Dim - Date"."Year" = VALUEOf("Warehouse Refresh Date Last Year"."CURRENT_CALENDAR_YEAR_LAST_YEAR") AND "Core"."Dim - Date"."Date" < VALUEOF("Warehouse Refresh Date Last Year"."LAST_REFRESH_DATE_LAST_YEAR") THEN "Core"."Fact - CRM - Service Request"."# of SRs" END
Hope this works, mark as correct

Logical Column(s) a.k.a. Pre-calculated Measures

I am looking for best practices around logical columns either in Presentation Layer or Business Layer. Specifically I want to know..
1) Is it advisable to have logical columns?
2) How many are good to have? Should one create logical columns for all frequent calculations which are done on dashboards?
3) Are there any performance implications?
4) Can we use Time Series function with logical columns? Like AGO etc.
In short I am looking for intelligent pros and cons of such implementations.
PS: Logical columns are derived from physical columns. For e.g. Profit = Income - Expense.
Regards.

Hi
1) all complex logic should be in the BMM layer in the RPD. Yes, it's advisable to have them in the BMM. Although another good practice is to try to delegate all complex calculations to ETL if possible.
2) As many as deemed necessary. Yes.
3) No, not really. But if you use Answers' logical columns - you have to be creative in propagating them to other reports.
4) Yes you can. But again, this is something that's better to have in the RPD.

Physical Column

Similar Messages

Maybe you are looking for