Change time dimension to persian calender

Hi ,
i have a time dimension which i have created it with OWB time wizard .
dates in my data sources are in Christian calender , i wanna show persian calender for end user .
how can i convert christian calnder to persian in presentation layer ?
Regards
Padideh

You can add three column in your time table and calculate the persian date from the gregorian date with a pl/sql transformation.
You can find on the internet some program that you may have to transform in PL/SQL :
http://www.farsiweb.info/jalali/jalali.phps
Cheers
Nico

Similar Messages

How Can I do automated update base on changing TIME dimension ?

I am a beginner of ESSBASEhow Can I do automated update base on changing TIME dimension ? how can I deal with the change of TIME dimension ? shall I update outline?one more question,how can i deal with the dimension like this:------gp--------- p1-----------c1-----------d1--------- p2-----------c2-------------cc2-------------cd2-------------ce2 -----------c3-----------c4 --------- p3the un-balance dimension? shall I make them to balance?

Hi man, where are you from?If you are a spansh spoken please send again the problem in Spanish cause I can't understand exactly what do you need.Greetings,Raleksander

Can I set calender invite to set at the same time, even when changing time zone. for example I am in the UK have set a meeting for 10am in NYC for weds, but when getting to NYC it is still set at 10am and doen't adjust to time zone?

Can I set my Calendar invites on a IOS 7 device to set at the same time, even when changing time zones. For example I am in the UK and need to set a meeting for 10am NYC time on Wednesday, but when I reach NYC I don't want the time zones to adjust which will then adjust my meeting I set in the UK to NYC time.

Here are the individual files for those that fear the my other file of virii.
Attachments:
HASP.vi ‏88 KB
File Setup.vi ‏11 KB
Gather and Output.vi ‏149 KB

Getting error while deploying a cube with time dimension

Hi,
I created a time dimension using WB with Cal yr and day heirarchy. Designed a cube using both and tried to deploy it. I got the following error.
Appreciate your help..
Name
Type
Status
Log
TIME_CUB1
Cube
Success
VLD-0001: Validation completed successfully.
TIME_CUB1
Description : Runtime User : OWB_REP_OWNER Started : 2006-12-13 15:37:17.0
Name
Action
Status
Log
TIME_CUB1
Create
Error
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "OLAPSYS.CWM2_OLAP_CUBE", line 394
ORA-06512: at line 5

Hi,
I'm having problems to deploy this cube (this was the origin of my problem), when I change it to "Deploy Data Object Only", It don't generate code and the cube is not created. This is what I get:
-- Product : Oracle Warehouse Builder
-- Generator Version : 11.1.0.6.0
-- Created Date : Wed May 12 08:41:59 CST 2010
-- Modified Date : Wed May 12 08:41:59 CST 2010
-- Created By : edennis
-- Modified By : edennis
-- Generated Object Type : TABLE
-- Generated Object Name : FACT_TMP_SALDOS
-- Comments :
-- Copyright © 2000, 2007, Oracle. All rights reserved.
WHENEVER SQLERROR EXIT FAILURE;
Ideas?
Thanks for your help!

Creating Time dimension in BW data model. - like seen in logical data model

Hello all,
I have been struggling with this thing and I am looking for some help from anyone on this forum.
We are trying to create a logical data model of our bw system. We are going live next month with Student module for universities. We have multiple Infocubes and DSO and since there is so much crossing over in between them most of the reporting is done on infosets.
One of the thing we were thinking; is it possible to create something like a common time dimension table for every infoprovider. Basically when we are providing the reports to the end user can we give them a drop down menu which gives a time frame for reporting rather than selecting.
Example: Like can we create something which looks in the drop down like current month data, last months data, three months ago, four months ago, five months ago, one year ago, two years ago. Can we make like these data slices in our cube and deliver it to the end user?
We have in our cube a few date infoobjects, like receipt date, decision date, cancellation date and like wise.
Please let me know if any one has done any similar thing, it will be very helpful.
Thank you so much in advance.

