Time Dimensions in Sales/PRM Subject Areas

Hello,
I am relatively new to the Sales Cloud. I come from an OBIEE background and I trying to understand things from the reporting angle.
In the OBIEE rpd, we join the time/date dimension with a suitable date key in the fact table and posssibly create mulitple aliases of the date dimension to create hierarchies for various dates, for example: Opportunity Closed Date, Opportunity Create Date, Status Change date and so on.
Which date do the default time dimensions in all the Sales/PRM subject areas join to in the rpd? I was unable to find any documentation around this. This information is critical is creating reports like Total Revenue from 'Closed' Opportunities.
Thanks in advance,
Gaurav

Try this link it has alot of information you may find helpful
Oracle Fusion Applications Reporting and Analytics Learning Center

Similar Messages

Pick a subject area at run time and create an analysis on this subject area.

We have a requirement wherein we need to create analyses at run time. We want to give the flexibility to users to pick up a subject area on which they wish to create an analysis. This will be done through a dashboard prompt. Once the user picks up a subject area from the prompt, we will create the analyses at run time based on the selected subject area.
The problem that we are facing at this point is how to create a dynamic 'FROM' clause for the analysis. As an example, consider the following scenario:
1. There is a dashboard prompt called 'Select a DataStore'. The possible values are all the subject areas in the RPD. For simplicity, lets assume there are two values DS1 and DS2.
2. If the user selects DS1, the analysis sql should be:
select <colgroup1>, <colgroup2>
from DS1;
However, if the user selects DS2, the analysis sql should be:
select <colgroup1>, <colgroup2>
from DS2;
Hence the requirement for a dynamic FROM clause.
I tried using a presentation variable in the from clause but I get the sql syntax error.
Is there a way of implementing this requirement?

To work around the license issue, see the Microsoft Knowledge Base article LICREQST.EXE Requesting a License Key from an Object and download licreqst.exe. Run licreqst.exe and find "CWUIControlsLib.CWSlide.1" under the registered controls section and click on it. The license string at the top can be passed to Licenses.Add and then you should be able to dynamically create the Measurement Studio controls. For example:
Private Sub Form_Load()
Licenses.Add "CWUIControlsLib.CWSlide.1", "[Add license string from licreqst here]"
Dim slide
Set slide = Controls.Add("CWUIControlsLib.CWSlide.1", "slide")
With slide
.Top = 120
.Width = 1215
.Visible = True
End With
End Sub
Creating controls like this would have an impact on performance since all calls are late bound. If you are using the Measurement Studio controls in a UserControl, though, you should not need to do this since the license would get compiled into the binary that contains the control. I don't think that you would have any problems creating your control since it would not be licensed.
- Elton

Multiple Subject Areas

