Calendar time constraints

I started another thread about this but have had no replies. I know this means no one has a fix, but it would help a lot to know the answer to this question:
Is anyone currently syncing calendars - iCal or Entourage - to an external device, particularly a Nokia phone, where the iSync time constraints - "Don't sync events older than:..." and "Don't sync events after:... - are actually working?
I've established that I'm not the only person for whom they no longer work, but if I can find someone for whom they do actually work, then I'll keep debugging my system, instead of looking for a workaround and hoping it's fixed in the next update.
Thanks in advance,
Steve = : ^ )

A time constraint indicates whether more than one infotype record may be available at one time. The following time constraint indicators are permissible:
1 = An infotype record must be available at all times. This record may have notime gaps. You may not delete the record last stored on the database because all records of this infotype would otherwise be deleted.
2 = Only one record may be available at one time, but time gaps are permitted.
3 = Any number of records may be valid at one time, and time gaps are permitted.
Other possible time constraint indicators are as follows:
A = Only one record may ever exist for this infotype. It is valid from 01/01/1800 to 12/31/9999. Splitting is not permissible.
View V_T582B Infotypes Which are Created Automically controls whether the system automatically creates the infotype record for an employee hiring or an applicant data entry action.
Infotypes with time constraintA may not be deleted.
B = Only one record may ever exist for this infotype. It is valid from 01/01/1800 to 12/31/9999. Splitting is not permissible.
Infotypes with time constraint B may be deleted.
T = The time constraint varies depending on the subtype.
Z: Refers to time management infotypes. The time constraint for these infotypes depends on the time constraint class defined in view V_T554S_I Absence: General Control. Collision checks are defined in view V_T554Y TimeConstraint Reaction.

Similar Messages

Need help to populate Calendar/Time Dimension

