Inaccurate Spread Data in Extended Schema
Last updated on NOVEMBER 22, 2017
Applies to:Primavera P6 Enterprise Project Portfolio Management - Version 18.104.22.168 and later
Information in this document applies to any platform.
Incorrect spread data is observed in the extended schema.
With spread period set to weekly, 1 row per week per assignment/activity is expected, but 2 rows are visible.
Steps to reproduce:
Project has a single activity that spans 20 working days, starting on a Monday.
1st day of the week is set to Sunday.
Working week (Calendar) is Monday to Friday (Sunday is a non work day). This calendar is both for the activity, and the resources.
The single activity has a single resource, with 40 units planned.
The project has been scheduled, summarized and published.
The activity, nor the assignments have been progressed (no actuals)
Expected Spread details:
Expect to see 4 (Assuming 4 weeks duration) different lines in the activityspread table, one line for each week (max 5 lines if it spilled over into the next week).
Seeing 9 lines - the lines are being split into Sunday to Sunday; and Friday to Sunday; all for the same week. Instead of just a single Sunday to Sunday.
select * from pxrptuser.activityspread where projectobjectid = <proj_id>;
select * from pxrptuser.resourceassignmentspread where projectobjectid = <proj_id>;
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