There is a large amount of DATA displayed within P6 that is calculated on the fly and not stored in the project management database (PPMDB or EPPMDB). As a result Oracle introduced the concept of a reporting database external to the project management database. This is optimised for reporting purposes and contains fields storing calculated values. In versions prior to R8.1 the creation and updating of the reporting database required an administrator to set up several additional DATABASES and configure standalone scripts to carry out the ETL (EXTRACT, transform, load) operations. From P6 EPPM R8.1 the reporting database schema forms part of the standard EPPMDB database, and the scheduled publishing of data is administered from within the product.

Once the publishing of data to the reporting database has been configured, any external reporting tool (e.g. PCF's QEI Management Reporting or CRYSTAL Reports) can be used to extract data from it.

There is a large amount of data displayed within P6 that is calculated on the fly and not stored in the project management database (PPMDB or EPPMDB). As a result Oracle introduced the concept of a reporting database external to the project management database. This is optimised for reporting purposes and contains fields storing calculated values. In versions prior to R8.1 the creation and updating of the reporting database required an administrator to set up several additional databases and configure standalone scripts to carry out the ETL (extract, transform, load) operations. From P6 EPPM R8.1 the reporting database schema forms part of the standard EPPMDB database, and the scheduled publishing of data is administered from within the product.

Once the publishing of data to the reporting database has been configured, any external reporting tool (e.g. PCF's QEI Management Reporting or Crystal Reports) can be used to extract data from it.