Skip to content
  • There are no suggestions because the search field is empty.

Oracle Primavera Unifier Integration

Sync Projects, Business Processes, and Cost Data into Cascade

Overview

The Oracle Primavera Unifier Integration allows you to automatically pull structured execution data from Unifier into Cascade so your strategic plan stays aligned with delivery and project controls.

Instead of manually updating Cascade, this integration can sync:

  • Business Process (BP) records (e.g., Issues, Risks, Change Requests, Contracts)
  • Cost data (Cost Sheets / Cost structures)
  • Shells (Unifier “projects” / containers)
  • Supporting reference data (CBS codes, etc.)

Unifier integrations are supported through RESTful APIs and Web Services.

Refer to link below;

https://docs.oracle.com/cd/F25628_01/English/Integration_Documentation/integration/helpmain.htm?toc.htm?10280474.htm

How it Works

Option 1 — Scheduled Pull via Unifier REST APIs (Recommended)

Cascade queries Unifier on a schedule (e.g., hourly/daily) to pull required records and then updates the mapped items in Cascade.

Option 2 — On-Prem: REST APIs + Network Access (Common Enterprise Setup)

If Unifier is hosted on-prem behind a firewall, the integration still uses REST APIs, but your IT team must ensure the Unifier REST endpoint is reachable from the integration runtime (via allowlisting).

Unifier services are sent/received over HTTPS.

Authentication

Unifier REST integrations must be executed using an Integration User (not a regular end-user login flow). Oracle explicitly states that “all REST services should be accessed via Integration User” and provides the UI path to create one.

There are two common authentication patterns:

Option A — Basic Authentication (Common, especially for On-Prem)

Use when: your Unifier environment is configured for Basic authentication for REST APIs.

Oracle provides guidance for setting up integration users for basic authentication and indicates you create an integration user and enable module permissions for that user.

Refer to link below; 

https://docs.oracle.com/cd/F88970_01/English/Integration_Documentation/integration/10312804.htm

What you provide to Cascade

  • Unifier base URL (customer-specific)

  • Integration username + password

  • Confirmation the integration user has permission to the required modules/shells/BPs

Option B — Token-Based Authentication (OAuth/JWT token for REST services)

Use when: your Unifier configuration requires a token for REST API access.

Oracle documents a token endpoint for generating a token to access REST services (example: GET /ws/rest/service/v1/oauth/token) and describes using Basic Auth (integration username/password) to request the token.

Refer to link below;

https://docs.oracle.com/cd/F46346_01/English/integration/10312797.htm

What you provide to Cascade

  • Base URL

  • Integration user credentials (used to request the token)

  • Any token configuration details required by your deployment

Data Sync

Unifier data is organized differently than typical project management tools. Unifier commonly exposes execution/control data through:

Shells (Projects / Containers)

Shells represent project containers where Business Processes and Cost structures live.

Unifier’s REST/web service methods include “Get” operations for Shell attributes and lists.

Business Process (BP) Records

BPs are configurable workflows (e.g., Risks, Issues, Change Orders, RFIs, Contracts). The Integration Interface Guide provides REST API details for BP actions like create/update/get records and supports rules/validation based on the BP forms.

Cost Sheet Data

Unifier includes REST methods for Cost Sheet operations (e.g., retrieving/updating column data, snapshots, work packages depending on configuration/version).

Recommended Mapping into Cascade

Because Unifier is highly configurable, the best practice is to map based on stable identifiers and agreed KPIs.

A typical mapping approach:

  • Unifier Shell → Cascade Objective / Initiative container (depending on your Cascade structure)
  • Unifier BP record (Issue/Risk/Change) → Cascade Action or Work Item
  • Unifier Cost Sheet values → Cascade Measures (numeric KPIs)

Always store Unifier record identifiers (IDs) as the stable key for ongoing sync, rather than relying on names/titles which can change.

Scheduling & Incremental Logic

Most Unifier integrations run on a fixed schedule.

Recommended best practices:

  • Sync only relevant shells/projects (avoid pulling entire instance)
  • Filter BP records by status and/or updated date where available
  • Keep schemas deterministic: define exactly which fields will be extracted for each BP type

Unifier REST services transmit over HTTPS and require appropriate certificate trust.

Customer Checklist

To implement the integration quickly, please provide:

A) Environment
  • Unifier deployment type: Cloud or On-Prem
  • Unifier version (if known)
B) Authentication
  • Confirm whether your environment uses:
    • Basic Authentication, or
    • Token-based authentication (OAuth/JWT token)
  • Provide integration credentials (service account)
C) Scope
  • Which Shell(s) to include
  • Which Business Process(es) to include (e.g., Risks, Issues, Change Requests)
  • Any required Cost Sheet structures / columns to include
D) Mapping
  • Where these should map inside Cascade (Plan / Focus Area / Objective)
  • Status mapping rules (Unifier status → Cascade status)
  • KPI definitions for any numeric measures
E) Schedule
  • Desired sync frequency (hourly/daily)

Troubleshooting Tips

  • 401 Unauthorized

    • Wrong credentials, wrong auth method (Basic vs token), or inactive integration user

    • Validate Basic Auth header generation and ensure integration user is active

  • 403 Forbidden

    • Integration user lacks module/shell/BP permissions

    • Ensure module permissions are enabled for the integration user

  • Timeout / Cannot reach endpoint (On-Prem)

    • Network routing not established (allowlist)