Somewhat new so please forgive me if the question is simple (if it is, please point me in the right direction). I've looked through the documentation and this forum, but have not found what I'm looking for yet.
I am trying to get a single worksheet to pull data from multiple subject areas (two or more fact tables). I would prefer to not join fact tables together, and so I have not created the joins between the folders (fact tables) because I thought the performance would generally be horrible. (example of functionality I'm looking for: I want to combine Sales and Inventory data on one worksheet).
I have kind of tried complex folders, but I would prefer to have the tool generate the SQL if possible because it won't just be me creating reports, and if it's possible, I'd like to avoid coding the SQL myself every time I want to join subject areas.
I also looked at Custom Folders, but my understanding is that they are used primarily to join 1 fact table with multiple dimensional tables, but not multiple fact tables (at least that was the example in the documentation).
My current setup is a 2 tier environment, with just Disco Admin and Disco Desktop on top of 10g. We don't have AS yet so I can't test anything that way.
I appreciate any comments in advance.
Nate

You should try both Complex folders as well as custom folders and see which gives you better performance. Discoverer SQL optimizations for example apply only on Complex folders and not on simple folders.
If you define the joins between the two tables, you can still use items from them in your Discoverer report without having to create a complex folder on them.
And finally, you can always create a view or materialized view and use that MV in your Discoverer query.
thanks
Abhinav
Oracle Business Intelligence Product Management
BI - http://www.oracle.com/bi
BI - http://www.oracle.com/technology/bi
Blog - http://blogs.oracle.com/
BI Blog - http://oraclebi.blogspot.com/

Illegal cross join within the same dimension caused by incorrect subject ar

hi!
Imagine the following BMM:
There is one Logical Dimension Table "Service Account" with the following LTS:
- LTS "D_SERVICE"
- LTS "D_SERVICE_CLASS"
- LTS "D_SERVICE_STATUS"
This Logical Tabe "Service Account" joins (One-to-many) with several Fact Tables (other Logical Tables).
In the Physical Layer the joins for the "Service Account" LTS are:
- One-to-many between D_SERVICE_CLASS and D_SERVICE
- One-to-many between D_SERVICE_STATUS and D_SERVICE
The problem is that when I build a report in Answers using only the following columns of the Logical Table "Service Account":
- Service Class Desc (which exists in the Logical Table "Service Account" and in the Physical Table D_SERVICE_CLASS)
- Service Status Desc (which exists in the Logical Table "Service Account" and in the Physical Tabl D_SERVICE_STATUS)
- MSISDN (which existis in the Logical Table "Service Account" and in the Phsyical Table D_SERVICE)
the following error appears:
Estado: HY000. Código: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14065] Illegal cross join within the same dimension caused by incorrect subject area setup: [ (select * from prd.D_SERVICE where SOURCE_SYS in ('ARBOR','PPB') and DW_SERV_ST_ID in (100000003,100000009)) as T1836, D_SERVICE_CLASS T1916] with [ D_SERVICE_STATUS T1948] (HY000)
SQL emitido: SELECT "SERVICE ACCOUNT"."TLC MSISDN9" saw_0, "SERVICE ACCOUNT"."IWS Service Class Desc" saw_1, "SERVICE ACCOUNT"."TLC Service Status Desc" saw_2 FROM "VFPT - Upgrade Siebel" WHERE "SERVICE ACCOUNT"."TLC MSISDN9" = '917330340' ORDER BY saw_0, saw_1, saw_2
Help, please!
Thanks.

Physically, only D_SERVICE is joined to the facts. Then D_SERVICE_CLASS is joined to D_SERVICE (one-to-many) and D_SERVICE_STATUS is joined also to D_SERVICE (one-to-many).
In the BMM, there is only one Logical Dimension Table for those 3 physical tables. This Logical Dimension Table is called "Service Account" and has 3 LTS: D_SERVICE, D_SERVICE_CLASS, D_SERVICE_STATUS. The Logical Dimension Table has several logical columns that are associated to those 3 LTS: SERVICE_KEY, SERVICE_CLASS_KEY, SERVICE_STATUS_KEY, SERVICE_MSISDN, SERVICE_CLASS_DESC, SERVICE_STATUS_DESC.
The Logical Dimension Table "Service Account" is then joined to a fact table (one-to-many).
I didn't understand the suggestion about the 3 LTS... Aren't we doing that already? Can you explain it better, please?
thanks.

Historical Reporting With Multiple Subject Areas

Hi All,
I am working on to decide the best way to create repository. I do have a requirement from my client that they need to see both Current and Historical Reporting via OBIEE. I am keeping Type 2 SCD. My model consists of about 30 fact tables - each of them represents a business process/event.
Following are my options:
1) One Subejct Area to keep current/historical reporting. Here the joins would be based on PK/FK relationships with Effective Start and Effective End dates. There is a flag in all tables to find the most updated record. Users can use the flag to find the most updated record or use Effective Start and Effective End dates to go point in time.
2) Create two Subject Areas - Current and Historical reporting. Current one will include the flag logic to get the most updated record in RPD
3) Create multiple Subject Areas for each Fact table and use Combining Multiple Subject Area approach to join Subject Areas. Additionally, create one Subject Area for Historical Reporting (that will have all the tables in one SA)
I am thinking of going ahead with option 3) This will have Subject Areas for all logical facts (for Current reporting) and one Subject Area for Historical reporting.
Is this a standard design? Any inputs?

