Preparing the Data Environment for PS Cloud Analytics
To ensure that PSA data displays correctly in PS Cloud Analytics, you must complete the following setup steps in your PSA data environment.
Objects Required by the PS Cloud Analytics Dataflow
The PS Cloud Core Analytics dataflow requires data from several PSA-related objects. To avoid conflicts, we recommend you have at least one record for each of the following objects in your PSA environment before you create your PS Cloud Core Analytics app.
Key
Y = Yes
N = No
| Object | Optional | Package | Further Information |
|---|---|---|---|
| Assignment | Y | PSA | Required to populate the Resourcing Adjacencies dataset. |
| Account | N | PSA | |
| Backlog Calculation | Y | PSA | |
| Backlog Detail | Y | PSA | |
| Backlog Detail Converted | Y | PSA | |
| Budget | N | PSA | |
| Est vs Actuals | N | PSA | |
| Expense | N | PSA | |
| Group | Y | PSA | Required to populate the Resourcing Adjacencies dataset. |
| Milestone | N | PSA | |
| Miscellaneous Adjustment | N | PSA | |
| Opportunity | N | PSA | |
| Practice | Y | PSA | Required to populate the Resourcing Adjacencies dataset. |
| Project | N | PSA | |
| Region | Y | PSA | Required to populate the Resourcing Adjacencies dataset. |
| Resource (Contact) | N | PSA | |
| Resource Request | Y | PSA | Required to populate the Resourcing Adjacencies dataset. |
| Resource Skill Request | Y | PSA | |
| Skill | N | PSA | |
| Time Period | N | PSA | When configuring your time periods in PSA, you must specify weeks, months, quarters and years. |
| Timecard | N | PSA | |
| Transaction | N | PSA | |
| User | N | PSA | |
| Utilization Calculation | Y | PSA | You must have utilization data available in either the Utilization Results object OR Utilization Details/Utilization Summary object. |
| Utilization Detail | Y | PSA | You must have utilization data available in either the Utilization Results object OR Utilization Details/Utilization Summary object. |
| Utilization Summary | Y | PSA | You must have utilization data available in either the Utilization Results object OR Utilization Details/Utilization Summary object. |
| Project Actuals Converted | Y | PSA | Required to use the Total Project Margin (Workspace) dashboards, which is optional to PS Cloud Analytics. |
| Revenue Forecast Type | Y | PSA | Required to use the PSA Revenue Forecast dashboard, which are optional to PS Cloud Analytics. |
| Revenue Forecast | Y | PSA | Required to use the PSA Revenue Forecast dashboard, which are optional to PS Cloud Analytics. |
| Revenue Forecast Version | Y | PSA | Required to use the PSA Revenue Forecast dashboard, which are optional to PS Cloud Analytics. |
| Revenue Forecast Version Detail | Y | PSA | Required to use the PSA Revenue Forecast dashboard, which are optional to PS Cloud Analytics. |
| Utilization Result | Y | PSA | Required to use the PSA Utilization Analytics dashboard, which is optional to PS Cloud Core Analytics. |
| Estimate | Y | Services Estimator | |
| Estimate Task | Y | Services Estimator | |
| Estimate Role Request | Y | Services Estimator |
Custom Settings Used by PS Cloud Core Analytics
To perform the necessary calculations to the data held in the Utilization Detail and Utilization Summary objects used by PS Cloud Core Analytics, ensure that the following PSA custom settings are enabled.
- Calculate Summary By Role
For more information, see Utilization Settings.
RPG Hierarchies in PS Cloud Core Analytics
If the RPG hierarchy in your PSA data environment is less than 12 levels deep, then the dataflow removes any surplus hierarchy levels from the datasets listed below. If you subsequently add further levels to your source data, you must reconfigure your PS Cloud Core Analytics app to see data for these additional levels displayed in your lenses and dashboards.
- Backlog
- Billings
- Capacity
- Project Reporting
- Revenue Forecast
- Utilization
- Utilization Results
Revenue Forecast User Permission Controls
If required, you can apply user permission controls set for your revenue forecast data in PSA, to filter the revenue forecast data displayed in the Revenue Forecast dataset and dashboard. For more information on this feature, see Revenue Forecast Flow Intermediate Processing.
In order to use this feature, you must have at least one revenue forecast setup record in your PSA data environment with the following options selected:
- Active
- Respect Permission Controls
Skills / Certification Ratings
In order to display a skill in the PSA Skills Capacity and Demand Planning dashboard, you must have at least one resource with a skill / certification rating of zero or higher in your PSA data environment for this skill. For more information, see Managing Skills, Certifications, and Experience for Resources.
Preparing the Utilization Calculations Used by PS Cloud Core Analytics
To enable the creation of your PS Cloud Core Analytics app, you must setup at least one utilization calculation in PSA.
Preparing the Utilization Calculations
To configure the Utilization calculation, see Calculating Utilization.
Preparing the Utilization Analytics Calculations
To configure the Utilization Analytics calculation, see Setting up Utilization Analytics.
Preparing the Data Required by Additional Features
If you want to enable additional features in PS Cloud Analytics, such as the Total Project Margin (Workspace) or the PSA Revenue Forecast dashboards, ensure you apply the necessary data preparation steps to the org before you create or upgrade your app.
Preparing the Data for the Backlog Dataset
To display the backlog data, PS Cloud Core Analytics uses the most recent backlog calculation available. In order to display your information correctly, PS Cloud Core Analytics requires you to create the backlog calculation in PSA as specified below:
- Ensure the checkbox Calculate Project Backlog is selected.
- In order to display the latest data in PS Cloud Analytics, we recommend you select the most recent date as the start date for the calculation.
- Ensure you have set up alternate backlog currencies in your org. PS Cloud Core Analytics requires that Backlog Details Converted records exist in your org's environment.
Setting up Alternate Backlog Currencies
- From Setup, navigate to Custom Code | Custom Settings.
- Click Backlog | Manage | Edit.
- In the Backlog Details Corporate Currencies field, enter your preferred reporting currency.
- Click Save.
For more information on working with Backlog, see Setting Alternate Backlog Currencies.
Preparing the Data for the Revenue Forecast Dataset
This dataset requires PSA Winter 2021 or later. This is due to a dependency on the PSA Opportunity Probability (%) field on the Revenue Forecast Version Detail object required for this dataset. In addition, you must have one or more records on the Revenue Forecast or Revenue Forecast Version objects in your PSA data environment.
Preparing the Data for Forecasts
PS Cloud Core Analytics Forecasts requires data from PSA Revenue Forecasting.
- Ensure you have installed a version of PSA that supports forecasting. It is recommended that PSA users adopt Revenue Forecasting as their forecasting solution. For more information, see About Forecasting.
- Ensure your data environment has at least one successful forecast calculation created and that you select the Current checkbox for this calculation.
- Ensure the associated forecast records for the calculation exist before running the dataflow.
For more information on running forecasts, see the PSA Help.
Preparing the Data for Project Margin
The following steps are necessary in order to run the PS Cloud Core Analytics dataflow with Project Margin enabled:
- Ensure that your org corporate currency matches the integration user currency. This is the currency displayed in all Analytics data.
- Add the corporate currency ISO code as a configuration value to the ProjectConvertionCurrencies configuration option in PSA.
- Ensure your org contains project actual converted records for the currency that matches your integration user currency. For more information on how to create converted records, see Recalculating Resource and Project Actuals.
- By default the parameter ignoreLast is enabled in the Total Project Margin (Workspace) dashboard. To prevent display errors, we recommend you generate project actual converted records for the current month even if the month is starting.
Preparing the Data for Resourcing Adjacencies
This dataset requires that you have the following data in your PSA environment:
- Assignments related to a resource request.
-
One or more of the following fields populated on the related resource request:
- Resource Role
- Region
- Practice
- Group
- One or more resource skill requests associated with the related resource request.