Timesheet Hours (Actual Units) Remain On A Resource Assignment Even Though The Timesheet Was Rejected And Zero Hours Resubmitted On The Assignment. (Doc ID 897077.1)

Last updated on JUNE 06, 2017

Applies to:

Primavera P6 Enterprise Project Portfolio Management - Version: 6.1 and later   [Release: 6.1 and later ]
All Platforms
***Checked for relevance on 03-15-2011***

Symptoms

Timesheet hours (actual units) remain on a resource assignment even though the Timesheet was rejected and zero hours resubmitted on the assignment.

Example:

1. Timesheet user adds an activity to the Timesheet and submits 40 hours for Activity 1000. These are the first hours this resource has submitted against this assignment.

2. Then the Timesheet is approved and actuals are applied to the project. There are now 40 Actual Units for this resource logged for Activity 1000.

3. The Project Manager then realizes that the resource logged hours against the wrong activity and rejects the Timesheet so the Timesheet user can correct.

4. Timesheet user then corrects the Timesheet by entering zero hours (or deleted the 40hrs) from Activity 1000, enters 40 hours on the correct activity ( Activity 2000), and resubmits the Timesheet.

5. Project Manager approves Timesheet and Applies Actuals, thinking the 40 Actual Unit on Activity 1000 will be set to 0 and Activity 2000 will now have 40 Actual Units for Activity 2000.

6. However, Activity 1000 still has 40 Actual Units and Activity 2000 now has 40 Actual Units. Activity 1000's hours were not set to zero. Why?


Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms