P
Pawel
Hi,
It's me again
I have a little but very annoying problem with timesheet approval.
In my organization I have a number of Project Managers each of them is
normally configured as both a Timesheet Manager and Default Assignment Owner
for all people in his/her team.
PJMs themselves have both above assignmets pointing to him/herself.
The problem is that some PJMs, while accepting timesheets of their team
members in PWA, have the "next approver" fields set to themselves, but when
they approve the timesheet they get the error message of "Timesheet owner or
previous approvers cannot be approver". The same error appears in the "manage
queue".
This does not apply to all of PJMs although I cannot determine why only
these ones and not the others.
It does not help to remove the "next approver" at all - the system does not
accept that. The only workaround I know is to set the "next approver" to one
of the other managers (not related to the given project, we normally use an
adaministrator for taht purpose) and let him finally approve the timesheet.
Which is very tiresome.
I do not understand that effect, and I do not see a difference between
configuration of managers that experience that effect and these that do not.
On the other hand, I am not aware about any way to disable the "next
approver" completely (it would help, because we do not use a multi-level
timesheet approvals, at least not yet).
Any guidiance on what I may do wrong? Please?
Thanks,
Pawel
P.S. I begin to have a feeling that we might have chosen a not quite optimal
way of woirking with OPS: the timesheets seem to be the single most
underdeveloped feature of the Project Sever. It's a pity, because the
functionality itself is really much desired and provides the
closest-to-the-source production data I can think of now. On the other hand
however, it seems that timesheet functionality lacks tools (e.g. seriously
below expectations timesheet page customization), workflow (e.g. lack of
automated import of timesheeet data to task progress for companies like mine
that uses only timesheets but now is forced to do extra manual timesheet
import to the tasks) and in post processing (see my positings on Data
Analysis, timesheets and enterprise custom fields).
But OK, it is new functionality, so maybe it is normal that it has some
drawbacks. It has always been so with Microsoft and Project in particular so
why hope that this time it would be different...
But maybe I should blame myself, maybe I'm too stupid to operate the system.
Or maybe it is also a lack of documentation... ;P
It's me again
I have a little but very annoying problem with timesheet approval.
In my organization I have a number of Project Managers each of them is
normally configured as both a Timesheet Manager and Default Assignment Owner
for all people in his/her team.
PJMs themselves have both above assignmets pointing to him/herself.
The problem is that some PJMs, while accepting timesheets of their team
members in PWA, have the "next approver" fields set to themselves, but when
they approve the timesheet they get the error message of "Timesheet owner or
previous approvers cannot be approver". The same error appears in the "manage
queue".
This does not apply to all of PJMs although I cannot determine why only
these ones and not the others.
It does not help to remove the "next approver" at all - the system does not
accept that. The only workaround I know is to set the "next approver" to one
of the other managers (not related to the given project, we normally use an
adaministrator for taht purpose) and let him finally approve the timesheet.
Which is very tiresome.
I do not understand that effect, and I do not see a difference between
configuration of managers that experience that effect and these that do not.
On the other hand, I am not aware about any way to disable the "next
approver" completely (it would help, because we do not use a multi-level
timesheet approvals, at least not yet).
Any guidiance on what I may do wrong? Please?
Thanks,
Pawel
P.S. I begin to have a feeling that we might have chosen a not quite optimal
way of woirking with OPS: the timesheets seem to be the single most
underdeveloped feature of the Project Sever. It's a pity, because the
functionality itself is really much desired and provides the
closest-to-the-source production data I can think of now. On the other hand
however, it seems that timesheet functionality lacks tools (e.g. seriously
below expectations timesheet page customization), workflow (e.g. lack of
automated import of timesheeet data to task progress for companies like mine
that uses only timesheets but now is forced to do extra manual timesheet
import to the tasks) and in post processing (see my positings on Data
Analysis, timesheets and enterprise custom fields).
But OK, it is new functionality, so maybe it is normal that it has some
drawbacks. It has always been so with Microsoft and Project in particular so
why hope that this time it would be different...
But maybe I should blame myself, maybe I'm too stupid to operate the system.
Or maybe it is also a lack of documentation... ;P