Cannot See Task In Timesheet

[navzjoshi00]

All

I have recently come across an issue wherein a user is unable to see the task in the their timesheet.

I've checked everything - from project to task to resource - everything open for time entry - trackmode for both - project and resource is Clarity.

But still, I am unable to figure out why the resource is unable to see the task in the timesheet.

Any suggestions as to what else I can look for are most welcome .. :)


Thanks & Regards
NJ

[Anon Anon]

There is always a reason! ;-)

I know you have said you have checked that the TASK is open for time entry, but have you also checked that all "parent tasks" in the WBS are also open for time entry?

(this is usually the trick that catches people out)

[navzjoshi00]

Hey Dave

Yep... have checked that as well..
.
Am unable to figureout what exactly would be the cause.

Interesting part is that for the time period start from Feb-07-2011 (that is posted), the task is available in the timesheet... :)

Regards
NJ

[Anon Anon]

Task is "completed"?

--

Can you "Add Task" it or are you just trying "Populate" (in which case the task dates have an effect)

[navzjoshi00]

Task Start Date = 10/25/2010
Task End Date = 2/28/2011
Task Status = Started

Assignment Start Date = 10/25/10
Assignment End Date = 2/28/11
Actuals for the resource on task = 81.00
ETC = 1

:(

Regards
NJ

[Tammi Reel-Davis]

We had instances of this issue, if you have a WBS in your project make sure you check the Phase, Activity and Task to make sure its open for time entry. If the Activity is closed for time entry then the task underneath could be effected.

Thanks
Tammi

[navzjoshi00]

Hi

We have checked all that, but still unableto figure out...

There is no reason as to why the task should not appear in the timesheet.

Regards
NJ

[navzjoshi00]

A quick one regarding this issue - if the task is marked as completed, and then again started, would that cause the task to not appear in the timesheet ?

Regards
NJ

[Anon Anon]

^ I don't think it "should" do that.

--

You never answered my question about whether you could "Add Task" it?

BUT....

If you really want to know the answer then;

(assuming it doesn't appear when you "Populate")

SQLTRACE_ACTIVE your session.

"Populate" the timesheet

Get the SQL that this generates from the trace file.

Run that SQL directly against the database - obviously this will not return your task.

Start commenting out / removing conditions in the SQL until your task appears...... and then you have found the answer.


Not fun to do, but if you really have exhausted all the "application investigation" you can do then that is the only way to know for sure.

[navzjoshi00]

Hi Dave

"You never answered my question about whether you could "Add Task" it? " - the task doesn't even appear - whether I click on "Add" / "Populate", and the most interesting part is that the same task of the same project can be located in the user's timesheet in other environments.

And yes, I did the SQL Trace , and got the below query -

[color=#1418F3]SELECT * FROM ( SELECT T.PRID AS TASK_ID
,T.PRNAME AS NAME
,T.PREXTERNALID AS UNIQUE_NAME
,T.PRSTART AS START_DATE
,T.PRFINISH AS FINISH_DATE
,T.PRSTATUS AS TASK_STATUS
,T.PRWBSSEQUENCE
,P.ID AS PROJECT_ID
,P.NAME AS PROJECT_NAME
,P.CODE AS PROJECT_UNIQUE_NAME
FROM INV_INVESTMENTS P, INV_PROJECTS PRJ, PRTEAM
, PRTASK T , (SELECT prtaskid, prresourceid FROM PRASSIGNMENT WHERE PRRESOURCEID=<ResourceID>) A
WHERE T.PRID = A.PRTASKID AND PRTEAM.PRRESOURCEID=<ResourceID>
AND PRTEAM.PRISOPEN <> 0
AND P.ID = PRTEAM.PRPROJECTID
AND P.IS_ACTIVE <> 0
AND PRJ.PRID = P.ID AND PRJ.IS_TEMPLATE = 0
AND P.IS_OPEN_FOR_TE <> 0 AND P.TRACK_MODE = 2
AND T.PRPROJECTID = P.ID
AND T.PRISMILESTONE = 0
AND T.PRISTASK <> 0
AND T.IS_OPEN_TE = 1 AND T.PRSTATUS <> 2 MINUS
SELECT T.PRID AS TASK_ID
,T.PRNAME AS NAME
,T.PREXTERNALID AS UNIQUE_NAME
,T.PRSTART AS START_DATE
,T.PRFINISH AS FINISH_DATE
,T.PRSTATUS AS TASK_STATUS
,T.PRWBSSEQUENCE
,P.ID AS PROJECT_ID
,P.NAME AS PROJECT_NAME
,P.CODE AS PROJECT_UNIQUE_NAME
FROM INV_INVESTMENTS P, INV_PROJECTS PRJ, PRTEAM
, PRTASK T , (SELECT prtaskid, prresourceid FROM PRASSIGNMENT WHERE PRRESOURCEID=<ResourceID>) A
WHERE T.PRID = A.PRTASKID AND PRTEAM.PRRESOURCEID=<ResourceID>
AND PRTEAM.PRISOPEN <> 0
AND P.ID = PRTEAM.PRPROJECTID
AND P.IS_ACTIVE <> 0
AND PRJ.PRID = P.ID AND PRJ.IS_TEMPLATE = 0
AND P.IS_OPEN_FOR_TE <> 0 AND P.TRACK_MODE = 2
AND T.PRPROJECTID = P.ID
AND T.PRISMILESTONE = 0
AND T.PRISTASK <> 0
AND T.IS_OPEN_TE = 1
AND (EXISTS
(SELECT PARENT.PRID FROM PRTASK PARENT
WHERE PARENT.PRPROJECTID = P.ID
AND PARENT.PRWBSSEQUENCE < T.PRWBSSEQUENCE
AND PARENT.WBS_NNBSEQ > T.PRWBSSEQUENCE
AND PARENT.IS_OPEN_TE = 0)
OR T.PRID IN
(SELECT DISTINCT A1.PRTASKID
FROM PRASSIGNMENT A1, PRTIMEENTRY TE1
WHERE TE1.PRASSIGNMENTID = A1.PRID
AND TE1.PRTIMESHEETID = <TimesheetId>)
) ) SORTABLE_DATA_SET ORDER BY PROJECT_NAME asc, PRWBSSEQUENCE asc;[color]

If you take off the first part (before 'minus') -

[color=#1418F3]SELECT * FROM ( SELECT T.PRID AS TASK_ID
,T.PRNAME AS NAME
,T.PREXTERNALID AS UNIQUE_NAME
,T.PRSTART AS START_DATE
,T.PRFINISH AS FINISH_DATE
,T.PRSTATUS AS TASK_STATUS
,T.PRWBSSEQUENCE
,P.ID AS PROJECT_ID
,P.NAME AS PROJECT_NAME
,P.CODE AS PROJECT_UNIQUE_NAME
FROM INV_INVESTMENTS P, INV_PROJECTS PRJ, PRTEAM
, PRTASK T , (SELECT prtaskid, prresourceid FROM PRASSIGNMENT WHERE PRRESOURCEID=<ResourceID>) A
WHERE T.PRID = A.PRTASKID AND PRTEAM.PRRESOURCEID=<ResourceID>
AND PRTEAM.PRISOPEN <> 0
AND P.ID = PRTEAM.PRPROJECTID
AND P.IS_ACTIVE <> 0
AND PRJ.PRID = P.ID AND PRJ.IS_TEMPLATE = 0
AND P.IS_OPEN_FOR_TE <> 0 AND P.TRACK_MODE = 2
AND T.PRPROJECTID = P.ID
AND T.PRISMILESTONE = 0
AND T.PRISTASK <> 0
AND T.IS_OPEN_TE = 1 AND T.PRSTATUS <> 2 [color]

the task does appear

In the second part -
[color=#1418F3] SELECT T.PRID AS TASK_ID
,T.PRNAME AS NAME
,T.PREXTERNALID AS UNIQUE_NAME
,T.PRSTART AS START_DATE
,T.PRFINISH AS FINISH_DATE
,T.PRSTATUS AS TASK_STATUS
,T.PRWBSSEQUENCE
,P.ID AS PROJECT_ID
,P.NAME AS PROJECT_NAME
,P.CODE AS PROJECT_UNIQUE_NAME
FROM INV_INVESTMENTS P, INV_PROJECTS PRJ, PRTEAM
, PRTASK T , (SELECT prtaskid, prresourceid FROM PRASSIGNMENT WHERE PRRESOURCEID=<ResourceID>) A
WHERE T.PRID = A.PRTASKID AND PRTEAM.PRRESOURCEID=<ResourceID>
AND PRTEAM.PRISOPEN <> 0
AND P.ID = PRTEAM.PRPROJECTID
AND P.IS_ACTIVE <> 0
AND PRJ.PRID = P.ID AND PRJ.IS_TEMPLATE = 0
AND P.IS_OPEN_FOR_TE <> 0 AND P.TRACK_MODE = 2
AND T.PRPROJECTID = P.ID
AND T.PRISMILESTONE = 0
AND T.PRISTASK <> 0
AND T.IS_OPEN_TE = 1[color]
the task does appear

Regards
NJ

[Anon Anon]

OK then just start running the "second part" of that query... you need to find out why it is "minus"-ing it from the list of available codes (the list provided by the first part of the query).

i.e. run that second query (where the code DOES appear) and then start removing conditions until it doesn't appear.

(Make sure you are only removing "conditions" not "joins" though)

[navzjoshi00]

Hey Dave
We further checked the database and found that the task ids -
A
B
are showing up as child tasks for the task (in the database) -
C

However, if we look at the GUI, the task ids -
A
B

are showing up as child tasks for -
D


This seems to be because of some task indent / outdent activity.

Since the task -
C
is not open for timeentry, hence, the tasks -
A
B
are not showing up on the timesheet.


We have suggested that the user should follow the below steps -

1. Access the WBS page of the project

2. Select the checkbox tasks -
A
B

3. Click on 'WBS Layout' button, and then select 'Outdent'

4. Then select these tasks again, and select 'Indent'




Regards
NJ

[Anon Anon]

Good news!

--

So your problem actually turned out to be what I posted in the 2nd post in the thread (and what Tammi restated in the 6th post!) :bashful:

......although, the application appeared to be hiding this from you, so no wonder it was hard to find. :mellow:

Any idea why (how?) your WBS had got 'corrupted' in this way? :wacko:
Does this affect any of your other plans?
(I would worry about that sort of thing)

[navzjoshi00]

Yep... that's what my concern is as well...

I had opened a case with CA to find out the reason for the task not appearing on the timesheet.... But now, since I know the reason, the question that I have put to CA is why it would have happened ... will keep u posted... :)

Thanks both - Tammi & Dave


Regards
NJ

[Tammi Reel-Davis]

I am glad it worked out! I experience it several times. First I check to see if the project, resource, task is open for time entry when that doesn't work I start looking at the WBS.

[Deactivated User]

The problem is that there are two field which define this

,[PRWBSLEVEL]
and
,[PRISTASK]
or even
,[PRISMILESTONE]

the only action available to the user in the GUI is indent or outdent and that is expected to automatically take care of both level and is task.
However, that does not always happen and it is even possible to fool the system.

This was also discussed in the OWB forum (RIP) every now and then. The structure of the OWB xml file shows the same

Task earlyStart="2004-09-01T08:00:00" baseTime="2006-01-26T01:25:37" lateStart="2004-09-01T08:00:00"
start="2004-09-01T08:00:00" proxy="false" earlyFinish="2004-09-02T17:00:00" lateFinish="2004-09-02T17:00:00"
critical="true" status="1"
outlineLevel="2"
baseFinish="2004-09-03T17:00:00" finish="2004-09-03T17:00:00"
summary="false"
baseStart="2004-09-01T08:00:00" baselineDuration="3.0" milestone="false"
name="Create Project Plan" taskID="1.0" fixed="false" locked="false" key="false"
percComp="1.0" totalSlack="0.0" unplanned="false">

the attributes are ouline level and summary level which do not always go together

The best known way to fool the system in OWB is to have tasks before the first summary level item.
Then even if the are tasks (summary leve = false) they are at the same outline level as phases

There were other work arounds on OWB site forum where you could have tasks after summary level items in WBS sequence but at the same indent level.

Martti

[navzjoshi00]

Thanks for sharing the info Martti.

Regards
NJ

[Deactivated User]

Just to illustrate it some more
When you create a WBS in Clarity at the beginning all tasks are at WBSlevel 1 and tasks.
To create summary level items you intend the items under them to make them children.
Indentation increases the WBS level number by one
An item having children maintains its WBS level number becomes a parent
At the end you have something like the illustration.
If you have the basic WBS levels
Phase
Activity
Task
you would expect that
Phase is level 1
Activity is level 2
Task is level 3
but as you can see that is not the case.
WIth no access to OWB site to verify the posts I would expect that things like moving items, deleting them, further indent and outdent which are quite normal actions if done ins a specific sequence would achieve a situation where a task does not have pristask = 1
What some poster on OWB site wanted was was to have
Phase
Task
Task
but so that the those task were not under the Phase in WBS hierarchy , but just after it in sequence


Martti K.

[Deactivated User]

That is when the system is working as designed.
but when it is not see eg.

TEC541669 Clarity: WBS Page does not refresh properly using Clarity 12.0.6.5471 generic_013 patch level.
After installing the generic 13 patch for Clarity 12.0.6. The Work Breakdown Structure page no longer refreshes properly when indenting or outdenting tasks.


Martti K.

[Slovak]

If this is a child taks to a parent make sure the parent is open for time entry. If the parent is not open for time entry, then ALL child tasks will not be open for time entry.

Check time period.
Check to see if the task resources have hours and they have been allocated.
Check to see if the porject is active and financails are open.