1 About This Accelerator

This accelerator provides a ready-to-deploy integration project that automates data synchronization between Primavera P6 Enterprise Project Portfolio Management (P6 EPPM) and Primavera Unifier.

It streamlines the flow of synchronization for both global reference data (resources, roles, work rates) and project schedule data (WBS, activities, assignments), and can also push actual activity dates captured in Primavera Unifier back into Primavera P6 EPPM to keep both systems aligned.

Note:

This accelerator is available as P6 EPPM — Primavera Unifier | Integrate Resources and Schedule in the Integration store.

Purpose

The purpose of this accelerator is to:

  • Integrate resources, roles, and work rates from Oracle Primavera P6 EPPM into Primavera Unifier's master rate sheet to standardize costing and enable downstream schedule/cost flows.
  • Synchronize schedule data (WBS, activities, assignments) from Oracle Primavera P6 EPPM to Primavera Unifier.
  • Optionally synchronize actual dates for activities captured in Primavera Unifier back to Oracle Primavera P6 EPPM.

Delivered Integrations

This accelerator delivers a project that includes multiple pre-built integrations.

Main Integrations

  1. Oracle P6 Unifier Resources Roles Sync

    Synchronizes global resources, roles, and their associated work rates from Primavera P6 EPPM to Primavera Unifier (master rate sheet).

  2. Oracle P6 Unifier Activities Sync

    Retrieves project details from Primavera P6 EPPM (EPS structure) and synchronizes WBS, activities, and assignments to Primavera Unifier.

  3. Oracle Unifier P6 Activity Actuals Sync

    Synchronizes actual start/finish dates for activities recorded in Primavera Unifier back to Primavera P6 EPPM.

Dependency

Always run Oracle P6 Unifier Resources Roles Sync first. This is because Oracle P6 Unifier Activities Sync requires resources/roles/rates to exist in Primavera Unifier.

Additional Helper Integrations

  • Oracle P6 Unifier Activities Sync Scheduler

    Scheduled wrapper that triggers Activities Sync at predefined intervals with the required Primavera P6 EPPM and Primavera Unifier project identifiers. Use this for unattended, periodic schedule updates.

  • Primavera Unifier Status Update Service

    Publishes integration job-status updates from Oracle Integration to Primavera Unifier. For integrations that support it, enables optional progress notifications so end users can see Started / In Progress / Completed / Failed directly in the Primavera Unifier user interface.

Integration Workflows Overview

The following sections describe the high-level behavior of each integration. For request payloads and detailed run steps, see Activate and Run the Accelerator.

Integrate Resources and Roles (Global Integration)

  1. Trigger
    • The integration is initiated by sending a request to the deployed integration in Oracle Integration.
    • The request can optionally include filters to limit synchronization to specific resources or roles.
  2. Initialization
    • Oracle Integration validates input parameters and prepares required runtime variables.
  3. Data retrieval
    • The integration queries Oracle Primavera P6 EPPM for resources, roles, and their associated work rates.
  4. Data creation/update
    • The retrieved records are created or updated in Primavera Unifier's master rate sheet.
    • Partial success handling - if individual records fail, the integration logs those items for audit while continuing with remaining data.
  5. Completion summary
    • A final synchronization summary is presented, showing counts of successful and failed records.

Note:

  • Unique IDs: Each resource ID and role ID must be unique. Primavera Unifier does not allow duplicate identifiers.
  • Single work rate: Each resource/role supports only one work rate value (pricePerUnit1) because Primavera Unifier does not allow multiple work rates under the same cost and rate type.

Integrate WBS, Activities, and Assignments (Schedule Integration)

  1. Trigger
    • The integration starts when a request is sent to the Oracle Integration-deployed integration, specifying both the Oracle Primavera P6 EPPM project ID and the Primavera Unifier project number for synchronization.
    • The request can optionally include options to also sync the current baseline from Oracle Primavera P6 EPPM or delete Primavera Unifier WBS/activities/assignments not present in Oracle Primavera P6 EPPM (full refresh)
  2. Initialization
    • Oracle Integration validates input parameters and prepares required runtime variables.
  3. Project linking
    • The integration reads project data from Oracle Primavera P6 EPPM (EPS structure) and establishes the link to the corresponding Primavera Unifier project.
    • Once linked, this relationship appears under the project's Gateway tab in Primavera Unifier.
  4. Data retrieval
    • Oracle Integration fetches schedule data from Oracle Primavera P6 EPPM, including:
      • Work breakdown structure (WBS)
      • Activities
      • Assignments
  5. Data creation/update
    • The integration creates or updates the above records in Primavera Unifier respected sheets.
    • For assignments, it cross-references resources and roles from Primavera Unifier's master rate sheet to maintain correct associations.
  6. Optional baseline sync
    • If baseline synchronization is requested, the current baseline set in Oracle Primavera P6 EPPM is also created or updated in Primavera Unifier, enabling baseline comparison within Primavera Unifier.
  7. Completion summary
    • The final report highlights how many records were synchronized and any items skipped due to errors.

Note:

  • WBS full refresh: Due to a current limitation, the integration cannot perform incremental WBS updates. Each run performs a complete refresh, deleting WBS records in Primavera Unifier that are no longer present in Oracle Primavera P6 EPPM.
  • Baseline uniqueness: Baseline project names should be unique across all projects to prevent naming conflicts.

Integrate Activity Actuals (Primavera Unifier to Oracle Primavera P6 EPPM)

  1. Trigger
    • The integration starts when a request is sent to the Oracle Integration-deployed integration, specifying both the Oracle Primavera P6 EPPM project ID and the Primavera Unifier project number for synchronization.
  2. Data retrieval
    • Oracle Integration reads activity data from the Primavera Unifier activity sheet.
    • The integration then queries Oracle Primavera P6 EPPM for project data.
  3. Update in Oracle Primavera P6 EPPM
    • The integration updates the corresponding activities in Oracle Primavera P6 EPPM with the latest actual dates.
  4. Completion confirmation
    • Results are logged in Oracle Integration and can be viewed via Integration Tracking.