Advanced Reporting with Jaspersoft

Learn more about advanced reporting with Jaspersoft to create ad hoc views of
Clarity
data.
ccppmop1593
HID_reporting_top_page
Learn about
Clarity
Advanced Reporting with Jaspersoft, reporting best practices, and the Jaspersoft Community. Advanced Reporting with Jaspersoft allows you to create ad hoc views of
Clarity
 data. You can save the information as a report, display a dashboard, or share it using different formats. You configure each ad hoc view and its corresponding report by selecting the data that you want to include. You can run a report immediately or you can set up a recurring schedule. In either case, you control the output method and delivery format.
2
New! Getting Started with Jaspersoft 7.8
Clarity
15.9.1 and higher release now support Jaspersoft 7.8. Clarity 15.9.1 also supports Jaspersoft 7.1.3.
When you plan to install Jaspersoft 7.8, some of the key things you need to remember are:
  • You need to be on Clarity 15.9.1 and Jaspersoft 7.1.3 to upgrade to Jaspersoft 7.8.
  • Jaspersoft 7.8.0 includes an installation keystore. Create a backup of the installation keystore (<user.home.dir>/.jrsks & <user.home.dir>/.jrsksp) to ensure you can connect to the Jaspersoft database in case of any issues. You will not be able to access your data if you don't have a copy of the keystore files. If you are using a Windows server, the keystores are available under C:\users\<user directory>.
  • Jaspersoft 7.8.0 now supports TCPS for the Oracle 19c database. Customers who wish to upgrade to Jaspersoft 7.8.0 and switch to TCPS would need to install Jaspersoft 7.8.0 on Oracle 19c. They can then import content from their current Jaspersoft instance.
  • Jaspersoft 7.8.0 supports PostgreSQL. You can only use PostgreSQL for Jaspersoft after
    Clarity
    (on-premise) officially supports PostgreSQL (expected in May 2021). You cannot install Jaspersoft on PostgreSQL and configure it to work with
    Clarity
    in scenarios where
    Clarity
    uses Oracle or MSSQL database. 
  • Jaspersoft 7.8.0 also supports Microsoft SQL Server 2017 and Microsoft SQL Server 2019.
  • Jaspersoft 7.8.0 supports the Adopt Open JDK 11 and Tomcat 9.0.37.
  • Jaspersoft 7.8.0 requires you to install Chrome 85 or higher release on the server where you plan to install Jaspersoft.
  • When you export content from Jaspersoft 7.8.0, use the Legacy Key option to ensure you can import content on all existing Jaspersoft servers.
  • Jaspersoft 7.8 will not work on Internet Explorer. You can use the relevant versions of Chrome, Firefox, and Edge.
Additional Resources
Available from TIBCO:
What's New in Jaspersoft Version 7.8 for
Classic PPM
?
  • Usability improvements in UI with a new brighter color, bigger collapsible menu button, and new icons.
  • PhantomJS has been deprecated and replaced with Chrome engine, which is used to render any HTML 5 or fusion charts based reports and dashboard
  • Support for Oracle 19c, SQL Server 2019, and OpenJDK 11
  • Domain schema syntax has been updated for better management
  • New key management mechanism used for enhanced security
  • Support for TCPS protocol for SSL communication with Oracle JDBC driver only
  • Jaspersoft Studio 7.9 with several enhancements
If you are implementing a custom REST API integration with Jaspersoft, and you encounter an issue, remove the | character and use %7c instead. Jaspersoft JRS-11883 notes that some application servers, such as Tomcat, are ending their support of the pipe character (|), which delimits a username and organization when they are passed as a URL to the server. The application server returns an illegal character error for pipe characters. TIBCO examples and documentation now use %7c instead of pipe.
For example, instead of:
  homeFlow&j_username=jasperadmin|organization_1
we now use:
  homeFlow&j_username=jasperadmin%7Corganization_1
Getting Started with Advanced Reporting
Prerequisites
: To manage ad hoc views, reports, and dashboards, your administrator sets up Advanced Reporting for you and grants you access rights.
  • If you do not see the Advanced Reporting menu link in
    Classic PPM
     when you click
    Home
    ,
    Personal
    , contact your administrator.
  • To work with the Advanced Reporting content, install it in your target environment.
  • Verify that your administrator has installed the PMO Accelerator.
Resources
: As a report designer or administrator, review the following resources:
  • : Tutorials and tips.
  • Oracle and SQL Database Performance Whitepapers: To establish performance benchmarks and validate system stability, Broadcom conducted a series of tests for
    Clarity
    . The data warehouse is optimized for reporting and analytics and is on a separate schema from the
    Classic PPM
    database. The data warehouse is populated at scheduled intervals by an ETL job. To help you plan for an upgrade, you can view examples of expected growth rates and loading times which are based on existing database sizes. See the
    Reference
    section of the English edition of the documentation.
  • To help you plan for a new installation or upgrade with Advanced Reporting, refer to the deployment architecture examples in the sizing guide for
    Clarity
    , see Install Jaspersoft 7.8.0
The Load Data Warehouse job determines the freshness of the data in the data warehouse. Running this job with great frequency impacts performance; not running it often enough yields stale data. We recommend that you run this job only once every day during non-peak hours. For more information, see
Jobs Reference
in the English edition of the documentation.
Advanced Reporting Components
The following image shows the Advanced Reporting components:
Image showing the Advanced Reporting components
Image showing the Advanced Reporting components
Clarity
 Data Warehouse
