10g - Most detailed table in the time dimension table source is not unique

hi, experts,
I cannot find any solution from google. please help
ERRORS:
BUSINESS MODEL ERP:
[38093] Most detailed table in the time dimension table source 'ERP_YEAR_MONTH' is not unique.

Hi Forreging,
the time key is incorrectly specified at the lowest level. In the 'ERP_YEAR_MONTH' table, have you correctly specified the primary key for the table?
For example, if the lowest level of granularity is MONTH, then the appropriate key is probably a combination of YEAR and MONTH (not simply MONTH).
Hope this helps,
Justin

Similar Messages

Create time dimension table in repository without data warehouse

Hi,
I want to implement only BI repository solution in my customer (not datawarehousing). Is it possible to transform the data by repository tools, so that the times columns in fact tables are categorized by the "time dimension" table?
To be more explanatory:
The "Sales" table has the "time of sale" column. It contains the timestamp when the sale was performed. I have imported this table in "physical layer" of the repository. Now I want to create a new "time dimension" table, something like:
CREATE TABLE dimension_time (
Day_Key INT NOT NULL PRIMARY KEY,
Day_Timestamp DATETIME NOT NULL,
Day_Name NVARCHAR(32) NOT NULL,
Day_Text NVARCHAR(32) NOT NULL,
INSERT INTO dimension_time VALUES (20110101, {d '2011-01-01'}, '1/1', 'January 1', 'Saturday', 0, 6, 1, 1, 185, 1, 201052, 'W52', 'Week 52', 52, 201101, '01', 'January', 1, 7, 1004, 'Winter', 'Winter', 20111, 'Q1', '1st Quarter', 1, 20103, 'Q3', '3rd Quarter', 3, 20111, 'S1', '1st Semester', 1, 20102, 'S2', '2nd Semester', 2, 2011, '2011', '2011', 2010, '10/11', '2010/2011', 0);
INSERT INTO dimension_time VALUES (20110102, {d '2011-01-02'}, '2/1', 'January 2', 'Sunday', 0, 7, 2, 2, 186, 2, 201052, 'W52', 'Week 52', 52, 201101, '01', 'January', 1, 7, 1004, 'Winter', 'Winter', 20111, 'Q1', '1st Quarter', 1, 20103, 'Q3', '3rd Quarter', 3, 20111, 'S1', '1st Semester', 1, 20102, 'S2', '2nd Semester', 2, 2011, '2011', '2011', 2010, '10/11', '2010/2011', 0);
and after to add a new column in "sales" fact table for "time dimension ID" and through the repository populate this column based on the "time of sale" column and the corresponding "time dimension ID".
I know that the ETL process might perform it, but I do not want to go for Data Warehousing (it is not real - time, needs more resources, etc).
Is it possible to perform such action only on repository?
Thank you.

Hi,
I can do it, but this would be usefull only to create "time dimension" table. But also the "sales" fact table needs to be altered (thus, the "time" column will not contain the value of the time, but the ID of the corresponding time in the "time dimension" table).
I know that on DW this procedure is done automatically by the ETL process.
My question is that does the repository has any tools similar to this?
Thank you.

Populating the time dimension in ODI

I need to populate my time dimension in ODI> I read a solution in this forum suggesting to create a time table/view in the source schema, reverse it in ODI and then use it as source to populate the time dimension. Is there another way to do this? One way I thought of was to use the ORDERDATE field in my ORDER table (my source table in Oracle) and map it to my time dimension in SQL Server via an interface. But I also have DUEDATE, SHIPDATE and PAYDATE fields in my ORDERS table and this approach would mean that I have to map them through separate interfaces to the time dimension as well. I have created a procedure in the source schema(Oracle) and want to use it in ODI to populate the time dimension. But I amnt sure if that is possible in ODI. Could anyone help me with this please?
Regards,
Neel

Hi Neelab,
Sorry for my delay to reply you, I had no time the lasts days...
To get the four distinct key from your time dimension, just add four instance of dimension table at interface each one joined with one of the columns.
I believe that you load your time dimension from some other table than PRJ_TBL_TRANSACTION because you have the HolidayType column in your time dimension...
A view is one possible solution to load the time table but depends how the performance of the query is.
A way to do it at ODI is:
- Create 4 interfaces, one for each column, to load 1 singe table with 1 single date column, don't worry about duplicated value at this time, than you can just use the "IKM Control Append" that has more performance but check the "Distinct" box (flow tab) at each interface
- Create a last interface from this temp table as source, to the time dimension target table. Now you will use the "IKM Incremental Update" and do choose the "Update" option to "NO". Check the "Distinct" box.
As this table will have no more than 6.200 records from the last 20 years it will be a small table where you shouldn't have performance problems.
These are some of possible solutions but I would like to add other "way to think".
By the table that you show here you have a simple time table with no special feature, for that, let me suggest you other way.
- in the current way you will join but didn't get the record that "fail" from the join once they will be exclude if a date do not exist at time dimension
My suggestion:
- Load the dimension time table from your source table
- as PK in time dimension table, use the ''Julian Day"
- At ODI target fact table (datastore), create a 4 reference constraints (one by column) to the time dimension
- at interface do not use the dimension as source and transform the 4 date to Julian and let the 4 constraints take care if they exists or not at dimension table.
OR
- Look for the minimum "possible" date at your company
- populate your time dimension with every each day since then until a future date (Dec 31, for instance)
- create a process to populate the future date that will be execute in a interval that you decide (once a year, once a month, as you wish) dependent on how further the date is populated
- use the "Julian date" as PK
- At interface just transform any date to "Julian Date" it will be at dimension time once it is naturally unique
You could substitute the Julian date for "YYYYMMDD" that is a unique value too.
I presented you 2 way to consider be considered, each one could be used based on how important is for the business know if a date was loaded or not.
Someone can question that has the dates loaded from source against has all dates previous loaded could help to find errors from days that wasn’t loaded but it has a failure. As there are 4 dates source columns (and we are talking just about one source table until now) if a date loaded math a date when the load failure there is no value in use the time dimension date to analyze this possibility.
I defend the full time dimension load.
Make sense and/or help you??

Modifying the time Dimension in OWB10G R2

Hello,
I've used the time-dimension wizard in OWB10G R2, but I am encountering some problems. Let me explain:
When you start with the wizard, it gives you the choice of a normal hierarchy based on year and/or quarter and/or month and/or day OR a week hierarchy, based on week and day. But I need a time dimension based on year, month, week and day. So I created a normal hierarchy time-dimension based on year, month and day and tried to alter it, by adding a week as an attribute (and level etc.).
So far no luck. I can't change the dimension, once it is created. Same for the other way around: create a weekbased hierarchy and ad month and year to it as attributes.
And now my question: Am I overlooking something? Or is it just a case of bad luck and do I have to build the time dimension myself by hand (not that much of a work, but still a pity of the wizard)? Or is there an other way around to fix this problem?
Regards,
Ingmar

Ingmar,
I just read your post and I am trying to accomplish the same thing with the time dimension - can you help me or direct me to another post that can?
After I create the time dimension with the wizard, I go back in via the Object Editor and I see the check box on the Levels tab and I have checked the Calendar_Week and all the attributes pop up, so far so good, then I navigate next to the Hieararchies tab and I don't see that the Level for Calendar_Week has been added?
How to I get a time dimension that has a single hierarchy that roles up as follows:
day ----> week ----> month -----> quarter ----->year
thx
monalisa

Multiple Date Fields (Fact Table) - Linking with Time Dimension

I have a fact table that has multiple date columns.
I can make a time dimension, but it has to be joined to a particular date column. This becomes difficult because of the limit in having multiple date fields reference one time dimension. I can see possibly
creating a date table which contains all dates, link to fact as well as time dimension table. I am trying to better visualize the table layout on this one. Or are there possibily better ways of looking at this senerio
Any idea's

Figured this one out; going to use one time dimension - what looking too much into the details in regard to this scenerio

Discoverer Condition on Time Dimension table

Hi,
We have a time dimension table TIME_DIM like this:
DATE_ID, YEAR, QUARTER, MONTH, WEEK, DAY
1, 2005, 1, 1, 1, '01-JAN-2005'
2, 2005, 1, 1, 2, '02-JAN-2005'
3, 2005, 1, 1, 2, '03-JAN-2005'
4, 2005, 1, 1, 2, '04-JAN-2005'
5, 2005, 1, 1, 2, '05-JAN-2005'
6, 2005, 1, 1, 2, '06-JAN-2005'
7, 2005, 1, 1, 2, '07-JAN-2005'
8, 2005, 1, 1, 2, '08-JAN-2005'
9, 2005, 1, 1, 3, '09-JAN-2005'
10, 2005, 1, 1, 3, '10-JAN-2005'
The week starts from a sunday and there are 52 weeks in a year. So, in 2005,
Week 52 will have all th days starting Dec-18 till Dec-31.
DATE_ID, YEAR, QUARTER, MONTH, WEEK, DAY
352, 2005, 4, 12, 52, '18-DEC-2005'
353, 2005, 4, 12, 52, '19-DEC-2005'
354, 2005, 4, 12, 52, '20-DEC-2005'
355, 2005, 4, 12, 52, '21-DEC-2005'
356, 2005, 4, 12, 52, '22-DEC-2005'
357, 2005, 4, 12, 52, '23-DEC-2005'
358, 2005, 4, 12, 52, '24-DEC-2005'
359, 2005, 4, 12, 52, '25-DEC-2005'
360, 2005, 4, 12, 52, '26-DEC-2005'
361, 2005, 4, 12, 52, '27-DEC-2005'
362, 2005, 4, 12, 52, '28-DEC-2005'
363, 2005, 4, 12, 52, '29-DEC-2005'
364, 2005, 4, 12, 52, '30-DEC-2005'
365, 2005, 4, 12, 52, '31-DEC-2005'
The condition we would like to have defined is as follows:
Last week(Or Previous Week)
If today is Jan-10, 2005. Current week number is 3 and hence Previous week is 2. So, i should get a condition as follows:
DATE_ID in (Select Date_ID from TIME_DIM where week=(select week - 1 from TIME_DIM where day = sysdate))
Discoverer does not allow subqueries in conditions. How to implement this?
Any help will be appreciated.
The problem is similar to accounting periods that do not correspond to the Gregorian calendar. For gregorian calendar, we can use the date functions to acheive the functionality.
Regards,
Ramesh

The best soultion would probably be to create a database function and register it through Discoverer Administration edition. You can then call the funciton in your condition, to replace the need for a sub-query

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

How to build the time dimension in Essbase with Fiscal Year (July thru Jun)

Hi,
In a recent project i have a situation where i need the time dimension to have some thing like this Fiscal Year (July - June) using BSO need to achieve DTS (YTD and QTD) functionality also.
And also my reports should also be able to drill through and needs comparison years(Prev Year Vs Current Year), months(Prev Year Vs Current Year) and Qtrs(Prev Year Vs Current Year).
How can i achieve this using BSO?.

Hi there,
This forum is for Oracle OLAP. The Essbase forum can be found here:- Essbase
Thanks,
Stuart Bunby
OLAP Blog: http://oracleOLAP.blogspot.com
OLAP Wiki: http://wiki.oracle.com/page/Oracle+OLAP+Option
OLAP on OTN: http://www.oracle.com/technology/products/bi/olap/index.html
DW on OTN : http://www.oracle.com/technology/products/bi/db/11g/index.html

How to build dynamic time series for the time dimension

I am planning to build dynamic time series using rule file instead of manually.Please let me know if there is any property need to assign to enable DTS property for TIME dimension.
Edited by: 844104 on Mar 14, 2011 3:37 AM

In the load rule in the dimension build settings you would need to go to the tab dimension definition, choose the time dimension and right click on it. Select Edit properties. If you have not done so, set the dimension to be the time dimension. Then go to the generations/levels tab and set the generation names you need. For example if you want YTD, you would set the generation name to Year, if you want QTD set it to Quarter. You would set the number to the generation number that coorisponds to the generation. The DBAG has the list of names for all of the DTS members.

How to find the common dimension tables used in Finance AR/PR and GL,

Hi All,
I need to find the common dimension table used in the Finance modules (AP,AR,PO,GL...), Since separate teams are working on populating each modules, and we need to find the dependency so that our loads shouldn’t impact others.
Thanks!
OBI

Hi Guys,
Thanks for all your answers.
Yes....You are all right. We can list out the used tables upto certain extent. Anyhow, I have done some R&D to derive the SQL's which is given below:
SELECT TABLE_NAME FROM USER_TABLES
MINUS
SELECT DISTINCT UPPER(REFERENCED_NAME)
FROM user_dependencies
where
referenced_type='TABLE' and UPPER(NAME) in
select distinct UPPER(object_name) from user_objects where UPPER(object_type) in
'MATERIALIZED VIEW',
'PACKAGE',
'PACKAGE BODY',
'PROCEDURE',
'TRIGGER',
'VIEW',
'FUNCTION'
UNION
SELECT UT.TABLE_NAME FROM
SELECT TABLE_NAME FROM USER_TABLES
MINUS
SELECT DISTINCT UPPER(REFERENCED_NAME)
FROM user_dependencies
where
referenced_type='TABLE' and UPPER(NAME) in
select distinct UPPER(object_name) from user_objects where UPPER(object_type) in
'MATERIALIZED VIEW',
'PACKAGE',
'PACKAGE BODY',
'PROCEDURE',
'TRIGGER',
'VIEW',
'FUNCTION'
AND REFERENCED_OWNER=(SELECT sys_context('USERENV', 'CURRENT_SCHEMA') FROM dual)
) UT,
( SELECT * FROM USER_SOURCE
WHERE NAME IN
( SELECT DISTINCT NAME FROM USER_SOURCE
WHERE TYPE NOT IN ('TYPE')
AND
UPPER(TEXT) LIKE '%EXECUTE IMMEDIATE%'
) US
WHERE
UPPER(US.TEXT) LIKE '%'||UPPER(UT.TABLE_NAME)||'%'
AND
(UPPER(US.TEXT) NOT LIKE '%--%')
The above SQL Query can list out unused tables by checking the Dynamic SQL Statement also upto some level only.
Once we extracted the list of unused tables, having a manual check would be also greater to verify as it is should not impact the business applications.
Regards,
Subramanian G

Where can I get the TIME dimension example files?

Where can I get / download the following files for creating this time dimension?
They are only in OWB R1.
[OWB Home]\owb\misc\time\readme.txt
[OWB Home]\owb\misc\time\owb_bp_time.mdl
and
[OWB Home]\owb\misc\time\owb_time_seq.sql
[OWB Home]\owb\misc\time\owb_time.sql
Thanks for help.

Hi,
Not sure if this answers the question, but in 10.2 you don't need these files any longer. Simply create the time dimension and it will load data for you (it acts as a data generator).
JP

Oracle 11gR2 use the time dimension wizard---the cube didn't show any information!

I created a Time Dimension with the Time dimension wizard , a category dimension, and a rel_expense cube in OWB 。what I do is following the oracle 11g r1's turtoial
The rel_expense cube has two forigen keys, one is refrence the category dimension's dimension_key(primary key in the category dimension), and the other one refrence the time dimension's start_day_date(bussniess key in the time dimension).
The result I get is the rel_expense_tab had datas, but the rel_expense cube had nothing.
.I delete the category dimension , it is the same result(cube rel_expense had nothing).
But if I only delete the time dimension, it is ok(both of them had datas)!!!
So I think is the time dimension's problem ,because the 11g r2's time dimension wizard didnt' generate the dimension_key for time. Is the forigen key(time dimension) i refrenced in the cube is error,so if it is, what should I do?
SEEK FOR YOU HELP!!!!!
ps:my mother language isn't English ,so it has many erros in the passage

can anybody help me? the measures in my cube were round to integer, i doubt it came from time dimension. did anyone encounts such a senario

Locking Periods using the Second Hierarchy in the Time Dimension

Hi,
They are not usiing work status for this...
I am at a client, and they used the second hierarchy in the time dimension to lock periods. If they left the second hierarchy blank, no data can be written to it. To open the open the period, they code the Second Heirarchy with CONS_OPEN. Just wondering if anyone has information on this?
It was working fine, then we needed to run a transport to move BPC to a new machine, and it stopped working. Not sure if anyone has done it this way before?
Thanks,
Chandra

Dear Kacper,
the way I understood, there are two separate questions in this post, namely:
I'm using a shared resource in multiple actors, and the code accessing the resource can take quite some time to execute. How can can I ensure this does not mess up the timing of one or all accessors?
I'm using a shared resource in multiple actors, and the code accessing the resource can generate errors if I try to access it from multiple places. How can I ensure synchronization between all accessors?
As for the first question, the optimal solution to separate the resource prone to timing issues in a different thread/actor. Put anything that is not strictly timed (file access, network comunication) in a separate loop. For each actor, you will get queue references to communicate with, so instead of logging the measurements in the actors where they are made, just queue them up for a different loop to process.
For the second part, the same logic still applies. Ideally, every singular resource should be handled by its own thread and nowhere else, so if anything else needs data from/to said resource, it can send a request to the dedicated thread or actor.
If, for some reason, this is not sufficient, you have to handle synchronization in some other way. There are a lot of techniques here, for example:
Create a named semaphore or lock as a part of the class. Have class functions use the semaphore before accessing the resource.
Use actor messages. Have a "resource in use" or "resource released" messages sent to all users whenever obtaining or releasing said resource.
Have a separate actor handle all resources, awarding them to threads needing them. This method also allows setting priorities between requests.
These are just a few examples, there are many other options.
Please let me know if this was helpful.
Kind regards:
Andrew Valko
National Instruments Hungary

Aggregation mode along one dimension (product) different than along the time dimension

Dear All,
In IBP S&OP, Is it possible that the aggregation mode along one dimension (product) could be different than along the time dimension?
For a demo, a customer has an input at the product family level (vehicle production) which we just “copy” for disaggregation purposes, to the product level (parts), see attached. So for aggregation we used average.
However, time-wise, we need to sum it up.
Thanks for your insight and help.
Kind Regards,
Omar

Hi Omar,
Yes it is possible.
1. Create a new planning level (say PERPRODCUST1) which will be a copy of PERPRODCUST (you base planning level).
2. In the PER section of PERPRODCUST1, do NOT mark any period attribute as root. In other words, the roots for this PL will only be PRDID and CUSTID.
3. Now your KF calculations will be:
VEHICLEPRODUCTION@PERPRODCUST1 = SUM(VEHICLEPRODUCTION@PERPRODCUST)
VEHICLEPRODUCTION@REQUEST = AVG(VEHICLEPRODUCTION@PERPRODCUST1)
Since your KF is editable, it is worth mentioning that, following the above steps has trade-offs. Since your KF is editable, you will have issues with disaggregation when you enter the values at an aggregated level of both time and other attributes. My recommendation (for your configuration) is that this will work fine as long you enter the values at the root level of you time attribute.
Hope this helps,
Chendur

Is it possible to add an all time member to the time dimension

We are on BPC 7. Our time dimension has the normal Year, Quarter, Month rollup.
Is it possible to add an "All_time" member to the time dimension that would have all years rolling up to it or are our only choices Year, Halfyear, Quarter, Month, Week, or Day?

TOTAL is not a valid selection for LEVEL. Did you create this "TOTAL" manually some how? I have seen "TOTAL" as a period but never a level. Do you have a dimension file that you can get to work with this example in APPSHELL that you could share?
According to the BPC Admin documentation it only comes with YEAR, HALFYEAR, QUARTER, MONTH, WEEK, DAY as valid options. How do you get the TOTAL member added as a valid option for the LEVEL property:
BPC Documentation Reference below:
LEVEL
Time can be a year, quarter, month, week or day. As described above, the PARENTH1 property is used to define the aggregation of the time periods.
The LEVEL property is also very important in defining your time periods. You must have the correct Level (Year, quarter, month, etc.) for each member. You must follow the chronological format throughout the Time dimension. The correct format is:
·        YEAR
·        HALFYEAR
·        QUARTER
·        MONTH
·        WEEK
·        DAY

10g - Most detailed table in the time dimension table source is not unique

Similar Messages

Maybe you are looking for