Friday Aug 08, 2014
By Jeffrey Mcdaniel-Oracle on Aug 08, 2014
Monday Jul 28, 2014
By Jeffrey Mcdaniel-Oracle on Jul 28, 2014
The current data is overwritten every ETL update. This will keep your data as up to date as the last ETL. If you worked on a project, deleted a project, updated tasks, deleted tasks, scheduled - that will all be reflected. In the Historical tables, these changes once captured will always remain. For example, you deleted a project. In your list of projects this will still be available. Once the data is captured it is always in the database. This way you truly have a historical perspective.
Wednesday Jun 25, 2014
Friday Jun 20, 2014
By Jeffrey Mcdaniel-Oracle on Jun 20, 2014
Thursday May 29, 2014
By Jeffrey Mcdaniel-Oracle on May 29, 2014
Prior to P6 Reporting Database version 3.2 sp1 range partitioning was used. This was applied only to the history tables. The ranges were defined during installation and additional ranges would need to be added once your date range entered the final defined range.
As of P6 Reporting Database version 3.2 sp1, interval partitioning was implemented. Interval partitioning was applied to the existing History table as well as Slowly Changing Dimension tables. One of the major advantages of interval partitioning is there is no more manual addition of ranges. The interval partitioning will automatically create partitions for the defined interval when data is inserted into the table and it exceeds the existing partitions. In 3.2 sp1 there are steps on how to update your partitioning. For all versions after 3.2 sp1 interval partitioning is the only partitioning option used. When upgrading it is important to be aware of these changes. Here is a link with more information on partitioning -the types and the advantages.
Friday May 09, 2014
By Shawn Lafferty-Oracle on May 09, 2014
In a previous blog, we covered how to bring indicator type UDFs (User Defined Fields) into the STAR data warehouse by manually adding them as text type UDFs in the staretl.properties file and adding a script into the ETL process. In this post we’ll cover how to use conditional formatting in Oracle Business Intelligence to display these indicator UDFs in analyses.
First, create a new analysis in Oracle Business Intelligence, in this example we’re
using the Primavera – Activity subject area, and a simple selection of two indicator
type Project UDFs, Schedule Status and Overall Status.
Since the indicators UDFs are being stored as text in the
STAR, the initial output from Oracle Business Intelligence is not what we want, we’ll
need to apply some conditional formatting in order to display the indicators
To accomplish this, we first need to add some place holder columns that we can use to display the indicator images. You can just add a second occurrence of each indicator column and rename them so you know which column will contain the text and which will be used to display the actual indicator image.
Next, go to the Schedule Status column, click on the menu drop
down and select Edit Formula.
We don’t want to display the text along with the indicator
image, so select the Custom Headings option, then in place of the actual column
name substitute a blank value(‘ ‘) in the Column Formula section.
Now we can take care of the conditional formatting. For the Schedule
Status column, click on the drop down and select Column Properties.
Then go to the Conditional Format tab, click Add Condition,
and select the column you want to base the formatting on, in this case Schedule
Select the condition and click OK. From the Edit Format
window click on Image.
Select an image to be displayed based on the Schedule Status
Text, click OK.
Enter any additional format changes, in this case we’ve
selected Center horizontal and vertical alignment for the column, then click
Repeat the conditional formatting steps for the other values of the indicator, and then repeat the process for any other indicators in the analysis, in this example we also selected Overall Status.
Once finished, the only remaining step is to hide the text
columns from the analysis so only the indicators will be displayed. From the
Results tab, right-click on the heading for the text columns and select Hide
Column from the drop down list.
Tuesday Apr 22, 2014
By Jeffrey Mcdaniel-Oracle on Apr 22, 2014
To help control this problem a new web configuration utility was created in P6 Reporting Database and P6 Analytics 3.3. Now there is a queuing mechanism to prevent ETL's from running at the same time.
You can setup separate tabs for each ETL. Define the schedule for each ETL. They will then queue up and be displayed on the home tab where the running and queued ETL's will show. They can also be Stopped or Removed from the queue. The main take away is for multiple data source environments the ETL's are sequential not parallel.
Monday Apr 07, 2014
By Jeffrey Mcdaniel-Oracle on Apr 07, 2014
To accommodate multiple data sources for codes and udfs requires a little coordination. Let's say you have 10 codes from your 1st data source and 10 codes from your 2nd data source that you would like to be used in P6 Analytics in OBI. Run the configuration utility for data source 1, choose your 10 codes using slots 1-10. Go to your \res folder and make a copy of the staretl.properties and save it to a different location (ds1staretl.properties). We're going to come back later to use this staretl.properties file for data source 1. Now for data source 2 lets go ahead and log into the configuration utility. Choose your codes, 1-10 don't really matter but choose codes 11-20 as the ones you want to represent this data source in OBI. Make a copy of this staretl.properties and save in a different location (ds2staretl.properties). Your are saving these backups so you can easily rebuild the codes list at a later time if runSubstitution or configuration utility are executed.
If you have a scenario where you have the same codes in data source 1 and data source 2 then this process is much easier. You would need to make the 'master copy' in just one of the data sources and then add it to the other properties files. If the data sources are truly unique and there are codes that don't exist in one of the other data sources you must follow the steps above.Do not worry about when the ETL process runs for data source 1 that it might not have the codes for data source 2 that are now defined in the properties file. This is adding it into the staging tables and mappings for OBI to use for the data associated with data source 2. When you try to add this code along with data from data source 1 it will not return any results just like any other project or activity that is not associated with a chosen code.
Wednesday Mar 26, 2014
By Shawn Lafferty-Oracle on Mar 26, 2014
An effort was made to explain in detail how information flows from P6 into P6 Analytics, specifically the Primavera - Burn Down Subject Area within Oracle Business Intelligence. The Primavera - Burn Down subject area captures data at a specific point in time (user defined), then uses that point in time capture to compare how a project should progress over time if everything goes "according to plan". P6 Analytics has the ability to capture which activities are progressing according to plan and which ones are ahead or behind schedule by comparison to the original point in time capture of the project. The Primavera - Burn Down Subject Area captures units and costs, as well as activity status counts (Not Started, In Progress, Completed, etc...).
For details on the exact measures that P6 Analytics displays in Oracle Business Intelligence, and how those measures are calculated and stored, we have created three new whitepapers. The three whitepapers detail how units and activity counts are calculated and stored on a daily basis. In addition, we have a whitepaper that details how the overall flow of data moves through the data capture process (ETL), and what the expected results will be in Oracle Business Intelligence within the Primavera - Burn Down Subject Area of P6 Analytics.
To download the three New whitepapers, follow the links below:
Monday Mar 17, 2014
By Jeffrey Mcdaniel-Oracle on Mar 17, 2014
In the STAR schema is not the only place these wid's are used. They are also used in the RPD for joining between dimensions and facts. This way if in a multiple data source environment the wid's make sure the data being returned in OBI is also correct and unique to that data source. If doing manual manipulation of the RPD be aware that wid's may be the field you want to join on. Consider your environment, it's needs, and it's future - do you foresee an expansion with more than one data source - if so, plan ahead.
Monday Feb 24, 2014
By Jeffrey Mcdaniel-Oracle on Feb 24, 2014
Wednesday Feb 19, 2014
By Jeffrey Mcdaniel-Oracle on Feb 19, 2014
Wednesday Jan 22, 2014
By Jeffrey Mcdaniel-Oracle on Jan 22, 2014
Thursday Jan 09, 2014
By Jeffrey Mcdaniel-Oracle on Jan 09, 2014
Provide new information on Primavera Analytics and Data Warehouse
- Upgrading Older Analytics\Data Warehouse Versions
- Parallel Loading
- Spreads in Primavera Analytics
- Having Trouble Publishing Projects?
- When Configuring Multiple Data Sources...
- I Created an ETL Schedule Through the Web Configuration, How Do I turn the Schedule Off?
- Summary Data and the Summarizer, What is Needed for P6 Analytics?
- Capturing Historical Financial Periods for Analytics
- How Could I Get a Project to Publish After a Certain Amount of Activity Code Changes?
- Why Aren't My Code Changes Being Reflected in Analytics?