The
Clarity
 data warehouse is the main data source for the advanced reporting features. The data warehouse schema is optimized for reporting. The schema includes the investment, resource, portfolio, timesheet, and project data. The data warehouse is populated at scheduled intervals by jobs that load the relevant data from the application database. The data warehouse can be extended to include custom objects and attributes.
The application provides a set of domains that contains the most common data. When you create an ad hoc view, you select from a list of the available domains. A domain provides a business view of the data warehouse. A domain limits your access to data based on your security permissions. A user who can access specific projects and resources in
Clarity
 can access the same projects and resources in the advanced reporting domains. If you add custom objects or attributes to the product, these custom objects and attributes can also be included in the domains.
To view the domains and reports, you must have the PMO Accelerator add-in installed with the required Jaspersoft Advanced Reporting content.
You create ad hoc views in the form of charts, tables, and crosstabs that let you analyze data from the domains. You can also use ad hoc views to generate and share reports.
Ad Hoc Views and Reports
Advanced Reporting lets you create ad hoc views of your project and portfolio data. You can use the ad hoc views in the following ways:
  • Create a dashboard of multiple related views.
  • Save the views as reports.
  • Export or email the reports as PDF, Word, Excel, PowerPoint, and other file formats
  • Display multiple related reports on a dashboard.
You customize each ad hoc view and report by selecting the domains and fields that you want to include.
The integrated JasperReports Server manages ad hoc views, reports, and dashboards. When you select the Advanced Reporting option from the Home menu, the Advanced Reporting page appears. This page, and all pages that are opened from this page, are based on the Jaspersoft application.
Note:
For information about using Jaspersoft, access the Jaspersoft Community website and click the Documentation link. On the Documentation page, select the version of Jaspersoft that corresponds to your
Clarity
 release. Then click the link for the JasperReports Server User Guide. Refer to the
Classic PPM
 Release Notes
for the Jaspersoft version that corresponds to your release.
Create an Ad Hoc View and Report
Use Advanced Reporting to create ad hoc views and reports by selecting fields from the domains. You can then run the reports or you can place the reports on a dashboard to monitor status and progress.
Follow these steps:
  1. Open Home, and from Personal, click Advanced Reporting.
    The Advanced Reporting page opens. You see links to the different Advanced Reporting functions (in blocks). The functions that you can see and access depend on your user role. The following blocks require explanation:
    • Ad Hoc Views
      Create a limited view of your data that you can use to prepare reports or access a list of existing ad hoc views.
    • Reports
      Create and format reports from existing ad hoc views or access a list of existing reports.
  2. Click the Ad Hoc Views, Create, select a domain, and click Choose Data.
    Click the Ad Hoc Views, View List link to see the existing ad hoc views that you can access.
  3. Select the domain fields that you want to have available for your ad hoc view. Click Table, Chart, or Crosstab (depending on the format that you want).
    We do not recommend that you select all fields in the domain. For best performance, use the following guidelines to create smaller views:
    For the Investment Management, Project Management, Application Management, Idea Management, and Resource Management domains, select one metric set for each view. The metric sets are Summary, Weekly, Calendar, and Fiscal.
    For the Financial Management domain, select one set for each view. The sets are Financial Transaction and Plan Data.
    For the Time Management domain, select one set for each view. The sets are Missing Time and Timesheets.
  4. Create an ad hoc view by selecting fields and measures and adding (dragging) them to the new ad hoc view.
  5. Save the ad hoc view.
    You can save the ad hoc view to the Shared folder. If you save to the Shared folder, other users can access your ad hoc view.
  6. (Optional) Create a report when you save the ad hoc view. Reports allow you to use scheduling and more formatting options.
    The Advanced Reporting features use the JasperReports Server. For information about using Jaspersoft with views, reports, and dashboards, access the Jaspersoft Community website and click the Documentation link. On the Documentation page, select the version of Jaspersoft that corresponds to your
    Classic PPM
     release. Then click the link for the JasperReports Server User Guide. See the
    Classic PPM
     Release Notes
    for the Jaspersoft version that corresponds to your
    Classic PPM
     release.
Run or Schedule an Advanced Report
Advanced Reporting lets you run, schedule, and manage scheduled reports that are based on
Classic PPM
 data. You can schedule reports with different output options (for example, PDF or Excel) and email reports to people that you want to notify.
To run and schedule advanced reports, verify that you meet the following prerequisites. If you do not, contact your administrator.
  • You can see the Advanced Reporting link in the Personal menu under Home.
  • A list of reports exists.