You should try both Complex folders as well as custom folders and see which gives you better performance. Discoverer SQL optimizations for example apply only on Complex folders and not on simple folders.
If you define the joins between the two tables, you can still use items from them in your Discoverer report without having to create a complex folder on them.
And finally, you can always create a view or materialized view and use that MV in your Discoverer query.
thanks
Abhinav
Oracle Business Intelligence Product Management
BI - http://www.oracle.com/bi
BI - http://www.oracle.com/technology/bi
Blog - http://blogs.oracle.com/
BI Blog - http://oraclebi.blogspot.com/

Time Dimension with Hourly base level

Hi all
I need to analyze data at Hour, Day, Month, and Year levels. The data in the fact and dimension tables are at the 'Hour' level with DATE datatype, such as:
02-SEP-10 10:00:00 AM
02-SEP-10 11:00:00 AM
To use Time-Series type calculations, I understand that I have to create an OLAP dimension of type 'TIME' (and not 'USER') and map it to the populated relational time dimension table. My questions are:
1) Can I have the primary key for 'Hour' level as the actual base level value of datatype DATE (eg. 02-SEP-10 10:00:00 AM) ?
2) For the END_DATE and TIME_SPAN attributes at the 'Hour' level, what should I use?
The documentation is only available for minimum 'Day' level hierarchies, which allows setting END_DATE and TIME_SPAN to the actual 'Day' value and 1, respectively.
3) For the END_DATE and TIME_SPAN attributes at the 'Month' level, do I need to supply the last-date-of-each-month and number-of-days-in-that-month, respectively?
Please bear in mind that I am relatively new to Oracle OLAP. Any assistance will be appreciated.
Cheers.

Thank you Szilard and Adnan for the very prompt and informative responses.
I managed to follow the advice on the oracleolap.blogspot link and created a time dimension with members at Hour level loaded into the dimension in character format: TO_CHAR(hour_id, 'DD-MON-YYYY HH24')
The problem now is the maintenance (loading) of the dimension is taking an abnormally large amount of time (over 1 hour) as opposed to when the members were being loaded in DATE format (5 minutes). The mapping table only as 10,000 entries.
Why is these such a big difference? Is it normal? Is there a way to speed up the maintenance time?
FYI, I have not created any indexes on any of the attributes.
My platform is:
11.1.0.7.0 DB
11.1.0.7.0B Client

ER Time Dimension

HI
i have a problem of creating a ER diagram for Time Dimension which consist of tables are DAY , WEEK , MONTH , QUARTER , YEAR and the relationship between those tables
can someone help i need a full solution with attributes for each table

Do you mean you need help designing the actual model or help putting the model in SDDM? (If you need an example Time Dimension model this is not the right forum. You can search online for examples as there are many published.)

DAC subject areas won't assembled.

I’ve run across a situation where I am trying to run in DAC both EBS and provided by third-party jobs in the same environment. It appears that provided by third-party vendor container is keeping the other containers subject areas from being able to be assembled.
I’ve deleted containers one at a time, imported one at a time, created new containers, new subject areas and so far nothing I do seems to clear this up.
When I install the Enterprise Container first, it is able to assemble, but after I import provided by the third-party container I am no longer able to assemble the Enterprise Container Subject Areas. Provided by the third-party Subject Areas assemble fine and execution plans run. Just can’t get the Enterprise one in a state where it will run.
Please share any thoughts on the possible cause and solution.
Thank you very much!

Thank you for getting back to me. Yes by third-party container i realy mean non-Oracle container. There is no error, it just won't complete the process. I've tried to kill DAC pracess and to start over - made no difference.

