Time Dimension Working Days

Hi i have a calendar table
Has Year , Month, Week, Date and a flag for a working day or not..
Is there anyway i can use this working day flag in my Time Dimension Hierarchy so that under Date i can have another drill Working Days ...
(Non working day is where flag = 'Y')
Year - Month - Week - Day - Working Day
or Even
Year - Month - Week - Working Day
Cheers
Bibi

Year - Month - Week - Working Day
You could acheive this by putting a filter on your logical table source to exclude non-working days. Or maybe just remove the non working days from the source table
The trouble with trying to put an extra level in beneath Day is that your primary key, I.e. your lowest level for the date dimension in this case is Day. Working Days won't roll up into Days as they are at the same level.

Similar Messages

How is lead time in working days calculated in 2LIS_05_QVUDN

I was wondering if someone knows how lead time is being caclulated for 2LIS_05_QVUDN. I've found the tables associated and the function module but I can't find the actual calculation
Thanks

Hello
The lead time in working days works like this
If you have 1 inspection lot for a material   -the time from Lot creation to Usage decision given is the lead time.
                                                          Lot created               Usage Decision made       Lead Time
for eg Material X , inspection lot no   14/05/2008 10: 00          14/05/2008 14: 00            4 Hours
it converts the hours in to days . =4/24= 0.16 days
For total lead time individual lot's lead time sum is calculated
Hope this clarifies your doubt
Regards
gajesh

Calculating the planned delivery time in calendar days or working days

Hi,
It seems that there is a way to calculate the planned delivery time in calendar days instead of working days.
When I use the "Planned delivery time calculation" (WPDTC), in Evaluation Options, I got the message :
"Note that follow-on applications are currently interpreting the planned delivery time as calendar days.
If they should be interpreting the planned delivery time as working days, you need to modify these applications. If the planned delivery time should be calculated in working days, there needs to be a factory calendar in Customizing with the calendar ID Country of vendor."
When MRP create a PR -with MDBT, MD03 or MD01- I want my Planned delivery time to be in working days.
I can't manage to make that "If the planned delivery time should be calculated in working days, there needs to be a factory calendar in Customizing with the calendar ID Country of vendor."
I would appreciate your help.
Thanks
PYR

Hi,
I understand that it makes sense that vendors calendar has to be different (compared to my plant).
But, I still don't understand why in the SAP help, they say "If the planned delivery time should be calculated in working days, there needs to be a factory calendar in Customizing with the calendar ID Country of vendor."
It seems that planned delivery time may follow a calendar.
Thanks,
PYR

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.

Working days in Purchase info Record

Hi,
I have some Subcontracting inforecords in which I would like to specify the Planned delivery time in working days instead of calender days.
Does anyone knows how to do that?
Thanks,
Anders

Hi,
the short answer is that you cannot have work days as the planned delivery period for the vendor. This must be calendar days.
Nor can you attach a calendar to a vendor to indicate their opening and closing times.
The Planning calendar on the MRP2 screen is designed to be used for "Time Phased" planning and you have already indicated that this is not appropriate because there is no set order day and delivery day.
The solution is to use the LONGEST lead time for the vendor (i.e. as if it was over the weekend). This should work fine for you, all that happens is that if it does not cross a weekend the PO will be raised a couple of days earlier than it needs to be. The delivery date should still be the date that you need it, if it is extending the delivery date in your case then you need to set the config to "allow start dates in the past" so that all requirements are raised with the actual date that you need the item even if the lead times are not long enough. This will then work as you require it.
Steve B

How to create a working day/holiday attribute in Time Dimension with OWB ?

Hello everybody,
I am trying with no success to create a Time Dimension (with the wizard it would be easier...) with a working day or holiday attribute (0 or 1) to be able to calculate measures only on working time !!! I am totally sure it's possible, obviously, but I found nothing on forums... Could you help me ??
I use OWB 11g, I need all fiscal year/quarter/month/week and all calendar year/quarter/month/week attributes so without any wizard it would be quite impossible... thank you for your help !
NB: of course I know how to define if a day is a working one or not, but I currently can't add any columns in Time dim created with wizard...
Francois
Edited by: [email protected] on Jun 15, 2009 8:24 AM

Hi,
First of all, thanks everyone for your help.
I did several tests this morning.
First of all, i've tried with time_from = 000000 and time_to = 235959 (23:59:59 CET) and the activity has been created with Time From = 04:00:00 and Time To = 03:59:59
Strange no ??
I've also tried with 230000 for time from and time to but the activity has been created with Time From = 03:00:00 and Time to = 03:00:00
I cannot understand the logic behind....
Thanks,
Johnny Baillargeaux

OracleBI Spreadsheet Add-in Not Working With ROLAP TIME Dimension