You can run a report immediately or you can schedule it to run at a specific interval and frequency. You can also manage your scheduled reports by monitoring the list of scheduled reports, changing schedules, or deleting schedules.
Your report output cannot exceed 500 pages. This limit applies to each output format that you select. As a best practice, we recommend that you filter the report to limit the output data. Do not use reports to extract large volumes of data.
Follow these steps:
  1. Open
    Home
    , and from
    Personal
    , click
    Advanced Reporting
    .
    The Advanced Reporting page opens. You see links to the different Advanced Reporting functions (in blocks). The functions that you can see and access depend on your user role. The following block requires explanation:
    • Reports
      Create and format reports from existing ad hoc views or access a list of existing reports.
  2. On the
    Reports
    block, click
    View List
    .
    A list of reports to which you have permissions appears.
  3. Run a report immediately by selecting and opening a report and entering values for the Options on the left. Click
    Apply
    .
    The Options act as filters to focus the report on only the data that you want to see.
  4. To schedule a report to run as a job, right-click the report name and select
    Schedule
    . Click
    Create Schedule
    . The New Schedule page opens with the Schedule tab selected.
    1. Select a schedule definition using a Simple or Calendar recurrence schedule.
    2. Select parameters, which are similar to the report filter options.
    3. Select output options (for example, PDF, Excel, and PowerPoint) and distribution methods. You can also specify a locale. When the scheduled report runs, the report is presented in the specified language.
      Formats
      Select a maximum of two options (for example, Powerpoint and Word, or PDF and Excel).
      Output to Repository
      Browse to select the Shared folder (or a subfolder) or your own user folder (under Users). If you save to the Shared folder, other users can access your report. Only you can access the report if you save to your own user folder.
      Output to Repository Examples:
      • /shared/reports
      • /users/
        username
      We do not recommend that you save your report to the
      Clarity
       folder or any of its subfolders. These folders are overwritten during a system upgrade, and your reports are then lost.
    4. Select the notifications that you want to send when the scheduler runs. The notifications can include the report as an email attachment.
      Email Notification To, CC, or BCC
      Enter email addresses, up to a maximum of 100 characters.  If you are sending the report to a large number of users, separate email addresses with commas. You can also enter email aliases, which we recommend.
  5. Click
    Save
    .
  6. Manage your scheduled reports by changing or deleting the scheduled jobs.
Recently Viewed Items and Modified Items
Access events are enabled for a maximum of seven days. As an Advanced Reporting user, you can see the recently viewed items and the modified items from the following locations:
  • Recently Viewed Items
    section on the Advanced Reporting Home page
  • Modified by me
    section under Advanced Reporting Home, View, Search Results
The items appear for up to seven days from the date you accessed or modified the reporting item. Say you modify the Application Assessment Analysis report today, then the report appears under the Modified by me items for the next seven days starting today. On the eighth day, the report no longer appears under Recently Viewed Items.
Task Data in the Data Warehouse
Beginning with Release 15.4, the data warehouse began including fields for tasks, phases, and milestones as seen on the new project task board. The stored data includes field names, task board values, columns, colors, task card position and color, and to-do items. You can develop reports on the following new data warehouse task board tables:
  • DWH_INV_BOARD
    : This table stores each task board as a row. The table includes a relationship back to the linked parent object.
  • DWH_INV_BOARD_LANE
    : This table stores every lane (column) on the board. Attributes include the lane level, position (sequence), and orientation.
  • DWH_INV_BOARD_CARD
    : This table stores basic data about every task card on the board. Attributes include the card color and position (sequence).
The Task Owner field also appears in its own column in the dwh_inv_task table.
Roadmap Data in the Data Warehouse
Release 15.4 also added thirteen (13) new tables in the data warehouse to support the new Roadmapping features:
DWH_CMN_SCENARIO DWH_LKP_ROADMAP_STATUS
DWH_CMN_SCENARIO_FACTS DWH_LKP_ROADMAP_TYPE
DWH_RDM_ROADMAP DWH_LKP_RDM_MUST_HAVE
DWH_RDM_ROADMAP_LN
DWH_RDM_PICKLIST
DWH_RDM_PICKLIST_LN
DWH_RDM_ROADMAP_ITEM
DWH_RDM_ROADMAP_ITEM_LN
DWH_RDM_ITEM_POSITION
DWH_RDM_ITEM_SUMMARY_FACTS
The following calculated attributes for the Roadmap Item object are also included:
  • Remaining Capacity = Capacity − Actual Capacity
  • Remaining Capital Cost = Capital Cost − Actual Capital Cost
  • Remaining Operating Cost = Operating Cost − Actual Operating Cost
  • Total Actual Cost = Actual Capital Cost + Actual Operating Cost
  • Total Cost = Capital Cost + Operating Cost
  • Total Remaining Cost = Total Cost − Total Actual Cost
Resource Team Data in the Data Warehouse
Release 15.5.1 added two (2) more tables in the data warehouse for the Team object:
   DWH_INV_TEAM_DEF    DWH_INV_TEAM_MEMBER
The following section summarizes these changes:
DWH_CMN_SCENARIO:
  • One row for every scenario
image2018-9-26_15-46-22.png
DWH_CMN_SCENARIO_FACTS:
  • Contains summary level facts
  • One row for every fact type for a scenario target or goal
image2018-9-26_15-47-41.png
DWH_RDM_ROADMAP
:
  • One row for every roadmap
image2018-9-26_15-49-47.png
DWH_RDM_ROADMAP_LN
  • One row for each roadmap and language
image2018-9-26_15-50-6.png
DWH_RDM_PICKLIST
  • One row for each value in a roadmap picklist
image2018-9-26_15-50-32.png
DWH_RDM_PICKLIST_LN
  • One row for each roadmap picklist value and language
image2018-9-26_15-50-46.png
DWH_RDM_ROADMAP_ITEM
  • One row for each roadmap item
image2018-9-26_15-51-18.png
DWH_RDM_ROADMAP_ITEM_LN
  • One row for each roadmap item and language
image2018-9-26_15-51-23.png
DWH_RDM_ITEM_SUMMARY_FACTS
  • Contains summary level facts
  • One row for each roadmap item
image2018-9-26_15-51-40.png
DWH_RDM_ITEM_POSITION
  • For roadmap items, stores each picklist, the selected picklist value, and position