if you add your common time dimension to your data model, first identify for each infoprovider the time against which 'current month' and other frames should be applied and map them to your dimension.
just a question... are you not using time dimension in cubes ? ideally this should be your time dimension llinking all.
when you use time dimension which uses 'current month' , 'current year' , you will have to address their historisation as well. (because current month now will not be so current after 2 months).
so in data load procedure every day these values need to change (meaning drop and reload).
and routines to populate these values based on reporting date.
Edited by: hemant vyas on May 6, 2009 1:56 PM

How do I change the dimensions of an image? The Image Size dialog box will not allow me to change it

How do I change the dimensions of an image? The Image Size dialog box will not allow me to change dimensions. I am taking an online class and the Image Size dialog box looks different than the one I am seeing in Photoshop CC. It has the option to change the dimensions.

When you say chage the dimentions, do you mean crop the image and adjust the size of the image at the same time, or do you mean you want to just resize the image? Can you post a screen shot of what you're trying to do?

Time Dimension Roll-Up Not Working

Hi Gurus,
We are on BPC NW 7.0 SP04. We are experiencing a strange problem with Time dimension. Even after defining the hierarchy correctly, the values are not being rolled up the hierarchy. Our requirement is to capture data at quarter level and year level. So we have defined the time dimension in following manner:
ID                     EVDESCRIPTION   PARENTH1     LEVEL         YEAR   PERIOD STYLE   MONTHNUM    TYPE   TIMEID           HLEVEL
2007.TOTAL     2007 TOTAL                               YEAR             2007     TOTAL   T3                12                       ACT   20070005        1
2007             2007                   2007.TOTAL   QUARTER     2007     Q1        T2                13                       ACT                        2
2007.Q1             2007 Q1                   2007.TOTAL   QUARTER     2007     Q1        T1                  3                       ACT   20070001        2
2007.Q2             2007 Q2                   2007.TOTAL   QUARTER     2007     Q2        T1                  6                       ACT   20070002        2
2007.Q3             2007 Q3                   2007.TOTAL   QUARTER     2007     Q3        T1                  9                       ACT   20070003        2
2007.Q4             2007 Q4                   2007.TOTAL   QUARTER     2007     Q4        T1                12                       ACT   20070004        2
Here TYPE is a custom dimension property . As the members depict, 2007.TOTAL value should be calculated as the sum of 2007.Q1, 2007.Q2, 2007.Q3 and 2007.Q4 (Quarters and Years are mutually exclusive in our case). But when we maintain data for Q1,Q2,Q3 and Q4, the TOTAL value is displayed as the value of Q4, and not the sum of quarters. We have tried changing MEASURES from PERIODIC to QTD and YTD, with no effect. We thought that it could be a problem with BI, and so built a simple BeX Query on top of the BPC application cube. But in the BEX query, the time dimension is properly aggregated, nd values are displayed correctly. So apparently it is not a problem with BI. In that case, we are missing something in BPC itself. Can any of you identify what it could be? Awaiting answers and Thanking in Advance.
Sincere Regards,
Amitabha

