Publishing Unifier Data to Analytics
You must send Unifier data to Analytics periodically on an incremental basis. To send data to analytics, you will need to:
- Publish Unifier data to staging tables
- Run ETL Using the Primavera Analytics Administration Web Application to send data to the STAR schema of Primavera Data Warehouse.
For more details on how to use the Primavera Analytics Administration Web Application, see the Primavera Analytics Cloud Service Administration Guide.
You can set the frequency of sending data to Analytics to Oracle Business Intelligence (OBI), by using the Schedule option in the toolbar.
Note: If you need location-specific details for Spatial Data in Analytics, ensure that the values for Country and State Data Elements (DEs) are according to the ISO standards. These values can be pulldowns or plain text fields.
Schedule Setup
The frequency for the data publication can be Daily, Weekly or None. The default value is Daily.
You can set the frequency to Every __ hours, Daily, Weekly, or None.
The default frequency is Daily.
If you select Weekly, the system sets the day to Sunday. You can change the day.
If you select None, there will be no periodic publication of Unifier data to Analytics.
You can set the time for the publication of data.
You must set the time format to 24-hour notation in the form hh:mm, for the publication of data. The Hour drop-down lists hours from 0 to 23 for hour and 0 to 59 for minute. The default option for time is set to 00:00. The system displays the server time zone after the minute.
You must select the check box for the Data Refresh option if you made changes to the DD value or labels. By default, the check box is unchecked.
You must select the check box for the Data Refresh option if you made changes to the data mapping fields. After the run is complete, the system resets the check box for the Data Refresh option and the check box will be unchecked.
Mapping Linked Elements
The linked elements can be mapped to Analytics fields. The values of linked elements from the source are rendered at run-time in the destination record. However, if there are any changes to the value of the linked elements in the source record, then you need to conduct a full refresh of data in order for Analytics to display these values. As a result, you must select Refresh All data for this purpose.
Run History
The Run History option allows you to see the status of the scheduled runs of the Unifier data publication to the Analytics server. When you select the Run History option, by clicking Run History on the toolbar, the Run History window opens and displays the following information:
- Requestor: Is always "System"
- Submit Date: The date entered by user
- Start Date: The date entered by user
- End Date: The date entered by user
- Status: The run status
You can view the Run History details by opening a record in the Run History log.
The history details window includes the Start Date, End Date, and a message.
- Success message: Data was sent to Analytics, successfully.
- Failure message: For example, An error occurred and data was not published to Analytics successfully. Contact System Administrator. The system then displays the actual error after the generic failure message.
See Also
Unifier and Primavera Analytics
Analytics Log (Business Process) Setup
Analytics Log (Cash Flow) Setup
Analytics Log (Cost Sheet) Setup
Analytics Log (Generic Cost Sheet) Setup
Analytics Log (P6 Summary Sheets)
Access Control Changes for Analytics Node in User Mode Access
Analytics Subject Areas and Unifier Data
Granting Permissions to Set Up Analytics
Accessing the Unifier Analytics Dashboard in OBI
Accessing Unifier from OBI server
Action Links (from OBI to Unifier)
Accessing Analytics from Unifier
Unifier Configurator and OBI Server for On-Premises
Analytics Block and Shell Templates
Last Published Friday, June 21, 2024