image2018-9-26_15-51-58.png
DWH_LKP_ROADMAP_STATUS
  • Lookup table for roadmap status
  • One row for each roadmap status and language
image2018-9-26_15-52-29.png
DWH_LKP_ROADMAP_TYPE
  • Lookup table for roadmap types
  • One row for each roadmap type and language
image2018-9-26_15-52-35.png
DWH_LKP_RDM_MUST_HAVE:
  • Lookup table for roadmap
    must haves
  • One row for each roadmap must-have and language
image2018-9-26_15-52-44.png
Two (2) New Tables in the Data Warehouse for the Team object in 15.5.1:
image2018-11-20_16-9-35.png
In 15.5.1, we added 2 new columns to the
DWH_RES_RESOURCE
dimension table :
  • TEAM_DEF_KEY
  • IS_TEAM
This table contains one row for each resource, including a team resource.
image2018-11-20_16-18-38.png
Advanced Reporting Domains
Classic PPM
 provides a set of domains that contains the most frequently used product data. A domain provides a business view of the
Clarity
 data warehouse. You select a domain from the ad hoc viewer when you build your ad hoc views. A domain limits your access to data based on your security permissions.
The domain fields are organized into sets and items. The sets act like folders that you can expand to view the items. Some examples of domain sets include the General and the OBS sets. For descriptions of the domain fields, see the Advanced Reporting and Database Schema Index page.
Custom attributes are listed and are viewable if they are enabled for the data warehouse. Each domain has its own custom attributes.
We do not recommend that you change the domains that are provided with the product. To modify a product-provided domain, copy the domain, place it in another location in the repository, and make your changes in the copied version. However, the dynamic domain updates that
Clarity
 performs are not reflected in your copied versions. We recommend that you request enhancements to the product domains, instead of making these changes yourself.
4
4
Domain Terminology
The following terms are commonly used with the domain descriptions:
Sets and Items.
The domains are organized into sets and items. The sets act like folders that you can expand and view the items. Some examples of domain sets include the General and the OBS sets. Items include fields and measures.
Fields.
Items that display qualitative information, such as name or location, are fields.
Measures.
Items that display numeric values or aggregate values are measures. Measures are the quantitative values of a record, such as an amount. In domains, all items that are based on numeric fields are designated as measures. The items in Measures are numeric fields or items for which you can do mathematical calculations.
Ad Hoc Viewer and Editor.
The Ad Hoc viewer and editor is the interactive designer for viewing, creating, and editing an ad hoc view. With an ad hoc view, you can explore and analyze data. Ad hoc views can also be used to create content for reports.
Common Characteristics of Advanced Reporting Domains
The following major characteristics apply to all Advanced Reporting domains. See the descriptions of the individual domains for information that is domain-specific.
  • Object Domains.
    Domains are provided for the most frequently used objects, including the new product investment objects (NPIOs), such as Ideas and Applications. In each domain, you can see only the product data that you have permission to view.
    When viewing a domain in the ad hoc editor, the Fields section of the left panel lists all field properties (such as Investment names, OBS, text fields, and dates). The Measures section of the left panel lists all numeric amounts that are related to the fields (such as hours and costs). The items in Measures are fields for which you can do mathematical calculations.
  • Internal IDs.
    Each domain contains an Internal ID set. You use internal IDs for building dashboards. Internal IDs are primarily used as filters by report developers and dashboard developers. These IDs, which are not used in ad hoc views, are the same across all domains. You can map these IDs to input controls and you can use them for filtering on dashboards.
    Internal IDs are related to objects, not domains. If Investment data exists in multiple domains, the same Investment key is available in each domain.
    Dashboards are not provided with
    Classic PPM
    . See the Jaspersoft documentation for information about how to build dashboards.
  • Custom Folder.
    The Custom folder appears in a domain if you have custom fields or objects (related to the domain objects) that are data warehouse enabled. To verify that your custom fields and objects are data warehouse enabled, see your administrator. The Custom folders also include add-in fields. The Custom folder always appears as the first set under each object (after the list of object fields). If you have multiple objects in a domain, the Custom folder appears under each object folder. For example, the Team object includes its own custom team fields in a Custom folder under the Team folder.
    If you add custom fields to an object (or if you install an add-in with custom fields) and the fields are data warehouse enabled, custom sets are created in the corresponding domains. The custom fields are included in the Custom sets under the related object.
    If a custom object or subobject has a lookup attribute, the key for it is included in the Internal IDs folder under the Custom folder.
  • Period Type:
    When you select period types, select the same period type for both Fields (top of the left panel on Advanced Reporting page) and Measures (bottom of left panel). Selecting different period types for Fields and Measures can produce unexpected results.
  • Domain Sets:
    Domains are organized into sets and field items. The sets act like folders that you can expand to view the field items. Some examples of sets are the General and the OBS sets.
  • Domain Security:
    You have access to specific domains based on your role. When you open Advanced Reporting, you see only the domains that you can access. However, you may not have access to all data in the domains that you can access. When you view a domain that you can access, you see all object sets and fields in that domain. However, the data that appears for the objects and fields depends on your access rights.
  • Date Fields
    :
    Most of the dates in the domains are business dates that are displayed without timestamps and time zone conversions. The exceptions are the system dates, which display date and time and have time zone conversions applied to them. The system dates include Created Date, Last Updated Date, and Warehouse Updated Date.
  • PMO Accelerator Fields:
    The PMO Accelerator fields are dynamically included in the domains (similar to custom attributes). However, the internal IDs of the PMO Accelerator fields are renamed when they are included in the data warehouse and the domains. The renaming of the internal IDs occurs only for PMO Accelerator fields. All other add-in fields have the same behavior as the custom attributes.
