Day Dimension
Hi ,
I have been setting up OBA 7.9.5 for Oracle ebiz 11i & been running the ETL.
Stumbled upon maps SIL_DayDimension_SeedData & SIL_DayDimension_GenerateRows & found that
they use a flat file FILE_DAY_SEED.csv as the source.
I fail to understand the purpose of this file and the kind of data its supposed to have?
Please explain with example & also let me know if there is a documnetation available for these parameters file
(as i can see a couple of them )
Thanks,
Sid
Hi Sid,
FILE_DAY_SEED is a flat file generated by informatica when executed through DAC.
Using the SIL_GenerateSeed Informatica generates this file with the $START_DATE, $END_DATE values which are the user input parameters from DAC.
Using SIL_GenerateRows Informatica genrates all the rows in between $START_DATE and $END_DATE inside the same FILE_DAY_SEED.
This file can be used as Day Dimension.
U can even generate the fiscal dates through other SIL's...!
Thanks,
Priyank.
Similar Messages
-
Day dimension and surrogate keys
Hello,
I'm trying to create a 'day' dimension using OWB. I was thinking about a set of levels like this:
- 'date_id'
- 'special_value' (such as unknown)
- 'calendar_date'
- 'month_day'
- 'month'
- 'year'
How can I implement something similar with OWB? I have to create one level for each dimension column? And how can I determine the value of date_id in the mapping?
Thanks in advance for the help
CosmaHi Cosma,
There's an example for this in the Oracle-by-Example session for OWB: http://www.oracle.com/technology/obe/obe9ir2/obe-dwh/owb/owb.htm
Around halfway through you'll find it.
Good luck, Patrick -
Who has built a "Day" dimension?
We have "Year" and "Period" for month. That's the typical set up for most of us. But has anyone built a "Day" dimension to keep track of data on a daily basis? If so, how would you build that?
Is that an Essbase question?
I've not seen a Day dimension in BSO. However it is just like any other dimension.
It can be a flat hierarchy with 31 members in it. Or it can have a weekly distrbution, or.....
Regards
Celvin
http://www.orahyplabs.com -
Hyperion Planning : Period Dimension in Days
I need to realize a period dimension in days! Moreover i need to have an organization in week whic include the existence of week day (Sunday, Monday..) to make a comparison beetween all Sunday in differnet Year.
Is it possible to have a native calendar function in Hyperion Planning, or Does exist another way to solve this problem?
ThanksBest practice would be to use Period dimension down to weeks then create a 'Days' dimension which holds the weekdays, this will help your blocksize too and will allow the reporting requirements you have mentioned.
-
Day of Month Dimension or is there another way?
I've been asked to build a cube which will contain data at the granularity of a day. For example, daily sales. However, Essbase does not allow duplicate member names. I've temporarily built an additional Day Of Month dimension to allow loading of the data, but the presentation back to the users is a bit clunky using Smart View in Excel as they expect the data to rollup by date. Has anyone tackled a similar project? Thanks.
I would not create a day dimension. I have done several "daily" cubes in my career. A good question to ask is "how far back does daily detail really matter?" For every daily project I've done, that answer is in the ballpark of two or three months... and no more. So what I did was to create a rolling two (or three) month cube with distinct daily detail (putting dates in aliases and refreshing via load rules then rolling to a new month. This cube balances with the same two months in the full year cubes at only monthly detail. I did my first one before there was partitioning or @XREF so now you have options to connect these cubes. Even if you load the full year monthly cube directly, it might be of interest to create a "linked" partition so that uses can jump from the current month or prior month, for instance, in the full year cube to the expanded daily detail in the daily cube.
If it turns out a full year of daily detail is required (though I doubt it's necessity in an OLAP model given the possibilities of drill-through to relational detail using EIS or Essbase Studio depending on your versions), then ASO would be my choice to handle the extra volume. Otherwise I'm talking BSO. I hope you find this helpful.
Regards, Darrell Barr
PS - don't forget you can enable duplicate names if you're on the latest product versions (though I don't really recommend it). -
How to control the measure based on the related dimension.
Hi Experts,
In order to improve performance, I have created three kinds of time tables in DB,such as Year .Month, Day.
Then import them into the physical layer in RPD, and combine them into one dimension in BMM.
Actually, it has three level fact related with three time tables,so they are also dragged into one fact in BMM,and one column will be corresponding with three column derived from different Fact table in physical layer.
So I want to know how to control the measure based on the related dimension.
For example:
when users drag the Year,Sales column, it will come from Year Dimension and Year Fact Table.
when users drag the Month,Sales column, it will come from Month Dimension and Month Fact Table.
when users drag the Day,Sales column, it will come from Day Dimension and Day Fact Table.Hi,
Create a dimension Hierarchy, with Year >> Month >> Day Levels and
Next Double click on Year Table LTS >> click on Ocntetnt Tab >> set as Year
same way for Month LTS and Day LTS.
So now when you select year column then server canknow which LTS to hit and Hits Year LTS.
Mark If Helpfu/correct
Thanks. -
Date Dimension for date pull up (Dimension to Dimension)
Need advise....
1. I have a person dimension table and sales fact table. Person_id is the foreign key in the fact. I want to be able to pull the date of birth. But the person dimension has only dob_sid that should point to the day dimension to get my the equivalent date. This is the problem...i cannot join person dimension to day dimension, i need to be able to do a join through fact, but the fact table is missing the dob_sid.
2. Second issue is, person dimension has other dates associated action_date, cancel_date, etc. more than one date field that i need to join to day dimension.
How will i be able to achieve this in BMM? Physcial layer?The key here (no pun intended) is to alias your date dimension for as many date lookups you require, join these aliases directly to your person dimension off the appropriate keys.
-
Creating a DWMQY DIMENSION using Analytic Workspace Manager
Hi everyone,
I need some help creating a "time aware" (DAY, WEEK, MONTH, QUARTER, and YEAR) dimension using Analytic Workspace Manager.
Let me give you some background. I'm coming from a traditional "Oracle Express" OLAP background where all our data is stored in cubes and these are defined, populated and operated on using OLAP DML, there is no SQL or traditional relational tables involved.
I now want to pull data from relational tables into some OLAP cubes and am using Analytic Workspace Manager to do this (maybe this is not the best way?)
Let me explain what I'm trying to achieve. In OLAP worksheet I can type the following DML commands:
DEFINE MY_DAY DIMENSION DAY
MAINTAIN MY_DAY ADD TODAY '01JAN2011'
What this will do is create a "day dimension" and will populate it with values for each and every day between 1st Jan 2011 and today. It will be fully "time aware" and thus you can use date functions such as DAYOF to limit the MY_DAY dimension to all the Fridays etc. Similarly if I define a "month dimension" there will be an automatic implicit relationship between these two dimensions, this relationship and time aware cleverness is built into Oracle.
However, a dimension defined using DML commands (and indeed all objects created using DML language) is not visible in Analytic Workspace Manager (as there is no metadata for them?) and for the life of me I cannot work out how to create such a dimension using AWM. If I create a "Time Dimension" then, as far as I can tell, this is not a proper time dimension but merely a text dimension and I, presume, I have to teach it time awareness.
Can anyone help me? I have no issues creating, and populating cubes from relational tables using Analytic Workspace Manager, the only issue I have is creating a "proper" time aware dimension.
Many thanks in anticipation.
Ian.When a dimension is of type "TIME" in AWM, then for each member of that dimension, you need END_DATE and TIMESPAN attributes in addition to the key column and description column.
So in your case, if there are 5 levels: DAY->WEEK->MONTH->QTR->YEAR
then you will need atleast 15 columns in your source sql table/view
or 20 columns if you have separate column for description.
For example the columns in your source table/view could be:
DAY_ID,
DAY_DESC,
DAY_END_DATE, (which will be that day's date)
DAY_TIMESPAN, (which will be 1)
WEEK_ID,
WEEK_DESC,
WEEK_END_DATE,
WEEK_TIMESPAN,
MONTH_ID,
MONTH_DESC,
MONTH_END_DATE,
MONTH_TIMESPAN,
QTR_ID,
QTR_DESC,
QTR_END_DATE,
QTR_TIMESPAN,
YEAR_ID,
YEAR_DESC,
YEAR_END_DATE,
YEAR_TIMESPAN
Just "map" this table/view to the 5-level time dimension in AWM.
NOTE that behind-the-scenes lot of useful structures are automatically defined to support time-series measures,
and there are lot of calculation templates available also.
Since you came from Express background, I have to say that try to use new OLAP Expression Syntax when creating calculated measures instead of OLAP DML.
Its very rare these days that we need OLAP DML.
Edited by: Nasar on Nov 22, 2012 12:11 PM -
Well it seems time is running out on the date dimensions.
The max day is on 12/30/2010, so how to extend the dates to 2015 on all date dimensions using DAC?
thanks for the help!1By default most of the SIL jobs for populating the Day dimension are not run in the incremental apart from the update job which takes the data form W_DAY_D itself (this is how it is 7.9.5 not sure if it behaves diff in 7.9.6)
The best option and probably the easiest one would be to insert it manually.
* Remember you should not trunacte and reload just this table as it would screw up the wids and your warehouse ;) -
Primary Key Data type in Time Dimension????
I have to create a Time dimension with day grain in a Datawarehouse system and I donât know what is the best data type for the primary key...
For example
1) I could put Number(8) datatype, then the dates will be: 20050114, 20050115, 20050116.... Then in the fact tables I put the Number(8) datatype in the date fields... But in my reporting tools I have to put the to_date function to show the dates in the right format.
2) Or I could put Date datatype, then the dates will be: 01/14/2005, 01/15/2005, 01/16/2005.... Then in the fact tables I put the Date datatype in the date fields...
Itâs the Date primary key a bad datatype? (Very slow)
What is the best Primary Key Data type in Time Dimension???
Thanks!<quote>I have to create a Time dimension with day grain</quote>
OK.
<quote>But in my reporting tools I have to put the to_date function to show the dates in the right format</quote>
Why? ... if youâve decided to have a Day dimension table what is stopping you from having the day represented as a DATE column in there? (plus all the other "right formats" you may need). The join keys should only be used for ⦠joining.
<quote> Itâs the Date primary key a bad datatype? (Very slow)</quote>
No ⦠DATE or NUMBER wonât make any noticeable difference when used as the join key between the time dimension and the fact table.
Some see advantages in having the DATE FK in the fact table â¦
1. One can have range partitioning in the fact using real DATEs
2. One can get Day-derived info right from the fact table ⦠that is, the join to the Day dimension is not needed
I donât (see them as advantages) ⦠for #1, range partitioning by some measure of time is still achievable as long as the PK values on the Day dimension are immutable (as they should) ⦠and I donât see #2 as an advantage for the DW end-users.
Personally, I prefer a surrogate numeric PK ⦠but not things like 20050129.
<William>If you need dates then use dates. They are more robust, you can never accidentally have November 43rd</William>
Of course this can not be about the fact table ⦠since there the column is constrained ⦠so this is about accidentally getting "November 43rd, 2004" into the Day dimensions when the PK is numeric 20041143; true, but is a DATE PK more robust in this case? ⦠No ⦠one could accidentally insert to_date('29-Jan-2005','DD-Mon-YYYY') and to_date('29-Jan-2005 00:00:01','DD-Mon-YYYY HH24:MI:SS') and that won't be very good, would it? In both cases, one would need something extra to 100% protect the integrity of the Day dimension (mind you, loading the Day dimension probably happens once a year under the supervision of the most technical people on the project).
There is no best PK data type for the Day dimension (between NUMBER and DATE) ⦠they are both workable solutions ... go with what youâre comfortable. -
After upgrading to OWB 9.0.4, we decided investigate combining several projects into one because the location and connectors will allow each developer to deploy their portion of the project to their own schema. We also think this will help us keep our dimensions which are shared across the projects conformed.
The simplest examples of our conformed dimensions are Time, Day, and MarketingCampaign (We're not using the built-in time and day dimensions). Previously we had a COMMONS project where these types of dimensions and functions were kept as the golden copies and then copied and pasted into the various projects. Nasty, but it basically worked.
Now we moved these to a COMMON_DIMENSIONS warehouse target in our combined project. Mappings from other warehouse targets can use the dimensions in the common area just fine, however, the facts in other warehouse targets are not able to reference the common dimensions as foreign keys.
Is there any way to get around this, or do we have to go back to copy and paste method again?I did find a workaround for this, though it's not ideal.
1. Go to the fact (cube now in 9.0.4) editor by right clicking and choosing "Editor" (double clicking gives you the properties which is not what you want)
2. Choose "Table Properties" from the Edit menu at the top.
3. Manually add the columns you want to refer to the dimensions in the other module.
4. Then manually add the foreign key constraints which refer to the column in the other module ("Referenced Application" column in the constraint table)
As far as I can tell from looking at the generated DDL, there is no difference between these foreign keys and the ones to dimensions in the local module. The only difference is in the OWB fact editor and properties because these are not included unless you look under the table properties in the editor.
Another issue I've run into with this is since you can't specify the deployment order sometimes different deploy actions can fail depending on what order OWB runs the DDL scripts in, so you might have to manually deploy a few things. I plan to setup OMB scripts for our deployment anyway so we can integrate our OWB projects into our automated build process. -
Hi .. I am using Axis(1) to select all the retrieved records. The MDX query looks like-
WITH MEMBER [Measures].[New Opportunity Count]
AS SUM(
{DESCENDANTS(
[Opportunity].[Opportunity].CURRENTMEMBER,
1
iif([Measures].[Opportunity Sales Days - Invisible] > 0,1,0)
//HAVING [Measures].[New Opportunity Count] = 1
MEMBER [Measures].[Latest Opportunity Count]
AS SUM(
EXCEPT( AXIS(1),
[Opportunity].[Opportunity].[All]
),[Measures].[New Opportunity Count])
MEMBER [Measures].[Opportunity Sales Days]
AS iif([Measures].[New Opportunity Count] =0,0,
iif([Opportunity].[Opportunity].CURRENTMEMBER.MEMBER_KEY =[Opportunity].[Opportunity].[All].MEMBER_KEY,
(SUM(
EXCEPT(AXIS(1),
[Opportunity].[Opportunity].[All]
),[Measures].[Opportunity Sales Days - Invisible])/[Measures].[Latest Opportunity Count]),
[Measures].[Opportunity Sales Days - Invisible]/[Measures].[New Opportunity Count])
SELECT
[Measures].[Latest Opportunity Count],
[Measures].[New Opportunity Count],
[Measures].[Opportunity Sales Days]
}ON COLUMNS,
[Opportunity].[Opportunity].&[{140D9883-6F49-E011-AEA0-00155D032A00}],
[Opportunity].[Opportunity].&[{3A2BB124-EE85-E011-8A06-00155D032A00}],
[Opportunity].[Opportunity].&[{60036FE8-DC48-E111-975F-00155D032A00}],
[Opportunity].[Opportunity].&[{CA158EE5-C445-E111-975F-00155D032A00}],
[Opportunity].[Opportunity].&[{B69F83EB-832D-E211-9861-00155D032A00}],
[Opportunity].[Opportunity].&[{D500AE90-606C-E211-83AD-00155D03570D}],
[Opportunity].[Opportunity].[All]
// [Opportunity].[Opportunity].members
ON ROWS
FROM [IMGROUP Base]
It works fine in SSMS editor, but while trying to access the same query from Excel pivot table, it gives the error : "Slicer axis cannot be referenced". I have taken the MDX query from excel and it looks like -
SELECT NON EMPTY Hierarchize({DrilldownLevel({[Opportunity].[Opportunity Hierarchy].[All]},,,INCLUDE_CALC_MEMBERS)}) DIMENSION PROPERTIES PARENT_UNIQUE_NAME,HIERARCHY_UNIQUE_NAME,[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Account Manager],[Opportunity].[Opportunity
Hierarchy].[Opportunity].[Opportunity Actual Close Date Time],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Age In Days],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Close Date],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity
Created On Date],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Created On Date Time],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Days In Sales Stage],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Delivery
Owner],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Estimated Close Date],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Estimated Project Duration In Days],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity
Estimated Project Duration In Months],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Estimated Project Duration In Working Days],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Estimated Project End Date],[Opportunity].[Opportunity
Hierarchy].[Opportunity].[Opportunity Estimated Project First Working Day Date],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Estimated Project Last Working Day Date],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Estimated
Project Start Date],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Latest News],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Latest News Updated On Date Time],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity
Lost Competitor],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Originating Lead Name],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Owning Organisation],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity
Revenue Spread],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Sales Assist],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Sales Assist-Hidden],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Sales Stage],[Opportunity].[Opportunity
Hierarchy].[Opportunity].[Opportunity Sales Stage Updated On Date Time],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Source Full Name],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity State],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity
Sub Source],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Updated On Date Time],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Won Lost Description],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Won Lost
Reason] ON COLUMNS FROM (SELECT ({[Opportunity].[Opportunity Hierarchy].[Opportunity].&[{B69F83EB-832D-E211-9861-00155D032A00}], [Opportunity].[Opportunity Hierarchy].[Opportunity].&[{CA158EE5-C445-E111-975F-00155D032A00}], [Opportunity].[Opportunity
Hierarchy].[Opportunity].&[{60036FE8-DC48-E111-975F-00155D032A00}], [Opportunity].[Opportunity Hierarchy].[Opportunity].&[{3A2BB124-EE85-E011-8A06-00155D032A00}], [Opportunity].[Opportunity Hierarchy].[Opportunity].&[{140D9883-6F49-E011-AEA0-00155D032A00}]})
ON COLUMNS FROM [IMGROUP Base]) WHERE ([Measures].[Opportunity Sales Days]) CELL PROPERTIES VALUE, FORMAT_STRING, LANGUAGE, BACK_COLOR, FORE_COLOR, FONT_FLAGS
Any help, will be greatly apreciated.
Sayan.Sorry, it was a mistake in my query. Now I have corrected each of them and individually each of them works fine. See below-
CREATE MEMBER CURRENTCUBE.[Measures].[New Opportunity Count]
AS SUM(
{DESCENDANTS(
[Opportunity].[Opportunity].CURRENTMEMBER,
1
iif([Measures].[Opportunity Sales Days - Invisible] > 0,1,0)
VISIBLE = 0 ,
ASSOCIATED_MEASURE_GROUP = 'Opportunity';
CREATE MEMBER CURRENTCUBE.[Measures].[Latest Opportunity Count]
AS SUM(
EXCEPT(Axis(0),
[Opportunity].[Opportunity Hierarchy].[All]
),[Measures].[New Opportunity Count]),
VISIBLE = 0 ,
ASSOCIATED_MEASURE_GROUP = 'Opportunity';
CREATE MEMBER CURRENTCUBE.[Measures].[Opportunity Sales Days]
AS iif([Measures].[New Opportunity Count] =0,0,
iif([Opportunity].[Opportunity].CURRENTMEMBER.MEMBER_KEY =[Opportunity].[Opportunity].[All].MEMBER_KEY,
(SUM(
EXCEPT(AXIS(0),
[Opportunity].[Opportunity Hierarchy].[All]
),[Measures].[Opportunity Sales Days - Invisible])/[Measures].[Latest Opportunity Count]),
[Measures].[Opportunity Sales Days - Invisible]/[Measures].[New Opportunity Count])
VISIBLE = 1,
DISPLAY_FOLDER = 'Days',
ASSOCIATED_MEASURE_GROUP = 'Opportunity';
CREATE MEMBER CURRENTCUBE.[Measures].[Opportunity Actual Value Home Currency New]
AS SUM(
{DESCENDANTS(
[Opportunity].[Opportunity].CURRENTMEMBER,
1
iif([Measures].[Opportunity Sales Days] > 0,[Measures].[Opportunity Actual Value Home Currency],0)
VISIBLE = 0,
ASSOCIATED_MEASURE_GROUP = 'Opportunity' ;
CREATE MEMBER CURRENTCUBE.[Measures].[Opportunity Actual Revenue Per Sales Day]
AS iif([Measures].[Opportunity Actual Value Home Currency New] =0,0,
iif([Opportunity].[Opportunity Hierarchy].CURRENTMEMBER.MEMBER_KEY =[Opportunity].[Opportunity Hierarchy].[All].MEMBER_KEY,
(SUM(
EXCEPT( AXIS(0),
[Opportunity].[Opportunity Hierarchy].[All]
),[Measures].[Opportunity Actual Value Home Currency New])/[Measures].[Opportunity Sales Days]),
([Measures].[Opportunity Actual Value Home Currency New]/[Measures].[Opportunity Sales Days]))
FORMAT_STRING = "£#,##0.00;-£#,##0.00;#",
VISIBLE = 1,
DISPLAY_FOLDER = 'Financial',
ASSOCIATED_MEASURE_GROUP = 'Opportunity';
But, when I want to select them together from Excel, I am geeing the below error-
CellOrdinal 0
VALUE #Error MdxScript(IMGROUP Base) (1436, 7) Members, tuples or sets must use the same hierarchies in the EXCEPT function.
FORMAT_STRING £#,##0.00;-£#,##0.00;#
LANGUAGE (null)
BACK_COLOR (null)
FORE_COLOR (null)
FONT_FLAGS (null)
The generated MDX in Excel as -
SELECT {[Measures].[Opportunity Actual Revenue Per Sales Day],[Measures].[Opportunity Sales Days]} DIMENSION PROPERTIES PARENT_UNIQUE_NAME,HIERARCHY_UNIQUE_NAME ON COLUMNS , NON EMPTY Hierarchize({DrilldownLevel({[Opportunity].[Opportunity Hierarchy].[All]},,,INCLUDE_CALC_MEMBERS)})
DIMENSION PROPERTIES PARENT_UNIQUE_NAME,HIERARCHY_UNIQUE_NAME,[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Account Manager],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Actual Close Date Time],[Opportunity].[Opportunity
Hierarchy].[Opportunity].[Opportunity Age In Days],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Close Date],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Created On Date],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity
Created On Date Time],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Days In Sales Stage],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Delivery Owner],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Estimated
Close Date],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Estimated Project Duration In Days],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Estimated Project Duration In Months],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity
Estimated Project Duration In Working Days],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Estimated Project End Date],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Estimated Project First Working Day Date],[Opportunity].[Opportunity
Hierarchy].[Opportunity].[Opportunity Estimated Project Last Working Day Date],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Estimated Project Start Date],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Latest News],[Opportunity].[Opportunity
Hierarchy].[Opportunity].[Opportunity Latest News Updated On Date Time],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Lost Competitor],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Originating Lead Name],[Opportunity].[Opportunity
Hierarchy].[Opportunity].[Opportunity Owning Organisation],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Revenue Spread],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Sales Assist],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity
Sales Assist-Hidden],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Sales Stage],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Sales Stage Updated On Date Time],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity
Source Full Name],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity State],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Sub Source],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Updated On Date Time],[Opportunity].[Opportunity
Hierarchy].[Opportunity].[Opportunity Won Lost Description],[Opportunity].[Opportunity Hierarchy].[Opportunity].[Opportunity Won Lost Reason] ON ROWS FROM (SELECT ({[Opportunity].[Opportunity Hierarchy].[Opportunity].&[{B69F83EB-832D-E211-9861-00155D032A00}],
[Opportunity].[Opportunity Hierarchy].[Opportunity].&[{60036FE8-DC48-E111-975F-00155D032A00}], [Opportunity].[Opportunity Hierarchy].[Opportunity].&[{3A2BB124-EE85-E011-8A06-00155D032A00}], [Opportunity].[Opportunity Hierarchy].[Opportunity].&[{E2E48CB7-8463-E411-831D-00155D035708}],
[Opportunity].[Opportunity Hierarchy].[Opportunity].&[{140D9883-6F49-E011-AEA0-00155D032A00}]}) ON COLUMNS FROM [IMGROUP]) CELL PROPERTIES VALUE, FORMAT_STRING, LANGUAGE, BACK_COLOR, FORE_COLOR, FONT_FLAGS
Any help?
sayan maity -
Hi,
I have an universe based on Teradata. I created a filter in IDT and it's like this :
@Select(Sales\Calendar Day) = @Prompt('Date:','D',,Mono,)
When I use this filter and execute a test query in IDT, the date format is shown different in these 2:
Enter a value : 10.Feb.2015
Date : 10.Feb .2015 00:00:00
I formatted the Calendar Day dimension and I can see it as 'mm/dd/yyyy' in the report result. That's fine.
However, I want to do the same for the prompt screen in IDT too. How can I do this?
The requirement is, I use the same filter for SAP Lumira and it does not provide a calendar component for date selection.
So, the format of date to pass to universe is not clear.
Thank you!Hi
Try to change the format Cal day using below options, and then check the filter date format is showing as per your requirement
predefined function TO_CHAR
Use the custom display format option.
Please find the below link for more info
BI4.1 Business Layer Enhancements - Create Display Format -
DAC: Increase $$END_DATE in W_DAY_D
Hi All,
Currently we are using BI Apps version of 7.9.5, we found that in W_DAY_D table data is till Dec
30th 2010 only. How we can load data till 31st Dec 2020 in same table. There are 2 parameters
used in the SIL_DayDimension mapping $$START_DATE and $$END_DATE.
$$START_DATE = 01/01/1980
$$END_DATE = 12/31/2010
If we change the END_DATE value in parameter to 12/31/2020 and then load Day Dimension will it
load till 2020? Please let me know what steps need to follow to load till Dec 31st 2020.
Thanks in Advance.
Regards,
BhoomiHi,
We are using Dac Build AN 10.1.3.4.1.20090415.0146.
The start date is 01-Jan-1980 and end date 31-dec-2010.
I am interested to change the end date to 31-dec-2020.
For that I have created a custom container.
Design -> Task -> Query on SIL_DayDimension ->Parameters
Click on value, change the end_date to required value.
Save.
Setup -> Physical Datasource
Click on DataWarehouse.
Change W_DAY_D Refresh dates to null.
After running DAC W_DAY_D table is not having any record and end_date is showing as blank in paramter file
So I want to change it to original one that is as it was before.
When I de-clone it, the value for end_date is showing as Custom Format() @MM/DD/YYYY and if I add any value to it the after running dac end_date is showing as blank in paramter file and W_DAY_D table is not having any record.
Any help is greatly appreciated.
Regards,
Bhoomi -
Time series functions in OBIEE
Hi
I am new to OBIEE.
In Report i want to use the AGO function to find the previous quarter revenue
But the AGO function requires time dimension level as shown in following syntax
how should i insert it in the function
Syntax
AGO(expr, [time_level], offset)
Thanks
SravanthiOnce you have day dimension with checked for 'Time dimension'
you can see day dimension in rpd expression builder, once you select the function you'll choose each columns.
for ref:
Check these links
http://gerardnico.com/wiki/dat/obiee/ago
or
http://iniu.net/content/obiee-time-comparison-using-time-series-function-ago
Pls mark as correct
Maybe you are looking for
-
Problem in sending mail for a pop3 account using transport.send(msg)
hi, i am having problem in not able to send mail for a pop3 account ... I have written an email gateway which listens to my pop3 account...on email arrival it listens nd extract the contents and send it as an sms msg...upon failure it needs to delive
-
Application builder error creating
After install Labview 9.0f2, no longer is possible to build application Solved! Go to Solution.
-
Repair permissions - always the same ones need repairing (Shockwave)
Each time I do a Repair Permissions after doing an installation (in this case Security 008 update for Intel on my MBP) the same permissions always are repaired and ONLY these. Here's the report I always get: Permissions differ on ./Library/Applicatio
-
I bought qq斗地主 for free and end up paying $15
in Oct I spot the game as above and it was for free, but I end up paying $15 for no reason
-
Excel not respondin when I send data
Hi All, I have created an Input chedule and when I try to send data, excel is not reponding. Could any one help me why this happens?