Hello,
I've been trying to figure this bizarre behavior for a while now.
I have created a TIME dimension (based on a relational table) using OEM and defined the metadata etc. My hierarchy has 4 levels: day->month->quarter->year. I have end_date and time_span attributes defined for each level. I have defined a simple cube dimensioned by TIME and having only 1 numeric measure.
When I open BI Spreadsheet Add-in, I can see my cube measure and the dimension in the list of available entities. I add them to the list of selected entities and hit 'next'. On the next screen I arrange them to my liking and hit 'next' again. This is where the problem occurs. Or rather where nothing occurs. The add-in just gets stuck at this point and no matter what I do or click, it won't advance to the next step.
If I change the dimension type from time to normal, then everything works as expected (although, I cannot do time-series analysis).
If I create and enable an analytic workspace and use it in the add-in, then everything works as expected as well.
Any ideas what's wrong here? I kind of suspect the end_date and time_span attributes are involved somehow...
Thanks!
Dobo

The expected format for a relational time table would be something like the following:
CREATE TABLE "BIBDEMO"."BIBDEMO_TIME"
("TIME_STD_MONTH" VARCHAR2(30),
"TIME_STD_MONTH_LLABEL" VARCHAR2(60),
"TIME_STD_MONTH_SLABEL" VARCHAR2(30),
"TIME_STD_QUARTER" VARCHAR2(30),
"TIME_STD_QUARTER_LLABEL" VARCHAR2(60),
"TIME_STD_QUARTER_SLABEL" VARCHAR2(30),
"TIME_STD_YEAR" VARCHAR2(30),
"TIME_STD_YEAR_LLABEL" VARCHAR2(60),
"TIME_STD_YEAR_SLABEL" VARCHAR2(30),
"TIME_YTD_YEAR" VARCHAR2(30),
"TIME_YTD_YEAR_LLABEL" VARCHAR2(60),
"TIME_YTD_YEAR_SLABEL" VARCHAR2(30),
CONSTRAINT BIBDEMO_TIME_PK PRIMARY KEY("TIME_STD_MONTH")
ALTER TABLE "BIBDEMO"."BIBDEMO_TIME"
ADD ("TIME_STD_MONTH_END_DATE" DATE,
"TIME_STD_QUARTER_END_DATE" DATE,
"TIME_STD_YEAR_END_DATE" DATE,
"TIME_YTD_YEAR_END_DATE" DATE) ;
ALTER TABLE "BIBDEMO"."BIBDEMO_TIME"
ADD ("TIME_STD_MONTH_TIMESPAN" NUMBER,
"TIME_STD_QUARTER_TIMESPAN" NUMBER,
"TIME_STD_YEAR_TIMESPAN" NUMBER,
"TIME_YTD_YEAR_TIMESPAN" NUMBER) ;
and the metadata registration script should look something like this:
-- This script modifies the bibdemo_time lookup table and bibdemo TIME dimension. It adds a period end date attribute.
ALTER TABLE "BIBDEMO"."BIBDEMO_TIME"
ADD ("TIME_STD_MONTH_END_DATE" DATE,
"TIME_STD_QUARTER_END_DATE" DATE,
"TIME_STD_YEAR_END_DATE" DATE,
"TIME_YTD_YEAR_END_DATE" DATE) ;
ALTER TABLE "BIBDEMO"."BIBDEMO_TIME"
ADD ("TIME_STD_MONTH_TIMESPAN" NUMBER,
"TIME_STD_QUARTER_TIMESPAN" NUMBER,
"TIME_STD_YEAR_TIMESPAN" NUMBER,
"TIME_YTD_YEAR_TIMESPAN" NUMBER) ;
begin
dbms_output.put_line('Drop level attributes of TIME prior to recreation.');
cwm_olap_dim_attribute.remove_level_attribute('BIBDEMO', 'TIME', 'Long Description', 'L1', 'TIME_STD_YEAR_LLABEL');
cwm_olap_dim_attribute.remove_level_attribute('BIBDEMO', 'TIME', 'Short Description', 'L1', 'TIME_STD_YEAR_SLABEL');
cwm_olap_dim_attribute.remove_level_attribute('BIBDEMO', 'TIME', 'Long Description', 'L2', 'TIME_STD_QUARTER_LLABEL');
cwm_olap_dim_attribute.remove_level_attribute('BIBDEMO', 'TIME', 'Short Description', 'L2', 'TIME_STD_QUARTER_SLABEL');
cwm_olap_dim_attribute.remove_level_attribute('BIBDEMO', 'TIME', 'Long Description', 'L3', 'TIME_STD_MONTH_LLABEL');
cwm_olap_dim_attribute.remove_level_attribute('BIBDEMO', 'TIME', 'Short Description', 'L3', 'TIME_STD_MONTH_SLABEL');
cwm_olap_dim_attribute.remove_level_attribute('BIBDEMO', 'TIME', 'Long Description', 'L4', 'TIME_YTD_YEAR_LLABEL');
cwm_olap_dim_attribute.remove_level_attribute('BIBDEMO', 'TIME', 'Short Description', 'L4', 'TIME_YTD_YEAR_SLABEL');
commit;
exception
when others then
dbms_output.put_line('ERROR: unexpected exception during seeding');
cwm_utility.dump_error;
rollback;
raise;
end;
ALTER DIMENSION BIBDEMO.TIME
DROP ATTRIBUTE L1
DROP ATTRIBUTE L2
DROP ATTRIBUTE L3
DROP ATTRIBUTE L4;
ALTER DIMENSION BIBDEMO.TIME
ADD ATTRIBUTE L1 DETERMINES
(BIBDEMO_TIME.TIME_STD_YEAR_LLABEL,
BIBDEMO_TIME.TIME_STD_YEAR_SLABEL,
BIBDEMO_TIME.TIME_STD_YEAR_END_DATE,
BIBDEMO_TIME.TIME_STD_YEAR_TIMESPAN)
ADD ATTRIBUTE L2 DETERMINES
(BIBDEMO_TIME.TIME_STD_QUARTER_LLABEL,
BIBDEMO_TIME.TIME_STD_QUARTER_SLABEL,
BIBDEMO_TIME.TIME_STD_QUARTER_END_DATE,
BIBDEMO_TIME.TIME_STD_QUARTER_TIMESPAN)
ADD ATTRIBUTE L3 DETERMINES
(BIBDEMO_TIME.TIME_STD_MONTH_LLABEL,
BIBDEMO_TIME.TIME_STD_MONTH_SLABEL,
BIBDEMO_TIME.TIME_STD_MONTH_END_DATE,
BIBDEMO_TIME.TIME_STD_MONTH_TIMESPAN)
ADD ATTRIBUTE L4 DETERMINES
(BIBDEMO_TIME.TIME_YTD_YEAR_LLABEL,
BIBDEMO_TIME.TIME_YTD_YEAR_SLABEL,
BIBDEMO_TIME.TIME_YTD_YEAR_END_DATE,
BIBDEMO_TIME.TIME_YTD_YEAR_TIMESPAN);
declare
timespan_desc_id number;
enddate_desc_id number;
TIME_DIM_ATTRIB_TYPE constant varchar2(30) := 'DIMENSION ATTRIBUTE';
TIME_ATTRIBUTE_TYPE constant varchar2(30) := 'LEVEL ATTRIBUTE';
begin
dbms_output.put_line('Create end_date and timespan attributes of TIME for BIBDEMO schema');
begin
cwm_olap_level_attribute.set_name('BIBDEMO', 'TIME', 'L1', 'TIME_STD_YEAR_END_DATE', 'TIME_STD_YEAR_END_DATE');
cwm_olap_level_attribute.set_name('BIBDEMO', 'TIME', 'L2', 'TIME_STD_QUARTER_END_DATE', 'TIME_STD_QUARTER_END_DATE');
cwm_olap_level_attribute.set_name('BIBDEMO', 'TIME', 'L3', 'TIME_STD_MONTH_END_DATE', 'TIME_STD_MONTH_END_DATE');
cwm_olap_level_attribute.set_name('BIBDEMO', 'TIME', 'L4', 'TIME_YTD_YEAR_END_DATE', 'TIME_YTD_YEAR_END_DATE');
cwm_olap_level_attribute.set_name('BIBDEMO', 'TIME', 'L1', 'TIME_STD_YEAR_TIMESPAN', 'TIME_STD_YEAR_TIMESPAN');
cwm_olap_level_attribute.set_name('BIBDEMO', 'TIME', 'L2', 'TIME_STD_QUARTER_TIMESPAN', 'TIME_STD_QUARTER_TIMESPAN');
cwm_olap_level_attribute.set_name('BIBDEMO', 'TIME', 'L3', 'TIME_STD_MONTH_TIMESPAN', 'TIME_STD_MONTH_TIMESPAN');
cwm_olap_level_attribute.set_name('BIBDEMO', 'TIME', 'L4', 'TIME_YTD_YEAR_TIMESPAN', 'TIME_YTD_YEAR_TIMESPAN');
cwm_olap_dim_attribute.create_dimension_attribute('BIBDEMO', 'TIME', 'End_Date', 'End_Date', 'End Date of time period');
cwm_olap_dim_attribute.create_dimension_attribute('BIBDEMO', 'TIME', 'Time_Span', 'Time_Span', 'Number of days in time period');
cwm_olap_dim_attribute.add_level_attribute('BIBDEMO', 'TIME', 'Long Description', 'L1', 'TIME_STD_YEAR_LLABEL');
cwm_olap_dim_attribute.add_level_attribute('BIBDEMO', 'TIME', 'Short Description', 'L1', 'TIME_STD_YEAR_SLABEL');
cwm_olap_dim_attribute.add_level_attribute('BIBDEMO', 'TIME', 'End_Date', 'L1', 'TIME_STD_YEAR_END_DATE');
cwm_olap_dim_attribute.add_level_attribute('BIBDEMO', 'TIME', 'Time_Span', 'L1', 'TIME_STD_YEAR_TIMESPAN');
cwm_olap_dim_attribute.add_level_attribute('BIBDEMO', 'TIME', 'Long Description', 'L2', 'TIME_STD_QUARTER_LLABEL');
cwm_olap_dim_attribute.add_level_attribute('BIBDEMO', 'TIME', 'Short Description', 'L2', 'TIME_STD_QUARTER_SLABEL');
cwm_olap_dim_attribute.add_level_attribute('BIBDEMO', 'TIME', 'End_Date', 'L2', 'TIME_STD_QUARTER_END_DATE');
cwm_olap_dim_attribute.add_level_attribute('BIBDEMO', 'TIME', 'Time_Span', 'L2', 'TIME_STD_QUARTER_TIMESPAN');
cwm_olap_dim_attribute.add_level_attribute('BIBDEMO', 'TIME', 'Long Description', 'L3', 'TIME_STD_MONTH_LLABEL');
cwm_olap_dim_attribute.add_level_attribute('BIBDEMO', 'TIME', 'Short Description', 'L3', 'TIME_STD_MONTH_SLABEL');
cwm_olap_dim_attribute.add_level_attribute('BIBDEMO', 'TIME', 'End_Date', 'L3', 'TIME_STD_MONTH_END_DATE');
cwm_olap_dim_attribute.add_level_attribute('BIBDEMO', 'TIME', 'Time_Span', 'L3', 'TIME_STD_MONTH_TIMESPAN');
cwm_olap_dim_attribute.add_level_attribute('BIBDEMO', 'TIME', 'Long Description', 'L4', 'TIME_YTD_YEAR_LLABEL');
cwm_olap_dim_attribute.add_level_attribute('BIBDEMO', 'TIME', 'Short Description', 'L4', 'TIME_YTD_YEAR_SLABEL');
cwm_olap_dim_attribute.add_level_attribute('BIBDEMO', 'TIME', 'End_Date', 'L4', 'TIME_YTD_YEAR_END_DATE');
cwm_olap_dim_attribute.add_level_attribute('BIBDEMO', 'TIME', 'Time_Span', 'L4', 'TIME_YTD_YEAR_TIMESPAN');
begin
SELECT descriptor_id INTO enddate_desc_id
FROM all_olap_descriptors
WHERE descriptor_value = 'End Date'
AND descriptor_type = 'Time Dimension Attribute Type';
begin
dbms_output.put_line('Classify entity descriptor use end date for TIME');
begin
cwm_classify.add_entity_descriptor_use(enddate_desc_id, TIME_DIM_ATTRIB_TYPE, 'BIBDEMO', 'TIME', 'End_Date');
exception
when cwm_exceptions.element_already_exists
then null;
end;
begin
cwm_classify.add_entity_descriptor_use(enddate_desc_id, TIME_ATTRIBUTE_TYPE, 'BIBDEMO', 'TIME', 'L3', 'TIME_STD_MONTH_END_DATE');
exception
when cwm_exceptions.element_already_exists
then null;
end;
begin
cwm_classify.add_entity_descriptor_use(enddate_desc_id, TIME_ATTRIBUTE_TYPE, 'BIBDEMO', 'TIME', 'L2', 'TIME_STD_QUARTER_END_DATE');
exception
when cwm_exceptions.element_already_exists
then null;
end;
begin
cwm_classify.add_entity_descriptor_use(enddate_desc_id, TIME_ATTRIBUTE_TYPE, 'BIBDEMO', 'TIME', 'L1', 'TIME_STD_YEAR_END_DATE');
exception
when cwm_exceptions.element_already_exists
then null;
end;
begin
cwm_classify.add_entity_descriptor_use(enddate_desc_id, TIME_ATTRIBUTE_TYPE, 'BIBDEMO', 'TIME', 'L4', 'TIME_YTD_YEAR_END_DATE');
exception
when cwm_exceptions.element_already_exists
then null;
end;
end;
end;
begin
SELECT descriptor_id INTO timespan_desc_id
FROM all_olap_descriptors
WHERE descriptor_value = 'Time Span'
AND descriptor_type = 'Time Dimension Attribute Type';
begin
dbms_output.put_line('Classify entity descriptor use time span for TIME');
begin
cwm_classify.add_entity_descriptor_use(timespan_desc_id, TIME_DIM_ATTRIB_TYPE, 'BIBDEMO', 'TIME', 'Time_Span');
exception
when cwm_exceptions.element_already_exists
then null;
end;
begin
cwm_classify.add_entity_descriptor_use(timespan_desc_id, TIME_ATTRIBUTE_TYPE, 'BIBDEMO', 'TIME', 'L3', 'TIME_STD_MONTH_TIMESPAN');
exception
when cwm_exceptions.element_already_exists
then null;
end;
begin
cwm_classify.add_entity_descriptor_use(timespan_desc_id, TIME_ATTRIBUTE_TYPE, 'BIBDEMO', 'TIME', 'L2', 'TIME_STD_QUARTER_TIMESPAN');
exception
when cwm_exceptions.element_already_exists
then null;
end;
begin
cwm_classify.add_entity_descriptor_use(timespan_desc_id, TIME_ATTRIBUTE_TYPE, 'BIBDEMO', 'TIME', 'L1', 'TIME_STD_YEAR_TIMESPAN');
exception
when cwm_exceptions.element_already_exists
then null;
end;
begin
cwm_classify.add_entity_descriptor_use(timespan_desc_id, TIME_ATTRIBUTE_TYPE, 'BIBDEMO', 'TIME', 'L4', 'TIME_YTD_YEAR_TIMESPAN');
exception
when cwm_exceptions.element_already_exists
then null;
end;
end;
end;
end;
commit;
exception
when others then
dbms_output.put_line('ERROR: unexpected exception during seeding');
cwm_utility.dump_error;
rollback;
raise;
end;
--UPDATE "BIBDEMO"."BIBDEMO_TIME" SET TIME_STD_MONTH_END_DATE = LAST_DAY(TO_DATE( time_std_month , 'monyy'));
--UPDATE "BIBDEMO"."BIBDEMO_TIME" t SET TIME_STD_QUARTER_END_DATE = (select max(t1.time_std_month_end_date) from bibdemo_time t1 where t1.time_std_quarter = t.time_std_quarter group by t1.time_std_quarter) ;
--UPDATE "BIBDEMO"."BIBDEMO_TIME" t SET TIME_STD_YEAR_END_DATE = (select max(t1.time_std_month_end_date) from bibdemo_time t1 where t1.time_std_year = t.time_std_year group by t1.time_std_year) ;
update bibdemo_time set time_std_month_end_date = to_date('31-JAN-2000', 'dd-mon-yyyy') where time_std_month = 'JAN00';
update bibdemo_time set time_std_month_end_date = to_date('29-FEB-2000', 'dd-mon-yyyy') where time_std_month = 'FEB00';
update bibdemo_time set time_std_month_end_date = to_date('31-MAR-2000', 'dd-mon-yyyy') where time_std_month = 'MAR00';
update bibdemo_time set time_std_month_end_date = to_date('30-APR-2000', 'dd-mon-yyyy') where time_std_month = 'APR00';
update bibdemo_time set time_std_month_end_date = to_date('31-MAY-2000', 'dd-mon-yyyy') where time_std_month = 'MAY00';
update bibdemo_time set time_std_month_end_date = to_date('30-JUN-2000', 'dd-mon-yyyy') where time_std_month = 'JUN00';
update bibdemo_time set time_std_month_end_date = to_date('31-JUL-2000', 'dd-mon-yyyy') where time_std_month = 'JUL00';
update bibdemo_time set time_std_month_end_date = to_date('31-AUG-2000', 'dd-mon-yyyy') where time_std_month = 'AUG00';
update bibdemo_time set time_std_month_end_date = to_date('30-SEP-2000', 'dd-mon-yyyy') where time_std_month = 'SEP00';
update bibdemo_time set time_std_month_end_date = to_date('31-OCT-2000', 'dd-mon-yyyy') where time_std_month = 'OCT00';
update bibdemo_time set time_std_month_end_date = to_date('30-NOV-2000', 'dd-mon-yyyy') where time_std_month = 'NOV00';
update bibdemo_time set time_std_month_end_date = to_date('31-DEC-2000', 'dd-mon-yyyy') where time_std_month = 'DEC00';
update bibdemo_time set time_std_month_end_date = to_date('31-JAN-2001', 'dd-mon-yyyy') where time_std_month = 'JAN01';
update bibdemo_time set time_std_month_end_date = to_date('28-FEB-2001', 'dd-mon-yyyy') where time_std_month = 'FEB01';
update bibdemo_time set time_std_month_end_date = to_date('31-MAR-2001', 'dd-mon-yyyy') where time_std_month = 'MAR01';
update bibdemo_time set time_std_month_end_date = to_date('30-APR-2001', 'dd-mon-yyyy') where time_std_month = 'APR01';
update bibdemo_time set time_std_month_end_date = to_date('31-MAY-2001', 'dd-mon-yyyy') where time_std_month = 'MAY01';
update bibdemo_time set time_std_quarter_end_date = to_date('30-JUN-2000', 'dd-mon-yyyy') where time_std_quarter = 'Q2.00';
update bibdemo_time set time_std_quarter_end_date = to_date('30-SEP-2000', 'dd-mon-yyyy') where time_std_quarter = 'Q3.00';
update bibdemo_time set time_std_quarter_end_date = to_date('31-DEC-2000', 'dd-mon-yyyy') where time_std_quarter = 'Q4.00';
update bibdemo_time set time_std_quarter_end_date = to_date('31-MAR-2000', 'dd-mon-yyyy') where time_std_quarter = 'Q1.00';
update bibdemo_time set time_std_quarter_end_date = to_date('31-MAR-2001', 'dd-mon-yyyy') where time_std_quarter = 'Q1.01';
update bibdemo_time set time_std_quarter_end_date = to_date('31-MAY-2001', 'dd-mon-yyyy') where time_std_quarter = 'Q2.01';
update bibdemo_time set time_std_year_end_date = to_date('31-DEC-2000', 'dd-mon-yyyy') where time_std_year = '2000';
update bibdemo_time set time_std_year_end_date = to_date('31-MAY-2001', 'dd-mon-yyyy') where time_std_year = '2001';
update bibdemo_time set time_ytd_year_end_date = to_date('31-DEC-2000', 'dd-mon-yyyy') where time_ytd_year = '2000';
update bibdemo_time set time_ytd_year_end_date = to_date('31-MAY-2001', 'dd-mon-yyyy') where time_ytd_year = '2001';
update "BIBDEMO"."BIBDEMO_TIME" set "TIME_STD_MONTH_TIMESPAN" = 31 where "TIME_STD_MONTH" = 'JAN00';
update "BIBDEMO"."BIBDEMO_TIME" set "TIME_STD_MONTH_TIMESPAN" = 29 where "TIME_STD_MONTH" = 'FEB00';
update "BIBDEMO"."BIBDEMO_TIME" set "TIME_STD_MONTH_TIMESPAN" = 31 where "TIME_STD_MONTH" = 'MAR00';
update "BIBDEMO"."BIBDEMO_TIME" set "TIME_STD_MONTH_TIMESPAN" = 30 where "TIME_STD_MONTH" = 'APR00';
update "BIBDEMO"."BIBDEMO_TIME" set "TIME_STD_MONTH_TIMESPAN" = 31 where "TIME_STD_MONTH" = 'MAY00';
update "BIBDEMO"."BIBDEMO_TIME" set "TIME_STD_MONTH_TIMESPAN" = 30 where "TIME_STD_MONTH" = 'JUN00';
update "BIBDEMO"."BIBDEMO_TIME" set "TIME_STD_MONTH_TIMESPAN" = 31 where "TIME_STD_MONTH" = 'JUL00';
update "BIBDEMO"."BIBDEMO_TIME" set "TIME_STD_MONTH_TIMESPAN" = 31 where "TIME_STD_MONTH" = 'AUG00';
update "BIBDEMO"."BIBDEMO_TIME" set "TIME_STD_MONTH_TIMESPAN" = 30 where "TIME_STD_MONTH" = 'SEP00';
update "BIBDEMO"."BIBDEMO_TIME" set "TIME_STD_MONTH_TIMESPAN" = 31 where "TIME_STD_MONTH" = 'OCT00';
update "BIBDEMO"."BIBDEMO_TIME" set "TIME_STD_MONTH_TIMESPAN" = 30 where "TIME_STD_MONTH" = 'NOV00';
update "BIBDEMO"."BIBDEMO_TIME" set "TIME_STD_MONTH_TIMESPAN" = 31 where "TIME_STD_MONTH" = 'DEC00';
update "BIBDEMO"."BIBDEMO_TIME" set "TIME_STD_MONTH_TIMESPAN" = 31 where "TIME_STD_MONTH" = 'JAN01';
update "BIBDEMO"."BIBDEMO_TIME" set "TIME_STD_MONTH_TIMESPAN" = 28 where "TIME_STD_MONTH" = 'FEB01';
update "BIBDEMO"."BIBDEMO_TIME" set "TIME_STD_MONTH_TIMESPAN" = 31 where "TIME_STD_MONTH" = 'MAR01';
update "BIBDEMO"."BIBDEMO_TIME" set "TIME_STD_MONTH_TIMESPAN" = 30 where "TIME_STD_MONTH" = 'APR01';
update "BIBDEMO"."BIBDEMO_TIME" set "TIME_STD_MONTH_TIMESPAN" = 31 where "TIME_STD_MONTH" = 'MAY01';
update "BIBDEMO"."BIBDEMO_TIME" t
set "TIME_STD_QUARTER_TIMESPAN" = (
select sum(t1.time_std_month_timespan)
from bibdemo_time t1
where t."TIME_STD_QUARTER" = t1.time_std_quarter
group by t1.time_std_quarter
update "BIBDEMO"."BIBDEMO_TIME" t
set "TIME_STD_YEAR_TIMESPAN" = (
select sum(t1.time_std_month_timespan)
from bibdemo_time t1
where t."TIME_STD_YEAR" = t1.time_std_year
group by t1.time_std_year
update "BIBDEMO"."BIBDEMO_TIME" t
set "TIME_YTD_YEAR_TIMESPAN" = (
select sum(t1.time_std_month_timespan)
from bibdemo_time t1
where t."TIME_YTD_YEAR" = t1.time_ytd_year
group by t1.time_ytd_year
commit;
quit;
Hope this helps
Business Intelligence Beans Product Management Team
Oracle Corporation

How do I disable "this connection is untrusted" I visit the same web site mutiple times in a day visit I get this same error, these are trusted sites within my work

How do I disable "this connection is untrusted" I visit the same web site mutiple times in a day and every visit I get this same dam error, these are trusted sites within my work environment. This is getting really old, and I am thinking that I should just uninstall, which is a pity becuase I do like firefox

Okay, before you copy 'n paste canned responses, you should read the post first.
'''The date & time on my computer is correct''' I've already checked this.
'''I don't give a damn why the site is untrusted''', I probably know why in fact (behind corporate proxy server).
As for exporting a known good certificate from another browser, sure good idea, but it doesn't seem to work. I tried exporting from IE, Firefox did the import without complaint, but it still complains. At any rate, I don't care about that. '''I just want to permanent disable it for ALL SITES for ALL TIME'''. Is that too much to ask for?
Judging by the number of posts on this topic, apparently I am not the only one complaining about this.

How/ where to change a weekly off to working day, working day to weekly off by maintaining IT0007 is 7-time evaluation without payroll integration

Dear Experts
We are doing Negative Time Management where we record only deviations
But customer has third party time machine which required to be integrated with SAP system
As I know, from the time recording terminal, i should map SAP number to all employees and then get a text mail the details with employee attendance for the respective dates and times. Then, have to create a ABAP report which will read the text file and update clock in/out with date into SAP system. After this we can check employee attendance infotype 2011.
But, Before going for above, time administrator wants to set IT0007 as 7- time evaluation without payroll integration, then maintain data in IT0050 & IT2011
Then run Time Evaluation then the out put will be according to the data maintained in IT 2011. Now the requirement is, time administrator wants to change eg. the day is suppose to be working day for any employee but based on adjustments that day became weekly off, another employee suppose to work but again due to some adjustments that day became weekly off, so how this time administrator can change this and where. This is like, time administrator need to see the total work schedule for an employee and needs to change whichever data and whenever or after time evaluation, he could see the total work schedule as desired.
And also, time administrator wants to change schedule manually for any of the employee during that particular period and view the same.
Please note that, ESS/MSS haven't implemented yet.
Appreciated all your prompt responses to this.
Thanks
SS

No
I have created a workschedule on wednesday In a year there can be weekly off 5 or 6 times on Saturday or Sunday So in that case there is no need to create three workschedules we can create one workschedule and change the days Again we need to regenerate the workschedules inorder to take 'off's" in to account. that is what iam thinkinng at the moment. Yes there is no need to do anything in IT 007 If there is any change in Shift in that Case User has to change workschedule in IT 007.
If there is weekly off he can select the dates on which day it is falling and generate the workschedule.
for changing shifts he should change work schedule in IT 007
Is this is right approach please throw some light on this
My client requirement was Sometimes there can be weekly off in the company It can be either wednesday off or saturday off or
unday off or it can be any day.
Edited by: My SAP Cronies on Feb 2, 2012 5:17 AM
Edited by: My SAP Cronies on Feb 2, 2012 5:22 AM

Since installation of Mavericks, Time Capsule works very slowly, and the next backup of 236 GM will take nearly 30 days. What can I do to get backup more rapidly ?

Since the installation of Mavericks, Time capsule works very slowly and will need 30 days or more to produce a complete backup of about 200 GB. What can I do to get a complete backup more rapidly ?

What setup is the TC now.. ? what model and what firmware? Maverick seems to need 7.6.4 on the older TC.. and latest firmware on the AC version.
Is it in router or bridge mode? Do not use wireless only.. join a wireless network.
Is the computer connected by wireless or ethernet? I strongly recommend a test by ethernet.. with wireless in the computer turned off. If it is still very slow something is majorly wrong.. but I need the info I asked for to troubleshoot further.

I had itunes working properly for a long time till one day, it was configuring to open the program then i get a message out of nowhere that says could not acess network location %APPDATA%\ i cant even uninstall without this, whats the big deal?!

I had itunes working properly for a long time till one day, it was configuring to open the program then i get a message out of nowhere that says could not acess network location %APPDATA%\ i cant even uninstall without this, whats the big deal?!

With that particular variety of 1606 (it's a 1606 error message even though the 1606 error message number isn't returned by the iTunes installer), the following Microsoft document is worth a try:
You receive an "Error 1606" error message when you try to install or remove a Microsoft program

Intra Day Time Dimension

Hi has anyone had any success implementing a Time Dimension which goes down to HOURS granularity?
So I want Year-Month-Day-Hour.
The only way I think I can achieve this is by creating two physical tables, one containing the DATES (DD-MON-YYYY) and the other containing the TIMES (ie. 24 records 1 for each hour).
I can't find a suitable method for getting them into a single OBIEE hierarchy as my requirement also has to OUTER JOIN so that when there is no FACT DETAIL record I still get the Dates/Times displayed.
If I create two seperate Business Model Dimension Tables (and Dimensions) and have a preferred drill path I am able to see the Outer Join Dates, but as soon as I drill into the detail (Hour) I only see a single Hour record (not 24).
Thanks in advance.

Ok cardinal rule broken, replying to my own thread.
I do have a way of doing this, however I haven't volume tested it!
1) Create 2 Phyiscal Tables DATES and TIMES.
2) Create a View on Top called DATE_TIMES_VW which SELECTS date_col, time_col FROM DATES,TIMES and creates a Cartesian Product.
3) Create Physical Model and joins from DATE_TIMES_VW to FACT
4) Create Business Model and complex join (left outer) from Dimension Tab to Fact Tab.
5) Create Dimension from for full hierarchy.
Step 2) is effectively the same as creating one big Timestamp table on the fly, without having to store a large volume of data.
I'm hoping there is a better OBIEE tool method for achieving the same, which would be more scaleable than this one.
Anybody got any suggestions?

