Monday Feb 24, 2014
Wednesday Feb 19, 2014
By Jeffrey McDaniel on Feb 19, 2014
Wednesday Jan 22, 2014
By Jeffrey McDaniel on Jan 22, 2014
Thursday Jan 09, 2014
By Jeffrey McDaniel on Jan 09, 2014
Wednesday Jan 08, 2014
By Jeffrey McDaniel on Jan 08, 2014
Here is a screenshot of a very simple analysis which can show this.
There is more that can be accomplished with the Resource Assignment subject area around Role and Resource usage and staffing. By using this subject area you can see enterprise wide role and resource usage, or filter down by assignments.
Thursday Dec 12, 2013
By Jeffrey McDaniel on Dec 12, 2013
Wednesday Dec 04, 2013
By Jeffrey McDaniel on Dec 04, 2013
Wednesday Nov 06, 2013
By Jeffrey McDaniel on Nov 06, 2013
Monday Oct 14, 2013
By Jeffrey McDaniel on Oct 14, 2013
If you would like to see how the Extended schema fields are mapped a good place to start is by looking in the ETL_MAPPING table. Choose what your source schema version is (example: EPPM 8.3 = 83)
select * from etl_mapping where source_version = 83;
Wednesday Oct 02, 2013
By Jeffrey McDaniel on Oct 02, 2013
In the example of udf's, you will see the projects listed and if there is a udf assignment you will see the value. If there is no assignment for that project you will see an empty column. If you never had an assignment, then added a udf you will see two rows. One for the previously empty row on that project, another for the new row containing the udf assignment. This will allow you over the life of your project to all the changes to it.
Friday Aug 30, 2013
By Jeffrey McDaniel on Aug 30, 2013
Indicator UDF's are not supported in P6 Analytics. The main reason being there isn't currently a way to move those same indicator images over into OBI, and the images that are used for indicators in P6 don't exist in OBI. There are some workarounds that can be used to achieve using UDF indicators in a way that based on the UDF indicator from P6 and image can be displayed in OBI.
There are two main pieces to this. First, the STAR data warehouse side. Second, how to have OBI display an indicator based on a text value. In this blog posting we'll look into the data warehouse side. In a later blog we'll look at the OBI side.
select * from udfvalue where projectobjectid = 4518;
You will get a result set back that shows UDFTEXT as BLUE, which is the text for the Blue Star icon. It will give subject area type and type of UDF - FT_STATICTYPE.
In the P6 Reporting Database these UDF's are not available in the configuration utility because they are not supported. But UDF's can be added directly to the staretl.properties file in the \res folder. This file is used for populating all dynamic code and UDF values on the OBI side. In this example this is the entry I added into my 6th position.
After you have added to the .properties file you will want to execute runSubstitution.cmd or .sh in the \etl\common folder. Running this will populate this new UDF row you just added through the .properties file into the other necessary files. Next step is to get the tables to populate this value. We are going to treat it like a text UDF . The only goal from the data warehouse side is to get it acting like a text UDF so a conditional statement can be added in OBI where if text = 'Blue Star' then display a certain icon.
update w_udfvalue_ds set DATATYPE = 'FT_TEXT'
where DATATYPE = 'FT_STATICTYPE' and SUBJECTAREA = 'PROJECT';
Save this file. (If all works out for you with your UDF's as indicators go back and add this same file as a template in \etl\oracle\templates\udf_load and save file as .tsql. This will save you from having to make edits to this script each time the config is run. Running config overwrites files in the \scripts directory.)
Tuesday Aug 20, 2013
By Jeffrey McDaniel on Aug 20, 2013
How can you tell what version of the P6 Reporting Database you have installed? There are two main ways.
1- Query the ETL_PARAMETER table with the following:
select p_feature, p_1 from etl_parameter
where p_feature = 'db.star.version'
or p_feature = 'etl.source.version';
The output will be similar to:
DB.STAR.VERSION will give the major release that this STAR database was installed from. The ETL.SOURCE.VERSION will tell you which P6 version the ETL process is running with, this helps determine the mappings.
2- In the <star installation directory> there is a version.txt that will also give the version number. The version.txt was added in the last couple releases and is updated when fix packs are added.
Thursday Aug 08, 2013
By Jeffrey McDaniel on Aug 08, 2013
In this example:
-P is the password of the new RPD
-I is the directory where the UDML file has been copied to
-O is the directory where your new RPD will be created.
Wednesday Jul 17, 2013
By Jeffrey McDaniel on Jul 17, 2013
Thursday Jul 11, 2013
By Jeffrey McDaniel on Jul 11, 2013
In the first part we discussed the types of slowly changing dimensions available in P6 Analytics and P6 Reporting Database.
Now lets look at how you would view the data. If you connected to your Staruser schema and queries w_project_hd you would be looking at your type 2 SCD project table. In this table you could have multiple rows per project if there were changes on that project and that project was opted in for slowly changing dimensions (see Part 1 of this blog for how to opt in).
In this screen shot we are looking at sample for project - Baytown.You'll notice three rows here for the same project id. The main rows we want to focus in on are:
effective_start_date, effective_end_date, and current_flag
When a project is first inserted into the w_project_hd table it will have current flag set to 'Y' to confirm this is the most recent value for this project row. The effective start date will be when it was inserted and the effective end data will be 01-Jan-3000. If you made a change for this project, ran the ETL you would get a second row. Now the original row would have an effective_end_date set to the effective_start_date of the new row and the current flag on that row would be set to 'N' and the new row would have the new current flag value of 'Y' and so on as more rows are added. It is a basic concept to follow and something you will want to be aware of if directly querying any _HF or _HD tables in the STAR schema.
Another thing to be aware of is if you are using P6 Analytics and the Primavera - Activity History subject area this is using the type 2 dimension tables along with a historical fact table. This will show all versions of these historical rows. You can add filtering to go on just current flag if necessary, but the ability to see and compare all historical dimension data will be available in this subject area.
Slowly changing dimensions and historical facts provide a very powerful tool to analyze data change over time. The ability to see historical dimensional changes gives a total project picture along with the existing and new history subject areas added in P6 Analytics 3.1 and P6 Reporting Database 3.1.
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'