Time dimension - not ordered

Hello,
I'm new on OLAP Cubes,
I've made one that works well instead of the fact that my time dimension is not sorted : dates are not in order.
I've tried to sort dates before the cube, in the views. but even if when i see time attribute sorted in my view my cube time dimension stays unsorted.
I'm working with AWM 10g
please help !

You can always use the time_end_date attribute to sort the results of the query. When you say that the time dimension values are not sorted? what do you mean .... is the hierarchy correct ... all nn-JAN-yyyy records under JAN-YYYY or is it also mixed up due to the improper sorting? If the hierarchy is alright.. you may need to
Can you provide more details... perhaps all details relating to db view/table - structure (table/view, columns, datatype, size etc) and sample data (few rows) as well as how the data appears in the olap time dimension when viewed through AWM results. Whats loaded (all of the records but sorted improperly or if only some of them => what're the records which dont get loaded?)
Also noticed that you used the term olap cube time dimension.. the time dimension is not exactly an independent component of the cube, its used by the cube. Its defined in the AW and exists only as a dimension (independent of any/all cubes). The cube only references it.
Another reason for mismatch (not very likely though) could be that you have time end date data in your view as a varchar field instead of a date and is interpreted wrongly while its being loaded as a date datatype attribute by the AW dimension load program. Depending on your NLS settings (and thereby the default date format), the date string is interpreted as a inappropriate date. You usually encounter errors during such a load ... day #13 interpreted as month #13 (invalid) as a result of a mismatch of date format settings.
HTH

Illegal cross join within the same dimension caused by incorrect subject.

Hello Gurus,
I am getting this error for one calculated column in OBIEE 11G
Illegal cross join within the same dimension caused by incorrect subject area setup. *[ WC_PC_POSITION_D AS Dim_WC_PC_POSITION_D] with [ W_GL_ACCOUNT_D AS Dim_W_GL_ACCOUNT_D On Dim_W_GL_ACCOUNT_D.ROW_WID = Fact_WC_PC_BUDGET_DTLS_F.GL_ACCOUNT_WID, WC_PC_BUDGET_DTLS_F AS Fact_WC_PC_BUDGET_DTLS_F] (HY000)*
the same column is calculated in OBIEE 10G and it's giving fine result.
the way it's calculated in BMM is we are using 2 different logical table's column for deriving new column.
is anyone having any idea?
Thanking You..

More Specially,
Physical Layer:
Dim:View1,View2,View3,View4
Fact:View5
all Views are PK joined in Phsical layer.
So I need all columns in 3 Views and few column in View4.
In BMM :
Dim:View1,View2,View3
Fact:View 5
are joined and created LTS in View3 for LTS View4 and dropped few coulmns and mapped the columns.
In reports,
If I pull the columns from View3 which is came from view4 then getting the error.
I hope does it make sense.
Please help on this.

Multiple Fiscal Calendars Displayed in Subject Area Time Dimension

Hi all,
Thanks for taking the time to review my post.
Environment
Oracle BI Applications 7.9.6 Financial Analytics
Oracle E-Business Suite 11.5.10
Query
The Time dimension on my Subject Areas (Financial Analytics) are showing more period data than I expected.
I have configured one Enterprise Calendar (WPG_Calendar) that I set in the DAC parameters - $$GBL_CALENDAR_ID (WPG_Calendar~Month) and $$GBL_DATASOURCE_NUM_ID (4). The warehouse Enterprise Calendar table W_ENT_PERIOD_D is populating with the periods as configured in EBS for that calendar(Jan-09, Feb-0, Mar-09, etc). I noticed that the Multiple Fiscal W_MCAL_PERIOD_D table is also been populated with the Enterprise Calendar data PLUS, the Seeded EBS calendar (JEBE_MONTH_VAT) and a generated Calendar that appears to be a 5-4-5-4 Calendar (Jan-01-09, Jan-02-09, Jan-03-09, etc). The trouble is these W_MCAL_PERIOD_D periods and dates are all coming through in my Time dimensions and make it confusing for the Answers Users when choosing a Time dimension.
Also, for columns W_CURRENT_MCAL_PERIOD_CODE, W_CURRENT_MCAL_QTR_CODE, W_CURRENT_MCAL_YEAR_CODE there are rows with Current, Previous and Next populated that span these different periods as you would expect, but I'm concerned these return multiple rows for Filters Current Fiscal Quater, Current Fiscal Year.
Funnily enough, W_CURRENT_MCAL_MONTH_CODE has nothing populated (NULLs for all rows).
Your comments are most welcome.
Kind Regards,
Gary.

The filtering of the calendar can be done directly on the logical layer.
for the logical dimension "Dim - Date Fiscal Calendar", Logical Table Source "Dim_W_MCAL_PERIOD_D_Fiscal_Period"
set the content as :
"Oracle Data Warehouse".Catalog.dbo.Dim_W_MCAL_PERIOD_D_Fiscal_Period.MCAL_CAL_WID = VALUEOF("MY_MCAL_WID")
and setup the repository variable MY_MCAL_WID to match with your calendar wid.
If your calendar depends on any context then you can use session variable instead of repository variable

Sales stage history subject area

Hi - Can someone clarify the sales stage history data. It's just keeping track of everytime the sales stage changes right and when it changed? However, if the opportunity was transferred from one owner to another, it can only associate the record/change with the current owner correct? For example, if this was the sequence...
Stage 0 - changed by owner 1 to Stage 3
owner changed to owner 2
Stage 2 - changed by owoner 2 to Stage 4
The report would say that owner 2 made both changes right?

Hi-
You are correct that Sales Stage History does not track the user making the change. This subject area captures a pre-defined set of field values each time the sales stage changes and is most useful for doing deal flow analysis.
Fields captured when stage changes:
Stage Start Date
Expected Revenue
Forecast Flag
Opportunity Close Date
Revenue
Probability
Sales Stage
Sales Status
There are also several metrics calculated for you:
Days as Opportunity
# of Days in Stage
Avg Days in Stage
Fallout
Fallout Ratio
Good luck!

How to know on which time dimension level we are ?

Hello,
I would like to know is there a variable or a mean to know dynamically on which time dimension level we are in order to use that in a CASE WHEN clause ?
By using a sort of aggregation tables in which one of the column contains the name of the level, I could know on which level I am but I can't use that for drill down. What I mean :
Tab1 :
'Year' as typelevel, year
Tab2 :
'Month' as typelevel, year, month
In BMM, I have made one logical table with as Source tab1 and tab2 and as columns typelevel, year and month.
tab1 has in content column the year level
tab2 has in content column the month level.
So when in Answers I retrieve
typelevel, year
the result is : 'Year', 2008
and when I request : typelevel, year, month
the result is : 'Month', 2008, 1
But if I want to drill from year to month in order to have :
'Year', 2008
and then after drill
'Month', 2008, 1
it is impossible as a filter on typelevel='Year' is added on the month level, so it retrieves 0 columns.
If someone has an idea on how to do that it would be very great.
Thanks in advance for your help.

Hi Supriya,
OOTB I think you can use SharePoint designer, but I would suggest custom code to iterate to all pages, and get the lists that are associated with these pages.
http://stackoverflow.com/questions/633633/sharepoint-how-can-i-find-all-the-pages-that-host-a-particular-web-part
another one would be if those lists were never used and you can check for list with empty data.
I would use Get-SPLists to get all of the lists to check for zero items.
http://blogs.technet.com/b/heyscriptingguy/archive/2010/09/15/use-windows-powershell-to-manage-lists-in-sharepoint-2010.aspx
http://sharepointrelated.com/2011/11/28/get-all-sharepoint-lists-by-using-powershell/
Hope this helps!
Ram - SharePoint Architect
Blog - SharePointDeveloper.in
Please vote or mark your question answered, if my reply helps you

How to limit data for a dimension in any subject area?

Hi folks,
I do have a little problem, maybe you can help me:
I have a large subject area for all my countries and product i sell there.
now i want to have special subject areas for certain countries.
that for i ducplucated my large subject area, went to the identity manager and there I set special Rights für the users: I chose my fact measure and put a data filter for it on the dimension country.countryname = Germany.
I hope you can fallow me until here. ;-)
Now I can build a query in answers and it works, within this subject area I only get data for Germany.
BUT: when I'm on the criteria tab and try to create a filter on my countryname (from the dimension) it shows me all the countries I have.
I think for the end users this is a litte bit confusing.
So how do I limit the dimension in this subject area to a particular value?
I would be very happy for help, cause then I could finish my development for today ;-)
Kind regards,
Sven

