Niku/Clarity

This forum is for Clarity consultant best practises and solutions to various questions in Clarity

Friday, November 18, 2011

TimeScaled Settings

Tech Document
Title: Error Received: [The time periods requested do not exist. Review the column's Time Scale settings.] after changing timescaled view configurations
Description:
Error received: [The time periods requested do not exist. Review the column's Time Scale settings.] after changing timescaled view configurations within views/portlets such as the Resource Utilization page under the Task Tab or the Team Utilization portlet used in the Dashboard
Solution:
There are limits to what can be display within the TimeScaled field within views/portlets such as the Resource Utilization page under the Task Tab or the Team Utilization portlet used in the Dashboard.
These are internal timeslices that can not be configured. Internal timeslice range is as follows:
28 Daily - One week in the past, the current week and 3 weeks in the future 16 Weekly - 2 weeks in the past, the current week and 13 weeks in the future 36 Monthly - 4 quarters in the past, the current quarter and 7 quarters in the future Year, Quarter and Monthly periods all use monthly slices Weekly period uses weekly slices .Daily period uses daily slices
RESOLUTION ==================
Follow these guidelines when setting up Timescaled view period information.
The numbers of periods available are limited in the following manner:
Year: may set 3 periods - viewable data will be available for the following range: 1 year in the past to 2 years in the future
NOTE: 1 year in the past is only available if the current date is in the first quarter of the year, once the slices roll over only 3 quarters in the past will be available, as this is less than a year you will get the error if you are requesting dates from a year in the past.
Quarter: may set 12 periods - viewable data will be available for the following range: 4 quarters in the past and 8 quarters from current period to future
Monthly: may set 36 periods - viewable data will be available for the following range: 12 months in the past to 24 months from current period to future
Weekly: may set 16 periods - viewable data will be available for the following range: 2 weeks in the past to 14 weeks from current period to future
Daily: may set 28 periods - viewable data will be available for the following range: 7 days in the past to 21 days from current period to future
The start date that you choose - be it rolling or specific must fall within the date ranges listed above. The date which determines the past/future line is the current system date.
These data ranges may not be changed by end users, nor through customizations to the system. Even if you have timeslice data that is outside those ranges, the system still limits the view to the ranges specified above.
Therefore, even though you may have weekly and daily data within your requested range for example as far back as January 1 2005 to October 25, 2005, because that date range does not fall within with the limits for Weekly and Daily you will see the error telling you to check your timescale configuration.
MORE INFORMATION ==================
The Timescaled views setting are dependent upon the system timeslices which are not customizable by the end user.
The Monthly, Quarterly, Yearly slices rollover quarterly. So 22 months, 7 quarters and 1 year will only be available during some months.
Enhancement has been submitted to allow end users to change what the timescaled views are dependent upon.

Thursday, May 19, 2011

Running gel from command prompt - Oracle Driver not found

Ensure that you have JAVA_HOME set,classes12.jar and ojdbc14.jar exists in JAVA_HOME/lib directory,ojdbc14.jar exists in XOGCLIENT/lib directory.
Search in your local system for those jar files. If not found, Check for those jar files in Clarity installation server and copy them to your local machine.

Wednesday, April 6, 2011

Active Directory LDAP Errors

Just to find it easily:
Common Active Directory LDAP bind errors:
80090308: LdapErr: DSID-0C09030B, comment: AcceptSecurityContext error, data 525, v893
HEX: 0×525 – user not found
DEC: 1317 – ERROR_NO_SUCH_USER (The specified account does not exist.)
NOTE: Returns when username is invalid.

80090308: LdapErr: DSID-0C09030B, comment: AcceptSecurityContext error, data 52e, v893
HEX: 0x52e – invalid credentials
DEC: 1326 – ERROR_LOGON_FAILURE (Logon failure: unknown user name or bad password.)
NOTE: Returns when username is valid but password/credential is invalid. Will prevent most other errors from being displayed as noted.

80090308: LdapErr: DSID-0C09030B, comment: AcceptSecurityContext error, data 530, v893
HEX: 0×530 – not permitted to logon at this time
DEC: 1328 – ERROR_INVALID_LOGON_HOURS (Logon failure: account logon time restriction violation.)
NOTE: Returns only when presented with valid username and password/credential.

80090308: LdapErr: DSID-0C09030B, comment: AcceptSecurityContext error, data 531, v893
HEX: 0×531 – not permitted to logon from this workstation
DEC: 1329 – ERROR_INVALID_WORKSTATION (Logon failure: user not allowed to log on to this computer.)
LDAP[userWorkstations: ]
NOTE: Returns only when presented with valid username and password/credential.

80090308: LdapErr: DSID-0C09030B, comment: AcceptSecurityContext error, data 532, v893
HEX: 0×532 – password expired
DEC: 1330 – ERROR_PASSWORD_EXPIRED (Logon failure: the specified account password has expired.)
LDAP[userAccountControl: ] – PASSWORDEXPIRED
NOTE: Returns only when presented with valid username and password/credential.

80090308: LdapErr: DSID-0C09030B, comment: AcceptSecurityContext error, data 533, v893
HEX: 0×533 – account disabled
DEC: 1331 – ERROR_ACCOUNT_DISABLED (Logon failure: account currently disabled.)
LDAP[userAccountControl: ] – ACCOUNTDISABLE
NOTE: Returns only when presented with valid username and password/credential.

80090308: LdapErr: DSID-0C09030B, comment: AcceptSecurityContext error, data 701, v893
HEX: 0×701 – account expired
DEC: 1793 – ERROR_ACCOUNT_EXPIRED (The user’s account has expired.)
LDAP[accountExpires: ] – ACCOUNTEXPIRED
NOTE: Returns only when presented with valid username and password/credential.

80090308: LdapErr: DSID-0C09030B, comment: AcceptSecurityContext error, data 773, v893
HEX: 0×773 – user must reset password
DEC: 1907 – ERROR_PASSWORD_MUST_CHANGE (The user’s password must be changed before logging on the first time.)
LDAP[pwdLastSet: ] – MUST_CHANGE_PASSWD
NOTE: Returns only when presented with valid username and password/credential.

80090308: LdapErr: DSID-0C09030B, comment: AcceptSecurityContext error, data 775, v893
HEX: 0×775 – account locked out
DEC: 1909 – ERROR_ACCOUNT_LOCKED_OUT (The referenced account is currently locked out and may not be logged on to.)
LDAP[userAccountControl: ] – LOCKOUT
NOTE: Returns even if invalid password is presented.

Friday, March 6, 2009

Timesheet Detail Report

What are conditions for Timesheet Detail Report to display data?
If the Timesheet Detail Report returns a message that there are no results that match your criteria you should check the following:

1.The person running the report must have Timesheet Edit or Timesheet Approve rights over the resources whose timesheets they expect to see on the report.

2.Are your Timeslices and Datamart jobs running without error.

3.Are the dates that you specified for the Timesheet Detail report with the defined date range for your Timeslices. The Timesheet Detail Report draws data from the DailyResourceActuals slice.

4.For data to display on this report, resources must be setup and assigned a Track Mode of “Clarity” in the resource general properties page. The resource must have entered hours worked into their timesheet in Time for the time period that is selected.

5.Timesheet Detail report will only show resources for which the logged in user has the 'resource-enter time' or ‘approve time’ instance or OBS right. Even if the user has all global timesheet permissions, the report will not show any resources.

Thursday, November 13, 2008

Resource Calendar

Below is the query to get calendar of a resource

select srmr.unique_name,
srmr.full_name,
prc1.prname basecalendar,
prc.prname calendar
from srm_resources srmr,
prj_resources prjr,
prcalendar prc,
prcalendar prc1
where srmr.is_Active=1
and srmr.person_type<>0
and srmr.id=prjr.prid
and prjr.prcalendarid=prc.prid
and prc.prbasecalendarid=prc1.prid(+)