My iPhone 4 home button doesn't always work. sometimes its just not responsive. other times, it works great. what's the problem, and how do I get it fixed? my iphone is 2 days old

my iPhone 4 home button doesn't always work. sometimes its just not responsive. other times, it works great. what's the problem, and how do I get it fixed? my iphone is 2 days old

Hi there,
I would recommend taking a look at the troubleshooting steps found in the article below.
iPhone: Hardware troubleshooting
http://support.apple.com/kb/TS2802
-Griff W.

Where to go to see Lead Time settings? Calendar days vs working days

Hi everybody,
II'm trying to find the screen where details regarding Lead Time settings are shown. I'm looking specifically for information on the type of days we're using to identify Processing LT's. I'm not certain whether we're using calendar days or working days.
I'm sure there is a simple way of finding this information out, but just don't know where to look/change the setting.
Thanks,
BG

This is NOT a setting that you can view.
Oracle always behaves like this.
Best way to verify this is to create an item with PreLt=5, Processing LT=7 and Post-processing lt=5.
Then create a sales order with a due date of say 9/21. Make sure 9/1 to 9/21 is regular 5 days week.
Assuming no holidays, it will mean that you need material on the dock on 9/15 (5 days of PPLT = 7 calendar days.)
So when MRP/ASCP creates a Req/PO, the promised date will be 9/15.
Also, the Days from today will point to 9/1 - which includes 7 days of processing + 7 days of preprocessing (5 working days)
Hope this answers your quesiton.

