C
cbyter
We are implementing MS Project Pro. and Project Server 2003, as a
front-end to push timesheet data to our ERP system (IFS), of which is
our Accounting, and Enterprise system backbone. We have an Enterprise
environment whereby approximately 200+ employees will be entering and
submitting daily timesheet updates.
We have customized the published fields, and the resource can change
that data in their Tasks view, if that setting is elected; that is what
we want to permit. This allows each resource to enter unique resource
employee data, i.e. Employee no., etc. into those published fields.
The primary problem is that, when the Project plan is updated, the last
entries made overwrites the existing published field data. In other
words, since a resource can only view their Tasks, we want their
employee data to be retained in the published fields, and not be
overwritten by the last Enterprise update. We have instances where
Employee No., or Cost Center entries have been overwritten and replaced
with another resources data. We do want the Project Plan to be updated,
in terms of 'Actual Work', 'Completion percentages', etc. but our
expectations where that the Published fields would remain static,
retaining the previously entered data, and only the Project Plan would
be updated, not republishing of custom fields to Project Server. At
least that's my interpretation of what the expectations were by the
Primary Administrator. I'm an Intern, and unfortunately don't have as
much time in the seat as the current Admin, whom is transitioning to a
new position within the company, as well as relocating to another
State. That Primary Admin has been stumped by this problem, and with
all going on, can't devote enough time to me, nor the issue,
unfortunately.
Any help that you may provide on this will be greatly appreciated.
front-end to push timesheet data to our ERP system (IFS), of which is
our Accounting, and Enterprise system backbone. We have an Enterprise
environment whereby approximately 200+ employees will be entering and
submitting daily timesheet updates.
We have customized the published fields, and the resource can change
that data in their Tasks view, if that setting is elected; that is what
we want to permit. This allows each resource to enter unique resource
employee data, i.e. Employee no., etc. into those published fields.
The primary problem is that, when the Project plan is updated, the last
entries made overwrites the existing published field data. In other
words, since a resource can only view their Tasks, we want their
employee data to be retained in the published fields, and not be
overwritten by the last Enterprise update. We have instances where
Employee No., or Cost Center entries have been overwritten and replaced
with another resources data. We do want the Project Plan to be updated,
in terms of 'Actual Work', 'Completion percentages', etc. but our
expectations where that the Published fields would remain static,
retaining the previously entered data, and only the Project Plan would
be updated, not republishing of custom fields to Project Server. At
least that's my interpretation of what the expectations were by the
Primary Administrator. I'm an Intern, and unfortunately don't have as
much time in the seat as the current Admin, whom is transitioning to a
new position within the company, as well as relocating to another
State. That Primary Admin has been stumped by this problem, and with
all going on, can't devote enough time to me, nor the issue,
unfortunately.
Any help that you may provide on this will be greatly appreciated.