Thursday Dec 12, 2013
I moved this project to a new EPS, but it still shows an older EPS name? Why?
The main culprit of most data mismatches is the ETL process was run before the P6 Extended Schema services were able to update the data. But don't worry it is just temporary. The services will continue to run and the data will be updated. One of the keys is understanding the data flow and what service controls what data.
If you are working in P6, updating your project and activities the project services will pick up these changes and the services will be running in the background and you wouldn't need to do anything manually, the environment would update itself based on the thresholds you defined.
For some items like EPS they are controlled by a different service. There are the global services - Enterprise Data, Resource Management, Security, and Enterprise Summaries. Enterprise Data consists of dictionary level data like Codes, Calendars, and Portfolios. Resource Management as expected handled Resources, Roles, and other related dictionary level resource data. Security handles new,removed,or updated users and access. Enterprise Summaries handles summary data along with updating EPS.
For the example above, if someone moved projects around from different EPS levels they would want to have the Enterprise Summaries service run before they ran the ETL process if they wanted to view the data immediately. Planning out when the global services run and when the ETL process runs is a good idea. Generally the global services are set to run daily, same as the ETL process. You can schedule your global services to run at midnight and your ETL process at 1am and in that case all your data will be up to date.
Wednesday Dec 04, 2013
By Jeffrey McDaniel on Dec 04, 2013
If you are working in the P6 Reporting Database or P6 Analytics and you notice that either your spread range or resource utilization and limit ranges haven't adjusted more than likely it has to do with your P6 Extended Schema.
First check in your STAR schema:
select min(day_dt),max(day_dt) from w_day_d;
In the P6 Extended schema an initial date range is set when the project services and global services are run the 1st time. Generally the range is not changed after that point. The date range creates a rolling window of time. You set your start date and then your finish range to be plus a certain amount of months or years in the future. An example is setting your start date to be:
Jan-1-2012 and a rolling 3 year window (today's date + 3 years).
Looking at the ReportDate table you want to see if this matches your expected date range:
select min(daydate),max(daydate) from reportdate;
If all global services were run today and project services this should be updated and max should reflect today's date. If for some reason it does not make sure the Enterprise Data service has been run. Make sure you are still publishing projects. And if all seems functional, a last case scenario you could truncate the reportdate table then rerun the Enterprise Data service. This will force a new recalculation of the date range for this table.
After this is completed you can run the StarETL and you should see w_day_d updated with this date range. If for any reason you are still seeing an issue then the w_day_d can be truncated and repopulated on the next ETL run. Again truncating of these tables should not be necessary and is only in extreme cases. In a majority of cases having the Enterprise Data service and ETL run will make sure all date ranges in the P6 Reporting Database and P6 Analytics are up to date.
Provide new information on P6 Analytics and Reporting Database.
- Before you upgrade...what to expect (P6 Reporting Database)
- P6 Extended Schema - advanced techniques and additional information
- Report on ETL Status of a Multiple Datasource Environment
- How to find resources without any assignments?
- Role Usage in P6 Analytics
- EPS changes in Analytics (and P6 Extended Schema)
- Analytics Date Range is Out of Date
- Why Does Adding a UDF or Code Truncates the # of Resources in List?
- Reference for STAR field mappings
- Usage of Historical UDF's and Current Flags When Creating Analysis'