R12 How is the Task Weightage Calculated in Project Management when Based on Effort and Effort has not yet been Incurred. (Doc ID 2143356.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Project Planning and Control - Version 12.2.4 and later
Information in this document applies to any platform.

Goal

The customer is using Effort based Task Weightage, Currently they have no effort on any subtasks for a particular Task, but the Weightage shows as:

Task 1        Start Finish 100%
Task 1.1      2/1/16 5/10/16       33.34
Task 1.2      1/1/16 6/10/16       33.33
Task 1.3     12/1/15 9/20/16      33.33

The customer expects that if there is no effort, the task weightage would be zero.

Troubleshooting Workplan Issues in Project Management (Doc ID 1671630.1):

31.Physical Percent Complete

Oracle Projects calculates physical percent complete for tasks based on one of four physical percent complete derivation methods: Cost, Effort, Deliverable, or Work Quantity. The task type provides the default physical percent complete derivation method for the task. You can optionally override the default physical percent complete derivation method. Different tasks for the same workplan structure can use different methods to derive physical percent complete

Using Effort to Derive Physical Percent Complete
When the physical percent complete derivation method for a task is Effort, Oracle Projects calculates physical percent complete using planned and actual quantities. The physical percent complete rollup method determines how Oracle Projects calculates physical percent complete for summary tasks. For information on physical percent It then uses the result of this calculation to calculate percent complete effort using the following formula:

Percent Complete Effort = (Actual Effort / Estimate at Completion) * 100

~~~~~~~~~~~~~~~~~~

Bug 6207986: TST1203.0:PJ:QA:TASK WT(%) CHANGES ON CHANGING ROLLUP METHOD TO EFFORT/PROC UPD2. EXPECTED BEHAVIOR:

Task weighting(%) is used only for duration and manual based rollup.  Hence, on changing the planned effort, the Task weighting(%) must not change. This was never the behavior which was intended in FP-M as Task weighting(%) would not have any meaning when the rollup method is Effort as we go by the Earned value method for rollup.
...
As there is no use of Task Weighing(%) when the roll up method is 'Effort', QA wants to retain the task weighing % same as that of rollup method Duration even though the rollup method is changed to 'Effort'.
..
1. Description
When the rollup method is changed from 'Duration' to 'Effort', then the task weighing percentage is also getting re-calculated for 'Effort'.


2. Resolution
This is the intended functionality.

~~~~~~~~~~~~~~~~~~

Indicates task weightage can be calculated on effort based tasks

What is the intended functionality if no effort.

Solution

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