My Oracle Support Banner

Remaining Early Units Are Not Spread Correctly When Using Bucket Planning. (Doc ID 2518833.1)

Last updated on DECEMBER 04, 2019

Applies to:

Primavera P6 Professional Project Management - Version 18.8 and later
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR:

Remaining Early Units are not spread correctly when using Bucket Planning.

While doing Manual Bucket Planning in Resource Assignment page, we are not getting proper Remaining Early Units value.

How is Remaining Early Units calculated?

EXPECTED BEHAVIOR:

Budgeted Units will remain same for Remaining Early Units, say for example day 2 is Budgeted 50 and Remaining Early Units also 50.

STEPS:

The issue can be reproduced at will with the following steps:
Activity Duration : 10 days
Resources (Material) : 50 Metric cube / per day

Activity type: Task Dependent, Duration Type: Fixed Duration and Units, Percentage Complete Type: Physical
Created Financial Period in Day wise:

Bucket Planning : Resource Assignment
                       DAY 1 DAY 2 DAY 3 DAY 4 DAY 5 DAY 6 DAY 7 DAY 8 DAY 9 DAY 10
Budgeted Units  40      50     70      30      50      50     50      50      60      50
Actual Units
Remaining Early 40      50     70      30      50      50     50      50      60      50
Units

Progress Updating :
Original Duration : 10 day, Actual Duration : 1day , Remaining Duration 9 day, At complete: 10day and Actual Units enter 40 Metric cube and store in Financial Period:

                       DAY 1   DAY 2   DAY 3   DAY 4   DAY 5   DAY 6   DAY 7   DAY 8   DAY 9   DAY 10
Budgeted Units  40        50        70       30        50        50       50        50        60        50
Actual Units       40
Remaining Early            37.36   49.20   52.84   34.62    45.56   45.56   45.56   52.84    46.47
Units

It seems to be applying the Default UPT of 50 once you change the RD to 9 instead of the Manual Curve value of 40. Once you move the DD one day, it applies the Actual Dur of 1 day and subtracts an additional 40 from the curve to get a RU total of 410 instead of 460 as expected.

If you use Update Progress to Schedule with Auto Compute Actuals applied at the Resource level, it calculates correctly.

BUSINESS IMPACT:

The issue has the following business impact:
Due to this issue, users cannot rely on spread results.

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.