Investment Management Domain
The Investment Management domain includes information about investments (for all investment types) and their corresponding teams. This domain-only includes information that is common to all investment types. For example, no information about assignments is included.
The Investment Management domain includes financial summary data for Investments, but not detailed financial planning or actual transaction data. The detailed financial planning and actual transaction data is included in the Financial Management domain.
Custom fields that you add to the Investment object in
Classic PPM
 appear in the Investment Management domain (in the Custom set under the Investment set). If you add custom fields to the Team object in
Classic PPM
, those fields appear in the Investment Management domain, Custom set under the Team set.
Custom subobjects that you add to the Investment object appear under the Custom set in their own subobject folder (set), for example, “Country”. The name of the subobject set is the same as the subobject name.
The Investment Management domain contains two main types of data: investment-level financial data (summarized for the total Investment and divided into periods) and team data (at the team level and by calendar periods). The domain has general information, financial information, OBS information, and team information for all team members in an investment.
The Investment Management domain does not have detailed Cost Plan or actual transaction detail data. See the Financial Management domain for that information.
Data security
. Data security is determined by investment-level access rights. If you have rights to view an investment in
Classic PPM
, then you see all data that is related to that investment in this domain. You can also view all subobject data that is enabled for the data warehouse.
Do not mix object types
when selecting from Fields and Measures. If you select Investment Name in the Fields area, select a total under the Investment Totals in the Measures area. Selecting a total from a different Measures object category (for example, Team Totals) could produce unexpected results. For Investment data, use investment fields and investment measures. To use Team data when creating an ad hoc view, select a team member field from the Team folder under Fields. Use a team amount from the Team folder under Measures. In general, use Investment data (Fields) with Investment metrics (Measures) and use Team data (Fields) with Team metrics (Measures).
Use Team data when you want specific data about a team and its members (for example, resources or allocation start dates).
Do not mix calendar types.
When you look at periodic data (for example, monthly data), do not mix calendar types when making ad hoc view selections. For example, use calendar period measures (Measures section, left panel) for calendar period fields (Fields section, left panel). Use fiscal period measures (Measures section) for fiscal period fields (Fields section). Also, do not mix the period types (week, calendar, fiscal). Otherwise, you get unexpected results because the data is repeated for each period type.
Portfolios.
The Investment Management domain includes portfolios (contents and properties). You can use the portfolios to filter and group the investment data by portfolio when building ad hoc views.
For example, you created a portfolio in
Classic PPM
 with 100 investments. In the Investment Management domain, you add Investment Name to the ad-hoc view (drag Investment Name from Fields to Columns in the New Ad Hoc View). Then drag Portfolio Name (from Fields) to the Filters, select the portfolio (that you created with 100 investments) from the drop-down, and click Apply. The ad hoc view now only shows the 100 investments in that selected portfolio. In this way, you are using Portfolios as a filtering method of reporting on your investment data.
You can also group your data by portfolio in the Investment Management domain. For example, you want to see the Total EAC Hours for the investments in each portfolio. You add (drag) Investment Name from the Fields area to Columns in the New Ad Hoc View. Then you drag Total EAC Hours from the Investment Totals in the Measures area to Columns in the New Ad Hoc View. Then you add Portfolio Name (from Fields) to Groups in the New Ad Hoc View. Your data is shown organized by portfolio in the format you selected (table, chart, pie diagram).
In the Investment Management domain, you are working with actual up-to-date investment data. You are not using the portfolio investment snapshot of the data that you use during portfolio planning in
Classic PPM
. Portfolio planning uses a copy of the actual investment data. Therefore, the Investment Management domain data does not match the data in the
Classic PPM
 portfolios that you use for portfolio planning. For more information about portfolio planning, see
Portfolio Management
Custom Fields.
If you have custom fields that are related to investments, these fields appear in a Custom folder in the Investment Management domain. This domain can have multiple Custom folders. For example, Team custom fields appear in the Team Custom folder.
Application Management Domain
The Application Management domain contains information about the investments, teams, and financials that are related to applications. Items that apply only to applications are included in this domain.
The Application Management domain contains two main types of data: investment-level financial data (summarized for the total Investment and divided into periods) and team data (at the team level and by calendar periods). The domain has general information, financial information, OBS information, and team information for all team members in an investment.
The Application Management domain does not have detailed Cost Plan or actual transaction detail data. See the Financial Management domain for that information.
Data security
. Data security is determined by application-level access rights. If you have rights to view an application in
Classic PPM
, then you see all data that is related to that application in this domain, including all subobject data that is enabled for the data warehouse.
Do not mix object types
when selecting from Fields and Measures. If you select Investment Name in the Fields area, select a total under the Investment Totals in the Measures area. Selecting a total from a different Measures object category (for example, Team Totals) could produce unexpected results. For Investment data, use investment fields and investment measures. To use Team data when creating an ad hoc view, select a team member field from the Team folder under Fields. Use a team amount from the Team folder under Measures. In general, use Investment data (Fields) with Investment metrics (Measures) and use Team data (Fields) with Team metrics (Measures).
Use Team data when you want specific data about a team and its members (for example, resources or allocation start dates). However, for Baseline hours, do not use Team data. You can find total Baseline hours summed under Investment data.
Do not mix calendar types.
When you look at periodic data (for example, monthly data), do not mix calendar types when making ad hoc view selections. For example, use calendar period measures (Measures section) for calendar period fields (Fields area) and use fiscal period measures (Measures area) for fiscal period fields (Fields section). Also, do not mix the period types (week, calendar, fiscal). Otherwise, you get unexpected results because the data is repeated for each period type.
Portfolios.
The Application Management domain includes portfolios (contents and properties). You can use the portfolios to filter and group the investment data by portfolio when building ad hoc views.
In the Application Management domain, you are working with your actual up-to-date investment data (not a copy of the data as you use when doing portfolio planning in
Classic PPM
).
For example, you created a portfolio in
Classic PPM
 with 100 investments. In the Application Management domain, you add Investment Name to the ad-hoc view (drag Investment Name from Fields to Columns in the New Ad Hoc View). Then drag Portfolio Name (from Fields) to the Filters, select the portfolio (that you created with 100 investments) from the drop-down, and click Apply. The ad hoc view now only shows the 100 investments in that selected portfolio. In this way, you are using Portfolios as a filtering method of reporting on your investment data.