Try this; @BMM Fact source properties->Content tab->WHERE clause section add the dimension country.countryname = 'Germany'.
Also set the implicit fact on the subject area.
Let us know how it works
Edited by: Srini VEERAVALLI on Apr 8, 2013 7:12 AM

OLAP time dimension - how are the weeks allocated

Could someone please help me understand what logic Oracle uses when one makes use of Oracles OLAP time dimension based on weeks.
I am use Oracle OLAP 11.2
I have a Time dimension that has the following hierarchy:-
YEAR
QUARTER
MONTH
WEEK
For calculating the weeks ID I make use ISO week and year i.e. IYYYIW
For calculating the end date I use the following:- NEXT_DAY( l_date, 'MON' ) -1
i.e. the weeks end date is the Sunday.
According to me this is the required result.
Problem is that for some months there are 3 weeks allocated which makes no sense to me.
I cannot understand the logic used in allocating the weeks.
The following is an example:-
the following weeks were allocated to the month February
201306 (end date= 10-2-2013)
201307 (end date= 17-2-2013)
201308 (end date= 24-2-2013)
but the following week was allocated to January which makes no sence to me,
I would have expected it to be found in February
201305 (end date= 3-2-2013)
Week 201309 (end date= 3-3-2013) was allocated to March which according to me is correct..
Another example is week *201030 (end date= 1-8-2010)* that is allocated to July while I would have expected that it should be August.
I would have thought that it uses the end date that is placed in the mapping to determine the month to place it in.
Could some one please explain what the reason for this could be.