Function Module for Date/ Time difference in Working Days

Hi all,
Are there any function modules which will calculate the difference between a date AND time, but in working days?
I can use the FIMA_DAYS_BETWEEN_TWO_DATES_2 FM for the dates, but I need to include times in this as well.
This is for situations where the 'starting date' is a non-working day, and the 'end date' is a working day. In this situation I need to take all the hours and minutes into account, which happened on the working day. To give an example -
Start date: 04.07.2010 (Sunday - Non working day)
Start time: 21:12:36
End date: 05.07.2010 (Monday - Working day)
End time: 04:47:24
I realise there is a Time option in this function module, but when I test it, it doesn't seem to be returning the desired results (returns 0 for days and time). I am using '5' as the I_STGMETH and 'GB' as the I_SKALID.
I need a calcuation which will return the time, post midnight on the working day - in this example, 4 hours, 47 minutes (seconds are optional!).
Can anyone help? - can I still use FIMA_DAYS_BETWEEN_TWO_DATES_2 but with different parameters?
Thanks
Mischa
Edited by: Mischa Gulseven on Jul 20, 2010 10:40 AM

Hi,
Thanks but this FM does not seem to account for working days.
For example, if I use:
DATE1                           04.07.2010 (non working day)
TIME1                           04:00:00
DATE2                           05.07.2010   (working day)
TIME2                           21:00:00
It will give the following results -
DATEDIFF                                                      1
TIMEDIFF                                                     17
EARLIEST                        1
I don't want to account for the non-working day so the result I actually want would be to calculate from midnight on 05.07 to 21:00 on 05.07 which should be 21 hours.
I suspect I probably need to include the STGMETH and the factory calendar somewhere in the FM?
Does such a FM exist, or could anyone help me with some ABAP for this?
thanks
Mischa

Time Dimension Working Days

Similar Messages

Maybe you are looking for