You can also group your data by portfolio in the Application Management domain. For example, you want to see the Total EAC Hours for the investments in each portfolio. You add (drag) Investment Name from the Fields area to Columns in the New Ad Hoc View. Then you drag Total EAC Hours from the Investment Totals in the Measures area to Columns in the New Ad Hoc View. Then you add Portfolio Name (from Fields) to Groups in the New Ad Hoc View. Your data is shown organized by portfolio in the format you selected (table, chart, pie diagram).
In the Application Management domain, you are working with actual up-to-date investment data. You are not using a copy of the data as you use during portfolio planning in
Classic PPM
. Therefore, the Application Management domain data does not match the data in the
Classic PPM
 portfolios that you use for portfolio planning. Portfolio planning uses a copy of the actual investment data.
Custom Fields.
If you have custom fields that are related to applications, these fields appear in a Custom folder in the Application Management domain. This domain can have multiple Custom folders. For example, Team custom fields appear in the Team Custom folder.
Idea Management Domain
The Idea Management domain contains information about the investments, teams, and financials that are related to Ideas. Fields that apply only to ideas are included in this domain.
The Idea Management domain contains two main types of data: investment-level financial data (summarized for the total Investment and divided into periods) and team data (at the team level and by calendar periods). The domain has general information, financial information, OBS information, and team information for all team members in an investment.
The Idea Management domain does not have detailed Cost Plan or actual transaction detail data. See the Financial Management domain for that information.
Data security
. Data security is determined by idea-level access rights. If you have rights to view an idea in
Classic PPM
, then you see all data that is related to that idea in this domain, including all subobject data that is enabled for the data warehouse.
Do not mix object types
when selecting from Fields and Measures. If you select Investment Name in the Fields area, select a total under the Investment Totals in the Measures area. Selecting a total from a different Measures object category (for example, Team Totals) could produce unexpected results. For Investment data, use investment fields and investment measures. To use Team data when creating an ad hoc view, select a team member field from the Team folder under Fields. Use a team amount from the Team folder under Measures. In general, use Investment data (Fields) with Investment metrics (Measures) and use Team data (Fields) with Team metrics (Measures).
Use Team data when you want specific data about a team and its members (for example, resources or allocation start dates). However, for Baseline hours, do not use Team data. You can find total Baseline hours summed under Investment data.
Do not mix calendar types.
When you look at periodic data (for example, monthly data), do not mix calendar types when making ad hoc view selections. For example, use calendar period measures (Measures area) for calendar period fields (Fields area) and use fiscal period measures (Measures section) for fiscal period fields (Fields section). Also, do not mix the period types (week, calendar, fiscal). Otherwise, you get unexpected results because the data is repeated for each period type.
Portfolios.
The Idea Management domain includes portfolios (contents and properties). You can use the portfolios to filter and group the investment data by portfolio when building ad hoc views.
For example, you created a portfolio in
Clarity
 with 100 investments. In the Idea Management domain, you add Investment Name to the ad-hoc view (drag Investment Name from Fields to Columns in the New Ad Hoc View). Then drag Portfolio Name (from Fields) to the Filters, select the portfolio (that you created with 100 investments) from the drop-down, and click Apply. The ad hoc view now only shows the 100 investments in that selected portfolio. In this way, you are using Portfolios as a filtering method of reporting on your investment data.
You can also group your data by portfolio in the Idea Management domain. For example, you want to see the Total EAC Hours for the investments in each portfolio. You add (drag) Investment Name from the Fields area to Columns in the New Ad Hoc View. Then you drag Total EAC Hours from the Investment Totals in the Measures area to Columns in the New Ad Hoc View. Then you add Portfolio Name (from Fields) to Groups in the New Ad Hoc View. Your data is shown organized by portfolio in the format you selected (table, chart, pie diagram).
In the Idea Management domain, you are working with actual up-to-date investment data. You are not using a copy of the data as you use during portfolio planning in
Clarity
. Therefore, the Idea Management domain data does not match the data in the
Clarity
 portfolios that you use for portfolio planning. Portfolio planning uses a copy of the actual investment data.
