By Jeffrey McDaniel on Dec 11, 2014
The scenario is, you logged into P6, you made a series of activity code changes on your project. An hour or two later you ran the ETL process, expecting to see the codes changes reflected when you viewed them in OBI or directly in your Star schema. However they are not updated, why?
Let's walk through the process of how the data gets there and why codes are different than updating activities directly.
Step 1: Project Publication - what counts as a change.
You are dependent on the thresholds being crossed for updating projects in the Extended schema (See earlier blog for more info on thresholds). Basically changes to a project are counted, then if you reach the threshold (say 100 changes) or the time threshold (say 24hrs. and 1 change) the project will be published. However items like code assignments do not count as a change. The only updated areas that count as a change are updates to the following tables:
PROJWBS (WBS rows), TASK (Activities), TASKRSRC (Resource Assignments), and TASKPRED (Relationships)
Step 2: Publishing the Project
The design behind this is these are the most commonly updated areas in a schedule. To throttle the system and avoid overloading the queue with unnecessary updates these are the core areas that drive updates. If you are making major changes to codes it is good to be aware of this and you can choose to 'Publish Now' which will then force a publication of your project and capture your code changes.
Step 3: Run the ETL
OK now that we have the Extended Schema (Project publication) side understood and worked out you can run the ETL as normal. Remember the Extended Schema is the heart of all the data that makes it into P6 Analytics. P6 Analytics and your STAR schema is only as up to date as your Extended Schema.