Amitabha,
It's just a problem that a lot of people run into when they are getting used to BPC. Once you see it happen to 10 or 15 people, you can start to recognize it pretty quickly
There are not a lot of examples of this in the Netweaver documentation. I think there are more in the Microsoft docs. However, there is mention of it on this page in the Netweaver documentation: [http://help.sap.com/saphelp_bpc75_nw/helpdata/en/65/84d6596224477d80cc8a4392e4c114/frameset.htm]
Ethan

Time Dimension and database 8.1.7.3

Hi,
I imported owb_bp project that is located in: <OWB install directory>\owb\misc\time directory into my OWB. Then i copied the standard time dimension and mapping from that project to my project. I changed the necesary things(removed day level, did reconcile inbound on a dimension in a mapping with "match by bound name" strategy) in the dimension and mapping and when i tried to deploy the mapping i got an error:
VLD-3268: A mapping can be deployed only if the database version is Oracle 9.2 or higher.
Is it true that you need Oracle 9.2 or higher for deploying this kind of time dimension. If that is so, how can i create a time dimension that is going to work with Oracle 8.1.7.3
Thx

Thanks for your answer Igor.
The problem is that we cant upgrade our database to 9.2, becouse our customers dont use it, so we are stuck with 8.1.7.3, which by the looks of things doesnt support a lot of things in OWB 9.04.
So I would really appreciate it if someone could give me some pointers as to how to generate data for time dimension, thats going to work on database 8.1.7.3.
Thanks you all for your time.

TIME dimension processing fails saying "..attribute key cannot be found.." in EPM 10

After upgrading from version 7.5 to EPM 10, when we ran a ‘Full Process’ on the TIME dimension, it ran into an error saying “Errors in the OLAP storage engine: The attribute key cannot be found when processing: Table: 'dbo_tblFactCapEx', Column: 'TIMEID', Value: '20090013'. The attribute is 'Time_TIMEID'. (1/13/2015 2:41:02 PM)”.
Full error message is attached herewith – ‘Time Dimension Error.txt’
After researching, we did discover that MONTHNUM needed to be converted to BASE_PERIOD. Re-processed which produced the same error.
Prior to migration to version 7.5, we ran a full process on TIME dimension there. It completed successfully, confirming the issue is only with version 10.
Confirmed we could see the TIMEID value of 20090013 in the following places:
Time Dimension in the appropriate TIMEID attribute column.
Confirmed mbrTIME table had base member ID with TIMEID attribute filled out correctly.
Data in tblFactFINANCE could be pulled using that TIMEID
We truncated all the records in all the fact tables associated to this TIME dimension.
Eventually, when none of the tables had any records, the TIME dimension then processed successfully.
We this began to suspect the issue may not really be related to bad records.
We conducted one more test to confirm this.
Using an input form in EPM 10, we manually entered data in one of the models (at this point none of the fact tables have any records)
Ran Full Optimize on that model with Compress Database and Index Defragmentation checked – This step failed with the error attached in ‘MatrixRateFullOptimize.txt’
Ran Full process on Time Dimension – Failed indicating issue with TimeID 2012001 (that’s my manual entry). Attached error report ‘TimeDim Error MatrixRate.txt’
At this point, the table only contains the manually entered records (no suspected bad records)
We then suspected there could have been an issue with the upgrade process.
So we reprocessed all the dimension and optimized all the models in version 7.5, made a new backup and restored it to version 10.
The issue still persisted!
At this point, we have tried all the possibilities we could think of. Each time the fact table is populated with records, the TIME dimension process fails indicating ‘the attribute key’ cannot be found.
There is probably something in the OLAP partition that is not able to link the dimension attributes to the cubes.
Additional Information:
Please find attached the existing Time Dimension – TimeDimensionMembers.xlxs
Version of Excel used: Excel 2007, SP3 MSO (12.0.6683.5000)
System Specs: Please see screenshot below.

Thank you all for responding! This issue is resolved.
Here’s what the issue was:
The time structure is TOTAL >> Years >> Quarters >> Months (e.g. T.ALL >> 2012.TOTAL >> 2012.Q1 >> 2012.P01)
As shown in the screenshot below, the LEVEL for ‘T.ALL’ member was set to YEAR, which is incorrect (we can’t have Year rolling up to a Year)
We changed the LEVEL to ‘TOTAL’ and this fixed the issue!!
If only it gave a better error message than the “..attribute key not found” message

Modifying Existing Time Dimension

Hi All,
Presently I have a Time Dimension and a Fact table which has a FK to this Dimension. The Time Dim has a level upto hourly values.
Now it's in production and I need to change the Time Dim to take on minutes 'cause some reports need minutes.
1. So what is the best way to go about this?
2. Is it better just to add another extra field which has the required date, in the fact table?
3. How can the existing data be easily ported to the new Time Dim(if it has a minute-level)?
Thanks,
Justin.

I am wondering how you implemented the time dimension which only has a level up to hourly values. Do you mean the time dimension only has 24+1 = 25 rows? Usually the time dimension is separate from the date dimension and its lowest level values are minutes or seconds, depending on the business requirements. Therefore the time dimension should have 24X60 + 1 or 24X60X60 +1 rows.
The solution is depended on what you want.
My suggestion is as the follows:
1.     Create a new time dimension with the desired lowest level values (minutes or seconds).
2.     Create or modify the foreign key of the fact table to point the new created time dimension.
3.     Modify the ETL mappings.
4.     Option 1: If you want the new functionality available for the existing rows in the fact, you have to reload the fact no matter which approach you use.
Option 2: If you only want the new functionality available for the subsequent refresh load, you can modify the foreign-key values pointing to the old time dimension to the new time dimension, using the rule XX --> XX:00 or XX --> XX:00:00 (where XX is the hour number in the old dimension). In the subsequent refresh load, map the foreign-key values to the actual time.
Maybe other else can provide better solutions. IF so, please let me know.
Good luck!

Setting up a TIME dimension in OBIEE

Hi,
We have an Oracle OLAP Cube built using AWM v10.2.0.3A. We have also created a relational view for this cube (using the OLAP view generator) and are now using this view as a data source in OBIEE v.10.1.3.3.2.
As part of defining the Time dimension in the Business Model Layer of OBIEE repository, we have done all the relevant mappings to the TIME dimension as in the AWM Cube and have marked the dimension as type 'TIME'. Also, for the TIME logical table, we have defined each level (All Years, Year, Month, Quarter, and Day) to have its own chronological key with unique values at all levels. The primary key for our TIME table in the business layer is 'Day'. This level 'Day' is mapped to TIME_DAY_LVLDSC column of the relational view created over the AWM cube. The data type for this column is "VARCHAR". (We basically picked up all the 'Description' columns while creating the view over the cube!)
With this background of the TIME dimension structure, here is the problem scenario:
When we try to create a report with one AGO and one TODATE function defined over the "Day" level (both are defined as logical columns), then the report takes forever to run and never comes back with any data/error even for a handful of rows. We are seeking the forum's help on the following:
1. Is it necessary for the primary key 'Day' of the TIME logical table to be of type DATE? If yes, does this mean that we have to change the column data type in our cube (or select a 'date' type column to be a part of the view and then redo the mapping in the repository) or do we just make a change to the column data type in the physical layer of OBIEE repository?
2. Going by the description above, is there something missing (other than point 1. above) in the setup of the TIME dimension in OBIEE so as to make it usable for Time Series type of calculations/functions?
Any help is much appreciated.
Thanks and Regards,
Piyush

Hi Wildmight,
Thanks a lot for your kind inputs.
1. No, VARCHAR is fine. You should have also defined unique time keys in your time dimension (Quarter Year, Month Year) and check box 'time dimension' in the properties of your time dimension.
-->> The Time dimension that we have defined in the Business layer of the repository is mapped to the respective level columns in the AWM cube and has already got unique members at each level. We are using the "Description (LVLDSC)" columns for each level and have defined the "Description" column to have unique values at each level. A sample data set looks like :
Year:
2007
2008
Quarter:
QUARTER1 2007
QUARTER2 2007
QUARTER1 2008
QUARTER2 2008
Month:
JANUARY 2007
FEBRUARY 2007
JANUARY 2008
FEBRUARY 2008
Day:
Monday, January 1st 2007
Tuesday, January 2nd 2007
So in the above case, do we still need to define a unique key for each level like Quarter Year, Month Quarter, etc.? (Please note that the check box for 'TIME' dimension is checked !)
2. Is your AGO based on TODATE? or your TODATE based on AGO?
-->> I am not sure what this really means - however I can tell you that we have created two new logical columns (in the fact table in Business Layer) : one to show the measure as TODATE for Day level, and the other to show the measure as Day Ago.
So it means that we are trying to create two reports with three columns as below:
- Day Measure on Day Measure Todate (Day)
- Day Measure on Day Measure Day Ago (Day, 1)
I hope I have been able to clarify the problem scenario with this. Does this setup seem correct to you?
Many thanks for your help.
Best Regards,
Piyush

Ibooks changes the dimensions of cover image

I have been working on an epub using Calibre as the converter platform. I have used the program in the past and it always works until now. I am working on a new book and the cover image dimensions are changed in iBooks. The image looks correct when I view it in an image viewer.
I have revised the cover image several times to change the dimensions, change the file size, modify the pixel count. The current dimensions are 1500 by 2400 pixels which is a size I have used before. The file size is 226kB. Any suggestions on how to get the cover image to show up correctly?

You don't think it would be that hard to get ACR to better match the in-camera engine...
I understand if its not able to read the "special" in camera user settings, such as increase saturation, etc as that may be proprietary...
But it (ACR) already knows what type of camera you are using... It would be nice if Adobe would make it at least set to better match the out-of-box camera settings per camera... it would be a much better starting point than the flat, discolored images I see, IMHO.
Example... the reds in my Rebel XT RAW's always come up orange, both in LR and ACR.

How to time dimension

How do you link a time dimension to the fact table?
If the time dimension has a sequence as the PK then
the following columns:
year
month
quarter
day
time
etc..
How is the fact table connected to the time dimension if the fact table has the
primary key as a FK in the fact table?
-Jim

Hi Ragnar
Because a date is in fact stored as a number you don't need a surrogate key for your time dimension. You can make the primary key the date itself. Then you just join from the fact to the time dimension on the date.
Oh yes, you would need to populate the time dimension before loading the fact table. But then this is true of all star schemas. You must populate the dimensions before you populate the facts.
However, in the case of time, because it never changes over time (pardon the pun) you could load years of dates way out into the future. Then you would never have to worry about it for a while.
I have customers who are using E-Business Suite where the time dimension is fed from GL_PERIODS and BOM_CALENDAR_DATES. Because the periods are entered once per year in most cases then they only need to run the load once per year. Matrialized vieww of time work well too.
Hope this helps
Regards
Michael

Time Dimension, i don´t bind the fact dimension and the time dimension

Well i don´t know why my fact table don´t bind with the time dimension, i create a time table in the data base and change the key to int32 for example year(date)*10000+month(date)*100+day(date), and create to similar in the fact table, and
this attributes binding, when i process the dimension all result without problems, after i process the cube and all result without problems, but when i try to deployment the browser, the measures in all years are equals, please help me

Hi franciscofelipe,
According to your description, you find the measures shows all same value for all years of time dimension. Right?
In this scenario, since your change the key of your time table into an integer, when pulling this dimension out in Browser, the measure will only regards those members as numeric value instead of date so that is will show an aggregate value. Even
all the members are displayed properly in your dimension. So please change the attribute type into appropriate date type.
If you have any question, please feel free to ask.
Regards,
Simon Hou
TechNet Community Support

Time Dimension in Dynamic Reporting

When creating a report that compares a current period (for example 2015.FEB) to the same period in the prior year (2014.FEB), what is the best logic to use in a report? Do I use a local member formula to perform this? I am willing to build in a property within the Time Dimension table if necessary.
I will probably have the same need to compare current period (2015.FEB) to prior period (2015.JAN) in the same report.
The average user isn't very knowledgeable working with reports besides picking from the context drop down so it needs to be where they pick the current month (2015.FEB) and the report does the rest.
***It should also be noted that we recently switched from a calendar year to fiscal year so it will not work to reference for example Period 2 in each year since 2014.FEB is period 2 and 2015.FEB is period 11 in each year respectively.
Thanks for the help.
Steve

Shrikant,
See attached 4 screenshots of all of the properties that I have in the time dimension.
We only have one hierarchy for time. As you can see its a little complex going from a calendar year reporting structure to a fiscal reporting structure. 2014 was a "short" year because of the change.
Thanks in advance,
Steve

Change time dimension to persian calender

Similar Messages

Maybe you are looking for