Oracle Primavera Unifier Report Extraction with Oracle Integration Cloud (OIC)

We designed and implemented an integration solution between Oracle Primavera Unifier and Oracle Fusion Applications using Oracle Integration Cloud (OIC), enabling the automated extraction of User Defined Report (UDR) data through scheduled processes and its seamless delivery to Fusion Applications.

Oracle Primavera Unifier serves as the source system, where User-Defined Reports are generated based on business process data and user-defined parameters.

Oracle Integration Cloud (OIC) acts as the integration layer, orchestrating the data flow, applying transformations and facilitating secure and seamless connectivity between Unifier and Oracle Fusion Applications.

Oracle Fusion Applications is the destination where the processed report data is delivered. This enables further business processing, reporting, or financial analysis within the Fusion ecosystem.

Reports Integrated and Corresponding Fusion Modules

UDR Type	Fusion Module	Submodule / Use Case
Budget	Oracle Fusion Financials / PPM	Budgetary Control, Project Costing
Invoice	Oracle Fusion Financials	Accounts Payable (AP)
Purchase Order	Oracle Fusion Procurement	Purchasing
Purchase Order Acknowledgements	Oracle Fusion Procurement	Supplier Portal, PO Acknowledgement
Change Orders	Oracle Fusion Project Portfolio Management (PPM)	Project Costing, Contract Adjustments
Contracts	Oracle Fusion PPM / Fusion Contracts	Project Contracts, Enterprise Contract Management

This integration enables stakeholders to maintain consistent, real-time data between Unifier and Fusion systems, reducing manual intervention and ensuring data accuracy across financial and project domains.

Exporting Projects from P6 EPPM: Manual and Automated Approaches

Oracle Primavera P6 EPPM offers robust capabilities for managing complex projects. One of its essential features is the ability to export projects, along with their baselines, into XML or XER file formats. This functionality is available through both the P6 web interface and P6 Professional.

To export project in P6 web interface, you choose Export Type format, Add Projects, choose Baselines and Export. Once the background process is completed, the export file is ready and available for download. You download the file and store it locally. While this process is easy to follow, it’s entirely manual. That means every time you need a backup or want to share a project, you must repeat these steps.

P6 EPPM data is stored in the database. Although databases are backed up at regular intervals, restoring a single project from the backed-up database copy may not be easy and convenient in a production environment. Having a copy of projects as files makes it convenient to restore in case the need arises.

There can be several reasons for exporting the project to a file

• Share with stakeholders – client, contractor, etc., who do not have P6 access.
• Restoring a project in case of accidental deletion or data corruption.
• Creating a backup before making major schedule changes.
• Archiving completed project.
• Audit requirement to retain a copy for extended period.
• Data migration between environment like production to non-production.
• Troubleshooting issues by sharing a copy with support team.

If you are comfortable writing a bit of code, then you can automate project export using P6 Web Services or P6 Rest API. They both use the same access control as P6 application. This works for both on-premises and Oracle SaaS implementation of P6 EPPM. 

Why choose programmatic project export?

• Daily Backups: Planners and schedulers can automate daily exports to their desktops.
• Automated Archival: Projects can be archived automatically based on criteria (e.g., two weeks after closure).
• Bulk Export for Migration: Export hundreds of projects based on pre-identified criteria.
• Scheduled Jobs: Run exports at regular intervals on Windows or Linux servers.
• Concurrent Exports: Export multiple large projects simultaneously to save time.
• GZIP Compression: Reduce file size for large projects during export and optimize storage.

To realize all the benefits listed above, we have developed a lightweight, configurable program using P6 rest API. It can export multiple projects of any sizes concurrently. It can be called ad-hoc or scheduled to run at pre-determined interval on Windows or Linux box. It can be used to export all projects in the P6 environment or selective few based on identified criteria. Each time the program runs, it stores project in a separate folder and avoid overriding the previously exported project. It can be used for data migration, bulk export, P6 data merge, archival, etc. 

It does not require any tool or utility installation. It can be used instantly by completing few configuration details.

What is your use case to automate export project in Oracle Primavera P6 EPPM?