Hi,
I need experts help in populating the calender dimension with the table structure as below. I need to populate this table from year 1900 to 2100. I was able to get the sql queries for some of the columns from web but could not find any help for most columns like 'DAY_IN_QUARTER'. If somebody could help me with a PL/SQL procedure to populate this table, I really appreciate your help. I know this is too much to ask for, but I have a time constraint in completing this!! :-(
DM_CALENDAR_ID is the primary kay with date in julian format.
Thanks in advance,
Ganesh
Calendar Dimension Table:
DM_CALENDAR_ID
DAY_NAME
DAY_ABBREVIATION
DAY_IN_WEEK
DAY_IN_MONTH
DAY_IN_QUARTER
DAY_IN_YEAR
WEEKDAY_IN_WEEK
WEEKDAY_IN_MONTH
WEEKDAY_IN_QUARTER
WEEKDAY_IN_YEAR
IS_MONTH_START_WEEKDAY
IS_QUARTER_START_WEEKDAY
IS_YEAR_START_WEEKDAY
IS_MONTH_END_WEEKDAY
IS_QUARTER_END_WEEKDAY
IS_YEAR_END_WEEKDAY
IS_MONTH_END
IS_QUARTER_END
IS_YEAR_END
DAYS_TO_GO_IN_MONTH
DAYS_TO_GO_IN_QUARTER
DAYS_TO_GO_IN_YEAR
WEEKDAYS_TO_GO_IN_MONTH
WEEKDAYS_TO_GO_IN_QUARTER
WEEKSDAYS_TO_GO_IN_YEAR
MONTH_ID
MONTH_LONG
MONTH_SHORT
MONTH_NUMBER_IN_YEAR
MONTH_NUMBER_IN_QUARTER
DAYS_IN_MONTH
WEEKDAYS_IN_MONTH
QUARTER_ID
QUARTER_NAME
QUARTER_NUMBER_IN_YEAR
DAYS_IN_QUARTER
WEEKDAYS_IN_QUARTER
YEAR_ID
DAYS_IN_YEAR
WEEKDAYS_IN_YEAR
CREATE_LOAD_DATE
CREATE_LOAD_USER_NAME

If somebody could help me with a PL/SQL procedure to populate this tablethis is one kind of proc, you can change according with your requirements...
CREATE OR REPLACE PROCEDURE TIME_DIM_PROC
(p_start_year IN NUMBER, p_end_year IN NUMBER) AS
v_calendar_date DATE ;
v_calendar_start_date DATE;
v_calendar_end_date DATE;
v_year NUMBER;
v_calendar_day NUMBER;
v_week_id VARCHAR2(12);
v_week_start_date DATE;
v_week_end_date DATE;
v_week_number NUMBER;
v_month NUMBER;
v_month_mm VARCHAR2(5);
v_month_start_date DATE;
v_month_end_date DATE;
v_month_id VARCHAR2(12);
v_quarter_start_date DATE;
v_quarter_end_date DATE;
v_quarter_id VARCHAR2(12);
v_half_year_start_date DATE;
v_half_year_end_date DATE;
v_half_year_id VARCHAR2(12);
v_year_start_date DATE;
v_year_end_date DATE;
v_fiscal_week_id VARCHAR2(12);
v_fiscal_week_month VARCHAR2(12);
v_fiscal_month NUMBER;
v_fiscal_month_start_date DATE;
v_fiscal_month_end_date DATE;
v_fiscal_month_id VARCHAR2(12);
v_fiscal_quarter_start_date DATE;
v_fiscal_quarter_end_date DATE;
v_fiscal_quarter NUMBER;
v_fiscal_quarter_id VARCHAR2(12);
v_fiscal_half_year_start_date DATE;
v_fiscal_half_year_end_date DATE;
v_fiscal_half_year_id VARCHAR2(12);
v_fiscal_year_start_date DATE;
v_fiscal_year_end_date DATE;
v_fiscal_year_id VARCHAR2(12);
v_fiscal_year NUMBER;
v_period_name VARCHAR2(12);
v_year_yy VARCHAR2(12);
v_year_id VARCHAR2(12);
v_loop_counter NUMBER;
v_number_of_days NUMBER;
v_fiscal_month_name VARCHAR2(10);
v_fiscal_quarter_name VARCHAR2(10);
v_fiscal_half_name VARCHAR2(10);
parameters_exception EXCEPTION;
BEGIN
IF p_start_year > p_end_year THEN
RAISE parameters_exception;
END IF;
v_calendar_start_date := to_date( p_start_year || '-01-01','YYYY-MM-DD');
v_calendar_end_date := to_date( p_end_year || '-12-31','YYYY-MM-DD');
v_calendar_date := v_calendar_start_date -1;
SELECT ( (v_calendar_end_date + 1 ) - v_calendar_start_date ) INTO v_number_of_days FROM dual;
FOR v_loop_counter IN 1..v_number_of_days
LOOP
v_calendar_date := v_calendar_date + 1;
v_year := TO_NUMBER(TO_CHAR(v_calendar_date,'YYYY'));
v_year_yy := TO_CHAR(v_calendar_date,'YY');
v_month := TO_NUMBER(TO_CHAR(v_calendar_date,'MM'));
v_month_mm := TO_CHAR(v_calendar_date,'MM');
v_calendar_day := TO_NUMBER(TO_CHAR(v_calendar_date,'DD'));
v_month_start_date := add_months(last_day( v_calendar_date ) +1 ,-1) ;
v_month_end_date := last_day( v_calendar_date );
v_week_id :=
CASE WHEN v_calendar_day BETWEEN 1 AND 7 THEN 'WK1'
WHEN v_calendar_day BETWEEN 8 AND 14 THEN 'WK2'
WHEN v_calendar_day BETWEEN 15 AND 21 THEN 'WK3'
WHEN v_calendar_day BETWEEN 22 AND 28 THEN 'WK4'
ELSE 'WK5'
END ;
v_week_id := v_week_id || '-' || v_month_mm || '-' || v_year_yy;
v_week_start_date :=
CASE WHEN v_calendar_day BETWEEN 1 AND 7 THEN add_months(last_day( v_calendar_date ) +1 ,-1)
WHEN v_calendar_day BETWEEN 8 AND 14 THEN add_months(last_day( v_calendar_date) +1 ,-1) + 7
WHEN v_calendar_day BETWEEN 15 AND 21 THEN add_months(last_day( v_calendar_date ) +1 ,-1) + 14
WHEN v_calendar_day BETWEEN 22 AND 28 THEN add_months(last_day( v_calendar_date ) +1 ,-1) + 21
ELSE add_months(last_day( v_calendar_date) +1 ,-1) + 28
END ;
v_week_end_date :=
CASE WHEN v_calendar_day BETWEEN 1 AND 7 THEN add_months(last_day( v_calendar_date ) +1 ,-1) + 6
WHEN v_calendar_day BETWEEN 8 AND 14 THEN add_months(last_day( v_calendar_date) +1 ,-1) + 13
WHEN v_calendar_day BETWEEN 15 AND 21 THEN add_months(last_day( v_calendar_date ) +1 ,-1) + 20
WHEN v_calendar_day BETWEEN 22 AND 28 THEN add_months(last_day( v_calendar_date ) +1 ,-1) + 27
ELSE last_day( v_calendar_date )
END ;
v_week_number :=
CASE WHEN v_calendar_day BETWEEN 1 AND 7 THEN 1
WHEN v_calendar_day BETWEEN 8 AND 14 THEN 2
WHEN v_calendar_day BETWEEN 15 AND 21 THEN 3
WHEN v_calendar_day BETWEEN 22 AND 28 THEN 4
ELSE 5
END ;
v_period_name :=
case when v_month = 1 then 'JAN'
when v_month = 2 then 'FEB'
when v_month = 3 then 'MAR'
when v_month = 4 then 'APR'
when v_month = 5 then 'MAY'
when v_month = 6 then 'JUN'
when v_month = 7 then 'JUL'
when v_month = 8 then 'AUG'
when v_month = 9 then 'SEP'
when v_month = 10 then 'OCT'
when v_month = 11 then 'NOV'
else 'DEC'
end || '-' || v_year_yy;
v_month_id :=
case when v_month = 1 then 'M01'
when v_month = 2 then 'M02'
when v_month = 3 then 'M03'
when v_month = 4 then 'M04'
when v_month = 5 then 'M05'
when v_month = 6 then 'M06'
when v_month = 7 then 'M07'
when v_month = 8 then 'M08'
when v_month = 9 then 'M09'
when v_month = 10 then 'M10'
when v_month = 11 then 'M11'
else 'M12'
end || '-' || v_year_yy;
v_quarter_start_date := case
when v_month between 1 and 3 then to_date( v_year || '-' || '01-01' , 'YYYY-MM-DD')
when v_month between 4 and 6 then to_date( v_year || '-' || '04-01' , 'YYYY-MM-DD')
when v_month between 7 and 9 then to_date( v_year || '-' || '07-01' , 'YYYY-MM-DD')
else to_date( v_year || '-' || '10-01' , 'YYYY-MM-DD')
end;
v_quarter_end_date := case
when v_month between 1 and 3 then to_date( v_year || '-' || '03-31' , 'YYYY-MM-DD')
when v_month between 4 and 6 then to_date( v_year || '-' || '06-30' , 'YYYY-MM-DD')
when v_month between 7 and 9 then to_date( v_year || '-' || '09-30' , 'YYYY-MM-DD')
else to_date( v_year || '-' || '12-31' , 'YYYY-MM-DD')
end;
v_quarter_id := case
when v_month between 1 and 3 then 'Q1'
when v_month between 4 and 6 then 'Q2'
when v_month between 7 and 9 then 'Q3'
else 'Q4'
end || '-' || v_year_yy;
v_half_year_start_date :=
case
when v_month between 1 and 6 then to_date( v_year || '-' || '01-01' , 'YYYY-MM-DD')
else to_date( v_year || '-' || '07-01' , 'YYYY-MM-DD')
end;
v_half_year_end_date :=
case
when v_month between 1 and 6 then to_date( v_year || '-' || '06-30' , 'YYYY-MM-DD')
else to_date( v_year || '-' || '12-31' , 'YYYY-MM-DD')
end;
v_half_year_id :=
case
when v_month between 1 and 6 then 'HALF1'
else 'HALF2'
end || '-' || v_year_yy ;
v_year_start_date := to_date( v_year || '-' || '01-01' , 'YYYY-MM-DD') ;
v_year_end_date := to_date( v_year || '-' || '12-31' , 'YYYY-MM-DD') ;
v_year_id := 'YR-' || substr(to_char(v_year),3,4) ;
v_fiscal_month_start_date:=add_months(last_day( v_calendar_date ) +1 ,-1) ;
v_fiscal_month_end_date:= last_day( v_calendar_date );
v_fiscal_month :=
case
when v_month = 1 then 10
when v_month = 2 then 11
when v_month = 3 then 12
when v_month = 4 then 1
when v_month = 5 then 2
when v_month = 6 then 3
when v_month = 7 then 4
when v_month = 8 then 5
when v_month = 9 then 6
when v_month = 10 then 7
when v_month = 11 then 8
else 9
end ;
v_fiscal_month_id :=
case
when v_month = 1 then 'M10' || '-' || substr(to_char((v_year-1)),3,4)
when v_month = 2 then 'M11' || '-' || substr(to_char((v_year-1)),3,4)
when v_month = 3 then 'M12' || '-' || substr(to_char((v_year-1)),3,4)
when v_month = 4 then 'M01' || '-' || substr(to_char((v_year)),3,4)
when v_month = 5 then 'M02' || '-' || substr(to_char((v_year)),3,4)
when v_month = 6 then 'M03' || '-' || substr(to_char((v_year)),3,4)
when v_month = 7 then 'M04' || '-' || substr(to_char((v_year)),3,4)
when v_month = 8 then 'M05' || '-' || substr(to_char((v_year)),3,4)
when v_month = 9 then 'M06' || '-' || substr(to_char((v_year)),3,4)
when v_month = 10 then 'M07' || '-' || substr(to_char((v_year)),3,4)
when v_month = 11 then 'M08' || '-' || substr(to_char((v_year)),3,4)
else 'M09' || '-' || substr(to_char((v_year)),3,4)
end ;
v_fiscal_quarter_start_date :=
case
when v_month between 1 and 3 then to_date( v_year || '-' || '01-01' , 'YYYY-MM-DD')
when v_month between 4 and 6 then to_date( v_year || '-' || '04-01' , 'YYYY-MM-DD')
when v_month between 7 and 9 then to_date( v_year || '-' || '07-01' , 'YYYY-MM-DD')
else to_date( v_year || '-' || '10-01' , 'YYYY-MM-DD')
end;
v_fiscal_quarter_end_date :=
case
when v_month between 1 and 3 then to_date( v_year || '-' || '03-31' , 'YYYY-MM-DD')
when v_month between 4 and 6 then to_date( v_year || '-' || '06-30' , 'YYYY-MM-DD')
when v_month between 7 and 9 then to_date( v_year || '-' || '09-30' , 'YYYY-MM-DD')
else to_date( v_year || '-' || '12-31' , 'YYYY-MM-DD')
end;
v_fiscal_quarter :=
case
when v_month between 1 and 3 then 4
when v_month between 4 and 6 then 1
when v_month between 7 and 9 then 2
else 3
end;
v_fiscal_quarter_id :=
case
when v_month between 1 and 3 then 'Q4' || '-'|| substr(to_char((v_year-1)),3,4)
when v_month between 4 and 6 then 'Q1' || '-'|| substr(to_char((v_year)),3,4)
when v_month between 7 and 9 then 'Q2' || '-'|| substr(to_char((v_year)),3,4)
else 'Q3' || '-'|| substr(to_char((v_year)),3,4)
end;
v_fiscal_half_year_start_date :=
case
when v_month between 4 and 9 then to_date(v_year ||'-04-01','YYYY-MM-DD')
when v_month between 10 and 12 then to_date(v_year ||'-10-01','YYYY-MM-DD')
else to_date((v_year-1) ||'-10-01','YYYY-MM-DD')
end;
v_fiscal_half_year_end_date :=
case
when v_month between 4 and 9 then to_date(v_year ||'-09-30','YYYY-MM-DD')
when v_month between 10 and 12 then to_date(v_year ||'-03-31','YYYY-MM-DD')
else to_date((v_year) ||'-03-31','YYYY-MM-DD')
end;
v_fiscal_half_year_id :=
case
when v_month between 4 and 9 then 'HALF1' || '-' || substr(to_char((v_year)),3,4)
when v_month between 10 and 12 then 'HALF2' || '-' || substr(to_char((v_year)),3,4)
else 'HALF2' || '-' || substr(to_char((v_year-1)),3,4)
end;
v_fiscal_year_start_date :=
case
when v_month between 4 and 12 then to_date(v_year ||'-04-01','YYYY-MM-DD')
else to_date((v_year-1) ||'-04-01','YYYY-MM-DD')
end;
v_fiscal_year_end_date :=
case
when v_month between 4 and 12 then to_date((v_year+1) ||'-03-31','YYYY-MM-DD')
else to_date((v_year) ||'-03-31','YYYY-MM-DD')
end;
v_fiscal_year_id :=
case
when v_month between 4 and 12 then 'FY' || '-' || substr(to_char((v_year)),3,4)
else 'FY' || '-' || substr(to_char((v_year-1)),3,4)
end;
v_fiscal_year :=
case
when v_month between 4 and 12 then v_year
else (v_year-1)
end;
v_fiscal_month_name :=
case when v_month = 1 then 'JAN'
when v_month = 2 then 'FEB'
when v_month = 3 then 'MAR'
when v_month = 4 then 'APR'
when v_month = 5 then 'MAY'
when v_month = 6 then 'JUN'
when v_month = 7 then 'JUL'
when v_month = 8 then 'AUG'
when v_month = 9 then 'SEP'
when v_month = 10 then 'OCT'
when v_month = 11 then 'NOV'
else 'DEC'
end;
v_fiscal_quarter_name :=
case
when v_month between 1 and 3 then 'Q4'
when v_month between 4 and 6 then 'Q1'
when v_month between 7 and 9 then 'Q2'
else 'Q3'
end;
v_fiscal_half_name :=
case
when v_month between 4 and 9 then 'HALF1'
else 'HALF2'
end;
INSERT INTO TIME_DIM
VALUES
( TIME_KEY_S.NEXTVAL ,
v_calendar_date,
'STANDARD-FISCAL',
v_week_start_date,
v_week_end_date ,
v_week_id ,
v_week_number ,
v_period_name,
v_month_start_date,
v_month_end_date,
v_month_id,
v_quarter_start_date,
v_quarter_end_date,
v_quarter_id,
v_half_year_start_date,
v_half_year_end_date,
v_half_year_id,
v_year_start_date,
v_year_end_date,
v_year_id,
v_year,
v_week_start_date,
v_week_end_date ,
v_week_id ,
v_week_number ,
v_fiscal_month_start_date,
v_fiscal_month_end_date,
v_fiscal_month,
v_fiscal_month_id,
v_fiscal_quarter_start_date,
v_fiscal_quarter_end_date,
v_fiscal_quarter,
v_fiscal_quarter_id,
v_fiscal_half_year_start_date,
v_fiscal_half_year_end_date,
v_fiscal_half_year_id,
v_fiscal_year_start_date,
v_fiscal_year_end_date,
v_fiscal_year_id,
v_fiscal_year,
1,
sysdate,
sysdate,
user,
user,
-1,
v_fiscal_month_name,
v_fiscal_quarter_name,
v_fiscal_half_name
COMMIT;
END LOOP;
COMMIT;
DBMS_OUTPUT.PUT_LINE ( 'v_calendar_date ' || v_calendar_date);
DBMS_OUTPUT.PUT_LINE ( 'v_year ' || v_year );
DBMS_OUTPUT.PUT_LINE ( 'v_month ' || v_month);
DBMS_OUTPUT.PUT_LINE ( 'v_month_start_date ' || v_month_start_date);
DBMS_OUTPUT.PUT_LINE ( 'v_month_end_date ' || v_month_end_date );
DBMS_OUTPUT.PUT_LINE ( 'v_period_name ' || v_period_name );
DBMS_OUTPUT.PUT_LINE ( 'v_month_id ' || v_month_id);
DBMS_OUTPUT.PUT_LINE ( 'v_quarter_start_date ' || v_quarter_start_date);
DBMS_OUTPUT.PUT_LINE ( 'v_quarter_end_date ' || v_quarter_end_date);
DBMS_OUTPUT.PUT_LINE ( 'v_quarter_id ' || v_quarter_id);
DBMS_OUTPUT.PUT_LINE ( 'v_half_year_start_date ' || v_half_year_start_date);
DBMS_OUTPUT.PUT_LINE ( 'v_half_year_end_date ' || v_half_year_end_date);
DBMS_OUTPUT.PUT_LINE ( 'v_half_year_id ' || v_half_year_id);
DBMS_OUTPUT.PUT_LINE ( 'v_year_start_date ' || v_year_start_date);
DBMS_OUTPUT.PUT_LINE ( 'v_year_end_date ' || v_year_end_date);
DBMS_OUTPUT.PUT_LINE ( 'v_year ' || v_year);
DBMS_OUTPUT.PUT_LINE ( 'v_fiscal_month ' || v_fiscal_month);
DBMS_OUTPUT.PUT_LINE ( 'v_fiscal_month_id ' || v_fiscal_month_id);
DBMS_OUTPUT.PUT_LINE ( 'v_fiscal_quarter_start_date ' || v_fiscal_quarter_start_date);
DBMS_OUTPUT.PUT_LINE ( 'v_fiscal_quarter_end_date ' || v_fiscal_quarter_end_date);
DBMS_OUTPUT.PUT_LINE ( 'v_fiscal_quarter ' || v_fiscal_quarter);
DBMS_OUTPUT.PUT_LINE ( 'v_fiscal_quarter_id ' || v_fiscal_quarter_id);
DBMS_OUTPUT.PUT_LINE ( 'v_fiscal_half_year_start_date ' || v_fiscal_half_year_start_date);
DBMS_OUTPUT.PUT_LINE ( 'v_fiscal_half_year_end_date ' || v_fiscal_half_year_end_date);
DBMS_OUTPUT.PUT_LINE ( 'v_fiscal_half_year_id ' || v_fiscal_half_year_id );
DBMS_OUTPUT.PUT_LINE ( 'v_fiscal_year_start_date ' || v_fiscal_year_start_date);
DBMS_OUTPUT.PUT_LINE ( 'v_fiscal_year_end_date ' || v_fiscal_year_end_date);
DBMS_OUTPUT.PUT_LINE ( 'v_fiscal_year_id ' || v_fiscal_year_id );
DBMS_OUTPUT.PUT_LINE ( 'v_fiscal_year ' || v_fiscal_year );
EXCEPTION
WHEN parameters_exception THEN
raise_application_error (-20001,'PASS p_start_date lesser than or equal to p_end_date');
WHEN OTHERS THEN
raise_application_error(-20002,'An error was encountered - '||SQLCODE||' -ERROR- '||SQLERRM);
END;
/

Time Constraint Error when calling a Function module from Webdynpro ABAP

Any help will be greatly appreciated - Thanks RM
Time Constraint Error
Information on where terminated
    Termination occurred in the ABAP program "SAPUP50R" - in
     "CHECK_TIME_CONSTRAINT_S1".
    The main program was "MP000000 ".
    In the source code you have the termination point in line 1069
    of the (Include) program "UP50RU01".
Error occurred during batch input processing
Source Code Extract
      l_is_inconsistent = 'X'.
    ENDIF.
Check if there are inverted time periods.
    IF l_prelp_line-begda > l_prelp_line-endda.
      l_is_inconsistent = 'X'.
    ENDIF.
Check if there are overlaps or gaps.
    IF NOT l_prelp_before IS INITIAL.
      l_date_difference = l_prelp_line-begda - l_prelp_before-endda.
      IF l_date_difference <> 1.
        l_is_inconsistent = 'X'.
      ENDIF.
    ENDIF.
    l_prelp_before = l_prelp_line.
ENDLOOP.
IF l_prelp_before-endda <> '99991231'.
    l_is_inconsistent = 'X'.
ENDIF.
IF l_is_inconsistent = 'X'.
    IF p_access_type = 'R'.
490 Datenbankschiefstand Personalnummer & Infotyp &
      MESSAGE x490 WITH l_prelp_before-pernr l_prelp_before-infty.
    ELSE.
491 Unzulässige Daten Personalnummer & Infotyp &
Line 1069 Error occcurs >>>> MESSAGE x491 WITH l_prelp_before-pernr l_prelp_before-infty.
    ENDIF.
ENDIF.
ENDFORM.                    " CHECK_TIME_CONSTRAINT_S1     "XYVN0352581
*&      Form clear_no_adapter_needed              new     "XREN844998
      text
FORM clear_no_adapter_needed .
CLEAR no_adapter_needed.
ENDFORM.                    " clear_no_adapter_needed
*&      Form set_no_adapter_needed              new     "XREN844998
      text
FORM set_no_adapter_needed .
no_adapter_needed = 'X'.
ENDFORM.                    " clear_no_adapter_needed

Hi,
Well, are you trying to do a batch input on infotype 0000? If yes you need to check that the proposed values respects the time constraint, meaning no gap, no overlaps and no inversions. Also fields SUBTY, OBJPS, SPRPS and SEQNR must remain initial when processing IT0000...
Kr,
Manu.

Calendar time zone on iOS 7

the time zone has disappearead on the calendar after updating to ios 7, how can it be defined? I travel a lot and this feature was very helpful in avoiding errors.

You have to enable Time Zone Support under Settings -> Mail, Contacts, Calendars -> Time Zone Support (in the Calendars section at the bottom). If you enable the setting while you are in the middle of creating an event, you have to cancel and re-create it.
Now, when you create a new Calendar entry, it will have a Time Zone field under the End time setting.

Calendar times off by 1 hour

Updated to new version of iTouch software today. After process was complete all of my calendar entry times for my corporate email account are off by 1 hour.

Some things you can check to troubleshoot this include:
Go to icloud.com, sign into your iCloud account, click your name at the top and choose Account Settings, click Time Zone and be sure it shows the correct time zone and that you have selected a city near you. Then open your calendar on icloud.com, click the gear-shaped icon on the bottom left and choose Preferences, click the Advanced tab and make sure you have not checked time zone support at the top.
On your iOS devices, go to Settings>Mail,Contacts,Calendars>Time Zone Support (in the Calendars section) and make sure this is set to Off. If you have a Mac, open the Calendar app and to to Mail>Preferences>Advances and uncheck “Turn on time zone support”.

Time Constraint for Boundary Events

Hi experts.
I am pretty new to BPM (NetWeaver Developer Studio 7.1 SP04 BPM SP05) and I am just making a test process to try to get the time constraint concept right. So far I have three tasks in my process, very much like a textbook example. In my first task I have an input field in which you're supposed to type in your name, which is then saved to the context and triggers the second task when completed. That second task is nothing but a screen displaying "You successfully generated a second task, (with the name you entered in the first task here)."
That works fine so far. Then there's the third task, which is linked to a boundary event on the second event with a start deadline which is critical exception. Here's the idea... You complete the first task (name input), then you fail to start the second task within a certain amount of time defined by an expression, so the process should go to the third task because of the deadline. By the way, it works fine when using a default time, so I must be doing something right so far, the problem is when trying to dynamically change the time with the expression.
What I tried was to define a context attribute type time and date (I tried both) and assigning a time (current time plus whatever amount of minutes) to that attribute via Java coding at the time you click on the button which completes the task, then use that context element in the expression, but that didn't work. I also tried to make that context attribute an integer and set it to whatever amount of minutes I want to use for the deadline, then in the expression get the current time and add that afore mentioned integer to its minutes. That didn't work either.
Please help, I have seriously done some research, and no success yet.
Edited by: david.palafox on Jul 1, 2010 5:54 PM

Figured it out.

Time Constraints and Boundary Events in BPM

Hi all,
I have done the following:
In the Task window, Time Constraints tab
- Checked "Define a default completion deadline" with the offset as 3 minutes.
- Checked the "Raise critical exception when deadline is reached" checkbox.
In the boundary events for the activity, I have added "CompletionDeadlineIsCriticalException".
From the boundary event, I have linked to to another activity that belongs to another user (User B).
When i am testing the BPM, the task goes into a Suspended status after 3 minutes. However User B did not received a new item in the UWL.
In the NWA, "Manage Process: Process Instances", i can see that Task is escalated by null and the status is suspended.
Does anyone has any advice over here?
Thank you.

Hi,
i have checked the BPEM-CORE version as instructed.
It says 1000.7.11.2.0.20090321233900
Does that means I need to update to the latest patch?
Please also check the version of your NWDI build plug-in BPEM-BUILDT in the respective NWDI track. This is used to build Process Composer DCs in your NWDI.
I am in the Development Infrastructure Perspective in NWDS
How do i check the version number for BPEM-BUILDT in the NWDI?
Thank you.

Any report to identify Time Constraint issues?

Hello,
Is there a report that I can run to get the employees and Infotype records with time constraint issues? So until last week, we had not turned on the PC-UI switch in T77S0 table. So the way it worked was, if in history there were 2 records with time gaps for Infotype with time constraint = 1, then it still allowed us to create new records. Now with the switch turned on, it gives an error. Once the historic records are corrected, it allows us to proceed. This is freaking out a lot of data specialists, and we were wondering if we can proactively identify the employees with these historic data inconsistencies and be able to correct them. Please let me know.
Thanks,
Nakul

Found it: RPUSCNTC
Thanks,
Nakul

Calendar Time Issue

I'm having a problem with viewing appointments in my calendar, and since I live in Saskatchewan we don't change our time, and the rest of the phone, including the main time on the phone are correct.
My issue is the "day view" shows everything an hour ahead, including the red line listing 4:18 PM, it's only 3:18 PM.
Also every appointment is listed an hour ahead, had one this morning at 8 AM and it shows 9 AM in the day view.
Even more confusing is when I click and open that calendar item, it shows the correct start time of 8 AM.
Any assistance anyone can provide would be greatly appreciated.
This is very annoying to say the least, especially with all appointments now being one hour ahead in the day view on the calendar...
My time zones settings are correct in the System Settings/Date and Time it is set to Saskatchewan (-6).

By changing my time display to 24 hours, under Settings/Date and Time and then moving the slider to ON for 24-Hour TIME, the calendar time view issues have disappeared.
Unfortunately the text messages are still out by an hour when viewing them individually. The time is correct on the main page when "conversations" are listed and the most recent text message is displayed, but going into each conversation each text message there displays an hour later than it should.
Hopefully this is something that BlackBerry is working on for the next update to the z10 software.

Calendar Time Problem

Hi, When I sync mi iphone 3gs with outlook 2007 calendar, it does, but the time for the event on my iphone shifts by one hour. Example: I create an appointment for today at 3:00PM on outlook, after the sync, it appears at 4:00PM on my Iphone and vice versa: if I create the same appointment on my iphone at 3:00PM, after the sync, it appears at 2:00PM on outlook. I tried everything but nothing worked.
Please Help

Hi pwmgen,
Welcome to Apple Support Communities!
Take a look at the article below and make sure the Time Zone Support settings aren't causing the issue that you are seeing on your iPhone.
iOS: How to adjust Time Zone Support for calendars
http://support.apple.com/kb/ht4576
When using Calendar on an iOS device, such as an iPhone, iPad, or iPod touch, you may notice that Time Zone Support is on by default. Depending on how you intend to use your iOS device, you may wish to either leave Time Zone Support on or disable it.
Time Zone Support is on by default for calendars on iOS. You can check and adjust this setting in Settings > Mail, Contacts, Calendars > Calendars > Time Zone Support.
Time Zone Support will allow you to create and view events in a time zone other than the one currently used by your iOS device (other than the one your clock is set to). If you do not use Time Zone Support, your iOS device will default to the current clock setting. iOS devices that are location aware will automatically set their time zone, date, and time using Location Services. You can verify your current date and time settings in Settings > Date & Time.
To disable Time Zone Support for calendars
Tap Settings > Mail, Contacts, Calendars.
Scroll down to Calendars.
Tap Time Zone Support.
Slide the slider for Time Zone Support to OFF.
To enable Time Zone Support for calendars
Tap Settings > Mail, Contacts, Calendars.
Scroll down to Calendars.
Tap Time Zone Support.
Slide the slider for Time Zone Support to ON.
Tap Time Zone.
Enter your current location or the closest city in the same time zone and tap it when it appears in the results list.
-Jason

Time constraints for IT0377

Hello All,
For the Benefits IT, 0377, we are using a benefit area 08 and subtype 0001.
For this Benefit Area and Subtype, we have configured several Benefit Plans such as BUPA, CYCL, TRVL etc.
We want to set the time constraint such that for an employee, multiple benefit plans for the same period can exist (Time Constraint 3), but at the same time, there should be no overlapping record for the same benefit plan.
for Ex, a BUPA can exist from 01.01.2007 - 01.01.2008 and
a CYCL could exist from 01.01.2007 - 01.01.2008 <i><b>but</b></i>
another BUPA with 15.01.2007 - 15.09.2007 should not be allowed. In this case the earlier BUPA should be delimited.
If I use time constraint 1 or 2 I cannot create multiple benefit plans, as all previous records with the same time range are deleted.
How can I configure the Infotype such that the above requirement can be fulfilled?
Thank You,
Vaishali

Hi..
I don't think it can be done, as this as time constraint depends on the startdate and enddate, and it has no connection with the Benifit Plan .

IPhone 3G Email and Calendar times off by one hour (slow one hour)

My times which I send/receive emails or put appointments on the calendar are 1 hour slow as compared to my computers. I have Mobile Me and Mobile Me (on the computer) and my Outlook emails and calendars match and my current time is correct on all. On the IPhone 3G the current time is correct but the time a email is sent or received and all appointments on the calendar are both off by one hour (one hour slow on the IPhone 3G).
I have set time automatically in "settings" to on, and under "email contacts and calendar" I have time zones disabled. I have tried each possible combination of these settings but cannot get the email/calendar times to match between my computers and the IPhone 3G regardless of how these are set.
I have numerous computers and all times are correct on all. On the IPhone 3G the current time (the clock) is correct, but times in emails and calendar appointments are all off (slow) by exactly one hour no matter what I do.
Anybody else have this issue, and/or know what the solution might be?
Thanks
The Omega

I have tried that and it did not work. I am now trying it with everything set to enable DST, and see if that works. Everything, so far, seems to be in sync. The phone would be right for a second when you went into the calendar and then change to be an hour off. Strange. I think the settings I have now (all, Windows, MobileMe, and the IPhone 3G set to DSL on, the same) may be working. Only time will tell.
Thank you.
The Omega

Position to Cost Center Relationship with time constraint 1

Hi,
I have a situation wherein:
1. There exists 2 records in PP01 with S-K relationship e.g. 01.01.2013 to 28.02.2013 and 01.03.2013 to 31.12.9999
2. There is a requirement to create another S-K record with dates; 01.02.2013-28.02.2013 automatically delimiting the first record.
Hence in all three records should exist
But when i try creating the 3rd record with end date 28.03.2013, it gives an information message stating End Date corrected to maximum end date of 31.12.9999. Thereby over writing the previous record(2nd one)
Do I need to change time constraint? Time constraint 1 should ideally allow this, as my records do not have gaps and exist at all times.
Please guide me through.

Hi Rohan,
Please check the table V_T777ZVK and the time constraint between S and A011 it must be 02 as per the standard system.
Then time constraint 2 means a maximum of one infotype record of the same type for the same object at the same time.
So if you change then end date must be 31.12.9999.
Regards,
Mithun K

N8 calendar times change when in new time zone

How do you stop the calendar times changing when you enter a new time zone? This is very frustrating, particularly when the calendar contains flight times etc which you have entered in the local time zone of place of departure. Then when you move into that time zone it automatically changes every calendar entry! Annoying! I realise I can deselect automatic time zones, but then I'm guessing when I do change the time zone manually to where I am (so that it shows the time of day, and I can set an alarm to wake me up, etc!!!) then the same thing will happen - all my calendar entries will change. Hope someone has worked it out already.

the times are stored on the phone in absolute time, lets call it gmt. they are then displayed on your handset in local time.
the times aren't actually changing as you change time zones. they are very much staying the same.
to achieve what you re after you are just going to have to enter the times in one of the text fields.
There's no dignity in begging for kudos. Do it for the karma.

How to make a custom infotype field the time constraint 1?????

Hello everyone I have this challenging question for gurus to answer it.
In custom created infotype for OM Ii have that field called ZZJOBID. When infotype was created I assigned the time constraint 1 for that infotype. That time constraint was base on OBJID not on ZZJOBID. Now the problem I am encountering is when I assign the 2nd ZZJOBID with time span 01011800-12319999 it overwrite the 1st assign ZZJOBID.
for the requirement reason I have to use PO10( not po03). If I change the time constraint to 3 which let me have the multiple records but I am losing the delimit and other functionality which comes with time constraint 1.

Suresh,
you are wright when you say that ' Time Constraint is for the Infotype/Subtype record and cannot be based off a field.' The OM infotype runs on bases of Object such as Organizational Unit, Job, etc... The point I was trying to draw is I am looking for a way that allow me to work via TC PO10 which run on Organizational Unit along with different ZZJOBID (with same begda and endda, if needed).

Calendar time constraints

Similar Messages

Maybe you are looking for