Custom Fields.
If you have custom fields that are related to ideas, these fields appear in a Custom folder in the Idea Management domain. This domain can have multiple Custom folders. For example, Team custom fields appear in the Team Custom folder.
Project Management Domain
The Project Management domain contains information about projects and programs that are related to the Project object. This information includes investments, teams, financials, issues, risks, and change requests. Change requests include metrics (under Measures), but issues and risks do not include metrics. This domain also contains tasks and assignments, with summary-level data (totals) for both objects. The financial attributes in this domain are project summary level and not cost plan level. You can find detailed financial information at the cost plan level in the Financial Management domain.
Custom attributes and subobjects for the investment and project objects are included in this domain. They appear combined in a Custom set. No distinction exists between the attributes and subobjects that belong to the investment and those that belong to the project.
This domain includes properties that apply specifically to the Project object. These properties appear in the General set.
The Portfolio properties are used for filtering projects by portfolios. You can see the projects that are associated with each portfolio. This domain does not contain aggregated data.
The Project Management domain contains two main types of data: investment-level financial data (summarized for the total Investment and divided into periods) and team data (at the team level and by calendar periods). The domain has general information, financial information, OBS information, and team information for all team members in an investment.
The Project Management domain does not have detailed Cost Plan or actual transaction detail data. See the Financial Management domain for that information.
Data security
. Data security is determined by project-level access rights. If you have rights to view a project in
Classic PPM
, then you see all data that is related to that project in this domain, including all subobject data that is enabled for the data warehouse.
Do not mix object types
when selecting from Fields and Measures. If you select Investment Name in the Fields area, select a total under the Investment Totals in the Measures area. Selecting a total from a different Measures object category (for example, Team Totals) could produce unexpected results. For Investment data, use investment fields and investment measures. To use Team data when creating an ad hoc view, select a team member field from the Team folder under Fields and use a team amount from the Team folder under Measures. In general, use Investment data (Fields) with Investment metrics (Measures) and use Team data (Fields) with Team metrics (Measures).
Use Team data when you want specific data about a team and its members (for example, resources or allocation start dates). However, for Baseline hours, do not use Team data. You can find total Baseline hours summed under Investment data.
If you want to add a task to an ad hoc view and you want to view the data by resource and task, add the Assignment Resource to the view. If you add the Team Resource (instead of the Assignment Resource), the resulting data is inaccurate. If you want to view team data (without task data) by resource, add the Team Resource to the view.
Do not mix calendar types.
When you look at periodic data (for example, monthly data), do not mix calendar types when making ad hoc view selections. For example, use calendar period measures (Measures area) for calendar period fields (Fields area) and use fiscal period measures (Measures area) for fiscal period fields (Fields area). Also, do not mix the period types (week, calendar, fiscal). Otherwise, you get unexpected results because the data is repeated for each period type.
Portfolios.
The Project Management domain includes portfolios (contents and properties). You can use the portfolios to filter and group the investment data by portfolio when building ad hoc views.
In the Project Management domain, you are working with your actual up-to-date investment data (not a copy of the data as you use when doing portfolio planning in
Classic PPM
).
For example, you created a portfolio in
Classic PPM
 with 100 investments. In the Project Management domain, you add Investment Name to the ad-hoc view (drag Investment Name from Fields to Columns in the New Ad Hoc View). Then drag Portfolio Name (from Fields) to the Filters, select the portfolio (that you created with 100 investments) from the drop-down, and click Apply. The ad hoc view now only shows the 100 investments in that selected portfolio. In this way, you are using Portfolios as a filtering method of reporting on your investment data.
You can also group your data by portfolio in the Project Management domain. For example, you want to see the Total EAC Hours for the investments in each portfolio. You add (drag) Investment Name from the Fields area to Columns in the New Ad Hoc View. Then you drag Total EAC Hours from the Investment Totals in the Measures area to Columns in the New Ad Hoc View. Then you add Portfolio Name (from Fields) to Groups in the New Ad Hoc View. Your data is shown organized by portfolio in the format you selected (table, chart, pie diagram).
In the Project Management domain, you are working with actual up-to-date investment data. You are not using a copy of the data as you use during portfolio planning in
Classic PPM
. Therefore, the Project Management domain data does not match the data in the
Classic PPM
 portfolios that you use for portfolio planning. Portfolio planning uses a copy of the actual investment data.