Oracle OLAP model/design (in this case, at least) cannot compensate to coverup existing flaws in the relational model/design.
I dont think this is a valid hierarchy even considering relational model/design.
Weeks do not fit in below Months (calendar months).
You can force fit them by making Weeks the source of truth and making all Months logical Months like "Business Month", "Business Quarter", "Business Year" etc. which will be composed of whole weeks but differ significantly from the calendar definition of Month, Quarter, Year etc.
You are better off modeling time as composed of two hierarchies:
H1: DAY -> MONTH -> QUARTER -> YEAR and
H2: DAY -> WEEK
Alternately if you dont want to introduce DAY level (lower granularity), you can split up the Time dimension into 2 different dimensions. And also modify your star schema to add an additional time dimension key to fact table - one key pointing to WEEK and another pointing to MONTH (independently).
TIME_MO: MONTH -> QUARTER -> YEAR
TIME_WK: WEEK
The fact data will need to be split up to correctly identify the coirrect MONTH-WEEK combination for the relational record.
E.g:
Fact table should have 2 dimension Fks for WK_KEY as well as MO_KEY so that a fact figure of 1000 evaluated over 7 days is split up into 300 from 29-31st of previous month and attached to MO_KEY of previous month and another record of 700 covering days from 1-4 and recorded/tied to same WK_KEY but next month (next month's MO_KEY).
HTH
Shankar

Time Dimensions in Sales/PRM Subject Areas

Similar Messages

Maybe you are looking for