Custom Fields.
If you have custom fields that are related to projects, these fields appear in a Custom folder in the Project Management domain. This domain can have multiple Custom folders. For example, Team custom fields appear in the Team Custom folder.
Resource Management Domain
The Resource Management domain includes information about investments, resources, teams and assignments, and task fields from the resource perspective.
Data security
. Data security is determined by resource-level access rights. If you have rights to view a resource in
Classic PPM
, then you see all data that is related to that resource in this domain. You can also see all subobject data that is enabled for the data warehouse.
Do not mix calendar types.
When you look at periodic data (for example, monthly data), do not mix calendar types when making ad hoc view selections. For example, use calendar period measures (Measures area) for calendar period fields (Fields area) and use fiscal period measures (Measures area) for fiscal period fields (Fields area). Also, do not mix the period types (week, calendar, fiscal). Otherwise, you get unexpected results because the data is repeated for each period type.
Time Management Domain
The Time Management domain contains information about created timesheets and missing timesheets. Use this domain if you are managing timesheets. This domain provides timesheet details at the date worked level. All created timesheets for all statuses are included in this domain. Incidents are also included in this domain.
This domain does not contain aggregated hours for a project or investment. For aggregated data, use the Investment Management domain.
If you do not use the integrated application timesheets for timekeeping, you can see the fields in this domain, but the fields have no data.
Data security
. Data security is determined by timesheet-level access rights. If you have rights to view a timesheet in
Classic PPM
, then you see all data that are related to that timesheet in this domain, including all subobject data that is enabled for the data warehouse.
Missing Timesheets.
This domain includes missing timesheets. You can view a specific resource by period and you can see the timesheets that were not created for that resource. The domain does not include missing time entries on a created timesheet.
If you forgot to create an entire timesheet for a given time period, that missing timesheet appears under Missing Time (in the Fields area). However, if you forgot to complete some of the time entries on an existing timesheet, those time entries do not appear under Missing Time. To see all time entries (entered hours and missing entries) in existing timesheets, look under the Timesheets set. Any missing time entry from an existing timesheet appears there.
Financial Management Domain
The Financial Management domain lets financial managers view financial data. This domain includes OBS and Investment data. The domain includes only fiscal time periods (not calendar or weekly time periods). All metrics (under the Measures area of the Ad Hoc Viewer/Editor) are fiscal.
This domain contains detailed financial planning data, including cost plans, cost plan details, benefit plans, benefit plan details, and WIP transaction details. The domain includes the data at a plan level (in the Financial Plans set under Investments in the Fields area of the Ad Hoc View/Editor). You can view the data for an actual plan of record or an actual Benefits plan.
This domain does not include invoicing or chargeback data.
Some of this financial planning data is also available in the Investment Management domain as a subset of the investment data.
If you do not use Financial Management, you can see the fields in this domain, but the fields have no data.
The Financial Management domain includes detailed financial planning data under Financial Plans. The domain also includes break-ups, such as charge codes. WIP transaction data is included at the transaction level. A row is included for every transaction (at the detail level not at the summary level).
Data security
. Data security is determined by financial plan-level access rights. If you have rights to view a financial plan in
Classic PPM
, then you see all data that are related to that financial plan in this domain. You can also see all subobject data that is enabled for the data warehouse.
Do not mix metric types
when selecting from Fields and Measures. If you select a total under the Investment Totals in the Measures area, do not also select a Transaction Measure under the WIP Transactions in the Measures area. This combination could produce unexpected results. When selecting a Measure in the Financial Management domain, select either Investment Totals or WIP Transactions, but not both simultaneously.
You cannot look at the investment-level summary financial data using detailed financial planning metrics. At the detail level, you have a row of data for each financial plan. All the financial plans for a project are available. To view only the POR plan data, for example, use the filter. Otherwise, you get duplicated or triplicated numbers.
Data that is shown under Investment Totals (Measures area) is investment-level data. Data that is shown under Financial Plans or Fiscal Periods (Fields area) is detail-level data. Data that is shown under WIP Transactions (Fields and Measures areas) is transaction-level data. Data that is not shown under Fiscal periods is total (summary/investment level) data.
Do not mix calendar types.
When you look at periodic data (for example, monthly data), do not mix calendar types when making selections. For example, use calendar period measures (Measures area) for calendar period fields (Fields area) and use fiscal period measures (Measures area) for fiscal period fields (Fields area). Also, do not mix the period types (week, calendar, fiscal). Otherwise, you get unexpected results, because the data is repeated for each period type.
Project Plans.
As you include financial plans in your Ad Hoc View, you notice that there are multiple plans for each investment project. You do not only see the plan of record. You see all plans for the investment. To view only the plan of record, use a filter.
Custom Fields.
If you have custom fields that are related to financial planning, these fields appear in a Custom folder in the Financial Management domain. This domain can have multiple Custom folders. For example, Team custom fields appear in the Team Custom folder.
Custom Master Objects Domain
The Custom Master Objects domain contains information about custom master objects and their child objects. This domain also includes the Language subobject and fields. Your administrator makes these objects data warehouse-enabled, and they are then included in the Custom Master Objects domain.
Custom Master Objects do not have parent objects and so are not related to any other objects in
Classic PPM
.
This domain contains custom master objects and their children. These objects are not related to any other object in
Classic PPM
. Each custom object has a corresponding set in this domain. The custom object name is also the set name. The objects in this domain are not related to each other.
View one custom master object at a time.
When you select the Custom Master Object domain for viewing in the Ad Hoc Viewer/Editor, select one of the custom master objects to view. You cannot view data for multiple custom master objects simultaneously, because the custom master objects do not have relationships with each other.
Data security
. Data security is determined by custom master object-level access rights. If you have rights to view a custom master object in
Classic PPM
, then you see all data that is related to that custom master object in this domain. You can also see all subobject data that is enabled for the data warehouse.
Do not mix calendar types.
When you look at periodic data (for example, monthly data), do not mix calendar types when making selections. For example, use calendar period measures (Measures area) for calendar period fields (Fields area) and use fiscal period measures (Measures area) for fiscal period fields (Fields area). Also, do not mix the period types (week, calendar, fiscal). Otherwise, you get unexpected results because the data is repeated for each period type.
Data Warehouse Database Schema
Schema information for
Classic PPM
 and the data warehouse is available on the Advanced Reporting and Database Schema Index page. You can download and view the following information:
  • Database schema information for the application and data warehouse
  • An ERD diagram for the data warehouse
  • Advanced Reporting domain field descriptions
  • PMO Accelerator add-in information
  • Jaspersoft Studio Professional Client and Report Development Guide